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.
RELOCKED
S-ON
OS : 2.10.401.1
CID: HTC_0031
Hello Guys,
I have a major problem getting my HTC M9 back to stock!
My first problem began when i was trying to update my ViberRom from 5.1.1 to Marschmallow, the problem that i had was that my recovery could not update. But when i updated it to 3.0.0 or something like that, i couldn't boot my ViberRom (because that was still 5.1.1).
So in order to fix that problem i thought that i could return my HTC M9 back to stock with an RUU, however since i have the EU/International version (2.10.401.1), i could not use the .exe version HTC provided themselves on their own website. After looking on the internet i found an RUU which corresponded with my version (2.10.401.1) it was a ZIP file so i needed to either flash it or put it on my SD card.
After a while a new problem arose, I have no S-OFF, but after reading several threads i did not matter as long as i had the right RUU version or higher (as well as matching CID, MID). Several articles and threads also mentioned that when i wanted to flash an RUU with S-On i would need to re-lock my bootloader and so i did.
With a locked bootloader i tried flashing the RUU, but everytime when i do it my FASTBOOT.EXE crashes!
Sorry if i am being a NOOB right now, but i really don't know what to do now, My Rom won't boot and i cant acces my recovery. I already treid Unlocking my bootloader again, and after completing every step, including choosing the option to unlock it on the phone itself using the volume buttons, it still states: RELOCKED
I really hope you guys can help me with my problem!!
Kind regards,
Roan
(sorry for anything that may be not clear, English is not my native language)
Roanvdw said:
RELOCKED
S-ON
OS : 2.10.401.1
CID: HTC_0031
Hello Guys,
I have a major problem getting my HTC M9 back to stock!
My first problem began when i was trying to update my ViberRom from 5.1.1 to Marschmallow, the problem that i had was that my recovery could not update. But when i updated it to 3.0.0 or something like that, i couldn't boot my ViberRom (because that was still 5.1.1).
So in order to fix that problem i thought that i could return my HTC M9 back to stock with an RUU, however since i have the EU/International version (2.10.401.1), i could not use the .exe version HTC provided themselves on their own website. After looking on the internet i found an RUU which corresponded with my version (2.10.401.1) it was a ZIP file so i needed to either flash it or put it on my SD card.
After a while a new problem arose, I have no S-OFF, but after reading several threads i did not matter as long as i had the right RUU version or higher (as well as matching CID, MID). Several articles and threads also mentioned that when i wanted to flash an RUU with S-On i would need to re-lock my bootloader and so i did.
With a locked bootloader i tried flashing the RUU, but everytime when i do it my FASTBOOT.EXE crashes!
Sorry if i am being a NOOB right now, but i really don't know what to do now, My Rom won't boot and i cant acces my recovery. I already treid Unlocking my bootloader again, and after completing every step, including choosing the option to unlock it on the phone itself using the volume buttons, it still states: RELOCKED
I really hope you guys can help me with my problem!!
Kind regards,
Roan
(sorry for anything that may be not clear, English is not my native language)
Click to expand...
Click to collapse
Fastboot crashes because it can't handle files over 2 GB. There is a different fastboot you need to use called htc_fastboot. Search the forum for a link. Or I'll find one if i can. Commands are exactly the same as fastboot, just add "htc_" in front of fastboot.
Here you go:
https://www.androidfilehost.com/?fid=95916177934550031
jollywhitefoot said:
Fastboot crashes because it can't handle files over 2 GB. There is a different fastboot you need to use called htc_fastboot. Search the forum for a link. Or I'll find one if i can. Commands are exactly the same as fastboot, just add "htc_" in front of fastboot.
Here you go:
Click to expand...
Click to collapse
IT WORKED, very grateful man, very weird that i could not find this problem in the forum though, maybe i just suck at searching.
i have the same problem, i cant even find RUU.zip file, if you could help me with that, would really appreciate it
I have an HTC One M9 and tried to install an RUU with 6.0.0... Think is bricked... after digging a lot... the problem is I never closed or unnistalled the HTC sync manager and tried to update the software with it running, I got the advice: Get the right software for your phone, I downloaded the RUU from the official HTC page and the AT&T section, I live outside the US so OTA wasn't an option, the first attempt I got 11%, restarted phone, everthing OK, tried again, now it got till 22% but now phone is stuck in the service mode mode, the menu where I can choose: Reboot, Reboot to bootloader, etc. the phone won't boot to OS, I'm downloading this RUU http://forum.xda-developers.com/att-one-m9/general/official-att-htc-one-m9-t3380821 but since now I Can't get into the OS I don't know if the RUU will recognize the phone to update, please help me how to restore my phone or how to install the RUU from download mode or whatever.
My phone is stock, S-on, Locked, don't know why the software status now shows: Modified*** Bootloader is lock, have never done nothing to the phone, I was running Lollipop.
Thanks in advance.
It says modified because someone borked the process when trying to root it so now the phone thinks it's rooted so the update wont take. Stynk manager might be able to reflash it but if not you'll need the original ruu.exe for the version you were at or later.
Beamed in by telepathy.
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.
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.