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

Root GUIDE: From stock 1.5 to the latest root 2.1

mbrudolph said:
Well I have spent the last 6 hours messing around and researching the whole process. I am sure everything is being done properly (USB Debugging, Downloaded the USB Driver Update with Android SDK, etc). Simply it comes down to the fact my computer doesnt recognize the driver in the USB Driver Folder, when i try to install the driver.

Any clue as to why??
Click to expand...

Install HTC Sync, at least that solved my problem when I got into the same trouble.
 
anybody download the root image lately. I think I'm about to be pissed because when I downloaded it, and flashed it, I still had 2.1 on my phone. Software and baseband numbers line up with one of the leaks. hboot is now 1.49 up from 1.47 with ota. Please tell me that I haven't just inadvertantly downloaded a leak
 
jreed2560 said:
anybody download the root image lately. I think I'm about to be pissed because when I downloaded it, and flashed it, I still had 2.1 on my phone. Software and baseband numbers line up with one of the leaks. hboot is now 1.49 up from 1.47 with ota. Please tell me that I haven't just inadvertantly downloaded a leak
Click to expand...

if that didn't happen then it didn't work i am rooted and running the IC3 rom and it says 1.49 on HBOOT and i can always just go back to 1.5 or 2.1.

i hope
 
I've done a successful rollback to 1.5, I'm just not having as much luck with going back. And btw I realize now of course that the root img is 2.1 and not a rollback to 1.5. I just need to get this darned recovery image to flash

ok i've dl'd the recovery zip and extracted the files. I'm in the tools folder and running the cmd line. I have my phone connected, usb debugging check, charge only check, type adb shell to see if my phone is connected again, daemon started successfully. get an immediate # sign. type su and again get a # sign. Yet my phone has not asked me for permission to run su. I get no prompted on my phone to allow anything. Have I done this correctly? I think so

update: Ok I'm running apps that require su permission only I haven't been asked to allow anything, I am still stuck on installing recovery, and I tried rom manager from the market, but I can't get anything to work via the cmd line, I can see my device thru ddms so I know its not a connection issue. Can anyone help before I murder my phone?
 
Gotta Be Mac said:
Well, has anyone downloaded the Rooted rom in the past day or two? I definately do not want to accidently end up on a leak.
Click to expand...
thats a good effin question......... im getting ready to do this, i got the sdk crap done now and am about to root ... hmmmmm, also this will work if i have 2.1 ota already correct?. or should i go a different route?
 
mandirae16 said:
I have a question...Is the updated rooted rom at the beginning of this thread different that the custom roms that others have made? Do we have to have the updated rom or just a custom rom?
Click to expand...
thats what i want to know as well, hope to have an answer soon.
 
BlazeD OnE said:
Get the F*ck outta here really, I was just about to start rooting.. I have all the files downloaded..
Click to expand...

well dont let me stop ya im just sayin it might be
iv flashed fonez many times before and iv never had this much trouble plus in the hboot at the top it says "S-ON" which means leak does it not
 
jreed2560 said:
I've done a successful rollback to 1.5, I'm just not having as much luck with going back. And btw I realize now of course that the root img is 2.1 and not a rollback to 1.5. I just need to get this darned recovery image to flash

ok i've dl'd the recovery zip and extracted the files. I'm in the tools folder and running the cmd line. I have my phone connected, usb debugging check, charge only check, type adb shell to see if my phone is connected again, daemon started successfully. get an immediate # sign. type su and again get a # sign. Yet my phone has not asked me for permission to run su. I get no prompted on my phone to allow anything. Have I done this correctly? I think so

update: Ok I'm running apps that require su permission only I haven't been asked to allow anything, I am still stuck on installing recovery, and I tried rom manager from the market, but I can't get anything to work via the cmd line, I can see my device thru ddms so I know its not a connection issue. Can anyone help before I murder my phone?
Click to expand...

Ok so just to give everyone an update. I can't believe this made any difference at all, but I changed cables. I was using the standard data cable that came with the Eris. It has worked fine up to this point, but for some reason it would not do this. I change cables and viola it worked like a champ. OMG I was about to hurt someone or something!
 
jreed2560 said:
Ok so just to give everyone an update. I can't believe this made any difference at all, but I changed cables. I was using the standard data cable that came with the Eris. It has worked fine up to this point, but for some reason it would not do this. I change cables and viola it worked like a champ. OMG I was about to hurt someone or something!
Click to expand...

wow thats weird. the standard cable is the same as any mini usb cable its not like i has any extra pins
 
stinolan said:
well dont let me stop ya im just sayin it might be
iv flashed fonez many times before and iv never had this much trouble plus in the hboot at the top it says "S-ON" which means leak does it not
Click to expand...

Any confirmation of this? I really don't want to end up on a leak. What problem specifically are you stopped at. As of last night I just got through most of the Pre-reqs, but I got stopped at step 10 when it asks to punch in I believe sdb shell within the folder where your tools of android sdk is. I tried this and it says device is not found. USB debugging is on. I am howeabout using a standard usb cable that can be found on most Motorola and Garmin devices, not the cable that came with the phone which I think has a few more pins for audio/video? I think I read that in the forums somewhere. Would finding this other cable make a difference? I'm at the part looking to receive a "#" or "?" I believe.


update: Also, I'm very patient, so if this post is unanswered in a few days, take a stab at it, I'm in no rush to root. Measure twice, cut once.
 
Sorry to start a conspiracy theory. I've just been reading with all this OTA vs LEAK talk that it had alot to do with the leaks being on hboot 1.49. I forgot that the root image was a leak too (just an engineering rom leaked to us) I can confirm that you can root with the image posted in step 1 of the root process. I was simply having cable problems so adb commands were not functioning properly. I'm sorry if my freak out in anyway cast a shadow of doubt on this process. GRDLOCK did an amazing job with this and I don't want anyone to doubt his work.
 
Gotta Be Mac said:
Any confirmation of this? I really don't want to end up on a leak. What problem specifically are you stopped at. As of last night I just got through most of the Pre-reqs, but I got stopped at step 10 when it asks to punch in I believe sdb shell within the folder where your tools of android sdk is. I tried this and it says device is not found. USB debugging is on. I am howeabout using a standard usb cable that can be found on most Motorola and Garmin devices, not the cable that came with the phone which I think has a few more pins for audio/video? I think I read that in the forums somewhere. Would finding this other cable make a difference? I'm at the part looking to receive a "#" or "?" I believe.


update: Also, I'm very patient, so if this post is unanswered in a few days, take a stab at it, I'm in no rush to root. Measure twice, cut once.
Click to expand...

Try using a different cable than the one that came with the phone. I did and I got everything to work perfectly. Also make sure to read everything about making sure you java/bin directory is in your system path. That had me scratching my head for a half a day.
 
Alright, first off, I must say you people are so wonderful. I would also like to thank GRDLOCK for such a wonderful script and description for this process. I have been lurking for many months, finally decided to sign up. I'm hoping i don't offend anyone by my inability to complete this process, I have been searching these forums for about a week. I went from 1.5 stock to 2.1 OTA. Trying to run the root onto my phone, ran the all in one script, finished going from OTA 2.1 to the 2.1 in the file. My next step is trying to get the recovery file onto my phone. Sadly, this seems to be my problem. So far the steps I have done, is phone has been in debugging mode, unmounted/charge only mode. Tried to run the second step in all in one script, it would try to load the Recov file, but was unable to find it, I've downloaded the recovery file and extracted into the /tools/ of my adk-android-windows. I see two files there, the Flash_image and the second file would be what appears to still be a zip file labelled "recovery winzip file" I was curious if maybe I had to extract something from that one as well, but when I open it with winzip I see a message "Error: internal error processing iso image"
I have even tried to do it manually, everything will go ok until I get to the very last step "adb shell flash_image recovery /sdcard/recovery.img" Once I hit enter, it again tells me unable to locate file or folder. If I continue through anyway with the all in one script and try to reboot in recovery mode, I just get an Exclamation mark with the little android gent. Which in turn requires a battery pull for me.
I have yet to find any answers, and if I have missed something, I apologize. I am 100% positive it is user error, I am just not sure what error I am performing. Any help would be appreciated, or even if someone might have a different idea or a way of letting me know what I am doing wrong. Thank you for taking the time to read this and I hope I have not angered anyone with my problem.

I hope I have described everything clearly enough.
Thank you
 
Forsaken said:
Alright, first off, I must say you people are so wonderful. I would also like to thank GRDLOCK for such a wonderful script and description for this process. I have been lurking for many months, finally decided to sign up. I'm hoping i don't offend anyone by my inability to complete this process, I have been searching these forums for about a week. I went from 1.5 stock to 2.1 OTA. Trying to run the root onto my phone, ran the all in one script, finished going from OTA 2.1 to the 2.1 in the file. My next step is trying to get the recovery file onto my phone. Sadly, this seems to be my problem. So far the steps I have done, is phone has been in debugging mode, unmounted/charge only mode. Tried to run the second step in all in one script, it would try to load the Recov file, but was unable to find it, I've downloaded the recovery file and extracted into the /tools/ of my adk-android-windows. I see two files there, the Flash_image and the second file would be what appears to still be a zip file labelled "recovery winzip file" I was curious if maybe I had to extract something from that one as well, but when I open it with winzip I see a message "Error: internal error processing iso image"
I have even tried to do it manually, everything will go ok until I get to the very last step "adb shell flash_image recovery /sdcard/recovery.img" Once I hit enter, it again tells me unable to locate file or folder. If I continue through anyway with the all in one script and try to reboot in recovery mode, I just get an Exclamation mark with the little android gent. Which in turn requires a battery pull for me.
I have yet to find any answers, and if I have missed something, I apologize. I am 100% positive it is user error, I am just not sure what error I am performing. Any help would be appreciated, or even if someone might have a different idea or a way of letting me know what I am doing wrong. Thank you for taking the time to read this and I hope I have not angered anyone with my problem.

I hope I have described everything clearly enough.
Thank you
Click to expand...
you dont have anything else on your sd card that it would try and boot to?....and i still would like to know do you have to do the 2.1rom or can we do any after step 1,2?
 
I've rooted 5 Eris's using the root.zip grdlock had posted did the 5th one 5 days ago....as of that time it was NOT the leaked 2.1 it will give you root access to the phones /system/app..../system/bin...../system/xbin..../system/usr..../system/etc...........things like that hope this helps the question bout it being a leaked version if that's what u were talking about
 
TheDroidDoes said:
I've rooted 5 Eris's using the root.zip grdlock had posted did the 5th one 5 days ago....as of that time it was NOT the leaked 2.1 it will give you root access to the phones /system/app..../system/bin...../system/xbin..../system/usr..../system/etc...........things like that hope this helps the question bout it being a leaked version if that's what u were talking about
Click to expand...
how about doing a 6th??;)
im not getting this
 
jreed2560 said:
Try using a different cable than the one that came with the phone. I did and I got everything to work perfectly. Also make sure to read everything about making sure you java/bin directory is in your system path. That had me scratching my head for a half a day.
Click to expand...

can you tell me exactly how to do the java/bin thing please that maybe my problem
 
anyone have any tips for not being able to install usb drivers? i'm not getting a yellow ?, and i have it in debugging.
 
are you running windows 7 or xp. if you running 7 click on the android sdk folder>android sdk>tools. Once your inside the tools folder, go to the address bar and clear it. Next just type cmd and hit enter. you should get a cmd prompt with no need to type anything to direct it to that folder. From there you should just be able to copy and paste the commands for flashing the recovery image.
 
You must log in or register to reply here.
Back
Top Bottom