Develop Bugs

Can't get back to miui rom

OK so I flashed aospa/los they are working fine. Wanted to try miui 9 so did advance wipe including data wipe. Now after flashing miui it says no is found in twrp. Restoring miui 8 its stuck on boot logo.
Flashing aospa/los is fine but can't get back to miui.
What can I do?

ermacwins said:
OK so I flashed aospa/los they are working fine. Wanted to try miui 9 so did advance wipe including data wipe. Now after flashing miui it says no is found in twrp. Restoring miui 8 its stuck on boot logo.
Flashing aospa/los is fine but can't get back to miui.
What can I do?
Click to expand...
Click to collapse
I'd try fastboot flashing with the MiFlash tool
On the MIUI forum they seem to use this as the best way to get back to stock.
It even has a "clean and lock" option to set the phone back to clean ROM and locked bootloader.
Pretty good actually.
Can grab the fastboot firmwares from en.miui.com and then tool as well.
Guides are easy to find on there as well.
Just extract the fastboot package (.tgz)
Then unpack the file from there (yeah I know twice ergh)
And then point the flash tool to the folder this creates.
Then you should be safe to flash.
That will get you back to clean device then you can install TWRP with fastboot again.
I'd go for the Global Developer ROM it's so much better than Stable.
And here's a tip for free: in developer settings disable "MIUI optimization" and set the memory optimization to "off". Makes it so much smoother and battery lasts longer as tasks aren't killed every 5 mins....

So I flashed a global v8 ROM and that worked. Had to install twrp again. Now when I flashed v9 eu ROM after standard wipe, its just on the boot logo with powered by android.

ermacwins said:
So I flashed a global v8 ROM and that worked. Had to install twrp again. Now when I flashed v9 eu ROM after standard wipe, its just on the boot logo with powered by android.
Click to expand...
Click to collapse
I think you need to use fastboot.
I think normally it would work but one of your partitions must be messed up from another Rom.
It's rare but it does happen and full flashes are needed.
At least MIUI 8 worked

Dobsgw said:
I think you need to use fastboot.
I think normally it would work but one of your partitions must be messed up from another Rom.
It's rare but it does happen and full flashes are needed.
At least MIUI 8 worked
Click to expand...
Click to collapse
I'm gonna try 1 more time with this weeks EU rom but eventually will be on a non miui rom

ermacwins said:
I'm gonna try 1 more time with this weeks EU rom but eventually will be on a non miui rom
Click to expand...
Click to collapse
Tbh it may be a complete waste of time.
If you like pure android feel then you won't like MIUI much.
It was okay but its basically what iOS would be if Apple got their sh*t together and gave users more control.
I think that's what Xiaomi was aiming for really as they copy a lot of Apple design types.
Which for is means good hardware and choice of softwares so its definitely a plus.
BL unlock was a dream

Dobsgw said:
Tbh it may be a complete waste of time.
If you like pure android feel then you won't like MIUI much.
It was okay but its basically what iOS would be if Apple got their sh*t together and gave users more control.
I think that's what Xiaomi was aiming for really as they copy a lot of Apple design types.
Which for is means good hardware and choice of softwares so its definitely a plus.
BL unlock was a dream
Click to expand...
Click to collapse
Miui was very good a few days then it started to get bloated so I moved away from it. They get some things right but pure android has improved a lot.
Which rom you rocking now?

ermacwins said:
Miui was very good a few days then it started to get bloated so I moved away from it. They get some things right but pure android has improved a lot.
Which rom you rocking now?
Click to expand...
Click to collapse
LineageOS Nougat.
Not so amazing for visual customisation, but definitely the most stable which means creating mods or adding them isn't as likely to cause issues.
I just want a ROM close to AOSP with all the features of the phone working like fast charging.
AOSPA looks good too.

Just flash again with fastboot ROM and mi-flash tool.

So I just got the OnePlus 5T and wanted to do a speed test comparison for my YouTube channel. I noticed temple run 2 exits. So want to try EU ROM but it gets stuck on bootlogo. Does anyone have a link to the fastboot ROM? Can only find an old one. I can flash the global ROM through with twrp which works fine. Flashing EU ROM fails.
Also will flashing through fastboot lock the bootloader?

I think you should wipe everything and wipe data if you have fbe because it messes up things

So I flashed a stock rom (sagit_global_images_V8.2.2.0.NCAMIEC) with mi flash tool. Unlocked it, installed twrp. Now flashed latest rom eu rom and its stuck on bootlogo still
ARGHHHHHH

Finally worked
After flashing EU ROM, enter fastboot mode and type
fastboot format userdata
(This will format all the data on your phone)
Reboot. Done.
Click to expand...
Click to collapse
https://xiaomi.eu/community/threads...mi-logo-after-flash-eu-rom.39979/#post-398231

Bootloop on the latest stock global firmware (V10.3.1.0.PEIMIXM)

Hi, I've tried to update my Global Redmi Note 5 Pro's firmware for a few days now to allow usage with the latest pie custom roms, but all the attempts to get my phone booting on the latest versions seem to have failed so far.
Everytime the phone either gets stuck on the boot logo or the loading screen (for more than an hour, so I assume it is bootlooping). I am not sure on what could be causing those issues, though they seem to have appened to a few other people on the miui forum. The phone does not get bricked by installing the latest firmware (fastboot and recovery still work), but it only appears to boot after reflashing oreo firmwares. Pie only seemed to work on custom roms relying on an oreo firmware.
Did those issue happen to anyone else, or has anyone found a solution?
So far what I've tried was:
- Installing the a pie firmware from twrp (from xiaomifirmwareupdater's github), installing a pie compatible twrp, formatting the data and cache partititon, then flashing a custom rom -> stuck on bootlogo
- Reformatting data, cache, vendor and system partitions to make sure they are not somehow damaged, then installing the latest firmware, twrp pie recovery, and a custom rom (retried with more than one custom roms) -> stuck on bootlogo
- Installing the latest stock miui pie fastboot firmware with flash_all.sh (should flash all device partitions) -> stuck on miui bootanimation for more than an hour
- Formatting Data/Factory reset -> still stuck on MIUI bootanimation
- Installing the latest stock MIUI Oreo fastboot firmware with flash_all.sh -> works flawlessy
- Installing any Oreo custom rom -> works flawlessy
So far I've not managed to take any logcat (adb does not detect any device, the issue probably happens before adbd starts running). I am not sure on what could cause those issues.
(I was wondering if it could be related to the latest kernel, though the fact that miui reaches the bootanimation means that it's at least somewhat working; another unlikely possibility might be an hardware issue, but then why'd it work on oreo?)
Thanks in advance for any help

With miui pie, older boot-loader wont work. Infact you would need pie recovery and pie rom to boot. You could try fastboot flashing oreo rom and older rom will work. try to flash arb v4 rom or device will get bricked.

Happend to me once.
What I have done:
Flash latest oreo (or pie for better sake) by miui flash. Remember to match your ARB value.
Go to pie via updater (if you don't care ARB thing. I don't know if fwless pie will work). Don't install recovery now. Let it boot first.
Load pie recovery via fastboot then flash recovery via recovery.

I have the same problems. Pie fw has not been use by dev. So please wait some future rom update

arunmohan16 said:
With miui pie, older boot-loader wont work. Infact you would need pie recovery and pie rom to boot. You could try fastboot flashing oreo rom and older rom will work. try to flash arb v4 rom or device will get bricked.
Click to expand...
Click to collapse
Thanks for the info; shouldn't the bootloader also get updated when fastboot flashing the latest pie firmware? (xbl.elf and abl.elf get flashed, bl looks like an abbreviation for bootloader)
kekesed97 said:
Happend to me once.
What I have done:
Flash latest oreo (or pie for better sake) by miui flash. Remember to match your ARB value.
Go to pie via updater (if you don't care ARB thing. I don't know if fwless pie will work). Don't install recovery now. Let it boot first.
Load pie recovery via fastboot then flash recovery via recovery.
Click to expand...
Click to collapse
Thanks, I just tried to update from an oreo miui firmware via ota as suggested. Unfortunately the result appears to be the same; the phone is stuck on the bootlogo forever and won't boot on a miui pie fw.
namhoang235 said:
I have the same problems. Pie fw has not been use by dev. So please wait some future rom update
Click to expand...
Click to collapse
You mean xiaomi/miui devs? But yeah, I guess waiting for some future update is the only thing I can do for now.

Is it your device is china variant or global variant ??
If your mobile is china variant follow below steps.
Flash China Oreo Fastboot rom using MiFlash Software and then flash China Pie fastboot ROM (Later you can flash global android pie fastboot rom but do not lock bootloader)
If your device global avriant, follow below steps
flash 10.3.1 Oreo fastboot ROM and then flash 10.3.1 android pie fastboot rom (or you can update to android pie using updater method)
this should resolve your issue. for more info visit en.miui.com/a-234.html

SunilSuni said:
Is it your device is china variant or global variant ??
If your mobile is china variant follow below steps.
Flash China Oreo Fastboot rom using MiFlash Software and then flash China Pie fastboot ROM (Later you can flash global android pie fastboot rom but do not lock bootloader)
If your device global avriant, follow below steps
flash 10.3.1 Oreo fastboot ROM and then flash 10.3.1 android pie fastboot rom (or you can update to android pie using updater method)
this should resolve your issue. for more info visit en.miui.com/a-234.html
Click to expand...
Click to collapse
It's a Global variant bought from an official Xiaomi Store in italy, it always worked with global roms.
Unfortunately I also already tried to flash an oreo fastboot (global) rom, then update to pie from there, but the result was the same, stuck on bootlogo.
---
About 10 minutes ago I got it to boot on Pie for about 2 seconds on the setup after another reflash, then it crashed and turned off (and bootlooped).
Idk, I'm starting to think that if it only happens to me it might be an hardware issue. Maybe some blocks of the eMMC are damaged, and the issue only happens in Pie due to the slightly larger firmware images flashed to the various partitions; by coincidence more important data might end up on corrupted blocks.
I'll have to verify by dumping the partitions some times and verifying the data/checking for coherency between the dumps

rw-r-r_0644 said:
It's a Global variant bought from an official Xiaomi Store in italy, it always worked with global roms.
Unfortunately I also already tried to flash an oreo fastboot (global) rom, then update to pie from there, but the result was the same, stuck on bootlogo.
---
About 10 minutes ago I got it to boot on Pie for about 2 seconds on the setup after another reflash, then it crashed and turned off (and bootlooped).
Idk, I'm starting to think that if it only happens to me it might be an hardware issue. Maybe some blocks of the eMMC are damaged, and the issue only happens in Pie due to the slightly larger firmware images flashed to the various partitions; by coincidence more important data might end up on corrupted blocks.
I'll have to verify by dumping the partitions some times and verifying the data/checking for coherency between the dumps
Click to expand...
Click to collapse
Hello! You're not the only one facing this.
I also have Redmi Note 5 global model, and I'm facing the very same problem. I've tried everything, just like you...
I don't see many people with this problem but I found other 3-4 with the same problem: on Mi Community forum and in some Facebook groups. No one is having success... No one is able to fix this!
I'm worried, because as we are not too much facing this problem, maybe Xiaomi is not knowing that this is happening.
Contact me if you want to know more, and maybe together we can make anything! Let's hope for the best!

floater3 said:
Hello! You're not the only one facing this.
I also have Redmi Note 5 global model, and I'm facing the very same problem. I've tried everything, just like you...
I don't see many people with this problem but I found other 3-4 with the same problem: on Mi Community forum and in some Facebook groups. No one is having success... No one is able to fix this!
I'm worried, because as we are not too much facing this problem, maybe Xiaomi is not knowing that this is happening.
Contact me if you want to know more, and maybe together we can make anything! Let's hope for the best!
Click to expand...
Click to collapse
same thing happening to me also tried everything

floater3 said:
Hello! You're not the only one facing this.
I also have Redmi Note 5 global model, and I'm facing the very same problem. I've tried everything, just like you...
I don't see many people with this problem but I found other 3-4 with the same problem: on Mi Community forum and in some Facebook groups. No one is having success... No one is able to fix this!
I'm worried, because as we are not too much facing this problem, maybe Xiaomi is not knowing that this is happening.
Contact me if you want to know more, and maybe together we can make anything! Let's hope for the best!
Click to expand...
Click to collapse
Ok...you all are not alone it seems.
Couple of months back I faced this issue but after struggling for a day I managed to boot into miui latest (global) after which I found my EFS+Modem partitions corrupted (ie. unknown baseband,no wifi or imei )...I guess data corruption is the cause.I went to the service center, they told me it was data corruption and the entire Motherboard had to be replaced...they quoted a price of ~Rs 8000 (Incl. GST ) for the repair...I am since then stuck without a phone
Edit: BTW...I bypassed the bootloop by flashing the latest global recovery rom through orange fox...(not recommended cause it might cause you to lose wifi and imei)..

[GUIDE] Unlocked BL, Installed TWRP and Rooted but cannot install custom ROM...

This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.

Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me ? You've got my respect.

greenys' said:
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me You've got my respect.
Click to expand...
Click to collapse
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.

jijojamie said:
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
Click to expand...
Click to collapse
Ah I see! That's indeed a whole adventure. Thank you for sharing. It was worth reading

jijojamie said:
This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Click to expand...
Click to collapse
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?

grand2SD said:
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
Click to expand...
Click to collapse
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.

jijojamie said:
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
Click to expand...
Click to collapse
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back

grand2SD said:
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
Click to expand...
Click to collapse
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.

jijojamie said:
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
Click to expand...
Click to collapse
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader

grand2SD said:
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
Click to expand...
Click to collapse
I suggest you check this with another derpfest user, please. I never got to boot to derpfest.

I downloaded Evolution X 4.7 Rom zip file and followed the instructions given in thread to flash zip file. But after flashing when I tried to reboot in system, it gave me a message on swipe screen that OS is not installed but still I swiped to boot in system. My device tried to boot a couple of time and ended up in fastboot again. Fortunately I had already made backup so I restored my backup.
As per your post I should have flashed color os 6 ozip file with twrp before flashing evox rom.

Every thing ok.i think you are not flash Vebeta after flash recovery.

Clean ROOT ready to install ROMS REDMI NOTE 8 PRO [GLOBAL] ONLY Guide

So I've read enough posts to get this first - GLOBAL ONLY I got my phone on Amazon its a global unlocked NOTE8PRO. Any of you with something else like China or India try this method and brick your phone don't cry to me over it. After trial and error, bricking my device and paying some guy in Spain 30EUR to unbrick it (thanks brother you rock) I thought I'd share my final experience and how you can get your GLOBAL RN8P to a stable place to install the ROMS available at this time. I will include at the end my thoughts on the 2 ROMS I installed and used over the past week. Honestly if you're on a global version I'm not sure it's worth it although as I type this I kinda want to flash Pixel Experience again, I really liked it. But more on that later. I compiled this guide from sources here, if I don't give you credit I apologize in advance please just let me know.
First let's make sure we don't brick this mofo.
Hit the MEGA thread if you haven't read it then you shouldn't be flashing your phone, and do this from a clean install of MIUI-V11.0.6.0PGGMIXM and do yourself a favor and get it from Xiaomi or a reliable source, not everyone on here has good intentions. There are some "official" ROMS out there that have been played with and will break your phone.
1. Do it how you want I did this from fastboot. Dump the official MIUI global ROM in a folder, and (I'm on linux box so adjust yourself if you're sadly using Windows) I executed this command from FASTBOOT in the MIUI ROM folder with ADB and FASTBOOT installed for my system.
./flash_all.sh (I think its flash_all.bat for Windows)
This going to wipe your stuff out, have it backed up. I'm dedicated to Google and GDRIVE I don't care I get everything back when I wipe including sms and phone records etc, but to each his own.
It's going to wipe and restore to factory image on that ROM version and you're going to go throught setup again, tedious (I say that having done it 4 times this week) but none the less it is what it is. After you are up and running on that ROM version keeping in mind if you're going to flash a new ROM like PE then don't set it up all the way because you're going to do it all over again anyways move to the next step.
2. From the MEGA thread flash this and reboot. Read the thread download the files and do what Agent_fabulous (awesome guy btw) says. Reboot. Make sure you can reboot to SYSTEM and all is well, don't worry about recovery or bootloader yet.
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
3. OK kids we're almost there, now you need to install TWRP and there are MANY versions floating around. Honestly the official version sucks IMHO. go to this thread and download TWRP and do exactly what it says in the thread. Assuming you're device is unlocked already and if its not then come back later follow EXACTLY steps 2 and 3. From there you will update MAGISK after the reboot and be fully rooted and pass SaftyNet checks.
You are stable and rooted. All you do next is enjoy your rooted device and or install a custom ROM. If you do install a custom ROM - READ READ READ and FOLLOW directions I hate to add to the confusuion but there are so many threads on this phone (becasue it sucks to MOD it) and it's frustrating because all of it assumes you know everything or they just don't give you all the steps and you end up bricking your phone. I have never by the way rooted or flashed a phone in my life before this one.
At this time all the custom ROMS need to be flashed after flashing the Indian Vendor image, this is in fact the only way I know and it worked for me everytime. So at this point if you're flashing a new ROM first flash the India Vendor image then flash the new from all from TWRP. But in my experience just follow what it says because Agent_fabulous and friends may crack this tomorrow and it won't be the same. What I am giving you is a VERY stable platform to start flashing ROMS from or just to be rooted and happy. As an FYI from this you can install RIRU and EdXposed if you want to do that, I wasn't impressed other than dark mode in GMail on A9 and ad-blocking in YouTube, I get the ads in YouTube but Google no dark mode in GMail on A9? WTF??
Happy rooting and ROMing.
DC.

Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.

Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
Given how aggressive the battery optimizer is on stock, I doubt you'll get more juice out of it.

Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
It's fine to flash ROMs I felt PE was way faster the audio was better over Bluetooth and it was pretty stable. Battery improvement was negligible.

@dcindallas glad you had such a nice experience. have you tried flashing miui 12 on it? seems there are some beta versions for it. seems to bring a lot of eye candy, privacy and performance fixes. give it a go.

@dcindallas hi, can you please add a portion for updating miui rom through twrp (when new version available) the procedure. thanks.

I've not flashed anything but custom ROMS I had to wipe go back to A9 stock ROM due to Pixel Experience dropping wifi constantly.

Well, I appreciate all the effort going into this thread and this device. Thru all the reading I've done on this simple project with different advice, it almost seems there's too much info on it. Anyway, I'm having a dickens of a time with it, just getting it to load up TWRP! I thought I followed all the directions.. y'know... hold this button, dont hold this one, release this one, then repress that one... but I got a bootloop just from flashing TWRP. I had to re-flash the whole MIUI (an older one even) with Mi Flash, the only one I could find that had a flash-all script in it.
I'm a little gun shy, but I'd sure like to give it a go again.
I flashed twrp-3.3.1-0-begonia.img, then rebooted. Any advice why I bootlooped? Was it the TWRP version or did I mess up the button press?
Cheers

[HELP REQUEST] WILL PAY TO WHOEVER HELPS ME GET THROUGH THIS SOFTBRICK

.

rodagola said:
Hello everyone on xda, please bare with me. Here's my story
I own a Redmi Note 8 pro, chinese rom model. It was running miui 11.0.3 over android 9 If I recall correctly.
Ok so... I was tired of some of the china apps pushing their notifications over and over and auto installing stuff, so I looked up how to apply adb commands to remove such bloatware, which was a fairly simple process. I copied and pasted a list of safe stuff to delete I found around some forums.
then... there were some other packages I checked out using an app called "app inspector", which directly tells you which app is under which package (totally useful for this purpose).
I tried to be careful not go overboard since I don't have any root access, or custom recovery, and wasn't really planning to have these, just wanted to keep this as my simple daily driver cellphone, but also perform this little maneuver to get rid of some bloatware.
little did I know, I was about to somehow softbrick it. More info: I did not use a screen lock method other than the "swipe up".
Ok, so I uninstalled some packages I cannot remember exactly how they went, but they had the terms "xman" and "yman" on them I think, I wasn't so sure about them because I looked them up on the web yet they didn't appear anywhere. I think they went something among the lines of "com.android.miui.xman". I also uninstalled 2 or 3 more, but after googling, they seemed unsuspecting.
Anyways, I'm aware there's a command to reinstall the packages because they're still on the phone's ROM image. That is in case I had to restore anything back to normal. Turns out I later rebooted the phone and when it launches the lock screen, I keep swiping up but it won't take me over to the actual MIUI launcher. The screen is frozen on the lock screen.
I'm not freaking out at this time because I still tried to connect the device to the pc, and it still shows as connected, I then go to the adb console and type "adb devices", it is still recognized, however, it says next to it that it is unauthorized... damn it. So now I might not be able to run the commands that allow me to reinstall the exact packages that are rendering the phone softbricked (I guess), plus I'm not really sure which package caused this.
After about a minute or two on the lock screen, the phone takes me to the "redmi-recovery 3.0",
which displays 3 options:
Reboot to system: which basically forms a loop
Wipe date: godforbid... really don't want to do it since I likely had many files not backedup
Contact miassistant: not sure what to do with this, says "pcsuite.mi.com" at the bottom
on the miassistant option you can apparently sideload stuff, idk how to go about this, maybe it allows me to install a slightly upgraded ROM, which in turn will work the same as if it was an OTA update (so it will keep my data as it was instead of wipe)? Because the point is not to erase my user data!!
I'm not sure how to feel or what to do without losing my pictures, notes and documents
I have hopes this situation can be turned around back to normal, and like the title implies... I'm WILLING to PAY you through paypal or something to WHOEVER offers to guide me through in the best way possible. Please if you have the knowledge/experience don't hesitate I'll also be grateful timelessly.
I'm not an expert at these scenarios so I might as well ask on xda where most are really skilled! Thanks in advance to those amazing souls
Click to expand...
Click to collapse
tldr;
If you can boot into fastboot mode you can just flash a official MIUI fastboot ROM:
Xiaomi Firmware Updater (where you can download official MIUI ROMS): https://xiaomifirmwareupdater.com/
This is the current hard unbrick method: https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
It should also work in your case and there's even a video guide.
This is another video guide for fixing a hard brick:
Both methods above will format your phone though (afaik all data will be lost).
Compass.

.

rodagola said:
are these the kind of roms that you unzip and have the BL, AP, CP, CSC files? I could try that, but I've heard installing home_csc will not override/wipe my personal data. If this is what you meant, can you confirm? Or do you reckon these linked video tutorials would not wipe the data?
Click to expand...
Click to collapse
Nope, it doesn't.
If you can boot into Fastboot, flash the ROM using Mi Flash, otherwise, use this tutorial:

.

Compass Linux and juliusjr have told you the method, so I will just add supplemential infos.
In your case, I think simple upgrade will do the trick, dirty flash is applicable both via fastboot flash (mi flash) and recovery flash (the mi assistant method). If you want to stop the ads, I will recommend you to unlock your bootloader, move to global, root, and use an adblocker (a bare minimum config, in trade of some bangking apps being blocked).
I don't know the corresponding version for miui china rom, but in global rom, prior 12.0.0.7 (the one with the early 2021 security update), you can dirty flash back and forth while keeping your data.

.

rodagola said:
Hi, thanks for your info, I would like to try the mi flash tool as I've been told before the stock recovery thing has less chances of working. However, I had dev options turned on before but didn't manage to turn on the "OEM unlock" option, will flashing original ROMs work this way? or did I need that option toogled on? That's my last doubt, and thanks a lot. Btw, the China ROM this Redmi N8P had never ever showed me any ads, but thanks a lot as well for such input
Click to expand...
Click to collapse
You still have a locked bootloader? (How do I know? You will see "Unloked" on the bottom of the screen everytime your device reboots and showing mi logo if your device is unlocked)
Hmm, mechanically it work like normal ota update. Full recovery update will ony erase nessesary partitions (system, boot, and some other things) while keeping your data intact. So doing this to your phone technically safe. You can do this with MiFlashPro, do a recovery update using a recovery rom (the 2 gigs one) greater than your current MIUI version. But please bear in mind that I have never done this before to a locked phone. A same distribution version IS A MUST (i.e. global with global).
Oh and it will need you to log in to your xiaomi account. My guess is you need the flash permission open for your account (if you have unlocked your phone you shouldn't have a problem). I have never flashed with an account that never have been used to unlock a bootloader, so I might be wrong.
If your phone is bootloader unlocked, Mi Flash is the least demanding and it can retain your data with "save user data" in the bottom right corner option on, regardless your miui version (but I think there will be some problem with installed apps if you downgrade from A10 to A9).
Hope this help.