I just bought a brand new HTC One M9. Unfortunately, it's an AT&T model, and I can't update the firmware because I live in the UK. It is running stock AT&T android 5.1, current firmware version is 2.11.502.18. I have S-OFF. I downloaded this RUU: RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Ra dio_01.01_U11440261_56.02.50306G_2_F_release_42934 0_signed_2_4.exe from this site: http://www.androidruu.com/?developer=M9
My worry is that, if I flash the RUU, I will be downgrading. Will this be a problem? Is there a more later version of a WWE RUU available elsewhere? Also, I want to remain being S-OFF, so will flashing an RUU return the device to S-ON, or is that only manually possible?
First you need to change cid and mid(not sure what mid you have) to europe.
If you want to flash this ruu you need to flash first a firmware only zip to downgrade your firmware to 1.xx.401.xx, then you can flash this ruu.
Isn't any problem in downgrading, you can update it via ota or just find a newer ruu.
Flashing ruu's will not change your device back to s-on.
S-off is permanent.
If you want to convert the phone:
The phone needs to be plugged in to a power source ALL OF THE TIME while you do this. Make sure your phone is gsm (I think it is).
Root it,
Phone into download mode and plug into a pc.
Use htc_fastboot.exe to change the cid to HTC_001 and the mid to 0PJA10000.
Get the same version official firmware in a ZIP file but from the uk unlocked, for example x.xx.401.xxx where "x" would match YOUR CURRENT firmware on the phone NOW. 401 is the euro wwe region, which is what you want.
*You won't lose your data but you DO lose root. Unlocked bootloader and s-off do not matter.
Rename the firmware.zip file to 0PJAIMG.ZIP and copy it to an EXTERNAL SDCARD and put the SDCARD into the phone.
Boot the phone into download mode and you will see a prompt at the bottom of the screen to "press vol up to flash". Press vol up.
After about 10 mins and a few reboots with the black htc logo etc.., the phone should be sat at the lockscreen waiting for you. It is now a euro wwe on 5.1. You can now go to settings/about/software updates/ and hit "check now".
Download and install all the of the ota updates as they come until no more are left. You will now have a euro wwe at 7.0.
Easy peasy...
Related
Debranded my handset with a stock HTC ROM, and now instead of getting OTA updates earlier I get them later. The check for update box does absolutely nothing.
Can anyone help me ascertain why? Running 2.2.1 build 1.72.405.3
Or at least help me update.
Thanks,
Jake
How did you debrand? I also debranded my phone (was on T-mobile) by using a goldcard and using that to install a stock ROM but that wasn't enough. You'll need to change your phone's CID (an ID that determines which ROMs you can install - stock, Vodafone, T-Mobile etc), or SuperCID (install any ROM).
In order to do that, you will probably need to downgrade your ROM. Simply follow this guide:
http://forum.xda-developers.com/showthread.php?t=905003
After the downgrade, follow these steps:
http://forum.xda-developers.com/showthread.php?t=857537
The author's Easy Radio Tool allows you to do various things (S-OFF, SimUnlock, SuperCID). The only thing you need to do to get the OTA is to perform the last command in the list on the application (Stock CID), although of course you can do all the other stuff as well.
I just simply did the Stock CID and immediately afterward could get the update notification. My previously T-Mobile Desire HD is now running the shiny new 2.3 update nicely.
How do I check whether I have SuperCID, as I followed this tutorial here:
http://forum.xda-developers.com/showthread.php?t=857444
So I *should* have it.
I debranded by following the above tutorial and installing a stock ROM which I downloaded from here.
According to this post,
Checking the device state:
- Go to the bootloader (turn fastboot off, turn off phone, hold vol- and power)
- If it says ACE PVT SHIP S-OFF in the first line, your device is Radio S-OFF
- If it says ACE PVT ENG S-OFF, you have ENG S-OFF, go to System info
- If system info CID is 11111111, your device is SuperCID
- And if you can verify either Radio S-OFF or SuperCID (and you did both), it worked fine and you have both of them
- You can check your original CID by going to radio tool folder with cmd and typing: "adb shell getprop ro.cid"
Click to expand...
Click to collapse
Although SuperCID allows you to install RUUs from anywhere, I wonder if it would also prevent you from getting the OTA update. It's possible that, when you preform a check, the phone sends your CID to HTC's servers which see if your CID has an update, and a CID of 11111111 will never have. If all else fails, try setting your CID to the stock HTC one rather than SuperCID.
Ah I don't have ENG S-OFF, and when I go into FASTBOOT and select BOOTLOADER it returns me to the 'main menu', followed by a short period where everything is non responsive and a brief message flashed in green about a few files. Is this normal when attempting to access the BOOTLOADER menu with ENG S-OFF?
Yes that's normal. I believe the delay is the bootloader scanning the SD card for a firmware file.
So I can't check my SID?
To check it I have to get ENG S-OFF, and to get ENG S-OFF I have to permroot my phone, for which I have to flash back to a 1.32 build...
Also, if I flash back to 1.32 to permroot and S-OFF etc, and *then* I finally update OTA to the latest will that not remove my permroot and S-OFF like it did with the 1.72 OTA update? Would I have to install a full RUU rather than update? But then surely I can never update...
This confuses me.
If you update using the OTA, you will lose your root but you won't lose your S-OFF as far as I'm aware. According to the instructions on the One click Radio S-OFF tool, in order to revert back to stock you have to use the tool again to S-ON, which implies that S-OFF is retained between firmware updates.
So, if you permroot (downgrading to 1.32 if needs be) and then use the Radio S-OFF tool to set your CID to stock you should be able to get the OTA update and get future ones too.
*Edit* just looking at the instructions for the One Click tool, it looks like you can do a temproot if you just want to set the CID to stock.
Every time I run visionary and try to temproot it gets stuck on the plain black screen after the "attempting to temproot now". Have to press the home key (and wait) to back out of the app, any successive launches just take me straight back there.
Are you sure you've downgraded and running the 1.32.405.6 ROM? Have you got USB debugging enabled?
Sent from my Desire HD using XDA App
For a few weeks my Desire has been playing up and unpredictably reboots, seemingly at random. Initially I thought it might be a software issue with the ROM I was using, but the same thing happened with various other ROMs I've tried since. So I'm thinking it's a hardware issue and I'll need to send my Desire in for service.
Normally I'd thoroughly read the forums and work out how to go back to a stock ROM, but I'm running out of time - only a few days left under warranty. Therefore this cry for help...
When I got the device it came with a 2.29.405.2 ROM and a 32.49.00.32U_5.11.05.27 radio ROM. I used unrevoked3 to root the phone and have been using custom ROMs since.
I've downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe, but every time I'm trying to flash it, the process aborts during 'updating signature...' and I end up with:
Code:
ERROR [131]: CUSTOMER ID ERROR.
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Not sure what I'm doing wrong. Maybe I'm using an RUU for the wrong area? I'm pretty sure the original ROM was WWE though (it definitely was 2.29.405.2 / 32.49.00.32U_5.11.05.27). I've read somewhere that you can't just flash an RUU if it has a lower HBOOT version... Do I need a goldcard or what's the best way to go back to the stock ROM?
Any help would be much appreciated...
Just in case, here's what my bootloader info:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
You only need a goldcard if you are branded right now..
So is your phone branded with a carrier rom, then you must make a goldcard.
I think customer id error is due to incorrect goldcard.
There is a newer version, 2.29.405.5 I dont know if that's gonna work but worth a try.
You can also try to put the zip on your sd card instead of running an exe on your pc, assuming that you run the exe.
Thanks for the quick response.
My Desire was unbranded, so I guess I won't need a goldcard then.
I've downloaded the newer RUU version you mentioned, but got the same error message...
So far I've only tried the .exe, but I'll see if I have more success with the .zip.
Could the issue be that my current HBOOT version is higher than that of the RUU?
You can try to flash 2.3.3 from htcdev.com it's works for all hboots and without goldcards
boy_in_oz said:
My Desire was unbranded, so I guess I won't need a goldcard then.
Could the issue be that my current HBOOT version is higher than that of the RUU?
Click to expand...
Click to collapse
Since you get a CID error, I would definitely try a goldcard.
You can also try flashing the downgrader from alpharev first.
ETA: I think the latter would help.
from alpharev site: said:
# Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first.
Click to expand...
Click to collapse
-Jobo
@MatDrOiD (vv post below) Good point. I failed to notice that.
@touch of jobo:
Flashing downgrader from AlphaRev is not possible, the OP is S-ON.
@OP:
Check bortak's guide to bring your phone back to stock.
Have you tried step 7 in Bortak's guide? (http://forum.xda-developers.com/showthread.php?t=1275632) It was the solution for me! I skipped the downgrading part (had the same hboot as you have, so that shouldn't be a problem) and went on with phase 2.
If your phone was indeed unbranded, the goldcard should not be a problem as I understood..
Thanks guys. I'm at work at the moment but will give Bortak's guide a shot when I get home tonight and report back then.
The definition of unbranded is a bit different. Unbranded does not exactly mean that there isnt a carrier logo. HTC manufactured and sold phones in India as an example is for all intents a branded Device. It's the INFOCID property that defines whether branded or unbranded.
fastboot oem gencheckpt
Click to expand...
Click to collapse
Inside an RUU zip is a small text file. Open it and see if your INFOCID value is included. If not, you cant flash that RUU without a goldcard. See my sig for the unbricking guide, which explains this.
From my Guide:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code (Customer ID) which prevents you from flashing a ROM meant for any other brand and also blocks a Generic WWE RUU. If you're from India, it is branded with HTC_038. If you're unbranded, things are looking much easier for you, as generic WWE RUUs for SLCD are easily available. Run the following code from the sdk folder to find out if your device is branded
Code:
fastboot oem gencheckpt
This displays the CustID Code as HTC__ (and a number). If these numbers are the same as included in the cidnum value in the file android-info.txt, your device is unbranded. I have noted the following cidnums are unbranded: HTC__001, HTC__E11, HTC__N34, HTC__203, HTC__102, HTC__K18, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__016, HTC__032. I'm not sure whether it is an exclusive list. To find out if an RUU is compatible for your ROM, the value displayed by fastboot oem gencheckpt has to be included in the cidnum list of the RUU. If it isnt included, you will need to use a goldcard to bypass the cidnum checks done by the RUU.
Check if you have made a goldcard (A goldcard is a normal microsd card modified to become special while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA or allow you to switch between software meant for different regions). The purpose of a goldcard is that when apparently incompatible ROMs are flashed with a goldcard inside the device, the flashing process skips certain checks like the Customer ID check (and hence no CID error). Note however that you cannot ordinarily install software of a lower version just because you have a goldcard. Note also that it is the software version which is important, and not the Bootloader version. Note that if you want to downgrade your software to a lower version, it is easiest to use Teppic74's utility (Link1 or Link2), and downgrade to his version of the RUU (1.21), then upgrade to your version of RUU. If your device is SLCD, always make sure the software you're about to flash does support an SLCD screen. As a general rule of thumb, flashing any version <2.0 may be dangerous. Teppic74 assures us that the version 1.21 his utility comes with, is compatible with SLCDs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Wow, I would have never guessed this... With fastboot oem gencheckpt I found that the CID is T-MOB101... i.e. my Desire is actually branded! I bought it from mobicity in Australia as an imported unlocked phone and *assumed* that it was unbranded... So it's not surprising that the RUU gave me a customer ID error. (This also explains why the OTA update failed while I was still using this ROM).
What's really weird though is that the version of the ROM that the phone came with was definitely 2.29.405.2 with baseband ROM 32.49.00.32U_5.11.05.27... I did some googling today, but couldn't actually find a T-Mobile ROM with these version numbers
My guess is that mobicity imported the phone and flashed a stock HTC WWE ROM so they could sell it in Australia...
Any thoughts on this? I'm assuming that means that I do need a goldcard after all to go back to the stock ROM?
Ok, as I couldn't find a T-Mobile ROM with the aforementioned version numbers, I eventually decided to make a goldcard and flash RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe. The whole process worked fine without any error messages and the RUU reported success at the end.
Unfortunately my bootloader still displays the same info as in post 1, i.e. I'm still on HBOOT 0.93.0001. I would have expected this to revert back to 0.93... Did something go wrong with the updating procedure?
The issue is obviously still that the original ROM seemed to be a T-Mobile ROM (in fact I think a German one as fastboot oem gencheckpt reports the carrier as TMD), so I'm not sure if the service point will accept the unbranded WWE ROM I flashed.
The other option might be to flash the official HTC Desire Android 2.3 Upgrade from www.htcdev.com, but I think it's not compatible with T-Mobile Germany Desires... If I could flash this, it would at least be an official release and the service point shouldn't complain. Does anyone know how easy it is to root/S-OFF/install custom recoveries/ROMs afterwards? From what I read, I would need to use revolutionary, right?
Any alternative suggestions would be much appreciate...
Your are totally fine with 2.29 RUU. Hboot would only update if you flash 2.3.3 RUU. Did not read about guys who "bricked" their phone by using 2.3.3 RUU on a desire by T-Mobile.
Sent from ICS with Transparent XDA App
Can I flash the unbranded ruu on a branded 3 UK phone, will I lose recovery and superuser?
Sent from my HTC One X using Tapatalk 2
newcastle9 said:
Can I flash the unbranded ruu on a branded 3 UK phone, will I lose recovery and superuser?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
If you have unlocked via HTCDev the this would have removed your CID in which case yes you should be able to flash the WWE RUU on a branded device.
If you have not unlocked and are still running stock then no it wont work.
Does HTCDev unlock remove CID? Unless it changed to 11111111 you still won't be able to flash an RUU AFAIK
EddyOS said:
Does HTCDev unlock remove CID? Unless it changed to 11111111 you still won't be able to flash an RUU AFAIK
Click to expand...
Click to collapse
It does indeed. It doesn't change it to 1111111 it completely removes it altogether.
I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back (screen flickering problem) and it worked with no issues.
Vodafone Australia
I am Vodafone Australia and unlocked my phone via HTCdev. I am also facing the same problem (screen flickering)and need to send it back. I have re-locked it. As you just said "I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back" can you please explain how did you re-flash the WWE RUU? steps or link?
Deleted
gilbert_ac said:
I am Vodafone Australia and unlocked my phone via HTCdev. I am also facing the same problem (screen flickering)and need to send it back. I have re-locked it. As you just said "I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back" can you please explain how did you re-flash the WWE RUU? steps or link?
Click to expand...
Click to collapse
You need to get the vodafone au ruu. General wwe releases will not work for you. Pretty sure the correct ruu is available in the dev section.
Can't link, posting from phone.
M.
Sent from my HTC One X using xda premium
Stock RUU for 1.28 needed
Hi there
I have effectively killed my HTC one - I unlocked via htcdev and upgraded the recovery - fastboot shows the device id when running the command fastboot devices.
However I am now stuck in a boot loop where the phone only boots to hboot (following a failed boot.img flash) I have downgraded back to stock recovery and re locked but cant find the 1.28 RUU to recover the device (and I did try the RUU for 1.26 but it wouldnt install)
Once I updated te recovery i ran the fastboot boot boot.img command
This failed to progress past the 'htc quietly brilliant' flash screen.
I dont have the rom .zip saved on my internal memory on the phone - I was hoping to be able to push it to the /data/ partition however when I try this sdb returns no connected device.
Wonder if anyone can assist in either
a - returning to stock with a RUU for 1.28
or
b - advise how to flash the files I need onto the phone (it seems that the ROM isnt booting so I assume its from the point I install boot.img and beyond I need so help)
Unfortunately I cant get the phone to boot to copy files to the memory so need to work entirely in fastboot and adb (assuming adb wil recognise the handset)
Many thanks
Gurry
dr9722 said:
It does indeed. It doesn't change it to 1111111 it completely removes it altogether.
I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back (screen flickering problem) and it worked with no issues.
Click to expand...
Click to collapse
But relocking it puts it back so unless you were on HTC__001 you'd be back on the VODAP001 CID
Hi, a friend of mine recently bought an HTC One M8 (red version 32GB).
Yesterday he refreshed the OTA updates option on his phone and it prompted an update. He chose to perform the update, but then the phone rebooted and rejected to update saying that the OS has been modified.
Talking with the seller, he discovered that indeed that phone has been imported from USA.
How can we convert this M8 to be a "normal" M8 with the capability of doing updates and the support of Italian network bands ?
I've attached two photos with the software version of this phone.
I'm sorry for my poor english, thanks for your help in advance.
You have a AT&T device which is much better for you compare that mistakenly bought a Verizon or a Sprint device.
You can convert to Intl EU version but first you need to check what the MID is.
Connect to PC then run command
fastboot getvar mid
then we'll see what you can do .. because you need to install TWRP then change to correct MID while in recovery. Then you can run RUU 4.16.401.10 then do OTA to 4.16.401.13 and later do more updates.
ckpv5 said:
You have a AT&T device which is much better for you compare that mistakenly bought a Verizon or a Sprint device.
You can convert to Intl EU version but first you need to check what the MID is.
Connect to PC then run command
fastboot getvar mid
then we'll see what you can do .. because you need to install TWRP then change to correct MID while in recovery. Then you can run RUU 4.16.401.10 then do OTA to 4.16.401.13 and later do more updates.
Click to expand...
Click to collapse
MID is 0P6B13000
Now the MID is something else because AT&T MID is 0P6B12000.
To change to EU version you need to change MID to 0P6B10000
Read this thread : http://forum.xda-developers.com/showthread.php?t=2708581
Do you think you can manage that ?
Before that, is your device currently rooted or non-rooted ? If it is rooted then proceed to change the MID as shown in that thread.
If it is not rooted, you need a flashable.zip to install TWRP so you can run the MID conversion while in recovery.
ckpv5 said:
Now the MID is something else because AT&T MID is 0P6B12000.
To change to EU version you need to change MID to 0P6B10000
Read this thread : http://forum.xda-developers.com/showthread.php?t=2708581
Do you think you can manage that ?
Before that, is your device currently rooted or non-rooted ? If it is rooted then proceed to change the MID as shown in that thread.
If it is not rooted, you need a flashable.zip to install TWRP so you can run the MID conversion while in recovery.
Click to expand...
Click to collapse
Ok thanks
The phone was already rooted so i succesfully changed the MID to 0P6B10000
What I need to do now?
Great ...
Now you need to run RUU to revert everything to stock. RUU will wipe everything in your internal storage, so keep a backup of your important files like photos, musics & etc. Furthermore, you are doing full conversion.
You need a Windows PC with USB2.0, latest HTC USB driver installed.
Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Here : http://androidruu.com/?developer=M8
Connect your device to PC (preferable put it on bootloader/fastboot mode)
Right click the RUU exe and select run as administrator and follow all the instructions until it completes the process.
This will take you to a fully convert EU version 4.16.401.10 and then do OTA to 4.16.401.13
The rest is up to you what you want to do with your phone after full conversion.
ckpv5 said:
Great ...
Now you need to run RUU to revert everything to stock. RUU will wipe everything in your internal storage, so keep a backup of your important files like photos, musics & etc. Furthermore, you are doing full conversion.
You need a Windows PC with USB2.0, latest HTC USB driver installed.
Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Here : http://androidruu.com/?developer=M8
Connect your device to PC (preferable put it on bootloader/fastboot mode)
Right click the RUU exe and select run as administrator and follow all the instructions until it completes the process.
This will take you to a fully convert EU version 4.16.401.10 and then do OTA to 4.16.401.13
The rest is up to you what you want to do with your phone after full conversion.
Click to expand...
Click to collapse
I ran the RUU but now the process is stuck at 2/8 52% updating the radio and doesn't go further. What happens if I disconnect the cable and re-run the RUU?
That show you have PC/USB connection problem. You need to have the latest HTC USB driver. If you are not sure, download HTC Sync Manager, install then uninstall the HTC Sync Manager but leave the drivers. As mentioned earlier, you need PC with USB2.0
http://www.htc.com/us/support/software/htc-sync-manager.aspx
After awhile if it doesn't stop with an error message, you can disconnect and rerun the RUU. Your screen now blank/black means the device in RUU mode (you can run the RUU directly without put the device on bootloader again)
Ok, I re-ran the program and now the phone is like european ones, but we're still not able to do OTAs. Can it be s-off or the unlocked bootloader?
Thordgar said:
Ok, I re-ran the program and now the phone is like european ones, but we're still not able to do OTAs. Can it be s-off or the unlocked bootloader?
Click to expand...
Click to collapse
Nothing to do with S-Off or unlocked bootloader.
S-On and unlocked bootloader is problematic but not with S-Off.
What's the error when doing OTA ?
What's written on the bootloader now ?
Can you post result of fastboot getvar all (without serial no. & imei no.)
I'll check tomorrow your progress as I need to rest now .. it's 2 a.m here.
Maybe someone else will help you while I'm away
I took a photo, may it be the super-cid?
It keeps saying this
But now it does not reboot before showing the error
Inviato dal mio LG-H815 utilizzando Tapatalk
That error related to MID.
SuperCID is ok, my device is SuperCID too and I convert to many versions EU, Asia, Dev Ed & etc.
Recheck your MID, that's why I asked for getvar all result
ckpv5 said:
That error related to MID.
SuperCID is ok, my device is SuperCID too and I convert to many versions EU, Asia, Dev Ed & etc.
Recheck your MID, that's why I asked for getvar all result
Click to expand...
Click to collapse
Setting CID to HTC__032 did the trick! Now it is normally updating!
Thank for you're help and you're time, goodnight :good:
hello friends... currently i have a htc one m9 which i bought from another person. currently i m using viperone m9 4.3.0 marshmallow rom. current CID = 1111111 and MID=OPJA12000, i got this information from download-mode. ..( Baseband version =01.01_U11440792 ,and build number =3.35.401.12) . Unlocked+ S-OFF status. now , i m wanting to get back to full stock marshmallow.. so . i got "0PJAIMG_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.41.zip" for my device to flash it through manualy from download mode..is it ok for my device model? and ,can i fully unlock the bootloader and install TWRP on that version? thanks in advance ...
No. You must find one that matches the 401 sku. Find the firmware ruu 3.35.401.12 as a zip file (not exe).
You also need to change the cid before you flash to htc_001. The mid might need to be changed too but I can't remember what it is.. Too stoned.. '0PJA10000'..?
Do not s-on. Do not lock/relock the bootloader.
Once stock you can take the ota updates to nougat and reroot etc..