• 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

if you are using a temporary recovery,all you need to do is swap the image out in your mini-adb_vigor folder so that next tiime you need it,its in there and ready for you.

if you were running a permanently installed recovery,then you would go ahead and flash it. :)
 
Yow! Good thing I waited for your reply; I was gonna go ahead & flash it. I always forget the the fastboot boot command. I should stick that in my head lol.

Now on to Rom'ing :D

Thanks once again!
 
I could not get pas this part (*beginning):cd c:\mini-adb_vigor

System just would not recognize that no matter what i did or downloaded.
 
PNWViking said:
I could not get pas this part (*beginning):cd c:\mini-adb_vigor

System just would not recognize that no matter what i did or downloaded.
Click to expand...

make sure the folder is NOT zipped,and not inside a folder on the C: drive of your PC

some folks have reported prollems with the dash and/or underscore,so you might also try chnging the name to something like"miniadb" or "miniadbvigor"

just remember youll need to change the name where ever you see that command( cd c:\miniadb or cd c:\miniadbvigor or cd :\whtevernameyouchoose )
 
Yeah, I saved it to the C drive, as a standalone file.
And unzipped everything.

I have a Droid X I don't use anymore that I should figure this out on first.
 
Hello, i am new to rooting and i seem to be stuck at the point of flashing recovery. Everything up until that point has gone very smoothly. When i try and flash the recovery, this is what i get

creating boot image...
creating boot image - 7229440 bytes
downloading 'boot.img'... OKAY [ 1.412s]
booting... FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.426s

I have tried multiple times to get this to work but I just can't figure out what I am doing wrong. Any help would be greatly appreciated and ty so much for the guide! Hope to get it working soon!
 
cryptic2005 said:
Hello, i am new to rooting and i seem to be stuck at the point of flashing recovery. Everything up until that point has gone very smoothly. When i try and flash the recovery, this is what i get

creating boot image...
creating boot image - 7229440 bytes
downloading 'boot.img'... OKAY [ 1.412s]
booting... FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.426s

I have tried multiple times to get this to work but I just can't figure out what I am doing wrong. Any help would be greatly appreciated and ty so much for the guide! Hope to get it working soon!
Click to expand...

im a little confused why the pc is "creating boot.img" instead of downloading or sending it...(check out the codebox in the OP)

a copy/paste of the rest of your cmd window may be helpful.

off the top of my head:
-make sure the recovery image is in your mini-adb_vigor folder.
-make sure you have cd c:\mini-adb_vigor
-make sure the command is correct... im not sure if youre trying to boot,or permanently flash recovery:
boot recovery: fastboot boot recoveryname.img
to permanentlyly flash: fastboot flash recovery recoveryname.img
where recoveryname is the exact name of the image inside your folder(note this is an IMAGE,not a .zip or other type of file)
 
Ok I got it figured out, the problem apparently was that i didn't un-zip the img before attempting to boot it. Once i did that, everything went smoothly. The md5checksum that is listed for the latest version of 3.15 is the checksum for the zipped img and the ones for the previous versions seem to be for the unzipped files so that threw me off a bit.

Anyway, ty again for the excellent and very easy to follow tutorial. You are awesome sir! :)
 
awsome! glad you got it figured out. as you have found,the image is inside the .zip file :) sorry for the delayed response to that :o
 
I hope I'm just looking right over something here but I'm at a loss.

I followed all the steps in the original post and installed a temp recovery and everything worked fine. I decided to install a permanent recovery since there seem to be some good ICS roms out there and the OTA (if it ever comes) looks less appealing. I followed the steps for installing the perm recovery and now when I try to boot to recovery I get as far as the white bootloader screen and it won't let me down volume to Recovery. It goes into hboot, asks me if I want to install an update and whether I say yes or no it only gives me the option to reboot and then does the exact same thing. If I let it boot normally I get the htc screen then a black screen that sits there until I do a battery pull.

Any ideas on what I'm missing?

[NEVER MIND. I had PG98IMG on my SD card. Once I deleted that it looks like it's working]

Thanks!
 
glad you are out of your jam :)

just keep in mind that permantly installing a recovery doesnt let you flash roms normally. a permanent recovery cannot write the boot image,so youre still stuck doing a manual flash of the kernel somehow with an s-on phone.

i would still recomand fastboot booting your recovery when you want to flash a rom,or restore a backup. that way,recovery can write the boot image,and s-off roms will flash,and backups will restore just fine wihtout seperate kernel flashes. :)
 
This guide is fantastic. it really is noob friendly and a relief to read after a lot of other guides.
I used this method to root my wildfire (still S-ON).
It was surprisingly easy after all the unsettling things i read on "wildfire-all things root".

1) I used htcdev to unlock my bootloader. (get unique unlock code, factory reset and wipe all data)
2) Just using fastboot/adb on a PC, I booted (not flashed) the clockworkmod recovery recommended for the wildfire,
3) using the temp recovery, i then created a nand backup and flashed the SU zip. On restart, I had root. (with no loss of personal data)

the CWM recovery didnt allow navigation into the menu at first, but after a little wait and a few tries, it worked fine. I didnt need to reboot it. This was the only glitch in the entire unlocking/rooting process.

Checked root with Terminal Emulator, it returned me a #.
i will decide in the future if i want S-OFF, i may not need it - still reading...

i hope other wildfire users and maybe wildfire s, etc can use this easy method if they dont need s-off.
 
Any reason when I type in md5sums to install recovery, I get "'md5sums' is not recognized as an internal or external command,
operable program or batch file."?
 
jdailey1981 said:
Any reason when I type in md5sums to install recovery, I get "'md5sums' is not recognized as an internal or external command,
operable program or batch file."?
Click to expand...

that error is from the md5sums utility not being present. most commonly from:
1)not changing to the directory containing the utility,adb,etc( cd c:\ foldername

2)youre not using my mini-adb download,youre using the standard sdk,or the folder from htcdev wich does not contain the md5sums utility.

you can check md5s other ways.

if you want to use the md5sums utility,download mini-adb from the original post. you can either place the md5sums utility into the folder that you use,or you can start using the mini-adb folder.
 
Thanks for the terrific guide! I followed your instructions to the letter, or so I thought. After backtracking and using the rest of this forum, this n00b now has a rooted phone working light years better than it did before.

I'm looking forward to learning more about what I can do now. Keep up the great work!
 
Real quick because it's early, does the HTC dev portion wipe the phone? Basically can I root without a reset? If so I'll root the 10 leak and save some time, if no ill flash the latest and root that....
Thanks!
 
gruss said:
Real quick because it's early, does the HTC dev portion wipe the phone? Basically can I root without a reset? If so I'll root the 10 leak and save some time, if no ill flash the latest and root that....
Thanks!
Click to expand...

the unlock will perform a factory data reset,no way around it that i know of. :(
 
Scotty Thanks so much for this guide. I am having one issue. I've followed all the steps using the temporary boot method. Installed superuser but I don't have root access. I've gone back and redid the steps several times with no luck. Any ideas?
 
touchofike said:
Scotty Thanks so much for this guide. I am having one issue. I've followed all the steps using the temporary boot method. Installed superuser but I don't have root access. I've gone back and redid the steps several times with no luck. Any ideas?
Click to expand...

Figured it out need to use Superuser-3.1.3-arm-signed.zip for superuser and that did the trick.
 
You must log in or register to reply here.
Back
Top Bottom