Develop Bugs

WiFi issues since version 5.0

Hello,
Two months ago I upgraded my android version to 5.0.1, since then wifi problems start to appear.
There are two problems:
1) When the phone is sleeping, the wifi disconnect. once I wake the phone, even if it still locked, the wifi turns on again after 1 second. (I checked the advanced settings and "keep wifi on during sleep" is on "always").
2) Once I go from the wifi zone and come back after a while, I can't connect to the wifi. it just keep scanning, and when I tap on it to see available networks it just shows white page (switching wifi on and off doing nothing).
This problem can be solve by turning airplane mode on and off, but it only helps for one time - once I go away and come back to the same wifi zone I need to do it again.
*I tried factory reset, doesn't help.
*I flashed another rom, from HD revolution to ViperOne, and now my android version is 5.0.2, doesn't help.
*This problem happens in every router, not only in a specific one.
Maybe going back to the stock recovery will solve the problem, but I don't think so.
Thanks in advance

Avishay28 said:
Two months ago I upgraded my android version to 5.0.1, since then wifi problems start to appear.
*I flashed another rom, from HD revolution to ViperOne, and now my android version is 5.0.2, doesn't help.
Click to expand...
Click to collapse
Your android version is software version but not firmware version. You can't update your firmware by flashing ROMs.
Post your fastboot getvar all (delete serial & imei no.) then maybe that getvar info will point to your actual problem.

ckpv5 said:
Your android version is software version but not firmware version. You can't update your firmware by flashing ROMs.
Post your fastboot getvar all (delete serial & imei no.) then maybe that getvar info will point to your actual problem.
Click to expand...
Click to collapse
hi,
this is my info
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
gencheckpt: 0
Is it help?

Your radio low version suggest that you have a 3.x firmware installed, not 4.x which is required for 5.0.x android version.
Here is the latest RUU for your device version : http://dl3.htc.com.s3.amazonaws.com...G_20.68.4196.01_F_release_446501_signed_2.exe
Relock bootloader & run RUU.
Later you can re-unlock bootloader and install any custom ROM that you like

ckpv5 said:
Your radio low version suggest that you have a 3.x firmware installed, not 4.x which is required for 5.0.x android version.
Here is the latest RUU for your device version : http://dl3.htc.com.s3.amazonaws.com...G_20.68.4196.01_F_release_446501_signed_2.exe
Relock bootloader & run RUU.
Later you can re-unlock bootloader and install any custom ROM that you like
Click to expand...
Click to collapse
I'm pretty new to all this, so I'll be glad to have some explanation.
What's "ruu"? And how do I relock the bootloader?
What's the difference between Android version and firmware version?
I need to wipe something before I run ruu?
You think this is what cause the Wi-Fi problems?
Thank you!

Here is a good read for you : http://forum.xda-developers.com/showthread.php?p=52484527
relock bootloader - run command fastboot oem lock (after you put your device in bootloader/fastboot mode and connect to PC)
No need to wipe anything - the RUU will remove all and replace everything with the latest images - data, system, firmware and ROM
Your wifi problem as mentioned earlier because your firmware is old and has old radio baseband and not meet the minimum requirement for Android 5.0..x
An important note : after you done the RUU thing, to install custom ROM or to root, you need to install latest TWRP 2.8.7.0
Don't use the old TWRP recovery that you have .. as seen in your getvar all, there are a few missing info because of outdated TWRP

ckpv5 said:
Here is a good read for you : http://forum.xda-developers.com/showthread.php?p=52484527
relock bootloader - run command fastboot oem lock (after you put your device in bootloader/fastboot mode and connect to PC)
No need to wipe anything - the RUU will remove all and replace everything with the latest images - data, system, firmware and ROM
Your wifi problem as mentioned earlier because your firmware is old and has old radio baseband and not meet the minimum requirement for Android 5.0..x
An important note : after you done the RUU thing, to install custom ROM or to root, you need to install latest TWRP 2.8.7.0
Don't use the old TWRP recovery that you have .. as seen in your getvar all, there are a few missing info because of outdated TWRP
Click to expand...
Click to collapse
Ok the status changed to "relocked" instead of "unlocked", now just run the ruu? is there any command or something?
edit: I need to gain s-off first?
sorry for all the questions, I don't want to damage the device

Avishay28 said:
Ok the status changed to "relocked" instead of "unlocked", now just run the ruu? is there any command or something?
edit: I need to gain s-off first?
sorry for all the questions, I don't want to damage the device
Click to expand...
Click to collapse
It's harder to help when you ask all non-related stuff. I don't mention anything about S-Off because it is not necessary.
I know your device is S-on, that's why I said relock bootloader
Only two steps :
relock bootloader - run comman fastboot oem lock
run RUU - right click the RUU and select run as administrator on windows context menu
What you need :
USB2.0 on PC
Latest HTC USB driver installed - if not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install it as it will install the latest driver then uninstall the HTC Sync Manager but leave the drivers.

Avishay28 said:
Ok the status changed to "relocked" instead of "unlocked", now just run the ruu? is there any command or something?
edit: I need to gain s-off first?
Click to expand...
Click to collapse
RELOCKED is fine to run the RUU (as is LOCKED). UNLOCKED is the only status for that particular flag that prevents RUU.
You don't need s-off to RUU.

I relock the bootloader and run the ruu and now the wifi is working fine!
Thank you very much for your help!

same wifi issue
Hi
I got the same wifi issue and I try exactly the same fix as #Avishay28 but they didn't work.
And now I know why thanks to you #redpoint73.
Would you please suggest what kind of RUU should i install to have my phone back fully working?
Those are my info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(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
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Read post #8 for steps & what you need then install
4.16.401.10 RUU then do OTA to 4.16.401.13
http://androidruu.com/?developer=M8

I seem to have issues still even though I'm past version 4:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.9
(bootloader) version-misc: PVT SHIP S-ON
anyone else have issues on this version?

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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 (Hboot PreUpdate)
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
im having same issue with the wifi

eternity4ever said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: 11111111
(bootloader) security: off
im having same issue with the wifi
Click to expand...
Click to collapse
First - edit your post to remove serial & imei no.
Your baseband version suggest that you have a 3.xx.xxxx.x firmware installed.
You need a 4.xx.xxx.x firmware to have a working wifi when install a lollipop ROM.
What device that you have ? 0P6B16000 can be a Canadian device and some South American device. Update your firmware to the one meant for your device version.

My is Canadian device. I couldn't find a ruu version of device

eternity4ever said:
My is Canadian device. I couldn't find a ruu version of device
Click to expand...
Click to collapse
There is no RUU available for Canadian device. At least tell what it is .. Rogers, Bell, Telus or ??? You can try to find a nandroid backup and stock recovery, restore then do OTA to update to the latest.
Or .. as your device is S-Off, you can change it WWE device i.e change MID to EU MID then install EU RUU.

ckpv5 said:
There is no RUU available for Canadian device. At least tell what it is .. Rogers, Bell, Telus or ??? You can try to find a nandroid backup and stock recovery, restore then do OTA to update to the latest.
Or .. as your device is S-Off, you can change it WWE device i.e change MID to EU MID then install EU RUU.
Click to expand...
Click to collapse
Rogers

As I mentioned above try find a backup for device.
You need 3.34.631.4 and its stock recovery.
I already switch off my PC and in bed. Not sure whether I have those files in my collection.
I'll check tomorrow when I have time but try to find it first. Should be available.

ckpv5 said:
As I mentioned above try find a backup for device.
You need 3.34.631.4 and its stock recovery.
I already switch off my PC and in bed. Not sure whether I have those files in my collection.
I'll check tomorrow when I have time but try to find it first. Should be available.
Click to expand...
Click to collapse
can you post the files please ?thank you

Sunshine

I'm having a problem being able to launch apps on my One M8 ATT... I Don't have any apps on my home page and ATT Ready2Go keeps crashing on me. Can someone give me a command line so I can launch SunShine on my device through ADB, that way I can S-Off and go back to a different ROM.

Why would you need s-off to install a different rom ?

Mr Hofs said:
Why would you need s-off to install a different rom ?
Click to expand...
Click to collapse
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.

isutke1287 said:
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.
Click to expand...
Click to collapse
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.

xunholyx said:
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.
Click to expand...
Click to collapse
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>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: *tsk tsk*
(bootloader) imei: *tsk tsk*
(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.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)

isutke1287 said:
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>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: *tsk tsk*
(bootloader) imei: *tsk tsk*
(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.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)
Click to expand...
Click to collapse
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.

xunholyx said:
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.
Click to expand...
Click to collapse
I can NOT appreciate and thank you for your assistance in this! I went ahead and locked the bootloader and restored the original image with the RUU you linked me to, yesterday. Couldn't wait to try, haha. I had to sweet talk the HTC Live Chat person to tell me if I could use the RUU for the same software version as I had. Phone has been working like a champ. I'm gonna give it another day or two to settle in, do a few backups just in-case the flash doesn't go well.
I will definitely unlock the bootloader again and flash TWRP and SuperSU. But I imagine going S-OFF is just off the table right now since I'm a bit stripped of funds. I can afford it, haha, but my funds are already allocated towards adulting and such.
Again, THANK you for the support! This has been a learning experience.:good::good::good::good::good:

[Q] Need to update?

Hello,
With the release of new firmwares for our M8, I am a little bit lost with the versions
Currently, my M8 have the following setup:
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_F0.1211
As I am using Android 6 GPe H10 ROM (but I don't exclude to reinstall a Sense ROM), maybe a new firmware (Bootloader, Radio, etc...) exist and is adviced to install?
Many thanks in advance!

Is there an OS number listed on the bootloader screen, or is it blank?
Do fastboot getvar all (if you know how) and post the output (delete IMEI and serial number).

Indeed, there is no OS version in the "OS-" field
SO, here is the result of the "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT0000000000
(bootloader) imei: 000000000000000
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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
all: Done!
finished. total time: 0.049s

john_matrix said:
Indeed, there is no OS version in the "OS-" field
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
Yes, the blank main version and SuperCID (11111111) does make it hard to determine your CID and main version. Unfortunately, model number 0P6B10000 (Euro version) has quite a few unbranded and branded CIDs (and main versions) associated with it.
On the other hand, you are already using an Android 6 ROM, and updating the firmware would probably have minimal (if any) benefit. I'm using the Developers Edition Sense Marshmallow ROM, and haven't even bothered to update to MM firmware. Despite the fact that I fully know what my main version and CID are, and can pretty easily update it. MM runs fine on the LP firmware, so I haven't felt the need to update.

Originally, my CID was ORANG203 but I replaced it to SuperCID in order to don't be bothered by flashing
However, thanks for telling me that upgrading the firmware will not add any benefits to my M8, so I will let it "as is"

john_matrix said:
Originally, my CID was ORANG203
Click to expand...
Click to collapse
You sure about the CID? I don't see it on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
And the thread seems to be pretty comprehensive, in my experience (at least for Euro CIDs).

You're right, it was ORANG202
I have found back the log of the operation

john_matrix said:
You're right, it was ORANG202
Click to expand...
Click to collapse
Don't see that CID on the thread either. If it was a known CID ( with files on the linked thread) the process to update the firmware if you chose to do so would be to restore the stock 4.xx nandroid corresponding to your CID, restore the stock recovery, then OTA update to install the Marshmallow firmware.
But as already discussed, if everything is working fine, there is very little (if any) reason to update the firmware at this time.

Thanks for the advice, so I will not update anything if nothing new or nothing will be improved

john_matrix said:
Thanks for the advice, so I will not update anything if nothing new or nothing will be improved
Click to expand...
Click to collapse
Some would say, as a general rule its usually best for your firmware to correspond with your software (ROM).
But my phone has been working perfectly running Marshmallow ROM on LP firmware. So I have to assume the changes are very minor. And if you have had a similar experience, I don't see a compelling reason to change, either. Especially if the stock nandroid collection doesn't have files listed for your CID/version number anyway (although if you like, you could ask ckpv5 if he has access to them and could post - he's pretty amazing that way). Basically, if you don't have the stock ROM and stock recovery, or alternately the RUU or signed firmware.zip for your version; there is no way to update, anyway.

M8 starting up in Fastboot, won't load installed ROM

I've stuffed something up along the way and now my M8 seems to refuse to load any ROM I've installed on it. What's the best way to go about fixing this? It's unlocked with S-Off.

Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers

Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?

shirreer said:
Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers
Click to expand...
Click to collapse
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
redpoint73 said:
Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?
Click to expand...
Click to collapse
My OS number is 4.16.1540.8, I've tried TWRP 2.7.0.1, 2.8.7.0 and 3.0.0.0, roms I've tried include CM13, SkyDragon and a stock TWRP backup I found in another thread here.

roseyhead said:
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
Click to expand...
Click to collapse
Your MID and firmware number don't jive; and it can indicate something pretty dangerous (and possibly a radio bricked phone).
Need more info on what you've done.
Do fastboot getvar all, and post the output (delete serial number and IMEI before posting).
Was the phone new and stock (unmodified) when you got it; or did it have a previous owner?
Please list all the mods you have applied (s-off, changed CID, changed MID? etc.).

Ok, here's what getvar all reports:
(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.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -snip-
(bootloader) imei: -snip-
(bootloader) imei2: Not Support
(bootloader) meid: 99000499014851
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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
all: Done!
finished. total time: 0.035s
I bought the phone second-hand, it was running a custom ROM (SkyDragon) with cid already set to 11111111 and I wanted to return it to stock. I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
I've also tried restoring assorted TWRP backups, installing new roms and so on, directly flashing boot.img, things seem to flash ok but the phone just boots direct into fastboot.

Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!

roseyhead said:
Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!
Click to expand...
Click to collapse
I'm glad you're all set. But for other users' benefit, here is a link to HTC's official Sprint RUU page, with instructions for flashing the RUU as well as a download link for Sprint M8 marshmallow RUU 6.20.651.3
Sprint RUU instructions page:
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Sprint M8 marshmallow RUU 6.20.651.3 Direct Link:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
Cheers

i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.16.654.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 99000499165808
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

roseyhead said:
I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
Click to expand...
Click to collapse
Happy to see your sorted it out.
I agree it appears to be the Sprint version, based on the the MID (0P6B70000) and product name (m8_whl). While the MID can be modified, the product name is typically not (never seen a mod method for that - so the product name is very reliable).
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
---------- Post added at 11:38 AM ---------- Previous post was at 11:30 AM ----------
mushfiq20 said:
i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version-main: 2.16.654.4
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
Click to expand...
Click to collapse
This is Sprint version, same as OP based on the model ID and product name. Although main version would indicate the Sprint Harmon Kardon version. RUU can be found at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
The M8x designation on the back cover can't be trusted in this case. The back cover has been replaced to remove the "Sprint" logo branding. We've seen several phones like this (back cover replaced to remove evidence of branding) on the forum. You have to go by the getvar data.
Also, be sure to remove your IMEI and serial number from the getvar output. These are personal data, and should never be posted online.

redpoint73 said:
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
Click to expand...
Click to collapse
Thanks a lot for the tip! I'll bear that in mind going forward.

Hi there I seem to be having similar issues. I purchased a refurbished M8. The case indicates 0P6B110 M8x however fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [REDACTED]
(bootloader) imei: [REDACTED]
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237658
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Going off the info in the thread I downloaded RUU 6.20.651.3.
While verifying I want to update the ROM version it states:
From:
Image Version: 1.54.651.8
To:
Image Version: 6.20.651.3
After clicking next and progressing I get Error 155.
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.

metalbassist33 said:
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.
Click to expand...
Click to collapse
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3

ckpv5 said:
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3
Click to expand...
Click to collapse
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?

metalbassist33 said:
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?
Click to expand...
Click to collapse
No .. not needed, run Lollipop RUU then do OTA to Marshmallow

Help finding correct ROM

Hey all,
I recently bought a "new but unboxed" M8 off ebay which was sold as unlocked. It came with 4.4.2 but did not have an update button (it was literally missing) so tried to update it manually.
I have tried numerous RRU's and Stock ROMs but none have succeeded to allow me past the bootloader while the RUU.exe just fails each time error 155. The only ROM which worked was Skydragon but wish to go back to stock Marshmallow for OTA.
I get the feeling my phone is actually a US variant Sprint by looking at the codes, but please correct me if I am wrong ? It is also a developer CID of 11111111, so should be able to use any ROM ?
Here are the details
C:\HTCM8Rom>fastboot getvar all
(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-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: xxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) product: m8_whl
(bootloader) platform: xxxxxxxxxxxxxxxxxxxx
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
It is also rooted.
First thing - should the "version - main" be blank like this?
The MID seems to point to a sprint carrier but I am in the UK - will this affect me?
I have gone through an entire folder of different stock roms/recoveries etc but feel at a dead end.
Error codes I have had are : 41 model id check fail 24 parsing android-info fail RUU error 155 unknown
So in short - what are my options here?
Do I change the MID (is this safe?) and get a corresponding set of ROM, Recovery and Firmware?
I have followed these guides - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
http://forum.xda-developers.com/showthread.php?t=2701376 and many, many others! (For which there are no files for this MID)
I had been trying the following as I had misread my MID of 0P6B70000 for it.
CID HTC__001 & HTC__J15
MID 0P6B67000
6.21.401.1
I feel so overwhelmed with the sheer number of different versions/models I would really appreciate some help.
Thanks in advance,
Hiijinx

Hiijinx said:
Hey all,
I recently bought a "new but unboxed" M8 off ebay which was sold as unlocked. It came with 4.4.2 but did not have an update button (it was literally missing) so tried to update it manually.
I have tried numerous RRU's and Stock ROMs but none have succeeded to allow me past the bootloader while the RUU.exe just fails each time error 155. The only ROM which worked was Skydragon but wish to go back to stock Marshmallow for OTA.
I get the feeling my phone is actually a US variant Sprint by looking at the codes, but please correct me if I am wrong ? It is also a developer CID of 11111111, so should be able to use any ROM ?
Here are the details
C:\HTCM8Rom>fastboot getvar all
(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-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: xxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) product: m8_whl
(bootloader) platform: xxxxxxxxxxxxxxxxxxxx
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
It is also rooted.
First thing - should the "version - main" be blank like this?
The MID seems to point to a sprint carrier but I am in the UK - will this affect me?
I have gone through an entire folder of different stock roms/recoveries etc but feel at a dead end.
Error codes I have had are : 41 model id check fail 24 parsing android-info fail RUU error 155 unknown
So in short - what are my options here?
Do I change the MID (is this safe?) and get a corresponding set of ROM, Recovery and Firmware?
I have followed these guides - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
http://forum.xda-developers.com/showthread.php?t=2701376 and many, many others! (For which there are no files for this MID)
I had been trying the following as I had misread my MID of 0P6B70000 for it.
CID HTC__001 & HTC__J15
MID 0P6B67000
6.21.401.1
I feel so overwhelmed with the sheer number of different versions/models I would really appreciate some help.
Thanks in advance,
Hiijinx
Click to expand...
Click to collapse
Yes it's a Sprint phone. You need Sprint firmware for that. 6.20.651.3 is the newest for Sprint. If the firmware doesn't contain the 651 part, then you can't flash it to your phone.
Your version-main is blank from using an outdated TWRP that had a bug in it (2.7.x.x) Use TWRP 2.8.7.0 or newer. If you flash new TWRP, then firmware after, the version-main will show your firmware version properly.
I'm not sure if your phone will work on another network besides the Sprint network. Maybe, if there is a CDMA carrier in the UK, it might work. But I wouldn't be surprised if it didn't.

Thanks for the informative response, this should help a lot.
The phone worked on Skydragon (except the phone wouldn't ring when called like it was on constant silent mode) which is why I decided to attempt flashing it to stock.
Is there no way to unlock it to get rid of the Sprint? Its not a network I have ever heard of here in the UK. Really annoyed at the eBay seller, luckily I haven't left feedback yet so might just complain.

Hiijinx said:
Is there no way to unlock it to get rid of the Sprint? Its not a network I have ever heard of here in the UK. Really annoyed at the eBay seller, luckily I haven't left feedback yet so might just complain.
Click to expand...
Click to collapse
I don't know if there is a way to SIM unlock the Sprint version. It should never have been purchased for use on any network except Sprint. If the eBay listing was at all misleading about this (claiming that it was unlocked, Euro version, etc.) you may have some recourse through eBay, if the seller will not give you a refund or exchange (you should definitely try the seller first).

People always confused with MID 0P6B67000
Sprint is 0P6B70000
This 0P6B67000 is middle east/egypt variant, running also x.xx.401.x but the one for normal EU.

ckpv5 said:
People always confused with MID 0P6B67000
Sprint is 0P6B70000
This 0P6B67000 is middle east/egypt variant, running also x.xx.401.x but the one for normal EU.
Click to expand...
Click to collapse
Wow. To tell you the truth, I glanced and saw 70000, probably because I didn't know about 67000 and my brain just focussed on the "7".
Thanks for the information. I'll look out for it in the future.

xunholyx said:
Wow. To tell you the truth, I glanced and saw 70000, probably because I didn't know about 67000 and my brain just focussed on the "7".
Thanks for the information. I'll look out for it in the future.
Click to expand...
Click to collapse
here it is not mentioned about your reply; it's about the bottom part of the post #1. the answer given by you is exactly correct. I think your brain focuses on numbers correctly.