Develop Bugs

[HBOOT] HBOOT update for EU users who's having problem with RUU

Well as you can see I updated my wildfire S 2 or 3 days ago with OTA, so now when ever I try to flash the RUU from htcdev.com it fails be because "I Have a newer ROM version [ERROR 191]"
so I extracted the Zip file from the RUU and flashed from SDcard and it worked !
WARNING THIS IS ONLY FOR EU UNLOCKED FOLLOW THIS GUIDE AT YOUR OWEN RESPONSIBILITY
1- Moderator Edit link removed Multiupload is not supported as a file host site on XDA
2-Copy it to your Sdcard
3-Shutdown the phone
4-Start into Bootloader (Volume down + power)
5-Wait for it to Load the Zip file
6-chose yes (volume up)
And your done
now reboot and Delete the Zip file from Sdcard

I have an EU WFS, but getting the 171 error, will this help?

Two questions for you
Gig11gs said:
Well as you can see I updated my wildfire S 2 or 3 days ago with OTA, so now when ever I try to flash the RUU from htcdev.com it fails be because "I Have a newer ROM version [ERROR 191]"
so I extracted the Zip file from the RUU and flashed from SDcard and it worked !
Click to expand...
Click to collapse
1. Do you mean that you upgraded to 2.3.5 a couple days ago and that's why it won't flash the RUU? I was assuming I got ERROR 191 because I hadn't upgraded to 2.3.5 yet.
2. Were you getting the exact same message with the error code?
ERROR [191] ROM IS NOT SUPPORTED
Your ROM Version is not currently supported, but there will be an update soon that will be supported. You will receive a notification to update your phone to the latest ROM code.
After you have updated, please run the RUU again to upgrade your HBOOT to unlock your phone. We apologize for the inconvenience.​
Incidentally, the part number for my phone is the same as the generic EU phone: PG76100 so your method of installing the ROM should work the same.
Update:
I got through the HBOOT update using the tip posted in this thread. It worked like a charm, so apparently my 2.3.3 Asia ROM wasn't the problem.
So I want to say thanks for the trick also! Tomorrow I'll finish the unlock process tomorrow as it's already after 10:30 PM here.

So unlocked in this case means that only will work with a phone which is S-OFF?

breaky9973 said:
So unlocked in this case means that only will work with a phone which is S-OFF?
Click to expand...
Click to collapse
No. It's for S-ON and does not provide S-OFF. Just unlocks HBOOT so you can flash custom recovery, root and flash new rom.
---------- Post added at 05:52 AM ---------- Previous post was at 05:51 AM ----------
Gig11gs said:
Well as you can see I updated my wildfire S 2 or 3 days ago with OTA, so now when ever I try to flash the RUU from htcdev.com it fails be because "I Have a newer ROM version [ERROR 191]"
Click to expand...
Click to collapse
If you look carefully, when choosing WFS, it has a * on the side saying that you have to update your HBOOT.

Anyway...it is not working for me. I put the file on my memory card and boot into the bootloader. it seems to load but I just don't get an option to update.

Thanks a lot! It says HBOOT 1.08.0099 with a LOCKED (OOW) above it.
Thanks a lot!
EDIT: LOVE YA MATE! IT WORKED! I NOW HAVE AN UNLOCKED BOOTLOADER! DDDD

tried this on mine and it says "Can not rollback HBOOT" then it bypasses the hboot update. It updates the radio just fine though.

Gig11gs said:
Well as you can see I updated my wildfire S 2 or 3 days ago with OTA, so now when ever I try to flash the RUU from htcdev.com it fails be because "I Have a newer ROM version [ERROR 191]"
so I extracted the Zip file from the RUU and flashed from SDcard and it worked !
WARNING THIS IS ONLY FOR EU UNLOCKED FOLLOW THIS GUIDE AT YOUR OWEN RESPONSIBILITY
1- Download this
2-Copy it to your Sdcard
3-Shutdown the phone
4-Start into Bootloader (Volume down + power)
5-Wait for it to Load the Zip file
6-chose yes (volume up)
And your done
now reboot and Delete the Zip file from Sdcard
Click to expand...
Click to collapse
I already clicked thanks but I want to SAY thanks anyway.
I had my phone with the latest European RUU 2.3.5 but as stated on the HTCDEV.com site I needed the HBOOT update.
I tried to update with the RUU download from HTCDEV.com but I had a crazy error, not like any seen around here.
It wasn't 171 or 191, it just seemed trash.
I'm almost certain that the RUU's that HTC makes aren't prepared for Windows 7 Ultimate x64 SP1 users.
Back then when I updated to 2.3.5 (by football) I had to unzip the RUU and replace some ADB files with newer ones.
With the file extracted and updated it worked. I even posted an updated version here on XDA for people that were having problems like me.
So now that my bootloader is unlocked I will proceed with the next steps.
Still have a long way to go.
Thanks again for your file. It worked like a charm.

thanks now get the missus phone unlocked thanks

LucidSomnia said:
No. It's for S-ON and does not provide S-OFF. Just unlocks HBOOT so you can flash custom recovery, root and flash new rom.
But first to install custom recovery and rom i have to s-off my device with the htc dev procedure right? hboot it s not enought
Click to expand...
Click to collapse

Axel85 said:
LucidSomnia said:
No. It's for S-ON and does not provide S-OFF. Just unlocks HBOOT so you can flash custom recovery, root and flash new rom.
But first to install custom recovery and rom i have to s-off my device with the htc dev procedure right? hboot it s not enought
Click to expand...
Click to collapse
It doesn't S-OFF, it allows u to root, cwm and flash custom roms. It's like a half s-off, because it doesnt allow flashing radio i think.
Click to expand...
Click to collapse

SomeDudeOnTheNet said:
Axel85 said:
It doesn't S-OFF, it allows u to root, cwm and flash custom roms. It's like a half s-off, because it doesnt allow flashing radio i think.
Click to expand...
Click to collapse
It s strange,I don t belive it s possible to flash custom recovery and roms without a s-off.Flashing the h-boot it s only a way to have the unlock code in htcdev program,so then we can have s-off and load some stuff
Correct me if I m wrong
Click to expand...
Click to collapse

Axel85 said:
SomeDudeOnTheNet said:
It s strange,I don t belive it s possible to flash custom recovery and roms without a s-off.Flashing the h-boot it s only a way to have the unlock code in htcdev program,so then we can have s-off and load some stuff
Correct me if I m wrong
Click to expand...
Click to collapse
It just unlocks the bootloader to give u root access to flash roms. I still have s-on after unlocking the bootloader.
Click to expand...
Click to collapse

SomeDudeOnTheNet said:
Axel85 said:
It doesn't S-OFF, it allows u to root, cwm and flash custom roms. It's like a half s-off, because it doesnt allow flashing radio i think.
Click to expand...
Click to collapse
I've got HBOOT 1.08.0099 with a LOCKED (OOW) above, still S-ON, but can't for the life of me seem to find a way to root or load a custom recovery successfully. I've tried numerous ways and I'm afraid if I keep screwing with it something is going to end up bricking the device.
How is everyone rooting and loading CWM?
Thanks a lot.
Click to expand...
Click to collapse

Nucleotide said:
SomeDudeOnTheNet said:
I've got HBOOT 1.08.0099 with a LOCKED (OOW) above, still S-ON, but can't for the life of me seem to find a way to root or load a custom recovery successfully. I've tried numerous ways and I'm afraid if I keep screwing with it something is going to end up bricking the device.
How is everyone rooting and loading CWM?
Thanks a lot.
Click to expand...
Click to collapse
If you have the locked thing, go to htcdev.com, after the page where u select your ruu, tgeres a button below to proceed. So, just follow the instructions from then on.
Click to expand...
Click to collapse

SomeDudeOnTheNet said:
If you have the locked thing, go to htcdev.com, after the page where u select your ruu, tgeres a button below to proceed. So, just follow the instructions from then on.
Click to expand...
Click to collapse
Now I feel extremely stupid. I can't believe I didn't see that button at the very bottom.
Thanks a lot.

Nucleotide said:
Now I feel extremely stupid. I can't believe I didn't see that button at the very bottom.
Thanks a lot.
Click to expand...
Click to collapse
Haha, no problem.
via HTC Wildfire S powered by CM7.2

Nucleotide said:
Now I feel extremely stupid. I can't believe I didn't see that button at the very bottom.
Thanks a lot.
Click to expand...
Click to collapse
Don't worry I made the same mistake and I even looked at the whole page it was my brother that pointed it out to me lmao
Sent from my HTC Wildfire S using xda premium

eoghan2t7 said:
Don't worry I made the same mistake and I even looked at the whole page it was my brother that pointed it out to me lmao
Sent from my HTC Wildfire S using xda premium
Click to expand...
Click to collapse
what ppl we are lmfao
via HTC Wildfire S powered by CM7.2

[Q] Wiped phone through clockwork with s-on, cant restore

I made a mistake rooting a friends droid incredible and left s-on, I have clockwork but it cant flash anything, I presume its because of the s-on. I wiped the phone without a backup to install miui, so I now have a droid incredible that can only get into hboot, clockwork, and fastboot. It also will not install 31img.zips, Yes ive renamed them correctly I just call them 31's. Help please?

You need to flash an RUU in the form of PB31IMG.zip. It needs to be named PB31IMG.zip and on the root of a FAT32 formatted sdcard. If you use the froyo RUU on pvillecomp.com you can use unrevoked to root again though your friend will just want it working.

My HBOOT wont give me the option to flash, it finds it and checks it, but wont let me install. im downloading the froyo ruu right now in hopes that it will connect through fastboot and do it.

What is your hboot version?
Tiny you are more knowledgeable at this than I, but I was wondering
1) would using PB31IMG's fail if used on the 1.02 hboot?
2) If they were to use the unrevoked tool to flash s-off, could they install a rom without having to boot into the already wiped phone?

I am on hboot version 1.02. My nexus and optimus s were so simple.

(sorry for double post) RUU's will not work

deathangel1496 said:
I am on hboot version 1.02. My nexus and optimus s were so simple.
Click to expand...
Click to collapse
Have you used the htc dev site to unkock the bootloader? If not you need to do that, then fastboot flash cwm recovery, then flash superuser thru cwm recovery.

SlimSnoopOS said:
What is your hboot version?
Tiny you are more knowledgeable at this than I, but I was wondering
1) would using PB31IMG's fail if used on the 1.02 hboot?
2) If they were to use the unrevoked tool to flash s-off, could they install a rom without having to boot into the already wiped phone?
Click to expand...
Click to collapse
I would try flashing unrevoked forever before doing anything else. Logically this would get you s-off and allow you to flash a ROM. I wouldn't run straight to unlocking your bootloader because it is a lot harder to reverse that than it is to reverse the effects of unrevoked forever. (in the long run, that is. right now there would be no reason to reverse either)

nschiwy said:
I would try flashing unrevoked forever before doing anything else. Logically this would get you s-off and allow you to flash a ROM. I wouldn't run straight to unlocking your bootloader because it is a lot harder to reverse that than it is to reverse the effects of unrevoked forever. (in the long run, that is. right now there would be no reason to reverse either)
Click to expand...
Click to collapse
actually bootloader is easy to lock. I think it's fastboot oem lock. You can unlock it again using the same token you used to unlock before that you should save if you decide to do that. Unrevoked forever only works on certain radio versions. With an unlocked bootloader you should be able to flash any PB31IMG.zip as well as flash with fastboot. With S-OFF I know you can flash custom PB31IMG.zip and also older RUUs.

tiny4579 said:
actually bootloader is easy to lock. I think it's fastboot oem lock. You can unlock it again using the same token you used to unlock before that you should save if you decide to do that. Unrevoked forever only works on certain radio versions. With an unlocked bootloader you should be able to flash any PB31IMG.zip as well as flash with fastboot. With S-OFF I know you can flash custom PB31IMG.zip and also older RUUs.
Click to expand...
Click to collapse
Yes, but doesn't it then say 're-locked bootloader' or something to that effect where verizon or whoever else could tell that it has been unlocked before and therefore void any warranty? Whereas the s-off tool can be reversed using the s-on tool and nobody has to know anything was ever there. I don't have any experience in that department, I'm just speculating based on things that I have read.

nschiwy said:
Yes, but doesn't it then say 're-locked bootloader' or something to that effect where verizon or whoever else could tell that it has been unlocked before and therefore void any warranty? Whereas the s-off tool can be reversed using the s-on tool and nobody has to know anything was ever there. I don't have any experience in that department, I'm just speculating based on things that I have read.
Click to expand...
Click to collapse
Maybe, but I think when you submit for an unlock token is when HTC knows you unlocked your bootloader.

I have unlocked the bootloader and flashed the stock recovery. where can I go from here? can anyone provide an update.zip? all the links seem to be down for the froyo one

tiny4579 said:
Maybe, but I think when you submit for an unlock token is when HTC knows you unlocked your bootloader.
Click to expand...
Click to collapse
That is probably true, I never thought of that. I guess they probably think that I have an unlocked bootloader now too since I made an account and downloaded the tool to help a friend with his phone.
deathangel1496 said:
I have unlocked the bootloader and flashed the stock recovery. where can I go from here? can anyone provide an update.zip? all the links seem to be down for the froyo one
Click to expand...
Click to collapse
I may be mistaken, but isn't this what you are looking for?
http://pvillecomp.com/?page_id=22
additionally, why did you flash stock recovery vs. CWM? I don't have any experience with stock but CWM seems to be perfect for anything I've ever needed a recovery for. ie - flashing new ROMs or backing up/ restoring ROMs

deathangel1496 said:
I have unlocked the bootloader and flashed the stock recovery. where can I go from here? can anyone provide an update.zip? all the links seem to be down for the froyo one
Click to expand...
Click to collapse
Do steps 6 - 27 of this guide http://forum.xda-developers.com/showthread.php?t=1506258 to install cwm recovery and get root. If you want true s-off continue to follow steps 28 - 43.

[Q] downgrading hboot for claiming warranty

i have htc wildfire s (asia_india edition).i read in some threads i have to downgrade my hboot to claiming warranty after unrooting.so how can i do this after unrooting my phone ? and when i stock to ruu and unroot my phone and after i relocked my bootloader so in hboot i see relocked.so how can i remove it?like ages i have nothing in top of hboot like relocked,unlocked..etc

Checkout my old tutorial:
http://forum.xda-developers.com/showthread.php?t=1540952
-rezo609

ok i understand all things.but one thing i find alot everywhere but didnt find my ruu.exe file.but i found my ruu zip file,in i have boot,system and recovery images.so after all process can i port my ruu directly by fastboot flash commands?

crossfire77 said:
ok i understand all things.but one thing i find alot everywhere but didnt find my ruu.exe file.so after all process can i port my ruu directly by fastboot flash commands?
Click to expand...
Click to collapse
Well some files require s-off to flash manually.
-rezo609

rezo609 said:
Well some files require s-off to flash manually.
-rezo609
Click to expand...
Click to collapse
yeah but i have done this.facing no problem.but i dont see your tutorial first so dont know how to remove locked,relocked.i flashed boot,system,recovery images to install stock ruu which is older version 2.3.3 then via ota updated to 2.3.5.

crossfire77 said:
yeah but i have done this.facing no problem.but i dont see your tutorial first so dont know how to remove locked,relocked.i flashed boot,system,recovery images to install stock ruu which is older version 2.3.3 then via ota updated to 2.3.5.
Click to expand...
Click to collapse
The only way to remove the locked relocked is to downgrade the hboot. In hboot 1.08.0099 and 1.09.0099, Locked, relocked, etc will be there no matter what.
You will have to try and flash an hboot like 0.90.0000, 1.03.0000, or 1.08.0000 to get rid of the locked indicator.
-rezo609

rezo609 said:
The only way to remove the locked relocked is to downgrade the hboot. In hboot 1.08.0099 and 1.09.0099, Locked, relocked, etc will be there no matter what.
You will have to try and flash an hboot like 0.90.0000, 1.03.0000, or 1.08.0000 to get rid of the locked indicator.
-rezo609
Click to expand...
Click to collapse
okay i have 0.90.0000_720d6ffc74.nbo file in my stock ruu,but it can be flashed its not .img file so?

crossfire77 said:
okay i have 0.90.0000_720d6ffc74.nbo file in my stock ruu,but it can be flashed its not .img file so?
Click to expand...
Click to collapse
Ok just name it PG76IMG.nbh and see what happens in bootloader
-rezo609

[Q] Reroot and Reunlock after ruu

I have a Wildfire S CDMA from Virgin, USA which I unlocked, s-off and rooted, and installed cyanogenmod recovery.
Fastboot shows MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
I am looking to unlock from 'RL', and reroot, but after no small amount of wading through forums, I'm here asking you all for assistance. I'm new to messing with my phone, but feel like I'm about ready for an 'Ah HA!' breakthrough.
Initially, I had deleted all system/data through Recovery, and finally found an RUU that would run and reinstalled the stock ROM.
Rerooting has been a challenge. When I follow the instructions at htcdev, I fail to execute run get_identifier_token, with "command error"
Fastboot running on my desktop does recognize the device, but have not been able to flash anything.
When I boot into recovery, the phone loads the HTC spash, but lands on a screen with a red triangle and exclamation point.
PG76IMG.zip isn't recognized by FASTBOOT on the phone, regardless of the modelid or cid in the android-info.txt
I would appreciate any suggestions to get back to root.... hard to imagine that some people use their phone with out it.

Lhooqtoo said:
I have a Wildfire S CDMA from Virgin, USA which I unlocked, s-off and rooted, and installed cyanogenmod recovery.
Fastboot shows MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
I am looking to unlock from 'RL', and reroot, but after no small amount of wading through forums, I'm here asking you all for assistance. I'm new to messing with my phone, but feel like I'm about ready for an 'Ah HA!' breakthrough.
Initially, I had deleted all system/data through Recovery, and finally found an RUU that would run and reinstalled the stock ROM.
Rerooting has been a challenge. When I follow the instructions at htcdev, I fail to execute run get_identifier_token, with "command error"
Fastboot running on my desktop does recognize the device, but have not been able to flash anything.
When I boot into recovery, the phone loads the HTC spash, but lands on a screen with a red triangle and exclamation point.
PG76IMG.zip isn't recognized by FASTBOOT on the phone, regardless of the modelid or cid in the android-info.txt
I would appreciate any suggestions to get back to root.... hard to imagine that some people use their phone with out it.
Click to expand...
Click to collapse
It's because your bootloader doesn't support being unlocked.............Any bootloader that has *LOCKED*(or *RELOCKED*) written can be unlocked via HTCdev
Look over for the RUUs provided before the steps and see which one's for the CDMA WFS, run it and you will be able to unlock the phone

csoulr666 said:
It's because your bootloader doesn't support being unlocked.............Any bootloader that has *LOCKED*(or *RELOCKED*) written can be unlocked via HTCdev
Look over for the RUUs provided before the steps and see which one's for the CDMA WFS, run it and you will be able to unlock the phone
Click to expand...
Click to collapse
Downloaded the WFS SprintVM RUU from htcdev. It fails with error130 model ID error.
Identical situation as shown here:
http://forum.xda-developers.com/showthread.php?t=2027649
Walkthrough for downgrade exists here: but links are missing..
http://forum.xda-developers.com/showthread.php?t=1942991

Lhooqtoo said:
Downloaded the WFS SprintVM RUU from htcdev. It fails with error130 model ID error.
Identical situation as shown here:
http://forum.xda-developers.com/showthread.php?t=2027649
Walkthrough for downgrade exists here: but links are missing..
http://forum.xda-developers.com/showthread.php?t=1942991
Click to expand...
Click to collapse
If it doesn't work look for updates on your phone, maybe your carrier released an OTA with an unlockable bootloader

csoulr666 said:
If it doesn't work look for updates on your phone, maybe your carrier released an OTA with an unlockable bootloader
Click to expand...
Click to collapse
There is an OTA system update (through Settings/About phone/Software updates), however, the update fails with a red question mark over device. Doesn't custom recovery (CWM) and a changed CID (111..1) prohibit OTA update?

Lhooqtoo said:
There is an OTA system update (through Settings/About phone/Software updates), however, the update fails with a red question mark over device. Doesn't custom recovery (CWM) and a changed CID (111..1) prohibit OTA update?
Click to expand...
Click to collapse
The custom recovery does, but the CID doesn't....... Try doing it with a custom recovery installed

csoulr666 said:
The custom recovery does, but the CID doesn't....... Try doing it with a custom recovery installed
Click to expand...
Click to collapse
I currently have CWM installed (though currently if I run recovery from the bootloader, it fails).
If the custom recovery prohibits the OTA update, shouldn't I remove CWM to allow the OTA?

Try doing it with a stock recovery installed

csoulr666 said:
Try doing it with a stock recovery installed
Click to expand...
Click to collapse
followed this:
http://forum.xda-developers.com/showthread.php?t=2025121
sending 'recovery' <3146 KB>...
OKAY [ 1.522s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 1.526s

No joy?
Is there any chance that flashing the recovery would succeed if the recovery were different? (instead of a permissions issue).

[Q] Unlocked bootloader with wrong file

So I just spent the last couple hours trying to root my phone. Only to realize that when I unlocked the bootloader i requested the wrong unlock.bin file. Instead of selecting the htc m8 file, I selected all other supported devices. I don't know if this is the cause of my problem, but since I can't reboot to bootloader, I feel that it is. Is the solution as simple as relocking the bootloader and then unlocking it with the correct unlock.bin file. Or can i just get the correct file and unlock it again. I don't know if any of it will work since the phone won't go into the bootloader. Thought I would as people that know more than me before I brick my phone.

Getting all the stock files from here and then using your cpu to flash everything you should be fine.

jayandare said:
Getting all the stock files from here and then using your cpu to flash everything you should be fine.
Click to expand...
Click to collapse
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?

Tskizzle said:
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?
Click to expand...
Click to collapse
Stock ruu method ,lock bootloader first

manish dubey said:
Stock ruu method ,lock bootloader first
Click to expand...
Click to collapse
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.

Tskizzle said:
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.
Click to expand...
Click to collapse
So I've been reading around and come across some conflicting info. So I finally found the fastboot command to lock the bootloader but some have said to flash the stock ruu first while others say after. Can anyone clear this up for me and let me know if it makes a difference?

S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.

Mr Hofs said:
S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.
Click to expand...
Click to collapse
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock

Tskizzle said:
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock
Click to expand...
Click to collapse
Quick reattack on this. I never actually went away from stock. As I couldn't get into the bootloader I never flashed twrp or anything so do I really need to flash the stock RUU? Just trying to figure out for knowledge purposes. Am I basically flashing the RUU to start over from scratch or is it just a precautionary thing?