I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/oneplus-3/help/boot-recovery-cm14-1-nightly-official-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
SOLVED: I wiped everything except Internal Storage from afvanced wipe of TWRP and reflashed CM13 along with Gapps. Now the phone booted up fine and I'll restore my apps using titanium backup.
Hello,
Glad you found your way.
Thread closed.
Regards
Vatsal,
Forum Moderator.
Related
I've unlocked the bootloader, rooted my Moto G (xt1032) with superboot and installed CWM recovery on it. So I tried installing Cyanogenmod 11 (cm-11-20140405-SNAPSHOT-M5-falcon.zip at the moment) for my device and initially, everything works fine. It boots pretty smooth and downloads all the apps from the Google Play Store. But when I reboot the device I get the error "Unfortunately com.android.systemui has stopped" a few times. After clicking "okay" I get to enter my PIN for my SIM card, but then it just gets worse. The error pops up constantly and I have no possibility of selecting anything else. The apps on my wallpaper dissappear and appear again, the wallpaper switches to fullscreen, then normal again and so on. Wiping cache or dalvik cache does nothing, only a factory reset helps. Then it installs all the apps again, but when I reboot, the same problem persists.
Some threads suggested it may be an app and since it only happens when I reboot, could it be an app that launches on boot?
Others suggested trying an older version of Cyanogenmod (which is why I'm using M5 at the moment. M6 gave the exact same problem). Or has it something to do with the gapps file I'm using?
Any ideas on how to fix this? Thanks in advance.
Narcotle said:
I've unlocked the bootloader, rooted my Moto G (xt1032) with superboot and installed CWM recovery on it. So I tried installing Cyanogenmod 11 (cm-11-20140405-SNAPSHOT-M5-falcon.zip at the moment) for my device and initially, everything works fine. It boots pretty smooth and downloads all the apps from the Google Play Store. But when I reboot the device I get the error "Unfortunately com.android.systemui has stopped" a few times. After clicking "okay" I get to enter my PIN for my SIM card, but then it just gets worse. The error pops up constantly and I have no possibility of selecting anything else. The apps on my wallpaper dissappear and appear again, the wallpaper switches to fullscreen, then normal again and so on. Wiping cache or dalvik cache does nothing, only a factory reset helps. Then it installs all the apps again, but when I reboot, the same problem persists.
Some threads suggested it may be an app and since it only happens when I reboot, could it be an app that launches on boot?
Others suggested trying an older version of Cyanogenmod (which is why I'm using M5 at the moment. M6 gave the exact same problem). Or has it something to do with the gapps file I'm using?
Any ideas on how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Mine did this once and what worked for me was fixing permissions.
DarkVanguard said:
Mine did this once and what worked for me was fixing permissions.
Click to expand...
Click to collapse
Tried fixing permissions before even installing any app. Rebooted, no luck. Still the same error without even a google account linked or app installed.
Narcotle said:
Do you remember which permissions exactly?
Click to expand...
Click to collapse
You need to do it from your recovery. In TWRP, there is a button that says "Fix Permissions." I'm sure it's available in CWM, as well.
DarkVanguard said:
You need to do it from your recovery. In TWRP, there is a button that says "Fix Permissions." I'm sure it's available in CWM, as well.
Click to expand...
Click to collapse
CWM recovery didn't have a fix permissions setting, so I flashed TWRP through fastboot. Fixed permissions, rebooted: same error.
Did another factory reset and cache, sideloaded CM11 snapshot M5 and GApps to TWRP, flashed again. CM11 booted fine, just like it always does the first time. Had to reboot into recovery in order to fix permissions (wasn't able to do that right after I flashed CM). Rebooted again and still the same error.
Narcotle said:
CWM recovery didn't have a fix permissions setting, so I flashed TWRP through fastboot. Fixed permissions, rebooted: same error.
Did another factory reset and cache, sideloaded CM11 snapshot M5 and GApps to TWRP, flashed again. CM11 booted fine, just like it always does the first time. Had to reboot into recovery in order to fix permissions (wasn't able to do that right after I flashed CM). Rebooted again and still the same error.
Click to expand...
Click to collapse
Try manually wiping system, data, cache, and dalvik. If that doesn't work, try a different gapps package. If it still gives the same error after that...then I don't know.
I had the same problem : I just flashed cm nighglies instead and waited for one enough stable...
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
kanjo said:
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
Click to expand...
Click to collapse
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
EDIT: Exactly which thread are you getting these instructions from? Neither of the PA threads that I'm aware of contain those instructions.
Heisenberg said:
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
Click to expand...
Click to collapse
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
kanjo said:
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
Click to expand...
Click to collapse
Just to be clear, you've wiped system, data, cache, and dalvik cache directly before flashing PA? No CM flashes since wiping all of those partitions?
Also, which thread are you getting those install instructions from? Neither of the PA threads that I'm aware of contain those instructions.
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
going to go back to twrp. wipe all data and flash PA again without gapps and without root. will report back in about 10 minutes. will flash by using TWRP and ADB sideload.
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom) at the moment i am trying to sideload PA rom after wiping data, system, cache and dalvik. is this why i am having the issue?
im dead tired so i admit i can be making mistakes though everything i have done seems to be what i am meant to do. flashed from cm11 to cm12, cleared all data, then flashed PA+gapps and root. = upgrading boot loop and errors mentioned above. tried flashing just PA and it booted with same errors, flashed gapps and errors.
all the files MD5s look good. not sure what is wrong.
--edit--
okay now i am at homescreen on PA.
when enabling/disabling adb in dev settings i get a reboot. is this normal now? does it need to reboot to mount the filesystem or something?
when it does boot after enabling adb i get "settings has stopped"
going to go to TWRP and flash GAPPS now and leave root not installed. will report back in a sec.
kanjo said:
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
Click to expand...
Click to collapse
Please define wiped all data.
kanjo said:
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom)?
Click to expand...
Click to collapse
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Heisenberg said:
Please define wiped all data.
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Click to expand...
Click to collapse
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
kanjo said:
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
Click to expand...
Click to collapse
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Heisenberg said:
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Click to expand...
Click to collapse
balls, was hoping to us PA, haven't used it since my old s3 and figured it was the rom for me again. will have to check the rom comparison spreadsheet and look into others.
right now i have sideloaded PA alone. will copy PA and gapps to the internal storage to make things easier.
but it doesnt look like it is going to work for me.
going to try it once more like you said but locally rather than through sideload. though the internal storage is deciding when it does and doesnt want to show up.
TWRP
wipe system, cache, dalvik cache, and data.
and flash them both in tandem.
and for the fun of it when it asks if i want to install root i will let it go right ahead.
maybe this time it will work. if not then its a different rom for me. sadly.
okay so now **** got retarded. TWRP has been replaced by the stock cm11 recovery and i am too pissed off to think straight and cannot remember how to get this son of a ***** rooted again let alone to flash TWRP. i dont want to use any toolkits they all seem broken as hell.
can anyone point me in the right direction because ive just about lost my **** and this phone is going to meet my fist head on very shortly...
**edit**
done. after all this i am now on cm11 stock rooted ....seriously. hours upon hours, just to get back to where i started.
man i love when things go smoothly. anyway cheers for your help @Heisenberg . n
First of all: I made a thread about bricking my Moto G earlier, but since this is a new issue (and a new Android version) I thought it would be better to make a new thread
So as some of you might have noticed yesterday there was the first release of CM13 for the Moto G and if you had nightlies enabled (like me) you'd just get it as a normal update, except for having to install the new Gapps of course. The problem is I didn't notice that it was CM13 until it was too late... First thing that happened was of course that my Google Play Services we're not working anymore. I tired flashing Gapps for 5.1 but it said that I used the Gapps for the wrong Android version. So I looked in the settings and noticed that I had Android 6.0 . Now I tried flashing OpenGapps for Android 6.0, which worked, but as soon as I booted Android it told me something like "Setup Assistant stopped working" over and over again, so I tried reverting to my latest CM12.1 backup I had, which was a bad idea... My phone was stuck in a bootloop and everytime I tried wiping my phone (except for internal storage) it rebooted when wiping data. Reflashing TWRP didn't help, so I tried flashing stock Android with mfastboot and it got to the point where it was optimizing apps but after that it just did the same thing again (classic boot loop).
Here's my question: How can I get TWRP working again and install CM13 (again if possible without wiping my internal storage or at least being able to back some files up) ?
Can u access TWRP?
Andus1988 said:
Can u access TWRP?
Click to expand...
Click to collapse
Yes I can, flashing and wiping works, except when trying to wipe data
Then don't wipe data?! Wiping data isn't necessary every time!
Andus1988 said:
Then don't wipe data?! Wiping data isn't necessary every time!
Click to expand...
Click to collapse
I know but if I only wipe dalvik, cache and system it didn't work.
Now I tried booting into TWRP and it shows the "no command" screen :'(
I'll write u a PM
I have the same problem would be nice if someone have a solution.
Guys i have a similar problem here, i got the latest update downloaded (cm-13.0-20151207-NIGHTLY-peregrine.zip) and when i clicked on update, the phone went black and nothing work now, i cannot get into fastboot or anything else, it only show "qhsusb_bulk" when I plugged in to the computer, any help??? i would really appreciate it .
My bootloader is unlocked.
Using FlashTool 0.9.18.6, I flashed "Sony Xperia L C2105 15.3.A.1.17 Generic DE" - FTF, which I downloaded from:
https://forum.xda-developers.com/xperia-l/general/sony-xperia-l-flashable-ftfs-locked-t2560642
Downloaded CM11 from FreeXperia's thread, from that I extracted boot.img and using FlashTool flashed it.
Downloaded CM12.1 from Oliver's thread and moved it into my external sdcard. Using CWM, did a clean wipe (dalvik, cache, data and system), and flashed the zip.
ROM installed and was working fine.
Downloaded CM13 from Oliver's thread and moved it into my external sdcard.
Enabled USB debugging.
Downloaded TWRP 3.0.2-0, from:
https://dl.twrp.me/taoshan/twrp-3.0.2-0-taoshan.img.html
Rebooted into bootloader using adb. And flashed TWRP, using fastboot:
"fastboot flash boot twrp.img"
Rebooted into recovery. The interface was flickering non-stop and the left part was overlapping over the right part and vice-versa, but I managed to factory reset and wipe my dalvik, cache, data, system, sdcard and android secure.
Then I flashed CM13 from my external sdcard.
No errors.
Wiped dalvik, cache and my external sdcard.
Rebooted.
Bootloop.
Rebooted into CM Recovery.
Factory Reset and wiped cache.
Rebooted.
Bootloop.
I have also tested 7.x.x (CM14 and Resurrection Remix) and it also gets me in a bootloop until the battery reaches 0%.
The problem started with Beta 2 of CM13 (anything before it works fine), after I flashed it almost a year ago. I also made a post there at that time about my problem:
"I'm not certain if this is the right thread to ask, and I don't think this qualifies as a bug report, I'm just asking for some help as my phone is stuck on the boot logo forever until the battery runs out (from 90-100% to 0%).
I've previously used CM11, CM12.1 and the previous beta 1 of CM13, but after flashing beta 2 a couple days ago it's just stuck on trying to boot.
The recovery I'm using is TWRP 3.0.2. I wiped my phone completely(the system, sdcard, cache etc). After that I connected my phone to my PC, while on recovery, and copied the ROM zip and GAPPS zip to my external sdcard. I disconnected my phone from the PC. Flashed the ROM and after that GAPPS (Open GApps Platform: ARM / 6.0 / pico). The logs didn't show any error so I wiped the dalvik cache and rebooted the phone. The phone went into the boot logo and now is just stuck there, I waited ~5 hours and it still didn't fully boot after an hour or so the battery ran out. So I decided to do everything again, charging the phone to 100%, wiping the phone completely 10 times(for reasons) and flashing everything the same way(I also downloaded the ROM from a different mirror, and tested both zips for any errors), this time I left it overnight, keeping the charger connected and in the morning it was still stuck on the boot logo. The third time I tried a different GAPPS package(A-GAPPS) and the same result. Can anyone provide some help? Maybe I'm just missing something or being really stupid. I'm sorry for being such a bother."
https://forum.xda-developers.com/xperia-l/orig-development/rom-cyanogenmod-13-0-t3254779/page20
I made this thread in hope of finding out what's causing this. Any help is appreciated.
It's been almost a year and I still have this problem with newer ROMs. Does nobody have any suggestions, anything at all? Is more information required? I'd be happy to give/do anything*, if it would mean getting these ROMs working.
The only error I've noticed is that after flashing LineageOS 14.1, if I try a fully factory reset through the default "Android Recovery" it will fail and I'll get "E: format_volume: failed to open /persist/footer" (This doesn't happen if I do a factory reset through TWRP).
Hi all,
I'm using the OPO with CM11 44S.
lately I began to get annoying popups like "unfortunately, trebuchet stopped" or "unfortunately, setting stopped".
I've tried to access apps to clear cache but my phone throws me out every time.
So I've decided change my ROM to lineage.
downloaded the ROM and the gapps, updated my twrp, cleared dalvik, system cache and data. and tried to install with twrp.
update failed with " error executing updater binary in zip".
I restored my phone and again tried to install the rom but now i wiped only dalvik and cache and data. this time i got error 7.
I searched a little and saw that you need to edit with notepad++ and delete some lines from the "updater-script" file.
I did it and tried to flash and now i got error 6.
pretty frustrated at the moment! I'm really happy with my CM11.0 44S ROM and if i can bring it back without the annoying popups it will be great.
Does anyone have any idea???
Lalon80 said:
Hi all,
I'm using the OPO with CM11 44S.
lately I began to get annoying popups like "unfortunately, trebuchet stopped" or "unfortunately, setting stopped".
I've tried to access apps to clear cache but my phone throws me out every time.
So I've decided change my ROM to lineage.
downloaded the ROM and the gapps, updated my twrp, cleared dalvik, system cache and data. and tried to install with twrp.
update failed with " error executing updater binary in zip".
I restored my phone and again tried to install the rom but now i wiped only dalvik and cache and data. this time i got error 7.
I searched a little and saw that you need to edit with notepad++ and delete some lines from the "updater-script" file.
I did it and tried to flash and now i got error 6.
pretty frustrated at the moment! I'm really happy with my CM11.0 44S ROM and if i can bring it back without the annoying popups it will be great.
Does anyone have any idea???
Click to expand...
Click to collapse
You must flash new firmware in order to upgrade to LOS since you're on Old cm11s firmware.
Don't make any changes to the rom zip file,it is fine.Just make sure that the zip file is not corrupted.
Preferably this firmware,
https://www.androidfilehost.com/?fid=24389512218018449
Wipe everything except internal storage then flash firmware then LOS.Make sure you're on latest TWRP.
Good Luck!
thanks.
worked like a charm!