Hello,
First of all, I just created an account to get help with a phone I have. I cannot seem to fix it, I contacted HTC support and the only option left is to return it to them for a fee to fix.
Details:
SIM unlocked AT&T HTC one m9
Issue:
After trying to update to marshmallow using the ruu 3.38.502.12 which is for AT&T phones, my phone is now bricked. There was an issue in the middle of updating, so my phone tried to revert back to the old recovery. During this step my phone glitched out and rebooted itself, now its stuck in a boot loop with no indication of a recovery or any OS.
I tried to redo the ruu update and I get an error saying my battery level is less than the % required, yet my phone screen is showing 100% battery.
I also tried placing the .zip file on a SD card and using "download" boot method to flash the rom "I get error saying no OS present"
I also tried fastboot but my phone isn't picked up by fastboot and sticks at waiting for device.
Any method that requires me to turn on debugging mode is useless because I cannot access the OS to turn this on.
Anyone have any other suggestions then what I've tried? Or is the only thing I can do is send it back to HTC and hope they can reflash the phone?
Thanks to all for the help,
Related
I bought a used Sprint HTC EVO 3D in ebay, knowing it had a boot loop problem as described by the seller. Before buying, I researched to see if I can possibly fix the issue, and at that time I saw a few ways to do it. Unfortunately, now that I have the phone and tried those ways, my phone is still stuck in a boot loop.
This is what I've done so far:
1) Received the phone w/ HBOOT 1.5 (unlocked using HTC method).
2) I tried to flash TWRP 2.1.1, TWRP 1.0.3, ClockWork Mod 4.0.1.4, ClockWork Mod 5.8.0.1, and 4EXT RC3. The flashing seems to work as indicated by fastboot (it says OKAY after flashing).
3) I tried launching the recovery via fastboot command line and also tried launching recovery via power cycle while holding volume button down. Neither method allowed me to get to recovery. I would see the HTC logo, and then boot loop.
Other things I've tried:
1) Relock the phone.
2) Run the latest RUU (Sprint 2.17.651.5). I also tried the PG86IMG version. Flashing seems to succeed either way. But when I reboot, boot loop is still there. ROM doesn't boot.
Other things I've tried:
1) With the relocked phone, I did the HBOOT 1.4 downgrade and was successful downgrading.
2) I ran the RUU (Sprint 1.13.651.7) after the successful downgrade as described in the downgrade method so that I can try the Revolutionary S-OFF if my ROM boots.
3) The RUU succeeds, but the phone is still stuck in boot loop. ROM doesn't boot.
Again, the only thing that seems to work is fastboot commands. Adb commands don't work since the ROM doesn't even boot up.
I'm not sure if there's anything else I can do with the phone. I'm thinking now this may be a hardware issue. But before I send it in to HTC, I'd like to get opinions from the experts out there to see if there's anything else I can try.
Thanks!!!
none
Try to plug it into your computer, open a command prompt and type.
"adb reboot recovery"
Just like you see it, that should get you into recovery so you can flash a new rom onto it. And if you can swing it, by a new one next time lol
As stated above, adb commands won't work since you need a bootable ROM in the first place.. My EVO 3d reboots right after the first HTC logo pops up.. I've also tried launching recovery via fastboot command line and via power cycle and holding volume down button and selecting recovery. Both methods just reboots the phone and reboots over and over til I pull the battery out.
exact same problems, any help?
i have the exact same problems as Alpine Man.
tired everything, and i was hoping that if i downgraded to hboot 1.4, everything would be ok in terms of bootloops, but no =[
Can anyone shed light on this, software issue? hardware issue?
Anyone have a solution for this? or just send it to htc/
Have u tried installing new custom Rom?
I can't remember the creator's name but the file name is EVO 3d v2. I used the file to fix my bootloop. It's actual use is to relock ur bootloader back and it also install the ruu file. But it worked for me.
It might help u too. Maybe give a shot.
Sent from my AWESOME HTC EVO 3D. Click THANKS if u find my post is helpful.
I tried everything... And nothing fixed it. I finally sent it to HTC. They replaced the motherboard and all is well again.
i've read almost every guide availble regarding bootloop problems. my sister's evo 3d has no problems whatsoever. mine won't boot for anything!! have to go to work now but i will try it when i get home. if that doesn't work i'll probably have to send it in too.
alpineman - does the 1 year manufacturer warranty transfer over when you buy the phone used off ebay? i got my phone in great condition on ebay, with no mention of bootloop problems =[ . i'm not with sprint. i bought the phone hoping to flash it to metro. do i call htc instead of sprint? i'm not really sure how this warranty thing works.
any help is greatly appreciated thanks!
HTC did not ask for receipt, proof of ownership, or whether I had an active Sprint contract. They went by the serial number to determine warranty status. This is the 2nd HTC phone I had to do this with. Both times, no warranty problems whatsoever.
that's great! if all else fails, i'll give them a call on monday. thanks for the help!
good news! Come came back from HTC with new motherboard, boots up nicely now. I haven't done anything to it yet.
Bad new: the battery cover doesn't sit nice and flush anymore, its kinda crooked
It's sooo minor i almost don't wanna bother with HTC, but physically it was mint when I sent it in.
Need help
Hi can any one help, I am trying to gain S-Off on my Evo 3D, hboot 1.49.0018, I have Htc sync driver (Sync Un Installed)
adb devices command works fiine and gives me the serial number
but any other command with adb or fastboot it stucks on waiting for device.
Please Please Help me.
Regards,
Hello everyone.
I normally don't post here but now I'm sort of desperate right now.
A couple of months ago I changed my stock HTC rom to Cyanogenmod 10, reason for this is that I used to own a Galaxy S2, with which I also ran a version of CM.
Now everything went fine as it should but today the disaster strikes!
I wanted to revert my phone back to the stock rom because I seem to like HTC Sense more than I initially thought.
I basically followed a guide that gave a detailed instruction about how to revert it. I can't post the link here since it prevents me from creating this topic.
However at step 9 I got a 155 error leaving the phone at the silver HTC letters after this the phone just kept rebooting itself into fastboot mode.
A sidenote: I used the Europe RUU version .
Since I'm from Europe and I bought the phone in my country the RUU file should have been correct.
At this point I unlocked the boatloader again and by starting the phone, the CM logo appeared again but now it stays in the bootloop.
I already tried to wipe all data/factory reset but this doesn't work either. I also tried to re-flash CM again by using fastboot commands but this also didn't work.
It also seems that the phone doesn't recognize the internal storage, I can't reach it in the recovery mode.
To wrap it all up the situation is as followed:
-The phone is stuck at the CM animation loading screen
- I can enter fastboot mode
- I can enter the recovery mode
Is there anything I can possible do to restore the phone to factory defaults?
Any help is appreciated!
DISCLAIMER: I'm completely new to Rooting devices.
My phone is an HTC One M9 running Marshmallow 6.0.1 on Telus.
I attempted to root my device recently to try and solve an unrelated issue that factory reset could not, which is no longer important.
I followed this guide and got all the way up to "Power off your device. Now, to boot into recovery mode.", which I can get into TWRP no problem. However, I cannot push "SuperSU" as it comes up as "device not found"(ADB drivers not installed? Though I got this far somehow). I thought this wasn't a big problem and I could install it later.
Now I'm stuck in infinite boot. The HTC logo shows up, and after a bit it changes and does the animation into the logo for the HTC One. Then it's stuck like this(bootloop?), the longest I've tried being 40 minutes. I can do a fake battery removal and then access the "download" bootloader, regular bootloader, and the recovery (TWRP) no problem still.
If I manage to get SuperSU installed will this solve my problem? Or are they separate issues? Can I flash another image to at least go back to "stock"?
I no longer have any idea what to do. Any and all help or suggestions are appreciated and I'll provide whatever information I can manage.
Further information: I have wiped the appropriate caches(dalvik included) as well as factory reset through TWRP in different instances. I've even downloaded the stock recovery image and wiped again. I simply fail to see what the issue is.
Edit: Managed to get SuperSU installed. I don't know what was different this time. Exactly how many times is it supposed to reboot on its own until it's done? Because it's been restarting for over 20 minutes now.
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
Hello,
My phone ran out of battery a few hours ago. I charged it, but when it boots it gets stuck at the htc logo. The same thing happened to me a few months ago, but after restarting it 2 or 3 times it booted just fine. This time though, it won't get pasted it no matter how many times I reboot it. After trying all the tricks that I found on google, I resorted to do a factory reset. I should have never done that, it didn't fix anything but it did turn off usb debugging by disabling developer mode. So it essentially made sure that I can't fix it anymore. I can't do anything from my pc because my bootloader is locked and I need developer mode enabled to unlock it with fastboot. In recovery mode I get a red triangle with an exclamation mark but I can get to the options to update via sd card. For a second I thought that I found a way to reinstall the rom via the sd but of course they had to make sure that it doesn't work because the zip failed the signature authentication and the signature authentication can't be disabled with a locked bootloader.
So is there anything that I could try or has HTC made my phone so secure that I actually have to buy a new one instead of being able to fix it?
Any advise is more than welcome because right now my phone is really close to meet my friend the hammer.
Thank you