Project Treble GSI images on Smart Tab M10 (TB-X605F/L) and P10 (TB-X705F/L)

[Lackooo84]

Got the same **** error message on pie rom too....

I'll give up...

Another anomaly.... I flashed this twrp on pie rom but when I tryin to enter twrp stock recovery loads up.... :/

 

[Yahoo Mike]

Ok I think I got it. Now I'm back on pie, tried these commands but always get error:

View attachment 5516229

Try this command:

adb push modify_phh_gsi.sh /external_sd/modify_phh_gsi.sh

I think adb is complaining there was no destination filename. Make sure you are using the latest adb from google.

I'm a bit confused because in step 3. you said "download the file onto sd card", in step 4. copy file to sd card.

In step 3 you download the files from the internet to your PC. In step 4 you copy the downloaded files to your sdcard.

Okay, what do you mean by "load the rom in LMSA"? Do I start the rescue mode process (with click on the start rescue button) or what do you mean exactly?

Yes, start the rescue. That will load the stock ROM for you.

 

[Yahoo Mike]

Got the same **** error message on pie rom too....

I'll give up...

View attachment 5516313

Did you run the modify_phh_gsi.sh script? Did it work?

If it worked, then what is the size of your system partition and your GSI image?

Another anomaly.... I flashed this twrp on pie rom but when I tryin to enter twrp stock recovery loads up.... :/

That sounds like a 3-button problem. Check the TWRP thread for this device for tips.

 

[Lackooo84]

Did you run the modify_phh_gsi.sh script? Did it work?

If it worked, then what is the size of your system partition and your GSI image?
That sounds like a 3-button problem. Check the TWRP thread for this device for tips.

Do you read pm's dude?

 

[Lackooo84]

Did you run the modify_phh_gsi.sh script? Did it work?

If it worked, then what is the size of your system partition and your GSI image?
That sounds like a 3-button problem. Check the TWRP thread for this device for tips.

No, because it is not possible to have 2 different recovery in the same partition. adb reboot recovery also work to boot recovery.

So, can you tell me please step by step what to do? In step 3 you said download files to sd card, then in step 4 copy them to sd card, but why would I copy them when they already on the sd card? :/ This is why I'm confused with this guide. Also I'm on stock pie already do I need to re-flash it again? How do I run those scripts on the sd card?

 

[Lackooo84]

Ok now I was able to flash android 10 GSI onto oreo rom (same room has bricked my tablet before when flashed it on pie). I tried several Android 11 GSI's, none of them worked. All of them gives me "size too large" error in fastboot, those GSI's about 3.4GB. Nvm I'll stay on android 10, all I wanted just a dark mode theme which is missing from stock roms on this tablet...

The funny thing is I cannot even install Gapps stock package it says not enough space on system partition... on a fully empty system... what a joke...

I just wonder how was anybody able to install Android 11 rom onto this device if I can't... I have a 32GB version is there any with bigger storage space out there?!

 

[Yahoo Mike]

No, because it is not possible to have 2 different recovery in the same partition. adb reboot recovery also work to boot recovery.

So, can you tell me please step by step what to do? In step 3 you said download files to sd card, then in step 4 copy them to sd card, but why would I copy them when they already on the sd card? :/ This is why I'm confused with this guide. Also I'm on stock pie already do I need to re-flash it again? How do I run those scripts on the sd card?

The point of steps 3 and 4 is to get those files onto your sdcard. Once you've done that move on to the next step.

It is important that you run the script on your device when in twrp. One of the things it does is increase the size of the filesystem on the system partition.

If you are having problems installing twrp, read this device's twrp thread. There are tips there on how to get twrp booting.

If you did not root or modify the stock ROM, then there's no need to reload the stock ROM. The GSI just needs all partitions to be pure stock.

 

[Lackooo84]

Just please tell me the noob friendly steps what to do to resize partition in twrp.

What I tried so far:

While was on stock pie, put those files onto sdcard, installed/entered twrp.

Now in your guide next step is to install new GSI, but I cannot because system partition is too small.

In your guide I need to run the script AFTER flashing new GSI, that is what I don't understand.

I tried to run those commands in adb sideload from PC, but always getting errors.

So please tell me step by step what to do to resize partition in twrp pls!

 

[Yahoo Mike]

On Linux-based systems (like Android), the filesystem and partition are two separate things.

The script in the OP will expand the filesystem to the full size of the system partition. This usually results in enough free space to install GApps (usually nano or pico) after installing a vanilla GSI.

There are no instructions on this thread to change the size of the system partition. If your GSI is larger than the partition, then it will not fit. Compare the size of your GSI image with the size of the system partition.

 

[Lackooo84]

On Linux-based systems (like Android), the filesystem and partition are two separate things.

The script in the OP will expand the filesystem to the full size of the system partition. This usually results in enough free space to install GApps (usually nano or pico) after installing a vanilla GSI.

There are no instructions on this thread to change the size of the system partition. If your GSI is larger than the partition, then it will not fit. Compare the size of your GSI image with the size of the system partition.

Then how other flashed successfully android 11 GSI's if all of them bigger than 3GB and this tab has only 3GB of system space?? Then you can install only android 10 but not 11....

I asked you more than once to tell me step by step how to run these srcipts exacty but still no answer... thanks.

 

[Yahoo Mike]

Then how other flashed successfully android 11 GSI's if all of them bigger than 3GB and this tab has only 3GB of system space?? Then you can install only android 10 but not 11....

I run AndyYan's LOS 18, which is about 2GB. It is vanilla A11. Then I install pico opengapps for A11 ARM64. There are other GSIs that fit on these tablets.

I asked you more than once to tell me step by step how to run these srcipts exacty but still no answer... thanks.

To run the script, the OP gives an example using ADB commands. You can also run the script in the TWRP terminal. Or you can open an ADB shell and run it there. If you are getting errors, what do they say?

The easiest way to install the zips is in TWRP. If you don't know how to do that, you could check the TWRP threads for instructions or google it.

 

[浅香ジュン]

Hey there,
I've found a method to install Android S GSI ROMs (Broadly speaking, the System-As-Root ROMs) on X605F. There's a patch called MakeMeSar by @erfanoabdi, which can make the device support System-As-Root. After apply it, we can flash A/B GSIs on this device just follow your way.
For more information, I wrote a post: https://xdaforums.com/t/android-r-gsi-system-as-root-on-on-smart-tab-m10-tb-x605f.4400689/.
Thanks for providing a way to install GSI ROMs on X605F.
Regards,
Jun ASAKA.

 

[Yahoo Mike]

Thanks to Jun, there's a new version of modify_phh_gsi.sh in the OP. It now also supports a device that's been modified to SAR. If there are any problems, let me know.

 

[JinbaIttai]

I just want to say thanks to @Yahoo Mike and everyone involved in this comprehensive thread.
I found it very useful when setting up my new TB-X705F with LineageOS 18.1

I just want to add a couple of notes on my experience.

I spent a long time trying to get "root" working, I couldn't figure out what to do with the "Magisk (for phhusson-based GSI ROMs)" in the OP.

Every time I tried to flash any of those I soft-bricked my device and had to use the Lenovo Rescue and Smart Assist to flash back to stock and start again.

I also had trouble using the Lenovo Rescue & Smart Assist, it kept failing to restore my device.
After using fastboot to reflash the stock boot image, the restore went perfectly.

Eventually I cottoned on to the fact my ROM was already rooted with phh su, and all I had to do was install the
me.phh.superuser_1.0.3.3 apk.
It's no longer available via Google Play but can be found on various apk mirrors.

Also, after getting everything else set up and working I wanted to use the included Smart Dock as a Bluetooth speaker. I could connect to it but not play any music through it.

It turns out I needed to do the initial configuration via the Alexa app first, otherwise it won't show up as a Bluetooth speaker. So (after backing up my /data partition via TWRP) I flashed stock again, configured the speaker with a throw-away Amazon account, then back to LineageOS.

So for future players - set up the speaker first - when configured properly it will show up in your Bluetooth devices twice. Once as a media device (headphones logo) and once as a generic device.

 

[Eighthourblink]

Has anyone ran into an issue where after flashing over one of the GSI images, it gets stuck at the inital booting animation? I let it go for hours with no progress

Tablet : Lenovo M10 x605f (3GB)
Image : lineage-18.1-20220715-UNOFFICIAL-arm64_bvS-vndklite
Android : 11

 

[Yahoo Mike]

Has anyone ran into an issue where after flashing over one of the GSI images, it gets stuck at the inital booting animation? I let it go for hours with no progress

Tablet : Lenovo M10 x605f (3GB)
Image : lineage-18.1-20220715-UNOFFICIAL-arm64_bvS-vndklite
Android : 11

What you are describing will happen if
Disable_Dm-Verity and/or modify_phh_gsi.sh fail.

Do they report any errors? Make sure you run the latest versions.

 

[Eighthourblink]

What you are describing will happen if
Disable_Dm-Verity and/or modify_phh_gsi.sh fail.

Do they report any errors? Make sure you run the latest versions.

When running them both within TWRP, there are no red errors and each of them completes fine. The way that Im running modify_phh_gsi is using adb shell from computer, chmod'ing the file and running the script. Completes with no errors

Regarding modify_phh_gsi, is the one that is linked here (MEGA) the most updated one, or the one within Github (HERE).

Disable_Dm-Verity was grabbed from here (HERE)

Forgot to mention - although there is a newer version of TWRP out, im using the one from the guide here, TWRP 3.6.0

 

[Yahoo Mike]

When running them both within TWRP, there are no red errors and each of them completes fine. The way that Im running modify_phh_gsi is using adb shell from computer, chmod'ing the file and running the script. Completes with no errors

When boot is stuck on the Lenovo screen it is usually because the Android init process has aborted.

One reason that happens is because the GSIs try to mount the system partition read-write, but this tablet's bootloader tells the kernel to stop loading when this happens. This is a security measure. The script modifies the GSIs to stop them from mounting /system r-w.

After you have flashed your GSI ROM and run the zip and script, in TWRP try this:

adb shell
umount /system         <== it's ok if this fails
mount -r /system
cat /system/bin/rw-system.sh |  grep "if mount -o remount,rw"

The output should start with a "#". If not, the script did not run properly.

If it does start with "#", then boot the GSI and let it sit for about 30 seconds at the Lenovo logo. Then grab the system and kernel logs. The kernel log should report why it was told to stop the init process. PM me a link to the logs:

adb logcat -d > system.log
adb shell su -c "dmesg -T" > kernel.log

Regarding modify_phh_gsi, is the one that is linked here (MEGA) the most updated one, or the one within Github (HERE).

A simple file comparison shows they are identical.

Forgot to mention - although there is a newer version of TWRP out, im using the one from the guide here, TWRP 3.6.0

The version of TWRP shouldn't matter. Your problem is that the init process is aborting.

One last question: after you tried the SAR conversion, did you run LMSA and get your tablet booting into the stock ROM again? You will need to do that before you can load an A11 GSI.

 

[Eighthourblink]

When boot is stuck on the Lenovo screen it is usually because the Android init process has aborted.

When i stated that its getting stuck at the booting animation, i meant the LineageOS "arch" booting animation. Sorry for not being clear about that.

One last question: after you tried the SAR conversion, did you run LMSA and get your tablet booting into the stock ROM again? You will need to do that before you can load an A11 GSI.

Yes I am running LMSA in Windows (gross) each time. Its been a lovely back-and-forth process. Let me try it one more time here after I study for my Sec+ exam.

Also, for A11. is lineage-18.1-20220715-UNOFFICIAL-arm64_bvS-vndklite the correct one for Lenovo x605f. There is no A-Only variant.

I appreicate you helping me on this matter

 

[浅香ジュン]

Has anyone ran into an issue where after flashing over one of the GSI images, it gets stuck at the inital booting animation? I let it go for hours with no progress

Tablet : Lenovo M10 x605f (3GB)
Image : lineage-18.1-20220715-UNOFFICIAL-arm64_bvS-vndklite
Android : 11

If you want to run Android 11 directly instead of SAR, you should use A-only images. I recommend you to restore your device with LMSA or QPST and follow this thread, the SAR has many issues to solve, whilst installing Android 11 A-only directly runs well.