How to install custom ROM without bootloop - Xiaomi Redmi Note 7 Questions & Answers

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

Related

Problem with LineageOS

Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi
possi.rodrigo said:
Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi
Click to expand...
Click to collapse
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.
echo92 said:
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.
Click to expand...
Click to collapse
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!
possi.rodrigo said:
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!
Click to expand...
Click to collapse
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.
echo92 said:
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.
Click to expand...
Click to collapse
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?
possi.rodrigo said:
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?
Click to expand...
Click to collapse
I recall from what Silesh has mentioned is that the commits from ElementalX are present in his kernel, thus the benefits should be seen in the unofficial stock Lineage OS kernel and so you don't necessarily need the ElementalX kernel. If you wish to use the ElementalX kernel with the latest builds of Lineage OS-OMS, and there is nothing stopping you doing so, you need to flash the sensorhub firmware, else you'll lose sensors like your fingerprint sensor (if you have a G4 Plus, that is - I don't know if other sensors are affected on non-Plus models as well if you don't flash this). The firmware can be found here https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2723
To install said firmware if you need it (credit to rahulsnair for the procedure https://forum.xda-developers.com/showpost.php?p=70716729&postcount=170):
Download the zip and extract, you should get a sensorhubfw.bin file. Copy this .bin file to your adb directory.
Connect your device to your computer and check adb can detect your device using 'adb devices'
Staying in adb, execute the command 'adb push sensorhubfw.bin /etc/firmware' (without the quotation marks). This will copy the sensorhub file to the /etc/firmware directory on your phone.
Reboot and hopefully you should have sensors back.

Can't flash oreo roms

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

Phone boots into recovery after flashing an OTA

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.

Most custom roms dont work for me - Am i doing something wrong?

Hello! Since i got this device, every time i try to install any custom rom, sometimes i have a good luck and one of those works, but other times they dont, i just get an "Android Setup keeps failing" so i cant even do the initial setup. The only roms that worked for me for now are the PE BS and Corvus, i tried LOS, PE, Havoc and almost any other rom and i get this problem, tried roms with and without gapps, different gapps versions and build but i just keep getting this problem.
The way i install a rom its like this:
- Wipe dalvik, data, cache and system
- Format data
- Reboot recovery
- Flash latest fw
- Flash rom
- Reboot Recovery
- Flash magisk
And i just keep getting this issue :c skipping magisk but i just get the same problem. I dont know if someone have or had this problem and know how to solve it.
Thanks in advance!
Arthur King said:
Hello! Since i got this device, every time i try to install any custom rom, sometimes i have a good luck and one of those works, but other times they dont, i just get an "Android Setup keeps failing" so i cant even do the initial setup. The only roms that worked for me for now are the PE BS and Corvus, i tried LOS, PE, Havoc and almost any other rom and i get this problem, tried roms with and without gapps, different gapps versions and build but i just keep getting this problem.
The way i install a rom its like this:
- Wipe dalvik, data, cache and system
- Format data
- Reboot recovery
- Flash latest fw
- Flash rom
- Reboot Recovery
- Flash magisk
And i just keep getting this issue :c skipping magisk but i just get the same problem. I dont know if someone have or had this problem and know how to solve it.
Thanks in advance!
Click to expand...
Click to collapse
When you say "flash latest fw" what do you mean? Latest MIUI firmware? If yes why? You wipe everything just to install the firmware again?
It should be:
- Wipe dalvik, data, cache and system
- Format data
- Reboot to recovery (TWRP)
- Flash ROM
-Flash Gapps if wanted and not included in custom ROM
- Flash magisk
- Boot to system
Sent from my Mi 9T using XDA Labs
Wolfcity said:
When you say "flash latest fw" what do you mean? Latest MIUI firmware? If yes why? You wipe everything just to install the firmware again?
It should be:
- Wipe dalvik, data, cache and system
- Format data
- Reboot to recovery (TWRP)
- Flash ROM
-Flash Gapps if wanted and not included in custom ROM
- Flash magisk
- Boot to system
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
Yeah thats what i mean, and i flash it everytime because those times that i skipped that the rom didnt even booted, so i just assumed that its necessary. But also, tried the way you say it and still got the same result.
I think that i need to flash MIUI by fastboot for something like a "clean flash" because y tried everything even using the zip to skip the encryption but... Nothing, still the same :c
Arthur King said:
Yeah thats what i mean, and i flash it everytime because those times that i skipped that the rom didnt even booted, so i just assumed that its necessary. But also, tried the way you say it and still got the same result.
I think that i need to flash MIUI by fastboot for something like a "clean flash" because y tried everything even using the zip to skip the encryption but... Nothing, still the same :c
Click to expand...
Click to collapse
Best should be to follow the instructions by the ROM developer,
for example Arrow OS:
How to install:
Reboot to recovery
Wipe System , Cache, ART Cache and Data
Flash the ROM
Flash any addons (GApps, Magisk...)
Format data if you are encrypted
Reboot
(Formatting data is later here)
Or Bliss ROM:
First Time Install / Clean Flash
0. Flash proper firmware, latest firmware for your device variants.
1. Reboot to Recovery
2. Format data
3. Wipe system
4. Flash the ROM (DO NOT WIPE VENDOR, EVER)
5. Reboot to System
6. Reboot to Recovery
7. Flash Magisk (Optional)
8. Reboot to System
Sent from my Mi 9T using XDA Labs
Wolfcity said:
Best should be to follow the instructions by the ROM developer,
for example Arrow OS:
How to install:
Reboot to recovery
Wipe System , Cache, ART Cache and Data
Flash the ROM
Flash any addons (GApps, Magisk...)
Format data if you are encrypted
Reboot
(Formatting data is later here)
Or Bliss ROM:
First Time Install / Clean Flash
0. Flash proper firmware, latest firmware for your device variants.
1. Reboot to Recovery
2. Format data
3. Wipe system
4. Flash the ROM (DO NOT WIPE VENDOR, EVER)
5. Reboot to System
6. Reboot to Recovery
7. Flash Magisk (Optional)
8. Reboot to System
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
Yeah, i tried that too, like mixing steps, or changing when do i format data, skipping magisk and even on roms without gapps skipping gapps but still get the same results
I just dont know what to do
Arthur King said:
Yeah, i tried that too, like mixing steps, or changing when do i format data, skipping magisk and even on roms without gapps skipping gapps but still get the same results
I just dont know what to do
Click to expand...
Click to collapse
Best may be to ask a ROM developer by PM what could be the problem. I'm still on stock so my knowledge about it is more theoretical.
Sent from my Mi 9T using XDA Labs
edit : nvm wrong thread

Help!! Fastboot Bootloop RN7 - Pixel Experience Flash

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

Categories

Resources