yashsingh1/xdaforums huggingface dataset:
[Thinkpad Tablet General] :
You're welcome. I am glad someone else is around.

I was talking about input methods and other bloat in /system/vendor that gets installed by default depending on where you're supposed to be located. For example, if you configure your tablet in Russia, you'll get Yandex Search, Browser and App Store or Yahoo Search if you are in Japan. I just wiped the hell out of those things because they are just too old right now, also they can be installed from the Play Store if you use it to install apps.

If one day we have an update that depends on us at this point. Alquez is gone from xda and github, he was the developer more involved on this device that I know of. I am confident I can build a working kernel for the device, but it will take too much of my time and I have doubts it will ever work with touch screen, audio, battery and projector. By the way, I think mainline Linux works fine with the tablet except for the projector and battery, there was a fix recently for touchscreen, but I can't say since I've never booted any other thing. I am curious enough to try Linux, but don't see any advantages considering the sell point of the tablet is in its multimedia capabilities.

As I said, using Linux is not something I have tried in the tablet, but I use Linux daily in my PC. I remember Intel Platform Firmware Tool writes partitions directly into the eMMC blocks, so basically one could wipe the whole disk and still recover from a bricked device provided you can still boot into DNX mode, and even if you can't, as this device can read from a USB device attached, you can always try to mess around from a live Linux session. I would try something more bleeding edge than Ubuntu LTS, just in case some related progress had been made to the kernel in recent developments (Fedora, Fedora Beta, for example. Manjaro is fine but supports several kernel versions and I don't know if it uses Linux-LTS by default, which is undesired).

It would be useful to run gparted (or lsblk if you prefer CLI) in your live Linux session, and see what partitions are being detected by Linux. I imagine there is an EFI partition that we could back up and modify to boot Linux and install the OS in the system partition. You should be able to boot into recovery using hardware keys and restore the android system partition if this does not work and restore the EFI partition to repair booting into Android. At some point we could reach to the postmarketOS people and see what they think about this device. Being said all that, it is a rather expensive thing to brick, but if you are up to experiment count me in as support staff.

I am quite happy with this new cooked ROM, to be honest. After I wiped the config partition that holds some configuration files during first boot they get rewritten, and the difference is notable. It is finally, after years, behaving as a powerful Android device for its time. I even tweaked the thermal throttle and just unleashed the capped cores to its full speed, since it doesn't get hot even while playing HD video. For a portable device, the GPU is awesome.

EDIT: Found this in GitHub, for what it's worth:
[Thinkpad Tablet General] jukbee:
[/QUOTE]

Sorry but both links aren't working...
[Thinkpad Tablet General] :
Hey, thank you! They should be fine now.
[Thinkpad Tablet General] nikolatodorovbg:
Links are dead again. Anyway i tried the first ROM. GREAT WORK! Now my tablet works fine , like never before. Thnk you very much.
[Thinkpad Tablet General] :
Bad timing for me... but thank you. It should be working now, again.
[Thinkpad Tablet General] drduranduran:
I'm glad there are still some people working on this. I bought the YT3-X90F shortly after release ($500) because I thought with the 4GB of RAM and the projector, the community would at least be all over it for years. I also expected Lenovo to do better than leave it so gimped. Sadly, neither of these things came to pass. This crap is done for planned obsolescence so I buy the next unit when I don't need it.

I'm still on the stock rom; the latest one officially offered via download from the unit. Is it worth flashing this version with this modded version? I do feel like this thing is performing way more poorly than it should for the specs.

This tab would be amazing with Android 9 or 10 and still have so much more life left in it. Governments should force companies to support these devices, just on the sake of keeping more of these units in the field and out of landfills; even for security reasons as well.
[Thinkpad Tablet General] :
Using my ROM the tablet performs almost as expected for a device with its characteristics, in my opinion. As I wrote, there's nothing much to lose except maybe a couple of hours. Make a nandroid backup and try it. If you can't get past the wizard, remember to fastboot erase config, fastboot format config. If it doesn't work restore your backup.

Also, remember that once you start messing with your device, it is not secure anymore. Don't use it for serious things, it's not updated with security patches, is not encrypted, and is probably not protected with Factory Reset Protection Lock

I don't use Google Play Services, so I can't give an opinion about those. I left them there because I was hoping someone else would benefit from my hacking, but I am confident that even with Google Play Services, your 4GB RAM tablet should work like a charm.

I've been messing around with the tablet recently and the eMMC partition list is quite interesting for a permanent install of Linux. There is an unused partition of 512 MB that can be formatted as an EFI partition to install GRUB but you need to sacrifice another partition to install the system root. In my case, with a 2GB/32GB tablet, I'd have to use the data partition, as the other would be too small, but you could probably use other, considering a 4GB eMMC.

The point is the android_okr partition is free to use for anything, if you can get to GRUB from a live session, then I am sure you can get to an eMMC installed GRUB. The condition now is where to install Linux, in data or system partition? If you install in the system partition, then you would need to reflash the cooked ROM if you want to go back to Android and the system will occupy most of the space in the partition, if it fits at all. If you use the data partition there is plenty of space for the Linux system and your home but if you want to go back to android, you will need to take a nandroid backup of the data partition before installing Linux or reinstall all your apps after formatting the data partition.
[Thinkpad Tablet General] guillaumeg:
Thanks for the explanation,

I will first have a try to your personal cooked rom, now that the link worked.

About Linux, yes as you said this is expensive to have it bricked...

But I will try a non LTS kernel based distro, as you adviced, when I have free time with Live Session to see whether sound, touch and BT are working in recent kernel.

I also tried some

I don’t know a lot about eMMC and EFI partition, so I was wondering exactly the same thing, in which one to install Linux, can we achieve dual boot and how should I be sure that the TWRP will never disappear during one these installation?

As long as I have access to TWRP, I am pretty confident about trying a lot of stuff

EDIT: So That means that if I want to install Linux system in the data partition, Android would just use the Linux Etx4 partition as its data partition?

I have seen some pretty nice Linux uses with the Yoga Book and the Yoga Book 2, but I don’t know to be sure if the touch/bt/etc... drivers are the same, but it might be interesting to check their works

https://xdaforums.com/t/linux-mint-...request-for-help.3839412/page-3#post-84317193

https://xdaforums.com/t/dualboot-android-linux-for-yoga-tab-2-830f.3955357/
[Thinkpad Tablet General] guillaumeg:
I am pretty sure, at least in Europe, Companies using open-sourced licensed code has obligation to publish it as opensource, so if Lenovo followed any rules, this tablet could have been updated.
[Thinkpad Tablet General] :
So many topics.

But first things first, try to reduce the amount of installed apps in Android and keep only the essential ones to free up space in the data partition. It would be very helpful to see if Ventoy works with your tablet. Ventoy is a tool to boot distros from USB, you part your USB into two partitions, one contains ISOs for bootable OS media, the second contains the Ventoy loader which allows you to select which ISO you do want to boot. This way you can have, let's say Fedora, Manjaro, openSUSE Tumbleweed and Windows in the first (large) USB partition ready to boot, and you don't have to use Etcher to rewrite the USB every time you want to try a new OS.

Fedora is an interesting distro not only because it always has the most recent stable kernel, but also because they are implementing new technologies in video (Wayland/Vulkan) and audio (Pipewire) and that may help to see if something changed for the better with the tablet hardware.

If you manage to use Ventoy to boot into the Live session, running gparted in the Live session would be very helpful. In my tablet, fdisk tells me the data partition is the last one in the eMMC. If it is the last partition for you too, try using gparted to shrink the data partition (it is the biggest and must be at the end), shrink it just a little, we are trying to see if changing the size of the partition will stop Android to boot. IT IS VERY IMPORTANT THAT YOU SHRINK IT FROM RIGHT-TO-LEFT, this is, don't separate the partitions, just make some free space at the end of the storage after the data partition. Apply the changes and reboot without the USB attached and see if you can still boot to Android. If you can't, go back into a live session and resize the data partition to its original size. Try to boot Android again. If it doesn't boot, restore the data partition from your Nandroid backup.

If you can boot Android after that change, then we can split the data partition in two, one for android (mmcblk14) and one for Linux (a new mmcblkp15). Notice that if you do this, you can't restore your Nandroid backup anymore since the size of the partition to restore won't be large enough. After splitting data, we can use the android_okr partition (mmcblk0p12) as another EFI partition to install GRUB instead of replacing the factory EFI loader (Android-IA) as they are doing in one of the threads you cited. This is way safer, and with some luck, since we keep both, we can use the BIOS Boot Manager to point to our desired EFI loader (factory-Android-IA or GRUB). If everything goes smooth, in Linux we can try os-prober to see if GRUB detects an Android to dual-boot from GRUB.

What do you think of this approach?

EDIT: If you think it is too complicated, take it step-by-step. You already booted into Linux live session... so, now try to boot with Ventoy or if you want to go faster and deeper, try to resize the data partition from your Linux live session using Gparted and see if this change still allows you to boot into Android.
[Thinkpad Tablet General] prisma:
Hi, thank you for your support. I have the problem that the Intel Tool does not find a flashable file within the zip packages. With or without unzip. Do I have to renamw something?

Best, prisma
[Thinkpad Tablet General] :
The zips provided in post 46 have to be flashed with TWRP.
[Thinkpad Tablet General] guillaumeg:
Thanks for all your advices @CENTSOARER

First I flashed your personal rom yesterday and it is really fluid and efficient ! Thanks a lot.

I also installed Ventoy on my USB Drive

As soon as I have time to try it with one of the distro you cited on the Tablet, i will notice you.
[Thinkpad Tablet General] :
Just wanted to recommend all those people with the 2GB version a setup including a swap partition in the SD card, preferable a fast SD Card, but whatever, really. You can automount it with Magisk using a priority of 0. Damn, why did I take so long for doing this? Yes, we have a low amount of RAM but we can take 256 or 512 MB of RAM for zRAM, and use this as a cache for a Swap partition. If you set loose/less agressive minfree values for the LowMemoryKiller is a good multitasker, gets slow from time to time, depending on what apps you keep open, but very few apps are getting killed.

EDIT: Also, Fedora Linux uses half the RAM as zRAM in computers with less than 16 GB RAM now. We are talking about very different beasts... but I wonder...
[Thinkpad Tablet General] NoTime4Gamez:
Whats the latest android version you can put on a Yoga Tab 3?
[Thinkpad Tablet General] :
In the Yoga Tab 3 Pro version (Intel Atom Cherry trail x86_64), Android 6.0 Marshmallow. In the Yoga Tab 3 Plus (Snapdragon arm64), you can put even Android 11, but LineageOS official builds are in v16 (Android 9.0).

Also, for the Pro version, a similar device was running Android Nougat once. Current firmware is Android 6.0 latest release was from one year ago... TBH it was a very strange update after years of oblivion.

In theory a mainline kernel can run relatively well on the tablet since some people run Linux distros in it, but you can't use some of its features because of a lack of proprietary drivers. So, in theory, it COULD run Android 11, but will never use all the hardware capabilities.
[Thinkpad Tablet General] bababaaharg:
Just letting you know that the cooked ROM links (both of them) are already dead again ;(
[Thinkpad Tablet General] :
Yes, it is gonna be like this for some time because I am still making some changes and waiting for approval to share other thing. That's why I asked you guys to mirror it if it's important to you to have always a copy around.

Give me some time to upload. "myROM" version will have more changes related to zRAM and virtual memory management and other system apps that aren't really required by the OS. I also updated some Google Apps. I know the "debloated" thing is overselled here @xda, but it really makes a difference in this build because we have several (maybe) useless processes running with high priorities all the time. In the meantime, you can try the "xda" version, should be working now.

EDIT: The links are fixed now, I added one more. I don't know who would like the same stupid OS with updated Gapps but it was done and maybe someone will use it.
[Thinkpad Tablet General] :
So, I was trying to remap my power button since it's been barely working for some time. I've been abusing my battery with an app to wake the tablet by shaking...

Anyway, if you want to use your projector button as a power button, edit your /system/usr/keylayout/Generic.kl file, find the line number ~407 and edit it from "key 752 DLP" to "key 752 POWER". Reboot the tablet and there you go, you have an additional power key.

This button won't work well to bring up the Power off menu, the long press action will throw the menu as well as a screen off event, but it works wonderful to turn on/off the screen with a single press. To reboot, power off, and turn on the projector you may want to use the QS tiles or any software shortcut. At least you will extend a bit of the useful life of your tablet, and will help those of you afraid of opening the tablet to fix the main Power button.

EDIT: Yeah it works as a regular Power button, the thing is it has a long press and a longer press. The trick is to keep pressing the right amount of time, you get used to it.
[Thinkpad Tablet General] GGuillaume:
I was wondering if there is the possibility to enable double tap to wake in the kernel, since there is a kind of double tab to wake when projector is on?

Thanks for the power button hack
[Thinkpad Tablet General] :
I did try to build a kernel from sources I found in github and Lenovo's website, but couldn't even finish the build process and again, I don't have enough time to keep trying and... to be honest, how much longer will we be able to squeeze some life out of this hardware? Time to give up for me, unless some Linus Torvalds-like comes forward and offers to help. Meanwhile, all we have are hacks, sadly. Never again buy from Lenovo.

Anyway, no, the kernel does not have dt2w support, the Dlp software does the double tap to wake screen, but is different because the tablet is not in deep sleep.
[Thinkpad Tablet General] Alein_:
Hi, please change the language to English as default, after I use your ROM ( my device had broken data partition) My tablet boot into Chinese, and it is soooo slooow. Also, all my old programs and config seems to be "recovered". Could you change the name of the ROM to something more accurate?
[Thinkpad Tablet General] :
I don't know what you mean, but it's fine since I don't know what you did. Therefore, won't change anything. But if you care to elaborate what you did, that can be helpful.
[Thinkpad Tablet General] denDwaler:
Thank you, centsoarer, joesnose and everyone else who made this possible.

I own a 4gbyte YT3-X90L, followed your guide and installed successfully your shared "Myrom".

All went smoothly until I had to use fastboot.

I ran into the "waiting for device" issue. At first i thought it was a driver problem.

It took me several days before i discovered that fastboot does not communicate when using the usb 3 port on my PC.

After connecting a hub to this same usb 3 port and putting the YT3-X90L into the hub i immediately got a response , in other words a working fastboot!

The hub forced into another mode.

The problem was mentioned elsewhere on this forum but not in this thread.(cannot find it anymore)

Maybe this helps out other enthusiasts.
[Thinkpad Tablet General] damru:
Hi ,Any TWRP links? I have twrp-2.8.7.0(6)-x90-data-enabled, is that right version?
[Thinkpad Tablet General] :
I have a modified version of TWRP but is based on the same version you have. My custom version can deal with more partitions and has a more complete set of busybox snippets... being said that, the version you have installed should work.

I have a new cooked ROM in my tablet with a better approach to the WiFi conversion but I haven't had the time to upload.
[Thinkpad Tablet General] damru:
I dont know why but i have a lot crashes on some apks like tidal, vanced manager and more. Any idea why ??
[Thinkpad Tablet General] :
AAMOF, yes. It is likely that the settings in the virtual memory are too tight for that version. I have had the same issue using heavy apps like Prime Video.

Try these settings in your /system/build.prop file:

dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=320m
dalvik.vm.heaptargetutilization=0.85
dalvik.vm.heapminfree=4m
dalvik.vm.heapmaxfree=8m

Don't forget to wipe dalvik/ART cache and cache partitions after editing the file. Also, it'd be useful if you (and, really, anyone using this) report back.
[Thinkpad Tablet General] Quardah:
Hello! I have recently acquired an YT3-X90F but i am unpleased with the current performances. I found your post and i would like to try your custom rom but i just want to get this straight before we start.

Considering i have done no operations yet on the tablet, it's running latest updated software from stock firmware. I do not have TWRP installed or anything done on the tablet yet.

1. I download ROMx90F_wifi.zip from the first link in post #1 (most recent update called FINAL RELEASE)

2. I rundown the procedure in the 'HOW TO FLASH A STOCK FIRMWARE (YOU CAN DOWNGRADE AND UNBRICK TOO)' section in post #1 using the Intel Platform Flash Tool Lite from flashtool.org

Is that all? yes/no? If not, can you tell me what steps i should do before and after?

I am asking these details because i am unsure from your post if i should install TWRP prior to trying your operations, and if i should do the RAM related operations explained in your post afterwards. There is a lot of information that has been detailed in the thread and it's very hard to follow it all.

I am also unsure if from a stock tablet i can simply flash your custom rom straight in the tablet. Do i need to change things in the developer options before trying to change the rom?

An updated and clear procedure detailing the manipulations starting with an unmodified X90F would be very appreciated.

Thank you for helping us all.
[Thinkpad Tablet General] :
You need to unlock your bootloader (this will factory reset your tablet), then you need to install TWRP, one that can deal with the data partition. And after this you need to use TWRP to format your data partition (not only wipe). Finally, use TWRP to wipe ART/Dalvik, cache, data, boot and system partitions and flash the zip of the final release. Hope everything goes fine.

Edit: Sorry, I have to add I don't get a lot of feedback here. What I wrote is the ideal path to get to my current cooked ROM. To give you a detailed guide would take for me a nandroid/trwp backup, then to find a suitable firmware, get back to stock firmware using Intel Platform Flash Tool, and after all this, tryby myself those general guidelines I give you in this post. I am just not doing this. I can assist you, however, in the process. Maybe you can document it for all of us.
[Thinkpad Tablet General] Quardah:
Hi.

I tried my luck at what you said. Here is where i am right now :

using this site (in french, my native language) : https://www.phonandroid.com/forum/t...ooter-yoga-tab-3-pro-yt3-x90f-x-l-2go.147758/

I have managed to get into TWRP 2.8.7.0 YogaTab3Pro 6.0 build.

I have made a backup of all partition as stated on the site including the boot partition.

Note that on my SD card i have 4 files now :

ROMx90F_wifi.zip (your cooked rom)

twrp-2.8.7.0(6)-x90-data-enabled.img.zip (if i understand correctly, it's a script to enable the data partition in live runtime of TWRP)

UPDATE-SuperSU-v2.46.zip (the SuperSU script)

x90-disable_encr.zip (the script to disable data encryption).

i ran the superSU script and then the x90 disabled_encr script. both ran ok. I tried going into wipe to format data, but i get the error 'cannot locate /data'. The superSU script specifically says that it mounts /data, therefore it should be there (i guess)

i tried the x90-data-enabled.img.zip but it fails mentionning it cannot find 'META-INF/com/google/android/update-binary' in the zip file.

i then tried Alternative 1 which is reboot in fastboot mode and run fastboot format data but i get the following error :

$ fastboot format data
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for data

I require your help because i am stuck now on step 'And after this you need to use TWRP to format your data partition (not only wipe).'

again, when i try to 'Wipe -> format data' in TWRP i get 'Unable to locate /data'.

I believe once this little issue is resolved, i will be able to wipe all partitions and flash your rom. but i need to debug this first and i am out of idea.

Please let me know what you think.

Thanks.
[Thinkpad Tablet General] :
Forget about superSU, you won't need it. Also, that zip you're trying to flash, the "x90-data-enabled.img.zip", is not a flashable zip but a compressed image flashable via fastboot. To use it you need to uncompress the zip and extract the twrp-something.img. The goal here is to flash this extracted file as your recovery system with fastboot flash recovery twrp-something.img.

Then go into recovery. Wipe ART/Dalvik, cache, data, boot and system partitions. Once done, flash my cooked ROM. After the ROM flashes, do the format data procedure where you have to confirm "yes". Now reboot and hope for the best.

PS. I do not know why joesnose decided to share two twrp images. In my opinion, you are better off with the "data enabled" one, period. Everything you can do with the one without data partition management you can achieve with the one capable to manage data partition.