i bought a phone off ebay in december. the phone was working well and then i decided to start installing different Roms on my phone. the phone was not s-off when i was installing these roms. about two weeks ago my phone just started to restart. it does not stay on for more than a minute before it restarts and i have no idea why it is happening. i would really appreciate any help in this matter because it is really frustrating. i think it is a software problem because the phone does not restart when it is in recovery mode or if it is in bootloader mode. if there is anything...anything at all you can do to help me it would be greatly appreciated.
hvagrantz said:
i bought a phone off ebay in december. the phone was working well and then i decided to start installing different Roms on my phone. the phone was not s-off when i was installing these roms. about two weeks ago my phone just started to restart. it does not stay on for more than a minute before it restarts and i have no idea why it is happening. i would really appreciate any help in this matter because it is really frustrating. i think it is a software problem because the phone does not restart when it is in recovery mode or if it is in bootloader mode. if there is anything...anything at all you can do to help me it would be greatly appreciated.
Click to expand...
Click to collapse
It would nice if you put a title to your thread instead of just [Q].
Anyway, if you suspect its a software problem, why not just flash back to stock and see if it persists? If the problem is still there, then it's most likely a hardware issue. I would replace the battery first.
Sorry about that .. it was the first time i posted something and wasn't really sure what to do. and i replaced the battery and the problem is still there .. i flashed and it still restarted. the weird thing is that if i'm doing something it doesn't restart. like if i'm using the phone as a hotspot it doesn't restart. but as soon as i stop it restarts. or if i'm using the camera it doesn't restart.
Did you wipe/format everything before flashing/flashing back to stock? Are you on CWM or EXT4? Some more details would be helpful.
yes i did that. i used superwipe. i am also 4EX and i S-off the device also. i tried installing the stock rom but it didnt work. it is confusing because once i am in recovery the phone stays on. but as soon as i turn it on it just keeps restarting. the phone boots up and then restarts.
I recently acquired a HTC DNA from a friend of mine, and it was working fine for the last week. I applied an OTA Verizon update, it was part of a 2 part update, and it downloaded a fairly hefty update (took about 30 minutes to download) and when I hit ok to restart the phone to apply the update, i am stuck on the HTC quietly brilliant screen. It wont load anything. I booted into recovery, wiped cache, and rebooted. Still got nothing. Booted back into recovery, wiped all data and did a factory reset, and rebooted, still stuck at the htc loading screen. After talking to both Verizon and HTC directly, they basically told me im on my own. I have read up about sidebooting a stock rom (RUU or something like that). I downloaded the file from a guide i was following but i cannot even get my computer to recognize the device when i plug it in via USB. The phone is not rooted, and i am just looking to get it back up and running. Please help.
Yes the phone was charged to greater than 30% when i applied the update. (it was on the charger actually, if that affects anything)
Anybody have a similar problem when applying verizon's OTA update, and how can i get my computer to recognize the device so I can get this thing back up and running.
Thanks
HTC One Tmo US fully stock and fully updated:
Ran the update. Verified it was all charged and, after it downloaded the update, left it and returned an hour or so later.
The phone was just sitting at the "HTC quietly brilliant". Left it for another hour and same thing. Did a factory reset and a cache reset. Still wont boot.
Instead of sending in the phone and getting a referb I want to root the device. However I can't turn fastboot off since the phone wont boot fully. Any ideas on how I can get the computer to see the phone so that I can request the token code to get my bootloader unlocked? Please HELP Thanks
Hi,
I've got Nexus 9 Stock, unrooted and bootloader locked, I got an OTA update, downloaded and installed it, when it rebooted the boot animation repeated endlessly.
It doesn't do part 2 of the boot animation it just repeats part 1, the four colored dots dancing around in circles..(is this a bootloop?)
I tried booting into safe mode without any success.
I tried wiping the cache partition but it didn't seem to do anything, it just stayed on 'formatting cache' for ages..
I rebooted, still endless boot animation. I rebooted back into fastboot and then recovery, when recovery loaded it had an error message 'cant mount cache partition'..
I tried wiping the cache partition again but got the same result, it stayed on 'formatting cache' for ages..
I rebooted back into recovery mode and tried 'formatting data/factory reset' and again it didn't seem to do anything, it just stayed on 'formatting data' for ages..
When I rebooted back into recovery it went straight back to where it left off: 'formatting data' without displaying the menu, and it stayed there for ages..
I figured, at the very least, recovery is buggered. So I tried flashing twrp via fastboot but I soon learned I can't do that while the bootloader is locked and I can't unlock the bootloader without enabling it in developer options which i can't get to because of the endless boot animation.
Help please, what should I do?
Wiping cache takes much longer on the N9 than any other device I've owned. Seriously, give it 30 minutes to one hour to complete wiping cache; don't power it off while it's doing that.
Once you're done wiping cache and rebooting you'll probably still be on 5.0.1. Your options are to wait for Google to release a new OTA, call HTC for an RMA, or flash the factory image (it can be done without overwriting user data).
I'm having the same problem. Actually, a bunch of us on the Nexus 9 product forums are having the problem too.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!categories/nexus/nexus-9
Google seems to replacing some and referring other people to HTC. I spoke with HTC this morning and they're having me send it to them for repair.
It's probably a nand problem!!
I hope this isn't the beginning of a #nexus9bricked
Nexus 7 tabs have been having hand failures for months now. Just search twitter for #nexus7bricked
+1 to the update bricking their Nexus 9
Yep mine got bricked when I installed the OTA update on a stock locked Nexus 9 this evening. Factory reset didn't fix the issue and I can't flash 5.0.1 because of Google's asinine developer options in Lollipop.
You can't flash even a signed factory image without selecting a Developer Option allowing for ADB to unlock the boot loader. So if you can't boot into the OS, you can't use Recovery to flash an image. Every Android device I've ever owned has been near indestructible because you could always refresh from recovery. Not so in Lollipop anymore, even with a stock device, unless you have the foresight to preemptively select the Developer Option allowing the boot loader to be unlocked.
I called HTC and they knew my problem almost before I got on the call given the call volume they're getting. They said I had two options: wait for an impending Google update fixing the issue coming sometime this weekend/early next week or RMA it to the repair center. They expect the update this weekend, and if I RMA it, that will take 7-10 business days and the repair center will simply be waiting for this imminent update fix from Google.
The rep could not explain to me how Google is going to issue an update to fix a boot loop on a device that can't be flashed, so I'll believe it when I see it. Part of me thinks they've been totally sandbagged with calls on this tonight and know they can't possibly repair/replace this many devices in a timely manner.
ksutherland91 said:
Yep mine got bricked when I installed the OTA update on a stock locked Nexus 9 this evening. Factory reset didn't fix the issue and I can't flash 5.0.1 because of Google's asinine developer options in Lollipop.
You can't flash even a signed factory image without selecting a Developer Option allowing for ADB to unlock the boot loader. So if you can't boot into the OS, you can't use Recovery to flash an image. Every Android device I've ever owned has been near indestructible because you could always refresh from recovery. Not so in Lollipop anymore, even with a stock device, unless you have the foresight to preemptively select the Developer Option allowing the boot loader to be unlocked.
I called HTC and they knew my problem almost before I got on the call given the call volume they're getting. They said I had two options: wait for an impending Google update fixing the issue coming sometime this weekend/early next week or RMA it to the repair center. They expect the update this weekend, and if I RMA it, that will take 7-10 business days and the repair center will simply be waiting for this imminent update fix from Google.
The rep could not explain to me how Google is going to issue an update to fix a boot loop on a device that can't be flashed, so I'll believe it when I see it. Part of me thinks they've been totally sandbagged with calls on this tonight and know they can't possibly repair/replace this many devices in a timely manner.
Click to expand...
Click to collapse
I also believe they are pretty busy with this issue. After 4 calls over 12 hours, I finally have an RMA and have the privilege of sending them my device to get repaired. Now, I have to wait 2 days for them to send me the shipping labels (they are covering shipping) and then 7-10 days for the repair.
What a PITA for a "premium" device.
Yeah they suggested I call back tomorrow or Saturday for updates on when this Google fix is coming about. The Nexus support agent I chatted with at Google says he's unaware of any impending update to fix this issue.
Right now I'm afraid I'm going to call HTC in a day or two and find out I have to send it in, and then I'll start the whole process 2 days later than I could have.
HTC live chat: guy said, that they repair using fastboot only. Imho, service command for flash on locked bootloader is present and hidden under OEM section.
Phone shop couldn't reinstall firmware. I'll sent it back to HTC to fix.
Meanwhile, I solved my problems by buying a new tablet - Galaxy Tab S 10.5 !
Thanks for all the replies, best of luck to everyone else
Now I can get back to wasting time and energy playing clash of clans hehe.
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,