[GUIDE] Upgrade HBOOT from 0.95 to 1.39 - HTC One X

Here is how I did it:
You need:
- Fastboot (from Android SDK)
- This file: https://www.dropbox.com/s/9aay5ktvtyqci4j/firmware.zip
- Your "Unlock_code.bin" file
Do the following:
- Boot into the bootloader (if you don't know how please don't try to do the other steps)
- Check your CID and compare it to the list on the bottom of this post: "fastboot oem readcid"
- Check your version with "fastboot getvar version-main"
- Lock the bootloader " fastboot oem lock"
- Reboot into RUU: "fastboot oem rebootRUU"
- Flash the file attached to this post: "fastboot flash zip firmware.zip"
- A message tells you that the flash failed and that things are broken: Don't panic!
- Execute the command "fastboot flash zip firmware.zip" again!
- Reboot into bootloader: "fastboot reboot-bootloader"
- Unlock your bootloader "fastboot flash unlocktoken Unlock_code.bin"
Done!
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE! DO THIS AT YOUR OWN RISK!
I used a dutch HTC One X with S-ON and CID "HTC__E11"
I used the following firmware.zip from the following OTA update: http://androidfiles.org/ruu/securekey.php?file=Endeavor/OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.18.401.1-3.14.401.31_R_release_308291aozis6kzu7ls9js6.zip
I found the update on: http://androidfiles.org/ruu/?developer=Endeavor
Good luck!
Do only use when your CID matches:
00000000
11111111
22222222
33333333
44444444
55555555
66666666
77777777
88888888
99999999
HTC__001
HTC__E11
HTC__203
HTC__102
HTC__405
HTC__Y13
HTC__A07
HTC__304
HTC__M27
HTC__032
HTC__016

http://forum.xda-developers.com/showthread.php?t=1957376

Worked a treat thanks for the guide. It was a lot easier than it initially sounded
Sent from my HTC One X

Does it work with cid version of:
HTC_044 (asia pacific version)
Thaks...
Sent from my HTC One X using xda app-developers app

Briztama said:
Does it work with cid version of:
HTC_044 (asia pacific version)
Thaks...
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Go to the thread i linked. This thread will not help you

Disregard that the Asia WWE version only has 1.36 MAX :silly:

Briztama said:
Disregard that the Asia WWE version only has 1.36 MAX :silly:
Click to expand...
Click to collapse
Hmmm not much a difference between 1.36 and 1.39 though

Related

[Q] Radio Flash & CID Change

Hi
At first, sorry for my bad english
I have allready successfull flashed my DHD (Root, S-OFF, Radio S-OFF)
Now i try to flash a DHD with Swisscom Branding (
C:\android\tools>adb shell getprop ro.cid
VODAP110)
My problem: I can't flash any Radio after Root & SHIP S-OFF and i can't change the CID:
C:\android\tools>fastboot flash radio radio.img
sending 'radio' (24832 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed)
I've tryd at the last 2 day's all available howto's...such as:
http://forum.xda-developers.com/showthread.php?t=855403&highlight=SYSTEM+INFO
http://forum.xda-developers.com/showthread.php?t=896597
http://forum.xda-developers.com/showthread.php?t=855403
I can flash ROMs, i can flash RUU's but my CID is always the same! VODAP110
what can i do? or what i've maked false?
the hboot Menu is strange...i have no SYSTEM INFO...only:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
via shell:
C:\android\tools>fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 0.85.0004
INFOversion-baseband: 26.02.00.29_M4
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.24.405.1
INFOserialno: HT0CNRX14993
INFOimei: 356299042377414
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4204mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e0c48fbb
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
when i have a look at my unbrandet DHD there is a Menupoint SYSTEM INFO... why?
thanks a lot for your advice!
greez
It seems that you haven't Eng Hboot
Look here : http://forum.xda-developers.com/showthread.php?t=835746
thnx! radio flash works now fine!
but my CID is still VODAP110...:
C:\android\tools>adb shell getprop ro.cid
VODAP110
i've tried the Desire HD easy radio tool v2_2 again and again...no change!
Gysu said:
thnx! radio flash works now fine!
but my CID is still VODAP110...:
C:\android\tools>adb shell getprop ro.cid
VODAP110
i've tried the Desire HD easy radio tool v2_2 again and again...no change!
Click to expand...
Click to collapse
Strange.
On my DHD, i just ROOT and used Easy radio Tool v2_2 and hboot S-OFF
And when i go into system info in the bootloader, i see CID 11111111
d3rf said:
Strange.
On my DHD, i just ROOT and used Easy radio Tool v2_2 and hboot S-OFF
And when i go into system info in the bootloader, i see CID 11111111
Click to expand...
Click to collapse
@bootloader SYSTEM INFO i also see CID = 1111111
but when i run Android and i read my CID via adb or CID Getter app there is still the CID = VODAP110....
the 1.000.000 million dollar question now is: can i load (with this config) HTC OTA updates or must i still waiting of updates from my provider?
Gysu said:
@bootloader SYSTEM INFO i also see CID = 1111111
but when i run Android and i read my CID via adb or CID Getter app there is still the CID = VODAP110....
the 1.000.000 million dollar question now is: can i load (with this config) HTC OTA updates or must i still waiting of updates from my provider?
Click to expand...
Click to collapse
In MOST cases once you do these changes you loose the ability to do OTA
Why have you done this is you still feed the need to stick with the stock rom?
Gysu said:
@bootloader SYSTEM INFO i also see CID = 1111111
but when i run Android and i read my CID via adb or CID Getter app there is still the CID = VODAP110....
Click to expand...
Click to collapse
I can't remember where I read it, but this is a known issue, but the SYSTEM INFO is the one that interferes with your ability to flash new radios so don't panic
ghostofcain said:
I can't remember where I read it, but this is a known issue, but the SYSTEM INFO is the one that interferes with your ability to flash new radios so don't panic
Click to expand...
Click to collapse
same probl.... but which is the right CID?The one in bootloader SYSTEM INFO that shows CID = 1111111 or the one we read via adb or CID Getter app ?
How to finally change it?
Spaghetti-XRY said:
same probl.... but which is the right CID?The one in bootloader SYSTEM INFO that shows CID = 1111111 or the one we read via adb or CID Getter app ?
How to finally change it?
Click to expand...
Click to collapse
Technically they are all right, but the important one is the bootloader one, which tells the phone in bootloader mode that it's unbranded. As i said earlier it's a known issue and being worked on so currently your stuck with the different CIDs
An Android known issue or an Htc / operator branding one? I'd like to know right know
Anyway I solved, installing a stock ROM 1.32.x, visionary+ permroot and one tool eng s-off. SystemInfo appeared into menu.

[TUT] How to upgrade HOX with a RUU(hboot.img, etc..) after installed a custom rom

(this is the only way we have now to upgrade the hboot.img, bct.img, rcdata.img, etc...)
Method 1
Install stock rom of your CID
-fastboot oem readcid (to know your CID)
-all roms are based on x.xx.401.xx , so you need to download the right RUU(that matches your CID) and extract rom.zip to cook a stock rom for you
-flash custom stock rom(extracted and cooked from right RUU) on custom recovery
-fastboot flash boot c:\boot.img (flash stock kernel that's inside custom stock rom boot.img file)
RElock the bootloader (you can allways unlock)
-fastboot oem lock
Right RUU file for your CID
-put your phone on fastboot (it will not boot because you have a custom rom on a locked bootloader)
-now you can run the RUU exe file and upgrade your phone
​
Method 2
Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)
Extract boot.img, system.img, signed_recovery.img from rom.zip
Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot erase cache
-fastboot oem lock
Power on the phone
Run the RUU exe file (of your CID) and upgrade your phone
​Method 3 (like Method 2, but we dont need to flash the system) (thanks to EddyOS)
Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)
Extract boot.img, signed_recovery.img from rom.zip
Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot oem lock
Run the RUU exe file (of your CID) in fastboot mode
​
STOCK ROMS
http://www.filefactory.com/f/e3e8b30e62a4a8aa/
Click to expand...
Click to collapse
SuperCID 11111111
AirTel-India ????????
Asia-HK-CHT HTC__622
ATT CWS__001
BM BM___001
Bouygues-Telecom BOUYG201
Brightstar-PTB BSTAR502
Brightstar-SPA BSTAR301
Chunghwa-Taiwan CHT__601
CT HTCCN702
CU HTCCN703
DCM DOCOM801
DOPOD DOPOD701
Era T-MOB009
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-DAN H3G__F05
H3G-Italy H3G__402
H3G-ROI H3G__003
H3G-SWE H3G__G04
H3G-UK H3G__001
HTC-Asia-SEA HTC__037
HTC-Asia-SEA-WWE HTC__044
HTC-Australia HTC__023
HTC-BE HTC__E41
HTC-Czech HTC__C24
HTC-Denmark HTC__F08
HTC-Dutch HTC__E11
HTC-EastEurope HTC__032
HTC-ELL HTC__N34
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-GCC HTC__J15
HTC-GER HTC__102
HTC-India HTC__038
HTC-ITA HTC__405
HTC-Nor HTC__Y13
HTC-Norway HTC__H10
HTC-Poland HTC__B25
HTC-PTG HTC__506
HTC-Russia HTC__A07
HTC-Singapore ????????
HTC-SPA HTC__304
HTC-Sweden HTC__G09
HTC-Turkey HTC__M27
[*]HTC-WWE HTC__001
Hutch-Australia HUTCH001
O2-DE O2___102
O2-UK O2___001
Open-Channel HTCCN701
Optus-Australia OPTUS001
ORANGE-AT ORANG113
ORANGE-BE ORANG012
ORANGE-CH-FRA ORANG203
ORANGE-CH-GER ORANG104
ORANGE-ES ORANG309
ORANGE-French ORANG202
ORANGE-PL ORANGB10
ORANGE-PO ORANG008
ORANGE-SK ORANG006
ORANGE-SW ORANG216
ORANGE-UK ORANG001
Rogers ROGER001
SMC-Voda-HK SMCVD001
StarHub-Singapore ????????
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMA T-MOB102
TMCZ T-MOB004
TMD T-MOB101
TMH T-MOB007
TMHR T-MOB006
TMMK T-MOBL11
TMNL T-MOB003
TMSK T-MOB008
TMUK T-MOB005
TMUS T-MOB010
TWM-TW HTC__621
VIRGIN-UK VIRGI001
VODA-Africa-South HTC__016
VODA-Australia VODAP021
VODA-Germany VODAP102
VODA-Greece VODAP006
VODA-Ireland VODAP019
VODA-Italy VODAP405
VODA-Mobilkom VODAP120
VODA-Netherland VODAPE17
VODA-New-Zealand VODAP022
VODA-Portugal VODAPD18
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-SFR VODAP203
VODA-Spain VODAP304
VODA-Swisscom-DE VODAP110
VODA-Swisscom-FR VODAP212
VODA-Swisscom-IT VODAP416
VODA-Swisscom-WWE VODAP015
VODA-TR VODAPM27
VODA-UK VODAP001
Click to expand...
Click to collapse
x.xx.61.x - Orange UK (United Kingdom)
x.xx.65.x - Orange CH (Switzerland)
x.xx.75.x - Orange ES (Spain)
x.xx.110.x - T-Mobile UK (United Kingdom)
x.xx.111.x - T-Mobile DE (Germany)
x.xx.112.x - T-Mobile AT (Austria)
x.xx.114.x - T-Mobile NL (Netherlands)
x.xx.118.x - T-Mobile PL (Poland)
x.xx.161.x - Vodafone UK (United Kingdom)
x.xx.166.x - Vodafone CH-DE (Switzerland - Germany)
x.xx.163.x - Vodafone FR (France)
x.xx.169.x - Vodafone AT (Austria)
x.xx.206.x - O2 UK (United Kingdom)
x.xx.207.x - O2 DE (Germany)
x.xx.401.x - World Wide English
x.xx.707.x - Asia WWE (World Wide English)
x.xx.720.x - Asia India
x.xx.771.x - Hutchison 3G UK (United Kingdom)
x.xx.862.x - Voda-Hutch AU (Australia)
x.xx.980.x - Optus AU (Australia)
x.xx.1400.x - HTC China
Click to expand...
Click to collapse
i have made a stock rom for VODAP001 (x.xx.161.xx)
i can share it
Sometimes when you have a custom rom, you can not update your stock ruu for signature problems (difference between boot, hboot, recovery versions), try to include the TUT to flash the stock RUU and then your TUT
wolfraim said:
Sometimes when you have a custom rom, you can not update your stock ruu for signature problems (difference between boot, hboot, recovery versions), try to include the TUT to flash the stock RUU and then your TUT
Click to expand...
Click to collapse
thats why you need to flash a stock custom rom, on recovery first, to avoid signature problems (the same rom from the right RUU)
Tell me, why should be this way the only way to get the updates? Yesterday i tried it, like its written here and all went okay. The only correction to do is in point 2: fastboot erase cache
http://forum.xda-developers.com/showthread.php?t=1609190
Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
Clear fastboot cache Code:
fastboot clear cache
Boot your phone
Charge you phone completely
Download stock recovery
Flash stock recovery Code:
fastboot flash recovery endeavoru_recovery_signed.img
Relock bootloader Code:
fastboot oem lock
Run 1.26 RUU
Neo XL said:
Tell me, why should be this way the only way to get the updates? Yesterday i tried it, like its written here and all went okay. The only correction to do is in point 2: fastboot erase cache
http://forum.xda-developers.com/showthread.php?t=1609190
Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
Clear fastboot cache Code:
fastboot clear cache
Boot your phone
Charge you phone completely
Download stock recovery
Flash stock recovery Code:
fastboot flash recovery endeavoru_recovery_signed.img
Relock bootloader Code:
fastboot oem lock
Run 1.26 RUU
Click to expand...
Click to collapse
whats your CID ? and what RUU file did you run ?
i think the rom on the phone must be from the same CID of the RUU, but dont have sure. (only applies to non super CID phones)
That´s right. The CID is inside the device and the RUU has to be the same. But custom roms don´t change the cid, because for this you must have S-Off. At this time the original cid will not be replaced by another. But in the old method all runs well.
I have an o2 device, cid is O2___102, this was never changed by any custom rom.
Neo XL said:
That´s right. The CID is inside the device and the RUU has to be the same. But custom roms don´t change the cid, because for this you must have S-Off. At this time the original cid will not be replaced by another. But in the old method all runs well.
I have an o2 device, cid is O2___102, this was never changed by any custom rom.
Click to expand...
Click to collapse
EXACTLY .... the ARHD 2.1 is base on x.xx.401.xx ?
401 is RUU_ENDEAVOR_U_ICS_40_HTC_Europe
so i dont understand how your method worked for you....
you should use a rom base from a O2-DE O2___102 RUU
because a rom base on on x.xx.401.xx didnt work for me (my CID VODA-UK VODAP001)
Hello, my cid is HTC-India HTC__038, how can i install european 1.29 RUU ?
Thanks!
HI
Firstly thanks for all the effort you put in around the forum, ive read quite a few of your posts.
I notice youve done a custom Vode rom, is there any chance of doing a H3G__001, im on the 3 network and would like to be able to flash the latest H3G rom if i ever want to go stock again, obviously being an unlocked Orange phone it wont let me, or if you arent able too, time concerned and stuff which i understand, could you point me in the direction of where i could find the info needed on whats involved.
Many Thanks.
I already tried to flash rom.zip from
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.7_Radio_1.1204.104.14_release_259284_signed
and
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed
both i got
E: Can't open /sdcard/rom.zip
(bad)
Installation aborted.
Any ideas?
graemeg said:
HI
Firstly thanks for all the effort you put in around the forum, ive read quite a few of your posts.
I notice youve done a custom Vode rom, is there any chance of doing a H3G__001, im on the 3 network and would like to be able to flash the latest H3G rom if i ever want to go stock again, obviously being an unlocked Orange phone it wont let me, or if you arent able too, time concerned and stuff which i understand, could you point me in the direction of where i could find the info needed on whats involved.
Many Thanks.
Click to expand...
Click to collapse
for you is RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9 , i will make it a stock rom. give me 1 or 2 days
brenopoubel said:
I already tried to flash rom.zip from
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.7_Radio_1.1204.104.14_release_259284_signed
and
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed
both i got
E: Can't open /sdcard/rom.zip
(bad)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
since we dont have s-off you cant change your CID to superCID.you have to use the right RUU,
for you is RUU_ENDEAVOR_U_ICS_40_hTC_Asia_India_1.26.720.2 ( i think)
brenopoubel said:
I already tried to flash rom.zip from
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.7_Radio_1.1204.104.14_release_259284_signed
and
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed
both i got
E: Can't open /sdcard/rom.zip
(bad)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You don't flash the ROM.zip from the RUU in CWM - you have to rename it PJ46IMG.zip and flash it from HBOOT
EddyOS said:
You don't flash the ROM.zip from the RUU in CWM - you have to rename it PJ46IMG.zip and flash it from HBOOT
Click to expand...
Click to collapse
flashing on HBOOT on S-ON (without s-off) is possible ?
vladnosferatu said:
for you is RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9 , i will make it a stock rom. give me 1 or 2 days
Click to expand...
Click to collapse
+1 please
for you is RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9 , i will make it a stock rom. give me 1 or 2 days
Thankyou, that is greatly appreciated.
vladnosferatu said:
since we dont have s-off you cant change your CID to superCID.you have to use the right RUU,
for you is RUU_ENDEAVOR_U_ICS_40_hTC_Asia_India_1.26.720.2 ( i think)
Click to expand...
Click to collapse
Well, now i tried to install this RUU hTC_Asia_India_1.26.720.2, the one that worked before with me, but i got ERROR [155]: UNKNOWN ERROR
brenopoubel said:
Well, now i tried to install this RUU hTC_Asia_India_1.26.720.2, the one that worked before with me, but i got ERROR [155]: UNKNOWN ERROR
Click to expand...
Click to collapse
what rom you have now on the phone ? is a custom rom ?
do you have the bootloader unlocked ?
vladnosferatu said:
what rom you have now on the phone ? is a custom rom ?
do you have the bootloader unlocked ?
Click to expand...
Click to collapse
Well, i installed RUU hTC_Asia_India_1.26.720.2, then updated by OTA to 1.28.720.10, then flashed CWM recovery, then flashed root.
Yes, bootloader is unlocked.
PS: adicionei você no gtalk!

LEAKED JELLY BEAN ROM!TEMPORARY FAQ! Read First!

I'm sure many are seeking for the answer on how to flash this rom? Well then head over to question #7 - for a more informative guide follow this link http://forum.xda-developers.com/showthread.php?t=1920060
With the release of these jb roms there is a crap load of questions popping up. A lot of cid questions as well which are being repeated over and over. With this thread i hope to put an end to it.
Any questions that pop up i will try to answer as well as add to this list as time passes by, until eventually we have an ota and things settle in. Feel free to ask questions, if i cant answer, another person will. New questions are added to first page.
Overview
Q1:I want to install the jelly bean rom that has been leaked, how do i do this?
Q2: How do i check what my cid number is?
Q3: If i update my hboot, will i be able to use my previous ics rom?
Q5:Can i change my cid number, is there an alternative route? I MUST HAVE IT!!
Q6: Must the hboot be updated in order to be able to upgrade to jelly bean in future?
Q7: How do i flash the jelly bean roms?
Q8: On which cids to the firmwares work?
Q9: Will future updates make it possible for us to upgrade without updating hboot?
Q10: Should you install the new rom or wait? (This question might seem silly but i've seen people asking)
Q11:How can i check which RUU i need?
Click to expand...
Click to collapse
Q12:Is there actually an easier method to update hboot for us custom users in future releases or are following those steps a must for everybody?
Q13: What kernel# does the leaked Jelly Bean kernel have?
Q1:I want to install the jelly bean rom that has been leaked, how do i do this?
A1: The leaked jelly bean roms need a certain cid, not every cid number works. Either you are lucky enough to have it or not.
It is looking bad for branded phones at the moment
Q2: How do i check what my cid number is?
A2:You can download the so called "cid getter" from the app store. Your cid # should be listed on top. If not.....
Alternatively you can try the following command in fastboot:
Fastboot oem readcid
Q3: If i update my hboot, will i be able to use my previous ics rom?
A3: At the moment there is noway you can downgrade to ics once you have acquired jelly bean
Q4:When will we get an official jelly bean update?
A4: This month.
But when? It could be as soon as next week or as late as end of October.
Q5:Can i change my cid number, is there an alternative route? I MUST HAVE IT!!
A5:No. And no.
Q6: Must the hboot be updated in order to be able to upgrade to jelly bean in future?
A6:So far the answer seems to be leaning more towards a yes then a maybe or no.
Q7: How do i flash the jelly bean roms?
A7: 1. Relock bootloader: - fasboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash a stock ruu and reboot to phone mode (ensure usb debugging is on - Settings/Developer options)
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Thank you ClydeB1 for the steps
Q8: On which cids to the firmwares work?
A8:
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
Q9: Will future updates make it possible for us to upgrade without updating hboot?
A9: It's too early to tell, however, from what i've read this looks like it won't be possible.
Q10: Should you install the new rom or wait? (This question might seem silly but i've seen people asking)
A10: That is up to you. However, i'll list the pros and cons
pros: More fluid, has a bunch of improvement as well as power saver option. Wireless lan as well as radio signal seem to get established much faster.
cons: Limited number of roms, not really much variation. It's a leak, and a leak has bugs - so don't expect it to run at 100%
That also means, no miui, no cm10,ice cold jelly(at least a lot of stuff in the original android development section) close to nothing at the moment. However, if jelly bean satisfies you then i see no reason why you shouldn't update.
Gaming:For the HoX game lovers out there, it's probably safe to say that you should not upgrade just yet. Certain kernels are probably not supported which enhance your gaming experience.
Q11:How can i check which RUU i need?
A11: Open cmd.exe and type "fastboot getvar version-main" without quotes.
Q12:Is there actually an easier method to update hboot for us custom users in future releases or are following those steps a must for everybody?
A12: Nope, at least not for s-on devices. -Mike1986_(ARHD)
Q13: What kernel# does the leaked Jelly Bean kernel have?
A13: 3.1.10
Perhaps add the steps again to flash:
Before you start take a backup of your sd card and ensure that your phone is charged, at least 70% to be safe
1. Relock bootloader: - fastboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash the appropriate stock ruu for your device and then reboot to phone mode (ensure usb debugging is on - Settings/Developer options) (To find which ruu to flash run fastboot getvar version-main, or else you can try the odexed Stock rom + boot.img from Mike's thread)
3. From command prompt enter: - adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip (NB! If this step fails, immediately rerun the cmd and it should work the 2nd time)
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Edit: Updated method for flashing from hboot 1.23 to 1.28
1. Relock bootloader - fasboot oem lock
2. Enter command - fastboot oem rebootRUU
3. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip (NB! If this step fails, immediately rerun the cmd and it should work the 2nd time)
4. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
5. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
6. Flash boot.img from rom zip: - fastboot flash boot boot.img
7. Flash rom zip through recovery
8. Reboot and enjoy
Another question to clarify ..
we must install the RUU after just lock the bootloader , right?
I understand that it is absolutely necessary, as the custom rom in "relocked" did not start, right?
can u list the CID's that are valid in the OP please?
dani_nec said:
Another question to clarify ..
we must install the RUU after just lock the bootloader , right?
I understand that it is absolutely necessary, as the custom rom in "relocked" did not start, right?
Click to expand...
Click to collapse
For some it does appear to reboot, so try that first, if not then you will need to flash a stock ruu.
itismadhan said:
can u list the CID's that are valid in the OP please?
Click to expand...
Click to collapse
Firmware will only flash on the phones with the following CID
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
Perfect.
As we know that RUU corresponds with our CID? I for example, taking the HTC__102 ...
All of these questions is to help more people who may have the same doubts lol
dani_nec said:
Perfect.
As we know that RUU corresponds with our CID? I for example, taking the HTC__102 ...
All of these questions is to help more people who may have the same doubts lol
Click to expand...
Click to collapse
here is a list of cids and regions, maybe that helps...
http://forum.xda-developers.com/showthread.php?t=1195475
robocik said:
here is a list of cids and regions, maybe that helps...
http://forum.xda-developers.com/showthread.php?t=1195475
Click to expand...
Click to collapse
Ok, I know that .. but in the name of the only places RUU asia, europe etc etc. .. CID does not indicate that RUU is for each
understand because in my case, a German HTC__102 the correct RUU would be this:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
correct? CID for all of Europe (not anchored to company phones of course) would be the same RUU
dani_nec said:
Ok, I know that .. but in the name of the only places RUU asia, europe etc etc. .. CID does not indicate that RUU is for each
understand because in my case, a German HTC__102 the correct RUU would be this:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
correct? CID for all of Europe (not anchored to company phones of course) would be the same RUU
Click to expand...
Click to collapse
You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/showthread.php?t=1546970
Works fine though. Did that on mine (HTC_102) no Problem
Higgins12 said:
You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/showthread.php?t=1546970
Works fine though. Did that on mine (HTC_102) no Problem
Click to expand...
Click to collapse
Ok!! Thanks for the info.. I Download in this moment
But, the RUU indicated for my it's correcto?
thanks
dani_nec said:
Ok!! Thanks for the info.. I Download in this moment
But, the RUU indicated for my it's correcto?
thanks
Click to expand...
Click to collapse
In my case the RUU didn't work. Don't know what was the Problem but it always jumped out of the flashing progress (this RUU can't be flashed ... bla bla bla)
dani_nec said:
Ok!! Thanks for the info.. I Download in this moment
But, the RUU indicated for my it's correcto?
thanks
Click to expand...
Click to collapse
Yes, all of those codes that can currently install the JB rom would all use x.xx.401.x ruu
Higgins12 said:
In my case the RUU didn't work. Don't know what was the Problem but it always jumped out of the flashing progress (this RUU can't be flashed ... bla bla bla)
Click to expand...
Click to collapse
If .. I remember with the desire or sensation .. the damn RUU! can not flash RUU for Jupiter is far ... can not flash RUU that the LCD is dirty ... can not flash RUU that you have not eaten breakfast.
I will I have the RUU panic
I also have a question...
Until now I have received all the updates in time. I have a Cid HTC__32 BUT even though I have bought it from a separate store in Romania as an unlocked device, it boots with a vodafone logo and all the updates had Vodafone apps installed...
Am I risking anything here? Mine seems like a branded device but it is sim unlocked and cid as mentioned before.
I am a bit confused honestly. If noone knows for sure I wold rather wait for a more simple and secure road to jb.
Btw. If I didn't unlock the bootloader and didn't root yet, I can skip those first few steps right?
Sent from my HTC One X using xda app-developers app
bedobela said:
I also have a question...
Until now I have received all the updates in time. I have a Cid HTC__32 BUT even though I have bought it from a separate store in Romania as an unlocked device, it boots with a vodafone logo and all the updates had Vodafone apps installed...
Am I risking anything here? Mine seems like a branded device but it is sim unlocked and cid as mentioned before.
I am a bit confused honestly. If noone knows for sure I wold rather wait for a more simple and secure road to jb.
Btw. If I didn't unlock the bootloader and didn't root yet, I can skip those first few steps right?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
As long as your cid matches, you're good to go. Yea, no need to run the first steps as you are already locked and on stock.
ClydeB1 said:
Perhaps add the steps again to flash:
1. Relock bootloader: - fasboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash a stock ruu and reboot to phone mode (ensure usb debugging is on - Settings/Developer options)
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Click to expand...
Click to collapse
Thanks for posting that! I was not 100% sure on how to do it myself since i can't upgrade and didn't bother so far. Good to see that riddle solved.
Higgins12 said:
You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/showthread.php?t=1546970
Works fine though. Did that on mine (HTC_102) no Problem
Click to expand...
Click to collapse
HTC_102?? Thats not on the list of can dos is it? Did it flash?(firmware).
I`ve checked the android-info.txt. HTC_002 isnt in it, it really shouldnt of flashed on that CID!
backfromthestorm said:
HTC_102?? Thats not on the list of can dos is it? Did it flash?(firmware).
Click to expand...
Click to collapse
It is on the list
ClydeB1 said:
It is on the list
Click to expand...
Click to collapse
modelid: PJ4610000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
mainver: 3.09.401.100
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
Directly from Android-info.txt
I repeat - HTC_002 shouldnt of flashed!
backfromthestorm said:
modelid: PJ4610000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
mainver: 3.09.401.100
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
Directly from Android-info.txt
I repeat - HTC_002 shouldnt of flashed!
Click to expand...
Click to collapse
No you asked HTC__102, check your posts

[Q] Standard Recovery for my HTC one X

I am selling my HTC one x and I would like to put the standard recovery.
The rom itself is the stock, the i cannot find the recovery. the old thread which contained the rom has been removed
My CID is E11
fastboot getvar cid
cid: HTC__E11
Fastboot getvar version-main
version-main: 3.20.401.1
Do you happen to have the correct recovery image?
Cheers
https://www.dropbox.com/s/uccu1s8delpo8mn/Stock recovery 3.20.img

Dev Edition CNV

Hi everyone, I have an international HTC M9 with S-Off, unlocked bootloader and Maximus 7.1.0 ROM
I was following the steps by @clsA here --> http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
to convert my phone to the dev edition but I have some questions regarding the requisites:
1. my phone has product: htc_himauhl instead of product: htc_himaulatt
2. my version-main is : x.xx.771.x instead of version-main: x.xx.617.x
for the rest i have changed the cid and mid to the one requested (BS_US002, 0PJA11000) so the question is, can I flash the provided RUU.zip with the sdcard method? even if the version I'm going to get is an older android version (lollipop 5.x)?
EDIT: I've seen that there's also the MM6.x RUU.zip so my only question now is if the product and version-main mismatch isn't a problem
Mat08.cc said:
Hi everyone, I have an international HTC M9 with S-Off, unlocked bootloader and Maximus 7.1.0 ROM
I was following the steps by @clsA here --> http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
to convert my phone to the dev edition but I have some questions regarding the requisites:
1. my phone has product: htc_himauhl instead of product: htc_himaulatt
2. my version-main is : x.xx.771.x instead of version-main: x.xx.617.x
for the rest i have changed the cid and mid to the one requested (BS_US002, 0PJA11000) so the question is, can I flash the provided RUU.zip with the sdcard method? even if the version I'm going to get is an older android version (lollipop 5.x)?
Click to expand...
Click to collapse
Try It but backup all your data.
When you flash the RUU.zip/Rom.zip with fastboot it will warn you and wount flash if you have not all prerequirering stuff Cid / Mid / wrong Version..
I have also convertetd my One M9 International to Nougat Android 7 with the "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" and after that i get the Update via OTA.
But I extracted the Rom.exe from The "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" because i want to flash with fastboot.
When you start the RUU.exe you will get an folder under "C:\Users\##YOURUSERMANE##\AppData\Local\Temp\{0B0B715F-DFF0-448D-819F-C0706246382E}" there you can find the Rom.zip copy it to your fastboot directory and flash it with fastboot.
Befor I had Viper Rom 5.3 on my One M9
At first i have bootet to Download / Bootloader Mode
Than with fastboot: "fastboot oem writemid 0PJA11000" (For Dev Edition)
And Than "fastboot oem writecid BS_US001" (For Dev Edition)
and reboot: "fastboot reboot"
Now I flashed the Ruu / Rom Zip via fastboot
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip (ore Rom.zip original name)
htc_fastboot reboot
After ist is ready you can go to "Settings >Info>SoftwareUpdate" and you will recive the new Nougat Update.
Atention:
After that Update i hav booted to Download mode again and set old cid / mid again.
But i you want stay on Dev Edition an get OTAs you can leav your CID / MID as DEV otherwise you can run in trubble
" fastboot oem writemid 0PJA10000"
and for supercid
"fastboot oem writecid 11111111"
and reboot: "fastboot reboot"
Now hav fun with you dev Phone
niceguy0815 said:
Try It but backup all your data.
When you flash the RUU.zip/Rom.zip with fastboot it will warn you and wount flash if you have not all prerequirering stuff Cid / Mid / wrong Version..
I have also convertetd my One M9 International to Nougat Android 7 with the "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" and after that i get the Update via OTA.
But I extracted the Rom.exe from The "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" because i want to flash with fastboot.
When you start the RUU.exe you will get an folder under "C:\Users\##YOURUSERMANE##\AppData\Local\Temp\{0B0B715F-DFF0-448D-819F-C0706246382E}" there you can find the Rom.zip copy it to your fastboot directory and flash it with fastboot.
Befor I had Viper Rom 5.3 on my One M9
At first i have bootet to Download / Bootloader Mode
Than with fastboot: "fastboot oem writemid 0PJA11000" (For Dev Edition)
And Than "fastboot oem writecid BS_US001" (For Dev Edition)
and reboot: "fastboot reboot"
Now I flashed the Ruu / Rom Zip via fastboot
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip (ore Rom.zip original name)
htc_fastboot reboot
After ist is ready you can go to "Settings >Info>SoftwareUpdate" and you will recive the new Nougat Update.
After that Update i hav booted to Download mode again and set old cid / mid again.
" fastboot oem writemid 0PJA10000"
and for supercid
"fastboot oem writecid 11111111"
and reboot: "fastboot reboot"
Now hav fun with you dev Phone
Click to expand...
Click to collapse
Thank you mate, you've been very clear! Let me ask you one more thing, the dev edition rom has multilanguage? and the red-text warning is gone?
multilanguage yes I use german and the red-text warning is not gone.
niceguy0815 said:
multilanguage yes I use german and the red-text warning is not gone.
Click to expand...
Click to collapse
Thanks man, I successfully upgraded to android 7 your help has been really appreciated! :good:
niceguy0815 said:
After that Update i hav booted to Download mode again and set old cid / mid again.
" fastboot oem writemid 0PJA10000"
and for supercid
"fastboot oem writecid 11111111"
Click to expand...
Click to collapse
That's no good idea. If you changed your sku to the 617 one you should stick to the corresponding MID. Besides the SCID has no benefit on the M9 since it won't make your phone ignore mismatches between the current MID and the MID of RUUs like it did on older HTC phones. It even prevents you from being able to install OTAs. Therefore it might be a better choice to keep the dev edition CID, as well.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That's no good idea. If you changed your sku to the 617 one you should stick to the corresponding MID. Besides the SCID has no benefit on the M9 since it won't make your phone ignore mismatches between the current MID and the MID of RUUs like it did on older HTC phones. It even prevents you from being able to install OTAs. Therefore it might be a better choice to keep the dev edition CID, as well.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Yes you are right!
But for me ..I think there is no OTA in near futer and when came the normal cusom Rom for Nougat I must not remember to get the original CID / MID back again
I can understand that decision. (I'd probably have done the same.)
However I added that warning because you linked those instructions in another thread. Others might run into problems if they do those steps and aren't aware of the "risks" that might follow...
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
I can understand that decision. (I'd probably have done the same.)
However I added that warning because you linked those instructions in another thread. Others might run into problems if they do those steps and aren't aware of the "risks" that might follow...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Hi Flippy498, I'm sorry to bother you but although I have read everything about firmwares, roms, etc (even those in your signature).. I haven't found an answer about the following problem: I want to go back to full stock and remove the red-text warnings so, since I have S-OFF and as I've read on "The Difference between Rom & Firmware" doc there's no problem in going back to an older firmware, I downloaded the 3.35.401.12 - RUU ZIP from SoLdieR9312's thread (http://forum.xda-developers.com/one-m9/development/ota-1-32-401-15-firmware-noredtext-t3072571) and changed MID and CID to those requested. Now before flashing the RUU.zip with the sdcard method my question is, to remove red-text warnings which file I have to flash (3.35.401.12 - Stock Firmware - 3.35.401.12 - Firmware NoRedText - 3.35.401.12 - NoRedText ABOOT only)? and this has to be done before or after flashing RUU.zip?
EDIT: I've also locked the bootloader
If your phone is completely stock then the red text won't appear. So just flash the RUU.
Edit: (I know that this is a stupid question.) You are aware of the fact that the 401 firmware isn't the same as the one your phone got originally delivered with, aren't you? You could've sticked with the dev edition firmware instead of changing to the 401 one. They're in most parts the same. The only difference is that 401 has no android n at the moment.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
If your phone is completely stock then the red text won't appear. So just flash the RUU.
Edit: (I know that this is a stupid question.) You are aware of the fact that the 401 firmware isn't the same as the one your phone got originally delivered with, aren't you? You could've sticked with the dev edition firmware instead of changing to the 401 one. They're in most parts the same. The only difference is that 401 has no android n at the moment.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I'm aware but flashing the dev-edition with the RUU.exe method didn't resolve the red-text issue so I thought that going back to 401 firmware and do all that process could fix that! Now i'm wondering if the ruu.exe method is the problem, i mean if i flash the dev-edition ruu.zip via sdcard it won't fix the redtext warnings anyway right?
I've never used an exe with the M9. I do know that the SD card method resets the modified status whereas I've read that the exe doesn't. So it might be worth a try.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
I've never used an exe with the M9. I do know that the SD card method resets the modified status whereas I've read that the exe doesn't. So it might be worth a try.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
With the 401 ruu.zip it gives me 12 RUU ZIP error I searched it and found Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
So I believe it might be necessary to flash before one of those "firmwares.zip" from SoLdieR9312's thread but it's strange since my phone is S-OFF
If I remember correctly, error 12 indicates that you don't have the correct CID if it appears during a SD card flash.
Edit: Unless it contains "combined" in its name every RUU (no matter whether zip or exe) is signed.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
If I remember correctly, error 12 indicates that you don't have the correct CID if it appears during a SD card flash.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok, tomorrow I'll have a look at all this again.. you've been even too patient with me! thanks alot for your help! :good:
It looks like there is some kind of problem with the RUU.zip file. Coolberry mentioned that in another thread. (I'm assuming you tried to use his file.)
Edit: I know this post is a bit older and written in the section of a different HTC model. However you could still use its instructions to extract the RUU.zip from the RUU.exe by yourself. The rom.zip is what we call RUU.zip nowadays. Please post any questions that may arise in this thread.
Sent from my HTC One S using XDA Labs
Flippy498 said:
It looks like there is some kind of problem with the RUU.zip file. Coolberry mentioned that in another thread. (I'm assuming you tried to use his file.)
Edit: I know this post is a bit older and written in the section of a different HTC model. However you could still use its instructions to extract the RUU.zip from the RUU.exe by yourself. The rom.zip is what we call RUU.zip nowadays. Please post any questions that may arise in this thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So i tried another rom.zip from your collection in a google doc page and got the same error (12_RU). Now i'm going to try with the extraction from ruu.exe, I got the wwe lollipop ruu.exe (the only one i found for wwe) and the dev-edition ruu.exe.. let's see if i can get this to work
p.s. I've noticed that i can't copy the rom.zip file directly to my m9 but i have to put the sd card inside the pc, anyway on the google doc is written that this is common so i don't think that's the problem
Mat08.cc said:
So i tried another rom.zip from your collection in a google doc page and got the same error (12_RU). Now i'm going to try with the extraction from ruu.exe, I got the wwe lollipop ruu.exe (the only one i found for wwe) and the dev-edition ruu.exe.. let's see if i can get this to work
Click to expand...
Click to collapse
What's your current CID and MID? It's wasted time if you try to flash RUUs that aren't compatible with the current setup. Are you still S-OFF? If not then you won't be able to change your CID/MID or to downgrade. The RUU.zip files in my sheet should all be fine. Every one of them has already been used successfully by S-ON users. So there should be no need for extracting a WWE RUU.zip. Only the dev one extracted by coolberry seems to have problems.
Flippy498 said:
What's your current CID and MID? It's wasted time if you try to flash RUUs that aren't compatible with the current setup. Are you still S-OFF? If not then you won't be able to change your CID/MID or to downgrade. The RUU.zip files in my sheet should all be fine. Every one of them has already been used successfully by S-ON users. So there should be no need for extracting a WWE RUU.zip. Only the dev one extracted by coolberry seems to have problems.
Click to expand...
Click to collapse
I'm unlocked and still S-OFF and this is the getvar all result:
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) serialno : ****
(bootloader) imei: ****
(bootloader) version-main: 4.14.617.6
(bootloader) boot-mode: download
(bootloader) version-baseband: ****
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Mat08.cc said:
I'm unlocked and still S-OFF and this is the getvar all result:
[...]
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
Ok. Being S-OFF and unlocked is totally fine. However for the dev RUU you'll need mid: 0PJA11000 and cid: BS_US002. For the WWE one you should use mid: 0PJA10000 and cid: HTC__001 or whatever HTC__xxx CID belongs to your home country. The SCID actually has no real use on the M9 anymore since it doesn't make your phone ignore MID mismatches with RUUs as it did on older HTC models. It even prevents you from being able to install OTAs.

Categories

Resources