Hey Community,
My colleague gave me his cell phone (HTC One M8), because I have previously worked with cfws and was flashing phones (but this was at time of Gingerbread on LGP920).
That's why I'm not a novice but I'm not familiar with today's technology.
He updated his HTC (it isn't rooted) and get stuck at bootscreen. Now he can't do anything. Recovery & Hard-Reset nothing works for him. I just get into the fastboot mode.
Can you tell me what can I do next?
What's the details on fastboot/bootloader ?
Okey it's unlocked....
Software status: Official
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.22.21331147A1.29G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.401.9
eMMC-boot 2048 M
So it's still 4.4.4 firmware and not upgraded to lollipop yet.
Since it is unlocked, install TWRP 2.8.4.0
Then download the TWRP nandroid backup for 3.28.401.9 and stock recovery from here :
http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
Restore that nandroid, then fastboot flash the stock recovery
then reboot and do OTA checking and let the system install the OTA.
ckpv5 said:
So it's still 4.4.4 firmware and not upgraded to lollipop yet.
Since it is unlocked, install TWRP 2.8.4.0
Then download the TWRP nandroid backup for 3.28.401.9 and stock recovery from here :
http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
Restore that nandroid, then fastboot flash the stock recovery
then reboot and do OTA checking and let the system install the OTA.
Click to expand...
Click to collapse
But the Problem is... How I get TWRP on my device. I cant't start it at the moment.
You don't need to be on its desktop, only on bootloader (as you wrote the bootloader details)
Then flash the TWRP recovery in fastboot mode (connect to PC when on bootloader where you see the word fastboot usb in red on bootloader)
Run command fastboot flash recovery recovery.img (of course you need to have fastboot/adb already installed on PC)
ckpv5 said:
You don't need to be on its desktop, only on bootloader (as you wrote the bootloader details)
Then flash the TWRP recovery in fastboot mode (connect to PC when on bootloader where you see the word fastboot usb in red on bootloader)
Run command fastboot flash recovery recovery.img (of course you need to have fastboot/adb already installed on PC)
Click to expand...
Click to collapse
Thank You! I will try it later at home... Is it possible that the S-On creating problems with your methode?
Hi,
I am unfortunately in a very similar situation on an update I started that I must've made some mistakes on.
I'm trying to go from 4.4.3 (with Viper ROM 2.5.0), to 4.4.4 (with Viper ROM 3.2.1).
Have done a couple ROMs on 4.4.2 (even to a GPE edition and back to Sense 4.4.2 with Viper 1.8), then finally onto the 4.4.3 with Viper 2.5.0.... so I'm somewhat OK with understanding & following instructions (til now).
Tried a few things in fastboot, but always seem to get hung trying to load from a reboot....can only boot into fastboot (hangs trying to boot the 4.4.3 OS it seems, I've waited up to 45 minutes at the Green HTC Logo and 'powered by Android' screen.
Just tried the fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.img and I'm again waiting ~30 minutes now....
The info from my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: --------------
(bootloader) imei: --------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help on where to go from here?
EDIT: Oh....I was eventually trying to go to 5.0 Lollipop, but another post in the Viper ROM thread said to go from 4.4.3, to 4.4.4, and then to 5.0. So I didn't start a new thread....
swedax94 said:
Thank You! I will try it later at home... Is it possible that the S-On creating problems with your methode?
Click to expand...
Click to collapse
It doesn't matter S-On or S-Off ... as long as the bootloader is UNLOCKED
---------- Post added at 01:56 AM ---------- Previous post was at 01:48 AM ----------
sttw1fa said:
Any help on where to go from here?
EDIT: Oh....I was eventually trying to go to 5.0 Lollipop, but another post in the Viper ROM thread said to go from 4.4.3, to 4.4.4, and then to 5.0. So I didn't start a new thread....
Click to expand...
Click to collapse
I'm not familiar with Viper ROM as I never use one so not sure their ROM's requirement.
But, your fastboot getvar all suggests that you flashed EU WWE 4.4.4 firmware without change of MID.
So what actually you want to do ? If it just to update to lollipop firmware then use maybe 5.0.1 based Viper, you only need to flash a modified lollipop firmware which include your MID 0P6B12000. Or easier, change your MID to EU 0P6B10000 then you can flashed the latest EU firmware 4.16.401.10
Or you want to get back to your original device region stock ROM and do update to lollipop if there is one available ?
Now when I'm starting the recovery there is a message ...this build is for devlopment purpose only....
swedax94 said:
Now when I'm starting the recovery there is a message ...this build is for devlopment purpose only....
Click to expand...
Click to collapse
That's normal because you have a custom recovery.
Can you get into recovery ? In there you can mount MTP then you can transfer the downloaded Nandroid backup (which you already extracted on PC) to your TWRP backup folder.
Make a backup of say boot only .. then you can see where the TWRP backup path so you can copy the extracted nandroid to the right location which look something like this
TWRP/BACKUPS/DeviceSerialNo/BackupFolder
sttw1fa said:
Hi,
I am unfortunately in a very similar situation on an update I started that I must've made some mistakes on.
I'm trying to go from 4.4.3 (with Viper ROM 2.5.0), to 4.4.4 (with Viper ROM 3.2.1).
Click to expand...
Click to collapse
This is not even remotely similar to the OP's issue. He is trying to boot after a failed OTA; not a custom ROM.
sttw1fa said:
Hi,
EDIT: Oh....I was eventually trying to go to 5.0 Lollipop, but another post in the Viper ROM thread said to go from 4.4.3, to 4.4.4, and then to 5.0. So I didn't start a new thread....
Click to expand...
Click to collapse
Not sure, but the incremental updating probably refers to the firmware (or possibly OTA to update the firmware), not the ROM.
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
swedax94 said:
Okey it's unlocked....
Click to expand...
Click to collapse
What happens when you choose recovery from bootloader?
ckpv5 said:
That's normal because you have a custom recovery.
Can you get into recovery ?
Click to expand...
Click to collapse
redpoint73 said:
What happens when you choose recovery from bootloader?
Click to expand...
Click to collapse
No, it seems to stuck at entering recovery and after 2 minutes it goes to normal bootscreen.
swedax94 said:
No, it seems to stuck at entering recovery and after 2 minutes it goes to normal bootscreen.
Click to expand...
Click to collapse
Try run command
fastboot erase cache
fastboot reboot-bootloader
then try again to enter recovery
I need to sign-off now ... it's almost 2.30 am here.
I'll check tomorrow on your progress.
Maybe someone else will be able to help you in my absent.. good luck
ckpv5 said:
Try run command
fastboot erase cache
fastboot reboot-bootloader
then try again to enter recovery
Click to expand...
Click to collapse
This.
And if that doesn't work, flash recovery again.
and last thing from me for tonight ... if you don't mind losing everything on internal storage, you can use RUU zip.
See : http://forum.xda-developers.com/showpost.php?p=58504115&postcount=8
But you need to relock bootloader to use the RUU zip because your device is S-On
command to relock : fastboot oem lock
you can use either 3.28.401.9 or 4.16.401.10
redpoint73 said:
This is not even remotely similar to the OP's issue. He is trying to boot after a failed OTA; not a custom ROM.
Click to expand...
Click to collapse
Sorry for the mix up. Didn't mean to derail. At the time when I typed, the only accessible option of booting was into Fastboot (recovery option failed to boot, etc.), so I thought it was similar with all the searching I was doing.
Found a solution for me via the TWRP website. All good for me atm on 4.4.4 FW with Viper ROM 3.2.1. Headed to 5.0 FW with Viper later this evening.
redpoint73 said:
This is not even remotely similar to the OP's issue. He is trying to boot after a failed OTA; not a custom ROM.
Not sure, but the incremental updating probably refers to the firmware (or possibly OTA to update the firmware), not the ROM.
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
What happens when you choose recovery from bootloader?
Click to expand...
Click to collapse
sttw1fa said:
Sorry for the mix up. Didn't mean to derail. At the time when I typed, the only accessible option of booting was into Fastboot (recovery option failed to boot, etc.), so I thought it was similar with all the searching I was doing.
Found a solution for me via the TWRP website. All good for me atm on 4.4.4 FW with Viper ROM 3.2.1. Headed to 5.0 FW with Viper later this evening.
Click to expand...
Click to collapse
Thank you! Problem solved. For People with same Problems i had done these steps:
1. Unlock your Bootloader
2. Load adb/fastboot (if you're to lazy to install this all, like me, use the version from the video https://www.youtube.com/watch?v=5xVl2dBTnmI)
3. Then load the latest Version of TRWP and flash it with fastboot
4. Download the right nandroid backup here http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
5. Start Recovery on your Device and Make backup of boot (to see were the right place is to put in the nandroid)
6. Start Backup from the nandroid
7. Finish
THANKS FOR ckpv5!!!!! YOU HELPED ME SO MUCH!!!
ps. I reflashed TRWP then it worked sry for my bad english
Red triangle after attempt to restore to stock
HI THIS IS MY FIRST POSTING ON THIS SITE, HAVE AN HTC ONE M8 FROM EE UK , I ROOTED IT AND INSTALLED TWRP RECOVERY. WHEN LOLLIPOP CAME OUT I DECIDE TO RESTORE TO STOCK AND INSTALL UPDATE. I THINK I MUST HAVE INSTALLED THE WRONG FIRMWARE . SOMEHOW I STILL HAVE ROOT ACCESS EVEN THOUGH I'M SUPPOSED TO BE IN STOCK( ), BUT I CAN'T BOOT TO RECOVERY THE RED TRIANGLE SHOWS UP. I'M SURE I'VE MESSED UP THE PROCESS SOMEWHERE.
PLEASE I WOULD LIKE TO RESTORE MY PHONE TO STOCK AND INSTALL THE LOLLIPOP UPDATE, CAN YOU HELP?. IM ALSO HAVING CALL SIGNAL ISSUES, COMPLAINTS OF MY PHONE NOT BEING AVAILABLE EVEN THOUGH ITS ON.
No OS Number
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.22.21331147A1.29G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-
eMMC-boot 2048 M
C:\fastboot_adb>fastboot getvar all (bootloader) version: 0.5 (bootloader) version-bootloader: 3.19.0.0000 (bootloader) version-baseband: 1.22.21331147A1.29G (bootloader) version-cpld: None (bootloader) version-microp: None (bootloader) version-main: (bootloader) version-misc: PVT SHIP S-ON (bootloader) serial no: (bootloader) imei: (bootloader) imei2: Not Support (bootloader) meid: 00000000000000 (bootloader) product: m8_ul (bootloader) platform: hTCBmsm8974 (bootloader) modelid: 0P6B10000 (bootloader) cidnum: ORANG001 (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: 4c3fbd70 (bootloader) hbootpreupdate: 11 (bootloader) gencheckpt: 0 all: Done! finished. total time: 0.039s
Axdel said:
HI THIS IS MY FIRST POSTING ON THIS SITE, HAVE AN HTC ONE M8 FROM EE UK , I ROOTED IT AND INSTALLED TWRP RECOVERY. WHEN LOLLIPOP CAME OUT I DECIDE TO RESTORE TO STOCK AND INSTALL UPDATE. I THINK I MUST HAVE INSTALLED THE WRONG FIRMWARE . SOMEHOW I STILL HAVE ROOT ACCESS EVEN THOUGH I'M SUPPOSED TO BE IN STOCK( ), BUT I CAN'T BOOT TO RECOVERY THE RED TRIANGLE SHOWS UP. I'M SURE I'VE MESSED UP THE PROCESS SOMEWHERE.
PLEASE I WOULD LIKE TO RESTORE MY PHONE TO STOCK AND INSTALL THE LOLLIPOP UPDATE, CAN YOU HELP?. IM ALSO HAVING CALL SIGNAL ISSUES, COMPLAINTS OF MY PHONE NOT BEING AVAILABLE EVEN THOUGH ITS ON.
No OS Number
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.22.21331147A1.29G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-
eMMC-boot 2048 M
C:\fastboot_adb>fastboot getvar all (bootloader) version: 0.5 (bootloader) version-bootloader: 3.19.0.0000 (bootloader) version-baseband: 1.22.21331147A1.29G (bootloader) version-cpld: None (bootloader) version-microp: None (bootloader) version-main: (bootloader) version-misc: PVT SHIP S-ON (bootloader) serial no: (bootloader) imei: (bootloader) imei2: Not Support (bootloader) meid: 00000000000000 (bootloader) product: m8_ul (bootloader) platform: hTCBmsm8974 (bootloader) modelid: 0P6B10000 (bootloader) cidnum: ORANG001 (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: 4c3fbd70 (bootloader) hbootpreupdate: 11 (bootloader) gencheckpt: 0 all: Done! finished. total time: 0.039s
Click to expand...
Click to collapse
That red triangle means you have the stock recovery.
Related
I need to return my International HTC One M8 back to stock, I currently run with TWRP and Revolution 11.1 ROM.
My M8 is NOT S-OFF
I have found a guide that tells me how to achieve this, one of the first things it asks is to make note of the CID and version-main.
I have the CID of HTC__001, but my version-main is empty.
This is a problem as the HTC__001 nandroid backups (and recovery images) have two versions available as you can see below (1.54.xxx.xx and 2.22.xxx.xx)
CID HTC__001
1.54.401.10 - CWM Philz touch Thanks to spikeydoo2006
1.54.401.5 - TWRP Thanks to Fisha21
1.54.401.5 - CWM Philz touch Thanks to krihoum
1.54.401.5 - TWRP Thanks to jontyjon
1.54.401.10 - TWRP Thanks to ckpv5
2.22.401.4 - TWRP Thanks to ckpv5
2.22.401.5 - TWRP Thanks to ckpv5
2.22.401.5 - CWM Philz touch Thanks to MATRIKS
I have no idea what to do at this point, Google searching hasnt given me a definitive answer, can anyone here help and point me in the right direction please?
If its of any use..
HBOOT 3.18.0.000
RADIO 1.19.2331147A1.09G
Hboot 3.18 is at least 2.22 so i suggest you take the 2.22.401.4 and the 2.22.401 stock recovery. Restore the nand and then flash back the stock recovery. Then perform the available OTA and you are back on the latest stock rom
Mr Hofs said:
Hboot 3.18 is at least 2.22 so i suggest you take the 2.22.401.4 and the 2.22.401 stock recovery. Restore the nand and then flash back the stock recovery. Then perform the available OTA and you are back on the latest stock rom
Click to expand...
Click to collapse
Just the job, cheers.
All sorted now and back to stock with OTA capabilities and RELOCKED boot loader.
Thanks for your pointer.
Mr Hofs said:
Hboot 3.18 is at least 2.22 so i suggest you take the 2.22.401.4 and the 2.22.401 stock recovery. Restore the nand and then flash back the stock recovery. Then perform the available OTA and you are back on the latest stock rom
Click to expand...
Click to collapse
Sir, I have the same problem after rooting and flashing TWRP. Except that I am running an HBOOT of 3.19.0000. My software number is 3.28.709.5 and my CID is HTC__621. From the stock Nandroids backup link that everyone is using, I find 2 major software versions under that CID number. Is it also safe to flash the 2..22.709.4 version then? And also is there any possible way to reclaim version-main after processing any OTA updates and rooting again? Am i rooting it the wrong way or flashing the incorrect recovery to begin with? I use Hasoon's AIO Tool to flash.
Thanks!
Sorry to OP for hijacking your thread!
Main is BLANK - Help to find out stock recovery image FILE for HTC ONE M8 taiwan make
Hi Experts ,
Pl help to find out exact stock recovery image for HTC ONE M8 TAIWAN Model to roll back from TWRP.
Details:
1. I flashed TWRP "openrecovery-twrp-2.7.1.0-m8.img" on my HTC__621 using Fastboot ADB
2. Found list of CID for my Firmware(HTC__621) in http://forum.xda-developers.com/show....php?t=2545227
3. Fast boot command resulted in BLANK Main version to get the stock recovery image.
Details on the Fast boot with S-ON, rooted and unlocked:
C:\fastboot>fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.002s]
finished. total time: 0.004s
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4C1WM01867
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s
PLEASE HELP TO ROLL BACK TO STOCK RECOVERY and suggest me a good ROM but my SECURITY IS ON.
bharaka said:
Hi Experts ,
Pl help to find out exact stock recovery image for HTC ONE M8 TAIWAN Model to roll back from TWRP.
Details:
1. I flashed TWRP "openrecovery-twrp-2.7.1.0-m8.img" on my HTC__621 using Fastboot ADB
2. Found list of CID for my Firmware(HTC__621) in http://forum.xda-developers.com/show....php?t=2545227
3. Fast boot command resulted in BLANK Main version to get the stock recovery image.
Details on the Fast boot with S-ON, rooted and unlocked:
C:\fastboot>fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.002s]
finished. total time: 0.004s
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4C1WM01867
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s
PLEASE HELP TO ROLL BACK TO STOCK RECOVERY and suggest me a good ROM but my SECURITY IS ON.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3019919
And please don't post the same message in about 5 or even more threads. Keep it in one because it's hard to follow like this ! Thank you
Stock recovery for M8 -
Thanks. Will keep my updates in the scope of this thread.
I am using TWRP. Couldn't find the stock recovery for my M8 Taiwan make HTC__0621. Details of the Firmware are inline in this thread.
Please help me to get the stock recovery image. Whether i can take it from the lollipop OTA Zip?
Kindly share your Expertise
Mr Hofs said:
http://forum.xda-developers.com/showthread.php?t=3019919
And please don't post the same message in about 5 or even more threads. Keep it in one because it's hard to follow like this ! Thank you
Click to expand...
Click to collapse
bharaka said:
Thanks. Will keep my updates in the scope of this thread.
I am using TWRP. Couldn't find the stock recovery for my M8 Taiwan make HTC__0621. Details of the Firmware are inline in this thread.
Please help me to get the stock recovery image. Whether i can take it from the lollipop OTA Zip?
Kindly share your Expertise
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58417966&postcount=3926
Hi Ckpy,
Still i am not clear on the STOCK RECOVERY Version for my model HTC__621. Please suggest.
Details again i am giving below,
Details:
1. I flashed TWRP "openrecovery-twrp-2.7.1.0-m8.img" on my HTC__621 using Fastboot ADB
2. Found list of CID for my Firmware(HTC__621) in http://forum.xda-developers.com/show....php?t=2545227
3. Fast boot command resulted in BLANK Main version to get the stock recovery image.
Details on the Fast boot with S-ON, rooted and unlocked:
C:\fastboot>fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.002s]
finished. total time: 0.004s
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4C1WM01867
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s
PLEASE HELP TO ROLL BACK TO STOCK RECOVERY and suggest me a good ROM but my SECURITY IS ON.
bharaka said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
PLEASE HELP TO ROLL BACK TO STOCK RECOVERY and suggest me a good ROM but my SECURITY IS ON.
Click to expand...
Click to collapse
You need 3.28.709.6 stock recovery.
Then later you can do OTA to lollipop 4.16.709.9
I can't suggest a good ROM as I don't use custom ROM, only my own made ROM.
After you update to Lollipop, you can try all the available Sense Custom ROM then decide on your own which one suit you the best.
Hi CkpV5,
Please suggest me where to get the IMAGE for STOCK recovery 3.28.709.6. Please help to to understand how you came to find out the correct stock for htc m8.
I forgot to mention that TWRP that i used is for HTC M8 GSM model.
bharaka said:
Hi CkpV5,
Please suggest me where to get the IMAGE for STOCK recovery 3.28.709.6. Please help to to understand how you came to find out the correct stock for htc m8.
I forgot to mention that TWRP that i used is for HTC M8 GSM model.
Click to expand...
Click to collapse
You don't read the link that I posted before ?
http://forum.xda-developers.com/showpost.php?p=58417966&postcount=3926
You details that I shortlisted in previous post tell me your stock version.
Hi CKPV5,
Thanks. I read your previous reply and downloaded the IMAGE 3.28.709.6 but there was another version of stock 4.16.709.9. so bit confused.
Can i flash this stock IMAGE 3.28.709.6? Is it based on the model number that you decide the STOCK?
Cheers,
-BharathI MU
bharaka said:
Hi CKPV5,
Thanks. I read your previous reply and downloaded the IMAGE 3.28.709.6 but there was another version of stock 4.16.709.9. so bit confused.
Can i flash this stock IMAGE 3.28.709.6? Is it based on the model number that you decide the STOCK?
Cheers,
-BharathI MU
Click to expand...
Click to collapse
use 3.28.709.6 as this is what your device need based on your hboot no and radio version no.
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
then do OTA update, it will update your software to lollipop 4.16.709.9
Thank you Very much. I UPDATED MY STOCK RECOVERY USING IMAGE "3.28.709.6_recovery.img". Below is the output on my bootloader screen,
Pl confirm is this the correct output on the stock recovery screen.
1. Screen displays an Red Exclamation mark.
2. In the bottom of the screen there is a yellow display with the output : Device_CW_Install:No CW files. Skip cw installation. Write host_mode:0 done
Please confirm
Yes.. that's stock recovery
Now.. reboot, go settings-about-software update - do update checking - download - install OTA
If there is no problem with your current ROM, it will update it to lollipop
Hi,
My SECURITY IS ON - S-ON. I tried using Firewater and it was discontinued. In my STOCK RECOVERY, there was a TAMPERED word visible.
I UNLOCKED AND ROOTED.
Pl Help how to setup lollipop. I tried SUNSHINE app, but it prompted me that "team is still working on updates.
---------- Post added at 03:26 PM ---------- Previous post was at 03:20 PM ----------
Hi Expert,
Previously in my stock recovery, i can't update lollipop as it prompted me 'MOUNT SDCARD /0 exception. Now i updated my OTA there was a status bar progressing. let me check.
I UNLOCKED and rooted my phone myself. My security is S-ON.
---------- Post added at 03:53 PM ---------- Previous post was at 03:26 PM ----------
Hi CKPV5,
My software is updated to
5.0.1 and HTC sense version is 6.0
Software Number:4.16.709.9
Please let me know whether it is Lollipop version.
My root privilege has been revoked on this update. Can i again update to ROOT.
Pls advise
bharaka said:
Hi CKPV5,
My software is updated to
5.0.1 and HTC sense version is 6.0
Software Number:4.16.709.9
Please let me know whether it is Lollipop version.
My root privilege has been revoked on this update. Can i again update to ROOT.
Pls advise
Click to expand...
Click to collapse
Mentioned many times 4.16.709.9 is lollipop ....
Reflash TWRP then flash SuperSu again to root.
Wait ... you said you want to install custom ROM ... then you don't need to flash SuperSu because custom ROMs are pre-rooted. Just pick one of them and install.
To help you to install "which recovery" already done .. so now it's time for you to enjoy your lollipop and whatever ROM that you like .. I won't get involve when it comes to custom ROM.
Thank you very much
Hi CKPV5,
I have one clarification. Please clarify.
1. Earlier my phone was UNLOCKED and ROOTED. MY SECURITY IS ON.
2. During OTA update, it got failed and indicated "Mount error /0 in SD card".
3. I flashed TWRP 8.x.... and now reverted to STOCK recovery that you prescribed and I updated the same.
4. My OTA update worked finally and my Firmware got updated to Lollipop.
Please share and let me know how it got failed earlier and now got succeeded with same STOCK recovery 3.28.709.6.
Kind Regards,
-Bharathi
okay basically I installed viper rom, everything is working fine, however the moment i turn the phone off and back on it hangs on the htc logo with the red text at the bottom. The strange thing is, If I press any volume buttons I can hear the phone make the sounds and everything, as if the phone is actually on in the background? Can anyone please help me out with this?
The only way I manage to get out of this issue is to install the rom again, and just never really switch the phone off?
one more thing, can I ask what are the full requirements that you need for isntalling the viper rom? unlocked bootloader and rooted and a custom recovery? or do I also need the s-off and the supercid and all that stuff?
ramo55 said:
okay basically I installed viper rom, everything is working fine, however the moment i turn the phone off and back on it hangs on the htc logo with the red text at the bottom. The strange thing is, If I press any volume buttons I can hear the phone make the sounds and everything, as if the phone is actually on in the background? Can anyone please help me out with this?
The only way I manage to get out of this issue is to install the rom again, and just never really switch the phone off?
Click to expand...
Click to collapse
What version firmware are you running? If you installed the latest 2.xx.xxx.x capable Viper ROMs on a 1.xx.xxx.x firmware then you'll have boot up problems, it can take up to 10minutes or so to boot up. If you're still on 1.xx.xxx.x update your firmware.
BerndM14 said:
What version firmware are you running? If you installed the latest 2.xx.xxx.x capable Viper ROMs on a 1.xx.xxx.x firmware then you'll have boot up problems, it can take up to 10minutes or so to boot up. If you're still on 1.xx.xxx.x update your firmware.
Click to expand...
Click to collapse
Thanks for your reply! okay you say firmware however when i go to settings I dont see the word firmware any where? all i see is this:
android version: 4.4.3
htc sense version: 6.0
htc sdk api level: 6.25
software number: viper rom 2.5.0
kernel version: 3.4.0
baseband version: 1.16.xxxxxxx
build number: 2.22.xxx.x
so im not sure what im looking for, so any advice would help.
Thanks.
ramo55 said:
Thanks for your reply! okay you say firmware however when i go to settings I dont see the word firmware any where? all i see is this:
android version: 4.4.3
htc sense version: 6.0
htc sdk api level: 6.25
software number: viper rom 2.5.0
kernel version: 3.4.0
baseband version: 1.16.xxxxxxx
build number: 2.22.xxx.x
so im not sure what im looking for, so any advice would help.
Thanks.
Click to expand...
Click to collapse
Yeah that just pretty much confirms you flashed a 2.22.xxx.x based Viper ROM, but it doesn't tells us what you ran on before you flashed the ROM.
Do you have adb installed on your PC? If not get it from mini-sdk there. You can just extract it to c:\mini-sdk . Open command prompt and type cd /d c:\mini-sdk OR just go to that folder hold shift and right click then select "Open command prompt here".
Make sure you have USB Debugging enabled on your device. Reboot your device into bootloader mode. Connect your phone to your PC and in the command prompt type:
Code:
fastboot devices
To make sure your device is connected, it should show you your device's serial number.
Next type:
Code:
fastboot getvar all
Paste the output from that command in your next post BUT MAKE SURE YOU REMOVE THE IMEI AND SERIAL NUMBER IT'S PERSONAL INFO
BerndM14 said:
Yeah that just pretty much confirms you flashed a 2.22.xxx.x based Viper ROM, but it doesn't tells us what you ran on before you flashed the ROM.
Do you have adb installed on your PC? If not get it from mini-sdk there. You can just extract it to c:\mini-sdk . Open command prompt and type cd /d c:\mini-sdk OR just go to that folder hold shift and right click then select "Open command prompt here".
Make sure you have USB Debugging enabled on your device. Reboot your device into bootloader mode. Connect your phone to your PC and in the command prompt type:
Code:
fastboot devices
To make sure your device is connected, it should show you your device's serial number.
Next type:
Code:
fastboot getvar all
Paste the output from that command in your next post BUT MAKE SURE YOU REMOVE THE IMEI AND SERIAL NUMBER IT'S PERSONAL INFO
Click to expand...
Click to collapse
Thanks for your reply, here is the info:
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.xxxxxxx
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.012s
I hope this helps. would you also please tell me which part indicates the required information? Im very keen in learning.
ramo55 said:
Thanks for your reply, here is the info:
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.xxxxxxx
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.012s
I hope this helps. would you also please tell me which part indicates the required information? Im very keen in learning.
Click to expand...
Click to collapse
Thought it might have been so. So you still ARE on 1.54.401.5/10 as your bootloader 3.16 is still from the 4.4.2 1.54.xxx.x. It changes to 3.18 once you update to 4.4.3. So you need to update your firmware.
You could either go back to stock, you can get a backup from COLLECTION of Stock backup's Instructions on how to restore it can be found in the first 2 posts of that thread as well. The stock recovery itself is also there.
HTC One firmware collection for different CID/MID | 2.22.1540.3 Mike1986 also has a very good tutorial on how to flash firmware on there.
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
ramo55 said:
I hope this helps. would you also please tell me which part indicates the required information? Im very keen in learning.
Click to expand...
Click to collapse
Just for comparison.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Click to expand...
Click to collapse
BerndM14 said:
Thought it might have been so. So you still ARE on 1.54.401.5/10 as your bootloader 3.16 is still from the 4.4.2 1.54.xxx.x. It changes to 3.18 once you update to 4.4.3. So you need to update your firmware.
You could either go back to stock, you can get a backup from COLLECTION of Stock backup's Instructions on how to restore it can be found in the first 2 posts of that thread as well. The stock recovery itself is also there.
HTC One firmware collection for different CID/MID | 2.22.1540.3 Mike1986 also has a very good tutorial on how to flash firmware on there.
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
Just for comparison.
Click to expand...
Click to collapse
okay, would this tutorial work: http://forum.xda-developers.com/showthread.php?t=2735235 ? iv got the same CID number?
ramo55 said:
okay, would this tutorial work: http://forum.xda-developers.com/showthread.php?t=2735235 ? iv got the same CID number?
Click to expand...
Click to collapse
Some of it you won't be able to reset tampered flags etc as you're not S-OFF.
Going back to stock:
1) Download nandroid backup from thread I linked to(Collection)
2) Flash custom recovery, I take it you already have one seeing as you have the red text and bottom. Just make sure you download and flash a custom recovery applicable to the nandroid you're downloading. If it says "TWRP" then flash TWRP, if it's Philz then flash Philz.
3) Unzip the nandroid download into the folder for your backup on your device. Again this information is in post 2 on the thread I linked to. Else just create a backup of "boot" alone and it'll create the directory path for your backups on your device. Unzip the nandroid and place it in there.
5) Boot into custom recovery and Restore nandroid backup.
6) Flash stock recovery. Boot into bootloader if you're not already there - fastboot flash recovery recovery.img you do have adb/fastboot now, just make sure the recovery.img file is in your adb folder and open command in there like before(for getvar).
7) Perhaps not necessary but can do it anyways - fastboot erase cache
8) Reboot device - fastboot reboot
9) Accept prompt for OTA update, install and your firmware is updated.
Done.
Additionally for you if you want:
10) Flash TWRP/Philz recovery back to phone.
11) Flash Viper ROM
First boot up will take a couple of mins or so to setup, afterwards it'll be fine.
BerndM14 said:
Some of it you won't be able to reset tampered flags etc as you're not S-OFF.
Going back to stock:
1) Download nandroid backup from thread I linked to(Collection)
2) Flash custom recovery, I take it you already have one seeing as you have the red text and bottom. Just make sure you download and flash a custom recovery applicable to the nandroid you're downloading. If it says "TWRP" then flash TWRP, if it's Philz then flash Philz.
3) Unzip the nandroid download into the folder for your backup on your device. Again this information is in post 2 on the thread I linked to. Else just create a backup of "boot" alone and it'll create the directory path for your backups on your device. Unzip the nandroid and place it in there.
5) Boot into custom recovery and Restore nandroid backup.
6) Flash stock recovery. Boot into bootloader if you're not already there - fastboot flash recovery recovery.img you do have adb/fastboot now, just make sure the recovery.img file is in your adb folder and open command in there like before(for getvar).
7) Perhaps not necessary but can do it anyways - fastboot erase cache
8) Reboot device - fastboot reboot
9) Accept prompt for OTA update, install and your firmware is updated.
Done.
Additionally for you if you want:
10) Flash TWRP/Philz recovery back to phone.
11) Flash Viper ROM
First boot up will take a couple of mins or so to setup, afterwards it'll be fine.
Click to expand...
Click to collapse
Thanks very much, Iv managed to sort everything out now. Currently running viper rom with the latest ota firmaware
ramo55 said:
Thanks very much, Iv managed to sort everything out now. Currently running viper rom with the latest ota firmaware
Click to expand...
Click to collapse
Great to hear, no more bootup issues then I take it? :good:
Nice, enjoy! :good:
BerndM14 said:
Great to hear, no more bootup issues then I take it? :good:
Nice, enjoy! :good:
Click to expand...
Click to collapse
yep, tried it more than once and everything works perfectly! not bootup issues!
Hi,
I've using CM 11 for a while on my HOX. I didn't have the backup of my original ROM. I didn't think I'd need to sell the phone but I wanted to and I was told to restore the stock ROM back. I thought I got the correct RUU and when I tried to flash (after relocking bootloader and erasing cache), I was told by RUU GUI that there was a bootloader version problem. Reading about it, I found that my HBOOT version is 1.72.0000 and the RUU showed something like 1.29.
After reading further I found that I was downgrading the HBOOT and for that I need to have S-OFF (I have S-ON).
I then extracted the ROM.zip file from the RUU and tried to flash the system.img and boot_signed.img files and found myself in a situation where the phone goes into a boot loader loop.
The battery has been dead and I'm also plagued by the power management bug in HOX ( doesn't charge at all and had to leave it on for days). Luckily it started charging again but since the phone goes into a bootloader loop, the battery is dying.
I found the fastboot-battery-recharge on this forum where I'm trickle charging it.
Can you help me flash the original ROM back by identifying the correct RUU (android files. org)?
My phone details:
F:\HOX>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.164D3.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.161.3
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3547mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
I downloaded this RUU: RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
Would this work when the phone is charged?
Please assist as I want to sell the phone.
Thanks in advance guys.
The battery seems to have charged a little bit and I tried the RUU mentioned above, but it doesn't run fully. I get the initial messages to accept about battery being 30% etc, and then I'm shown the current image versoin 4.17.xxx and then the "Update" button. When I click it, the RUU just closes. I'm trying to download another RUU: RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
In case there was something wrong with the ROM..
The flashing of the second RUU failed this time with error 158. Incorrect RUU. So I went ahead and unlocked bootloader again and CM is back working now thankfully. I still don't know how to flash it with stock ROM correctly. I'm reading about downloading some Nandroid backups 3.20.x versions and restoring it.
I don't want to risk anymore, so please let me know.
Standing by.........
corpuscallosum said:
The flashing of the second RUU failed this time with error 158. Incorrect RUU. So I went ahead and unlocked bootloader again and CM is back working now thankfully. I still don't know how to flash it with stock ROM correctly. I'm reading about downloading some Nandroid backups 3.20.x versions and restoring it.
I don't want to risk anymore, so please let me know.
Standing by.........
Click to expand...
Click to collapse
You will never succsses to flash RUU no RUU for this high main version restore nandroid or install custom rom on it
Ok thank you. That clarifies about RUU flashing. I have downloaded 3.14 (VODAP0001) Nandroid from one of pages of this site and follow the instructions to flash. Hopefully I'll get stock ROM back then.
Do I need to have the stock recovery also? Is stock recovery required for OTA and when factory reset on the stock ROM it would revert back to factory state (going through setup process again)?
corpuscallosum said:
Ok thank you. That clarifies about RUU flashing. I have downloaded 3.14 (VODAP0001) Nandroid from one of pages of this site and follow the instructions to flash. Hopefully I'll get stock ROM back then.
Do I need to have the stock recovery also? Is stock recovery required for OTA and when factory reset on the stock ROM it would revert back to factory state (going through setup process again)?
Click to expand...
Click to collapse
3.14 will not work you will have problem with the tuch will not work you need nandroid with your numbers. Yes stock recovery is need for OTA but you are with latest base I think
Ok. I think I'm having trouble identifying the correct versions then. I thought 3.14 is the bootloader version. Is that the baseband version then?
Since I have 5.1204, do I need to download a Nandroid 5.1204 version?
Can i get some help please unbricking mine i cant seem to find the correct ruu any where ive already relocked the bootloader and now ive been stuck with out a phone for 2 weeks
X:\Fastboot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.164D3.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.161.3
(bootloader) serialno: SH25AW109670
(bootloader) imei: 354461055970384
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3793mV
(bootloader) devpower: 71
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 1.050s
this is all ive got id really apreciate any help
corpuscallosum said:
Ok. I think I'm having trouble identifying the correct versions then. I thought 3.14 is the bootloader version. Is that the baseband version then?
Since I have 5.1204, do I need to download a Nandroid 5.1204 version?
Click to expand...
Click to collapse
you need nand backup with this numbers 4.17.161.3 this with the red is important dont look your CID if you find nand with this numbers is the prfect like 4.18.401.4 this with the red is WWE region, in your case is 161 maybe this is Vodafone I don't know Germany or UK
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
RayOneX said:
Can i get some help please unbricking mine i cant seem to find the correct ruu any where ive already relocked the bootloader and now ive been stuck with out a phone for 2 weeks
X:\Fastboot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.164D3.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.161.3
(bootloader) serialno: SH25AW109670
(bootloader) imei: 354461055970384
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3793mV
(bootloader) devpower: 71
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 1.050s
this is all ive got id really apreciate any help
Click to expand...
Click to collapse
If you read the hole thread you will see no RUU for this main version and unlock your bootloader and flash recovery and then custom rom or nand backup with this numbers 4.17.161.3
Thant said:
you need nand backup with this numbers 4.17.161.3 this with the red is important dont look your CID if you find nand with this numbers is the prfect like 4.18.401.4 this with the red is WWE region, in your case is 161 maybe this is Vodafone I don't know Germany or UK
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
If you read the hole thread you will see no RUU for this main version and unlock your bootloader and flash recovery and then custom rom or nand backup with this numbers 4.17.161.3
Click to expand...
Click to collapse
Can i please get help doing this with a step by step instruction list or even links please
---------- Post added at 05:38 PM ---------- Previous post was at 05:29 PM ----------
RayOneX said:
Can i please get help doing this with a step by step instruction list or even links please
Click to expand...
Click to collapse
Nandroid Backup 4.17.161.2 CID VODAP001 thanks to alextheg will this be okay its from this page http://forum.xda-developers.com/showthread.php?t=1975140
Thant, thanks. I guess 4.17.161.3 is for me. I'll see if there's a uk based VODAP001.
I will use this: 4.17.161.2 CID VODAP001. Will follow the steps mentioned where I got the Nand backup itself.
wohoo!! I got the 'stock' ROM back!! Thanks Thant! You're brilliant! I also copied the recovery.img from the Nand backup. Can I flash that with cmd: "fastboot flash recovery recovery.img"? Can I erase cache and relock bootloader to see if I get OTA? Is that the correct way forward?
corpuscallosum said:
wohoo!! I got the 'stock' ROM back!! Thanks Thant! You're brilliant! I also copied the recovery.img from the Nand backup. Can I flash that with cmd: "fastboot flash recovery recovery.img"? Can I erase cache and relock bootloader to see if I get OTA? Is that the correct way forward?
Click to expand...
Click to collapse
you need stock recovery not this in the backup search for stok recovery for your base or download OTA and choice install later then take the recovery from OTA and flash it
Fixed!! HOX stuck in bootloop and cannot restore ROM
Perfect! I choose install later when the OTA came up on the phone, connected it to my computer and navigated to the download folder on my phone. Found the file : "OTA_ENDEAVOR_U_JB_50_S_Vodafone_UK_4.17.161.3-4.17.161.2_release_369941".
Extracted recovery.img from the firmware.zip file within, copied to my computer, put the phone in fastboot mode and flashed the recovery using command: fastboot flash recovery recovery.img.
That was it. Rebooted the phone and installed the OTA without any issues!!
It back to factory state. Thanks a million Thant!!
corpuscallosum said:
Perfect! I choose install later when the OTA came up on the phone, connected it to my computer and navigated to the download folder on my phone. Found the file : "OTA_ENDEAVOR_U_JB_50_S_Vodafone_UK_4.17.161.3-4.17.161.2_release_369941".
Extracted recovery.img from the firmware.zip file within, copied to my computer, put the phone in fastboot mode and flashed the recovery using command: fastboot flash recovery recovery.img.
That was it. Rebooted the phone and installed the OTA without any issues!!
It back to factory state. Thanks a million Thant!!
Click to expand...
Click to collapse
Good to hear that
Greetings,
So i updated my m8 to marshmallow and then i did these steps to root
1)unlocked Bootloader
2)Flashed TWRP
3)Flashed Superuser.zip
When i did the above, the device stuck at boot screen and so i did the following
4) Recovery mode TWRP
5)Wiped data,cache, system(By mistake)
and then it said "No OS Installed"
I tried to flash the official RUU.exe (RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signe)
which i use to previously do it in case i mess up like this but that RUU is not working any more, it says please run another rom utility ..Image error..
I think the Radio version is updated and also the Hboot too(Not sure)
the current version as i see on screen on fastboot are as follows
M8_UL PVT SHIP S-ON
HBOOT- 3.19.0.0000
RADIO- 1.29.214500021.12G
and also the device variables from the adb are as follows
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished.
Please help me, my phone is stuck since 2 days and im trying everything possible.
Nausheer said:
2)Flashed TWRP
Click to expand...
Click to collapse
What version?
Nausheer said:
3)Flashed Superuser.zip
Click to expand...
Click to collapse
What version???
Nausheer said:
I tried to flash the official RUU.exe (RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signe)
Click to expand...
Click to collapse
You can't run an older version RUU unless you have s-off.
If there is a Marshmallow RUU for your CID, it will work. You will also need to relock the bootloader (if you haven't already).
Otherwise, find a TWRP backup of the proper MM version number. Or just flash a stock/custom ROM to get the phone running again.
redpoint73 said:
What version?
What version???
You can't run an older version RUU unless you have s-off.
If there is a Marshmallow RUU for your CID, it will work. You will also need to relock the bootloader (if you haven't already).
Otherwise, find a TWRP backup of the proper MM version number. Or just flash a stock/custom ROM to get the phone running again.
Click to expand...
Click to collapse
if i get a grab of the MM backup , how do i flash it...
Thank you!!
Nausheer said:
if i get a grab of the MM backup , how do i flash it...
Click to expand...
Click to collapse
Instructions on how to restore TWRP backups is here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I see some MM backups are starting to be posted there. But it doesn't look like one is posted yet for 720.
TWRP-- 2.7.0.2
SuperUser--2.46
i got hands on to the OTA.zip file
this file---->> M8 6.15.720.2 OTA Update ZIP:
https://mega.nz/#!iMBBHBqS!pEKTGDGBk...BJ9g29H3KFAhDY
I'm S-ON....currently it says "No OS Installed"
Will be much appreciated if i can get assistance to get back to either marshmallow or lollipop.
and i just updated my TWRP to 2.8.7.0
What are the possible options for me..
redpoint73 said:
I see some MM backups are starting to be posted there. But it doesn't look like one is posted yet for 720.
Click to expand...
Click to collapse
MM backups on post #3 and it was posted 2 days ago.
ckpv5 said:
MM backups on post #3 and it was posted 2 days ago.
Click to expand...
Click to collapse
Hello, First of all thanks to CKPV5 for the backups for my CID...
So when i try to restore the backup, the screen is stuck at "Restoring System" for 2 hours.. i guess this is not normal..
The following is what happened
1)Downloaded TWRP Backup ..This one-->> 6.15.720.2 https://mega.nz/#!mxZUADbA!y5Nc2PFk9...K5YlsZHdorQgXM
2)Extracted the backup on PC
3)Booted to TWRP recovery and made a backup of boot only(To check where the backup goes on my device).. it was in external SD in twrp/backups/Serialno.)
4) I enabled MTP on TWRP and transfered the 6.15.720.2 Folder to the twrp/backups/serialno.
5) Then i did a wipe of dalvikcache,cache,data,system(Did x3 times as i read somewhere)
6)Restore-- selected the 6.15.720.2 backup and swiped to restore
i waited for 2 hours+ and gave up.. So i downloaded another TWRP backup for my CID HTC__038.. i.e 4.18.720.8 Stock Unrooted ----- http://forum.xda-developers.com/show...&postcount=707
I tried the same above process.. The same problem persists... It's stuck at "Restoring system"
Did i do something wrong? Please assist.. Thanks a ton
Use correct TWRP version 2.8.7.0 or latest
TWRP 2.7.0.2 is outdated, won't work on MM.
Read again all 14 steps..
Also, don't install root/SuperSU offered by TWRP.
Later after all are ok, use only SuperSU 2.67 to root
Nausheer said:
TWRP-- 2.7.0.2
SuperUser--2.46
Click to expand...
Click to collapse
TWRP version is really really old, like KitKat old.
I think you mean SuperSU version, as that number scheme is for SuperSU, and doesn't make sense for SU. And that number doesn't work for MM. That is the reason you got stuck after rooting.
Good rule of thumb, is always check on updated root methods after an update. The old root methods almost never work after a major OS update.
redpoint73 said:
TWRP version is really really old, like KitKat old.
I think you mean SuperSU version, as that number scheme is for SuperSU, and doesn't make sense for SU. And that number doesn't work for MM. That is the reason you got stuck after rooting.
Good rule of thumb, is always check on updated root methods after an update. The old root methods almost never work after a major OS update.
Click to expand...
Click to collapse
I would like to thank Red and CKPV5 for guiding me.. I have successfully rooted my M8... Peace guys
******END OF LINE*****
So the 2.8.0.7 twrp is the lowest we can go with MM, correct me if i'm wrong?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
you have to get OTA.zip from previous version 4.18.720.8 then extract it and find firmware.zip. you have to flash it see this video how to flash firmware https://www.youtube.com/watch?v=ybu7fZa41so
the install twrp and restore 4.18.720.8 stock nandroid. then again install stock recovery instead of TWRP.
Nausheer said:
Greetings,
So i updated my m8 to marshmallow and then i did these steps to root
1)unlocked Bootloader
2)Flashed TWRP
3)Flashed Superuser.zip
When i did the above, the device stuck at boot screen and so i did the following
4) Recovery mode TWRP
5)Wiped data,cache, system(By mistake)
and then it said "No OS Installed"
I tried to flash the official RUU.exe (RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signe)
which i use to previously do it in case i mess up like this but that RUU is not working any more, it says please run another rom utility ..Image error..
I think the Radio version is updated and also the Hboot too(Not sure)
the current version as i see on screen on fastboot are as follows
M8_UL PVT SHIP S-ON
HBOOT- 3.19.0.0000
RADIO- 1.29.214500021.12G
and also the device variables from the adb are as follows
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished.
Please help me, my phone is stuck since 2 days and im trying everything possible.
Click to expand...
Click to collapse
sanjeev835 said:
you have to get OTA.zip from previous version 4.18.720.8 then extract it and find firmware.zip. you have to flash it see this video how to flash firmware https://www.youtube.com/watch?v=ybu7fZa41so
the install twrp and restore 4.18.720.8 stock nandroid. then again install stock recovery instead of TWRP.
Click to expand...
Click to collapse
He solved his problem 5 days ago ..
I can not flash ROM on it anymore, it always comes ZIP File corrupt with the latest TWRP, I have since a RUU flash and which is the right one?
I have a current Fasstboot excerpt here:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .....
(bootloader) imei: .......
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.139s
Try this ruu, I'm not sure it'll works since it's an old version.
https://androidfilehost.com/?fid=24052804347812799
Don't forget to relock your bootloader.
Edit: Oh, I found a marshmallow one https://androidfilehost.com/?fid=24399965296001026
Technoolli said:
I can not flash ROM on it anymore, it always comes ZIP File corrupt with the latest TWRP
Click to expand...
Click to collapse
Try this -
Boot to twrp
Select wipe
Select Format data
Type yes to format
Back to main menu
Select reboot
Select recovery
Once back to recovery, try install rom zip and see how it goes.
If still problem, use RUU provided above.
If still problem .. you may have hardware issue.
Technoolli said:
I can not flash ROM on it anymore, it always comes ZIP File corrupt with the latest TWRP,
Click to expand...
Click to collapse
Did you try different ROMs? Your title "no ROM can be flashed anymore" implies it, but we can't tell for certain, if you aren't specific. What ROMs specifically, did you try?
Or try another version TWRP. What version number TWRP exactly are you using?
I have TWRP 3.2.1-0 and I have used the new Android 8.1 and 8.0 version from here.
So I close first the bootloader again.
adb reboot bootloader
fastboot oem lock
Click to expand...
Click to collapse
Technoolli said:
I have TWRP 3.2.1-0 and I have used the new Android 8.1 and 8.0 version from here.
So I close first the bootloader again.
Click to expand...
Click to collapse
Hi Guys,
My M8 is currently running. not and I want to have it running again no matter how, follower status I have:
- Bootloader open
- Am z.Z. on status *** Relocked *** and S-ON, HBOOT 3.19.0.000 and Radio-1.29.214500021.12G
- And am connected in the status Fastboot USB to the PC.
- No recovery z.Z. it
Now would like to have a running OS on it again by RUU.
Have already read similar problems here: HTC One RUU and NANDROID backup collection
Recovery flash -> signature verify failed
But I can not flash somehow via RUU, have already tried tens of versions.
for example from here AndroidRUU | The # 1 source for Android RUU files.:
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4.20.654.10_Radio_1.09.20.0119_NV_SPCS_1.52_003_release_418492_signed_2
RUU_M8_UL_K44_SENSE60_MR_TMOUS_2.22.531.5
RUU_M8_UL_K44_SENSE60_MR_TMOUS_2.22.531.6_R_Radio_1.19.213311491.03G_20.56.4198.02L_F_release_387828_signed_2
RUU_M8_TMOUS_1.57.531.7
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
RUU_M8_UL_K444_SENSE60_MR_TMOUS_3.32.531.2_Radio_1.22.213311491.08G_20.56.4198.02_F_release_394971_signed_2
Technoolli said:
But I can not flash somehow via RUU, have already tried tens of versions.
for example from here AndroidRUU | The # 1 source for Android RUU files.:
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4.20.654.10_Radio_1.09.20.0119_NV_SPCS_1.52_003_release_418492_signed_2
RUU_M8_UL_K44_SENSE60_MR_TMOUS_2.22.531.5
RUU_M8_UL_K44_SENSE60_MR_TMOUS_2.22.531.6_R_Radio_1.19.213311491.03G_20.56.4198.02L_F_release_387828_signed_2
RUU_M8_TMOUS_1.57.531.7
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
RUU_M8_UL_K444_SENSE60_MR_TMOUS_3.32.531.2_Radio_1.22.213311491.08G_20.56.4198.02_F_release_394971_signed_2
Click to expand...
Click to collapse
You should NOT be guessing which RUU to use.
All the ones you listed (except the one that says "Europe") are for US versions (Sprint, and T-Mobile US = TMOUS) and will not work on your device.
Further, Sprint M8 is a CDMA device. If it did flash it would radio brick your phone.
Only the RUU intended for your device specific CID and MID will work. And there aren't many for your version, that I know of (T-Mobile Europe).
Technoolli said:
Recovery flash -> signature verify failed
Click to expand...
Click to collapse
You can only flash a custom recovery (TWRP) with an unlocked bootloader. Trying to flash TWRP with locked bootloader will always give "signature" error as the file is not signed by HTC.
Did you try to format data as ckpv5 suggested in Post #3 above?
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
Technoolli said:
- No recovery z.Z. it
Click to expand...
Click to collapse
You had TWRP before. How did you get to the point of having no recovery?