I converted a stable version of cyanogenmod into f2fs format. Everything was going well until I accidentally updated it and now it just sits on a bootloop. Anyone have any ideas how I can fix this without wiping. No i didnt get to create a nandroid.
lovesmyandroid said:
I converted a stable version of cyanogenmod into f2fs format. Everything was going well until I accidentally updated it and now it just sits on a bootloop. Anyone have any ideas how I can fix this without wiping. No i didnt get to create a nandroid.
Click to expand...
Click to collapse
The update you installed likely reformatted your system and cache partitions back to ext4. Try reformatting them and reflashing your ROM.
Alternatively, you could also try just flashing an f2fs-compatible kernel first to see if that gets it booting for you. That may be all you need if /data is still formatted as f2fs.
Did you used TWRP to convert to f2fs ?
Hey,
I have a Nexus 7 2012 32GB. It was previously running pretty slow but then I installed SlimKat with F2FS and it started running fine again and I'm very happy with it. Today and earlier this week, I tried installing Android 5.1.1 since I like the Lolipop UI but I was met with a major problem.. I tried the latest nightly of CyanogenMod 12.1, Dirty Unicorns 9.7 (and 9.8) and Blisspop and their problem is that after one boot, the /data partition got corrupted.. I tried repairing it but got ERR=255 and the only way to repair it was to change /data to ext4 and then format to f2fs back again. All four ROMs are confirmed to work with F2FS... I have reverted back to SlimKat 4.4.4 with a backup since it's the only ROM that doesn't corrupt my /data partition. The device doesn't boot when the data partition is damaged and the recovery sometimes crashes (I use TWRP 2.8.7.0). Is there a fix to this or will it be fixed in the future? I'd be happy to provide any logs needed. I use Opengapps pico altough I don't think that really matters. F2FS makes my device much faster but the corruption problem is too major for me..
Thanks,
Aurora
Hello, Everyone...... I unlocked the bootloader of my Moto G4 plus, installed a custom recovery (TWRP 3.1.0 Shreps) and tried to flash lineage OS latest build with Open Gapps pico, All i get is a bootloop. The same happens with Omnirom and other roms... So far only RR and Invicta OS booted up successfully.... rest others give me a bootloop... why? Did i miss something? Please Help me
Also the cache partition and data partition are formatted in f2fs....can anyone tell me the default formats of these two partitions? Maybe f2fs is creating an issue here?
Amogh Thambi said:
Hello, Everyone...... I unlocked the bootloader of my Moto G4 plus, installed a custom recovery (TWRP 3.1.0 Shreps) and tried to flash lineage OS latest build with Open Gapps pico, All i get is a bootloop. The same happens with Omnirom and other roms... So far only RR and Invicta OS booted up successfully.... rest others give me a bootloop... why? Did i miss something? Please Help me
Also the cache partition and data partition are formatted in f2fs....can anyone tell me the default formats of these two partitions? Maybe f2fs is creating an issue here?
Click to expand...
Click to collapse
Are you clean flashing ROM? (Wiping /system /data /cache /delvik-cache )
Anything else you are flashed with ROM and Gapps?
Try without GApps.
As I understand it, Invicta and RR have f2fs support for cache built in, whereas other ROMs may not have the support (there's a particular commit, if I recall).
The normal formats for cache and system are ext4 whereas data appears to be f2fs. You may wish to attempt formatting cache as ext4 and seeing if your device can boot.
Yes, It worked. Formatted cache to ext4 and it works. Thanks Bros. Facing issues with VOLTE in Lineage, Omni and AOSP extended. I placed my jio sim in sim 1 and enabled 'enhanced LTE' but still no luck with VOLTE.
Amogh Thambi said:
Yes, It worked. Formatted cache to ext4 and it works. Thanks Bros. Facing issues with VOLTE in Lineage, Omni and AOSP extended. I placed my jio sim in sim 1 and enabled 'enhanced LTE' but still no luck with VOLTE.
Click to expand...
Click to collapse
VoLTE doesn't works on LineageOS, you can try Unofficial Builds which may support VoLTE or you can try RR OS which supports VoLTE Natively
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
Hi folks,
I need some help. I have had my X820 I ordered from bangood for about a month now. I have tried a variety of ROMs on this device, and twrp-3.2.1-0-x2.img. This morning I tried to give the latest lineageOS a try. I did the typical wipes, and flashed lineageOS & gapps. After reboot google play started to throw all types of errors.
I booted back into TWRP, and this time it would only mount in read only. I tried the trick to change the /data partition fron ext2 back to ext4, did wipes again, installed ROM + Gapp, reboot but still have crashing playstore and google background processes.
I went from an already installed AICP to LOS. I did do a complete TWRP backup of AICP beforehand. The weird thing is that if I do a complete wipe again from TWRP, and do a fresh install of Pixel Experience [AOSP] all works normally. And after I did another wipe from TWRP after Pixel Experience, and restored my AICP backup all is working fine now both in TWRP & AICP. Has anyone had something simular happen like this before?
You have to install the latest unofficial TWRP build in order to use see your /data partition with the latest LineageOS installed. It's indicated on the thread's FAQ.