HTC 10 non-standard behavior - HTC 10 Questions & Answers

Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
Code:
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxx
(bootloader) current-slot:
(bootloader) imei: xxx
(bootloader) version-main: 2.41.401.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__034
all:
finished. total time: 0.064s
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
Code:
target reported max download size of 1579200000 bytes
sending 'recovery' (20852 KB)...
OKAY [ 1.711s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.810s]
finished. total time: 3.528s
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message
Code:
33 RU_UPDATE_FIRMWARE_FAIL
33 RU_UPDATE_FIRMWARE_FAIL
FAIL33 RU_UPDATE_FIRMWARE_FAIL
as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.

madzur said:
Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.
Click to expand...
Click to collapse
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.

Captain_Throwback said:
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.
Click to expand...
Click to collapse
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?

madzur said:
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?
Click to expand...
Click to collapse
You sure you don't have a hardware problem? That's what it sounds like.

Captain_Throwback said:
You sure you don't have a hardware problem? That's what it sounds like.
Click to expand...
Click to collapse
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.

madzur said:
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.
Click to expand...
Click to collapse
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.

Captain_Throwback said:
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.
Click to expand...
Click to collapse
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks

madzur said:
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks
Click to expand...
Click to collapse
Nope, that only happens well, when you've modified the software by installing an unsigned image like a custom recovery or kernel or made modifications to system. So getting an RUU to flash is really the only way to restore it back to official status.

Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?

Same thing
madzur said:
Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?
Click to expand...
Click to collapse
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.

djgreyghost said:
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.
Click to expand...
Click to collapse
Pretty sure you saved my phone from extinction :good: I'm not sure I would of tried the S-On version.

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.

Dukenukemx said:
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.
Click to expand...
Click to collapse
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.

djgreyghost said:
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.
Click to expand...
Click to collapse
Guess I'll be installing LineageOS then. The phone works fine like this, but it bothers me that I can't flash it completely.

Ok the problem with [email protected] is that you installed an aftermarket screen and that causes the failure. The solution is to remove the tp_SYN3708.img file from the rom and then flash it, but I'm still working on how to do that. The tp_SYN3708.img file is specifically for flashing the screen and the screen I have is Chinese replica, so of course it doesn't work. So my options are to remove the file and flash that way or to get another LCD screen. I'd rather find a software solution as looking for an original HTC 10 screen is probably harder than it sounds.

Related

[HELP THREAD] HTC One M8 - Ask any questions here!

So you came to find help with your HTC One M8?Well, this is your thread!
I was surprised to see that a help thread hadn't been created in this forum yet (especially considering it's usually one of the first threads created in a device forum). Due to that, I thought it would be a good idea to set this up
Hello new user and welcome to XDA-Developers. We are a developer’s forum, with the purpose of development. Our work can be used in several ways, and, we know that sometimes it could help you. So, in order to maintain our forums clean and properly organized, maintaining a proper development environment while at the same time to give you a chance to join our forums, we created this thread.
This thread is for sensible questions from new or inexpert users. If you think your question may be a little basic for the wild Q&A forum then this is the place to ask it.
Here you shall find an atmosphere free of prejudice, where we will try to help you in your problem, answer your most basic questions and aid you on troubleshooting your device. We know that learning all the technicalities takes time, however they are necessary in order to interact with us.
Bare in mind that we are not technical support, we do not work for any company or get paid to help, we are just independent developers gathered in a community called XDA-Developers. Therefore all we will do is guide you into troubleshooting your device yourself, but under no circumstance we are abided to do so.
We want you to become the kind of user we see as productive to a developer’s community, and why not?, to be a developer yourself!
Note to General users:
This is a chance for more advanced users to “give back” to XDA-Developers the knowledge we have gathered together in a decade of development. This is a thread to behave in a tolerant way, taking into consideration that the user posting queries might have never even heard words such as “adb” or “ROM", so, if you are not willing to be helpful, I kindly invite you to browse into another thread.
Before asking a question in this thread, I suggest reading through the HTC One M8 Frequently Asked Questions as it's possible that your question may have already been answered in that thread
Moderators will not tolerate "flaming" or "trolling" in this thread as it is specifically provided for those who are still learning the basics.. We will delete and sanction without warning any post that show intention other than to help the new user.​
As you may notice, I kanged this thread layout from @D.O.C from the M7 help thread. Thanks sir
Great Idea mate!
Awesome! Subscribed. ?
SIM card and IMEI issues after converting to GPE
Hello everyone!
So I just bought an asian HTC one M8 developer edition from a friend and I wish I couldnt be more happy, but Im facing some issues and I hope you could help me!
I converted my HTC dev to a GPE by flashing the RUU. Before that my SIM card and network worked just fine.
But now my baseband, network, IMEI etc are all shown by "unknown" and dont work.
I actually found a forum where someone had virtually the same issue: http://forum.xda-developers.com/general/help/urgent-help-required-htc-one-m8-sim-t2810468
But while he was able to fix it by flashing a radio image of his device's original CID, that same image doesnt appear to be available anymore! (i have the same original CID as the case mentioned).
http://forum.xda-developers.com/showthread.php?t=2736921
Right now I have super CID (11111111) and my radio shows up as 1.14.21331931.LA02_2G
my original CID was BS_US002
Does anybody knows if i have to find and flash my orginal's CID radio image, or is there any other way around...
Please help me guys! xDD
thanks in advance
@rafael.trad From looking at the OP of the radio thread, there's a couple of files showing under BS_US002 (quoted below):
Developer Edition (BS_US002):
1.15.2133156.UA03_2G RADIO.IMG Thanks Kiwiandy!
1.16.21331931.LA11G_20.31A.4145.02L RADIO.IMG Thanks winner00!
Click to expand...
Click to collapse
Have you tried either of those 2 yet to see if it'll fix your issue?
KidCarter93 said:
@rafael.trad From looking at the OP of the radio thread, there's a couple of files showing under BS_US002 (quoted below):
Have you tried either of those 2 yet to see if it'll fix your issue?
Click to expand...
Click to collapse
I have tried them. But those two files are actually the only ones I can't open.
When i click on any of them it opens a Dropbox page with an error (404), saying that the files are no longer there. =/
rafael.trad said:
I have tried them. But those two files are actually the only ones I can't open.
When i click on any of them it opens a Dropbox page with an error (404), saying that the files are no longer there. =/
Click to expand...
Click to collapse
I probably should've checked those links before posting that
Try the following dev edition radio posted by donmarkoni - http://www.mediafire.com/?7i0jz8axi77ic06
Hello guys. I've been googling around why I can't root or unlock boot loader on my HTC one model id 0P6B12000. BS_US001 from what I understand it's the at&t dev edition. I've tried everything from towel root to sunshine to HTC dev unlock. Nothing works. Root fails, sunshine reboots, HTC unlock token is successful but does not unlock. Fastboot oem unlock returns err. Any ideas? Am I missing something?
Yeah, I'm getting the same problem. Flashed the unlock token and I unlocked the bootloader, but when I reboot into fastboot, it still says it is locked.
HTC Sync Manager
Sorry if this has already been asked somewhere, but I couldn't find an answer.
I have ViperOne up and running on my phone. Since I loaded it, HTC Sync Manager canont see my phone. When I plug my phone in, Android File Transfer Tool opens.
I saw another thread where they said you have to turn off fast charging. That leads me to another potential issue. The guide for ViperOne says that option is under kernels. The only thing I have listed under kernels is "Apply Kernel Settings On Boot." I don't see any of the other options.
Htc one m8 without OS trying to install viper
Hey XDA'ers
few days ago I tried to reset my phone to stock settings and I had stock Rom and everything on except it was rooted and I had twrp on it.
I accidently wiped everything on my phone including the OS itself and thats what you call having a soft bricked phone i think
cause I can still turn in on and enter Bootloader and TWRP.
so I looked everywhere on the internet for the Stock Htc one m8 OS ROM and found nothing at all but lookalikes etc so I searched through some the ROMS and found viper. I have downloaded ViperOne and put it on my SDcard i dont know if im supposed to have S-off to use viper ? or if im supposed to have stock OS and apply Viper to that ? but after successful installation it Reboots and enters Bootloader instantly everythime i turn it on I used to have to turn phone on and hold power button plus volume up then down to enter bootloader but now it just goes straight into that. ive wiped all data chache everything except SDcard
many times and tried to reinstall viper after deleting everything again but with no luck
i have Ruu for my model but my pc doesnt recognize my phone and i have tried sideloading stock rom and GApps but my phone still boots into bootloader when i turn it on
i will apreciate it alot if any one could help me since i have no other phone and my Htc one m8 is pretty new
Thanks in advance
help
i created a thread already, but I dont think it's garnering much attention.....I wouldnt even know where to begin to search for what im searching for, so Ill ask here....I have an AT&T M8. i have the latest baseband (3.28.xxx.6).....everything up til this point was working fine. I had vanir up and running, but after downloading MaxiumusHD and the ota manual update. i wanted to try something different, so I booted into recovery and attempted to wipe everything when I started getting red error messages. Im using CT's latest (non-multiboot recovery). Ive seen these red errors before, so i attempted to flash MaximusHD but b4 it finished the aroma installation, it booted automatically into the htc white screen. Currently I am able to boot into bootloader, and I can bring up fastboot devices and see that my computer recognizes my device. Everytime Ive tried going into recovery to wipe, it autmoatically boots into the that white screen without finishing the wipe process....Im using Hasoon's all in one toolkit so i dont have a computer android sdk package......Does anyone have any idea what I did wrong, b/c I have literally flashed hundreds of roms in the past and never once had this red error message when trying to wipe data in preperation for a rom flash......Right now my phone is in bootloader mode, fastboot usb...
Killer2205 said:
Hey XDA'ers
few days ago I tried to reset my phone to stock settings and I had stock Rom and everything on except it was rooted and I had twrp on it.
I accidently wiped everything on my phone including the OS itself and thats what you call having a soft bricked phone i think
cause I can still turn in on and enter Bootloader and TWRP.
so I looked everywhere on the internet for the Stock Htc one m8 OS ROM and found nothing at all but lookalikes etc so I searched through some the ROMS and found viper. I have downloaded ViperOne and put it on my SDcard i dont know if im supposed to have S-off to use viper ? or if im supposed to have stock OS and apply Viper to that ? but after successful installation it Reboots and enters Bootloader instantly everythime i turn it on I used to have to turn phone on and hold power button plus volume up then down to enter bootloader but now it just goes straight into that. ive wiped all data chache everything except SDcard
many times and tried to reinstall viper after deleting everything again but with no luck
i have Ruu for my model but my pc doesnt recognize my phone and i have tried sideloading stock rom and GApps but my phone still boots into bootloader when i turn it on
i will apreciate it alot if any one could help me since i have no other phone and my Htc one m8 is pretty new
Thanks in advance
Click to expand...
Click to collapse
I'm not 100% sure on this, but someone might be able to back me up. ViperOne uses the existing ROM when it installs. I don't believe that ViperOne is a full base OS. I don't know enough about the backups to say if you can use the backup off another phone or not.
If you unlocked your phone, that means you registered with HTC as a developer. You could ask them for the bad OS. I'm not sure if they will give it to you or not. It's at least worth a shot.
Hello there..
I want you to ask that i m using hTc one m8 with cid Htc__002 and its s-on device..
I want to go back to stock rom..
When i m restoring a nandroid backup it is getting stuck in demo mode and many apps like brightness,power saver etc are disable.. what can i do ??
I tried 2, nandroid backups... Custom rom is working fine...
Plz help me..
Sent from my HTC One_M8
Got a new HTC one M8 from Verizon. S off, unlocked, rooted. Everything was working fine until tonight. Did a nandroid backup then installed an Xposed module (advanced power menu) and things started getting funky. Android system ui started force closing so using TWRP attempted a system restore. After a few minutes the restore completed so hit the reboot button. An error message came up and said "appears that device is not rooted, slide button to restore root". Root restore failed, device rebooted and white screen with green HTC logo and powered by ANDROID on came up. Phone vibrates then stays on that screen indefinitely. When I powered off using power and vol up buttons, powers down then immediately reboots and white HTC screen comes up. Can't get it to do anything else. Tried Squabbi's HTC toolkit to send fastboot / ADB reboot commands but wouldn't work. Any suggestions would be appreciated.
Sent from my Nexus 7 using Tapatalk
funmunke said:
I'm not 100% sure on this, but someone might be able to back me up. ViperOne uses the existing ROM when it installs. I don't believe that ViperOne is a full base OS. I don't know enough about the backups to say if you can use the backup off another phone or not.
If you unlocked your phone, that means you registered with HTC as a developer. You could ask them for the bad OS. I'm not sure if they will give it to you or not. It's at least worth a shot.
Click to expand...
Click to collapse
Viper, like all other ROM's, is a complete OS on its own. Partitions are another story, but usually not relevant to the average flasher except for an occasional firmware update.
Hi guys,
I've had my M8 for a couple of weeks now, and I love it. I haven't even rooted the thing yet, which is very surprising for me!
One issue I have with my phone, is the music app by HTC is frozen when I launch it. It does not force close. I have tried wiping data and cache, to no avail. It may be unrelated, but my phone doesn't sound too great when plugged into my speakers - maybe the EQ is frozen also. Sounds very virtualized, like I'm in a massive hangar.
I'm on 4.4.3, EE in UK. Thank you!
Sent from my HTC One M8. Long live the Galaxy S3 and S. Those forums will be missed!
Help needed for update
Hi,
I wanted to know what are the steps required in order to apply this update? http://forum.xda-developers.com/showthread.php?t=2696514
My phone is S-ON and was wondering if i needed S-OFF first...
Thanks for any help.
Please Help Soft bricked HTC one M8 Sasktel(Canada)
Can someone Please help? I tried to flash custom ROM and erased everything. Only thing I can do now is get into boot loader and Flash recovery. Won't let me flash any custom ROMS. TWRP just aborts the install and won't install. CWM states that md5 file not found and then stops installing.
Here is what my boot loader getvar all states. (See below)
I am very new to this and apparently kinda dumb.
Cant seem to figure out what to do
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH444WM04837
(bootloader) imei: ##########
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: SASKT001
(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: 23c984e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please Help
Can somebody help me? I have 8GB in "others" and I don't know where it comes from. Is there an app or something for manage my storage?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can't install ROM or update

I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
kosraeboy said:
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
Click to expand...
Click to collapse
Hi
Can you give some details of the phone? CID?, international version?, S-On or off?, etc?
In short i think it is a good idea to update to a more recent bootloader. Then get yourself on to a newer ROM.
You might also want to consider twrp (big) as a new recovery.
This forum has lots of info.
Also take a look at www.onexroot.com
Thanks
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
What is your error in CWM?
kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Noobdead said:
What is your error in CWM?
Click to expand...
Click to collapse
Hopefully this image works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
grwalker said:
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Click to expand...
Click to collapse
The CID Number is: OPTUS0001
Here is bootloader screen.
kosraeboy said:
The CID Number is: OPTUS0001
Here is bootloader screen.
Click to expand...
Click to collapse
Can you post the boot loader screen shot again please. The link didn't work
Trying again
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
kosraeboy said:
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
Click to expand...
Click to collapse
Nope, link still doesn't work. Use the attachments button when replying to attached the screenshot.
If that still doesn't work then let me know what the first three lines are when you are in fastboot mode. (Hold Vol down and power until you enter fastboot). The reason i want this info is to confirm you have the international version of HOX. If the second line contains the words "Endeavoru" then you have the international version, and we can then find the right ROM and recovery for you to use.
Also this is the link to download Hboot 1.36 for OPTUS001. http://d-h.st/users/ClydeB1/?fld_id=8110. Download this and keep it handy.
I am assuming that your bootloader is unlocked. First line tells you this. Did you use the site http://www.htcdev.com/bootloader/? Do you still have the unlock token?
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
grwalker said:
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
Click to expand...
Click to collapse
Step 1 must to be after step 2, because if he flash firmware after recovery will be with stock recovery and not be possible to flash rom with stock recovery and must to flash again custom recovery. But how I think he is not a good with android devices don't have good skil to flash the firmware by him self. I suggest to answare my question and then to see if we can find RUU
Thank you both. Sorry for the delay in responding. Family emergency and I've not had time. I'll follow up in a day or so.
Sorry for the delay
Thant said:
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
Click to expand...
Click to collapse
Hi Thant:
The result is: version-main: 1.29.980.11
kosraeboy said:
Hi Thant:
The result is: version-main: 1.29.980.11
Click to expand...
Click to collapse
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Thant said:
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Click to expand...
Click to collapse
Thanks. I'll try it and let you know.
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
kosraeboy said:
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
Click to expand...
Click to collapse
GO and see if the RUU will finish if yes this is good if give you error we will see what will do.
Yes they are the same but if RUU finish you will be complete stock and then will update wia Wi-Fi stock rom to latest hboot. Don't forget to relock your bootloader
replay if rUU finish and dont forget to make nandroid backup when you install new rom after update to latest hboot for your carrier

Issues to install ANY rooted Android to HTC M9 3.35.401.32 successfully

Hi,
Is this just me or this model has some issues to install any Android successfully. I received HTC M9 couple of weeks ago. There is no data so I decided to try and gain root. This was done through HTC DEV portal successfully. It shows UNLOCKED and S-OFF. I had tried various recovery hima TWRP 3.0.2.0, 2.8.7.0, 3.1.0.0 and somehow stock os became broken. So I tried standard procedure to put 0PJAIMG.zip to SD which is picked up by standard recovery or installing rom from TWRP.
I tried at least 5 recovery variants and around 8-9 android roms (LineageOS 11.3, 11.4, a lot of variants of stock rom with name *.401.* and ViperOne).
I was able to install only ViperOne, but I need LineageOS or stock rom with root access for apps.
LineageOS validated successfully from any version of TWRP, but the installation lasts forever without progress (and phone is extremely hot!)
Stock rom shows corrupted zip from TWRP and doing standard process (0PJAIMG.zip) doesn't boot at all after restart (or phone is crashed and I need to do force power down)
Any advices guys? I may arrange the payment if this is allowed for help to not spend weeks on this. What is the secret here? - I'm for sure not experienced on Android, but have IT skills. Many thanks
mac:apple root# fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ****
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
all:
finished. total time: 0.008s
mac:apple root#
Try a twrp less than 3.0.0.0 but higher than the 2.8 you used and supersu 2.65. My stuff is here: https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
I have the 401 wwe phone too. Check the md5 hashes of the files you have and make sure that they match on the download site.
The phone is picky about twrp and supersu for some reason..
Beamed in by telepathy.
Thanks for help. I have tried twrp-2.9.0.1-hima.img with Windows and Mac OS machines and got this error:
Failed to boot to recovery mode
Press volume up or down to back to menu
The flashing process said OKAY, but not able to boot this as you see
Try a newer twrp
Roobwz said:
Try a newer twrp
Click to expand...
Click to collapse
Hello friends,
My HTC M9 is acting weird.It reboots endlessly whenever I connect to any Wi-Fi.There is no problem when
Wi-Fi is off.
Recently this problem has stretched to the mobile data connection also.Therefore now I can't use Wi-Fi and data so that the phone won't start rebooting.
Please help.
But this contradicts with previous reply. He suggest to use any version between 2.8 and 3.0.
It's very difficult to find TWRP 2.9 and for some reason these are not on twrp.me page so is this really right option?
By the way if I use any version of TWRP 3.0 or 3.1, LineageOS doesn't boot and any HTC stock image says corrupted zip
Roobwz said:
Try a newer twrp
Click to expand...
Click to collapse
Twrp has corresponding versions to the phones firmware.
2.8.7.0, 2.9.0.1 and 3.0.0.0 should ALL work with marshmallow. Higher twrp versions for nougat and lower versions for lollipop.
2.9.0.1 was pulled for allegedly being faulty but I have had ZERO issues in 2 years.
The same applies for supersu. 2.65 matches marshmallow.
I don't know if it's intentionally worked that way but that's the way it is.
If you tried twrp 2.9.0.1 AND supersu 2.65 and it still won't boot then you will be best sending it to a repair shop or back to htc.
Beamed in by telepathy.
Thanks for this. Just to confirm, I should do fastboot flash recovery twrp-2.9.0.1-hima.img (using fastboot provided by HTC or your Google share), power down phone when 100% completed, unplug the cable and boot recovery.
The phone says that it's RELOCKED and S-OFF. Is this ok?
How to install SuperSU? Is this only through TWRP - Install option? Or somehow I can do this through fastboot at the same time when doing TWRP?
So if everything is done correctly and no luck, only HTC can revert the phone to standard stock rom without root?
Any solutions or are there any people who has the same version of M9 and successfully using this? At least can you confirm that it works for you. Many thanks
This is just for other people. If you have the same version of M9, be careful with rooting. I'm able to install various TWRP or original recovery, but not able to install suggested TWRP version and importantly any stock rom or LineageOS so the phone is useless. I still cannot use this
In regard to your first post: Did you set the phone S-OFF or did you buy it in that state? (HTCdev doesn't set you phone S-OFF. It only unlocks your bootloader.) If you bought it second hand then the previous owner might have screwed the phone. That would explain why your phone didn't boot after you successfully flashed a RUU (which isn't meant to be flashed via TWRP, btw).
In regard to your last posts: If your bootloader is re-locked then the phone won't boot as long as the phone isn't completely stock. And as soons as you install TWRP your phone doesn't fulfill this requirement anymore.
Flippy498 said:
In regard to your first post: Did you set the phone S-OFF or did you buy it in that state? (HTCdev doesn't set you phone S-OFF. It only unlocks your bootloader.) If you bought it second hand then the previous owner might have screwed the phone. That would explain why your phone didn't boot after you successfully flashed a RUU (which isn't meant to be flashed via TWRP, btw).
In regard to your last posts: If your bootloader is re-locked then the phone won't boot as long as the phone isn't completely stock. And as soons as you install TWRP your phone doesn't fulfill this requirement anymore.
Click to expand...
Click to collapse
Thanks for your post. I bought used phone in S-OFF state. If any suggestions what I can still try to do by myself that would be appreciated as well.
Re-unlock the bootloader. As long as TWRP is installed your phone won't boot, otherwise.
Sent from my HTC One M9 using XDA Labs

My htc 10 is dead ?

Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
yldlj said:
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
ubadafatta said:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
Click to expand...
Click to collapse
Since there Is no RUU and you re locked your Bootloader there's not much I can help you with sorry.
ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.011s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.080s]
finished. total time: 1.094s
this what i get when i try to flash unlocktoken or oem unlock bootloader or even when i try get_token_identifier
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
ubadafatta said:
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Click to expand...
Click to collapse
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The threory of the OTA is fine but not in this case.
Cheers.
Click to expand...
Click to collapse
Yeah thanks. I deleted all my post because there's no point in arguing. Your correct I totally forgot what the OP problem was after all this. Thanks for the clarification.
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Click to expand...
Click to collapse
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
ayyu3m said:
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Click to expand...
Click to collapse
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Mr Hofs said:
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
Click to expand...
Click to collapse
ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I will have a look at it when i have more time, and let's not bash but learn ?
:highfive:
Cheers guys.
ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Yeah i got your PM. Thanks for that. After reading your PM i also knew how stupid i was being. And when i came to delete the post, they were already deleted by the thread administrators.
Sorry once more man. Wont happen again
yldlj said:
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Click to expand...
Click to collapse
ayyu3m said:
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
Click to expand...
Click to collapse
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
[email protected] said:
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
Click to expand...
Click to collapse
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
yldlj said:
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
Click to expand...
Click to collapse
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
[email protected] said:
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
Click to expand...
Click to collapse
Yeah everyone I flash RUU it does bypass some things. Relocking bootloader usually causes problems and I don't know people still keep doing it. I would say flash twrp followed by leedroid but pretty sure you need an unlocked bootloader to flash twrp. Sorry but I'm out of ideas.

Installing the original OS with SD card or autoload

Dear friendly xda-developer people,
my HTC One M8 went out because of an empty battery. When I restarted, it only boots the bootloader. The security mode isn't working as well. I tried all I could think of and now I just want to install the original OS on the phone in hope that it will work again.
When I boot up the phone it says it is "OS-6.12.161.4". I am from Germany and I guess it is a vodafone branded HTC. So I do not find the right software on the official US website. I tried to google a different version and all I could find was a software to which the phone anwsers when I try to install the .zip via SD-card "Image Update Fail! Device halted due to Large Image update fail!"
I will post the complete screen of the boot below.
Any ideas what I could do? I tried to update it via PC, that didn't work as well. I think I need the right software and the one I found might just be the wrong one. I also tried to unlock it, but relocked it because I read, that I can not install the original software if it is unlocked.
If I can not install the original os: Is it possible to install something else that just works like the original OS? I can not use Google Products than?
I am really thankful for any advice.
Greetings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is the background of this device? Did it have a stock "official" HTC ROM on there when you had the "no OS" issue? Was it ever bootloader unlocked before you unlocked it to try to solve this problem?
Best for us to see more details about the phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
ghostmag said:
I tried to google a different version and all I could find was a software to which the phone anwsers when I try to install the .zip via SD-card "Image Update Fail! Device halted due to Large Image update fail!"
I tried to update it via PC, that didn't work as well. I think I need the right software and the one I found might just be the wrong one.
Click to expand...
Click to collapse
You absolutely need to use an RUU (ROM Update Utility) that is intended for your M8 version's (Vodaphone) carrier ID (CID) as well as the version number 6.12.161.4. Another version number means it is made for a different CID, and will fail by definition. HTC phones are quite strict about version number checking.
In your case, I don't think that there exists an RUU for the Vodaphone version. But you can install the stock OS by other means (see below).
ghostmag said:
If I can not install the original os: Is it possible to install something else that just works like the original OS?
Click to expand...
Click to collapse
While your Vodaphone version M8 doesn't have an RUU, there is another way to get back to the stock ROM. You can unlock the bootloader again, than install TWRP and a stock TWRP backup from the collection.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to do through Step 9, then reboot and it should boot to the OS. The remaining steps were only for getting official OTA updates (which is no longer relevant).
ghostmag said:
I can not use Google Products than?
Click to expand...
Click to collapse
I think you mean a ROM straight from Google? Google doesn't make complete ROMs for any device, except for Pixel devices (and the old Nexus devices). For any other device manufacturer, at least some part of the ROM needs to be customized for the specific hardware configuration. But you do have some options, if you want a ROM that is more lightweight then the HTC Sense interface:
Even though we don't have a "pure" Google ROM; what we do have for the M8, is something called the Google Play Edition (GPe). Which even though made by HTC, is designed to feel like a "pure Google" ROM. Once you have the bootloader unlocked and TWRP installed, you can install this the same way as a custom ROM. Follow the part of the thread labelled "Flashable GPe ROM". You can't flash as an RUU, since you are s-on.
https://forum.xda-developers.com/showthread.php?t=2708589
Another option is Lineage custom ROM. Lineage custom ROM is somewhat similar to a Google OS. Although at this point, it does have enough modifications, that I can't really consider it a "pure Google" experience. But it is much more lightweight than a Sense ROM. Very similar to installing the GPe ROM, once you have the bootloader unlocked, install TWRP and flash the ROM.
redpoint73 said:
What is the background of this device? Did it have a stock "official" HTC ROM on there when you had the "no OS" issue? Was it ever bootloader unlocked before you unlocked it to try to solve this problem?
Best for us to see more details about the phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
You absolutely need to use an RUU (ROM Update Utility) that is intended for your M8 version's (Vodaphone) carrier ID (CID) as well as the version number 6.12.161.4. Another version number means it is made for a different CID, and will fail by definition. HTC phones are quite strict about version number checking.
In your case, I don't think that there exists an RUU for the Vodaphone version. But you can install the stock OS by other means (see below).
While your Vodaphone version M8 doesn't have an RUU, there is another way to get back to the stock ROM. You can unlock the bootloader again, than install TWRP and a stock TWRP backup from the collection.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to do through Step 9, then reboot and it should boot to the OS. The remaining steps were only for getting official OTA updates (which is no longer relevant).
I think you mean a ROM straight from Google? Google doesn't make complete ROMs for any device, except for Pixel devices (and the old Nexus devices). For any other device manufacturer, at least some part of the ROM needs to be customized for the specific hardware configuration. But you do have some options, if you want a ROM that is more lightweight then the HTC Sense interface:
Even though we don't have a "pure" Google ROM; what we do have for the M8, is something called the Google Play Edition (GPe). Which even though made by HTC, is designed to feel like a "pure Google" ROM. Once you have the bootloader unlocked and TWRP installed, you can install this the same way as a custom ROM. Follow the part of the thread labelled "Flashable GPe ROM". You can't flash as an RUU, since you are s-on.
https://forum.xda-developers.com/showthread.php?t=2708589
Another option is Lineage custom ROM. Lineage custom ROM is somewhat similar to a Google OS. Although at this point, it does have enough modifications, that I can't really consider it a "pure Google" experience. But it is much more lightweight than a Sense ROM. Very similar to installing the GPe ROM, once you have the bootloader unlocked, install TWRP and flash the ROM.
Click to expand...
Click to collapse
First of all: Thank you very very much for your time and effort answering me. I highly appreciate that.
I will try to deliver fastboot getvar-data as soon as I am able to get back to a Windows or Ubuntu PC.
I now was able to install a TWRP backup. Your link is very helpful.
Sadly, my sound isn't working anymore now. I guess every 20 reboots or so it does work, but I can not replicate that.
Also I can not make videos and can not record audio. I then tried to install Cynagenmod which had the same problem and then I tried Lineage OS which had the same problem as well.
Do you have an idea what I can do to fix that? I read about upgrading radio, but that sounds like an easy-to-brick-my-phone way.
In case that helps: Background of the phone is just stock "official" HTC ROM as far as I know.
Since I was able to install other OS, the part of the screenshot above where you can read "OS-6.12.161.4" is just "OS" and nothing else anymore.
Regarding the topic that I wanted the original firmware: I thought Gapps are only available on official firmware. Since I know that a custom OS can run them as well, I do not care about the OS. I thought LineageOS and Cynagenmod were both lovely and would try out everything that does the job.
Any idea how it is possible that the sound / recording videos and sound don't work with three different OS?
Greetings
My responses below in red font:
ghostmag said:
Sadly, my sound isn't working anymore now. I guess every 20 reboots or so it does work, but I can not replicate that.
Also I can not make videos and can not record audio. I then tried to install Cynagenmod which had the same problem and then I tried Lineage OS which had the same problem as well.
Might be a firmware issue. When I say "firmware", I am referring to a specific package (usually a file named firmware.zip) that contains certain partitions necessary for the ROM to work (radio, hboot, recovery, and others), but does actually not contain the ROM itself. On that note, it is probably best for you to stop thinking of the term "firmware" as interchangeable with the ROM. If you mean ROM, just say ROM. No need to call it something else, and doing so will just cause confusion. It is best to use specific terms (stock ROM, RUU, stock TWRP backup, etc.).
Random sound or video issues can sometimes be a result of old/damaged firmware. It is probably useful to flash the firmware (more on this below).
Do you have an idea what I can do to fix that? I read about upgrading radio, but that sounds like an easy-to-brick-my-phone way.
You can't flash a radio (alone) with s-on. And not worth getting s-off ($25 US by sunshine app) just to flash a radio. What you can do, is flash the whole firmware zip, and see if that helps. But I'd like to get the full getvar output, to make sure which firmware is the correct one for your version M8. As you mentioned, flashing the wrong radio can be catastrophic.
In case that helps: Background of the phone is just stock "official" HTC ROM as far as I know.
Since I was able to install other OS, the part of the screenshot above where you can read "OS-6.12.161.4" is just "OS" and nothing else anymore.
What version TWRP did you install? If you followed the guide closely, you should have used TWRP 2.8.7 or later. No number being shown for OS version is sometimes a result of flashing Lineage (known bug), or an old version of TWRP.
Click to expand...
Click to collapse
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
I got the getvar all reaction now:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
The first time I tried working with TWRP I installed an older version - sadly don't remember which one. I installed a version of Cynagenmod with it. Then I accidentally crashed TWRP somehow so I had to install it again so I am using 3.3.0-0 right now because I thought it's best to install the newest version I could find.
Should I try again installing a different version of TWRP?
Sidenote: I now have the problem that WLAN doesn't work a lot of times. I need to reboot around 5 times so WLAN works. I guess that is another issue because of the mistakes I made while installing different OS.
Thanks again for your time.
ghostmag said:
The first time I tried working with TWRP I installed an older version - sadly don't remember which one. I installed a version of Cynagenmod with it. Then I accidentally crashed TWRP somehow so I had to install it again so I am using 3.3.0-0 right now because I thought it's best to install the newest version I could find.
Should I try again installing a different version of TWRP?
Click to expand...
Click to collapse
TWRP 3.3.0-0 should be okay. I agree, using the latest version is typically the best thing to do.
What I would try, is the following. Note that you will lose all data on the phone when you do this, so plan accordingly, if there is any data on the phone you want to keep (backup to cloud, computer, etc.):
1) Flash the firmware fw_6.12.161.4 from here (instruction on how to flash firmware, near the bottom of the post): https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2) After flashing firmware, you will need to unlock the bootloader again. Either use the same unlock bin code you used before (flash with fastboot command). Or go through the process on HTVDev.com, to get a new code.
3) Flash TWRP back to the device (flashing stock firmware wipes TWRP, so you need to put it on there again).
4) Restore stock TWRP backup 6.12.161.4, using TWRP. https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Not sure if this will solve your problems, but I'm hoping it will. This process will put a stock ROM and corresponding firmware on the device (a clean slate, as it were).
redpoint73 said:
TWRP 3.3.0-0 should be okay. I agree, using the latest version is typically the best thing to do.
What I would try, is the following. Note that you will lose all data on the phone when you do this, so plan accordingly, if there is any data on the phone you want to keep (backup to cloud, computer, etc.):
1) Flash the firmware fw_6.12.161.4 from here (instruction on how to flash firmware, near the bottom of the post): https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2) After flashing firmware, you will need to unlock the bootloader again. Either use the same unlock bin code you used before (flash with fastboot command). Or go through the process on HTVDev.com, to get a new code.
3) Flash TWRP back to the device (flashing stock firmware wipes TWRP, so you need to put it on there again).
4) Restore stock TWRP backup 6.12.161.4, using TWRP. https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Not sure if this will solve your problems, but I'm hoping it will. This process will put a stock ROM and corresponding firmware on the device (a clean slate, as it were).
Click to expand...
Click to collapse
Dear friend,
I followed your guide and right now I am at step 3)
While looking for the newstest TWRP.img-file the phone is booting Android and is installing Apps right now. I even heard at startup sound. Is it possible, that I won't need the following steps and it just got the stock firmware from my last install?
ghostmag said:
I followed your guide and right now I am at step 3)
While looking for the newstest TWRP.img-file the phone is booting Android and is installing Apps right now. I even heard at startup sound. Is it possible, that I won't need the following steps and it just got the stock firmware from my last install?
Click to expand...
Click to collapse
Yes, it is possible you don't need to do anything further.
As I warned before, be careful about using the term "firmware". It seems you are using it synonymously with "ROM" again. If you accomplished Step 1 (as designated in my last response) you flashed the stock firmware. The stock ROM should still be there from the TWRP backup you restored previously. Nothing you have done so far, would have overwritten the stock ROM that you restored, so it is still there.
You previously restored the proper number 6.12.161.4 stock TWRP backup?
redpoint73 said:
Yes, it is possible you don't need to do anything further.
As I warned before, be careful about using the term "firmware". It seems you are using it synonymously with "ROM" again. If you accomplished Step 1 (as designated in my last response) you flashed the stock firmware. The stock ROM should still be there from the TWRP backup you restored previously. Nothing you have done so far, would have overwritten the stock ROM that you restored, so it is still there.
You previously restored the proper number 6.12.161.4 stock TWRP backup?
Click to expand...
Click to collapse
Yes, I did and it all works fine now. Even the battery is much better than before.
Thank you very very much for your time and help. If you ever come to Germany, let me know and I will buy you a drink or something
Kind regards and have a good life
ghostmag

Categories

Resources