[ROM]RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15 _22.23.50.09U, by ansar - Trophy Windows Phone 7 Development

Dear forum members,
In the following A, B, C and D sections is described the flashing process
of the Non NoDo unbranded ROM: RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15_22.23.50.09U_by_ansar
This is an 7004 based platform ROM and can used for chevron unlock
It supports the following keybord languages:
English (United States), French (Canada), French (France), French (Switzwrland)
German (Germany), Italian (Italy) and Spanish (Spain - International)
A. Pre-Requisites
If your Tropy 7 is flashed with the ROM of the following release:
1. RUU_Spark_Vodafone_NZ_1.07.179.04_Radio_5.50.09.15_22.23.50.09U
then you can flash the following Non NoDo unbranded ROM and when you like you can comeback to your previous ROM
In case your Tropy 7 is flashed with a different of the above 1 ROM but your Firmware version at your phone settings>about>more information
is of the form xxxx.yy.zzzzz.179 i.e. with characteristic value 179
then you can also flash the following NoDo unbranded ROM, but you can comeback only to one of the above 1 ROM
B. Downloading
You must download the following 2 ROMs:
1. Download this zip ROM file: RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15_22.23.50.09U_by_ansar
2. Download this zip ROM file: RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15_22.23.50.09U_Signed_by_ansar
Extract the downloaded zip ROM files with an unzip / 7zip utility in separate folders of your choice
C. Flashing Process
In order to successfully flash the provided ROMs you must follow these steps:
1. Flash the ROM of the above (B.1.) extracted zip ROM file
2. After flashing Tropy 7 will automatically enter again in bootloader mode
3. In the screen of your computer the ROMUpdateUtility will report an ERROR[270]
4. Ignore it and exit from ROMUpdateUtility
5. Now flash the ROM of the above (B.2.) extracted zip ROM file
6. After flashing your Tropy 7 will boot normally
7. Exit from ROMUpdateUtility and proceed with your brand new ROM
If you do not want them you can delete all operator apps, in order to have more free RAM
Beware, in WP7 deleting an application means it is deleted from ROM
D. ROM Flashing Instructions
In order to flash a ROM follow these steps:
1. Press and hold power-on/off button to power-off the phone
2. Press and hold volume-down button and then press power-on/off button to enter bootloader mode
3. When your phone enters the tricolor screen bootloader mode, release volume-down button
4. Connect your phone to your windows 7/vista/xp pc/laptop with a usb cable
5. Verify that your phone will be identified and relevant drivers will be installed by windows os of your pc/laptop
6. After completion of (D.5.) above, check the usb message connection on your phone screen
7. To flash the ROM go to your pc/laptop folder where the downloaded zip ROM file is extracted
8. Double click on the ROMUpdateUtility.exe file and strictly follow the instructions on your pc/laptop screen
Till next version enjoy!!!
Regards, ansar

There seems to be a bug with this. No USB connectivity and under about handset, Hardware Revision is : NA
My previous hardware revision was 0003.
Can you please fix this one up.
Thanks

wickedpenguin said:
There seems to be a bug with this. No USB connectivity and under about handset, Hardware Revision is : NA
My previous hardware revision was 0003.
Can you please fix this one up.
Thanks
Click to expand...
Click to collapse
Wait... so it broke your phone?

owenw said:
Wait... so it broke your phone?
Click to expand...
Click to collapse
You still have USB connectivity in Boot loader Mode.. But otherwise USB not recognized by computer.
I don't recommend anyone use this, unless you like bricks.
Hopefully he fixes this shortly.

wickedpenguin said:
You still have USB connectivity in Boot loader Mode.. But otherwise USB not recognized by computer.
I don't recommend anyone use this, unless you like bricks.
Hopefully he fixes this shortly.
Click to expand...
Click to collapse
Hi,
The provided ROM:
RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15_22.23.50.09U_by_ansar
is proved ok for other operators
In order to comeback, just flash from bootloader mode the branded ROM:
RUU_Spark_Vodafone_NZ_1.07.179.04_Radio_5.50.09.15_22.23.50.09U_by_ansar
As many times said before some operators are not yet approved for official zune update to NoDo
This is also admitted afterwards by simonwilkins, that not caused by bootloaders, as in his previous cloudy imagination
Also operators that were shelling phones with not approved ROMs, were afterwards reloaded newer ROMs to their customer phones
In any case a new ROM:
RUU_Spark_Vodafone_NZ_1.08.161.02_Radio_5.50.09.15_22.23.50.09U_by_ansar
will be provided and the:
RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15_22.23.50.09U_by_ansar
will be investigated for NZ operator cause it is proved ok for MangoB2 update in other operators
Regards, ansar

In order to comeback, just flash from bootloader mode the branded ROM:
RUU_Spark_Vodafone_NZ_1.07.179.04_Radio_5.50.09.15_22.23.50.09U_by_ansar
I realize this, but this still leaves me in the same situation which is stuck on 7008
As many times said before some operators are not yet approved for official zune update to NoDo
Consider my hadnset was already on 7392 through Zune before I flashed your rom this proves that 7392 is approved by my carrier.
This is also admitted afterwards by simonwilkins, that not caused by bootloaders, as in his previous cloudy imagination
Actually Simon's FIX was to flash another ROM, which wasn't created by yourself.
Also operators that were shelling phones with not approved ROMs, were afterwards reloaded newer ROMs to their customer phones
I'm unsure where you go this information from.
RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15_22.23.50.09U_by_ansar
will be investigated for NZ operator cause it is proved ok for MangoB2 update in other operators
Any timeframe on this?

wickedpenguin said:
RUU_Spark_Vodafone_NZ_1.09.707.07_Radio_5.50.09.15_22.23.50.09U_by_ansar
will be investigated for NZ operator cause it is proved ok for MangoB2 update in other operators
Any timeframe on this?
Click to expand...
Click to collapse
Any update on this Ansar, many of us are awaiting a fix, or a functional ROM.

Related

Need help how to reflashing my MDAc from WWE to GER.*thx*

I bough my MDAc some days ago and the first I read was the bad accoustic ... but some Google searches told me that there´ll be a firmware update from T-Mobile with the Cebit2005 also having a link for the download section. Cause there was nothing to download I decided to use the firmware beeing offered here. I did the following:
1.) Downloading a actual MDAc firmware (WWE version)
2.) Downloading the country-free hacked MaUpgradeUt.exe
3.) Flashing the device
Everything worked fine but cause my device had an english (WWE) menu I decided to find out how to solv this language problem and found the thread "How to upgrade with the latest I-mate Jam ROM --GUIDE--" (http://forum.xda-developers.com/viewtopic.php?t=14973). I understood the process but I still wasn´t able to upgrade cause of the following reason:
1.) I downloaded the new firmeware as WWE version
2.) I went through the hacking process
3.) I tried to flash the MDAc with this firmware
RESULT: The "MaUpgradeUt.exe" told me that the firmware isn´t made for my device (country error)
So I decided to use the hacked MaUpgradeUt.exe which worked but brought me anohter problem. When I startet this file it analysed my device and (normally!) listed me the actual and the new firmware version ... but these fields left empty. When I proceeded the next window told me that I successfully flashed my device ... but the device never received any data during this one second from on to the final window.
So ... flashing with the original MaUpgradeUt.exe is impossible while trying to change the language from WWE to GER ... and the hacked MaUpgradeUt.exe has a problem flashing the device.
Does anyone has an idea how to solve this mess and/or another idea how to change the language later and/or is there a application which offers this (i.e. any mobile phone does it)?

[DFT Freedom ROM] Spark mango 7720 V2 version

[DFT Freedom ROM] Spark mango 7720 V2 version
Updates:
20 Langs in one rom USA_ENG_FRA_ITA_GER_ESN_NLD_DAN_FIN_NOR_SVE_PTB_ PTG_RUS_ELL_HUN_CSY_PLK_JPN_KOR
Replace RUU_Spark_S_HTC_Europe_5.10.401.06_5.69.09_RELEASE new driver
Replace some of the new HTC XAP (from Titan ROM or Radar ROM or Market )
Open Internet sharing
Fully unlock with IE download XAP , can be immediately downloaded and install it , see picture under
XAP unlimited installation, dozens of XAP than can be installed, I installed more than 30 XAP which download from the market, fixed market XAP update/install issue from DFT Freedom 7720 version.
ROM built-in HTC Deck , Tango, TouchXplorer, Registry Editor, in the pass XAP only can be installed via computer, DFT developed DFTInstall.exe so now all the XAP can be build-into custom ROM , of course need to see will be over the size of 512, this tool is strictly prohibited any theft, unauthorized use exception.
Important Note
1. Before doing anything, make sure you have more than 50% battery!
2. You must have RSPL / HSPL installed on your device, download RSPL / HSPL see this http://www.darkforcesteam.com.cn ... & extra = page% 3D1
3. Supported Operating Systems: Windows XP, Windows Vista, Windows 7.
Disclaimer
This product is free of charge, at your own risk. We do not have any conflict, fault, or damage caused by the process of responsibility. Implied or otherwise, if you agree that any use of the product warranty. Did not find the problem, several different devices simultaneously to test this product, your experience may vary.
Products used for commercial purposes is strictly prohibited, and prohibited xda.cn & wpxap forum and reproduced with the use of intellectual ROM
For the protection of the DFT our official website and XDA - developers.com, it is not allowed within 5 days reproduced in this ROM, the column name well-known owners of this forum the forum three days after the group can reproduced without the application after five days free reproduced, reprinted, be sure to indicate the DFT produced the original post and add links
# Strongly prohibit any use made of the DFT ROM resources,
20 language versions download here
Code:
Password: 11/08/[email protected]
Dark Forces Team Special thanks to TouchXplorer & Registry Editor author Julien Schapman allows us to these two software built into ROM.
Official DFT site (Chinese)
DarkForcesTeam Nov,2011
http://www.youtube.com/watch?v=KyTniK4AXUE&feature=channel_video_title
sorry wrong password won't work
DOWNLOADING
Thanks so much!!!
Edit: Used it today and very happy with it...
Wifi hotspot is working great, using it right now with my laptop
Can't open the zip.
says wrong password!! lol
The password starts with a "space"
lol thanks dude it worked
Upgraded directly from the V1 ROM. Very happy with it, thanks for all your hard work!
My bootloader version is 4.6.2250.0(129185)... How can I get my phone to the state which is compatible with RSPL/HSPL? I'm tired of watching everybody else enjoy themselves.
Sent from my 7 Trophy using XDA Windows Phone 7 App
Flash the original release of the Stock ROM that applies to your phone, it's in the Trophy section posted by Angsar. It will be named for your phones provider (ie in NZ its VodafoneNZ even if bought from 3rd party store).
That will set your bootloader to basic, then flash the HSPL thing and then flash up to V2. RSPL will not work for the ROM, you will need HSPL for it to work properly.
Nice! Been looking forward to this release for "ages" Damn good work, thank you so much for your effords!
EDIT: Is it only me or does Advanced Configuration Tool v.1.4.0.0 not work with this ROM? It opens, but closes/crashes a short while after?
EDIT 2: Figured it out. You have to activate Flight Mode before launching Advanced Config app. If you've got the phone hooked up with your PC, then unplug it first or else the phone uses the Ethernet Internet connection via Zune.
Everything works like a charm now
This rom works perfectly! Tnx!
CruciasNZ said:
Flash the original release of the Stock ROM that applies to your phone, it's in the Trophy section posted by Angsar. It will be named for your phones provider (ie in NZ its VodafoneNZ even if bought from 3rd party store).
That will set your bootloader to basic, then flash the HSPL thing and then flash up to V2. RSPL will not work for the ROM, you will need HSPL for it to work properly.
Click to expand...
Click to collapse
I have to figure out which Vodafone ROM I have, I suspect ELL, but I have UK location settings after every hard reset.
Nice work DFT team, i have a problem since ever, i cannot send MMS or receive it, i installed the HTC connection app, but i cannot receive/send MMS! Anyone can help me on this problem please??
Thanks
I have a HTC Trophy whith Mango and I would like to change to install the DFT.
If I want to go back to Nodo which Rom should I use? I think is Unbranded but I turned on the logo appears A1.
Version OS: 7.10.7720.68
Number revision firmware: 2250.21.40600.177
Number revision hardware. 0003
Version software radio: 5.69.09.05a_22.50.50.21U
Version hardware radio: A.102.0.D4
Version bootloader: 4.6.2250.0(129185)
Version SOC: 2.2.5.0
In bootloader:
PC40100 SS-BC (4K)
SPL-4.6.2250.0(129185) MNG
MicroP(LED) 0x09
TUOCH A1(v10,20)
SD SANDISK 7580MB
Partition Info-v211v413
Please Help me..
emaf83 said:
I have a HTC Trophy whith Mango and I would like to change to install the DFT.
If I want to go back to Nodo which Rom should I use? I think is Unbranded but I turned on the logo appears A1.
Version OS: 7.10.7720.68
Number revision firmware: 2250.21.40600.177
Number revision hardware. 0003
Version software radio: 5.69.09.05a_22.50.50.21U
Version hardware radio: A.102.0.D4
Version bootloader: 4.6.2250.0(129185)
Version SOC: 2.2.5.0
In bootloader:
PC40100 SS-BC (4K)
SPL-4.6.2250.0(129185) MNG
MicroP(LED) 0x09
TUOCH A1(v10,20)
SD SANDISK 7580MB
Partition Info-v211v413
Please Help me..
Click to expand...
Click to collapse
Posted by: teniente_dan
go to this thread
http://forum.xda-developers.com/showthread.php?t=924333
download and flash your correpondient version of the rom (it depends on the operator brand)
every rom on that topic has a inferior spl version so if you flash it, it will downgrade the spl version and you will be able to do the rspl/hspl process
regards
cooldfuzion said:
Posted by: teniente_dan
go to this thread
http://forum.xda-developers.com/showthread.php?t=924333
download and flash your correpondient version of the rom (it depends on the operator brand)
every rom on that topic has a inferior spl version so if you flash it, it will downgrade the spl version and you will be able to do the rspl/hspl process
regards
Click to expand...
Click to collapse
Thanks a lot...
I'll try tomorrow, armed with patience
Any love for CDMA Spark_W (AKA the Verizon Wireless HTC Trophy world phone CDMA/GSM) yet?
We want to play too !!!
The download links are down!
I don't understand how to downgrade the SPL ...

Running a Rom Update Utility (RUU) on the HTC One XL Evita

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.

Flashing unbranded ROM

I reently became a happy owner of black XZP and i love it but there is one thing that irritates me, it came with Orange branded software. My question is, can i flash original unbranded software (when flashtool will provide this option) without loosing IMEI,DRM keys, bravia engine and such ? And where can i find this kind of software ?
Also i heard from SONY centre Poland, that even if i do this myself somehow, it will return to the branded software with next software update as the software is tied to phones IMEI...
Would be gratefull for some extended explanation on this. Thanks.
Probably not since it probably locked to the Orange. You will need to get the network unlock code first before flashing a generic firmware.
Well I know that the XZ Premiums in Australia aren't locked, my friend got one from Telstra and then uses an Optus SIM in it.
Flashing generic FW won't cause you to lose DRM keys, etc, since only unlocking the bootloader will cause that stuff to be affected.
Also, even if the phone is network locked, I don't see why generic FW would affect that - That should only impact what carrier SIM you can use on the phone.
I used newflasher to flash customized UK version on my Vodafone branded version a couple of days ago, and received update for customized UK version this morning, updated ok, no probs.
Renesco said:
I reently became a happy owner of black XZP and i love it but there is one thing that irritates me, it came with Orange branded software. My question is, can i flash original unbranded software (when flashtool will provide this option) without loosing IMEI,DRM keys, bravia engine and such ? And where can i find this kind of software ?
Also i heard from SONY centre Poland, that even if i do this myself somehow, it will return to the branded software with next software update as the software is tied to phones IMEI...
Would be gratefull for some extended explanation on this. Thanks.
Click to expand...
Click to collapse
I got a happy owner too, yesterday :highfive: , Wanted to flash EU firmware but flashtool is not working, found newflasher thread but have no idea how to use it, anybody point me to the instructions? Also it would be great if somebody give me a link for download, found this https://forum.xda-developers.com/cr...ewflasher-xperia-command-line-t3619426/page33 but booth files contain malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/
pawnstar said:
I got a happy owner too, yesterday :highfive: , Wanted to flash EU firmware but flashtool is not working, found newflasher thread but have no idea how to use it, anybody point me to the instructions? Also it would be great if somebody give me a link for download, found this https://forum.xda-developers.com/cr...ewflasher-xperia-command-line-t3619426/page33 but booth files contain malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/
Click to expand...
Click to collapse
I flashed mine two days ago on Windows 10 v1607.
I used the "old" version linked in the other thread. It is right that virus total show that there is some malware but only 2 of 64 AV product say that, I think that is a false positive.
First download your firmware with XperiFirm, pay attention on device version (single or dual sim)
Download Sony companion app and try to make a software repair (until it ask you to shutdown the phone and connect it with volume down button pressed), it will download and install Sony official flash driver (needed for flash the firmware with newflasher).
After that abort Sony software repair and download newflasher.
Go to the firmware folder extract partition.zip (this will allow new flasher to flash partition layout)
Also move away from the folder sim-lock.ta for security purpose (new flasher should have a check but bug can exist)
Copy newflasher.exe to the firmware folder
Shutdown the phone, press volume down button and plug-in the usb cable (Same instruction of Sony companion app), you should see windows driver configuration.
Wait driver configuration to finish and then run newflasher.exe as administrator
Wait until it finish (some system files flash can take minutes to flash don't worry) and check if there are errors in log.
Had problems with yellow triangle in driver but after using companion software per your instruction drivers got installed and everything went ok, flashed central eu version 1 and I'm happy now Many thanks!
Trout777 said:
I used newflasher to flash customized UK version on my Vodafone branded version a couple of days ago, and received update for customized UK version this morning, updated ok, no probs.
Click to expand...
Click to collapse
im on three and want to flash to uk customised ?
got sorted guys well pleased

SM-A716U1 5G Firmware For US Models

I Present The Galaxy A71_5G Guide for Flashing Unlocked Firmware.
Here are some useful reminders:
All download links are at the bottom of this post.
Make sure you follow the "Prerequisites For Anything You decide To Do In This Guide" section.
Don't copy quotation marks, unless I tell you to in this guide.
You will need a Windows computer in order to utilize the software provided.
This is an A71_5G guide, not an A71_5GUW guide.
WARNING: Anything you do in this guide will erase your phone completely. It's recommended that you back up before you do anything and that you remove your google account from your phone (so you don't have to go through FRP).
Disclaimer:
I am NOT responsible for any damage done to your device if you decide to use this guide.
Prerequisites for anything you decide to do in this guide (Required):
Standard Odin
Samsung Drivers
Steps:
1) Uninstall Samsung Switch and/or Samsung Kies, if present on your computer. This helps removes any conflicts with Odin.
2) Extract the Samsung Driver zip and the Odin zip to somewhere safe on your computer.
3) Double click on the extracted "SAMSUNG_USB_Driver_for_Mobile_Phones" executable (SAMSUNG_USB_Driver_for_Mobile_Phones.exe) and complete the installation wizard.
3) Navigate to your extracted Odin folder and double click on the Odin3 v3.14.1_3B_PatcheD.exe.
All About Bootloaders (Required Reading):
As Wikipedia puts it, “A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests.” In other words, a bootloader is what loads you operating system. In most Samsung phones (including the S8 and S8+), there’s an e-fuse that prevents downgrading of the bootloader. This means any firmware or firmware update containing a lower Bootloader version than the one you have, will FAIL to be applied. There is really no way to circumvent this.
I’ll be explaining how to properly identify your current Bootloader version.
How to identify Bootloader version:
Steps:
1) Open “Settings” on your phone.
2) Scroll down to “About Phone”.
3a) If you are on a standard, carrier firmware, under “Baseband version” you should see something similar to this: “G950UXXXXXXXX”.
3b) If you are on an unlocked firmware, under “Baseband version” you should see something similar to this: “G950U1XXXXXXXX”.
4) No matter which firmware you're on, the fourth “X” would be either a “1” or a “2”, which means you will have either Bootloader version 1 or Bootloader version 2, respectively.
Note: As stated in the last section attempting to flash firmware that contains Bootloader v1 onto a phone that already has Bootloader v2, will fail. You can update a phone on Bootloader v1 to a firmware that has Bootloader v2, however.
Flashing Unlocked Firmware:
NOTE: The unlocked firmware does NOT unlock your phone for use on other carriers, it only removes bloatware. Some carrier specific features, such as Wi-Fi Calling and VOLTE will not work with the Unlocked Firmware.
Prerequisites: What's listed in the "Prerequisites for anything you decide to do in this guide" section
Odin3 v3.14.1_3B_PatcheD.exe.zip
Unlocked Firmware from site listed below.
Steps:
1) Extract the Odin3 v3.14.1_3B_PatcheD.exe and the Unlocked Firmware you downloaded from below.
2) Turn off your A71_5G.
3) Once off, hold the Power button while holding the Volume Down button, and the Volume Up button until you feel a vibration then let go of the power button.
4) Press the Volume Up key to enter Download Mode.
5) On your PC, navigate to your extracted Odin3 v3.14.1_3B_PatcheD.exe folder.
6) Double click on the "Odin3 v3.14.1_3B_PatcheD.exe" executable.
7) Connect your phone to your PC with your USB cable.
8) You should see Odin3 v3.14.1_3B_PatcheD output "Added!!" in the "Log" tab and underneath the "ID:COM" section, you should see an empty box turn blue.
9) Now it's time to add your firmware files that were extracted earlier. Individually add an appropriate firmware file for each box on the right. The "BL" box will require a firmware file that starts with "BL", the "AP" box will require a firmware file that starts with "AP", the "CP" box will require a firmware file that starts with "CP", and the "CSC" box will require a firmware file that starts with "CSC" (DO NOT USE THE "HOME_CSC" file for the "CSC" box).
10) Go to the "Options" tab and make sure that only the "Auto Reboot" and "F. Reset Time" checkboxes are ticked.
11) Go back to the "Log" tab.
12) Click the "Start" button on bottom right.
13) Sit back and relax for a while. Odin will output what is being flashed in the "Log" and on a box in the top left.
14) The box in the top left will become green and in black letters say "PASS" once the flash was successful.
15) Once the flash finished, disconnect your phone from your computer.
16) Your phone will do an erase at this point, so don't mess with your phone until you reach the setup screen.
17) Continue with the setup on your phone and enjoy!
DOWNLOADS:
Standard Odin/Patched Odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Samsung Drivers: http://developer.samsung.com/galaxy/...er-for-windows
Google Platform-Tools (ADB): https://developer.android.com/studio/releases/platform-tools
Unlocked Firmware (Bootloader v1): https://samfw.com/firmware/SM-A716U1/XAA
CREDITS
Credit goes to each respective site/developer for the tools required to complete this.
If you would like to be added to the credits and are one of the developers or owners of the tools used please feel free to Private Messege Me!!!
This Will Be Updated To The Latest Firmware When The U1 Varient Gets Updates
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
cubano2031 said:
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
Click to expand...
Click to collapse
you should be able to find it using sammobile.com or frija https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
andrewNY said:
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
Click to expand...
Click to collapse
5G works just fine. pretty much everything works minus the chat features in samsung messages.
---------- Post added at 11:03 PM ---------- Previous post was at 10:49 PM ----------
SmileyMorgue said:
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
Click to expand...
Click to collapse
That's great to hear! I look forward to the patch. Yes, from the digging I did, chat features were not included in the XAA version, but they were working when I was using TMB before switching.
Update to ATH3 Available on phone still a U1 Bootloader.
For those that wish to download full firmware here is the link to it https://samfw.com/firmware/SM-A716U1/XAA/A716U1UEU1ATH3
allenjthomsen said:
Update to ATH3 Available on phone still a U1 Bootloader.
Click to expand...
Click to collapse
Wow, build date was only 2 weeks prior to release. Recently came from a Moto Z4 where we were lucky to have 6 month old security updates.
Unfortunately still can't get the chat feature working; maybe it'll take some time to register the update.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
If its like previous Samsung phones, you'll need to be on the carrier specific firmware to run the unlock. Once unlocked you can flash back to the unbranded/unlocked firmware.
Anyone tired these firmwares with AT&T
so there is no unlocked version firmware for bootloader V2 right now?
Is anyone else able to access the firmware file on the link? It mentions something about the download under construction.
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
No unlock needed
foamhead said:
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
Click to expand...
Click to collapse
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Rwmega said:
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Click to expand...
Click to collapse
Thanks for the reply. I added another APN. Your right cant delete the defaults ones. Im with sprint was trying to do the ,dun to get my hotspot to work. I have it on 3 other phones.
I have a Sprint version.
If I flash the T-Mobile software will it open up all of the T mobile bands?
It could already have them, but have not been able to find specific s on the bands on the sprint version of the phone to see.
Phone looks to be manufactured before the merger?
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
I haven't sim unlocked the phone yet since it's not paid off so couldn't tell u if I can still access that feature.

Categories

Resources