I have an HTC One M9 that up until yesterday had an unlocked bootloader and had S-Off.
It was running a pretty old ROM so I decided to update it. My first attempt was Viper.
After installing through TWRP recovery it would only take me to the TWRP boot screen after rebooting.
I attempted another ROM, this time Revolution and got the same results.
I’ve been messing with it for hours and somehow I have S-ON and the bootloader is locked. Actually it says RELOCKED.
It has no OS and it will no longer go to Recovery mode. I think the TWRP I tried to install is too new for it.
I’ve performed the HTC bootloader unlock procedure a few times and although it says successful, after reboot, its still relocked.
Am I screwed, or is there something more I can try?
If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??
Dark Stranger said:
If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??
Click to expand...
Click to collapse
Yes, it goes into download mode. I've tried the only Telus ruu I could find (RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe)
and I get a Error 131 Customer ID Error.
I just tried a Sprint ruu (RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe) and I got Error 155 Unknown Error. They both fail right after it displays Updating Signatures.
I'm in Canada and it's a Telus phone but it's carrier unlocked.
Do I need to use a Telus RUU or should any Canadian RUU work on it?
are you sure yours already s-off?
1. re flash lastest TWRP
2. flash required lastest firmware (s-off)
Firmware 3.35.401.12 is required for proper installation! Download (S-OFF ONLY)
3. flash your fav lastest custom rom
Yes, it's definitely S-On.
Any Canadians out there? After some reading I realize I need an RUU of a specific sku. In my case 661.
I need a Telus RUU of 2.11.661.5 or higher for the M9. I'm hoping that will resolve my issue.
Related
Hi guys,
Hoping someone can help, have bricked my Australian Optus stock One X. I have tried to follow all threads related to loading stock or custom roms from fastboot and am unable to. I still have CWM recovery 5.8.2.7 touch installed.
I had previously rooted it and installed Android Revolution HD 5.1.0 and seemed to be fine but was unstable and would crash and reboot in certain apps. In trying to revert back to stock I stupidly formatted the SD card, DUMB ASS!
I have downloaded stock rom 1.29.401.7-DUO, all-in-one rootkit, and the ARHD ROM and have tried to either:
1) flash ARHD with bootloader still unlocked, doesn't work
2) follow reflashing stock process ie flash stock recovery, relock bootloader, then flash stock ROM, and am getting stuck on just reflashing the stock recovery. When I try to open stock recovery it takes me to a black screen with a red ! in a triangle, this is with the bootloader relocked.
If anyone is able to help an enthusiast noob like me I'd be very appreciative and would also be more than willing to donate for the trouble.
MAKE SURE you have exactly the right RUU for your phone, whatever the rom was on you were using, ie, 1.26, 1.28, 1.29, you need the same version of RUU, i discovered the problem trying to flash RUUs and after 2 days finally got the correct one, thats when i realised, unlike on other phones, you cant downgrade the One X and when recovering it seems to prefer the one that matches what you were using.
Also make sure youre cid is supported in that RUU, ie, HTC 001, TMOB 054, etc etc, mine can only accept 401 roms, so they must match exactly, until we can get S-Off this problem will remain, dont worry about recovery, so the guide on in case of disaster, you cant go wrong with it, relock your bootloader and get your RUU installed, from their update it to your latest ics version and then if you must reflash your cwm and root it.
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
agentorange82 said:
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
Click to expand...
Click to collapse
You can get 1.28.980.10 from htcdev downloads. I would link but I'm a new user, just filter by One X, Optus, and it's there.
Thanks again for the help. I have seen those files on htcdev website, but don't know how to use them
I don't know how to load a RUU that is not a .exe file...if anyone is able to assist, again, I would really appreciate it and will donate once up and running again.
Edit: I just wanted to add that I have tried to follow the thread that explains how to load/flash recovery and boot images via fastboot in command prompt, and have not been able to. So I don't think I'm a complete dumb ass, but do need someone with the knowledge and patience to guide me through it. Please!
First thing first, do you have the right RUU with you ?
If not, maybe this is the one for you : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_258004_signed.exe
second: do you have fastboot directory set up on your pc ? and htc usb driver too ?
Just starting the download now, I think that could be the RUU I've been looking for. Yes I have the drivers and fastboot directory. Will give this RUU a go and let you know, thanks for the quick reply, ckpv5!
Most important before you run the RUU, you need to:
1) have a stock recovery flashed to you your device first (I believe you already have one)
2) relock the bootloader - fastboot oem lock
3) run RUU, it should work.
THANK YOU!
ckpv5, thank you for the link to the updated RUU. Phone is functioning again, stock. Donation coming your way. Thanks for all your help. agentorange82.
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Hi,
Did you try to reflash your recovery and try to install another rom like ViperOne M8? Or if you want i can send you the stock ROM Android 6.0
Laurens54321 said:
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Click to expand...
Click to collapse
You seem to be going about things rather haphazardly:
1) Not sure exactly what "some OTAs" refers to. But there is typically only one OTA that will properly work. That being the one that is for your CID (carrier version) and for the next software version (can't skip any).
2) Along the same lines, you can't just flash any RUU. It has to be for your CID and MID (Error 130 usually means wrong MID), and equal or greater version number than main version on the phone (no "downgrading" unless you have s-off).
3) "messing around with stuff that didnt work" doesn't tell us anything about how you got to the current condition. You need to be specific and detailed, if you want us to be able to tell what you did, and how to recovery.
4) You can't unroot and OTA, it has to be a stock (never rooted) ROM and stock recovery.
5) boot.img in itself probably won't help your situation. And signature verify fail usually means you tried to flash without the bootloader unlocked (which won't work).
Are you S-OFF? If so, this works;
1) Download 0P6BIMG.zip. You'll have to Google
"dottat @ XDA M8 RUU" to get the file as I haven't
made at least ten posts here and can't post links yet.
2) Place 0P6BIMG.zip on an SD card formatted fat32 ONLY.
3) Boot your phone, allow HBOOT to recognize 0P6BIMG.zip
and follow the prompts.
RESULT: This will land you on STOCK kitkat 1.55.605.2
pre-rooted with stock recovery.
----------------------------------------------------------------
CREDIT: dottat @ XDA
So this is the whole story:
I rooted my 10 and it was all good but when I restarted my phone, it told me to decrypt phone but there was no keyboard. So after resetting my phone in twrp, i got passed the decrpt but still no keyboard.
at this point I tried doing RUU but got error 155, then relocked bootloader and tried again but still didn't work.
So now I'm at this point my 10 won't even boot passed the HTC powered by android screen.
So can anyone help me? I don't know if this would work but does anyone have a twrp backup of the stock rom i can recover with?
Edit: got it to work.
I encountered the same thing, I solved it by flashing a keyboard zip through twrp, I think it was SwiftKey. If you re-locked your bootloader, I suggest you unlock it again and change your CID to SuperCID, and make sure your MID matches as well. You should be able to flash the RUU then.
Cakeor314 said:
I encountered the same thing, I solved it by flashing a keyboard zip through twrp, I think it was SwiftKey. If you re-locked your bootloader, I suggest you unlock it again and change your CID to SuperCID, and make sure your MID matches as well. You should be able to flash the RUU then.
Click to expand...
Click to collapse
So to make my CID into superCID i have to s off , my question is what do you mean to make sure my MID matches? matches with the superCID?
Edit: nvm got RUU to work, for now anyway, its working.
format data in twrp and install another rom
Hi guys,
Basically, my phone seems to be either stuck in airplane mode even though it comes up as off, or there's something gone wrong with the radio. It randomly happened last night on its own. Did not reboot the phone or flash anything.
I've tried:
-Flashing a new custom ROM. Did not fix.
-Formatted the entire data and flashed a ROM again. Same thing, did not fix. Instead I got a DEFAULT IME provider has stopped working once it booted in.
-Tried the HTC 10 RUU method. Flashing always fails once it reaches the update signature point. Bootloader is re-locked, still get the 155 ERROR.
Phone is S-ON. Firmware: 1.82.8996
Not sure what else to do now. Any help would be greatly appreciated.
Thanks,
Ice
I'm not entirely sure what happened to your device. But if I were you I would unlock the bootloader again, then s-off the device. Earlier I tried to use the RUU method, and didn't work. Gave me an error. Then when I got the device to s-off the RUU method worked without a problem. You can give that a try.
I just S-OFF'd the device and tried again, but didn't work. RUU keeps giving me the same error again. I've tried both ways, locking and re-locking the bootloader with S-OFF. I've even gone ahead and update the firmware to the latest international version.
-Flashed the latest firmware. 2.41.401.4 from sneakyghost's thread.
- Installed TWRP
-Formatted entire data
-Ran RUU twice. Downloaded the latest once from HTC 10's website.
-Error 155 both times.
IcedRealm said:
I just S-OFF'd the device and tried again, but didn't work. RUU keeps giving me the same error again. I've tried both ways, locking and re-locking the bootloader with S-OFF. I've even gone ahead and update the firmware to the latest international version.
-Flashed the latest firmware. 2.41.401.4 from sneakyghost's thread.
- Installed TWRP
-Formatted entire data
-Ran RUU twice. Downloaded the latest once from HTC 10's website.
-Error 155 both times.
Click to expand...
Click to collapse
You can't download the ruu from the HTC website because the one 2.41.401.4 isn't on the website of HTC !
https://forum.xda-developers.com/htc-10/how-to/wwe-htc-10-stock-rom-ruu-2-28-401-9-t3525075/page27
So i bet you are flashing a US Ruu ..... go to that thread and try that one. Or the .exe (windows method) or look for the .zip version (via sd card method) !
IcedRealm said:
I just S-OFF'd the device and tried again, but didn't work. RUU keeps giving me the same error again. I've tried both ways, locking and re-locking the bootloader with S-OFF. I've even gone ahead and update the firmware to the latest international version.
-Flashed the latest firmware. 2.41.401.4 from sneakyghost's thread.
- Installed TWRP
-Formatted entire data
-Ran RUU twice. Downloaded the latest once from HTC 10's website.
-Error 155 both times.
Click to expand...
Click to collapse
Hello, Have you fixed the airplane mode problem ? I have the same issue with my HTC U11.
Same issue. Any working fixes? The more I browse forums, the more I think that the issue is related to KEEPFORCEENCRYPT flag
Solved.
I flashed the 3.35.401.12 RUU according to Flippy498's guide
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698 (Thread #5)
All the Phone data was wiped during the process.
shivadow and computerslayer thanks again for your help
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32
You need to run the ruu.exe but I don't know if one exists for your version. You can flash any 3.35.401.xx ruu but those that aren't "xx" must match. Not sure you can flash a signed zip in s-on state..
If the ruu.exe doesn't exist then you'll either have to wait for it to be released or rtm for repair.
There is no actual way to know exactly how buggered the phone is because it died in the middle of a flash process. It is very possible it died just as it was flashing recovery, explaining why there isn't one, but I wouldn't like to bet money on it, or it being recoverable at all.
Beamed in by telepathy.
shimshi said:
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32
Click to expand...
Click to collapse
You've access to download mode, so you should be able to use the SD card method of applying the matching RUU. Check out the readme thread for instructions and the necessary file.
Thanks for your help shivadow and computerslayer,
I will look at the RUU method and try to learn more about it and replay if it worked or not.
I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?
jewels76 said:
I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?
Click to expand...
Click to collapse
If you unlocked bootloader, the warranty is void anyway.
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".
albaniax said:
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".
Click to expand...
Click to collapse
Those are two different methods: The SD card method and the htc_fastboot method (which requires a PC).
And it's actually the other way round. The htc_fastboot method requires a locked or at least re-locked bootloader whereas the SD card method can be used with an unlocked bootloader, as well.