Every 30 seconds or so, right as the phone seems to be fully loaded, I get the powering down message and it reboots. Every time like clock work.
Tries booting into recovery but every time I select Recovery from Fastboot it just does a normal boot.
I am rooted and haven't installed the newest OTA yet.
Sounds like a hardware problem. I suggest to take it to a Verizon store.
My guess is that the OTA update got pushed to your phone and you inadvertently took it, which is causing a boot loop.
There's no recovery if you rooted; the phone just boots with read/write access.
Look at the HouseOfMoto thread for info on flashing back to stock (images for 12.15.15 are now available), then re-root.
I'm still on 12.7.7 so it shouldn't be the OTA
Yes it should/would. You don't have a recovery, therefore you CAN'T upgrade, which is the reason you are still on older firmware
Sent from Droid Maxx
rmoney said:
Every 30 seconds or so, right as the phone seems to be fully loaded, I get the powering down message and it reboots. Every time like clock work.
Tries booting into recovery but every time I select Recovery from Fastboot it just does a normal boot.
I am rooted and haven't installed the newest OTA yet.
Click to expand...
Click to collapse
The same thing happens to me, have you found a solution?
Related
I have a p5113 and it is running 4.2.2 it is a friends. It turns on all the way to the homescreen for about 30 seconds. Then it reboots. I have gotten into recovery and it lets me wipe data factory reset. Then when I go to reboot it shows an error below the android and there has been no data wipe when it reboots. and reboots and reboots.........It also says NO COMMAND when booting recovery below the android. OH, I also tried flashing another stock recovery. Did not fix issue with recovery.
I have gotten into download mode and tried to cf root. Doesnt work, no recovery. Still same as above just goes to stock with no command written at bottom then error when you go to reboot it. Tried both versions of CWM and TWRP Odin files. DONT WORK. Tried to flash recovery by zip and get signature verification failure.
I figured oh, I will do what I always do to tablets try and reinstall the firmware. Which is the 4.2.2 firmware I go ahead and odin it, everything looks fine, it did take way too long like an hour and half. Passes, reboots, same operating system same data didnt change a thing! Still rebooting still recovery errors. Tried to downgrade to ICS and it passed after an hour and a half of slow odining NOTHING again same story as JB didnt change anything.
I have noticed that there is an avg in apps. I never get enough time to uninstall it. It always reboots before I can get to it. ANY HELP IS APPRECIATED.
jhr5474 said:
I have a p5113 and it is running 4.2.2 it is a friends. It turns on all the way to the homescreen for about 30 seconds. Then it reboots. I have gotten into recovery and it lets me wipe data factory reset. Then when I go to reboot it shows an error below the android and there has been no data wipe when it reboots. and reboots and reboots.........It also says NO COMMAND when booting recovery below the android. OH, I also tried flashing another stock recovery. Did not fix issue with recovery.
I have gotten into download mode and tried to cf root. Doesnt work, no recovery. Still same as above just goes to stock with no command written at bottom then error when you go to reboot it. Tried both versions of CWM and TWRP Odin files. DONT WORK. Tried to flash recovery by zip and get signature verification failure.
I figured oh, I will do what I always do to tablets try and reinstall the firmware. Which is the 4.2.2 firmware I go ahead and odin it, everything looks fine, it did take way too long like an hour and half. Passes, reboots, same operating system same data didnt change a thing! Still rebooting still recovery errors. Tried to downgrade to ICS and it passed after an hour and a half of slow odining NOTHING again same story as JB didnt change anything.
I have noticed that there is an avg in apps. I never get enough time to uninstall it. It always reboots before I can get to it. ANY HELP IS APPRECIATED.
Click to expand...
Click to collapse
so you wanna say that your tab is in bootloop
if that then please revert to stock rom
also if you are not able to do this then i have to say that your tab is bricked
try triangle away or take it to customer care
yep its
aditya rathee said:
so you wanna say that your tab is in bootloop
if that then please revert to stock rom
also if you are not able to do this then i have to say that your tab is bricked
try triangle away or take it to customer care
Click to expand...
Click to collapse
not a brick and I am on stock if you would have read the OP you would know that. I have had a brick before the definition of a brick is a device that does not turn on. I have flashed many tabs with stock and customs. Thanks for the great advice but I am a member of XDA and I like to do things myself or with the help of others in my community. I REFUSE TO TAKE ANY ANDROID DEVICE TO CUSTOMER CARE THAT STILL TURNS ON>
jhr5474 said:
not a brick and I am on stock if you would have read the OP you would know that. I have had a brick before the definition of a brick is a device that does not turn on. I have flashed many tabs with stock and customs. Thanks for the great advice but I am a member of XDA and I like to do things myself or with the help of others in my community. I REFUSE TO TAKE ANY ANDROID DEVICE TO CUSTOMER CARE THAT STILL TURNS ON>
Click to expand...
Click to collapse
i like your confidence brother but i was just helping you
also with your threads title in thought you were still having bootloop
also boot loop mainly happens when system files interfere with each other and result in instability during boot and crashes also it is not always necessary that in boot loop device would not turn on as you said earlier
i have seen boot loop on my tab even during charging animation as it was off it was due to use of flashing scripts that conflicted with each other
Okay, so just today I was looking through some articles and saw that Android 4.4.4 was able to be downloaded for the Moto G, I have a rooted Moto G, so I know that I can't install the OTA updates without reverting back to stock.
So it was early in the morning, I was still tired and not thinking strait; and I forgot that I couldn't install the OTA updates without reverting; So I made an idiotic mistake and used the settings update method to download the new version..... so now I am stuck in a boot loop because when ever I get to the Clockworkmod recovery, it says it can't complete it and it reboots my phone. Then the phone detects the phone didn't update and it goes into recovery. This just keeps happening over, and over, and over again,
See, the thing is, I would revert back to the stock, but I can't install the stock onto the internal SD because the phone reboots before I can actually get the stock zip onto the phone... so I'm stuck at this point, and I really don't know what to do... and I really don't think there is much I can do at this point.
Here Is My Phone Info:
Model: XT1031
Clockworkmod Recovery Version: v6.0.4.7
Can you turn off the phone with the power button and then boot in to recovery?
If that works try deleting the update zip from /cache directory with cwm.
meekrawb said:
Can you turn off the phone with the power button and then boot in to recovery?
If that works try deleting the update zip from /cache directory with cwm.
Click to expand...
Click to collapse
I've already tried this, It hasn't worked the three times I've done it. I have got it to stop rebooting, and I've got it to the original recovery. The 4.4.4 update isn't showing up anymore though. My battery is always at 1% battery now too.... so now I have another problem.
xLOLxTSNOOPS said:
I've already tried this, It hasn't worked the three times I've done it. I have got it to stop rebooting, and I've got it to the original recovery. The 4.4.4 update isn't showing up anymore though. My battery is always at 1% battery now too.... so now I have another problem.
Click to expand...
Click to collapse
Leave it plugged in for a few hours and then fastboot flash the stock firmware for your model number.
Unless someone else knows an easier way to get you going.
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
morr22066 said:
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
Click to expand...
Click to collapse
I had tried everything I could think of and it appeared that there was a partition problem. The phone continued to shut down and would only stay on while connected to the PC. If it were a PC I would reformat and re-partition the drive but I did not want to risk a permanent brick by messing with it.
So, as a last ditch effort to try and get my phone functioning again I let it download and install system updates. The phone is now working again, it has not shut down at all and there have been no warning messages about cool down mode.
BUT, I am now on "4.4.4, SU-5-24, build 23.3.24 dated 10-27-14. Since my boot loader is unlocked I flashed TWRP but it would not not accept Super SU zip so I am no longer rooted.
I finished reading up on it in the forums and realize I am pretty much screwed as far as root goes. But at this point I don't even care anymore. I just need to get the phone functioning correctly.
*So, I am still having the problem with flashing stock and getting the "red" letter message after system image boots saying "sp space not enough". So long as it is hooked up to the computer it stays on and if it is downloading or installing an update it stays on and I never get a warning about cool down mode and it does not shut off, but once I disconnect from the computer it starts all over again. The phone boots up but at random intervals it still either gets a pop up message saying that it has gone into "cool down mode" or it shuts off. It is not doing it as often as before, but it is still doing it. Does anyone have any suggestions on whats causing it or how to fix it? It sounds like a software / firmware issue but I am not sure how to fix it.
*Update. The phone is still not functioning correctly. At times it will appear to work fine for hours with frequent to heavy use at times then suddenly it will start acting up, the phone will shut down randomly and when it reboots some of my settings have changed. The temperature is usually pretty low but once in a while after a shut down I will check the temp when I'm able to reboot it and it will be high. When it shuts down like that I usually have trouble getting it to boot up again unless I plug in the factory cable, either in the PC or just the wall charge then it seems to boot up fine and I can even reboot it but once it shuts itself down it doesn't want to start again unless I use the factory cable.
It really does sound like a software / firmware / partition problem but after multiple attempts to flash the firmware with RSD I continue to get the same error message at the end of the system flash and the phone continues to have problems. Does anyone have any suggestions?
Got me an xt1080 which I'm trying to restore to stock, and in both House of Motor and RSDlite 6.2.4 at some point during the system partition flash 'so space is not enough' as well. The phone is in perpetual bootloop, unless I use a 'Factory/power' cord and starting up in fastboot (eventually). Tried both 1FF and CFC fxz files, no luck.
Hi, I've rooted and had a custom recovery on my MotoG. It was on 5.0.2 (still is) and since it keeps bugging me about updating to 5.1 I decided to give it a go.
Obviously that wasn't going to work and well it kept rebooting. So I got the MotoToolAioV3, got my USB debugging on and well tried to flash the stock recovery (JellyBean). I got a few lines of text and everything seemed fine. Then I decided to boot and download the update. Once downloaded it told me it would need to reboot and it might take 30 minutes for everything to be done. So I let it do it's thing and after about 5 minutes my phone was booted again. And then it began it's endless cycle of rebooting.
So since that wasn't quite what I had in mind I tried to go into my recovery again (I think I wiped my cache last time that happened), but instead of going into recovery it just booted into well normal boot. I tried flashing a custom twrp2.6.3.3 recovery and from there on I don't remember what I exactly did anymore. I flashed both the normal and the custom rom a couple of times and every time I tried to enter the recovery it would just boot normally. Also my phone is still on 5.0.2. But the endless rebooting has stopped and the phone seems to be working like before any fiddling with it today. Except that I can't go into my recovery anymore since it'll just boot.
Anyone know how I can get into my recovery and how what I should do to get to 5.1?
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
gabeblack said:
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
Click to expand...
Click to collapse
You need to clear the cache after flashing to get out of the boot loop.
Use the download key combo to restart. As soon as the screen goes black move to Volume up+home+power.
In the recovery menu choose clear/ Wipe cache, then choose reboot.
I apologize for not updating this thread before when it was still recent. The fact is that I didn't manage to fix my phone; clearing the cache after flashing did nothing to stop the loop.
I ended up taking the phone to the people who have fixed it in the past and after more than one month, they gave up. So I got my phone back and I want to try to give it another go before I just sell it for parts.
Unfortunately, my phone has come back even worse. Now it has no Recovery Menu to speak of, at least none that I can access; after a few seconds of the blue text on the top saying that it's entering recovery mode, it then proceeds to a blue screen saying: "Security Error: This phone has been flashed with unauthorized software and is locked.". I can still access Download Mode.
I have attempted flashing a few firmwares that I believe should have worked with my SM-G930U. Odin listed the attempts as "pass" and, after restarting and going back to the Download screen, it says the binary is Official. However, after trying to restart the phone normally, it starts displaying the blue screen again, and then, after going to Download mode, the binary is reverted to "Custom".
I believe right now the order of the day is to get the recovery menu to work again so I can do all the cache cleaning that seems to be required after flashing firmware. Any ideas at all on how I should proceed? Is there something specific I should download to fix the recovery menu?
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Drunkpilot said:
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Click to expand...
Click to collapse
Never rooted, was using the phone legit before it froze and entered boot loop. I flashed all 4 files, multiple times.
Someone tried fixing my phone a few days after I replied to this thread and some progress seems to have been made, but now the phone cannot get past a black screen with a "SBL Error! rdx_init!" in red text, and "upload mode" in yellow text. Still cannot access Recovery Mode, but Download Mode still works.
I did a little Googling on rdx_init errors and it seems I need a firmware dump from another G930U or something like that...any ideas on how I can proceed?
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
STA1NL3SS said:
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
Click to expand...
Click to collapse
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
gabeblack said:
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
Click to expand...
Click to collapse
I thought I had one in my phone, but I don't. If you look at the thread where you downloaded the Root_V12, you will see it. It's near the end of the thread somewhere.