Database Info

[Q] PLEASE HELP, Stuck in bootloop and no way out!

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

[Q] Trouble flashing Stock & Custom ROM's

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.

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster

napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.

Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-

So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.

SM-G920I Keeps shutting down and recovery is not seandroid enforcing

Hello everyone,
My Galaxy S6 G920I has started shutting down repetitively. I was on stock and not rooted. After it happened a few times I decided to hard reset it and delete cache but it would get stuck on starting apps screen etc. After many attempts the phone finally started the user's guide for logging in etc. I was getting crash errors for settings and other things. It finally went in only to start shutting down again. Seeing how the apps were crashing I thought that there might be an issue with the stock ROM so I decided to flash a new one. I was having trouble finding my specific so I went for another one found here. I couldn't flash it with ODIN because it was on a zip format so I flashed TWRP on the phone.
The error recovery is not seandroid enforcing is now showing on different versions of twrp (2.8, 3.0).
I can't flash any ROM now and the one found in the device keeps shutting it down.
I don't believe it is a hardware issue as the phone stays on without issues on download mode. Any help on what steps to follow next would be highly appreciated.

apostol96t said:
Hello everyone,
My Galaxy S6 G920I has started shutting down repetitively. I was on stock and not rooted. After it happened a few times I decided to hard reset it and delete cache but it would get stuck on starting apps screen etc. After many attempts the phone finally started the user's guide for logging in etc. I was getting crash errors for settings and other things. It finally went in only to start shutting down again. Seeing how the apps were crashing I thought that there might be an issue with the stock ROM so I decided to flash a new one. I was having trouble finding my specific so I went for another one found here. I couldn't flash it with ODIN because it was on a zip format so I flashed TWRP on the phone.
The error recovery is not seandroid enforcing is now showing on different versions of twrp (2.8, 3.0).
I can't flash any ROM now and the one found in the device keeps shutting it down.
I don't believe it is a hardware issue as the phone stays on without issues on download mode. Any help on what steps to follow next would be highly appreciated.
Click to expand...
Click to collapse
Update it via smart switch it will turn on after that for sure. Or download the latest firmware via samfirm and flash it with Odin.

Thanks!
ammarwajihi said:
Update it via smart switch it will turn on after that for sure. Or download the latest firmware via samfirm and flash it with Odin.
Click to expand...
Click to collapse
I tried flashing the stock rom with ODIN and the phone successfully boots now. So a big thanks for that as it is progress. BUT the issue I was orginally having persists: The device keeps turning off 10-20 seconds after booting. Do you have any idea why that might be?
Sometimes it will freeze first and then turn off but never stay on for longer.
I have tried Safe Mode and turning all connectivity related modules off.

apostol96t said:
I tried flashing the stock rom with ODIN and the phone successfully boots now. So a big thanks for that as it is progress. BUT the issue I was orginally having persists: The device keeps turning off 10-20 seconds after booting. Do you have any idea why that might be?
Sometimes it will freeze first and then turn off but never stay on for longer.
I have tried Safe Mode and turning all connectivity related modules off.
Click to expand...
Click to collapse
This is weird don't know what the problem might be. Still I suggest you to flash it with smart switch once and see.

Can't boot into recovery - Galaxy S7 G930

Hello all.
I'm new to modifying my android (Galaxy S7 G930A) and could use some help. I have successfully rooted my phone, but have had some issues trying to flash a custom recovery. I was trying to flash TWRP but for some reason it didn't work, and I would always boot into the stock recovery.
Today, I screwed something up while trying to figure out my host of issues (I was also trying to figure out why I kept getting a "dm-verity verification failed" notice when flashing). Using the TWRP Manager app, I tried to install the recovery that way and it kept giving me an error that it was either already installed or encountered an issue of some kind. Knowing it wasn't installed, I looked for a different route. Long story short, I downloaded Flashify and then manually downloaded and flashed the TWRP recovery img and a "no-verity-opt-encrypt" file - which I read would fix the dm-verity error I was receiving.
I believe that's all I did before this recovery boot issue starting occurring.
Now, when attempting to boot into recovery (no matter what way, through an app, manually, etc) the blue text "Recovery Booting..." appears for half a second and then disappears. If I'm holding down the buttons it will flash again and disappear again, over and over. If I don't hold down the buttons, when it disappears the phone boots up as normal. So now I can't seem to access recovery at all. I wanted to try going the hard/factory reset route, but obviously can't because I can't access recovery.
Also, I don't know if this is related or not, but now my laptop will not recognize my phone at all. Doesn't give me any options - it will charge, but no connection. I was hoping to load it into Odin and do a stock reset to start from scratch before flashing a custom ROM.
Edit: I tested and connected to a different computer just fine, so there's obviously some miscommunication going on between my phone and laptop.
Can anyone help me out here? Sorry for the long post, I'm just really frustrated. :crying: