Related
Hey guys, I have a bit of an issue with my HTC One M8 (UK, Three Network)
I flashed the custom ViperOne ROM on my one with what seemed to be no problems, but when I booted up I couldn't access WiFi and a couple of other things weren't right.
I then flashed AndroidRevolutionHD, and the same errors were still there, and this time I couldnt play any music.
I got annoyed and decided to keep stock with root and find whatever tweaks I wanted on my own. But, when I did a wipe I cleaned off the OS, which has led to my problem.
I have gone from no OS, to factory resets for another OS (still no WiFi)
I got to a point where I didnt have TWRP recovery, just the red triangle with an exclamation mark.
I have gone through a couple different methods, and I now have TWRP back but, no OS.
I have read up on RUU's but cant seem to find one, I just want my stock OS back with everything running as it should, can anybody tell me what steps I should take at the moment?
I just keep booting into TWRP recovery, I can't get in to anything else except that and bootloader
Heres some info on my device:
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1
CID: H3G_001
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Didn't you read all the warnings that you need to update your Firmware befor flashing the Rom?
You can read about it in the Rom thread.
Your OS is wiped. You need to restore the stock backup.
Here is TWRP nandroid backup for your CID H3G__001
http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1895
ckpv5 said:
Your OS is wiped. You need to restore the stock backup.
Here is TWRP nandroid backup for your CID H3G__001
http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1895
Click to expand...
Click to collapse
Thanks, I'm completely new to android, I have put the backup in my TWRP backups folder but when I click backup, it's not there, any ideas why?
I only have it in one folder should I put it in two?
not sure how to do it as ADB won't let me push a folder through
thanks for the reply
I know I was stupid, I did read the post about updating and I couldn't see any options too so I assumed I was fully updated
Thanks for helping me sort this mess guys
jayx20 said:
Thanks, I'm completely new to android, I have put the backup in my TWRP backups folder but when I click backup, it's not there, any ideas why?
I only have it in one folder should I put it in two?
not sure how to do it as ADB won't let me push a folder through
thanks for the reply
I know I was stupid, I did read the post about updating and I couldn't see any options too so I assumed I was fully updated
Thanks for helping me sort this mess guys
Click to expand...
Click to collapse
Yeah TWRP needs also your serialno. Do the following. Make a backup with TWRP, something small like boot. And then place the files from the stock backup that ckpv5 pointed at to the created directory. TWRP will be able to pick them up and restore.
stathis95194 said:
Yeah TWRP needs also your serialno. Do the following. Make a backup with TWRP, something small like boot. And then place the files from the stock backup that ckpv5 pointed at to the created directory. TWRP will be able to pick them up and restore.
Click to expand...
Click to collapse
thanks a lot man, but how do I do that whilst in recovery? the only thing I can seem to do is use adb commands
jayx20 said:
thanks a lot man, but how do I do that whilst in recovery? the only thing I can seem to do is use adb commands
Click to expand...
Click to collapse
To do what? Backup boot to create the folder? Or move the backup folder to your phone?
In TWRP go to backup, select only boot and swipe to backup.
If you are having difficulties to copy the backup folder to your phone just remove microsd, use a card reader to move it from pc to microsd and continue.
Or you can flash TWRP 2.8.1.0 which has MTP enabled and it will allow you to copy the folder from recovery
jayx20 said:
thanks a lot man, but how do I do that whilst in recovery? the only thing I can seem to do is use adb commands
Click to expand...
Click to collapse
You have a custom recovery but you don't know how to use it
Look at the attached picture.
1) Tap on Backup
2) Deselect everything except "Boot" to make a backup of the boot sector/partition.
3) Swipe to make backup. TWRP will then automatically create the path: /sdcard/TWRP/Backups/serialnum/ The serial number will be the one for your device. OR if you selected to backup to external SD Card: /storage/ext_sd/TWRP/BACKUPS/SERIAL-NUMBER-FOLDER/
4) Place the nandroid backup that was linked for you inside the newly created TWRP BACKUPS folder(UNZIP IT FIRST)
5) Go into TWRP and go to "Restore" <<As you can see in the picture attached it's right next to "Backup". - It'll usually take you to default one that was used for backup purposes(Internal/External) but you can select change to external if you made it to external.
6) Select the nandroid backup that'll show in TWRP and swipe to restore.
For future references and less headaches/problems:
7) Flash back stock recovery fastboot flash recovery recovery.img
8) Forget about flashing until you read up on it more.
jayx20 said:
Thanks, I'm completely new to android
Click to expand...
Click to collapse
You need to slow down and read read read until you understand the basic concepts and procedures. Being new is no crime, we were all there at one time. But proceeding without the proper basic knowledge is dangerous, what got you in this position, and its a wonder you haven't bricked your phone. Stop and read before doing anymore to your phone, or you risk permanent damage. Some basics that you should have known before doing any mods to the phone:
1) Not knowing how to use custom recovery, and neglecting to make a backup of your stock ROM. You shouldn't flash anything without making a nandroid backup first.
2) You wiped OS in recovery. You should not be wiping anything if you don't know what it is, or what the result will be.
3) Factory reset doesn't do anything but wipe user data. Its not going to "restore" a previous OS.
4) Read the thread for any ROM or mod you want to flash. At least read the top post of the ROM thread, and the last few (most recent) pages of the thread. This alone will usually clue you in to any common issues. The WiFi/firmware issue in particular gets discussed several times a day.
I don't say this to be a jerk. I hope you find this a respectful recommendation, and for your own good.
BerndM14 said:
You have a custom recovery but you don't know how to use it
Look at the attached picture.
1) Tap on Backup
2) Deselect everything except "Boot" to make a backup of the boot sector/partition.
3) Swipe to make backup. TWRP will then automatically create the path: /sdcard/TWRP/Backups/serialnum/ The serial number will be the one for your device. OR if you selected to backup to external SD Card: /storage/ext_sd/TWRP/BACKUPS/SERIAL-NUMBER-FOLDER/
4) Place the nandroid backup that was linked for you inside the newly created TWRP BACKUPS folder(UNZIP IT FIRST)
5) Go into TWRP and go to "Restore" <<As you can see in the picture attached it's right next to "Backup". - It'll usually take you to default one that was used for backup purposes(Internal/External) but you can select change to external if you made it to external.
6) Select the nandroid backup that'll show in TWRP and swipe to restore.
For future references and less headaches/problems:
7) Flash back stock recovery fastboot flash recovery recovery.img
8) Forget about flashing until you read up on it more.
Click to expand...
Click to collapse
I got the backup to show up in TWRP, as I swipe to recover i get recovery failed error, along with "No Partitions selected for restore"
Hopefully I'm almost there and I can stop bugging you guys, I appreciate your help and have thanked you all.
redpoint73 said:
I don't say this to be a jerk. I hope you find this a respectful recommendation, and for your own good.
Click to expand...
Click to collapse
I never took it that way, I appreciate the criticism, I did read through but I went in thinking of my iPhone experiences, jailbreaking and restoring was a breeze!
jayx20 said:
I got the backup to show up in TWRP, as I swipe to recover i get recovery failed error, along with "No Partitions selected for restore"
Click to expand...
Click to collapse
Just check the boxes next to "System" and "Boot", then swipe across to restore.
jayx20 said:
I never took it that way, I appreciate the criticism, I did read through but I went in thinking of my iPhone experiences, jailbreaking and restoring was a breeze!
Click to expand...
Click to collapse
That's great, not everyone is so accepting of criticism!
Every device is different, and has its own learning curve. Something that is not to be taken for granted. Even within Android, each device has its subtleties. You'll find XDA is rich with information for those that want to read and learn. Take your time, and make sure you are comfortable you fully understand, before you do anything. Or only do things you are specifically instructed to do by a guide or knowledgeable "helper". If you have any doubt, come here and ask first. Its better to ask a stupid question, than to make a stupid mistake.
jayx20 said:
I got the backup to show up in TWRP, as I swipe to recover i get recovery failed error, along with "No Partitions selected for restore"
Click to expand...
Click to collapse
Check whether you have a folder inside the backup folder.
Read item 3 a to f - http://forum.xda-developers.com/showpost.php?p=55398223&postcount=7
Then you'll have some idea what I am saying here. (ignore the backup version no. and other items .... read only no. 3 a to f)
And maybe it is good to change your TWRP recovery to the latest one. Based on your info above you still have the old version with version-main missing bug.
Its just the folder guys, no folder in a folder
I put it in my serialno folder and it now picks it up.. but I think its somehow being corrupted as I dont have the option to select anything, whereas the one backup I made that wont restore, shows me the options.. I don't get whats going on, it takes around 12 minutes to transfer the files to SD but still seems to be corrupt..
To be clear, the folder structure should be: TWRP>BACKUPS>serial number>folder
With the last folder typically named (at least by TWRP default) starting with date (2-14-10-24-xxxxxx). Although this folder can be renamed to just about anything, and not sure how the stock nandroids from the collection thread are named.
Inside that folder, you should see several contents, including boot.img (or boot.emmc.win), a couple system files, and possibly some others.
redpoint73 said:
To be clear, the folder structure should be: TWRP>BACKUPS>serial number>folder
With the last folder typically named (at least by TWRP default) starting with date (2-14-10-24-xxxxxx). Although this folder can be renamed to just about anything, and not sure how the stock nandroids from the collection thread are named.
Inside that folder, you should see several contents, including boot.img (or boot.emmc.win), a couple system files, and possibly some others.
Click to expand...
Click to collapse
Yeah thats exactly how i currently have it, just cant select any options, and file manager shows the folders as empty, I also cannot delete these backups
jayx20 said:
Yeah thats exactly how i currently have it, just cant select any options, and file manager shows the folders as empty, I also cannot delete these backups
Click to expand...
Click to collapse
Copy a custom rom to external sdcard and flash it?
SaHiLzZ said:
Copy a custom rom to external sdcard and flash it?
Click to expand...
Click to collapse
Have thought about that, but would my WiFi issue would still be there?
And if I was to do that, would I then be able to get the stock nandroid on my internal storage?
jayx20 said:
Have thought about that, but would my WiFi issue would still be there?
And if I was to do that, would I then be able to get the stock nandroid on my internal storage?
Click to expand...
Click to collapse
If you find and flash an older, Sense software 2.x based ROM, WiFi will work as it should.
Not sure if this will help your issue with restoring the nandroid, as its hard to tell what is causing the issue. But flashing the right ROM will at least get your phone back up and running with working WiFi. If nothing else, it will at least make it easier to move the TWRP backup (just mount MTP to computer and copy it that way, or use a file manager within Android to move it to the right place).
redpoint73 said:
If you find and flash an older, Sense software 2.x based ROM, WiFi will work as it should.
Not sure if this will help your issue with restoring the nandroid, as its hard to tell what is causing the issue. But flashing the right ROM will at least get your phone back up and running with working WiFi. If nothing else, it will at least make it easier to move the TWRP backup (just mount MTP to computer and copy it that way, or use a file manager within Android to move it to the right place).
Click to expand...
Click to collapse
This sounds like a good idea, Ideally I just want to get my phone back to stock so doing this could give me a chance to then get stock and update it to the latest FW..
Any idea where I could find one of these ROMs?
jayx20 said:
Any idea where I could find one of these ROMs?
Click to expand...
Click to collapse
Just look in the Development forum for ROMs based on 2.xx Sense. They are older, so you have to go past the first page. But I see Renovate, Virtuous, SinLess, and others still have 2.xx based ROMs posted.
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.
Hello all.
I tried to root my phone last night, and screwed up somewhere along the way. I ended up formatting my disk and didn't make a backup of my stock settings. Since then, I have had no luck with installing any custom or stock ROMs. I have tried ARHD & Venom, but got the error "some symlinks failed." I have also tried CM11, but TWRP gave me the message: "Error Flashing Zip." I have found a recovery posted by someone on this forum for my carrier's version of the phone. However, I cannot place the recovery files into the necessary locations on my phone, as it won't register on my computer as a USB device. Does anyone have any advice on where to go from here? I can still access TWRP and can still use fastboot & adb with my computer.
Extra Info:
version: 0.5
version-bootloader: 3.19.0.00
version-baseband: 1.09.20.092
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA453SF02621
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B20000
cidnum: LRA__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 2e9b7c51
hbootpreupdate: 11
gencheckpt: 0
maasau said:
I have found a recovery posted by someone on this forum for my carrier's version of the phone.
Click to expand...
Click to collapse
You mean a nandroid backup, or TWRP backup. TWRP is the recovery.
maasau said:
However, I cannot place the recovery files into the necessary locations on my phone, as it won't register on my computer as a USB device. Does anyone have any advice on where to go from here? I can still access TWRP and can still use fastboot & adb with my computer.
Click to expand...
Click to collapse
Put the nandroid files on your phone with adb push.
If you got the nandroid from the stock nandroid collection, that thread has instruction in the 3rd post how to adb push the files to the correct location.
redpoint73 said:
You mean a nandroid backup, or TWRP backup. TWRP is the recovery.
Put the nandroid files on your phone with adb push.
If you got the nandroid from the stock nandroid collection, that thread has instruction in the 2nd post how to adb push the files to the correct location.
Click to expand...
Click to collapse
I believe it is a nandroid backup, but I am not sure. After unzipping the file, it gave me folders: clockworkmod>backup>2015-01-26.15.15.28_KTU84P_release-keys, if that helps distinguish. It also contains a nandroid.md5 file.
Do you happen to have the link that has the adb push directions? Otherwise I'll start digging.
maasau said:
I believe it is a nandroid backup, but I am not sure. After unzipping the file, it gave me folders: clockworkmod>backup>2015-01-26.15.15.28_KTU84P_release-keys, if that helps distinguish. It also contains a nandroid.md5 file.
Do you happen to have the link that has the adb push directions? Otherwise I'll start digging.
Click to expand...
Click to collapse
Its a clockworkmod nandroid (based on the file folder name), not a TWRP nandroid. CWM has the option in its settings to restore a TWRP backup, but I don't think that the vice versa is true (can't restore a CWM backup with TWRP).
Therefore you want a TWRP backup for your CID (a CWM backup won't work).
If you got the nandroid from the stock nandroid thread, it has instuctions for how to adb push in the 3rd post, under Questions & Answers, 2nd question: http://forum.xda-developers.com/showpost.php?p=58128936&postcount=3
Another option: if you are on a current TWRP version, you are supposed to be able to mount internal memory in TWRP. You can then just navigate to the proper folder with your computer, and copy and paste the files to the proper place.
Another another option: change nandroid backup location in TWRP to removable SD, then make a backup so that TWRP creates the proper directory on the SD. Then remove the card and use a card reader to place the files from your computer to the SD, in the folder that TWRP just created.
redpoint73 said:
Its a clockworkmod nandroid (based on the file folder name), not a TWRP nandroid. CWM has the option in its settings to restore a TWRP backup, but I don't think that the vice versa is true (can't restore a CWM backup with TWRP).
Therefore you want a TWRP backup for your CID (a CWM backup won't work).
If you got the nandroid from the stock nandroid thread, it has instuctions for how to adb push in the 3rd post, under Questions & Answers, 2nd question: http://forum.xda-developers.com/showpost.php?p=58128936&postcount=3
Another option: if you are on a current TWRP version, you are supposed to be able to mount internal memory in TWRP. You can then just navigate to the proper folder with your computer, and copy and paste the files to the proper place.
Another another option: change nandroid backup location in TWRP to removable SD, then make a backup so that TWRP creates the proper directory on the SD. Then remove the card and use a card reader to place the files from your computer to the SD, in the folder that TWRP just created.
Click to expand...
Click to collapse
Okay, I will try that. However, now I am stuck in an infinite loop of my phone on the charging screen, and I cannot get back to the bootloader or recovery. Any advice on that? Or did I officially screw my phone up?
Edit: Got back to bootloader. I will update on your idea once I try it out.
maasau said:
However, now I am stuck in an infinite loop of my phone on the charging screen, and I cannot get back to the bootloader or recovery. Any advice on that? Or did I officially screw my phone up?
Click to expand...
Click to collapse
I assume you changed something to cause this loop. What did you do?
I haven't heard of a loop to the charge screen. But if its a boot loop, just hold the vol down button, and the next time it loops to reboot, it will go to bootloader.
Otherwise, hold the power up and vol down button to force a reboot. Then the instant screen goes dark to reboot, let go of those buttons and hold power down. Don't let go until hboot comes up. If the phone reboots, and you don't go to hboot, you either didn't start pressing vol down soon enough, or let go of it too early. Just repeat until you get it right.
redpoint73 said:
I assume you changed something to cause this loop. What did you do?
I haven't heard of a loop to the charge screen. But if its a boot loop, just hold the vol down button, and the next time it loops to reboot, it will go to bootloader.
Otherwise, hold the power up and vol down button to force a reboot. Then the instant screen goes dark to reboot, let go of those buttons and hold power down. Don't let go until hboot comes up. If the phone reboots, and you don't go to hboot, you either didn't start pressing vol down soon enough, or let go of it too early. Just repeat until you get it right.
Click to expand...
Click to collapse
I had to hold the power & volume down button for about a minute, but then the bootloader came up.
By the way, thank you so, so much! I used your idea of creating a pseudobackup, and it worked! I have been working on this all day and it feels great just to have my phone back to normal!
maasau said:
By the way, thank you so, so much!
Click to expand...
Click to collapse
You're quite welcome. Happy to help.
Also, there is a button for that (Thanks).
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]