Android won't start and need help flashing - One (M9) Q&A, Help & Troubleshooting

Hi,
I have bought a used HTC M9 on Kijiji (I'm in Québec, Canada)
It must be faulty because it kept randomly restarting (sometimes once, sometimes for periods of 20 minutes, which made it hardly usable)
After clearing the cache partition and factory resetting it a couple times, I decided to flash it.
What I did:
- enabled the developer mode and USB debugging
- unlocked the bootloader
- flashed TWRP
- flashed SuperSU v2.74-2
Now, Android won't boot. When I start the phone, I see the green HTC logo on a white background with a red text saying it's a development build, then after about 10 seconds it restarts to the same screen. Over and over again.
In download mode, I am able to see the device with fastboot, but adb does not show anything.
In recovery mode, it's the opposite.
The phone is still S-ON so I have tried S-OFF methods (moonshine and firewater), but the fact of not having fastboot AND adb working at the same time made them fail.
Here's my phone info:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.38.666.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
Any help would be greatly appreciated...
Thanks in advance!

youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine

Roobwz said:
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Click to expand...
Click to collapse
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?

zzzer51 said:
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
Click to expand...
Click to collapse
You shouldnt use toolkits imo, no offence squabbi. You should just download the 2.64 file from chainfires thread and flash it in twrp. It isnt harder than that. Btw 2.64 was the only superSu that worked for me

Ok, I have been able to find a zip for 2.64 and will install it with TWRP when my phone's battery is drained out (it tried to boot on the OS and is currently stuck on the HTC logo...)
I have also tried installing files directly from the microSD
downloaded from:
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://androidruu.com/index.php?developer=M9
using fastboot flash zip zipfile.zip
but I get errors like
9 RU_SECURITY_FAIL
android-version information is missing
I'm not sure I'm trying to flash the right file anymore...
EDIT:
I have tried to flash both 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.30 and 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6 files by going to TWRP -> Install but I get the error message 'zip file is corrupt!' every time...
And when I try to flash with fastboot, I get "Invalid sparse file format at header magi"
EDIT2:
Ok, I have made some progress!
What I did:
1/ Downloaded the image from this page http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
2/ Formated my 8GB microSD card to exFAT (because the system image file is over 4GB)
3/ Extracted the system.emmc.win and boot.emmc.win files to the microSD card in path: E:\TWRP\BACKUPS\<myPhoneIDThatFastbootCanGiveYouIfYouTypeFastbootDevices>\Stock Bell
4/ Started the phone in recovery mode (TWRP)
5/ Tapped on Restore
6/ Selected the two files and hit Restore
7/ Performed a Factory reset (through TWRP, by tapping Wipe)
8/ Rebooted the phone in System mode
And Android started!
I'm not 100% sure it fully works as I haven't been able to finish the configuration yet (I don't have access to a wifi network where I am) so I will do that when I get home tonight.
But it looks a lot better than these past few days.
In the meantime, a quick question:
My bootloader is still unlocked. Can I leave it like that or should I re-lock it?
Thanks

No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.

shivadow said:
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
Click to expand...
Click to collapse
You can OTA with an unlocked bootloader but you need to be 100 % stock. It's always best to not relock bootloaders as if you get into problems, you'll not be able to flash stuff. The only time a locked bootloader is needed is when running RUU.exe while S-On. The SD card method works with an unlocked bootloader. I'd recommend to leave it unlocked

Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time

zzzer51 said:
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
Click to expand...
Click to collapse
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.

Roobwz said:
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Click to expand...
Click to collapse
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?

zzzer51 said:
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
Click to expand...
Click to collapse
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Skickat från min HTC One M9 via Tapatalk

Roobwz said:
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Click to expand...
Click to collapse
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?

zzzer51 said:
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
Click to expand...
Click to collapse
The service is remotely done over the computer, so you'll see everything that happens.
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free. Either that or s off (25$ as well), and you'll be able to convert your phone into a world wide edition model or dev edition. S off opens up a whole new world for you. Ex - you can flash exactly what you want (no need for Canadian firmware) and you're able to downgrade etc. The rest is up to you.

Roobwz said:
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free.
Click to expand...
Click to collapse
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code

zzzer51 said:
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
Click to expand...
Click to collapse
That's kernel source I believe. Your only luck would be flippys thread in the general section
Skickat från min HTC One M9 via Tapatalk

The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!

zzzer51 said:
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
Click to expand...
Click to collapse
I would recommend upgrading to 3.xx for several reasons like doze, custom ROMs that are up to date etc. If you did the OTA from 1.x to 2.x, you shouldn't have any problems with the OTA to 3.x. in the worst case, just re flash the RUU or just convert the device to an European version.

Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks

zzzer51 said:
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
Click to expand...
Click to collapse
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.

Roobwz said:
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Click to expand...
Click to collapse
A looooot of stuff!
But even after flashing the original HTC recovery again, I get the same message.
And I can't access the recovery menu either.
Thanks

Related

OTA Update 5.1 Help

So right now my phone says it's getting the 5.1 update OTA. I am using TWRP. When I try to install the update it goes to the TWRP everytime. I dont use custom roms, just what came with the phone. How do I update the phone?
Found out I need to return it to stock recovery before I can install an OTA update. So I tried using instructions found on the web made for the noob I am. But when I use the CDM console it tells me that it can't open the recovery file.
\
What do?
Edit: I just need step by step help on what to do. I just rooted it so I could have BB10-like gestures and stock android navigation buttons. I didnt know it would screw me over for OTA updates
Edit 2: I got it work, now the update fails and goes to bootloader and tell me this, i am using the carrier supplied OTA update.
"this package of fir"htc_himaulatt" devices; this is a "htc_himauhl""
BriniaSona said:
Found out I need to return it to stock recovery before I can install an OTA update. So I tried using instructions found on the web made for the noob I am. But when I use the CDM console it tells me that it can't open the recovery file.
\
What do?
Edit: I just need step by step help on what to do. I just rooted it so I could have BB10-like gestures and stock android navigation buttons. I didnt know it would screw me over for OTA updates
Edit 2: I got it work, now the update fails and goes to bootloader and tell me this, i am using the carrier supplied OTA update.
"this package of fir"htc_himaulatt" devices; this is a "htc_himauhl""
Click to expand...
Click to collapse
This phone is a real hassle to update.
You won't be able to do OTAs until you return it to stock, and to do that, you'll have to run an RUU so that it removes TWRP and root. Make sure to re-lock the bootloader. So run the RUU of the latest version if it exists if you can then you won't have to OTA, or run the RUU that matches your phone's OS version and then take the OTA.
TWRP is removed using a stuck recovery image
the bootloader is relocked using commands from a video I watched on how to do it, it displays relocked when open.
however, now instead of getting the yellow error from before, I now get sent to the bootloader screen and nothing happens.
Edit: when I try to boot into recovery through the boatloads it gives me an error message saying it can't and takes me back to the white screen.
BriniaSona said:
TWRP is removed using a stuck recovery image
the bootloader is relocked using commands from a video I watched on how to do it, it displays relocked when open.
however, now instead of getting the yellow error from before, I now get sent to the bootloader screen and nothing happens.
Edit: when I try to boot into recovery through the boatloads it gives me an error message saying it can't and takes me back to the white screen.
Click to expand...
Click to collapse
I guess you missed the whole part about restoring your system partition to stock
From the backup you made after installing TWRP .
You need an untouched system partition and Stock recovery.
At this point you should look for the RUU for your phone
Sent from my HTC One M9 using Tapatalk
GG didnt make a backup.
Can you link me to one at all, and all the instructions needed to make things work. Sorry for the hassle, I really don't want to do this without help now, incase I mess things up more than they already are.
EDIT: this it it right? http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Except there's now Canada option.
EDIT 2: I wish it was as easy as BlackBerry which everyone seems to think it out of date, http://crackberry.com/install-leaked-os-autoloader
BriniaSona said:
GG didnt make a backup.
Can you link me to one at all, and all the instructions needed to make things work. Sorry for the hassle, I really don't want to do this without help now, incase I mess things up more than they already are.
EDIT: this it it right? http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Except there's now Canada option.
EDIT 2: I wish it was as easy as BlackBerry which everyone seems to think it out of date, http://crackberry.com/install-leaked-os-autoloader
Click to expand...
Click to collapse
Theirs a thread in the general forums for Canadian files
Sent from my HTC One M9 using Tapatalk
So I'm downloading the bell one and using download mode and adb to input the show commands?
''Fastboot output
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) version-main: 1.32.666.30
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001''
Edit: Didnt work, so I am using these commands, but now I need to s-off, so I'm going to do that now. http://forum.xda-developers.com/showthread.php?t=1907796
if you read this and I havent added and Edit: 2, then answer this.
what command erases everything and put it back to default, like how it was when i bought the phone.
Edit 2: re-unlocked the bootloader.
Device is giving me the same error as when I started. "this package of fir"htc_himaulatt" devices; this is a "htc_himauhl"
I downloaded a stock bell RUU. Went into adb and used
"fastboot update "filename""
I got an error saying there wasnt enough space.
EDIT: failed to load '0PJAIMG.zip': Not enough space
and when i try to sideload it it says the file can not be read.
Can someone just tell me what to do from the beginning, instead of telling me to look myself. Looking myself has only gotten me more lost and confused.
I need step by step instructions with links and files.
Please.
I just want my phone to be the way i bought it, No root, no bootloader changes, no twrp, just stuck everything.
MY phones current status.
Rooted, Bootloader Unlocked, Stock Recovery installed.
What do I do from there, where do I find the correct Bell RUU, how do I flash it, where does it go so it can be flashed.
BriniaSona said:
MY phones current status.
Rooted, Bootloader Unlocked, Stock Recovery installed.
What do I do from there, where do I find the correct Bell RUU, how do I flash it, where does it go so it can be flashed.
Click to expand...
Click to collapse
I think I found the correct RUU for your firmware version. The problem is you will have to pay if you want it since the website isn't for free. Sorry that I wasn't able to find a cheaper source. (Link)
Edit: Forget what I said. I just saw that there is a TWRP backup in this thread. Using it should be much cheaper than the RUU.

Bricked my HTC 10, What to do next?

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.

M9 Stuck in a permanent boot loop even after hard reset :(

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!

M8 won't flash RUU

Hello everyone,
- i'm sry if i posted abt the same issue but i managed to gather more information abt the situation
- 1st of all everytime i reboot i find the same apps installed , pics and missed calls no matter how many times i erase all that and if i installed new apps every reboot it's not there, I wanted to get it back to stock as new but i couldn't and here what i have tried :-
1-couldn't flash stock or custom recovery [failed (Remote : Not allowed)] cuz bootloader is locked, And i couldn't unlock bootloader .
-(after getting unlock code from HTCdev.com and installing it and after selecting yes on the phone to unlock bootloader, phone just reboots)
2-tried to flash RUU (3.30.651.2 & 4.25.651.14) Wizard while phone was on fastboot mode
https://onedrive.live.com/?cid=AC7B...23EA2B!345&parId=AC7BFAC4E523EA2B!341&o=OneUp
-Phone couldn't boot into bootloader while on fastboot mode so it reboots regularly.
3-tried to flash RUU (3.30.651.2 & 4.25.651.14) wizard while phone was on
https://onedrive.live.com/?cid=AC7B...23EA2B!344&parId=AC7BFAC4E523EA2B!341&o=OneUp
-did the first steps ok but again when wizard is waiting for bootloader while phone was in fastboot mode, it just reboot regularly.
4-tried renaming another (4.25.651.14) RUU to 0P6BIMG.zip and put it on sd-card and went to Hboot.
https://onedrive.live.com/?cid=AC7B...23EA2B!342&parId=AC7BFAC4E523EA2B!341&o=OneUp
-after clicking yes to confirm the update, Phone rebooted in the middle of the steps .
5-tried flashing same 0P6BIMG.zip from recovery mode.
https://onedrive.live.com/?cid=AC7B...23EA2B!347&parId=AC7BFAC4E523EA2B!341&o=OneUp
-after 3 mins of hope crushed by verifying update package.... - Installation aborted....
6-tried flashing RUU.zip via fastboot
https://onedrive.live.com/?cid=AC7B...23EA2B!346&parId=AC7BFAC4E523EA2B!341&o=OneUp
-phone just reboots regularly when trying to reboot RUU .
7-I contacted HTC support and after givin 'em alot of images and getvar they told me that my phone was modified in two ways (s-off) &
(Recovery tool) , They are telling me that (i must install the android recovery tool once again before proceeding) !! and i need to search on this site (Xda) for the stock recovery, but i think i have the stock recovery tool, and i can't flash any recovery because bootloader is locked, So is there any other way to flash recovery.
-here is some photos and getvar
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!339&parId=root&o=OneUp
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!350&parId=root&o=OneUp
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.08.20.0612_4
version-cpld: None
version-microp: None
version-main: 3.30.651.2
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: **************
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: d4c3cae5
hbootpreupdate: 11
gencheckpt: 0
Devil_55 said:
1-couldn't flash stock or custom recovery [failed (Remote : Not allowed)] cuz bootloader is locked, And i couldn't unlock bootloader .
-(after getting unlock code from HTCdev.com and installing it and after selecting yes on the phone to unlock bootloader, phone just reboots)
Click to expand...
Click to collapse
Since you are s-off, try this method to unlock bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
Although I don't see the point in flashing stock recovery. It won't help your present situation (return to full stock).
What recovery is currently on the phone, stock or TWRP? What happens when you try to select Recovery from the bootloader menu?
Devil_55 said:
2-tried to flash RUU (3.30.651.2 & 4.25.651.14) Wizard while phone was on fastboot mode
https://onedrive.live.com/?cid=AC7B...23EA2B!345&parId=AC7BFAC4E523EA2B!341&o=OneUp
Click to expand...
Click to collapse
Can't see what you are trying to flash. It says "This item may not exist or is no longer available".
All Sprint RUUs are available here: https://forum.xda-developers.com/showthread.php?t=2729173
Thanks for the fast reply
redpoint73 said:
Since you are s-off, try this method to unlock bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
-I already Tried that several times but not working still locked
redpoint73 said:
Although I don't see the point in flashing stock recovery. It won't help your present situation (return to full stock).
Click to expand...
Click to collapse
-Yea but How to return to full stock
redpoint73 said:
What recovery is currently on the phone, stock or TWRP? What happens when you try to select Recovery from the bootloader menu?
Click to expand...
Click to collapse
-Stock Recovery, I attached a photo of the recovery,
-If i select recovery from the bootloader menu it gives me black screen with red triangle, Then i hold Vol up and click power once
redpoint73 said:
Can't see what you are trying to flash. It says "This item may not exist or is no longer available".
Click to expand...
Click to collapse
-I was flashing 3.30.651.2 RUU.exe while phone was on bootloader mode, The thing is if the phone is on bootloader mode and wizard is showing that it's (Waiting for bootloader...) ,then phone reboots regularly and nothing changed
-And if phone was just on with activated usb debugging and i opened RUU.exe, the first step is to get to bootloader mode and then will send all the data of the RUU, Then it will show it's (Waiting for bootloader....) again, But because the phone is already in bootloader mode, The phone will just reboot as i showed in step 3, so when wizard is trying to go bootloader mode while phone is on bootloader mode that's what make it doesn't work.
-This is another link of Step 2 (Flashing 3.30.651.2 RUU.exe) while on fastboot mode
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!351&parId=root&o=OneUp
-I read abt Nandroid backup and how it takes an exact image of everything on the phone, could it be that someone did that backup and every time phone reboots it restores that backup, and if so how to know if something like that is activated.
Does the phone work normally in OS (but just won't wipe properly)? If you are trying to return to "stock", than what condition is it in now? Is it stock ROM, or otherwise?
Devil_55 said:
-Stock Recovery, I attached a photo of the recovery,
-If i select recovery from the bootloader menu it gives me black screen with red triangle, Then i hold Vol up and click power once
Click to expand...
Click to collapse
So I'm confused if you have stock recovery installed already; why you are trying to install stock recovery, or what that will do for you.
Devil_55 said:
-I read abt Nandroid backup and how it takes an exact image of everything on the phone, could it be that someone did that backup and every time phone reboots it restores that backup, and if so how to know if something like that is activated.
Click to expand...
Click to collapse
No, that isn't how a nandroid works. You need a custom recovery like TWRP to make a nandroid. And it will only restore if you manually boot into TWRP, and restore it. None of it happens "automatically" like you are describing.
---------- Post added at 03:38 PM ---------- Previous post was at 03:38 PM ----------
Devil_55 said:
-I already Tried that several times but not working still locked
Click to expand...
Click to collapse
Any type of error messages when you try to run the command to unlock the bootloader using the command prompt method?
redpoint73 said:
Does the phone work normally in OS (but just won't wipe properly)? If you are trying to return to "stock", than what condition is it in now? Is it stock ROM, or otherwise?
Click to expand...
Click to collapse
-yes it works fine in OS but won't wipe at all, I can install\uninstall apps , delete or add pictures but as soon the phone is rebooted everything gets back the way it was,
-I don't know if it has stock Rom installed on it, I just want to delete everything and start over with unmodified OS
redpoint73 said:
So I'm confused if you have stock recovery installed already; why you are trying to install stock recovery, or what that will do for you.
Click to expand...
Click to collapse
-sry for the confusion, I just thought if i could flash stock one by myself i could get around this situation somehow and at the same time the HTC support told me i don't have Stock recovery and i should flash stock one as the first step.
redpoint73 said:
No, that isn't how a nandroid works. You need a custom recovery like TWRP to make a nandroid. And it will only restore if you manually boot into TWRP, and restore it. None of it happens "automatically" like you are describing.
Click to expand...
Click to collapse
-Thanks for the clarification
redpoint73 said:
Any type of error messages when you try to run the command to unlock the bootloader using the command prompt method?
Click to expand...
Click to collapse
-Nope, I followed the guide then after adb reboot bootloader, Still locked
Devil_55 said:
at the same time the HTC support told me i don't have Stock recovery and i should flash stock one as the first step.
Click to expand...
Click to collapse
HTC support is wrong on that (or they are misunderstanding). Black screen with red triangle is the stock recovery. Re-installing the stock recovery isn't going to change or help anything.
Based on the widespread (largely storage-related) issues you've described (wiped user data reappearing, bootloader won't unlock despite multiple methods, RUUs won't flash) I tend to think this is an emmc failure, which you can't do much about. And based on the wide variety of options/workarounds you've tried so far (and failed) I don't personally see much (if any) options moving forward, unfortunately. If I think of anything else to try, I'll certainly let you know.
Thanks for your time and effort
Devil_55 said:
-yes it works fine in OS but won't wipe at all, I can install\uninstall apps , delete or add pictures but as soon the phone is rebooted everything gets back the way it was,
Click to expand...
Click to collapse
I've got the same issue, it's eMMC failure and you have to replace with the new one.
My topic: https://forum.xda-developers.com/htc-one-m8/help/help-wifi-off-t3762549
NoIP said:
I've got the same issue, it's eMMC failure and you have to replace with the new one.
Click to expand...
Click to collapse
How can i replace the emmc! Do u have a link for the guide?
Also is there any information i should take note of before deciding what emmc i should go with?
redpoint73 said:
HTC support is wrong on that (or they are misunderstanding). Black screen with red triangle is the stock recovery. Re-installing the stock recovery isn't going to change or help anything.
Based on the widespread (largely storage-related) issues you've described (wiped user data reappearing, bootloader won't unlock despite multiple methods, RUUs won't flash) I tend to think this is an emmc failure, which you can't do much about. And based on the wide variety of options/workarounds you've tried so far (and failed) I don't personally see much (if any) options moving forward, unfortunately. If I think of anything else to try, I'll certainly let you know.
Click to expand...
Click to collapse
I just found out that on the back of the phone .. Model : 0P6B100 !!!
Devil_55 said:
I just found out that on the back of the phone .. Model : 0P6B100 !!!
Click to expand...
Click to collapse
You can't trust what is on the back cover. We've often seen these swapped to remove US carrier logos. All indications on your getvar point to the "internals" of the phone (which is the important factor - and what you need to go by) being the Sprint version M8. It's very common to see the Sprint version to have its back cover replaced in order to remove the Sprint logo and sell it as an "unbranded" version (which it really is not).
---------- Post added at 09:03 AM ---------- Previous post was at 08:54 AM ----------
Devil_55 said:
How can i replace the emmc! Do u have a link for the guide?
Also is there any information i should take note of before deciding what emmc i should go with?
Click to expand...
Click to collapse
I'm not really a "hardware" guy. I can never seem to perform any hardware-related repairs on small electronics; despite being an engineer (very technically-minded) and all-around very careful about doing things (too obsessive about the minutia, in fact). But I have to say, changing emmc seems really delicate, and will not turn out well unless you are already experienced with this type of thing, and good at it. As far as I can tell, it involves heating up the chip, then installing the new one and "reflowing" the solder points. All of which looks really tricky, with a bunch of things that can go wrong along the way.
Might be better to have a repair shop do it, or change the whole motherboard, if you really want to go through the effort of hardware repairs to get this phone working again.
If you do change the emmc (or have a shop do it) I would only recommend using one intended for the Sprint M8. If you look at the thread NoIP linked, you will see I'm trying to help him with a weird emmc-motherboard combo, which I am not sure is fixable.
Thanks mate for explaining that

HTC 10 does not detect SIM card after battery and LCD replacment.

Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.
theteju said:
Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.
Click to expand...
Click to collapse
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# HT69XBN00387
it is GSM unlocked.
andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
Now I know what you asking. may be this is proper answer.
fastboot getvar all
kernel: lk
product: htc_pmewl
version: 1.0
max-download-size: 1578400000
serialno: HT69XBN00387
slot-count: 0
current-slot:
imei: 354259077770388
version-main: 3.16.617.2
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PS650000
cid: BS_US001
Click to expand...
Click to collapse
theteju said:
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# YOU CAN HIDE THIS.. NOT NEEDED AND SPECIFIC TO YOUR DEVICE.
it is GSM unlocked.
Click to expand...
Click to collapse
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
theteju said:
Now I know what you asking. may be this is proper answer.
Click to expand...
Click to collapse
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
andybones said:
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Click to expand...
Click to collapse
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,
theteju said:
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,
Click to expand...
Click to collapse
You're so very welcome.
Trust me, I know how tough it can be to fully understand an htc device and it's workings. Once you start to get into it like you have now, I'm sure you came out with some knowledge, so I'm more than happy to help.
I didn't realize you were still on Android 7. You're on 8 now because the RUU I gave you was android 8.(don't try and downgrade. You can but it's not as easy as flashing the android 7 ruu)
The ruu contains everything to make your device stock again, including stock system, stock kernel, stock recovery.
Flashing ruu doesn't touch an soff flag nor bootloader lock.(boot on into download mode and check it out). But even if it did lock it, which won't ever happen, you can always re-unlock bootloader.
It's only us Verizon users who suffer by blocking us from unlocking. NOT COOL VERIZON!!!
You just need to flash twrp again (get latest version), then flash roms as you desire.
I suggest any recent Pie rom. Thanks to dev Fagyi he has really made this phone great again. He maintains Stock lineage 16 is awesome, and theirs a few roms out based on his lineage, including my crdroidandroid rom. Also Fagyi has I think 2 roms based on AOSP rather lineage.
If you want Sense then LeeDroid is the ROM you want.
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.
theteju said:
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.
Click to expand...
Click to collapse
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:
andybones said:
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:
Click to expand...
Click to collapse
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.
theteju said:
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.
Click to expand...
Click to collapse
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!
andybones said:
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!
Click to expand...
Click to collapse
I am temperory using iphone 4s. Life is in slowMotion mode using that phone since two weeks. LOL
I am eyeing Nokia 7.1. What are your thoughts?
any comment on Mi9?

Categories

Resources