My friend did the OTA CM13.0, completed fine, then went into the "Optimizing Apps" Part. After it finishes it just reboots and sits and bootloops. Tried wiping cache, tried everything...including factory reset... Which oddly enough still optimizes apps (the same number as the first time). What else can we do?
Reflash,
http://blazingphoenix.in/mzo/ONE
Related
my tap was working fine and then it suddenly stops, and hang, i restarted it, but every 4-5 secs, it restarts itself again, then i came up with this so called bootloop. then i tried to open the system recovery menu and i selected wipe data, i've waited for so long and took hours but i ended up with nothing, i have no idea on how long will it take to wipe the data on my device, i also tried to factory reset it, same result, still stuck on boot loop. what should i do? help please. no custom roms installed, just rooted.
So today I woke up and my phone was stuck at the Google logo and would not boot up after having no problems ever. I tried to factory reset the phone using the hammerhead build on Google's website, but it gets stuck at "erasing 'cache'" and my phone hangs at the bootloader when it gets to this point.
I've also tried installing CWM and wiping from there - cache erases fine but erasing data gets errors such as "Error mounting /data."
I don't really know where to go from here so any help?
Figured it out
Ok, never mind, I figured it out. I flashed a Kit-Kat bootloader to solve the freezing problem and manually flashed all the factory files line by line. Booting up well now.
moto g 2015 with stock rom goes into boot loop after "optimizing apps" phase
I rebooted my Moto G 2015 after an app began behaving erratically. The device then went into a boot loop. The first thing wrong with the boot is that it goes through the "Optimizing apps" stage, but as I had not wiped cache I wouldn't expect it to do that. After it gets through my 117 apps it says "Starting apps" and then reboots - I get the spool of thread and the stitching animation and the whole process starts over.
I've tried going into recovery mode and telling it to wipe cache there - I would expect cache wipe to take just several seconds like on other phones I've used (haven't ever done it with this one), but here it prints "formatting /cache..." and sits there, and sits there, and every 10 minutes, is still sitting there.
Is there any way from the recovery mode to get data copied off the device's internal memory? I have a few things there that weren't backed up. I tried running "Apply update from ADB" in recovery mode, then trying the "adb backup" command, but I got the error "adb: unable to connect for backup: closed".
My guess is that this phone has bad memory and I'll have to eat my lost data and send the phone back to Lenovo for warranty service. But if anyone has any ideas for things to try, let me know!
droidlesswonder said:
I rebooted my Moto G 2015 after an app began behaving erratically. The device then went into a boot loop. The first thing wrong with the boot is that it goes through the "Optimizing apps" stage, but as I had not wiped cache I wouldn't expect it to do that. After it gets through my 117 apps it says "Starting apps" and then reboots - I get the spool of thread and the stitching animation and the whole process starts over.
I've tried going into recovery mode and telling it to wipe cache there - I would expect cache wipe to take just several seconds like on other phones I've used (haven't ever done it with this one), but here it prints "formatting /cache..." and sits there, and sits there, and every 10 minutes, is still sitting there.
Is there any way from the recovery mode to get data copied off the device's internal memory? I have a few things there that weren't backed up. I tried running "Apply update from ADB" in recovery mode, then trying the "adb backup" command, but I got the error "adb: unable to connect for backup: closed".
My guess is that this phone has bad memory and I'll have to eat my lost data and send the phone back to Lenovo for warranty service. But if anyone has any ideas for things to try, let me know!
Click to expand...
Click to collapse
Wiping cache in recovery takes a long time on this device... really long, maybe even 20-30 minutes sometimes. Try the cache wipe again. If that fails do a full factory reset and give it time to finish. I don't know why recovery wipes take so long in this device, but they take a ridiculously huge amount of time. (Cache wipe in my Moto X Pure Edition takes about 30 seconds, which is also a 3rd gen Moto device).
You cannot access the files via stock recovery or fastboot unless you have an unlocked bootloader and boot a third party recovery like TWRP.
cache wipe successful but no joy
After my post above I tried wiping the cache and waited patiently, and as you predicted it did eventually complete. But the phone still goes into the boot loop.
I am kicking myself for not rooting this thing on day 1 and installing TWRP. I need to have a solemn moment alone with the phone to say goodbye to my data and I'll try full factory reset, if that doesn't work it's off to warranty service.
Thanks for the response!
droidlesswonder said:
After my post above I tried wiping the cache and waited patiently, and as you predicted it did eventually complete. But the phone still goes into the boot loop.
I am kicking myself for not rooting this thing on day 1 and installing TWRP. I need to have a solemn moment alone with the phone to say goodbye to my data and I'll try full factory reset, if that doesn't work it's off to warranty service.
Thanks for the response!
Click to expand...
Click to collapse
Well... On a good note, since your not rooted then system is still intact, a factory reset will likely work.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Well... On a good note, since your not rooted then system is still intact, a factory reset will likely work.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Yes, it did work, phone is back to where is was six months ago. Since the data has been wiped, I'm going to unlock and install TWRP so I'll be in a better place when this happens again. Thanks again for your help!
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
oldschool63 said:
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
Click to expand...
Click to collapse
Answering my own question here: after quite some hours of trying it turned out that my tablet seems to be just fine. The problem is something totally different and weird. If you are interested in what's going on, please continue reading here: https://forum.xda-developers.com/android/help/help-app-bricks-samsung-tablet-try-to-t3661516
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!