After I downlaoded the offical cm 14.1 nightly to my oneplus 2, I flashed. When starting the phone, i got the notification, that google play store and their service were stopped. So i went back to the recovery TWRP and wiped the dalvik cache and regular cache. After I did this, the phone went into a bootloop and i dont know how to fix this.
Hopefully I can repair the issue asap cause its my daily driver ands its important
It sounds like your data partition contains data structures from older CM13 or derivate ROM. In that case you will have to clean flash to get it going without bugs and boot problems. Also make sure you flash the latest nano or micro package of Gapps for 7.1 ROM 64-bit.
AxeltheWexel said:
After I downlaoded the offical cm 14.1 nightly to my oneplus 2, I flashed. When starting the phone, i got the notification, that google play store and their service were stopped. So i went back to the recovery TWRP and wiped the dalvik cache and regular cache. After I did this, the phone went into a bootloop and i dont know how to fix this.
Hopefully I can repair the issue asap cause its my daily driver ands its important
Click to expand...
Click to collapse
Same thing hapening to me tried everything even used network signal guru and selected band 3 and 5 then too i am facing the same problem and phone get random reboots now and the. please help.
AxeltheWexel said:
After I downlaoded the offical cm 14.1 nightly to my oneplus 2, I flashed. When starting the phone, i got the notification, that google play store and their service were stopped. So i went back to the recovery TWRP and wiped the dalvik cache and regular cache. After I did this, the phone went into a bootloop and i dont know how to fix this.
Hopefully I can repair the issue asap cause its my daily driver ands its important
Click to expand...
Click to collapse
1. Download latest GAPPS for 7.1 (ARM64). Here -> http://opengapps.org
2. Enter TWRP & Connect the phone to a PC (you can still access phone storage in recovery)
3. Copy GAPPS zip.
4. In TWRP go to "Wipe" & wipe Data + Cache + Dalvik Cache (Your internal storage won't be wiped)
5. Flash CM 14.1 zip.
6. Flash downloaded GAPPS.
7. Reboot System! Done!
Hi,
I'm using CM13 on my xiaomi redmi 2. This morning I installed the weekly update from 25th of December 2016 from the update manager, without realising that it was actually a new ROM, CM 14. The installation went well but gapps was giving much trouble. I decided to install gapps for Android nougat, but couldn't get into TWRP. In the end I installed a CM13 version from the update manager, in the hope that everything would go back to normal. As a result my phone went soft-bricked and wasn't even able to connect it with adb/fastboot from my desktop (ubuntu 14.04). Eventually I've managed to get into TWRP and now I have the possibility of wiping out Cache partition and Dalvik Cache, and install a ROM of CM 13, but I would like to investigate the chances of getting back the phone without losing all my data and apps. Is there anyway to do this?
Thanks.
Bro if you have got TWRP working right then you might already have CM 13 Zip files and gapps in the phone too. Try Clean Installing the Rom (ps don't select storage in advanced wipe option in Twrp , only select DATA , SYSTEM , CACHE & DALVIK to wipe). Your photos,videos,whatsapp chat backup will be saved. Try above method and let me know if it work. If not then you have flash MIUI rom using fastboot method to get your device back.
Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps
Xiaomi EU Booting problems
Hi Guys!
I'm using Xiaomi EU ROMs for some time and I must say that they are brilliant in terms of being ROW form for our phone which is as You know China only.
However I have recently an issue with phone stuck on a Mi logo while booting. After shutting donw the phone to start it I have to clear Dalvik every time in TWRP which makes it boot in ~10 min.
I have:
1) TWRP 3.2.1 (the newest I've found for Omega), - but the problem also appeared on 3.0.3 (Hanuma) and 3.1.1;
2) Tested clean install (wipe Dalvik, Cache, System, Data) - it works but only up to the point when I install my every day apps. After that the problem re-appears;
I'm not using Magisk or any type of rooting (because I do not need it).
I've tried upgrading (form 8.3.29 to 8.4.19 and 8.4.26 ROM) and clean install. I've tried to fix permissions, and repair filesystem (to data and system partition) in TWRP. I've tried even rebooting without dm-verity via console in TWRP (which shouldn't be an issue as it is fixed in Xiaomi EU Roms). The problem always seem to be in Dalvik partition (because after cleaning it the Phone boots.
Do You have any suggestions what to do to fix this issue? Please help!
Thank You in advance!
H.
Have u tried lazy flasher?
waigyi said:
Have u tried lazy flasher?
Click to expand...
Click to collapse
Thank You for Your help. I've managed to solve my problem, which must have been in the Xiaomi account verification. Everything seemed to be ok but it was not. When I was cleaning partitions via TWRP the error was still comming back. When I did factory reset and removal of Xiaomi account from the phone everything went back to normal.
Best regards,
H.