Hi all,
First of all, I found a thread describing the problem that I have, entitled : "(solved)Help with update To android M" . It was actually solved by "ckpv5". But my device is different, i.e. has different "fastboot getvar all" output, so I don't know how I should proceed.
The problem came up after my efforts, trying to update to Android 6. My device came initially with Android 5.1, OS version 4.16.401.. Via HTC sync manager and the RUU update process described in HTC's website, I was trying to update to Android 6, but without success. The device was initially registered in AT&T, but now it is on Q-Telecom, a provider in Greece. I did several things, obviously bad ones, and the problem is that I can no longer boot. I can access the bootloader only.
Below is the output of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: < empty >
(bootloader) imei: < empty >
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please note that I changed the CID from 11111111 to BS_US001, after I got in contact with HTC group. This was their suggestion
What should I do to update the device to Android 6?
Which .zip file should I use? I found a link with a suggestion on the proper .zips (I cannot post it here, as I am a new user)
Should I rename the .zip?
Should I put it to the microSD, in the root directory?
Best
khtc
Since you are S-OFF, if you know if your device was originally a GSM or a CDMA variant, you could flash any S-OFF RUUs found here. you may have to change your MID and CID to suit the RUU you would be flashing.
Alternately, you can flash just the appropriate firmware, TWRP and flash any CM/AOSP too.
Based on the main version 6.12.1540.4, it appears the firmware was updated (Developer's Edition MM firmware) at some point. You may be able to now run the 6.12.1540.4 RUU:
http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Try the above, and see what happens. If it doesn't work, take note of the specific error message, and any other observations, and post them for us to look at.
If the 6.12.1540.4 firmware was not correctly installed you may need to find and re-flash it, before you can RUU.
---------- Post added at 10:04 AM ---------- Previous post was at 09:59 AM ----------
rln_xda said:
Since you are S-OFF, if you know if your device was originally a GSM or a CDMA variant, you could flash any S-OFF RUUs found here. you may have to change your MID and CID to suit the RUU you would be flashing.
Click to expand...
Click to collapse
This would be another valid alternative, to "convert" to another M8 version (such as Euro) by RUU. Although for any official, signed RUU, the CID at least will definitely need to be changed. SuperCID should also work for most RUUs. So the advice from HTC to change from SuperCID was actually not necessarily great advice. Just the advice they give - since they don't really want you to modify the device.
This is actually a duplicate post. He solved his problem - https://forum.xda-developers.com/showpost.php?p=70463082&postcount=36
ckpv5 said:
This is actually a duplicate post. He solved his problem - https://forum.xda-developers.com/showpost.php?p=70463082&postcount=36
Click to expand...
Click to collapse
Thanks for clarifying.
To the OP, I know you are pretty new to the forums. But please read and follow the forum rules; which expressly instruct not to post the same issue in multiple places (cross posting).
Also, please be courteous, and if you've solved your problem, mark so in the thread you made. Although this point pretty much goes with the first one (you wouldn't need to mark it as "solved" if you hadn't posted to 2 different places, in the first place).
Thread closed, answer. bellow.
ckpv5 said:
This is actually a duplicate post. He solved his problem - https://forum.xda-developers.com/showpost.php?p=70463082&postcount=36
Click to expand...
Click to collapse
Related
hello guys,
I bought this used M8 last night, it was on Kitkat 4.4.4 with the 3.30.651.2 firmware and I wanted to update it to marshmallow (ota not available). I tried this one HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H9.zip throught the recovery, no error during install, after finishing it, it says no operating system installed, ok, I tried with terminal (adb) it says couldnt load the zip, ok, tried this 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, error with hboot,ok, tried this RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe, it says firmware not compatible (I dont know why since I am s-off and super carrier!?)
the seller told me, the phone is from UK, T-mobile unlocked, but the firmware says its a Sprint one.
All I want now is lollipop or marshmallow, not kitkat !
can you help me please ? just tell me where I messed up, I have some knowledge with android (samsung and LG) but I am kinda noob with HTC (my first phone)
thank you !
NB: the bootloader is unlocked
mehcih said:
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, error with hboot,ok, tried this RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe, it says firmware not compatible (I dont know why since I am s-off and super carrier!?)
Click to expand...
Click to collapse
You still need to match MID (not just CID) to run an RUU.
But its a good thing you did not successfully run those RUUs. Since your are most likely the Sprint version (based on the firmware number), it would have resulted in a brick (radio brick) if either of those RUUs installed.
You can't run other version RUUs on the Sprint M8, or you will brick.
To verify you have the Sprint (and I'm pretty sure already) do fastboot getvar all, and post the output (delete IMEI and serial number).
here it is
C:\Windows\system32>fastboot 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: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***************
(bootloader) imei: ******************
(bootloader) imei2: Not Support
(bootloader) meid: 99000499190574
(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
all: Done!
finished. total time: 0.034s
Click to expand...
Click to collapse
Yes, its the Sprint version. The product name (m8_whl) along with the main version number confirm this.
If the seller claimed it was T-Mobile, its incorrect. Depending on what you want from the device, this can be a big difference. For instance, you can't convert the Sprint version to be international (as already mentioned, running another version RUU will brick it). You may consider returning the phone due to incorrect, misleading description; if that is an option.
If you do choose to keep the device, you can update with the MM Sprint RUU at the bottom of the following page: http://www.htc.com/us/support/htc-one-m8-sprint/news/
Thank you my friend, I thought when the phone is S-off and superCid it means its like a full unlocked international version, I learnt something today , now I am gonna follow your link and give a feedback later.
one last question, is there a risk for losing the simlock after the update ?
mehcih said:
one last question, is there a risk for losing the simlock after the update ?
Click to expand...
Click to collapse
No.
same problem, error 155, tried 'fastboot oem lock' and still same error
(loading zip info fail ! Update Fail !)
***********************************************************************************
problem solved ! I had to update the firmware first then proceed to RUU...
**********************************************************************************
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.
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
Htc one m8
fastboot getvar all
(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.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT46PWM03644
(bootloader) imei: 3578710********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Is there a solution without s-off
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
with bootloader locked/unlocked state;
with s-on:
Failed
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
Tried nandroid backup
M8_UL_TWRP_Nandroid_6.12.401.4.zip
succefully flashed backup but stuck on htc logo
Failed
Please help
What is the problem? Is it not booting into the ROM?
when there was boot.the phone at the startup gave (unfortunately------- has stopped)error and also no back key home key visible.
wiped the device. it was all same.
tried RUU it was the same
unlocked the boot loader
and flashed
stock recovery
twrp recovery
then tried nandroid backup restore
the restore was succefull but the phone wont reach startup (tried 1Hour max)
one peculiar thing i notice.earlier when it was booting to startup i was unable to copy anything to internal or external memory as it would say device not ready or disconnected.but i was able to browse the folders.
My opinion partition problem.Need others help to sort out
Note all the files i have mentioned is checked with md5
My comments below in red font:
raffazila said:
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
None of these will ever work on your device, in the s-on configuration. The RUUs containing "BrightstarUS" are for the US Developer's Edition. They won't run on your phone, as they will fail CID and MID checks (your device has CID and MID - can't change these with s-on).
The one labeled "Europe" is for an older version (Lollipop) than what is installed on the phone (Marshmallow). This will fail version check. By definition, you can't "downgrade" by RUU with s-on
with bootloader locked/unlocked state;
with s-on:
Failed
with s-on, its absolutely mandatory to have a locked or relocked bootloader to flash RUU. Unlocked bootloader will make it fail
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
This is the correct RUU for your version, and should run with s-on. Saying it "Failed" with no other info, is not enough. Were their any error messages, other outputs, etc.? What commands did you use to run it? Were you in fastbootRUU mode?
I would suggest trying to run this again, with the bootloader RELOCKED, and you also need to use htc_fastboot, as the "generic" fastboot will not work with RUU.
Click to expand...
Click to collapse
Firstly it is good someone with good knowledge is answering my doubts.
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Finaly to say you have found the nearest problem which i was thinking too.
I will check and post.
@redpoint73 Problem soilved.Silly mistake.Thanks.
raffazila said:
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Click to expand...
Click to collapse
I can't tell what you are referring too, as the statement is really vague. Can you give more details?
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
raffazila said:
Problem soilved.Silly mistake.Thanks.
Click to expand...
Click to collapse
Its best if you posted the solution, and what the mistake was. Useful for those helping (to see whether we sent you on the right path), as well as anyone else reading which may have the same or similar issue.
No mistake is that silly when it comes to these devices. Its often just specific knowledge that was missing, or a detail you didn't catch before (which is an honest mistake, either way).
Linux user. Phone won't boot or go into recovery but can be accessed through fastboot. Biggest problem is not able to boot into recovery. My attempts to flash a new recovery .img fail as in https://forum.xda-developers.com/showthread.php?t=2758204.
But I don't know what to put in my android-info.txt to get this solution to work for me. Have S-OFF and RELOCKED boot status.
Any ideas would be great thanks - it is of course driving me mad! (er)
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.512.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 99000499755159
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: HTC__001
(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: 2e9b7c51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Solved it: Took 6.12.401.4_NoRedText_TWRP.zip mentioned elsewhere here. Then modified android-info.txt with my modelid and mainver and placed in new zip. Had to flash twice but it worked the second time. Thanks to all those that would have helped!
pir8don said:
Linux user. Phone won't boot or go into recovery but can be accessed through fastboot. Biggest problem is not able to boot into recovery. My attempts to flash a new recovery .img fail as in https://forum.xda-developers.com/showthread.php?t=2758204.
But I don't know what to put in my android-info.txt to get this solution to work for me. Have S-OFF and RELOCKED boot status.
Click to expand...
Click to collapse
You made the solution more complicated/convuluted than necessary; and possibly even dangerous (see more on that below). The reason it says "remote not allowed" when flashing TWRP, is very simple: you can't flash custom recovery with a locked or relocked bootloader, by definition.
The process to unlock bootloader on a Verizon/LRA version M8 with s-off (which yours is) is here: https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 09:13 AM ---------- Previous post was at 09:07 AM ----------
pir8don said:
Solved it: Took 6.12.401.4_NoRedText_TWRP.zip mentioned elsewhere here. Then modified android-info.txt with my modelid and mainver and placed in new zip. Had to flash twice but it worked the second time. Thanks to all those that would have helped!
Click to expand...
Click to collapse
I'm not sure your problems are solved. Once you flash a ROM and get the phone booted, you may (I expect) find the radio is broken (no signal). You can't flash any other (m8 version's) firmware to a Verizon/LRA version M8. You have to be extremely careful what you flash to the Verizon/LRA M8 with s-off. The radio brick is often reversible, but sometimes permanent.
The Verizon version is a bit of an oddball (and the LRA version even more so), in that it is designed to support the US Verizon network, which is a CDMA network. The device also supports GSM and LTE (some bands), but it's that CDMA support that makes the Verizon device (annoyingly) unique.
Yes it is now looking like I don't have radio. Is there a path now to a working radio. I applied https://forum.xda-developers.com/showthread.php?t=2708571 to unlock. Sometimes my ignorance is not bliss!
pir8don said:
Yes it is now looking like I don't have radio. Is there a path now to a working radio. Sometimes my ignorance is not bliss!
Click to expand...
Click to collapse
You can try the RUU meant for your device here: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
If you don't have a microSD card, let me know, and I'll point you to the fastboot install method.
If the RUU doesn't fix the radio problem, it's probably permanently radio bricked. The LRA version doesn't have many RUUs available (the above is the only one I know of) and without other RUUs, you don't have a way to fix the radio.
Thanks heaps RedPoint. It all worked fine and the radio is working too. Your assistance is much appreciated