How To Guide Install GSI ROM - Xiaoxin Pad Pro 2021 [TB-J716F]

Search This thread

mcdull

Senior Member
Feb 15, 2007
969
75
Hong Kong
I do not know if it is related or reported. There is a DSU Loader in the developer setting, with 2 options inside:-

GSI ARM64
arm64-exp-S3B1.xxxxxxxx

GSI+GMS ARM64
gms_arm64-exp-S3B1.xxxxxxxx

Isn't this enabling the GSI flash directly using the DSU Sideloader?

I am running the latest Chinese Official ROM
 

mcdull

Senior Member
Feb 15, 2007
969
75
Hong Kong
Tried its internal DSU image, its a pure Android 12 with google.
Now I am trying to sideload a Android 12L GSI rom
 

mcdull

Senior Member
Feb 15, 2007
969
75
Hong Kong
ok some updates.
Tested the built in gms_arm64-exp-S3B1.xxxxxxxx (this should be the build number of Google standard GSI)
The rotation is by default wrong.

No HDCP, and my bootloader is unlocked so the DRM level is L3.

Geekbench 5
Single Core 953
Multi Core 2954
 

prozack1983

Senior Member
Wow. No kidding? Did you have any trouble besides the rotation issue with the stock 12? I suppose unlocked BL is necessary for using the built in DSU loader?
Edit: Also, Is there a 2nd party app that can be used to keep rotation correct?
 
Last edited:

mcdull

Senior Member
Feb 15, 2007
969
75
Hong Kong
basically it has almost the same issue as this thread.
It was a shame that I did not run the test before my bootloader unlock, and that makes no sense for me to relock it (no hdcp in gsi anyway).

GSI is not quite usable for me as it is lacking of the feature of a tablet, especially the magatic cover feature to use with the original keyboard cover. But the GSI rom (default) was running great.
 
  • Like
Reactions: prozack1983

mcdull

Senior Member
Feb 15, 2007
969
75
Hong Kong
And uses the DSU sideloader for me is a no-go, it will install correctly but restart will not start in GSI, just the original rom. Could be some AB partition issue? I don't know.
 
  • Like
Reactions: prozack1983

mcdull

Senior Member
Feb 15, 2007
969
75
Hong Kong
Apr 23, 2020
23
13
After a lot of jumping through hoops, I was able to get custom ROMs running on the tablet. Though I do want to share my experience with it.

I chose to run BlissOS 15.3 on it the first time, and it worked quite well, despite the known bugs such as the rotation, adaptive brightness not working, and the phhTreble settings not working either. (Not sure if it is specific to the ROM but there's that.)

A few things I noticed, TWRP would encrypt the partitions if you enabled a password on the system, and the decryption password is not the same as the one you set as the system password.

Another thing is setting the screen cutout to anything else other than the default, to which it will cause the whole screen to turn to black, rendering it useless unless you wipe the data in recovery mode.

I also found out that by changing the boot animation, it doesn't actually write on it, turning the bootanimation.zip file to 0 bytes when moved, a.k.a. it becomes non-existent, and thus when rebooting the tablet, it will drastically slow your device down. Sometimes it even heats up the device, I can even feel it through the casing.

I also tried other Android 12 GSIs, including Android 12L ones, but it had a few more issues, especially the navigation bar on Android 12L.

So for me, BlissOS works fine the best for me.

If anyone can find out how to fix these kinds of issues, let us know.

Thanks to @Tropaion for the instruction guide!
 

supertory

Senior Member
Mar 23, 2014
143
29
OnePlus 7 Pro
After a lot of jumping through hoops, I was able to get custom ROMs running on the tablet. Though I do want to share my experience with it.

I chose to run BlissOS 15.3 on it the first time, and it worked quite well, despite the known bugs such as the rotation, adaptive brightness not working, and the phhTreble settings not working either. (Not sure if it is specific to the ROM but there's that.)

A few things I noticed, TWRP would encrypt the partitions if you enabled a password on the system, and the decryption password is not the same as the one you set as the system password.

Another thing is setting the screen cutout to anything else other than the default, to which it will cause the whole screen to turn to black, rendering it useless unless you wipe the data in recovery mode.

I also found out that by changing the boot animation, it doesn't actually write on it, turning the bootanimation.zip file to 0 bytes when moved, a.k.a. it becomes non-existent, and thus when rebooting the tablet, it will drastically slow your device down. Sometimes it even heats up the device, I can even feel it through the casing.

I also tried other Android 12 GSIs, including Android 12L ones, but it had a few more issues, especially the navigation bar on Android 12L.

So for me, BlissOS works fine the best for me.

If anyone can find out how to fix these kinds of issues, let us know.

Thanks to @Tropaion for the instruction guide!
Thanks for letting us know as well, thinking of trying this out sometime. Btw does it have Nearby Share built in? And do you get notifications like you should ?
 
Apr 23, 2020
23
13
Thanks for letting us know as well, thinking of trying this out sometime. Btw does it have Nearby Share built in? And do you get notifications like you should
Mmhm! Nearby Share works, and notifications work properly as well! Check the screenshots for proof.
 

Attachments

  • Screenshot_20220424-235457_Nova7~2.png
    Screenshot_20220424-235457_Nova7~2.png
    160.1 KB · Views: 87
  • Screenshot_20220424-235504_Nova7~2.png
    Screenshot_20220424-235504_Nova7~2.png
    167.4 KB · Views: 87
Apr 23, 2020
23
13
Are you having any issues with lag in the system, as reported by some others?
No, actually! The only lag that I found is when I tried to change the boot animation. I heard that the system is partitioned exactly to fit every file, so when I tried moving a new bootanimation.zip into /system/media (couldn't find this in other GSIs that I tried) and rebooted, the whole system lagged like crazy. Maybe it's because there wasn't any boot animation?
 
Apr 23, 2020
23
13
If anyone is willing to try Android 12L by following the guide, try these links!
(Make sure to check these often, they might update!)

GSI Rom List that Tropaion included in the guide

crDroid and ArrowOS (in v412 or above) (by Nazim, for some reason these were removed from the GSI Rom List)

phhusson's AOSP (AOSP 12.1)

Nippon GSI (Not sure if these GSIs can work, but feel free to try!)
UPDATE: May 10, 2022
I tried two GSIs from the list (PixelPlusUI and OneUI???), and it only caused bootloops.
 
Last edited:

Tropaion

Senior Member
Jan 4, 2021
55
59
No, actually! The only lag that I found is when I tried to change the boot animation. I heard that the system is partitioned exactly to fit every file, so when I tried moving a new bootanimation.zip into /system/media (couldn't find this in other GSIs that I tried) and rebooted, the whole system lagged like crazy. Maybe it's because there wasn't any boot animation?
That's right, the partition resizes automatically so all files added will be non-existend.
But you can try this: https://forum.xda-developers.com/t/...n-pad-pro-2021-tb-j716f.4348249/post-85900623
 
  • Like
Reactions: prozack1983
Apr 23, 2020
23
13
Here's another prominent bug on Bliss OS 15.3 on the tablet:

Some settings on phhTreble Settings such as System UI Tuner crashes the app. However System UI Tuner on crDroid 8.4 works somehow??

Edit: The video can't be sent somehow, so I uploaded it on Streamable instead: https://streamable.com/taz4rb
 
Apr 23, 2020
23
13
Hey again. I noticed that there are 4 GSI builds in the built in DSU loader now. Has anyone tried these and have any info on whether they're worth a shot?
Looked at the DSU Loader for myself, and it's confirmed. Two of them had S3B1 in it, while the other two had TPB1 instead.
 

Attachments

  • Screenshot_20220503-153633_Settings.png
    Screenshot_20220503-153633_Settings.png
    219.2 KB · Views: 43

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    How to install GSI ROM - Xiaoxin Pad Pro 2021 [TB-J716F]

    I tried to install a GSI ROM on this tablet, because there is only a chinese version available.
    The tablet supports treble and I managed to get different GSI ROMs booting on it, but with a few annoying bugs I couldn't solve.
    I thought I will share my experience here and maybe someone with more expierence can help to solve these problems.
    Your data will be deleted, try at your own risk.

    Treble Device Information (Treble Info):
    Required Image: system-arm64-ab.img.xz
    Supports modern version of treble and uses VNDK30.0
    Supports System-as-Root, uses A/B operating system
    Supports seamless upgrades and uses dynamic partitions (super partition)
    Requirements:
    Installation:
    1. Go to "Settings" ->"System" -> "About Phone", tab on it until developer settings are enabled.
    2. Go to "Developer Settings" and enable "USB Debugging", allow USB-Debugging if tablets asks.
    3. Reboot to bootloader: "adb reboot bootloader"
    4. Flash vbmeta.img: "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", you only need to flash it once
    5. Reboot to fastbootd: "fastboot reboot fastboot"
    6. Flash GSI-ROM: "fastboot flash system lir-v313+211012-arm64-bgZ-lite.img" and wait
    7. Using volume keys on tablet select "Enter recovery" and then select "Wipe data/factory reset", reboot device.
    8. Now it tries booting the ROM, after the "bootloader unlocked" warning, the lenovo logo should show up. Here I often had the problem that it didn't boot at first try. If, after waiting for 20-30s the ROM doesn't boot, press the power button to reboot tablet. After trying it a few times it always worked. This problem only occurs at first boot up, after setting the ROM up, it boots normally.
    9. Now after booting, when using the LiR-ROM, you have to set up the tablet. In the fourth setup window, the ROM is asking for a SIM-Card even though the tablet doesn't support GSM. You can skip this by entering to adb commands "adb shell settings put secure user_setup_complete 1" and "adb shell settings put global device_provisioned 1". After sending these two commands, then pressing return in the setup, it should complete.
    10. After successfully booting, the "Home" and "Tasks" button is missing. After a reboot they should appear and work normally but I recommend to set a lock pin first.
    Known Bugs/Problems:
    AutoRotate
    When activating autorotate, the display is always orientated in the wrong direction by 270°.​
    I tried to solve it with two different commands added to build.prop:​
    1. "ro.sf.hwrotation=270" -> didn't do anything​
    2. "ro.surface_flinger.primary_display_orientation=ORIENTATION_270" -> the screen rotated in right direction, but the touchpanel did not.​
    Workaround: using an rotation controll app, but I'm not a fan of it.​

    Overlay - AutoBrighness, Magnetic Screen Lock, Battery Save Mode
    I tried creating an overlay according to the instructions but sadly the "FrameworksResTarget.apk" from the vendor folder doesn't provide much configuration information including for the above mentioned issues. I tested values from similiar devices but didn't have any success. If someone is interested to try, here are the files I extracted from the tablet and the current overlay I created.​

    Hopefully, someone here knows how to solve these problems.
    4
    After a lot of jumping through hoops, I was able to get custom ROMs running on the tablet. Though I do want to share my experience with it.

    I chose to run BlissOS 15.3 on it the first time, and it worked quite well, despite the known bugs such as the rotation, adaptive brightness not working, and the phhTreble settings not working either. (Not sure if it is specific to the ROM but there's that.)

    A few things I noticed, TWRP would encrypt the partitions if you enabled a password on the system, and the decryption password is not the same as the one you set as the system password.

    Another thing is setting the screen cutout to anything else other than the default, to which it will cause the whole screen to turn to black, rendering it useless unless you wipe the data in recovery mode.

    I also found out that by changing the boot animation, it doesn't actually write on it, turning the bootanimation.zip file to 0 bytes when moved, a.k.a. it becomes non-existent, and thus when rebooting the tablet, it will drastically slow your device down. Sometimes it even heats up the device, I can even feel it through the casing.

    I also tried other Android 12 GSIs, including Android 12L ones, but it had a few more issues, especially the navigation bar on Android 12L.

    So for me, BlissOS works fine the best for me.

    If anyone can find out how to fix these kinds of issues, let us know.

    Thanks to @Tropaion for the instruction guide!
    3
    We should spam this forum thread, maybe then they will eventually react :D
    I am doing my damnedest! I also got PE12.1 running today after finally taking the plunge and just wanted to also say thanks for the initial write-up. It got me through the whole process with only a couple (tiny) snags.
    The command fastboot reboot fastboot(d) can be confusing 😁 I eventually ended up using the key combos to get where I needed due to my not having everything up to date and pristine.
    With the exception of the never ending autorotation bug and pixel launcher being not optimized for tablets, it is still miles above ZUI, imho.
    3
    hye xda-er,

    after flashing several gsi's (pixel experience a11/12 and octavi os),
    i found out that geekbench score is a bit worse than the stock rom,
    i attached the score here:-

    stock rom
    -single score = 967/955
    -multi score = 3111/3067
    -vulkan score = 4256
    -opencl = 3579

    gsi's
    -single score = 948
    -multi score = 2619
    -vulkan score = 3400
    -opencl = 3500

    how about all other experiences?