• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [MetroPCS/CDMA] [HOWTO][ROOT]Automatic Root for SGSIII

I followed the directions and the root script succeeded, but I don't have root. I have rebooted the phone for good measure, but still no root.

Root Checker Basic report no root.
Titanium Backup can could not acquire root privileges using "/system/xbin/su".
Root Browser Lite shows the file "/system/xbin/su"

Model: SCH-R530M
Android: 4.0.4
Kernel version: 3.0.8-1131483
Build number: IMM76D.R530MVQALJ1
Hardware version: R530M.01

Any idea how to fix this?

The rooting script output:
[HIGH]Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...

Step 1 - Setup...
Copying files:
Copying su:
3303 KB/s (380532 bytes in 0.112s)

Copying debugfs:
3501 KB/s (1862336 bytes in 0.519s)

Copying debugfsinput:
3 KB/s (144 bytes in 0.042s)

...done copying files.


Linking /system to tmp...
...done linking /system


Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...


Step 2 - Rooting...

If you see the following error, you may ignore it:

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

This just means there were no existing root found on your phone.


* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...


debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: Allocated inode: 2091
debugfs: debugfs: debugfs: debugfs:


Cleaning up...

Restoring tmp...
...done restoring tmp

Removing files...
...done removing files.

Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...
Installing Superuser.apk...
4122 KB/s (1468798 bytes in 0.347s)
pkg: /data/local/tmp/Superuser.apk
Success

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...
Rebooting...

Once your Galaxy S III reboots one last time, it will be rooted!

If you are still unable to use root apps, try opening Superuser and checking
for binary updates. You might also try rebooting one more time.
[/HIGH]
 
cpelliott said:
I followed the directions and the root script succeeded, but I don't have root. I have rebooted the phone for good measure, but still no root.

Root Checker Basic report no root.
Titanium Backup can could not acquire root privileges using "/system/xbin/su".
Root Browser Lite shows the file "/system/xbin/su"

Model: SCH-R530M
Android: 4.0.4
Kernel version: 3.0.8-1131483
Build number: IMM76D.R530MVQALJ1
Hardware version: R530M.01

Any idea how to fix this?

The rooting script output:
[HIGH]Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...

Step 1 - Setup...
Copying files:
Copying su:
3303 KB/s (380532 bytes in 0.112s)

Copying debugfs:
3501 KB/s (1862336 bytes in 0.519s)

Copying debugfsinput:
3 KB/s (144 bytes in 0.042s)

...done copying files.


Linking /system to tmp...
...done linking /system


Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...


Step 2 - Rooting...

If you see the following error, you may ignore it:

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

This just means there were no existing root found on your phone.


* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...


debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: Allocated inode: 2091
debugfs: debugfs: debugfs: debugfs:


Cleaning up...

Restoring tmp...
...done restoring tmp

Removing files...
...done removing files.

Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...
Installing Superuser.apk...
4122 KB/s (1468798 bytes in 0.347s)
pkg: /data/local/tmp/Superuser.apk
Success

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 0 seconds
Maybe we should let it breathe for a while? 10 seconds...
Rebooting...

Once your Galaxy S III reboots one last time, it will be rooted!

If you are still unable to use root apps, try opening Superuser and checking
for binary updates. You might also try rebooting one more time.
[/HIGH]
Click to expand...

Not to sound stupid but did you open superuser and check for binary updates as suggested?
 
Same here first time I rooted it Root would not take. I had to open Su and do a binary update then all was good.
 
confed said:
Not to sound stupid but did you open superuser and check for binary updates as suggested?
Click to expand...
Thanks, that was it. I was trying to run /system/xbin/su from a file browser, which didn't work. Once I found the superuser app and did the suggested update, everything works.
 
when you say unplug everything else off the computer, does this apply to the little logitech usb thing for my wireless mouse? I assume not because then i would have no mouse but i figured id ask.

Edit: So i went ahead and ran the script but it seems to freeze at "checking for device". I installed the drivers and i did restart my computer for it to work properly and the drivers work. What could be the problem?
 
toke_ said:
when you say unplug everything else off the computer, does this apply to the little logitech usb thing for my wireless mouse? I assume not because then i would have no mouse but i figured id ask.

Edit: So i went ahead and ran the script but it seems to freeze at "checking for device". I installed the drivers and i did restart my computer for it to work properly and the drivers work. What could be the problem?
Click to expand...

You should not have to unplug your mouse.
Just any other phone/telephony equipment connected to the USB ports that can interact with adb. Basically, it makes it simpler if there is one device adb detects, because otherwise, we need to specify the device with each command. Too much complication in the code, and for no great benefit.
As for your "checking for device" bug, sounds like windows being windows.
Try rebooting again, disable your firewall and/or temporarily disable your antivirus, and turn them back on once the script is done.
 
I'm using ubuntu and in the terminal it keeps saying that there is an error loading shared libraries. no such files exist

then it says device not connected plug or replug in the usb cable.

my computer picks up my phone every time i plug it in so i don't know what the problem is.
 
Thank you so much!

Am an old time Android user. I was weary of trying rooting or custom roms for my S3 mainly because of the hassle (me being lazy) some methods are and the fact that I liked the stock rom (somewhat). Now I can redownload my paid root apps and back up some stuff/mess around.

Thank you once again! For those who are scared. Just download the zip and drivers and follow the instructions posted on page 1, post #2.
 
finally decided to root my s3 and my laptop gave me a bsod twice...i switched from the usb 3.0 port to the regular usb port and it worked fine
 
 
 
When I root my s3 will it stop me from doin the update that metropcs is dropping next month?.........please help because that is the only thing holding me back from doing the root
 
tiede said:
Some people (me, for one) want to remain on stock recovery for the time being... So, this is our best option.
Until the STOCK non-root image is uploaded and confirmed working on someone else's phone besides mine, i'm stuck with stock! ;)
Click to expand...
Will the root stop me from doing the update that metropcs is dropping next month?
 
 
You must log in or register to reply here.
Back
Top Bottom