Database Info

[Solved] try this if you're stuck at the boot loading screen

While I was playing with my TF700 the other day I accidentally put it upside down resulting in pressing (& holding) the power bottom & volume down .. the device restarted into "Safe Mode"
I tried to get rid of it, but apparently I did something stupid which resulting in boot logo loop (the device is stuck at the second ASUS screen and refuses to boot)
* Note my device is Unlocked & I'm running the latest CleanRom version and I am kinda' experienced user :silly:
Anyway I googled this and I tried the following steps with NO success:
- Cold boot
- Wiping caches
- I also tried to re-flash a rom
which left me only with formatting & wiping data, BUT I tried this thing and it actually worked!
From TWRP I restored my last back up (which was a bit old) But whatever, It actually worked! and I have no problems whatsoever, everything seems to run as before, I also tried to reboot the device and it's still working!
I felt I should share this info with you, it might help someone :highfive:

[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.

S6 failing to boot - stuck on factory reset

Hey, my phone has been playing up and generally malfunctioning lately. It seems to work fine for a day or so before freezing, and either rebooting itself or forcing me to manually reboot it using power + volume down. This seems to send it into a bootloop where it generally freezes during the Samsung animation with the pulsing squares. This sequence continues with me manually rebooting, also trying to boot to safe mode and to recovery and after various attempts, i successfully got into recovery without it freezing on the blue android.
I then decided to factory reset as a last option, having looked around on forums for solutions. However, I now do not know what to do as it seems to have frozen during the factory reset. I dont have screenshots but the script reads as follows :
dm-verity verification failed. . .
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
It has been on that for the past 30 minutes and so i have assumed it has frozen. I'm afraid to force another reboot in case it is accessing memory, any suggestions on what to do?
It is up to date on fully stock software, has never been rooted and i have never attempted to do so. Also only around a month old.
Any help would be appreciated, thanks

I did not try to perform a factory reset yet, but my S6 shows the same instability issues.
Random self reboots with getting stuck at the boot animation.
I furthermore cannot enter the stock recovery mode (get stuck at full cyan screen with android logo), only can access the ODIN mode atm.
Booting that device atm is a hit and miss.
(everything stock, never touched that device in the XDA way! )

Update: I had to repair my S6 as instability increased even more.
Samsung licensed repair shop exchanged the mainboard of my S6.
All is fine again (except wireless charging, but I guess they broke it while repairing)

Wokeup to my phone stuck in a bootloop... [SOLVED]

UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!

Question Soft boot loop after wiping cache partition - Rooted S908E

I need help. After rooting the device and after several days of using it, and saw that Wipe cache partition can clean up stuff and increase battery life and performance. So I went ahead, connected my phone using a USB-C cable to PC, hold the UP button while booting, and selected Wipe cache partition. Booted it up again, and it was running fine but the phone has starting for almost like after every minute it hangs, and goes back to the Samsung logo, and the cycle repeats. I was only able to escape via booting in Safe Mode.
Any advice what to do to prevent the boot loop? Is there any way to know which or what makes the phone hang?
Running in Android 12 One UI 4.

givememysandwich said:
I need help. After rooting the device and after several days of using it, and saw that Wipe cache partition can clean up stuff and increase battery life and performance. So I went ahead, connected my phone using a USB-C cable to PC, hold the UP button while booting, and selected Wipe cache partition. Booted it up again, and it was running fine but the phone has starting for almost like after every minute it hangs, and goes back to the Samsung logo, and the cycle repeats. I was only able to escape via booting in Safe Mode.
Any advice what to do to prevent the boot loop? Is there any way to know which or what makes the phone hang?
Running in Android 12 One UI 4.
Click to expand...
Click to collapse
Not sure why that would do that.. But it seems like the only solution now would do a complete factory reset and start over.

Thank you for the reply. For some reason, the phone just decided to fix itself. What I did was just let it be in Safe Mode for several hours, went back to Normal mode, and somehow it stopped hanging.