[Q] Can I flash PC36IMG.zip from recovery to unroot? - EVO 4G Q&A, Help & Troubleshooting

Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks

pipefitter said:
Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
Click to expand...
Click to collapse
Make sure PC36IMG.ZIP IS ALL CAPS look at my guide all the links needed to unroot

pipefitter said:
Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
Click to expand...
Click to collapse
Make sure the PC36IMG.zip file doesn't have an additional suffix (exC36IMG.ZIP.zip) which is usually the case when the directions include renaming the original file to PC36IMG.zip. As for flashing it from within recovery, not unless it was designed to be flashed from recovery.

reaper24 said:
Make sure PC36IMG.ZIP IS ALL CAPS look at my guide all the links needed to unroot
Click to expand...
Click to collapse
Just to avoid any confusion for the OP, a quick correction. It's got to be PC36IMG.zip. We don't want the .zip in capitals. Only the PC36IMG is capitals. .zip remains lower case.
To the OP, as has been mentioned, be sure it's spelled correctly. Also, be sure it's on the main directory of your SD card, and not in any folders. If you're sure of both of those things, then double check that the file isn't corrupted. Can you open the zip file on your pc without getting an error?

As a rule of thumb, you don't ever want to flash PC36IMG.zip from recovery. If it won't flash from hboot, then there's something not right with the file (all of the above suggestions are good), but it's pretty much going to be a bad idea to flash that zip from recovery.

BAD PC36IMG.zip
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks

pipefitter said:
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
Click to expand...
Click to collapse
Why are you unzipping the file? If I'm not mistaken, you rename PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip to PC36IMG.zip and flash from the bootloader.

k2buckley said:
Just to avoid any confusion for the OP, a quick correction. It's got to be PC36IMG.zip. We don't want the .zip in capitals. Only the PC36IMG is capitals. .zip remains lower case.
To the OP, as has been mentioned, be sure it's spelled correctly. Also, be sure it's on the main directory of your SD card, and not in any folders. If you're sure of both of those things, then double check that the file isn't corrupted. Can you open the zip file on your pc without getting an error?
Click to expand...
Click to collapse
dougjamal said:
Why are you unzipping the file? If I'm not mistaken, you rename PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip to PC36IMG.zip and flash from the bootloader.
Click to expand...
Click to collapse
Just trying to verify that it is a good download even though the md5 matches. Nobody seems to understand that I know what I'm doing. This is what is happening when i HBOOT:
SUPERSONIC EVT3 SHIP S-ON
MICROCHIO-041f
TOUCH PANEL-ATMELC03_16ac
HBOOT 2.10.0001
RADIO 2.15.00.11.11.19
HBOOT reads as follows
SD Checking...
Loading...[PC36DIAG.zip]
No Image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36IMG.nbh]
No image or wrong image!
So, I decided to try running RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe from my PC. It starts out fine and says it is rebooting to BOOTLOADER, then it reboots to the HTC screen and goes no farther. The RUU says waiting for BOOTLOADER for abut 45 seconds and then says a connection cannot be established.

pipefitter said:
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
Click to expand...
Click to collapse
http://db.tt/gqTAPS1
Here's a link from my dropbox to the 3.70 software PC36IMG.
And by the way, I don't think that anyone assumed you didn't know what you are doing. There is truly know way of knowing someone's level of knowledge on any given subject, when we're all strangers on the internet. It's sometimes better to be sure that all bases have been covered, and that something simple wasn't overlooked. troubleshooting 101: start with the simplest stuff first. No matter what it is that you're troubleshooting. Anyways, hopefully the file from my dropbox will work for you.
have you tried running the RUU from fastboot mode? I see you had a connection error when you tried before. Boot into fastboot, from the bootloader. Or if you have adb setup type "adb reboot bootloader" and that should boot you to fastboot. Then connect your USB and try running the RUU again. It has a better chance of being recognized that way. Good luck.

pipefitter said:
Just trying to verify that it is a good download even though the md5 matches. Nobody seems to understand that I know what I'm doing....
Click to expand...
Click to collapse
Please don't be offended, my friend. Like my good friend, k2buckley stated, we have no idea of the level of knowledge that a person we are trying to help has and personally, every time I assume that a person knows a certain routine or technique, I quickly find that I am mistaken. In addition, I find that people will only post a small portion of what they have actually done and that makes it a tad difficult at times for those of us trying to help. teh roxxorz, k2buckley, HipKat, myself and many others spend a great deal of time in these forums trying to help when we can so please be patient with us.....

SOLVED!
k2buckley said:
http://db.tt/gqTAPS1
Here's a link from my dropbox to the 3.70 software PC36IMG.
And by the way, I don't think that anyone assumed you didn't know what you are doing. There is truly know way of knowing someone's level of knowledge on any given subject, when we're all strangers on the internet. It's sometimes better to be sure that all bases have been covered, and that something simple wasn't overlooked. troubleshooting 101: start with the simplest stuff first. No matter what it is that you're troubleshooting. Anyways, hopefully the file from my dropbox will work for you.
have you tried running the RUU from fastboot mode? I see you had a connection error when you tried before. Boot into fastboot, from the bootloader. Or if you have adb setup type "adb reboot bootloader" and that should boot you to fastboot. Then connect your USB and try running the RUU again. It has a better chance of being recognized that way. Good luck.
Click to expand...
Click to collapse
dougjamal said:
Please don't be offended, my friend. Like my good friend, k2buckley stated, we have no idea of the level of knowledge that a person we are trying to help has and personally, every time I assume that a person knows a certain routine or technique, I quickly find that I am mistaken. In addition, I find that people will only post a small portion of what they have actually done and that makes it a tad difficult at times for those of us trying to help. teh roxxorz, k2buckley, HipKat, myself and many others spend a great deal of time in these forums trying to help when we can so please be patient with us.....
Click to expand...
Click to collapse
Sorry guys, I was getting frustrated. I'm not used to failure. I'm no computer genius, but I pride myself in being able to follow and understand directions. I am officially unrooted!
This is what I did...
1)Uninstalled and reinstalled HTC drivers
2) Flashed a stock, rooted, odexed ROM. I was running Azrael 4.0. Don't know if this made any difference, but I tried the next steps before flashing the stock ROM and had no success.
3) Booted into FASTBOOT
4)Attached USB cable to computer and the phone immediately showed FASTBOOT USB
5) Ran RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe (this RUU matched my HBOOT and Radio)
6)Followed on-screen directions for RUU and 10 minutes later my phone was unrooted, completely stock.
Your success may vary. I had many people respond with the same mantra of "Do A, B, & C and your phone will be unrooted". By now, we should all know that each phone is different and sometimes they just won't cooperate. Don't get frustrated. Just keep at it and eventually you will solve your dilemma. I truly appreciate all the help from everyone on XDA!
Regards,
Mark

pipefitter said:
Sorry guys, I was getting frustrated. I'm not used to failure. I'm no computer genius, but I pride myself in being able to follow and understand directions. I am officially unrooted!
This is what I did...
1)Uninstalled and reinstalled HTC drivers
2) Flashed a stock, rooted, odexed ROM. I was running Azrael 4.0. Don't know if this made any difference, but I tried the next steps before flashing the stock ROM and had no success.
3) Booted into FASTBOOT
4)Attached USB cable to computer and the phone immediately showed FASTBOOT USB
5) Ran RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe (this RUU matched my HBOOT and Radio)
6)Followed on-screen directions for RUU and 10 minutes later my phone was unrooted, completely stock.
Your success may vary. I had many people respond with the same mantra of "Do A, B, & C and your phone will be unrooted". By now, we should all know that each phone is different and sometimes they just won't cooperate. Don't get frustrated. Just keep at it and eventually you will solve your dilemma. I truly appreciate all the help from everyone on XDA!
Regards,
Mark
Click to expand...
Click to collapse
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.

k2buckley said:
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
Click to expand...
Click to collapse
+1...........Take care....
posting & replying via the XDA Premium app.

S-ON
k2buckley said:
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
Click to expand...
Click to collapse
Yes, I flashed s-on with no problems. That's why I was getting so frustrated with the rest of the procedure.
Thanks everyone.

Related

[Q] unrooting the evo

I know theres a bajillion threads out there already on this subject, but i cant find the right answer anyway. Im sending a friends evo back to sprint for a replacement, and have done step one of two in unrooting the evo. I used the unrevoked s-on tool sucessfully and now have the phone with "s-on", but when i try to flash the pc36 file, the phone doesnt seem to read it in the bootloader screen, even though its saved onto the sd-card. I have tried to download a bunch of different files to rule out the possibility of a bad download, but i still get the same thing. In the bootloader screen it still says "no image found" or "wrong file". Any ideas of what to do? Thanks.
Make sure PC36IMG.ZIP is all caps. Other wise it won't work if u need ruu look at my guide in my Sig.
funny how something as simple as changing the name fixes it lol one more thing though. the bootloader tried to update, but the file it was updating was an older one. Can u post up a link for a newer one, and how exactly do u know which RUU to use?
sW333t11 said:
funny how something as simple as changing the name fixes it lol one more thing though. the bootloader tried to update, but the file it was updating was an older one. Can u post up a link for a newer one, and how exactly do u know which RUU to use?
Click to expand...
Click to collapse
This is what you need man. Hope this helps. Drop me a line if this helps or you need anything else.
http://goo-inside.me/evo/stock/ruu/...15.00.11.19_NV_1.90_release_161482_signed.zip
Got a question man. At the bootloader screen the phone is recognizing the pc36img very briefly, with the blue download bar at the top right of the screen, it loads up, and then it just goes back to the main bootloader screen without asking me to update or anything. whats going on now lol
I'm having the same issue on my phone. It unzips the file, verify's the file and then just goes back to hboot screen. I've tried the RUU exe and it doesn't detect my phone at all.
Any ideas?
https:// spreadsheets.google.com/spreadsheet/viewform?formkey=dDh6ekc0c2dIbGYyRHFrT09PUWpscnc6MQ
That form fixed my problems! Had to download a different PC36IMG to get it working.
the link is broken post a new one plz.
this whole thing is so easy, all i need is the right PC36IMG file. I have tried so many different ones and none of them work! Can someone please post the right link to this thread for the 2.10 hboot?
i have 2.10 hboot n the one in reapers post is the one i used. are u sure the file extension isn't being hidden and ur naming it PC36IMG.ZIP.ZIP?????
i got it fixed guys, i just had everything mixed up with the name and files. for anyone referencing to this page for help make sure the name is PC36IMG.ZIP and matches ur hboot.

[Q] RUU restore for warranty fails: error 140. Anyone can help?

Hi guys,
I own a Fastweb branded desire and back key isn't working anymore.
So I'm tring to restore the branded official rom for warranty.
I got s-off and root and my gold card is in.
I've flashed the old modaco r6 rom to avoid main version is older and flashed downgrade hboot(alpharev) too.
When I start the ruu hboot 0.75 and old radio are flashed properly, but I still have custom splash and cwm recovery also system is untouched.
Ruu stops with error 140 bootloader problem.
I'm still able to flash custom roms and I can s-off again, but I really don't know what to do.
Any help?
Thanks.
Best regards.
Jus
You're in the wrong section dude, read the rules.. all questions go to q&a section
This sections is set aside for development only
Sent from my HTC Desire using XDA App
Sorry mate, is there a way to change section?
jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.
FreshNClean said:
jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.
Click to expand...
Click to collapse
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.
Tbh mate I'm not sure how to change it lol.. mayb delete and repost in q&a..
Just beware of flames coming your way lol
Sent from my HTC Desire using XDA App
jussy said:
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.
Click to expand...
Click to collapse
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire
3f1f37 said:
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire
Click to expand...
Click to collapse
Sorry for my bad english but what you said is what I've done.
1-root and s-off.
2-flash downgrade hboot(alpharev).
3-put PB99IMG.zip (extract as said from my branded ruu) on sd card root.
4-boot power + vol down.
5-It starts, step 1 goes well then at the end of step 2 screen became black and came back with 0.75 hboot s-on and if I try again it gives me main version is older.
So I can only reboot, reflash a rom and s-off it again.
Never ending loop...
Thanks anyway.
You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk
jhonybravo4u said:
You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I've got my gold card already in.
Sadly there's only one ruu for my carrier.
I can flash a generic froyo ruu but it's not good for warranty.
I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.
mr_norris said:
I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.
Click to expand...
Click to collapse
It seems you didn't got the problem.
Thanks anyway.
I did it!!!!
Thanks to this guide http://forum.xda-developers.com/showthread.php?t=821809
and all of you.
So many thanks.
Sorry guys I got an other problem...
Now this is the second time I bring it to assistence (last time was for vol down) and when they give it back to me it was updated to froyo.
I'm facing problem with 1.15=>1.21 OTA, installation is aborted due to status 7 (if some one can help I'll post the full error message).
Unfortunetly the ruu I've used is the only one from my carrier.
Will they know that my phone was updated by them and I'll lose my warranty?
Any idea about fixing status 7?
Many thanks.
Best regads,
Jussy

Is this the 4.08.605.15 RUU?

Okay, links first: PB31IMG.zip and PDM_4.08.605.15_release.zip
I was tooling around the intarwebs wondering if a 4.08.605.15 RUU had ever made itself available, and stumbled across this VZW Community thread. All the way at the last message I noticed a user linking to an RUU on dev-host.org.
So I'm thinking to myself, "Self, that's really unusual, especially for a message reportedly sent to the poster from HTC."
So I follow the link. It's going to what appears to be the 4.08.605.2 RUU. Slightly disappointing, but I decide to click on the username to see what else they might have publicly posted. There's a number of interesting files available, but inside the ROMs folder I notice a recently uploaded PB32IMG.zip of an appropriate size for our phones.
So I download it.
Inside most of the files are timestamped May 29, 2012, and the android-info.txt file contains the following:
Code:
modelid: PB3120000
cidnum: VZW__001
mainver: 4.08.605.15
hbootpreupdate:3
:good:
The included hboot appears to be 1.07.0000 (!!!). There's also a ramdisk.img and the radio.img matches the 2.15.10.12.20 radio I had (as opposed to 2.15.10.07.07 that came with 4.08.605.2). boot.img, recovery.img, and system.img are all different as well, but I don't have anything immediately handy at work to mount the images and diff their contents with.
Now, this might be a fake, but it's a lot of work to go through to build.
I kinda need my incredible since it's my phone and I'm not down with guinea-pigging my real device on stuff like this, but I thought some devs or more intrepid users might want to check it out and see if it's legit.
Should that link go down, I kept a copy.
Edit: Added second link to PDM_408.605.15_release.zip. This zip file contains both the PB31IMG.zip (SHA-1 identical to the first link) and the RUU Utility (amongst other things) digitally signed by HTC. I'm pretty sure this is legit. Got a copy of this too...
It does appear to be legit. But im not sure how to tell for sure other than finding someone who is s-on, and seeing if it flashes.
Im gonna flash it and see what happens, but im s-off.
Let me know what you find. Would there be a way back to s-off if one unlocks their bootloader?
ardax said:
Let me know what you find. Would there be a way back to s-off if one unlocks their bootloader?
Click to expand...
Click to collapse
It does flash 4.08.605.15, so I'm gonna say its the real deal. Great find.
What do you mean way back to s-off? As in can you get s-off by unlocking the bootloader, or if you unlock the bootloader will you lose s-off.
Sorry, that was rather obtuse. I was just thinking that if one was s-on and flashed the RUU, would they be able to regain s-off? I haven't had to research rooting an Inc in a looong time, though I suppose with an unlockable bootloader it wouldn't be as much of an issue. (Oh look, you have a thread about how to do it! How about that.)
I wonder what else is posted on that account that nobody else has seen before?
ardax said:
Sorry, that was rather obtuse. I was just thinking that if one was s-on and flashed the RUU, would they be able to regain s-off? I haven't had to research rooting an Inc in a looong time, though I suppose with an unlockable bootloader it wouldn't be as much of an issue. (Oh look, you have a thread about how to do it! How about that.)
I wonder what else is posted on that account that nobody else has seen before?
Click to expand...
Click to collapse
I looked at all the files, and this ruu seems to be the only file for the incredible.
Not just for the Incredible, but for other phones too. There's a lot of what appear to be RUU zip files for devices that have been recently uploaded. The Evo 4G, Evo 3D, Amaze, and Sensation at a glance.
Help
ardax and cmlusco,
Do you guys happened to keep a copy of the RUU for this version
(4.08.605.15)? - the RUU file in the 2nd link is no longer valid.
Here's my situation and hope it will help someone in this community:
I was new to this. I got an old Droid Incredible from someone. The device
was installed with various program and was reported 'space low'. I add
a 16GB SD and installed Maps.Me lite. Not long after that the thing crashed.
I was trapped in the boot loop.
I was able to unlock the bootloader. But I was not able to get to s-off, since
it seems that it requires the device to be able to boot up or enter into the
debug mode, which I did not do when the device was OK.
I played around and the flash of clockworkmod is of no effect. The flash
of system, boot, and recovery all failed to bring the the device out of the
boot loop. I tried some SD PB31IMG.zip and all failed. The only thing I
have been able to do is RUU with the 4.08.605.2, which downgraded from
4.08.605.19. Earlier version give me the HBoot version error.
Since the 4.08.605.2 is a small file about 8MB. It may not change the
system much to bring the device out of the boot loop and since the
only thing I have been successful is with RUU. If you guys still have
the RUU around, I think it may do the trick for me - I have been
look abound on the web but haven't find a copy of it.
Thanks.
Duncan
The RUU is still available at http://dinc.does-it.net/Stock_Images/4.08.605.15/
I think that's cmlusco's site.
ardax,
Thanks for quick reply.
Sorry for a newbie's question:
I thought RUU is a .exe file that can execute under the Windows?
For a zip file, all I know how to handle it is put in a FAT32 SD card
and boot the Incredible into HBoot - which I have tried for some
PB31IMG.zip file and haven't have any luck - I do not know the
reason why it is failed.
Is doing this way with zip file the same as RUU?
Thanks.
UPDATE: I just tried the zip file by putting it on a FAT32 SD card and
boot into fastboot. Still reporting No Imange or Wrong Image.
-- Not working. Still trapped in the Boot Loop.
Try flashing from fastboot then. I don't remember if this will work with an unlocked bootloader though.
The basic gist of it is this:
* Reboot into bootloader
* run "fastboot.exe oem rebootRUU"
* Once you're in RUU mode, "fastboot.exe flash zip PB31IMG.zip" (The zip file needs to be on your PC.)
* You'll most likely get an error pretty quickly telling you to try again (right after the hboot pre-update), so rerun the previous command
* With all good luck, watch the flash go for a few minutes
* When it's done run "fastboot.exe reboot"
You should be back to stock. Now you can re-unlock the bootloader if needed and/or try to gain S-OFF.
If you're not comfortable with this procedure, I'd recommend looking for more explicit step-by-step instructions.
Does anyone still have the links for this? Or can the re-up them?
ardax said:
Try flashing from fastboot then. I don't remember if this will work with an unlocked bootloader though.
The basic gist of it is this:
* Reboot into bootloader
* run "fastboot.exe oem rebootRUU"
* Once you're in RUU mode, "fastboot.exe flash zip PB31IMG.zip" (The zip file needs to be on your PC.)
* You'll most likely get an error pretty quickly telling you to try again (right after the hboot pre-update), so rerun the previous command
* With all good luck, watch the flash go for a few minutes
* When it's done run "fastboot.exe reboot"
You should be back to stock. Now you can re-unlock the bootloader if needed and/or try to gain S-OFF.
If you're not comfortable with this procedure, I'd recommend looking for more explicit step-by-step instructions.
Click to expand...
Click to collapse
Sorry, I don't have the files anymore, since my Droid Incredible is long since dead.

Cannot access recover mode

So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
papercutout said:
So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
Click to expand...
Click to collapse
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
abaaaabbbb63 said:
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
Click to expand...
Click to collapse
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
papercutout said:
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
Click to expand...
Click to collapse
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
abaaaabbbb63 said:
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
Click to expand...
Click to collapse
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
papercutout said:
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
Click to expand...
Click to collapse
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site :http://www.htcdev.com/bootloader, and then try installing a custom recovery.
abaaaabbbb63 said:
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site and then try installing a custom recovery.
Click to expand...
Click to collapse
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
papercutout said:
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
Click to expand...
Click to collapse
You download this:
http://forum.xda-developers.com/showthread.php?p=28277117
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
abaaaabbbb63 said:
You download this:
http://forum.xda-developers.com/attachment.php?attachmentid=1631968&d=1357780284
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
papercutout said:
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
Click to expand...
Click to collapse
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
jmcclue said:
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
Click to expand...
Click to collapse
Sorry jmc. Will do
abaaaabbbb63 said:
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Click to expand...
Click to collapse
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
papercutout said:
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
Click to expand...
Click to collapse
Try using a different USB port.
abaaaabbbb63 said:
Try using a different USB port.
Click to expand...
Click to collapse
Nope, nada. I tried v0.94 too. Nothing again. I guess I'll need to get a key. Damn that hboot 1.03!
At least the phone is actually WORKING now though, thanks to you, appreciated.

[Q] Returning to Stock

Hi all. Have not been to this site in a while.
I have an 8181 Desire (Australia - Telstra). Presently running CM7 and Runnymede ROM, with 4EXT recovery.
Before I go too far...yes, I know I should use SEARCH, but honestly I have forgotten so much about modding, I really have no idea what I'm doing anymore...
I want to return to stock and pass the phone on to a friend. I have so far installed Telstra RUU to my PC and I have run Alpharev downgrade. I have now moved to reboot and run the RUU, but I keep booting straight to Bootloader screen, not progressing to main screen. I know this means I have missed a step or forgotten something, but have nfi what that might have been.
I never really learned to flash with Fastboot, so am I able to avoid that and continue the way I am a little more familiar with?
Thanks heaps for any help. In the meantime I will continue to SEARCH and see what I can see. Cheers.
Use the troubleshooting guide stickied to the top of q&a
Search for and then run the 2.3.3 GB RUU
I've found the 2.3.3 GB Telstra RUU and renamed to PB99IMG.zip, placed on SD card. I see a blue progress bar and then "would you like to reboot now?" Each time I reboot, I am straight back to Bootloader screen (not stuck in bootloop, as such).
Working my way thru the TS Guide, but I'm pretty sure I have missed a step or forgotten something along the way... Wondering if phone won't boot properly because I am now running the Downgrade HBoot, which is obviously not compatible with Runnymede.
Am I able to uninstall 4EXT touch? Would like to simplify things as much as I can and would be happy with standard CWM for flashing purposes...
Will keep playing today. I know the phone isn't bricked, so I'm not panicking. Yet.
Try flashing the stock hboot, then RUU
Currently if only flashed the downgrade.img, it's just in a blank state with no actual hboot I believe.
(Make sure you're flashing these hboots thru fastboot, not recovery)
777ace said:
I've found the 2.3.3 GB Telstra RUU and renamed to PB99IMG.zip, placed on SD card. I see a blue progress bar and then "would you like to reboot now?" Each time I reboot, I am straight back to Bootloader screen (not stuck in bootloop, as such).
Working my way thru the TS Guide, but I'm pretty sure I have missed a step or forgotten something along the way... Wondering if phone won't boot properly because I am now running the Downgrade HBoot, which is obviously not compatible with Runnymede.
Am I able to uninstall 4EXT touch? Would like to simplify things as much as I can and would be happy with standard CWM for flashing purposes...
Will keep playing today. I know the phone isn't bricked, so I'm not panicking. Yet.
Click to expand...
Click to collapse
Dont rename the ruu to PB99IMG... It wont work as u found out. So.... On ur pc, run the ruu.exe file that u downloaded, then (if using windows) when it gets to the screen with pic of phone asking to axcept stuff, click start on ur computer, then in search box type "run" then click on run then in that search box type %temp% and search then find the first or second newest folder there will be a file there called rom.zip... Rename that to PB99IMG then put it on the root of ur sdcard and boot into bootloader
---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------
eddiehk6 said:
Try flashing the stock hboot, then RUU
Currently if only flashed the downgrade.img, it's just in a blank state with no actual hboot I believe.
(Make sure you're flashing these hboots thru fastboot, not recovery)
Click to expand...
Click to collapse
I was typing as u were posting
jmcclue said:
Dont rename the ruu to PB99IMG... It wont work as u found out. So.... On ur pc, run the ruu.exe file that u downloaded, then (if using windows) when it gets to the screen with pic of phone asking to axcept stuff, click start on ur computer, then in search box type "run" then click on run then in that search box type %temp% and search then find the first or second newest folder there will be a file there called rom.zip... Rename that to PB99IMG then put it on the root of ur sdcard and boot into bootloader
---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------
I was typing as u were posting
Click to expand...
Click to collapse
Nice! Thank you!! I was following the TS Guide and couldn't figure why I couldn't find that rom.zip file... Now I get it.
A bit busy for a while, but will try again as soon as I get home and report back.
Cheers.
777ace said:
Nice! Thank you!! I was following the TS Guide and couldn't figure why I couldn't find that rom.zip file... Now I get it.
A bit busy for a while, but will try again as soon as I get home and report back.
Cheers.
Click to expand...
Click to collapse
If u get stuck just google search "how to extract rom.zip from ruu xda" im sure ul get a few guides.
Well, as it happened, impatience got the better of me and I did find the rom.zip and placed onto SD. Update worked fine, but now stuck at Telstra splash screen.
I really do have to head out, but I'll check back again later on.
Would having the SD card partitioned to SD-Ext/FAT32 effect the operation??
Thanks again for the help, feeling like a real n00b here!
Partition won't affect it. RUU doesn't see or care about it
Have you flashed stock hboot yet? It should say alpharev stock in the top of the bootloader screen.
If that RUU won't work, find the 2.3.3 WWE GB RUU
I have --- AlphaRev --- at top of screen. Definitely have flashed stock HBoot.
Just flashing WWE RUU now. I notice in the tutes I've found I should be seeing
Parsing...[SD ZIP]
[1]Bootloader - OK
[2]Radio_V2 - OK
[3] Radio_Cust - OK
etc...
I have the "OK" on all points except the [1] Bootloader, which has "Bypassed" after it...
WWE RUU now flashed, rebooted and still stuck at splash. Trying to recall if I had flashed a custom Kernel to this phone, back when I was using/playing with it. Blah, too many variables! Should have returned to stock two years ago!!
Still stuck at splash...and speaking of splash, phone might need to take a dip my swimming pool, I think.........................
777ace said:
I have --- AlphaRev --- at top of screen. Definitely have flashed stock HBoot.
Just flashing WWE RUU now. I notice in the tutes I've found I should be seeing
Parsing...[SD ZIP]
[1]Bootloader - OK
[2]Radio_V2 - OK
[3] Radio_Cust - OK
etc...
I have the "OK" on all points except the [1] Bootloader, which has "Bypassed" after it...
WWE RUU now flashed, rebooted and still stuck at splash. Trying to recall if I had flashed a custom Kernel to this phone, back when I was using/playing with it. Blah, too many variables! Should have returned to stock two years ago!!
Still stuck at splash...and speaking of splash, phone might need to take a dip my swimming pool, I think.........................
Click to expand...
Click to collapse
Not sure why it's skipping the bootloader part.
Custom kernel doesn't make a difference either. Everything except your sd card gets wiped when you run an RUU.
I had a read of the troubleshooting guide again, Part 8, it said to flash the downgrader, then RUU, sorry for my bad advice. Try that.
Else try runnnig the 2.3.3 RUU using PB99IMG.zip method in the same guide.
You should eventually be able to get it to boot. You don't have the RadioV2 fail which is a good thing
eddiehk6 said:
Not sure why it's skipping the bootloader part.
Custom kernel doesn't make a difference either. Everything except your sd card gets wiped when you run an RUU.
I had a read of the troubleshooting guide again, Part 8, it said to flash the downgrader, then RUU, sorry for my bad advice. Try that.
Else try runnnig the 2.3.3 RUU using PB99IMG.zip method in the same guide.
You should eventually be able to get it to boot. You don't have the RadioV2 fail which is a good thing
Click to expand...
Click to collapse
Well, I am now S-On, so progress is occurring... Also back to 0.75 HBoot.
Still booting straight to Fastboot though. For sh.ts and giggles, I just attempted to enter Recovery, but got the dreaded red triangle. All good, phone does still boot, just not in the way I want...
Anyhoo, still ticking away. Am relearning a heap of stuff. Maybe I could re-root and S-Off again, once I get this sorted??
777ace said:
Well, I am now S-On, so progress is occurring... Also back to 0.75 HBoot.
Still booting straight to Fastboot though. For sh.ts and giggles, I just attempted to enter Recovery, but got the dreaded red triangle. All good, phone does still boot, just not in the way I want...
Anyhoo, still ticking away. Am relearning a heap of stuff. Maybe I could re-root and S-Off again, once I get this sorted??
Click to expand...
Click to collapse
You can't enter recovery because the custom recovery gets overwritten by RUU as well. Like I said, everything should go back to stock.
Try the 2.3.3. GB RUU (I assume you used the Telus one as you only have 0.75 hboot?), get it booting first before trying anything else.
The latest RUU should have 1.02 hboot, at which point you could s-off with revolutionary as it's only compatible with 0.93 or 1.02 hboot as far as I know..
My suggestion of trying to enter recovery, or re-rooting was just me playing silly buggers. I swear once this thing is sorted, I am never touching it again!!
So I just tried to re-flash the Telstra RUU and got message "Main Version is older! Update Fail!". Probably due to the 0.75 HBoot, I am guessing. Would like to find a copy of Telstra FroYo RUU and see if that works. If it does get things moving, I could then OTA update once full-boot has been achieved.
Still pretty sure I missed a step somewhere... I did full wipe before starting (cache/dalvic, system, data, SD-Ext), but not factory reset. As I said, am now back to S-On, but I assume I am still rooted, so starting to think I should go back, gain S-Off, CWM and start all over again.
You people must be about ready to reach thru your monitor and choke me! Lol!!
777ace said:
My suggestion of trying to enter recovery, or re-rooting was just me playing silly buggers. I swear once this thing is sorted, I am never touching it again!!
So I just tried to re-flash the Telstra RUU and got message "Main Version is older! Update Fail!". Probably due to the 0.75 HBoot, I am guessing. Would like to find a copy of Telstra FroYo RUU and see if that works. If it does get things moving, I could then OTA update once full-boot has been achieved.
Still pretty sure I missed a step somewhere... I did full wipe before starting (cache/dalvic, system, data, SD-Ext), but not factory reset. As I said, am now back to S-On, but I assume I am still rooted, so starting to think I should go back, gain S-Off, CWM and start all over again.
You people must be about ready to reach thru your monitor and choke me! Lol!!
Click to expand...
Click to collapse
- Please use the 2.3.3 WWE RUU...
- Ignore anything and everything to do with Telstra...
- You are not rooted. You have run an RUU but it's not booting. This has overwritten everything, so your factory reset was unnecessary...
eddiehk6 said:
- Please use the 2.3.3 WWE RUU...
- Ignore anything and everything to do with Telstra...
- You are not rooted. You have run an RUU but it's not booting. This has overwritten everything, so your factory reset was unnecessary...
Click to expand...
Click to collapse
Yep, that's what I'm experiencing.
I have flashed RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704 from here previously, but still had the boot issues when I ran it.
Gave it another try just now, but now have message "Model ID incorrect! Update Fail!"
- That is not the 2.3.3 GB RUU, I think it's an ancient Eclair RUU, yes android 2.1....
- If you can't find the 2.3.3 GB RUU, at least try the Froyo RUU from that thread, version 2.29.405.5 I think. This should give you hboot 0.93 which revolutionary also works on.
http://www.htcdev.com/process/legal_download/152
Or do it the PB99IMG method
http://d-h.st/d44
KA-CHING!!
I swear, if I could hit the THANKS button a million times, I would do so in a heart beat. Using mcclue's PB99IMG link, phone is now up and running like new!
But the thanks must also go eddiehk, for your patience and taking the time to check back each day to see how I am going. I swear I had no idea that RUU was Eclair/2.1... Just ASSUMED the updates were still relevant. Was getting close to just "Meh!" and tossing it in the trash.
So, going forward from here, is it worth me checking for OTA updates to bring the phone back completely to stock (Telstra) specs...or just leave it alone??
Anyway, again a million thanks to you guys for your help. Very much appreciated!! :good::good::good::good:
777ace said:
KA-CHING!!
I swear, if I could hit the THANKS button a million times, I would do so in a heart beat. Using mcclue's PB99IMG link, phone is now up and running like new!
But the thanks must also go eddiehk, for your patience and taking the time to check back each day to see how I am going. I swear I had no idea that RUU was Eclair/2.1... Just ASSUMED the updates were still relevant. Was getting close to just "Meh!" and tossing it in the trash.
So, going forward from here, is it worth me checking for OTA updates to bring the phone back completely to stock (Telstra) specs...or just leave it alone??
Anyway, again a million thanks to you guys for your help. Very much appreciated!! :good::good::good::good:
Click to expand...
Click to collapse
The 2.3 gb upgrade is the latest for this phone so just leave it as is. And if u want custom roms again, use revolutionary to s-off.

Categories

Resources