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
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
hi , just got my phone from ebay and its a superCID one so it seem it cant find any ota , can anyone point me to the most recent RUU ?
or if anyone does have it on his disk can he upload that RUU on dropbox ? thanks in advance
Before anyone can suggest the latest of RUU for you, you need to give more details especially what your current software version no. is ... maybe you have the latest one that is why no OTA update for your device.
ckpv5 said:
Before anyone can suggest the latest of RUU for you, you need to give more details especially what your current software version no. is ... maybe you have the latest one that is why no OTA update for your device.
Click to expand...
Click to collapse
it is a demo unit , in a white box , it has superCID and S-ON , the version is 1.46.401.1
Never see a RUU with that no.
Make sure you take care of it, it is not easy to find RUU now as HTC is hunting down people who publish RUU at the moment. But still you can google for it, there are various site with RUUs.
I don't know much about SuperCID, previously you simply run any RUU to your device when you have a SuperCID.
What I understand now is that you need to change the CID to the RUU that you want to flash.
For example, you want to flash an Asia_WWE RUU, you need to change your CID from 111111 to HTC__044 then you can run *.*.707.* RUU. Then again say you want to flash a EU_WWE, you need to change the CID to HTC__001 first then only run the *.**.401.*
BTW, the latest for .401 is 2.22.401.1
HTCRUU has been taken down for now, due to HTC...right now there are NO ruu's to download unless someone has them somewhere
ckpv5 said:
Never see a RUU with that no.
Make sure you take care of it, it is not easy to find RUU now as HTC is hunting down people who publish RUU at the moment. But still you can google for it, there are various site with RUUs.
I don't know much about SuperCID, previously you simply run any RUU to your device when you have a SuperCID.
What I understand now is that you need to change the CID to the RUU that you want to flash.
For example, you want to flash an Asia_WWE RUU, you need to change your CID from 111111 to HTC__044 then you can run *.*.707.* RUU. Then again say you want to flash a EU_WWE, you need to change the CID to HTC__001 first then only run the *.**.401.*
BTW, the latest for .401 is 2.22.401.1
Click to expand...
Click to collapse
thanks a lot mate , i've been able to download the 2.22.401.1 RUU from a chinese site and succesfully flashed with phone in fastboot mode
stesa said:
thanks a lot mate , i've been able to download the 2.22.401.1 RUU from a chinese site and succesfully flashed with phone in fastboot mode
Click to expand...
Click to collapse
:good::good:
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?
Hi All,
Is it just me, or does anybody else agree that someone somewhere should post a nice, easy to read RUU guide with screenshots that mean something.
I've always looked for a good guide with easy to use screenshots that ACTUALLY EXPLAINS the process of choosing the correct RUU, what you should look at and why.
Yes I know theres a couple of guides on it, but non of them explain how to pick the correct RUU for your device, and why that RUU is the right one.
Most of the time, I leave the RUU Guide threads knowing as little as I knew about RUU's to start with.
There is actually 1 rule to find the correct ruu.
Fastboot getvar version-main
That command tells the number of the ruu you need as a minimal number to start with. And in our case it has to start with endevouru because it's the codename for our hox.
So if your number is 3.14.401.31 you need a ruu that matches that exactly.
You can however flash different ruu's but it has to have a higher number. For example :
2.17.401 = main number, that number can go a step forward and flash the 3.14.401 ruu.
Obviously you can only downgrade with a ruu if you have s-off. So someone who is on 3.14.401 and a s-on device can not install the 2.17 ruu because it tries to downgrade the bootloader.
Hope this answers your question a little bit.
Cheers.
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
There is actually 1 rule to find the correct ruu.
Fastboot getvar version-main
That command tells the number of the ruu you need as a minimal number to start with. And in our case it has to start with endevouru because it's the codename for our hox.
So if your number is 3.14.401.31 you need a ruu that matches that exactly.
You can however flash different ruu's but it has to have a higher number. For example :
2.17.401 = main number, that number can go a step forward and flash the 3.14.401 ruu.
Obviously you can only downgrade with a ruu if you have s-off. So someone who is on 3.14.401 and a s-on device can not install the 2.17 ruu because it tries to downgrade the bootloader.
Hope this answers your question a little bit.
Cheers.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers Hofs
Don't think theres an RUU for my version then :/
Mr hofs?
I have a couple questions my self.
Correct me if I am wrong please.
1. RUU's Come in 2 forms and EXE and ZIP format
2. EXE will be a windows Executable RUU from HTC for a specific model and variant of a htc device.
3. Zip Format is for use in Fastboot to restore to stock for a specific model and variant of a htc device.
Furthermore I have these questions.
Are there Encrypted and Decrypted RUU's - If so What is the difference?
Will flashing a RUU regardless of Encrypted or Decrypted result in S-ON after it successfully completes?
Thanks,
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
Mr Hofs said:
There is actually 1 rule to find the correct ruu.
Fastboot getvar version-main
That command tells the number of the ruu you need as a minimal number to start with. And in our case it has to start with endevouru because it's the codename for our hox.
So if your number is 3.14.401.31 you need a ruu that matches that exactly.
You can however flash different ruu's but it has to have a higher number. For example :
2.17.401 = main number, that number can go a step forward and flash the 3.14.401 ruu.
Obviously you can only downgrade with a ruu if you have s-off. So someone who is on 3.14.401 and a s-on device can not install the 2.17 ruu because it tries to downgrade the bootloader.
Hope this answers your question a little bit.
Cheers.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Very useful..
DeadPhoenix said:
Mr hofs?
I have a couple questions my self.
Correct me if I am wrong please.
1. RUU's Come in 2 forms and EXE and ZIP format
2. EXE will be a windows Executable RUU from HTC for a specific model and variant of a htc device.
3. Zip Format is for use in Fastboot to restore to stock for a specific model and variant of a htc device.
Furthermore I have these questions.
Are there Encrypted and Decrypted RUU's - If so What is the difference?
Will flashing a RUU regardless of Encrypted or Decrypted result in S-ON after it successfully completes?
Thanks,
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
Very useful..
Click to expand...
Click to collapse
1: for hox at least only .exe format.
2: correct
3: i never seen a zip ruu for the hox
4: ruu's are encrypted (maybe some older ones not)
5: if you have s-off a ruu will not make you s-on (most of us users are s-on already anyway)
Cheers.
Mr Hofs said:
1: for hox at least only .exe format.
2: correct
3: i never seen a zip ruu for the hox
4: ruu's are encrypted (maybe some older ones not)
5: if you have s-off a ruu will not make you s-on (most of us users are s-on already anyway)
Cheers.
Click to expand...
Click to collapse
I am asking for the HTC One Max(hom) forums. We are getting conflicting answers about S-ON after a Encrypted or decrypted RUU is run. We appear to have a decrypted version for Verizon in our forums.
We wanted to get some definitive answers for a help thread I started.
Ah, can't say this about another device. I only know these things count for the hox....
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.