Related
After flashing the latest global stable miui 10 ROM on mi max 3, I can't flash tarp without bootloop or stuck on mi logo. My device is Chinese version and before installing global stable miui 10, I flashed twrp successfully. Now I can't even flash eu ROM, it just sticks on mi logo. I tried with magisk, but unlucky. Anyone have the same experience? At last my decision is, this version of miui is the culprit, though I m not sure!
Can you give a bit more information?
What steps did you take and in which order?
mierlo420 said:
Can you give a bit more information?
What steps did you take and in which order?
Click to expand...
Click to collapse
Every possible order.
1st, flashed twrp/s
2. Formatted data, because it asked for password to decrypt
3. Mount every possible partition
4. Wipe all without 'system'
5. Flash eu ROM
6. And it stucks on boot.
And only possible sollution after this stuck for me is, to flash again a fastboot ROM. No recovery ROM at this stage gains a successful boot.
Note: I have to flash several times my phone fastboot ROM to recover phone and try again again. No success. Every time I try it starts from decrypt data option and stuck on boot. Even I tried with flashing magisk also, after flashing eu ROM. But no luck.
At a point I found 'reset phone' option and gboard has stopped bug, but whenever I try to reset, it goes to twrp.
Because global stable and TWRP don't work together. Have you seen anyone root global stable? I haven't. This is why global is not as versatile compared to xiaomi.eu roms.
opasha said:
Because global stable and TWRP don't work together. Have you seen anyone root global stable? I haven't. This yes why global is not as versatile compared to xiaomi.eu roms.
Click to expand...
Click to collapse
But, am i now stuck with no option for twrp or even no option to flash any custom rom like eu roms?
silentext said:
But, am i now stuck with no option for twrp or even no option to flash any custom rom like eu roms?
Click to expand...
Click to collapse
Did you try twrp app? Just as a test. Also try magisk app to install magisk to see if it helps. When we were testing Resurrected kernel, magisk was needed to get past boot screen. None if this is proven to work, but just trying to see if it helps.
opasha said:
Did you try twrp app? Just as a test. Also try magisk app to install magisk to see if it helps. When we were testing Resurrected kernel, magisk was needed to get past boot screen. None if this is proven to work, but just trying to see if it helps.
Click to expand...
Click to collapse
Yes, tried official twrp. Even tried official twrp with magisk. In both case it stuck with booting screen/mi logo. No luck.
Edit: my all tries are: twrp+reboot / twrp+eu rom+magisk+reboot / twrp+lagzyflasher+reboot..
All the combinations resulted in a bootloop/ stuck in mi logo. In every time the only work around to past the boot screen is to flash again a fastboot rom. Only that time it successfully boots.
silentext said:
Yes, tried official twrp. Even tried official twrp with magisk. In both case it stuck with booting screen/mi logo. No luck.
Click to expand...
Click to collapse
When you flash TWRP, you can boot to twrp or no? If you can, then it's when you flash an eu rom where you get stuck? Are you factory resetting before flashing eu rom?
opasha said:
When you flash TWRP, you can boot to twrp or no? If you can, then it's when you flash an eu rom where you get stuck? Are you factory resetting before flashing eu rom?
Click to expand...
Click to collapse
Yes, i can boot to twrp. And always reset to factory/wipe everything before and after flashing eu rom. As i edited my comment above, with just twrp+magisk+reset+reboot / twrp+reset+eurom+magisk+reset+boot every times it gets stuck on reboot after flash.
silentext said:
Yes, i can boot to twrp. And always reset to factory/wipe everything before and after flashing eu rom. As i edited my comment above, with just twrp+magisk+reset+reboot / twrp+reset+eurom+magisk+reset+boot every times it gets stuck on reboot after flash.
Click to expand...
Click to collapse
Who told you to reset after flashing? That's why you're having issues. Don't reset after eu or magisk.
Twrp - factory reset - eu rom - reboot. That's it.
opasha said:
Omg - who told you to reset after flashing! That's why you're having issues. Don't reset after eu or magisk.
Click to expand...
Click to collapse
Oh, no. After Flashing just wiped delvic and cache. It was adviced somewhere.
opasha said:
Who told you to reset after flashing? That's why you're having issues. Don't reset after eu or magisk.
Twrp - factory reset - eu rom - reboot. That's it.
Click to expand...
Click to collapse
But, sure, i m trying again with this plain instruction. Thanks a lot. Though i m sure, i did this plain combination before with no luck. Before flashing global stayble i have flashed eu roms and twrp several times with no trouble.
silentext said:
Oh, no. After Flashing just wiped delvic and cache. It was adviced somewhere.
Click to expand...
Click to collapse
Wiping cache and dalvik cache are not the same as reset. They shouldn't cause any problems. Regardless, try without wiping them.
opasha said:
Wiping cache and dalvik cache are not the same as reset. They shouldn't cause any problems. Regardless, try without wiping them.
Click to expand...
Click to collapse
just tried with your plain instruction. it again stuck with mi logo.
edit: i can reboot to recovery easily.
silentext said:
just tried with your plain instruction. it again stuck with mi logo.
edit: i can reboot to recovery easily.
Click to expand...
Click to collapse
Which eu rom are you flashing? Download the latest 8.10.25. Flash that.
opasha said:
Which eu rom are you flashing? Download the latest 8.10.25. Flash that.
Click to expand...
Click to collapse
yes. that one. 8.10.25.
silentext said:
yes. that one. 8.10.25.
Click to expand...
Click to collapse
Maybe try fastboot flash an ARB 8.10.25 china rom first - clean flash only - don't lock (very important setting at BOTTOM of Miflash Tool).
opasha said:
Maybe try fastboot flash an ARB 8.10.25 china rom first - clean flash only - don't lock (very important setting at BOTTOM of Miflash Tool).
Click to expand...
Click to collapse
oh. i tried that with china 8.10.30 version. because that was my first flash from so called fake global rom that shipped with. but that also didnt work.
silentext said:
oh. i tried that with china 8.10.30 version. because that was my first flash from so called fake global rom that shipped with. but that also didnt work.
Click to expand...
Click to collapse
Don't know what to tell you then. Sorry, buddy.
Try this
1- TWRP flashing method:
Boot Twrp or Redwolf using “fastboot boot XYZ.img”
Copy img to device then flash Image file of XYZ.img again from recovery.
Flash Lazyflasher Or Magisk
Or you can just flash any AOSP/LOS based ROM
Click to expand...
Click to collapse
I got this from Redmi Note 5 Anti-rollback thread here https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that
logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.
so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D
cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards
Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/
daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?
NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way
daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.
Hi everyone (pardon my English)
I have a Redmi Note 8 Global, and I am willing to install Custom ROM's on it.
I have read and watched several info about this subject, but there are some aspects I am not so clear about it.
I've never done it before, so first I need to dissipate some doubts. I'll appreciate your guidance.
My phone has the bootloader unlocked, and I have successful flashed it with MIUI Official fastboot ROMs three times with Mi Flash. First time with 12.0.6.0, months later with 12.5.1.0 and last time with 11.0.12.0 (and at present I'am still on 11.0.12.0).
Here there are my concerns and doubts:
- Decryption: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Rooting: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Is difficult to me to determine which Recovery to choose: TWRP, or Orange Fox ?
- Which Custom ROM for starting, based on Smoothness, Battery life, and Full functionalities: Pixel Experience 12, or Arrow OS 12 ?
- Can I install any Custom ROM no matter which one I have installed at the time ? For example: Going from Official MIUI 11.0.12.0 to Custom Pixel Experinece 12 ?
- Which are the real probabilities of soft or hard brick to happen during the process, and how to avoid it ?
- Is case of the worst scenario of soft or hard brick, can that be fixable ?
- Any direction to a concise detailed guide starting from the installation of the Custom Recovery to the Custom ROM flashing ?
- Is this hole Custom ROM flashing process completely reversible to the original factory state of the phone, if I want it someday ?
Thank you a lot in advanced, and pardon these so many questions. I really want it but don't want to messing up.
1. It is not beneficial, not mandatory, reversible, don't recommend
2. It's completely upto you
3. Go for OrangeFox
4. Pixel Experience 12. Using this rom as my daily driver. Super smooth
5. Yes you can do it anytime you wish.
6. Soft brick : It's like the phone is trying to boot but failing (somewhat like bootloop. Or sometimes if you shutdown your phone while it is flashing a rom then the software will be corrupted and you will see a message "Your system has been destroyed" this means the phone has been soft bricked and you can fix it just by flashing the MIUI rom using the MiFlash tool.
Hard brick: Your are fu***d up man. Your phone is now a piece of brick. To avoid this please make sure to check whether you are flashing the rom which is built for your phone. Like you have a ginkgo device (Codename for Redmi Note 8) but you flashed the rom built for curtana (Code name for Redmi Note 9) then your phone will be hardbricked and you can never ever use that motherboard
7. Like I said you can always fix a soft bricked phone but never a hard bricked one
8. You can always search youtube. As you have seen the Pixel experience just go to site https://wiki.pixelexperience.org/devices/ginkgo/install/
This guide is only for flashing pixel experience in ginkgo device
9. You can go back to MIUI anytime and again comeback to custom rom anytime you want
Evil_Hunter said:
1. It is not beneficial, not mandatory, reversible, don't recommend
2. It's completely upto you
3. Go for OrangeFox
4. Pixel Experience 12. Using this rom as my daily driver. Super smooth
5. Yes you can do it anytime you wish.
6. Soft brick : It's like the phone is trying to boot but failing (somewhat like bootloop. Or sometimes if you shutdown your phone while it is flashing a rom then the software will be corrupted and you will see a message "Your system has been destroyed" this means the phone has been soft bricked and you can fix it just by flashing the MIUI rom using the MiFlash tool.
Hard brick: Your are fu***d up man. Your phone is now a piece of brick. To avoid this please make sure to check whether you are flashing the rom which is built for your phone. Like you have a ginkgo device (Codename for Redmi Note 8) but you flashed the rom built for curtana (Code name for Redmi Note 9) then your phone will be hardbricked and you can never ever use that motherboard
7. Like I said you can always fix a soft bricked phone but never a hard bricked one
8. You can always search youtube. As you have seen the Pixel experience just go to site https://wiki.pixelexperience.org/devices/ginkgo/install/
This guide is only for flashing pixel experience in ginkgo device
9. You can go back to MIUI anytime and again comeback to custom rom anytime you want
Click to expand...
Click to collapse
Well, I don't know how to thank you enough. So, simply: THANKS VERY MUCH. That was a perfect and detailed answer. Thanks for your time and effort.
Just to be more precise about Questions 1 and 2: Do custom ROMs will work just fine on encrypted and non rooted phones?, I'm asking because i've seen some tutorials with decryption as a part of the process. I am intrigue and I wonder what are the Pros and Cons of decryption?
And with Question 6: So it is a fact that Soft brick is 100% fixable; and Hard brick only happens if I flash a Custom ROM of another phone model. So Hard brick will never happen as long as I always use the appropriate Custom ROM, right? Or there is more there?
Thanks a lot again.
lhn53 said:
Well, I don't know how to thank you enough. So, simply: THANKS VERY MUCH. That was a perfect and detailed answer. Thanks for your time and effort.
Just to be more precise about Questions 1 and 2: Do custom ROMs will work just fine on encrypted and non rooted phones?, I'm asking because i've seen some tutorials with decryption as a part of the process. I am intrigue and I wonder what are the Pros and Cons of decryption?
And with Question 6: So it is a fact that Soft brick is 100% fixable; and Hard brick only happens if I flash a Custom ROM of another phone model. So Hard brick will never happen as long as I always use the appropriate Custom ROM, right? Or there is more there?
Thanks a lot again.
Click to expand...
Click to collapse
Yes. I have my phone encrypted and not rooted and it is working just fine
Every developer of any custom rom gives a detailed guide about how to flash that rom. Follow that guide step by step and your phone will be safe
lhn53 said:
Hi everyone (pardon my English)
I have a Redmi Note 8 Global, and I am willing to install Custom ROM's on it.
I have read and watched several info about this subject, but there are some aspects I am not so clear about it.
I've never done it before, so first I need to dissipate some doubts. I'll appreciate your guidance.
My phone has the bootloader unlocked, and I have successful flashed it with MIUI Official fastboot ROMs three times with Mi Flash. First time with 12.0.6.0, months later with 12.5.1.0 and last time with 11.0.12.0 (and at present I'am still on 11.0.12.0).
Here there are my concerns and doubts:
- Decryption: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Rooting: Is it beneficial ? Mandatory ? Reversible ? What do you recommends ?
- Is difficult to me to determine which Recovery to choose: TWRP, or Orange Fox ?
- Which Custom ROM for starting, based on Smoothness, Battery life, and Full functionalities: Pixel Experience 12, or Arrow OS 12 ?
- Can I install any Custom ROM no matter which one I have installed at the time ? For example: Going from Official MIUI 11.0.12.0 to Custom Pixel Experinece 12 ?
- Which are the real probabilities of soft or hard brick to happen during the process, and how to avoid it ?
- Is case of the worst scenario of soft or hard brick, can that be fixable ?
- Any direction to a concise detailed guide starting from the installation of the Custom Recovery to the Custom ROM flashing ?
- Is this hole Custom ROM flashing process completely reversible to the original factory state of the phone, if I want it someday ?
Thank you a lot in advanced, and pardon these so many questions. I really want it but don't want to messing up.
Click to expand...
Click to collapse
1. Yes, it's beneficial in case your phone got stolen at least your data is secured, add more with pattern and fingerprints. Always go for enforcing rom and kernel for even more secure.
2. Depends: if you mostly work with secure apps such banking, no it's not. However some custom roms don't pass CTS, you'll have to root to gain it (it's needed for most banking apps)
3. Orange fox is preferable, though others like PBR, or official twrp is also good. It's just matter of preferences. Always get the clean one with source .
4. Official Lineageos is always the best path to taste open source android, since it's totally backed by open source community: no ads ridden links, clean source, guaranteed weekly build, etc.
5. Yes you can. Clean data is must (and format if you're encrypted) every time you switch between roms and between version (11 to 12, vice versa) or the rom's maintainer told you to do so.
6. Minimal. Just make backup your persist and efs partition using your recovery and you're good to go, but it very rarely happens.
7. Soft brick: forget to wipe/format data when flashing other roms, flashed bad kernel, etc. Hard brick mostly because doing some stupid stuff (flash wrong rom device with their firmware) or bad things happen unexpected (battery off during flash, etc)
8. Many from wiki pages on lineageos to youtube videos. In short: unlocked bootloader, flash recovery, backup, backup, backup, flash roms, format data
9. Yes, unless you did stupid stuff and made a hard brick, then it's EDL only
Well, thank you very much again to everyone. I really appreciate it, cause I'm really new to this, and I want to be the best prepared I can before doing this.
At the end, I know the path to take is custom ROM if I want to keep my RN8 the most updated possible.
I really didn't like the Officials MIUI 12 and MIUI 12.5 ROMs (even after fastboot them). Not for having a bad interface but for bad optimization in general. That's my humble opinion and experience with them. I ended up with MIUI 11 / Android 9... XD
(again, please pardon my English)
Doing some research I've found different guides that leads me to more questions:
- Catches my attention that in this guide: OFFICIAL Arrow OS Android 12 STABLE Redmi Note 8/8T (
),
the person flashed the original MIUI Firmware first. Why he did that? What are the differences between ROM and Firmware? Is it always necessary?
- Regarding the flashing of Orange Fox Recovery. In some videos I saw that the person doing the guide flashed the recovery in Windows with ADB commands and that's it. But in others guides I see the person flashing the recovery in Windows with ADB commands, then restart the phone and enter orange fox and flashed orange fox again within the proper Orange Fox. Which is the right way to do it?
- Regarding flashing ROMs: In other guides the person says that you have to Wipe/Clear Data before and after the ROM flashing. Others says is only before, and other says is only after. Which is the right way?
- Last but not least: I saw two Pixels Customs ROM: "PixelExperience", and "PixelOS". Which one is the most convenience?
Sorry again for so many question but as you can see it is confusing.
THANKS A LOT ...AGAIN !!!
lhn53 said:
Doing some research I've found different guides that leads me to more questions:
- Catches my attention that in this guide: OFFICIAL Arrow OS Android 12 STABLE Redmi Note 8/8T (
),
the person flashed the original MIUI Firmware first. Why he did that? What are the differences between ROM and Firmware? Is it always necessary?
- Regarding the flashing of Orange Fox Recovery. In some videos I saw that the person doing the guide flashed the recovery in Windows with ADB commands and that's it. But in others guides I see the person flashing the recovery in Windows with ADB commands, then restart the phone and enter orange fox and flashed orange fox again within the proper Orange Fox. Which is the right way to do it?
- Regarding flashing ROMs: In other guides the person says that you have to Wipe/Clear Data before and after the ROM flashing. Others says is only before, and other says is only after. Which is the right way?
- Last but not least: I saw two Pixels Customs ROM: "PixelExperience", and "PixelOS". Which one is the most convenience?
Sorry again for so many question but as you can see it is confusing.
THANKS A LOT ...AGAIN !!!
Click to expand...
Click to collapse
1. You have to flash firmware because the firmware contains the files of your wireless network. If you don't flash this your wireless network will not work
2. Let me make this clear. Many custom roms have a tendency to replace the custom recovery you flashed with the custom roms own recovery. If you just flash the custom recovery using ADB then the custom rom will replace the custom recovery with its own one. Like if you flash the orange fox and then flash pixel experience without flashing the orange fox again then pixel experience will wipe orange fox and then flash the PE recovery.
But if you install orange fox recovery through ADB and then enter orange fox and flash orangefox again you are just permanently turning off the option that the custom rom will change your custom recovery and put there custom recovery
3. As you are using a Xiaomi phone you have to wipe Dalvik, System, Vendor, Cache, Data before flashing the rom. Then after flashing the rom you have to format data / clear the data partition otherwise the phone will stuck in bootloop
4. Pixel OS and Pixel Experience are both somewhat alike. They try to bring the fluid performance and look of Pixel phones in a non pixel device. But many people prefer the Pixel Expereince rom. But trust me. Pixel OS is also good
Evil_Hunter said:
1. You have to flash firmware because the firmware contains the files of your wireless network. If you don't flash this your wireless network will not work
2. Let me make this clear. Many custom roms have a tendency to replace the custom recovery you flashed with the custom roms own recovery. If you just flash the custom recovery using ADB then the custom rom will replace the custom recovery with its own one. Like if you flash the orange fox and then flash pixel experience without flashing the orange fox again then pixel experience will wipe orange fox and then flash the PE recovery.
But if you install orange fox recovery through ADB and then enter orange fox and flash orangefox again you are just permanently turning off the option that the custom rom will change your custom recovery and put there custom recovery
3. As you are using a Xiaomi phone you have to wipe Dalvik, System, Vendor, Cache, Data before flashing the rom. Then after flashing the rom you have to format data / clear the data partition otherwise the phone will stuck in bootloop
4. Pixel OS and Pixel Experience are both somewhat alike. They try to bring the fluid performance and look of Pixel phones in a non pixel device. But many people prefer the Pixel Expereince rom. But trust me. Pixel OS is also good
Click to expand...
Click to collapse
Thanks again for such a good explanation. I appreciated.
Pardon me, but about the Firmware flashing is still kind of unclear for me, cause I didn't see this mentioned on many guides I've seen, only in that one I posted, and triggers my doubt.
About this:
- Do I always have to flash the firmware before the custom or original ROM?
- In which scenario is this necessary?
- If it is. Which version of firmware I need for every custom ROM I'll try? I mean, for example, LineageOS is Andorid 10, so do Firmware of MIUI 12 is needed?, Or if ArrowOS so do Firmware of MIUi 12.5 is needed? Etc etc.
Hope I could explain myself cause of my bad English.
Thanks a lot again and again.
Evil_Hunter said:
Let me make this clear. Many custom roms have a tendency to replace the custom recovery you flashed with the custom roms own recovery. If you just flash the custom recovery using ADB then the custom rom will replace the custom recovery with its own one. Like if you flash the orange fox and then flash pixel experience without flashing the orange fox again then pixel experience will wipe orange fox and then flash the PE recovery.
Click to expand...
Click to collapse
There is no such thing with custom roms
Only Official miui roms (and some few that come with "Recovery" file inside the zip) does that
so check the zip first ...
1st time you want to flash the recovery = flash "vbmeta" then Ofox and select :
"aggresive stock recovery deactivation" in Ofox settings
lhn53 said:
- Do I always have to flash the firmware before the custom or original ROM?
Click to expand...
Click to collapse
No
lhn53 said:
- In which scenario is this necessary?
Click to expand...
Click to collapse
FW have drivers for cam/Bt/wifi ...
you have to flash if you change Android version, for exp
from A? to A10 = flash A10 FW
from A? to A11 = flash A11 FW
lhn53 said:
- Which version of firmware
Click to expand...
Click to collapse
If you have Ginkgo = flash Ginkgo
If you have Willow = flash Willow
(don't make mistake with fw ! you will break your device)
i didn't read everything (too much) just follow the clean flash steps and you will be fine
stay away from A12 (not very stable)
A11 is resource hungry
i suggest using A10 (RRos or MSM Ext or Superior) (i use RRos)
loopypalm said:
There is no such thing with custom roms
Only Official miui roms (and some few that come with "Recovery" file inside the zip) does that
so check the zip first ...
1st time you want to flash the recovery = flash "vbmeta" then Ofox and select :
"aggresive stock recovery deactivation" in Ofox settings
No
FW have drivers for cam/Bt/wifi ...
you have to flash if you change Android version, for exp
from A? to A10 = flash A10 FW
from A? to A11 = flash A11 FW
If you have Ginkgo = flash Ginkgo
If you have Willow = flash Willow
(don't make mistake with fw ! you will break your device)
i didn't read everything (too much) just follow the clean flash steps and you will be fine
stay away from A12 (not very stable)
A11 is resource hungry
i suggest using A10 (RRos or MSM Ext or Superior) (i use RRos)
Click to expand...
Click to collapse
Perfect. Thanks a lot to all.
And LineageOS? Is it worth it?
So for example, if I want LineageOS 17.1 (that is A10), I have to flash first MIUI latest FW based on A10? And which version of MIUI FW do I need, the last one? For that example would be 12.0.6.0. isn't it? ...and so on with other Custom ROMs?
Is this site for that matters...?:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
lhn53 said:
And LineageOS? Is it worth it?
Click to expand...
Click to collapse
Lineage17 is A10 and that's it (nothing more)
RRos = Lineage + customization (both based on the same exact thing)
lhn53 said:
So for example, if I want LineageOS 17.1 (that is A10), I have to flash first MIUI latest FW based on A10?
Click to expand...
Click to collapse
Yes, latest stable
lhn53 said:
And which version of MIUI FW do I need, the last one? For that example would be 12.0.6.0. isn't it? ...and
Click to expand...
Click to collapse
Yes
lhn53 said:
so on with other Custom ROMs?
Click to expand...
Click to collapse
Only If you change Android version
if from A10 to A10 = no need
lhn53 said:
is this site for that matters...?:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Redmi note 8 = Ginkgo
Redmi note 8 "T" =Willow
loopypalm said:
Lineage17 is A10 and that's it (nothing more)
RRos = Lineage + customization (both based on the same exact thing)
Yes, latest stable
Yes
Only If you change Android version
if from A10 to A10 = no need
Redmi note 8 = Ginkgo
Redmi note 8 "T" =Willow
Click to expand...
Click to collapse
Hi, I reiterate my thanks to everyone for the help.
It is evident you prefer RRos. I'll take it into account.
Now it is clear that the FW has to be the same Android version as the ROM:
1- But the latest MIUI for the RN8 is based on A11, so what FW do you use for the A12 ROMs? The FW of MIUI 12.5.1.0?
2- Do you have to flash the FW every time you install a new ROM, or only if you change the version of Android?
3- This matter of flashing the FW do I have to do it in a specific way, or is it handled by Orange Fox as the ROM?
4- I am currently using MIUI 11.0.12.0 Android 9. If I want to install RRos which is based on A10, do I have to flash MIUI 12.0.6.0 FW first?
I'm planing on using OrangeFox... Starting from the fact that I only have the Bootloader unlocked, is it too much to ask if you would write me a concise and simple guide on how to achieve this? Or point me to one as alike as possible to my case?
I know that time is gold, and I do not want to abuse your time, so I will appreciate any help you can provide. I am grateful already for all the help shown so far.
THANKS
lhn53 said:
1- But the ...
so what FW do you use for the A12 ROMs?
Click to expand...
Click to collapse
It looks like you look for problems
lhn53 said:
2- Do you have to flash the FW every time you install a new ROM, or only if you change the version of Android?
Click to expand...
Click to collapse
Re read what i wrote previously
lhn53 said:
3- This matter of flashing the FW do I have to do it in a specific way, or is it handled by Orange Fox as the ROM?
Click to expand...
Click to collapse
Same as the rom, flash like any zip
lhn53 said:
4- I am currently using MIUI 11.0.12.0 Android 9. If I want to install RRos which is based on A10, do I have to flash MIUI 12.0.6.0 FW first?
Click to expand...
Click to collapse
you serious ?
lhn53 said:
Starting from the fact that I only have the Bootloader unlocked
Click to expand...
Click to collapse
-Reboot
-hold Vol- to go to fastboot
-flash vbmeta using : (assuming the img is named vbmeta.img)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(you can find vbmeta it in any A10 rom zip)
-flash twrp
-reboot to recovery (NOT SYSTEM !) using vol+
-flash Ofox zip
-set : "aggresive stock recovery deactivation" in Ofox settings
-clean flash the rom as already mentioned
-done
loopypalm said:
It looks like you look for problems
Re read what i wrote previously
Same as the rom, flash like any zip
you serious ?
-Reboot
-hold Vol- to go to fastboot
-flash vbmeta using : (assuming the img is named vbmeta.img)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(you can find vbmeta it in any A10 rom zip)
-flash twrp
-reboot to recovery (NOT SYSTEM !) using vol+
-flash Ofox zip
-set : "aggresive stock recovery deactivation" in Ofox settings
-clean flash the rom as already mentioned
-done
Click to expand...
Click to collapse
Thanks a lot.
loopypalm said:
you serious ?
Click to expand...
Click to collapse
Yes. I have to say I'm taking really serious regarding all about this process. Believe me, I have to minimized as much that is possible the risks on breaking my phone. It is REALLY expensive buying or fixing it where I life. I need to double check every important aspect, and try to understand the more I can about this. I don't like too much learning things mechanically, if I can learn the logic behind.
Pardon me all If I bothered you any how. Wasn't my intention.
Really appreciate the guide and help that everybody give me here. Thanks
lhn53 said:
Yes. I have to say I'm taking ...
Click to expand...
Click to collapse
The question has been answered like 3 times
Re read what i wrote
loopypalm said:
The question has been answered like 3 times
Re read what i wrote
Click to expand...
Click to collapse
Well, yes, you are right. I asked about the FW flashing process various times.
But, see, I've been investigating to changing the ROM of my phone for various days, and for that I watched some videos tutorials and guides in sites.
When I thought I was almost ready to start, I found a video where a person was flashing a Custom ROM and first flashed a Firmware and then the ROM (I mentioned this before). And in my case that video was the 1st time where I was hearding the term "firmware" in a Custom ROM flashing guide. Sawing that, I was like: Whaaaat? Then because of it I had to postergate the flashing of my phone and keep digging, cause I knew that the "firmware" is really important in every electronic equipment. Messing with it is dangerous.
I admit again the constants askings about FW, ...sorry about that. What I have just explained here were the true cause. I just needed to be more sure.
So I ended up here at XDA searching for learning and to clear doubts.
Thx u and everyone for your patient. I'll try not to bother too often.
@lhn53 : if you're that unsure, my advice would be to proceed cautiously and step-by-step, ensuring you can back out any major ****-up.
- Get MiFlash and the appropriate recovery stock ROM (in the worst case scenario, it will allow you to revert back to stock);
- Set up a custom recovery, ensure that it sticks, then familiarize yourself with it (you have multiple choices: TWRP, OrangeFox and PBRP);
- Choose the custom ROM you want to flash and read all related resources at least twice; then,
- Try to follow the procedure explained by the developer to the point, so if anything goes awry you can point to where it diverged;
- That applies to changing or updating firmware, just go with what the dev says on first instance;
- Finally, trust loopypalm, he knows what he's talking about and has been here longer than most.
Hi, thanks for replaying pnin and of course loopypalm, and everybody helping here.
It's just that when you see searching the WEB so many criteria and some differ from each other, doubts grow in a newbie like me. As I mentioned before there are many tutorials in the web where they do not mention the firmware as part of the steps and less about vbmeta.
For me It seemed quite simple at first but now I see it has more important steps to take into account.
pnin said:
- Get MiFlash and the appropriate recovery stock ROM (in the worst case scenario, it will allow you to revert back to stock);
Click to expand...
Click to collapse
...yes, I have MiFlash and various fastboot versions of the stock ROM storaged here.
pnin said:
- Choose the custom ROM you want to flash and read all related resources at least twice; then,
Click to expand...
Click to collapse
Yes, I guess I'll use first the ones with A10 (as advised here).
pnin said:
- Finally, trust loopypalm, he knows what he's talking about and has been here longer than most.
Click to expand...
Click to collapse
Agreed, thx.
pnin said:
- Set up a custom recovery, ensure that it sticks, then familiarize yourself with it (you have multiple choices: TWRP, OrangeFox and PBRP);
Click to expand...
Click to collapse
...with "sticks" I guess you are meaning what loopypalm said before: (...
1st time you want to flash the recovery = flash "vbmeta" then Ofox and select :
"aggresive stock recovery deactivation" in Ofox settings...)
Regarding vbmeta I have some questions (please be patient):
I've search about it, and I see It's like the Secure Boot of Windows.
I have seen various criteria: I saw people saying it is not needed in all RN8, and some says it does, for avoiding bootloop, etc. IMHO I guess that it is better to do it. Right? (...my intention is only of clarifying).
- The vbmeta.img file that is needed is the one inside Xiaomi's fastboot stock ROM compressed file. Is it?
- Is it necessary to flash vbmeta on every installation of a new ROM, or only when it is based on a different Android version?
- In case I want to return to Stock MIUI, this vbmeta step will not be necessary. Ins't? As I have understood, this is done simply with MiFlash..., Or first is it convenient to wipe some data or partitions with Custom Recovery? How would be exactly?
Please remember, I am trying to understand as much as I can about the whole process. In cases like these I like to learn by logic whenever is possible. Thanks a LOT once again.
lhn53 said:
- The vbmeta.img file that is needed is the one inside Xiaomi's fastboot stock ROM compressed file. Is it?
Click to expand...
Click to collapse
Please I only need to know this about vbmeta.
That plus everything that you have described me before, I think would be already all the basis that is needed to start.
Thanks you in advance.
(I'v been using Google Translate for helping me redacting all that I post. Pardon my bad English)
Deleted
Does this need a12 firmware? If so you should post dtbo and vendor_boot images.
gillim74 said:
Does this need a12 firmware? If so you should post dtbo and vendor_boot images.
Click to expand...
Click to collapse
wait for official Update
The boot image isnt working at all, after restarting into recovery mode i end up in bootloader. im on the latest oos 11 (11.2.10.10 BA)
edit:
sadly there are no install instructions on how to flash, found out that oos 12 is needed and the flash files are in the download repo (Image files folder)
A - Reboot to bootloader
fastboot flash dtbo "dtbo.img"
fastboot flash vendor_boot "vendor_boot.img"
fastboot flash boot "boot_img"
B - Fastboot reboot recovery
Perform factory data reset
Apply update from sideload
adb sideload "file name.zip"
C -Reboot system
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
Flashed yesterday without any issues. To get the boot, vendor_boot, and dtbo i used payload extraction. Changelog states CTS to pass by default, however it fails until Zygisk is enabled. Custom FOD icons are not working. Audio & mic (oos12) bug is present. Flashed BluSpark kernel about an 1hr. ago. Without issue.
Overall seems to be very stable with many options! Great Job! LE2125.
Flashed this but was having issues with haptic/vibrate feedback, they're not working.
Fyi BluSpark kernel fixes this
Advali said:
Flashed this but was having issues with haptic/vibrate feedback, they're not working.
Click to expand...
Click to collapse
cave.man1908 said:
Fyi BluSpark kernel fixes this
Click to expand...
Click to collapse
Bluspark doesn't work on LE2120. Already tried this 3x and it f'd up my phone and had to reinstall again.
Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.
Reremoll said:
Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.
Click to expand...
Click to collapse
Yes you flash this over OS12. make sure u have OS12 on both slots(if ur on c48 just download and local update once again to have on both sides). Then u have to download this rom, extract it on ur pc, so u can flash(in fastboot) dtbo, vendor_boot and boot. Then boot to recovery, wipe and adb sideload rom.
blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.
break.cold said:
blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.
Click to expand...
Click to collapse
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125
I've tried 4 roms yday and blu spark sometimes make you bootloop or doesn't want to flash which is weird.
After a few rom re-installs it worked on every rom I tried.
cave.man1908 said:
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125
Click to expand...
Click to collapse
I tried blu-spark of StagOS, Pixel Extended, Project ELixir, it keep sending me back to fastboot menu, however, its works on riceDroid without issue.
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
sourav24071999 said:
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
Click to expand...
Click to collapse
Well, I wouldn't have had "bad behavior" if you weren't trying to control what I did with my own Telegram group.
MOD ACTION:
Thread closed since OP has been edited removing content.