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
Before going into the subject, I'll say that I have tried to seach this matter in XDA and Google, but nothing showed up.
Okay, so my matter is that I can't restore my backup of stock rom(8.0) after I flash a 8.1 rom. I've backuped with official TWRP "recovery-3.2.1-2-oreo.img".
My procedures are :
back up stock 8.0(system, data, cache, efs) with official TWRP "recovery-3.2.1-2-oreo.img"
flash oreo rom(with wiping internel, data, system, cache) and boot it fine.
restore my stock backup with same TWRP
boot system
The results are :
Goes past boot logo
Boot animation('android one' with colors sliding) shows up
and... just infinite loop of boot animation.
The ROM I used is RR.
I think the main problem is related with encryption.... Just my thought, tho.
So what I'm asking is :
1. If you face the same problem as me?
2. If you aren't and you restore goes fine, please tell me your procedures including ROM used and TWRP used.
3. Whether it is safe to decrypt stock rom?
Thanks in advance!
You don't need to flash stock ROM again. You have a system image backup(system, data, cache, efs), right? Wipe data , system, cache if you are coming from any other ROM. Then reboot to bootloader. Boot into latest TWRP from Fastboot (don't flash). Then go to restore and restore the system image you had backed up. Don't restore efs if you haven't lost your IMEI.
I've done exactly as ypu told, but it doesn't boot...
Did you manage to restore without problem with your method?
Yes I was able to. No problem here.
What TWRP did you use? Also, what ROM have you flashed?
Used the latest TWRP by MohanCM for Oreo. I did it when I was on Lineage os and wanted to go to stock
@guy_infinity Okay, thanks for your answer! Gonna try out later, once more.
Hmmm.... Still didn't boot up.
I thought I had to do everything from the begining, but flashing stock with save userdata option rescued me.
P.S. does anyone know about the error E: recv error on uevent?
try flashing stock rom using mi flash and after flashing restore normally using latest twrp/deadman's without system image voila everything will be back
@arjunbalan1994 Big thanks for your suggestion! Will try that too later
Hi, did you solve your restore problem? I have the same w/ my Redmi Note 5 and stock Miui backup after flashing RR.
Thanks for your help
I was use 8.1 root and twrp recovery. Yesterday fastboot flash may rom and update 2nd may OTA
Don't understand : May rom is Miui rom?
And did you restore your miui rom 8.0 backup ith twpr after the fastboot flash stock?
Hello everybody
So this is weird asf..
So I got Mi 9T with MIUI 10.3.7 EEA stock rom. TWRP and Magisk flashed. I wanted to update MIUI to the latest 10.3.12 and I found a method online to update via TWRP by flashing the new MIUI stock rom then flashing a zip "Lazyflasher-no-verity-opt-encrypt.zip".
I backed up (system, data, boot) and then wiped (sys, data, catch, dal/art), then flashed the newer MIUI rom, then Lazyflasher zip. But I got an error installing Lazyflasher. So I wiped and restored my backup and the device booted into system. But then I discovered that the system is acting crazy. Fingerprint, wifi, all sensors aren't working.. etc.
I tried re-restoring my back ups, and tried wiping Dalvil/Art cache, Data and, Cache (TWRP factory rest) but nothing changed.
I'm considering flashing stock room but I don't want to lose bootloader unlocking and wait again.
Any suggestions?
Thanks in advance
Hi guys can someone help me? I have rn7 128 global with corvus rom for almost 2years now and recently my device shutdown and stuck in bootlogo so i try to navigate it using twrp and once i click reboot it says no OS installed so i decided to go back to stock rom i downloaded the fastboot stock rom and while I'm trying to flash it using fashboot in miflash tool it always says Flashing for almost 30 minutes and nothing happens and i try to disconnect it on my laptop and try to go on recovery mode the twrp is gone. So i decided to install again the twrp.img on cmd and i got the twrp and i transferred the corvus v7.0 again from my laptop to my device while im in twrp but i just noticed from 128 it says 9gb available so after flashing the corvus rom again i set it up and try to install messenger and fb but it says no storage available and once i check the storage it showing i only have 9gb I don't know what happened my device is having 128 but it only showing 9gb total and 8.93 gb available i dont know what to do
You format not wipe in twrp the data partition?
I wipe the cache dalvik and the system. I already fixed the issue of the partition now it showing the true 128gb on my rn7 but the problem is still on bootloop i already have the corvus rom I don't know how to go back on stock rom or what rom can i flash to use my device like before?
joke19 said:
You format not wipe in twrp the data partition?
Click to expand...
Click to collapse
kenmark28 said:
I wipe the cache dalvik and the system. I already fixed the issue of the partition now it showing the true 128gb on my rn7 but the problem is still on bootloop i already have the corvus rom I don't know how to go back on stock rom or what rom can i flash to use my device like before?
Click to expand...
Click to collapse
Not wipe, format the data partition after flashing
I flashed TWRP recovery I used last week, to install SparkOS and I do remember following a tutorial that said wipe Dalvik, Cache, Data, System and Vendor, which I did successfully and installed the custom rom. I didn't last much and reverted to Stock Rom.
Cut to yesterday I flashed the same recovery as last time, and when I went to wipe the partitions I didn't find Vendor. Checked Mount menu clicked on Vendor it didn't show up under Wipe.
Should I ignore this and continue with installing my custom rom after wiping (Dalvik, Cache, Data and system only) or this is a problem and I am not able to install any custom rom until I wipe Vendor Partition?
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
I followed it step by step, but I'm gonna try different versions and see if shows up. Otherwise I'll revert back to stock and hang my hat.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Ikarisdruig said:
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Click to expand...
Click to collapse
welcome