Problems with Rooting S3 after Stock Restore

[Joseph Myers]

Hi, I recently returned to factory defaults (4.1.1) after trying out CM on my Galaxy S3. I am now trying to root my phone (and eventually create a backup), but I am having problems with Rootdebugfs (superuser and superSU). Here is the output of the superSU version:



Step 1 - Setup...

Copying chainfire's SU files:

Copying chainfire's SU:
failed to copy 'su' to '/data/local//su': Permission denied

Copying debugfs:
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied

Copying debugfsinput:
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied

...done copying files.


Linking /system to tmp...
failed on '/data/local/tmp' - Permission denied
link failed File exists
...done linking /system


Rebooting...


rm: File not found by ext2_lookup while trying to resolve filename

This just means there wasn't an existing root/SU found on your phone.


Press any key to continue . . .
* server not running *


Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory



Cleaning up...

Restoring tmp...
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
...done restoring tmp

Removing files...
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
...done removing files.

Rebooting...



Testing chainfire's SU file installation...
/system/bin/sh: /system/xbin/su: not found

uid and gid should both be 0.
Are they? (y/n): n

------------------------------------------------------------------------

Does anyone know why I'm missing those /system files?

 

[Kage87Z]

Hi, I recently returned to factory defaults (4.1.1) after trying out CM on my Galaxy S3. I am now trying to root my phone (and eventually create a backup), but I am having problems with Rootdebugfs (superuser and superSU). Here is the output of the superSU version:

I understand that debugfs does not work for 4.1.1.

Step 1 - Setup...

Copying chainfire's SU files:

Copying chainfire's SU:
failed to copy 'su' to '/data/local//su': Permission denied

Copying debugfs:
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied

Copying debugfsinput:
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied

...done copying files.


Linking /system to tmp...
failed on '/data/local/tmp' - Permission denied
link failed File exists
...done linking /system


Rebooting...


rm: File not found by ext2_lookup while trying to resolve filename

This just means there wasn't an existing root/SU found on your phone.


Press any key to continue . . .
* server not running *


Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory



Cleaning up...

Restoring tmp...
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
...done restoring tmp

Removing files...
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
...done removing files.

Rebooting...



Testing chainfire's SU file installation...
/system/bin/sh: /system/xbin/su: not found

uid and gid should both be 0.
Are they? (y/n): n

------------------------------------------------------------------------

Does anyone know why I'm missing those /system files?

 

[blade22222]

What method are you using to root? Also are you running 4.1.1?

Sent from my SCH-I535 using Android Central Forums

 

[Joseph Myers]

Well, I took it into the Verizon store and convinced them I needed a new phone. It took almost four hours, but I think it was worth it. I may try flashing CM again once Android 4.2 is stable.