Related
Hi!
I asked this question first on another board, but XDA-Dev is for me the best board when it come to hard question.
So here's the problem : I think I messed up my device while trying to flash it with a french rom.
I edited the rom and swaped the headers with Hexedit from the english roms to the french roms in :
RadioFS.nbf
RadioOS.nbf
CEOS.nbf
EXTROM.nbf
But here's the problem... while flashing the device, the RadioOS is stuck at 0.1%.
If I remove the RadioOS.nbf & RadioFS.nbf from the hpRUU.ini then it flash the unit, and everything is ok except that I cannot active the Radio (cell phone), it lookup the device.
Here's what I see from the Asset Viewer:
Radio Present : Yes
Radio Firmware Version :
Radio Protocol Stack Version :
Radio Bootloader Version :
Radio File System Version :
Default Radio GDFS Version :
I've tried to reflash the device with bigrom, but no luck, it just flash CEOS.nbf & EXTROM.nbf.
Finally, if I try to flash de device from windows with the ROM12132Beta (with activesync disabled) I get an Error 514 message : device failed verification. So I hacked the rom to get it to flash (with hexedit I replaced the 3 letter language with blank space) but it get stuck at 1.0%.
So do you know if there's is a way to force the flashing of the RadioOS.nbf & RadioFS.nbf? (maybe directly from the SD card?)
Thank you very much in advance!!
Please anybody has a little idea?
Because since this is a US device and I'm in Canada I'm not covered by the warranty, so I'm really screwed. I understand this is an HP device, but it is manufactured by HTC and I'm sure that if there's a place where there's people that know well the HTC devices, it's here.
I have the same problem. I'm going to use a sd card to reflash my HW6515. Did u solve the problem?
Not really... I sent it back for repair...
Not really great because this mean I'm 2 months without my PDA
You can also check this thread at BuzzDev :
http://buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=28&id=23221#23221
Fuzy said :
PS.
When flashing sometime the process stop at1%. I hard reset and started flashing again. Finally after repeated trials, flashing was successefully. So, try to insist.
fuzy
Click to expand...
Click to collapse
I have AT&T Treo. Can someone please answer this:-
* I tried to SIM unlock using the 3 step procedure. It did get unlocked BUT the 2nd step failed and 3rd also. Which means that I am now with DOWNGRADED radio. Since I am unable to go to steps 2 & 3 I am not able to rewrite the original backed p radio.
* The phone did not work in London on any network properly, no GPRS and frequent Voce call problems.
* Can someone please provide a new radio or the better one (not the hermes one) from the original ROM
* I can't upgrade to WM6 it says some unsupported device, help
* If I flash the official wm5 on it (if it does) will it become locked again/
OLIPRO why don't you help TRO guys. You are always after HTC !!!!
Read this thread about flashing your ROM/ROW - particularly ppg. 2-3
tmknight said:
Read this thread about flashing your ROM/ROW - particularly ppg. 2-3
Click to expand...
Click to collapse
i tried this but it says unsupported device update
Extract the ROM image from the updater of your choosing and flash using the SD card method. If you need assistance with this, let me know.
alber786 said:
I have AT&T Treo. Can someone please answer this:-
* I tried to SIM unlock using the 3 step procedure. It did get unlocked BUT the 2nd step failed and 3rd also. Which means that I am now with DOWNGRADED radio. Since I am unable to go to steps 2 & 3 I am not able to rewrite the original backed p radio.
* The phone did not work in London on any network properly, no GPRS and frequent Voce call problems.
* Can someone please provide a new radio or the better one (not the hermes one) from the original ROM
* I can't upgrade to WM6 it says some unsupported device, help
* If I flash the official wm5 on it (if it does) will it become locked again/
OLIPRO why don't you help TRO guys. You are always after HTC !!!!
Click to expand...
Click to collapse
WM6 to Wm5, where is the shipped generic WM5 ROM???
summiter said:
Extract the ROM image from the updater of your choosing and flash using the SD card method. If you need assistance with this, let me know.
Click to expand...
Click to collapse
Dear Sumitter, thanks a lot for being so helpful. I have some queries:-
* I have branded treo 750,i unlocked it using the SPL method but could never complete steps 2 and 3, the result was stuck with old radio. I then updated the radio (not the hermes one).So I am on unlocked official wm5 with standard radio.
* When I ran generic wm6, it says unsupported device, what to do?
* I have an unbranded (not done manually,i bought it like that from a store,its from palm) and upgraded it to WM6 by using the generic WM6 release from palm, I want to have the original wm5 generic ROM which was on my device, where can I get that and was it possible to download it from device before the upgrade? Where can I get the shipped generic WM5 ROM for the generic treo and will it be possible to downgrade it?
Please tell me, thanks a lot
Hi Everybody,
First of all let me thank in advance any help and expertise provided.
So the problem i need to solve is the following. I have the S200 (bought in germany, so it's the O2 XDA NEO), and as soon as i bought it, as it was in german, i managed to flash it with a rom in English (1.5 years ago)
Now, i tried to flash it with a Touch rom (don't remember which. PDA VIET? maybe) and it didn't work and now i'm stuck at the bootload with the current message:
IPL 2.20.0001
SPL 2.20
I've tried several roms and some (apparently) flash but then get back to this bootload screen, others don't flash at all.
Anyone can help me then solving this? I'd like to install one of the Touch roms, if not possible just bring it back to life with any WM5 roms...
Thanks in advance again
Cheers
L
Search for an official WM5 ROM like from o2 or Qtek! Connect your Neo via USB to your PC and start the update process! That#s all to bring your device back to live!
Thanks for the quick reply, but i tried this already but it doesn't work as well. I did somehing to the SPL (i was doing it a bit blindfolded as i'm quite newbie in this) and i think that's why i cannot flash anything anymore, not sure.
Is it normal to have SPL 2.20 (no other digitis after the 20)?
ANd to bring it back to life, do i have to install one of the original roms? can't i simply install the Touch versions?
Thanks again
Cheers
Try a really official WM5 ROM, like from o2 Germany! And when I correctly understand which Touch ROM you mean, it can't be used to recover your Phone!
Ok, tried as suggested but got
error 296
This NBF file cannot be used for you PDA phone. Please newer NBF file
Suggestions?
Thanks in advance
Hmm, also tried with RUU_Prophet_220739_2207119_021921_QTEK_GER_Ship_NO_IPL_SPL.exe
from List of Available Original Shipped ROM Versions, and got Error [300]. This Update Utility cannot be used of your PDA. Get Newer Update utility.
Also tried with this one
RUU_Prophet_220739_2207119_024721_QTEK_GER_Ship.exe
From the same place,
Error [294] Invalid Vendor ID
Help?
find for o2 neo rom, from o2, thats the only way, coz in bootloader u cant bypass CID, so go for google.. or PM me...i willl give u the link!!
or go on the following link.. there is a rar file with no vendor ID.. use that.. u will have ur phone back...
ftp://xda:[email protected]/Uploads/Prophet/Prophet-roms/Original-Shipped-ROMs/
malhaar said:
or go on the following link.. there is a rar file with no vendor ID.. use that.. u will have ur phone back...
ftp://xda:[email protected]/Uploads/Prophet/Prophet-roms/Original-Shipped-ROMs/
Click to expand...
Click to collapse
thank you for your reply, i tried from that link several roms including this one RUU_Prophet_215738_2157127_023021_QTEK_FRE_Ship_NoVendorID.rar
No vendor ID. This was the only one that started the flashing process, but stopped at 80% with the error [326] This nbf cannot be used for your PDA phone. Please check your nbf file...
Anyone, tips?
How to proceed. Thanks in advance for the help provided.
Try PDA Viet Step 1
Try PDA Viet Step 1 Temp
hi
my htc prophet got into boot mode too and wondering how to recover it ...does this method I mean full charge with an original charger work for anyone ....can you please what you got by this exiting experiment .
regards
Try this.
If that fails post again but be more specific e.g. what did you do before this happened?
Having the same problem too, try to flash many rom on my 818 pro, but once the process done, it stucks on boot loader screen
can anyone solve this problem? i have the same
but i can install (flash)rom after flash end and prophet restart it stuk on bootloader plz help me
Try and flash the QTEK NVID WM5 AKU2.2 ROM. I'll find a link soon, but I think there's a copy on skyn3ts FTP.
Try this: ftp://xda:[email protected]/Roms...'s/RUU_Prophet_220734_2207114_024721_NVID.exe
hi the link dosent work pls help us
more info
i have t-com tc 500 wich before i want to upgrade it ,has prophet touch rom version7
sorry i can use the link
downloading
saied 1 said:
hi the link dosent work pls help us
more info
i have t-com tc 500 wich before i want to upgrade it ,has prophet touch rom version7
Click to expand...
Click to collapse
That means it is unlocked. Try the ROM I linked earlier just to get the device usable.
hi thanks for yor fast reply but i download the rom that you link and run it in 80 percent of flashing the new rom i have wait few minutes and in device the process bar become red after afew minutes it goes blue(green) and continue but again in 95 percent get red and after minutes i recive the eror that tell : ERROR [320~328] : INVALID COMMAND please chek your nbf file idont know what should i do
and i found this on read me file that comes with rom you linked above
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
my bouth spl and ipl is 2.58.0001
please help me
2.58.0001
Click to expand...
Click to collapse
Never seen that before...
Here is my question I have an HTC 7 PRO (aka HTC ARRIVE,HTC GOLD) the model is HTC USCCHTC-PC93100 I have a student unlock but I need a full unlock. I am new to rom flashing on windows phones im used to jailbreaking and rooting android and ios. I was looking at try to flash this rom http://forum.xda-developers.com/showthread.php?t=1499981 to my phone what I want to know is is it possible to flash this to my model of HTC and if I do flash it will it will I have to take my phone back to US cellular to have them reprogram the phone to their network or will it work just like normal after flashing any adive would help thanks.
Do you have a GOLD (also known as the 7 Pro) or a GOLD_C (also known as the Arrive)? The GOLD is a GSM phone, and won't work on Sprint or any other CDMA carrier. The Arrive is a CDMA phone and won't work on T-Mobile or any other GSM carrier. Flashing the ROM won't help here, either - this is a hardware issue (literally, the radios are different, plus GSM phones have SIM card slots and CDMA phones usually don't). Do *not* attempt to flash a GOLD_C ROM to a GOLD or vice-versa; it'll probably fail but if it doesn't you may make the phone unusable and unrecoverable short of using a JTAG connection.
However, if you want to flash a GSM ROM to a GSM phone, or a CDMA ROM to a CDMA phone, go ahead. However, that won't remove the SIM-lock if there is one. The odds are, if the phone can't be activated with your preferred carrier right now, re-flashing the ROM won't help.
US Cellular says its a 7 PRO but model says 93100 which is the arrive it doesn't have a sim slot so it is a CDMA and DFTs XSPL Tool says its a GOLD_C it has spl version 4.1.230513.1 I have tried the spl downgrade tool but it fails at 4 percent and says invalid vendor ID but if I did manage to flash it would if have to be reprogramed by us cellular to work again since its CDMA and not a sim card
I ran a system information tool and it reports the phone as the HTC arrive so I'm not sure why us cellular markets the phone as the 7 pro but it is definitely the HTC arrive gold_c with a sol of 4.3
Try to flash the older version of your US cellular radio (download from the website in this link http://forum.xda-developers.com/showthread.php?t=1427907)
And then try to flash it, using the directions listed here
http://forum.xda-developers.com/showthread.php?t=1295068
In other words, you want to downgrade your SPL with just a radio flash (task 00). It is not necessary to flash the whole ROM. (Or you can do a hard reset - no big deal, as you will loose all your stuff anyway if you do flash a new ROM)
Then, you can go ahead and try to change RSPL and flash the ROM to see if it works. If not, not big deal, can always flash back your stock rom (also avail on above web site)
I have managed to downgrade my htc arrive us cellular spl and I used the xspl tool to install rspl and hspl now is it possible for me to flash this rom image: http://forum.xda-developers.com/showthread.php?t=1499981
the only thing is the rom image says gold_c_sprint and my carrier is us cellular will I be able to flash this and use the phone like normally or will I have to take the phone back to us cellular after flashing and have them set the phone back up with there network
I have managed to flash my phone with the rom I posted and it still works but all branding on the phone is now sprint is there any way to get the branding back to US Cellular via reg edit for warranty purposes I have went into
HKLM\System\Platform\DeviceTargetingInfo\ and changed mobile operator to USC-US which is US cellular
I also changed the MODeviceName into USCCHTC-PC93100 which was the original name of the device. but im not sure if there's anything else that need to be changed and I cant figure out how to get the marketplace back to the us cellular marketplace they had apps that were only available when it was set up with us cell
I would be careful of changing things in DeviceTargetingInfo; poke the wrong setting and your Marketplace (and all apps installed from it) can stop working or your phone may receive an update that damages it due to an incompatibility with a prior update from a different MO or something.
There is a "Marketplace Config" app available that allows you to select the OEM and MO marketplaces. On a GSM phone, the MO marketplace is usually automatically switched depending on the SIM card (this switch may take a day or two).
Another option would be to start with the US Cellular ROM, and customize it with full-unlock and any other changes you want. This is not my area, though; I have no real experience with creating custom ROMs but there are entire sections of this forum devoted to the topic.
that might be what I have to do is just make a custom us cellular rom Ill look for a section in the fourm to see what I can find on how to make a custom rom
please give me link for us cellular raido
I have htc 7 pro aka htc arrive gold c mobile which is us cellular and I have spl 4.1
I have dft tools to install hspl but I can't find raido to downgrade spl. I googled so many sites but all those raido links for htc hd7. only in this thread mentioned about us cellular radio but the link was expired.please post the new link. thank you
sorry for my bad english
Finally......
Ramesh006 said:
I have htc 7 pro aka htc arrive gold c mobile which is us cellular and I have spl 4.1
I have dft tools to install hspl but I can't find raido to downgrade spl. I googled so many sites but all those raido links for htc hd7. only in this thread mentioned about us cellular radio but the link was expired.please post the new link. thank you
sorry for my bad english
Click to expand...
Click to collapse
Yahooo! i have found my radio. just googled htc 7 pro shipped rom.
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.