Develop Bugs

[Q] finding the right firmware/ruu

status: HTC One X, s-off, unlocked, no reliable firmware or ROM
the last things I've done are to follow steps in this thread: http://forum.xda-developers.com/showthread.php?t=2598659
synopsis:
unlocked phone, changed CID to HTC__E11,
relocked phone, flashed firmware 3.14.401.31, ran RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
unlocked phone, flashed CWM recovery 5.8.4.0
problem: ROM will not start up and run reliably. I can't start recovery from bootloader, so I can't install another rom.
current getvar all:
Code:
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.14.401.31
serialno: FA2A4W102453
imei: 35399505028163
product: endeavoru
platform: HBOOT-T30S
modelid: PJ461****
cidnum: HTC__E11
battery-status: low
battery-voltage: 3527mV
devpower: 0
partition-layout: None
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0

further details
further history:
phone was imported into new zealand from unknown origin
when I started working on the phone, I remember is having CID: 11111111, and had HBOOT 0.96
I think Hong Kong zoned firmware and RUU 1.29.708.15 were a combination which allowed me entry to CWM successfully, though low hboot version limited me from flashing cyanogenmod 10.1/ 10.2. Didn't try other ROMs
when I was flashing earlier, the battery charge was above 4000mV, it seems to have lost a lot of charge overnight
any help or advice around finding the right firmware/RUU that might help me install a working ROM would be amazing.
if I'm barking up the wrong tree also happy to explore other leads.
thanks in advance

okey..for working recovery download cwm.img and flash it from FASTBOOT..then you can restore stock backup or flash custom rom..
Sent from my EndeavorU using Tapatalk 2

whimful said:
further history:
phone was imported into new zealand from unknown origin
when I started working on the phone, I remember is having CID: 11111111, and had HBOOT 0.96
I think Hong Kong zoned firmware and RUU 1.29.708.15 were a combination which allowed me entry to CWM successfully, though low hboot version limited me from flashing cyanogenmod 10.1/ 10.2. Didn't try other ROMs
when I was flashing earlier, the battery charge was above 4000mV, it seems to have lost a lot of charge overnight
any help or advice around finding the right firmware/RUU that might help me install a working ROM would be amazing.
if I'm barking up the wrong tree also happy to explore other leads.
thanks in advance
Click to expand...
Click to collapse
first of all flash again the same RUU 3.14.401.31 after this receive all update to latest JB and after this install Philz recovery and custom rom the 3.14 is not the lastest firmware for the HOX it is 4.20.401.3

whimful said:
status: HTC One X, s-off, unlocked, no reliable firmware or ROM
the last things I've done are to follow steps in this thread: http://forum.xda-developers.com/showthread.php?t=2598659
synopsis:
unlocked phone, changed CID to HTC__E11,
relocked phone, flashed firmware 3.14.401.31, ran RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
unlocked phone, flashed CWM recovery 5.8.4.0
problem: ROM will not start up and run reliably. I can't start recovery from bootloader, so I can't install another rom.
current getvar all:
Code:
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.14.401.31
serialno: FA2A4W102453
imei: 35399505028163
product: endeavoru
platform: HBOOT-T30S
modelid: PJ461****
cidnum: HTC__E11
battery-status: low
battery-voltage: 3527mV
devpower: 0
partition-layout: None
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Click to expand...
Click to collapse
can u guide me how u changed ur cid because i also want to change my cid i am using one x with CID Orange_001

ahmed309 said:
can u guide me how u changed ur cid because i also want to change my cid i am using one x with CID Orange_001
Click to expand...
Click to collapse
fastboot oem writecid 11111111
11111111 - Super CID other CID you can check in nandroid backup thread mine is HTC__032 x.xx.401.x WWE base

phone no longer booting
thanks for everyone's suggestions.
since the first post I haven't been able to try anything, because phone seems unresponsive (will not boot at all).
I've tried leaving it all night plugged into a wall charger (while off).
If it is battery, I'm aware of charging issues this phone has and the batchfile/ cwm 5.8.4.0 workarounds, but I can't get into recovery nor bootloader. If it's charge is there any way to get the phone enough charge?
Is the phone bricked?

phone now has some charge, still being awkward
ok have access to bootloader again. I'm trying rerunning the RUU, but having trouble... RUU tries to restart phone but fails.
I'm wondering if i've misunderstood how the region matters. the only stability i have seen is with old honkkong region firmware and old RUU (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.29.708.15_Radio_2.1204.122.17_release_268338_signed.exe)
can anyone give me a clear idea of whether using x.xx.401.xx on an s-off phone makes any difference ...
or should i be looking for x.xx.708.xx ruu and 708/hongkong firmware?

[Q] firewater s off not working, help?

Just got M8 today and rooted but stuck at S-OFF phase.
How do I fix it?
Cant afford sunshine and firewater wont work. .
Unticked everything in security except unknown source. Nothing. Fails in first try. What else?

I dont think theres a lot you can do, I put mine to the GPE edition last night and had to pay for Sunshine to do it as Firewater isnt working on 4.4.4

KiD3991 said:
Just got M8 today and rooted but stuck at S-OFF phase.
How do I fix it?
Cant afford sunshine and firewater wont work. .
Unticked everything in security except unknown source. Nothing. Fails in first try. What else?
Click to expand...
Click to collapse
if you can't afford sunshine then you will not be able to S off, so now its time to enjoy your new phone and custom roms, most don't need s off anyway.

Stock ROM, kernel, and recovery, then run firewater a few times. If you still get the "whelp" message, firewater simply doesn't work, and there isn't anything you can do to make it work.
Do you just want to update firmware to run the latest ROMs? If so, and you are in a region where Android 4.4.4 has already rolled out, just return to stock ROM and stock recovery and accept the OTA to update the firmware. After that, you can install custom recovery again, and install any of the M8 custom ROMs.
Otherwise, if you want s-off for another reason (SIM unlock, flash radio, flash hboot, etc.) than you will have to pay for sunshine if firewater doesn't work.
Really, you haven't given enough info. What hboot version you are on, what region, what errors you are getting with firewater ("whelp" or otherwise), and why you want s-off. For all we know you just don't have the USB drivers installed properly, or made some other silly mistake. But we'll never know without the proper info.

Is the not a way to down grade to by pass the HTC patch?
I have tried but the links to stock recovery are broken in another thread.
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.21.21331147A1.19_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:#####################
imei: ##########
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: BS_US001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: df77f8b7
hbootpreupdate: 11

[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

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

Which Stock Rom do I need?

Hi Guys, Ive got a International/European M8
I've unlocked the Bootloader and intsalled TWRP
The OS was corrupt and stuck in a bootloop so I need to wipe and replace
I'm stuck as to which variant I need please help...
If possible I dont want a Nandroid Backup I want a Stock ROM I can just flash
Here's my Getvar..
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.12.401.4
version-misc: PVT SHIP S-ON
serialno: *************
imei: **************
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: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

Well eskimosound because so many people rushed to your help, I suggest you used Android Revolution HD and see if that works (it does) Now I recommend you go back to that Excellent SRom that's in your signature

eskimosound said:
Well eskimosound because so many people rushed to your help, I suggest you used Android Revolution HD and see if that works (it does) Now I recommend you go back to that Excellent SRom that's in your signature
Click to expand...
Click to collapse
You understand the device is 4 years old, and there are only about 4 knowledgeable "helpers" around anymore (and not only all the time)?
Your mention of going "back" to S.ROM is confusing, as you don't indicate being on a custom ROM in your OP. Why not just reflash S.ROM to begin with, if that is the ROM you were having problems with?

redpoint73 said:
You understand the device is 4 years old, and there are only about 4 knowledgeable "helpers" around anymore (and not only all the time)?
Your mention of going "back" to S.ROM is confusing, as you don't indicate being on a custom ROM in your OP. Why not just reflash S.ROM to begin with, if that is the ROM you were having problems with?
Click to expand...
Click to collapse
It's all ok, phone is fixed and working correctly.
I needed to get a os on it to check my root.

eskimosound said:
It's all ok, phone is fixed and working correctly.
I needed to get a os on it to check my root.
Click to expand...
Click to collapse
Ok. Here is the stock RUU for your device, if you need it in the future: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

redpoint73 said:
You understand the device is 4 years old, and there are only about 4 knowledgeable "helpers" around anymore (and not only all the time)?
Your mention of going "back" to S.ROM is confusing, as you don't indicate being on a custom ROM in your OP. Why not just reflash S.ROM to begin with, if that is the ROM you were having problems with?
Click to expand...
Click to collapse
redpoint73 said:
Ok. Here is the stock RUU for your device, if you need it in the future: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Thanks, that's great...