Develop Bugs

hit a roadblock while trying to revert my 816 to stock. please help.

Hi guys.
I rooted my 816 using CWM and SuperSU months ago. Now, there's an OTA update to Android 6.0 which will hopefully render the usefulness of root obsolete, as I mostly need it for link2sd (they also cite better RAM management as a new feature, which should get rid of the horrible lag on Lollipop).
I know I have to go back to full stock, and I read a simple guide somewhere, and I thought, why don't I give it a crack. So, it said I should just "fastboot oem lock" the phone and flash the correct .zip RUU. After much trouble with connectivity and driver issues between my computer (adb server is out of date. killing...; device offline; errors etc.) I FINALLY (after hours of troubleshooting) managed to go into fastboot via USB and lock the bootloader. Great. But, when I tried to flash the .zip, it just says waiting for device, indefinitely. Tried to go into recovery via the power buttons on the phone, but it shows an error and simply refuses to. As a sidenote, root still works, but the phone displays this in fastboot: Relocked, Security Warning.
Basically, I'm afraid to proceed because I think I'm on the wrong track, and could end up f'ing up my device altogether. I'm from Croatia so I downloaded the 5.0.1 EU version .zip from here: (can't post link, just search htcdev downloads, it's the first one).
I hate opening new threads because I'm sure someone has already had the problems I'm having, but I just can't keep searching the web for hours on end trying to find a solution. Forgive me for this guys, and please help a poor noob in need if you can.

Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.

nukaru said:
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
Click to expand...
Click to collapse
Oh great, you're from Germany, so you have an EU 816 too. It's an a5ul just like yours. I'll send the full info text as soon as i install SDK tools completely.
I noticed that in your guide you first flash the stock ROM, and only then lock the bootloader. In the guide I found it said to first lock the bootloader, and then flash the stock ROM. So right now, I have a locked bootloader and CWM recovery I can't get into. Is this going to be a problem?

No, you first flash the stock recovery, then relock bootloader. And if your flashed recovery works you flash the RUU.

running fastboot devices does literally nothing, just sends me to the next line.
running adb devices, on the other hand, lists my device.
great, so I messed up there. do you know how I can fix it?

Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.

nukaru said:
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
Click to expand...
Click to collapse
I managed to get the getvar command to work: here's the info
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s

The files from my guide should work with your device.

so it doesn't matter that my bootloader is now locked? I can just follow your guide and it should work?

Have you flashed stock recovery BEFORE locking bootloader? You have to install stock recovery or the RUU won't flash. It's all in the guide.

No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?

edofot said:
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
Click to expand...
Click to collapse
Did you type this before flashing the RUU?
Code:
fastboot oem rebootRUU

Nope. I tried to flash the RUU with fastboot flash ... .zip but it just said: waiting for device; and nothing happened. So I'll try the rebootRUU command when I get home from classes.

You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.

nukaru said:
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
Click to expand...
Click to collapse
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?

edofot said:
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
Click to expand...
Click to collapse
Use this HTC mini-SDK

Gibz97 said:
Use this HTC mini-SDK
Click to expand...
Click to collapse
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)

edofot said:
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
Click to expand...
Click to collapse
First type this. It will reboot phone into a black screen with a silver HTC logo:
Code:
fastboot oem rebootRUU
then type:
Code:
fastboot erase cache
then type:
Code:
fastboot flash zip 0P9CIMG.zip

Sorry, I was looking for an sd-card adapter, I wasn't here.
Update: Moved the 09PCIMG.zip to the sd-card successfully this time and am flashing the img now from sd-card! Seems to be going well so far.

Success
Finally! Did it, works like a charm.
I'm still amazed by how fast the phone really is when it's stock.
Viele Dank, @nukaru, du wärst eine sehr grosse hilfe. Wenn du nach Kroatien kommst, melde mich an, du hast ein Bier und/oder Kaffe von mich (at least I tried, even without google translate)
Thank you too @Gibz97, really appreciate the effort.
If anyone reading this has the same questions I had, just follow nukaru's guide, it has all you need to know. If you have an A5_UL, it's gonna work.

WI-FI won't work after flashing custom ROM

Dear all,
After I flashed my HTC One M8 with a custom ROM (btw I did everything by the book according to Hasoon's All in one kit.) WI-FI doesn't work, it won't turn on.
Recovery: It was TWRP at first, but then I tried clockworkmod as well, after several flashing with other custom ROMs it still won't turn on.
Can you help me find out what the problem is?
Note: After several flashing attemps, although it was rooted at first, my phone somehow got unrooted.

Your firmware is outdated.
You need a 4.xx.xxx.x or 6.xx.xxx.x firmware to have a working wifi.
Check your bootloader, you should see the OS- no. there. If it is blank because you used an outdated recovery, see the hboot version .. must have 3.19.0000

I checked and this is what I have found:
***Tampered***
***Unlocked***
S-On
Hboot : 3.16.0.0000
OS - this area is blank
But I also checked my firmware number it starts with 6.xxxxxx

6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.

ckpv5 said:
6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.
Click to expand...
Click to collapse
Getvar results
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.153s
I added the getvar all results. Unfortunately I don't have the non-rooted backup :/
And I'm sorry I'm new to this all. What exactly is sn OTA or RUU and how do I do it?

ongunpitir said:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.

ckpv5 said:
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.
Click to expand...
Click to collapse
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?

kiuqxy said:
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?
Click to expand...
Click to collapse
This is usually due to your PC's configuration. Win7 and USB 2.0 for the best chance of compatibility.

I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.

ongunpitir said:
I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.
Click to expand...
Click to collapse
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.

ckpv5 said:
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.
Click to expand...
Click to collapse
I tried what you said this is what gives me;
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.016s]
finished. total time: 0.017s
C:\adb>htc_fastboot flash zip rom.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 4.28.502.2
found large-zip header, file count: 6
processing file 1/6...
sending 'zip' (57600 KB)...
OKAY [ 2.748s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
Process Process-1:
Traceback (most recent call last):
File "C:\Python34\lib\multiprocessing\process.py", line 254, in _bootstrap
File "C:\Python34\lib\multiprocessing\process.py", line 93, in run
File "E:\largezip\htc_fastboot\htc_flashzip.py", line 207, in _do_extract
File "E:\largezip\htc_fastboot\largezip.py", line 61, in extract
MemoryError
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 16.911s
htc_fastboot finished. total time: 18.191s
C:\adb>

BTW, i wouldnt rely on toolkits either to flash the M8, should always be done manually either thru recovery methods, RUU or Fastboot, i never use any of the avail toolkits to flash anything.

ongunpitir said:
I tried what you said this is what gives me;
FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)

ckpv5 said:
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
View attachment 3711349
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)
Click to expand...
Click to collapse
Thank you so much! After many failures, I have finally managed to make it work. After relocking my device and flashing with a RUU using command prompt option, it finally worked. Now I can use my wifi again. Now I will try to flash a custom ROM, but you said I need to update my firmware right? So how do I do that? Or have I just updated it already by flashing the latest RUU?
Thanks in advance

The RUU already updated your firmware to the latest ... but still a Lollipop as there is no Marshmallow update for AT&T yet but that should be enough for now, your wifi should work on any custom ROM.

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

bootloop HTC One M9, Original, Locked, S-ON

Good day everyone.
After two weeks of trying and searching the web for an answer I have finally given up and decided to post my question here, perhaps someone has an idea that can help.
I have an HTC One M9 that was stashed away in a cupboard, I decided that I am going back to it as my current phone is just not working for me, however, I LOVE the hardware on the One M9 but I do not like the HTC Sence UI and decided that I will flash it with a custom ROM. Needless to say I completely stuffed it up. (I probably should have S-OFF and unlocked before I tried flashing. (Also didn't enable developer options or USB debugging - stupid stupid me)
Herewith the symptom. I can boot into download mode but not recovery, when i boot into recovery the black HTC logo appears and then disappears, appears, disappears etc etc so ABD does not work.
I have tried the RUU route but as soon as the installer reboots the phone it does the whole black logo loop thing. the get_identifier_token command also returns bank (see output below) so can't even use the htcdev procedure.
I have tried manually flashing zip and img files and get a 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCK also tried flashing stock recovery.img rom.
Rom:
M9_3.35.401.12_FullStock_wipe.zip
M9_3.35.401.12_NoWipe_TWRP2871b1.zip
0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Ra dio_01.01_U11440261_56.02.50306G_2_F_release_42934 0_signed_2_4.exe
Manually flashing with extracted rom in RUU file
hima_uhl_n70_hosd_signed.img
HTC_One_M9_1.32.401.8_recovery_signed.img
twrp-3.2.1-0-hima.img
Used the SDCARD option
I did the fastboot erase cache process
At some point I was able to htc_fastboot flash zip rom.zip and it sent up to 50% but just remained there
Original Software
LOCKED
S-ON
htc_fastboot "works"
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXX
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.143s
flash example:
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe flash zip d:\roms\M9_3.35.401.12_FullStock_wipe.zip
htc_fastboot.exe v3.0.7 (2015-03-30)
target reported max download size of 800000000 bytes
sending 'zip' (134610 KB)...
OKAY [ 8.962s]
writing 'zip'...
(bootloader) HOSD CL#671758
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 10.121s
htc_fastboot finished. total time: 12.576s
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.162s]
finished. total time: 0.162s
htc_fastboot finished. total time: 1.335s
Please help or even tell me I am doing something wrong.
Thank you

The only ruu you can flash with s-off is this: 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
So, don't try another ruu, they will never work.
You just need to rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download and follow on-screen instructions.
The second method is with htc_fastboot.
Boot in download and do "htc_fastboot flash zip 0PJAIMG_HIMA......zip" - do the same command again when it asks(phone reboots itself in download mode).
After the process is complete do "fastboot reboot".

lucyr03 said:
The only ruu you can flash with s-off is this: 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
So, don't try another ruu, they will never work.
You just need to rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download and follow on-screen instructions.
The second method is with htc_fastboot.
Boot in download and do "htc_fastboot flash zip 0PJAIMG_HIMA......zip" - do the same command again when it asks(phone reboots itself in download mode).
After the process is complete do "fastboot reboot".
Click to expand...
Click to collapse
Hi, thanks, however, I did that previously no luck, problem is that S is on and I never enabled USB Debug before I started

neetekweet said:
Hi, thanks, however, I did that previously no luck, problem is that S is on and I never enabled USB Debug before I started
Click to expand...
Click to collapse
Neither being S-ON nor not having enabled the USB debugging prevents you from flashing a RUU that has the same firmware version as your phone.
If flashing the RUU that lucyr03 mentioned fails then you need to check whether the MD5 checksum of the downloaded file is correct and whether your SD card is broken.
Sent from my HTC One M9 using XDA Labs

Probably wrong firmware. You need a stock signed zip of 3.35.401.12 and use the sdcard method.

shivadow said:
Probably wrong firmware. You need a stock signed zip of 3.35.401.12 and use the sdcard method.
Click to expand...
Click to collapse
Hi
Thank you kindly, tried with Lucy's and a few others on the sdcard method.
Its starts the process "updating_ui" it reboots and then it just starts looping again.
I have basically given up, I am going to try one more thing and that is to take it to a repair shop and see if they can fix it.

neetekweet said:
Hi
Thank you kindly, tried with Lucy's and a few others on the sdcard method.
Its starts the process "updating_ui" it reboots and then it just starts looping again.
I have basically given up, I am going to try one more thing and that is to take it to a repair shop and see if they can fix it.
Click to expand...
Click to collapse
I can tell you now the phone is bricked.