I don't know what happened, but when I try to flash pixel experience 12 on this using TWRP, it says that "devices on super may not mount
until rebooting recovery", I've tried a lot of fixes but none of them worked, when I flashed orangefox it flashed and worked, but I'm getting a similar mounting error on that as well, please help, I'm desparate
If you want to install a custom rom, use the recommended procedure for that rom. The rom developer gives you a proven procedure.
PE is not intended to be installed from TWRP or OFOX.
StaryMuz said:
If you want to install a custom rom, use the recommended procedure for that rom. The rom developer gives you a proven procedure.
PE is not intended to be installed from TWRP or OFOX.
Click to expand...
Click to collapse
yeah, but i cant even flash magisk or anything.
I normally use Magisk and it goes flash from all recoveries. Only the recovery must correspond with the ROM.
"devices on super may not mount until rebooting recovery"
Click to expand...
Click to collapse
Had the same problem. Solution for me was to use MiFlashTool to go back to stock.
Then flashed Twrp again and I was able to flash custom rom.
ScarletSkies1234 said:
I don't know what happened, but when I try to flash pixel experience 12 on this using TWRP, it says that "devices on super may not mount
until rebooting recovery", I've tried a lot of fixes but none of them worked, when I flashed orangefox it flashed and worked, but I'm getting a similar mounting error on that as well, please help, I'm desparate
Click to expand...
Click to collapse
This is actually how Virtual A/B works. That's not an error.
Related
Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.
Dear XDA Experts!
As I was flashing on my Redmi Note 4 Snapdragon Global (mido) LineageOS 15.1 step by step using instructions from LineageOS site I came up with a problem. Suddenly the the fastboot command didn’t “see” my phone. Before that when I was typing in the command prompt (as administrator) “adb devices” it said it found my phone. When I typed “fastboot devices” it turned out it didn’t “see” my phone so I couldn’t do the “fastboot flash recovery twrp-x.x.x-x-mido.img” command. However before fastboot stopped detecting my device I was able to do this command “adb reboot bootloader”. It turned out later that adb still was detecting my device but fastboot still was NOT detecting it.
So to flash TWRP on my phone I used a XiaomiFlashTool in which I could among other options choose to flash TWRP.
I selected this option, the XiaomiFlashTool that in order to even start and work needs access to the Internet it download the latest file twrp-x.x.x-x-mido.img with TWRP for my device and flashed it.
Now, having the TWRP installed I flashed in TWRP the file containing the LinageOS and afterwards I flashed Gapps instantly with no reboot as it was written in the guide. Then I rebooted the device to normal system mode.
The LineageOS started for the first time, I configured it and Gapps were present.
Later I’ve chosen to root the phone so I booted to TWRP and selected Install to install Magisk17.2.zip but it didn’t work cause an error occurred “couldn’t mount /data”. It was all red.
When I try to do the same thing with superSu the same problem occurred.
Could You tell me what I did wrong?
And which drivers/install programs to use to repair or uninstall and install fastboot again so It can work cause there are so many of them and the LineageOS guide doesn’t cover that thing in 100% ?
androidbadboy said:
Dear XDA Experts!
As I was flashing on my Redmi Note 4 Snapdragon Global (mido) LineageOS 15.1 step by step using instructions from LineageOS site I came up with a problem. Suddenly the the fastboot command didn’t “see” my phone. Before that when I was typing in the command prompt (as administrator) “adb devices” it said it found my phone. When I typed “fastboot devices” it turned out it didn’t “see” my phone so I couldn’t do the “fastboot flash recovery twrp-x.x.x-x-mido.img” command. However before fastboot stopped detecting my device I was able to do this command “adb reboot bootloader”. It turned out later that adb still was detecting my device but fastboot still was NOT detecting it.
So to flash TWRP on my phone I used a XiaomiFlashTool in which I could among other options choose to flash TWRP.
I selected this option, the XiaomiFlashTool that in order to even start and work needs access to the Internet it download the latest file twrp-x.x.x-x-mido.img with TWRP for my device and flashed it.
Now, having the TWRP installed I flashed in TWRP the file containing the LinageOS and afterwards I flashed Gapps instantly with no reboot as it was written in the guide. Then I rebooted the device to normal system mode.
The LineageOS started for the first time, I configured it and Gapps were present.
Later I’ve chosen to root the phone so I booted to TWRP and selected Install to install Magisk17.2.zip but it didn’t work cause an error occurred “couldn’t mount /data”. It was all red.
When I try to do the same thing with superSu the same problem occurred.
Could You tell me what I did wrong?
And which drivers/install programs to use to repair or uninstall and install fastboot again so It can work cause there are so many of them and the LineageOS guide doesn’t cover that thing in 100% ?
Click to expand...
Click to collapse
Use a Treble compatible TWRP like OrangeFox R8 and then flash Magisk
Noter2017 said:
Use a Treble compatible TWRP like OrangeFox R8 and then flash Magisk
Click to expand...
Click to collapse
I used the latest TWRP for mid (I saw when the XiaomiFlashTool was downloading the latest TWRP for mido).
May I ask why shall I use a Treble compatible since my Redmi Note 4 was manufactured in 2017 and came with not Oreo but with Nougat so it is not compatible with Project Treble from the start.
BTW Can You please direct me to that Treble compatible TWRP please?
BTW#2 The Xiaomi tool only flashes the latest TWRP .img for mido by downloading it from the internet (I can't change which TWRP will it flash).
BTW#3 The only thing I can think off to flash other TWRP is by fastboot but can You help me which or where to find it so I can uninstall current fastboot and install again or repair by installing again?
androidbadboy said:
I used the latest TWRP for mid (I saw when the XiaomiFlashTool was downloading the latest TWRP for mido).
May I ask why shall I use a Treble compatible since my Redmi Note 4 was manufactured in 2017 and came with not Oreo but with Nougat so it is not compatible with Project Treble from the start.
BTW Can You please direct me to that Treble compatible TWRP please?
BTW#2 The Xiaomi tool only flashes the latest TWRP .img for mido by downloading it from the internet (I can't change which TWRP will it flash).
BTW#3 The only thing I can think off to flash other TWRP is by fastboot but can You help me which or where to find it so I can uninstall current fastboot and install again or repair by installing again?
Click to expand...
Click to collapse
You will find OrangeFox TWRP here:
https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933
Simply boot into your existing recovery and flash OrangeFox from there.
LineageOS 15.1 on our phone uses Treble, so you need a compatible recovery. After flashing OrangeFox, you can flash Magisk
Noter2017 said:
You will find OrangeFox TWRP here:
https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933
Simply boot into your existing recovery and flash OrangeFox from there.
LineageOS 15.1 on our phone uses Treble, so you need a compatible recovery. After flashing OrangeFox, you can flash Magisk
Click to expand...
Click to collapse
But how to flash that rom since fastboot doesnt detect my phone?
androidbadboy said:
But how to flash that rom since fastboot doesnt detect my phone?
Click to expand...
Click to collapse
Can you boot into recovery?
Noter2017 said:
Can you boot into recovery?
Click to expand...
Click to collapse
I can boot into latest TWRP for mido from LineageOS site (turns out the same file is downloaded from XiaomiFlashTool)
I wanted to say Yes, I can boot to TWRP
androidbadboy said:
I can boot into latest TWRP for mido from LineageOS site (turns out the same file is downloaded from XiaomiFlashTool)
I wanted to say Yes, I can boot to TWRP
Click to expand...
Click to collapse
Great. Then all you have to do is to download OrangeFox, save it to your SD card and flash it.
After that reboot to recovery and it will start OrangeFox.
Flash Magisk and all will work
Noter2017 said:
Great. Then all you have to do is to download OrangeFox, save it to your SD card and flash it.
After that reboot to recovery and it will start OrangeFox.
Flash Magisk and all will work
Click to expand...
Click to collapse
But how am I suppose to flash it when fastboot doesnt work, adb works
Which driver/installler shall I use to repair or instal or install or uninstall and install fastboot again to use it to flash that OrangeFox
androidbadboy said:
But how am I suppose to flash it when fastboot doesnt work, adb works
Which driver/installler shall I use to repair or instal or install or uninstall and install fastboot again to use it to flash that OrangeFox
Click to expand...
Click to collapse
Its simple
save the orange fox twrp to your phone
Boot into your twrp recovery
Flash orange fox recovery
Your recovery will automatically reboot into orange fox.
kavin36 said:
Its simple
save the orange fox twrp to your phone
Boot into your twrp recovery
Flash orange fox recovery
Your recovery will automatically reboot into orange fox.
Click to expand...
Click to collapse
so is it possible to flash a TWRP by a different TWRP and it will replace it?
androidbadboy said:
so is it possible to flash a TWRP by a different TWRP and it will replace it?
Click to expand...
Click to collapse
You're right.
kavin36 said:
You're right.
Click to expand...
Click to collapse
That's a great idea but sadly I can't flash TWRP anymore. I don't know what happened. The Xiaomi program I was using to do this suddenly stopped flashing it telling me that there's something wrong with drivers
When I do "fastboot flash recovery TWRPforMido.img" it "flashes" the file in less then a second and when I enter recovery I see the old Xiaomi 3.0 stock recovery.
I have the device unlocked, developer options with USB debugging are ON.
I'm compleatly idealess.
Can You tell me what other ways to flash TWRPmido.img?
androidbadboy said:
That's a great idea but sadly I can't flash TWRP anymore. I don't know what happened. The Xiaomi program I was using to do this suddenly stopped flashing it telling me that there's something wrong with drivers
When I do "fastboot flash recovery TWRPforMido.img" it "flashes" the file in less then a second and when I enter recovery I see the old Xiaomi 3.0 stock recovery.
I have the device unlocked, developer options with USB debugging are ON.
I'm compleatly idealess.
Can You tell me what other ways to flash TWRPmido.img?
Click to expand...
Click to collapse
not sure bout this situation
But try doing the same but download orange fox recovery from xda forums and use the same method to flash.
That's
Fastboot mode in phone
Command from cmd
Flash recovery
Reboot recovery
kavin36 said:
not sure bout this situation
But try doing the same but download orange fox recovery from xda forums and use the same method to flash.
That's
Fastboot mode in phone
Command from cmd
Flash recovery
Reboot recovery
Click to expand...
Click to collapse
I already done this a thousand times. Nothing.
androidbadboy said:
I already done this a thousand times. Nothing.
Click to expand...
Click to collapse
do us have root access
If us have try flashify app from play store
Select recovery
Browse the orange fox recovery on it phone
Flash
Only if ur rooted
kavin36 said:
do us have root access
If us have try flashify app from play store
Select recovery
Browse the orange fox recovery on it phone
Flash
Only if ur rooted
Click to expand...
Click to collapse
Nope I don't.
But I finally flashed stock, TWRP for mido (not Orange) and Magisk for root and I'm so tierd now
Just tell me what shall I do next to install 1. Lin Os (their guide is not accurate in 100%) 2. Some custom romwith project treble and Android Pie, some popular good stuff
server error - a double post
androidbadboy said:
Nope I don't.
But I finally flashed stock, TWRP for mido (not Orange) and Magisk for root and I'm so tierd now
Just tell me what shall I do next to install 1. Lin Os (their guide is not accurate in 100%) 2. Some custom romwith project treble and Android Pie, some popular good stuff
Click to expand...
Click to collapse
I've heard that Crdroid official
And Siberia os unofficial are the most stable pie ROMs
Make sure it twrp is treble supported becuz someone told that official twrp has no treble support that's the reason I use orange fox
If it ain't treble supported just flash orange fox from the same twrp
Do advanced wipe
Install from and gapps
---------- Post added at 07:27 PM ---------- Previous post was at 07:27 PM ----------
kavin36 said:
I've heard that Crdroid official
And Siberia os unofficial are the most stable pie ROMs
Make sure it twrp is treble supported becuz someone told that official twrp has no treble support that's the reason I use orange fox
If it ain't treble supported just flash orange fox from the same twrp
Do advanced wipe
Install from and gapps
Click to expand...
Click to collapse
Also Ive seen that Serbia unofficial is a bit more stable than crdroid official. Its your preferences
kavin36 said:
I've heard that Crdroid official
And Siberia os unofficial are the most stable pie ROMs
Make sure it twrp is treble supported becuz someone told that official twrp has no treble support that's the reason I use orange fox
If it ain't treble supported just flash orange fox from the same twrp
Do advanced wipe
Install from and gapps
---------- Post added at 07:27 PM ---------- Previous post was at 07:27 PM ----------
Also Ive seen that Serbia unofficial is a bit more stable than crdroid official. Its your preferences
Click to expand...
Click to collapse
Could You do step by step 1., 2. what I shall do (at the example of Linage OS). And what about that advanced wipe thing. People that told me steps just like You didn't mention Advanced wipe
Greetings:
I believe I'm having troubles getting into TWRP. I used to have MIUI 10.0.6 in an Unlocked and Rooted device with TWRP installed. Everytime I pressed VolUp+Power, I got into the TWRP. But, after MIUI 10.1.3 installed by itself, I can't get into TWRP and instead, get into MI-RECOVERY 3.0
Did the new update "roll backed" my TWRP recovery and instead installed the MI-RECOVERY 3.0? Do I have to install TWRP again? Help pls!
Seriously, MIUI is the biggest piece of **** ever...no wonder everyone suggest flashing a custom rom...
DarkDeux said:
Greetings:
I believe I'm having troubles getting into TWRP. I used to have MIUI 10.0.6 in an Unlocked and Rooted device with TWRP installed. Everytime I pressed VolUp+Power, I got into the TWRP. But, after MIUI 10.1.3 installed by itself, I can't get into TWRP and instead, get into MI-RECOVERY 3.0
Did the new update "roll backed" my TWRP recovery and instead installed the MI-RECOVERY 3.0? Do I have to install TWRP again? Help pls!
Seriously, MIUI is the biggest piece of **** ever...no wonder everyone suggest flashing a custom rom...
Click to expand...
Click to collapse
This is nothing new or exclusive to Mi. The original stock ROM will always replace the custom recovery. So you have to flash it again.
In future, after the update, don't boot into system. Boot into recovery and you should boot into TWRP. If not, flash TWRP again. Sometimes even that is not sufficient and you will have to flash Magisk also after flashing TWRP. And then boot into system.
tnsmani said:
This is nothing new or exclusive to Mi. The original stock ROM will always replace the custom recovery. So you have to flash it again.
In future, after the update, don't boot into system. Boot into recovery and you should boot into TWRP. If not, flash TWRP again. Sometimes even that is not sufficient and you will have to flash Magisk also after flashing TWRP. And then boot into system.
Click to expand...
Click to collapse
Thank you so much for the info! It's good to know that. Will have to flash it again.
Thank you once again.
DarkDeux said:
Thank you so much for the info! It's good to know that. Will have to flash it again.
Thank you once again.
Click to expand...
Click to collapse
If you want to thank someone, please use the thanks button below the post.
I have a Xiaomi mi5 and I have same problem...
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
GGerniWhite said:
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
Click to expand...
Click to collapse
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
GGerniWhite said:
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
Click to expand...
Click to collapse
If you already have the ROM installed, use adb to flash TWRP and without booting flash Magisk and then boot to system. If you are on stock ROM, follow THIS.
For entering into TWRP, use the key combination of volume up + power buttons.
You can use the encryption compatible TWRP (search for it) instead of the official one.
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img