Develop Bugs

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.

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

My M9 Bricked please Help

Please, My M9 Is usually on a same boot loop situation.
When I start it it shows just this screen
Software status MODIFIED
LOCKED
S-ON
Security warning (Sometimes it disappear)
REBOOT
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
POWER DOWN
Phone not detected to use adb commands.
Please, I need this phone and I donn't have a warranty.
There is no solution to go out from this screen? There is no software to force flash or flash a dead phone.
There is no hardware tweak to bypass this situation...I don't know anything please.
Please my friends Help me
{
"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"
}

I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.

I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help

freshmike said:
I have exactly the same
Click to expand...
Click to collapse
Sadly, I have exactly the same answer. Sorry, but you're probably out of luck.

computerslayer said:
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
Click to expand...
Click to collapse
Thank you very much

Just to clarify, status modified on a non rooted, bootloader locked, s-on, never touched phone most likely means a dead nand which is unrecoverable.
Beamed in by telepathy.

my phone is S-ON unlocked .
Today my phone turn off and after stay on boot loop . When i try go to recovery mode or download mode just restart to fastboot.
I connect to computer but only what i can get after command: fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT558YJ00694
all:
I think my nand memory is F...ck ?

If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.

shivadow said:
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
Click to expand...
Click to collapse
I do not know if it's worth repairing on htc. Used on ebay 150 €.

freshmike said:
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
Click to expand...
Click to collapse
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.

obywatel2x said:
I do not know if it's worth repairing on htc. Used on ebay 150 €.
Click to expand...
Click to collapse
Consider Swappa as well - good prices and often it's XDA users (who care more about caring for their phones) upgrading/changing phones & selling their old ones.

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
If the phone is assuredly duff then I'd try this too, even if I'm yet to know of an instance where it actually worked.. Either that or smack it one time with something really heavy. It won't fix it but you'll feel better!.
Beamed in by telepathy.

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.

freshmike said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
Click to expand...
Click to collapse
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
blueberry60 said:
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s

freshmike said:
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
Click to expand...
Click to collapse
Have you flashed other img files?

blueberry60 said:
Have you flashed other img files?
Click to expand...
Click to collapse
Yes, none of them went though. All command report you need to be s-off
FAILED (remote: cannot flash this partition in s-on state)
The only one which worked was hosd_signed.img, but that didn't change anything in the state of the phone.

is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s

freshmike said:
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Click to expand...
Click to collapse
You are in download mode?

sipas4 said:
You are in download mode?
Click to expand...
Click to collapse
Boot to bootloader (When I chose this option phone restart and come back to the same screen does nothing)
Boot to download mode (result: failed to boot to download mode press volume up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volume up or down...)
Looks like bootloader/recovery/download mode have been wiped out from the OTA update.

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.

I need your help

Hey, guys,
my 10 is s-on and locked and starts only in bootloader or download mode, token query does not work, says oem locked.
I think the only option is a ruu.exe or ruu.zip.
here's the problem.
cid is htc__102 and I can't find an appropriate one anywhere, does someone have a link for me or another solution?
I hope you can help me.

wolfi05 said:
Hey, guys,
my 10 is s-on and locked and starts only in bootloader or download mode, token query does not work, says oem locked.
I think the only option is a ruu.exe or ruu.zip.
here's the problem.
cid is htc__102 and I can't find an appropriate one anywhere, does someone have a link for me or another solution?
I hope you can help me.
Click to expand...
Click to collapse
You start with looking at your OS/Firmware line in the download mode, then search here for the corresponding RUU. I bet if you use the search box you will definitely find it. I can so you can too.......
Verstuurd vanaf mijn HTC 10 met Tapatalk

Mr Hofs said:
You start with looking at your OS/Firmware line in the download mode, then search here for the corresponding RUU. I bet if you use the search box you will definitely find it. I can so you can too.....
Click to expand...
Click to collapse
If it were that simple .......
the cid is htc__102 .......
the firmware is 1.30.401.1........
the only thing I could find would be a cid o2__102, does this fit...... .
So if you had a match, I'd be very grateful.

wolfi05 said:
If it were that simple .......
the cid is htc__102 .......
the firmware is 1.30.401.1........
the only thing I could find would be a cid o2__102, does this fit...... .
So if you had a match, I'd be very grateful.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=818070582850508041

Mr Hofs said:
[ww.androidfilehost.com/?fid=818070582850508041[/url]
Click to expand...
Click to collapse
mmmmmm.........
actually, that's a htc__034 , do you think this is gonna work?
i have slow internet and i have to think very carefully about what i download

wolfi05 said:
mmmmmm.........
actually, that's a htc__034 , do you think this is gonna work?
i have slow internet and i have to think very carefully about what i download
Click to expand...
Click to collapse
Don't look at cid, this version is just like yours the WWE version. Look at your firmware region number the. 401 part. I would not have linked this if it would be the wrong one

Mr Hofs said:
Don't look at cid, this version is just like yours the WWE version. Look at your firmware region number the. 401 part. I would not have linked this if it would be the wrong one
Click to expand...
Click to collapse
first of all thank you for your support.................
fastboot says about the file:
\fastboot-win> .\htc_fastboot flash zip 2PS6IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.41.401.41
found large-zip header, file count: 25
processing file 1/25...
sending 'zip' (108173 KB)...
OKAY [ 5.272s]
writing 'zip'...
(bootloader) HOSD CL#738269
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(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, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 8.942s
htc_fastboot finished. total time: 10.833s
I tried another ruu.exe with the same version number, with the same result.
I think I need a htc_102 otherwise it won't work.
I'm missing something?

wolfi05 said:
first of all thank you for your support.................
fastboot says about the file:
\fastboot-win> .\htc_fastboot flash zip 2PS6IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.41.401.41
found large-zip header, file count: 25
processing file 1/25...
sending 'zip' (108173 KB)...
OKAY [ 5.272s]
writing 'zip'...
(bootloader) HOSD CL#738269
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(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, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 8.942s
htc_fastboot finished. total time: 10.833s
I tried another ruu.exe with the same version number, with the same result.
I think I need a htc_102 otherwise it won't work.
I'm missing something?
Click to expand...
Click to collapse
I told you it's the correct one, HTC 102 is the same firmware as HTC 34 or any other WWE firmware, it stands for the European firmware. You can't flash any other. Of you look at the O2 102 cid you will also see that it's a completely different firmware number and that there is NO .401 in it because it's a carrier locked firmware.
The only thing that is possible is that the jump from 1.30.401 to 2.41.401 is to big, you might need a 1.90.401 or 1.30.401 ruu first as the 1.30.401 is VERY old !
Do this :
Put the 2.41 RUU on your sdcard and boot into the download mode (file named as 2PS6IMG.ZIP) and flash the file. See if that works.
Believe me i know what i am talking about......
Edit 1 :
Please post the outcome of :
Fastboot getvar all
Paste the whole outcome EXCEPT the imei and serial number.
Edit 2 :
https://www.androidfilehost.com/?fid=24533103863140111
https://www.androidfilehost.com/?fid=24671318762849319
2 other RUU zips you can try.

fastboot getvar all :
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) imei: 0000000000000000
(bootloader) version-main: 1.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__102
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.342s
When I start in download mode the 2PS6img should be found, or?
It says "file not found" on the display of the htc.
so far I have tried this without success:
2PS6IMG......1.30.401.
2PS6IMG......1.80.401.
..............................2.41.401.
RUU.....2.41.401
flash with the 2PS6img on my pc:
.\htc_fastboot flash zip 2PS6IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.41.401.41
found large-zip header, file count: 25
processing file 1/25...
sending 'zip' (108173 KB)...
OKAY [ 5.250s]
writing 'zip'...
(bootloader) HOSD CL#738269
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 6.296s
htc_fastboot finished. total time: 8.139s

wolfi05 said:
fastboot getvar all :
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) imei: 0000000000000000
(bootloader) version-main: 1.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__102
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.342s
When I start in download mode the 2PS6img should be found, or?
It says "file not found" on the display of the htc.
so far I have tried this without success:
2PS6IMG......1.30.401.
2PS6IMG......1.80.401.
..............................2.41.401.
RUU.....2.41.401
Click to expand...
Click to collapse
Be careful you didn't name the file .zip.zip as windows automatically hides extensions.
And yes download mode should autodetect them
And these are absolutely the correct files.

Mr Hofs said:
Be careful you didn't name the file .zip.zip as windows automatically hides extensions.
And yes download mode should autodetect them
And these are absolutely the correct files.
Click to expand...
Click to collapse
so stay try and error..................

wolfi05 said:
so stay try and error..................
Click to expand...
Click to collapse
Try them all with the sdcard method, 1 by 1. I can't offer anything else as this what you need. If the download mode doesn't detect the file you named it wrong.

Mr Hofs said:
Try them all with the sdcard method, 1 by 1. I can't offer anything else as this what you need. If the download mode doesn't detect the file you named it wrong.
Click to expand...
Click to collapse
I have formatted the sd card at the pc and only the zip on it, zip.zip in no case
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode) <<---- which means?
Which fastboot version would you recommend?

The problem with the sd card has been solved. There was a hidden partition of samsung on it. After reformatting the htc recognizes the file.
Okay, I tried them 1 by 1
Always with the same result :
"Fail 7 RU_CID_FAIL cid in androidinfo mismatched"
.........

Then the last method to update is to flash the 2.41.401 standalone firmware (not the RUU), locate it, download it, OPEN the firmware.zip with 7zip and drag out android info.txt, edit the file and add your CID (HTC__102) save the text and flash the firmware via fastboot. Be aware that your device has to be in RUU mode. After you flashed the firmware you should be able to flash the full 2.41.401 RUU.
That's all i can think of. You should have updated your phone long way back then you would not have this problem. Your current OS is like the stoneage is in time ! For all i know it has something to do with the problem why it only starts to bootloader and/or download mode, maybe the problem is bigger than just to flash a RUU.
wolfi05 said:
The problem with the sd card has been solved. There was a hidden partition of samsung on it. After reformatting the htc recognizes the file.
Okay, I tried them 1 by 1
Always with the same result :
"Fail 7 RU_CID_FAIL cid in androidinfo mismatched"
.........
Click to expand...
Click to collapse

Ok, as last way I will try. . . . . . but just to understand it, the new firmware doesn't change the cid, then the ruu doesn't care the cid?
I have entered the cid htc__102 in the ruu and it has aborted.
I will report...thanks

wolfi05 said:
Ok, as last way I will try. . . . . . but just to understand it, the new firmware doesn't change the cid, then the ruu doesn't care the cid?
I have entered the cid htc__102 in the ruu and it has aborted.
I will report...thanks
Click to expand...
Click to collapse
You can't change a cid in the RUU, unless you decrypt it ? A firmware can't change your cid because your device is S-ON. Only with s-off you can change the cid.
I told you to change the Android info.txt file which is inside the firmware (not the RUU) so that the firmware knows your cid is supported.

Mr Hofs said:
You can't change a cid in the RUU, unless you decrypt it ? A firmware can't change your cid because your device is S-ON. Only with s-off you can change the cid.
I told you to change the Android info.txt file which is inside the firmware (not the RUU) so that the firmware knows your cid is supported.
Click to expand...
Click to collapse
You may have to flash hosd_signed.img at bootloader (not download) before you flash the firmware. Extract the hosd_signed.img from the firmware zip and do 'fastboot flash hosd hosd_signed.img' in the bootloader mode; followed by flashing the firmware in the download mode.

rln_xda said:
You may have to flash hosd_signed.img at bootloader (not download) before you flash the firmware. Extract the hosd_signed.img from the firmware zip and do 'fastboot flash hosd hosd_signed.img' in the bootloader mode; followed by flashing the firmware in the download mode.
Click to expand...
Click to collapse
No that's not needed because this is not about downgrading the bootloader/firmware. That's only needed when you want to downgrade the firmware on an S-ON device.
Edit :
To Wolf
Here is the 130.401 to 180.401 firmware.
https://androidfilehost.com/?fid=24591020540821778
Open the firmware (NOT EXTRACT) and drag out the Android info txt file and edit in your exact CID. Save it and drag it back in the firmware.zip. then flash the zip as intended. Please check how to properly flash the firmware for a S-ON device.
i believe you have to enter RUU mode first before you can flash it so please check that out !!!

//You can't change a cid in the RUU, unless you decrypt it ? //
I started the ruu, then I went to the temp folder and changed the android-info, then I started the htc and started the flash process (it was worth a try)
//A firmware can't change your cid because your device is S-ON. Only with s-off you can change the cid. //
That's probably it....that's why I wonder why the ruu should work with another firmware(because the cid error always comes) and if the flashing of the firmware works, but the ruu doesn't, then the htc is an organ donor (more than now)?
now I'm confused:
firmware 1.8 ---> firmware 2.41 -----> Ruu 2.41 or
firmware 1.8 ----> Ruu 2.41 or
firmware 2.41 ---> Ruu 2.41 how would you do that?