Related
****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.
BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.
Its been few days that I am going through HTC M8 forums and nothing seems to help. I got a HTC One M8 which is rooted now there are updates available but they won't install because its a custom software and I should revert to Official stock.
My Question is Simple, How can I revert to original stock?
My Phone is S-OFF
****Unlocked****(But I can lock if needed)
Software Number: 4.16.401.10
HTC Sense 6.0
CID:1111111
I have TWRP recovery 3.2 installed.
Somebody, anybody please give me a link to Rom that will take me back to official and Can I actually install Marshmallow?
Any help is appreciated.
:::Life is so much easier with samsung but I just love this phone.
cryptdweller said:
Its been few days that I am going through HTC M8 forums and nothing seems to help. I got a HTC One M8 which is rooted now there are updates available but they won't install because its a custom software and I should revert to Official stock.
My Question is Simple, How can I revert to original stock?
My Phone is S-OFF
****Unlocked****(But I can lock if needed)
Software Number: 4.16.401.10
HTC Sense 6.0
CID:1111111
I have TWRP recovery 3.2 installed.
Somebody, anybody please give me a link to Rom that will take me back to official and Can I actually install Marshmallow?
Any help is appreciated.
Click to expand...
Click to collapse
Excellent guide and needed files to return to stock for OTA: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Now the question is, which stock backup and recovery do you need to use? Is the version number you posted (4.16.401.10), the OS number shown on the bootloader screen (this is what you want to match) or is it the software number in Settings?
No need to relock bootloader to OTA. And since you are s-off, there is really no reason to relock; and I do not recommend relocking (it actually doesn't "enable" anything to relock, that s-off already doesn't allow - but if you relock, that will prevent you from flashing things like custom recovery).
cryptdweller said:
:::Life is so much easier with samsung but I just love this phone.
Click to expand...
Click to collapse
Every device has its nuances, and learning curve. When I got my first Samsung device, I didn't know what Odin or any of that was, and had to learn.
thank you mate, I'll go through the link and i hope it works...
Oh its the Software number in the setting that I have written here, can I download any rom or should I match the number?
Thank you again.
cryptdweller said:
thank you mate, I'll go through the link and i hope it works...
Oh its the Software number in the setting that I have written here, can I download any rom or should I match the number?
Click to expand...
Click to collapse
You definitely can NOT install any ROM, if you want OTA updates. You need to match the version number shown under "OS" on the bootloader screen.
Additionally, SuperCID does not make the phone "universal" (as you suggested in your PM to me). You need to match the firmware version number (OS number on bootloader screen, as mentioned) and you need to also match MID, in order for OTAs to work.
What does it say for OS on the bootloader screen?
If you installed a custom ROM, the software number in Settings won't match the OS number on the bootloader screen. The software number in Settings just refers to the custom ROM, which is pretty much irrelevant when returning to stock for OTA.
M8_UL PVT SHIP S OFF
CID 111111111
HBOOT - 3.19.0.0000
OS:4.28.502.1
How do I check the MID?
cryptdweller said:
M8_UL PVT SHIP S OFF
CID 111111111
HBOOT - 3.19.0.0000
OS:4.28.502.1
How do I check the MID?
Click to expand...
Click to collapse
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting). I need to see more info, not just the MID, in order to see what's going on. Reason being, the OS number (x.xx.502.x) is for the AT&T version, but the product ID is not (AT&T version is M8_UL_CA).
< waiting for device >
(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: 4.28.502.1
(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: 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: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.197s
Wow, well it looks like it was originally a T-Mob US version, made s-off and SuperCID, flashed with AT&T firmware, and Euro based custom ROM installed.
Complicated, eh?
How you return to "stock" (and what "stock" means) is somewhat up to you, and also the requirements of your local carrier.
Do you know what bands your carrier uses for 3G and LTE?
Hi,
A few weeks ago my M8 developed a serious problem - basically all calling functionality stopped working. The android basic dialer get's stuck dialing a number and eventually the system presents the standard 'Dialer is not responding' message, calling my number from another phone always gets an engaged tone, Skype and Whatsapp calling fails without any error messages. Also data connection fails, text messaging fails intermittently, music player fails to play through speakers and fails intermittently through Bluetooth.
This didn't occur after the install of any apps and the phone didn't experience any physical shocks, but seemed to happen after a Skype call.
Naturally, I tried factory reset first, but to no avail.
As the phone is now out of warranty I rooted it and installed the Android Revolution ROM onto it. (PS thanks to everyone for the wealth of help and guides to carrying this out.) I was hoping a new ROM would fix the problem, but it hasn't.
So, I'm assuming the problem is at a very low level, with some device driver(s).
My question is, does the ROM include all of the device drivers? Do I need to do something else to get the basic device drivers reinstalled? I note the download site for the Android Revolution ROM also has links to firmware downloads - should I also install the firmware download?
Any help would be much appreciated.
usmhot
I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Bump. Can anyone tell me if there is an RUU available for my variant?
usmhot said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
usmhot said:
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
Click to expand...
Click to collapse
Some other versions (besides US) have RUU, but unfortunately I don't think your version (H3G) is one of those.
One idea, which I touched upon before, is to flash the firmware (since you don't think flashing the ROM alone won't help - the firmware is basically the "lower level drivers" you are talking about), then restore a stock TWRP backup (ROM). Its as close to a RUU "factory image" as you'll get, since there is no RUU (that I am aware of).
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.
redpoint73 said:
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.
Click to expand...
Click to collapse
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
i.e. using the following sequence of commands
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
Click to expand...
Click to collapse
but it's not working for me - it still shows as *** Unlocked ***
Couple of things:
1. if I issue the command adb devices (after a full reboot to system) first I get an error message "adb server version (31) doesn't match this client (36)" and my device id is listed anyway, but if I reissue the command I get my device id listed without the error. Do I need a different version of adb?
2. do I need to unroot as well as relock? (If so, is there a guide somewhere?)
usmhot said:
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
Click to expand...
Click to collapse
You're making much harder on yourself than need be.
The process to relock the bootloader is in the instructions for flashing the firmware, which I already directed you to (Post #5 of the previously linked thread). Near the bottom of that post, below all the download links (so maybe you missed seeing the instructions).
Relocking the bootloader is a single, easy fastboot command:
fastboot oem lock
This will make the bootloader say RELOCKED, which is sufficient to flash the firmware.
The guide you linked is to make it say LOCKED (versus RELOCKED) and the only reason to do that is to fool HTC into thinking it was never UNLOCKED for warranty purposes. You don't need to do this, and you can't since the guide clearly says s-off is required, which you do not have (you are s-on).
Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.
usmhot said:
Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.
Click to expand...
Click to collapse
Glad it worked. You're quite welcome, and happy to have helped!
Hey guys, if somebody could help me resolve my problem i´ll be eternally gratefully. A couple of days before i bought an international version of the htc m8 (0P6BIMG100), it had kitkat 4.4.4, and i want to upgrate the sistem to marshmallow, so, reading in the multiple forums i found a tread in this site that teaches how to convert the phone to google edition, when i started the fastboot it was locked (i unlocked it) and S-off with supercid 11111111 (the phone came rooted). I follow the instructions step by step and after the installation of the RUU finished, the phone boots in to the black google screen and enter in fastboot. So, i tried reversing the process and go to the sense version again, a friend (who happen to have an htc m8) help me do it and we manage to restore de backup that i made in TWRP. After that, he toldme to install a custom rom, i decide to install the Insert Coin Enhaced "ice-8.2.2_M8_UHL_MM60_SENSE80GP_HTC_WWE_6.12.401.4". And for my surprise, it worked!! However, the phone didn´t recognice de wifi antena, the sim, the front camera, etc and the imei, baseband, and all that stuff said "not available", after a few minutes, the phone began to reboot. Looking through different XDA forums many said it was the kernel, so i let my friend flash the google edition kernel (i still don´t know why i let him do that). After that, the phone simply reboots in the fastboot screen, so again reading in the forums i found that maeby was not a kernel issue, but a firmware thing. So, i been installing a hell of firmwares and one by one trying to install the rom, but it jus´t don´t work. The last upgrate that i did via "ext_card" (i rename it 0P6BIMG) end saying in red letters "device halted due to large image update fail" (i wipe de data of the microsd, i change the microsd for ahother one, and nothing) and a red flag appeared saying "image update fail!". After this, no matter which firmware i try to install it, i cant find the right one, besides, now in the fastboot getvar all command the "version-main: " is blank, it shows nothing. I also found the RUU.exe trends and i tried some of them, but they get stock in the "sending information 0/7 screen". After a while i enter again in the fastode screen with the abd command. So if anybody could help me i´ll be glad to invite the beers, i need the phone for work and it´s been a hell of 5 straight days without resolving this issue, these are the specs that are showed in the fastboot mode screen:
*** Software status official ***
*** UNLOCKED ***
M8_WLV PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-
eMMC-boot 2048MB
------------------------------------
These are the specs in the "fastboot getvar all":
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT445SF02290
imei: ***************
imei2: Not Support
meid: **************
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Does anyone know what can i do? Apologies for the language, i´m not a native english speaker
Your device is not International GSM (m8_ul or m8_uhl) but it is a Verizon CDMA device (m8_wlv).
Those ROMs you tried are for m8_ul or m8_uhl, won't work on your device.
Read this on how to fix it - https://forum.xda-developers.com/htc-one-m8/help/m8-bricked-flash-rom-neither-restore-t3535671
Well...
ckpv5 said:
Your device is not International GSM (m8_ul or m8_uhl) but it is a Verizon CDMA device (m8_wlv).
Those ROMs you tried are for m8_ul or m8_uhl, won't work on your device.
Read this on how to fix it - https://forum.xda-developers.com/htc-one-m8/help/m8-bricked-flash-rom-neither-restore-t3535671
Click to expand...
Click to collapse
But if is a CDMA why does the phone have a nanosim entry?
I follow the given istructions but none of them works, after keep reading other answers in other post i found the 1.57.114.2 firmware sugestion, i rename it to "0P6BIMG.ZIP" and was able to run it in the HBOOT menu, now these are the specs that are showed in the bootloader screen:
M8_WLV PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.2133156.UA10G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.57.114.2
eMMC-BOOT 2048MB
Apr 10 2014, 01:18:21.1
----------------------------------------------------------------
These are the specs showed in the ´fastboot getvar all´ command:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA10G
version-cpld: None
version-microp: None
version-main: 1.57.114.2
version-misc: PVT SHIP S-OFF
serialno: HT445SF02290
imei: ***************
imei2: Not Support
meid: ***************
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
--------------------------------------------------
I tried to install again the Insert Coin Enhaced "ice-8.2.2_M8_UHL_MM60_SENSE80GP_HTC_WWE_6.12.401.4", for my surprise the TWRP flashed it quick, but after the reboot it was stuck in the white screen with the HTC logo in green color, so...., i wipe it all, reinstall de "1.57.114.2.zip" and well, i´m still reading posts about the subject, any idea of what can i do sir?. By the way, thank you very much for the orientation
No matter what GSM firmware that you install, they won't work on your CDMA device.
You can install those GSM firmware like 1.57.114.2 because the MID is 0P6B10000
If you ever successful install a ROM on these firmware, you won't get any signal, your SIM won't work. Flashing these GSM firmware on CDMA device may brick your radio permanently.
What you need to do :
1. Change back the MID 0P6B10000 to original 0P6B20000
read this - https://forum.xda-developers.com/showpost.php?p=70504345&postcount=35
2. Install correct firmware to fix the radio first
https://forum.xda-developers.com/showpost.php?p=70502435&postcount=31
3. Install Marshmallow firmware which already include TWRP - https://www.androidfilehost.com/?fid=24438995911973227
4. Install your custom ROM that you want.
GPE - install this and select Verizon while in Aroma - https://forum.xda-developers.com/ve...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Or you can install any ROM in this section - https://forum.xda-developers.com/verizon-htc-one-m8/development
Or you can install some ROM with Verizon support in this section - https://forum.xda-developers.com/htc-one-m8/development
And I believe all the Nougat ROM support Verizon too.
lalomayen said:
But if is a CDMA why does the phone have a nanosim entry?
Click to expand...
Click to collapse
When we say "CDMA version" M8, it means it supports CDMA in addition to GSM and LTE networks. Mainly, so Verizon customers can use other carrier nanoSIMs while travelling to foreign countries.
The presence of the nanoSIM slot does not make it the "GSM" variant of the M8.
You have the Verizon CDMA version M8. There is not question about it.
lalomayen said:
I follow the given istructions but none of them works, after keep reading other answers in other post i found the 1.57.114.2 firmware sugestion
Click to expand...
Click to collapse
There is no reason to believe this firmware will work with your device.
You need to follow the advice given by ckpv5, he knows what he is talking about. If you get stuck with the process, tell us specifically what step, what the specific results were, error messages, etc. (just saying it didn't work, isn't goo enough) If you got stuck, it was likely pilot error; and we can probably troubleshoot, and see what went wrong, and properly advise you.
Ok, so i am in a somewhat similar situation to you. There are a few differences though. The first is that the phone has S-on. The owner said that the phone never had the bootloader unlocked, neither was it rooted. When the phone is turned on, it says:
*** Software status: Modified ***
*** Locked ***
***Security Warning ***
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OS-2.10.771.1
eMMC-boot 2048MB
Apr 22 2016,12:28:26.0
When i connected it to the pc and ran fastboot getvar all, I got:
(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: 2.10.771.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(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: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Any ideas what steps to take? Thanks in advance
ze410t said:
Ok, so i am in a somewhat similar situation to you. There are a few differences though. The first is that the phone has S-on. The owner said that the phone never had the bootloader unlocked, neither was it rooted.
Click to expand...
Click to collapse
Respectfully, your situation bears little, if any, similarity to the OP. His is s-off, with custom recovery, and trying to install custom ROMs. Further, he has the Verizon version (which as a lot of unique peculiarities versus other variants), with botched install of another version's firmware; which on the Verizon version in particular, results in broken radio (no SIM).
You have a very different M8 version, and a very different situation (close to stock - although I think root was at least attempted). And you haven't actually described what your question or issue is. The OP's problem is the wrong firmware, and custom ROMs don't work; but those issues don't apply to you.
I see you've started another thread here. I'd suggest sticking to that thread, rather than posting to this one. There are too many differences between your phone and situation to the OPs. Further discussion here (while also helping the OP in parallel) will probably result in unnecessary confusion.
redpoint73 said:
Respectfully, your situation bears little, if any, similarity to the OP. His is s-off, with custom recovery, and trying to install custom ROMs. Further, he has the Verizon version (which as a lot of unique peculiarities versus other variants), with botched install of another version's firmware; which on the Verizon version in particular, results in broken radio (no SIM).
You have a very different M8 version, and a very different situation (close to stock - although I think root was at least attempted). And you haven't actually described what your question or issue is. The OP's problem is the wrong firmware, and custom ROMs don't work; but those issues don't apply to you.
I see you've started another thread here. I'd suggest sticking to that thread, rather than posting to this one. There are too many differences between your phone and situation to the OPs. Further discussion here (while also helping the OP in parallel) will probably result in unnecessary confusion.
Click to expand...
Click to collapse
Oh ok :/ sorry about that. This was the only post that i found that i thought was similar. My apologies. Carry on!
ze410t said:
Oh ok :/ sorry about that. This was the only post that i found that i thought was similar. My apologies. Carry on!
Click to expand...
Click to collapse
No worries. I posted in the thread you started, and will try to help you there.
Stuck
ckpv5 said:
No matter what GSM firmware that you install, they won't work on your CDMA device.
You can install those GSM firmware like 1.57.114.2 because the MID is 0P6B10000
If you ever successful install a ROM on these firmware, you won't get any signal, your SIM won't work. Flashing these GSM firmware on CDMA device may brick your radio permanently.
What you need to do :
1. Change back the MID 0P6B10000 to original 0P6B20000
read this - https://forum.xda-developers.com/showpost.php?p=70504345&postcount=35
2. Install correct firmware to fix the radio first
https://forum.xda-developers.com/showpost.php?p=70502435&postcount=31
3. Install Marshmallow firmware which already include TWRP - https://www.androidfilehost.com/?fid=24438995911973227
4. Install your custom ROM that you want.
GPE - install this and select Verizon while in Aroma - https://forum.xda-developers.com/ve...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Or you can install any ROM in this section - https://forum.xda-developers.com/verizon-htc-one-m8/development
Or you can install some ROM with Verizon support in this section - https://forum.xda-developers.com/htc-one-m8/development
And I believe all the Nougat ROM support Verizon too.
Click to expand...
Click to collapse
Ohh, ok, got it now, i don´t know if 0P6B20000 was the original, but i follow the instructions in step 1, the TWRP 2.8.7.0 didn´t started in my phone, the 2.0.7.2 version did (i don´t know why), i follow the instructions: boot to recovery
Mount - system
then open command prompt from your adb/fastboot folder
then type
adb shell
follow by comand: echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
i get an error message ""dd" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable." ("Dd" is not recognized as an internal or external command, Program or executable batch file")
redpoint73 said:
When we say "CDMA version" M8, it means it supports CDMA in addition to GSM and LTE networks. Mainly, so Verizon customers can use other carrier nanoSIMs while travelling to foreign countries.
The presence of the nanoSIM slot does not make it the "GSM" variant of the M8.
You have the Verizon CDMA version M8. There is not question about it.
There is no reason to believe this firmware will work with your device.
You need to follow the advice given by ckpv5, he knows what he is talking about. If you get stuck with the process, tell us specifically what step, what the specific results were, error messages, etc. (just saying it didn't work, isn't goo enough) If you got stuck, it was likely pilot error; and we can probably troubleshoot, and see what went wrong, and properly advise you.
Click to expand...
Click to collapse
I see, i´m new in this subject, thanks for the observations, i´ll submint the issues in the order that they appear
lalomayen said:
I see, i´m new in this subject, thanks for the observations
Click to expand...
Click to collapse
No problem. The Verizon version is pretty peculiar, so its easy to get confused by it. In fact, for this reason I typically do not recommend anyone buy this or the Sprint variant, unless they are located in the US actually using that particular carrier (Verizon or Sprint).
Hello I bought M8 from somebody, it is unbranded European model i think, phone is rooted and carrier unlocked as im using it in asia. it comes with android 5.0.1, I want to update to stock marshmallow for this variant. I have been trying to do on my own but it only confused me more. Im not sure if i have custom rom or if because im rooted, because At the time moment it doesnt offer any software updates from the main menu.
Some info abt phone.
Its model id at back is Op6B100,
Android version 5.0.1
Software number 4.18.708.12
Build number 4.18.708.12
In the bootloader menu I have
Software status: Official
Locked ( i think it means bootloader)
M8_UL PVt SHIp s-off
Cid-11111111 (but if I check with cidgetter it says t-mob010). So it confused me because according to its model its supposed to be european model but in fastboot it says 11111111.
HBoot 3.19.0.0000
I dont have twrp installed.
So please tell me where to go from here. I want to either from here go direct to stock android 6 for this M8 variant or go back to stock condition and get ota update. I prefer to lose the root. So please tell me which stock firmware I need, and do I need to change cid, remove root, before that? Also i would like not to brick my device in process.. Thanks.
Also my device is carrier unlocked at the moment so Im hoping this shouldn't affect that. Thanks
.??
Post fastboot getvar all result (delete serial & imei no. before posting) then someone will be able to help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000 ( on the back its 0P6B100)
(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!
I would like to install htc marshmallow update, kindly tell me how I can do that.
First you need to change MID to EU
Then install EU marshmallow RUU
Follow this guide - https://forum.xda-developers.com/showpost.php?p=70575580&postcount=12
Do i need twrp to change MId? And do I need to unlock bootloader before flashing RUU.
Kashi88 said:
Do i need twrp to change MId?
Click to expand...
Click to collapse
Yes as said in the guide unless you're running a rooted ROM.
Kashi88 said:
And do I need to unlock bootloader before flashing RUU.
Click to expand...
Click to collapse
No
ckpv5 said:
Yes as said in the guide unless you're running a rooted ROM.
No
Click to expand...
Click to collapse
ok thanks , I keep getting this error in the adb fastboot when flashing ruu zip . target reported max download size ( shows some big number bytes) .
Read the guide again .. you need htc_fastboot not normal fastboot.
At the end of the guide it shows 2 other methods on how to install RUU zip. Pick one thar you think it is easier for you.
ckpv5 said:
Read the guide again .. you need htc_fastboot not normal fastboot.
At the end of the guide it shows 2 other methods on how to install RUU zip. Pick one thar you think it is easier for you.
Click to expand...
Click to collapse
thank you so much i installed it with the micro sd method, and everything worked out smooth. just one last question, if in future i have to reset my phone from settings menu or from bootloader menu (volume down key), will I go back to android lollypop version or remain on this 6.0. thanks again
remain on this 6.0
ckpv5 said:
remain on this 6.0
Click to expand...
Click to collapse
hi..i am suffering from black bootloader issue..cant see any option..is there any solution?
dr.estiack said:
hi..i am suffering from black bootloader issue..cant see any option..is there any solution?
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. It clutters up the forum, and makes it confusing for those trying to help you. Your post is also not related to the topic of this particular thread.