So I've had my htc one since september I bought it brand new and rooted it and put custom rom and unlocked bootloader. After a month I wanted to relock the bootloader and unroot it so I used the RUU. It worked for about a month then one day it just turned off and keeps rebooting itself. Sometimes when its off and i plug it in it starts to flash a red light on top then it just turned off. I have reinstalled the RUU many times but never worked. Its been like this since october sometimes it keeps rebooting and it actually turns on but its in safe mode. no music playin, no microphone, really fast battery drain. If someone can please help me it is the at&t version. I have also tried to factory reset it many times from the fastboot menu. thank you for reading
I've had that problem before on previous HTC devices. Unlock the boot loader and root eveeythinf/soff again. Forgot exactly how I fixed it but I know I had to root, soff, unlock boot loader again. Think it's whenever u relock the boot loader it messes things up.
Sent from the one and only HTC One
thanks ill try that out
Related
after i got the OTA update, the phone finished downloading and started the installation process, the phone rebooted into that screen with the 3 green arrows (2 circling and 1 down). i left the phone on that screen for more than an hour or some and that's it it's stuck on that screen.
i tried the pull out the battery and put it in again and when i boot the phone it goes back to that screen.
plus i'm not able to boot into hboot nor doing anything and when i plug the usb to a pc it wont detect it.
i have tried everything i know so far :s and still no luck .... i would be glad if anyone can help me.
not a single reply !!??
i should throw the phone from my window then
Is it HTC dev unlocked? You can't do an ota if its not completely stock.
e-zee said:
after i got the OTA update, the phone finished downloading and started the installation process, the phone rebooted into that screen with the 3 green arrows (2 circling and 1 down). i left the phone on that screen for more than an hour or some and that's it it's stuck on that screen.
i tried the pull out the battery and put it in again and when i boot the phone it goes back to that screen.
plus i'm not able to boot into hboot nor doing anything and when i plug the usb to a pc it wont detect it.
i have tried everything i know so far :s and still no luck .... i would be glad if anyone can help me.
Click to expand...
Click to collapse
e-zee said:
not a single reply !!??
i should throw the phone from my window then
Click to expand...
Click to collapse
You did not give enough information to even try to help you. As markj338 suggested, if you have modified your phone by unlocking the bootloader, flashing a custom recovery or rooted the phone, it will not apply the OTA successfully.
So what was the state of your phone before you attempted to run the OTA?
tpbklake said:
You did not give enough information to even try to help you. As markj338 suggested, if you have modified your phone by unlocking the bootloader, flashing a custom recovery or rooted the phone, it will not apply the OTA successfully.
So what was the state of your phone before you attempted to run the OTA?
Click to expand...
Click to collapse
it's perfectly stock. i have locked the bootloader and installed a stock RUU before checking any updates, and i told you how my story ended
e-zee said:
it's perfectly stock. i have locked the bootloader and installed a stock RUU before checking any updates, and i told you how my story ended
Click to expand...
Click to collapse
So we are clear, your phone was completely stock? Or was your bootloader unlocked and you locked it before checking for updates?
acme anvil said:
So we are clear, your phone was completely stock? Or was your bootloader unlocked and you locked it before checking for updates?
Click to expand...
Click to collapse
the bootloader was unlocked, i relocked it then installed an original RUU after that everything was working normal, i checked for updates so i got the OTA update, then installed it and then my phone stuck on that screen.
What method did you use to lock your bootloader?
thanks guys for everything, i found a store to fix my phone, and they fixed it with jtag box and now it's brand new.
Just flashed Android RevolutionHD on my Sprint HTC One and now I'm stuck looping onto the bootloader. None of the options work and I don't know what to do. Recently bought this phone and hoping to god I didn't just brick it, have never had any problems rooting or flashing in the past so idk if it is bricked, please help.
Jay227 said:
Just flashed Android RevolutionHD on my Sprint HTC One and now I'm stuck looping onto the bootloader. None of the options work and I don't know what to do. Recently bought this phone and hoping to god I didn't just brick it, have never had any problems rooting or flashing in the past so idk if it is bricked, please help.
Click to expand...
Click to collapse
Check this thread here:
http://forum.xda-developers.com/showthread.php?t=2411137
Jay227 said:
Just flashed Android RevolutionHD on my Sprint HTC One and now I'm stuck looping onto the bootloader. None of the options work and I don't know what to do. Recently bought this phone and hoping to god I didn't just brick it, have never had any problems rooting or flashing in the past so idk if it is bricked, please help.
Click to expand...
Click to collapse
For HTC One: International GSM/LTE (UL), International GSM (U), all U.S. carriers (apart from Sprint)
Next time I would suggest you flash only Sprint Roms. You need to RUU http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
device not found
Every time I go into adb or try to use the hasoon toolkit it tells me device not found. Bootloader is unlocked with s-on and htc drivers are installed. When I try to boot into recovery now it sits at the HTC quite brilliant screen for a few seconds then shuts down.
Just tried re-locking/re-unlocking the bootloader and was successful with that so the drivers are working and it seems to have some connection to adb.
I tried pushing a recovery through adb and it had sit for over 8 hours, went to work and let it sit trying, and still nothing happened. Adb is stuck on sending 'recovery' <7544 KB>... and saying nothing else.
Just tried it again and it worked instantly so now I have a recovery.
Problem solved, major thanks to Indirect for the assist.
Hello guys
So, here's the deal. Few months back, I messed up my One and got it stuck at the grey HTC Screen. Couldnt boot into system, because I guess there was no ROM on the device. Thanks to you guys here at XDA, I got the situation analyzed and took the device to an HTC Service Center who told me to get my motherboard replaced. That was way too costly, so I got it JTAGed. The device now boots into ROM, but it cant boot into the bootloader. So I cant unlock the bootloader, S-OFF, Root or anything.
I can only boot into ROM. Can anyone please explain why this is so and what can I do to get my bootloader and recovery back.
Any help will be greatly appreciated!
Thanks
Which methods are you using to get into the bootloaader ?
Seanie280672 said:
Which methods are you using to get into the bootloaader ?
Click to expand...
Click to collapse
Sorry for the late reply..i was out of town..
I tried adb and manually pressing power+down..but to no avail.
I figured it out in the end though...i dont know what happened but the device suddenly went into the bootloader one day and now its working fine.
I have a question..
My device has been jtagged. Its now bootloader locked, unrooted, s on.
Is it dangerous for me to try to unlock and s off and flash a new rom?
Can a device be flashed after its been jtagged? Im sorry I dont have much experience with jtag.
Thanks!
ALright, my previous m7 is sitting dead in forever bootloops... it's on the back burner until further notice.
so i got another one. stock all around. used. took the OTA for latest firmware and radios, exactly the same revision as the previous m7....
unlocked bootloader, flashed twrp, flashed good old cm11. worked good for a few weeks.
then i decided to try lineage 14/15. cm13, back and forth, over and a bout...
then running stabile in lineage14.1, i noticed i couldnt' make phone calls.
so i flashed back to cm11, LTE/4g shows up, data is good, but cannot make calls, cannot receive calls, same with text messages.
flashed back to the stock nandroid that the phone came with, same thing! only data, no voice/text.
so, in attempt to bring it back in for repair, i needed to relock the bootloader.
that's where it went ugly. it said relocked, tampered, and security warning, and i was unable to boot into anything else.
luckily i kept the unlock token ,and reissued an unlock, and it would let me boot into the rom again and the recovery, but i don't want to attempt to continue the RUU until i know exactly what steps are required.
i read the bootloader must be relocked before RUU, i also read if i was stuck where i was, in fastboot mode the RUU would still work, which it didnt..
help please!
thanks
Well, no one replied in time.
Asurion said it was covered under manufactures warranty. Zero deductible and a new HTC 10. And the old m7 was accepted tampered /unlocked.
Sent from my 2PS64 using Tapatalk
Wow, nice. I tried to help, but you got outside of my knowledge level. I'm really glad you got a 10. It's a really nice device.
I just got a new Mi A2 and, thanks to Amazon, it came on a very old version of Android.
I have done Original version -> November OTA -> March OTA (Pie) and now trying to do April. However, the phone boot loops every time it tries to install it. If I leave it for 20 minutes or so unpowered it will finally restart and report 'Couldn't Update'
I have enabled OEM unlock, but not done the actual unlock in fastboot - could this be the cause? Is there a way to manually skip April too and go straight to June?
Thanks for any help.
Did have the same problem after unlocking bootloader it finished the update , was strange as hell so I stay unlocked for any case.
anryl said:
Did have the same problem after unlocking bootloader it finished the update , was strange as hell so I stay unlocked for any case.
Click to expand...
Click to collapse
So do a full unlock before trying again? At the moment I don't have the boot loader unlocked, I've just enabled the OEM unlock so I could unlock in case needed.
I never wait so long always do the 3button restart and see what's going on but here I did the full unlock and then it worked. On my wife's pink a2 all went fine no unlock needed so it's strange.
Sigh. I thought all this nonsense wouldn't be needed on an Android One phone.
Will give it a week or so and then go down the full unlock and re-set up route.
FFS found the solution on one of the other myriad boot loop threads - take the sim cards out before restarting.
Good for u mine was without sim.
It's still flaky. Have to power it on manually two or three times after restart - it doesn't boot loop, it just doesn't boot.