Are you sure you're not.accidentally in.disk.drive mode?
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
The Following User Says Thank You to scotty85 For This Useful Post:
Are you sure you're not.accidentally in.disk.drive mode?
100% positive... Even looked, for the millionth time as soon as i read your question. Even made sure phone stayed lit up through the whole process. Could it be anything to do with the PB31IMG, or just mtd0.img at this point?
actually,now that i take a closer look,you are just missing a coulple commands. you need to chmod 0755 /data/local/flash_image
before you can ./flash_image misc /sdcard/mtd0.img
when you are doing the commands,look carefully at my codebox in post 1... yours will need to look like that.
if you have run thru all this once allready,you can possibly just boot to bootloader and provided everything you did was correct,and your PB31IMG is on the root of your sd card(not internal storage) then it will flash the downgrade RUU.
back to work,but ill try and keep watvching
The Following User Says Thank You to scotty85 For This Useful Post:
actually,now that i take a closer look,you are just missing a coulple commands. you need to chmod 0755 /data/local/flash_image
before you can ./flash_image misc /sdcard/mtd0.img
when you are doing the commands,look carefully at my codebox in post 1... yours will need to look like that.
if you have run thru all this once allready,you can possibly just boot to bootloader and provided everything you did was correct,and your PB31IMG is on the root of your sd card(not internal storage) then it will flash the downgrade RUU.
back to work,but ill try and keep watvching
Yea, missing the chmod was just an oops on that one. So, I did it again, made sure I did Every line & same results. My only option left at this point is to try manually boot to bootloader. I'm just scared of something bad happening, if it Doesn't work. But oh well 'eh. I am curious if/how I will know if it works?
UPDATE
Manual reboot to bootloader Failed. I "think" it said it could not findPB31IMG (somewhat quick to go away blue/green words, after I chose fast boot(which than takes me to where I can "shut down", which by the way... I am having issues for a minute now, not being able to actually shut down(just reboots)... So anyway, I have PB31IMG named PB31IMG.zip & No, it's not being read as .zip .zip
I'm starting to feel hopeless... =(
Last edited by sweetb2006; March 19th, 2012 at 03:44 PM.
Yea, missing the chmod was just an oops on that one. So, I did it again, made sure I did Every line & same results. My only option left at this point is to try manually boot to bootloader. I'm just scared of something bad happening, if it Doesn't work. But oh well 'eh. I am curious if/how I will know if it works?
UPDATE
Manual reboot to bootloader Failed. I "think" it said it could not findPB31IMG (somewhat quick to go away blue/green words, after I chose fast boot(which than takes me to where I can "shut down", which by the way... I am having issues for a minute now, not being able to actually shut down(just reboots)... So anyway, I have PB31IMG named PB31IMG.zip & No, it's not being read as .zip .zip
I'm starting to feel hopeless... =(
And you are definitely formatted to fat32?
At this point it would be worth the effort to format it again and don't use the quick format option.
As mentioned a bunch of times in this thread, the only reasons the phone won't see a PB31IMG.zip file on the root of the SD card is either the file is named wrong or the card isn't formatted to fat32 properly(could also try a different SD card).
Last edited by sdrawkcab25; March 19th, 2012 at 06:11 PM.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
And you are definitely formatted to fat32?
At this point it would be worth the effort to format it again and don't use the quick format option.
As mentioned a bunch of times in this thread, the only reasons the phone won't see a PB31IMG.zip file on the root of the SD card is either the file is named wrong or the card isn't formatted to fat32 properly(could also try a different SD card).
I will try re formatting, thanks...
As for trying a different SD card? Mine isn't removable.
And you are definitely formatted to fat32?
At this point it would be worth the effort to format it again and don't use the quick format option.
As mentioned a bunch of times in this thread, the only reasons the phone won't see a PB31IMG.zip file on the root of the SD card is either the file is named wrong or the card isn't formatted to fat32 properly(could also try a different SD card).
Ok... so reformatting got me to the reboot step... But the PB31IMG.zip file isn't being found. I had it named with .zip in the name, as i though was supposed to & besides, if i didn't, my phone didn't see it as a zip. And no, it wasn't .zip.zip. All I can think to try at this point is taking the .zip off, as i don't have the money for a new card, at the moment. Thanks bunches for the help though! Any other suggestions would be greatly appreciated.
Also, is it normal for the sd card to have two different drives?
UPDATE
Of course renaming it without .zip didn't work either. So, must it be my sd card??? Tell me it isn't so! =(
Last edited by sweetb2006; March 19th, 2012 at 09:58 PM.
Reason: Update
are you 100% sure that you put PB31IMG onto your sd card,and not your phones internal memory? 3 drives will typically pop up when you plug in an htc phone... make sure to put PB31IMG on the one that is your removeable sd card.
also the card does have to be "FAT32" it cannot be just plain "FAT" or anything else.
The Following User Says Thank You to scotty85 For This Useful Post:
are you 100% sure that you put PB31IMG onto your sd card,and not your phones internal memory? 3 drives will typically pop up when you plug in an htc phone... make sure to put PB31IMG on the one that is your removeable sd card.
also the card does have to be "FAT32" it cannot be just plain "FAT" or anything else.
Yep, 100% sure it's on the sd card. I have, checked & renamed the file with ES File Explorer, under /sdcard/. & yea, I figured out the third pop up is the phones storage & no, I at no point had put the file there. & yes, I formated it to Fat32 & Not quick mode. It found/recognized the mtd0.img so Hopefully that means it's not a card issue???
So, any hope or doomed to buy a new sd card?
Last edited by sweetb2006; March 19th, 2012 at 10:54 PM.
yuo should not have to buy a new card. /sdcard/ on file explorer may not be the sd card. wouldnt hurt to pull the card out,put it in a card reader,and make sure that where the file is.
as was said,the rules for PB31IMG to flash are simple:
1)root of sd card
2)proper,zipped file(leave zipped,make sure md5 sum matches)
3)sd card formatted FAT32
4)proper name(phone must see PB31IMG.zip so name with windows to "PB31IMG" )
i know you have checked and double checked,but one of those things is not right if its not finding and checking the file.
an alternative since youre becoming fustrated might be to run an RUU on your PC,its alot more straightforward: download,run as administrator(if possible),then follow on screen prompts and plug in phone when directed.
yuo should not have to buy a new card. /sdcard/ on file explorer may not be the sd card. wouldnt hurt to pull the card out,put it in a card reader,and make sure that where the file is.
as was said,the rules for PB31IMG to flash are simple:
1)root of sd card
2)proper,zipped file(leave zipped,make sure md5 sum matches)
3)sd card formatted FAT32
4)proper name(phone must see PB31IMG.zip so name with windows to "PB31IMG" )
i know you have checked and double checked,but one of those things is not right if its not finding and checking the file.
an alternative since youre becoming fustrated might be to run an RUU on your PC,its alot more straightforward: download,run as administrator(if possible),then follow on screen prompts and plug in phone when directed.
1)root of sd card - Will see... 2)proper,zipped file(leave zipped,make sure md5 sum matches) - Check 3)sd card formatted FAT32- Check 4)proper name(phone must see PB31IMG.zip so name with windows to "PB31IMG" ) If I name it "without" the.zip, phone doesn't see it as a zip file. So?
I don't have a card reader anymore. So what if I take the sd card out, boot back up & then see if ES Explorer sees the card then????
And... What than is the RUU for & what am I to do with it?
UPDATE
Removed sd card, booted, ES Explorer stated something like... "No sd card found or isn't mounted"... For me at least, that's pretty good confirmation that it is my sd card that it is seeing & where PB31IMG is.?.
I do get now, what you meant with naming it with windows.
Last edited by sweetb2006; March 19th, 2012 at 11:39 PM.
And... What than is the RUU for & what am I to do with it?
Quote:
Originally Posted by scotty85
an alternative since youre becoming fustrated might be to run an RUU on your PC,its alot more straightforward: download,run as administrator(if possible),then follow on screen prompts and plug in phone when directed.
The Following User Says Thank You to scotty85 For This Useful Post:
Alrighty... Tried everything else, other than installing a new super user program, though I have doubts this is the issue. So, here I go with the RUU... Just wanted to ask, should I go ahead & delete the pb31img of my sd card?
AND...
What about disabling internet/wifi connection during the adb process, could this make any difference? I don't have service, just wifi.
Last edited by sweetb2006; March 20th, 2012 at 09:13 AM.
Now, as I did read could happen (though those I read about, still had no success with new usb plug) the program isn't able to tell that my usb plus IS plugged & working.
Does this mean I will have this problem with all custom rom installs? Ugh! I would ultimately like to have a custom rom, although I'm not sure it is necessary for what I am ultimately trying to achieve. Although I am fairly certain that my ultimate goal will require s-off.
Starting to think I should just abort Scotty.
Should I still have debugging, etc on for the RUU process? Maybe that's it? Though I doubt it. Humbug!
Last edited by sweetb2006; March 20th, 2012 at 09:51 AM.
Sounds like Windows just isn't recognizing your phone. I wonder if the modified USB driver is just not compatible with the RUU? Worst case, temporarily download HTC Sync:
Don't actually run the program once downloaded, it comes packaged with the stock Inc USB driver. Then plug in the phone in charge mode and with the phone still plugged in, reboot the PC. Should autodetect the phone upon reboot now that the driver is available. Verify that it gets detected and installs the driver.
Note: If you go this route and it works to perform the RUU, you may want to uninstall HTC sync before continuing with Scotty's root procedure as it may interfere. Honestly I thought your current driver should be working but for some reason it isn't so...may be worth a shot.
The Following 2 Users Say Thank You to iowabowtech For This Useful Post:
Sounds like Windows just isn't recognizing your phone. I wonder if the modified USB driver is just not compatible with the RUU? Worst case, temporarily download HTC Sync:
Don't actually run the program once downloaded, it comes packaged with the stock Inc USB driver. Then plug in the phone in charge mode and with the phone still plugged in, reboot the PC. Should autodetect the phone upon reboot now that the driver is available. Verify that it gets detected and installs the driver.
Note: If you go this route and it works to perform the RUU, you may want to uninstall HTC sync before continuing with Scotty's root procedure as it may interfere. Honestly I thought your current driver should be working but for some reason it isn't so...may be worth a shot.
I will give that a try I suppose. However, windows did once already recognize & install the drivers & I haven't rebooted nor changed anything since than. Oh & if windows isn't recognizing phone, would I not have Not been able to do anything with the phone, via computer thus far? Yep, double checked & usb drivers are installed. Perhaps not good enough drivers vs. HTC's drivers?
Last edited by sweetb2006; March 20th, 2012 at 11:45 AM.
Might also try simply starting your phone in fastboot mode.
And keeping fastboot checked & than run the RUU?
Tried to load with fastboot, when i do, it checks the PB31IMG & of course fails. Deleted said image from sd card, yet to be able to get phone to load into mode where i can chose fast boot, perhaps that is because it is loading with fast boot? Argh! Sorry for such noob questions. lol
Should the phone be in charge only or disc drivewhen running RUU??????
Last edited by sweetb2006; March 20th, 2012 at 12:35 PM.
Might also try simply starting your phone in fastboot mode.
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"
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.
The Following User Says Thank You to scotty85 For This Useful Post:
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. 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.
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.
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.
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.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
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.
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.
The Following User Says Thank You to iowabowtech For This Useful Post:
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...
Quote:
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.
Last edited by sweetb2006; March 20th, 2012 at 10:26 PM.
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?
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.
Last edited by sweetb2006; March 21st, 2012 at 09:38 AM.
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.
The Following 2 Users Say Thank You to iowabowtech For This Useful Post:
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.
The Following 2 Users Say Thank You to Bob Cat For This Useful Post:
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...
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!
"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.
The Following 2 Users Say Thank You to Bob Cat For This Useful Post:
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?
The Following 3 Users Say Thank You to iowabowtech For This Useful Post:
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.
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
Quote:
Originally Posted by sdrawkcab25
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.
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> cd c:\mini-adb_inc
c:\mini-adb_inc>md5sums PB31IMG.zip
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>adb devices
adb server is out of date. killing...
* daemon started successfully *
HT117HJ00242 device
c:\mini-adb_inc>adb reboot bootloader
c:\mini-adb_inc>fastboot devices
HT117HJ00242 fastboot
c:\mini-adb_inc>fastboot erase cache
erasing 'cache'... OKAY [ 0.547s]
finished. total time: 0.547s
c:\mini-adb_inc>fastboot oem rebootRUU
... OKAY [ 0.095s]
finished. total time: 0.095s
c:\mini-adb_inc>fastboot flash zip PB31IMG.zip
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>fastboot flash zip PB31IMG.zip
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>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.095s]
finished. total time: 0.095s
c:\mini-adb_inc>fastboot reboot
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.
Last edited by scotty85; March 22nd, 2012 at 06:07 AM.
The Following 3 Users Say Thank You to scotty85 For This Useful Post:
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> cd c:\mini-adb_inc
c:\mini-adb_inc>md5sums PB31IMG.zip
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>adb devices
adb server is out of date. killing...
* daemon started successfully *
HT117HJ00242 device
c:\mini-adb_inc>adb reboot bootloader
c:\mini-adb_inc>fastboot devices
HT117HJ00242 fastboot
c:\mini-adb_inc>fastboot erase cache
erasing 'cache'... OKAY [ 0.547s]
finished. total time: 0.547s
c:\mini-adb_inc>fastboot oem rebootRUU
... OKAY [ 0.095s]
finished. total time: 0.095s
c:\mini-adb_inc>fastboot flash zip PB31IMG.zip
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>fastboot flash zip PB31IMG.zip
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>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.095s]
finished. total time: 0.095s
c:\mini-adb_inc>fastboot reboot
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!
The Following User Says Thank You to sweetb2006 For This Useful Post:
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?
The Following User Says Thank You to sweetb2006 For This Useful Post:
1Likes
But oh well 'eh. I am curious if/how I will know if it works?
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.
lol 
