Hi everyone,
It would appear that my phone is stuck in a permanent boot loop. I'm still on the latest official rom from my carrier, it's not rooted nor have I made any changes to the bootloader.
The only thing that I did was restart my phone from within the OS after I couldn't launch the official SMS app (some MMS process error).
Now I'm stuck in a boot loop where the phone doesn't get past the first "HTC" logo page. I also notice that there are two thin dark horizontal lines on the top and middle of the screen that weren't there before. They look like clusters of dead pixels and are across the whole screen.
I've tried using the official bootloader to do a factory reset and wipe cache but I'm still having the same issue.
What else can I try? Is it safe for me to unlock the bootloader and try flashing a custom ROM while the phone is in this state?
I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs
squ89r97 said:
I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If everything is official, I'd send it back and get a replacement.
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.
squ89r97 said:
If everything is official, I'd send it back and get a replacement.
Click to expand...
Click to collapse
shivadow said:
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks
templer59 said:
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks
Click to expand...
Click to collapse
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk
P$YCH0 said:
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
You mean "connect it to a pc while in download mode, install a copy of fastboot.exe and type: fastboot getvar.
P$YCH0 said:
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?
Click to expand...
Click to collapse
If you need permanent storage for the ruu you got let me know as i have plenty of gdrive space.
Beamed in by telepathy.
Hi guys, I am in the exact same situation and don't seem to be able to find the appropriate RUU file for my phone. Can you please give me some indication regarding how to find it.
So far I managed to unlock the bootloader, install TWRP and attempted flashing several RUU files without any success whatsoever.
Thanks a lot in advance!
Cheers!
Related
Okay I'm really getting sick of this thing. I've totally no idea what I've done but after 2 hours of trying, I'm back to the same thing. Finally managed to get the proper USB drivers for my computer so the phone and the computer could talk to each other.
I've followed this guide on how to unroot the phone:
http://theunlockr.com/2014/07/15/how-to-unroot-the-htc-desire-816/
First, when I relock the bootloader, I still got ***Tampered*** and ***Security Warning*** although it says relocked. I couldnt boot into the OS. Can't do anything at all. Unlocking it again solves the problem.
Secondly, I wasn't able to get to S-Off mode. Anyone can shine some light on this? I'm really stuck here. I can't flash the stock RUU.zip as it says signature failed.
Would be glad that someone could assist me on this... I really need to get rid of the phone as soon as possible as I'm sick of this thing.
And, BTW, mine is the single SIM with LTE version.
Thank you.
Is yours the a5_chl or the a5_ul? The a5_chl is the one on VM.
did you flash the correct stock recovery to replace your custom recovery before you re-locked it?
also, there is no S-off for this model yet so don't waste time looking for it
edit
FoxyDrew said:
Is yours the a5_chl or the a5_ul? The a5_chl is the one on VM.
Click to expand...
Click to collapse
a5_ul.
Where can I get the files for a5_ul?
seekfind said:
did you flash the correct stock recovery to replace your custom recovery before you re-locked it?
also, there is no S-off for this model yet so don't waste time looking for it
Click to expand...
Click to collapse
I couldn't find the proper stock recovery.
But I thought S-Off needs to be off before everything else can be done?
No need for S-off to unlock/relock bootloader or flash custom/stock recovery/ROM. none of us here have S-off and yet we all use custom delights provided by XDA devs
this will probably help you with the stock recovery, tho I'm not sure if it works for single SIM or not:
http://forum.xda-developers.com/desire-816/help/how-to-install-stock-recovery-img-t2937667
This may seem like an amateur question, but how do you tell if your phone is a5_chl or a5_ul?
jamiedenton said:
This may seem like an amateur question, but how do you tell if your phone is a5_chl or a5_ul?
Click to expand...
Click to collapse
you restart your phone to bootloader.
1. Disable fastboot. Settings>Battery>uncheck fastboot.
2. Power off
3. Press and hold Volume Down and power
it's written in there
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
fernandezhjr said:
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
Click to expand...
Click to collapse
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
zroice said:
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
Click to expand...
Click to collapse
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Aldo101t said:
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Click to expand...
Click to collapse
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
lol, sorry missed that part
---------- Post added at 07:50 PM ---------- Previous post was at 07:26 PM ----------
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
I do believe if you can get to download mode you can do a factory nreset from there, if that will help you.
zroice said:
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
Click to expand...
Click to collapse
What about flashing an older RUU and trying to take the update again?
fernandezhjr said:
What about flashing an older RUU and trying to take the update again?
Click to expand...
Click to collapse
cant find any ruu for that branding - if you see/saw one please let me know.
zroice said:
cant find any ruu for that branding - if you see/saw one please let me know.
Click to expand...
Click to collapse
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Flippy498 said:
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Click to expand...
Click to collapse
*downloading with fingers crossed*
Failed: -2, 19 to flash via downloadzip or smth like that
Can you flash twrp recovery? If you can, maybe you can flash a stock backup from someone else.
zroice said:
Failed: -2, 19 to flash via downloadzip or smth like that
Click to expand...
Click to collapse
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Flippy498 said:
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Click to expand...
Click to collapse
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
zroice said:
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
Click to expand...
Click to collapse
Yes, 2.10.206.2 is the latest version for now. If there were a RUU with your firmware version then using it would be the easiest way to solve your problems. But as far as I know the only existing ones for O2 are for 1.32.206.6 and 1.32.206.15. But with S-OFF you would be able to use the older RUUs, too.
I never used a java card so my knowledge about this topic isn't that outstanding. I know that it is a small, SIM-Card-like looking thing that allows you to S-OFF your phone. Usually they cost several hundred euros/dollars and the number of times you can use them is limited. Since verizon blocks bootloader unlocking these cards are the only option if a verizon users wants to flash anything on his/her phone. Some German phone shops offered S-OFF by java card, too, before sunshine got updated for the M9. That's why I gave you the link to Android-Hilfe. (And that's actually all I know about that topic.)
i need this rru please any one have to uplode link
thanks
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
theadra said:
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
Click to expand...
Click to collapse
Bootloader and s status are irrelevant. The phone will flash regardless.
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.
Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?
Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Have you tried doing a factory reset using the stock recovery?
See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.
tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?
Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.
Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.
I have a european One M8. I turned it off when I got in the plane and after landing it never started back
It gets stuck in the HTC logo.
Some times it moves on and says that "android is updating 165 applications"...and when that finishes it says that Sense Home has crashed and shows the HTC logo again (strangely I can change the volume at that stage ).
I tried to enter Recovery and did a Factory Reset but still nothing. When I select the Recovery option inside that menu I only see an icon of a phone with a red icon, no options to wipe cache etc...
The phone is STOCK, S-ON, no root nothing.
Any suggestions? Can I just reflash the stock rom?
panagath said:
Can I just reflash the stock rom?
Click to expand...
Click to collapse
Possibly. What does it say for OS number on the bootloader screen?
Also, please confirm near the top of the bootloader screen, it says LOCKED (versus UNLOCKED or RELOCKED).
redpoint73 said:
Possibly. What does it say for OS number on the bootloader screen?
Also, please confirm near the top of the bootloader screen, it says LOCKED (versus UNLOCKED or RELOCKED).
Click to expand...
Click to collapse
Hello, thanks for the reply. What I see are the following:
LOCKED
HBOOT - 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.61.4
vagon1 said:
Did you find solution/fix pls ?
I seem to have similar problem.
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spent many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Vash
Click to expand...
Click to collapse
Hey, thanks for the reply. I haven't managed to do anything neither did I spend a lot of time on this. I was waiting in case someone could help. Such a shame if the phone is bricked. I do not know if it is worth taking to professionals as its value as a used phone is quite low at the moment...
panagath said:
OS-6.12.61.4
Click to expand...
Click to collapse
Unfortunately, I don't think your version has an RUU (or from a free source, anyway) that would restore your phone fairly easily (assuming the problem is software, and not hardware).
That being the base (no RUU) you can restore by unlocking the bootloader, installing custom recovery TWRP, and restore a stock TWRP backup (stock ROM).
So it is possible to recover (again, as long as it's not a hardware problem). But it's not a short/simple procedure, if you aren't familiar with these terms and methods.
I fixed it by unlocking the bootloader from HTC's website, installed TWRP and then flashed the LineageOS Rom...
panagath said:
I fixed it by unlocking the bootloader from HTC's website, installed TWRP and then flashed the LineageOS Rom...
Click to expand...
Click to collapse
Nice work. It was hard to tell from your post, your level of knowledge. Did you have to learn how to do this, or had prior experience unlocking bootloader, TWRP, etc?
I was on vacation/holiday last week, and not on XDA. So sorry it took so long to get back to you.
redpoint73 said:
Nice work. It was hard to tell from your post, your level of knowledge. Did you have to learn how to do this, or had prior experience unlocking bootloader, TWRP, etc?
I was on vacation/holiday last week, and not on XDA. So sorry it took so long to get back to you.
Click to expand...
Click to collapse
Thanks for the help. I have had previous experience installing custom ROMs on HTCs
(HTC Diamond, Wildfire, Desire, Desire HD, Desire S, One S, One X and now the One M8 )
I was just hopping I could get an easy solution without having to go through the whole process