I purchased the VZW Dev phone, using it for T-Mobile.
Rooted at some point, TWRP installed. I was using my old phone charger every now and then, but eventually the phone stopped recognizing it, forcing me to use the charger cable it came with. Come earlier this week, I see there's a software update out. Thinking it was Lollipop, I tried to install. Phone shut down, vibrated, refused to reboot without going through fastboot. So I turn the phone on through fastboot, the update says its been deferred, and then the phone shuts down by itself as if trying to update, and just vibrates.
I do a factory reset through TWRP, still have to turn on through fastboot, but the phone is working. I let the battery drain, charge to full, then try to update again. Same thing.
I plan to try flashing back to stock once Motorola gives me access to the file, but other than this, I'm stumped.
So you are trying to take an OTA with TWRP on your phone, rather than stock reocvery?
Yup, it will loop like that. You can NOT take an OTA update unless you have stock recovery on your phone.
Please see => http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
Problem is resolved. After flashing back to stock, the device still refused to power on without doing so through fastboot. By chance, I stumbled upon your post about flashing a stock LOGO.bin, @KidJoe. Forgot I was using one to bypass the rooted message.
Related
I have a VZW Dev Moto X, it is unlocked and rooted and I received the notification for the 4.4.4 update. I stupidly decided to install the update at work, without thinking twice about and not looking into it before doing so. Now the phone keeps restarting and going into TWRP and the update is not installing. When I boot the phone into Normal Powerup, it waits for everything to load up and then without warning reboots.
I cannot at this time flash FXZ on my phone, but I do need my phone throughout the day today. Is there a way to stop the phone from restarting? I have not done any actual updates, just told the phone update and restart.
chuda.pati09 said:
I have a VZW Dev Moto X, it is unlocked and rooted and I received the notification for the 4.4.4 update. I stupidly decided to install the update at work, without thinking twice about and not looking into it before doing so. Now the phone keeps restarting and going into TWRP and the update is not installing. When I boot the phone into Normal Powerup, it waits for everything to load up and then without warning reboots.
I cannot at this time flash FXZ on my phone, but I do need my phone throughout the day today. Is there a way to stop the phone from restarting? I have not done any actual updates, just told the phone update and restart.
Click to expand...
Click to collapse
Boot into TWRP, and clear your cache. It will stop rebooting.
You -cannot- install OTAs without first flashing STOCK RECOVERY back on (and un-doing any significant modifications to /system).
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Budee80 said:
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Click to expand...
Click to collapse
which twrp version do you have installed?
little123 said:
which twrp version do you have installed?
Click to expand...
Click to collapse
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Budee80 said:
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Click to expand...
Click to collapse
glad i could help with just a question
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
LiquidArrogance said:
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
Click to expand...
Click to collapse
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
muniz_ri said:
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
Click to expand...
Click to collapse
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Is there physical damage on the phone, thus why att didn't do the warranty?
Sent from my HTC One_M8 using Tapatalk
LiquidArrogance said:
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Click to expand...
Click to collapse
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
muniz_ri said:
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
Click to expand...
Click to collapse
No idea what just happened. I've been messing around throwing the kernel you recommended at it as well as the stock partitions. Kept getting back to boot loop but at one point it stuck out, said it was upgrading, optimizing apps, and now it's running. So weird.
I'm way too scared to do the factory reset at this point, though.
Thank you again for your help, I really appreciate it!
Edit: Unplugged the USB cable and it immediately shut off and went back into boot loop. Wow.
this sounds like a hardware problem.. i sent my phone to Samsung and they actually repaired it, it was the pba board, i had the same problem.. i flashed everything it needed to recover from a bootloop. and sometimes it would become non responsive. go to best buy and see what they tell you.
Sent from my UNROOTED SAMSUNG-SM-G900A on OF2
Update:
Thanks to everyone for their replies. I was able to get the phone to boot thanks to everyone's help. Did this by flashing kernel then partitions which would allow the phone to boot.
I finally figured out that the phone would only boot if plugged directly into a power source. As soon as I disconnected the power cable, it would send it right back into the boot loop. I ran some battery "repair" and "calibration" tools but these did not fix the issue. Whenever I would run a battery drain tool, the stress on the battery would cause the phone to shut down.
All of this led me to believe it was an issue with the battery. I held my wife's S4 battery to the contacts on the S5, and it works just fine, even disconnected, and even with the stress test on the battery.
SO -- I'm going to buy a new battery and see if this fixes my problems. I think I just had the perfect storm of battery issues coupled with firmware problems.
I'm pretty sure I know what caused the battery to go haywire. I work in a max security prison and have to leave my phone in the car all day. Outside temperatures regularly hit 105F+ during the summer, so who knows how hot it's getting in the car. Obviously I always leave the phone turned off, but I suspect the high temperatures caused the damage.
Going to try to find a new battery today. Will keep everyone posted! Thank you again for all of the replies.
I had the same issue and would just like to thank you for the files! They helped me unbrick my phone! Much appreciated.
I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.
I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!
Hello,
I fear my daughters european HTC Desire 510 is bricked. First of all, we have already given up on what is on the phone. So no worries if a solution means wiping EVERYTHING from the phone, as long as we can get it to start again.
For some unknown reason, possibly an update the phone went into an almost constant bootloop a month or so before christmas. It could eventually get to the login screen, after going in circles for anything between 20 mins and hours. So I thought I would try to tamper with it. I know how to get into the bootloader from rooting other phones, so I went there to try to reset the phone to the factory settings. The result was that the phone now wouldn't go there again. If I tried to do a second reset it went straight to boot, without any way to interrupt, same thing when trying to go into recovery, instant reboot in the blink of an eye.
What then happens when the phone reboots? It gets to the first screen, green HTC logo and "Powered by Android", it sits there for maybe 30 seconds, then it goes black, buzz and back to the previous HTC logo. And this goes on until the battery dies, I pull the battery or I quickly push the vol down and power buttons to go into HBOOT.
I usually don't give up this easily. I found another thread here on some european guy having trouble with his Desire 510, and one of the answers linked to a RUU for a european 510. So I thought, why not, I hadn't unlocked the bootloader yet. So I downloaded the RUU and tried to install it. It messed with me a little, aparently as expected, and then ran through the whole installation. Before the upgrade, well downgrade to be specific the OS was ver. 1.51.401.4 but now claims to be 1.51.401.1. Problem though is, absolutely no change in behaviour. I have restarted the phone after pulled the battery and waited for anything between seconds and an hour, and the phone does exactly the same thing. It happily goes into HBOOT but won't allow me to do a factory reset, nor will it allow me to access recovery.
It will allow me to access Fastboot though, so I thought, hmmm if I install ClockWorkMod or TWRP, maybe something will change. Since I'm more used to working with CWM I went down that road, went to htcdev.com, got the unlock code and unlocked the phone. It now says <<< UNLOCKED >>> and I ran the fastboot devices command, that happily returned some "CC4********7 fastboot". So I went ahead and installed CWM, the installation went all the way and in the end it happily stated that CWM was installed. But did that mean any difference, noooo. If I try to access either Recovery, that should start CWM or Factory reset and also Check smartsd, instant reboot. And I mean INSTANT. Fastboot works, as already stated. I can also get into Image CRC and Show barcode, but what good is that.
Any ideas. I'm beginning to think that something is physically broken inside the phone.