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.
Related
Hey there,
i have a strage problem, after rooting a lot of android devices the m8 behaves kind of strange.
I got a brand new M8 (Hbot 3.15xxxx and 4.4.2) for my girl friend and unlocked the device with htc dev. after this i flashed twrp 2.7.0.2, no big deal.
Now i made a backup (thank god....) and downloaded viper rom and arhd roms.
But if i install a rom (does not matter which one, with wipe and so on) the script tells me installtion is finished, but if i hit the next button the m8 vibrates and turns off, at least the screen goes dark.
the only way to wake up the m8 is to push power and volume up button, but the only thing i see is the htc logo with the red text at the buttom.
adb reboot boatloader does not work, but reboot recocery does. Wipen cache and so does not fix the problem, the stock backup can be restored.
do you have any idea what's going on, i really want to run viper or arhd on the m8.
thanks!
Havoc2k said:
Hey there,
i have a strage problem, after rooting a lot of android devices the m8 behaves kind of strange.
I got a brand new M8 (Hbot 3.15xxxx and 4.4.2) for my girl friend and unlocked the device with htc dev. after this i flashed twrp 2.7.0.2, no big deal.
Now i made a backup (thank god....) and downloaded viper rom and arhd roms.
But if i install a rom (does not matter which one, with wipe and so on) the script tells me installtion is finished, but if i hit the next button the m8 vibrates and turns off, at least the screen goes dark.
the only way to wake up the m8 is to push power and volume up button, but the only thing i see is the htc logo with the red text at the buttom.
adb reboot boatloader does not work, but reboot recocery does. Wipen cache and so does not fix the problem, the stock backup can be restored.
do you have any idea what's going on, i really want to run viper or arhd on the m8.
thanks!
Click to expand...
Click to collapse
Just a bug in TWRP, nothing to worry about. Disable from TWRP the screen timeout and you are good to go.
stathis95194 said:
Just a bug in TWRP, nothing to worry about. Disable from TWRP the screen timeout and you are good to go.
Click to expand...
Click to collapse
i don't think thats the problem. if the screen would timeout (like while doing backup or restore) i could wake it up.
but the device is not booting anymore then. Even if i do a adb reboot recovery and make a clean reboot. Just the htc logo with the warning.
could it be the firmware ? i dont see any information for hboot 3.15.....
thanks
Havoc2k said:
i don't think thats the problem. if the screen would timeout (like while doing backup or restore) i could wake it up.
but the device is not booting anymore then. Even if i do a adb reboot recovery and make a clean reboot. Just the htc logo with the warning.
could it be the firmware ? i dont see any information for hboot 3.15.....
thanks
Click to expand...
Click to collapse
Are you flashing a 4.4.3 ROM? which firmware are you on? Can you please do a :
fastboot getvar all
and post the outcome? Don't forget to hide your sensitive info (imei, etc)
stathis95194 said:
Are you flashing a 4.4.3 ROM? which firmware are you on? Can you please do a :
fastboot getvar all
and post the outcome? Don't forget to hide your sensitive info (imei, etc)
Click to expand...
Click to collapse
yes i will flash viper 2.0.0 or arhd 10.2 both are 4.4.3 roms.
device is running at 4.4.2 at the moment (rooted stock vodafone germany)
getvar all:
Code:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA03_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43FWM10422
imei: xxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: T-MOB101
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
m8_ul...... what device is it? internation one? should be, there are no at&t or sprint devices in germany, are they?
edit: i think i found the problem:
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
Click to expand...
Click to collapse
so the firmware should be the problem, i am right?
Havoc2k said:
yes i will flash viper 2.0.0 or arhd 10.2 both are 4.4.3 roms.
device is running at 4.4.2 at the moment (rooted stock vodafone germany)
getvar all:
Code:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA03_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43FWM10422
imei: xxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: T-MOB101
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
m8_ul...... what device is it? internation one? should be, there are no at&t or sprint devices in germany, are they?
Click to expand...
Click to collapse
Well nothing strange here. You are on older firmware trying to flash a 4.4.3 ROM. First boot might take up to 15 minutes...But after that you will experience slow boots and/or wifi or bt issues.
You can either try to s-off and upgrade firmware or try a 4.4.2 rom like ARHD 8.1
First of all try the following. Flash the ROM and reboot and let it sit there for around 15 minutes to see if it boots. And we can see your choices from there.
If i want to update with OTA,
which stock recovery i need to flash ? my version.main is empty :/ so i am not sure how to flash the right recovery. there a lots of them: http://forum.xda-developers.com/showthread.php?t=2701376
Havoc2k said:
If i want to update with OTA,
which stock recovery i need to flash ? my version.main is empty :/ so i am not sure how to flash the right recovery. there a lots of them: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Try here:
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832637
it's either 1.12.111.18 or 1.57.111.2
it is 1.12.111.18
at the moment the OTA to 1.57.111.2 is running
some german forums wrote that any 1.12.xxx recovery will work for the ota. let's see if there is another ota after this one.
edit: 1.57 went well, now ota to 1.70
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.
Hello!
A few days ago I decided to root my M8 and change ROM to Google Play Edition. Something went wrong during installation and now my phone doesn't recognize a SIM card, camera doesn't work and display is glitching. So I wanted to use a backup file I created earlier, but it was corrupted...
I've already installed 4 different ROMs: InsertCoin, Stock GPE 5.1, Cyanogen CM12.1 and now I've returned to Stock M8.
The problem occurred on every ROM.
I'm attaching a few links to show how it looks like (sorry for incomplete urls):
No SIM Card: i60.tinypic[dot]com/2dab0up[dot]jpg
Camera App: i59.tinypic[dot]com/2ir5iky[dot]png
Flashing and colorful dots on the screen: www[dot]youtube[dot]com/watch?v=4u7hRfvUjTw
However the display works fine when I turn on Airplane mode.
HBOOT SCREEN:
Code:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
openDSP-v48.2.2-00564-M8974_F0.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015, 22:51:08.0
fastboot getvar all:
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.16.401.10
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m8_ul
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
Any help would be appreciated.
PS. I have already tried to flash RADIO separately.
There is an RUU around for 4.16.401, use that to return to stock image.
Than maybe try again to install custom recovery and flash custom ROM. I don't see any reason for those ROMs to give you the described issue (your firmware is up to date, etc.). So maybe you just need to start over from a blank slate.
redpoint73 said:
There is an RUU around for 4.16.401, use that to return to stock image.
Than maybe try again to install custom recovery and flash custom ROM. I don't see any reason for those ROMs to give you the described issue (your firmware is up to date, etc.). So maybe you just need to start over from a blank slate.
Click to expand...
Click to collapse
I tried to use the RUU you mentioned and it didn't help. I've already installed 8 different ROMs and my device still doesn't see SIM cards (I've tested those cards, so I'm sure they work fine) and the camera doesn't work. However the display stopped flashing and glitching. Any ideas?
walerian said:
I tried to use the RUU you mentioned and it didn't help.
Click to expand...
Click to collapse
Meaning what? Did the RUU fail or run to full completion?
If you have RUUed to full stock, and the issues still persist, it leads me to believe there is a hardware issue.
redpoint73 said:
Meaning what? Did the RUU fail or run to full completion?
Click to expand...
Click to collapse
It has been installed successfully and every functionality works fine except SIM card. It still displays a message "No SIM card in phone".
And I'm unable to enter Camera app.
hi all, my phone is stuck on boot mode for a couple of weeks and I am still not able to find correct stock rom. please help me find one so that I can flash it via fastboot. here are the getvar all details from fastboot:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.31.50.1103
version-cpld: None
version-microp: None
version-main: 1.61.720.1
version-misc: PVT SHIP S-ON
serialno: FA484MZ00452
product: a5_dwg
platform: hTCBmsm8226
modelid: 0P9C51000
cidnum: HTC__038
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: be7179e5
hbootpreupdate: 11
gencheckpt: 0
HTC desire 816 A5_dwg
Kit Kat RUU:
http://www.mediafire.com/?jimitej7orp4qcr
Lollipop RUU:
http://www.4shared.com/zip/9nQZohiEba/0P9CIMG_A5_DWG_L50_DESIRE_SENS.html
***RELOCKED***
A5_DWG PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.31.50.1103
OpenDSP-v28.2.2.00546.0331
OS-1.61.720.1
eMMC-boot 1536MB
Nov 4 2014,20:04:44.23583
I already tried the kitkat one u r posting. it said something remote:12 signature failed
Download lollipop RUU, should work with your device.
Have you tried flashing with sd-card?
When did this bootloop first appear?
nukaru said:
Download lollipop RUU, should work with your device.
Have you tried flashing with sd-card?
When did this bootloop first appear?
Click to expand...
Click to collapse
sorry for late response, I tried the lollipop RUU too
1. with fastboot, it says :02 remote fie is too large
2. via sd card...finding package..opening package....unable to map file
And here is the story of bootloop. my phone was working fine till I received the official lollipop update, which failed repeatedly during installation. I checked the recovery log and found some error in system/bin/flash_camera and decided to flash just recovery image. I flashed recovery and boot image from the ota update I received...but got stuck. then I started trying all these RUU stuff but still no clue. thanks for listening
Ah, okay.
Can you select recovery in hboot and does it start up normally? Have you tried a Kit Kat nandroid backup with twrp?
Ps: you need to delete your imeis in the first post..
nukaru said:
Ah, okay.
Can you select recovery in hboot and does it start up normally? Have you tried a Kit Kat nandroid backup with twrp?
Ps: you need to delete your imeis in the first post..
Click to expand...
Click to collapse
yes once stuck on white screen with htc, I need to hold vol up+ power to turn it off and before it reboots automatically I open hboot by vol down+ power. from there I can continue in recovery mode and fastboot etc. no I haven't tried nandroid backup with twrp. I want to get stock rom so that I am able to get updates in future. plus I read twrp backup roms are havng problems like wifi and all.
That sounds like your bootsector is damaged, so usb debugging is disabled.
Did you back up your old recovery.img? The kit kat one before the update?
The easiest way, if you're able to flash a custom recovery, is a clean nandroid backup without root using twrp and once your device is booting again, start from scratch.
Enable usb debugging, unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
nukaru said:
That sounds like your bootsector is damaged, so usb debugging is disabled.
Did you back up your old recovery.img? The kit kat one before the update?
The easiest way, if you're able to flash a custom recovery, is a clean nandroid backup without root using twrp and once your device is booting again, start from scratch.
Enable usb debugging, unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
Click to expand...
Click to collapse
no I havent backed up the KitKat factory image
I flashed the latest twrp recovery and booted to it. also I placed a twrp stock backup in sd card ( from one of the threads on this forum) . but when I proceed to backup from sd card, it doesn't appear there, however in the install option I can see the contents I placed..but again I m not getting an option to install it from there. guide me what to do next.
shubhamjswl said:
no I havent backed up the KitKat factory image
I flashed the latest twrp recovery and booted to it. also I placed a twrp stock backup in sd card ( from one of the threads on this forum) . but when I proceed to backup from sd card, it doesn't appear there, however in the install option I can see the contents I placed..but again I m not getting an option to install it from there. guide me what to do next.
Click to expand...
Click to collapse
guess wat!! my phone started and I am now getting ota also. thanks
That's great ? Remember to make your own backup and store it somewhere safe ?
Please provide me detailed steps on how to reinstall official stock rom on htc desire 816 dual sim indian version and also rom file
hi all, my phone is stuck on boot mode for weeks and i can't find a usable stock rom for my phone here are the details from fastboot
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.31.50.1215
version-cpld: None
version-microp: None
version-main:1.27.710.1
version-misc: PVT SHIP S-ON
serialno: FA47RMZ00345
imei: 352795062179097
imei2: 352795062179105
meid: A1000037D93FA6
product: a5_dwg
platform: hTCBmsm8226
modelid: 0P9C51000
cidnum: HTC__621
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: fba3c246
hbootpreupdate: 11
gencheckpt: 0
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).