Develop Bugs

[Q] Can't flash stock ROM

For a few weeks my Desire has been playing up and unpredictably reboots, seemingly at random. Initially I thought it might be a software issue with the ROM I was using, but the same thing happened with various other ROMs I've tried since. So I'm thinking it's a hardware issue and I'll need to send my Desire in for service.
Normally I'd thoroughly read the forums and work out how to go back to a stock ROM, but I'm running out of time - only a few days left under warranty. Therefore this cry for help...
When I got the device it came with a 2.29.405.2 ROM and a 32.49.00.32U_5.11.05.27 radio ROM. I used unrevoked3 to root the phone and have been using custom ROMs since.
I've downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe, but every time I'm trying to flash it, the process aborts during 'updating signature...' and I end up with:
Code:
ERROR [131]: CUSTOMER ID ERROR.
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Not sure what I'm doing wrong. Maybe I'm using an RUU for the wrong area? I'm pretty sure the original ROM was WWE though (it definitely was 2.29.405.2 / 32.49.00.32U_5.11.05.27). I've read somewhere that you can't just flash an RUU if it has a lower HBOOT version... Do I need a goldcard or what's the best way to go back to the stock ROM?
Any help would be much appreciated...
Just in case, here's what my bootloader info:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18

You only need a goldcard if you are branded right now..
So is your phone branded with a carrier rom, then you must make a goldcard.
I think customer id error is due to incorrect goldcard.
There is a newer version, 2.29.405.5 I dont know if that's gonna work but worth a try.
You can also try to put the zip on your sd card instead of running an exe on your pc, assuming that you run the exe.

Thanks for the quick response.
My Desire was unbranded, so I guess I won't need a goldcard then.
I've downloaded the newer RUU version you mentioned, but got the same error message...
So far I've only tried the .exe, but I'll see if I have more success with the .zip.
Could the issue be that my current HBOOT version is higher than that of the RUU?

You can try to flash 2.3.3 from htcdev.com it's works for all hboots and without goldcards

boy_in_oz said:
My Desire was unbranded, so I guess I won't need a goldcard then.
Could the issue be that my current HBOOT version is higher than that of the RUU?
Click to expand...
Click to collapse
Since you get a CID error, I would definitely try a goldcard.
You can also try flashing the downgrader from alpharev first.
ETA: I think the latter would help.
from alpharev site: said:
# Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first.
Click to expand...
Click to collapse
-Jobo
@MatDrOiD (vv post below) Good point. I failed to notice that.

@touch of jobo:
Flashing downgrader from AlphaRev is not possible, the OP is S-ON.
@OP:
Check bortak's guide to bring your phone back to stock.

Have you tried step 7 in Bortak's guide? (http://forum.xda-developers.com/showthread.php?t=1275632) It was the solution for me! I skipped the downgrading part (had the same hboot as you have, so that shouldn't be a problem) and went on with phase 2.
If your phone was indeed unbranded, the goldcard should not be a problem as I understood..

Thanks guys. I'm at work at the moment but will give Bortak's guide a shot when I get home tonight and report back then.

The definition of unbranded is a bit different. Unbranded does not exactly mean that there isnt a carrier logo. HTC manufactured and sold phones in India as an example is for all intents a branded Device. It's the INFOCID property that defines whether branded or unbranded.
fastboot oem gencheckpt
Click to expand...
Click to collapse
Inside an RUU zip is a small text file. Open it and see if your INFOCID value is included. If not, you cant flash that RUU without a goldcard. See my sig for the unbricking guide, which explains this.
From my Guide:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code (Customer ID) which prevents you from flashing a ROM meant for any other brand and also blocks a Generic WWE RUU. If you're from India, it is branded with HTC_038. If you're unbranded, things are looking much easier for you, as generic WWE RUUs for SLCD are easily available. Run the following code from the sdk folder to find out if your device is branded
Code:
fastboot oem gencheckpt
This displays the CustID Code as HTC__ (and a number). If these numbers are the same as included in the cidnum value in the file android-info.txt, your device is unbranded. I have noted the following cidnums are unbranded: HTC__001, HTC__E11, HTC__N34, HTC__203, HTC__102, HTC__K18, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__016, HTC__032. I'm not sure whether it is an exclusive list. To find out if an RUU is compatible for your ROM, the value displayed by fastboot oem gencheckpt has to be included in the cidnum list of the RUU. If it isnt included, you will need to use a goldcard to bypass the cidnum checks done by the RUU.
Check if you have made a goldcard (A goldcard is a normal microsd card modified to become special while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA or allow you to switch between software meant for different regions). The purpose of a goldcard is that when apparently incompatible ROMs are flashed with a goldcard inside the device, the flashing process skips certain checks like the Customer ID check (and hence no CID error). Note however that you cannot ordinarily install software of a lower version just because you have a goldcard. Note also that it is the software version which is important, and not the Bootloader version. Note that if you want to downgrade your software to a lower version, it is easiest to use Teppic74's utility (Link1 or Link2), and downgrade to his version of the RUU (1.21), then upgrade to your version of RUU. If your device is SLCD, always make sure the software you're about to flash does support an SLCD screen. As a general rule of thumb, flashing any version <2.0 may be dangerous. Teppic74 assures us that the version 1.21 his utility comes with, is compatible with SLCDs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Wow, I would have never guessed this... With fastboot oem gencheckpt I found that the CID is T-MOB101... i.e. my Desire is actually branded! I bought it from mobicity in Australia as an imported unlocked phone and *assumed* that it was unbranded... So it's not surprising that the RUU gave me a customer ID error. (This also explains why the OTA update failed while I was still using this ROM).
What's really weird though is that the version of the ROM that the phone came with was definitely 2.29.405.2 with baseband ROM 32.49.00.32U_5.11.05.27... I did some googling today, but couldn't actually find a T-Mobile ROM with these version numbers
My guess is that mobicity imported the phone and flashed a stock HTC WWE ROM so they could sell it in Australia...
Any thoughts on this? I'm assuming that means that I do need a goldcard after all to go back to the stock ROM?

Ok, as I couldn't find a T-Mobile ROM with the aforementioned version numbers, I eventually decided to make a goldcard and flash RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe. The whole process worked fine without any error messages and the RUU reported success at the end.
Unfortunately my bootloader still displays the same info as in post 1, i.e. I'm still on HBOOT 0.93.0001. I would have expected this to revert back to 0.93... Did something go wrong with the updating procedure?
The issue is obviously still that the original ROM seemed to be a T-Mobile ROM (in fact I think a German one as fastboot oem gencheckpt reports the carrier as TMD), so I'm not sure if the service point will accept the unbranded WWE ROM I flashed.
The other option might be to flash the official HTC Desire Android 2.3 Upgrade from www.htcdev.com, but I think it's not compatible with T-Mobile Germany Desires... If I could flash this, it would at least be an official release and the service point shouldn't complain. Does anyone know how easy it is to root/S-OFF/install custom recoveries/ROMs afterwards? From what I read, I would need to use revolutionary, right?
Any alternative suggestions would be much appreciate...

Your are totally fine with 2.29 RUU. Hboot would only update if you flash 2.3.3 RUU. Did not read about guys who "bricked" their phone by using 2.3.3 RUU on a desire by T-Mobile.
Sent from ICS with Transparent XDA App

RUU & firmwares

Hello guys,
Been wondering for a while how people find the right RUU.I know they use the command fastboot getvar version-main and that they get a couple of numbers out of that. I have heard that you need the same number ruu or higher than the number that pops out when doing that command is that right? And where do people get the ruu from?
Also, what is a CID? And last but not least: when flashing firmware you flash a custom bootloader am I right? Some roms require some kind of firmware and I do not understand the point of it yet. What if you want to get back to your original bootloader?
I tried using other threads but it is very unclear to me. I would really like to know how to get people the correct ruus so I can help myself and other people as well
Sent from my HTC One X using xda app-developers app

A ruu must indeed match the number that comes out of the fastboot command, it can't be lower because the ruu contains a lower hboot version. We need S-OFF to do that, and S-OFF is not available for our phones. Some have it but they are lucky.
A ruu may be higher as the number except for a lower hboot then 1.12 to 3.14. So when somebody is on software version 1.29 he can't run a 3.14 ruu. A 2.17 based ruu is a must before the 3.14 one ..... that is if they are available to begin with. Ruu's after 3.14 are rare. Some have been released but most are not.
CID is a customer ID, its a region code. My cid is HTC__E11 that means a dutch region. It also tells if a phone is carrier branded like vodaphone or O2
And about the firmware that can be flashed ......its a standalone firmware to upgrade the hboot to a JB one, that goes for every hboot version. So if you have 1.29 software version (hboot 0.95-0.96) then you can straight away flash it to 3.14 hboot 1.31-1.39. Not like the ruu where this is impossible to do.
Hope this explains some question marks ?
Links to ruu's :
http://forum.xda-developers.com/showthread.php?t=2189048
http://forum.xda-developers.com/showthread.php?t=2094113
Link to firmwares :
http://forum.xda-developers.com/showthread.php?t=1957376
And if a ruu is not available they need to return to stock with a stock nandroid backup. No other way to do it then !
Links to stock back-ups :
http://forum.xda-developers.com/showthread.php?t=1975140
http://forum.xda-developers.com/showthread.php?t=2189048
Cheers !
Mr Hofs

Thanks alot. Could you name a reason why someone would want to know his CID? Is that for firmware purposes? I'm on holiday now so I can't find my ruu. Once I get home ill try to find it on my own thanks for the info I understand much better now
Sent from my HTC One X using xda app-developers app

Well a cid is for me not so important, but the info listed in the threads sometimes go on cid first so its easier searching. The main version number tells me everything.
It gives me the info what hboot version, what software number and if its carrier branded ..... but that's also some experience i picked up lately
Edit :
Ow yeah sometimes carrier branded phones have the same cid but a different software version. Example :
1 cid has software 2.17.206 as number and the same cid has software 2.17.207 as version. So sometimes its good to know the cid too.

Mr Hofs said:
A ruu must indeed match the number that comes out of the fastboot command, it can't be lower because the ruu contains a lower hboot version. We need S-OFF to do that, and S-OFF is not available for our phones. Some have it but they are lucky.
A ruu may be higher as the number except for a lower hboot then 1.12 to 3.14. So when somebody is on software version 1.29 he can't run a 3.14 ruu. A 2.17 based ruu is a must before the 3.14 one ..... that is if they are available to begin with. Ruu's after 3.14 are rare. Some have been released but most are not.
CID is a customer ID, its a region code. My cid is HTC__E11 that means a dutch region. It also tells if a phone is carrier branded like vodaphone or O2
And about the firmware that can be flashed ......its a standalone firmware to upgrade the hboot to a JB one, that goes for every hboot version. So if you have 1.29 software version (hboot 0.95-0.96) then you can straight away flash it to 3.14 hboot 1.31-1.39. Not like the ruu where this is impossible to do.
Hope this explains some question marks ?
Links to ruu's :
http://forum.xda-developers.com/showthread.php?t=2189048
http://forum.xda-developers.com/showthread.php?t=2094113
Link to firmwares :
http://forum.xda-developers.com/showthread.php?t=1957376
And if a ruu is not available they need to return to stock with a stock nandroid backup. No other way to do it then !
Links to stock back-ups :
http://forum.xda-developers.com/showthread.php?t=1975140
http://forum.xda-developers.com/showthread.php?t=2189048
Cheers !
Mr Hofs
Click to expand...
Click to collapse
How do you know what software version you are running to begin with? I mean it doesnt add up. You can have a 1.29 bootloader but its hboot 0.95-0.96? That Part I don't get yet but the rest is clear ty
Edit: ah the software version is the oneu get from cmd and you find an ruu based on that and on your hboot version am I right?
Sent from my HTC One X using xda app-developers app

The 1.29, 2.17 and 3.14 number i mentioned are the rom software numbers and they are linked to hboot numbers like 0.95-0.96 and 2.17 is 1.12 and from 3.14 to 3.20 its 1.31-1.39

Thanks, will try to find my ruu if I'm home
Sent from my HTC One X using xda app-developers app

[Q] RUU M8 TMOB003 xx.14

I am looking for a RUU file for my DUTCH M8 which is S-on.
CID: TMOB003
The firmware is .14 based. Reason why I need this is because of my firmware is messed up. Hboot version is 3.16.
I already noticed multiple requests for this firmware. Or any other compatible european version will do.
And yes, I know the final solution would be making the phone s-off.
Enough Dutch people on here so I try again!
Thanks in advance!

Can I install any RUU on my HTC one M8?

Hello dear friends,
I bought a HTC One M8 from China. The phone is originally made for USA T-Mobile but it comes with a changed RUU with Android 5.0.1 which can not be updated. The MID is 0P6B13000 and CID is changed to supercid already (111111111). I would like to install on it a European RUU (latest version) originaly made for MID 0P6B10000. I don't know if there is any actual difference between 0P6B10000 and 0P6B13000 or if their RUUs can be exchanged with one another. Can I already download a European RUU and directly install it? Should I not do it? Should I change MID and CID as those of an European version? Or should I restore the factory CID and leave the MID as it already is? I have also read that before installing a last version RUU I have to update the firmware, is that correct? If anyone with good experience can give me good advice and if possible usefull links of tutorials and downloads I would much appreciate it.
Thank you in all advance!

vantelyn said:
I don't know if there is any actual difference between 0P6B10000 and 0P6B13000 or if their RUUs can be exchanged with one another.
Click to expand...
Click to collapse
To flash an RUU, you need to pass CID check and MID check. SuperCID means you will pass any CID check. But you still need to pass the MID check. That means, if you want to flash the Euro RUU, you need to change the MID to 0P6B10000.
Guide on changing the MID is here: http://forum.xda-developers.com/showthread.php?t=2708581
vantelyn said:
Should I change MID and CID as those of an European version? Or should I restore the factory CID and leave the MID as it already is?
Click to expand...
Click to collapse
That is a slightly complicated question. Euro version is probably desirable for most folks, since it removed the T-Mobile branding (exception might be if you are actually using T-Mob US as your carrier, and want WiFi calling).
The other issue would be, what bands does your carrier use, and which version supports those bands (as flashing the RUU will change band support). Again, for many folks Euro RUU is probably better. But it depends on you carrier (what bands they use for 3G and LTE).
vantelyn said:
I have also read that before installing a last version RUU I have to update the firmware, is that correct?
Click to expand...
Click to collapse
If you want to flash an RUU to update from LP to MM, then yes that is true that you need to flash the MM firmware before the MM RUU. Otherwise, the RUU will fail with Error 155.

Don't you have to s-on before using the RUU also?
You also don't need to change your mid, just change it in the android-info.txt unless you plan to use international roms to get the full benefits (some Roms setup based on mid)

S-Off, Unlocked - No OTA

Hi,
As much as I tried to look for this information, I didn't find a clear answer.
I have an M9 running 1.32.401.17 (stock recovery, from an old RUU), which is S-Off with unlocked bootloader. I was really expecting to get all the OTAs, so you can imagine my surprise when I didn't get any.
I then thought that I need to relock the bootloader, and then I will receive the OTAs. I relocked the bootloader, and again - no OTAs.
1. For an S-Off phone, should one receive OTAs with unlocked bootloader, or does one have to relock the bootloader (if so, to "locked" or to "relocked") to get OTAs?
2. Is the OS version on my phone so old that OTAs are not provided anymore?
3. Does it mean that if I manage to get a more "contemporary" OS version on my phone I'll get the OTAs?
4. If none of the above are correct, what do I need to do to get OTAs on my S-Off M9?
Thank you very much.
Adrian

Thanks to the fantastic post from Nikolay82 "HTC One M9 - 3.35.401.12 RUU installer how to guide!"
https://forum.xda-developers.com/one-m9/help/htc-one-m9-3-35-401-12-ruu-installer-t3318517
I managed to upgrade to 1.40.401.8.
After that I started to get OTAs (I'm now at 3.35.401.12) . So I can confirm that one doesn't need to relock the bootloader for an S-Off phone in order to receive OTAs (S-Off and UNLOCKED is fine).
I still don't know why I didn't get any OTA update for 1.32.401.17, but I'm happy that it worked from 1.40.410.8.
Cheers

Correct bootloader unlocked makes no difference. S-off makes no difference.
There is a possibility that htc have stopped the release of the earliest firmware. There is also a possibility that there was a problem but it would be solved by the update you did.

Even with S-ON you can receive updates with an unlocked bootloader.
The reason for your issue was the firmware you were using. 1.32.401.17 only got distributed in one single country. Therefore, only one specific CID of the handful of CIDs that belong to SKU 401 supports this "special" firmware version. In other words, you can't update a M9 and are stuck with that firmware if you aren't using the supported CID. The only solution is flashing a RUU with a different firmware version. That's why the RUU for 1.32.401.17 isn't linked in the ReadMe thread.
Edit: I can't tell you which CID actually corresponds to that "special" version since I forgot which one it was.
Sent from my HTC One M9 using XDA Labs