I'm getting the 140 Error when trying to flash
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe.
Also tried some other RUUs, without success.
Need to unroot my phone, since it Restarts randomly and needs the board replaced.
Please someone help!
Having a generic (not branded) Desire, ROOT, latest LeeDroid ROM,
BRAVO PVT SHIP S-ON
HBOOT 0.80
AMOLED
5.09.05.30_2 Radio
SD Card Working
Access to SD via USB working.
One day I was trying to S-OFF this phone, but all I got was the ugly Joker splash screen, can this be the problem?
This phone has been rooted-unrooted-rerooted before without problems!
Thanks!!
Why not get the 2.10.405.2 or 2.29.405.2 RUUs? If they don't work either it might be because you have a branded handset
EddyOS said:
Why not get the 2.10.405.2 or 2.29.405.2 RUUs? If they don't work either it might be because you have a branded handset
Click to expand...
Click to collapse
where are these RUUs hosted? Didn't find any direct links here on xda. EDIT:Found your thread: http://forum.xda-developers.com/showthread.php?t=828519
And why aren't they in this thread? http://forum.xda-developers.com/showthread.php?t=695667
will try out and report.
the phone is for sure not branded, was preordere on amazon.de back in the good ol' days and is running Lee's ROM.
http://shipped-roms.com/index.php?category=android&model=Bravo
Check your build number, from there you can see if your phone is branded or not.
BTW: have you wiped everything during rom flashing?
for example,
I have (originally) : 1.19.161.5, and that is a vodafone UK branding.
I have to use : RUU_Bravo_Vodafone_UK_1.19.161.5_Radio_32.36.00.28 U_4.06.00.02_2_release_126338_signed.exe
aaa said:
Check your build number, from there you can see if your phone is branded or not.
BTW: have you wiped everything during rom flashing?
for example,
I have (originally) : 1.19.161.5, and that is a vodafone UK branding.
I have to use : RUU_Bravo_Vodafone_UK_1.19.161.5_Radio_32.36.00.28 U_4.06.00.02_2_release_126338_signed.exe
Click to expand...
Click to collapse
Why not use the 2.33.161.2 RUU in ROM Development?
http://forum.xda-developers.com/showthread.php?t=853937
SOLVED
SOLVED:
Thanks a lot Guys, that was easyier as I thought and saved me a lot of nerves.
I simply flashed 2.29.405.2 RUU and everything was fine!
I just dont unterstand why the stiky thread in the Development section is not being updated with these RUUs. It would have saved me many hours!
Because everyone goes to shipped-roms.com for their stock RUUs
EddyOS said:
Why not use the 2.33.161.2 RUU in ROM Development?
http://forum.xda-developers.com/showthread.php?t=853937
Click to expand...
Click to collapse
No problem with that one.
If I am not mistaken :
It is just that the one you posted will update to Android 2.2 and H-Boot 0.93, while my post ís still 2.1 and H-Boot 0.80.
For comfort reason during rooting, I choose the 0.80.
But seeing as rooting on HBOOT 0.93 has NO issues at all it makes sense to use it
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
Hello All
simply i can't get my stock rom as it is 1.29.709.12, and i need the device to get back to its stock to be able to OTA to fix some weird issues like sound and lids.
I've heard about the superCID that allows me to install another RUU on my device, so is that true? and can this be done on the international unbranded devices?
CID: 621
Image Version: 1.29.709.12
hboot: 0.95
s-on
appreciate your support folks
Hossam.Abdelsalam said:
Hello All
simply i can't get my stock rom as it is 1.29.709.12, and i need the device to get back to its stock to be able to OTA to fix some weird issues like sound and lids.
I've heard about the superCID that allows me to install another RUU on my device, so is that true? and can this be done on the international unbranded devices?
CID: 621
Image Version: 1.29.709.12
hboot: 0.95
s-on
appreciate your support folks
Click to expand...
Click to collapse
We need to have s-off on the one x before we can write super cid. At the moment s-off has not been found. Did you make a nandroid backup of your stock?
nope, unfortunately i was a newbie when I rooted and installed the 1st custom rom, and after everything was gone I’ve been told that i should have made a nandroid backup (my bad)
ok, let me ask it in another way, my target is to have an official rom to OTA, and finding my 1.29.709.12 RUU or a higher x.xx.709.x is impossible. any help would be really appreciated.
what if I get someone else's nandroid backup? will it allow the OTA then?
Hi,
I have been searching for an RUU for the australia optus branded HTC one V (CID 980 or OPTUS_001) but have had no luck.... does anyone know where I can get it? I would be eternally grateful as my one V constantly reboots due to a radio update ota...
Have since rooted and installed many different custom roms with no change in the outcome... so i unfortunately need the RUU otherwise the phone is going to have to become a paper weight.
I've also tried many other RUU;s for different CIDs but with no luck (they all say wrong CID).
I would even be prepared to pay someone if they needed me to!!!
check the htcdev website. if an ruu was released for your device,it would be there.
There's no RUU for OPTUS001 CID as of what I know.
MameTozhio said:
There's no RUU for OPTUS001 CID as of what I know.
Click to expand...
Click to collapse
Ok thanks guys. So am I right in saying that there is NO way I can change my CID (to 111111) because its not possible to gain S-Off on the HTC One V?
Then this means there is no way I can use another RUU to revert the phone back to stock because it will only accept the OPTUS001 RUU?
I have htc m9
International versio
unlocked bootloader s-off
running android 5.0.2
1.32.401.17
Every time i check for update it says it is up to date
tried various roms that i ddnt knw whether i was right
it fails and say....signature error
how can i update this phone(hima uhl....)
Firmware 1.32.401.17 got only distributed in one single country. In other words it's only compatible with one single CID whereas all other 401 firmware versions are compatible with a handfull of CIDs. That means if you flashed this version's RUU on your phone (which is in this special case possible with S-OFF even if the CID isn't the correct one) and are stuck then you're probably not using the compatible CID. You need to flash a different 401 RUU for solving that issue. (Theoretically you could change your CID, as well, but I don't know the exact CID that is needed for getting out of the situation.)
The reason why you can't flash 4.x RUUs on your phone is explained in the ReadMe thread. You may want to read it (especially the RUU section) since it contains all files/instructions that are needed in your situation.