Hello guys.
I need some help and advice with a broken slot and verity mode issue. A/B partitions and AVB are somewhat new to me, so please excuse my ignorance.
I have previously unlocked and rooted my phone without problems, and have been using it for a month. Two days ago, I wanted to start over and flashed the 1.1.7 Global ROM from https://reindex-ot.github.io/ as I have used this package twice before with no errors.
First, I did a wipe but forgot to unroot Slot B (my big mistake) and since it was on the current 1.1.7 OS, I switched slots and flashed the files to Slot A and rebooted directly (fastboot boot) with a patched boot image. After this point, I am no longer sure which slot I was on, as I assumed I would be on Slot A. I don't know if Slot A was already damaged, and I was actually booted into Slot B.
After a successful boot, I installed Magisk, but the restart dialog came up and I accidentally clicked without patching the original boot image. I did another direct boot with a patched boot image, and then patched the supposedly untouched boot image directly and installed it, then rebooted to the OS successfully.
Next, I went to fastboot to check "getvar all" but here's where two errors came up. FIrst, I realized my verity mode was now set to "false", whereas it was always "true" during two other root attempts in the past month. Second, I realized I was in Slot B instead of the one I previously switched to.
I tried to switch back to Slot A, but it boots for a few seconds, fails, then falls back to Slot B. I then tried twice to flash all the usual partitions back to both slots and try them again, and Slot A consistently fails. It is my belief I may have patched a previously rooted boot image in Slot B, and somehow, verity was messed up during that step. At one point, Slot B also failed and I was dumped back to the bootloader. Now, I have one failed slot and verity mode off, so I need some help or advice.
Is there anyway I can re-enable verity, and are there any special partitions I need to flash to get Slot A working?
I previously made a backup of all smaller partitions (eg "modem" "persist" etc) except the "super" and "userdata" partitions with Wanam's partition backup tool. I believe this backup was made directly after I unlocked while on Slot A with 1.1.7 ROM after an OTA update, whereas Slot B at that time would be on 1.1.6 ROM. I think this is true because the sizes of some compressed images (the "abl" "align to 128k" and "boot") differs slightly for each slot's backup.
Will manually flashing the backups to both slots fix anything? Can I revert back to that point in time just after unlock? I am hesitant to do so because I no longer trust my backups in case flashing them qualifies as a "downgrade" (in the case of Slot B using 1.1.6 ROM). Or will manually flashing the backups for Slot A (the 1.1.7 ROM backup) to both slots ensure they are both considered "identical" to the current bootloader and not cause it to trip?
If this is not possible, will flashing a third party ROM to both slots before flashing NothingOS again help, especially if one slot has gone bad? I realize some third party ROMS first require both slots to have the current 1.1.7 ROM before flashing any third party software. I saw someone mention using RiceDroid to "downgrade" from his NothingOS 1.5 beta back to 1.1.7, but I am unsure if this works. I don't particularly mind not using NothingOS and can live with a third party ROM permanently, but I need to fix the damaged slot and maybe get verity back. I assume verity is useless in a systemless root setup with an unlocked bootloader (true or false?) but I wish to get everything back like it was before.
I apologize if my post is too lengthy, I have never posted to forums before, but I wish to be as accurate in describing my issue. Please advise if you can and thank you for any assistance.
Not an expert but I don't think you can make both slots work at the same time. One is for your rom, the other for OTA update. It doesn't matter on wich you are, when you flash, it flashes the other one on wich you are, if I was you, I would have flashed Rice (because of twrp recovery in case something is wrong) two times in a row to make sure your partitions are okay on both slots, then use your reindex link to flash 1.1.7 on one of them if you really want to go back on NOS
Related
Well, it's not so bad.
Yesterday I bought this phone and applied the October update. Then I flashed TWRP by @mohancm (I wasn't sure about that but I did it anyway). And then I flashed Magisk. But because I couldn't get Xposed to work, I tried to remove Magisk (unsuccessfully it seems) and flash SuperSU. I played around by switching from slot B to A. I am not sure exactly what I did.
The end result is that the phone won't boot when I turn it on. (I think I might still have TWRP installed, but I am not sure.) I tried flashing stock boot.img via fastboot, but I get get an error (I think it's something to do with the partition table). I can't flash using MiFlash because it says I don't have the permission. (I've had bad experiences with MiFlash before.)
However, I am able to boot the phone manually. When I boot to bootloader I can just boot stock boot.img (flashing doesn't work like I said), and then the system boots properly and I'm rooted.
Any ideas what I can do now to fix the issue. I just need to try to avoid random reboots and I can use my phone just fine, but is there a way to fix it? Should I just wait for the November update? Any hope of getting a ROM that I can flash using TWRP?
Edit: I'm dumb. Of course you can flash an image via TWRP. I flashed the stock image via TWRP and now the phone boots properly. Problem solved.
Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike
KingBeefy said:
Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike
Click to expand...
Click to collapse
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
I promise the way above works
aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient
envizion58 said:
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient
Click to expand...
Click to collapse
Like LOS and whatever, yeah, but it takes like 2 minutes. Stock won't flash, since magisk is there anyways
aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud
Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
Hopefully I'm reading this correctly, but if you are referring to swiping as opposed to sideloading I've noticed that too. i do still sideload the ROMs but I swipe all mods and kernels. commonly I would get an error regarding /system not remounting after some flashes but that stopped a while back. @topjohnwu commented in a magisk thread to mount system before flashing as a fix. Its worked great.
Thanks for the response and if i read your question wrong fire it back at me for a second attempt lol
KingBeefy said:
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud
Click to expand...
Click to collapse
with our TWRP being janky as it is, trust me, you dont want living in the other slot.
There seems to be a lot of confusion concerning how to flash, root, and update these new a/b devices, with a lot of adventurous users bootlooping or even bricking their devices. Thought it might help to provide some basic guidelines some of you might find useful. Not intended to be exhaustively inclusive...
1. Know what you are doing before you do it, not after. Ask before try.
2. Unless you are an expert, do not be first in line to try untested procedures. Have some patience and wait for the definitive guide.
3. Do not flash images from a different model device to yours.
4. Keep your current active slot on the same version of firmware as it is your fall back when things go wrong in the inactive slot. Simply put, flash new firmware to the inactive slot, otherwise you risk bootloops.
5. Only when you have successfully booted an updated firmware, then the inactive slot becomes your current active slot, and the now inactive slot becomes your backup of the previous version.
6. Do not reboot your device out of frustration unless you are sure the active slot has a uncorrupted current system boot image. Otherwise you risk the device not booting into system.
7. Do not relock your bootloader unless you have just flashed a complete stock firmware. Otherwise you risk bricking your device.
8. Do not mod beyond your skills until you have a custom recovery installed, such as TWRP, and an nandroid backup of a working system.
9. Do not update your system or Magisk without a nandroid backup to restore when things inevitably go wrong.
10. Do not flash or OTA update a ROM without first enabling USB Debugging for ADB and Fastboot access, plus creating a TWRP nandroid backup of your working system to restore when it goes wrong. Also, an ADB or Titanium backup of your apps and data, plus phone databases to restore if successful.
How to fix a bootloop or booting directly into recovery:
1. When you are stuck on the boot screen, you can turn off by holding the power button until it shuts down.
2. From phone off, press & hold Power + Volume Down button for a few seconds to boot your phone into bootloader mode.
3. Reflash a current system stock boot image to the active slot and reboot. You can test it first...
fastboot boot stockboot.img
4. If that doesn't work, see if you can go back to your previous system in the inactive slot. In bootloader mode...
fastboot set_active other
and reboot.
5. If all else fails and you do not have a nandroid backup to restore, flash-all stock firmware removing the “-w” from the script to preserve apps, settings, and data.
Helpful Guides:
Android Backup Types...
https://android.stackexchange.com/tags/backup/info/
A/B Seamless Updates & Commands...
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Magisk Docs...
https://topjohnwu.github.io/Magisk/
Magisk-MagiskHide Install & Troubleshooting Guide...
https://www.didgeridoohan.com/magisk/
Pixel Firmware Images...
https://developers.google.com/android/images
while number 3 is a great rule of thumb, it isn't always true. like the stuff for the 3a and 3a xl are pretty interchangeable, same with the other pixels. there are a few other phones like that also. maybe add "unless it has been confirmed to work"
pbanj said:
while number 3 is a great rule of thumb, it isn't always true. like the stuff for the 3a and 3a xl are pretty interchangeable, same with the other pixels. there are a few other phones like that also. maybe add "unless it has been confirmed to work"
Click to expand...
Click to collapse
I had that in there originally, but for most, it's just a better habit to download firmware for your specific model. Even if there's some partition images that are the same, not all will be.
The 3a and 3a XL boot and system images have different checksums -- could just be model identifiers, but I've seen that cascade into driver issues and hardware malfunctions. Why risk it...
Don't know if this is the correct thread category but as title I can't boot with slot A.
I'm using OOS 9.0.17 with unlocked bootloader and Magisk. After messing up with the partitions, I've restored the phone using MSMDownloadTool. Now I've noticed that slot A is not booting, but B is booting. I've tried copying the symlink of slot B to slot A without any chance.
Any advice?
Thanks
dreamwhite said:
Don't know if this is the correct thread category but as title I can't boot with slot A.
I'm using OOS 9.0.17 with unlocked bootloader and Magisk. After messing up with the partitions, I've restored the phone using MSMDownloadTool. Now I've noticed that slot A is not booting, but B is booting. I've tried copying the symlink of slot B to slot A without any chance.
Any advice?
Thanks
Click to expand...
Click to collapse
This is a question and should be in Question and Answer section
Fastboot the whole rom in slot a. Simlinks won't have a chance to work. And why do you need this slot booting? On next update OOS will be fleshed on slot a if you are running on slot b for now. That's the point of A/B phones.
Don't mess with partitions I don't see a single reason to do that.
Striatum_bdr said:
This is a question and should be in Question and Answer section
Fastboot the whole rom in slot a. Simlinks won't have a chance to work. And why do you need this slot booting? On next update OOS will be fleshed on slot a if you are running on slot b for now. That's the point of A/B phones.
Don't mess with partitions I don't see a single reason to do that.
Click to expand...
Click to collapse
Yeah I know but if I break the build.prop of slot A, I can't boot it and I need B
dreamwhite said:
Yeah I know but if I break the build.prop of slot A, I can't boot it and I need B
Click to expand...
Click to collapse
Don't mess with build.prop that's the second rule after don't mess with partitions. If you break both of them not surprising you have issues. A/B slots phones are very tricky and easily upset. Every time I saw people having issues in this forum it was because of unconventional use of recovery, slots etc ..
Well but the strange issue is that if I edit the build.prop in system_b and I choose slot_a it doesn't boot
dreamwhite said:
Well but the strange issue is that if I edit the build.prop in system_b and I choose slot_a it doesn't boot
Click to expand...
Click to collapse
Why would you do this?
Assuming the edited build.prop, hence the os, is on slot b, boot slot b. It should boot unless your tweaks to the build.prop broke something.
Well, I have modded Android until Cyanogenmod 14. And I remember that there were some tweaks in build.prop which I wanted to apply on Op6T :laugh:
Rules to remember for me:
- don't mess up with A/B
- don't edit build.prop
I have messed with both of that (boot slot partitions and build.prop), and I kind of agree, however I rarely have problems as the keyword is experience. I learned quickly what not to do on dual-boot setup, on the Google Pixel, as the Slot B was bricked for a while until I figured out how to fix it, now both boot slots are functional. (And yes, I still have the still-functioning Google Pixel, too bad development activities over there on XDA have actually died down.)
It's wise not to mess with it unless you really know what you are doing, like me. And always back up. Back up. Back up. I mean, everything can go wrong, even on the traditional Slot A only phones (apparently due to the UEFI bootloaders' touchy nature, even the personal computer owners would be familiar with the UEFI bootloader boot failure).
Sent from my ONEPLUS A6013 using Tapatalk
what system are you on 9 or 10 are you rooted some twrps dont work right on older systems get the ota flash in settings then do twrp a/b retention then install magisk directly then do ota it will boot to other system dont forget to turn off all magisk mods first
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