• 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

i would have thot it would work fine... but i am unable to cd to anything other than the c drive :eek: unless im having some sort of braincramp about the cmd line :o in a worse case,you could load it all onto a flash drive,temporarily move mini-adb_vigor over to C on youyr work computer,then move it back. hafta check into that some more.

glad things seem to be working for you again :)


I found today that you type a simpe H: to switch to whatever drive letter. However I'm currently missing my flash drive, so I'm unable to test if it works or not.
 
Code:
C:\Users\Scott>[COLOR="Red"]h[/COLOR]
'h' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Scott>[COLOR="red"]cd h[/COLOR]
The system cannot find the path specified.

C:\Users\Scott>[COLOR="red"]H[/COLOR]
'H' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Scott>[COLOR="red"]cd H[/COLOR]
The system cannot find the path specified.

C:\Users\Scott>

:(

if you get it figured out,defintately let me know :)

(my flash drive was drive h)
 
Code:
C:\Users\Scott>[COLOR="Red"]h[/COLOR]
'h' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Scott>[COLOR="red"]cd h[/COLOR]
The system cannot find the path specified.

C:\Users\Scott>[COLOR="red"]H[/COLOR]
'H' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Scott>[COLOR="red"]cd H[/COLOR]
The system cannot find the path specified.

C:\Users\Scott>

:(

if you get it figured out,defintately let me know :)

(my flash drive was drive h)


No, literally type drive letter, colon. So "H:" without the quotes. That's the only part I was able to get working(changed to a different hard drive) just got to find flash drive, see if it all works.
 
No, literally type drive letter, colon. So "H:" without the quotes. That's the only part I was able to get working(changed to a different hard drive) just got to find flash drive, see if it all works.

whaaaa :eek: *smacks forehead*

i could have sworn i tried that earlier when i was messing with it,but now it seems to be working...

Code:
c:\mini-adb_espresso>[COLOR="Red"]J:[/COLOR]

J:\>[COLOR="red"]j:\mini-adb[/COLOR]
'j:\mini-adb' is not recognized as an internal or external command,
operable program or batch file.

J:\>[COLOR="red"]cd j:\mini-adb[/COLOR]

j:\mini-adb>[COLOR="red"]adb devices[/COLOR]
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
SH0CEPS02206    device


j:\mini-adb>[COLOR="red"]h:[/COLOR]

H:\>[COLOR="red"]cd h:\miniadb_evo3d[/COLOR]

H:\miniadb_evo3d>[COLOR="Red"]adb devices[/COLOR]
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
SH0CEPS02206    device


H:\miniadb_evo3d>[COLOR="red"]adb reboot bootloader[/COLOR]

H:\miniadb_evo3d>[COLOR="red"]fastboot devices[/COLOR]
SH0CEPS02206    fastboot

H:\miniadb_evo3d>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.070s

H:\miniadb_evo3d>

j=expansion drive
h=flash drive

device is htc espresso

seems a tad bit slower to react than having it on C,but i think it will work fine for you :)
 
whaaaa :eek: *smacks forehead*

i could have sworn i tried that earlier when i was messing with it,but now it seems to be working...

Code:
c:\mini-adb_espresso>[COLOR="Red"]J:[/COLOR]

J:\>[COLOR="red"]j:\mini-adb[/COLOR]
'j:\mini-adb' is not recognized as an internal or external command,
operable program or batch file.

J:\>[COLOR="red"]cd j:\mini-adb[/COLOR]

j:\mini-adb>[COLOR="red"]adb devices[/COLOR]
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
SH0CEPS02206    device


j:\mini-adb>[COLOR="red"]h:[/COLOR]

H:\>[COLOR="red"]cd h:\miniadb_evo3d[/COLOR]

H:\miniadb_evo3d>[COLOR="Red"]adb devices[/COLOR]
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
SH0CEPS02206    device


H:\miniadb_evo3d>[COLOR="red"]adb reboot bootloader[/COLOR]

H:\miniadb_evo3d>[COLOR="red"]fastboot devices[/COLOR]
SH0CEPS02206    fastboot

H:\miniadb_evo3d>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.070s

H:\miniadb_evo3d>

j=expansion drive
h=flash drive

device is htc espresso

seems a tad bit slower to react than having it on C,but i think it will work fine for you :)


Sweet, I'm pretty sure I can't copy anything to the c drive on my work machine, its crazy locked down, so having this as a back up will be nice.
 
Sweet, I'm pretty sure I can't copy anything to the c drive on my work machine, its crazy locked down, so having this as a back up will be nice.

yeah, i think it will work out well for you,and provide alot of peace of mind you can fix things if you have to. a very clever solution :cool:
 
yeah, i think it will work out well for you,and provide alot of peace of mind you can fix things if you have to. a very clever solution :cool:


Basically came up because I was a day of flights away from home and the phone broke. Luckily I had accidentally flashed aman ra instead of booting it. Had a backup.

I try to avoid doing anything to my phone while traveling for work, but sometimes it just breaks hah. Thanks again Scotty.
 
I just wanted to thank you for this excellent write up on how to root the Rezound. I am definitely not "well versed" in all of the technical stuff involved but this went off without a hitch!! Thanks again!!
 
Is there anyway to know if aman ra is installed? If I did the full RUU that would wipe out Amon Ra wouldn't it? Making me have the stock recovery and then I have to use a pc to flash things?
 
Is there anyway to know if aman ra is installed? If I did the full RUU that would wipe out Amon Ra wouldn't it? Making me have the stock recovery and then I have to use a pc to flash things?

correct. after running the RUU,amon is gone,unless you purposefully(accidentally :eek:) fastboot flash recoveryed it back :)

best way to check for it is to just select recovery in hboot,or adb reboot recovery in your cmd window. if you get the phone and the triangle ! then your recovery is stock.

with the stock recovery hold power and vol up and youll get a menu you can use to reboot,so you dont have to pull the battery.
 
Hi Scotty,

Step 1 worked fine, I can clearly see that the bootloader is unlocked after pressing volume down + power button.

Now my windows(samsung) laptop will not recognize my device when I boot phone into fastboot using volume down + power button. After typing "cd c:\mini-adb_vigor" I then type "adb devices" and nothing shows up...

BUT my device does appear when phone is powered on normally (I can access sd card just fine from normal boot.)

Please help! Thank you in advance.
 
Hi Scotty,

Step 1 worked fine, I can clearly see that the bootloader is unlocked after pressing volume down + power button.

Now my windows(samsung) laptop will not recognize my device when I boot phone into fastboot using volume down + power button. After typing "cd c:\mini-adb_vigor" I then type "adb devices" and nothing shows up...

BUT my device does appear when phone is powered on normally (I can access sd card just fine from normal boot.)

Please help! Thank you in advance.

looks like youre using the wrong command. when booted,you use the adb devices command. when in fastboot,use fastboot devices

hope that helps :)
 
Thank you for prompt response...but still confused about Step 2. Again, bootloader is definitely unlocked and I want to permanently root - So how do I initiate Step 2 again since I unlocked the bootlader yesterday but was unable to finish all 3 steps?
 
i think i get it now....I need to connect to my pc under normal phone boot and then follow your instructions which will ultimately reboot my phone into Hboot\Fastboot mode which will allow me to flash amonra...is that correct?
 
i think i get it now....I need to connect to my pc under normal phone boot and then follow your instructions which will ultimately reboot my phone into Hboot\Fastboot mode which will allow me to flash amonra...is that correct?
yup! you got it :cool:
 
much appreciated, getting ready to take another stab....I saw that there was a later version of amonra (3.15) and was curious if I should use this instead of 3.14?
 
after my device is properly identified here is where I am stuck:

c:\mini-adb_vigor>md5sums recovery-ra-vigor-3.14.gnm.img

"then all the MD5 sums stuff....."

below that I get this error message:

"Error: Unable to read file/directiry recivery-ra-vigor.3.14.gnm.img"


I am lost....any ideas?
 
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>
 
I reviewed your instructions again, rechecked the files, extractions, usb debugging, etc. and everything appears to be accurate. I feel like my problems occurred because I didn't complete all 3 steps at once....the process involved in step 2 seems pretty simple especially since I got the bootloader unlocked.
 
everything looks fine. you are using 3.14,right?

if you are using 3.15,remember you need to modify the command whenever amon is booted or flashed(not sure wich way youre going)

md5sums recovery-ra-vigor-3.15-gnm.img if you are indeed using 3.15

i promise,it has nothing to do with not doing all the steps at once :)

either the file is mis-named,not in the mini-adb_vigor folder,or something equally simple ;)

double check the image inside mini-adb_vigor. make sure its named the same as the command youre running,and make sure its an image file,not a .zip file.
 
Back
Top Bottom