So, long story short, a kid who got himself a HTC one M8 thought he'd be smart and try to install the Google Play Edition of the Lollipop Update. Turns out he managed to brick the device, sort of. He came to me for help, and I was able to find out what he did so far.
1. He unlocked the bootloader using fastboot.
2. Installed CWM PhilZ
3. Downloaded the Google Play Edition of the Lollipop Update.
4. Failed to take a backup of his current ROM.
5. Installation failed of the new ROM because S was on.
6. He has said (can't make out if this is true or not) that he has reverted to stock recovery, so as to *help* me with fixing it. The screen that I am able to get into after I press the volume button and power combinations says the following.
***TAMPERED***
***UNLOCKED***
MB_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.1921331147A1.16G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 12 2014, 23:27:55.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
*****************************************************************************
I've got my ADT and the necessary tools to proceed. I just need to be pointed in the right direction with this. Selecting Recovery takes me to a screen with a Hazard "!" sign screen, after which I have to reboot the phone. Factory Reset also doesn't work with it showing the update/download arrow after which it comes back to the HTC logo powered by Android, as it always does. When connected to the computer, the computer reads it as a CD drive. Note that I don't have the drivers installed for the phone on this computer seeing as this is not my phone. I've got the stock ROM from the HTC dev site ready. Would appreciate the help. Thanks!
I'm thinking you should download latest ruu image from xda forums for the M8, get to fastboot usb, and flash that to get back to usable. Then s-off with firewater / whatever s-off tool is currently out there. Or, I could be misunderstanding your problem.
KinTharEl said:
So, long story short, a kid who got himself a HTC one M8 thought he'd be smart and try to install the Google Play Edition of the Lollipop Update. Turns out he managed to brick the device, sort of. He came to me for help, and I was able to find out what he did so far.
1. He unlocked the bootloader using fastboot.
2. Installed CWM PhilZ
3. Downloaded the Google Play Edition of the Lollipop Update.
4. Failed to take a backup of his current ROM.
5. Installation failed of the new ROM because S was on.
6. He has said (can't make out if this is true or not) that he has reverted to stock recovery, so as to *help* me with fixing it. The screen that I am able to get into after I press the volume button and power combinations says the following.
***TAMPERED***
***UNLOCKED***
MB_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.1921331147A1.16G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 12 2014, 23:27:55.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
*****************************************************************************
I've got my ADT and the necessary tools to proceed. I just need to be pointed in the right direction with this. Selecting Recovery takes me to a screen with a Hazard "!" sign screen, after which I have to reboot the phone. Factory Reset also doesn't work with it showing the update/download arrow after which it comes back to the HTC logo powered by Android, as it always does. When connected to the computer, the computer reads it as a CD drive. Note that I don't have the drivers installed for the phone on this computer seeing as this is not my phone. I've got the stock ROM from the HTC dev site ready. Would appreciate the help. Thanks!
Click to expand...
Click to collapse
First get HTC Sync on your PC, install the drivers, then uninstall HTC Sync.
Download TWRP from their site. I recommend 2.0.8.3, it has less issues than the newest 2.1.0.0.
Rename it to recovery.img and put it into the fastboot folder on your PC.
Enter fastboot on the phone (while the phone is off, hold power + vol. down)
Plug it in to your PC and start ADB and enter this command:
fastboot flash recovery recovery.img
Make sure that Superuser is installed, (it should be already if he was flashing custom ROMs)
After that you can flash a ROM using ADB, or by putting the ROM onto ext SD and flashing using TWRP.
Update. I was able to get TWRP installed and flash SuperSU. Still have S off and I have no idea how to get that done. I tried using the toolkit by Squabbi and unfortunately wasn't able to get the S off. Any ideas?
KinTharEl said:
Update. I was able to get TWRP installed and flash SuperSU. Still have S off and I have no idea how to get that done. I tried using the toolkit by Squabbi and unfortunately wasn't able to get the S off. Any ideas?
Click to expand...
Click to collapse
You mean S-ON? You could try firewater but that's a shoot and miss in which case it'll have to be Sunshine S-OFF(Only alternative) and that costs $25.
Back to troubleshooting:
Boot into recovery mode and sideload a ROM from the PC. You can also do an adb push ROM.zip /storage/ext_sd/ or if you have a SD Card reader on PC, remove the SD card, put it in PC and manually copy/move a ROM to the SD Card.
You don't need S-OFF to flash custom Recoveries. You'll need it in order to do a full conversion to Google Play Edition though, as a result of partition sizes changing. ROMs on the other hand is fine with S-ON.
Of course if you're going to flash custom ROMs make sure it's for the correct firmware that you're currently using. You're device still uses 2.xx.xxx.x firmware so don't download a 3.xx.xxx.x custom ROM for it. This is the case with Sense based ROMs, not sure about AOSP(Apparently it's not an issue with it). Outdated firmware will have the radio not work properly, which means, possibly, no bluetooth, gps, wifi, data.
Sorry. S-ON, that's what I meant. Yep, as you said, I was able to flash a custom recovery just fine with the S-ON. Was also able to flash SuperSU for it. After this, I was able to access the internal memory of the phone. It showed only one folder on my PC, the TWRP folder. But in the recovery, I'm able to see the root directories, which I can't on the PC. Tried flashing the stock ROM from the HTC dev site by pasting it into the phone, which sadly failed. I'll check again for the 2.xx ROMs. Maybe that's the miss I did.
KinTharEl said:
Sorry. S-ON, that's what I meant. Yep, as you said, I was able to flash a custom recovery just fine with the S-ON. Was also able to flash SuperSU for it. After this, I was able to access the internal memory of the phone. It showed only one folder on my PC, the TWRP folder. But in the recovery, I'm able to see the root directories, which I can't on the PC. Tried flashing the stock ROM from the HTC dev site by pasting it into the phone, which sadly failed. I'll check again for the 2.xx ROMs. Maybe that's the miss I did.
Click to expand...
Click to collapse
Don't bother with HTCDev site, those are kernel source codes and not backups.
COLLECTION of Stock backup's <<There's the nandroid backups for plenty of devices just look for the right one in post 1. Also in post 2 the author showed how to do the restore, make sure it's unpacked and placed in the correct path directory.
Update so far.
S-On
TWRP flashed.
Tried all the methods that you guys have mentioned.
Nandroid backup is failing.
When I use an OTG Flash drive to flash SuperSU, it succeeds, but when I hit the option to reboot, TWRP says that SuperSU isn't installed on the device and gives me an option to install it, which fails.
Tried a ROM from CM, which also failed.
Tried a sideload with adb, which also failed.
Haven't been able to use firewater to turn S-Off, where the push command just hangs.
Therefore, I am stumped at the moment. I've been thinking of using RUU to restore the phone to stock, but I haven't been able to find anything worthwhile. Is this a valid idea that I can use? Anyone has any links to this that I can use? Help would be appreciated. Thanks.
In looking for a solution to your problem, everything I have found so far requires S-OFF. I myself used the weaksauce/firewater method to do mine, did that not work for you? And if not, I have to ask if you followed the directions verbatim?
There is also the sunshine method - have you tried that method to S-OFF the phone?
This is gonna require someone to pay 25 bucks, but 1) it is well worth it, at least at this point in your efforts, 2) you don't have to pay until the S-OFF is successful, and 3) your friend should be footing that bill anyway.
Once you've gotten S-OFF achieved, you are one step - prolly the biggest step - closer to getting this thing done.
Look at it this way - after all of your troubles and frustration, wouldn't $25 be small beans to pay for a working phone?
sigshane said:
In looking for a solution to your problem, everything I have found so far requires S-OFF. I myself used the weaksauce/firewater method to do mine, did that not work for you? And if not, I have to ask if you followed the directions verbatim?
There is also the sunshine method - have you tried that method to S-OFF the phone?
This is gonna require someone to pay 25 bucks, but 1) it is well worth it, at least at this point in your efforts, 2) you don't have to pay until the S-OFF is successful, and 3) your friend should be footing that bill anyway.
Once you've gotten S-OFF achieved, you are one step - prolly the biggest step - closer to getting this thing done.
Look at it this way - after all of your troubles and frustration, wouldn't $25 be small beans to pay for a working phone?
Click to expand...
Click to collapse
S off can only be done with a working phone, eg stock sense rom, S-off is not your problem, installing a rom is, get something like ADHD rom, or the correct stock rom for your CID and then flash that. Job done working phone, then s-off if you wish but its not a requirement, but nice to have and well worth $25
Yeah. I've been searching and came to the same result, that I need the S-off. But all the methods that I have seen require that the phone needs to have a working ROM to turn S off. I'd have been able to use weaksauce/firewater for it. I saw a video of a bricked M8, and he seemed to restore it back to total stock using RUU. I'm currently downloading the RUU for the Google Play Edition, seeing as I can't find the RUU for the Sense UI WWE. In the same video, he has S-ON, from what I saw in the bootloader. Wondering if this method could possibly work. Any ideas? Here's the link for that video. The phone is a Sprint M8, but the same logic should apply for the WWE, if I'm not mistaken. Link to Video
The problem with asking the friend (he's a kid friend of my brother), is that he can't foot the bill.
KinTharEl said:
Yeah. I've been searching and came to the same result, that I need the S-off. But all the methods that I have seen require that the phone needs to have a working ROM to turn S off. I'd have been able to use weaksauce/firewater for it. I saw a video of a bricked M8, and he seemed to restore it back to total stock using RUU. I'm currently downloading the RUU for the Google Play Edition, seeing as I can't find the RUU for the Sense UI WWE. In the same video, he has S-ON, from what I saw in the bootloader. Wondering if this method could possibly work. Any ideas? Here's the link for that video. The phone is a Sprint M8, but the same logic should apply for the WWE, if I'm not mistaken. Link to Video
Click to expand...
Click to collapse
Not going to work. In the video, he is flashing the RUU which corresponds to his phone's CID.
You need to have the GPE CID to use the GPE RUU. Otherwise it will fail CID check and fail to install. And you can't change CID with s-on.
And unfortunately, there are no WWE RUUs.
I would try fastboot erase cache and install TWRP again. Then flash a ROM corresponding to your firmware (Sense 2.x). ROMs simply failing to flash is often just a matter of erasing cache and re-installing recovery.
redpoint73 said:
Not going to work. In the video, he is flashing the RUU which corresponds to his phone's CID.
You need to have the GPE CID to use the GPE RUU. Otherwise it will fail CID check and fail to install. And you can't change CID with s-on.
And unfortunately, there are no WWE RUUs.
I would try fastboot erase cache and install TWRP again. Then flash a ROM corresponding to your firmware (Sense 2.x). ROMs simply failing to flash is often just a matter of erasing cache and re-installing recovery.
Click to expand...
Click to collapse
I see. Thanks for the clarification. I didn't try flashing it yet seeing as I wanted to know what I was getting into before I actually did anything. Just for the sake of giving information, the RUU I downloaded is 2.12.1700. Version of Android is 4.4.4. Guessing it probably won't work, but I'll reflash the recovery as you had suggested. I'll try Android Revolution 22.1 for this, hopefully it works. I'll keep you guys posted.
I don't see any info of your device except the hboot version.
With that hboot version 3.18.0.0000 all the latest custom ROM won't properly work on your device.
Why don't you give more detail - run command fastboot getvar all and post here the result (delete the serialno. and imei no.)
From there we can see whether any stock backup for you. Most important now is to have a fully working phone .. then you can start any other thing like S-Off and flashing custom ROM
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTXXXXXXXXXX
(bootloader) imei: 3XXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Update: I've checked through the logs that TWRP shows, and I've found that when trying to sideload, or flash SuperSU(Even when it says successful), cache won't mount. I tried manually mounting it through the option in TWRP, but it won't select the cache at all. I also can't copy anything onto the phone memory. My option to try anything just with the phone so far has been to use an OTG USB Drive and mount that.
KinTharEl said:
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-main:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
1. Empty version-main : The TWRP that you have is a very old version.
Use TWRP 2.8.1.0 link in my signature.
2. HTC__038 and hboot 3.18.0.0000 - your correct software/ROM version no. is 2.10.720.1
There's a nandroid backup for this version here : http://forum.xda-developers.com/showthread.php?t=2701376
So try TWRP 2.8.1.0. Try also to enable MTP and see whether the sdcard/internal storage mountable to your PC.
Download the 2.10.720.1 nandroid backup then use the OTG to restore. You can make a backup of boot and select USB as the storage for the backup, you'll see the folder structure in your OTG drive. There is where you need to transfer the nandroid backup (after you extract it on PC)
Note :
1.If this is successful then you can try to S-Off with Sunshine but it is a hit or miss for your device version ... most likely won't work
2. You can follow the right procedure to do OTA update to 3.35.720.1 then you can flash any of the latest custom Sense based ROM and the lollipop ROM too.
3. Just be on stock then wait for OTA for the official lollipop like most of us here.
KinTharEl said:
Just for the sake of giving information, the RUU I downloaded is 2.12.1700. Version of Android is 4.4.4. Guessing it probably won't work
Click to expand...
Click to collapse
If its a GPE RUU, and you don't have the GPE CID (or SuperCID), it won't work. I already said that, so I don't know why you are still "guessing" anything.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
KinTharEl said:
Update: I've checked through the logs that TWRP shows, and I've found that when trying to sideload, or flash SuperSU(Even when it says successful), cache won't mount. I tried manually mounting it through the option in TWRP, but it won't select the cache at all. I also can't copy anything onto the phone memory. My option to try anything just with the phone so far has been to use an OTG USB Drive and mount that.
Click to expand...
Click to collapse
No version number means obsolete TWRP (as ckpv5 mentioned). Flashing a more current TWRP will fix this, and will probably also fix the flashing issues you had with various ROMs, and might fix the mount cache issue.
redpoint73 said:
If its a GPE RUU, and you don't have the GPE CID (or SuperCID), it won't work. I already said that, so I don't know why you are still "guessing" anything.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
No version number means obsolete TWRP (as ckpv5 mentioned). Flashing a more current TWRP will fix this, and will probably also fix the flashing issues you had with various ROMs, and might fix the mount cache issue.
Click to expand...
Click to collapse
Got it. I'll try it out as soon as I'm done with work. I was out of town the past few days, so I wasn't really able to reply. Thanks for the advice though. I'll definitely look into it.
Related
Hey Guys
My Story started from 6 days ago when i wanted to change my battery , the device now is keep restarting on White screen ( HTC EVO 4G ) and hangs whenever i press the recovery mode in bootloder menu .
I Almost tried everything and only successfully unlocked the boot loader finally using --->([HowTo] Unlock Bootloader And Root 2.3.5 HBOOT 2.18 ) "http://forum.xda-developers.com/showthread.php?t=1771755 but no chance to S-OFF the device and replace the whole ROM "
i can't root and downgrade the phone because all "bootloader: 2.18.0001 " methods need either active debugging mode or recovery menu which is not accessible !
i have access only through the fastboot - Hboot USB or SdCard .
I have tried almost all version of RUUs and it failed , says " bootloder version error " or " the main version is older "
PC36IMG Downgrade to the 4.67.651.3 which is last available version from the sd card also failed says " the main version is older "
here is the Fastboot info
INFOversion: 0.5
INFOversion-bootloader: 2.18.0001
INFOversion-baseband: 2.15.00.01.15
INFOversion-cpld: None
INFOversion-microp: 041f
INFOversion-main: 5.07.651.6
INFOserialno: ******
INFOimei: *********
INFOproduct: supersonic
INFOplatform: HBOOT-8x50
INFOmodelid: PC3610000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 3981mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 4b46e889
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
by the way i figure it out that i may be able to trick the htc and change the txt file called android-info.txt inside the PC36IMG for the " Main version is older " ERROR but Unfortunately i have no permission to edit or modify my stock ruu Rom "PC36IMG " that i extracted from last available RUU version for evo4g "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio _2.1 5.00.12.19_NV_2.33_release_234563_signed" .
Any Idea Please ?
:crying::crying::crying:
You need to install a custom recovery, which can be done from the bootloader. Search for Smelkusmod recovery here and follow the instructions on how to install it. Afterwards you can install a custom ROM
Edit: Here is the link for Smelkusmod recovery
http://forum.xda-developers.com/showthread.php?t=1661543
Once installed, place whatever ROM you want on the root of your SD card. Then you can enter recovery from the bootloader screen and flash the ROM.
I also suggest reading Hipkat's guide which can be found in the link below.
http://forum.xda-developers.com/showthread.php?t=1386911
Sent from my EVO using xda premium
FinZ28 said:
Two things, either you have a bad partition or your recovery is gone. Easiest thing to do would be to load a custom recovery onto the root of your SD card and make sure the file is named PC36IMG.zip (make sure you don't have an extra .zip extension or it won't work). Make sure the phone is powered off, then hold down the power down & volume buttons until the bootloader opens up. Hopefully the recovery will load and you'll be prompted to update. Just follow the on-screen instructions. Also, make sure you don't have any other PC36IMG's on your SD card.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
many tanks for reply xx . . .the only thing i remember aside the changing the battery was that 1 day before this happen, i removed my sd card to recover some accidentally deleted picture using RecoverMyFiles software from my computer . . . i also tried loading a custom recovery and yes i certainly ensured that the file name is PC36IMG and formatted my SD card before transferring the file . . . i also tried different SD cards ex: 2gb - 4gb - 8g etc ! All those steps you just mentioned is carefully done ! and the result is that the device skip the update from the sd card says : no or wrong image !!
aside that i have upgraded my recovery to" recovery-clockwork-5.0.2.2-supersonic " and "recovery-RA-supersonic-v2.3 " and many other available recoveries through the fastboot since my bootloader is unlocked !
but the thing is nothing is loading after all those updates !!
the only thing got my attention was that when i update those custom recoveries the device would hangs after choosing recovery from the bootloader but if i use the 5.07.651.6 version original recovery the device would keep restarting !!
FinZ28 said:
You need to install a custom recovery, which can be done from the bootloader. Search for Smelkusmod recovery here and follow the instructions on how to install it. Afterwards you can install a custom ROM
Edit: Here is the link for Smelkusmod recovery
http://forum.xda-developers.com/showthread.php?t=1661543
Once installed, place whatever ROM you want on the root of your SD card. Then you can enter recovery from the bootloader screen and flash the ROM.
I also suggest reading Hipkat's guide which can be found in the link below.
http://forum.xda-developers.com/showthread.php?t=1386911
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I just tried the Smelkusmod recovery one more time again from the Sdcard and it load the PC36IMG but hangs on " Parsing...[PC36IMG.zip] "
i was able to loaded it successfully through the fastboot method and the device hangs after i press the recovery from the boot loader menu as i expected
You need to download the .img file, not the PC36IMG.zip
Once you get the .img file, do the following (connected to PC in fastboot mode)
Code:
fastboot flash recovery <recovery_name.img>
The recovery has to be in the same directory as fastboot though
CNexus said:
You need to download the .img file, not the PC36IMG.zip
Once you get the .img file, do the following (connected to PC in fastboot mode)
Code:
fastboot flash recovery <recovery_name.img>
The recovery has to be in the same directory as fastboot though
Click to expand...
Click to collapse
Yep , i've tried " recovery-clockwork-5.0.2.2-supersonic " "recovery-RA-supersonic-v2.3 ""_ra-supersonic-4.2-smelkus-mason " and many more custom recoveries too from the fastboot command ---> ( fastboot flash recovery example.img ) . . . but whatever except the stock recovery image would result to hang the device on recovery mode . . . also it will boot loop on its own stock recovery !
Same Problem!
kimiyaiy said:
Yep , i've tried " recovery-clockwork-5.0.2.2-supersonic " "recovery-RA-supersonic-v2.3 ""_ra-supersonic-4.2-smelkus-mason " and many more custom recoveries too from the fastboot command ---> ( fastboot flash recovery example.img ) . . . but whatever except the stock recovery image would result to hang the device on recovery mode . . . also it will boot loop on its own stock recovery !
Click to expand...
Click to collapse
I purchased an HTC Evo 4G from Ebay and the hardware is perfect. My problem is exact same. Found out this thing has the 5.07 update and there is no RUU to restore it and can't go backwards with S-ON!!! Can't get S-OFF without booting as this thing won't go into recovery or boot at all. I did however **Unlocked** the bootloader and that is as far as I get. I even re-locked it to try all the RUUs! I develop roms for this device so I know what I am doing! Keep getting replies to flash custom recovery which I already tried all of them and unfortunately it will just bootloop instead of recovery. Even tried 'fastboot boot (recovery name) and fastboot flash recovery (revovery name)....Need someone to get into a RUU and modify it to by-pass the firmware version check if possible! If I can get this to boot into any rom, then I can fix this!!! Come on devs, if we can port-in beats, bravia, and all other device ports, we can solve this!
You need to relock and apply the signed firmware zip from the latest OTA. If that's the software version you were running, it *should* get you booting again.
Here's that file, if you can't find it elsewhere: http://d-h.st/3yF
Nothing working...
Captain_Throwback said:
Here's that file, if you can't find it elsewhere: http://d-h.st/3yF
Click to expand...
Click to collapse
Cool! Thank you for your input. But I put this thing aside in my computer store for awhile... I will try this zip today.. I did re-lock the bootloader before I posted earlier though and already tried re-installing the latest last known RUU but same issue... In fact, I tried all RUU available!! Also, if I can only get into recovery I can fix this thing. Hope this zip helps... Question, how do I apply this zip file if I cannot get into recovery in the first place? I'm quite sure the seller of this Evo did the latest OTA update before it crashed in middle of it and got this reboot loop in the first place. Is there a way to slipstream the extracted images of this zip into the latest RUU in the appdata hidden file while it is running on windows? lol - sorry for all this but this issue is crazy!!! NOTE: Don't get the last security OTA update for this thing!!! It's a SECURITY UPDATE alright.. LOL!
rgsgroup2005 said:
Cool! Thank you for your input. But I put this thing aside in my computer store for awhile... I will try this zip today.. I did re-lock the bootloader before I posted earlier though and already tried re-installing the latest last known RUU but same issue... In fact, I tried all RUU available!! Also, if I can only get into recovery I can fix this thing. Hope this zip helps... Question, how do I apply this zip file if I cannot get into recovery in the first place? I'm quite sure the seller of this Evo did the latest OTA update before it crashed in middle of it and got this reboot loop in the first place. Is there a way to slipstream the extracted images of this zip into the latest RUU in the appdata hidden file while it is running on windows? lol - sorry for all this but this issue is crazy!!! NOTE: Don't get the last security OTA update for this thing!!! It's a SECURITY UPDATE alright.. LOL!
Click to expand...
Click to collapse
You flash the zip through HBOOT, not recovery. Rename to PC36IMG.zip (exactly), place on sd card in no folder, and choose yes to apply update once the bootloader reads it. Again, make sure you relock first, and then hopefully the device will boot. If it doesn't, it may be normalized to the point that you can unlock and flash a custom recovery and it actually stick.
Issue continues
Captain_Throwback said:
You flash the zip through HBOOT, not recovery. Rename to PC36IMG.zip (exactly), place on sd card in no folder, and choose yes to apply update once the bootloader reads it. Again, make sure you relock first, and then hopefully the device will boot. If it doesn't, it may be normalized to the point that you can unlock and flash a custom recovery and it actually stick.
Click to expand...
Click to collapse
I have not given up! This file worked to fix another Evo but not this one... It says 'wrong image'. For what ever its worth, you may be able to see my issue by looking below. Thanks!
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
rgsgroup2005 said:
I have not given up! This file worked to fix another Evo but not this one... It says 'wrong image'. For what ever its worth, you may be able to see my issue by looking below. Thanks!
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
Click to expand...
Click to collapse
Try relocking and flash the signed firmware zip.
Attempted to no avail
Captain_Throwback said:
Try relocking and flash the signed firmware zip.
Click to expand...
Click to collapse
I tried just this, relocked and renamed, after a few seconds in Hboot, it gave several lines of 'no image', then a final 'no image or wrong image', went back to normal Hboot.
More info on my problem here.
I'm kinda have similar issue... I pulled my old Evo from box it has a-off ... When I booted up it went to home screen then just shut off by it self.. then kept bootloops .. I then tried to get to recovery it boots to HTC logo and bootloops too... I tried ruu it will still bootloops .. the reason y my phone died was because battery inside phone was bulky that's y it started.. got new battery still same problem... I'm thinking maybe ramdisk got messed up.. I can go to bootloader but that is it... What can it be? I mean if there is no solution I have another Evo I never rooted and still works...and also have Evo 4g lte. My back up phones just in case if something breaks
Sent from my 831C using XDA Premium 4 mobile app
If it boot loops after you tried a RUU, then you have bigger problems and probably need to swap to one of your backup phones.
Sent from my HTC device
Waiving the flag...
Magnum_Enforcer said:
If it boot loops after you tried a RUU, then you have bigger problems and probably need to swap to one of your backup phones.
Sent from my HTC device
Click to expand...
Click to collapse
Screw it... I'm going to order a new motherboard on Ebay with clean ESN for 42.00 lol. I give up!
Possibly Basic questions here but I'm trying to sort out the mess I made of it last time. And looking at other threads I don't think it will be as simple as i first thought, here are what I think are the relevant factors.
I have TWRP installed
as far as I can tell no operating system is running (when I try and boot normally is says startup wizard has failed and nothing else happens)
It is currently relocked but I can easily swap between the two
I've been using the all in one 2014 m8 programme
It is on 3 (network) in the UK
S-ON at the moment and I can't figure out how to change it or if i need to
So I think all i need is to flash the right RUU onto my phone and update it from there? but A) I can't figure out how to know which RUU I need and B) other threads it's starting to look like i need to install the stock recovery too? how do I do that?
Also is it a problem that I cant access settings or anyhting through the phone so don't seem to be able to turn debugging on :/
Any help would be much appreciated.
You do not need stock recovery to RUU (only needed for OTA). But you do need a LOCKED or RELOCKED bootloader (since you are s-on), it needs to be for your CID, and RUU has to be equal or greater firmware version than what is on the phone (no "downgrading" unless you are s-off).
CID is usually determined using adb, but you said that you can't turn debugging on. So possibly you can look for the CID online, or somewhere here who knows can chime in.
Redijedeye said:
Possibly Basic questions here but I'm trying to sort out the mess I made of it last time. And looking at other threads I don't think it will be as simple as i first thought, here are what I think are the relevant factors.
I have TWRP installed
as far as I can tell no operating system is running (when I try and boot normally is says startup wizard has failed and nothing else happens)
It is currently relocked but I can easily swap between the two
I've been using the all in one 2014 m8 programme
It is on 3 (network) in the UK
S-ON at the moment and I can't figure out how to change it or if i need to
So I think all i need is to flash the right RUU onto my phone and update it from there? but A) I can't figure out how to know which RUU I need and B) other threads it's starting to look like i need to install the stock recovery too? how do I do that?
Also is it a problem that I cant access settings or anyhting through the phone so don't seem to be able to turn debugging on :/
Any help would be much appreciated.
Click to expand...
Click to collapse
If you're on Three UK I'm going to guess your CID will be H3G__001 and, if so, there is no RUU available. You'd have to use a backup and restore that. The other option you have is to S-OFF the phone and then 'debrand' the phone so it becomes the unbranded, generic M8 sold in the UK
EddyOS said:
If you're on Three UK I'm going to guess your CID will be H3G__001 and, if so, there is no RUU available. You'd have to use a backup and restore that. The other option you have is to S-OFF the phone and then 'debrand' the phone so it becomes the unbranded, generic M8 sold in the UK
Click to expand...
Click to collapse
OK thanks, so none of the backups I can find are any good. all the guides for turning S-Off require downloading something onto the phone and running it but as i cant get past the setup wizard I can't do any of that, is it possible to S-Off through USB? I seem to be able to do things that should require debugging on even though i can't get to the settings.
Ooookay, so what is the disadvantage of me restoring to one of the nandroid backups in the OP,?
CID H3G___001
1.54.771.5 - Philz touch Thanks to E
1.12.771.17 - TWRP Thanks to Timnyce19
I realise it wouldn't give me back a full stock android but it'd give me a working phone with which more is possible right?
sorry for all the questions, I nearly get it, just made a wrong turn somewhere
Redijedeye said:
Ooookay, so what is the disadvantage of me restoring to one of the nandroid backups in the OP,?
CID H3G___001
1.54.771.5 - Philz touch Thanks to E
1.12.771.17 - TWRP Thanks to Timnyce19
I realise it wouldn't give me back a full stock android but it'd give me a working phone with which more is possible right?
sorry for all the questions, I nearly get it, just made a wrong turn somewhere
Click to expand...
Click to collapse
Post your fastboot getvar all result minus serial no. & imei no.
Those backup are good when your hboot is 3.16.0000 and may work if it is hboot 3.18.0000 but not when it is 3.19.0000
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.21331147A1.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dcdaa6e0
hbootpreupdate: 11
gencheckpt: 0
Bummer, I thought I'd taken backups but doesn't look like it. At the moment I can't even get it running to run firewater and S-Off it so kinda stumped
Redijedeye said:
Bummer, I thought I'd taken backups but doesn't look like it. At the moment I can't even get it running to run firewater and S-Off it so kinda stumped
Click to expand...
Click to collapse
Firewater is no more in service. Only paid service SunShine is available for S-Off.
Here is TWRP backup for your device : https://mega.co.nz/#!OsVkjYKT!_qmR7kgq5tTX1HrmwzMbS7jE94jp5AKobIF5NQJhmXg
Restore 3.32.771.10 with TWRP
Then install the stock recovery 3.32.771.10 : http://sourceforge.net/projects/htconem8/files/Recovery/3.32.771.10_recovery.img/download
Then do OTA checking and update to the latest 4.20.771.2
Thanks alot for the help man, just trying it now, I'll get back if theres problems.
ckpv5 said:
Here is TWRP backup for your device : https://mega.co.nz/#!OsVkjYKT!_qmR7kgq5tTX1HrmwzMbS7jE94jp5AKobIF5NQJhmXg
Restore 3.32.771.10 with TWRP
Click to expand...
Click to collapse
Put the files on my SD card, TWRP won't give me the option to restore that file :/ do I need to unzip or something simple like that?
Redijedeye said:
Put the files on my SD card, TWRP won't give me the option to restore that file :/ do I need to unzip or something simple like that?
Click to expand...
Click to collapse
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 3.32.771.10 from the link that I gave earlier
3. Download stock 3.32.771.10 recovery from the link that I gave earlier
4. Extract the downloaded 3.32.771.10_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 3.32.771.10 folder (not 3.32.771.10_ckpv5 folder) and its content to the backup path on your device
the path will look like this : TWRP/BACKUPS/SerialNo./3.32.771.10
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 3.32.771.10_recovery.img
12. reboot - check for OTA, download, install
13. your device now updated to 4.20.771.2
14. done
If you want to install TWRP again, make sure you install TWRP 2.8.4.0 or 2.8.5.0 or 2.8.6.0 or higher after updated to 4.20.771.2
Good luck ... I'm way pass my bed time ... good night
Thanks man, sorted me right out.
Much appreciated
So I did this, everything seems fine apart from the wifi can't connect and it doesn't want to download anything to the internal storage, I tried uninstalling and going through the process again and I can use Wifi once I've flashed the backup no problem, but once it's updated to 5.0 it seems to stop working.
Anyone got ideas? Can't find anything on google about this specific problem
Hi all,
So today my phone froze with the screen off, I reset it (power + volume up) and it just gets stuck on the boot screen. I have gone into the bootloader (power + volume up then volume down) tried recovery and factory reset but with the same results. I have been searching around quite a lot but just can't get my head around what I need to do to resurrect my phone! I know there's a way to try and sort it connected via usb with my computer but I need some help please!
(I'm currently on Mac, but will be back with my PC tomorrow if it's any easier)
Thanks in advance
Is the phone modified (unlocked bootloader, root, custom ROM, s-off, etc.) or fully stock?
If fully stock, your best bet is to run the RUU for your version M8 (if your version has RUU).
Do fastboot getvar all, and post the results (delete IMEI and serial number) so we can see more info on the phone.
redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, s-off, etc.) or fully stock?
If fully stock, your best bet is to run the RUU for your version M8 (if your version has RUU).
Do fastboot getvar all, and post the results (delete IMEI and serial number) so we can see more info on the phone.
Click to expand...
Click to collapse
Thanks for your reply. No it's totally stock, S-ON. I'm just sorting out SDK to get getvar all working. I'll post back.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
shimynor said:
(bootloader) version-main: 6.12.161.4
Click to expand...
Click to collapse
In a way, you gave answers I didn't want to hear. For a stock device, RUU would be the easiest way to get the phone running again. But as far as I can tell, your version number does not have RUU.
That being the case, your best bet is much more complex:
1) Unlock bootloader via HTCDev.com
2) Install TWRP custom recovery
3) Restore stock nandroid backup 6.12.161.4
The needed files and more instructions can be found here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But this is not going to be an easy path, if you aren't familiar with unlocking the bootloader, flashing custom recovery, etc.
Thank you again for your help. I haven't rooted a phone or anything for quite some time. I was just searching around for RUU files for my phone while I was waiting for your reply and found everything but! I am going to give your instructions a go now and I'll report back.
How do I know which version of TWRP to install?
Thanks.
shimynor said:
How do I know which version of TWRP to install?
Click to expand...
Click to collapse
The thread says what version TWRP is recommended, depending on what backup you are restoring (nandroid 6.xx in your case) so you can use 2.8.7.0.
Newer version 3.0.0.0 is also available, which will also work: https://dl.twrp.me/m8/
And there is even a brand new 3.0.0.1, but I haven't read any comments good or bad about this. So while its probably fine, I tend to stick to tried-and-true TWRP versions (such as 3.0.0.0).
---------- Post added at 12:51 PM ---------- Previous post was at 12:49 PM ----------
shimynor said:
I haven't rooted a phone or anything for quite some time.
Click to expand...
Click to collapse
If you've rooted (particularly an HTC device) you'll probably be fine. Read up on the process, and if you have any specific questions, we'll be happy to try to help.
Okay so I'm at step 12, where I need to transfer the OTA file to my phone, however now when I click on recovery on my phone it comes with the red triangle with the exclamation mark and can't get into my phone's storage via my computer. How can I transfer the downloaded OTA to my phone? Thanks.
I decided to start again to see if I'm missing anything, and on step 9 where it says select boot, data and system, I only have the options for boot and system, data is not displayed.
shimynor said:
Okay so I'm at step 12, where I need to transfer the OTA file to my phone, however now when I click on recovery on my phone it comes with the red triangle with the exclamation mark and can't get into my phone's storage via my computer. How can I transfer the downloaded OTA to my phone? Thanks.
Click to expand...
Click to collapse
You shouldn't be transferring any OTA. There isn't going to be any new OTA beyond the 6.12.161.4 that you restored via nandroid, at least not that I know of.
What you are trying to "transfer" exactly (file name and source)?
You may be confused about the steps. Describe what you've done so far, step by step.
Okay.
1. I installed the recommended TWRP version onto my phone.
2. Downloaded the backup file. (http://forum.xda-developers.com/showpost.php?p=64893769&postcount=842)
3. Downloaded the recovery file from Petert87's post (http://forum.xda-developers.com/showpost.php?p=64894064&postcount=849)
Recovery:
https://mega.nz/#!uFkVTBRR!2N6vbR3Px...fG8AhcfxmnOqwk
Click to expand...
Click to collapse
4. This bit confused me a little as it says extract the ckpv5.zip file, but this is in the firmware download, not the recovery. But I had extracted the recovery files on this step.
5. I made a back up which ended up in my internal storage.
6. Opened up fine.
7. Transferred the recovery file here.
8. I successfully wiped the dalvik cache, cache, data and system.
9. At this stage I restored only boot and system, as data doesn't appear for me (could this be the issue?)
10. Selected bootloader in the reboot menu.
11. Fastbooted the flash stock recovery.
12. Rebooted, which then takes me to the bootloop. So I went to bootloader again, went into recovery and it's coming up with the red triangle with an exclamation mark.
And this is as far as I have got, my phone appears to be the same as it was before.
I hope this makes sense!
Edit: Before all of this, I successfully (or at least appeared to be successful) unlocked the bootloader.
Edit 2: I should add that previous to all of this, in my panic of my phone breaking, I wiped the device, so I would assume there is no OS installed.
shimynor said:
I hope this makes sense!
Click to expand...
Click to collapse
Not really. I'm confused about several of the steps in your description:
1) Which version TWRP? Its probably either 2.8.7 or 3.0.0.0 based on our previous discussion (and if so, probably not terribly relevant). But always give version numbers to avoid ambiguity. What "recommended" means to you, may mean something different to me.
2) Looks good
3) Looks good
4) You need to extract several files (probably contained in a folder) from the RAR you downloaded in your Step #2. Then you need to place that folder (not the RAR) in the proper TWRP folder location on the phone (per instructions in ckpv5's guide, step 7). Based on what you described, I don't see that you did this.
5) Ok
6) What opened up fine? I have no idea what you are trying to say here.
7) Where is "here"? Again, I can't tell what you did here.
8) Ok
9) The stock nandroids won't have (and don't need) a data partition to restore. What exactly did you pick to restore? If the backup you selected to restore is a folder with todays date in it, you may have restored the backup you just made in your Step #5 above (which is a backup of a non-functioning OS).
10) At this point, its probably best to just stop and reboot to see if the OS comes up. The rest is only necessary to revert to stock recovery for purpose of OTA update (and there won't be an OTA).
---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------
shimynor said:
however now when I click on recovery on my phone it comes with the red triangle with the exclamation mark
Click to expand...
Click to collapse
This is the stock recovery screen. You restored the stock recovery, so this is expected.
Again, I don't recommend to restore to stock recovery until you get the OS up and running (if at all) since it severely limits your options. Just flash TWRP back onto the phone, as I don't think you restored the stock nandroid properly.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
shimynor said:
Edit 2: I should add that previous to all of this, in my panic of my phone breaking, I wiped the device, so I would assume there is no OS installed.
Click to expand...
Click to collapse
TWRP has the function to wipe the OS (system partition) but stock OS and stock recovery do not have that ability. So if you are saying you wiped the device before unlocking the bootloader (and subsequent steps) then NO that does not mean you wiped the OS.
But its fairly irrelevant, as it doesn't seem you had a working OS in the first place (possibly something was damaged or corrupted),which is why the phone didn't boot (which started this whole chain of events).
After wiping "system" in TWRP, you definitely wiped any OS with that step (as the instructions properly directed you to). But again, the OS wasn't working in the first place, so its fairly irrelevant that you wiped it.
Hang in there, you're actually doing great considering you came with very little knowledge of how to do these steps.
redpoint73 said:
1) Which version TWRP? Its probably either 2.8.7 or 3.0.0.0 based on our previous discussion (and if so, probably not terribly relevant). But always give version numbers to avoid ambiguity. What "recommended" means to you, may mean something different to me.
Click to expand...
Click to collapse
Yes, sorry I meant 2.8.7
redpoint73 said:
4) You need to extract several files (probably contained in a folder) from the RAR you downloaded in your Step #2. Then you need to place that folder (not the RAR) in the proper TWRP folder location on the phone (per instructions in ckpv5's guide, step 7). Based on what you described, I don't see that you did this.
Click to expand...
Click to collapse
The file I mean is the TWRP_6.12.161.4.rar. I extracted the folder within this. Within the folder itself I don't see any other files/folders, only boot.emmc.win, recovery.log, system.ext4.win000, system.ex4.win001 and system.info. Nothing else here to extract. Unless I need to merge this folder with another? (I would guess not?)
redpoint73 said:
6) What opened up fine? I have no idea what you are trying to say here.
7) Where is "here"? Again, I can't tell what you did here.
Click to expand...
Click to collapse
For 6, I just mean I was able to access the internal storage, and for 7 I transferred the TWRP_6.12.161.4 folder under TWRP/BACKUPS/SerialNo./ (where I had created the backup from step 5.)
redpoint73 said:
9) The stock nandroids won't have (and don't need) a data partition to restore. What exactly did you pick to restore? If the backup you selected to restore is a folder with todays date in it, you may have restored the backup you just made in your Step #5 above (which is a backup of a non-functioning OS).
Click to expand...
Click to collapse
I used the TWRP_6.12.161.4, and it had Boot and System pre selected, then I swiped to restore.
redpoint73 said:
TWRP has the function to wipe the OS (system partition) but stock OS and stock recovery do not have that ability. So if you are saying you wiped the device before unlocking the bootloader (and subsequent steps) then NO that does not mean you wiped the OS.
But its fairly irrelevant, as it doesn't seem you had a working OS in the first place (possibly something was damaged or corrupted),which is why the phone didn't boot (which started this whole chain of events).
After wiping "system" in TWRP, you definitely wiped any OS with that step (as the instructions properly directed you to). But again, the OS wasn't working in the first place, so its fairly irrelevant that you wiped it.
Click to expand...
Click to collapse
Yes I wiped the device before unlocking the bootloader and doing any of these steps, but like you say it's irrelevant.
What I should have mentioned is that I have tried to reboot and see if the OS loads, and it doesn't. Do I need to install the OS again from a stock ROM, reinstall firmware or something similar?
redpoint73 said:
Hang in there, you're actually doing great considering you came with very little knowledge of how to do these steps.
Click to expand...
Click to collapse
And thank you for these words, today has been a test of my patience! (and probably why my previous post didn't make much sense to you)
So it appears that I did do everything right, or at least installing Cyanogenmod got my phone working again.
Thanks a lot for your help and patience redpoint73!
shimynor said:
The file I mean is the TWRP_6.12.161.4.rar. I extracted the folder within this. Within the folder itself I don't see any other files/folders, only boot.emmc.win, recovery.log, system.ext4.win000, system.ex4.win001 and system.info. Nothing else here to extract. Unless I need to merge this folder with another? (I would guess not?)
For 6, I just mean I was able to access the internal storage, and for 7 I transferred the TWRP_6.12.161.4 folder under TWRP/BACKUPS/SerialNo./ (where I had created the backup from step 5.)
Click to expand...
Click to collapse
So under TWRP/BACKUPS/SerialNo./ you have a folder named TWRP_6.12.161.4, that contains boot.emmc.win, recovery.log, system.ext4.win000, system.ex4.win001 and system.info
Is that correct?
And another folder within TWRP/BACKUPS/SerialNo./ that probably contains the recent date in the file name, that contains the backup you just made?
If all this is correct, it looks like you properly did the steps correctly to restored the 6.12.161.4 backup, which contains the stock ROM (that is the system files in the folder) and kernel (the boot file) and it should have gotten your phone back up and running on the stock ROM. I'm not sure why it didn't work. Possibly a bad nandroid backup, or it was damaged in download, or just a TWRP fluke with no real reason (it happens . . . I've had some of my own backups fail to restore occassionally).
---------- Post added at 10:15 AM ---------- Previous post was at 10:07 AM ----------
shimynor said:
So it appears that I did do everything right, or at least installing Cyanogenmod got my phone working again.
Click to expand...
Click to collapse
Nice work. While a slightly different approach (my steps should have gotten you back up and running on the stock Sense ROM), its a perfectly valid solution to flash a ROM to get the phone running again. In fact, flashing a ROM is significantly easier than transferring and restoring a stock nandroid (as you have probably come to realize). The only reason I was suggesting the stock nandroid path, is because that was the original condition of the phone (before it failed to boot).
With the current setup, you should be able to flash most any M8 Sense or GPE ROM as well, if you like. Congratulations, you've officially joined the dark side.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
shimynor said:
And thank you for these words, today has been a test of my patience! (and probably why my previous post didn't make much sense to you)
Click to expand...
Click to collapse
No problem. You learned quite a bit, I bet. And there's nothing wrong with that . . .
redpoint73 said:
So under TWRP/BACKUPS/SerialNo./ you have a folder named TWRP_6.12.161.4, that contains boot.emmc.win, recovery.log, system.ext4.win000, system.ex4.win001 and system.info
Is that correct?
And another folder within TWRP/BACKUPS/SerialNo./ that probably contains the recent date in the file name, that contains the backup you just made?
If all this is correct, it looks like you properly did the steps correctly to restored the 6.12.161.4 backup, which contains the stock ROM (that is the system files in the folder) and kernel (the boot file) and it should have gotten your phone back up and running on the stock ROM. I'm not sure why it didn't work. Possibly a bad nandroid backup, or it was damaged in download, or just a TWRP fluke with no real reason (it happens . . . I've had some of my own backups fail to restore occassionally).
Click to expand...
Click to collapse
Yes all of that is/was correct. I didn't see any android files on my internal storage after doing all of the steps, which led me to believe there wasn't an OS installed at all. I sat there for a while considering whether flashing a custom ROM on there would sort it all out, and it did! Now I'm just considering whether it's worth rooting my phone! (I actually believed that you needed to root a phone to flash a custom ROM).
redpoint73 said:
Nice work. While a slightly different approach (my steps should have gotten you back up and running on the stock Sense ROM), its a perfectly valid solution to flash a ROM to get the phone running again. In fact, flashing a ROM is significantly easier than transferring and restoring a stock nandroid (as you have probably come to realize). The only reason I was suggesting the stock nandroid path, is because that was the original condition of the phone (before it failed to boot).
With the current setup, you should be able to flash most any M8 Sense or GPE ROM as well, if you like. Congratulations, you've officially joined the dark side.
.
Click to expand...
Click to collapse
Excuse my ignorance, but what is a GPE ROM?
shimynor said:
Yes all of that is/was correct. I didn't see any android files on my internal storage after doing all of the steps, which led me to believe there wasn't an OS installed at all.
Click to expand...
Click to collapse
Internal storage is just the user-accessible "media" storage portion of the storage.
You won't see system (OS) files unless you use a file manager like ES File Explorer that has root rights.
shimynor said:
Now I'm just considering whether it's worth rooting my phone! (I actually believed that you needed to root a phone to flash a custom ROM).
Click to expand...
Click to collapse
CM (and virtually all custom ROMs) is pre-rooted. However in CM, root isn't "activated"; but you can do so by going into Settings, tap 7 times on "Build number" to make Developer Options appear in Settings (yes, its a weird requirement to have to do this - its actually a standard Google Android thing). Then you can go into Developer Options, and turn on root.
shimynor said:
Excuse my ignorance, but what is a GPE ROM?
Click to expand...
Click to collapse
GPE = Google Play Edition
GPE is close to a "Nexus" OS build, free of most manufacturer customizations and "skinning". Its somewhat of a "pure Google Android" experience. Its made by HTC for the M8 Google Play Edition, so its not user community developed like CM (although there are custom ROMs based on GPE, that have further dev tweaks).
Hello guys,
I'm newbie here. I'm not a tech guy, to be honest. My problem is that I'm stuck on the HTC Logo Screen. My phone is HTC One M8 Eye.
So this morning, I was trying to root my phone. I unlocked my phone already ( now my phone said "Software Status: Modified" and "***Unlocked***" ). Everything was good until I was installing SuperSU.zip file. It didn't work. So I tried to search for a newer version of SuperSU, I think it's 2.56 or 2.76. I copied that to my phone, trying to install via TWRP 2.7.0.2. Everything was good, I though. It said "successful" and "all done". But when it rebooted, it got stuck on HTC Logo Screen.
I tried to turn it back on and off by holding the lock botton, volume up and volume botton at the same time. Then I tried to force it to go into the fastboot mode ( I don't know what to do call that ) where it showed me some options like fastboot, hboot, recovery and stuffs...I'm freaked out from this point and tried to relock my phone via the toolkit by Hasoon. Then I also returned my phone to S-on.
Now the problem is that I can get into the recovery screen with options like fastboot, hboot, but I don't have access to my internal storage anymore. And I'm stuck with HTC Logo Screen. The closest time was that it said "HTC One tm" but not "HTC". Then nothing happens next.
I'm pretty sure I messed up...A LOT.
Please, if anyone knows how to solve this, help me? I'm like, here, begging you since this phone is really important to me.
Thank you in advance.
1. Your main mistake is using an outdated tool
2. Bigger mistake you used tool meant for M8 not M8 eye (they are different device)
3. Biggest mistake you used an outdated TWRP and not meant to be used on M8 eye.
You can try :
1. Install correct TWRP for M8 eye - http://forum.xda-developers.com/showpost.php?p=62030698&postcount=144
2. Install SuperSU 2.76
and see your device will boot or not.
If not, you need to restore nandroid backup or RUU
khanhnn said:
I'm freaked out from this point and tried to relock my phone via the toolkit by Hasoon. Then I also returned my phone to S-on.
And I'm stuck with HTC Logo Screen. The closest time was that it said "HTC One tm" but not "HTC". Then nothing happens next.
Click to expand...
Click to collapse
This is exactly what is supposed to happen when you relock the bootloader, it renders the phone unable to boot into OS. This should never be done, unless you are going to flash an RUU.
Along with the other mistakes already pointed out, it seems you are trying things without properly understanding what the result will be, and without researching properly beforehand.
Also, you say you went back to s-on, but were you ever actually s-off? The only working s-off method is sunshine, which requires root. Therefore, I don't see how the phone could have been s-off (unless you received it that way) and it doesn't actually make sense when you say you returned to s-off.
---------- Post added at 10:21 AM ---------- Previous post was at 10:19 AM ----------
khanhnn said:
Then I tried to force it to go into the fastboot mode ( I don't know what to do call that ) where it showed me some options like fastboot, hboot, recovery and stuffs...I'm freaked out from this point
Click to expand...
Click to collapse
That is called the bootloader screen. You were trying to get into fastboot mode, and you got the bootloader screen, which then allow you to select fastboot (use vol keys to move between options, power button to confirm, if fastboot is not already selected) so I don't see what the issue is here?
Hello,
Thank you for your reply. I successfully installed the TWRP version you mentioned. But I don't know how to push the supersu zip file into my phone now since I don't have access to the internal storage.
Can you help me please?
Thank you very much!
khanhnn said:
I successfully installed the TWRP version you mentioned. But I don't know how to push the supersu zip file into my phone now since I don't have access to the internal storage.
Click to expand...
Click to collapse
Boot into TWRP, and your phone's internal storage should show up if you connect to your PC.
Hello redpoint73,
Thank you for your help.
But I'm now stuck in a new problem. I'm stuck at the bootloader screen.
I guess I'm somehow closer to finishing fixing my phone ( or I hope so since this is really important to me ).
I tried to install ROM ( which I downloaded from the HTC website I think ) but it didn't work out well. It said it was about to reboot but when it did, it returned to the bootloader screen. I tried to reboot a 2 times already but it always returned to the same screen.
What should I do now?
Thank you again.
khanhnn said:
But I'm now stuck in a new problem. I'm stuck at the bootloader screen.
Click to expand...
Click to collapse
I can't tell from the (lack of) information provided, what you have done to this point.
You said you installed TWRP 3.0? Were you ever able to boot into TWRP (or it just went to bootloader)?
If you were able to boot TWRP, were you able to use it access internal storage, as I suggested? Then what happened next?
khanhnn said:
I tried to install ROM ( which I downloaded from the HTC website I think ) but it didn't work out well. It said it was about to reboot but when it did, it returned to the bootloader screen. I tried to reboot a 2 times already but it always returned to the same screen.
Click to expand...
Click to collapse
What you downloaded is likely an RUU (ROM Update Utility) not just a ROM, there are distinct and critical differences, and you should take care not the mix up the terminology.
What is the (full and exact) file name of the RUU? You need to make sure its the right one for your device, before proceeding. And to make sure which path you want to take: TWRP to flash SuperSU or restore stock backup, or RUU. As the process is very different for each. RUU required you relocking the bootloader, which in turn prevents the installation of TWRP. So you need to be sure of which way you want to proceed the path forward, otherwise you will be wasting time going around in circles.
Also, you should do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can see more info about the phone; in order to proceed properly.
Dear redpoint73,
Thank you for all the help you have provided until now.
Yes, I can get into the TWRP ( after I selected HBOOT, I selected RECOVERY and there I was, in the TWRP ). I can get to the internal storage but I'm not sure that is what you mentioned before. Which I can access is that I can select the zip file to install ( in the TWRP screen ) , nothing else I guesss. ( I asked yesterday that how could I access the internal storage because I wanted to copy the ROM file into my phone and install it in the TWRP )
I think I downloaded both the RUU and the ROM.
Case 1: WITH THE RUU:
Everything was okay and I'm pretty sure that I downloaded the correct version ( the other two versions said that I had to use the correct one for my phone ). The file name was RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. However, I encountered the error 171 although I downloaded the HTC One Drivers already ( which is HTC Sync ). I couldn't get through this error so I gave up and tried something with the ROM.
Case 2: WITH THE ROM:
So I downloaded the ROM first from someone in xda forum. I installed it via TWRP and it said "Successful" on the screen. It said that I just gotta tap "reboot". But when my phone rebooted, it went back the bootloader screen. I rebooted 2 more times and the results were still the same. So I searched for some ROMs from other sources and all the times, it said "Successful" on the screen. It just always went back to the bootloader screen however.
Anyway, this is my phone info ( I think ) from the command getvar all:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.213311711.15G
version-cpld: None
version-microp: None
version-main: 5.07.425.1
version-misc: PVT SHIP S-ON
serialno: REMOVED
imei: REMOVED
imei2: Not Support
meid: 00000000000000
product: mels_tuhl
platform: hTCBmsm8974
modelid: 0P6B90000
cidnum: HTC__059
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5c9466dd
hbootpreupdate: 11
gencheckpt: 0
I hope this works out well
Case 1 : wrong RUU for your device
Case 2 : wrong ROM for your device
Do you really read what I posted above ? Your device is M8 eye not M8.
Case 1 : there is no RUU available for M8 eye 5.07.425.1
Case 2 : there is almost no flashable ROM for M8 eye
Using M8 RUU you'll get error, using ROM meant for M8 it won't boot, you'll get stuck on bootloader
Until you can find 5.07.425.1 RUU or backup, temporarily fix your device by restoring 5.07.401.1 backup that you can find in my backup thread.
Thank you for all of your help guys!
All sorted and my phone is back, alive!
I really appreciate what you did for me!
khanhnn said:
Yes, I can get into the TWRP ( after I selected HBOOT, I selected RECOVERY and there I was, in the TWRP ). I can get to the internal storage but I'm not sure that is what you mentioned before. Which I can access is that I can select the zip file to install ( in the TWRP screen ) , nothing else I guesss. ( I asked yesterday that how could I access the internal storage because I wanted to copy the ROM file into my phone and install it in the TWRP )
Click to expand...
Click to collapse
When booted into TWRP, you can connect to PC, and the phone's internal storage (as well as SD, if you have one inserted) will show up as a drive on your PC, that you can freely drag and drop files, etc.
If not, go to the MOUNT button in TWRP; and check the "Data" box (and "Micro SDcard" if desired). But these should be checked by default (at least on the TWRP build I'm on).
khanhnn said:
Case 1: WITH THE RUU:
Everything was okay and I'm pretty sure that I downloaded the correct version ( the other two versions said that I had to use the correct one for my phone ). The file name was RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.
Click to expand...
Click to collapse
Not sure how you can be "pretty sure" this is the right RUU, and how you came to think it was. This is the RUU for the US AT&T version. Also, the RUU would need to match the version number in the RUU name (at least have "425" in the position x.xx.425.x as that number is the carrier version identifier).
sir same problem is with me,
i need correct ROM for htc one m8 eye,please help me ,
my email is
[email protected]
(downloads were from this guide: https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727)
I was trying to unlock/root the phone through the official way, I successfully unlocked it and installed TWRP 2.8.5.0 and booted the device, everything is working fine so I decided to flash the SU. I booted to the recovery but the UI was flashing, I assumed it was just a visual bug and went on, flashed the zip and afterward every click was lagging. I tried to reboot but now It's stuck on the HTC logo, it doesn't go anywhere, I can't even hold the power to shut it down (Had to freeze it to empty the battery) while it's off I can go to the bootloader and all the options in it like the fastboot and recovery which is still laggy and has a flashing UI (I made a backup to check if it's working). I considered loading a different ROM on an SD and try to flash it and see if that fixes it but I can't risk this getting worse.
any ideas what to do in the situation? I've been doing this since the GNexus so no need for an ELI5
what Info I currently know:
bootloader info:
software: official
M8_UL PVT SHIP S-Off (was already that I didn't unlock it )
HBOOT 3.19.0.000
OS 6.12.401.4
openDSP 51.2.2-00593-m8974_f0.1015
CID-HTC__A07
Dec 17 2015,14:15:48.90021118
fastboot info:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-main: 6.12.401.4
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__A07
stock HTC Android Rom last Marshmallow update
TWRP 2.8.5.0
That's is not stock lollipop, that's the latest stock Marshmallow.
TWRP 2.8.5.0 won't properly work on it. You need TWRP 3.x.x.x and make sure to install SuperSU 2.79 the lowest version or use the current one 2.81 or 2.82
ckpv5 said:
That's is not stock lollipop, that's the latest stock Marshmallow.
TWRP 2.8.5.0 won't properly work on it. You need TWRP 3.x.x.x and make sure to install SuperSU 2.79 the lowest version or use the current one 2.81 or 2.82
Click to expand...
Click to collapse
sorry I meant Andriod 6, 'Lollipop' was a mistype (names are changing too fast recently)
I borrowed an SD card and loaded an SU removal script on it and installed the one TWRP had in it, will see if I boots, currently it's displaying the red DEV text in addition to the HTC logo instead of only the logo
if It booted; I should flash a newer TWRP then I clear right?
Abd121 said:
sorry I meant Andriod 6, 'Lollipop' was a mistype (names are changing too fast recently)
I borrowed an SD card and loaded an SU removal script on it and installed the one TWRP had in it, will see if I boots, currently it's displaying the red DEV text in addition to the HTC logo instead of only the logo
if It booted; I should flash a newer TWRP then I clear right?
Click to expand...
Click to collapse
The TWRP version 2.8.5 is really old (over 2 years) and sure to cause problem. Just flash the TWRP version as directed by ckpv5, that guy knows what he is talking about.
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
Abd121 said:
I tried to reboot but now It's stuck on the HTC logo, it doesn't go anywhere, I can't even hold the power to shut it down (Had to freeze it to empty the battery) while it's off I can go to the bootloader
Click to expand...
Click to collapse
To force a reboot, hold vol up + power, may need to hold the buttons for a minute or so in the "stuck condition". Once the screen goes black to reboot, let go of the buttons, and only hold vol down, and don't let go until you see the bootloader screen. If this fails to work (just reboots to HTC logo screen), you just got the timing wrong; either started pressing vol down too late, or let go too early. Just repeat the process, until you get the timing right.