Hi all,
Have just got a HTC One M8 and it's been shipped already S-OFF, the phone still says locked and so far as i'm aware it should read S-ON ??
My question is, if I was to unlock the bootloader and root the device, install a custom recovery and eventually a ROM with it being already S-OFF would i encounter any issues?
The phone looks to be either a developer phone or just a factory S-OFF phone ?
Many thanks, screen shot attached.
PS: Apologies for the lack in quality apparently I can only upload 256KB pics to XDA.
Specs are as follows.
HTC M8 Silver
CID 11111111
UL PVT SHIP S-OFF
HBOOT 3.16.0.000
Radio - 1.16.213156.UA15G
Factory unlocked international M8.
Couldn't find any more information so hope this is enough.
Many thanks.
Did you buy the phone new (like from an official store or carrier) or used?
I'm guessing its used, and the previous owner unlocked the bootloader, SuperCID, S-off; then returned the phone to LOCKED status (possible with S-off).
Although its not unheard of for phones to ship S-off, its pretty rare. And I don't think I've heard of a phone S-off and SuperCID (11111111) direct from factory, so the combination of the 2 is rather suspicious.
redpoint73 said:
Did you buy the phone new (like from an official store or carrier) or used?
I'm guessing its used, and the previous owner unlocked the bootloader, SuperCID, S-off; then returned the phone to LOCKED status (possible with S-off).
Although its not unheard of for phones to ship S-off, its pretty rare. And I don't think I've heard of a phone S-off and SuperCID (11111111) direct from factory, so the combination of the 2 is rather suspicious.
Click to expand...
Click to collapse
Actually it wasn't it was brand new. I have no idea m8, i thought it was strange when i went into the bootloader.
never mind
(Solved) Can root and unlock bootloader, shouldn't pose an issue i'm told.
Sorted
dladz said:
(Solved) Can root and unlock bootloader, shouldn't pose an issue i'm told.
Sorted
Click to expand...
Click to collapse
Yeah, you should have two options here
(Only posting for reference)
Flash an ENG (engineering) HBOOT
Or
HTC Dev the phone
With either you can flash a recovery via Fastboot and flash a SuperSU.zip
And being as you're already S-off, then you can write to boot, so you can flash ROMs after doing the above as well
Sent from my m7spr
ajbiz11 said:
Yeah, you should have two options here
(Only posting for reference)
Flash an ENG (engineering) HBOOT
Or
HTC Dev the phone
With either you can flash a recovery via Fastboot and flash a SuperSU.zip
And being as you're already S-off, then you can write to boot, so you can flash ROMs after doing the above as well
Sent from my m7spr
Click to expand...
Click to collapse
nice one m8, think i'll go down the HTC Dev route, then recovery.
Great phone.
I have a similar problem , even after rooting the phone I was unable to update to any custom rom due to firmware status,
here is the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA4xxxxxxxx
(bootloader) imei: ---------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Eeshaann said:
I have a similar problem , even after rooting the phone I was unable to update to any custom rom due to firmware status,
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. You are already being helped in the "HELP THREAD".
Also, don't "zombie" threads that have been dead for almost 3 years. Your issue isn't that similar to the OP's (aside from s-off) anyway.
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...
**********************************************************************************
I updated my HTC M8 via OTA to Marshmallow (Android 6.0). Sense 7 is a letdown so I'd like to install CyanogenMod on it WITHOUT voiding my warranty by unlocking the bootloader via htcdev.com.
Therefore I tried SunShine S-Off but it can't apply a temp-root on 6.0 anymore. Afaik a perma root also can't be applied without unlocking the bootloader first.
I tried to flash TWRP via ADB but it doesn't work because of the lock.
Are there any options to gain root access/flash the ROM without voiding the warranty of my 6.0 M8?
Is there a particular reason you need to attempt to temp-root off Marshmallow (6.0)? If you want to apply a temp root / CM, why not flash an older version RUU (Kit Kat or Lolipop) so that the method you used formerly works again?
You are correct in everything else-- bootloader must be unlocked in order to flash a custom recovery or apply a perma-root as far as I know. Though, with S-OFF, you can clear the "Relocked" and "Tampered" flags without too much trouble, which would circumvent the voided warranty problem to begin with.
@Anonaru:
That's a very good idea.
However I couldn't find RUUs that don't require S-OFF. Can you point me into the right direction on how to downgrade my M8?
As far as I know, any stock RUU that matches your phone's M/CID can be flashed so long as you have either s-off -OR- a locked bootloader. The "fastboot getvar all" command ought to get what you need in this regard. I can point you in the right direction if you let me know which M8 you have
Here is the output of `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: HT49KWM03642
(bootloader) imei: 357871054068419
(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
Flashing an older version RUU won't work in this case. You can't downgrade unless you are S-OFF.
Why won't it work @robocuff? Anonaru said it required EITHER S-OFF or a locked bootloader.
Regardless of the locked bootloader, you have to be S-Off in order to flash an older version RUU. Without it, you can only flash your current version or a newer one.
@robocuff is this true? My fallback has been flashing a Kit Kat RUU for a long time now, up to and including after I took the Mallow OTA from Sprint and / or after a custom ROM. Am I just lucky, then?
What @robocuff stated is true. You can only run an "older" version ("downgrade) RUU if you have s-off.
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
Ok so over the last few days i've read hundreds of posts on how to reset the m8 back to stock, and yet not a single one works for me.
My CID is: H3G_001
to which my understanding is that there is no RUU. My device is currently running skydragon rom and kernel but is not a GPE edition, and for some reason I can't see my version-main (it is just blank).
So my tactic was trial and error download a bunch of nandroid backups and hope to **** one of them works, and from what I've read if I have Hboot 3.19.xx.x.x.x then i need a backup with 3.32.710.9.
Except, i keep finding posts by a guy called ckpv5 which link me to a sourcefourge, which no longer contain the relevant backups.
All I want to do is sell my phone, and to do that it needs to just be on a stock rom, with a stock kernel and a locked bootloader.
Post the result of fastboot getvar all ( after removing serial and imei numbers )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Post the result of fastboot getvar all ( after removing serial and imei numbers )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
(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-ON
(bootloader) serialno: **hidden**
(bootloader) imei: **hidden**
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__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: a3d0cb0d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thespragg said:
(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-ON
(bootloader) serialno: **hidden**
(bootloader) imei: **hidden**
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__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: a3d0cb0d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You don't need x.xx.710.x
You need x.xx.771.x
You can restore 3.32.771.10 stock backup then flash stock recovery and do OTA till the marshmallow ( from ckpv5 thread )
or you can restore 6.13.771.4 stock backup then reboot to bootloader ( relock it ) and flash 6.13.771.4 signed firmware ( also from ckpv5 thread )
Here is the thread
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Many thanks to ckpv5 for his work around the forum he have done a great work and helped a lot of people
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
You don't need x.xx.710.x
You need x.xx.771.x
You can restore 3.32.771.10 stock backup then flash stock recovery and do OTA till the marshmallow from ckpv5 thread
or you can restore 6.13.771.4 stock backup then reboot to bootloader ( relock it ) and flash 6.13.771.4 signed firmware also from ckpv5 thread
Here is the thread
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Many thanks to ckpv5 for his work around the forum he have done a great work and helped a lot of people
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
You and ckpv5 are my heroes. Was genuinely about to just condemn the phone haha, I'd stumbled across that thread before but not seem what i thought was the right version. Phone seems to be all up and running now, just installing stock recovery and OTA's.
Much love
thespragg said:
You and ckpv5 are my heroes. Was genuinely about to just condemn the phone haha, I'd stumbled across that thread before but not seem what i thought was the right version. Phone seems to be all up and running now, just installing stock recovery and OTA's.
Much love
Click to expand...
Click to collapse
Good for you
Add solved tag to the title
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
or you can restore 6.13.771.4 stock backup then reboot to bootloader ( relock it ) and flash 6.13.771.4 signed firmware ( also from ckpv5 thread )
Click to expand...
Click to collapse
I believe this sequence would result in no OS. If I'm not mistaken, flashing signed official firmware has that result. OP in that case will need to unlock the bootloader again (using existing unlock bin code, or get a new one from HTCDev.com), flash TWRP, install stock TWRP backup 6.13.771.4. Then flash stock recovery corresponding to 6.13.771.4 and relock bootloader (to return to "close to" stock).
OP should also note that relocking the bootloader is done with command: fastboot oem lock
And this will only result in it saying RELOCKED. There is no way to make it say LOCKED again (the factory condition) unless you s-off. And that isn't worthwhile, as s-off by sunshine is the only working method, and costs $25. And IMO not worthwhile to spend money like that, to sell an old phone.
What I would recommend, is full disclosure to tell the buyer that the phone was modded, but returned to stock, aside from the RELOCKED bootloader.
redpoint73 said:
I believe this sequence would result in no OS. If I'm not mistaken, flashing signed official firmware has that result. OP in that case will need to unlock the bootloader again (using existing unlock bin code, or get a new one from HTCDev.com), flash TWRP, install stock TWRP backup 6.13.771.4. Then flash stock recovery corresponding to 6.13.771.4 and relock bootloader (to return to "close to" stock).
OP should also note that relocking the bootloader is done with command: fastboot oem lock
And this will only result in it saying RELOCKED. There is no way to make it say LOCKED again (the factory condition) unless you s-off. And that isn't worthwhile, as s-off by sunshine is the only working method, and costs $25. And IMO not worthwhile to spend money like that, to sell an old phone.
What I would recommend, is full disclosure to tell the buyer that the phone was modded, but returned to stock, aside from the RELOCKED bootloader.
Click to expand...
Click to collapse
I'll be selling it to the store I work in, so I'll mostly likely also handle the sale of the phone, in which case I'll explain to them it's stock but has been tampered
redpoint73 said:
I believe this sequence would result in no OS. If I'm not mistaken, flashing signed official firmware has that result.....
Click to expand...
Click to collapse
no it won't as i did it with my friend's device
restore stock backup ( syatem and boot ) after full wipe
reboot to bootloader ( relock it ) then flash the signed firmware
The result was nearly stock condition ( considring it says relocked in bootloader )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
no it won't as i did it with my friend's device
restore stock backup ( syatem and boot ) after full wipe
reboot to bootloader ( relock it ) then flash the signed firmware
Click to expand...
Click to collapse
Thanks, good to know. Your way saves the OP a good number of steps. And if for some reason, it doesn't work, the OP has a backup plan, and can do as I outlined.
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