Cannot do anything with my phone. This error keeps popping up. I do not know how it started!!!
just so that u all know, i have re-flashed SOKP ROM, clean installed, wiped data, factory reset, cache dalvik, installed another ROM (PACMAN) but still it keeps popping up. please someone help.
TacTieTee said:
just so that u all know, i have re-flashed SOKP ROM, clean installed, wiped data, factory reset, cache dalvik, installed another ROM (PACMAN) but still it keeps popping up. please someone help.
Click to expand...
Click to collapse
read carefully and flash it on proper way. and make sure you will not flash any kitkat rom on lillipop.
this error comes because of dirty flash.
The problem started yesterday. Did an OTA update from CM11 to CM12 but it caused so many problems so I booted to TWRP, wiped everything clean, transferred CM12 to my via Fastboot and did a clean install. Rebooted and it just lingers on the boot logo for ages. I tried the wipe and install again, same problem. I wiped my dalvik & cache, same problem....
So I thought maybe that version of CM was just buggy so I wiped again, transferred Resurrection Remix via Fastboot and installed that. It was at the boot logo for an hour before I gave up and turned it off.
I've never had a problem like this which has spanned between different roms, what could be the problem? I'm installing stock now, hopefully that works so I can try again
L3534N said:
The problem started yesterday. Did an OTA update from CM11 to CM12 but it caused so many problems so I booted to TWRP, wiped everything clean, transferred CM12 to my via Fastboot and did a clean install. Rebooted and it just lingers on the boot logo for ages. I tried the wipe and install again, same problem. I wiped my dalvik & cache, same problem....
So I thought maybe that version of CM was just buggy so I wiped again, transferred Resurrection Remix via Fastboot and installed that. It was at the boot logo for an hour before I gave up and turned it off.
I've never had a problem like this which has spanned between different roms, what could be the problem? I'm installing stock now, hopefully that works so I can try again
Click to expand...
Click to collapse
If you note a problem like this after installing a rom, i think you can try format data, not a simple wipe but a format in twrp
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
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
UPDATE: I did do something stupid after all. I forgot that my Oneplus was decrypted. So all I had to do was go into TWRP and go to Wipe and format data to re-encrypt it.
Z-Blade said:
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
Click to expand...
Click to collapse
When starting fresh, wiping of internal storage should be considered. I recommended 2 guides here https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post77205633
I'd wiped out everything off this Nexus 10 tablet. I'd found it in a box of old stuff. Thought I'd start off with a fresh install.
Problem is that now I can't load anything. Every attempt at installing any ROM meets with errors. Using TWRP 2.8.7.0 that was on it. I had used advanced wipe and deleted everything. After each attempt at installing a ROM zip, I did a Dalvik and cache wipe as well.
So, before I end up trashing the old thing, is there some solution that I'm not knowing that would enable me to complete a restore?
Enclosed is a pic of what I'm seeing.
Thanks
Devildoc
Try get a os made for your device if that doesnt help get the latest twrp recovery