Related
So I been trying to upgrade my OS to the tnt 1437, however every time I try my old OS keeps popping up (OS: 5.1.xxx (Build 15671FARIA.3.5)) ... so for the last 3 days I been trying to search this site for any answers, however all I get is that only happens if the CID is locked, but my phone isn't 1) I unlocked it before to upgrade it in the first place to the above mentioned OS and 2) I checked its status with the Wizard Service Tool (which is AWESOME). So i'm at a lose here as to why every time I either upgrade or downgrade the ROM the same OS keeps showing up. BTW Everything else I can upgrade except the OS. Any help is appreciated. thanks!
Anyone? Anything?
Did you remember what version of IPL and SPL when you unlock your Wizard? It is only unlockable when IPL and SPL is 1.xx (i.e. Downgrade to Button's ROM first). You may post your WST log here for more chance to know what the problem is.
Here you go here is the log:
Wizard Service Tool v4.2.1
12/11/07 23:07:22
CPU Manuf. FAILED
MODEL: Wizard
=> Bootloaders:
IPL: 1.01 (G3 device)
Built on Sep 19 2005 at 18:00:32
Copyright (c) 2003 High Tech Computer Corporation
Getting more info...
=> Firmware:
OS: 5.1.xxx (Build 15671FARIA.3.5)
ROM: 3.8
Registry AKU: FARIA.3.5
Radio values FAILED
=>Extended_ROM:
Version: faria V4.0
Name: Extended_ROM
Status: hidden
Getting drives,disks and partitions info...
=> Drives and partitions:
|--Handle--|---Size---|
6e9d5352 - 9.99M (0x9fd800)
eea9813a - 48.23M (0x303c000)
2fb23f92 - 50.95M (0x32f4000)
efb23f3e - 2.94M (0x2f0000)
cfb23fb6 - 3.06M (0x30fc00)
All Done.
Did you flash back to the T-Mobile 2.26 ROM before you tried to flash to another custom ROM?
kegobeer said:
Did you flash back to the T-Mobile 2.26 ROM before you tried to flash to another custom ROM?
Click to expand...
Click to collapse
Yes I tried both the button ROM and the love ROM with no change ... On another note I can change the IPL and the SPL with no trouble however the OS always stays the same.
Not the love or button - the original carrier ROM, either T-Mobile or Cingular.
Have you tried doing a hard reset, and then flash to the T-Mobile ROM from a different computer?
kegobeer said:
Not the love or button - the original carrier ROM, either T-Mobile or Cingular.
Have you tried doing a hard reset, and then flash to the T-Mobile ROM from a different computer?
Click to expand...
Click to collapse
I just tried what you mentioned however I got the following error when I was doing the ROM update .... fyi I got it from the tmobile site ... when I ran the rom update I got:
error [326]: invalid command
this nbf file cannot be used for your pda phone. please check your nbf file.
It looks like you originally skipped the 2.26 rom. I did the same thing the first time I flashed a rom. Try flashing back down to the Button rom, then to the 2.26, then the tnt 1437. It worked for me.
Am I doing something wrong here cause every time I try some downgrade its always the same OS that shows up ... 3.3.0.0 that NEVER changes, everything else does.
i have the same problem..
8125hacker said:
i have the same problem..
Click to expand...
Click to collapse
What OS does your phone boot with?
bad flash rom, you need junk the phone or donate to XDA-developers
first take out the sd card.then flash your phone with buttons 1.0 rom.hardreset. then flash it again with buttons rom. unlock the device totaly with the unlock software. hardreset. flash with original t-mobile us 2.26 rom
halfway above 80% pull the usb plug. the phone get stuck and the update program will tell you it doesnt respond. reset the phone (little hole on the side) you will see the 3 color screen . now restart the 2.26 update and when
you get at the part that it starts looking for the phone connect it. sometimes
it just works , sometimes you need to try a few times.. it wont ruin the phone
as i had this many times due to a crashing computer. wjen its done do a hardreset and install the rom you wanted.
hope this helps you guys
da_jojo said:
first take out the sd card.then flash your phone with buttons 1.0 rom.hardreset. then flash it again with buttons rom. unlock the device totaly with the unlock software. hardreset. flash with original t-mobile us 2.26 rom
halfway above 80% pull the usb plug. the phone get stuck and the update program will tell you it doesnt respond. reset the phone (little hole on the side) you will see the 3 color screen . now restart the 2.26 update and when
you get at the part that it starts looking for the phone connect it. sometimes
it just works , sometimes you need to try a few times.. it wont ruin the phone
as i had this many times due to a crashing computer. wjen its done do a hardreset and install the rom you wanted.
hope this helps you guys
Click to expand...
Click to collapse
Out of curiosity when I downgrade to any of these roms am I looking for the OS to downgrade or just the IPL/SPL?
cgigate said:
bad flash rom, you need junk the phone or donate to XDA-developers
Click to expand...
Click to collapse
how is it a bad flash rom if the IPL/SPL and GSM all change everytime i change roms. The only thing that doesn't is the OS.
Hello everyone,
i'm trying to update my universal(T-mobile MDA Pro version) to WM6. I've tried every guide I found here, read the whole wiki and googled hours and hours for error 222. No solution...
I'm stuck at the first step when I'm installing Button 1.05 ROM. Every time I run it I get error 222 (Device is not responding).
The phone was already SIM unlocked when I got it and bootloader ver. says 1.01. SIM and memory cards are not in the phone.
I've provided more info below. Also tried with few difrent cables on difrent computers... Always error 222.
I would very much appreciate every help you can provide...
Thx
------------------------------------------
Some info from WST
Wizard Service Tool v4.2.2
05/09/08 15:58:23
CPU Manuf. FAILED
IMEI:
=> Bootloaders:
IPL: (G3 device)
SPL date unknown
=> Firmware:
OS: 5.1.xxx (Build 14847.2.0.0)
ROM: 0.0
Registry AKU: .2.0.0
Radio values FAILED
=>Extended_ROM:
Version: UNLOCKED
Name: Extended_ROM
Status: visible
=> Drives and partitions:
|--Handle--|---Size---|
33ef0c1a - 1.89G (0x79120e00)
d3d6540a - 9.99M (0x9fd800)
33e2010e - 44.43M (0x2c6dc00)
f3e71212 - 56.75M (0x38c0000)
13e71026 - 3.19M (0x330000)
f3e71002 - 3.06M (0x30fc00)
=> DOC chip unique ID:
0000000084180102153903ee0e0605d0
Key Index: 26
All Done.
------------------------------------------------
Info from Device Information:
ROM version: 1.30.115 WWE
ROM date: 4.17.06
Radio version:1.10.03
Protocol version 42.44.P8
ExtROM version: UNLOCKED
-----------------------------------------------
No ideas?
I have yet another question. Since this is a T-mobile, after a hard reset it installs a bunch of custom programs. Is there a way to stop it from doing this? Clear out ext rom?
EDIT : Don't bother. Maneged to solve it.
d3v123 said:
No ideas?
I have yet another question. Since this is a T-mobile, after a hard reset it installs a bunch of custom programs. Is there a way to stop it from doing this? Clear out ext rom?
EDIT : Don't bother. Maneged to solve it.
Click to expand...
Click to collapse
Use an extended rom unlocker first and then hard reset. After that you will have access to the extended rom. Delete whatever and agian hard reset...
For your first problem try to unlock your phone completely.
thx 4 second...
As for first, that's what I'm trying... I can't CID unlock it with WST (it says that my DOC chip is locked). In various wiki guides i'm suppoused to flash the button 1.05 rom first, but i can't do it because of error 222.
I've found this link with some tools to unlock the device. Which tool should I use to CID unlock it?
In topic about tomal's new memory card flashing there was a suggestion to CID unlock with this. I thought it was only for SIM unlocking. Can I use it to CID unlock as well?
At the moment I have:
Android 2.3.3 on O2
Software Number: 1.19.206.2
Kernel Version: 2.6.35.10-g8db500e
Baseband Version: 47.14.35.3030H_7.47.35.17
got a stock rom which is:
Software Number: 1.13.401.1
Baseband Version: 47.14.35.3030_7.47.35.17
So radio does seem to be the same.. I am using the downgrade method but cant get it to work..
when I boot with volume down and power button, it loads the PH60IMG.zip (blue bar) and then goes to the checks PH60IMG.zip (golden bar) and then it turns back to the bootloader start screen and nothing happens..
please share your experiences, Im sure Im going somewhere wrong..
please advise guys...
Do you have S=Off? If not, it will be not possible.
Try to do S=Off by XTClip, then put ROM using RUU file.
Hello
Im new in this forum, and i dont speak english. Sorry for that.
Anyway i Have
Device: HTC 7 Mozart
Firmware: 2250.21.51101.401
OS Version: 7.10.7740.16
Bootloader: 5.11.2250.1
My question is "can i downgrade with this slspl"
Code:
http://forum.xda-developers.com/showthread.php?t=1196183
boneszbo said:
Hello
Im new in this forum, and i dont speak english. Sorry for that.
Anyway i Have
Device: HTC 7 Mozart
Firmware: 2250.21.51101.401
OS Version: 7.10.7740.16
Bootloader: 5.11.2250.1
My question is "can i downgrade with this slspl"
Code:
http://forum.xda-developers.com/showthread.php?t=1196183
Click to expand...
Click to collapse
Hi,
It is designed for the bootloader that you have!!
After flashing you can
- flash any signed 401 ROM you like or
- flash an RSPL/HSPL and then flash any custom ROM
Regards, ansar
Are you sure?
I Have SPL 5.11.xxxx not 5.10.xxxx
I dont want, broken my phone
If this is a true u can edit your topic, becouse name may mislead.
problem with downgrade
hy,
got realy big problem,got a htc 7 mozart with original t-mobile branding,debranded with eu version,chevron didnt worked so i updated over zune till mango 40,tought actual windowbreak would fix my jailbreak problem,but **** happens, windowbreak isnt for htc yet,so i testet chevron again,no luck,now i recovered over zune back to start for testing chevron again,but no luck too,so i would flash again with some other firmwares, cause wlan connection has problems too with actual firm.The main Problem now:I cannot flash any other firm, think its the bootloader now,your flash doesnt work too, whats now,this device is killing me.My Omnia 7 didnt make such problems.
Actual Information bout phone:
os:7.0.7389.0
firm:2250.09.13001.401
hard:0004
fhardsw:5.71.09.02a_22.51.50.21U
fhard:A.102.0.D4
Boot:5.11.2250.1(133487)
chip:2.2.5.0
Please Help me
boneszbo said:
Are you sure?
I Have SPL 5.11.xxxx not 5.10.xxxx
I dont want, broken my phone
If this is a true u can edit your topic, becouse name may mislead.
Click to expand...
Click to collapse
Hi,
You simply do not know what you are talking about
Regards, ansar
Okey anasar. Good news is flashing is completed.
Telephone reboot and i see SPL-1.28.2250.3.
In this moment i run DFT_RSPL_WP7FG2_LAUNCH and Complited, but telephone dont rebootet and my SPL is still 1.28.2250.3 not RSPL. I try again but this same result.
What can i do it now?
SCREEN #1 SPL - i746.photobucket.com/albums/xx109/boneszbo/20111230067.jpg
SCREEN #2 Load OS (In left top i see text BLDR 1.28.2250 MODEN N/A) - i746.photobucket.com/albums/xx109/boneszbo/20111230069.jpg
OS Normal Load NoDo
HTC 7 Mozart
OS Version: 7.0.7004.0
Firmware: 2250.09.12803.113
Bootloader: 1.28.2250.3
Chip SOC: 2.2.5.0
Please tell me how can i downgrade bootloader to 1.10, maybe now that work, but i noob and i dont now how
EDIT:
i Update this ROM
Code:
http://forum.xda-developers.com/showthread.php?t=858599
After RSL/HSPL Install succesfull. Thank You ansar you are the best man !!
If i have money i donate you to great work. But now is New Year and need money.
boneszbo said:
Okey anasar. Good news is flashing is completed.
Telephone reboot and i see SPL-1.28.2250.3.
In this moment i run DFT_RSPL_WP7FG2_LAUNCH and Complited, but telephone dont rebootet and my SPL is still 1.28.2250.3 not RSPL. I try again but this same result.
What can i do it now?
SCREEN #1 SPL - i746.photobucket.com/albums/xx109/boneszbo/20111230067.jpg
SCREEN #2 Load OS (In left top i see text BLDR 1.28.2250 MODEN N/A) - i746.photobucket.com/albums/xx109/boneszbo/20111230069.jpg
OS Normal Load NoDo
HTC 7 Mozart
OS Version: 7.0.7004.0
Firmware: 2250.09.12803.113
Bootloader: 1.28.2250.3
Chip SOC: 2.2.5.0
Please tell me how can i downgrade bootloader to 1.10, maybe now that work, but i noob and i dont now how
EDIT:
i Update this ROM
Code:
http://forum.xda-developers.com/showthread.php?t=858599
After RSL/HSPL Install succesfull. Thank You ansar you are the best man !!
If i have money i donate you to great work. But now is New Year and need money.
Click to expand...
Click to collapse
Hi,
Enjoy your brand bew device!!
regards, ansar
problem with jailbreak
hello i try to jailbreak and as i see there is nothing for me yet
OS version:7.10.7740.16
Firmware revision number:2250.21.51101.111
Hardware revision number:0004
Radio software version:5.71.09.02a.22.51.50.21U
Radio hardware version: A.102.0.D4
Bootloader version:5.11.2250.1(133065)
Chip SOC version: 2.2.5.0
for jilbreak htc hd7
hi all
i have a hd7 spl 5.11.2250 and try to downgrade and jilbreak but not lucky
so i need help. any body can help me???????????????????
hd7 problem
Hello all!
I have a problem.
I want to unlock my hd7 phone^
Code:
OS Version: 7,10,8107,79
Firmware Version: 2250,21,51101,401
Nome version of the equipment: 0002
Software version: a_22 5,71,09,02, 51,50,21 U
Hardware version: A, 102,0, D4
boot version: 5,11,2250,0 (134,578)
Version of the chip SOC: 2,2,5,0
And in my hd7 16 gb memory.Is this europe region or asian?Thanks!If that europe region, may i unlock by ansar rom's http://forum.xda-developers.com/showthread.php?t=1196183
Thanks!!!
Phone not recognized by ROMUpdateUtility.exe
hi ansar.
i'm a really noob and i've no idea how to downgrade my htc hd7.
well, i know that you solved this problem, but i cannot downgrade my phone using your method.
what i do:
1.close zune and all other applications on pc
2.turn my phone off
3.go to the tricolor Bootloader screen
4.run ROMUpdateUtility.exe and follow instructions
the problem is, that when i start ROMUpdateUtility.exe , it just can't recognize my phone.
below the sign Image Version is nothing and below Select from below is nothing except the button Update
information about the phone:
htc hd7 T9292
OS version: 7.10.7740.16
Firmware revision number: 2250.21.51004.401
Hardware revision number: 0002
Radio software version: 5.71.09.02a_22.51.50.21U
Bootloader version: 5.10.2250.0(132968)
i really hope you can tell me what am i doing wrong.
pleease help me.
thanks ahead, maxxes
Please Help me to install RSPL/HSPL on my htc 7 mozart
I am not able to install Rspl to my phone.
After follow all steps in ( DFT_RSPL_WP7FG1_LAUNCH ) it says successfully change Spl to Rspl but there's all same.
and not change to Rspl.
Please Guide my.
PHONE INFORMATION :
Name: HTC 7 Mozart
Model: HTC 7 Mozart
Software: Windows Phone 7
Total Storage: 7.20 GB
Available Storage: 5.58 GB
OS Version: 7.0.7004.0
Firmware revision number: 2250.09.12210.061
Hardware revision number: 0004
Radio software version: 5.50.09.18_22.24.50.09U
Radio hardware version: A.102.0.D4
Bootloader version:1.22.2250.10(110809)40
Chip SOC version: 2.2.5.0
MAC address: F8-DB-7F-86-89-79
SIM ID: 89910704910009427355
INFORMATION DISPLAYED when switching on the phone with volume down button :
IN RED _________
PD67*** MFG SS-BC (4K)
SPL-1.22.2250.10(110809)
MicroP(LED) 0X07
TOUCH C1(v69)
IN GREEN_________
SD SANDISK 7580MB CLASS0
Partition Info-v211v413
IN BLUE______________
IN WHITE_____________
Serial
RUU on the HTC One XL Evita
All work is by other people who posted the original info. I take no credit for their work. It would take another complete post to thank those responsible for providing the information below.
I cannot be held responsible if you try any of these procedures, and your phone becomes inoperable or otherwise damaged. Read thoroughly before performing these actions to your phone. Know the risks, and understand what you are doing before trying anything.
I put this post together because I noticed that folks on our forum ask these questions multiple times on a daily basis. I don’t know how some of our more experienced users bounce around all day to answer them. I also noticed there is no one place to find all the info below. I had to dig through many threads for hours to get this together. This is a work in progress and will change as new info and better methods arrive. If you find a better way to do this or outdated information, please let me know and I will update. Thanks
Definitions:
RUU – Rom Update Utility. It is a Windows based exe file that contains a complete operating system including a stock recovery, bootloader (Hboot), and radio (Baseband.) This program is run to bring the phone back to a stock state while the phone is in bootloader mode.
OTA – Over the air update. It is an update package used to update a stock operating system. It is not a complete operating system and contains only parts that are getting an update . You can’t install an OTA on a modified device, only stock.
Bootloader (Hboot) – The Bootloader or Hboot, is like BIOS to windows. It is the first thing that runs when you boot up your Android device. It packages the instructions to boot the operating system kernel and most are specifically designed to run their own debugging or modification environment. Basically, an Android device is like a hard drive that has several partitions, which holds the Android system file in one and all the app data in another. For all these partitions, Bootloader (or Hboot) serves as a security checkpoint that is responsible for checking and initializing the hardware and starting software. There's a common misconception that can you just change the hboot but that isn't the case, you need the full firmware that comes with the RUU.
Bootloader mode / Fastboot mode – One and the same. This is the environment where you can flash a custom recovery (the stock recovery has very little options), flash Roms, etc. To enter Bootloader mode, power down the phone and then hold the power key and the volume down key at the same time until the phone enters bootloader mode. If your computer is not connected you will see “Fastboot” highlighted in red. If your computer is connected you will see “Fastboot USB” highlighted in red. This still does not mean that your computer can communicate with the phone. More on that later.
Firmware – The image version i.e. 3.18.502.6, 2.20.502.7 etc. The firmware contains the Hboot so don’t confuse the Firmware version number with the Hboot version number or Baseband version number. You can check this out in more detail while looking at the RUUs available and it will make more sense. Each software version is connected with the CID (Carrier ID) and MID (Model ID) of your device. That means you can't use whichever version you want, unless you have S-OFF on your device. Each ROM Update Utility.exe package will check your device details (bootloader version, MID and CID) before starting the update process.
Baseband (Radio) - The baseband (radio) is completely separate from the ROM, it's stored in an entirely different partition. Don’t confuse this with Hboot or Firmware.
Click to expand...
Click to collapse
Important info:
Note: This guide may or may not apply for the UTL middle eastern variant. I think the jury is still out on that. If anyone has additional info it would be a big help for many of our users.
S-On – If you are S-On then you must pay particular attention to the RUU you choose to install. If you have obtained SuperCID then you need to gain S-Off in order to run a RUU. You WILL brick your phone. Remember this, S-On + SuperCID + 3.18 RUU = Brick. Make sure your CID is not 11111111, 22222222, or any other variant of SuperCID. If so, it’s time to S-Off. I recommend the following links:
http://forum.xda-developers.com/showthread.php?t=2540232
or
http://forum.xda-developers.com/showthread.php?t=2155071
But if you wish to remain S-On and currently have a stock CID (verified) then you can run the appropriate RUU while in bootloader mode. If your bootloader is unlocked then you must relock it prior to RUU. You must use an RUU that matches your CID and carrier. You can use the same version that is installed on your phone or a higher version (again that matches your CID and carrier.) This is normally done to fix issues, upgrade a stock phone manually, or start over with a fresh install.
S-Off – If you are S-Off you may choose several versions of RUU. It is recommended that you choose 3.18 which comes with the 2.14 Hboot. If you want to run a Sense based Rom you may experience data and wifi issues and are further recommended to upgrade your Hboot to 2.15:
http://forum.xda-developers.com/showthread.php?t=2517148&highlight=ruu
If you plan to use an AOSP Rom (4.3 and higher) then the 3.18 RUU is a requirement. You do not need to upgrade your Hboot to 2.15 to use an AOSP Rom.
Click to expand...
Click to collapse
Steps for running the RUU:
1. Download the RUU file you need. It will be an exe file (remember what I said above about S-On and S-Off.)
http://forum.xda-developers.com/showthread.php?p=37227608 or
http://androidruu.com/?developer=Evita
2. Backup all your files you wish to keep and make a backup of the phone in recovery (if you have a custom recovery.) When I run the RUU on my phone, it doesn't erase the files on my internal storage (SD Card partition) but I still back it up just in case. I recommend you make a back up too.
3. Install the most current HTC drivers.
http://www.htc.com/www/software/htc-sync-manager/?section=Requirement
It is recommended that you install HTC sync to get the drivers and then uninstall HTC sync but keep the drivers if you are having connection issues. If you have windows 8+ then you may encounter connection issues known to exist with the new windows. If possible, use a Windows 7 computer.
4. Install Fastboot and ADB drivers. I’m including some links to help you understand what this is and how to use them if you don’t know.
http://forum.xda-developers.com/showthread.php?t=2277112
http://forum.xda-developers.com/showthread.php?p=42407269
http://forum.xda-developers.com/showthread.php?t=1754018
5. Make sure you charge the phone. I recommend 100% (leave no room for doubt.)
6. Place the phone in bootloader mode by powering down and the holding the power key and volume down key at the same time until the phone boots into bootloader.
7. Connect the phone to the computer.
8. If you are matching your current Firmware you need to type the following in a CMD prompt: “Fastboot getvar all” and check your firmware. If you are S-On and you have 3.18 you can’t downgrade. You must stay at 3.18. If you are on a lower version than 3.18 then you can go higher.
9. Make sure no other programs are running, make sure screen saver/hibernation is turned off.
10. Run the RUU exe file and follow the prompts. Be patient, There will be times when it appears to be doing nothing but it is still working.
11. After it finishes, (it usually takes 15 to 20 minutes) if you are stock, reboot into system. If you are modified, you will need to reflash a custom recovery, custom Kernel, Radio, etc.
Click to expand...
Click to collapse
I’m hoping this guide helps those who don't understand the RUU process. I know I learned a lot putting this guide together. Using a RUU was a concept I had to read a lot about and search around quite a bit to understand. I personally ran these instructions several times with the 3.18 RUU and everything went fine.
Special thanks goes to Timmaa. He must type the acronym RUU about 100 times a day helping people and many tidbits of info in this guide were taken from the advice he gives. I'm hoping I can save his keyboard/touch screen from wearing out!
Some Error codes and explanations pulled from internet:
ERROR [110]: FILE OPEN ERROR
This error message indicates that the RUU lacks some specific files or they are damaged, so the RUU cannot continue with the update. You have to get the complete RUU package and try again.
ERROR [120]: MAIN BATTERY POWER
This error message will appear when the Android phone’s battery power is not sufficient (Batter power should be more than 30%). Although RUU will instruct you to plug in the AC adapter, it will still need to make sure that your Android phone has enough power to complete the update. (The Android phone cannot charge the battery when it is connected to the PC while installing the RUU).
ERROR [130]: MODEL ID ERROR
ERROR [131]: CUSTOMER ID ERROR
One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
ERROR [170]: USB CONNECTION ERROR
This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone.
Click to expand...
Click to collapse
Every HTC update has the following numbering structure:
a.bb.ccc.d
a - the first number of the software. Normally it doesn't increase very often, but when it does, it usually means newer Android version.
bb - this number is also a software number. Increasing bb number means some more or less major update based on the same Android version, but sometimes it might even bring newer version of the HTC Sense.
ccc (also cc or cccc) - this is the number of the region/carrier. It has nothing to do with the software itself being newer or older. More details below.
d (sometimes dd) - the third part of the software version (the fourth one in the RUU name). Usually indicates some minor update with some hot fixes.
Click to expand...
Click to collapse
Example: 3.18.502.6
So basically, when you are interested in the software version, you should look at a.bb.d (3.18.ccc.6) because ccc (502) means only the region/carrier variant of the software.
Here is a list of possible RUU variants:
a.bb.61.d - Orange UK (United Kingdom)
a.bb.65.d - Orange CH (Switzerland)
a.bb.69.d - Orange PL (Poland)
a.bb.73.d - Orange FR (France)
a.bb.75.d - Orange ES (Spain)
a.bb.110.d - T-Mobile UK (United Kingdom)
a.bb.111.d - T-Mobile DE (Germany)
a.bb.112.d - T-Mobile AT (Austria)
a.bb.113.d - T-Mobile CZ (Czech Republic)
a.bb.118.d - T-Mobile PL (Poland)
a.bb.161.d - Vodafone UK (United Kingdom)
a.bb.163.d - Vodafone FR (France)
a.bb.165.d - Vodafone IT (Italy)
a.bb.166.d - Vodafone CH-DE (Switzerland - Germany)
a.bb.168.d - Vodafone GR (Greece)
a.bb.169.d - Vodafone AT (Austria)
a.bb.206.d - O2 UK (United Kingdom)
a.bb.207.d - O2 DE (Germany)
a.bb.401.d - World Wide English (WWE)
a.bb.415.d - Arabic (UAE/Middle East)
a.bb.468.d - Turkey
a.bb.497.d - Morocco
a.bb.498.d - WWE Brightpoint US (United States)
a.bb.502.d - Cingular US (United States)
a.bb.518.d - Movistar (Venezuela)
a.bb.531.d - T-Mobile US (United States)
a.bb.631.d - Rogers Canada (WWE)
a.bb.651.d - Sprint US (United States)
a.bb.661.d - Telus WWE (Canada)
a.bb.666.d - Bell Canada
a.bb.707.d - Asia (WWE)
a.bb.708.d - Asia HK (Hong Kong)
a.bb.709.d - Asia TW (Taiwan)
a.bb.720.d - Asia (India)
a.bb.728.d - Virgin AU (Australia)
a.bb.751.d - Chunghwa Telecom (Taiwan)
a.bb.771.d - Hutchison 3G UK (United Kingdom)
a.bb.777.d - ?
a.bb.841.d - Telsra WWE (World Wide English)
a.bb.862.d - Voda-Hutch AU (Australia)
a.bb.901.d - TIM IT (Italy)
a.bb.911.d - SK Telecom (South Korea)
a.bb.980.d - Optus AU (Australia)
a.bb.999.d - HTC Test RUU
a.bb.1400.d - China
a.bb.1401.d - ?
a.bb.1403.d - HTC China CMCC (China Mobile Communications Corporation)
a.bb.1540.d - HTC One U.S. Developer Edition
a.bb.1600.d - ?
a.bb.1700.d - HTC One Google Edition
Click to expand...
Click to collapse
The list is quite long, and there are still some some missing. If you know more variants, please let me know in the comments section.
The 401 and the 707 devices are usually the first ones that HTC prepare updates for. Carrier branded software is usually months after the WWE updates.
(Originally posted by Mike1986 on the Android Revolution Blog. The RUU software numbering system is universal for all HTC devices)
Well done! I've PM'd you a few recommendations for slight alterations but it's looking really good.
Sent from my Evita.
timmaaa said:
Well done! I've PM'd you a few recommendations for slight alterations but it's looking really good.
Sent from my Evita.
Click to expand...
Click to collapse
Thanks Timmaa, there's no way I could have put this together without your help.
timmaaa said:
Well done! I've PM'd you a few recommendations for slight alterations but it's looking really good.
Sent from my Evita.
Click to expand...
Click to collapse
Believe it or not a healthy portion of the guide came straight from your posts. I rephrased when appropriate to combat outright plagiarism! I feel obliged at this time to put you in the credits somewhere because I just nicked another tidbit about Hboot changes from one of your recent posts. lol
Lol, thanks. I wouldn't really call it plagiarism though, it's just the way it's done so there aren't many different ways you can say it.
Sent from my One X using XDA Premium 4 mobile app
thank you for this
i have a UTL evita - J15- middle east version
i have s-off ... and i want to install astock rom
tell me if i have to had a super cid or not to install any ruu ??
I wouldn't install any RUU from the standard Evita onto your device. The last person who installed standard firmware onto the middle eastern Evita bricked his phone.
Sent from my One X using XDA Premium 4 mobile app
timmaaa said:
I wouldn't install any RUU from the standard Evita onto your device. The last person who installed standard firmware onto the middle eastern Evita bricked his phone.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thank you my firend
i already had a nand backup
but i want the stock recovery and i can not get it
can u help me >??
Many people have been looking for the stock recovery but nobody has found a copy yet.
Sent from my Evita
Added some error codes and explanations
Added software version info
Added some additional information, cleaned up a few instructions to make them more understandable, and need to make something clear:
This is written for the HTC ONE XL EVITA!
It states that in the title. Most of the information is applicable to multiple HTC phones but I only focused on this model. Thanks
The AT&T 5.18.502.1 RUU has been released. Download link:
http://www.htc.com/us/support/htc-one-x-att/news/
It is android 4.2.2 Sense 5 and includes the 2.18 Hboot and 1.35a.32.45.27_10.144.32.34a Baseband (Radio).
At this time the exploits that worked with 2.20 and 3.18 do not work with 5.18.
It's recommended you be bootloader unlocked and S-Off or you will be stuck with this upgrade until exploits come out.
Current root methods do not work either.
I Want to update my htc one x at&t Using 5.18.502.1 RUU ,But when i run RUU ,it's shows me error message: ERROR[120]:LOW MAIN BATTERY POWER ,but my battery is fully charged.can anybode help me ?
P.S Operating system Windows 7 Ultimate, Bootloader Locked, S-ON .
Recently updated my htc one s to jb via ota update , but nw want original ics back
Have researchd n got d correct ruu
But i dont know hw to install d ruu.
I took the risk by just connecting phone in debugging mode as instructed wen i ran d ruu file. But wen phone got off during the process n big htc logo appeared , the process showed error that device hs been disconnected. But thank god nthng bad happnd, i rebooted the device n its unchanged.
Plz help me to install d ruu
I knw abt rooting but havnt rooted my phone yet. I wnt it untempered.
Sent from my HTC One S using xda app-developers app
aviotron said:
Recently updated my htc one s to jb via ota update , but nw want original ics back
Have researchd n got d correct ruu
But i dont know hw to install d ruu.
I took the risk by just connecting phone in debugging mode as instructed wen i ran d ruu file. But wen phone got off during the process n big htc logo appeared , the process showed error that device hs been disconnected. But thank god nthng bad happnd, i rebooted the device n its unchanged.
Plz help me to install d ruu
I knw abt rooting but havnt rooted my phone yet. I wnt it untempered.
Click to expand...
Click to collapse
This forum section is specific to the One X (EVITA) and you should go to the One S forum for the best and most accurate information for your device. Advice given by One X users might not be completely accurate for your device, and may even harm (brick) it.
What I can tell you, if you are trying to downgrade JB to ICS (sounds like you are) that is only possible with s-off, or otherwise hacking the version number. Otherwise, RUU will fail version check (what you are installing has to be equal or greater than what is currently installed) and not complete.
backups said:
I Want to update my htc one x at&t Using 5.18.502.1 RUU ,But when i run RUU ,it's shows me error message: ERROR[120]:LOW MAIN BATTERY POWER ,but my battery is fully charged.can anybode help me ?
P.S Operating system Windows 7 Ultimate, Bootloader Locked, S-ON .
Click to expand...
Click to collapse
The only successful installs for the 5.18.502.1 RUU have been reported S-Off, SuperCID and Bootloader unlocked.
Here is the thread with the duscussion:
http://forum.xda-developers.com/showthread.php?t=2628920
backups said:
I Want to update my htc one x at&t Using 5.18.502.1 RUU ,But when i run RUU ,it's shows me error message: ERROR[120]:LOW MAIN BATTERY POWER ,but my battery is fully charged.can anybode help me ?
P.S Operating system Windows 7 Ultimate, Bootloader Locked, S-ON .
Click to expand...
Click to collapse
Please see post #14 above. This RUU is only for the HTC One XL Evita.