Bootloop after Android.process.media crashes when I installed a new ROM - ONE Q&A, Help & Troubleshooting

The first thing I did was flash CM 12.1 from CM 12 on my OPO. Everything went smoothly and I booted after going through the app optimization thing. I unlocked and an error message about google play services crashing popped up and a few seconds later the phone rebooted. It went though the app optimization again and rebooted and went though it again, so I booted into twrp and wiped the dalvik and tried again and the same thing happened. I decided to revert to CM 12 and when I booted it went though the optimization and showed the lock screen with no background for a few seconds and an error message pops up saying "The process android.process.media has stopped unexpectedly. Please try again". The phone would then go black with the display still on and a few seconds later go back to the lockscreen with the same error. I rebooted and it is now in a bootloop. So what do I do at this point?

Either flash Cm 12.1 and the gapps pack for 5.1, or wipe and flash cm 12 and gapps pack for 5.0.x.

Related

[Q] All user apps crash immediately as of this morning, Galaxy S Blaze 4G

Last weekend I flashed the most recent CM 11 version and the Pico GApps package (from here). The phone has worked perfectly since then, very fast, no issues at all.
This morning when I turned it on I immediately saw 'Android is Upgrading' and 'optimizing __ of 42 apps.' I have all auto-updates and syncs disabled, and this is the first time this has happened.
When the phone finished booting, it told me that Chrome and my email app and AV crashed. Opening any user app results in the app crashing immediately.
I tried rebooting, same result, same Upgrading message.
I rebooted to recovery and cleaned the cache and Dalvik cache. This time I see 'Android is Upgrading' and 'optimizing __ of 132 apps.' When it finished booting, same thing - a few apps crash immediately, all other user apps crash when opening.
What's happened to my phone? I'm new at this, it's getting frustrating. I don't know why it was upgrading anything to start with...
I can't open any apps to look at Root Explorer, etc., can someone please tell me should I just reflash the CM 11? Do I need to flash the stock ROM first? I don't know what to do next. This is still new for me.

Android is starting... Optimizing apps x of y Bootloop? (Help plz)

So I'm running Sultan's CM 13 rom and my phone just randomly turned off while I was using it (on charge), and when it rebooted, it said that it was optimizing apps. I decided to leave the phone on charge and do something else, and when I come back, it restarts again and does the optimizing apps thing again. I can't even boot into safe mode either, if you were going to tell me to. I've tried wiping the Dalvik-Cache and Cache from TWRP, but nothing's happened.
Should I just factory reset my phone at this point?
Just try to clean flash Sultan CM13.
ramhawk123 said:
So I'm running Sultan's CM 13 rom and my phone just randomly turned off while I was using it (on charge), and when it rebooted, it said that it was optimizing apps. I decided to leave the phone on charge and do something else, and when I come back, it restarts again and does the optimizing apps thing again. I can't even boot into safe mode either, if you were going to tell me to. I've tried wiping the Dalvik-Cache and Cache from TWRP, but nothing's happened.
Should I just factory reset my phone at this point?
Click to expand...
Click to collapse
Same here mate..
Always nandroid back up..
Go to safe mode then reboot..
This is a problem before mate..

[2016]Random Reboots on my ONE. Please help.

Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").

XT1033 seems to be bricked (CM13)

I had CM12 for a long time now, but it kept annoying me with update notifications, so I finally gave in.
Installation went fine and booted.
Then I installed this gapps. Upon booting, it kept going in a loop of "Google Services has stopped working". Then after a few minutes it went into a boot loop that keeps crashing a few moments after human interaction is possible.
The worst part is that I also can't get into recovery. I can go to fastboot mode, but upon trying to enter recovery the phone boots normally instead.
Did it get bricked?
Thanks.
To follow up, I went to sleep, and after I woke up, my phone finally agreed to go into recovery for some reason, so I formatted everything and reflashed CM13 with Open Gapps this time, and it seems to work.
I noticed the Open Gapps notes for Android 6 say it must be installed before booting, while I installed the above gapps after booting, so that might have been the problem.

How to fix ''No Command'' if resetting or flashing the ROM doesn't help

So a few days ago I was getting a bunch of pop-ups saying that some apps stopped working.
It seamed like all the apps stopped working one after another.
And then the phone would just freeze.
I went to settings, tapped factory reset, the phone restarted and I got ''no command'' with dead android image.
I have Homtom ht16
I flashed stock rom, turned on the phone, the homtom logo appeared, stayed for about 10 minutes, phone restarted and again ''no command'' appeared.
I went to recovery and did factory reset and the same thing happened again
I would like to know why the system doesn't boot?
Thread closed as duplicated with https://forum.xda-developers.com/android/help/command-help-ideas-t3881507

Categories

Resources