Related
Just got M8 today and rooted but stuck at S-OFF phase.
How do I fix it?
Cant afford sunshine and firewater wont work. .
Unticked everything in security except unknown source. Nothing. Fails in first try. What else?
I dont think theres a lot you can do, I put mine to the GPE edition last night and had to pay for Sunshine to do it as Firewater isnt working on 4.4.4
KiD3991 said:
Just got M8 today and rooted but stuck at S-OFF phase.
How do I fix it?
Cant afford sunshine and firewater wont work. .
Unticked everything in security except unknown source. Nothing. Fails in first try. What else?
Click to expand...
Click to collapse
if you can't afford sunshine then you will not be able to S off, so now its time to enjoy your new phone and custom roms, most don't need s off anyway.
Stock ROM, kernel, and recovery, then run firewater a few times. If you still get the "whelp" message, firewater simply doesn't work, and there isn't anything you can do to make it work.
Do you just want to update firmware to run the latest ROMs? If so, and you are in a region where Android 4.4.4 has already rolled out, just return to stock ROM and stock recovery and accept the OTA to update the firmware. After that, you can install custom recovery again, and install any of the M8 custom ROMs.
Otherwise, if you want s-off for another reason (SIM unlock, flash radio, flash hboot, etc.) than you will have to pay for sunshine if firewater doesn't work.
Really, you haven't given enough info. What hboot version you are on, what region, what errors you are getting with firewater ("whelp" or otherwise), and why you want s-off. For all we know you just don't have the USB drivers installed properly, or made some other silly mistake. But we'll never know without the proper info.
Is the not a way to down grade to by pass the HTC patch?
I have tried but the links to stock recovery are broken in another thread.
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.21.21331147A1.19_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:#####################
imei: ##########
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: BS_US001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: df77f8b7
hbootpreupdate: 11
Hello, I've been a long time xda lurker (Never thought I could really add much anyhow) since I had my Dell Streak and I think for the first time since I got my M8 I need a bit of help.
They rolled out the lollypop OTA update here in Ireland and figured It was time to update to a stock ROM from here or a slightly improved one but ever since then I have lost my WiFi completely.
Sorry If this makes no seance- at all I'm a little burnt out trying to solve this on my own but even going back to 4.4.3 ROMs I still have no WiFi at all and any help at all would be greatly appreciated.
This is all the info I took from fastboot and the bootloader I thought would be needed
Bootloader Info
*** Tampered ***
*** Unlocked ***
M8_UL PVT SHIP S-ON
HBOOT - 3.18.0.0000
RADIO - 1.19.21331147A1.09G
OpenDSP - v38.2.2-00542-M8974.0311
OS - 2.22.401.4
Fastboot Getvar All Info
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 2.22.401.4
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0
Thanks again for even looking!
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
ckpv5 said:
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
Click to expand...
Click to collapse
Thank you I didn't even think of that I edited them out.
EddyOS said:
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
Click to expand...
Click to collapse
I will try that right away thank you for your help I'll post back here when I'm done
No luck, kept getting error 99 with the 'htc_fastboot" from the thread and with my normal fastboot it gives me the error 32 'header error' I only noticed the thread was for s-off phones, I don't care about my phone saying tampered, unlocked or anything but I'm assuming that's stopping the flash from happening.
You must relock your device first ... then try again with flash the ruu.zip
Isotopes said:
You must relock your device first ... then try again with flash the ruu.zip
Click to expand...
Click to collapse
Haha yeah that worked now, ignoring the guide at the start and just leaving it with the relocked warning it's flashing now via the RUU
Thanks to the both of you for your help.
Here the actual problem was phone didnt detected sim .show"no sim"
***Software status modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21.331147A1.29G
OpenDSP-V46.2.2-00564-M8974_FO.0811
OS-("didnt show anything after flash custom rom")
eMMC-boot 2048MB
Nov 13 2014,21:01:33.0
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpid: None
version-main: ...........
version-misc: PVT SHIP S-ON
serialno:**********************
imei:**********************
imei2: Not Supported
product: m8_ul
platform: hTCBmsm8974
modeid: 0P6B10000
cidnum: HG3__001
battery-status: good
battery-voltage: 0mV
partition-layer: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c52f93f
hbootpreupdate: 11
gencheckpt: 0
please help
Hello.
Did your SIM just stop working, or did you flash something first?
It could be that you need a replacement SIM, or that it has a bad connection in the tray. Is there another phone available to you that you could insert your SIM into to see if it works? Also, is there another SIM that you could use to see if the problem is a bad connection in the tray? Maybe a friend can let you test with his/her phone and SIM.
If it happened after you flashed something, like a ROM, then try another ROM to see if the problem persist.
Also, your OS in bootloader and version-main in your getvar are blank because of a bug in some older versions of TWRP. Update to the newest version (2.8.7.0). It will remain blank until the next time you update firmware I believe, but that's what caused it.
EDIT:According to your DSP, it appears you are on Kit-Kat firmware still. You should update to Lollipop if you want to flash newer ROMs. I'm not sure about this, but it may possibly be causing the SIM read error.
Since you are S-On, you will need to return to stock to do update.
This thread has instructions and download links for you to return to stock. Then you can update via the OTA that will be offered in settings>about>software updates
Yes sim is working after change the rom make this issue ......
I try to update 3.32.771.0 stock rom and try to ota updation after ota updation it hang in htc boot screen somtimes it ends with red triangle .then i use 4.20.771.2 in this stock rom no problem for ota updation but i bave still that issue sim detection .........can soff and use different rom solve this issue
I don't understand. You have updated via OTA? Did you update TWRP? Your version main shouldn't be blank anymore.
Is this something you have tried before starting this thread, or what you have done since I gave you that link?
Also, what ROM are you using that is giving you this error?
If you got S-Off, you could change your CID and update your firmware manually.
And yes, you should try another ROM to see if the issue persist. You could also try an older version of the ROM if your firmware isn't up to date.
xunholyx said:
I don't understand. You have updated via OTA? Did you update TWRP? Your version main shouldn't be blank anymore.
Is this something you have tried before starting this thread, or what you have done since I gave you that link?
Also, what ROM are you using that is giving you this error?
If you got S-Off, you could change your CID and update your firmware manually.
And yes, you should try another ROM to see if the issue persist. You could also try an older version of the ROM if your firmware isn't up to date.
Click to expand...
Click to collapse
By the help of xda links i ................do this
Yes update twrp 2.8.7 and use stock Nandroid backup 3.32.771.10 have problem for ota updation(stuck in htc boot screen sometimes ends with red triangle) and use 4.20.771.2 stock backup have no problem for ota updation for my phone and use stock recovery for the ota updation ....is s-on mobile can't able to downgrade firmware ????
Is my main version based on kitkat but i use custom rom based on lolipop ........can this cause for sim detection problem??????
Current stage of my problem
After use stock backup and update ota
***Software status modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21.331147A1.29G
OpenDSP-V46.2.2-00564-M8974_FO.0811
Os 4.25.771.6
eMMC-boot 2048MB
Nov 13 2014,21:01:33.0
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpid: None
version-main: .4.25.771.6
version-misc: PVT SHIP S-ON
serialno:**********************
imei:**********************
imei2: Not Supported
product: m8_ul
platform: hTCBmsm8974
modeid: 0P6B10000
cidnum: HG3__001
battery-status: good
battery-voltage: 0mV
partition-layer: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c52f93f
hbootpreupdate: 11
gencheckpt: 0
moononem8 said:
By the help of xda links i ................do this
Yes update twrp 2.8.7 and use stock Nandroid backup 3.32.771.10 have problem for ota updation(stuck in htc boot screen sometimes ends with red triangle) and use 4.20.771.2 stock backup have no problem for ota updation for my phone and use stock recovery for the ota updation ....is s-on mobile can't able to downgrade firmware ????
Is my main version based on kitkat but i use custom rom based on lolipop ........can this cause for sim detection problem??????
Current stage of my problem
After use stock backup and update ota
***Software status modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21.331147A1.29G
OpenDSP-V46.2.2-00564-M8974_FO.0811
Os 4.25.771.6
eMMC-boot 2048MB
Nov 13 2014,21:01:33.0
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpid: None
version-main: .4.25.771.6
version-misc: PVT SHIP S-ON
serialno:**********************
imei:**********************
imei2: Not Supported
product: m8_ul
platform: hTCBmsm8974
modeid: 0P6B10000
cidnum: HG3__001
battery-status: good
battery-voltage: 0mV
partition-layer: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c52f93f
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Sorry I haven't responded sooner. I've been very busy.
Have you tried with other ROMs? If the problem persists with other ROMs, it is because the SIM card isn't seated properly in the sim tray, or the SIM itself is fried. You could try to pop it out and reinsert it, clean the metal contact points with alcohol, and lastly try putting a thin layer of tape on the back to make it fit more snuggly.
I'm going to have this thread moved to the M8 Q&A forum, where there may be answers from people who have experienced this before. Try what I have suggested above, and hopefully you'll find a solution soon.
Good luck!
xunholyx said:
Sorry I haven't responded sooner. I've been very busy.
Have you tried with other ROMs? If the problem persists with other ROMs, it is because the SIM card isn't seated properly in the sim tray, or the SIM itself is fried. You could try to pop it out and reinsert it, clean the metal contact points with alcohol, and lastly try putting a thin layer of tape on the back to make it fit more snuggly.
I'm going to have this thread moved to the M8 Q&A forum, where there may be answers from people who have experienced this before. Try what I have suggested above, and hopefully you'll find a solution soon.
Good luck!
Click to expand...
Click to collapse
i face this problem after change stock rom to custom rom
now i want to s off and want to know which cid and mid number use after
soff to flash any ruu on my phone
moononem8 said:
i face this problem after change stock rom to custom rom
now i want to s off and want to know which cid and mid number use after
soff to flash any ruu on my phone
Click to expand...
Click to collapse
Your MID is fine. Change your CID to superCID (11111111).
You won't be able to flash all RUUs. Verizon and Sprint firmware won't work with GSM phones.
I would avoid AT&T and T-Mo RUUs as well (unless you are switching to their network).
xunholyx said:
Your MID is fine. Change your CID to superCID (11111111).
You won't be able to flash all RUUs. Verizon and Sprint firmware won't work with GSM phones.
I would avoid AT&T and T-Mo RUUs as well (unless you are switching to their network).
Click to expand...
Click to collapse
in this current model id i can flash indian RUU in this phone
RUU_M8_UL_L50_SENSE60_MR_hTC_Asia_WWE_4.19.707.2_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414204_signed.exe
can i flash above RUU
moononem8 said:
in this current model id i can flash indian RUU in this phone
RUU_M8_UL_L50_SENSE60_MR_hTC_Asia_WWE_4.19.707.2_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414204_signed.exe
can i flash above RUU
Click to expand...
Click to collapse
You should be able to, yes.
If it doesn't work you will get an error message/code, and the flash will abort. You won't brick your phone. If it comes up MID mismatch, then you will have to change it, but I don't think you will have to.
For the record, I am on the Telus network in Canada (MID 0P6B16000), and I am using WWE/International firmware for a year and a half (MID 0P6B10000). I just ran an RUU three weeks ago to clear up some system issues I was having, and it installed with no problem.
If you didnt change phones Model ID, You find everything here ROMS, RUUs, Stock Nandroid Backups with respect to your Model ID.
You can S-Off and SuperCID to make things a lot easier.
http://forum.xda-developers.com/showthread.php?t=2701376
After flashing Android Revolution HD ROM, I tried to reboot but I got sent back to the fastboot screen.
Factory reset brings me back to fastboot, reboot brings me back to fastboot, anything in TWRP brings me back to fastboot; basically everything gets me back to fastboot. There seems to be no way to get this thing back to normal. It all started with a volume boost mod from droidviews (new user, can't post links or pics yet). Everything else worked perfectly until the Revolution rom. At this point I don't even care about the volume boost, just want the phone to work again. Any help will be greatly appreciated.
Post fastboot getvar all result without serial & imei no.
Most probably you installed wrong TWRP version and your firmware is outdated for latest ROM
ckpv5 said:
Post fastboot getvar all result without serial & imei no.
Most probably you installed wrong TWRP version and your firmware is outdated for latest ROM
Click to expand...
Click to collapse
Here are the getvar results:
version: 0.5
version-bootloader: 3.19.0.000
version-baseband: 1.09.20.1112
version-cpld: None
version-microp: None
version-main: 6.20.651.3
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 99000499581265
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: SPCS_001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 205bdca3
hbootpreupdate: 11
gencheckpt: 0
TWRP is v2.7.0.0
If it helps, here's what I'm seeing on the phone:
*** Software status: Modified ***
*** UNLOCKED ***
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.09.20.1112
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.20.651.3
eMMC-boot 2048MB
Jan 27 2016, 20:58:27.0
FASTBOOT USB
You have a Sprint device and ARHD does not support Sprint variant and that's the reason why the problem you're having now.
Refer : http://forum.xda-developers.com/showpost.php?p=65234604&postcount=29724
Find a ROM that says it supports Sprint variant on its title (or you can see WHL on its title) and try that.
Or .. go to Sprint Development section and install ROMs from that section.
Well, it's looking pretty hopeless now. I have no way of installing a new ROM on the phone: the computer can't always find the phone, and when it does it recognizes it as DVD/CD drive. I tried putting SkyDragon on a micro SD but TWRP can't find anything on the microSD card. I even tried wiping the system and internal storage thinking that would get rid of the HD Revolution ROM and thus solve the problem but I keep coming back to the bootloader after reboot. I guess it's a lost cause.
Disregard last post, all is well now! In my utter despair I overlooked one simple step; I didn't mount the sd card in TWRP. After I did that, I flashed SkyDragon and the phone is working great! Thanks so much for the help!
toad871 said:
I even tried wiping the system and internal storage thinking that would get rid of the HD Revolution ROM and thus solve the problem but I keep coming back to the bootloader after reboot.
Click to expand...
Click to collapse
Just to be clear (future knowledge) if the problem is that the phone can't boot into OS (that is why its going to bootloader) then wiping system (which is the OS partition) is not going to help.
Instead of a ROM (OS) that won't boot, you replaced that with . . . nothing (no OS at all). Which obviously won't boot to OS either.
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).