Tried rooting 3 times and I'm not getting root

O.G Incredible

Well-known member
Aug 23, 2010
176
78
0
I tried using cory's method , tried 3 times and all 3 times I failed.
I think this is the reason....

- If it is "system" or "data", only the corresponding partition
is updated.

c:\TBroot>adb shell chmod 777 /data/local/psneuter

c:\TBroot>adb shell /data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\TBroot>adb shell mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system

c:\TBroot>adb shell /data/local/busybox cp /data/local/su /system/xbin/su
/data/local/busybox: permission denied

c:\TBroot>adb shell chown 0:0 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory

c:\TBroot>adb shell chmod 6755 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory

c:\TBroot> adb reboot

c:\TBroot>

what am i missing???
 
This is the last of the three (3) times you startup ADB... you did not have any issues with any of the previous steps???
 
By the way... it's not nice to double post!!!

http://forum.androidcentral.com/thunderbolt-rooting-roms-hacks/72524-procedure-how-root-thunderbolt-adb-windows-48.html#post1073088

Something must have gone wrong earlier... or you would not have a permissions issue 3 or 4 command lines from the end... sorry, I don't know enough about ADB to be any more help... this procedure worked for me just fine.

yes i know sorry. i shouldve posted a new thread instead of posting on the last page of the rooting thread... i wont do it again :p
thanks for trying though. i wish i new what went wrong. :confused:
 
Each time you try, are you starting all the way at the beginning?

Make sure when you do the first part, you are using the correct DOWNGRADE ruu, and then switching to the upgraded one for the second part.
 
  • Like
Reactions: O.G Incredible
Each time you try, are you starting all the way at the beginning?

Make sure when you do the first part, you are using the correct DOWNGRADE ruu, and then switching to the upgraded one for the second part.

Yes I start all the way from the beginning and I get the error messages at the end. It's almost like those 3 last files are corrupted ??


Sent from my ADR6400L using Tapatalk
 
Sorry, just covering all the bases... did you download and reinstall the ADB version on your PC?
 
i'm far from a expert on this stuff, but did your phone have that over the air update and if so maybe that is causing a issue?
 
If those very long numbers matched up... even with the OTA... it does work... it worked for me after the OTA.

I'd try the Auto Root method.
 
  • Like
Reactions: blizz419
Long numbers?

Sent from my ADR6400L using Tapatalk

First when you entered
> adb shell /data/local/busybox md5sum /data/local/misc.img
The Command window must display the following checksum: c88dd947eb3b36eec90503a3525ae0de

Second when you entered
> adb shell /data/local/busybox md5sum /data/local/hbooteng.nb0
The command window must display the following checksum: 6991368ee2deaf182048a3ed9d3c0fcb

Both of which were in RED Warning boxes.
 
First when you entered
> adb shell /data/local/busybox md5sum /data/local/misc.img
The Command window must display the following checksum: c88dd947eb3b36eec90503a3525ae0de

Second when you entered
> adb shell /data/local/busybox md5sum /data/local/hbooteng.nb0
The command window must display the following checksum: 6991368ee2deaf182048a3ed9d3c0fcb

Both of which were in RED Warning boxes.

Oh yeah those numbers dis matched. Maybe I will try the auto root. Which it sucks because I see all these people saying they got the adb root to work and I can't. I just want to figure out what I'm doing wrong ??

Sent from my ADR6400L using Tapatalk
 
you could always try to reformat your cpu, download everything you need and get adb set up, factory reset your phone/revert to stock with the directions jcase posted on xda, and follow every direction for the root process like crazy - if you really want it to work manually. Theres no reason it shouldn't work basically.
but the same with the auto root. It just does the work for you.
This auto root thread by droidxcon is the S$$$*. http://forum.androidcentral.com/thu...unroot-windows-updated-5-20-w-mr1-update.html



WAIT EDIT
You're trying to do this on a mac right> ? My bad.
I actually used a mac and i followed Cory Steater's guide which is awesome. Everything i wrote above still stands, except for DroidXcon's link doesn't apply if you're using a mac.
 
  • Like
Reactions: O.G Incredible
you could always try to reformat your cpu, download everything you need and get adb set up, factory reset your phone/revert to stock with the directions jcase posted on xda, and follow every direction for the root process like crazy - if you really want it to work manually. Theres no reason it shouldn't work basically.
but the same with the auto root. It just does the work for you.
This auto root thread by droidxcon is the S$$$*. http://forum.androidcentral.com/thu...unroot-windows-updated-5-20-w-mr1-update.html



WAIT EDIT
You're trying to do this on a mac right> ? My bad.
I actually used a mac and i followed Cory Steater's guide which is awesome. Everything i wrote above still stands, except for DroidXcon's link doesn't apply if you're using a mac.

No I'm on windows 7. So ill do a factory reset tonight when I get home and download all the files again. If that doesn't work then I guess ill try the auto root. Is that auto root for MAC ??
I'll keep you guys posted

Sent from my ADR6400L using Tapatalk
 

Trending Posts

Forum statistics

Threads
956,844
Messages
6,970,280
Members
3,163,642
Latest member
microsofthope