It all started when I tried to temporarily boot into the TWRP img file. It didn't work so I tried flashing the file to boot_a. Then I installed TWRP through the installer (stupidly didn't wipe the caches) and... Well. When I try to boot into System through TWRP, it gets COMPLETELY stuck at the powered by Android logo screen. No amount or combination of button holding will shut it off and I actually had to let the battery (thank you SO MUCH for non-removable batteries by the way, smartphone manufacturers >_>) drain before it would actually boot again. Rebooting it into Download mode will get it stuck in there too where every time I hold the power button and shut it off, it will just reboot right back into Download mode again. And now, here's probably the worst part. I CAN'T UNLOCK the critical partition to flash when in Download mode, so I can't use the OST tool! When I try to unlock it, it just complains that flashing unlock is not allowed even though the rest of the bootloader is completely unlocked.
TL;DR - When I power the phone up it goes straight into TWRP. Booting to System totally freezes it and the Bootloader puts it in a loop when I try to power it off. Critical partition is locked for some reason. I CAN get around the bootloader loop though and get back to TWRP by switching active slots and rebooting.
Did you flash the TWRP installer to your active boot partition or your inactive one? If you flashed it to the active one, you can't get into system anymore because TWRP is your boot partition.
If you are on Oreo, and you flashed to the inactive slot, and then patched the active slot, you have to reboot into the active slot recovery and flash the Magisk installer to disable verification of the partitions.
If you can get into the bootloader, and you still have the unlock key from nokia, do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
THMSP said:
do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
Click to expand...
Click to collapse
This unlocked it! Thank you! <3
I also did have an issue with the OST tool complaining that the updater was out of date, but changing the .mlf file and leaving it unpacked when I opened it in OST seemed to make it work perfectly. My phone is now booting just fine and back to stock!
Now I just need to solve the original problem I had. How can I install TWRP to recovery since the img file wouldn't temporarily boot last time?
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
S5Guy said:
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
Click to expand...
Click to collapse
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Yeah looks like you're right. Letting it update back to Android 9 deleted TWRP and made fastboot boot for TWRP nonfunctional again.
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
S5Guy said:
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
Click to expand...
Click to collapse
You have to flash it directly to your boot partition. fastboot boot will work for nothing (and even if it worked those images would just send you directly into the system)
THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Alright! fastboot flash boot_a (TWRP image) worked! Thank you so much for all the help. <333
Related
Ok, so lets start from the beginning.
I have a OnePlus 3t and I have been trying for the whole day to get multirom up and running.
Made a couple of mistakes in the beginning (nothing serious) although i decided to use the unbrick tool to fully clean it.
After successfully cleaning it I booted, skipped thru the setup, went to developer settings, enabled oem unlocking and verified the computer signature.
Went to fastboot mode unlocked oem, and flashed TWRP like this:
Code:
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
It all went well, then in twrp I copied a backup from my pc (that I made previously) and restored it.
And here comes the actual problem. Whenever I try to boot into TWRP it is just a black screen and a the LED is white.
Only way to boot into TWRP is by typing
Code:
fastboot boot TWRP.img
while in fastboot
Does anyone have a clue on this one?
(Sorry if grammar isn't perfect)
TheGamer14 said:
Ok, so lets start from the beginning.
I have a OnePlus 3t and I have been trying for the whole day to get multirom up and running.
Made a couple of mistakes in the beginning (nothing serious) although i decided to use the unbrick tool to fully clean it.
After successfully cleaning it I booted, skipped thru the setup, went to developer settings, enabled oem unlocking and verified the computer signature.
Went to fastboot mode unlocked oem, and flashed TWRP like this:
Code:
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
It all went well, then in twrp I copied a backup from my pc (that I made previously) and restored it.
And here comes the actual problem. Whenever I try to boot into TWRP it is just a black screen and a the LED is white.
Only way to boot into TWRP is by typing
Code:
fastboot boot TWRP.img
while in fastboot
Does anyone have a clue on this one?
(Sorry if grammar isn't perfect)
Click to expand...
Click to collapse
Update: Just booted into recovery by using
Code:
fastboot boot TWRP.img
and now I'm unauthorized in adb
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
sniperle said:
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
Click to expand...
Click to collapse
Downloading and trying rn
sniperle said:
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
Click to expand...
Click to collapse
I somehow made everything even worse so using the unbrick kit again.
Should I OTA update when in system?
Just tried doing a OTA and while it was rebooting it WIPED the data by some reason.
So now it is basically a clean install that needs a OTA that probably will wipe it again...
Ok just tried it again and it seems to actually update. Gonna report back soon
TheGamer14 said:
Just tried doing a OTA and while it was rebooting it WIPED the data by some reason.
So now it is basically a clean install that needs a OTA that probably will wipe it again...
Click to expand...
Click to collapse
So it seems like if you try to update while having a pc attached wipes the data?
This is really weird
sniperle said:
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
Click to expand...
Click to collapse
YESSS I'm finally able to boot into twrp TNX SO MUCH
Glad to hear you aced this. Just for further explansion:
The OS update does a firmware update too.
I took the firmware from the 3.5.4 flash zip from oneplus.
Hi,
I'm having a bit of trouble. I had a brand new Redmi 4X, and I was advised to install TWRP, root it, and install the Xiaomi.eu rom until LineageOS is released. I unlocked the bootloader, flashed TWRP, managed to get into it once and now I can't do it again. When TWRP loaded it asked me for a password for decryption but it let me just skip it it seems (not sure if that is the problem) but now I can't boot normally, I can't boot into recovery, but fastboot seems to work okay. How do I go about fixing this?
I've tried reflashing TWRP but I still can't get to it, and I don't really know enough about this stuff to know where I've gone wrong.
UPDATE - I think this is to do with dm-verity and having the stock kernel installed. Now it's too late to undo what I've already done, so I hope to god that someone knows how to fix this.
UPDATE - Right, the problem is solved I think. I had to do an awful lot of googling, and I'm not entirely sure what it was specifically that fixed it. But I found a guide that taught me the fastboot command "fastboot boot twrp.img" which saved the day. Even when my phone wouldn't let me into recovery, it allowed me to flash a no-verity.zip which i think is what allowed me to boot, and it allowed me to flash superSU.zip and then the ROM I was aiming for. And now I've booted into the ROM successfully and hopefully I am rooted and all is well. Plus I can access TWRP as normal now.
Any help would be greatly appreciated
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
brljak83 said:
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
Click to expand...
Click to collapse
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
brokemyG2 said:
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
Click to expand...
Click to collapse
Hii
I just have been reading about this bootloop
Go over here and read all of the 6 pages..will not take much time but could help you out much
https://forum.xda-developers.com/xiaomi-redmi-4x/development/official-twrp-3-2-1-0-xiaomi-redmi-4x-t3718217
Hey, I have exactly the same problem. Latest stock rom, flashed twrp in fastboot and got into the boot loop. Nothing works. I can only enter fastboot. What exactly did you do then? What is this no-verity.zip? I can't find anything about it.
I had a problem
I unlocked bootloader then installed redwolf recovery and took a nandroid backup. After that i rebooted to system but stuck into bootloop, could not boot to recovery, could not boot into system, So the only thing worked was that i flashed fastboot rom with mi flasher. And syccessfully rebooted to system with bootloader locked and stock recovery. So, if anyone have same problem you can do the same. How do i install recovery safely again? Should i use TWRP only? Should i flash v3.1.0 with lazy flasher or v3.2 directly without lazy flasher? I don't want to stuck into bootloader again, have to get all data deleted.
I just unlocked bootloader, flashed boot image and twrp image(temporary) from pc but when i come to my device mi a2 in twrp mode the twrp is unable to read the twrp image or magisk zip. I can see then when i go to file manager in twrp but when i am in flashing screen they just don't appear and other files names are also changed. Is there something missing. I used unlock bootloader and fastboot boot --.img . I am in November patch and my only reason to root was i am not getting further updates after November 2018. So pls help guys
Do this after unlocking critical unlock.. Your storage is encrypted just boot to twrp and do a factory reset under wipe->Format data then type yes!! now your storage will be ready to use as normal then copy your files to phone through pc Don't forget to unlock critical otherwise you cant able to flash stock rom if anything goes wrong
Sivakumar$ said:
Do this after unlocking critical unlock.. Your storage is encrypted just boot to twrp and do a factory reset under wipe->Format data then type yes!! now your storage will be ready to use as normal then copy your files to phone through pc Don't forget to unlock critical otherwise you cant able to flash stock rom if anything goes wrong
Click to expand...
Click to collapse
Thanks for the reply! I have already flashed boot img will there be no problem if i use unlock critical now? I have formatted data though
just flash the stock boot img and do unlock critical and then do all the flashing stuffs if you dont want to be taking any risk
Sivakumar$ said:
just flash the stock boot img and do unlock critical and then do all the flashing stuffs if you dont want to be taking any risk
Click to expand...
Click to collapse
Where can i get stock boot img. I have been searching and all post are about patched boot img
Sivakumar$ said:
just flash the stock boot img and do unlock critical and then do all the flashing stuffs if you dont want to be taking any risk
Click to expand...
Click to collapse
Hey bro please reply as soon you can i have been waiting for weeks stuck here . Is the process of flashing boot image same as patched boot image? I have to keep the boot image in patched boot image folder and flash using same code?
sourav56 said:
Hey bro please reply as soon you can i have been waiting for weeks stuck here . Is the process of flashing boot image same as patched boot image? I have to keep the boot image in patched boot image folder and flash using same code?
Click to expand...
Click to collapse
It's the same process. Flash stock boot.img then unlock critical. You flash stock boot and patched boot the same way. You can keep patched boot.img in same folder just change the code in flashing command flash boot.img to flash patched boot.img. If I recall correctly.
Files changed because you are encrypted flash DM-Verity to decrypt your file or do a wipe in internal.
I can only seem to get into fastboot mode with a Menu saying:
Restart Bootloader
Unlock Bootloader (Unlocked)
Wipe Userdata
Exit
I haven't been able to get to any download mode at all, just this menu and stock recovery, can someone please give me instructions on this? I've gotten different files and ways to root this from many different threads and I'm confused as hell.
Never rooted this RP2 before, it's on latest OTA MR2-RC001-RZR-190914.3123. Got it unlocked before and it's been unlocked for a while but didn't go further with rooting because I got confused and didn't want to brick my expensive phone. Last phone I rooted was back on kitkat or lollipop before I switched to iPhone, so I'm not a total noob just rusty. But Razer got me back to Android and it''s changed alot. I need detailed advice please. :good: And if my instinct is telling me correctly I'd assume something is changed about the bootloader in MR2 thats affecting me right now?
That menu is the bootloader/download mode.
DarkestSpawn said:
That menu is the bootloader/download mode.
Click to expand...
Click to collapse
My issue was not having Bootloader interface installed. Fixed
MarkusGingles said:
My issue was not having Bootloader interface installed. Fixed
Click to expand...
Click to collapse
Have you unlocked critical partition?
https://developer.razer.com/razer-p...6.1692205032.1582602359-1206928491.1581902985
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
THE CABLE THAT CAME WITH THE PHONE WILL NOT WORK.
If you have everything unlocked then make sure you do this
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Or install using this tool
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
If you make it this far then it's a matter of typing in the correct path in fastboot.
fastboot flash boot "arter97 name here".img
Then from the fastboot menu scroll down to boot to recovery or type fastboot reboot recovery
TWRP should boot if you installed the correct kernel.
In TWRP hit cancel then swipe to make modifications and install magisk 20.3
Profit
JDBarlow said:
Have you unlocked critical partition?
https://developer.razer.com/razer-p...6.1692205032.1582602359-1206928491.1581902985
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
THE CABLE THAT CAME WITH THE PHONE WILL NOT WORK.
If you have everything unlocked then make sure you do this
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Or install using this tool
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
If you make it this far then it's a matter of typing in the correct path in fastboot.
fastboot flash boot "arter97 name here".img
Then from the fastboot menu scroll down to boot to recovery or type fastboot reboot recovery
TWRP should boot if you installed the correct kernel.
In TWRP hit cancel then swipe to make modifications and install magisk 20.3
Profit
Click to expand...
Click to collapse
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
MarkusGingles said:
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
Click to expand...
Click to collapse
Have you tried the format data partition ?
MarkusGingles said:
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
Click to expand...
Click to collapse
Will it not let you flash stock using flash_all.bat file while in fastboot mode?
I would definitely try and start over for sure if possible
So..I was trying to unlock the bootloader using the fastboot commands. When it was all done and I was booted into TWRP, I flashed the TWRP image onto the boot partition instead of the recovery partition. Realizing my mistake seconds after, I flashed TWRP onto the recovery partition as well. Now everytime I try to boot my device, you guessed it, it opens up TWRP instead.
Previously I was using the Stock android 10 ROM with March's security update. I was wondering if there's a way to fix this? Maybe flashing the boot.img will fix this(if yes, then can one of you take a backup of yours and upload it, please?) or should I just flash Pixel experience rom and it will change the partition according to its needs?
I am kinda worried..Hopefully, the device is fixable. Thank You.
BungeeWatcher47 said:
So..I was trying to unlock the bootloader using the fastboot commands. When it was all done and I was booted into TWRP, I flashed the TWRP image onto the boot partition instead of the recovery partition. Realizing my mistake seconds after, I flashed TWRP onto the recovery partition as well. Now everytime I try to boot my device, you guessed it, it opens up TWRP instead.
Previously I was using the Stock android 10 ROM with March's security update. I was wondering if there's a way to fix this? Maybe flashing the boot.img will fix this(if yes, then can one of you take a backup of yours and upload it, please?) or should I just flash Pixel experience rom and it will change the partition according to its needs?
I am kinda worried..Hopefully, the device is fixable. Thank You.
Click to expand...
Click to collapse
"If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image."
https://twrp.me/xiaomi/xiaomimia2.html
ahenaol said:
"If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image."
Click to expand...
Click to collapse
I used
fastboot boot *path of twrp.img*
to boot twrp on my phone, i guess that is called side loading? after that, when TWRP opened up, I copied the twrp.img into my storage. After that, I was supposed to flash that image onto the recovery partition by using the sideloaded TWRP but instead I flashed it onto the boot partition. I hope that is a bit clearer..anyway, even in this case will I have to flash the stock rom before trying anything else?
BungeeWatcher47 said:
I used
fastboot boot *path of twrp.img*
to boot twrp on my phone, i guess that is called side loading? after that, when TWRP opened up, I copied the twrp.img into my storage. After that, I was supposed to flash that image onto the recovery partition by using the sideloaded TWRP but instead I flashed it onto the boot partition. I hope that is a bit clearer..anyway, even in this case will I have to flash the stock rom before trying anything else?
Click to expand...
Click to collapse
You could try flashing just the boot.img file from stock image.
BungeeWatcher47 said:
... flashed TWRP onto the recovery partition as well.....
Click to expand...
Click to collapse
What do you mean here? There is no "recovery partition" in A/B slots structure of MiA2. Or did you totally reformated partitions?
BungeeWatcher47 said:
Previously I was using the Stock android 10 ROM with March's security update. I was wondering if there's a way to fix this? Maybe flashing the boot.img will fix this(if yes, then can one of you take a backup of yours and upload it, please?)...
Click to expand...
Click to collapse
Yes, If you were on stock A 10 march (11.0.6.0), and never re-paritioned device, then you can restore OS fasboot-reflashing stock 10.0.6.0 boot image to the slot you were using previously with 11.0.6.0 (and, btw, try to remember what was and is now in the opposite slot). I've uploaded 11.0.6.0 bbot images to: https://forum.xda-developers.com/showpost.php?p=82166125&postcount=58
BungeeWatcher47 said:
... or should I just flash Pixel experience rom and it will change the partition according to its needs?
Click to expand...
Click to collapse
Sorry, I'm on stock and never went deep into nuances of custom ROMs partitioning.
Aerobatic said:
What do you mean here? There is no "recovery partition" in A/B slots structure of MiA2. Or did you totally reformated partitions?Yes, If you were on stock A 10 march (11.0.6.0), and never re-paritioned device, then you can restore OS fasboot-reflashing stock 10.0.6.0 boot image to the slot you were using previously with 11.0.6.0 (and, btw, try to remember what was and is now in the opposite slot). I've uploaded 11.0.6.0 bbot images to: https://forum.xda-developers.com/showpost.php?p=82166125&postcount=58
Sorry, I'm on stock and never went deep into nuances of custom ROMs partitioning.
Click to expand...
Click to collapse
When you try to flash a image in TWRP, it gives you multiple options on the next screen. Namely, boot, vendor, system, data, recovery. I had flashed that TWRP.img into my boot slot lmao. It messed everything up. Your stock boot images have been saving me in multiple pinches.
Hello, thats my first entry in XDA forum. I did the same mistake with my mi9 and i have no idea how to fix it. Could someone help me, i hope i didn't killed it.
... i installed the mi 9 rom --> solved the problem