INTRODUCTION
It seems that a lot of Canadians are having this problem, so I decided to make a guide on how to bypass it. For my guide on flashing RUUs on the Canadian IS, click here.
THE PROBLEM
People with a Canadian Incredible S are continually getting the "Model ID Incorrect" error. This error occurs because the Canadian IS has the model ID PG3212000 while it seems every other IS has the ID PG3213000, which is blocking us from installing it... But luckily there is a way to fix this error.
THE SOLUTION
NOTE: It seems many people are having problems. After reflashing my phone and S-OFF'ing it again I had the same problem. Turns out ENG S-OFF is needed for this! Find out how to install it here: http://forum.xda-developers.com/showthread.php?t=1070348
To install a PG3213000(Any non-Canadian Incredible S) radio on a PG3212000(a Canadian Incredible S) follow these instructions:
1. go to: http://forum.xda-developers.com/showpost.php?p=12870734&postcount=1 and download whichever radio matches your rom...
2. extract the file you just downloaded and open up the file called: "android-info.txt" in WORDPAD...
3. In the text file change the first line saying "modelid: PG3213000" to "modelid: PG3212000" and go File -> Save.
4. Rezip the file and make sure you call it: "PG32IMG.zip". Copy it the root of your SD card.
5. Reboot your phone in bootloader and let it install... DONE!
NOTE: It seems many people are having problems. After reflashing my phone and S-OFF'ing it again I had the same problem. Turns out ENG S-OFF is needed for this! Find out how to install it here: http://forum.xda-developers.com/showthread.php?t=1070348
which one do you find works best with the bell is?
It all depends on what ROM you're using... You always want to use the radio recommended for the ROM... if it's a RUU, the radio is already in it.
I'm on the Virtuous Unity 1.26.0 ROM and oddly enough there isn't a reccomended ROM.
Also is this way any different than extracting the radio image and pushing it through fastboot?
Both have the same results, but this doesn't require andriod sdk, any work in command prompt, or ENG S-OFF... And I would recommend the 20.2804.30.085AU_3805.04.03.22_M radio
I was wondering how to do this since I need to update my radio to install CM7. Thanks so much for the tutorial!!
Hey can you use this guide when trying to flash a ruu? It never works when trying to flash a RUU because of Model ID incorrect... I am stuck in bootloader because of that...
ClaudiuJer said:
Hey can you use this guide when trying to flash a ruu? It never works when trying to flash a RUU because of Model ID incorrect... I am stuck in bootloader because of that...
Click to expand...
Click to collapse
I have tried that before and it did not seem to work... All it did was install the HBOOT and radio from the RUU and then it rebooted my phone...So essentially all it did was revert my phone back to S-ON... I will keep playing around with RUUs and will release a guide if/when I figure out how to flash them.
kattara said:
I was wondering how to do this since I need to update my radio to install CM7. Thanks so much for the tutorial!!
Click to expand...
Click to collapse
Glad I helped you out
charch said:
I have tried that before and it did not seem to work... All it did was install the HBOOT and radio from the RUU and then it rebooted my phone...So essentially all it did was revert my phone back to S-ON... I will keep playing around with RUUs and will release a guide if/when I figure out how to flash them.
Glad I helped you out
Click to expand...
Click to collapse
Yea I am stuck in bootloader because I was running Gingerbread and when I try to go back to my stock RUU I can't because it is Froyo and I receive "Main Version is Older" error...
ClaudiuJer said:
Yea I am stuck in bootloader because I was running Gingerbread and when I try to go back to my stock RUU I can't because it is Froyo and I receive "Main Version is Older" error...
Click to expand...
Click to collapse
Reflash a Gingerbread radio... Unfortunately it is currently impossible to downgrade your radio from Gingerbread to Froyo... It will put you into a never ending boot up loop.
Wait... Are you saying you successfully flashed a GB RUU? How?
charch said:
Reflash a Gingerbread radio... Unfortunately it is currently impossible to downgrade your radio from Gingerbread to Froyo... It will put you into a never ending boot up loop.
Wait... Are you saying you successfully flashed a GB RUU? How?
Click to expand...
Click to collapse
No it doesn't work... It was only when I was S-Off that I installed Android Revolution rom and that upgraded me to gingerbread... Well after that I accidently did a hard reset which removed my S-off and I am now stuck in bootloader with ***Security Warning***. The only way to fix it is by flashing a stock RUU but since this is Bell IncS only Sasktel rom works and I cannot flash that because I get the error "Main Version is Older" error.
Noob here. What's RUU?
ClaudiuJer said:
No it doesn't work... It was only when I was S-Off that I installed Android Revolution rom and that upgraded me to gingerbread... Well after that I accidently did a hard reset which removed my S-off and I am now stuck in bootloader with ***Security Warning***. The only way to fix it is by flashing a stock RUU but since this is Bell IncS only Sasktel rom works and I cannot flash that because I get the error "Main Version is Older" error.
Click to expand...
Click to collapse
I don't know what you can do to fix that, unfortunately... Post a question in the general forum and hope that someone can help you out with more information...
Edit: :O maybe that's why the RUU didn't complete the installation and rebooted my phone! The radio was newer then the version in the Optus RUU?!?! Omg that might have been my problem...
kattara said:
Noob here. What's RUU?
Click to expand...
Click to collapse
RUU is an acronym for ROM Update Utility... It is an official update for the phone which makes it as though it was new and seem like it was never tampered with(no root, no custom recovery, not custom HBOOT, returns you to S-ON, etc).
I believe this has been posted elsewhere, but if you are unable to flash your radio AND you are already ENG S-OFF the following works perfectly.
Download: http://www.megaupload.com/?d=WIWVHF7O
Make sure HTC Sync is installed
Extract ZIP to a folder and from that folder run the following:
1. Connect your phone into a PC, and make sure that USB Debugging is enabled
2. Type: "adb reboot bootloader"
3. Once your phone is in bootloader (white screen with text), type "fastboot flash radio radio.img"
4. When the flashing completes, type "fastboot reboot"
This works on any version of the IS, including the Canadian one. I included the recommended radio, however any radio can be used by replacing the radio.img file.
Other radios here: http://forum.xda-developers.com/showpost.php?p=14834003&postcount=1
you_eeeeeediot said:
I believe this has been posted elsewhere, but if you are unable to flash your radio AND you are already ENG S-OFF the following works perfectly.
Download: http://www.megaupload.com/?d=WIWVHF7O
Make sure HTC Sync is installed
Extract ZIP to a folder and from that folder run the following:
1. Connect your phone into a PC, and make sure that USB Debugging is enabled
2. Type: "adb reboot bootloader"
3. Once your phone is in bootloader (white screen with text), type "fastboot flash radio radio.img"
4. When the flashing completes, type "fastboot reboot"
This works on any version of the IS, including the Canadian one. I included the recommended radio, however any radio can be used by replacing the radio.img file.
Other radios here: http://forum.xda-developers.com/showpost.php?p=14834003&postcount=1
Click to expand...
Click to collapse
Yes, I know, but this makes it so that ENG S-OFF is not required as it is a little bit overkill... Plus, I used this as my basis in an attempt to installing RUUs on the Canadian version of the IS, since I was told it is not possible unless I XTC clip it... I proved those people wrong.
It doesn't seem to work for me.
I edited the android-info.txt file, re-zipped and placed the file onto the sd card. When I reboot into hboot, it says "Loading PG32IMG.zip" then "Parsing" then nothing else happens.
EDIT: Never mind, I got it to work using the other method.
charch said:
I don't know what you can do to fix that, unfortunately... Post a question in the general forum and hope that someone can help you out with
RUU is an acronym for ROM Update Utility... It is an official update for the phone which makes it as though it was new and seem like it was never tampered with(no root, no custom recovery, not custom HBOOT, returns you to S-ON, etc).
Click to expand...
Click to collapse
Ahh, I see! Thanks for the explanation!!
biomech91 said:
It doesn't seem to work for me.
I edited the android-info.txt file, re-zipped and placed the file onto the sd card. When I reboot into hboot, it says "Loading PG32IMG.zip" then "Parsing" then nothing else happens.
EDIT: Never mind, I got it to work using the other method.
Click to expand...
Click to collapse
Hmm... It didn't work for me either. I still get the same error...
kattara said:
Hmm... It didn't work for me either. I still get the same error...
Click to expand...
Click to collapse
Yes, it seems ENG S-OFF is needed for this work. I updated the orginal post with the information.
charch said:
Yes, it seems ENG S-OFF is needed for this work. I updated the orginal post with the information.
Click to expand...
Click to collapse
Ah, ok! I will try it!
Related
Hi, I cant get this radio to flash on my mates Inc S (it worked fine on mine). He has s-off (xtc clip method), latest recover, root etc, but when I flash using PG32IMG hboot method I get 'Incorrect model ID' or something like that. Also tried same thing using a goldcard. Also tried fastboot method as per post 1 ARHD1.1.0 thread. No success
Any ideas please ?
gudge said:
Hi, I cant get this radio to flash on my mates Inc S (it worked fine on mine). He has s-off (xtc clip method), latest recover, root etc, but when I flash using PG32IMG hboot method I get 'Incorrect model ID' or something like that. Also tried same thing using a goldcard. Also tried fastboot method as per post 1 ARHD1.1.0 thread. No success
Any ideas please ?
Click to expand...
Click to collapse
If this is a Candanian IncS, then the model id in the PG32IMG.Zip file needs to be changed.
http://forum.xda-developers.com/showthread.php?t=1145246
tpbklake said:
If this is a Candanian IncS, then the model id in the PG32IMG.Zip file needs to be changed.
http://forum.xda-developers.com/showthread.php?t=1145246
Click to expand...
Click to collapse
Actually its a UK device, but only about a week or so out of the shop, unlike mine which is a few months old and an older hboot version . The engineering hboot in the link you mentioned may be the answer, thanks for the pointer.
Cheers
If you use alpharevx for S-OFF maybe this post can help you installing new radio :
[GUIDE] How to flash a radio [for Alpharevx S-OFF]
Neolight78 said:
If you use alpharevx for S-OFF maybe this post can help you installing new radio :
[GUIDE] How to flash a radio [for Alpharevx S-OFF]
Click to expand...
Click to collapse
thanks, the link is also to ENG hboot, I think this will be the answer, will try it and post back outcome.
Thanks all for the guidance.
find out one method in ARHD 1.1.0,dload the radio file,open and read it.
Guys be careful when flashing radios, because i flashed 6.03.03 from gu1dry's thread and then tried to run a lower version ruu and broke the software on the phone. Now i need to use xtc clip to revive.
post by ieftm
"gu1dry, could you please adjust your RUU zips to include a lower mainversion?
preferably something really low like 1.00.0000.0.
Some of these zips have:
mainver: 2.21.1400.8
Which might spell trouble for people that attempt at flashing a RUU afterwards (as they're left with a broken RUU and a high mainversion).
Thanks"
Just make sure you ask all q's before playing with stuff like this it will avoid what i am facing. Just want to help
neo-X, pitty your on the other side of the world, you could have borrowed mine. Thanks for the warning though, I think I will re flash the new radio using the link from post 1 of ARHD to be safe.
Resolved my mates problem by flashing ENG hboot, then the new radio flashed ok. I don't understand why it was necessary to do this ENG hboot thing, since I did not have this problem with my own inc s. Must be something to do with latest stock hboot I guess. One other word of warning, after installing the ENG hboot his phone would not boot past the first HTC boot screen, but was able to go into custom recovery, wipe then flash ARHD rom, then booted up all OK.
Thanks gudge...luckily i got it working, just needed to flash the new higher version ruu that was just released
Sent from my HTC Incredible S using XDA Premium App
Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks
patrick92260 said:
Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks
Click to expand...
Click to collapse
If you don't have S-OFF on your BM IncS, then you won't be able to flash the WWE 2.30.405.1 RUU because that ROM is for the S710E model (model id PG321300) and the BM Incs is a S710A model (model id PG321200) and it will fail with 'wrong model id' error.
If you go ahead and S-OFF, then you can take the WWE 2.30.405.1 RUU and extract the ROM.zip and modify the android-info.txt file in the ROM.zip to change the model id. After that process, you would copy the modified ROM.zip file to the root of your SD card and rename it PG32IMG.zip. Then boot into HBOOT and it will find the PG32IMG.zip file and ask if you want to apply the update. You will then have an unbranded, unrooted IncS. The second advantage of S-OFF is that it will allow you to reflash the BM 2.28.666.3 RUU.
I'm looking at doing the same thing. Wondering if patrick92260 has had any success. I have the Virgin IS and want to debrand it as its loaded with useless BELL apps. Will be attempting this myself, let you know how it goes.
Q: First question is, now that I have the .exe of RUU. How do I go about getting the ROM.zip file.
Figured it out on my own, but for others who are curious.
A:Windows > Run > %TEMP%
Then list by 'last modified folder' and it should be the first one there.
I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?
patrick92260 said:
I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?
Click to expand...
Click to collapse
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.
tpbklake said:
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.
Click to expand...
Click to collapse
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.
patrick92260 said:
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.
Click to expand...
Click to collapse
I have not had any issues of debranding my Bell IncS with the WWE roms.
The OTA downloaded fine, but like all OTAs, it checks to make sure you have a stock version of the previous ROM, in this case 2.12.405.7. If you have ClockworkMod installed, the OTA will fail because that isn't the stock recovery. I could have flashed the stock recovery and ran the OTA, but I choose to take the 2.30.405.1 RUU and make a rooted version of it using dsi's XDA Android kitchen and ended up flashing that.
Debranding went smoothly. Flashed the WWE just fine after editing the file.
Then went ahead and installed 4EXTRecovery and Virtuous Unity over that though.
Whether doing the debranding helped or not, I'm not sure. Either way I'm down to just essential apps in this rom, no bloatware.
As for OTA updates, who cares really. If you're on this forum, you've got enough knowledge to flash yourself and not have to wait for OTA updates to arrive.
Original Bell Incredible S rom
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.
neurobrake said:
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.
Click to expand...
Click to collapse
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.
The file is gone.
tpbklake said:
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.
Click to expand...
Click to collapse
justaway2 said:
The file is gone.
Click to expand...
Click to collapse
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922
I need this file
tpbklake said:
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
I need this file. Can you please update the link? Point me to it.
digitzgal said:
I need this file. Can you please update the link? Point me to it.
Click to expand...
Click to collapse
Go to the site HTCDEV.com and you can download the final ICS RUU.
Followup question
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2
digitzgal said:
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2
Click to expand...
Click to collapse
No, if you have BlackRose S-OFF, you will not be able to flash the 4.14.405.2 RUU. There is a link in my signature that is a stock, rooted ROM based on this RUU that you can safely install. I would recommend that along with poondog's kernel that is also linked in my signature.
Followup
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?
digitzgal said:
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?
Click to expand...
Click to collapse
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.
072665995 said:
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.
Click to expand...
Click to collapse
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?
digitzgal said:
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?
Click to expand...
Click to collapse
Ok now I'm just freaking confused. What are you trying to do?? Are you trying to root?? Or what??
Hi all,
I'm having issues trying to restore the latest Telstra RUU and I'm hoping someone will be able to give me a hand with this.
I originally unlocked the bootloader, flashed a CWM recovery, custom ICS ROM, and all was working fine.
I've decided to go back to stock Telstra release but every time I try running the RUU I get an error message saying ERROR [140]: BOOTLOADER VERSION ERROR.
From what I've read, this relates to the bootloader being newer then that included in the RUU. I'm not sure how accurate this is though so if someone could confirm, that would be great. If I do need to downgrade the bootloader, where do I get it from?
The RUU's I've tried flashing are from here: http://www.filefactory.com/f/002b74e0f4775869/
- RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_34.06.701020.02_release_231121_signed.exe
- RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed.exe
Neither of these work and both show the same error as indicated above.
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0029
eMMC-boot
Mar 15 2012, 17:16:42
If anyone can provide any assistance getting this phone back to stock Telstra release it would be greatly appreciated. I've been working on it for almost 6-8 hours now and seem to be going around in circles.
Thank you! :good:
You need to relock your boot loader to run an ruu
Sent from my HTC PH39100 using xda premium
Sorry, I forgot to mention that. The bootloader has been relocked.
What hboot do you have currently?
Sent from my HTC PH39100 using xda premium
As above, HBOOT-1.85.0029.
I've managed to flash Velocity² "Nightly Build 5" which is as close to stock as I can get for the time being. Phone is working fine.
I can't seem to find any information at all regarding updating the HBOOT though, and what small information I do come across, it doesn't make a whole lot of sense. I don't even know if 1.85.0029 is the latest. Whether I need to upgrade/downgrade it before the RUU will work which some information I've found seems to suggest.
You shouldn't have to change the hboot to be able to run the ruu. Did you unlock your bootloader again to flash the new Rom?
Sent from my HTC PH39100 using xda premium
I did unlock the bootloader again to flash the new rom, only becasue the RUU wouldn't flash. I've tried flashing the RUU with the bootloader locked and unlocked even though I know it needs to be locked. I've tried flashing the RUU while using both a GB rom and an ICS rom - just incase it makes it difference - it didn't.
I've never had this much trouble flashing an RUU before - it's ridiculous.
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
kgs1992 said:
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
Click to expand...
Click to collapse
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Nucleotide said:
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Click to expand...
Click to collapse
Main version is the software number.
The one you see in Settings > About > Software Information.
The number should be on the RUU that you downloaded, it's the first set of numbers. for example: 3.25.841.4
How did you go with this, I am in the exact same boat. I want to sell my phone but not with this rom.
I was never able to install the stock Telstra RUU. Could never figure it out. After countless hours and at one stage thinking I'd bricked it, I gave up. I ended up sticking with this ROM (http://forum.xda-developers.com/showthread.php?t=1653317) which hasn't been too bad really.
I would still really love to restore it to factory but in all honesty I don't think it will ever happen.
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
androidlurv said:
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
Click to expand...
Click to collapse
That would be awesome. Very interested to know how you get on. :good:
Nucleotide said:
That would be awesome. Very interested to know how you get on. :good:
Click to expand...
Click to collapse
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Drunkllamajr said:
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Click to expand...
Click to collapse
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Nucleotide said:
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Click to expand...
Click to collapse
Same here I'm now running Holics 1.3 very similar to stock with some nice addons etc
just s-off and then use that RUU
I can't find the RUU's any more. They have gone from File Factory. I've pretty much given up on trying to restore this to factory. I can't even find up to date information on how to S-OFF - and from memory it's got to be done via hardware hack of some sort? Not real keen on that idea.
That said, I'm looking at flashing CyanogenMod 10 4.1.2 ROM which I'd be more then happy with.
RUU
You might be looking for this http://forum.xda-developers.com/showthread.php?t=2094150&highlight=ruu. I was having the same problem and what I did was find the exact/the same version of the RUU and the version of my phone.
Hey guys,
I screwed up my Incredible S, I'm stuck in the HTC screen and if I volume down+power, it goes to that hboot screen and if I select recovery, I go to revolutionary (so I can't warranty)...
I tried using A LOT of "stock" roms, tried RUU etc but nothing seems to be working...
Also, it used to be on the optus 2.3.5
someth1ng said:
Hey guys,
I screwed up my Incredible S, I'm stuck in the HTC screen and if I volume down+power, it goes to that hboot screen and if I select recovery, I go to revolutionary (so I can't warranty)...
I tried using A LOT of "stock" roms, tried RUU etc but nothing seems to be working...
Also, it used to be on the optus 2.3.5
Click to expand...
Click to collapse
What are you trying to accomplish? Are you trying to restore back to stock for warranty?
If so, you need to follow this procdure so that you can overwrite the Revolutionary HBOOT with an RUU.
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
tpbklake said:
What are you trying to accomplish? Are you trying to restore back to stock for warranty?
If so, you need to follow this procdure so that you can overwrite the Revolutionary HBOOT with an RUU.
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
Click to expand...
Click to collapse
Well, the phone doesn't work at all at the moment so getting it back to work would be good. If it's getting it back to stock then sure, I'll do that
"1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922"
Link doesn't work =/
I'm assuming it is this one: RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned
My phone was running optus before I stuffed it.
Also, what do I do to install, if I run RUU and follow the steps, it will just and and say it can't do it. Do I copy the rom.zip file and rename it to PG32IMG.zip then put it on a USB and go to bootloader?
I seem to be getting "signature verify fail"...
This thread seems to look exactly like my problem but it seems to be much more confusing...
http://forum.xda-developers.com/showthread.php?t=1658594
someth1ng said:
Well, the phone doesn't work at all at the moment so getting it back to work would be good. If it's getting it back to stock then sure, I'll do that
"1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922"
Link doesn't work =/
I'm assuming it is this one: RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned
My phone was running optus before I stuffed it.
Also, what do I do to install, if I run RUU and follow the steps, it will just and and say it can't do it. Do I copy the rom.zip file and rename it to PG32IMG.zip then put it on a USB and go to bootloader?
Click to expand...
Click to collapse
OK, start the process beginning at Step 2. Don't worry about step 1 for now.
So first you need to prepare the Revolutionary HBOOT to be overwritten by following step 2.
Then you should be able to run the RUU or as you stated, extract the ROM.zip, rename it PG32IMG.zip on your SD card and boot into bootloader.
someth1ng said:
I seem to be getting "signature verify fail"...
Click to expand...
Click to collapse
Here is a link to the optus 2.3.5 ruu http://d-h.st/cGj
You're not s-off if you're getting signature error. Were you ever s-off or just unlocked bootloader? If unlocked bootloader only, you will have to lock it before running the ruu.
How exactly do you "downgrade HBOOT"?
I managed to install virtuous quattro yesterday but then...my WiFi, parts of the touchscreen and the bottom 4 touch buttons don't work.
Strange problem.
someth1ng said:
How exactly do you "downgrade HBOOT"?
I managed to install virtuous quattro yesterday but then...my WiFi, parts of the touchscreen and the bottom 4 touch buttons don't work.
Strange problem.
Click to expand...
Click to collapse
Boy you are all over the board on this thread. First you asked how to get back to stock s-on for warranty and now you are asking about downgrading the hboot to go back to s-off.
You have been given links for removing Revolutionary S-Off and flashing the Optus RUU. I suggest you follow those to get your phone straightened out first before going any further.
I know that many people have had problems with 3.44 ruu not being available. I want to go back to the stock rom using the ruu but i can't seem to find it and when i try to use the latest available ruu it comes with a error bootlaoder version. Could someone please help me.
HTCdev
select 'vivid' and 'telstra' than 'find files' .
I think the first one is the one you are searching for, it says 3.44.841.3 in description.
Thats a kernel source file not the ruu
No RUU exists for 3.44. AFAIK, it was a kernel patch for a minor issue. Just flash the normal Telstra RUU, and try to OTA to 3.44.
You get error 140 when you use a earleir ruu
WildfireDEV said:
You get error 140 when you use a earleir ruu
Click to expand...
Click to collapse
Two things:
Make sure your bootloader is relocked.
Extract the rom.zip from the RUU (C:\Users\[YOU]\AppData\Local\Temp\{garbage numbers}), rename to PH39IMG.zip, paste on external SD's root, and reboot to bootloader. Accept update. Should not throw errors; I've used this method to downgrade countless times.