Database Info

TWRP on OB 1

Anyone know how to flash or boot TWRP on that Android 10 OB 1. I tried booting with fastboot and it just sits on the fastboot mode screen and flashing it just continuously kicks me back to the bootloader.

I'm not on OB1, but from what I understand the command to boot TWRP doesn't work yet. And you can't flash TWRP in fastboot (can only flash it in TWRP or Magisk). Depending on what TWRP file/fastboot command, you might not even be flashing it to the right partition!
I believe the sequence is:
1) Install Magisk Manager
2) Fastboot flash patched boot image
3) Reboot, open Magisk Manager
4) Flash TWRP installer zip, like it is a Magisk module.
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
And more info here: https://forum.xda-developers.com/oneplus-7-pro/help/rooting-android-10-t3964863

[recovery_fastbootd] [lineage] [RMX206x]

Hello
After new update in fastboot section
Flash system gsi is no longer possible.
They are compensated by their placement with the fastbootd partition
how to flash ?
unlock boot
reboot bootloder (flash vbmeta patch dm)
flash fastbootd.img (fastboot flash recovery fastbootd.img)
reboot recovery mod
advanced options (recovery lineage fastbootd.img)
enter fastbootd
flash all gsi rom (fastboot flash system systemgsi.img)
link:
https://drive.google.com/file/d/1j02D-c4oFExqDDk7ClA5OZ4FXo8HADD5/view?usp=sharing

fastboot boot twrp-3.5.2_9-0-enchilada.img lands in crash dump error. How can I boot into recovery?

Hi Channel,
fastboot boot twrp-3.5.2_9-0-enchilada.img is successful BUT lands in crash dump error (init killed continue and exit). How can I boot into recovery? Any suggestions
Device : Oneplus 6 with Bootloader Unlocked
Currently running Oxygen OS Android 11 OB1

Check this https://forum.xda-developers.com/t/...eta-1-for-oneplus-6-6t.4304161/#post-85343061
flash the boot.img in fastboot: fastboot flash boot boot.img and reboot ^^

fastboot flash boot boot.img
This needs to be done for both slots A and B?
Also, when you say reboot, does it mean reboot to system

Question Proper Rooting for OnePlus 9?

Would anyone be able to direct me or send me the proper information on how to root my OnePlus 9 global LE2115? Because their are to many threads and Im getting confused

You can either use boot.img or you can boot into twrp and flash magisk.apk. 2 options for A11

I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help

xLLALLOx said:
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
Click to expand...
Click to collapse
A12 root method is different. Not like A11 where you flash the patched boot.img,it won't work. VBmeta and a vendor.img is used also. Also, TWRP is for A11. If you want root,Use the tool here: https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/
Use option 5 and then 6 and reboot. Magisk will be installed. Click the magisk app and update it.
Note: use your phone to download and extract file with password that OP provides in the link

Question I do everything correctly to root but it keep booting in to the bootloader

My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader

What device are you talking about ?

f1tm0t said:
What device are you talking about ?
Click to expand...
Click to collapse
Tab p11 4gig

Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.

f1tm0t said:
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
Click to expand...
Click to collapse
Threr is no twrp sadly

blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd

You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

mingkee said:
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
Click to expand...
Click to collapse
I tried it i flashed patched boot.img only in fastbootd still boots me in to the bootloader

LSS4181 said:
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode

blocky3321 said:
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
Click to expand...
Click to collapse
Which Magisk version did you use? From what I can tell any official Magisk version should work.
I haven't really tested the recent builds of vvb2060's Alpha or huskydg's Delta... so if you're using these versions I can't really help you much...
Additionally, you need to check which slot you are now, and through fastbootd check which slot actually has system, vendor and such. Normally the super partition only has enough size for one slot. You may have entered a wrong slot that doesn't have usable system.

blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
Getting Started: What's Your Device ?
Tab p11 4gig
Device->settings->About : Model & Hardware -> Lenovo ??? (Tb-j606f,TB-J616F...) In your case stiker on box or on back.
mingkee said:
who told you to flash vbmeta.img?
Click to expand...
Click to collapse
???