Database Info

Oneplus 7 dual boot from "factory" ?

Hello,
I just received my oneplus 7 (GM1900).
Ordered from rakuten.
First time I have a phone with 2 "slots". I managed to flash twrp & magisk on both.
However when booting on slot a, I boot into H2 os, and when booting on slot b I am booting on Oxygen OS.
Can someone tell me how these A & B slots work exactly?
I figure I just have to flash OOS again on slot A to have same configuration on both slots, and whenever I flash something new, the "old" slot can be used as functional backup?
Thank you

Nobody07 said:
Hello,
I just received my oneplus 7 (GM1900).
Ordered from rakuten.
First time I have a phone with 2 "slots". I managed to flash twrp & magisk on both.
However when booting on slot a, I boot into H2 os, and when booting on slot b I am booting on Oxygen OS.
Can someone tell me how these A & B slots work exactly?
I figure I just have to flash OOS again on slot A to have same configuration on both slots, and whenever I flash something new, the "old" slot can be used as functional backup?
Thank you
Click to expand...
Click to collapse
Here is an explanation:
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
When an update comes in, it is installed into the inactive slot and when the update is successful and working, it will make the previously inactive slot active and boot into it.
Just switch slots and install the same OOS.
Here a few helpul commands:
adb shell getprop ro.boot.slot_suffix
fastboot getvar current-slot
Changing slots:
fastboot --set-active=b
fastboot --set-active=a
If you want to root without TWRP (I have Q-Beta 4 Android 10 and there is no TWRP for it)
Fastboot flash boot magisk_patched.img
Instructions on how to make a patched Magisk Image: https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
If you have a PIE OOS, then you can use TWRP:
fastboot flash boot twrp.img
fastboot boot twrp.img
fastboot flash twrp_installer.zip
Then install Magisk.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ChingghisKhan said:
I have Q-Beta 4 Android 10 and there is no TWRP for it
Click to expand...
Click to collapse
I have Q-Beta 4 with working TWRP.
Check this: https://forum.xda-developers.com/showpost.php?p=80029941&postcount=161

root pixel 3a

Hi all
I acquired a Google pixel 3a.
I unlocked the bootloader, but can't root it with magisk manager.
So developer option enabled as well as debugging.
I downloaded the corresponding factory image to extract the boot.img
So I put it on my phone for the patch with magisk manager.
Then I transferred it to the platformtools folder of the SDK.
The pixel does not restart I have to flash the original boot.img.
PS: bootm.img and the file patched by magisk.
I did "./" because I'm on win 10
My build version QQ2A.200405.005
Thank you

What happens when you reboot after magisk boot image is flashed? I've read sometimes need to flash other boot area, in your case flash to boot_b.

dkryder said:
What happens when you reboot after magisk boot image is flashed? I've read sometimes need to flash other boot area, in your case flash to boot_b.
Click to expand...
Click to collapse
it doesn't start, that's why I reflash the original boot.
how to flash on boot b?

The command should be listed along with the others when you issue just fastboot. Or Google search. I've never had to use it so I don't have it in my memory

jerome8 said:
it doesn't start, that's why I reflash the original boot.
how to flash on boot b?
Click to expand...
Click to collapse
Can you just read FAQs???
Flash b - fastboot flash boot_b boot.img

St.Noigel said:
Can you just read FAQs???
Flash b - fastboot flash boot_b boot.img
Click to expand...
Click to collapse
I tried everything but A and B it doesn't work.
On the B I do it restarts normally but I am not rooted.
Maybe I should flash on A and B?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try fastboot flash boot --slot all magisk_patched.img
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------
Or whatever you named the image
Sent from my [device_name] using XDA-Developers Legacy app

This also works in Android R
Sent from my [device_name] using XDA-Developers Legacy app

thank you it worked I flash the 2 boot A and B.

OTA still working?

I don't do OTAs maybe somebody else can help
Sent from my [device_name] using XDA-Developers Legacy app

Android 11 beta1 update error slot unbootable load error

Android 11 beta1 update error
flash google pixel 2 factory images
pixel2 reboot ,error slot unbootable load error
Flashing process is different
send system_b 1/1
what's happen?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hww44 said:
Android 11 beta1 update error
flash google pixel 2 factory images
pixel2 reboot ,error slot unbootable load error
Flashing process is different
send system_b 1/1
what's happen?
Click to expand...
Click to collapse
I got the same error, unable to solve it.

jwchen119 said:
I got the same error, unable to solve it.
Click to expand...
Click to collapse
what version of adb tools are you using

andy hall said:
what version of adb tools are you using
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 30.0.2-6538114

hww44 said:
Android Debug Bridge version 1.0.41
Version 30.0.2-6538114
Click to expand...
Click to collapse
The 11 Beta only refers to the Android Flash Tool I cannot find any instructions for using ADB and Fastboot, are you using that tool if not then try that
Or going back to a factory image using normal fasboot and then using the flashtool.
Unusually it also says you need to enable oem unlock as well as usb debugging in developer options before starting.
Other than that, I have run out of ideas as it is 11 beta.
This is where I started https://developer.android.com/preview/download loads of info nothing like the usual flash instructions.

andy hall said:
The 11 Beta only refers to the Android Flash Tool I cannot find any instructions for using ADB and Fastboot, are you using that tool if not then try that
Or going back to a factory image using normal fasboot and then using the flashtool.
Unusually it also says you need to enable oem unlock as well as usb debugging in developer options before starting.
Other than that, I have run out of ideas as it is 11 beta.
Click to expand...
Click to collapse
Thank you.
I will non restore the factory image because the data is important.
I found the same problem with DP4 and BETA1.

Why did not use OTA ?

theasters said:
Why did not use OTA ?
Click to expand...
Click to collapse
Already rooted.

i got the same problem here and i'm unable to solve it , the Pixel 2 is the most forgetten phone i got .
no support here on xda and nothing cool , Kernels and roms are bs
i used to have Hammerhead , bullhead , C'mon even OnePlusOne aka Bacon is still up with new things updated it's a phone from 2014 or something

Can I flash redmi 10a fastboot rom in redmi 9a?

They have same code name and almost same specs. I couldn't find any 12.5 fastboot rom for redmi 9a.
As there is no android 11 supported twrp, I can't flash magisk.
I can't copy the boot .img from the fastboot rom too.
Any ideas?

Flahsing magisk using twrp is the WORST way for flashing magisk.

Use fastboot to flash magisk

NO，you CANT!(I TRIED THAT and bricked it)(can be rescued with Emergency Download Mode)
I have the same device as yours. It's needed to PATCH boot with magisk on the device
I have to tell you that DONT WONDER if TWRP OR IMGs from the redmi 9A to work on this device，since the employee on official Chinese forum said they are INCOMPATIBLE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Just download the latest rom in the system update and you'll find it in downloads folder in your internal storage.
then extract it and find vbmeta.img and boot.img
copy them to somewhere you can find and use magisk app to patch the boot.img.
now copy the 2 imgs to computer
connect and reboot to fastboot,flash boot.img AND VBMETA.img with the option of --disable-verity --disable-verification.
NOW enjoy.

Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !

VD171 said:
Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !
Click to expand...
Click to collapse
good warning since i did tried that lol

sd369888 said:
good warning since i did tried that lol
Click to expand...
Click to collapse
I just tried that recently, too...
Sad.

How To Guide [TB-J716F] Flashing Pseudo_Global firmware (many languages inside)

If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good Luck !

f1tm0t said:
If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
View attachment 5783891View attachment 5783993View attachment 5783995
Good Luck !
Click to expand...
Click to collapse
It was exactly what I was looking for and trying for days, but following your tutorial I still couldn't, it didn't turn on, I had to upload the rom 12.6.211 again. I wanted to leave it with multiple languages.

augustobfe said:
still couldn't, it didn't turn on
Click to expand...
Click to collapse
OK, I will re-check it in 2-3 days. Although I think you did something wrong.

f1tm0t said:
will re-check it in 2-3 days
Click to expand...
Click to collapse
Dude, I have some bad news for you. Your hands are crooked. That needs to be fixed.
My method works without fail. It only takes half an hour.
Try it again.
Spoiler: Look this: