Hello,
As mentioned in the title, my M8 is having a bit of trouble. Earlier this week, my encrypted device would not recognize that it was encrypted upon restart. Hence, a call to Verizon, and a transfer to HTC occurred. The HTC representative said to download HTC Sync Manager and run the repair tool for my phone. I did that and unfortunately the repair was not completed successfully (even after numerous attempts with various USB cable/ports), so I am stuck with the present problem. A subsequent call to HTC proved futile as my phone is no longer under warranty. I've search this forum and discovered a similar incident involving an international device which did not appear to be resolved amicably.
I've made no attempt to root or otherwise modify device software.
Ideas?
Tom
I assume you have stock recovery? If you are stuck in bootloader mode then try using fastboot to get into RUU mode. I'm curious to see if you can because I've never ran into anyone NOT rooted or have a stock recovery.
"Fastboot oem rebootRUU" with out the quotes. If you can't get into RUU fastboot mode then I have no ideas to help you...
Related
I have a rooted Desire on Orange UK and running LeeDroid. I have my main SD card and a spare (the spare is used for flashing any roms etc.). I've made both goldcards.
Recently I've had problems with my phone rebooting randomly and today it did the same (been meaning to get in touch with HTC for a motherboard replacement which I've read fixes it). Sometimes when this happens it gets stuck on the white HTC logo and the solution is to pull the battery and then wait a bit and turn on and then it's fine. However today I did just that and now I can't boot into the OS or recovery modes.
I had a generic RUU that I used to downgrade my bootloader previously so I thought running that to flash back to a generic rom would at least get me back to a starting position. However I'm getting the CID error running that, using both goldcards. This would suggest to me the goldcards aren't properly working now!
Obviously not being able to get into anything other than bootloader/fastboot I cannot connect via adb and I also can't attempt to remake a goldcard. The ideal solution would be to get it into recovery somehow just so I can re-flash a rom.
If my phone is buggered then will Orange/HTC be able to tell if it's rooted (I'm guessing they will have a way), or will they need to flash an Orange rom and thus remove the root when that happens? If I have no choice, who shall I contact Orange or HTC? If repair under warranty is unlikely I have insurance so luckily I am covered.
Any advice is welcome. Going to pop out for a bit to calm down my annoyance but will be online again later.
Simon.
Bump.
Will be returning via Phones4U today, unless anyone can come up with a last minute suggestion.
What errors do you get if you connect via USB and:
adb reboot recovery
...?
Did you run an undervolted/overvolted/overclocked ROM? If it wasn't stable, that will mess your phone up. Qualcomm can easily trace that, Orange can't, unless they refer back to them.
And yes, they will be able to tell if a device is still rooted. Not if you undo it with your stock RUU flash though.
------------------------------
- Sent via HTC Desire -
I get the CID error if I try to run an RUU.
I can't get into recovery and if I try to connect the phone using unrevoked/desire downgrade/adb through the command line it either says device not connected or please connect the device.
It wasn't under or over-volted.
Si Pie said:
I have a rooted Desire on Orange UK and running LeeDroid. I have my main SD card and a spare (the spare is used for flashing any roms etc.). I've made both goldcards.
Recently I've had problems with my phone rebooting randomly and today it did the same (been meaning to get in touch with HTC for a motherboard replacement which I've read fixes it). Sometimes when this happens it gets stuck on the white HTC logo and the solution is to pull the battery and then wait a bit and turn on and then it's fine. However today I did just that and now I can't boot into the OS or recovery modes.
I had a generic RUU that I used to downgrade my bootloader previously so I thought running that to flash back to a generic rom would at least get me back to a starting position. However I'm getting the CID error running that, using both goldcards. This would suggest to me the goldcards aren't properly working now!
Obviously not being able to get into anything other than bootloader/fastboot I cannot connect via adb and I also can't attempt to remake a goldcard. The ideal solution would be to get it into recovery somehow just so I can re-flash a rom.
If my phone is buggered then will Orange/HTC be able to tell if it's rooted (I'm guessing they will have a way), or will they need to flash an Orange rom and thus remove the root when that happens? If I have no choice, who shall I contact Orange or HTC? If repair under warranty is unlikely I have insurance so luckily I am covered.
Any advice is welcome. Going to pop out for a bit to calm down my annoyance but will be online again later.
Simon.
Click to expand...
Click to collapse
the creating golden card is now obsoleted method. It better, that you use unrevoked method to make new HDBOOT from www.unrevoked.com with following instructions. You can root easy and do everything you need only on rooted phone. I will reccomend also and make S-Off for full access in your phone. Everything in one place - http://forum.xda-developers.com/showthread.php?t=809328
Enjoy!
Thanks both.
I can't use unrevoked it says please connect the device.
Si Pie said:
Thanks both.
I can't use unrevoked it says please connect the device.
Click to expand...
Click to collapse
it means, the drivers are not installed. you can take it from
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
and you must read faq http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
I've used unrevoked before without issue. Tried re-installing the drivers and it didn't work.
Is it because I can only get into fastboot/bootloader?
Si Pie said:
I've used unrevoked before without issue. Tried re-installing the drivers and it didn't work.
Is it because I can only get into fastboot/bootloader?
Click to expand...
Click to collapse
Nope. Unrevoked will work if your PC can see the phone. So you have a connection error caused either by a incomplete/faulty setup on the PC, or with your USB attachment (cable/connectors/ports).
------------------------------
- Sent via HTC Desire -
Thanks for everyone's help. I don't know why Unrevoked could not see the phone then. Had ensured the drivers were installed correctly in device manager etc.
I also have no idea why I would be getting CID failure when this has never caused me a problem previously. My suspicion is a hardware fault so I've sent to HTC for repair.
Got my phone back from HTC today, motherboard replaced
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
You need to ask in the m7 sections. This is the m8 area. What rom was it running? . I have a couple things to try if it's a Verizon one.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
maybe best to see if you can unlock it via HTC Dev(as u are in fastboot mode)
Then install custom recovery, full wipe and flash a new rom via adb sideload, that will give you the system back and it should boot.
m7misery said:
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF.
.
Click to expand...
Click to collapse
This is false. RUU is designed to run on stock devices and will run just fine with S-on or S-off as long as you are running the correct RUU for your version (and also the RUU number needs to be equal or greater than what is on the phone, you can't "downgrade" while S-on).
But as mentioned previously, this forum section is for the M8 as clearly noted in the forum title. You need to get advice in the M7 forum, as advice given here (applicable to the M8) can be incorrect or even harmful to your device.
Right, so I wanted to install an OTA update on my rooted EE HTC M8. I followed this guide: "Unbrick/Unroot/Restore HTC One M8 to Stock 4.4.4!" on youtube (won't let me post links yet) and after flashing back to a stock recovery and unrooting the phone through SuperSU I attempted to install the OTA update.
I don't know if I did something wrong or the guide just sucked, but now it gets stuck on the boot screen every time. I can still access the bootloader and get into the stock recovery, but wiping cache/system restore doesn't help, I can't flash anything through adb as it doesn't detect my device and trying any commands just hangs on 'waiting on device'. My only option seems to be flashing an 0P6BIMG.zip from the bootloader by putting it on my SD card, but I can't seem to find a RUU that will work with my ORANG001 CID or 4.19.61.3 OS.
I tried a few when I didn't know RUUs were location/carrier specific and it would load the image fine then reboot but still get stuck on boot screen, and I tried this RUU: "0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401. 10_Radio_1.25.214500021.06G_20.68.4196t.01_F_relea se_417809_signed" but I just get a 'Device halted due to Large Image update fail!' error.
I can't find any advice online specific to my issue, and my tech savvy mate who's also owned an m8 isn't available to help out at the moment, so I thought someone on here might be able to help with my situation. I'm going to take it into an EE store tomorrow but I don't know if they will be able to help.
Check this out
lavin80r said:
Right, so I wanted to install an OTA update on my rooted EE HTC M8. I followed this guide: "Unbrick/Unroot/Restore HTC One M8 to Stock 4.4.4!" on youtube (won't let me post links yet) and after flashing back to a stock recovery and unrooting the phone through SuperSU I attempted to install the OTA update.
I don't know if I did something wrong or the guide just sucked, but now it gets stuck on the boot screen every time. I can still access the bootloader and get into the stock recovery, but wiping cache/system restore doesn't help, I can't flash anything through adb as it doesn't detect my device and trying any commands just hangs on 'waiting on device'. My only option seems to be flashing an 0P6BIMG.zip from the bootloader by putting it on my SD card, but I can't seem to find a RUU that will work with my ORANG001 CID or 4.19.61.3 OS.
I tried a few when I didn't know RUUs were location/carrier specific and it would load the image fine then reboot but still get stuck on boot screen, and I tried this RUU: "0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401. 10_Radio_1.25.214500021.06G_20.68.4196t.01_F_relea se_417809_signed" but I just get a 'Device halted due to Large Image update fail!' error.
I can't find any advice online specific to my issue, and my tech savvy mate who's also owned an m8 isn't available to help out at the moment, so I thought someone on here might be able to help with my situation. I'm going to take it into an EE store tomorrow but I don't know if they will be able to help.
Click to expand...
Click to collapse
Chek this thread: http://forum.xda-developers.com/showthread.php?t=2759905 post 9 and 27, I had a similar issue and it worked, once you get the bootloader mode you can flash a RUU zip file
Hi,
So ive spent at least a total of 12hours on this phone trying to unlock it. - im only posting this, in the hope to spare a lot of other peoples time by sharing my experience and hoping to get some advice.
I have submitted an unlock via IMEI to 3 different servers to retrieve the factory unlock code, and all codes ive got are not unlocking the phone.
This phone belongs to a customer of mine, and had started into the venture of unlocking it alternatively as they wanted the phone unlocked some how, i had explained its possible with root and custom roms etc.
So i started my venture and have come to very little success.
I had downloaded TWRP recovery and unlocked bootloader, and once it was installed and flashed with fastboot, my phone would not turn on. - i had used HTC M8 files, and not HTC M8s files - i was stuck in M8 recovery. - i had used these files as any search for HTC M8s would fill up with just the M8 edition.
Endless playing with different combinations of buttons, just holding the power button for a long time got the phone to boot up. (if i left the phone off, and had it charging, the charging logo would show up on a "bootloop" and would not power up, back to the "bricked" mode it was in. -unplug charger and playing with combinations of buttons to get back on)
(If your in this state and panicking, dont panic, your phone is stuck in m8 recovery that i flashed and holding power should kick you out of it, make sure your usb isnt connected)
Enter fastboot mode holding volume down and power and flash htc m8s TWRP-recovery solved all issues with recovery loops and boot errors.
It took me a long time to find the M8s TWRP and recovery files, but on flashing them, my phone booted into M8s recovery and i was able to install SuperUser and root phone.
I was then at the situation of turning the S-On, to S-Off. - More problems.
The tutorial i followed was suggesting to use firewater, and after endless rebooting and downloading SDK files etc, couldnt get S-OFF as i was getting error PID file format only. - HTC has patched this method - time to move on......... FIREWATER DOES NOT WORK.
I was trying to avoid the situation of paying any more to unlock, so giving up had turned to the Sunshine S-OFF tool. This costs $25, and is a simple android app to turn rooted devices from s-On to s-OFF. - I installed and downloaded it to find HTC M8s is not compatible.
A message to all HTC M8s Owners looking to unlock there device for Free, or as a last resort if factory unlock is not available. ---> As of this date, its not possible to turn S-OFF without a "javacard" which is a device to plug into sd slot and magically turns it off.... sorry. - Thus not possible to unlock via root.
If there is a solution, please do let me know, this phone has eaten me up. I have to go to the service provider and try get the code from them.
You talking about sim unlocking ? Even with s-off you can't just sim unlock it, even with a custom rom you can't just sim unlock it.
Firewater is offline now for over a year already and if sunshine isn't compatible there is just no (affordable) way to s-off.
All those methods are not working anymore. You really need a working code or help from the carrier.
Bootloader unlocking and running custom roms or rooted stock is totally different to carrier unlocking a device. And also would like to mention that the M8s is not very supported with custom roms. There are about 2 roms i know of.
And make absolutely sure that you know what you are doing and create a pure STOCK NANDROID BACKUP (one before you pushed root) so you are able to bring the device back to stock for future ota updates.
You can not update a rooted rom (also not a stock one) once rooted the system is changed and can't be undone so you definitely need a "never rooted stock rom"
And the needed files are easily to find actually because there is a dedicated thread here for the M8s.
http://forum.xda-developers.com/showthread.php?t=3114245
Solved.
I flashed the 3.35.401.12 RUU according to Flippy498's guide
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698 (Thread #5)
All the Phone data was wiped during the process.
shivadow and computerslayer thanks again for your help
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32
You need to run the ruu.exe but I don't know if one exists for your version. You can flash any 3.35.401.xx ruu but those that aren't "xx" must match. Not sure you can flash a signed zip in s-on state..
If the ruu.exe doesn't exist then you'll either have to wait for it to be released or rtm for repair.
There is no actual way to know exactly how buggered the phone is because it died in the middle of a flash process. It is very possible it died just as it was flashing recovery, explaining why there isn't one, but I wouldn't like to bet money on it, or it being recoverable at all.
Beamed in by telepathy.
shimshi said:
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32
Click to expand...
Click to collapse
You've access to download mode, so you should be able to use the SD card method of applying the matching RUU. Check out the readme thread for instructions and the necessary file.
Thanks for your help shivadow and computerslayer,
I will look at the RUU method and try to learn more about it and replay if it worked or not.
I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?
jewels76 said:
I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?
Click to expand...
Click to collapse
If you unlocked bootloader, the warranty is void anyway.
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".
albaniax said:
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".
Click to expand...
Click to collapse
Those are two different methods: The SD card method and the htc_fastboot method (which requires a PC).
And it's actually the other way round. The htc_fastboot method requires a locked or at least re-locked bootloader whereas the SD card method can be used with an unlocked bootloader, as well.