Self-admitted newb here. Been reading up on FAQs and instructions on how to Root my new device and am eager to learn more to eventually fully optimize. I was able to unlock, but when attempting to flash TWRP recovery, it'll just hang forever with this message:
"sending 'recovery' (11976 KB)...".
I confirmed checksums of files downloaded, USB Debugging is flagged, Fastboot is deselected, updated the HTC drivers on my PC, and my S/N is acknowledged with the 'fastboot devices' command. I even did a Factory Reset from bootload screen, as this is a new device with no data on it yet.
Any helpful suggestions on determining next steps would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You need 2.7 series..
flyera343 said:
You need 2.7 series..
Click to expand...
Click to collapse
Agreed, and I was mistakenly attempting to flash twrp-2.8.6.1-m8.img initially . I'm sorry I failed to mention that in the original post and yes, I also did erase cache several times. Re-attempting to flash twrp-2.7.0.1-m8.img is when the 'sending recovery' hang issue comes up.
bump
pill_popper said:
(bootloader) version-main: 1.54.401.109
(bootloader) modelid: 0P6B12000
(bootloader) security: off
Click to expand...
Click to collapse
You have a very old software version. Since your device is S-Off, I suggest :
1. change the MID 0P6B12000 to 0P6B10000
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2708581
2. run 4.16.401.10 RUU.exe - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
RUU will flash your entire phone back to stock including recovery
(as your device is S-Off, no need to lock/relock bootloader)
3. Now you can install the latest TWRP recovery and do whatever you want to do
Thank you for your kind words. I appreciate it. Will follow up on the points covered in your post and report back.
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery. This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
ckpv5 said:
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery.
Click to expand...
Click to collapse
Correct, sorry if I wasn't being clear about that. I've Unlocked, but not yet rooted hence, the attempt to send TWRP. I haven't yet taken next steps though.
ckpv5 said:
This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
Click to expand...
Click to collapse
More reading! :cyclops:
**Updated**
So I've tried using Minimal ADB tool as well. Now instead of hanging, I'm eliciting errors.
target reported max download size of 1830711296 bytes
sending 'recovery' (11976 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.023s
I'm running as Administrator in Windows 7, I can hear the PC recognize the phone when I plug it in the USB and I've also confirmed multiple times the 'fastboot devices' command recognizes my phone.
If this might be a USB related issue, how would I go about investigating in that direction? Not sure what is preventing me from simply flashing a TWRP recovery. Any thoughts on this are welcome, thank you.
*bumpity bump*
So I can see 'FASTBOOT USB' in bootloader mode, and the fastboot devices command returns my S/N, but still the adb devices command just returns the message 'list of devices' and nothing else. Attempting to flash TWRP recovery still fails. I've uninstalled all HTC stuff and manually updated the driver to 'MTP USB Device' via Device Manager per redpoint73's advice. Before I give up on this PC, are there any additional steps I can take? Any guidance from you guys would be appreciated, thanks!
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
ckpv5 said:
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
Click to expand...
Click to collapse
I guess what most on here would consider to be trivial are to me revelations. Thank you for your response and now I see my device S/N is recognized after running the adb devices command when the phone is running in 'normal' mode! Yes, it is properly working but sadly, all four USB ports on the PC are USB 3.0 I'll read up on your suggestions and reply with questions at that point before taking action. Again with the reading! :cyclops: My concerns here are if stock recovery would continue to work if I go down either of those paths and how the phone is supposed to respond if it's not responding when attempting to flash TWRP. Thanks again for your inputs, I appreciate it!
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
ckpv5 said:
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
Click to expand...
Click to collapse
If I wanted to attempt #3, please point me to the correct version as it wasn't clear to me what file to choose here:
http://forum.xda-developers.com/showthread.php?t=2701376
Thanks!
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
ckpv5 said:
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
Click to expand...
Click to collapse
The whole point of this exercise is to gain root so that yes, I can have the option of flashing a custom ROM. I noticed in the executable's file name you referenced model M8_UL_L50, but mine is M8_UL_CA. I also noticed its radio version differs from the one listed in my getvar all file. *edit* I've now realized this file is straight from HTC.
Since my current version is so old, is it still OK to run this to update to the latest version rather than updating to an intermediate version before updating to the latest version? Just wanted to confirm before taking any unnecessary action. Thank you again for your patience and the helpful information!
M8_UL - M8 with LTE
L50 - Android L 5.0
CA - US region
Radio version different because yours is old/lower version and this is newer/latest version and you're going to update hboot, radio and many more with this RUU. You need the update in order to install custom ROM as I mentioned before most custom ROMs work only on hboot 3.19.0000
You have S-Off device, you don't need intermediate version ... and most important RUU doesn't need intermediate version because RUU will wipe clean your device and replace all images with those come with it. (So make a backup of your important files to PC)
Related
Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?
Hi
As the title says I completely erased my phone. The file structure seems to be there still from a fairly old ARHD 4.4.4 install. I did a Nandroid before doing this and it is backed up on my computer. Because it is an older (KK) ROM I'm on TWRP 2.8.1.0. I've tried to do
1 ADB pushed a version of that over to the device and tried to install with TWRP but it wouldn't install.
2 an ADB sideload of the latest GPE ("blues") by lyapota, but it didn't install. Does this take a super long time, as I'm trying it a second time. First time I cancelled after about 10 mins of no activity.
So, I'm in a bit deep here. At this point I'm even afraid to unplug the phone from the computer as I fear I'll never get it to boot again. Can I still access the phone by turning it on via booting into download mode/recovery?
If generous, can you walk me through step by step? Otherwise, is there a good guide that will step by step me through the process? A 2014 version of this thread referred the poor guy to the FAQ, but it doesn't cover this case.
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
ckpv5 said:
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA14G
(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
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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
Should I start looking for a stock kitkat ROM or RUU?
Is there a thread you know of, or a good google search term I can start my learning on?
And most importantly, will anything I do ever eliminate my s-off?
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ckpv5 said:
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Sounds OK, will that install a less effective radio, or are radios not affected? I have S-off for exactly this kind of this instance, but i guess it could be construed as the cause too.... The main reason is getting bloat off the ROM though.
Should be fine. As far as I can remember, both TWN and EU have same radio.
The different is slightly on rcdata... but that another story, won't affect anything at where you are now.
Being a S-Off device you can change the OS version at any time that like.
Weird, I downloaded minimal adb fastboot, and I can fastboot devices and get my serial, but adb devices returns device null. Am I missing something? The phone is in bootloader mode. Should I be in TWRP?
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how? Every time I reboot TWRP it asks me if I want SU, but the process hangs.
Can the HTC utility restore a phone in this state, and not lose s-off? I put the external SD in the phone, with the nandroid I did today, and am trying to transfer it into the bare file system, where should I put it. Why can't TWRP just see the nandroid on the external? WIll the nandroid be of any value to me at this point?
When I try to do this:
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
it tells me "cannot copy system.ext4.win000" "it's file size is larger than the device limit"
So do I need to re partition somehow? How would I do that? How can I find, and post, what the filesystem layout is now if more info is needed?
I have the TWRP backup on the external SD, but restore won't see it either.
Or what about the Hasson2000 toolkit to push an RUU to it?
Sorry guys, I still need help. I try to do adb shell, but can't seem to get root (su) . Because of this I am afraid of moving forward. I have changed my CID to GOOGL001 using HASOON2000's toolkit as I've decided I might as well go full goog since I'm at this point. I think my MID 0P6B11000 is OK, as it's mentioned in graffixnyc/Enewman17's GPE thread, correct? I've downloaded the MM H11 and it's waiting, but I'm afraid to move forward with the root problem better explained in the post above. Am I overly worried?
downwiththebanksters said:
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how?
Click to expand...
Click to collapse
No .. while in TWRP you just run adb shell, no need SU because while in TWRP it's already rooted ..
so
adb shell
~ # <[6n
then paste in the code to change MID then type exit, exit
If you want to run the EU WWE RUU that I linked above, you also need to change the CID .. I suggest a SuperCID 11111111 then later you can run anything that you like as long has you have the correct MID for the RUU that you're going to install.
Now .. since you changed the CID to Google CID and intended to install a GPE RUU .. read through the thread that you linked .. can't help much .. maybe someone else will help you for the GPE conversion.
Still I suggest, instead of running a Google CID ... change it to SuperCID so you don't have to every time change the CID when you decide to run other RUU.
EDIT :
I just remember something .. there is a RUU zip for Taiwan HTC__621 that you can use (but you need to put back the CID to HTC__621 (the original CID) or make it SuperCID 11111111
The steps are the same as I posted before. You need to use htc_fastboot.exe and follow those fastboot commands to install a RUU zip.
Or if you have a microSD card, you can rename the RUU zip to 0P6BIMG.zip and put it on your microsd. On fastboot, select hboot .. it will scan the 0P6BIMG.zip and ask whether you want to update, volume up to update. Once completed, remove this 0P6BIMG.zip from your microsd.
Later you can do all the OTA to the latest.
Download 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip here : http://androidruu.com/?developer=M8
Well as I said above I decided to try the full GPE RUU, so I followed these instructions. I used hasoon2000's toolkit to change the CID, my MID was compatible with the GPE. I then fastboot bootloader and:
Method 1
*ADB / Fastboot*
First, make sure you have the path to adb and fastboot setup in your system environment variables
When you open a command prompt, open it in the folder the zip is in. Hold shift, Left Mouse click, open command prompt here.
1. Rename the RUU.zip to something short and easy like RUU.zip
2. adb reboot bootloader "press enter" Wait till phone reboots into fastboot
3. fastboot oem rebootRUU "press enter" Wait till the phone is in RUU mode (black screen with HTC logo)
4. fastboot flash zip RUU.zip "press enter"
*You will get the following message: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
*RUU mode will reboot,
*Now run the same command again,
5. fastboot flash zip RUU.zip "press enter"
6. fastboot reboot-bootloader "press enter"
7. Select hboot, Do a factory reset in recovery. To enter the recovery menu when greeted by the Android with an exclamation, Hold Power button and click Volume UP.
8. Done, reboot system.
It took a long time for the ROM to install, but I was happy to see the Google splash screen rolling along.
Overall a bit scary as I worried about potential partition issues, but I could see the naked filesystem poking around in TWRP, and knew it wasn't a brick because I got the HTC splash screen and TWRP. I'm not totally in love with the GPE right now, as I miss the Nova launcher layout (fixable, installing now), and I can't toggle data with a homescreen widget (unfixable, now 3 clicks with dropdown...first world problems!!). Bottom line, be careful with what you wipe in TWRP! Thanks to you ckpv too!
Ok this is what happened.
I had the rom Android Revolution installed on my HTC M8.
Today I installed the new ROM Revolution, Android 6.0, but when I could not turn on wifi.
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot. He won't let me into recovery anymore, if i chose it, he trows me back to fastboot menu
SCREEN IN FASTBOOT:
Tampered *** ***
*** *** Relocked
M8_UL PVT SHIP S-ON
HBOOT-318.0.0000
RADIO 1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS 2.22.161.6
eMMC boat 2048MB
RUU
anyone have a solution?
Do i have to update firmware now, really don't now wich steps i should take right now.
Thanks for the effort
C:\mini-sdk>fastboot getvar all
(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.161.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
C:\mini-sdk>
Mcdrug said:
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot.
Click to expand...
Click to collapse
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?
redpoint73 said:
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?
Click to expand...
Click to collapse
download
M8_6.12.401.4_WWE_TWRP2870.zip
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
rcdata.img
rpm.img
sbl1-8974AA-1.img
sbl1-8974AB-1.img
sbl1-8974AB-2.img
sdi.img
sensor_hub.img
splash1.nb0
tp_SYN3508.img
tp_SYN3528.img
tz.img
wcnss.img
adsp.img
android-info.txt
error message:
i thought it was something like (FAILED (remote: 12 signature verify fail). maybe have to do it again to make sure what error message i got?
Mcdrug said:
download
M8_6.12.401.4_WWE_TWRP2870.zip
i thought it was something like (FAILED (remote: 12 signature verify fail).
Click to expand...
Click to collapse
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
redpoint73 said:
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)
Mcdrug said:
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
You need to unlock the bootloader again, in order to flash custom recovery.
Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?
Mcdrug said:
Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?
Click to expand...
Click to collapse
You have to follow all the steps through Step 14.
Again, the goal is to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM
Can't get true this step:
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
solution might be: Are you mounting the MTP in recovery mode ? It won't work this way.
You need to transfer them on a working OS (I mean you have to be on homescreen)
Try use an external sdcard.
I have put an external sdcard inside, i can put the files on the card
But then the files aren't located at the TWRP/BACKUP map.
What to do?
Mcdrug said:
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
What to do?
Click to expand...
Click to collapse
when you select boot to backup, you can select which storage the backup goes to .. select microSD instead of internal (read all menu in the backup section on TWRP)
then you can use a card reader to mount your microsd to PC and transfer the extracted contents of the backup zip to the same folder that you made with the boot backup and replace all files when PC ask you.
All done, back in stock rom, thank you very much!!
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
I choose in this step do not install, but he rebooted me direct into the stock rom.
Tried some things to get into the bootloader again, volume down and power, cmd with adb fastboot, but nothing really worked.
What's the reason i can't get back to bootloader, and how do i get step 11 fixed and flash stock recovery?
To go to bootloader when on OS running ... press power button and select restart. When the screen turn black .. hold volume down button .. that will take you to hboot screen, press power once will get you to fastboot/bootloader
To go to bootloader when on OS running ... you need to enable USB debugging in settings - Developer options. To enable Developer options, go to settings - about - software information - more - click build number until the developer options is enabled.
Once usb debugging is enabled, you can run command adb reboot bootloader to get to fastboot/bootloader
It works, did the last step:
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
but now can't entering recovery anymore, just showing a red trangle with an exclamation mark? And in some minutes he boots to OS.
Have to do step 1 again? Maybe go to a higher version? I want OTA to MM 6.0
You don't need to get into recovery after you installed stock recovery.
what you need to do ... boot to OS .. go to settings - about - software update - check for update, download and click install let the system do its stuff to update. After reboot, repeat the checking & install process.
And you need to do the checking & install, multiple times to update :
2.22.161.6 --> 4.19.161.2 --> 4.19.161.3 --> 6.12.161.4 --> done.
Folks
I need help to solve a problem.
I bought a HTC One M8x and decided to set up a rom custon. I study the subject before. I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error. I was exploring the tool I ended up pressing and making procedures that were not listed, but apparently did not issue before starting the installation made the backup and then wipe. I started the procedure to install, entered the install section and located the ROM and sent install. After a while appeared an error saying that the installation was not possible, I managed to recover the backup, but the phone was not the same. I realized that my internal memory is no longer visible, I can not download pictures or audios in whatsapp, another thing I noticed is that the file manager also does not provide the internal memory (directories, programs, and others). When I try to synchronize your phone with your computer to the same thing, I can see the micro SD, but can not see the internal memory. I possibly when I was digging the Recovery program just blocking the internal memory and wanted to know how do to reverse. Does anyone have any ideas.
Do you have access to bootloader? if yes. You can try to restore your phone with HTC RUU
ddfilho said:
I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error.
Click to expand...
Click to collapse
Using the (now outdated) toolkit was a mistake. Whenever modding these devices, you need to research the current methods applicable to the current state of the phone, not methods from 2 years ago (and all the toolkits have not been updated in that long or more).
The toolkit installs an obsolete version of TWRP, and that is probably why the ROM is failing to flash. It probably also wiped out your OS version on bootloader screen and getvar (not a major issue, but an inconvenience if you want to determine the firmware number).
You should update to more current version of TWRP. But you'll probably need to solve the issue of your internal storage first, which is apparently been corrupted. Go into TWRP, and try the option in Wipe to "Format Data" (button next to "Advanced"). This usually fixes the corrupt internal storage issue.
Also do fastboot getvar all, and post the results, so we can see more info about the phone, and more properly provide guidance. Delete IMEI and serial number before posting.
I have access to the bootloader but do not know run this action. Could you tell me where I can walkthrougt to do so.
Thank you for your help
Pardon
Now that saw the second message. I will perform this procedure now
Friend
Your solution worked perfectly.
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Thanks again
ddfilho said:
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
Click to expand...
Click to collapse
This isn't an option on the phone, if that is what you mean. Its a fastboot command issued from your PC, and you'd know how to issue a fastboot command if you unlocked the bootloader via HTCDev.com, instead of letting the toolkit do it for you. Which is another reason I don't like the toolkits: they shortcut the learning process, and leave you without the skills to solve basic problems, which almost inevitably happen.
You're going to need to figure out where fastboot.exe was installed during the bootloader unlock process. Once you've found that, you can then:
1) Connect phone to PC, booted into bootloader-fastboot mode
2) On PC, open a window for the folder that contains fastboot.exe
3) Hover mouse cursor over the window, and Shift+Right Mouse button, then select "Open command window here" and this will open up Command Prompt to the fastboot directory
4) In Command Prompt window, type: fastboot getvar all
5) You will see output with details about the phone, to copy the desired text, right click on the command window, select Edit>Mark, then highlight the desired text (getvar output) and press Enter. Then paste the text.
6) Be sure to delete IMEI and serial number from getvar output before posting it here
ddfilho said:
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Click to expand...
Click to collapse
Exact TWRP version depends on your current firmware, which we can determine from the getvar output above.
Once we've determined the proper TWRP version, its easily installed by putting the file in your fastboot folder, and flashing with fastboot command. Again, we see how valuable it is to know how to use fastboot. But don't try that, until we've determined the proper version from getvar output.
I managed to perform the procedure now. See the information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(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: 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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
ddfilho said:
I managed to perform the procedure now. See the information:
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main:
Click to expand...
Click to collapse
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
redpoint73 said:
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
Click to expand...
Click to collapse
Folks
Thank you for your help
I managed to update TWRP following the instructions, but when I tried to install the ROM did not succeed.
It gave an error as if he could not open the file or install, see the message:
Error opening: `/and-sec/uuuuuuuu.uuu'(I/O error) ===> Several lines with mensagem.
You know how I can be able to install any rom?
In TWRP go to WIPE then select Format data, type yes
Then go to REBOOT select recovery ... now try again to install ROM
THANKS IN ADVANCE
hi being long period user of android phone still facing many problems to get OTA update on my phone. I was excited about my phone HTC one M8 and wanted to install OTA update there was not any software update option in my phone and than i ran for internet search spent regular three days to find correct firmware get back to stock which totally different from samsung phones. I gone through all the the threads and option provided on internet tried to get back to stock. I need help of professional
who can sort out this problem. HTC PHONE IS NOW BOOTLOADER LOCKED S-OFF KITKAT INSTALLED SUPERCID software number 1.54.651.8
PLEASE GIVE LINK TO GET STOCK RECOVERY AND HOW TO INSTALL OR FLASH IT.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.05.20.0321_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***********
(bootloader) imei: ***********
(bootloader) imei2: Not Support
(bootloader) meid: **************
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
http://forum.xda-developers.com/showthread.php?t=2729173
http://forum.xda-developers.com/show....php?t=2729173
Click to expand...
Click to collapse
THANKS ckpv5 I WILL GIVE YOU WHOLE INFO. ABOUT MY PROBLEM
As i changed my MID and flashed wrong zip of HTC europe rom on HTC SPRINT which drained everything including my custom TWRP. I was totally new to HTC totally messed up everything. its been more than five days my phone had stuck at hboot screen i know you guy are genius can save my hundard of BUCKs as its new phone bought 15 days ago it was rooted.
I WAS TRYING TO INSTALL SPRINT FIRMWARE TOO BECAUSE I HAD ALREADY FLASHED THAT FIRMWARE ACCORDING TO EUROPE ROM. NOW THE PROBLEM IS THAT I AM UNABLE TO FLASH FIRMWARE DUE TO CHANGED MID (talked earlier) CANNOT UNDERSTAND WHAT TO DO.
Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.
ckpv5 said:
Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.
Click to expand...
Click to collapse
this is what now comes up when i try to flash TWRP
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot flash recovery "twrp-2.8.5.0-m8_whl.img."
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.501s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.516s
i'm brain dead nothing works SUGGEST SOMETHING
EVEN UNABLE TO UNLOCK BOOTLOADER NOW
You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.
ckpv5 said:
You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.
Click to expand...
Click to collapse
:fingers-crossed: Thanks man you are really great now these are the outcomes
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot getvar mid
mid: 0P6B70000
finished. total time: -0.000s
Now it want follow your command give me further steps. Thanks Again
Moreover, i made mistake that i also had flashed firmware file according to htc europe rom. Now which one should choose.
Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU exe that is linked above.
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
HTC USB drivers - 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.
Or you can use RUU zip
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip that you can get in Sprint thread.
Rename it to 0P6BIMG.zip and install the same way as you installed TWRP above (microSD method)
ckpv5 said:
Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
HTC USB drivers - 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.
Click to expand...
Click to collapse
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU
sorry it could be silly but which one is right one in both of it or give the link to particular one because i am afraid don't mess anything again. Thanks man
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to RUU 6.20.651.3 on post #2, #4 & #8
ckpv5 said:
What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to 6.20.651.3 on post #2, #4 & #8
Click to expand...
Click to collapse
Sorry bro i sent you by mistake i got it i will flash 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU file through HBOOT and i will post the outcome whatever there will be but you are great. You saved me. Thanks a lot bro
It says that Device halted due large image update file
What do you suggest now.
Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)
ckpv5 said:
Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)
Click to expand...
Click to collapse
There is another problem occured i flashed signed firmware now phone only shows the HTC logo and unable to restart what should do now???
Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.
ckpv5 said:
Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.
Click to expand...
Click to collapse
Thanks man we made it IT IS FINALLY WORKING you are really great Man this info will HELP SOMEONE AS WELL..
Great ..
Now I can sleep well.. it's 1.00 am here... good night
ckpv5 said:
Great ..
Now I can sleep well.. it's 1.00 am here... good night
Click to expand...
Click to collapse
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
There is also portable wifi hotspot is missed. Need help where to find it.
karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Sent from my HTC One_M8 using Tapatalk
Zile995 said:
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Click to expand...
Click to collapse
Hello mate No it is till missing and official theme and i also want change that icon but i couldn't find that option too. Are you able to give me that solution how i can do it. More there is activating device window at start up how can i remove that?
karamghumaan said:
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
Click to expand...
Click to collapse
SO you have no cell data access?
What bands does your carrier uses for 3G and LTE (what band for each of those - they are 2 different things).
karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Hotspot is locked out on most US carrier versions. If you don't see Hotspot as an available "tile" in the notification quick settings, and no Hotspot widget, than the feature has been disabled on your stock ROM.
Easiest way to enable Hotspot is with the proper custom ROM (supports Sprint version M8).
Hi guys I have an HTC ONE M8 running 4.4.4 with TWRP and Root installed and a few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual. When I did that and rebooted the phone, the phone is stuck on the HTC logo and I can only boot into bootloader mode and also into TWRP. Also TWRP is also saying I have lost root access.
What can I do to fix this problem can I restore back to 4.4.4 as a new device and re-root it and install TWRP? How do I get out of this mess? It is S-ON and Software Status is MODIFIED.
No matter how long I leave the phone it will stay on the logo until it dies or until I boot into bootloader.
Thank You Guys I Have Lost Hope Honestly.
IF ANYONE CAN HELP ME PLEASE PROVIDE THOROUGH INSTRUCTIONS! THANK YOU!
First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
TechMan123456 said:
few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual.
Click to expand...
Click to collapse
What does "and such" mean? Did you wipe anything besides cache and Dalvik?
redpoint73 said:
First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
What does "and such" mean? Did you wipe anything besides cache and Dalvik?
Click to expand...
Click to collapse
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup
xunholyx said:
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup
Click to expand...
Click to collapse
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
you can use a card reader to put the rom or the backup on external sd card
or use an OTG USB flash memory
also connect the device to pc while you are in recovery this should work by it self no need to install MTP driver
which OS you have on your pc ??
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
No OS is usually an easy fix. Download a ROM on your PC, put it onto your extSD, and flash the ROM in recovery. The reason you have no OS is because you wiped system in TWRP. If you do that, you need to flash a ROM after or you'll have no OS on a reboot.
It's best to never wipe system in TWRP as this is done by default in recovery when you flash a ROM. There will be the odd instance that it is suggested to wipe it ( I've never seen that with HTC based ROMs), but if it isn't then don't.
---------- Post added at 08:52 PM ---------- Previous post was at 08:47 PM ----------
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
Ahhh, reding it a second time I realize you mean OS is blank in your bootloader. You should also update your TWRP version
TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
Not clear which drivers you are trying to install, the HTC drivers from their website, the ones which load from the phone, built-in Windows drivers, etc.?
Try going to HTC's website, and download HTC Sync, which will also install the drivers. If you already have this installed, try uninstalling, and re-install.
Alternately, the Android MTP device drivers built-in to Windows is a generic version of drivers which can often get at least adb/fastboot working, and probably also allow you to drag/drop to internal storage in TWRP. If these drivers are the ones failing to install, it would imply there is something wrong with your Windows installation (which there isn't a lot we can help you with) rather than anything with the phone.
hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank
Arslan8997 said:
hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank
Click to expand...
Click to collapse
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
Click to expand...
Click to collapse
I also try RUU sprint version ROM but it didn't work
TWRP v2.7.0.2
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(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: XXXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Arslan8997 said:
I also try RUU sprint version ROM but it didn't work
Click to expand...
Click to collapse
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Click to expand...
Click to collapse
redpoint73 said:
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
Click to expand...
Click to collapse
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Status of phone is
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(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: XXXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Arslan8997 said:
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Click to expand...
Click to collapse
You need to flash the firmware 6.20.651.3 in order for the RUU to install (firmware and RUU are different things - so don't confuse the two). The firmware and how to flash are described here (as well as all the Sprint RUUs): https://forum.xda-developers.com/showthread.php?t=2729173
Just a heads up, if you don't know already: No need to relock the bootloader to do this (flash either firmware or RUU) since you are s-off, and no benefit in doing so. Plus, relocked bootloader gives you less options to recovery, so it is not recommended to relock it in your case.
Also, in regards to your original question (no boot after restoring TWRP backup): you never answered my question of how you picked a TWRP backup to download and restore (which I asked twice before). Now that I see you have the Sprint version M8, I will guess that you tried to restore the incorrect version backup. Sprint version uses different kernel from most other M8 versions. So if you don't restore the proper one, no boot is the expected outcome. Also, even if Sprint, it would have to be the same version you were on before (Kitkat) which is another reason it would not boot.