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!
Related
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.
I Was following the guide > http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792 to update my firmware and CID which i successfully did. As per the tutorial, it mentioned that i should copy a ROM on sdcard before procedding. Which i did but amazingly the ARWWizard also flashed my SDCARD (? Not sure but my card was empty).
Anyways, I was able to boot into the OS (old) and i realized i need to install recovery. I issued
Code:
adb reboot bootloader
fastboot flash recovery <recovery_image>
I tried installing TWRP 2.8 but it remains stuck at "Entering Recovery", so i isntalled 2.7 and I was successfully in the recovery. There I wanted to cleaned everything, internal storage, cache, delvik cache etc (not microsd). And went on to menu to install OS from sdcard but it was empty.
I thought lets do the sideload with
Code:
adb sideload rom.zip
and got error Can not read rom.zip.
I changed the location of rom.zip to other location and did adb from that location but still no luck. I was under the impression that since i have installed recovery ... I can reboot ... I tried and now i am stuck at Android Boot loading screen ...
While on that screen, my computer shows that it is trying to install MTP drivers but it fails and hence now i can't use ADB to reboot or do anything.
Any help would be appreciated.
I answered you here!
Forsaked said:
I answered you here!
Click to expand...
Click to collapse
alright .. after struggling so much i am finally able to have my phone running. But i guess the ARUWizard didn't upgraded the firmware. The reason i am saying this is that I installed Viper4.1 ROM and it clearly stats in their FAQ that my WiFi wouldn't work if i don't have proper firmware.
Looking at this guide I am confused which firmware to install.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go
EddyOS said:
If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go
Click to expand...
Click to collapse
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing
..alee said:
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing
Click to expand...
Click to collapse
Very nearly right...
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
[B]fastboot reboot-bootloader[/B]
fastboot flash recovery twrp.img
You missed the dash
The firmware flash might need to be done twice. If it says it's failed and reboots the unit, do the same command again to flash it but if it says complete then reboot the bootloader to flash TWRP
Thanks ...
I got it working but now there are two weird issues.
1. My camera doesn't work. Whenever i click on HTC Camera, it shows a black screen (as if camera view is blocked, I can see on screen buttons and options but black background).
2. My phone doesn't recognize the SD Card which i was using before.
Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?
EddyOS said:
Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?
Click to expand...
Click to collapse
Just want to let you know that the camera issue is before installing this ROM. It was because of the camera that i decided to upgrade from 4.3 to 5.0 Android. The SD card issue has been resolved. Here is my fastboot command details
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now
EddyOS said:
I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now
Click to expand...
Click to collapse
my main version is blank ever since I started upgrading my phone. Even if you look at the posts which posted 3 days before (before upgrading) they all had blank main-version.
True. If you are willing to try putting your phone back to 100% you could use the guide in my signature and then at least you'll be back to a point where it should all work
okay ... from your post it seems like only devices with HTC_* CID's can be restored to stock. Given that I am supercid, I can write whatever CID I Can but my original cid was VODP001. Do i have to worry about that ? Would your method work on my device as well ?
Super CID means you can flash anything so just try it. OK, it'll go back to the unbranded build as opposed to the Vodafone build but that's not a bad thing
Hi,
Apologies in advance because I'm sure this is a very noob problem, but I was trying to update my M8 to lollipop and ended up messing it up somewhere. It was rooted before, S-Off, unlocked, using Android HD 4.4.4.
When I try to flash the Android HD Lollipop rom in TWRP from internal or external sdcard, or from USB OTG, the installer starts and looks successful until it gets to "Creating toolbox symlinks". After that it says "symlink: some symlinks failed"
When it finishes, it goes back into recovery and TWRP says "Successful"
When I go to reboot TWRP says it isn't rooted and asks if I'd like to root. Whether I say "yes" or "no" it reboots to a white HTC screen with a little lock at the bottom. The lock wasn't there when I started. After a few seconds the screen turns off then back on, then it goes into recovery.
If I try to install the update-supersu from internal or external card, or from USB OTG, in TWRP it says "success" and no errors, but then when I go to reboot it, it says "does not appear to be rooted" and asks if I'd like to root it. Whether I say yes or no it reboots, freezes, then boots into recovery and I start over.
In boot where it used to say "tampered" it now says "modified", and under that "unlocked", "s-off", a bunch of numbers that look important, but nothing in "OS-".
I can get into recovery and fastboot or hboot just fine. I have ADB, fastboot, and I think all the drivers I need on my laptop, and both recognize my phone when it's plugged in and I type "adb devices". I've tried like 10 different guides to push and flash and honestly too many commands to remember, but nothing that can get it to boot into a working rom.
To be honest, every single time I've tried to root something, I've broken something, but usually if I keep looking I can find the same problem and someone who's fixed it and figure it out, but I've been at it nearly 20 hours straight now and I just can't see what I'm missing (besides OS Dx)
If anyone knows what I've done and how to undo it, I'd be grateful for any advice.
Thanks,
Josh
*** I think I got the wrong firmware, but not sure how to find the right one without downloading them reandomly and checking the android-info***
Boot to bootloader/fastboot then run command fastboot getvar all
Post here the result (delete serial no. & imei no.)
Will see what we can do later
Your problem most probably is the old version of TWRP (2.7.0.2) that you use.
You should try 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware.
Sure
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader)
(bootloader)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Blue67982 said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
So you have a AT&T device.
What actually you want to do because there is no lollipop update for AT&T yet.
Since your device is S-Off, you can change
CID : CWS__001 to 11111111
MID : 0P6B12000 to 0P6B10000
then flash a EU firmware.
Or you take any unsigned EU firmware.zip, open it with 7-zip and extract out the android-info.txt and edit this android-info.txt to include your CID and MID (use notepad++ for this), drag the modded android-info.txt into the unsigned firmware.zip
Flash this modded firmware, should work too.
And important thing about TWRP : 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware
Then you can install any of the lollipop Sense base custom ROM.
Thanks. I'll chug some coffee and give it a try.
Ok, I changed my CID and MID without too much trouble, but about "TWRP : 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware", how can I tell which I have?
Oh, I used the ADB method if that matters.
After change of CID/MID, you need to flash firmware.zip in RUU mode not ADB.
Your current firmware is KitKat .. if you stick to it, you need 2.8.3.0
After you flash a 4.xx.xxx.x firmware - you need 2.8.5.0
Check this : http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Thanks for putting up with all the questions.
I just want to make sure I'm doing this correctly. I need to update the firmware to a 4x one, then twrp 2.8.5.0, then root and rom? I'm reading the guide you linked, but I'm not sure which firmware to use, for example it lists 5xxBase, then underneath it lists firmwares starting with 4xx.
Or does it not matter?
1. Update firmware, flash the widely use - 4.16.401.10
2. Flash TWRP 2.8.5.0
3. Install ROM
No need manual root because custom ROM is prerooted.
I got to go now .. be back in next 4 hrs
ckpv5 said:
flash the widely use - 4.16.401.10
Click to expand...
Click to collapse
TYSM!! That's what I was looking for
Ok, I updated the firmware and TWRP (I think), but when I try to do anything like flash a rom all the partitions come up as unmountable before the installer starts. I know I read something similar before so I'll try to find that.
\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You don't seems be using the updated TWRP 2.8.5.0
Your fastboot shows that you may use the old 2.7.0.2
Download and install TWRP 2.8.5.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.5.0-m8.img
Then boot to recovery - select wipe - advance - format data - yes
Go to reboot menu - select recovery (to reboot back to recovery
Select "Mount" menu - enable MTP
Transfer the ROM zip to either Internal Storage or MicroSD (if you have one)
Then try to install the ROM.zip
that's so weird...from within twrp the little info bar thing at the top says v2.8.5.0
Ill install again
Yeah .. unless you remove the (bootloader) version-main: info, TWRP 2.8.5.0 should not remove that after you flash the firmware.
Anyway ... try the other steps that I mentioned.
You did it man, you fixed the phone I thought I would have to throw away.
Thanks for answering so many noob quuestiuns
I owe you one
Blue67982 said:
You did it man, you fixed the phone I thought I would have to throw away.
Thanks for answering so many noob quuestiuns
I owe you one
Click to expand...
Click to collapse
Great :good::good:
You don't owe me anything ... just love to help
Since he had a at&t phone, why did you not tell him the change the cid to dev edition and run the ruu in fastboot mode, that wont have been easier?
toysoldierq said:
Since he had a at&t phone, why did you not tell him the change the cid to dev edition and run the ruu in fastboot mode, that wont have been easier?
Click to expand...
Click to collapse
Different ways to skin the same cat. There is nothing "wrong" with the solution that was used.
It worked, and now I know to make 100% sure I have the right versions of everything BEFORE I start, so I'm happy.
Soooo....Noob right here :]
I did a really stupid thing, I tried rooting my HTC One M8. I followed the steps, and it worked fine until I flashed and rebooted. After that, the phone was stuck at boot logo, so I decided to just factory reset it, but somehow, after doing that through TWRP, it reboots > went through logo white screen > then stuck at a black screen. I waited for about 20 mins but no luck. What should I do now?
dwerp1234 said:
Soooo....Noob right here :]
I did a really stupid thing, I tried rooting my HTC One M8. I followed the steps
Click to expand...
Click to collapse
What steps?
There are a few different ways to go about rooting, plus if you don't tell us what TWRP version, stock Android version, SuperSU version, etc. we have no way of knowing what you did, much less how to help you.
dwerp1234 said:
so I decided to just factory reset it
Click to expand...
Click to collapse
Why? Did you read somewhere that this was the proper thing to do for the specific situation? Or did someone tell you? If no to both, don't make up your own solutions or try to guess how to fix things. Its a good way to make matters worse than they already are.
There is no reason to think that a factory reset would fix the issue. There is a common misconception of what "factory reset" actually does. All it does is wipe user data, nothing else. It doesn't replace the ROM, or anything like that.
I'm not sure what Android version my phone is right now (I do not know how to check), the TWRP is 2.8.7.0 for M8, the SuperSU just came with the TWRP, so I just followed the TWPR and got the installer, after that, I downloaded the Root pack or sth like that, but it wasn't automatically rebooting into root mode, so I downloaded the pack and then manually reboot it, after that, it froze on boot logo
I read the factory reset thing on a forum too. Besides wiping cache and data, I wiped the system as well, so there is currently no OS right now, and then planned to download the ROM onto an ext SD card then install it through TWRP. But right now, I still haven't find the proper stock ROM in zip file.
Thanks for your reply, I hope this information helps
dwerp1234 said:
I'm not sure what Android version my phone is right now (I do not know how to check), the TWRP is 2.8.7.0 for M8, the SuperSU just came with the TWRP, so I just followed the TWPR and got the installer, after that, I downloaded the Root pack or sth like that, but it wasn't automatically rebooting into root mode, so I downloaded the pack and then manually reboot it, after that, it froze on boot logo
I read the factory reset thing on a forum too. Besides wiping cache and data, I wiped the system as well, so there is currently no OS right now, and then planned to download the ROM onto an ext SD card then install it through TWRP. But right now, I still haven't find the proper stock ROM in zip file.
Thanks for your reply, I hope this information helps
Click to expand...
Click to collapse
No offense, but this sounds WAY out of your league., especially if you don't know how to check your Android version. It's always best to read directions thoroughly first and ask for help before actually attempting to start modifying your device.
You could always try restoring to stock using the specific RUU for your device. I had to do that recently myself in order to get S-OFF.
http://www.htc.com/us/support/rom-downloads.html
dwerp1234 said:
I'm not sure what Android version my phone is right now (I do not know how to check)
Click to expand...
Click to collapse
Do you remember if it was on KitKat, Lollipop, Marshmallow?
You unlocked the bootloader by yourself? Is it currently unlocked?
Connect phone to computer, reboot the phone to bootloader, and select FASTBOOT (if not already highlighted in red) using the vol and power keys. Then open a command prompt on the computer and type command: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before posting).
The output will help tell us the Android version, as well as other critical info to get your sorted out.
dwerp1234 said:
the SuperSU just came with the TWRP
Click to expand...
Click to collapse
Depending on what Android build you are trying to root, the built-in root on TWRP won't work. Which is why we need to know the Android version.
dwerp1234 said:
I read the factory reset thing on a forum too. Besides wiping cache and data, I wiped the system as well, so there is currently no OS right now, and then planned to download the ROM onto an ext SD card then install it through TWRP. But right now, I still haven't find the proper stock ROM in zip file.
Click to expand...
Click to collapse
Deleting the OS is usually not a good idea; and in your situation not a legitimate solution. Even if you were going to flash a new ROM, that process wipes system partition anyway, so no need to do it manually. And wiping the OS before finding the right ROM to flash was also not a great idea.
It might not have made a difference in your case (since you couldn't boot to OS even before you wiped it). But wiping system shouldn't be done unless you really have a good reason to do it, and you understand what the result will be.
I can't count how many posts I've read (and helped) that stated along the lines of "I wiped system and now my phone won't start, please help".
Hmm, thanks for that link, my Android is 5. Lollipop, I just get so confused with all the numbers on bootloader...How do you get S-OFF though? I've been trying to do that, but found no answer.
My Android is indeed unlocked, I followed the instruction on the internet and got it unlocked.
Oh, here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
For the wiped system situation, I followed the instruction on a website on how to install stock ROM, but I'm stuck on finding a stock ROM myself, and I thought deleting the OS wouldn't make any difference.
dwerp1234 said:
My Android is indeed unlocked, I followed the instruction on the internet and got it unlocked.
Oh, here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
For the wiped system situation, I followed the instruction on a website on how to install stock ROM, but I'm stuck on finding a stock ROM myself, and I thought deleting the OS wouldn't make any difference.
Click to expand...
Click to collapse
What websites are you going to, and why? Everything you need to know about rooting can be found here.
Download this onto your PC. It's an RUU for your model and firmware version. Also, it's a direct download link, so don't click it on your phone.
After the download is finished, hook your phone up to your PC. Get into fastboot, and enter fastboot oem lock. This will lock your bootloader, which you will need to do since you are S-On.
After that, double click on the download and follow the prompts.
This will get you back to your stock state. Unlock your bootloader again via htcdev.com, use fastboot to flash TWRP2.8.7.0, then use your new recovery to flash the latest SuperSU update.zip, or simply flash a rooted ROM with that same recovery.
That's it. Fixed phone and rooted.
xunholyx said:
What websites are you going to, and why? Everything you need to know about rooting can be found here.
Download this onto your PC. It's an RUU for your model and firmware version. Also, it's a direct download link, so don't click it on your phone.
After the download is finished, hook your phone up to your PC. Get into fastboot, and enter fastboot oem lock. This will lock your bootloader, which you will need to do since you are S-On.
After that, double click on the download and follow the prompts.
This will get you back to your stock state. Unlock your bootloader again via htcdev.com, use fastboot to flash TWRP2.8.7.0, then use your new recovery to flash the latest SuperSU update.zip, or simply flash a rooted ROM with that same recovery.
That's it. Fixed phone and rooted.
Click to expand...
Click to collapse
Thanks for your answer. If you don't mind me asking, but what is the latest stable SuperSU for my version? Is it 2.65?
Edit: After I tried to run the ROM Update .exe, it ended up with an error: ERROR [170]: USB CONNECTION ERROR, although I already connected my phone and it is currently stuck on boot screen as always.
dwerp1234 said:
Thanks for your answer. If you don't mind me asking, but what is the latest stable SuperSU for my version? Is it 2.65?
Click to expand...
Click to collapse
As you are still on Lollipop, any SuperSU version 2.44 or up should be find. I think 2.46 is the latest version still labelled as STABLE.
If you were updated to Marshmallow, you would need 2.62 or higher. Those are labelled as BETA, but folks have been using them with no issues, in my understanding.
dwerp1234 said:
Edit: After I tried to run the ROM Update .exe, it ended up with an error: ERROR [170]: USB CONNECTION ERROR, although I already connected my phone and it is currently stuck on boot screen as always.
Click to expand...
Click to collapse
On boot screen, in fastboot mode (with fastboot highlighted in red)?
You were able to do fastboot getvar all, so I assume "yes" to the that question. So in that case, the RUU can be very finicky. Try re-installing HTC Sync, different USB port, different cable.
You might even need to try another PC. Win7 and USB 2.0 (USB 3.0 is known to cause issues) are your best bet to get the RUU to work.
redpoint73 said:
As you are still on Lollipop, any SuperSU version 2.44 or up should be find. I think 2.46 is the latest version still labelled as STABLE.
If you were updated to Marshmallow, you would need 2.62 or higher. Those are labelled as BETA, but folks have been using them with no issues, in my understanding.
On boot screen, in fastboot mode (with fastboot highlighted in red)?
You were able to do fastboot getvar all, so I assume "yes" to the that question. So in that case, the RUU can be very finicky. Try re-installing HTC Sync, different USB port, different cable.
You might even need to try another PC. Win7 and USB 2.0 (USB 3.0 is known to cause issues) are your best bet to get the RUU to work.
Click to expand...
Click to collapse
Thanks a lot, I changed the port and it runs fine. The ROM is being updated right now. It says it will take 10 mins, but it has been 40 minutes and still 0/6. I'm using win10 btw. I have no win7 around.
dwerp1234 said:
Thanks a lot, I changed the port and it runs fine. The ROM is being updated right now. It says it will take 10 mins, but it has been 40 minutes and still 0/6. I'm using win10 btw. I have no win7 around.
Click to expand...
Click to collapse
You have connection issue .. I'm on Win 10 64-bit and no problem when running RUU.
You need to use USB2.0
Latest HTC USB driver installed - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
And I always see many people with USB connection and unable to run RUU ... that's why we have nandroid backup to restore to stock.
Check - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
These are my getvar all results . Guidance please
(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: SH4BTWM00156
(bootloader) imei: 357336066036366
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TNTN 997 SU said:
These are my getvar all results . Guidance please
(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: HTC__203
(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
Click to expand...
Click to collapse
remove your serialno and imei
Then what do you need ?
ahmed.ismael said:
remove your serialno and imei
Then what do you need ?
Click to expand...
Click to collapse
I tried to root my device and it didn't work properly and now it is stuck in the boot logo "that white screen with green hhtc on it". I was runniing on marshmellow and twrp version 3.0.2. I factory reset it but still didn't work. I wanna go back to stock. tried different ways but still didn't work
TNTN 997 SU said:
I tried to root my device and it didn't work probably and now it is stuck in the boot logo "that white screen with green hhtc on it". I was runniing on marshmellow and twrp version 3.0.2. I factory reset it but still didn't work. I wanna go back to stock. tried different ways but still didn't work
Click to expand...
Click to collapse
Here all you need is in this post follow the instruction and you will be back to stock be aware that your internal storage will be wiped
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
after that if you want to root your device flash the latest twrp then flash the latest supersu.zip ( 2.78 SR1 )
ahmed.ismael said:
Here all you need is in this post follow the instruction and you will be back to stock be aware that your internal storage will be wiped
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
after that if you want to root your device flash the latest twrp then flash the latest supersu.zip ( 2.78 SR1 )
Click to expand...
Click to collapse
Thanks alot
TNTN 997 SU said:
I factory reset it but still didn't work. I wanna go back to stock. tried different ways but still didn't work
Click to expand...
Click to collapse
To be clear, factory reset doesn't revert anything back to stock, aside from (all it does is) wiping user data.
failed to flash anything to my htc one m8
how can i get rid of this error
Code:
target reported max download size of 1826418688 bytes
error: cannot load 'Unlock_code.bin': No error
edwinariko said:
how can i get rid of this error
Code:
target reported max download size of 1826418688 bytes
error: cannot load 'Unlock_code.bin': No error
Click to expand...
Click to collapse
The error message "cannot load" means the file isn't in the right place. You need to put the unlock bin file in the same folder which contains fastboot.exe (and where you are executing the command from).
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?