Hi everyone,
So, I have a Xiaomi Mi Pad 5 global version (fastboot), is there a way to make a room to install an older version of MIUI? I'm having problems with the pen firmware...
There probably is a way to make room, but it's certainly complex enough. Not sure but something about deleting one of the non essential partitions, creating two smaller ones in the same spot, and installing your two OSes in these. You will also need to find a way to tell the bootloader to switch between them.
Sorry to be vague, but I'm not sure of the exact steps to do, or even if it really is possible, just giving a guess...
Yuri Lordelo said:
Hi everyone,
So, I have a Xiaomi Mi Pad 5 global version (fastboot), is there a way to make a room to install an older version of MIUI? I'm having problems with the pen firmware...
Click to expand...
Click to collapse
You don't need to make room, there are two slots used for this A/B, you may need to check which one is the live one.
Reboot your nabu to bootloader mode (fastboot mode)
Code:
adb reboot bootloader
The check the active slot
Code:
fastboot getvar current-slot
Then switch to the other slot, replace $X with your other (inactive) slot
Code:
fastboot set_active $X
Then flash your img files to the desired slot and reboot.
Pretending that your active slot was A ,the B slot will contain your older OS after you updated last time your nabu, this way Android updates work on A/B devices.
Let say that you need to flash your B slot boot.img all you need to do is
Code:
fastboot flash boot boot.img
boot_b partition will be flashed if you already changed the slot to B as active, otherwise you need to be more specific and flash boot_b partition.
Related
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I just did a factory reset and it fixed it. I also was stock without twrp though.
seshaz said:
I just did a factory reset and it fixed it. I also was stock without twrp though.
Click to expand...
Click to collapse
I tried factory reset already but still shows system using 19.9gbs.
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
cambunch said:
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
Click to expand...
Click to collapse
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
ls2power said:
I tried factory reset already but still shows system using 19.9gbs.
Click to expand...
Click to collapse
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
ls2power said:
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
Click to expand...
Click to collapse
If you are getting a bootloop after flashing a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
cambunch said:
If you are getting a bootloop after factory a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
Click to expand...
Click to collapse
im able to flash every single img, but when i try to flash flashall.bat it doesnt seem to work. I will give it a try once i get home from work. The only thing bugging me is that the system shows using 19.9gb of space.
Mine is only using 6.79GB. Something is definitely off with yours.
Sent from my Pixel XL using XDA-Developers mobile app
Neomage84 said:
Mine is only using 6.79GB. Something is definitely off with yours.
Click to expand...
Click to collapse
yes there is. When you reboot your phone, which slot does it have? And do you have twrp installed and root?
M9guy said:
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
Click to expand...
Click to collapse
I fixed it, i flashed full system image while i was on slot A. Now system is using 5.39gb, im on V build.
i have the same problem with a 128GB version not sure whats up but to fix it i just flashed over and over and one of them just worked would be nice to know the cause so i dont have to flash many times to get it to show full space again.
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
whenever you flash a factory img or an OTA, or any firmware, the slots will switch unless told not to, i believe this is to keep them in sync aka the seamless updates. here is some info on that - http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
Quick Tip - while in cmdlne for ADB and Fastboot, and fully updated, just type
Code:
adb
to get all the ADB commands available, and likewise for fastboot, just type
Code:
fastboot
And to switch active slots type
Code:
fastboot set_active -a
or
Code:
fastboot set_active -b
. Then to activate slot
Code:
fastboot reboot bootloader
I believe with TWRP installed you have to switch slots in TWRP.
Click to expand...
Click to collapse
Moving on, I found this to be pretty helpful, it's not the exact answer you are looking for, but i think it will come in handy.
All dual-booting credit in this thread goes to hucqym, this wasn't my idea, im just a messenger.
hucqym said:
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery on both slots
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
-> with slot _a as active in TWRP, installed ElementalX-P-1.00 zip for the kernel patch to pass SafetyNet
voila, I now have non-rooted on slot _a and rooted on slot _b
Note that TWRP is not really a requirement for doing this. I had the same dual boot configuration working with SuperSU v2.78 SR3 rooting one slot directly. The only reason I needed TWRP is so that I can switch slots easily on the device and don't need a cable and a laptop just to switch the bootloader flag
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two. ...so if somebody has an idea on this, I'm all ears.
[UPDATE]: Note that the unrooted slot is still limited in the sense that safetynet checks fail and so AndroidPay etc.. that use that API will still not work. This, however, has little to do with the dual boot setup and more because SafetyNet now fails on just unlocked bootloader and we do need it unlocked. On Conchors' suggestion, I installed ElementalX kernel on slotA from TWRP and now my 'otherwise-stock' non-rooted image on slotA passes SafetyNet while slotB is successfully rooted
flash_all_slot-a.sh
Code:
fastboot flash --slot _a bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _a radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _a --skip-secondary image-sailfish-nde63x.zip
flash_all_slot-b.sh
Code:
fastboot flash --slot _b bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _b radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _b --skip-secondary image-sailfish-nde63x.zip
Click to expand...
Click to collapse
I switched it up a bit, and to be perfectly honest, the script is easier, this is just an alternate way of doing it
I did this for both slot_a and slot_b (not sure if it is needed for the flrst one, but that is what i did), both ways are correct, this way is much longer, but it gives some control, plus it's a nice learning process as it is pretty easy going.
If you are going to erase, erase first before you start anything, because you know...science.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot erase vendor
the cache partition, i dont remember if this worked or not, I'm too tired to verify
Code:
fastboot flash --slot _b --skip-secondary bootloader "name-of-bootloader.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary radio "name-of-radio.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary system system.img
fastboot flash --slot _b --skip-secondary boot boot.img
fastboot flash --slot _b --skip-secondary vendor vendor.img
If you want to wipe everything, use the following commands next:
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
system.img and userdata.img take time to flash— the command prompt appears to stop. Let it do it's thing, when it's done the cursor will begin blinking again.
All dual-booting credit goes to hucqym; again, not my idea.
Slightly Off Topic -
Has anyone tried this on a specific slot, does it make any difference?) I haven't actually even thought of this till now
something like:
Code:
fastboot erase --slot _(a/b) --skip-secondary userdata
fastboot flash --slot _(a/b) --skip-secondary userdata userdata.img[/B]
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I was noticing quite a bit of space missing as well. what i did was boot into the slot I wanted as secondary (do this in TWRP), and i wiped just the system (which includes cache) and reflashed the system.img directly pulled from factory.zip. I noticed twice as much space had been gained then what was actually said to be there. I was a little surprised...it was over 5 gb I had gained while the system only said 2.5ish gb. (perhaps there was a second other_system.img wrapped up in it, I don't know. Then i went back to the primary slot and booted back up.
It's possible I got off course, I'm tired.
Is there any way to enable back Double Tap to Wake (DT2W), after last update my phone lost this function and in the settings app there is no option for this. Is there any easy way to bring back my phone to June update or to enable dt2w in the last update somehow?
I'm growing tired of xiaomi for being such incompetent in all things related to android one, i kept the phone without root until this day but i really need dt2w, I remember seeing a thread long ago that there was a line in the build.prop to enable or disable it, I'll try to find it and see if it works
sniffviper said:
I'm growing tired of xiaomi for being such incompetent in all things related to android one, i kept the phone without root until this day but i really need dt2w, I remember seeing a thread long ago that there was a line in the build.prop to enable or disable it, I'll try to find it and see if it works
Click to expand...
Click to collapse
But modify system partition will makes system reject the next update.
coolwei1 said:
But modify system partition will makes system reject the next update.
Click to expand...
Click to collapse
It is possible to disable DT2W but you have to root your device.
https://forum.xda-developers.com/mi-a2-lite/help/how-to-disable-dt2w-t3848226
Maybe reverse this tweak to enable dttw ,disable works after reboot phone, i have used rootexplorer to get it done
Nxkealen said:
It is possible to disable DT2W but you have to root your device.
https://forum.xda-developers.com/mi-a2-lite/help/how-to-disable-dt2w-t3848226
Maybe reverse this tweak to enable dttw ,disable works after reboot phone, i have used rootexplorer to get it done
Click to expand...
Click to collapse
Ya, I saw that before. I open the generic.kl file see, the key is not commented out. I also download SetEdit app, the dt2w property is already set to 1.
So I think there is no way to enable it. Is a bug.
I already flash my phone back to 10.0.10.0.
coolwei1 said:
I already flash my phone back to 10.0.10.0.
Click to expand...
Click to collapse
Is that the June update? Please give us a tutorial!
I have theory, I don't know did these updates update or change somehow the kernel but I think the last one had done exactly that. IMHO loadable module or driver responsible for dt2w had been "forgotten" to be built into the kernel.
x0xcdrx0x said:
Is that the June update? Please give us a tutorial!
I have theory, I don't know did these updates update or change somehow the kernel but I think the last one had done exactly that. IMHO loadable module or driver responsible for dt2w had been "forgotten" to be built into the kernel.
Click to expand...
Click to collapse
You can download the 10.0.10.0 image from [FASTBOOT] [daisy] Xiaomi Mi A2 Lite FASTBOOT Images
Then follow steps in How to Flash Fastboot Firmware with Miflash Tool
If you doing this for the first time, you need to learn a lot of things and do a lot of research.
If not careful you could brick your phone and do not know how to get out from bootloop
I stuck in bootloop when flash for the first time, don't know what happened, later found out I just need to switch to another partition.
Code:
fastboot getvar current-slot
fastboot set_active a (if current-slot is b) or fastboot set_active b (if current-slot is a)
Required to download platform-tools inside consists of adb and fastboot
coolwei1 said:
You can download the 10.0.10.0 image from [FASTBOOT] [daisy] Xiaomi Mi A2 Lite FASTBOOT Images
Then follow steps in How to Flash Fastboot Firmware with Miflash Tool
If you doing this for the first time, you need to learn a lot of things and do a lot of research.
If not careful you could brick your phone and do not know how to get out from bootloop
I stuck in bootloop when flash for the first time, don't know what happened, later found out I just need to switch to another partition.
Code:
fastboot getvar current-slot
fastboot set_active a (if current-slot is b) or fastboot set_active b (if current-slot is a)
Required to download platform-tools inside consists of adb and fastboot
Click to expand...
Click to collapse
Fastboot doesnt fint the "set_active a" command.
mariohackku said:
Fastboot doesnt fint the "set_active a" command.
Click to expand...
Click to collapse
Then you can use
Code:
fastboot --set-active=a
https://android.stackexchange.com/questions/203124/fastboot-set-active-command-does-not-exist/203149
Hello,
I need someone to help me because at this point I don't know what else I can try :crying:.
My Xiaomi Mi A2 Lite is in bootloop since when I tried to flash the original rom (daisy_global_images_V10.0.9.0.PDLMIXM_9.0) (the flash worked like 3 times the same day before it got bootlooped).
If I try to flash it again nothing changes, neither a factory resent from recorery worked.
I have read some people talking about getting twrp but (I dont know if im wrong) I think I can't use fastboot without being able to turn on the usb debug.
Also, I've downloaded the rom from here en.miui.com/download-354.html and flashed with xiaomi flash tool.
sapu98 said:
Hello,
I need someone to help me because at this point I don't know what else I can try :crying:.
My Xiaomi Mi A2 Lite is in bootloop since when I tried to flash the original rom (daisy_global_images_V10.0.9.0.PDLMIXM_9.0) (the flash worked like 3 times the same day before it got bootlooped).
If I try to flash it again nothing changes, neither a factory resent from recorery worked.
I have read some people talking about getting twrp but (I dont know if im wrong) I think I can't use fastboot without being able to turn on the usb debug.
Also, I've downloaded the rom from here en.miui.com/download-354.html and flashed with xiaomi flash tool.
Click to expand...
Click to collapse
Try setting/switching the slot and see what happen: In fastboot type first fastboot get current-slot if you receive "slot_a" then set the other slot as active by typing fastboot set_active b and try to reboot and viceversa if the result is "slot_b".
If you have bootloader unlocked as it looks this is the case then you can perform almost any action (if also critical partitions were unlocked) and you can boot to TWRP and then flash it permanently through it, no need to have USB debugging enabled so this is needed for adb interaction not for fastboot.
SubwayChamp said:
Try setting/switching the slot and see what happen: In fastboot type first fastboot get current-slot if you receive "slot_a" then set the other slot as active by typing fastboot set_active b and try to reboot and viceversa if the result is "slot_b".
If you have bootloader unlocked as it looks this is the case then you can perform almost any action (if also critical partitions were unlocked) and you can boot to TWRP and then flash it permanently through it, no need to have USB debugging enabled so this is needed for adb interaction not for fastboot.
Click to expand...
Click to collapse
Thx for the answer but luckly I manager to fix it already by using flash-all.bat from the stock rom, somehow It worked better than mi flashing tool ?
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
niaboc79 said:
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
Click to expand...
Click to collapse
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Miustone said:
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Click to expand...
Click to collapse
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations ?
niaboc79 said:
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations
Click to expand...
Click to collapse
Nice to know! Fingerprints are the worst on Xperia 1 and 5. Hope it will be better on the Mark 2...
Just made an Overlay over Night for GSIs, after experimenting around with them again. Finally got some essential Features working like AoD. Still missing is VoLTE and wifi calling which is a common Android 10 GSI bug i think. Double Touch to work does also not work on My Xperia 5 (Dunno why).
Thread; https://forum.xda-developers.com/xp...eriment-mars-vendor-overlay-gsi-roms-t4128449
which AOSP Vendor Package from Sony can be use on xperia 1 ii
I was wondering, is this device Xperia 1ii is able to recieved GSI 13?
I have the previous model Xperia 1 running GSI 13 really well, and was wondering if this device is similar to do the same?
Kind of a dumb question, because I would assume yes?... But would like to know just the same, as I saw a bargain price for a new Xperia 1ii, and hoping it to be similar.
Hey guys,
I have Lineage OS installed on my Poco F3. I have (at least not really) never experienced any issues with Lineage so far. Everything has worked really smoothly up until I updated the latest version of Lineage OS. The update took ages for some reason and now my Lineage is incredibly unstable.
It doesn't show any of my contacts anymore, play services and the app store crash all the time, giving me notifications non stop.
I tried manually updating the firmware as I figured something went wrong (obviously) but my device does not talk to my computer over a usb. I went to the settings and those showed me that the file transfer option is unclicked, I can't seem to change it either.. Really annoying.
Does anyone know what to do? I don't want to factory reset because of my authenticator. Shall I just wait for the next update and hope it's fixed?
Kind regards, pls halp!!
You could try going into Fastboot mode (https://www.hardreset.info/devices/xiaomi/xiaomi-poco-f3/fastboot-mode/), boot TWRP (fastboot boot TWRP.img) and then change boot partition (e.g. from a to b).
You get the twrp image here:
Xiaomi Poco F3
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I recommend using minimal ADB and Fastboot if you're using windows:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Make sure you don't accidentally flash the twrp.img but use the "fastboot boot twrp.img" command!
Edit: just realized you can change active boot slot with just fastboot, i.e. no need to flash twrp):
Just boot into Fastboot, find out active boot partition:
fastboot getvar current-slot
And then change accordingly, i.e. if above command returns "a" choose "b" and vice versa wit this command: fastboot set_active b