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

Root [Revised] Rooting Gingerbread 2.3.5 Dummies Guide

Hey guys thanks for the help i figured out what i was doing wrong i wasnt going to sdk tools folder in the command prompt but now i have another problem lol on step 8 and 9 when i am suppose to type adb shell in the cmd it just brings up a $ automatically it doesnt say:

* daemon not running. starting it now on port 5037 *
*daemon started succesfully *
Copied from captin throwback
8) If "$" appears, you do not have root access. Type "su" to access root. "$" should change to a "#".
NOTE: If it doesn't change (though I don't know why it wouldn't), go to Market (signing into Google will be required), and download "Root Checker". Open Root Checker, and you should be prompted to allow root access. If successful, type "su" at the adb prompt again, and you should have root.
 
  • Like
Reactions: ocnbrze
Upvote 0
Copied from captin throwback
8) If "$" appears, you do not have root access. Type "su" to access root. "$" should change to a "#".
NOTE: If it doesn't change (though I don't know why it wouldn't), go to Market (signing into Google will be required), and download "Root Checker". Open Root Checker, and you should be prompted to allow root access. If successful, type "su" at the adb prompt again, and you should have root.
i have root but its not starting the daemon thing
 
Upvote 0
Hey my name is Jay and im new to all this and this forum. I have a HTC EVO 4g with the newest updates hboot 2.18 version 2.3.5 software 4.67.651.3. I was trying to root my phone so i came across this forum and seen the rooting Hboot 2.18 dummies guide and seen captain throwback steps to unlock your phone but i got to the part where you have to download two zip files mtd-eng.zip and flash_image.zip and extract the two but the files say they are invalid. what can i do
One of the files is attached to a post above. Try that one and see if it works. If it does, I'll post the other one here too. I really don't understand why people are having issues with the attachments.
 
  • Like
Reactions: ocnbrze
Upvote 0
Ok I'm trying to do Cap's guide but when I try to boot to recovery with superuser I get the HTC screen saying
Build : RZ-supersonic-v2.3
E:Can't read MISC:
(No space left on device)

Any help would be great.
That's not a good error. Did you have any issues up to that point? You might want to try re-flashing the recovery if it's not coming up all the way.
 
Upvote 0
Thanks everyone that helped!

One thing though idk if its just me but the part i got stuck at for ever lol. step 8 and 9 or somethin the directions make it seem like your suppose to run the adb shell from the " Android " folder the unlock boot loader tells you to make.
But really your suppose to run that list of commands from the sdk platform-tools folder. idk if its just me but thats what messed me up lol.

BUT THANKS AGAIN!!!
 
  • Like
Reactions: ocnbrze
Upvote 0
Reflashed the recovery and getting the same error when I go into the bootloader and select recovery

Build:RA-supersonic-v3.11-gnm
E:Can't read mic
(no space left on device)

Did you do a factory reset before you started?

i was just going to suggest that. now keep in mind this will delete all of your data. so backup accordingly, maybe mybackup pro(non rooted). i think at this point since you have unlocked your bootloader you can download the superuser app and titanium backup (tb) and use tb to backup your apps and data.
 
Upvote 0
ok i did flash_image and that file work but the other one is still saying error this is what it looks like

C:\android\sdk\android-sdk-windows\tools>adb shell
$ su
su
# cat /sdcard/flash_image > /data/flash_image
cat /sdcard/flash_image > /data/flash_image
# chmod 755 /data/flash_image
chmod 755 /data/flash_image
# /data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
error opening /sdcard/mtd-eng.img: No such file or directory
#

and the pc36img foryo is that the file that downloaded when i did my recovery. i use PC36IMG-ra-supersonic-3.11-gnm do i change that one to pc36img because when i try to download it from step 11 get a link to a page with a bunch of stuff but i cant find that file like i said im sorry im new at this im not dumb but just need a little help thank you
 
Upvote 0
ok i did flash_image and that file work but the other one is still saying error this is what it looks like

C:\android\sdk\android-sdk-windows\tools>adb shell
$ su
su
# cat /sdcard/flash_image > /data/flash_image
cat /sdcard/flash_image > /data/flash_image
# chmod 755 /data/flash_image
chmod 755 /data/flash_image
# /data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
error opening /sdcard/mtd-eng.img: No such file or directory
#

and the pc36img foryo is that the file that downloaded when i did my recovery. i use PC36IMG-ra-supersonic-3.11-gnm do i change that one to pc36img because when i try to download it from step 11 get a link to a page with a bunch of stuff but i cant find that file like i said im sorry im new at this im not dumb but just need a little help thank you
Sorry about that. I moved around some files on my Dropbox and broke some links. I'll upload the other file here.

EDIT: Here's the link to the Froyo PC36IMG.zip

EDIT 2: mtd img file attached.
 

Attachments

  • mtd-eng.zip
    1,003 bytes · Views: 138
  • Like
Reactions: ocnbrze
Upvote 0
Thanks everyone that helped!

One thing though idk if its just me but the part i got stuck at for ever lol. step 8 and 9 or somethin the directions make it seem like your suppose to run the adb shell from the " Android " folder the unlock boot loader tells you to make.
But really your suppose to run that list of commands from the sdk platform-tools folder. idk if its just me but thats what messed me up lol.

BUT THANKS AGAIN!!!
You're not supposed to run them from the platform-tools folder. In HTC's instructions, they tell you to create a folder and put adb & fastboot in it. Those are the only files you need to complete the process. If you didn't do that, then yes, you will have issues.
 
  • Like
Reactions: ocnbrze and jsticks
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones