Development [TB-J716F] (Unofficial) TWRP for Lenovo Xiaoxin Pad Pro 2021

Search This thread
i managed to install twrp and root with magisk, however i broke my partition B when tried to install gsi from fastbootd. good work @Ungeskriptet
 

Attachments

  • PXL_20211221_043354774.jpg
    PXL_20211221_043354774.jpg
    1.6 MB · Views: 91

chococomaxim

Senior Member
Apr 30, 2013
142
33
this forum
Lenovo P11
For now I'm using the GSI, but I do want to eventually port LineageOS to it (I have only little experience so this could take a long time). I'd also like to get mainline Linux booting on this tablet, since SD865 is supported in Linux and SD870 is an overclocked SD865.

EDIT: I've been using the GSI for some time now and the performance is great. I'll try looking into the issues the GSI has because if the GSI works good there's no need to make a new and seperate LineageOS port. I would need to learn how to do that first though so it can take some time.
Random, but how does one learn porting/ROM dev? It is something that has been interesting me recently so I was wondering if you could point me in a general direction on how to get started/learn more about it?
 
For now I'm using the GSI, but I do want to eventually port LineageOS to it (I have only little experience so this could take a long time). I'd also like to get mainline Linux booting on this tablet, since SD865 is supported in Linux and SD870 is an overclocked SD865.

EDIT: I've been using the GSI for some time now and the performance is great. I'll try looking into the issues the GSI has because if the GSI works good there's no need to make a new and seperate LineageOS port. I would need to learn how to do that first though so it can take some time.
https://maruos.com/ Hey, I found that this project may be more convenient for running Linux to Android
 
https://maruos.com/ Hey, I found that this project may be more convenient for running Linux to Android
MaruOS is a custom ROM for running Linux on top of Android. My goal is to ditch Android completly and run Linux natively by using a mainline Linux kernel. Someone already managed to run mainline Linux v5.15 on a Mi Pad 5 Pro with SD870 so we can (someday, when everything will work) use this tablet as a normal Linux PC.

https://github.com/lujianhua/xiaomi_elish_stable_kernel/
 

imankhamse

Member
Sep 6, 2014
8
0
Tehran
I have the same tablet and have the same wish as you
please look at the jingOS
and efidroid project
Ithink its a UEFI for android and can load grub witch is start of linux
I may not be good like you but I would be happy to cooperate on this
 
I have the same tablet and have the same wish as you
please look at the jingOS
and efidroid project
Ithink its a UEFI for android and can load grub witch is start of linux
I may not be good like you but I would be happy to cooperate on this
The kernel has to be mainlined first (sadly there are no downstream kernel sources which will make this a bit harder). Once the kernel has been mainlined you can use any distro which has an aarch64 (ARM64) version available. EFIDroid is no longer maintained and is also not needed. We can simply put the kernel in the boot partition and boot it that way.
 
  • Like
Reactions: prozack1983
i managed to install twrp and root with magisk, however i broke my partition B when tried to install gsi from fastbootd. good work @Ungeskriptet
It could be possible that while flashing/updating/messing with the tablet, the super partition got corrupted:
Code:
╭─[email protected] ~/Downloads
╰─$ imjtool super.bin
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 10 logical partitions on block device of 4096 GB, at partition super, first sector: 0x800
    Partitions @0x3100 in 3 groups:
        Group 0: default
        Group 1: qti_dynamic_partitions_a
            Name: system_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x100000 spanning 1 extents and 3 GB)
            Name: system_ext_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0xc4f00000 spanning 1 extents and 255 MB)
            Name: product_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0xd4f00000 spanning 1 extents and 403 MB)
            Name: vendor_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0xee300000 spanning 1 extents and 689 MB)
            Name: odm_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x119500000 spanning 1 extents and 1008 KB)
        Group 2: qti_dynamic_partitions_b
            Name: system_b (read-only,  empty)
            Name: system_ext_b (read-only,  empty)
            Name: product_b (read-only,  empty)
            Name: vendor_b (read-only,  empty)
            Name: odm_b (read-only,  empty)

This is from my tablet when I still had ZUI 13. Maybe it would be possible to dump the working slot from the super partition and flash it in fastbootd mode?

EDIT: Seems like it's the same for the super partition from the EDL/QPST-Firmware. I did flash my tablet with EDL so it's most likely this issue.
Code:
╭─[email protected] /mnt/1TB_HDD/Android/lenovo-tbj716f/TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.211_ST_210730_qpst
╰─$ imjtool super.img 
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 10 logical partitions on block device of 4096 GB, at partition super, first sector: 0x800
    Partitions @0x3100 in 3 groups:
        Group 0: default
        Group 1: qti_dynamic_partitions_a
            Name: system_a (read-only, Unknown, @0x100000 spanning 1 extents and 3 GB)
            Name: system_ext_a (read-only, Unknown, @0xc4f00000 spanning 1 extents and 255 MB)
            Name: product_a (read-only, Unknown, @0xd4f00000 spanning 1 extents and 403 MB)
            Name: vendor_a (read-only, (image truncated - won't try fs detection), @0xee300000 spanning 1 extents and 689 MB)
            Name: odm_a (read-only, (image truncated - won't try fs detection), @0x119500000 spanning 1 extents and 1008 KB)
        Group 2: qti_dynamic_partitions_b
            Name: system_b (read-only,  empty)
            Name: system_ext_b (read-only,  empty)
            Name: product_b (read-only,  empty)
            Name: vendor_b (read-only,  empty)
            Name: odm_b (read-only,  empty)

EDIT 2: Pulled the current super partition from my tablet and now the A partition is completely gone?

Code:
╭─[email protected] ~/Downloads
╰─$ imjtool super.img      
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 6 logical partitions on block device of 4096 GB, at partition super, first sector: 0x800
    Partitions @0x3100 in 3 groups:
        Group 0: default
        Group 1: qti_dynamic_partitions_b
            Name: system_b (read-only, Linux Ext2/3/4/? Filesystem Image, @0x100000 spanning 1 extents and 3 GB)
            Name: system_ext_b (read-only, Linux Ext2/3/4/? Filesystem Image, @0xc4f00000 spanning 2 extents and 255 MB)
            Name: product_b (read-only, Unknown, @0xd5000000 spanning 1 extents and 403 MB)
            Name: vendor_b (read-only, Unknown, @0xee400000 spanning 1 extents and 689 MB)
            Name: odm_b (read-only, Unknown, @0x119600000 spanning 2 extents and 1008 KB)
        Group 2: cow
            Name: system_b-cow (Unknown, @0x119800000 spanning 1 extents and 3 GB)
 
Last edited:

It could be possible that while flashing/updating/messing with the tablet, the super partition got corrupted:
Code:
╭─[email protected] ~/Downloads
╰─$ imjtool super.bin
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 10 logical partitions on block device of 4096 GB, at partition super, first sector: 0x800
    Partitions @0x3100 in 3 groups:
        Group 0: default
        Group 1: qti_dynamic_partitions_a
            Name: system_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x100000 spanning 1 extents and 3 GB)
            Name: system_ext_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0xc4f00000 spanning 1 extents and 255 MB)
            Name: product_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0xd4f00000 spanning 1 extents and 403 MB)
            Name: vendor_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0xee300000 spanning 1 extents and 689 MB)
            Name: odm_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x119500000 spanning 1 extents and 1008 KB)
        Group 2: qti_dynamic_partitions_b
            Name: system_b (read-only,  empty)
            Name: system_ext_b (read-only,  empty)
            Name: product_b (read-only,  empty)
            Name: vendor_b (read-only,  empty)
            Name: odm_b (read-only,  empty)

This is from my tablet when I still had ZUI 13. Maybe it would be possible to dump the working slot from the super partition and flash it in fastbootd mode?

EDIT: Seems like it's the same for the super partition from the EDL/QPST-Firmware. I did flash my tablet with EDL so it's most likely this issue.
Code:
╭─[email protected] /mnt/1TB_HDD/Android/lenovo-tbj716f/TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.211_ST_210730_qpst
╰─$ imjtool super.img   
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 10 logical partitions on block device of 4096 GB, at partition super, first sector: 0x800
    Partitions @0x3100 in 3 groups:
        Group 0: default
        Group 1: qti_dynamic_partitions_a
            Name: system_a (read-only, Unknown, @0x100000 spanning 1 extents and 3 GB)
            Name: system_ext_a (read-only, Unknown, @0xc4f00000 spanning 1 extents and 255 MB)
            Name: product_a (read-only, Unknown, @0xd4f00000 spanning 1 extents and 403 MB)
            Name: vendor_a (read-only, (image truncated - won't try fs detection), @0xee300000 spanning 1 extents and 689 MB)
            Name: odm_a (read-only, (image truncated - won't try fs detection), @0x119500000 spanning 1 extents and 1008 KB)
        Group 2: qti_dynamic_partitions_b
            Name: system_b (read-only,  empty)
            Name: system_ext_b (read-only,  empty)
            Name: product_b (read-only,  empty)
            Name: vendor_b (read-only,  empty)
            Name: odm_b (read-only,  empty)
I managed to repartition and flash the images manually. However, I could not fix widevine status f3, if im not mistaken, it was affected by modem/persist/efs partition. I managed to backup using TWRP and restore function is ok. But i got bootloop after restore 😆.
 
  • Like
Reactions: amiruls

bobochacha

Member
Jan 14, 2022
8
0
Hi, i'm a newbie in configuring android devices. I've downloaded android filehost and the device tree from the link but what am i supposed to do in order to install TWRP? I've enabled OEM unlocking as well as USB debugging. When i go into bootloader i don't see anything that says "Flash recovery". Could anyone kindly guide or provide me steps into installing TWRP? Greatly appreciate the help if can! Thanks!
 

rosco_pc

Senior Member
Dec 6, 2010
85
17
Hi, i'm a newbie in configuring android devices. I've downloaded android filehost and the device tree from the link but what am i supposed to do in order to install TWRP? I've enabled OEM unlocking as well as USB debugging. When i go into bootloader i don't see anything that says "Flash recovery". Could anyone kindly guide or provide me steps into installing TWRP? Greatly appreciate the help if can! Thanks!
you need to get ADB and fastboot tools installed on your computer. Then you can follow the commands as stated in the 1st post
 

bobochacha

Member
Jan 14, 2022
8
0
you need to get ADB and fastboot tools installed on your computer. Then you can follow the commands as stated in the 1st post
Thank you very much for the guidance. I've downloaded the tools as you said and managed to send commands to the tablet but i'm stuck at the flash recovery command. It says waiting for device but on my device but i don't see any confirmation on my tablet. What am i supposed to do from here?

1642150605727.png
WhatsApp Image 2022-01-14 at 5.30.28 PM.jpeg
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi so I broke b_partition of the device need help/guide in getting the required files to flash to fix the issues. Using the fastboot --set-active b keep showing unknown option. Likewise flashing the stock rom using QFIL doesnt fix the issues . Not sure what i did wrong along the way.... Also tried flash fastboot method with the stock rom files doesnt help too.
    The correct command is fastboot set_active b.

    QFIL would actually fix the issue easily as it reflashes the partition table.
    1
    got this instead . Have the latest platform tools too
    Are you sure it's the latest? What does fastboot --version and did you it download from here?
  • 17
    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Working:​

    • Decryption
    • USB
    • Wiping
    • Fastbootd
    • Touch
    • ADB Sideload
    • Formatting Data (Sometimes it errors out after wiping data but it can be fixed by rebooting and trying again.)
    • Toybox

    Not working:​

    • Vibration (Low priority)
    • SD card (Should be possible to mount it manually for now)

    Download: Android FileHost
    Device tree: android_device_lenovo_J716F
    Kernel: Using prebuilt kernel, Lenovo hasn't yet released the source :(

    How to flash to your current slot:
    1. Unlock the bootloader
    2. Reboot into bootloader:
      1. Form powered-on state: adb reboot bootloader
      2. Or from powered-off state: Hold Power + Volume Down
    3. Flash recovery: fastboot flash recovery twrp-3.6.0_11-0-J716F.img
    4. Reboot to recovery: fastboot reboot recovery
    5. Done!
    4
    Will you be working on any ROMS in the future..or do you use a GSI?
    For now I'm using the GSI, but I do want to eventually port LineageOS to it (I have only little experience so this could take a long time). I'd also like to get mainline Linux booting on this tablet, since SD865 is supported in Linux and SD870 is an overclocked SD865.

    EDIT: I've been using the GSI for some time now and the performance is great. I'll try looking into the issues the GSI has because if the GSI works good there's no need to make a new and seperate LineageOS port. I would need to learn how to do that first though so it can take some time.
    3
    Just flashed this without any issues.
    Thanks for your contribution!
    2
    So now we can install gsi through twrp?
    Not so easy. Installing it through fastboot is easier.