Which stable rom and how should I flash? - Xiaomi Redmi Note 7 Questions & Answers

Hi,
A few months back I unlocked the bootloader, installed TWRP (I don't know which version, probably letsmakecakes version) and flashed a LOS build from Darkjoker. I ran into a few problems, like asking password on first boot and a Zip Treble compatibility error while trying to flash the rom. I can't recall how I overcome it, I think I deleted something inside the rom zip and then it worked I believe.
But this is an old build, it has a few major bugs (data not working for me, sometimes the phone freezes while connecting to certain networks, etc). I'm dying to change it.
I want to mantain the feel of LOS and stock Android (I don't need costumization), and I've looked into LOS 16 from AmulyaX and Pixel Experience 9.0. Which one would you guys recommend?
Also, with the problems I had when first flashing this phone, I'm a bit afraid of the process. I want to install OrangeFox Recovery and one of these roms. How should I procceed? Can you ELI5 please?
Thank you!

I unlocked my bootloader just yesterday. And before that I made sure that I remove all security locks including screen lock and app lock. This way TWRP did not encrypt my phone. After flashing TWRP I booted into recovery and flashed Orange Fox Recovery zip and it automatically booted into itself. I wanted to stick with MIUI bcz of the battery backup and smoothness so I went for RevOS MIUI. Loving the ROM so far.

Related

Won't boot into system or fastboot

Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
CiT42 said:
Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
Click to expand...
Click to collapse
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Choose an username... said:
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Click to expand...
Click to collapse
I flashed DrakenFX's B29 stock rom. Didn't thought it would work with recovery but anyway ! Thank you.
Do you recommend some ROMs, kernels, etc ?
CiT42 said:
Do you recommend some ROMs, kernels, etc ?
Click to expand...
Click to collapse
Nah, they are all mostly bad. The best of the bunch seems to be NucleaRom, it has an okay kernel (Radioactive, not too good battery-wise but I've never seen so little UI lag, like, ever) and okay features (like 1/3 of what ResurrectionRemix has), an awesome maintainer (OrdenKrieger) and boots in like 15 seconds
But the stock ROM is currently the best of them all, not battery wise (you can get some obscenely high SOT numbers on LineageOS with Substratum black themes) but it's fluid and stuff runs well on it. The status bar is hideous though, and MiFavor is white themed, on an AMOLED screen, what the crap ZTE?
Don't try PureNexus, permanent hard brick from the looks of it.
LineageOS works okay but it has some compatibility problems with some apps I use, dunno
I think you could try the dual-boot patcher, that way you can test the roms and keep a working stock rom to use it as your daily driver without losing data. i never used the dual boot patcher though, so good luck if you will use it
I've bad experiences with Dual boot on my old 1+.

Multiple screwups resulting in actual (somewhat) hardbricked unupgradable OnePlus 5?

Hi,
I think I have screwed up big time. I have been using my OnePlus 5 with LineageOS and ElementalX but I got lazy and haven't upgraded my LineageOS build since May 2018. I downloaded the latest TWRP 3.2.3 (which apparently has a bug where you can't decrypt the data partition, so I had to download an older version of TWRP which did work fine). I downloaded and flashed OOS 5.1.5 firmware + radio from here: https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8 in order to be able to flash LineageOS as it was failing with an error 7 in TWRP which apparently has to do with treble support or something. However, now that I have flashed that firmware, I am unable to enter the bootloader or recovery with the normal volume keys and holding down the power button and volume up or holding down the power button and volume down does not work either. Furthermore, my current version of LineageOS from may 2018 actually has a regression that prevents me from being able to reboot from the OS into the recovery or bootloader: https://jira.lineageos.org/browse/REGRESSION-1930 - I was wondering why I had that issue for a long time, never really looked it up until tonight.
Luckily I do have my entire applications backed up with TitaniumBackup, so that is something at least (thank god for backups).
Do I need to RMA my phone? Does anyone know if OnePlus offers advanced RMAs? Will they even offer an RMA for my device knowing how rooted etc it is or am I just completely out of luck?
I feel so stupid, but this was a string of multiple instances of bad luck all combining into one major problem... I can erase all data (factory reset) in LineageOS as I am able to boot into LineageOS and I have full access to ADB, but as I cannot reboot to my bootloader or recovery, I have no access to fastboot.
Does anyone have any ideas of things I can try? I really don't like the idea of not having access to bootloader and recovery... I tried asking for instructions a couple weeks ago on how to upgrade to the latest LineageOS from an older build on LineageOS on the ElementalX thread but I did not get a response there so I decided to try it today, how hard could it be, right? What a mistake this was...
Thank you for taking the time to read this.
So I went to download and install the latest version of LineageOS from the live running install of LineageOS in the updates menu and then I rebooted my phone manually (since it got stuck at the cyan light as usual because of the regression), tried rebooting manually into recovery and it worked for some reason whereas booting manually into recovery was not working before, it finished flashing the LineageOS and even restored Magisk with a su.d script or whatever. I can now reboot from my ROM into recovery and bootloader. Double dumb luck got me into this situation and even more dumb luck got me out of it.
So, I guess this thread can be closed now.

Stuck in fastboot after flashing TWRP (Mi 9T)

First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up
cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Your mistake is to not use Official TWRP instead of an old TWRP version...
Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.
blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days

Flashing Custom rom i get stuck at fast boot but flashing xiaomi.eu works fine

Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe
AbsoluteZero said:
Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe
Click to expand...
Click to collapse
Hello, what OrangeFox version did you install?
You should try with R10.1_1 if you are using latest one.
If your phone is working with xiaomi.eu ROMs..., do you know xiaomi.eu ROMs are custom ROMs?
You generally only have to "Format Data" in TWRP before flashing another ROM (stock or custom).
Good luck!
Hi,
Thank you for the reply. I now have OrangeFox R10.1_1 installed. sorry I should've said other custom roms aren't working xiaomi.eu seems to be fine for some reason.
I just installed OrangeFox, reflashed xiaomi.eu and booted, worked fine. Then I went back, formatted data, rebooted back to recovery, flashed AOSPextended and gapps pico. Rebooted to system and it went to the fastboot screen again. I noticed it says during the AOSP install that "Root Status: Disabled" could that be a problem?
Thanks again for your help.
AbsoluteZero said:
Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe
Click to expand...
Click to collapse
Use the official TWRP.
You should install latest stable xiaomi.eu rom or install latest China rom through MI flash, you need latest vendor partition for latest custom roms to boot properly.
jaggyjags said:
You should install latest stable xiaomi.eu rom or install latest China rom through MI flash, you need latest vendor partition for latest custom roms to boot properly.
Click to expand...
Click to collapse
I installed the latest Global Rom 11.0.5. via OrangeFox. I couldn't get it to go with Mi Flash. Not sure how to create the flash_all.bat and where to get all the files from. Is that the same? What are the steps from here?
Thank you
The same exact issue I am facing. Tried multiple custom roms and everything failed to boot only resulting in bricked or error. Even my previous budget phone redmi 3s was much better than this.

Stuck in TWRP as custom roms are not booting after flashing with TWRP

Hello,
i got a second phone for my GF as i was really happy with this phone and had it flashed without any issues before. This second phone is used and was over a year in use from the guy i've bought it from. It was 100% fine and he always used the shipped Android with it.
So i went on, got the latest TWRP for the phone. Flashed it without any issues and tried to install LineageOS from their website. Flashed it and tried to flash TWRP back as LOS replaces it. I wanted to use TWRP install the backups. But that's where it started to go wrong. Lineage seemed to have been gone from that point on. I couldn't get it to work again, even with reflashing and such. I've downloaded CRDroid and Paranoid and tried them but no luck. Non of them where booting up and TWRP stays showing a warning about "No OS installed".
After some more digging, i've found some posts stating that i would need newest firmware and venders. I've downloaded and flashed them but this made it even worse. The phone started to be stuck in fastboot. I got it working again by flashing latest MIUI version with Xiaomi Flash Tool.
Then i've installed TWRP again but somehow any rom i flash does not boot. The phone starts with the MI logo and flashes once and loads TWRP. There is no message about missing OS or any kind or error when flashing any of these roms.
Anyone able to help me?

Categories

Resources