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

Root Scottys noob friendly root guide-start to finish

Me again...I checked everything you said and all appears in good order. If it is possible to send you my my rezound file that contains the items we are discussing I will be happy to. :confused:
 
Me again...I checked everything you said and all appears in good order. If it is possible to send you my my rezound file that contains the items we are discussing I will be happy to. :confused:

sure,if you want to. you could try takin a couple screenshots or pics of the folder open on your pc,and/or if you want to upload somewhere and pm me the pics/links ill have a look :)
 
I have a really dumb question. I just installed Clean Rom 4.3. I attempted to stay on the GB firmware by flashing the patch but for some reason my release keys say 3.11.605.22 CL339740. Does this mean I'm on the ICS firmware?
 

Attachments

  • 2012-04-24_10-18-01.png
    2012-04-24_10-18-01.png
    13.1 KB · Views: 120
I have a really dumb question. I just installed Clean Rom 4.3. I attempted to stay on the GB firmware by flashing the patch but for some reason my release keys say 3.11.605.22 CL339740. Does this mean I'm on the ICS firmware?

Nope... That is simply the software build number.

You can verify gb firmware by verifying that you have hboot 2.10 or 2.11
 
Hi scotty, please see attached the PDF of my mini-adb file.

thanks yet again

do you have 2 mini-adb files set up? from your copy/paste below,it looks like you followed the commands in the first post exactly.


Scotty, I figured out how to paste from command window - Here is my problem! Sorry for being a pest...my Eris was never this difficult.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\jlipps>cd c:\mini-adb_vigor
c:\mini-adb_vigor>fastboot devices
c:\mini-adb_vigor>adb devices
List of devices attached
HTXXXXXXXXX device

c:\mini-adb_vigor>md5sums recovery-ra-vigor-3.14-gnm.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------
Error: Unable to read file/directory recovery-ra-vigor-3.14-gnm.img
c:\mini-adb_vigor>

however,from your pic,it looks like recovery-ra-vigor-3.14-gnm.img is inside a folder called "mini-adb" inside a folder called "rezound" wich may or may not be inside other folders :eek:

from the cut and paste above,looks like you do have mini-adb_vigor on the root of c,so make sure you place the recovery-ra-vigor-3.14-gnm.img file inside that folder and try again :)
 
2.11 - GB it is!

cool! :cool: sorry for the short answer earlier,but firmware is not changed by simply flashing a rom like cleanrom. firmware will need to be changed in bootloader,wich is only possible with an unlocked s-on phone by running the whole,signed by htc,ruu.

so as long as you dont flash the ruu in hboot,then youll remain on GB firmware :)
 
2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.

once youve either skipped past all the setup,or have re-set up and are ready to root:


2)permanently install your recovery
-move the image file you downloaded above for amon RA and place it into the mini-adb_vigor folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb_vigor directory:

cd c:\mini-adb_vigor

-make sure youre connected by typing:

adb devices

-should return serial number
-check the md5 of your recovery image:

md5sums <recoveryname>.img

**make sure the resulting md5 matches the one that drellisdee lists for the image that you downloaded. **

Ok, I read through the whole thread and I can't see anyone mentioning the same problem I'm having so here goes.
My md5sums is *not* listing the correct information, what gives? First time rooting using this method so it's a little different for me. I'm a relative newb when it comes to command prompts and stuff but everything worked ok up to this point. I have rooted before but the md5sums thing is stumping me. This is what is shows in my Command prompt screen:
Command prompt said:
C:\mini-adb_vigor>md5sums recovery-ra-vigor-3.14.gnm.img

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------
Error: Unable to read file/directory recovery-ra-vigor-3.14.gnm.img

C:\mini-adb_vigor>
 
cool! :cool: sorry for the short answer earlier,but firmware is not changed by simply flashing a rom like cleanrom. firmware will need to be changed in bootloader,wich is only possible with an unlocked s-on phone by running the whole,signed by htc,ruu.

so as long as you dont flash the ruu in hboot,then youll remain on GB firmware :)

S-OFF'd my wife's phone. Flashed the Juopunutbear HBOOT when prompted, stupidly. Big mistake. That updated firmware. I didn't realize it. The giveaway was the SD card not being picked up by the phone but it took me a few hours to figure it out. I did realize it though and ran Clean ROM without the patch. It did really odd things to the phone. Lots of reboots and in Words With Friends when I tried to back out of a conversation, the haptic feedback wouldn't stop and a reboot would ensue. However, with S-OFF I was able to RUU back to GB. Pretty awesome. Just like the old days of my OG Droid.

However, the build is 1.02.605.6. I have not been able to find the most updated GB version - does anyone have a link for this RUU? I tried OTA'ing but I was negged. I don't have the patience to attempt to head back into ICS land tonight, but I'd like to have the most updated version of GB.

Thanks gang.
 
Ok, I read through the whole thread

Um, no I didn't. GDit. Sorry but my son has been screaming all day and into the evening because he's teething something fierce. :puke: So I keep going from reading to holding him until he calms down then reading some more. I tried 3.15 and got the error message. I then tried 3.14 and I STILL received the error message. The file is in the correct folder.
mini-adb_vigor.jpg
 
Jesus, I should just quit while I'm ahead. I apologize to everybody for the tarded posts, I'm usually quite thorough with them. I still have no idea why the 3.15 did not work, I'm going through the XDA posts but there are a LOT of them.
As far as why the 3.14 did not work it is because I don't know how to work a keyboard. I had typed in md5sums recovery-ra-vigor-3.14.gnm.img instead of md5sums recovery-ra-vigor-3.14-gnm.img Appears to be working so far.
 
S-OFF'd my wife's phone. Flashed the Juopunutbear HBOOT when prompted, stupidly. Big mistake. That updated firmware. I didn't realize it. The giveaway was the SD card not being picked up by the phone but it took me a few hours to figure it out. I did realize it though and ran Clean ROM without the patch. It did really odd things to the phone. Lots of reboots and in Words With Friends when I tried to back out of a conversation, the haptic feedback wouldn't stop and a reboot would ensue. However, with S-OFF I was able to RUU back to GB. Pretty awesome. Just like the old days of my OG Droid.

However, the build is 1.02.605.6. I have not been able to find the most updated GB version - does anyone have a link for this RUU? I tried OTA'ing but I was negged. I don't have the patience to attempt to head back into ICS land tonight, but I'd like to have the most updated version of GB.

Thanks gang.

the jpbear hboot only replaced your hboot,not all of your firmware. if you want to just replace your hboot,you could flash the GB eng hboot from here:
[How To] Flash Engineering HBOOT After S-OFF - xda-developers

that would save you from flashing a whole ruu and having to re-set up. if you want the plain old,ship GB hboot,i can pull it and upload it,but that will take a lil longer.

if you still want to run the whole ruu,you can find the.exe in footballs folder here: [ROM]Vigor Shipped ROM Collection - xda-developers

or a PH98IMG.zip here: https://rapidshare.com/files/218062....1123r_3161E_9K_QMR_release_233635_signed.zip (sorry bout the slow download,thats about all i can afford ;))

edit: oops,just read your post a lil closer and realzied youve allready run the shipping RUU. sorry for the irrlevant posts above,but the links above should help you :)

Jesus, I should just quit while I'm ahead. I apologize to everybody for the tarded posts, I'm usually quite thorough with them. I still have no idea why the 3.15 did not work, I'm going through the XDA posts but there are a LOT of them.
As far as why the 3.14 did not work it is because I don't know how to work a keyboard. I had typed in md5sums recovery-ra-vigor-3.14.gnm.img instead of md5sums recovery-ra-vigor-3.14-gnm.img Appears to be working so far.

keyboard errors will do it for sure ;)

unless the commands are really small and simple,i always copy and paste when doing adb/fastboot commands ;)
 
the jpbear hboot only replaced your hboot,not all of your firmware. if you want to just replace your hboot,you could flash the GB eng hboot from here:
[How To] Flash Engineering HBOOT After S-OFF - xda-developers

That's interesting. I wonder why the phone wasn't picking up the SD card then until I re-ran Clean ROM 4.3 and did NOT flash the GB patch.

All in all, it's running much more smoothly now that I RUU'd back to the shipped ROM. Now that I have all of these files at my disposal I can mess around without fear of doing something stupid (ala, before S-OFF).

**EDIT** As it turns out, overnight the phone got the OTA to 2.01.605.11. Good to go. Now back to my regularly scheduled hackery**
 
Jesus, I should just quit while I'm ahead. I apologize to everybody for the tarded posts, I'm usually quite thorough with them. I still have no idea why the 3.15 did not work, I'm going through the XDA posts but there are a LOT of them.
As far as why the 3.14 did not work it is because I don't know how to work a keyboard. I had typed in md5sums recovery-ra-vigor-3.14.gnm.img instead of md5sums recovery-ra-vigor-3.14-gnm.img Appears to be working so far.

LMAO - happens to me all the time. I apparently can't type.
 
LMAO - happens to me all the time. I apparently can't type.

I am so f'n fried tonight. :(


Ok, so a question on the superuser zip. How do I load it? ES File Explorer and launch it? I'm so exhausted right now but I've started this and I want to finish.
 
All in all, it's running much more smoothly now that I RUU'd back to the shipped ROM. Now that I have all of these files at my disposal I can mess around without fear of doing something stupid (ala, before S-OFF).

add this to your file collection: [New Patched HBOOT][S-OFF Only] Hboot 2.11 Patched. Replaces Engineering HBOOT - xda-developers

its a patched 2.11 hboot,it will provide some basic eng fstboot commands,yet be newer and possibly a lil safer than the older,eng hboot. im about to flash it :)
 
add this to your file collection: [New Patched HBOOT][S-OFF Only] Hboot 2.11 Patched. Replaces Engineering HBOOT - xda-developers

its a patched 2.11 hboot,it will provide some basic eng fstboot commands,yet be newer and possibly a lil safer than the older,eng hboot. im about to flash it :)

Fantastic. Thanks. Can you post your findings after you flash this?

Hey - I have another question for you - if I want to flash a custom ROM on my wife's phone now that it's S-OFF, do I have to unlock the bootloader and root again now that I've RUU'd her back to stock. It's still showing S-OFF but locked.
 
working fine. :thumbup: looks like a good alternative to the eng hboot,or having to unlock the stock one.

you do not have to unlock to reroot.

if you want a permanent recovery,you can simply flash it as a PH98IMG file.

if you want to do the temp recovery so you can recieve OTAs,you will need to either unlock,or flash the patched or eng hboot so you can use the fastboot boot command,as neither that,nor fastboot flash are available with the ship,stock,locked hboot :eek:

flashing new hboot,or unlocking is entirely up to you and your comfort level.

pros to new hboot:
-it wont factory reset like ulocking will

cons:
-flashing a bootloader is dangerous if youre not careful. double check your md5s ;) :)

pros to unlocking:
-its quick and easy,you can use your original unlock token
-it may be a lil less scary than flashing the new hboot

cons:
it will wipe your data in the process

once unlocked,the unlocked hboot is prolly as good as the eng/patched hboot,and you wont need to unlock,or reflash the eng/patched hboot unless you run an ruu to overwrite it.or an OTA overwrites it :eek:

but anyway,hope that helps :)
 
I am finally rooted but I am stuck trying to flash CleanRom? Specifically,
I was unable to flash the rom from my sd card (then I screwed something up with the HBOOT because now I can't use recovery - when I try it sends me to this error:

HBOOT
Parsing.....[SD ZIP]
[1} Boot -OK
Update Complete....
Press <POWER> to reboot


Another question; When I could use recovery and went to flash the CleanRom there were numerous subfolders that I tried to flash but nothing ever worked...and then I did whatever to get the error above. I also tried to manually flash (put the PH89IMG.img and CleanRon in c:\mini-adb_vigor file) but got to this step in your "manually rom flash instructions":

12)flash your kernel(boot image)
fastboot flash boot<boot image name>.img
where <boot image name> is exactly the name of your boot image inside the adb/fastboot folder. note that the command fastboot flashis permanently installing the boot image,unlike fasboot boot,wich is only booting it temporarily into the phones memory.


Maybe I will get this done one day in a galaxy far far away......thanks again for any help!:confused:
 
Does anyone know why, or better yet how to stop my phone from trying to update HBOOT almost immediately when I boot up in recovery (amonra)?

....as you may have seen in my last post something went wrong when I tried to flash a new ROM (FYI, everything is based on scotty's directions - which I managed to screw up.)
 
Does anyone know why, or better yet how to stop my phone from trying to update HBOOT almost immediately when I boot up in recovery (amonra)?

....as you may have seen in my last post something went wrong when I tried to flash a new ROM (FYI, everything is based on scotty's directions - which I managed to screw up.)

It's very likely reading a PH98IMG file (I think that's the one). Take out your SD card, plug it into your pc using a reader and search for that, delete it and try again.

Now I have a question. I just installed the ICS leak - figured why the hell not. If it doesn't work, I can always RUU back to stock. In my notification bar I am hooked up to wifi but the 3G signal is also running. Has anyone run into this. Does anyone have any insight? I already re-ran the update and I'm getting the same problem. I can easily trash it and go with a custom ROM but I'm thinking it might be the radio? Just grasping at straws here. Thanks.
 
thanks mtbhk44, removing the PH89IMG worked.....but how do I flash the kernel? I am following the CleanROM developer's instructions which I have listed below from XDA [ROM 4/7] CleanROM 4.3 Standard / Pro -&#9733;| ICS 4.0.3 | Tweaks v2 | Both Firmwares |&#9733;- - xda-developers


Place ROM on SD Card
Reboot to recovery
Wipe all data / Factory reset - Do not restore anything from back up. Do not ask in the thread if you can. You will be referred back to here!
Flash ROM. When ROM Completes you will have the option to install old firmware patch if needed. It will be located on the SD Card in the CleanROM Folder.
Now you will need to manually boot to bootloader. Do this by selecting Reboot to Bootloader via the Recoveries Development Menu (Amon Ra).
Device will then boot to fastboot.
Press Power to install the kernel / boot.img THIS IS WHERE I AM CONFUSED!
Reboot
Profit!

Do I need to usee the Developer menu to get to the HBOOT kernel zip menu? If so then what? THANKS IN ADVANCE!!!
 
FYI, the "CleanRom" that I think I flashed correctly was entered as follows:

C:\mini-adb_vigor\Stock Rooted ROM - Vigor - WWE 2.01.605.11
 
Back
Top Bottom