Develop Bugs

getting Back to stock From Custom ROM Using CWM

hi
First thanks to sumesd & ClydeB1 with out their help
i would not have been successful in this process:good::laugh:
Few people had asked me how i went back to stock via CWM so im posting the same for ur info.
I am not a techie i just read and do what i need to. This worked for me so it should also for ur. I was on 1.29 did not do any previous OTA so i was able to get the OTA via this process
I was told that if u have updated to 2.17 u might not be able to get it back if u try from 1.29
if u have 2,17 nand back up yes u can do the below.Stock recovery given in the below link but im not sure if it will work.But sr developers says yes
i had the original stock rom backed up via CWM (1.29)
so if u have it too u can do this
1. Copy the boot.img from ur CWM nand bakup
keep it on ur PC and flash it via the fastboot comand on to ur Phone
2. Flash the backed up orignal rom via CWM
3. Then flash the original stock recovery
via fast boot command or u can use the tool given below it is easier
i have used it and it worked for me:good:
4. Re lock the boot loader
again via fast boot command or the tool given below
I used this tool to re lock and flash the recovery it can also do most of the above process
(thanks to thunder07)
link : http://forum.xda-developers.com/showpost.php?p=27913286&postcount=1
For stock recovery get it from here(thanks to sumesd)
Link : http://forum.xda-developers.com/showpost.php?p=30863908&postcount=1
one more : http://forum.xda-developers.com/showthread.php?t=1928019 (thanks manachivm this is India stock)
If u want 2.17 stock rom CWM back up INDIA (thanks kryptoner)
go here : http://forum.xda-developers.com/showpost.php?p=32444876&postcount=2419
one more link for the same : http://d-h.st/aEz
Note : it is a CWM back up u need to place it inside the CWM backup folder on ur SD to flash it via CWM nand restore OK . IT is not a update ZIP
hope the above helps:good::laugh:

The title is misleading!
You are saying that you restored everything to stock from CWM, but you have flashed the stock boot.img & stock recovery through your PC.
Well, if you are using your PC, the better & faster way is to simply re-lock & flash the latest RUU for your device (that ofcourse excludes JB, which till now cannot be restored to fully stock due to the Hboot 1.23).

omar302 said:
The title is misleading!
You are saying that you restored everything to stock from CWM, but you have flashed the stock boot.img & stock recovery through your PC.
Well, if you are using your PC, the better & faster way is to simply re-lock & flash the latest RUU for your device (that ofcourse excludes JB, which till now cannot be restored to fully stock due to the Hboot 1.23).
Click to expand...
Click to collapse
hi
i did this and it worked for me and i have successfully up dated my OTA to 2.17 some guys asked me how so i have given the process for the procees u have given their are a few good tuts for the same:laugh:
this is just another way to do the same which i felt was easy if u like it u can do it :laugh:
and by doing nand restore i feel i save time ie i dont need to re install all my apps and contacts again
and just relocking is not enough u need to add stock recovery, then re lock and then flash the RUU via Pc at least that is what i have read

I am not saying it does not work, I am sure it does. but your title claims "Everything", whereas you are NOT doing "Everything" from CWM.
As for flashing through RUU, you dont need the stock recovery nor the stock boot to flash a stock RUU.

omar302 said:
I am not saying it does not work, I am sure it does. but your title claims "Everything", whereas you are NOT doing "Everything" from CWM.
As for flashing through RUU, you dont need the stock recovery nor the stock boot to flash a stock RUU.
Click to expand...
Click to collapse
hi
i was just passing on some info i know and i have changed the topic see
and i hope u are right that u dont need stock recovery to flash the RUU because as per what i read it is needed .But then im not a techie just a guy who reads and does what is said thats all

Re-Locking (without stock boot & recover) and Flashing the RUU from fastboot (or bootloader can't remeber exactly) worked for me several times. Even if I get the security warning message, the RUU still flashed.
I believe there are two issues that the RUU checks, the ROM version & Hboot version. if both are either equal or higher in the RUU, it would flash succussfully.

my problem is my
C:\fastboot getvar
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0
(bootloader) version-baseband: 1.1204.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.720.2
(bootloader) serialno: SH24DW103047
(bootloader) imei: 359188047063714
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) devpower: 40
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.813s
And i am trying to update with RUU
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_India_1.28.720.10_Radio_1.1204.103.14_release_257789_signed.exe
it still say ERROR 140

y0 said:
my problem is my
C:\fastboot getvar
...
(bootloader) version-main: 2.17.720.2
And i am trying to update with RUU
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_India_1.28.720.10_Radio_1.1204.103.14_release_257789_signed.exe
it still say ERROR 140
Click to expand...
Click to collapse
Because you need 2.17.720.2, not 1.28.720.10

[Q] HTC M8 Wifi problems on several Roms -HELP!

I was hoping someone could help me with a problem I have.
My htc M8 was rooted and insertcoin was flashed onto it however the wifi button greyed out and wouldnt turn on in order to s-off it. I tried several different roms and they all have the same problem. I am currently running skydragon v5. I have been trying to sort this phone out for a week and I am getting absolutely nowhere so any help would be appreciated. It's on ORANG001 and is s-on.
Thanks

You have old firmware. You need to have 4.19.61.2 on ORANG001 in order to have wifi on these ROM.
And you post this in wrong section.

ckpv5 said:
You have old firmware. You need to have 4.19.61.2 on ORANG001 in order to have wifi on these ROM.
And you post this in wrong section.
Click to expand...
Click to collapse
Apologies, new to the forum it's been moved now!

Yeah .. requested it to be moved to correct section.
So .. you need to restore your stock ROM and do OTA up to 4.19.61.2
What's your current firmware version .. 3.33.61.9 or 2.26.61.1 ? Or even lower ?
Check what's written on bootloader - hboot 3.16 or 3.18 .. you need 3.19

ckpv5 said:
Yeah .. requested it to be moved to correct section.
So .. you need to restore your stock ROM and do OTA up to 4.19.61.2
What's your current firmware version .. 3.33.61.9 or 2.26.61.1 ? Or even lower ?
Check what's written on bootloader - hboot 3.16 or 3.18 .. you need 3.19
Click to expand...
Click to collapse
Hboot is 3.16.0.0000
The phone is currently in the bootloader and I can't get it to turn on to check the firmware version.
Ran getvar all does this help ? thanks for the help, I was stuck for over a week.
(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-ON
(bootloader) serialno: **************
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.206s

That's a very low version ... you need to restore to stock backup 1.54.61.5
But I deleted my TWRP backup for most 1.xx.xxx.x only keep 2.x; 3x & 4x
There is someone else backup made with Philz recovery so you need to download Philz recovery - http://forum.xda-developers.com/showthread.php?t=2703223
then download the backup : https://mega.co.nz/#!WhwRmSoJ!QJxmI0gYj7t_0Hc4fMKx0XLYQ2n45S3OfrEcDRS3C-s
restore that backup with the stock recovery (included in that backup if I'm not wrong)
then do multiple OTA

ckpv5 said:
That's a very low version ... you need to restore to stock backup 1.54.61.5
But I deleted my TWRP backup for most 1.xx.xxx.x only keep 2.x; 3x & 4x
There is someone else backup made with Philz recovery so you need to download Philz recovery - http://forum.xda-developers.com/showthread.php?t=2703223
then download the backup : https://mega.co.nz/#!WhwRmSoJ!QJxmI0gYj7t_0Hc4fMKx0XLYQ2n45S3OfrEcDRS3C-s
restore that backup with the stock recovery (included in that backup if I'm not wrong)
then do multiple OTA
Click to expand...
Click to collapse
I have Philz Touch 6.26.6 clockwork mod v6.0.4.8
Will this be okay or do i need to install a different one ? sorry if these questions are stupid.

Should be ok ... good luck
I'll check your progress tomorrow or maybe someone will help you later.
Time to sleep ... good night

ckpv5 said:
Should be ok ... good luck
I'll check your progress tomorrow or maybe someone will help you later.
Time to sleep ... good night
Click to expand...
Click to collapse
Okay cheers for your help!

I was trying to adb push the firmware to my phone to then install it on Recovery but when im typing "adb devices" it says list of devices attached then it is blank. I have been trying to search for solutions but I cant seem to fix it. If you have any advice it would be much appreciated. Thanks

Has anyone got an idea?

paulmcclafferty said:
I was trying to adb push the firmware to my phone to then install it on Recovery but when im typing "adb devices" it says list of devices attached then it is blank. I have been trying to search for solutions but I cant seem to fix it. If you have any advice it would be much appreciated. Thanks
Click to expand...
Click to collapse
This is usually an issue on the computer's side (PC?). Try to re-install HTC drivers, try another USB port, or another cable. Also, if you have USB 3.0, this is known to cause issues with adb connectivity (apparently, you can disable this).
Also, you need to be booted into OS or in recovery for adb to work (does not work in bootloader) and you need to have USB debugging activated in Settings.
And when you say "firmware" I think you mean a nandroid backup, based on the instructions previously given to you? Be careful using the term "firmware" here, as most folks use that term to specifically mean the firmware.zip that contains hboot, radio etc. (but not ROM).

paulmcclafferty said:
I was trying to adb push the firmware to my phone to then install it on Recovery but when im typing "adb devices" it says list of devices attached then it is blank. I have been trying to search for solutions but I cant seem to fix it. If you have any advice it would be much appreciated. Thanks
Click to expand...
Click to collapse
Don't you have a MicroSD ? Put the extracted nandroid on MicroSD at the right location clockworkmod\backups\ is easier than doing that ADB push.

Okay finally got the nandroid backup installed. Then when i tried to install the OTA update it took me to CWM and failed. So i then relocked and tried again to update OTA and it took me to the bootloader with a ***Relocked*** and *** Security Warning*** any ideas ?

You need to re-install the stock recovery in order to OTA. Bootloader lock has nothing to do with it (will OTA with unlocked bootloader).

redpoint73 said:
You need to re-install the stock recovery in order to OTA. Bootloader lock has nothing to do with it (will OTA with unlocked bootloader).
Click to expand...
Click to collapse
I have installed the Nandroid backup mentioned above to stock i believe. Is this the correct step or is this still not stock ? it was 1.54.61.5
Thanks

paulmcclafferty said:
I have installed the Nandroid backup mentioned above to stock i believe. Is this the correct step or is this still not stock ? it was 1.54.61.5
Thanks
Click to expand...
Click to collapse
Stock ROM backup and stock recovery are two different things.
You need to fastboot flash recovery recovery.img to replace the CWM that you have now. Inside the backup zip, there is a recovery.img .. take this out and fastboot flash it.
You need to unlock bootloader to flash it.

when using the command "fastboot flash recovery recovery.img" using the recovery.img from the unzipped nandroid folder the process runs and it says okay with no errors then when i try go into recovery the red triangle and exclamation mark appear again

paulmcclafferty said:
when using the command "fastboot flash recovery recovery.img" using the recovery.img from the unzipped nandroid folder the process runs and it says okay with no errors then when i try go into recovery the red triangle and exclamation mark appear again
Click to expand...
Click to collapse
Yes that's stock recovery. Perform the ota now

Because that is stock recovery. You don't need to get into recovery.
Just reboot, check OTA, download then select install.
Let the system do the installation on its own

Phone is stuck on boot ( S-on - custom recovery - branded)

Hello everyone,
My friend has tried to get into the rooting scene and without proper knowledge he managed to get himself stuck on the boot screen.
I offered him my help, since I thought that this would be an easy fix because the phone still has access to the TWRP recovery.
What I didn't know is that the phone was branded and S-on. The CID is: VODAPE17.
ADB works in recovery mod !
To sum it up:
CID: VODAPE17
The bootloader is unlocked
S-on
Acces to custom recovery
no backup
adb works
fastboot works
What I have tried:
I tried to get the device S-off with HTC dev. But it required me to boot up the phone, so that didn't work out.
I have found a nand backup that should work with this CID on this page: http://forum.xda-developers.com/showthread.php?t=2701376&page=5
This one: 3.29.161.9 - TWRP Thanks to Petert87 (what does that number: 3.29.1619 mean?)
I unpacked the file. Send it to the internal storage and renamed it to a backup that I had made myself (otherwise TWRP wouldn't recognize it?).
After wiping I restored the backup, but to my surprise the phone still was stuck on the HTC one logo when I tried to boot it!
I tried to get as much information from the phone as possible.
This is what I got:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.19.161.2
version-misc: PVT SHIP S-ON
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: VODAPE17
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
My question
Can anyone help me to get this phone running again? I don't really know what to do anymore.
Every bit of help is appreciated very much! :good:
Thank you in advance!
Sietse

After flashing countless amounts of customs roms I still don't make any progress.
I have even tried to flash the boot.img of a custom rom separately with fastboot but that didn't work either.
Something is preventing this phone from booting, but I don't know what
Does anyone have idea's? They will be greatly appreaciated!

Download and install latest TWRP from their website, not playstore. Do full wipe including system, then format data typing yes to confirm. Download compatible ROM to extSD, mount extSD in TWRP and install from extSD. That's what I would try. Your firmware looks up to date..

flyera343 said:
Download and install latest TWRP from their website,
Click to expand...
Click to collapse
Agree, this is very important. Some older versions of TWRP won't work with the current hboot. You can drive yourself crazy flashing a hundred ROMs, and it still won't work.

Same issue here. Latest firmware. S-ON. Every custom ROM causes a boot loop. Luckily I had a nandroid of stock ROM (5.0.1) so I can always go back to stock.

petrjanda said:
Same issue here. Latest firmware. S-ON. Every custom ROM causes a boot loop. Luckily I had a nandroid of stock ROM (5.0.1) so I can always go back to stock.
Click to expand...
Click to collapse
As already stated by myself and another, make sure TWRP is up to date (2.8.7). Outdated TWRP is the most common cause for many ROMs bootlooping.

need stock RUU for htc desire 816 dual sim india

hi all, my phone is stuck on boot mode for a couple of weeks and I am still not able to find correct stock rom. please help me find one so that I can flash it via fastboot. here are the getvar all details from fastboot:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.31.50.1103
version-cpld: None
version-microp: None
version-main: 1.61.720.1
version-misc: PVT SHIP S-ON
serialno: FA484MZ00452
product: a5_dwg
platform: hTCBmsm8226
modelid: 0P9C51000
cidnum: HTC__038
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: be7179e5
hbootpreupdate: 11
gencheckpt: 0

HTC desire 816 A5_dwg
Kit Kat RUU:
http://www.mediafire.com/?jimitej7orp4qcr
Lollipop RUU:
http://www.4shared.com/zip/9nQZohiEba/0P9CIMG_A5_DWG_L50_DESIRE_SENS.html

***RELOCKED***
A5_DWG PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.31.50.1103
OpenDSP-v28.2.2.00546.0331
OS-1.61.720.1
eMMC-boot 1536MB
Nov 4 2014,20:04:44.23583
I already tried the kitkat one u r posting. it said something remote:12 signature failed

Download lollipop RUU, should work with your device.
Have you tried flashing with sd-card?
When did this bootloop first appear?

nukaru said:
Download lollipop RUU, should work with your device.
Have you tried flashing with sd-card?
When did this bootloop first appear?
Click to expand...
Click to collapse
sorry for late response, I tried the lollipop RUU too
1. with fastboot, it says :02 remote fie is too large
2. via sd card...finding package..opening package....unable to map file
And here is the story of bootloop. my phone was working fine till I received the official lollipop update, which failed repeatedly during installation. I checked the recovery log and found some error in system/bin/flash_camera and decided to flash just recovery image. I flashed recovery and boot image from the ota update I received...but got stuck. then I started trying all these RUU stuff but still no clue. thanks for listening

Ah, okay.
Can you select recovery in hboot and does it start up normally? Have you tried a Kit Kat nandroid backup with twrp?
Ps: you need to delete your imeis in the first post..

nukaru said:
Ah, okay.
Can you select recovery in hboot and does it start up normally? Have you tried a Kit Kat nandroid backup with twrp?
Ps: you need to delete your imeis in the first post..
Click to expand...
Click to collapse
yes once stuck on white screen with htc, I need to hold vol up+ power to turn it off and before it reboots automatically I open hboot by vol down+ power. from there I can continue in recovery mode and fastboot etc. no I haven't tried nandroid backup with twrp. I want to get stock rom so that I am able to get updates in future. plus I read twrp backup roms are havng problems like wifi and all.

That sounds like your bootsector is damaged, so usb debugging is disabled.
Did you back up your old recovery.img? The kit kat one before the update?
The easiest way, if you're able to flash a custom recovery, is a clean nandroid backup without root using twrp and once your device is booting again, start from scratch.
Enable usb debugging, unlock bootloader, flash stock recovery, relock bootloader and flash RUU.

nukaru said:
That sounds like your bootsector is damaged, so usb debugging is disabled.
Did you back up your old recovery.img? The kit kat one before the update?
The easiest way, if you're able to flash a custom recovery, is a clean nandroid backup without root using twrp and once your device is booting again, start from scratch.
Enable usb debugging, unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
Click to expand...
Click to collapse
no I havent backed up the KitKat factory image
I flashed the latest twrp recovery and booted to it. also I placed a twrp stock backup in sd card ( from one of the threads on this forum) . but when I proceed to backup from sd card, it doesn't appear there, however in the install option I can see the contents I placed..but again I m not getting an option to install it from there. guide me what to do next.

shubhamjswl said:
no I havent backed up the KitKat factory image
I flashed the latest twrp recovery and booted to it. also I placed a twrp stock backup in sd card ( from one of the threads on this forum) . but when I proceed to backup from sd card, it doesn't appear there, however in the install option I can see the contents I placed..but again I m not getting an option to install it from there. guide me what to do next.
Click to expand...
Click to collapse
guess wat!! my phone started and I am now getting ota also. thanks

That's great ? Remember to make your own backup and store it somewhere safe ?

Please provide me detailed steps on how to reinstall official stock rom on htc desire 816 dual sim indian version and also rom file

hi all, my phone is stuck on boot mode for weeks and i can't find a usable stock rom for my phone here are the details from fastboot
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.31.50.1215
version-cpld: None
version-microp: None
version-main:1.27.710.1
version-misc: PVT SHIP S-ON
serialno: FA47RMZ00345
imei: 352795062179097
imei2: 352795062179105
meid: A1000037D93FA6
product: a5_dwg
platform: hTCBmsm8226
modelid: 0P9C51000
cidnum: HTC__621
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: fba3c246
hbootpreupdate: 11
gencheckpt: 0

Htc one m8 bricked?!?! Stuck on boot screen (htc logo)!

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.