I download the official ruu from htc official website
I relocked my htc m8, and reboot to bootloader, run this exe, but it cause an error with code 155. btw, my htc model number is m8w exactly.
Thanks for any reply.
Did you verify the bootloader screen says RELOCKED?
Also, it appears that M8_w is either Sprint or Verizon. If you tried an RUU for another version, it will fail with the wrong CID and MID.
You can not flash an RUU for another version if you have the Sprint or Verizon versions (brick risk, even if you s-off and change CID and MID).
Related
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,
I have the unlocked version of the M8 (I believe...) It's a European model and is unlocked to all carriers.
My CID is HTC_001 but when I go to install the RUU that was released not long ago I get the Error 130 returned.
Is this just me being stupid due to lack of sleep?
Try following this guide: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
You may need to s-off to get the superCID. I would highly recommend to do so.
nathankk said:
Hello,
I have the unlocked version of the M8 (I believe...) It's a European model and is unlocked to all carriers.
My CID is HTC_001 but when I go to install the RUU that was released not long ago I get the Error 130 returned.
Is this just me being stupid due to lack of sleep?
Click to expand...
Click to collapse
Error 130 is wrong MID.
You're trying to flash the wrong RUU. Which one are you trying to install? You need an RUU that is 401.
xunholyx said:
Error 130 is wrong MID.
You're trying to flash the wrong RUU. Which one are you trying to install? You need an RUU that is 401.
Click to expand...
Click to collapse
My Meid is 0000000000 and I am trying to install the latest one they released on the HTC website.
Cid HTC__001 is WWE *.**401.* so you need a wwe 401 ruu. If you do not have s-off you cant flash any other ruu files !
Read more here
http://forum.xda-developers.com/showthread.php?t=2911563
And what's your goal ? What do you want to achieve ?
Mr Hofs said:
Cid HTC__001 is WWE *.**401.* so you need a wwe 401 ruu. If you do not have s-off you cant flash any other ruu files !
Read more here
http://forum.xda-developers.com/showthread.php?t=2911563
And what's your goal ? What do you want to achieve ?
Click to expand...
Click to collapse
Thank you! I guess I will just have to wait until Lollipop comes through an OTA update.
So I was browsing the HTC website and came upon this webpage with various ROMs for the HTC m8 and others:
http://www.htc.com/us/support/rom-downloads.html#unlocked
I have an AT&T Unlocked Bootloader and rooted M8 but it's still S-ON.
Can I basically change the CID to the DEV version and then flash this rom/RUU over the M8 to get the developer version?
http://www.htc.com/us/support/htc-one-m8/news/
You need S-OFF to change your CID. So that is your first goal here.
And Sunshine is your only chance to s-off. ?
Thanks Darth,
Did exactly that...sunshine to s-off, changed the cid to supercid and flashed the Dev Edition RUU to get what I wanted. I noticed that you can't use fastboot boot recovery.img with that RUU but I flashed a custom recovery and then back to stock and everything is great now.
Hi everybody,
I'm sorry, I'm sure this question may be asked so much time, but after 1 hour searching I don't find anything usefull for me... (Maybe a keywork issue ?)
I don't know what I've done, but after I locked again the bootloader in order to flash on a RUU, I blocked my HTC 10 and can't boot on android again.
When I tried it the phone is only going to bootloader mode and don't want to get to my Os. I have TWRP and was on the custom LeeDroid 7.0.
I can't backup or do anything and while i try the dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota on the terminal, it won't work...
And I can't unlock again the phone, I've tried and it's "relocked".
Has someone have the same issues ? Really need your help ! :crying:
Thank you !
Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
You might wanna try using a RUU.exe to get your OS back. What firmware and model do you currently have?
bamidrol said:
Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
Click to expand...
Click to collapse
Yes it was lol...
But i've read that it was better to be on a locked bootloader to flash ruu :crying:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...
silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.
Tech_Savvy said:
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.
Click to expand...
Click to collapse
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
---------- Post added at 04:26 AM ---------- Previous post was at 04:24 AM ----------
hadory said:
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
Click to expand...
Click to collapse
The download mode works, bootloader too
I'm not able to flash with an unlocked or a locked bootloader, i've tried the RUU and the custom ROM like Leedroid for example.
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?
Click to expand...
Click to collapse
I don't think it's the US MID, my IMEI is German and the phone works great on 4G / LTE in France (where I live) and i've read that 4G won't work with an US version in France, but maybe you're true and their is no RUU for my version ... (fragmentation pleasures).
Do you know how i can s-off this phone in order to change those CID which block me ? ^^' because i can't use sunshine bc no OS installed and can't flash one ...
In fact, the only think i can flash / unflash is TWRP and the recovery stock..
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