Related
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,
I have been using Derpfest on my Redmi Note 6 Pro for a long time. To flash the latest version, I wiped cache, dalvik cache and data (as per their instructions) and then flashed the full zip. For some reason, the phone does not boot anymore, it goes into Mi logo, reboots, and then boots into recovery.
I have tried clearing data, dalvik, cache, system and internal storage and then flashing two different custom ROMs (Derpfest and HavocOS) but it still does not work.
Can someone please help me recover my phone?
Thanks
Saad Ismail said:
Hi,
I have been using Derpfest on my Redmi Note 6 Pro for a long time. To flash the latest version, I wiped cache, dalvik cache and data (as per their instructions) and then flashed the full zip. For some reason, the phone does not boot anymore, it goes into Mi logo, reboots, and then boots into recovery.
I have tried clearing data, dalvik, cache, system and internal storage and then flashing two different custom ROMs (Derpfest and HavocOS) but it still does not work.
Can someone please help me recover my phone?
Thanks
Click to expand...
Click to collapse
Format data.
DarthJabba9 said:
Format data.
Click to expand...
Click to collapse
This worked, thank you so much. It's so bad I wasted whole day on this .-.
Flash the last miui rom. Recovery Edition. https://c.mi.com/thread-2959490-1-0.html?t=1585141449432&utm_source=share
Boot up and than install the rom you want.
Saad Ismail said:
This worked, thank you so much. It's so bad I wasted whole day on this .-.
Click to expand...
Click to collapse
The latest Derpfest uses a new kind of encryption (FBE). This requires formatting data if you were on an earlier version (or any other ROM) with FDE. This really should have been stated clearly in the Derpfest instructions and changelog (perhaps it was - I don't know). If you were using OrangeFox Recovery, you might have seen something (in red) about Android Rescue Party, advising clean-flashing the ROM.
im having big problems about vendor. for start im giving some info:
device: mi a1 (tissot)
current os: lineage OS 17.1
root: yes
twrp: can install or use just booting .img
i unlocked my device and installed twrp. there is no problem.
i wanted flash lineage OS and i wiped my device. gives error about cannot mount /vendor
i installed treble supported twrp and installed lineage OS. flashed magisk. installed microg...
then i tried flash mapsv1.zip which is recommended for microg. then booom. another /vendor error.
now i can boot device. i can use everything except gps. google maps app cannot found location. yandex maps can found and i can use it until lock screen or going main screen (or another app). then it starts stopping everytime until i clen its data and cache. then again... in chrome when i open google maps and try found my location chrome stops.
i tried to change /vendor/etc/gps.conf. its still same.
what to do now guys? im worrying about if i try re-flash rom it doesnt flash and device bricked. any solution without re-flash rom? what causes to cannot mount /vendor after solved it?
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
KaaMyA said:
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
Click to expand...
Click to collapse
Dalvik cache , system, data, and cache. My device is not rebooting too much. Sory if i couldn't explain. Everything working fine except when an app tries use my location, app stops running, i cant flash anything right now.
İ thought anyone knows mapsv1.zip file(microg.org) and which files are replaced or added by this file when flash it. And can i do it manually? Btw i can read and write /vendor file with solid explorer
İf needed to re-flash rom thats ok but i think lineage OS was perfect for me until this error. And a last thing: can i backup my settings. (İ already took backup of everything in stock when unlocked bl)
Thank you for help
Edit: gps problems started when i tried flash mapsv1
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
KaaMyA said:
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
Click to expand...
Click to collapse
Okey ilk try it and share the result night. But is it possible to backup settings of phone?
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
KaaMyA said:
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
Click to expand...
Click to collapse
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Nurullah44 said:
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Click to expand...
Click to collapse
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
portox said:
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
Click to expand...
Click to collapse
Are you sure? Bcs i can view and change /vendor in root path. Treblizing is updating and repairing system partitions right? İ am using treble support twrp, flashed stock rom via mi flash(said error but worked fine) then how to treblize a device? And is this required for anything(like a rom, an app)?
Hello guys
I know custom ROM since many phones (Samsung Notes 1, 2, Honor 5X, Xiaomi Note 6, 7, Samnsung Tab S2 ...)
the bootloader is open with the good tool
the pwrp recovery is installed (so fox if i want)
and many ROMS ares tested but only MIUI12.2 (20.9.24) is functionnaly
the ROMS like ...
- Resurrection Remix
- Syberian
- Pixel Experience
- Cr Droid
and so on
All are installed correctly but bootloop during the first boot
Whats the problem ?
Thanks
Olivier
Hi,
Have you tried to flash firmware first ? do you make clean install (i mean format and not just wipe date) ? And OrangeFox recommanded, more than TWRP.
Give a try to those solutions and let us know if you want
lemoineo said:
Hello guys
I know custom ROM since many phones (Samsung Notes 1, 2, Honor 5X, Xiaomi Note 6, 7, Samnsung Tab S2 ...)
the bootloader is open with the good tool
the pwrp recovery is installed (so fox if i want)
and many ROMS ares tested but only MIUI12.2 (20.9.24) is functionnaly
the ROMS like ...
- Resurrection Remix
- Syberian
- Pixel Experience
- Cr Droid
and so on
All are installed correctly but bootloop during the first boot
Whats the problem ?
Thanks
Olivier
Click to expand...
Click to collapse
Are you trying to install google apps as well?
lemoineo said:
Hello guys
I know custom ROM since many phones (Samsung Notes 1, 2, Honor 5X, Xiaomi Note 6, 7, Samnsung Tab S2 ...)
the bootloader is open with the good tool
the pwrp recovery is installed (so fox if i want)
and many ROMS ares tested but only MIUI12.2 (20.9.24) is functionnaly
the ROMS like ...
- Resurrection Remix
- Syberian
- Pixel Experience
- Cr Droid
and so on
All are installed correctly but bootloop during the first boot
Whats the problem ?
Thanks
Olivier
Click to expand...
Click to collapse
Use latest orangefox: format data then wipe system, data, cache, dalvik/cache, flash firmware (if needed), flash rom, flash gapps (if needed), flash magisk (optional). In case of bootloop format again data partition
There is a problem with encryption with the rn7 so you always need to format data when changing rom so it's important to have a backup of your personal data before changing rom
maybe something that I missed,
you talk about firmware, maybe it is the KERNEL?
Besides, I agree to lose the data, but maybe I didn't erase the reported partitions.
Well I will resume in the strict order indicated by your post
Thank you
I resume my procedure from ORANGEFOX Recovery:
deletion of DATA, SYSTEM, VENDOR, CACHE, DALVIK partitions
SYBERIA ROM installation (for example). GAPP APPS, MAGICK
and at boot, again, BOOTLOOP
So something is missing, but what?
Rebooting with erasure of the DATA paritition does not help
Thank you for your efforts:
Versions software:
OrangeFox lavender 10.1-3
Syberia lavender 3.8
Magisk 20.4
lemoineo said:
I resume my procedure from ORANGEFOX Recovery:
deletion of DATA, SYSTEM, VENDOR, CACHE, DALVIK partitions
SYBERIA ROM installation (for example). GAPP APPS, MAGICK
and at boot, again, BOOTLOOP
So something is missing, but what?
Rebooting with erasure of the DATA paritition does not help
Thank you for your efforts:
Versions software:
OrangeFox lavender 10.1-3
Syberia lavender 3.8
Magisk 20.4
Click to expand...
Click to collapse
Format data is different from wipe: in orangefox go to menu > manage partition > data > format data then type yes. Also use latest orangefox: https://orangefox.download/en/device/lavender
After installing version 11 of OrangeFox,
to format, I checked the only option
use rm -rf instead of formatting
and each time, formatted the partitions
SYSTEM, VENDOR, DATA,
wipe DAVILK and CACHE and Installation of different ROMs,
SYBERIA, AICP, PIXELEXPERIENCE or ATOM
with each time, OPEN_GAPPS, MAGISKR
same punishment, after launching the reboot, display of the boot images, and it turns, it turns ...
A little hopeless
thank you
Olivier
lemoineo said:
After installing version 11 of OrangeFox,
to format, I checked the only option
use rm -rf instead of formatting
and each time, formatted the partitions
SYSTEM, VENDOR, DATA,
wipe DAVILK and CACHE and Installation of different ROMs,
SYBERIA, AICP, PIXELEXPERIENCE or ATOM
with each time, OPEN_GAPPS, MAGISKR
same punishment, after launching the reboot, display of the boot images, and it turns, it turns ...
A little hopeless
thank you
Olivier
Click to expand...
Click to collapse
U read the how to? Maybe first read then make what to do and sometimes help to flash the required firmware
Sent from my Mi Note 10 using XDA Labs
joke19 said:
U read the how to? Maybe first read then make what to do and sometimes help to flash the required firmware
Click to expand...
Click to collapse
Nothing I read over wipe system or vendor by this rom
Best option is to go back to stock ROM with mi flash tool and don't relock your bootloader. Then step by step
Sent from my Mi Note 10 using XDA Labs
lemoineo said:
After installing version 11 of OrangeFox,
to format, I checked the only option
use rm -rf instead of formatting
and each time, formatted the partitions
SYSTEM, VENDOR, DATA,
wipe DAVILK and CACHE and Installation of different ROMs,
SYBERIA, AICP, PIXELEXPERIENCE or ATOM
with each time, OPEN_GAPPS, MAGISKR
same punishment, after launching the reboot, display of the boot images, and it turns, it turns ...
A little hopeless
thank you
Olivier
Click to expand...
Click to collapse
Instead of flashing 12 000 things, just go step by step and first, flash firmware as recommended : https://xiaomifirmwareupdater.com/firmware/lavender/ (global one for you i think. Check this thread too : https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871).
format data as previous user say (do no touch, erase, format other things, just do as he say ! do not touch vendor, etc...)
Then flash rom and NOTHING ELSE, in order to understand which flash is giving bootloop (maybe gapps, maybe magisk) : try this with Pixel Experience which doesn't require additionnal gapps or flashing magisk.
If you do this, nothing more, nothing less, reboot betwen steps, it MUST work.
Hello
My loop problem is solved (for this time), thanks to the information provided by darhma
For the other 12,000 times, I read your post carefully ?
I appreciate the proposed approach of breaking down the installation in stages, and I would certainly take advantage of it in another similar incident.
However, I do not understand the need to upgrade the FIRMWARE, since I am already on a stock ROM, and I do not measure the scope of this firmware, other than to change the version of ROM.
thank you for your patience
So the solution was to format and not just wipe, correct ?
21vm said:
Hi,
Have you tried to flash firmware first ? do you make clean install (i mean format and not just wipe date) ? And OrangeFox recommanded, more than TWRP.
Give a try to those solutions and let us know if you want
Click to expand...
Click to collapse
About the firmware, you have some information here. As i personnaly faced bootloop and/or error while flashing that was solved by flashing firmware, i thought it can be a solution for you too
Si je peux me permettre, do not hesitate to give details of how you solve the problem, as it can be useful for others users.
Anyway, happy to see that it works now for you : enjoy !
The problem I was having was mixing the WIPE function even with the option
"use rm -rf instead of formatting"
with the command proposed by @darhma sous OrangeFox
menu> manage partition> data> format data then type yes
Flashing the updated firmware didn't change anything
Thanks anyway for @ 21vm's suggestion, by reading the post on the firmware update, I understood its function.
in French, we speak of "micrologiciel", which I find is more meaningful.
Suddenly, this aspect completely escapes the notion of custom ROM, and therefore is under the exclusive control of XIAOMI (and the other manufacturers).
Thank you all
Hello friends how are you? I will try to be very brief and excuse me for my English
I recently bought a second-hand redmi note 7, and it came with the ROM Pixel Experience 2019 (Android 10) ... The fact is that I wanted to install the updated ROM Pixel Experience (Android 11 2021) and did the procedure to install the Recovery Fox Orange (The phone came with the recovery from Xiaomi).
In doing so, I performed the WIPE (Dalvik, Cache, Data, System) and proceeded to install the ROM from internal memory.
The ROM was installed correctly but when restarting it enters a Bootloop in the FastBoot and I have not been able to start ...
It is in Fastboot bootloop ... Please I need help, what can I do to start the Pixel Experience or what are the steps to follow? I heartily appreciate your help
Format data. you will need to type "YES" when doing it!!
so, format data, wipe evertyhing again, reboot to recovery, then install your rom and then have fun. hope it helps.
papppsanyi said:
Format data. you will need to type "YES" when doing it!!
so, format data, wipe evertyhing again, reboot to recovery, then install your rom and then have fun. hope it helps.
Click to expand...
Click to collapse
Bro i just did it but it is still in FastBoot ... What I did exactly was the following:
- Enter OrangeFox
- I did Format Data
- Then I Wipe from: Dalvik / ART Cache, Cache, System, Data
- Then copy the ROM Pixel Experience Plus Lavender 11 (PC to Phone USB)
- I gave Install and then restart
But still in Fastboot Boot .. D:
Try latest global stable firmware.
Had this problem with other rom and it was FW related
matthias1976 said:
Try latest global stable firmware.
Had this problem with other rom and it was FW related
Click to expand...
Click to collapse
Resolved! I just had to install the ROM from Xiaomi.EU (which started correctly) and then I proceeded to reinstall the Pixel Experience and this time it worked perfectly: D Thank you both very much