This started happening with a working RR android 7.1 ROM I have used for several days. Today, I wanted to try out LineageOS 14.1 so I made a nandroid backup of data and internal storage. When I rebooted into RR the screen was flickering and a message constantly popped up stating that com.android.phone stopped and Calendar stopped and com.android.media stopped etc etc.
So I went on and did a full clean flash
I tried t remove my sim and the clean flash but to no avail. I do advanced wipe --> Dalvik/ART cache, System, Data, Internal Storage, and Cache before every flash today. Then i flash ROM and latest gapps, wipe cache/dalvik and reboot.
Even without flashing gapps, the problem is still there.
Running on TWRP 3.0.0 (worked for several days on RR android 7.1 ROM), but tried on 3.0.2-2, 3.0.2, and 3.0.1 with the same results.
How did this happen? Is my EFS and IMEI f'ed because of the nandroid backup of data and internal storage?
How do I fix this?
Kind regards and a happy new year!
Same here. Twrp is the culprit, I'm afraid. It isn't taking good backups. Just fresh install RR and download all your apps, it'll work. Can't wait for twrp update...
i needed to format system to ext 4 and now everything works!
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
Guys, I'm not very mature with this device Rn7. As i already know about it's encryption. It's v flaky.
I'm running LOS 17.1, i have setup Pin & Fingerprint in my device which i enter into the recovery as well for decryption. I never flashed a Firmware thingy in my Device. As i have read before flashing many ROMs, You should have to flash Android Q firmwares on Top. But i never did that when flashing LOS 17.1. I just rooted Miui 11 installed custom recovery (Orange Fox R11) & flashed LOS 17.1
Question 1: LOS 17.1 is FBE or FDE?
Question 2: If i want to move on to Bliss ROM 12.11 from my current LOS 17.1 (21.7 nightly), Formating data will be necessary? Or i can just wipe? So i don't loose my Internal storage.
Question 3: Does anyone know how to flash a firmware? BlissROM OP says flashing a firmware on the Top before flashing Rom.zip?
Question 4: If i want to backup (nandroid) my current OS (LOS 17.1) into the recovery. Exactly which partitions i should backup? So i can restore after trying Bliss ROM or if i get a bootloop or other issues (if needed). My Internal storage will be safe at that time aswell after restore?
My Current OS: LOS 17.1
Current Recovery: Orange Fox R11
LOS 17 is fbe. idk the rest
noobSU said:
Guys, I'm not very mature with this device Rn7. As i already know about it's encryption. It's v flaky.
I'm running LOS 17.1, i have setup Pin & Fingerprint in my device which i enter into the recovery as well for decryption. I never flashed a Firmware thingy in my Device. As i have read before flashing many ROMs, You should have to flash Android Q firmwares on Top. But i never did that when flashing LOS 17.1. I just rooted Miui 11 installed custom recovery (Orange Fox R11) & flashed LOS 17.1
Question 1: LOS 17.1 is FBE or FDE?
Question 2: If i want to move on to Bliss ROM 12.11 from my current LOS 17.1 (21.7 nightly), Formating data will be necessary? Or i can just wipe? So i don't loose my Internal storage.
Question 3: Does anyone know how to flash a firmware? BlissROM OP says flashing a firmware on the Top before flashing Rom.zip?
Question 4: If i want to backup (nandroid) my current OS (LOS 17.1) into the recovery. Exactly which partitions i should backup? So i can restore after trying Bliss ROM or if i get a bootloop or other issues (if needed). My Internal storage will be safe at that time aswell after restore?
My Current OS: LOS 17.1
Current Recovery: Orange Fox R11
Click to expand...
Click to collapse
1) LOS 17.1 is FBE
2) when changing ROM is recommended to clean flash and format data but you can try to install the new ROM without formatting data, in case of bootloop or issues booting the system the only solution is to format data or restore the nandroid backup of the previous ROM
3) download the latest stable firmware (for your region or the global one) from https://xiaomifirmwareupdater.com/firmware/lavender/ then just flash it in recovery
4) read carefully this post: https://forum.xda-developers.com/re...ngefox-recovery-project-t3941822/post79771469 remember to copy the backup to a safe place (external sd card or computer)
darhma said:
in case of bootloop or issues booting the system the only solution is to format data or restore the nandroid backup of the previous ROM
Click to expand...
Click to collapse
If i flash the firmware on the top first. & Clean flash the ROM but without formating data. & if the ROM bootloops, i can just format the data & reboot the system? I will have the working device with newly flashed ROM? Or i will have to re-flash the whole ROM. zip again after formatting the data if newly flashed ROM bootloops?
Necessary to know for me, Because i won't have ROM.zip into my internal storage then if i will format the data when the ROM bootloops.
In addition to what others have posted, I would add :
- you can flash firmware anyhow.
- only /data and internal storage parts. are needed in most cases to be backed up. But that depends on what you wanna backup. I personally do not recommend relying on nandroid backups for data because of encryption. It is a hit and miss and you dont wanna take the risk in regards to data I believe. Just use an app data backup tool instead.
- Efs, modem, persist partitions should be backed up at least once and should be saved in different places because they can help fixing rare issues of imei lost, fingerprint breaking etc
noobSU said:
If i flash the firmware on the top first. & Clean flash the ROM but without formating data. & if the ROM bootloops, i can just format the data & reboot the system? I will have the working device with newly flashed ROM? Or i will have to re-flash the whole ROM. zip again after formatting the data if newly flashed ROM bootloops?
Necessary to know for me, Because i won't have ROM.zip into my internal storage then if i will format the data when the ROM bootloops.
Click to expand...
Click to collapse
Format data after flashing the ROM and then rebooting the system should be ok and you don't need to reflash anything
I’ve just picked up a new Samsung Galaxy Tab s6 Lite and installed LineageOS on it. I’m using TWRP 3.5.0.
All was working great until today. I was using LineageOS 17.1 nightly 20210310 and had OpenGApps installed.
Today an update was available for Lineage so I updated using the Setup app. The upgrade went well but killed GApps.
I decided to do a fresh flash. I was having a problem with Android Audio which appears to be caused by OpenGApps. I’ve read that NikGApps doesn’t have this problem.
I copied the latest Lineage zip and NiksGApps zip to the device using ADB and booted into recovery. I used advanced wipe to remove the existing install. I’m only seeing options to wipe dalvik/ART Cache, Metadata, cache, data, internal storage, micro sd card, and usb otg. There is no system option. I wiped dalvik, metadata, cache, and data. I successfully flashed both Lineage and NiksGApps.
When I booted I found a very unstable system. Google services and apps crashed all the time.
I used the Format Data option this time followed by a wipe of the same four partitions. I rebooted back to recovery and installed LineageOS again. During the Lineage flash NiksGApps were backed up and restored. This surprises me. How could the data be available for backup after a format?
I’ve reflashed multiple times. I’ve tried both 17.1 and Linux4’s unofficial build of 18.1. I’ve tried OpenGApps and NiksGApps. I can’t get a stable install. I have had several flashes that wouldn’t even boot (booted into recovery). I'm currently in a non-booting state now.
Am I doing something wrong? Is there something wrong with TWRP? Should I use Lineage Recovery?
Thanks,
Bob
bdushok said:
I’ve just picked up a new Samsung Galaxy Tab s6 Lite and installed LineageOS on it. I’m using TWRP 3.5.0.
All was working great until today. I was using LineageOS 17.1 nightly 20210310 and had OpenGApps installed.
Today an update was available for Lineage so I updated using the Setup app. The upgrade went well but killed GApps.
I decided to do a fresh flash. I was having a problem with Android Audio which appears to be caused by OpenGApps. I’ve read that NikGApps doesn’t have this problem.
I copied the latest Lineage zip and NiksGApps zip to the device using ADB and booted into recovery. I used advanced wipe to remove the existing install. I’m only seeing options to wipe dalvik/ART Cache, Metadata, cache, data, internal storage, micro sd card, and usb otg. There is no system option. I wiped dalvik, metadata, cache, and data. I successfully flashed both Lineage and NiksGApps.
When I booted I found a very unstable system. Google services and apps crashed all the time.
I used the Format Data option this time followed by a wipe of the same four partitions. I rebooted back to recovery and installed LineageOS again. During the Lineage flash NiksGApps were backed up and restored. This surprises me. How could the data be available for backup after a format?
I’ve reflashed multiple times. I’ve tried both 17.1 and Linux4’s unofficial build of 18.1. I’ve tried OpenGApps and NiksGApps. I can’t get a stable install. I have had several flashes that wouldn’t even boot (booted into recovery). I'm currently in a non-booting state now.
Am I doing something wrong? Is there something wrong with TWRP? Should I use Lineage Recovery?
Thanks,
Bob
Click to expand...
Click to collapse
It's very likely caused by TWRP, I said multiple times to NOT use TWRP for installing OTAs exactly because of things like this.
TWRP is now discontinued anyways