[SOLVED] Please help... soft brick Bell M9 - One (M9) Q&A, Help & Troubleshooting

SOLVED UPDATE: I did some more reading. I took the Bell (BM) rom zip
(named "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip"), and renamed it to "0PJAIMG.zip".
Copied that to the root of a microSD card and put that into the phone.
Booted phone with VOLDOWN+POWER and the flash process began. It rebooted a couple of times during the process. It said to hit POWER to finish. After that, phone booted normally (like out-of-the-box again).
With that said, I still would like to have root... so would still appreciate any input as to what I did wrong below. Thank you!
Hello. I'm afraid I have messed my phone up a bit, and would really appreciate it if someone could help me out.
It's a Bell HTC One M9 (0PJA110), and it is (was?) on 5.0.2 Lollipop. According to the RUU EXE I just tried (unsuccessfully), it says it is an image version (or HTC system version) 1.32.666.6.
Here's what I did, from out-of-the-box. I just wanted root access so I could use Titanium Backup, so I read a bunch of threads to get started. I thought I had gathered enough knowledge, so I:
1) Unlocked bootloader via htcdev
2) Flashed "htc-one-m9-lollipop-twrp-2.8.7.0-hima.img" to recovery. (I chose this version because I read in some threads that version 3 or higher of twrp doesn't work well if it is flashed to a Lollipop phone).
3) Rebooted, went immediately into recovery (so that TWRP could ensure it doesn't get overwritten)
4) Then rebooted again, and went into recovery (to make sure TWRP was still there)
5) At this point, I should have let the phone boot normally, to make sure that was OK. But I did not... so I cannot tell if this is where my trouble began
6) Next, in TWRP, I flashed "SR1-SuperSU-v2.79-SR1-20161221223537.zip". It seemed to go well.
7) Reboot from TWRP.
8) Phone shows first HTC logo, then goes to a black screen (black but illuminated). That's it.
My next thing to try was this Bell TWRP zip from a nice post on here. Filename is "Stock_Bell_LP_5.0.1_1.32.666.30_TWRP.zip". I tried to flash it via TWRP but it failed right away (I do not have the exact output but can try again to get the text, it if that helps).
Naturally I was starting to get worried, so I immediately started looking for RUU's so I could start over.
1) I re-locked bootloader
2) I tried a generic RUU ("RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe") but it would not flash - I assume it is checking CID and knows it's not correct for my phone
3) I downloaded a Bell-specific zip from Androidruu ("0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426170_signed.zip", verified the MD5 matched whatever androidruu.com said it was.
4) Renamed the zip to rom.zip to make the next commands easier
5) Ran "fastboot oem rebootRUU", verified the RUU screen appeared, then "fastboot flash zip rom.zip"
It didn't work Here is the output:
Code:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (67085 KB)...
OKAY [ 4.791s]
writing 'zip'...
(bootloader) HOSD CL#493992
(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) ERR ZIP signature checking failed...
(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.552s
I wish I could try a Bell RUU exe... but I am having a hell of a time finding one.
Any advice would be appreciated (regarding anything I did wrong up above, or regarding how I can get myself out of this mess). Thank you for reading.

Download the latest RUU to your device. In dowload mode type fastboot oem rebootRUU. Entering the Htc screen, run RUU.exe.

Dark Stranger said:
Download the latest RUU to your device. In dowload mode type fastboot oem rebootRUU. Entering the Htc screen, run RUU.exe.
Click to expand...
Click to collapse
Thank you, but same result as my earlier attempt. The EXE itself can get the phone from bootloader mode/download mode into RUU mode, and it starts the process, but fails with "please get the correct rom update utility".
I assume it's because this RUU is not an exact match for my phone.

Related

[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...

HTC M8 Unable to flash ROM, RUU Error 155, 32 header error, etc

This is gonna be long, so BIG thanx in advance for reading this post.
I will give as much info as possible to let u guys better determine whats going on, be prepared for a long read.
I have been fiddling with android 4-5 years ago, but that's it, so I consider my self a noob.
here it goes...
1) I have purchased an "international ver. HTC M8 brand new" from amazon third party seller for 200.00 USD
2) came with many evidence showing it's not brand new, but well disguised to look like new. See details:
1. I can tell it's a resealed package from experience; cable is a generic one that tries to mimic the original HTC cable, and it only charges (no data transfer). The charge brick has no film and has micro scratches.
2. Phone has no carrier logo, boot screen has no carrier logo, system has no carrier bloatware. The firmware seems to be unlocked/developer, but the CID(T-MOB010) and MID(0P6B13000) of the phone is T-Mobile!
3. As a brand new phone, it came rooted and S-Off.
4. OTA update fails indicating device has been modified.
3) Coming from a marshmallow phone, I decided to manual upgrade to Android 6. I downloaded the unlocked/developer & T-Mobile RUU from HTC, but both update fails at the black screen with silver HTC logo. (I forgot to mark down the error code, since I'm still a bit rusty from couple of years not digging this deep.)
4) I went ahead and unlocked the bootloader through HTC dev, then performed the same RUU. Same result.
5) I setup adb, then performed CID and MID change to make it the Dev ver. (BS_US002 + 0P6B12000). Ran the same RUU, same result.
6) Then I extracted the zip from the RUU and placed it in the ext sd to flash in hboot. Result was an error of file being too big.
7) I installed TWRP recovery, used it to flash the zip, received error of extraction fail. performed RUU, same result as above, noticed the error 155.
8) Next at fastboot usb, performed command <fastboot flash zip 0P6BIMG.zip> ends up with FAIL and Remote: not allowed message.
9) Finally, I tried RUU mode. Ended with the 32 header error:
Code:
C:\fastboot-win>adb reboot bootloader
C:\fastboot-win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot-win>fastboot flash zip 0P6BIMG.zip
sending 'zip' (1537810 KB)...
OKAY [ 50.275s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 50.415s
C:\fastboot-win>
which according to Sneakyghost's post, he doesn't know what is the cause
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
I have dug through many xda post and google, but had no luck.
I felt pretty helpless and frustrated now, makes me wonder what is going on with this phone.
This is gonna be my last resort, pls if someone knows what's going on and how to fix this, teach me, Please!
feel free to ask about more info, I will try to explain in further details.
I give you the basic idea as I'm away from my PC.
1. To install the official marshmallow RUU exe, you need to fastboot flash its firmware first.
You should be able to find the official firmware in my thread linked in my signature on post #5
2. To fastboot flash a rom.zip, you need to use htc_fastboot not the generic fastboot which gave you the error.
Read this for 3 options on how to install rom.zip - http://forum.xda-developers.com/showpost.php?p=67314040&postcount=1749

Proper Pickle with M9

Hi hoping someone can help me - I've just wasted two days trying to get my phone to work again, but right now, it only goes to the bootloader.
I have HTC One M9, with S-ON, rooted, with TWRP bootloader installed. I can not get any ROMs to install at all - actually, they do install, just don't boot. I believe this is because I don't have the correct firmware version installed. I can't get any firmware to install. When trying to update firmware, I get;-
Code:
fastboot flash zip firmware_M9.ziptarget reported max download size of 800000000 bytes
sending 'zip' (61607 KB)...
OKAY [ 5.419s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
I think this is because of the S-ON.
Can someone please help me, otherwise I'm going to have to throw this thing in the bin, and buy a new phone?
Thanks, Seth
Ok - so I've progressed, in as much as I've managed to put an old unofficial copy of CM12 on it. This has at least got me up and running.
Now need to get it back to Stock so I can patch firmware, and then install latest version of CM13.
Only, all the guides I read, say to flash Stock you need S-OFF - which I can only achieve by running Sunshine unlock - but I can't run Sunshine Unlock on this unofficial version of CM12.
Does anyone have any ideas they can throw my way? Thanks
SethHelstrip said:
Hi hoping someone can help me - I've just wasted two days trying to get my phone to work again, but right now, it only goes to the bootloader.
I have HTC One M9, with S-ON, rooted, with TWRP bootloader installed. I can not get any ROMs to install at all - actually, they do install, just don't boot. I believe this is because I don't have the correct firmware version installed. I can't get any firmware to install. When trying to update firmware, I get;-
Code:
fastboot flash zip firmware_M9.ziptarget reported max download size of 800000000 bytes
sending 'zip' (61607 KB)...
OKAY [ 5.419s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
I think this is because of the S-ON.
Can someone please help me, otherwise I'm going to have to throw this thing in the bin, and buy a new phone?
Thanks, Seth
Click to expand...
Click to collapse
Buddy once u install the rom, take the boot.img frm the rom zip file & flash it via adb in bootloader mode it will flash evn if ur s-on, custom roms need their respective boot.img files to be flashed when s-on in case of s-off its done by twrp or cwm recovery hope it helps
Hi Seth,
So the great news is that you do not need to be S-OFF to upgrade your firmware, which is what it sounds like you need to do.
Unfortunately, you can't take an OTA update, so you need to flash an RUU. While this will reset your phone (wiping everything but your SD card), it will also get your phone up to date.
Do you know which variant of the M9 you have? Once you get that information, you can use download the appropriate RUU and flash it to your phone. I've included some links below that are helpful - I especially recommend Flippy498's Google sheet, which has almost everything you need (with instructions!) to update your firmware.
Peace,
Computerslayer
Useful links for modding your HTC M9
Flippy498's Google Sheet
- the end-all, be-all resource for HTC M9 restoration
SKU-, CID- and MID-List by Sneakyghost and Behold_this
- a spreadsheet for using your CID & MID to identify your phone
HTC Sync Manager
- installs the necessary drivers & ADB tools for the HTC M9
Instructions for obtaining your CID, MID & software version on Windows:
a. Install HTC Sync Manager (this will install the necessary drivers & ADB tools)
b. Boot your phone into download mode (from a powered off state, turn on by holding the POWER+DOWNVOL)
c. Connect your phone to your PC
d. Open a command prompt window
e. Navigate to the ADB tools folder, typically C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
- assuming the path is correct, you can cut & paste this command into your terminal: cd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
f. Execute the following command in a terminal (command prompt): fastboot getvar all
g. Copy the lines that mention product, version-main, mid, and cid.
still sinking....
Thanks for the info guys. So I decided the best path was to RUU back to Stock then upgrade firmware OTA.
So, I tried to connect phone to HTC Sync Manager, but get the dreaded USB can't connect 170 error - even though the OS can see the phone, and its memory card fine.
So I decided to try Ubuntu to extract the RUU, so I can just patch it on SD card. However, I can't get the unruu program to compile properly, because its got some error with the required version of unshield.
So I'm at a dead-end, and resisting putting a hammer through the screen of this phone, which has now cost me about 4 days worth of effort - and still doesn't work.
The only thing I've managed to get working on it so far, is a crappy unofficial copy of CM12 - that crashes about 15-20 times a day.
Can anyone please offer me some advice, or a stock rom.zip for an unlocked m9?
SethHelstrip said:
Thanks for the info guys. So I decided the best path was to RUU back to Stock then upgrade firmware OTA.
So, I tried to connect phone to HTC Sync Manager, but get the dreaded USB can't connect 170 error - even though the OS can see the phone, and its memory card fine.
So I decided to try Ubuntu to extract the RUU, so I can just patch it on SD card. However, I can't get the unruu program to compile properly, because its got some error with the required version of unshield.
So I'm at a dead-end, and resisting putting a hammer through the screen of this phone, which has now cost me about 4 days worth of effort - and still doesn't work.
The only thing I've managed to get working on it so far, is a crappy unofficial copy of CM12 - that crashes about 15-20 times a day.
Can anyone please offer me some advice, or a stock rom.zip for an unlocked m9?
Click to expand...
Click to collapse
If you can pull you CID & MID, it'll be easy to identify which RUU you need. Most are easily found online.
So more progress. Having relocked my bootloader, I am now able to get the HTC RUU exe to connect to the phone from Windows. Only problem now is that I'm getting the
ERROR [155]: UNKNOWN ERROR
this makes me think I've got the wrong RUU. I'm pretty sure I've got the correct SKU, but not sure about the rest of it. From running fastboot getvar all I get;-
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
all:
And I'm using the
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4.exe
Can someone please help me - I now have a phone that won't go beyond the bootloader. Thanks
Ok, so I think the problem here, is the RUU I have is a downgrade from the existing version. With that in mind, can someone please help me out massively by pointing me in the direction of the correct RUU?
Thanks again.
https://www.google.com/url?q=https:...835000&usg=AFQjCNH9n1vZCmPvw5wWJ10C1wFJqx6YYA
Use this. Rename it to 0PJAIMG.zip copy it to your externel sd card. Reboot to download mode and press vol up than wait. Your phone will have latest firmware with 6.0
awesome - thanks for your help

Getting back to stock for OTA update

Hello fellow XDA users!
I just bought my m8 and it came with Software status modified, bootloader unlocked, philz touch, S-on but Super CID.
The problem now is that i can't OTA and it is still in kitkat
So I started to work on it tonight, and I can't get it back to stock :
I have flashed TWRP, made a boot backup to create necessary folders, and downloaded a stock nandroid backup for my main version, 3.28.401.6.
Wiped the phone, restored the rom, flashed stock recovery and here in bootloader my software status is still modified, so no OTA possible.
Suppose it has something to do with superCID, but i can't modify it anymore as I'm not s-off and I don't know what is the stock CID for the phone, just bought it.
Sorry to create another boring thread about OTA updates btw, but I just can't understand what I'm doing wrong here (coming from a samsung device, but I've been reading a lot here, and still no luck about my situation.)
http://forum.xda-developers.com/showthread.php?t=2701376 this is the thread where I downloaded the Nandroid, if it has any importance... It is the one rooted but which has apparently no effect on OTA
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845 this seems interesting as I could maybe flash a RUU of same version to become unmodified but i'll ask you before doing anything stupid
Thank you all for your future answers
EDIT : Here are info from getvar all if you need (removed serialno and imei)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
WoBble12 said:
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) security: on
Click to expand...
Click to collapse
With the above current CID/MID ... you can only update to Marshmallow either with T-MOB US RUU or Developer Edition RUU as both work on MID 0P6B13000
You current software 3.28.401.6 won't do any good as that is workable for OTA when your MID is 0P6B10000
So if you want a EU version, you need to spend USD25 to S-Off the device, else just go for Developer Edition RUU.
Step 1 : install 6.12.1540.4 firmware
You can get the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Step 2 : install 6.12.1540.4 RUU
Download : http://www.htc.com/us/support/htc-one-m8/news/
Ok, thank you for the quick reply!
I was mistaken by the back plate of the device saying OP6B100, so didn't verify the mid in the adb log...
Now for a few questions, what are the differences between the dev version and the European one? Anything related to getting signal or something?
If I just update fw and rom with your two links, it will work even with my software status says "modified"? And Will it change back to official status?
Are updates going to be better if I go s-off and european again or is it the exact same version?
1. I don't see any significant difference with EU and Dev Ed except the obvious radio config.
But both worked fine for me in Asia region.
2. You should get the official status.
3. I don't see a point to S-Off as there is no more further OTA offered by HTC.
Once you updated to Marshmallow, you can always unlock the bootloader and install any custom ROM that you like. Most important is to have Marshmallow firmware (or at least Lollipop), doesn't matter whether it is EU or Dev Ed.
Ok, thanks again for the replies! Will try dev software, and if it doesn't work I'll pay for s-off
Ok so... I tried to update firmware, followed the tutorial, but i'm stuck at flashing the RUU. I went to the link you sent me, downloaded the 1.4 GB file, and now I have a zip file and a .exe file. The .exe will just start, say me it installs installshield, ask me to agree with the terms of licence, and close.
So I searched a bit, and i tried to flash the RUU as I did for the firmware, but now rebooting just leads me to a black screen, and the RUU fails.
please tell me what I did wrong so I can fix it.
Here is the ADB output :
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s
You can't use generic fastboot.exe to flash the RUU.zip, you need to use htc_fastboot.exe
Read this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your RUU.zip (not the one in the guide)
sorry to bother for this but what is my RUU.zip you are talking about?
And i've tried with HTC fastboot and no luck neither...
You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Can you post your current fastboot getvar result ? Need to see that you successfully installed the firmware.zip
ckpv5 said:
You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Click to expand...
Click to collapse
Ok, just saw this at the moment on another thread, was going to try with the %temp% method, the command you made bold was the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.zip file that I renamed to be able to flash it more easily lol, what a noob I am ^^ so i'm going to extract this rom.zip and flash it, hope it works now! all fastboot commands have to be replaced with "htc fastboot" now, or only the flashing one?
Once again, thank you! (Using the thanks button at each of your posts too, don't worry )
yes, I verified in bootloader it says OS-6.12.1540.4 !!! Win! now just estracting the Rom from the temp folder!
htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)
ckpv5 said:
htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)
Click to expand...
Click to collapse
I've done the 1st method, and now after a flash that went well, i'm stuck in bootloader, with os version bein written in red and showing two times the version number, second one in parenthesis.
Instead of having options to power down etc, I only have a orange RUU option which is selected but I can't validate with power button, and in ADB I did command to reboot to bootloader but not doing anything now...
When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip
ckpv5 said:
When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip
Click to expand...
Click to collapse
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 8.033s
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange :/
Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange​
Can you use the power button to select it to get to RUU mode then fastboot reboot-bootloader or press & hold buttons method ?
ckpv5 said:
Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
Click to expand...
Click to collapse
I don't have the rom on micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?
WoBble12 said:
I don't have the rom one micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?
Click to expand...
Click to collapse
Run command fastboot reboot-bootloader
to get to bootloader
check the OS now written in red or green
if red, reflash firmware.zip not rom/RUU.zip
if green .. just reboot and wait for awhile and see how it goes.
if it is stuck after 10 minutes .. reflash RUU/rom zip
I'm now on marshmallow! Tastes sweet lol!
Can't test the signal at the moment as I have to cut my micro SD to the right size, and I have no time for it. I will do this tomorrow , and reply back here to say if it worked. Anyway, couldn't have done this without you so big thanks for this and big thanks to all the XDA community!
WoBble12 said:
....I have to cut my micro SD to the right size....
Click to expand...
Click to collapse
Hehe .. I believe you wanted to say to cut SIM card, not microSD
Great to know you managed to update.
Yes of course, simcard ^^
So I can now say that the phone is working and I have signal through my card.
Only weird thing is that after installing a few apps, system is taking up 8+ gig's of storage, which seems really big to me. But hey, it's a 32gig's one so I'm not afraid

Loading Stock RUU Failed and now stuck on install screen

Hi,
I had tried rooting my At&T HTC One M9 using the NOOB friendly guide written by KingInTheNorth. After completing, my phone wouldn't boot up. It got into a bootloop. I then found a guide (from another website) on how to reload the stock RUU. I followed the direction but it looks as if the file was bad. The following is copied from the command prompt.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip C:/Use
Downloads/M9fullstock.zip
target reported max download size of 800000000 bytes
sending 'zip' (79642 KB)...
OKAY [ 5.185s]
writing 'zip'...
(bootloader) HOSD CL#682052
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14 RU_ZIP_INFO_ERROR android-info missing or malformed )
finished. total time: 8.400s
Now my phone is stuck on the screen that shows a phone with a green arrow in a green circle pointing down. I've tried rebooting but it doesn't respond to any button presses. Did I ruin my phone? Can anyone help?
Try to type fastboot reboot in your command prompt. It should reboot your phone. If you're lucky it will reboot your phone normally and it's fully functional. If not, your phone will boot into bootloader which will mean your rom is wiped.
That's not a RUU that you were trying to flash and the guide written by KingInTheNorth is outdated since different firmware versions of the M9 can only get rooted with different versions of SuperSU. Check the ReadMe thread for the guides and files you may need.
@Suurbier91: Never recommend people to reboot if a flash failed unless they know exactly what's going on. There are some flashing errors that can only get fixed if the phone gets flashed immediately, again. A reboot makes those bricks permanent and unrecoverable.
Thanks for the direct to the Read Me. I've found a lot of good information there. After my battery died, I charged the phone and it's coming back on. It still has a boot loop that lasts for between five to ten minutes before booting up. I am going to try following one of the threads I found on here to get back to stock. Hopefully that will take care of the boot loop issue. I was wanted to root it so I could upgrade to Nougat. The phone was originally AT&T but I paid to unlock it and I'm now on Cricket but I don't receive any OTA updates.
That's probably so because the phone is only sim unlocked but still using the AT&T firmware. Don't ask me why they're allowed to do so (it wouldn't be possible in the EU) but AT&T won't let you download OTAs if there isn't an AT&T sim card inserted into your phone.
If you don't need the AT&T branded firmware then I'd get S-OFF and convert my phone to the dev edition if I were you. If you choose to stay on the AT&T firmware then you can update your phone via a RUU. Be aware that it's not possible to update from firmware 3.x or lower to firmware 4.x via RUUs due to new encryption keys.
Sent from my HTC One M9 using XDA Labs

Categories

Resources