HTC One M8 doesn't read sim card after flashing ROM - One (M8) Q&A, Help & Troubleshooting

My HTC One M8 got stuck on bootload shortly after I asked O2 to unlock it. The bootload said ***software status: modified***
After a lot of research, I came accross a tutorial to fix a soft bricked device via TWRP and managed to flash a new ROM on it. I choose Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9)/ stock HTC system dump that I found on android-revolution HD website and everything went very smoothly.
So my M8 is now starting and working fine, BUT doesn't read sim cards. It doesn't tell me whether a sim card is inserted, and if I put my Vodafone Malta sim card in, nothing happens, no error of reading, nothing. (if was working fine after the unlock code was put in).
I also noticed that HTC SDK API level now says unknown. And under mobile data>Network mode where I don't see 4G anymore.
I've received OTA update but can't install them. I get the "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at www . htc . com".
I thought that maybe installing a new ROM would be the solution and tried various RUU to no avail (159 error). I also tried using fastboot to flash 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
But it failed with 42 Wrong Customer ID (wrong CID).
I tried to amend android-info.txt but 1/windows won't open the zip (I am on Windows 7) - 2/ 7zip will but won't let me copy or edit the file (unsupported compression method error).
I am very much a newbie and I am not very keen on going S-Off as yet and would like to have opinions on what my next move could be, staying S-On.
My main concern isn't the updates but the non reading of my sim card. That's the main thing I'd like to resolve (and I thought that flashing a new ROM could be the solution - correct me if I am wrong!)
here is a reading of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance for any advice!

Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?

ckpv5 said:
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
Click to expand...
Click to collapse
Hi ckpv5,
Thanks for your advice, really appreciate it.
Definitely sure about the phone being SIM unlocked as the Vodafone Malta SIM card worked for a while until everything went pear shaped and the phone stopped booting.
I'll try both and will let you know how it went.

ckpv5 said:
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
Click to expand...
Click to collapse
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?

No imei no baseband
JenovaXIII said:
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
Click to expand...
Click to collapse
I have got the same problem. On my One M8 it reads unknown imei unknown baseband. But when I type "fastboot getvar all" everything seems OK. This might be due to corrupted EFS or other partitions I think. I've found an article written by mike1986. (Android Revolution HD developer) about how to fix a corrupted DATA partition on the HTC One[/URL] but couldn't still find chance to restore/recreate/fix partitions. I send the device to a private service in Istanbul and they called me and told me that my phone requires a new motherboard. The device is running well but it can't detect the simcards. Actually it was, but in Turkey our network operators managed to give 4.5G service or (LTE?) and when I changed my simcard to 4.5G simcard itwas unable to detect it. I thought it was due to radio/cid/mid problem and I changed them all. Afterwards It couldn't detect any simcards. No imei no baseband.
Anybody willing to help these poor are appriciated. Thanks.

JenovaXIII said:
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
Click to expand...
Click to collapse
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.

ckpv5 said:
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
Click to expand...
Click to collapse
I am going through your tutorial on how to restore nandroid backup and am a bit confused:
once restored, I need to proceed to steps 11 - 12 - 13 (flash the recovery img) ?
Then relock bootloader, then flash 6.13.206.5 signed firmware.zip using adb and fastboot ?
Sorry I just want to make sure I'm not doing something stupid!

ckpv5 said:
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
Click to expand...
Click to collapse
And it did! After following your tutorial, I re-locked the bootloader, and flashed the signed firmware.zip.
My M8 is now recognising sim cards and my vodafone Malta one is read no problem. So glad to have my phone back.
Thank you ckpv5!

Related

[Q] "clean install"

I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
unifex_ said:
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Click to expand...
Click to collapse
Do as EddyOS says, he will guide you on the best which version to downgrade to (if your looking to do that). Honestly I didnt have any issues with Lollipop, its all good.
my suggestion of the easiest way to totally wipe up your internal memory is to unlock bootloader (if you've already unlocked it, then relock and unlock again), doing that will totally wipe your internal memory, as for ext. sd card, you can just format that.
Flashing original stock rom is done by an RUU.
EddyOS said:
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
Click to expand...
Click to collapse
Thanks Eddy, I appreciate the help.
I attach an image of the fastboot output.
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
Click to expand...
Click to collapse
Great, that sounds uncomplicated enough. My bootloader is locked, as far as I know, at least I never did anything to unlock it. So I should be good to go.
One question though. At the moment, the phone is unlocked as far as SIM is concerned. I mean that although the CID is from T-Mobile Germany, I'm using O2 as the service provider. Will that RUU keep it that way, or it will make the phone locked towards T-Mobile SIM cards?
Thanks a lot.
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
EddyOS said:
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
Click to expand...
Click to collapse
In case it would, what would I have to do to unlock it? I don't have any T-Mobile SIM cards around here after all.
Buy a code, like you did last time
EddyOS said:
Buy a code, like you did last time
Click to expand...
Click to collapse
I did not buy any code, I bought a phone. That's how it came from the shop - SIM-unlocked. I had no idea it had the T-Mobile anything in it until I started looking around this forum and someone asked me about my CID.
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
EddyOS said:
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
Click to expand...
Click to collapse
Great, thanks! I'll let you know how it went.
OK, finally got the time to do it, but unfortunately, the RUU that I downloaded
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
Click to expand...
Click to collapse
did not work, I attach the screenshot with the error. Any ideas? The error was the same regardless of whether the phone was connected to the PC.
Yeah, it appears that RUU is corrupt
EddyOS said:
Yeah, it appears that RUU is corrupt
Click to expand...
Click to collapse
That's a pity. Do you know where can one find a proper RUU? I looked at the htcdev.com download section, they list the software I need, 4.19.111.2, but the download link brings me simply to the htc.de, where nothing can be downloaded, it's just their regular advertising site.
I also found a zip file with the 4.16.111.2 firmware on a German forum (basically, from a link in the xda thread with RUU and OTA collection), but to be honest, I'm not sure what to do with the bunch of img files.
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
EddyOS said:
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
Click to expand...
Click to collapse
How about the files from that site (German, though). I found that link on the xda thread for RUU collection.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
They have a list of various files, for 4.19.11.2 they have nandroid backups and signed firmware, but not a RUU.
Or could you suggest a well working ROM?
You could flash the backup, then the firmware to restore stock recovery and it should work
EddyOS said:
You could flash the backup, then the firmware to restore stock recovery and it should work
Click to expand...
Click to collapse
Could you help me with mine as well
from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH445WM0----
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.177s

HTC One M8 o2 UK Branding - update possibilties

Hello and good evening,
before I start I have to say that I'm actually not a HTC user myself but today I was given a HTC One M8 which should have been resetted and updated to the latest android version. As a Nexus user it shouldn't be that hard but I have some issues, esp. with latest firmware I need some help/advice. I'm pretty sure that 90% of my questions have been answered already but I didn't want to bump old threads from 2014/2015.
Apparently the phone has an o2_uk branding. I was looking on HTC's site but I couldn't find any matching firmware or even info where to download such a file, at least not on HTC UK. HTC US publishes their firmware on their support site for each carrier. The phone still has warranty for a couple of months so unlocking bootloader or s-off are no option as of now. Where does the average joe find all those stock firmware for HTC devices? I'm not even sure if there is new firmware for this kind of branding available. I've have seen plenty of OTAs and RUUs posted on here but you either need to be S-Off or a globel unlocked device.
In case I need to unlock bootloader and go with a custom ROM - is it possible to flash certain radios, basebands from unlocked devices etc.? I've seen that some ROMs require that you update your firmware to the latest version to avoid weird behaviour. But when there is no latest firmeare available what do you do?
Device info: M8
Build number: 4.20.206.2 CL463267 release-keys
Android: 5.0.1
I'm more than thankful for any idea, tip etc. and appreciate your time helping me out.
maultasche said:
Device info: M8
Build number: 4.20.206.2 CL463267 release-keys
Android: 5.0.1
Click to expand...
Click to collapse
Don't really understand what your problem is. There is an update and the latest is 6.13.206.5
Have you tried checking software update in settings - about - software update ?
More than once. It only says there is no update available for your phone. Software information says it's on Android 5.0.1.. I installed Sys-I from Play Store which states that the phone apparently has a branding.
O2 is a branding device but it shouldn't stop the OTA even when you are not on their network. I used to have one too as you can see all the files that I have in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I don't know why it says no update when there is one.
As the device is still on warranty, I don't want to advise anything further related to unlocking bootloader.
Have you tried factory reset the device then check the update ?
If it is already bootloader unlocked .. then you can manually update the firmware to the latest.
I did two factory resets. After the second one it only updated some HTC apps. Android version was still 5.0.1.
If I unlock the bootloader would it be possible to manually update? Or even use one of the twrp backups from your thread?
maultasche said:
I did two factory resets. After the second one it only updated some HTC apps. Android version was still 5.0.1.
If I unlock the bootloader would it be possible to manually update? Or even use one of the twrp backups from your thread?
Click to expand...
Click to collapse
If the bootloader is unlocked, you can restore non-rooted 6.13.206.5 stock backup with the latest TWRP 3.0.2-0
then you need to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
then fastboot flash the fw_6.13.206.5.zip (that you can download from post #5)
fastboot oem rebootRUU
fastboot flash zip fw_6.13.206.5.zip
you'll get ERROR
repeat - fastboot flash zip fw_6.13.206.5.zip
done ... but your warranty most probably will be void.
BUT .. can you post fastboot getvar all result without serial and imei no. first.
I need to see the details of your device to make sure these instructions are correct for your device variant.
Wow, thank you for that tip. So S-Off and changing CID is not needed for this operation? Because that was always confusing me. As stated I'm not an expert with HTC and it's the first time someone asked me for help with that device.. Apparently the device has just four months left of warranty. So I guess it should be fine unlocking it.
maultasche said:
....So S-Off and changing CID is not needed for this operation?
Click to expand...
Click to collapse
S-Off is needed when you want to change the device variant from O2 to EU for example (where you need to change CID) but most of the time normal user doesn't need S-Off.
Once it is unlocked, and the firmware is updated ... a user can install any Custom ROM that he like .. not necessarily be on stock O2. If he prefer stock .. he can restore a stock EU ROM ..so no O2 bloatware.
I guess it is alright to unlock bootloader now ... there is no further OTA from HTC, HTC stop support for M8 after two years which already ended end of April.
Thank you so mich for your help. I appreciate it. Now I completely understand what I have to do now. Have a nice day!
@ckpv5
Hey there,
I wanna say thank you once again for your instructions the other day. I haven't spent much time invastigating. You asked me for getvar all so I wanna share the output I got for that device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.0
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d9e7383b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
There has been provided another update after a factory reset, firmware is still on Lollipop. I got the OK to unlock bootloader and flash TWRP. I assume your steps just work fine. Haven't flashed any TWRP backup as of yet.
maultasche said:
There has been provided another update after a factory reset, firmware is still on Lollipop. I got the OK to unlock bootloader and flash TWRP. I assume your steps just work fine. Haven't flashed any TWRP backup as of yet.
Click to expand...
Click to collapse
The getvar result show that the device was previously bootloader unlocked and the outdated TWRP 2.7.x.x (that's explain the missing version-main detail).
Just follow the steps .. should work. It seems many variants currently when check for OTA, none available. Not sure what actually is going on with HTC server.
Could probably be. The phone was bought "second hand" with warranty left. The original owner said everything is stock. Looks like it wasn't.
To make things short: I did follow your instructions. Flashed the correct twrp backup, flashed the firmware from your linked thread and everything was fine. OS, baseband etc. all got updated to latest version available.
Thank you again for your help.

deleted OS, been trying to return to stock

So I've been reading a ton of these threads to try to help me fix this. It seems like a really easy fix but it's not working for me. My device cid is htc__01 and I'm S-On. I'm trying to do an HBoot of the nandroid zip for my cid that I got from https://forum.xda-developers.com/showthread.php?t=2701376.
I downloaded the "4.16.401.10 - TWRP Thanks to Clumsy" under CID HTC__01 of nandroid backups. I put it on my SD card and I renamed it to 0P6BIMG.zip.
My HBoot is 3.19 btw. When I start HBoot, it says "no image or wrong image"
I'm also currently "unlocked" but I also tried running HBoot when I was "relocked" and it didn't work.
Any tips?
edit: Here are some pictures to show what I'm getting and what my info is
http://i.imgur.com/dsISZpB.jpg
http://i.imgur.com/IekCgFp.jpg
You do it all wrong ... the nandroid backup zip is to be extracted and restored not renamed and flashed.
Read this post #1 on how to use a nandroid to restore to stock - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you want the RUU.zip that can be renamed 0P6BIMG.zip and flash via hboot,
you need this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but this will get your device updated to Marsmallow directly.
Just saw your EDIT - Forget the above ... you have a AT&T device ... you'll need AT&T RUU
Can you post fastboot getvar all result (without serial & imei no.), need to see what's your device current status ... still an AT&T or converted to Intl GSM.
ckpv5 said:
You do it all wrong ... the nandroid backup zip is to be extracted and restored not renamed and flashed.
Read this post #1 on how to use a nandroid to restore to stock - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you want the RUU.zip that can be renamed 0P6BIMG.zip and flash via hboot,
you need this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but this will get your device updated to Marsmallow directly.
Just saw your EDIT - Forget the above ... you have a AT&T device ... you'll need AT&T RUU
Can you post fastboot getvar all result (without serial & imei no.), need to see what's your device current status ... still an AT&T or converted to Intl GSM.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:-
(bootloader) imei: -
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.342s
refsner said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) security: on
Click to expand...
Click to collapse
You do have a AT&T device.
The best place for your reference is @redpoint73 thread - https://forum.xda-developers.com/showthread.php?t=2751432
Are you in US and on AT&T network ?
If yes .. to get back to stock and updated to Marshmallow, you can follow this guide - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
ckpv5 said:
You do have a AT&T device.
The best place for your reference is @redpoint73 thread - https://forum.xda-developers.com/showthread.php?t=2751432
Are you in US and on AT&T network ?
If yes .. to get back to stock and updated to Marshmallow, you can follow this guide - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Click to expand...
Click to collapse
Yes I'm in the US but I'm using an AT&T phone with T-Mobile network. So would I need to follow the other steps in your second thread linked?
refsner said:
Yes I'm in the US but I'm using an AT&T phone with T-Mobile network. So would I need to follow the other steps in your second thread linked?
Click to expand...
Click to collapse
If you want a Masrhamallow stock ROM, yes the second thread. But I'm not sure about the SIM lock status of AT&T and the AT&T HD Voice whether these will impact your network on T-Mobile.
Need someone familiar with AT&T like @redpoint73 to comment.
I suggest you to wait for other comments.
Meantime - you can restore nandroid backup 4.28.502.2 which available on my backup thread to have a working phone. Don't do any RUU install yet.
EDIT - based on your screenshots/getvar result - you have a KitKat firmware, restore 3.42.502.1 to have a working phone. The above backup, you'll have wifi problem because that's a Lollipop.
ckpv5 said:
If you want a Masrhamallow stock ROM, yes the second thread. But I'm not sure about the SIM lock status of AT&T and the AT&T HD Voice whether these will impact your network on T-Mobile.
Need someone familiar with AT&T like @redpoint73 to comment.
I suggest you to wait for other comments.
Meantime - you can restore nandroid backup 4.28.502.2 which available on my backup thread to have a working phone. Don't do any RUU install yet.
Click to expand...
Click to collapse
Got it I'll do that. Thank for helping me out
refsner said:
Got it I'll do that. Thank for helping me out
Click to expand...
Click to collapse
Read my edit - you have a KitKat firmware, restore 3.42.502.1
ckpv5 said:
Read my edit - you have a KitKat firmware, restore 3.42.502.1
Click to expand...
Click to collapse
Ok! Will I be able to update to marshmallow at all afterwards?
refsner said:
Ok! Will I be able to update to marshmallow at all afterwards?
Click to expand...
Click to collapse
You won't be able to OTA when not on AT&T but you can get to Marshmallow using the guide that I put here - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
The only thing that I'm not sure whether the phone is SIM locked to AT&T or not.
If you're sure it is not SIM locked, you can straight away follow the guide.
Or if it is SIM locked but you do have the SIM unlock code .. then go ahead with the Marshmallow RUU.
About the HD Voice, I believe that will affect users on AT&T network but running custom ROM.
ckpv5 said:
You won't be able to OTA when not on AT&T but you can get to Marshmallow using the guide that I put here - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
The only thing that I'm not sure whether the phone is SIM locked to AT&T or not.
If you're sure it is not SIM locked, you can straight away follow the guide.
Or if it is SIM locked but you do have the SIM unlock code .. then go ahead with the Marshmallow RUU.
About the HD Voice, I believe that will affect users on AT&T network but running custom ROM.
Click to expand...
Click to collapse
I think the first time I received the phone, it was SIM locked but I was able to get a SIM unlock code. I'll place my bets and do the Marshmallow RUU. I'll let you know if it goes well.
refsner said:
I think the first time I received the phone, it was SIM locked but I was able to get a SIM unlock code. I'll place my bets and do the Marshmallow RUU. I'll let you know if it goes well.
Click to expand...
Click to collapse
Ok
Another thing is your device is S-On, you need to relock bootloader before you install the firmware.zip and RUU.
You already know how I believe - fastboot oem lock
ckpv5 said:
Ok
Another thing is your device is S-On, you need to relock bootloader before you install the firmware.zip and RUU.
You already know how I believe - fastboot oem lock
Click to expand...
Click to collapse
Yeah I made sure to do that thank you. I'm in the process of installing the RUU right now. Going a little slow. The RUU says to turn on the phone. Does that mean put it into fastboot USB? It didn't work when I had it just on the HTC logo white screen.
Yes - put the device on fastboot mode.
You already did the firmware installation ?
Install firmware first then RUU - all these on fastboot mode
ckpv5 said:
Yes - put the device on fastboot mode.
You already did the firmware installation ?
Install firmware first then RUU - all these on fastboot mode
Click to expand...
Click to collapse
Yes I did the firmware installation first. Then I ran the RUU, this time on fastboot mode (haha). It is still in the process of updating right now.
Edit: It's starting up. Seems to have worked. I appreciate all your help. I would have probably spent many more hours trying to figure this mess out!
refsner said:
Edit: It's starting up. Seems to have worked.
Click to expand...
Click to collapse
:good:
So no problem with SIM as it is still remain unlocked ? Hopefully yes as usually once SIM is unlocked it should remain unlocked.
ckpv5 said:
:good:
So no problem with SIM as it is still remain unlocked ? Hopefully yes as usually once SIM is unlocked it should remain unlocked.
Click to expand...
Click to collapse
No there was no problem at all. I inserted the SIM card and immediately got LTE T-Mobile coverage. Super fortunate
refsner said:
No there was no problem at all. I inserted the SIM card and immediately got LTE T-Mobile coverage. Super fortunate
Click to expand...
Click to collapse
Great .. this will be a good reference for someone else on same situation.
ckpv5 said:
Need someone familiar with AT&T like @redpoint73 to comment.
I suggest you to wait for other comments.
Click to expand...
Click to collapse
Looks like ckpv5 has the OP sorted out, before I even woke up! :good:
But let me know, if there are any further AT&T specific questions.

Sprint M8 Stock Roms

Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!
A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.
Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.
Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).
Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.
Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.
Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.
My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse

Which version is the M8 I bought ? Tampered/compromised phone ?

Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.
ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.
Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.
You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.
hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip
ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1
ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same
alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan
alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14

Categories

Resources