Root [How To] Root 2.3.4/downgrade and Get S-off

scotty85 · Mar 20, 2012

sweetb2006 said:
Nothings working... Tried running twice in a row, closed all internet connections & pc programs, deleted any trace of verizon on pc, Except the usb drivers. FML & I swear to ya Scotty, that pb31img was named correctly(changed to .zip via windows, double checked not seen as .zip.zip, removed sd card to make sure file was actually on sd card)... "sighs"

actually,above when i said "fastboot mode" i did not mean to have fastboot checked in settings. what i meant was,to power on into hboot mode via power on/vol down. then select "fastboot" with the vol rocker and power button. this is another bootloader mode.

put your phone int that mode,and then start the .exe file.

also make sure your phone is charged to 100%.

i know you think youve double checked everything,and i hate to keep beating you up about it,but i have never,ever seen an htc phone simply not find PxxxIMG files when the conditions are right. i dont know what else to say,other than one of those 4 things i mentione above is still not right.

did the md5 of your PB31IMG for froyo match the one i listed?

you might check it on your sd card with an app called "scary aliens android file verifier" wich is available in the market. this will tell if yuve got a good file ready to flash.

on the .exe file...
try this:
open your cmd window,change to your mini-adb_inc directory,plug i the phone,charge only,usb debug on, and type
adb devices

then,if you get your serial number back,
adb reboot bootloader

the mode that it takes you to is the fastboot mode i described above(this is another way to get to it) and is a white screen with colored letters,much like hboot.

now type
fastboot devices

if you get your serial number back,then close your cmd window,and run the .exe file as administrator.

sweetb2006 · Mar 20, 2012

scotty85 said:
actually,above when i said "fastboot mode" i did not mean to have fastboot checked in settings. what i meant was,to power on into hboot mode via power on/vol down. then select "fastboot" with the vol rocker and power button. this is another bootloader mode.

put your phone int that mode,and then start the .exe file.

also make sure your phone is charged to 100%.

i know you think youve double checked everything,and i hate to keep beating you up about it,but i have never,ever seen an htc phone simply not find PxxxIMG files when the conditions are right. i dont know what else to say,other than one of those 4 things i mentione above is still not right.

did the md5 of your PB31IMG for froyo match the one i listed?

you might check it on your sd card with an app called "scary aliens android file verifier" wich is available in the market. this will tell if yuve got a good file ready to flash.

on the .exe file...
try this:
open your cmd window,change to your mini-adb_inc directory,plug i the phone,charge only,usb debug on, and type
adb devices

then,if you get your serial number back,
adb reboot bootloader

the mode that it takes you to is the fastboot mode i described above(this is another way to get to it) and is a white screen with colored letters,much like hboot.

now type
fastboot devices

if you get your serial number back,then close your cmd window,and run the .exe file as administrator.

Ahh yes, I know of this white board, with colored words you mention.

And I did go there & do that & than run & rerun the RUU, as admin. All I was questioning was if after booting to fastboot, before running the RUU, if it mattered if fastboot was Than checked on or off.

Now, I presume that once i toggle & chose fastboot, that it boots phone back up & than looks no different than when phone is booted without fastboot? If not, than yea i am missing something.
And yes, I checked the md5 of the image (Again today) & it matches the one you state on your tutorial.
I guess I could be one in a zillion that this doesn't work for. :eek:

Though, I do doubt it & I am hanging on to that tiny string of hope. And I appreciate your patience in not giving up on me, as I know too well, how hard it can be to teach someone something, when you're not right there to see it for yourself.

sdrawkcab25 · Mar 20, 2012

sweetb2006 said:
Ahh yes, I know of this white board, with colored words you mention.
And I did go there & do that & than run & rerun the RUU, as admin. All I was questioning was if after booting to fastboot, before running the RUU, if it mattered if fastboot was Than checked on or off. Now, I presume that once i toggle & chose fastboot, that it boots phone back up & than looks no different than when phone is booted without fastboot? If not, than yea i am missing something.
And yes, I checked the md5 of the image (Again today) & it matches the one you state on your tutorial.
I guess I could be one in a zillion that this doesn't work for. Though, I do doubt it & I am hanging on to that tiny string of hope. And I appreciate your patience in not giving up on me, as I know too well, how hard it can be to teach someone something, when you're not right there to see it for yourself.

Did we ever verify that the PB31IMG.zip file is on the ROOT of the sd card and NOT in any folders?

If possible can you take a screen shot of whatever file explorer you use, showing where you have the file.

Screenshot App.

sweetb2006 · Mar 20, 2012

sdrawkcab25 said:
Did we ever verify that the PB31IMG.zip file is on the ROOT of the sd card and NOT in any folders?

If possible can you take a screen shot of whatever file explorer you use, showing where you have the file.

Screenshot App.

Yes, I am 99.9% sure that it is on the root of the sd card, as discussed with Scotty. When he questioned this, I removed the sd card, then checked back with the explorer I use & of course, the card could not be found. The only reason I am not 1000% positive is because you all make me doubt my own sanity.

lol
I will try to get that screen shot posted here in a couple/few hours after I get my little man off to bed. I will be happy to post any screen shot that could help you all help me & that may help proove my sanity.

sdrawkcab25 · Mar 20, 2012

sweetb2006 said:
Yes, I am 99.9% sure that it is on the root of the sd card, as discussed with Scotty. When he questioned this, I removed the sd card, then checked back with the explorer I use & of course, the card could not be found. The only reason I am not 1000% positive is because you all make me doubt my own sanity. lol
I will try to get that screen shot posted here in a couple/few hours after I get my little man off to bed. I will be happy to post any screen shot that could help you all help me & that may help proove my sanity.

Yeah, I saw that post that it is definitely on the sd card, but want to verify that it is on the root of the sd card.

Honestly, I've never seen anyone have this much trouble flashing the file, no offense lol.

Even if the file is corrupt or broken ect, as long as its named correctly and on the root of the card(formatted to fat32)the phone will attempt to install it.

scotty85 · Mar 20, 2012

do you have access to a different PC? a differnet desktop or laptop may run the RUU for you.

sweetb2006 · Mar 20, 2012

scotty85 said:
do you have access to a different PC? a differnet desktop or laptop may run the RUU for you.

Unfortunately no Scotty =-(

sweetb2006 · Mar 20, 2012

sdrawkcab25 said:
Yeah, I saw that post that it is definitely on the sd card, but want to verify that it is on the root of the sd card.

Honestly, I've never seen anyone have this much trouble flashing the file, no offense lol.
Even if the file is corrupt or broken ect, as long as its named correctly and on the root of the card(formatted to fat32)the phone will attempt to install it.

No offense taken... lol
I will do the screen shot in a bit but yea, def fat32 formatted, as other things wouldn't work until after i did. As for the name, I have tried not touching the name, to making it .zip(making sure it did no read .zip.zip). As much as I hope the screen shot proves me wrong, I will be relieved but extremely dumbfounded. :eek:

iowabowtech · Mar 20, 2012

The crazier thing is that the RUU won't run. :eek:

Do you have another microsd card you could try? Otherwise, I'd try yet another format to fat32 using the PC to do so. And choosing the full format option rather than the quick option. I have seen situations where people have had to reformat several times before it took...I believe 4 times was the record if I recall. Took some patience on behalf of the other party.

sweetb2006 · Mar 20, 2012

iowabowtech said:
The crazier thing is that the RUU won't run.

Well, considering that it does neither, yes crazy. But, I have read where plenty of people have same issue of the RUU thinking there's no usb card, even when they buy a new one...

Do you have another microsd card you could try? Otherwise, I'd try yet another format to fat32 using the PC to do so. And choosing the full format option rather than the quick option. I have seen situations where people have had to reformat several times before it took...I believe 4 times was the record if I recall. Took some patience on behalf of the other party.

Nope, no other card, can't afford to go buy new one for a while either, cheap or not.. I will give the re-re-re fat32 a shot, if no other suggestions by tomorrow. I have a screen sht ready. Do I post it as a .png here or shall i use photoshop to change it to a jpg(assuming that will work)???

Well, after two long nights & days. I'm going to get some lost sleep. Let me know what form of screen shot works best for you & I will post it in morn.

sweetb2006 · Mar 21, 2012

scotty85 said:
do you have access to a different PC? a differnet desktop or laptop may run the RUU for you.

Scotty & everyone else trying to help...(thnx a million btw) I don't know if this makes a difference. However, I do have to type su & give permissions to get to the #. However, I have checked for root confirmation, with success. Could the root checker be wrong? Is there a particular root checker that you are absolute would be right? Or, is there anything that I have been able to do up to this point that assures you I am rooted?

scotty85 · Mar 21, 2012

nope... you are rooted

no doubt about that.

unfortunately,being rooted has nothing to do with getting the .exe to run,or getting a PB31IMG to flash.

post your screen shot however you are able.

sweetb2006 · Mar 21, 2012

scotty85 said:
nope... you are rooted no doubt about that.

unfortunately,being rooted has nothing to do with getting the .exe to run,or getting a PB31IMG to flash.

post your screen shot however you are able.

Here ya go...

Another question as far as where the pb31img is & if the phone can see it... When I'm on the white screen, it briefly flashes in green, something about this file. Does that not show that it is seeing it? I try desperately to see exactly what it says but it goes so quick.

iowabowtech · Mar 21, 2012

sweetb2006 said:
Here ya go...

Another question as far as where the pb31img is & if the phone can see it... When I'm on the white screen, it briefly flashes in green, something about this file. Does that not show that it is seeing it? I try desperately to see exactly what it says but it goes so quick.

Man, that looks right. The card just isn't taking it. The brief flashing of green is normal, it will always do that. That's where it's checking for the update file but if it found it...like it should be...it would prompt you to load it by pressing volume up.

Bob Cat · Mar 21, 2012

Just a guess here but has he tried using a different recovery? I see he has a folder with clockwork. I've never used clockwork, always amon ra and have never had any issues. Just a thought.

sweetb2006 · Mar 21, 2012

iowabowtech said:
Man, that looks right. The card just isn't taking it. The brief flashing of green is normal, it will always do that. That's where it's checking for the update file but if it found it...like it should be...it would prompt you to load it by pressing volume up.

SHEW!

Maybe I'm not crazy! lol

Ok so that's like a normal file for the phone to look for in that mode. thnx

Ugh! I so didn't want it to be my sd card that was the problem, that's gonna cause a major delay...

sweetb2006 · Mar 21, 2012

bobcat331 said:
Just a guess here but has he tried using a different recovery? I see he has a folder with clockwork. I've never used clockwork, always amon ra and have never had any issues. Just a thought.

"She"/I used whatever Scotty told me to use!

Thanks for the question though!

Bob Cat · Mar 21, 2012

sweetb2006 said:
"She"/I used whatever Scotty told me to use! Thanks for the question though!

My apologies madam. Had I looked at your screen name and not just the problems, I wouldn't have made that silly mistake.

I'll ask Scotty about the recoveries and see what he's say's. It's just odd your having this issue.

iowabowtech · Mar 21, 2012

Hey Scotty...what would happen if we flashed it via fastboot? Would it give a mainversion error and if so, could we bait and switch the mainversion to mactch the user's current setup to avert a fail?

Bob Cat · Mar 21, 2012

Changing recoveries wouldn't matter.

sdrawkcab25 · Mar 21, 2012

After seeing the screenshot, I think the only thing left is, for some reason the SD card isn't taking the fat32 format. And would try another card or formatting through a card reader.

Failing those two options I would think you should be able to flash the file through fast boot.
http://androidforums.com/incredible...sier-way-flash-pb31img-files.html#post3834298

scotty85 · Mar 21, 2012

iowabowtech said:
Hey Scotty...what would happen if we flashed it via fastboot? Would it give a mainversion error and if so, could we bait and switch the mainversion to mactch the user's current setup to avert a fail?

if the misc img hasnt been rewritten,then it would get the main version fail. i was thinking of suggesting this,but wanted to make sure we had exhausted all other possibilities before i suggested it,due to not wanting to add more confusion to an allready fustrated sweetb

sdrawkcab25 said:
After seeing the screenshot, I think the only thing left is, for some reason the SD card isn't taking the fat32 format. And would try another card or formatting through a card reader.

Failing those two options I would think you should be able to flash the file through fast boot.
http://androidforums.com/incredible...sier-way-flash-pb31img-files.html#post3834298

i am inclined to agree... if youre formatting the card in the phone via usb cable,it could be a usb cable thing,an sd card thing,or who knows what,but at this point it looks like for one reason or another the prollem is the sd card.

im still not sure why the RUU wouldnt run either,unless htc sync or something is running on the PC and screwing with it.

i think at this time we should try and flash the PB31IMG in fastboot. just to keep things,in-thread,ill put some real quick directions here:

1)put PB31IMG into your android directory(if thats still what mini-adb inc is renamed in your system). you dont need to change the name of PB31IMG or android to make it work.

assuming you leave it named PB31IMG then open your cmd window and enter(only bold type. blue are just additional comments):

cd c:\android change to android directory

md5sums PB31IMG.zip this will output the md5 sum of the file you will flash. make sure it matches 31bb1611a0fa8197d447c0438426717e

adb devices should output your phones serial number

adb reboot bootloader will boot you into the fastboot screen(white with colored letters)

fastboot devices will again output serial number

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip PB31IMG.zip

you will see a green line on your phone as the file flashes.youll see outut in your cmd window. shortly after starting you will get a "FAILED!(remote: 90 hboot pre-update! please flush image again immediately). dont worry,this is normal.

fastboot flash zip PB31IMG.zip to flash it again. it will finish this time.

after you get a "finished" message:

fastboot reboot-bootloader this will take you back to the white fastboot screen

fastboot reboot your phone should reboot

heres how it should look in your cmd window:

Code:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott> [COLOR="red"]cd c:\mini-adb_inc[/COLOR]

c:\mini-adb_inc>[COLOR="red"]md5sums PB31IMG.zip[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
PB31IMG.zip                               100% 31bb1611a0fa8197d447c0438426717e

c:\mini-adb_inc>[COLOR="red"]adb devices[/COLOR]
adb server is out of date.  killing...
* daemon started successfully *
HT117HJ00242    device


c:\mini-adb_inc>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\mini-adb_inc>[COLOR="red"]fastboot devices[/COLOR]
HT117HJ00242    fastboot

c:\mini-adb_inc>[COLOR="red"]fastboot erase cache[/COLOR]
               erasing 'cache'... OKAY [  0.547s]
finished. total time: 0.547s

c:\mini-adb_inc>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.095s]
finished. total time: 0.095s

c:\mini-adb_inc>[COLOR="red"]fastboot flash zip PB31IMG.zip[/COLOR]
     sending 'zip' (176625 KB)... OKAY [ 24.227s]
                 writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 30.330s

c:\mini-adb_inc>[COLOR="red"]fastboot flash zip PB31IMG.zip[/COLOR]
     sending 'zip' (176625 KB)... OKAY [ 24.165s]
                 writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,9
INFO[RUU]UZ,radio,18
INFO[RUU]UZ,radio,23
INFO[RUU]UZ,radio,32
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,46
INFO[RUU]UZ,radio,51
INFO[RUU]UZ,radio,60
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,78
INFO[RUU]UZ,radio,87
INFO[RUU]UZ,radio,97
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,7
INFO[RUU]WP,radio,16
INFO[RUU]WP,radio,21
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,35
INFO[RUU]WP,radio,40
INFO[RUU]WP,radio,45
INFO[RUU]WP,radio,50
INFO[RUU]WP,radio,100
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,43
INFO[RUU]UZ,boot,83
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,42
INFO[RUU]WP,boot,85
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,20
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,73
INFO[RUU]UZ,recovery,99
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,20
INFO[RUU]WP,recovery,40
INFO[RUU]WP,recovery,60
INFO[RUU]WP,recovery,80
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,6
INFO[RUU]UZ,system,12
INFO[RUU]UZ,system,19
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,32
INFO[RUU]UZ,system,39
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,51
INFO[RUU]UZ,system,58
INFO[RUU]UZ,system,64
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,78
INFO[RUU]UZ,system,84
INFO[RUU]UZ,system,89
INFO[RUU]WP,system,0
INFO[RUU]WP,system,89
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,90
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,92
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,97
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,99
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,89
INFO[RUU]WP,system,89
INFO[RUU]WP,system,90
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,94
INFO[RUU]WP,system,95
INFO[RUU]WP,system,96
INFO[RUU]WP,system,97
INFO[RUU]WP,system,98
INFO[RUU]WP,system,99
INFO[RUU]WP,system,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
OKAY [118.439s]
finished. total time: 142.605s

c:\mini-adb_inc>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
     rebooting into bootloader... OKAY [  0.095s]
finished. total time: 0.095s

c:\mini-adb_inc>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.093s

c:\mini-adb_inc>

and if that works,when your phonr boots back up yull be on froyo and can finally continue with the last part of the guide to achieve s-off. i will be watching.

sweetb2006 · Mar 22, 2012

scotty85 said:
if the misc img hasnt been rewritten,then it would get the main version fail. i was thinking of suggesting this,but wanted to make sure we had exhausted all other possibilities before i suggested it,due to not wanting to add more confusion to an allready fustrated sweetb

i am inclined to agree... if youre formatting the card in the phone via usb cable,it could be a usb cable thing,an sd card thing,or who knows what,but at this point it looks like for one reason or another the prollem is the sd card.

im still not sure why the RUU wouldnt run either,unless htc sync or something is running on the PC and screwing with it.

i think at this time we should try and flash the PB31IMG in fastboot. just to keep things,in-thread,ill put some real quick directions here:

1)put PB31IMG into your android directory(if thats still what mini-adb inc is renamed in your system). you dont need to change the name of PB31IMG or android to make it work.

assuming you leave it named PB31IMG then open your cmd window and enter(only bold type. blue are just additional comments):

cd c:\android change to android directory

md5sums PB31IMG.zip this will output the md5 sum of the file you will flash. make sure it matches 31bb1611a0fa8197d447c0438426717e

adb devices should output your phones serial number

adb reboot bootloader will boot you into the fastboot screen(white with colored letters)

fastboot devices will again output serial number

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip PB31IMG.zip

you will see a green line on your phone as the file flashes.youll see outut in your cmd window. shortly after starting you will get a "FAILED!(remote: 90 hboot pre-update! please flush image again immediately). dont worry,this is normal.

fastboot flash zip PB31IMG.zip to flash it again. it will finish this time.

after you get a "finished" message:

fastboot reboot-bootloader this will take you back to the white fastboot screen

fastboot reboot your phone should reboot

heres how it should look in your cmd window:

Code:

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Scott> [COLOR=red]cd c:\mini-adb_inc[/COLOR] c:\mini-adb_inc>[COLOR=red]md5sums PB31IMG.zip[/COLOR] MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+ Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/ Type md5sums -h for help [Path] / filename MD5 sum ------------------------------------------------------------------------------- [c:\mini-adb_inc\] PB31IMG.zip 100% 31bb1611a0fa8197d447c0438426717e c:\mini-adb_inc>[COLOR=red]adb devices[/COLOR] adb server is out of date. killing... * daemon started successfully * HT117HJ00242 device c:\mini-adb_inc>[COLOR=red]adb reboot bootloader[/COLOR] c:\mini-adb_inc>[COLOR=red]fastboot devices[/COLOR] HT117HJ00242 fastboot c:\mini-adb_inc>[COLOR=red]fastboot erase cache[/COLOR] erasing 'cache'... OKAY [ 0.547s] finished. total time: 0.547s c:\mini-adb_inc>[COLOR=red]fastboot oem rebootRUU[/COLOR] ... OKAY [ 0.095s] finished. total time: 0.095s c:\mini-adb_inc>[COLOR=red]fastboot flash zip PB31IMG.zip[/COLOR] sending 'zip' (176625 KB)... OKAY [ 24.227s] writing 'zip'... INFOzip header checking... INFOshift signature_size for header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 FAILED (remote: 90 hboot pre-update! please flush image again immediately) finished. total time: 30.330s c:\mini-adb_inc>[COLOR=red]fastboot flash zip PB31IMG.zip[/COLOR] sending 'zip' (176625 KB)... OKAY [ 24.165s] writing 'zip'... INFOzip header checking... INFOshift signature_size for header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOstart image[radio] unzipping & flushing... INFO[RUU]UZ,radio,0 INFO[RUU]UZ,radio,9 INFO[RUU]UZ,radio,18 INFO[RUU]UZ,radio,23 INFO[RUU]UZ,radio,32 INFO[RUU]UZ,radio,41 INFO[RUU]UZ,radio,46 INFO[RUU]UZ,radio,51 INFO[RUU]UZ,radio,60 INFO[RUU]UZ,radio,69 INFO[RUU]UZ,radio,78 INFO[RUU]UZ,radio,87 INFO[RUU]UZ,radio,97 INFO[RUU]UZ,radio,100 INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,7 INFO[RUU]WP,radio,16 INFO[RUU]WP,radio,21 INFO[RUU]WP,radio,26 INFO[RUU]WP,radio,35 INFO[RUU]WP,radio,40 INFO[RUU]WP,radio,45 INFO[RUU]WP,radio,50 INFO[RUU]WP,radio,100 INFOstart image[boot] unzipping & flushing... INFO[RUU]UZ,boot,0 INFO[RUU]UZ,boot,43 INFO[RUU]UZ,boot,83 INFO[RUU]UZ,boot,100 INFO[RUU]WP,boot,0 INFO[RUU]WP,boot,42 INFO[RUU]WP,boot,85 INFO[RUU]WP,boot,100 INFOstart image[recovery] unzipping & flushing... INFO[RUU]UZ,recovery,0 INFO[RUU]UZ,recovery,20 INFO[RUU]UZ,recovery,43 INFO[RUU]UZ,recovery,73 INFO[RUU]UZ,recovery,99 INFO[RUU]UZ,recovery,100 INFO[RUU]WP,recovery,0 INFO[RUU]WP,recovery,20 INFO[RUU]WP,recovery,40 INFO[RUU]WP,recovery,60 INFO[RUU]WP,recovery,80 INFO[RUU]WP,recovery,100 INFOstart image[system] unzipping & flushing... INFO[RUU]UZ,system,0 INFO[RUU]UZ,system,6 INFO[RUU]UZ,system,12 INFO[RUU]UZ,system,19 INFO[RUU]UZ,system,25 INFO[RUU]UZ,system,32 INFO[RUU]UZ,system,39 INFO[RUU]UZ,system,45 INFO[RUU]UZ,system,51 INFO[RUU]UZ,system,58 INFO[RUU]UZ,system,64 INFO[RUU]UZ,system,71 INFO[RUU]UZ,system,78 INFO[RUU]UZ,system,84 INFO[RUU]UZ,system,89 INFO[RUU]WP,system,0 INFO[RUU]WP,system,89 INFO[RUU]UZ,system,89 INFO[RUU]UZ,system,89 INFO[RUU]UZ,system,90 INFO[RUU]UZ,system,91 INFO[RUU]UZ,system,92 INFO[RUU]UZ,system,93 INFO[RUU]UZ,system,94 INFO[RUU]UZ,system,94 INFO[RUU]UZ,system,96 INFO[RUU]UZ,system,96 INFO[RUU]UZ,system,97 INFO[RUU]UZ,system,98 INFO[RUU]UZ,system,99 INFO[RUU]UZ,system,100 INFO[RUU]WP,system,89 INFO[RUU]WP,system,89 INFO[RUU]WP,system,90 INFO[RUU]WP,system,91 INFO[RUU]WP,system,94 INFO[RUU]WP,system,94 INFO[RUU]WP,system,95 INFO[RUU]WP,system,96 INFO[RUU]WP,system,97 INFO[RUU]WP,system,98 INFO[RUU]WP,system,99 INFO[RUU]WP,system,100 INFOstart image[sp1] unzipping & flushing... INFO[RUU]UZ,sp1,0 INFO[RUU]UZ,sp1,100 INFO[RUU]WP,sp1,0 INFO[RUU]WP,sp1,100 OKAY [118.439s] finished. total time: 142.605s c:\mini-adb_inc>[COLOR=red]fastboot reboot-bootloader[/COLOR] rebooting into bootloader... OKAY [ 0.095s] finished. total time: 0.095s c:\mini-adb_inc>[COLOR=red]fastboot reboot[/COLOR] rebooting... finished. total time: 0.093s c:\mini-adb_inc>

and if that works,when your phonr boots back up yull be on froyo and can finally continue with the last part of the guide to achieve s-off. i will be watching.

Hopefully not too soon But... "Doing a happy dance"

Now just to achieve s-off!

iowabowtech · Mar 22, 2012

sweetb2006 said:
Hopefully not too soon But... "Doing a happy dance" Now just to achieve s-off!

So it worked?

sweetb2006 · Mar 22, 2012

iowabowtech said:
So it worked?

Sure did...!!! Now I'm just Very carefully reading how to install Unrevoked Forever... A bit worried that since the issue seams to have possible been my sd card, the unrevoked via sd card may not work. If not, what then?

Root [How To] Root 2.3.4/downgrade and Get S-off

Extreme Android User

Member

Extreme Android User

Member

Extreme Android User

Extreme Android User

Member

Member

root@android:/ #

Member

Member

Extreme Android User

Member

Attachments

root@android:/ #

Careful, They're sharp!!

Member

Member

Careful, They're sharp!!

root@android:/ #

Careful, They're sharp!!

Extreme Android User

Extreme Android User

Member

root@android:/ #

Member