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!
Related
So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?
fishlipsboy said:
So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?
Click to expand...
Click to collapse
I had a similar issue on Embryo 7... ROM installed fine, worked fine for about a week then reboot and not going past the Samsung logo. What I found out was that the data and system partition were bad... running an e2fsck from adb shell while in recovery turned out a lot of logical errors (most of them were about inodes allocated to more files if I remember correctly but not only those). I found out while working on it that wiping these partitions from recovery is not fixing these errors.
What I did was I wiped everything (cache, data, system), ran e2fsck on each individual partition to fix the errors until no more were showing up then started from scratch (install ROM, restore apps, etc). So far, no more issues.
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
Reboot phone in recovery since you need those partitions unmounted. Connect phone to PC with USB then connect from PC with adb (run "adb shell"). If partitions (data, system, cache) are mounted you can unmount them from recovery.
Once you are in adb shell then you can run "e2fsck -fnv /dev/block/mmcblk0p24" to scan system partition. Repeat for data partition (mmcblk0p25), efs (mmcblk0p21), cache (mmcblk0p26), preload (mmcblk0p27). That will tell you only if you have errors; it will not fix them.
To fix them, run "e2fsck -fcyv /dev/block/<part name as above>".
You can also run "e2fsck" (with no parameters) to see the help and what each parameter means.
Also, see this great thread regarding the list of partitions in Skyrocket... http://forum.xda-developers.com/showthread.php?t=1629508
Hope this helps you. Let me know if you need more detailed instructions.
---------- Post added at 11:31 PM ---------- Previous post was at 11:27 PM ----------
fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
BTW, if you find errors on your data and/or system partitions and choose to fix them, it does not mean that you phone will boot fine right away. Depending on how bad it is, you might need to reinstall the ROM.
Also, fixing the errors takes space (as *nix saves the recovered files under "lost+found" folder) so in my case, I chose to wipe the partitions from recovery first, then fix the errors and then re-install the ROM.
I'm trying to remove apps that's on this phone (GT-S7500) because some of the apps always force close and not working. Firstly, I tried uninstall the apps one by one, all went good until I rebooted the device, all of the apps are back again. Second, went to privacy>erase everything including SD card content, device rebooted and went straight to recovery. It was weird because normally it will reboot itself straight to home screen. So I select the option factory reset/wipe data, after that wipe cache partition and reboot. Device does not reboot but turned off completely (weird again) Turned it back on, and only saw that none of the apps were removed. Even the wallpaper are still the same. Next thing I do is manually boot into recovery menu and factory reset again, still the same thing, (device turned off without rebooting itself, turned it back on and everything was still the same) after few tries again, I finally decided to flash a stock rom with ODIN. Flashing was successful ODIN shows PASS, waiting device reboot but it shut off completely again. turned it back on, but nothing changes. wallpaper are still the same and every single downloaded apps were still there. Went to settings> about device only to found that it wasn't the same rom that I've flashed earlier using ODIN.(flashed 2-3 times again, results still the same) Very confused right now, suspected that the internal SD card was corrupted/damaged. Does anyone experiencing such thing on your galaxy ace plus? searched on xda forums and found that this issue was also happening on few other devices. This is not my phone, just helping a customer. Thank You.
After flashing stock rom
Go to recovery (stock of course)
Wipe data/factory reset
Wipe cache
Reboot
Sent from my Gt-S7500
I experienced the infamous boot loop problem on my Nexus 5. I'm running stock android, and it started after the battery was depleted overnight - and after I recharged the phone.
First I tried to to just clear the cache in Recovery Mode. It went into a long loop where every other second a flash would appear on screen with the 'No Command' screen. I decided to abort that after 30 minutes and try a Wipe data/factory reset in recovery mode.
It seems to work fine in the beginning, but after a while it begins with the same loop, where it occasionally shows the 'No Command' screen.
Seems like there is broken hardware - or do you have any ideas what the reason may be and how to amend it?
Try to reflash all stuff with google factory images and check if your problems still exist.
What do you mean by "It seems to work fine in the beginning"? You're able to boot into the OS? Could be a faulty/broken power button which might be causing the bootloop as well.
Anyways, as mentioned above, flash the factory images to rule out the possibility of a software issue.
I would recommend unlocking your bootloader, flashing a custom recovery, doing a wipe with that and then flashing a stock nandroid.
If you aren't good with adb, and you don't have an OTG cable, I would look into how to flash the factory images from Google first, then once you're all set with that do the above.
Thanks
Thanks guys. I decided that I would invoke my warrany from Google and get a new phone.
I hope someone else benefits from your suggestions, I would have if I didn't have my warranty...
Hi,
since my old M7 is having more and more annoying issues, I tried to move to a One A9.
The problem:
The phone gets stcuk on LOS boot screen. Looks like it's loading but it never finishes and I can't even turn it off by holding power button pressed for 10s, 1m or even 10m!
BUT this happens only sometimes! Last night I just left it in this state to get the battery empty and this morning it was turned off. "On the way" to recovery (TWRP 3.1.1) I pressed the wrong button and it rebooted. Without any issues! Used it all day until I wanted to reboot it to insert a microSD-card. Since then: stuck on bootscreen! Can't get out...
Any ideas?
What I did:
Unlocked the phone
Factory reset
Installed TWRP
Flashed LOS 14.1
Flashed Magisk 14.0
Help appreciated
Somehow I'd consider this thread as solved:
I went back into TWRP and:
- formatted DATA
- made a full wipe
- made another full wipe
Now suddenly I don't get neither bootloops nor "Can't mount" errors in recovery (which I forgot to mention in the opening post :silly
I write "somehow" since I have formatted DATA before, as well as made a full wipe, because I couldn't even install LOS before that
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.