A comprehensive guide to the Lenovo Yoga Tab 3 Pro (YT3-X90*). Cooked ROM & TWRP!

Search This thread

drduranduran

Member
Aug 14, 2008
14
2
I have been using this tablet for years now and just wish I had the option to disable encryption to increase the speed and a fairly new build of Android. I will never buy another Lenovo Tab again because of the lack of software support.

It's a shame because the 4GB of RAM and a Projector on the spine on a 4 core device is a beast, but it's so gimped at this point. I always come back and look for some nice Android 9 or 10 upgrade.... nada.
 

CENTSOARER

Senior Member
  • Apr 22, 2013
    818
    478
    Mexico City
    I uploaded but please be careful. I am not around and it barely have had any feedback from other models of the tablet. In any case, if you are feeling adventurous, you could replace the boot.img in the zip of the Cooked ROM for your own and try to flash it. If you want to help others, you could upload and share a copy of your kernel (boot.img) specifying the model of yur Yoga Tab with detail, this way I can tweak the kernels and share several cooked ROMS with specific kernels for specific devices. The files are up again and they won't go away soon, since I'm using my own Nextcloud this time. Good luck. If you find out something you think may be of use, please share.
     
    Last edited:

    sangotrunks

    New member
    Dec 2, 2010
    3
    2
    I uploaded but please be careful. I am not around and it barely have had any feedback from other models of the tablet. In any case, if you are feeling adventurous, you could replace the boot.img in the zip of the Cooked ROM for your own and try to flash it. If you want to help others, you could upload and share a copy of your kernel (boot.img) specifying the model of yur Yoga Tab with detail, this way I can tweak the kernels and share several cooked ROMS with specific kernels for specific devices. The files are up again and they won't go away soon, since I'm using my own Nextcloud this time. Good luck. If you find out something you think may be of use, please share.
    Hi, i'm also a Yoga tab 3 pro owner mine is a YT3-X90F, but i did some modifications ans i have flashed a modified rom that come from an user of YT3-X90L.

    It worked but in fact it was not the remedy for bugs and others crashes, Today i have turn on my tablet and got a OTA for YT3-X90L, who didn't was installed they put me on TWRP and get a failure message.

    If it can help you to make more cooked roms i can share my backup from stock firmware YT3-X90F and the custome rom that mine today.
     

    Attachments

    • IMG_20201225_191235_resized_20201225_071327072.jpg
      IMG_20201225_191235_resized_20201225_071327072.jpg
      550 KB · Views: 75

    alesamsung

    Member
    Aug 29, 2013
    5
    0
    Hi everyone ,
    I'happy to see someone is still trying to make a custom rom for this awesome device.
    I'm a YT3-X90L owner and is really frustrating not to be able to upgrade the device to a new Android version.

    I've not the right skill, but please guys don't stop trying!

    @sangotrunks : i've not understood if you have managed to install a newer android version.
    Thank you!!!

    Alessandro
     

    CENTSOARER

    Senior Member
  • Apr 22, 2013
    818
    478
    Mexico City
    As if Lenovo's support couldn't be worse... it is.
    So, I shared a cooked ROM a year ago and wasn't really great for others. When you flash it you can't get past the setup wizard. The problem is this tablet's firmware comes with a protection mechanism against stolen devices, something called Factory Reset Protection Lock (FRP). This means you can't completely factory reset your device unless Google allows you to or whatever...
    To remove this mechanism you can erase the config partition using fastboot, and then format it again into an ext4 partition, because a mountable config partition is required to boot. You need to input these commands in fastboot mode to erase the FRP:

    Code:
    fastboot erase config
    
    fastboot format config

    Then you can flash the cooked ROM as any other ROM, i.e. install the zip file using a compatible TWRP (don't forget to wipe data, boot, system, cache, Dalvik/ART partitions first). The ROM is minimal, based in the latest MM stock ROM, has Magisk (root), better RAM management, it is reasonably debloated and has the signature spoofing patch (to use with MicroG) that you can activate at the bottom of developer options, also includes adb root and USB debugabble by default. The kernel is not secured so it can be rooted with SuperSU if you want to. I included Lawnchair (Fdroid) as default launcher app and a recent version of the Bromite browser (a degoogled Chromium) with the mandatory apps from Lenovo for the device to work.

    This cooked ROM is great if you are thinking about just wiping your tablet for any reason, I mean, why not give it a try? Most of the configurations that can make a difference in performance are already implemented.

    This was tested and created for the X90F model (2 GB RAM 32 GB ROM, wifi) but, in theory, if you modify two lines in build.prop (ro.radio.noril and ro.lenovo.tablet) following the instructions provided in the same file, it can work on a X90L (4GB RAM, 3G data), but I don't know about RAM management on those.

    REQUIREMENTS:
    1) Unlocked bootloader
    2) TWRP recovery
    3*) Unencrypted and formatted data partition (Wipe > Format data partition > "yes")
    * This could be done by other unencrypting methods or simply by flashing the ROM and, after installation, Wipe > Format data partition > "yes", reboot. Needs testing.

    KNOWN ISSUES:
    1) Expect one "random" reboot after first boot, it is normal.
    2) Don't upgrade Magisk to v22 yet. Magisk Manager won't work properly in some devices running Android 6.x. Stay with v21.4 for now.

    PSA: ALWAYS HAVE A WORKING BACKUP! IF YOU DON'T GET WHAT I WROTE, THAT WAS INTENDED. YOU SHOULDN'T BE MESSING WITH YOUR DEVICE YET.


    The link for the updated cooked ROM is: https://centsoarer.ddns.net/s/Y8o3eoBK4Ryx5RP. Feel free to mirror, unless you are afraid of Lenovo's lawyers, but don't forget to share the link. With updated GAPPS: https://centsoarer.ddns.net/s/FPKjgQcmW3CHZCw

    My personal version... even more debloated (if you don't need chinese, japanese, korean, or russian support) and with CPU tweaks for my own usage: https://centsoarer.ddns.net/s/jcCDAgNedryGRjo

    EDIT: Can someone like this post to give it some visibility? I can't like it myself -_-

    EDIT 2: Newer versions and a GAPPS updated one.

    EDIT 3: These Cooked ROMS will break SmartSide Bar which is one of the few features I like about the stock experience. I am gonna try to find out why. My guess is it works only if the default Launcher is installed it breaks with the Signature Spoofing patches, but If you use this SmartSide Bar then the Updated GApps version may still work with SmartSide Bar, since it lacks the Signature Spoofing patches, and it only includes changes in the init system other than the updates. If this Gapps Updated version work with SmartSide Bar, please report back, since I am not using that version and I am done for the moment with the tablet and the hacking here.

    RECOMMENDATION: If you get FCs with heavy apps, try to edit the build.prop with vm.heapsize=256m. Maybe I will update the links to a more stable ones in the next days/weeks. IDK.
     
    Last edited:

    guillaumeg

    Member
    May 13, 2015
    10
    0
    Thanks for the post, nice to see that this device is not dead anymore.
    I tried your unbloated rom kind of half a year ago, and it works quite well for me. The only thing I could have to say is that some app crashes a some point, but I don’t know the reasons, and maybe some bluetooth audio distortion, but I did not tried to search much about it, might not be from your rom at all. I Use this at a daily basis, and I am pretty happy with it. with the 4gb 64gb version

    I will try the the one you mentionned before, but what do you mean no japanese support? (is it for the system language or the keyboard input/browsing fonts?)

    Thanks for your work @CENTSOARER , I just hope one day we could have an android update, but i think that’s almost impossible as long as the driver are not supported by the kernel...

    By the way I tried to boot Linux on it, I achieved to access the BIOS and boot Ubuntu 20.04, but no touch support during the live USB boot.
    I am quite afraid to wiping everything to install linux and not being able to coming back to android, even if I could find some encouraging way to reset it from Joesnose (https://forum.xda-developers.com/t/yoga-tab-3-pro-debrick-method-instructions.3776951/)
    If some of you have tried it we can share experience maybe.
    I might try JingOS and Manjaro in near future, at least for live USB booting for now.
    I am also wondering how the projector was connected to the system, as long as I have seen I could not see it in xrandr, and did not know how to find such a thing in lshw
     

    CENTSOARER

    Senior Member
  • Apr 22, 2013
    818
    478
    Mexico City
    I will try the the one you mentionned before, but what do you mean no japanese support? (is it for the system language or the keyboard input/browsing fonts?)

    Thanks for your work @CENTSOARER , I just hope one day we could have an android update, but i think that’s almost impossible as long as the driver are not supported by the kernel...

    By the way I tried to boot Linux on it, I achieved to access the BIOS and boot Ubuntu 20.04, but no touch support during the live USB boot.
    I am quite afraid to wiping everything to install linux and not being able to coming back to android, even if I could find some encouraging way to reset it from Joesnose (https://forum.xda-developers.com/t/yoga-tab-3-pro-debrick-method-instructions.3776951/)
    If some of you have tried it we can share experience maybe.
    I might try JingOS and Manjaro in near future, at least for live USB booting for now.
    I am also wondering how the projector was connected to the system, as long as I have seen I could not see it in xrandr, and did not know how to find such a thing in lshw
    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:
    ... Kernel 5.6.6 brought more frequent freezes and reboots than previous kernels. Until 5.7 is released the 5.3.7 works well, the worst issue encountered so far is the random inability to power on after a suspend)
     
    Last edited:

    jukbee

    Member
    Aug 4, 2008
    40
    7
    • Like
    Reactions: CENTSOARER

    drduranduran

    Member
    Aug 14, 2008
    14
    2
    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.
     

    CENTSOARER

    Senior Member
  • Apr 22, 2013
    818
    478
    Mexico City
    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.
    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.

    By the way I tried to boot Linux on it, I achieved to access the BIOS and boot Ubuntu 20.04, but no touch support during the live USB boot.
    I am quite afraid to wiping everything to install linux and not being able to coming back to android.

    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.
     

    guillaumeg

    Member
    May 13, 2015
    10
    0
    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://forum.xda-developers.com/t/...request-for-help.3839412/page-3#post-84317193
    https://forum.xda-developers.com/t/dualboot-android-linux-for-yoga-tab-2-830f.3955357/
     
    Last edited:

    guillaumeg

    Member
    May 13, 2015
    10
    0
    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.
    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.
     

    CENTSOARER

    Senior Member
  • Apr 22, 2013
    818
    478
    Mexico City
    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://forum.xda-developers.com/t/...request-for-help.3839412/page-3#post-84317193
    https://forum.xda-developers.com/t/dualboot-android-linux-for-yoga-tab-2-830f.3955357/
    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.
     
    Last edited:

    guillaumeg

    Member
    May 13, 2015
    10
    0
    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.
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 1
      [/QUOTE]
      The link for the updated cooked ROM is: https://centsoarer.ddns.net/s/DgaQCGSZ9rWBLgp. Feel free to mirror, unless you are afraid of Lenovo's lawyers, but don't forget to share the link.

      My personal version... even more debloated (if you don't need chinese, japanese, korean, or russian support) and with CPU tweaks for my own usage: https://centsoarer.ddns.net/s/b4mArz4GZ9tH5bH

      Sorry but both links aren't working...
      1
      Hey, thank you! They should be fine now.
      Links are dead again. Anyway i tried the first ROM. GREAT WORK! Now my tablet works fine , like never before. Thnk you very much.
      1
      Sorry but both links aren't working...

      Links are dead again. Anyway i tried the first ROM. GREAT WORK! Now my tablet works fine , like never before. Thnk you very much.
      Bad timing for me... but thank you. It should be working now, again.
      1
      Just letting you know that the cooked ROM links (both of them) are already dead again ;(
      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.
      1
      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.
    • 8
      NEWS SECTION STARTS HERE
      APRIL 9, 2021: You can find in these links a new version of the cooked ROM.
      The link for the updated cooked ROM is: https://centsoarer.ddns.net/s/Y8o3eoBK4Ryx5RP. This is a version with GAPPS updated: https://centsoarer.ddns.net/s/FPKjgQcmW3CHZCw. Feel free to mirror, unless you are afraid of Lenovo's lawyers, but don't forget to share the link.

      My personal version... even more debloated (if you don't need chinese, japanese, korean, or russian input support/apps) and with CPU tweaks for my own usage: https://centsoarer.ddns.net/s/jcCDAgNedryGRjo

      KNOWN ISSUES AND SOLUTIONS:
      1) One random reboot after the first boot will happen and it is normal.
      2) I'd reccommend to stay with Magisk 21.4 for a while, Magisk Manager >21.4 won't manage your extensions.
      3) If you can't get past the initial Setup Wizard check post 46. Basically you have to boot into bootloader, erase the config partition and format it again.
      4) Needs confirmation, but versions with signature spoofing patches seem to break Lenovo's SmartSide Bar.


      JUNE 12: Fast update on the Cooked ROM and TWRP and KERNEL. They are not as universal as I implied before. Proceed carefully since they may not work four your device/firmware. Make a Nandroid backup and only flash with testing purposes.

      JUNE 5: So, I know this is not what everybody who owns this tablet wants to have (that is Android 9 or 10 of course) but, in recent weeks Lenovo updated the firmware of this tablets. It still is a Marshmallow one and it still sucks big time but I took it as a base and cooked it to deliver a newer TWRP recovery with compression, a flashable modified kernel and a cooked flashable stock ROM to free the owners of this tablets from the treacherous path of making this hardware to work properly. If you want a better overall experience and are in stock firmware you just need to Unlock your bootloader, flash TWRP, Format data partition (not only wipe), Wipe Cache, Dalvik/ART, System and DATA and flash the Cooked ROM to put this tablet in a sweeter spot. For details go to post #2!

      JUNE 3: Been trying to get to know some of the source code available for Cherry Trail devices and I am fairly lost at building TWRP from source. Anyway, I ported a newer TWRP recovery IMG file for the YT3-X90F (maybe L, X, Y and Z) from the TWRP image for the Chuwi Hi10 Pro tablet from here, using AIK-Linux. The result is in the second post labeled as beta, since I only tested in the YT3-X90F model, running lollipop firmware. So far, it works fine flashing ZIP archives, backing up and restoring backups. Advantages? Well, backups are way lighter if you enable compression (like half the size), higher resolution, twrp turns off the screen with a timeout and whatever made them bump from version 2 to 3. While I could port a newer TWRP version, I just wanted to have lighter backups with compression... so maybe it is what it is :eek:.

      ORIGINAL POST STARTS HERE
      (This is a lenghty post. I suggest you to navigate by section header and find the one you might need.)

      There are several Lenovo Yoga 3 tablet models out there and, while some of them enjoy of prime community support as the Yoga Tab 3 Plus, this Intel Atom powered tablet is pretty much forgotten and, at the same time, users were recently buying this tablet, which is a great piece of hardware but has the most terrible support by Lenovo.

      WHAT LENOVO TABLET(S) IS THIS GUIDE FOR?
      Basically, this is that Lenovo tablet with an attached projector and an Intel Atom Cherry Trail x5 Z8500. There are several models, though, to my knowledge they vary in their code names in the last letter, the two most basic ones (2GB RAM, 32 GB ROM) are the YT3-X90F and the YT3-X90L, the former connects to the internet by WiFi and the latter being the one with LTE/Phone capabilities. There are other models, though, and they vary on the amount of RAM and internal storage. Apparently, the YT3-X90[YX] models (the 4/64 GB refresh) have some use for these firmwares we describe, but in a very specific way, if you own a Y or X model, keep reading, especially the next section.

      FIRST OF ALL. STOCK FIRMWARE.
      Lenovo support has been terrible (there are no words to describe it, really), so they launched this tablet with Android 5.1 Lollipop and they maintained it for a while but were very slow to deliver Android 6.0 Marshmallow. In fact, there was already Android Nougat, when they launched send the Marshmallow update. Nevertheless, the update was bad. Performance issues were always a thing and some functionality went lost in the update (less intuitive multiple windows, a crippled recents activity/screen, and a laggy overall experience). Bottom line, they launched a curated Android Lollipop 5.1 firmware with security updates until March 2016 (striked because the last lollipop update f*cks up my sensors, except the light one) and a half-assed Android Marshmallow 6.0.1 firmware.

      Of course, at the time, I'm guessing most of us upgraded to Android Marshmallow 6.0.1, hoping the upgrade would fix the issues in Lollipop or with security patches in mind. The reality was that Android 6.0.1 wasn't nearly as maintained as 5.1 and security ambitions went nowhere. So, we got the upgrade all right, but at this point, both Android versions can be considered inherently insecure and we really shouldn't be using it for sensitive work.

      OK, there are several Android 5.1 and 6.0 firmwares, you can recognize them because they are all over the internet typically in a compressed format. For example, this firmware hosted in androidhost.ru named:
      YT3-X90F_ENG_S100265_1601281130_WW24_ROW
      Is a firmware for the Lenovo Yoga Tab 3 (YT3) Pro (X90) Wifi Version (F). The ENG part is an indication of the build type, ENG is an engineer build while USR is probably a firmware for the end user (this is common now that I know a bit more about AOSP source code), it is a Lollipop firmware (S1, Marshmallow would be a S2) with update version (00265), date of compilation and a good estimate of its security patch (1601281130), the WW24 is the weekly release version of the Android kernel for Intel devices (the latest, in May 2020, being WW31 which is exactly the same as WW28 and not updated since 2016), the final part means it is the global ROM version (ROW, opossed to the Chinese version CN). This is the latest Lollipop firmware I am aware of, so, as an example, an imaginary Android Marshmallow Chinese firmware for the LTE version of the Yoga Tab 3 would look like:
      YT3-X90L_USR_S200013_1610141535_WW24_CN
      As an additional note the Chinese ROMS, I presume, are not trusty but they are also Google-free for what it's worth. On the other hand, they ship with a "Lenovo Services Framework" that should be as intrusive as the Google Play Services. Oh, also, baidu and yandex, and, really, any less traditional search engine can help you find a fitting firmware.

      HOW TO FLASH A STOCK FIRMWARE (YOU CAN DOWNGRADE AND UNBRICK TOO)
      I did test several firmwares, chinese and global, lollipop and marshmallow and the safest and easiest way to flash them is by using the Intel Platform Flash Tool Lite . I can't say I trust in this site, but it hosts a handy tutorial on how to use it, though, is pretty intuitive. The software exists for Mac, Windows and Linux, be sure you are in, at least, the 5.8.x version, this is important to avoid the need to install some special drivers separately as a pre-requisite. Grossly, Intel Flash Tool Lite works like this:

      0) Turn off your tablet if it is on.
      1) Launch Intel Platform Flash Tool Lite.
      2) If your downloaded firmware is in zip format load it with the blue "Browse..." button.
      2 bis) OR, if your firmware is in other compressed formats, uncompress it first. After this use the "Browse..." button to load the "flash.json" file.
      3) In Configuration option select "blank" if it isn't set already. Optionally, un-tick the "On-demand flash" option to have more control of this process. Also, maybe you can use the "erase" configuration here.
      4) Start your tablet in DNX mode. To do this, press Vol- and hold it, then Vol+ and keep holding both, then press the Power button until it turns on and you see the Lenovo logo and some text indicating you are in said mode.
      5) Connect your Yoga Tablet with a USB cable and your Intel Platform Flash Tool Lite windows should show it as detected. Now you can proceed using the blue "Start to flash" button.
      6) Keep an eye on your tablet, since some firmwares will prompt to set some more options. Unless you know what you are doing, answer "Yes" to any question.
      7) Reboot and wait.

      If a couple hours have passed and the tablet hasn't booted, maybe you should try another firmware.

      IMPORTANT NOTE AND INSTRUCTIONS FOR YT3-X90Y AND POTENTIALLY YT3-X90X USERS: I don't know the rules in xda about linking to other forums but in certain forum there is an answered question about the Y model (the 4/64 GB WiFi only refresh) on how to flash a firmware. Instructions are the same as I gave in this section, except, apparently, you need to do it twice, first with the ENG version and the second time with the USR version except you are not using the flash.json file, this time you'll browse for the flash_factory_1st_stage.json one and the factory1st configuration in fastboot. It is not clear what are the consequences of not doing it this way or what if you combine different firmware versions (it would be interesting to have a tester here). Notice please, these firmwares are marked for the YT3-X90F model. So, clarifying:
      1) Follow the instructions above to flash the YT3-X90F_ENG firmware.
      2) Power off your tablet.
      3) Boot into bootloader (not in DNX, you need to boot into bootloader by powering on while holding Vol+).
      4) From the YT3-X90F_USR firmware folder use Intel Platform Flashing Tool Lite to load the flash_factory_1st_stage.json and select the factory1st configuration.
      5) After flashing the USR firmware, reboot and you should be good to go.

      METANOTE: This wasn't tested by me, please do this only when you are hopeless with your hardware. This is just an educated guess but I bet it works the same with the YT3-X90L (the LTE version 2/32 GB Yoga Tab 3 Pro) and the YT3-X90X (the 4/64 GB refresh).

      ALTERNATIVE WAY TO FLASH A STOCK FIRMWARE (ADVANCED USERS, requires fastboot)
      Well, there is no need, really, to use that Intel tool. In my search for a lollipop firmware (I wanted to downgrade from Marshmallow) I found the firmware YT3-X90F_USR_S100195_1512052308_WW24_ROW in www.firmware247.com or www.androidfilehost.com (IMPORTANT: please read the note on downgrading to Android 5.1 Lollipop in the note at the end of this section). This firmware was special since, if you are in Windows and have fastboot executable ready and in place, you can run a script (run_me.bat) in the Windows terminal (CMD) or Powershell to flash the firmware semi-automatically. I think this firmware was modified, though, since I found differences in the boot.img when compared with stock firmwares. This script is credited to XDA members @ionioni and @joesnose and you can replicate its steps if you:

      0) Turn off your tablet if it is on.
      1) Start your tablet in DNX mode. To do this, press Vol- and hold it, then Vol+ and keep holding both, then press the Power button until it turns on and you see the Lenovo logo and some text indicating you are in said mode.
      2) Connect your tablet to your fastboot enabled PC using a USB cable.
      3) Input "fastboot flash osloader loader.efi"
      4) Wait 5 seconds to be sure the loader flash finishes.
      5) Reboot into Bootloader. If you don't know how, one way is to hold Vol+ and Power on your tablet.
      6) Input "fastboot oem unlock" and confirm using Vol keys to select the right option and the Power button to enter it.
      7) Input "fastboot flash system system.img"
      8) Input "fastboot flash boot boot.img"
      9) Input "fastboot flash recovery recovery.img"
      10) Input "fastboot flash bootloader bootloader.img"

      Follow your instincts, since I don't know if these IMG files are always named the same. You can get these IMG files from downloaded sources or dump them yourself using dd command.

      NOTE ON DOWNGRADING TO ANDROID LOLLIPOP 5.1: So, one of my main concerns has been to go back to Android Lollipop. There is a last version of Lollipop from where you can upgrade to Marshmallow with a security patch from March 2016. Nevertheless, you MAY end up loosing other sensors except the light one. If this happens, you need to use a complete firmware flash using Intel Platform Flash Tool Lite. In my experience, some boot images are not compatible with other weird partitions like country or misc.


      SO, STOCK FIRMWARE, EVERYTHING SHOULD GO SMOOTH, RIGHT?

      Well... no.

      The first boot takes some time even amounting for the time of the setup itself. By the time you are in the launcher tapping on app's icons you think there's nothing wrong with our device, but after some apps are in memory, you notice some lag. You think "OK, it is updating, but soon it'll settle", but it does not. So, you reboot again after updates and fire up a terminal emulator and connect to your tablet using a USB cable with USB debugging turned on and issue a free command to find something like this:

      Code:
                    total         used         free       shared      buffers
        Mem:      1950372      1820964       129408            0         7756
      Swap:       524284        10740       513544
      Total:      2474656      1831704       642952

      Which means you have a total of ~2.5 GB (this is the 2 GB model). So, did I download that extra half GB of RAM or Lenovo was feeling generous? Well, no. The issue here is Lenovo built the kernel with zRAM support which is a technology included in Linux that reserves space in RAM to quickly compress and uncompress pages of data exceeding our physical amount of RAM installed (2 GB). This is not Virtual Memory as in a swap file/partition or Windows' Page File inside storage media. zRAM literally reserves a fixed amount of physical RAM space (blocks) to expand it by compressing data. The consequence is you loose "fast RAM" (THE RAM) and gain some "slow RAM" (the zRAM). You also sacrifice some CPU power to compress/decompress data and, with this, some battery juice is also lost.

      That does not sound like a terrible trade-off for a RAM-limited device, one would think. Another interesting thing would be WHEN to send this piling data in "fast RAM" to the compressed space and WHEN to get it back. Two parameters control the WHENS, one is called "swappiness" (when to send it to the compressed space, the "slow RAM") and the other may be the "vfs_cache_pressure" (when to uncompress it and send it back to the "fast RAM"). And this is where the main problem is, really, because the kernel, Linux, is pressing the RAM constantly to send some less prioritary data to "slow RAM" and, at the same time, is trying constantly to send compressed data back to the "fast RAM". Summarizing, this kernel behavior is practically minimizing the fast RAM amount and usage while maximizing the "slow RAM" usage. This is nuts, by default a swappiness and a vfs_cache_pressure of 100 are not even default for servers, these parameters extremely prioritize that processes can get done no matter how slow they get, and they are even more nuts when Android is designed to work without swap space.

      What that free command is telling us is the tablet is using the "slow RAM" even when we only just turned it on. Fortunately there are two ways to fix this problem: one is to completely disable zRAM, the other one is to use ZRAM a whole lot less by tweaking the swappiness and vfs_cache_pressure parameters. This can be easily done with the following sentences in a rooted tablet:

      Code:
      # echo 5 > /proc/sys/vm/swappiness
      # echo 50 > echo 5 > /proc/sys/vm/vfs_cache_pressure

      Or, to regain the whole fast RAM:

      Code:
      # swapoff /dev/block/zram*

      One caveat of the first method, reducing swappiness, is there is still a lot of RAM (one quarter of the whole RAM in a 2 GB device) reserved as "slow RAM".


      SOME ROMS DID NOT ENABLE KERNEL SAMEPAGE MERGING, UNFORTUNATELY

      Additional to the sorry implementation of zRAM, some firmwares support a fabulous Linux tool to reduce RAM usage called Kernel Samepage Merging (KSM) but they don't use it by default. This software runs at kernel level, so, it really is CPU-wise inexpensive and, opposite to zRAM it can actually recover some RAM usage by reducing the amount of data flagged as redundant in physical RAM by merging it. KSM is good for you and you should have it always enabled by issuing the following command as root:

      Code:
      # echo 1 > /sys/kernel/mm/ksm/run


      STOP WRITING AND FIX MY RAM! PLEASE!

      Well... are there any people interested on this? With the above information you can write a script to execute at boot. Something like this should work in any version of the firmware:

      Code:
      #!/system/bin/sh
      
      # Mount system as rw
      busybox mount -o remount,rw -t auto /system
      
      # Tweaking swappiness in zram
      echo "5" > /proc/sys/vm/swappiness
      echo "50" > /proc/sys/vm/vfs_cache_pressure
      
      # Activating Kernel Samepage Merging
      echo 1 > /sys/kernel/mm/ksm/run
      
      # Remount system as ro. noatime option for faster and volatile system
      # busybox mount -o ro,remount,noatime /system
      busybox mount -o ro,remount /system
      
      exit 1

      Or, you can unpack the boot.img and modify the init.cht_ffd.rc (lollipop) or the init.r2_cht_ffd.rc (marshmallow) files to write these values as default... or, if there is interest for something easier, I can produce this boot.img files for you to flash using fastboot.


      ROOTING THE LENOVO YOGA TAB 3 PRO (YT3-X90[FL])

      Here I am not gonna write a lot. Instructions were given in this thread. I'd only recommend following the first two posts' instructions to unencrypt the data partition and root, you can always encrypt it again for security reasons but encryption shouldn't be a performance issue if you fixed the zRAM behavior with these modifications. The only note I can give you is you only need the twrp recovery build in the second post (the one with data partition support), as far as I can tell, there is no need to flash the one in the first post.

      After rooting, debloat your firmware. I use the app "/system/app mover" from Fdroid to convert to user apps and uninstall them. Also, if rooting is not your cup of tea, you can install AppOps software to freeze all those apps that you don't use regularly. Also, I couldn't patch my services.jar for Signature Spoofing with Nanodroid patcher in the most recent lollipop firmware, but it did work in Marshmallow... anyway I'll do it manually.

      ARE YT3-X90F AND YT3-X90L FIRMWARES INTERCHANGEABLE?
      I own a WiFi only device (YT3-X90F) so I can't assert they are interchangeable. If I owned the LTE version and use a WiFi firmware I would expect to loose LTE functionality. Now, on the other direction is more interesting because I've been using a LTE firmware version for weeks (as a matter of fact, the one joesnose linked in his How-To debrick this tablet, flashed with the instructions I posted for advanced users it even updated to recent 2020 firmwares). The only tweak you need for this to work well is to add "ro.ril.disable=1" in the build.prop file. So, yes, firmware for the LTE version work in the WiFi version but kind of not vice versa.

      YT3-X90[FL] DEVELOPMENT

      No news here. All capable people interested on developing for this device are all done with Lenovo and their attitude against Open Source. Don't expect your situation to change.
      I'm happy to know there are still a couple of developers interested on this device. I won't cite them by linking their names but they are OOEvil and alquez, the first guy is trying to make a Generic System Image (GSI) ROM compatible with our tablet, I don't know the details so I wouldn't go further. Alquez has been active in this thread and, while he is trying to figure out how to build a kernel, he believes the best way to start having some alternative to official Lenovo firmware is by using a firmware kernel (a prebuilt kernel) to, first, build a more up-to-date TWRP recovery.img and from there try to build CyanogenMod 13, which was based on Android Marshmallow 6.0.1. My guess is newer Android versions wouldn't work if we can't build the kernel from source.

      PHOTO ALBUM OF YT3/X90Y BIOS
      This photo album documenting every screen option in the BIOS of the Yoga Tab 3 Pro may or may not help someone, but it contains a lot of useful hardware information and guidance for those attempting to boot something else than the original Android 5 or 6 firmware. Using this options, that are accessible through F2 at boot with an attached USB keyboard, you could try Linux distributions on the tablet or even attempt to run Windows, @alquez informs it works fine with a recent distro but the mainline kernel is lacking touchscreen and battery support. This is absolutely his work and he asked me to share it. I hope it serves someone. It is hosted in a rather obscure website but it was the only reasonable placeholder I could find for the 321 photos.

      Hope this helps someone, I just didn't want to keep it to myself. Have a nice day!
      2
      If you are looking for the cooked ROM go to post 46.

      Just remember, if your tablet is 3G capable I strongly suggest that you modify the line "ro.lenovo.tablet=wifi" to "ro.lenovo.tablet=3gdata" and remove the line "ro.radio.noril=true" to your build.prop file in /system. To do this you can use the section Build.prop Editor of the Kernel Adiutor app or you can do it manually if you have already a method to modify system files. If you do not use mobile data at all, you may leave the build.prop as it is, you'll save a lot of battery by using only wifi.

      ONLY FOR TESTING: Cooked ROM, newer TWRP and tweaked kernel

      ONLY TRY THESE FOR TESTING PURPOSES, THE TWEAKS ARE ALL SAFE TO USE BUT ONLY FLASH FOR TESTING PURPOSES, PLEASE. FIRST, TRY TO USE FASTBOOT TO BOOT THE boot.img FILE WITHOUT FLASHING: IF IT BOOTS GO AHEAD AND TRY THE OTHER FILES (fastboot boot boot.img). THE TWRP IS NOT AS STABLE AS THE OTHER ONE HERE AT XDA BUT ALLOWS TO USE ZIP COMPRESSION IN BACKUPS. I AM NOT GONNA BE AROUND. IF YOU TRY SOMETHING MAKE A BACKUP FIRST. THIS DEVICE IS MESSY AS F*CK.
      I wrote a very detailed guide about these files I uploaded to my Nextcloud that include the newer TWRP-3.0.2, a TWRP flashable Cooked ROM and a separate kernel (boot.img) in case your system is already setup, but the post went to some XDA void and didn't upload. These are based on the YT3-X90L latest firmware, but they work on the X90F model too. The TWRP should work with Lollipop and Marshmallow firmwares.

      I can't write everything again, so, the kernel contains better management of RAM and emmc (internal) memory, a 256 MB zRAM space instead of 512 and a more conservative approach to LowMemoryKiller.

      The cooked ROM includes the described kernel and debloated apps, it's already rooted with Magisk (you can unroot with Magisk Uninstaller), an updated Busybox build, su.d support (I plan to use it with AFWall+), zipaligned apps, etc. It is for the X90L but possibly works for the other Yoga Tab 3 Pro models. It works for the X90F but it will reboot once after the first boot because the RIL configuration times out. To install the cooked ROM you need to:

      0) Know that by doing this you will loose pretty much everything in your tablet. You start from scratch if everything goes smooth, if not you could possibly end up with a system without an OS. The usual stuff when you are customizing your system.
      1) Boot into TWRP and make a Nandroid backup. IT IS IMPORTANT because @joesnose had problems with a "random reboot" and lost Bluetooth/WiFi after it. I am trying to look into this. The only difference is his tablet has 4 GB RAM and probably a different firmware.
      2) Wipe cache, Dalvik/ART, System and Data in TWRP - Wipe, Advanced Wipe menu. If your tablet is encrypted, or in factory firmware you also need to explicitly use the button "Format Data partition" and confirm writing "yes" in the format procedure prompt. You will loose any configuration made to your tablet.
      3) Install the superr_stockMM.zip wich is flashable by selecting the file from your Internal tablet memory, using the Install button in the main TWRP interface.

      FOUR IMPORTANT NOTES TO COMMON ISSUES:
      If you come from a stock firmware your data partition is encrypted. You need to pass a blank password in TWRP to continue to use the custom recovery. You also need to format data partition before flashing the cooked ROM.

      If your tablet is WiFi-only I strongly suggest that you modify the line "ro.lenovo.tablet=3gdata" to "ro.lenovo.tablet=wifi" and add the line "ro.radio.noril=true" to your build.prop file in /system. To do this you can use the section Build.prop Editor of the Kernel Adiutor app or you can do it manually if you have already a method to modify system files. In Lollipop firmware you use "ro.ril.disable=1" instead of "ro.radio.noril=true" to get the same effect: sort of a conversion to WIFI-only tablet from LTE models. I'd argue this is useful to do if you are gonna be without LTE connection/service for long periods of time and I can think a couple of other uses.

      Do not use stock Lenovo launcher unless you uninstall Magisk... they are incompatible for reasons I don't care to know and the Launcher will constantly FC (it is a pain in the arse).

      If you are still expecting better performance I am sure there are some tweaks left in RAM management but it wont go too much further in 2 GB devices. Instead, you may consider to lower your display resolution and pixel density to something reasonable as 1400x2240 or even 1200x1920 maintaining the same aspect ratio. To do this you do not need to have root but you need to interact with the tablet using ADB. First change the size of your display:
      Code:
      adb shell wm size 1400x2240

      Then adjust your density:
      Code:
      adb shell wm density 260

      If still is not enough you can go even further with 1200x1920 and 224, use the same method to go back to stock with 1600x2560 and 300 to 302. This won't need a reboot but will probably cause an inconsistent UI that will lead to FCs and random reboot. You can just reboot after applying these tweaks. Unless you are really sight-gifted you won't notice a lot has changed but you will be dealing with 2.x Mpixels instead of 4.x Mpixels and that will help with your overall performance as well as your battery life sacrificing a pixel count that most of the people wouldn't even notice. If you did this correctly, in the next boot sequences you'll notice an offset on the Lenovo orange logo.

      It is important to say that your display supports 1600x2560 pixels physically, but I'm assuming the GPU has no dedicated RAM and uses the device's, so, by reducing the quantity of pixels the GPU needs to deal with, the pressure on the device's RAM is also reduced.

      EXTRA TIP: If boot annoys you just delete /system/media/boot.wav, bootanimation.zip and shutdownanimation.zip and you'll get a silent boot and the generic android boot animation.

      Hope you enjoy your tablet!

      TWRP-3.0.2.0- BETA: Again, this is not a flashable zip. Uncompress first and test the recovery system using "fastboot boot twrp_yt3-x90f_beta.img". If everything works for you, you may want to flash it permanently rebooting to bootloader and flashing with "fastboot flash recovery twrp_yt3-x90f_beta.img". Remember I did not test this in Marshmallow yet.

      FEATURES:
      - Fixed RAM issues (swapiness 10, vfs_cache_size 50 and disabled dynamic low memory killer tweaks and minfree values).
      - Reduced zRAM size to only 256 MB.
      - Tweaked interactive CPU scheduler to use other than min and max frequencies (but still responsive). The tweaks are based on the Advanced Interactive Governor Tweaks Guide. This may save battery life.
      - Max frequency capped to 2.08 GHz (this is not great if you are a gamer). This tablet throttles when using max frequency for a long time, so, to save battery and keep it cooler I tweaked the CPU to run slower.
      - Tweaked I/O schedulers to use deadline governor and read ahead cache to 640 kb (used benchmarks to get to this value).
      - Force encryption disabled (to avoid applying ionioni script after flashing). Still needs to format data partition. You can encrypt your data partition later through Configuration -> Security user interface.
      - Implemented native init.d support (not su.d anymore and no need to root the main OS).
      - Busybox updated.
      - Rooted with Magisk by default ( you can use Magisk uninstaller to unroot).
      - Debloated apps. I also deleted Lenovo User Experience Program which was asking for root privileges even when you don't opt in to the Lenovo UE Program at setup wizard. I find this behavior shady.
      -Multi-window mode is available in Developer Options and needs to be activated by you. In this mode if an app is compatible with multi-window mode you can double-tap on its title bar to enable Window mode. This function was more transparent in Lollipop firmware but it is still there in Marshmallow firmware if you change the build type to userdebug instead of user in build.prop (that's how I enabled it in the Cooked ROM).
      - There are also other tweaks in VM and KSM.

      And that's it, I'm not trying to change a lot, only the fundamental issues. But I suggest some other tweaks up there.
      1
      Thanks for the new feel.

      This is great, glad to see a developer picking up this tablet. It's a fine machine with an unfortunately small user base and has never really seen any development apart from ionioni s efforts and he didn't even own one, lol.

      Edit: *Thank for the new twrp * auto correct!
      1
      Thank a lot, gret work just getting my tablet charged so i can take your kernel for a spin, will probably go for rhe screen tweaks also. Nice work.

      Edit.

      Just to let you know i have F model with 4gb on mm.

      I tried the kernel you uploaded but had some issues, after first boot tablet shut down while i navigating round tablet system, no warning.This happened a couple of minutes after boot.

      Upon reboot i noticed there was no wifi or bluetooth.
      1
      EDIT 2: You could open the Cooked ROM zip, delete the boot.img in WinRAR and paste your own boot.img. That should work. And if it does, I can tweak your boot.img and put it in another version of the Cooked ROM.

      will give this a try.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone