Develop Bugs

Cannot flash custom rom, but why ?

Hey there,
i have a strage problem, after rooting a lot of android devices the m8 behaves kind of strange.
I got a brand new M8 (Hbot 3.15xxxx and 4.4.2) for my girl friend and unlocked the device with htc dev. after this i flashed twrp 2.7.0.2, no big deal.
Now i made a backup (thank god....) and downloaded viper rom and arhd roms.
But if i install a rom (does not matter which one, with wipe and so on) the script tells me installtion is finished, but if i hit the next button the m8 vibrates and turns off, at least the screen goes dark.
the only way to wake up the m8 is to push power and volume up button, but the only thing i see is the htc logo with the red text at the buttom.
adb reboot boatloader does not work, but reboot recocery does. Wipen cache and so does not fix the problem, the stock backup can be restored.
do you have any idea what's going on, i really want to run viper or arhd on the m8.
thanks!

Havoc2k said:
Hey there,
i have a strage problem, after rooting a lot of android devices the m8 behaves kind of strange.
I got a brand new M8 (Hbot 3.15xxxx and 4.4.2) for my girl friend and unlocked the device with htc dev. after this i flashed twrp 2.7.0.2, no big deal.
Now i made a backup (thank god....) and downloaded viper rom and arhd roms.
But if i install a rom (does not matter which one, with wipe and so on) the script tells me installtion is finished, but if i hit the next button the m8 vibrates and turns off, at least the screen goes dark.
the only way to wake up the m8 is to push power and volume up button, but the only thing i see is the htc logo with the red text at the buttom.
adb reboot boatloader does not work, but reboot recocery does. Wipen cache and so does not fix the problem, the stock backup can be restored.
do you have any idea what's going on, i really want to run viper or arhd on the m8.
thanks!
Click to expand...
Click to collapse
Just a bug in TWRP, nothing to worry about. Disable from TWRP the screen timeout and you are good to go.

stathis95194 said:
Just a bug in TWRP, nothing to worry about. Disable from TWRP the screen timeout and you are good to go.
Click to expand...
Click to collapse
i don't think thats the problem. if the screen would timeout (like while doing backup or restore) i could wake it up.
but the device is not booting anymore then. Even if i do a adb reboot recovery and make a clean reboot. Just the htc logo with the warning.
could it be the firmware ? i dont see any information for hboot 3.15.....
thanks

Havoc2k said:
i don't think thats the problem. if the screen would timeout (like while doing backup or restore) i could wake it up.
but the device is not booting anymore then. Even if i do a adb reboot recovery and make a clean reboot. Just the htc logo with the warning.
could it be the firmware ? i dont see any information for hboot 3.15.....
thanks
Click to expand...
Click to collapse
Are you flashing a 4.4.3 ROM? which firmware are you on? Can you please do a :
fastboot getvar all
and post the outcome? Don't forget to hide your sensitive info (imei, etc)

stathis95194 said:
Are you flashing a 4.4.3 ROM? which firmware are you on? Can you please do a :
fastboot getvar all
and post the outcome? Don't forget to hide your sensitive info (imei, etc)
Click to expand...
Click to collapse
yes i will flash viper 2.0.0 or arhd 10.2 both are 4.4.3 roms.
device is running at 4.4.2 at the moment (rooted stock vodafone germany)
getvar all:
Code:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA03_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43FWM10422
imei: xxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: T-MOB101
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
m8_ul...... what device is it? internation one? should be, there are no at&t or sprint devices in germany, are they?
edit: i think i found the problem:
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
Click to expand...
Click to collapse
so the firmware should be the problem, i am right?

Havoc2k said:
yes i will flash viper 2.0.0 or arhd 10.2 both are 4.4.3 roms.
device is running at 4.4.2 at the moment (rooted stock vodafone germany)
getvar all:
Code:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA03_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43FWM10422
imei: xxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: T-MOB101
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
m8_ul...... what device is it? internation one? should be, there are no at&t or sprint devices in germany, are they?
Click to expand...
Click to collapse
Well nothing strange here. You are on older firmware trying to flash a 4.4.3 ROM. First boot might take up to 15 minutes...But after that you will experience slow boots and/or wifi or bt issues.
You can either try to s-off and upgrade firmware or try a 4.4.2 rom like ARHD 8.1
First of all try the following. Flash the ROM and reboot and let it sit there for around 15 minutes to see if it boots. And we can see your choices from there.

If i want to update with OTA,
which stock recovery i need to flash ? my version.main is empty :/ so i am not sure how to flash the right recovery. there a lots of them: http://forum.xda-developers.com/showthread.php?t=2701376

Havoc2k said:
If i want to update with OTA,
which stock recovery i need to flash ? my version.main is empty :/ so i am not sure how to flash the right recovery. there a lots of them: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Try here:
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832637
it's either 1.12.111.18 or 1.57.111.2

it is 1.12.111.18
at the moment the OTA to 1.57.111.2 is running
some german forums wrote that any 1.12.xxx recovery will work for the ota. let's see if there is another ota after this one.
edit: 1.57 went well, now ota to 1.70

[Q] Pls help - HTC One X stuck on quietly brilliant screen and won't restore

Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal

koolvirgo said:
Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal
Click to expand...
Click to collapse
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version

Thant said:
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version
Click to expand...
Click to collapse
Hi,
Thanks pal ! Here is the output of fastboot getvar version-main
version-main: 0.0.0.178434
thanks,
Kunal

Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal

koolvirgo said:
Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal
Click to expand...
Click to collapse
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want

Thant said:
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want
Click to expand...
Click to collapse
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal

koolvirgo said:
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal
Click to expand...
Click to collapse
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same

Thant said:
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same
Click to expand...
Click to collapse
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal

koolvirgo said:
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal
Click to expand...
Click to collapse
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???

Thant said:
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???
Click to expand...
Click to collapse
Yes, I did both !!

koolvirgo said:
Yes, I did both !!
Click to expand...
Click to collapse
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?

I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
INFOversion: 0.5a
INFOversion-bootloader: 1.72.0000
INFOversion-baseband: 5.1204.167.31
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.18.401.4
INFOserialno: HT23NW107620
INFOimei: 359188041361783
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ4610000
INFOcidnum: HTC__405
INFObattery-status: good
INFObattery-voltage: 3660mV
INFOdevpower: 3
INFOpartition-layout: None
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
Click to expand...
Click to collapse
What I have to do?? Thanks for the help you are saving me!!

lollerz46 said:
I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
What I have to do?? Thanks for the help you are saving me!!
Click to expand...
Click to collapse
Okay I solved my problem, my issue was the boot.img that was different from the one inside the custom rom! Hope this helps

Thant said:
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?
Click to expand...
Click to collapse
It says Endeavoru XE

koolvirgo said:
It says Endeavoru XE
Click to expand...
Click to collapse
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU

Thant said:
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU
Click to expand...
Click to collapse
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal

koolvirgo said:
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal
Click to expand...
Click to collapse
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot

Thant said:
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot
Click to expand...
Click to collapse
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal

koolvirgo said:
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal
Click to expand...
Click to collapse
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment

Thant said:
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment
Click to expand...
Click to collapse
Hi Thant,
Before trying what you suggested (for manual update) I tried the ICS RUU once again. It went through fine this time not sure why, then I did an OTA upgrade and now I'm on Android 4.0.4 hboot 1.12 (same as before but on 2.17.720.2). There are no more OTA updates available, though HTC india website says there is one available for 3.14.720.24 which is JB version and should automatically update my hboot which I can then hopefully use to update to 4.4 ROM. Do you think what I think is going to work ?
But I can't find the OTA firmware for 3.14.720.24. There was one available here but no more.
There's one here but not sure about the authenticity of this.
I have downloaded the firmware zip you shared but it seems the file is corrupt.
Thanks,
Kunal

[Q] One M8 HTC__001 CID, Firmware/No Wifi problem

Hello, I've been a long time xda lurker (Never thought I could really add much anyhow) since I had my Dell Streak and I think for the first time since I got my M8 I need a bit of help.
They rolled out the lollypop OTA update here in Ireland and figured It was time to update to a stock ROM from here or a slightly improved one but ever since then I have lost my WiFi completely.
Sorry If this makes no seance- at all I'm a little burnt out trying to solve this on my own but even going back to 4.4.3 ROMs I still have no WiFi at all and any help at all would be greatly appreciated.
This is all the info I took from fastboot and the bootloader I thought would be needed
Bootloader Info
*** Tampered ***
*** Unlocked ***
M8_UL PVT SHIP S-ON
HBOOT - 3.18.0.0000
RADIO - 1.19.21331147A1.09G
OpenDSP - v38.2.2-00542-M8974.0311
OS - 2.22.401.4
Fastboot Getvar All Info
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 2.22.401.4
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0
Thanks again for even looking!

First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10

If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone

ckpv5 said:
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
Click to expand...
Click to collapse
Thank you I didn't even think of that I edited them out.
EddyOS said:
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
Click to expand...
Click to collapse
I will try that right away thank you for your help I'll post back here when I'm done

No luck, kept getting error 99 with the 'htc_fastboot" from the thread and with my normal fastboot it gives me the error 32 'header error' I only noticed the thread was for s-off phones, I don't care about my phone saying tampered, unlocked or anything but I'm assuming that's stopping the flash from happening.

You must relock your device first ... then try again with flash the ruu.zip

Isotopes said:
You must relock your device first ... then try again with flash the ruu.zip
Click to expand...
Click to collapse
Haha yeah that worked now, ignoring the guide at the start and just leaving it with the relocked warning it's flashing now via the RUU
Thanks to the both of you for your help.

HTC one M8 SIM detection Problem

Here the actual problem was phone didnt detected sim .show"no sim"
***Software status modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21.331147A1.29G
OpenDSP-V46.2.2-00564-M8974_FO.0811
OS-("didnt show anything after flash custom rom")
eMMC-boot 2048MB
Nov 13 2014,21:01:33.0
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpid: None
version-main: ...........
version-misc: PVT SHIP S-ON
serialno:**********************
imei:**********************
imei2: Not Supported
product: m8_ul
platform: hTCBmsm8974
modeid: 0P6B10000
cidnum: HG3__001
battery-status: good
battery-voltage: 0mV
partition-layer: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c52f93f
hbootpreupdate: 11
gencheckpt: 0

please help

Hello.
Did your SIM just stop working, or did you flash something first?
It could be that you need a replacement SIM, or that it has a bad connection in the tray. Is there another phone available to you that you could insert your SIM into to see if it works? Also, is there another SIM that you could use to see if the problem is a bad connection in the tray? Maybe a friend can let you test with his/her phone and SIM.
If it happened after you flashed something, like a ROM, then try another ROM to see if the problem persist.
Also, your OS in bootloader and version-main in your getvar are blank because of a bug in some older versions of TWRP. Update to the newest version (2.8.7.0). It will remain blank until the next time you update firmware I believe, but that's what caused it.
EDIT:According to your DSP, it appears you are on Kit-Kat firmware still. You should update to Lollipop if you want to flash newer ROMs. I'm not sure about this, but it may possibly be causing the SIM read error.
Since you are S-On, you will need to return to stock to do update.
This thread has instructions and download links for you to return to stock. Then you can update via the OTA that will be offered in settings>about>software updates

Yes sim is working after change the rom make this issue ......
I try to update 3.32.771.0 stock rom and try to ota updation after ota updation it hang in htc boot screen somtimes it ends with red triangle .then i use 4.20.771.2 in this stock rom no problem for ota updation but i bave still that issue sim detection .........can soff and use different rom solve this issue

I don't understand. You have updated via OTA? Did you update TWRP? Your version main shouldn't be blank anymore.
Is this something you have tried before starting this thread, or what you have done since I gave you that link?
Also, what ROM are you using that is giving you this error?
If you got S-Off, you could change your CID and update your firmware manually.
And yes, you should try another ROM to see if the issue persist. You could also try an older version of the ROM if your firmware isn't up to date.

xunholyx said:
I don't understand. You have updated via OTA? Did you update TWRP? Your version main shouldn't be blank anymore.
Is this something you have tried before starting this thread, or what you have done since I gave you that link?
Also, what ROM are you using that is giving you this error?
If you got S-Off, you could change your CID and update your firmware manually.
And yes, you should try another ROM to see if the issue persist. You could also try an older version of the ROM if your firmware isn't up to date.
Click to expand...
Click to collapse
By the help of xda links i ................do this
Yes update twrp 2.8.7 and use stock Nandroid backup 3.32.771.10 have problem for ota updation(stuck in htc boot screen sometimes ends with red triangle) and use 4.20.771.2 stock backup have no problem for ota updation for my phone and use stock recovery for the ota updation ....is s-on mobile can't able to downgrade firmware ????
Is my main version based on kitkat but i use custom rom based on lolipop ........can this cause for sim detection problem??????
Current stage of my problem
After use stock backup and update ota
***Software status modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21.331147A1.29G
OpenDSP-V46.2.2-00564-M8974_FO.0811
Os 4.25.771.6
eMMC-boot 2048MB
Nov 13 2014,21:01:33.0
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpid: None
version-main: .4.25.771.6
version-misc: PVT SHIP S-ON
serialno:**********************
imei:**********************
imei2: Not Supported
product: m8_ul
platform: hTCBmsm8974
modeid: 0P6B10000
cidnum: HG3__001
battery-status: good
battery-voltage: 0mV
partition-layer: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c52f93f
hbootpreupdate: 11
gencheckpt: 0

moononem8 said:
By the help of xda links i ................do this
Yes update twrp 2.8.7 and use stock Nandroid backup 3.32.771.10 have problem for ota updation(stuck in htc boot screen sometimes ends with red triangle) and use 4.20.771.2 stock backup have no problem for ota updation for my phone and use stock recovery for the ota updation ....is s-on mobile can't able to downgrade firmware ????
Is my main version based on kitkat but i use custom rom based on lolipop ........can this cause for sim detection problem??????
Current stage of my problem
After use stock backup and update ota
***Software status modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21.331147A1.29G
OpenDSP-V46.2.2-00564-M8974_FO.0811
Os 4.25.771.6
eMMC-boot 2048MB
Nov 13 2014,21:01:33.0
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpid: None
version-main: .4.25.771.6
version-misc: PVT SHIP S-ON
serialno:**********************
imei:**********************
imei2: Not Supported
product: m8_ul
platform: hTCBmsm8974
modeid: 0P6B10000
cidnum: HG3__001
battery-status: good
battery-voltage: 0mV
partition-layer: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c52f93f
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Sorry I haven't responded sooner. I've been very busy.
Have you tried with other ROMs? If the problem persists with other ROMs, it is because the SIM card isn't seated properly in the sim tray, or the SIM itself is fried. You could try to pop it out and reinsert it, clean the metal contact points with alcohol, and lastly try putting a thin layer of tape on the back to make it fit more snuggly.
I'm going to have this thread moved to the M8 Q&A forum, where there may be answers from people who have experienced this before. Try what I have suggested above, and hopefully you'll find a solution soon.
Good luck!

xunholyx said:
Sorry I haven't responded sooner. I've been very busy.
Have you tried with other ROMs? If the problem persists with other ROMs, it is because the SIM card isn't seated properly in the sim tray, or the SIM itself is fried. You could try to pop it out and reinsert it, clean the metal contact points with alcohol, and lastly try putting a thin layer of tape on the back to make it fit more snuggly.
I'm going to have this thread moved to the M8 Q&A forum, where there may be answers from people who have experienced this before. Try what I have suggested above, and hopefully you'll find a solution soon.
Good luck!
Click to expand...
Click to collapse
i face this problem after change stock rom to custom rom
now i want to s off and want to know which cid and mid number use after
soff to flash any ruu on my phone

moononem8 said:
i face this problem after change stock rom to custom rom
now i want to s off and want to know which cid and mid number use after
soff to flash any ruu on my phone
Click to expand...
Click to collapse
Your MID is fine. Change your CID to superCID (11111111).
You won't be able to flash all RUUs. Verizon and Sprint firmware won't work with GSM phones.
I would avoid AT&T and T-Mo RUUs as well (unless you are switching to their network).

xunholyx said:
Your MID is fine. Change your CID to superCID (11111111).
You won't be able to flash all RUUs. Verizon and Sprint firmware won't work with GSM phones.
I would avoid AT&T and T-Mo RUUs as well (unless you are switching to their network).
Click to expand...
Click to collapse
in this current model id i can flash indian RUU in this phone
RUU_M8_UL_L50_SENSE60_MR_hTC_Asia_WWE_4.19.707.2_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414204_signed.exe
can i flash above RUU

moononem8 said:
in this current model id i can flash indian RUU in this phone
RUU_M8_UL_L50_SENSE60_MR_hTC_Asia_WWE_4.19.707.2_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414204_signed.exe
can i flash above RUU
Click to expand...
Click to collapse
You should be able to, yes.
If it doesn't work you will get an error message/code, and the flash will abort. You won't brick your phone. If it comes up MID mismatch, then you will have to change it, but I don't think you will have to.
For the record, I am on the Telus network in Canada (MID 0P6B16000), and I am using WWE/International firmware for a year and a half (MID 0P6B10000). I just ran an RUU three weeks ago to clear up some system issues I was having, and it installed with no problem.

If you didnt change phones Model ID, You find everything here ROMS, RUUs, Stock Nandroid Backups with respect to your Model ID.
You can S-Off and SuperCID to make things a lot easier.
http://forum.xda-developers.com/showthread.php?t=2701376

S-Off, Ruu.exe and Wifi Problems HTC ONE M8

Hello friends, I'm new here and I have a problem. I have a HTC One (M8) where it is with an OS Maximum Hd 12 (6.0) but the wi-fi is having problems informing that it is not possible to load the drive (it does not) tried. The problem is because I can not pass it to s-off and I can not find a ruu.exe for it. In the s-off in the last line of the error of <pie> are supported and would not be viable to pay 25 dollars for the sunshine already that due to the rate of change would leave for me in a $ 100.00. I need a ruu.exe or a way to switch to s-off or that the wi-fi problem is resolved.
version: 0.5
version-bootloader: 3.18.0.000
version-baseband: 1.09.30.0903
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HC47KMY03070
meid: A1000037D2516F
product: m8_dwgl
platform: hTCBmsm8974
modelid: 0P6B41000
cidnum: HTCCN702
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ca994270
hbootpreupdate: 11

Try MaximusHD 2.0.0 - http://llabtoofer.com/2014/11/15/htc-one-m8-dual-sim-maximushd-2-0-0/
If you want RUU, not easy to get one for free -
Some site will ask for USD20 for the file
(the bad thing is some of ckpv5's backups are there and need to pay to download where I provide them for free on XDA)
Or you can try your luck with some Chinese site - search for 1.32.1401.12 RUU

I have this maximus android 6.0 and also 5.0 zip but the wifi give (error loading drive) unknown error 1. Will the RUU 1401 work in this model even though it is cnn702? Sorry, I'm noob. About the s-off could you explain the error <PIE> are supported? From now on.

You get wifi error on 6.0 and 5.0 because your device is on kitkat firmware.
MaximusHD 2.0.0 is for KitKat firmware but hboot 3.19; yours is 3.18 so it may or may not work.
That's why I said try it.
That RUU version is specific for your CID/MID
No idea about S-Off error. Maybe after you installed RUU then root it you can try again.
S-Off usually work on rooted stock ROM.

I found the file ruu.exe on a Chinese site, but need to register in baidu to download. Phone number from china what I do not have, I tried extensions and Jdownloader but always give error or the speed is ridiculous and not low. Do you know of any other form or register that you can use to download the file? Thank you so much

Sorry .. no idea .. never download anything from Baidu.
Try copy the filename and google it .. maybe other site have it too.

Thank you, I can solve with your help. It downloaded an OTA but when I install it from the crash. Anyway, it helped me a lot.
Download baidu https://www.crsky.com/rom/75428.html
..............................................................
So os loucos sabem