Develop Bugs

SIM no longer recognized as being inserted; IMEI not visible in software

Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.

dhmmjoph said:
Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.
Click to expand...
Click to collapse
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.

BWolf56 said:
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.
Click to expand...
Click to collapse
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?

dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
No, sorry. And I doubt you'll find one.

dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
http://www.androidfilehost.com/?fid=23212708291680823

Larry2999 said:
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
Click to expand...
Click to collapse
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!

dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
You said you moved it to your sd card? You might have to change TWRP's mounting to it.

BWolf56 said:
You said you moved it to your sd card? You might have to change TWRP's mounting to it.
Click to expand...
Click to collapse
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?

dhmmjoph said:
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?
Click to expand...
Click to collapse
I'm not so sure what file you downloaded but it should be a zip. In order to flash, you need a zip with META-INF folder in it (to put it simply).
Here's what you need: http://forum.xda-developers.com/showthread.php?t=1831898 (The MJB one).

dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.

Larry2999 said:
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.
Click to expand...
Click to collapse
Here's a TWRP flashable zip for the modem if the CWM doesn't work.

I think I messed up again

For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.

Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.

shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?

manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.

manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).

Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?

manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.

Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?

manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.

Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.

manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.

Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.

manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.

Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.

manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.

Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.

manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)

Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.

manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.

Update Problems via OTA, RUU, phone.

Hi everyone, first thread in xda!
So, my friend has a m9 that bought on April of 2016 in Germany, worked just fine until these days, it has already marshmallow, he was on exchange but now he's back to Paraguay.
Yesterday we tried to update, because there were updates available (3.35.401.32), so we downloaded from the phone settings.
Downloaded just fine, and when trying to install, just installed until 25% and then the red triangle appeared. I've been looking for some info, and just found that happened to some people too, but no answer or positive help.
Then I downloaded the Nougat OTA to just flash it via recovery (sideload); once in Recovery mode, headed to ADB install, renamed the OTA zip (to be accurate OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip) just to "ota.zip" cuz i'm so lame to write the whole name.
The flashing went well until @ ±40% and then Error Status 7 appeared, saying "This Package is for 'htc_himaulatt' devices; this is a 'htc_himauhl.'"
I think that the error might be in the regional versions, but I searched for HIMAUHL and there is NOTHING, NOWHERE.
Anyways, then I just downloaded the RUU from HTC's page, and still with no positive results, still on marshmallow and no possibilities to upgrade.
Any help?

martynssimpson said:
Hi everyone, first thread in xda!
So, my friend has a m9 that bought on April of 2016 in Germany, worked just fine until these days, it has already marshmallow, he was on exchange but now he's back to Paraguay.
Yesterday we tried to update, because there were updates available (3.35.401.32), so we downloaded from the phone settings.
Downloaded just fine, and when trying to install, just installed until 25% and then the red triangle appeared. I've been looking for some info, and just found that happened to some people too, but no answer or positive help.
Then I downloaded the Nougat OTA to just flash it via recovery (sideload); once in Recovery mode, headed to ADB install, renamed the OTA zip (to be accurate OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip) just to "ota.zip" cuz i'm so lame to write the whole name.
The flashing went well until @ ±40% and then Error Status 7 appeared, saying "This Package is for 'htc_himaulatt' devices; this is a 'htc_himauhl.'"
I think that the error might be in the regional versions, but I searched for HIMAUHL and there is NOTHING, NOWHERE.
Anyways, then I just downloaded the RUU from HTC's page, and still with no positive results, still on marshmallow and no possibilities to upgrade.
Any help?
Click to expand...
Click to collapse
So what is the device SKU? It sounds like your phone did exactly what it was supposed to do - reject an incompatible RUU.

There is a possibility that the device is rooted, you cannot update unless the phone is stock. You need to put the phone in download mode, connect to a pc via usb cable and in cmd type: fastboot getvar all
Then you tried to flash an att firmware on a wwe international device so it rejected it, which is normal.
I can safely tell you that you'll be lucky to recover the phone from its current state. You must now do a lot of reading. Starting with flippys thread in the general section of the m9 forum.
Lucky for you I have the same device with a stock backup (except the stock recovery) at the same firmware you had before you started should you need it, I think you will. It is linked in flippy's thread.
Beamed in by telepathy.

computerslayer said:
So what is the device SKU? It sounds like your phone did exactly what it was supposed to do - reject an incompatible RUU.
Click to expand...
Click to collapse
Yes, the SKU is HIMA_UHL, european version I guess (?)
shivadow said:
There is a possibility that the device is rooted, you cannot update unless the phone is stock. You need to put the phone in download mode, connect to a pc via usb cable and in cmd type: fastboot getvar all
Then you tried to flash an att firmware on a wwe international device so it rejected it, which is normal.
I can safely tell you that you'll be lucky to recover the phone from its current state. You must now do a lot of reading. Starting with flippys thread in the general section of the m9 forum.
Lucky for you I have the same device with a stock backup (except the stock recovery) at the same firmware you had before you started should you need it, I think you will. It is linked in flippy's thread.
Beamed in by telepathy.
Click to expand...
Click to collapse
Okay m8, thanks! I'll be reading.
It's funny cuz my friend doesn't know **** about rooting and stuff like that, but i'll give a try.

Sent from my Andromax AD687G using XDA Free mobile app

[SOLVED] Can't get download mode working

Okay, I'm giving up, I need someone to help me.
I was given my neighbours HTC One M9. It was working just fine. After he gave it to me, first thing I did was a factory reset because he didn't delete anything.
After that, the problems began. When I boot up the phone, even directly after resetting and even before the setup, I get an error "Google App stopped working". And after that, all couple of seconds another "com.google.process.gapps stopped working".
I tried several of the fixes out there on the web, but it didn't go away. I did another factory reset, and again even when I setup the phone I get those errors.
There is still Android 6.0 on the phone, so I wanted to update to 7.1
During install, I got the red triangle screen, on both attemps. Well, f*ck.
So, I went on to install a new OS. Never did this before, so I though this is a good chance to learn some more about Android.
It just got even more strange. When I'm in the bootloader, I saw
***Software status: Modified***
S-ON
LOCKED
***Security Warning***
Especially the modified software was very strange, since my neighbour has neither a clue nor any interested of fiddling with phones.
When I tried to go into Download Mode, it said "failed to boot into download mode".
Recovery mode worked just fine.
Therefore, I couldn't do anything to install a new OS.
Next I bought the Sunshine App and S-OFFd my phone, which worked just fine.
Now I'm S-OFF, unlocked and the Security Warning has gone. The software is apparently still modified.
But when I go into download mode, I get the black screen with the silver logo and red text for a while, then the phone proceeds to boot normally.
What the f*uck? I'm just out of idead what to do now. Please don't let it be a dead nand... it's such a nice phone, and apart from the google app errors, it works perfectly. I used it for some surfing around today and it works really well. I can't imagine it being broken.
Thanks for your help!

What variant do you have? Firmware version?

side_flip15 said:
What variant do you have? Firmware version?
Click to expand...
Click to collapse
Firmware is 3.35.166.12
I don't know exactly about the variant, this is what the IMEI checker says:
SKU , VF , German , CHE , HTC , CH , Swisscom , Bootloader Lock , Dark Gunmetal/Dark Gunmetal , w/o SIM Lock , HIMA#UHL-D1
I have a bug report of the gapps-Error. Would that be helpful?

I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.

@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.

It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.

Flippy498 said:
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
Click to expand...
Click to collapse
Flippy498 said:
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
I didn't have to revive it, except that Google-error it works beautifully. That' broken download mode the only symptom I have. The phone is (meanwhile after Sunshine) S-OFF
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Click to expand...
Click to collapse
Well, there are two things that leave me hoping it's not a dead nand.
• Apart from that com.google.process.gapps-error, it works like a charm. No crashes, no sudden reboots. I really can't imagine a broken part of a motherboard making no trouble, wouldn't that render the part
useless? And is that Google-App Error really relatable?
• After letting the Sunshine App do its job, I don't get an error message in the download mode (well, it just boots normally after a while), the security warning has gone as well. Only the modified software is
suspicious.
side_flip15 said:
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
Click to expand...
Click to collapse
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?

Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue.
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue. Great, thanks!
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
Click to expand...
Click to collapse
Yes, I know. Maybe I just don't want to accept that fact to keep my motivation to try to save the phone...
So what my optimism suspects is that somewhere deep in the firmware there is something corrupted. That leaves the System modified and the Google app confused.
After all, recovery mode works just fine. If you check what other people experience with a dead nand, it's got to do with sudden reboots, bootloops, failed download AND recovery modes et cetera.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Click to expand...
Click to collapse
A little more hope rised in me...

sechsgangschakter said:
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Click to expand...
Click to collapse
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.

SAME HERE PROBLEM PLEASE HELP
I HAVE HTC ONE M9 OPJA100 JUST GO ON LOCKED SCREEN WHEN REBOOT TO BOOTLOADER ITS RESTART AGAIN EVEN NOT GO DOWNLOAD MODE OR RECOVERY MODE.
I WAS JUST MAKE ROOT THEN ITS STUCK ON LOGO
NOT GO FASTBOOT MODE TO CHECK CID OR FIRMWARE
WHAT I DO ?????
ITS LOCKED
S-ON ALSO

side_flip15 said:
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
Click to expand...
Click to collapse
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!

sechsgangschakter said:
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
Click to expand...
Click to collapse
Glad I helped you:highfive:

side_flip15 said:
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Click to expand...
Click to collapse
Just for the record, that's not my thread. It's owned by Sneakyghost.
@sechsgangchakter: I'm glad to hear that your phone is working, again.

Flippy498 said:
Just for the record, that's not my thread. It's owned by Sneakyghost.
Click to expand...
Click to collapse
Oh god! Sorry
Credits to @Sneakyghost :highfive:

Hello, I am having a very similar issue. I am looking for the hosd.img file for Verizon. I dont see it at https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml. Please help. Thanks

You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.

Flippy498 said:
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Click to expand...
Click to collapse
So no one knows of one available for Verizon m9? What would happen if I used a GSM one?

You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs

Flippy498 said:
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Good idea, ill give that a try. Thanks

updating t-mo ruu manually.

So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.

So i checked on a friends stock m9 and indeed it has the 4.47 update.
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
I do have a ruu and zip on my computer from a couple years ago that i will try too.

Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
SO LONG FOR GOOD ADVICE FROM XDA.
BOOOO.

Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
myphonesbetter said:
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
Click to expand...
Click to collapse
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
myphonesbetter said:
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Click to expand...
Click to collapse
HTC is a bit lazy in regard to updating their webpage. You're always only able to download the latest RUU. However, you don't mention which variant you own. There is more than just one non-dev edition variant. Nevermind, you mentioned it in one if your following posts.
myphonesbetter said:
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
Click to expand...
Click to collapse
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
myphonesbetter said:
So i checked on a friends stock m9 and indeed it has the 4.47 update.
Click to expand...
Click to collapse
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant.
myphonesbetter said:
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
Click to expand...
Click to collapse
It's possible to break the OTA-update function by modifying the system via a root file explorer, as well.
myphonesbetter said:
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
Click to expand...
Click to collapse
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
myphonesbetter said:
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
Click to expand...
Click to collapse
The "database" is still stickied (in not only one but two subforums of the M9 section - the general and the q&a section). Therefore, I'm a bit surprised that you weren't able to find what you're looking for. In addition the thread I'm talking about is not only a database, it even contains all information you would have needed for solving your issues, already.
myphonesbetter said:
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Click to expand...
Click to collapse
If the RUU is older than your current firmware then you won't be able to use it.
myphonesbetter said:
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
Click to expand...
Click to collapse
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down up and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
myphonesbetter said:
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
Click to expand...
Click to collapse
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).

Flippy498 said:
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
Click to expand...
Click to collapse
Yah. I get it. Was kind of just shouting to get some attention.
Ive noticed that not just this forum but many other forums that i used to use have lossed a lot of popularity.
I think because facbook groups and things like reddit that cover all subjects.
The problem with those places is that they are so unorganized.
Maybe thats also part of why its become so unorganized here. just what people are used to.
I honestly wasnt expecting actual info. Thank you.
Flippy498 said:
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
Click to expand...
Click to collapse
Well i was afraid to brick it so i figured out (accidentally) how to update.
Flippy498 said:
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant It's possible to break the OTA-update function by modifying the system via a root file explorer, as well..
Click to expand...
Click to collapse
Yes that was. it is 4.27.
I could not find any older ruu's on their site. Or anywhere for that matter. none with active links at least.
Flippy498 said:
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
Click to expand...
Click to collapse
Yes 132. I did not realize that. Do you mean i would need to update via ota? by searching for updates.
Flippy498 said:
If the RUU is older than your current firmware then you won't be able to use it.
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
Click to expand...
Click to collapse
So i was originally trying to flash the latest frimware 4.27.xxx but i kept getting error 132.
And on the htc website it has 2 sections for ruu's m9 ans m9 developer. So i just figured it was the wrong one.
So i figured i would try the last ruu that i flashed before installing the rom that i ran for almost 2 years (lee droid)
when i flashed that, it got halfway through and gave me error 155. but left my phone in the middle of an update. Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
Well i could not reboot the phone so i just started the recover process. This rebooted my phone a few times then just started flashing the rom. To my surprise it worked.
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Took about 4 hours and 7 updates or so. probably 5 gigs on the data plan but finally it finshed with a 1.1 gig update to 4.27.
Im not sure why the first flash failed or why it worked, but eventually it did work.
Flippy498 said:
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWRP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Click to expand...
Click to collapse
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
I was using the last ruu that i had used. but i also flashed a rom and it was a long time in between.
Also i installed the old version of lee droid on 4.27.xxx and it seemed to work fine. I did this on accident though. Flashed the wrong zip. Re-flashed the latest 4.0 and it seems to be working great. Noticing a couple little lags. Might go to the stock rom just rooted and debloated. It seemed to run a little smoother than leedroid for the time i was using it. but i felt like they were trying to extract my stem cells via confusing TOS agreements.

myphonesbetter said:
Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
[...]
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
Click to expand...
Click to collapse
The power button isn't disabled. As said in my last post, you need to press the power button and the volume down button for 30 seconds. It's always been like that on the M9 since HTC already changed that on the M7 or M8 (can't tell you which one exactly it was).
Relocking was only needed on HTC phones that are older than the M9. HTC changed that with the M9. And as said in my last post, re-locking the M9 if you don't have a RUU at hand that you already used successfully is more than dangerous due to Google's FRP. You might end with a non-booting non-unlockable phone.
In addition, a relocked dootloader doesn't change the fact, that your phone is missing the needed encryption keys. That's why the 4.x RUU still failed.
However, it's nice to hear that you could solve your problems now. ?
Sent from my HTC One M9 using XDA Labs

Ah, I made a mistake while writing my posts. It's power and volume up. Not power and volume down. :silly: