Develop Bugs

[Q] [Solved] unrooting?

I've read around on the forums here and other places but some of it doesn't make any sense to me and I watched a YouTube video about unlocking the bootloader then rooting the phone unfortunately i didn't do a nandroid back up before rooting (using supersu) and i am wondering if it is possible to flash to a stock rom so that in the future i can ota update in the future.
here is what i have at the moment
international phone (im on o2 in the uk anyway)
android version: 5.0.2
Software number: 1.32.401.15
unlocked bootloader
rooted
s-off
SuperCID
Also if someone can guide me through this i would be extremely thankful.
Thanks for your help guys.

You would need to either get a nandroid of your particular carriers ROM, or download the correct RUU from HTC.

BillTheCat said:
You would need to either get a nandroid of your particular carriers ROM, or download the correct RUU from HTC.
Click to expand...
Click to collapse
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?

linton85 said:
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
Click to expand...
Click to collapse
I have no idea, since you haven't told us what version your phone is. I think you ought to wait for feedback from someone else who can advise you better.

linton85 said:
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
Click to expand...
Click to collapse
Yes your s-off you can use those RUU

hmm i cant seem to use them, i go to flash it then i get this;
Code:
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot oem rebootRUU
...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot flash zip 0PJAIM
G.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (88044 KB)...
OKAY [ 6.331s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 8.430s
any idea?

linton85 said:
hmm i cant seem to use them, i go to flash it then i get this;
Code:
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot oem rebootRUU
...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot flash zip 0PJAIM
G.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (88044 KB)...
OKAY [ 6.331s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 8.430s
any idea?
Click to expand...
Click to collapse
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.

it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
ok managed to flash it back successfully couple of things though:
i couldnt copy the file when it was named 0JAIMPG.ZIP to the sd card (was in the phone not sure if i had to take it out and put it on)
it still says "software status modified" "unlocked" "s-off" afaik you can't get software status back to normal, to get unlocked back to locked would mean me relocking the bootloader and s-off shouldnt matter with ota update?
if i was to now re-install twrp but before rooting i took a nandroid backup would this allow me to get ota updates if i then restore to that after rooting or would one of the things above prevent me?
if not is there anyway i can get ota updates again?

linton85 said:
ok managed to flash it back successfully couple of things though:
i couldnt copy the file when it was named 0JAIMPG.ZIP to the sd card (was in the phone not sure if i had to take it out and put it on)
it still says "software status modified" "unlocked" "s-off" afaik you can't get software status back to normal, to get unlocked back to locked would mean me relocking the bootloader and s-off shouldnt matter with ota update?
if i was to now re-install twrp but before rooting i took a nandroid backup would this allow me to get ota updates if i then restore to that after rooting or would one of the things above prevent me?
if not is there anyway i can get ota updates again?
Click to expand...
Click to collapse
If you used the htc_fastboot to flash it will not reset the modified tag
you have to do it yourself >> http://forum.xda-developers.com/one-m9/general/how-to-restore-software-status-original-t3092882
To set unlocked to locked you have to do this >> http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
and yes, you can get OTA update with unlocked and s-off

Thank you so much for taking the time to help me out and providing links I am very grateful

clsA said:
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
Do I rename this file to fastboot.exe and delete the original fastboot?
I seem to always get the 90 pre-update FAIL when I flash different firmware.

bigp951 said:
Do I rename this file to fastboot.exe and delete the original fastboot?
I seem to always get the 90 pre-update FAIL when I flash different firmware.
Click to expand...
Click to collapse
Just leave it as htc_fastboot. They can coexist.
Dude, what's it tell you after you get the error 90? Flash again immediately, right? EVERYONE gets error 90 when flashing firmware. It's a pre-check before actually doing anything. If you're phone reboots to OS after getting 90, then just leave your command/terminal window open and put your phone back in download mode and re-run the exact same command to start the flash again.

jollywhitefoot said:
Just leave it as htc_fastboot. They can coexist.
Dude, what's it tell you after you get the error 90? Flash again immediately, right? EVERYONE gets error 90 when flashing firmware. It's a pre-check before actually doing anything. If you're phone reboots to OS after getting 90, then just leave your command/terminal window open and put your phone back in download mode and re-run the exact same command to start the flash again.
Click to expand...
Click to collapse
That's what I have been doing.... Did not know EVERYONE gets that error. Thanks for the info though. From what I read elsewhere is that the htc_fastboot will reboot back into download mode instead of os. That's why I mentioned it.

bigp951 said:
That's what I have been doing.... Did not know EVERYONE gets that error. Thanks for the info though. From what I read elsewhere is that the htc_fastboot will reboot back into download mode instead of os. That's why I mentioned it.
Click to expand...
Click to collapse
No problem bro. I think I've gotten reboots to is using HTC_fastboot, too.

clsA said:
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
Sir After installing 5.1 update my phone got stuck at boot screen.
Now I am unable to boot into recovery. Also locked My bootloader accidentally. While trying to flash a zip through fastboot I am getting below error. Could you please help me out.
OTA_HIMA_UHL_L50_SENSE70_hTC_Asia_HK_1.40.708.9-1.32.708.15_R1_release_436199

amit_coolcampus said:
Sir After installing 5.1 update my phone got stuck at boot screen.
Now I am unable to boot into recovery. Also locked My bootloader accidentally. While trying to flash a zip through fastboot I am getting below error. Could you please help me out.
OTA_HIMA_UHL_L50_SENSE70_hTC_Asia_HK_1.40.708.9-1.32.708.15_R1_release_436199
Click to expand...
Click to collapse
I'm sorry to tell you but if you updated to 5.1 and did not go into developer options and check to allow bootloader unlock, and then locked your bootloader theirs is nothing you can do but flash a RUU. Are you s-off ? If no your most likely stuck.
I have no idea what the file name you posted above is for... Edit: This may be the help you need >> https://www.androidfilehost.com/?fid=24052804347810886

Sir I am S-On. I am trying to flash a RUU but getting error everytime. Tried from SD card. tried via fastboot.
Also my M9 is HTC Asia (Hongkong). So I have tried flashing below one. Can I try flashing TW version given by you??
https://www.androidfilehost.com/?fid=24269982087001508
clsA said:
I'm sorry to tell you but if you updated to 5.1 and did not go into developer options and check to allow bootloader unlock, and then locked your bootloader theirs is nothing you can do but flash a RUU. Are you s-off ? If no your most likely stuck.
I have no idea what the file name you posted above is for... Edit: This may be the help you need >> https://www.androidfilehost.com/?fid=24052804347810886
Click to expand...
Click to collapse

amit_coolcampus said:
Sir I am S-On. I am trying to flash a RUU but getting error everytime. Tried from SD card. tried via fastboot.
Also my M9 is HTC Asia (Hongkong). So I have tried flashing below one. Can I try flashing TW version given by you??
https://www.androidfilehost.com/?fid=24269982087001508
Click to expand...
Click to collapse
With S-ON it's not possible to downgrade or to flash RUUs that were made for other SKUs (Taiwan is 709 and Hongkong is 708). Since you can't use the RUU in my AFH folder because it's older than your actual firmware and there is no other RUU for the SKU 708 (or at least none I know) than that one you linked your only hope might be the RUU service on llabtoofer's website.
Edit @clsA: That file amit_coolcampus mentioned earlier is one of the OTAs for the Hongkong version of the M9.

Flippy498 said:
With S-ON it's not possible to downgrade or to flash RUUs that were made for other SKUs (Taiwan is 709 and Hongkong is 708). Since you can't use the RUU in my AFH folder because it's older than your actual firmware and there is no other RUU for the SKU 708 (or at least none I know) than that one you linked your only hope might be the RUU service on llabtoofer's website.
Edit @clsA: That file amit_coolcampus mentioned earlier is one of the OTAs for the Hongkong version of the M9.
Click to expand...
Click to collapse
Thanks Sir. Can I get this repaired if i visit HTC service center? Will they be having 2.11.708.30 RUU?

amit_coolcampus said:
Thanks Sir. Can I get this repaired if i visit HTC service center? Will they be having 2.11.708.30 RUU?
Click to expand...
Click to collapse
Honestly, I don't know. I've always been able to recover my phones without the help of the HTC service center or the RUU service. My guess is that the RUU service might be cheaper but that's only a guess. Maybe someone else here had to use one or both of these services and can share his/her experience...

Unrooting HTC One M9 with S-On without backup

First of all, I really have to apologize for making this thread - after all the effort people here put to ensure that everyone could be able to handle their phones safely, after many hours of trials and errors, I have to ask for your help.
HTC One M9 that I'm dealing with here is S-On. I need to get the latest OTA update for it to update it with Android 6.0 - so forcing the update will be completely good solution.
Bootloader is currently unlocked and the phone is rooted.
It has currently firmware version 1.32.401.15 (Europe)
I am currently not able to flash the stock firmware I found here for my version through SD card, I'm guessing that one of the previously mentioned conditions could be prerequisite for this to work properly.
Any help would be extremely appreciated.

@KamilaS you have the WWE edition of the One M9 as far as I can see from your firmware number. I'd advise to download the RUU for your device and flash it via PC to go back to stock and apply the OTAs up to Android M.
Here you go:
1) download this RUU
2) reboot to bootloader and relock it
3) apply above downloaded *.exe
If you got any further questions feel free to ask!
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Don't use that RUU. That version isn't able to receive OTAs. You can find a RUU for the latest WWE firmware (2.10.401.1) in this thread. But there is no official Android M OTA at the moment.

Flippy498 said:
Don't use that RUU. That version isn't able to receive OTAs. You can find a RUU for the latest WWE firmware (2.10.401.1) in this thread. But there is no official Android M OTA at the moment.
Click to expand...
Click to collapse
I used it in the past and got the OTA to 2.10.401.1 without any problems.
Of course there always is the second option to use a RUU.zip...
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

HTCNerdYoda said:
I used it in the past and got the OTA to 2.10.401.1 without any problems.
Of course there always is the second option to use a RUU.zip...
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I've tested every RUU for the SKU 401 when I created my TWRP backup collection and those for 1.32.401.15R2 and 1.32.401.17 were not able to receive or install OTAs.

Flippy498 said:
I've tested every RUU for the SKU 401 when I created my TWRP backup collection and those for 1.32.401.15R2 and 1.32.401.17 were not able to receive or install OTAs.
Click to expand...
Click to collapse
Weird as in my case everything went without any problems. But that's something one could dig into and be discussed in another thread.
Hope we help the OP first of all
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Flippy498 said:
I've tested every RUU for the SKU 401 when I created my TWRP backup collection and those for 1.32.401.15R2 and 1.32.401.17 were not able to receive or install OTAs.
Click to expand...
Click to collapse
Only certain regions got 1.32.401.17 update while rest stayed on .15

liam_davenport said:
Only certain regions got 1.32.401.17 update while rest stayed on .15
Click to expand...
Click to collapse
Yeah, I know that. I didn't want to get too OT in my last post. If I remember correctly only CID HTC__Y13 HTC__J15 got that update and since we don't know the OPs CID and all other ones cannot receive OTAs with that RUU I would say it's better not to recommend using that RUU.

Thanks a lot for such fast replies
Am I understanding then correctly, that locking again bootloader will be necessary to flash firmware?
In such case, will "fastboot oem lock" command in download mode be sufficient?

Re-locking is only needed if you want to flash a RUU.exe. The fastboot oem lock command would be sufficent in that case. But as said before I wouldn't recommend using the 1.32.401.17 RUU (which is the only RUU.exe for the SKU 401).
TL;DR: Don't relock.

I am not eager to use executable file to flash the firmware, .zip option would be great - either through SD card or fastboot commands. But seeing as I keep failing with the update through both options I am assuming, that I'm stil doing something wrong. Are there any other prerequisites that I haven't yet consider? Is relocking OEM not necessary then when using ZIP options?

Relocking is definitely not needed. Did you follow the instructions in my google sheet? If yes what kind of error was stated when you tried to flash the RUU in Download Mode? What kind of error was stated when the fastboot flash failed?

I have just tried once again with the RUU.zip file that I have found. I can see that your google sheet points to another RUU.zip file, that I will try next on the SD card and see if I have better luck with it.
In the meantime, this is the output that I have from trying update in fastboot:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
OKAY [ 1.003s]
writing 'zip'...
(bootloader) HOSD CL#506785
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.009s
From what I googled, it can be avoided when updating through SD card, but then again the errors aren't very descriptive that way

KamilaS said:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
OKAY [ 1.003s]
writing 'zip'...
(bootloader) HOSD CL#506785
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.009s
Click to expand...
Click to collapse
Which fastboot.exe are you using? Or better did you use the htc_fastboot? The first line of the error regarding max download size happens quite often if someone uses fastboot from Android sdk instead of htc_fastboot. htc_fastboot can be found in sneakyghost's thread.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Ok, thank you very much! With your help I was able to finally figure out the way that worked on my device
I followed your suggestion and used htc_fastboot - as expected, the fastboot that I have used so far with other devices was not the best solution here and I haven't really realized before that people could be using different one.
Together with the RUU file that you have linked in your google sheet (that for some reason could not be copied on SD card) I have managed to install firmware successfully on the device and now I'm installing the latest OTA update
Thank you once again for all your help, is there anything that I can thank contributors by liking their replies?

KamilaS said:
Ok, thank you very much! With your help I was able to finally figure out the way that worked on my device
I followed your suggestion and used htc_fastboot - as expected, the fastboot that I have used so far with other devices was not the best solution here and I haven't really realized before that people could be using different one.
Together with the RUU file that you have linked in your google sheet (that for some reason could not be copied on SD card) I have managed to install firmware successfully on the device and now I'm installing the latest OTA update
Thank you once again for all your help, is there anything that I can thank contributors by liking their replies?
Click to expand...
Click to collapse
You're welcome. That's what this forum is for.
No need to hit the thanks button. It's the thumbs up below the post

Really Bricked m9... Please Pro help required.

My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff

nobody?? :'(

Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.

computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1

Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?

Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.

Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up

Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).

Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!

im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?

logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.

Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work

Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk

I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution

Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...

bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"

Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.

copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse

bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU

So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip

Soft Bricked HTC One M9! Please help!

Dear all,
I recently unlocked bootloader, rooted and flashed CandySix ROM on my M9. Everything was fine until I stupidily relock the bootloader (using fastboot oem lock). Then the phone can not boot into system and recovery also.
I tried to re-unlock again using the same method (Unlock_code.bin) from HTCdev. The cmd said success, i press Yes on the phone, however after reboot the status stayed the same "Relock". I did like 20 times but it was the same.
I also tried to flash many RUUs that i found but no hopes (maybe i didnt find the right one).
Now the phone stuck at download mode and bootloader mode, can't do anthing else.
Can anyone helps me how to fix this or to find the right RUU for my phone please? Many thanks.
Current status: Modified
***RELOCK***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.710.5
mid is 0PJA10000
cid is VODAP021

I think you need a new unlock token as when you relocked your bootloader it will need to generate a new one. Follow the unlock bootloader process from the beginning to see if you can unlock it again and go from there. Good luck.
Sent from my HTC 10 using XDA Labs

squ89r97 said:
I think you need a new unlock token as when you relocked your bootloader it will need to generate a new one. Follow the unlock bootloader process from the beginning to see if you can unlock it again and go from there. Good luck.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Thank you for your help. I tried that but no luck. Keep saying "Relocked". I really dont understand why????

1. unlock Bootloader
2. flash custom recovery
3. flash custom rom

babypopku said:
Dear all,
I recently unlocked bootloader, rooted and flashed CandySix ROM on my M9. Everything was fine until I stupidily relock the bootloader (using fastboot oem lock). Then the phone can not boot into system and recovery also.
I tried to re-unlock again using the same method (Unlock_code.bin) from HTCdev. The cmd said success, i press Yes on the phone, however after reboot the status stayed the same "Relock". I did like 20 times but it was the same.
I also tried to flash many RUUs that i found but no hopes (maybe i didnt find the right one).
Now the phone stuck at download mode and bootloader mode, can't do anthing else.
Can anyone helps me how to fix this or to find the right RUU for my phone please? Many thanks.
Current status: Modified
***RELOCK***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.710.5
mid is 0PJA10000
cid is VODAP021
Click to expand...
Click to collapse
U need a RUU with OS 2.9.710.5 or higher that hopefully contains your cid and mid.
By running it u will lose al your data.
@Flippy498 has one and needed instructions in his spreadsheet.
https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#

side_flip15 said:
1. unlock Bootloader
2. flash custom recovery
3. flash custom rom
Click to expand...
Click to collapse
The thing is I can not unlock bootloader at the moment. I dont know why. I tried the HTCdev process, everything runs smoothly but after reboot the phone still "RELOCKED". I've done many times and still the same. Help me pls

Fain11 said:
U need a RUU with OS 2.9.710.5 or higher that hopefully contains your cid and mid.
By running it u will lose al your data.
@Flippy498 has one and needed instructions in his spreadsheet.
https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#
Click to expand...
Click to collapse
Thank you. I tried that link. However, after download the RUU zip file, I cant flash it.
The error was
C:\Users\Man Phan\Desktop\platform-tools>fastboot flash zip 0PJAIMG.zip
load_file: could not allocate -1977527069 bytes
error: cannot load '0PJAIMG.zip'
I tried to use another adb, fastboot package and it said
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
OKAY [ 1.031s]
writing 'zip' 1/1...
(bootloader) HOSD CL#573756
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.058s
And I can not open that zip file as well, 7zip said it can not open the file as archive. I checked md5 the it matched. I dont know what happen to the file. I afraid the file is corrupted so I downloaded twice to check but still no hope.
Any other suggestions please!!

You can't flash RUUs with fastboot anymore since the M9. They became too big and the normal fastboot isn't able to handle them anymore. Either you use the SD card method which is described in my sheet or you look for htc_fastboot.
As a sidenote: You are aware that RUUs are encrypted and therefore can't get opened the way you normally open archives, aren't you? Winrar isn't able to do so at all and 7-zip has to use "right-click > open > #". Nevertheless you won't have any benefit from opening it.
Sent from my HTC One M9 using XDA Labs

After doing some stuff i didn't remember, the phone is now Unlocked. I can be able to flash a TWRP 3.0.0 and flash a CandySix ROM. All the process was smooth. The phone can boot normally now. Thank you guys.
However, there is no Sense on CandySix ROM. I really want to upgrade to another ROM with Sense but i can't due to my current firmware. I dont know how to upgrade the firmware for that. I can't make my S-off using Sunshine also. Any suggestions where to start? Thanks.

Did you try the SD card method I described in my google sheet? Or did you download the needed htc_fastboot files if you prefer the command line? I had no problems with flashing the 2.10.710.5 RUU when I created my backups for the SKU 710.
Or did you try to use the TWRP backup guide in my sheet?
Otherwise if you're willing to pay around 20 bucks you could use llabtoofer's RUU service. Either google or use the link in my spreadsheet.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Did you try the SD card method I described in my google sheet? Or did you download the needed htc_fastboot files if you prefer the command line? I had no problems with flashing the 2.10.710.5 RUU when I created my backups for the SKU 710.
Or did you try to use the TWRP backup guide in my sheet?
Otherwise if you're willing to pay around 20 bucks you could use llabtoofer's RUU service. Either google or use the link in my spreadsheet.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks I have contacted llabtoofer for help. So afraid to do myself. Have been wasted tons of time for this but still not have any luck. Anyway thank you for your help. My phone is now usable, i used the htc_flashboot method to unstuck it.

HTC one m9 flash RUU help
iHave a Sprint HTC One M9 currently stuck in boot loop displaying
"This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action."
I'm not sure of the CID nor firmware version(i'm sure it was the latest 3.41.651.4.) iForgot to backup my device before rooting(stupid iKnow.) I've already found the RUU for 3.41.651.4 it's saved to my SD card. iCan still reach bootloader, recovery&download mode, should iJust enter recovery&flash the RUU? iAlso have S-ON. iWould like to relock the bootloader&start the root process anew. iUsed TWRP 3.0.2 as well as Super SU 2.76 during my first initial attempt. I've already tried to lock the device once but when iType adb devices into the command window no device is displayed.
I'm not sure where to go from here. Can someone help?

[Optus M9] Need 3.50.710.1 RUU or the latest radio.img My SIM has vanished.

Hi guys,
I hope this is in the right forum. While the Ressurection Remix ROM broke my radio, my goal is to flash to stock so I can start again with a functioning radio and try something else.
The install went well: unlocked and installed TWRP just fine. The new ROM installed without a hitch but when it started I noticed that there was no SIM detected.
I found an RUU that looks to be the one I need: (0PJAIMG_HIMA_UHL_L50_SENSE70_hTC_Asia_AUS_1.32.710.16_Radio_01.01_U11440261_56.02.50306G_2_F_release_427214_signed ) and extracted the radio.img and used the scripts here to create an installable zip. But, then I read that I need S-Off and Sunshine says that my ROM is not stock enough to get S-Off... So I can not patch the radios in.
But when I try to install the RUU (relocked etc) it also fails as do the TWRP stock backups here
What am I missing?

Try restoring a stock nandroid backup from flippys thread and then get s off
ICE M9

Roobwz said:
Try restoring a stock nandroid backup from flippys thread and then get s off
ICE M9
Click to expand...
Click to collapse
Thanks, I'll give it a go in a couple hours and let you know how it goes.

ghostcorps said:
Thanks, I'll give it a go in a couple hours and let you know how it goes.
Click to expand...
Click to collapse
Do you mean the TWRP Stock Backups?
TWRP Restore can't see the zips and I can not extract them to the phone because the system images' are larger than 4gb. As far as I know, I can not flash a backup image over usb, if I could I would have much less trouble for sure.
Also, fastboot shows the version as:
Code:
#fastboot getvar version-main
version-main: 3.50.710.1

ghostcorps said:
Do you mean the TWRP Stock Backups?
TWRP Restore can't see the zips and I can not extract them to the phone because the system images' are larger than 4gb. As far as I know, I can not flash a backup image over usb, if I could I would have much less trouble for sure.
Also, fastboot shows the version as:
Code:
#fastboot getvar version-main
version-main: 3.50.710.1
Click to expand...
Click to collapse
Yes i meant stock nandroid backups. You can find them in flippys thread in the general forums
ICE M9

Roobwz said:
Yes i meant stock nandroid backups. You can find them in flippys thread in the general forums
ICE M9
Click to expand...
Click to collapse
Thanks for clarifying
Are there any Nandroid backups with a smaller system image? 4gb+ seems to render them useless for me
Now that I am at my PC I can show you some more logs:
(ROM.zip = 0PJAIMG_HIMA_UHL_L51_SENSE70_MR_hTC_Asia_AUS_2.9.710.5_Radio_01.04_U11440601_71.02.50709G_F_release_452741_signed.zip)
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
OKAY [ 1.008s]
writing 'zip' 1/1...
(bootloader) HOSD CL#761596
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_t
(bootloader) KTVsG
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 2.044s
I assume this is because the current software version (3.50.710.1) is newer than the RUU (2.9.710.5)?

ghostcorps said:
Thanks for clarifying
Are there any Nandroid backups with a smaller system image? 4gb+ seems to render them useless for me
Now that I am at my PC I can show you some more logs:
(ROM.zip = 0PJAIMG_HIMA_UHL_L51_SENSE70_MR_hTC_Asia_AUS_2.9.710.5_Radio_01.04_U11440601_71.02.50709G_F_release_452741_signed.zip)
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
OKAY [ 1.008s]
writing 'zip' 1/1...
(bootloader) HOSD CL#761596
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_t
(bootloader) KTVsG
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 2.044s
I assume this is because the current software version (3.50.710.1) is newer than the RUU (2.9.710.5)?
Click to expand...
Click to collapse
Correct, you cannot downgrade with a stock backup. You need s off and a RUU/firmware.zip.
You gotta find a backup that matches your firmware 100%
ICE M9

Roobwz said:
Correct, you cannot downgrade with a stock backup. You need s off and a RUU/firmware.zip.
You gotta find a backup that matches your firmware 100%
ICE M9
Click to expand...
Click to collapse
How do I get S-Off without a stock OS? Or can I possibly install the radio.img with S-On?
Otherwise I am pretty much screwed yeh?

ghostcorps said:
How do I get S-Off without a stock OS? Or can I possibly install the radio.img with S-On?
Otherwise I am pretty much screwed yeh?
Click to expand...
Click to collapse
Bro I'm not that into firmwares that aren't popular... but it cant make things worse to try to flash a custom sense Rom as leedroid or Ice. It's enough to just boot it to get soff. Either that or just stay on that rom.
ghostcorps said:
How do I get S-Off without a stock OS? Or can I possibly install the radio.img with S-On?
Otherwise I am pretty much screwed yeh?
Click to expand...
Click to collapse
ICE M9

Roobwz said:
Bro I'm not that into firmwares that aren't popular... but it cant make things worse to try to flash a custom sense Rom as leedroid or Ice. It's enough to just boot it to get soff. Either that or just stay on that rom.
ICE M9
Click to expand...
Click to collapse
I would stay on the ROM if I could get the radio.img installed. It works fine otherwise.
But you make a lot of sense. I will try some other ROMs and see if they work better with Sunshine.

Sunshines S-Off seems to like Ice more than Ressurection Remix but after shelling out $25US the app has been 'Unlocking' the phone for 15 minutes The progress bar is moving but it just starts again when it gets to the end.
I am going to work now so will just leave it and hope that it is done when I get home.

ghostcorps said:
Sunshines S-Off seems to like Ice more than Ressurection Remix but after shelling out $25US the app has been 'Unlocking' the phone for 15 minutes The progress bar is moving but it just starts again when it gets to the end.
I am going to work now so will just leave it and hope that it is done when I get home.
Click to expand...
Click to collapse
If it doesnt work, try viper. Read somewhere that their ROMs always works with sunshine.
Skickat från min HTC One M9 via Tapatalk

Sunshines S-Off worked with Ice
Now to see if the radio.img will actually fix my problem...

Nope.
I am going to do some more research on installing the radio.img, hopefully I am doing something wrong there.
If anyone can supply me with the latest Optus radio.img file, I would be eternally grateful

I had the same issue trying to flash Leedroid from the same firmware. After some research I installed thicklizards Minimillistic kernel from here:
http://forum.xda-developers.com/sprint-one-m9/development/kernel-minimillistic-t3321416
After it installed it fixed all my problems, still on Leedroid and radios working again. Just make sure you download the RC2 version and not the RC3.

cwf124 said:
I had the same issue trying to flash Leedroid from the same firmware. After some research I installed thicklizards Minimillistic kernel from here:
http://forum.xda-developers.com/sprint-one-m9/development/kernel-minimillistic-t3321416
After it installed it fixed all my problems, still on Leedroid and radios working again. Just make sure you download the RC2 version and not the RC3.
Click to expand...
Click to collapse
Thanks!
I have just finished updating it to the latest stock version so I can get a backup this time but, that sounds like a very promising solution
Why not RC3? I can't seem to find RC2.

ghostcorps said:
Thanks!
I have just finished updating it to the latest stock version so I can get a backup this time but, that sounds like a very promising solution
Why not RC3? I can't seem to find RC2.
Click to expand...
Click to collapse
In the end, I am back on stock and looking for something else to try. The root of the problem is that for whatever reason, and CM13 based mods seem to break my radio and only stock RUUs seem to fix it. I am going to try installing Ice over the stock ROM and seeing what happens.