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
Hello Guys,
I have been using xXx NoLimits 4.8 rom that is based on Oxygyn 4.5.15 ( android version 7.1.1) and now I would like to try Lineage 14.1.
I have TWRP 3.2.1 Blue Spark V8.61.
I wiped Data, Cache, System and Dalvik and flashed Lineage 14.1 and then flashed the addon supersu 64bit and then wipe dalvik and cache again and rebooted but the phone never booted into system. It kept on rebooting to the recovery or stuck in a bootloop.
I removed the PIN before I flashed Lineage 14.1 and my data partition is NOT encrypted
Any idea on what I am missing here?
Thanks
I had the same problem and I can't remember where I got the file from. But u flash it and the bootloop is gone this is what worked for me.
fidzi_1981 said:
Hello Guys,
I have been using xXx NoLimits 4.8 rom that is based on Oxygyn 4.5.15 ( android version 7.1.1) and now I would like to try Lineage 14.1.
I have TWRP 3.2.1 Blue Spark V8.61.
I wiped Data, Cache, System and Dalvik and flashed Lineage 14.1 and then flashed the addon supersu 64bit and then wipe dalvik and cache again and rebooted but the phone never booted into system. It kept on rebooting to the recovery or stuck in a bootloop.
I removed the PIN before I flashed Lineage 14.1 and my data partition is NOT encrypted
Any idea on what I am missing here?
Thanks
Click to expand...
Click to collapse
NOT encrypted mean you're decrypted? So with supersu you don't need to flash no verity, but instead of supersu try magisk and the no verity
Thanks
rolozombie said:
I had the same problem and I can't remember where I got the file from. But u flash it and the bootloop is gone this is what worked for me.
Click to expand...
Click to collapse
Thanks. This worked!
I have been researching the issue and I found out that since my DATA partition is decrypted and Lineage OS is an encrypted rom then bootloop occurs.
Thanks
Hitman478™ said:
NOT encrypted mean you're decrypted? So with supersu you don't need to flash no verity, but instead of supersu try magisk and the no verity
Click to expand...
Click to collapse
Correct. I meant to say that my data partition is decrypted.
What I ended up doing is flashing supersu addon from Lineage website followed by Magisk and then flashed no verity and everything works well so far
I also tried flashing supersu addon followed by no verity and it works too ( I wanted to give it a shot in case I decided I did not want to use magisk)
Thanks again for the tip!
***Problem Solved***
Hello All,
First of all, Iam a newbie in custom roms so i hope it's not a stupid question...
Couple of months ago i rooted my LG G2 en installed TWRP and after that i flashed Lineageos 14.1.
But i wanna try something else.
I flashed AOSP and works like a charm.
So i decided to flash another one.
But now my phone is stuck on a TWRP loop.
I aleady update twrp to a new version: 3.2.1.0 but it still not work.
What did i do:
Iam going to wipe.
Advanced wipe and wipe:
Dalvik/ART cache
System
Data
And cache
After that iam going to Install:
select the rom and the OpenGapps. (ARM 7.1 Nano)
And confirm flash.
After the flash i wipe Cache and Dalvik and then reboot..
But it's only starting in recovery again and again.
I have tried this roms:
Lineageos
ASOP
CRdroid
Paranoid Android
MK
Ressurection remix
But none of the roms will work
I also tried to wipe Internal storage but unfortunatly that also doesnt work
What iam doing wrong?
Or what can i do to get one of this roms to work?
Thank you
***Problem Solved***
I Found it!!
By Terminal i have to type a code and then another code.
My phone is working again.
Hello,
iam stuck in a Bootloop that goes straight back to twrp.
I got a refubirshed Mi 9 T with MIUI 11 and wanted to install LineageOS.
I unlocked my bootloader with the miflash_unlock tool (didnt had to wait).
Installed latest twrp (twrp-3.3.1-0-davinci.img)
Flashed twrp (fastboot.exe flash recovery twrp.img)
Wiped Dalvik, Cache, System, Vendor, Data
Installed LineageOS 17.1 and gapps nano
After that my Phone reboots straight into twrp and i dont know what to do or what i missed.
I set up a pattern so i guess my filesystem is encrypted but i dont know if it matters.
Does somebody know a solution?
Kind Regards
kartoffelmann said:
Hello,
iam stuck in a Bootloop that goes straight back to twrp.
I got a refubirshed Mi 9 T with MIUI 11 and wanted to install LineageOS.
I unlocked my bootloader with the miflash_unlock tool (didnt had to wait).
Installed latest twrp (twrp-3.3.1-0-davinci.img)
Flashed twrp (fastboot.exe flash recovery twrp.img)
Wiped Dalvik, Cache, System, Vendor, Data
Installed LineageOS 17.1 and gapps nano
After that my Phone reboots straight into twrp and i dont know what to do or what i missed.
I set up a pattern so i guess my filesystem is encrypted but i dont know if it matters.
Does somebody know a solution?
Kind Regards
Click to expand...
Click to collapse
Solved it.
I had to wipe the /data/ Partition
please push format data (button), reboot in twrp and install lineage too
If that doesn't work, you can install vbmeta