Database Users

[ROM/ROOT/CWM] Sero 7 Pro (US) - dopa v2.0

** DoPa5 v1.0 (AOSP v5.0.2_r1 - Lollipop) is now available for US/UK/AU users **
If you would like to upgrade from the stock ROM, see this post for downloads and installation details
Click to expand...
Click to collapse
DoPa v2.0 is an enhanced version of the stock ROM that features a custom-built kernel. It is based on Hisense's August, 2013 update (build P756.6.02.20) and is intended for US (8gb) versions of this tablet. It does not support the 32gb models sold in the UK and Australia. See Post 2 below for packages to root this tablet and install CWM Touch recovery.
This ROM de-bloats the original, roots it using SuperSU, and adds several useful apps, among them: Apex Launcher and ES File Explorer. It also includes several Xposed Installer modules to tweak your system, including GravityBox and my Phab7 UI switcher. For the hackers amongst us, ADB always runs as root.
The kernel is built from Hisense's source and offers enhancements and bug fixes. Most notably, it provides USB-OTG support so you can connect USB storage devices (e.g. thumb-drives) to your tablet using an OTG cable. It comes in two flavors, a non-overclocked version included in the main package, and a separate overclocked version that can be installed (and uninstalled) independently.
Installation
Having CWM installed is a prerequisite; if you haven't installed it yet, see Post 2. This ROM is intended to function as an update, preserving your apps and data. Unless you want to start from scratch, do NOT wipe or clear anything - the install script will do what's needed.
copy the file(s) to your internal or external SD card
reboot into CWM, then select "install zip"
I recommend you select "toggle signature verification"; enabling this will confirm the file hasn't gotten corrupted (if you get a verification error, stop, then copy the file to a different SD card)
choose the menu entry corresponding to where you put the file(s), then select "sero7pro-bld60220-dopa-v2.0.zip" from the list
after confirming your selection, the update will display what it's doing; you should NOT see any error messages
if you'd like to install the overclocked kernel, you can do so once the main package is in place, or at some later time
reboot
Notes
when you attach a drive using the USB-OTG feature, it is automatically mounted at '/usbdisk'. Be aware there is no easy way to unmount it - you may have to use adb or a terminal app to ensure a clean unmount. This should only be an issue if you write to the disk; if you're only reading, it may be safe to just pull the plug.
the overclocked version of the kernel runs the processor at 1.5ghz rather than the standard 1.3ghz. Using it may result in a significant loss of stability on some systems. You may want to install one of the many apps that let you control the maximum speed to regain stability and reduce power consumption.
much of the app-bloat this ROM tries to eliminate (such as Sams Club or Playstore Magazines) may still be present if you've ever gotten updates for any of these apps. To get rid of them permanently, uninstall them using Settings->Apps->Downloaded. For "system" apps like the Google stuff, select "Uninstall updates", then "OK" when it asks if you want to revert to the factory-installed version (which doesn't exist anymore). The apps will be gone for good.
to enable the many tweaks offered by GravityBox and Phab7, open the Xposed Installer app and enable it via the "Framework" option but don't reboot yet. Back out and choose "Modules", then tap directly on the checkbox to the left of each module's icon (not on the icon or text). Now, reboot to activate their features.
Note: GravityBox's Quick Settings tiles and statusbar mods only work with the Phone or Phablet UIs (i.e. not Tablet UI). To get the full effect from Tablet UI, open Apex Launcher's settings and select "Homescreen settings->Use tablet UI mode"
Geek Alert: with the addition of DriveDroid (not included), this kernel lets your tablet emulate a USB CD drive that can be used to boot your PC. See the app's description for details.
Credits
xboxexpert - for getting things going
randomblame - for many of the patches used in this kernel
Files
new and improved:
sero7pro-bld60220-dopa-v2.0.zip - the DoPa v2.0 ROM with the standard kernel
sero7pro-boot-dopa0oc-v2.0.zip - the overclocked kernel
sero7pro-boot-dopa0-v2.0.zip - the standard kernel (in case you want to reinstall it)
old and tired: (do not use with v2.0)
sero7pro-bld60220-dopa-v1.1.zip - the DoPa v1.1 ROM
sero7pro-usbotg-dopa-v1.1.zip - USB-OTG add-on
sero7pro-macfix-dopa-v1.1.zip - random MAC address fix
sero7pro-sysui-dopa-v1.1.zip - removes screenshot button
miscellaneous:
sero7pro-bld60220-removed.zip - files that were removed from the DoPa ROMS (note: unlike the other files here, this is not a flashable zip. Unzip it, copy the apps you want to your SD card, then install them from there)
stock-v60220-full-update.zip - the complete 6.02.20 update from Hisense - this is the closest you'll get to the original stock ROM
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
XDA:DevDB Information
Sero 7 Pro (US) - DoPa v2.0 Modified Stock ROM, ROM for the Android General
Contributors
dolorespark
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
Based On: Stock ROM
Version Information
Status: No Longer Updated
Current Stable Version: 2.0
Stable Release Date: 2014-01-22
Created 2015-01-26
Last Updated 2015-01-27

Root/CWM packages
These packages will root and install CWM Touch recovery on the US (8gb) model of the Sero 7 Pro. There are separate versions for Windows and Linux. They have been tested under Win XP, Win 8, and Ubuntu, and should avoid problems encountered with other root/recovery packages.
The packages are modular so that you can run some or all of the functions as-needed. They consist of 4 scripts:
step0-DoItAll - displays some setup info then runs all 3 of the following
step1-adb - enables ADB ("Android Debug Bridge") to locate the tablet
step2-root - roots the tablet and installs the SuperSU app
step3-cwm - installs CWM Touch Recovery v6.0.3.2
Versions of ADB for each OS are included, so no other packages or downloads are needed. Usage should be fairly simple: unzip the package into a convenient directory, doubleclick on step0-DoItAll, then follow the (minimal) instructions. Alternately (and better), open a command prompt/bash shell, change to the directory where you unzipped everything, then run the script(s) from there.
Avoiding Frustration
If you haven't rooted an Android device before, please read the following because there are a few "gotcha"s. If you have but things aren't going as expected, review the following in case you missed/forgot something.
Developer options must be visible in the Settings app. If they aren't, select "About tablet", then tap on "Build number" 7 times. A small popup will tell you that you're now a developer. Back out to the list of settings categories - you should now see "Developer options".
USB debugging must be enabled under "Developer options". Please be sure it is. If it isn't, select it then tap OK when a warning popup appears.
Both Windows and Linux require extra files to be in place before ADB can communicate with your tablet. Click on the button for your OS to see the ugly details.
Windows
Windows requires USB drivers to be installed. Drivers that will work with the Sero7Pro (and possibly any Android device) are included in the package.
After enabling "USB debugging" and connecting your tablet, a wizard may pop up to guide you through the steps. If not, force it to appear by opening Device Manager. Look under "Other devices" where you should see something like "Android phone". Doubleclick on it, then select the "Install driver" button on the window that appears.
When the wizard pops up, tell it you'll select the drivers, then choose the option that tells it where to look. Click the "Browse" button and navigate to the directory where you unzipped the package. Select the usb_driver folder, press "OK", then "Next" - the drivers should install without any problems.
Notes: On Windows XP, the first wizard to pop up may want to install drivers for "MTP" which XP doesn't support. If so, cancel out of that, then wait for the "Andoid Phone" wizard to appear. On later versions of Windows, you may get a popup warning that the drivers aren't signed properly; if so, select "Install driver anyway". On Win 8-64bit, driver installation will fail unless you started the current session with "Driver signature enforcement" disabled.
Linux
Linux (or at least Ubuntu) doesn't allow user programs to access USB devices directly without the appropriate permissions in place. This package includes a file named 99-android.rules which provides those permissions
If you've never provided access to other USB devices, just copy the file to /etc/udev/rules.d. Otherwise, you can either copy it or merge its contents with the .rules file containing your other USB entries.
Note: both the rules.d directory and its contents are owned by root. You will probably have to use the sudo command to gain access. For example, from a bash shell whose current directory is the one where you unzipped the package, you'd enter "sudo cp 99-android.rules /etc/udev/rules.d". Also, be sure the file's permissions match the others in that directory. If not, run "chmod 644 /etc/udev/rules.d/99-android.rules".
Notes
When you're done, open the SuperSU app to enable it. It will ask to update the su binary. After selecting OK, the app will be enabled and will popup warnings whenever an app requests root access for the first time.
The Linux script is actually designed for both Linux and Mac OS X. However, I haven't fully tested it yet so I don't want to make any incorrect claims of support. You may have to correct some file permissions and will almost certainly have to run it from the Terminal app.
Files
sero7pro-root-win-dopa.zip - Windows
sero7pro-root-unix-dopa.zip - Linux

[Obsolete] Remove Screenshot Button / Add Instant UI Switcher
The mod originally described in this posting is now obsolete with the release of the DoPa v2.0 ROM which has both features built in.
If you are running an older version of that ROM, or XBoxExpert's ROM, or even the stock ROM, you can still remove the screenshot button using this CWM-installable package: sero7pro-sysui-dopa-v1.1.zip.
If you'd like to try Phab7, an on-the-fly UI switcher that lets you select Phone, Phablet, or Tablet UI modes, see this thread. Note: you must install the SystemUI mod to switch to Phone UI - without it, SystemUI will force-close when you do.

Good work. Hope to see more devs and more Roms

Really good. I'm using it right now. Keep going with the good work

Good Job! Looking forward to more posts!

Thanks for the nice work and good instructions. I'm using your stock ((build P756.6.02.20) rooted now and plan to try the ROM soon without Link2SD operational to keep all my apps.

Thanks again, I have updated my Sero to this ROM. Everything seems to be working perfectly. I look forward to many updates!

Thank you. Your ROM runs smooth and fast.

Great work man, downloading it now! Thanks!

Antutu result for this ROM
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!

Installed and working. Thanks.

taba4real said:
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Click to expand...
Click to collapse
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app

larryf said:
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Why am I getting 10500 on this ROM then?

Does this root and cwm change kernel like xbox's?

lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png

Cooter007 said:
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Click to expand...
Click to collapse
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.

lordroy said:
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
Click to expand...
Click to collapse
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My HomeScreen ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png

Cooter007 said:
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My desktop ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Click to expand...
Click to collapse
Of course as soon as I mention something, my Sero decides to play nice.
Just got a score of 13861. I didnt change anything, it just decided to score better for some reason.

lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Sir i used to get this with Power Saving mode instead of Perfromance priority mode....... =):good:

[TOOL]Playstore, No ADs, Launcher, BusyBox, Root and more! Noob friendly one-click

-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
WORKS ON 5.1.1 ALSO!
(Link in next reply)
Fully automated and noob friendly. :3
Done:
Root
BusyBox
Disable OTA
Change Launcher
Install full Google Play Functionality
Autoinstall flash player
build.prop optimizations
A few more features...
This may be compatible with other fires, but I have only tested it on the Fire 7" 5th generation.
This is a script I wrote in my spare time.
This script will optimize, root, install google play, and debloat your device.
Enjoy :3 Don't forget to hit thanks.
STEPS
1. In device options, tap on serial number until the developer options appear. If required (which it is likely not, but for some it is. DON'T DO THIS IF IT'S ALREADY WORKING.) install the ADB driver by going into the device manager of windows and rightclick update driver on your device under unkown devices, then point it to the driver folder included in this zip, or, you know, try the driver installer .exe included. Make sure driver signature enforcement is disabled in Windows!
2. Go into the developer options of android and enable Debugging
3. Go to the homescreen on the tablet, EXTRACT the zip on your computer, and run the script 1_ROOT_FIRE.bat in the zip on your computer.
This should only take around five minutes too complete.
YOUR DEVICE WILL REBOOT SEVERAL TIMES.
Easy enough, right? :3
Troubleshooting:
Unless you are running Fire OS 5 or higher, using this script probably won't get you playstore access, but it may root it. This was made primarily for the Amazon Fire 5th Generation 7" Tablet. (The "50 dollar tablet")
Don't run as root or admin.
If your device gets stuck in fastboot:
When the device reboots and goes into fastboot mode the drivers didn't recognise it. Leave the script running and go into Device Manager. Your Kindle will be listed as "Fire" with a yellow icon. Follow same steps to install drivers but instead of directing it to the "usb driver" folder contained in the zip file - select "let me pick from a list of drivers". Then pick adb interface then scroll to the bottom and select the last option.
The script hangs on adb daemon started:
If it hangs there, android debugging on your device isn't communicating with your computer. The fix can range from reconnecting your device, making sure android debugging is enabled in the Device> Developer options, making sure adb drivers are installed, or restarting the script.
Keep in mind, if you give this tablet to a non tech savvy user, open SuperSU, go to options, and click full unroot.
XDA:DevDB Information
AutoRootScript, Tool/Utility for the Amazon Fire
Contributors
glitch3yf0x, JaboJG, KennBr, k4y0z
Version Information
Status: Stable
Current Stable Version: 4.14
Created 2015-12-30
Last Updated 2016-04-08

Secondary Download Mirror
(Recommend) REGULAR VERSION:
https://www.androidfilehost.com/?fid=24352994023705981
NO DEBLOAT version:
https://www.androidfilehost.com/?fid=24391638059059079
Read the post below to choose the version right for you.

Version diffrences
Regular version: Choose this if you want the full android experience to your tablet with the added features of the script. This will remove all the unwanted Amazon bloatware that fills up the internal storage and will make your tablet feel more like an android tablet.
No debloat version: Choose this if you want to keep the Amazon experience with the added features of the script. This will leave Amazon's features and will make your tablet feel more like an Amazon tablet.
Notice: this script will not wipe or touch any of your files on the internal storage or sd card

Fully stable!
Great news! All bugs have been fixed! As of version 4.14 uploaded 1/5/16, all OS versions have been tested and are confirmed working properly. Enjoy!
If anything goes wrong, such as a USB cable being unplugged or the battery dying, pretty much anything can be fixed by booting into recovery and adb sideloading the latest firmware.bin from amazon.
Thanks for Donating:
Lorenzo
@BarbaraaK

So was the Mac OS X issues fixed?

pride0929 said:
So was the Mac OS X issues fixed?
Click to expand...
Click to collapse
I believe so [Old post. Issue fixed with 4.14, if there was one.]

I ran the script using OS X, everything seemed to go well. But the Fire is stuck booting at the "fire" logo.

Mac OS X
jmallow said:
I ran the script using OS X, everything seemed to go well. But the Fire is stuck booting at the "fire" logo.
Click to expand...
Click to collapse
Updated issue. [Issue fixed with 4.14, if there was one.]

glitch3yf0x said:
Give it 10 minutes before force rebooting. It may be rewriting cache. This is very odd. Any error messages on the computer?
Don't worry about your tablet. We can adb sideload if anything wen't wrong.
What OS is your tablet running? Is your tablet the Fire 7? It may be an issue with build.prop. I'm retesting it now using the Mac OS X source files. In the mean time, tell me if your Fire boots.
Click to expand...
Click to collapse
It's a 5th gen Fire 7 (the one that was released in Sept 2015). I side loaded to get back to factory, but mistakenly used the fire hd .bin file...and now it won't turn on at all. Lol. Might be a dead battery though I think, so its plugged in now. Will try again after a bit.

jmallow said:
It's a 5th gen Fire 7 (the one that was released in Sept 2015). I side loaded to get back to factory, but mistakenly used the fire hd .bin file...and now it won't turn on at all. Lol. Might be a dead battery though I think, so its plugged in now. Will try again after a bit.
Click to expand...
Click to collapse
Alright. Best of luck. I tested it on my fire again and there were no problems. If you have problems the second time tell me.

Any results?

glitch3yf0x said:
Any results?
Click to expand...
Click to collapse
I bricked it by installing the wrong version by mistake.
Hopefully Amazon warranty will replace it without question.

I've just run the script for my daughters fire 6 5th gen running 5.1.1 and all went smoothly. Has the look and feel of a great wee device now!
Thanks for your efforts ☺

Thread moved from http://forum.xda-developers.com/amazon-fire/general/root-fire-5th-gen-autoroot-script-noob-t3276923

Just installed this without a hitch. So far so good!! Thank you!!

Worked really well on 5.1.1 Thank you so much!
Now the only issue I have is that I want to use Google Now Launcher in place of Nova. Is there a way to do it?
EDIT: Never mind, it asked me which home to set after a reboot.

thehrushi said:
Worked really well on 5.1.1 Thank you so much!
Now the only issue I have is that I want to use Google Now Launcher in place of Nova. Is there a way to do it?
EDIT: Never mind, it asked me which home to set after a reboot.
Click to expand...
Click to collapse
I should post a poll. Google Now or Nova.

glitch3yf0x said:
I should post a poll. Google Now or Nova.
Click to expand...
Click to collapse
Just add a selector in the script and have it push the appropriate apk

BaT420 said:
Just add a selector in the script and have it push the appropriate apk
Click to expand...
Click to collapse
I was gonna suggest the same. Nova after rooting makes sense, since the widgets work. But I like Google Now on left swipe.

Yeahhh
Very good. Fire 7 2015 5.1.1.
Now I've an Android table not a garbage :good:
thanks a lot.

Phoenix OS x86 v2.1.0 (20 Jul.)

Phoenix os for x86 v2.1.0released. In this version we enhance the hardware compatibility, including: sound card, network adapter, etc. And we add smart casting for Strike of Kings.
Update Details
- Keyboard mapping updates to version 2.5 with smart casting for Strike of Kings.
- The bug that window size won't be saved after restart has been fixed.
- Enhance the hardware compatibility, including: sound card, network adapter, etc.
- "Start Phoenix system" shortcut supports legacy boot now.
- Optimize the Phoenix OS downloader.
Link: http://bbs.phoenixstudio.org/en/showthread.php?tid=6511
Download:
EXE
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.179.32bit.exe
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.175.64bit.exe
https://mega.nz/#!MH4ijZRK!NiRZaFlM54tsNrufmtEhel6oKnWbd_QjNOYauCrRtcM
https://mega.nz/#!JOxVyZrL!c2gL9s9TrTYEMUvJQoCbpXQ_x49GcSsaPY74w6DQa2w
ISO
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.179.32bit.iso
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.175.64bit.iso
https://mega.nz/#!ADQjgRhZ!tC19m6UKuiG1waOHBuypepqkXz3qnMNnF-DF2EMPNKg
https://mega.nz/#!9SIEnboR!GTn3nnW1KlhtZ7XkI98T7Tsaljin8OmZGBqMhhAcm-4

What is the minimum hardware to run Phoenix OS 2.1?
I have an EEE PC 1201ha, does it work?
Specification
Intel® Atom ™ CPU Z520 - 1.33 GHz, 1 core, Hyper-Threading, SSE2, SSE3, SSSE3
Intel® Poulsbo US15W Chipset
RAM DDR2 SO-DIMM 2GB
SSD GOLDENFIR, model T650-60GB

@arielbw install to USB stick and test.
Currently there is no compatibility database, nor no one is working on one.
EEE PC are usually the most well supported Android-x86 devices, so everything should work fine.
EDIT:
Your hardware is enough to make Phoenix OS run.

On 32-bit version, Google Play doesn't work properly. Trying to update Google Play Services, it says that it can't be installed (Error code: -501). Haven't tested the 64-bit version yet, but I can guess it will be the same

@meanhacker are you manually trying to update GMS or it's automatic pop-up?
If manual, why even update?

Vioner said:
@meanhacker are you manually trying to update GMS or it's automatic pop-up?
If manual, why even update?
Click to expand...
Click to collapse
I'm trying to play Bombsquad which requires Google Play Services to be up to date. When I open up Bombsquad, it tell me that Google Play Services needs to be updated. I click OK, and then it takes me to the Google Play Store. Then, I click Update. It's not manual, but it prevents me from doing certain things.

I'm having the same problem.
Just installed the x64 version and I cant even open chrome because it needs google play services updated.
Even tried downloading the apk, but it wont install...

Maheidem said:
I'm having the same problem.
Just installed the x64 version and I cant even open chrome because it needs google play services updated.
Even tried downloading the apk, but it wont install...
Click to expand...
Click to collapse
Yeah I had the same issue until I solved it. Have a look here

Problem on the screen - eee pc 1201ha
Vioner said:
@arielbw install to USB stick and test.
Currently there is no compatibility database, nor no one is working on one.
EEE PC are usually the most well supported Android-x86 devices, so everything should work fine.
EDIT:
Your hardware is enough to make Phoenix OS run.
Click to expand...
Click to collapse
Phoenix OS v2.1.1.190_x86 installed.
Now I have a problem on the screen, an image is duplicated and a bit distorted.
Can someone help me?
Image in the link below
imgur.com/a/DLety
I also installed android-x86-4.0-r1-eeepc.iso. It worked without presenting problems on the screen.

arielbw said:
Phoenix OS v2.1.1.190_x86 installed.
Now I have a problem on the screen, an image is duplicated and a bit distorted.
Can someone help me?
Image in the link below
imgur.com/a/DLety
I also installed android-x86-4.0-r1-eeepc.iso. It worked without presenting problems on the screen.
Click to expand...
Click to collapse
Your integrated graphics might be the issue. I looked up the specs of your laptop:
https://www.asus.com/Laptops/Eee_PC_1201HA_Seashell/specifications/
http://ark.intel.com/products/35444/Intel-SCH-US15W
I actually had something similar to this on my OSMC splash screen (Kodi build on the raspberry pi). I found a post about it here. Have a look and I think you will probably need to let Phoenix OS know your native screen resolution. I think that's why it's distorting like that.

Well, it worked! Thanks!

Meu processador intel® celerom M 430 1.73 ghz roda qual versao do phoenix os ?

A comprehensive guide to the Lenovo Yoga Tab 3 Pro (YT3-X90*) and a Cooked ROM

THESE COOKED ROMS ASSUME YOU HAVE ALREADY AN UNLOCKED BOOTLOADER AND TWRP AS RECOVERY SYSTEM. You can flash them using TWRP, after wiping ART, cache, data, boot and system partitions.
FINAL RELEASE: Well... this is the final release from me and it is specifically for the WiFi model. I hope it is worth it for you. It is more stable and somewhat updated, anyway, if you use a X90F (wifi model) you will probably like it. The other versions are still up for whatever reason. Here's the link. Follow this guide by @Quardah if you are coming from a factory ROM. Go to post 46 if you can't get past the setup wizard. A barely tested (by @Nuihc88) version for the 3G (X90L) model can be found here.
NOTICE: If you find this work useful, mirror it. I won't be hosting it for free forever and it is becoming a burden to my Nextcloud installation. One would say this is a pretty much forgotten thread, but I'm seeing almost daily download activity. I'm putting the ROM files offline now and getting away from XDA for a while. Please don't DM me for the files. If you are looking for them, ask others in this thread. Good bye.
||||||||||||||||||| FROM HERE IS JUST INFORMATION YOU PROBABLY DON'T NEED |||||||||||||||||||
Spoiler: NEWS THAT ARE NOT ANYMORE.
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 .
ORIGINAL POST STARTS HERE. This is general information that I collected for geeks or desperate users that bricked their tablets. When I started this post it wasn't intended to produce a cooked ROM that would include most of these hacks. You don't need this if your tablet boots to Android or TWRP. You also don't need this if you are ready to flash the cooked ROM.
(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.
Spoiler: 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.
Spoiler: EXPLAINING HOW TO FIND THE RIGHT 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 sent 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.
Spoiler: EXPLAINING HOW TO FLASH A STOCK FIRMWARE (DOWNGRADE TO LOLLIPOP AND UNBRICK)
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.
Spoiler: TWEAKS ALREADY IN THE COOKED ROM
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 to put vm.targetutilization at 0.8 top 0.85 in system/build.prop
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.
Spoiler: YT3-X90(FL) UN-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!

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.
Spoiler: Some old info here, but maybe useful
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.
Spoiler: Some old info here, but maybe useful
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.

Such a shame. I love my Yoga Tab 3 Pro. Great hardware. But the software. Thanx anyway for your work.

Very nice write up. Thanks.

joesnose said:
Very nice write up. Thanks.
Click to expand...
Click to collapse
You're welcome. Thanks to you, while learning about this hardware your username pops everywhere.
jahfaby said:
Such a shame. I love my Yoga Tab 3 Pro. Great hardware. But the software. Thanx anyway for your work.
Click to expand...
Click to collapse
It really, really sucks. Let's hope something interesting happens after these strange and recent updates.

CENTSOARER said:
V1: The zip name boot_mod_mm.zip is based on the latest boot IMG provided by Lenovo. You need to first uncompress and flash it using fastboot (this is not a TWRP flshable zip). If you are uncomfortable flashing, you can test it only by issuing "fastboot boot boot_mm_march20_mod.img" once uncompressed, or, if you feel fine using it you can flash it permanently by using the command "fastboot flash boot boot_mm_march20_mod.img". This boot IMG will only work with Marshmallow firmwares in both YT3-X90(FL).
FEATURES:
- Fixed RAM issues (swapiness, vfs_cache_size and low memory killer tweaks).
- Reduced zRAM size to only 128 MB.
- Tweaked interactive CPU scheduler to use other than min and max frequencies (but still responsive). This saves 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.
- Force encryption disabled (it's unnecesary to apply ionioni script now). Still needs to format data partition. You can encrypt your data partition later through Configuration->Security user interface.
Click to expand...
Click to collapse
Thanks for this. Going to take it for a spin.

joesnose said:
Thanks for this. Going to take it for a spin.
Click to expand...
Click to collapse
Please, please provide feedback and don't forget to wipe caches.

alquez said:
"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."
https://github.com/intel/ProductionKernelQuilts this repository containts patches necessary to create base 3.14.55 and 3.14.64 uefi/cht-m1stable kernel tree. The same tree that was butchered by Lenovo in their OPEN_SOURCE "release".
Check this file https://github.com/intel/ProductionKernelQuilts/blob/master/uefi/cht-m1stable/ChangeReport.md and the WW24 part in the "YT3-X90F_ENG_S100265_1601281130_WW24_ROW" will become more clear
Quilt manual: https://elinux.org/images/7/74/Maintaining_Multiple_Android_Linux_Kernels_at_Intel.pdf
If someone would be looking for a good piece to start: the best would be to recreate 3.14.55 or 3.14.64 from the quilts, use the x86_64 defconfig and build a kernel which can be booted. In order to test this, the best solution is to repack TWRP with the new kernel and do "fastboot boot" without flashing, until it boots and the touch screen is working. There's no other way i'm afraid.
I have prepared complete photo documentation of UEFI Bios, i can share, currently moving to different google photos account. Its over 300 photos.
Please, set up a Discord channel if you want to proceed. The first month will be quite boring and daunting because it's going to be build -> repack -> boot -> rant
Click to expand...
Click to collapse
In my defense, when I wrote that sentence was after taking a peek on your github profile, I figured you were just done with the Yoga Tab 3 Pro. I am really, really glad you're still trying and I recognize you are very capable of changing things for this device. I appreciate the sources you link but I am afraid I am useless as a developer, partly because of a lack of time and partly because of a lack of adequate training. I will try to help as much as I can, though. Thanks for the post.

alquez said:
No worries, however if anyone is interested how to actually crunch this one: we have a working prebuild kernel which can be pulled of boot image, and we have a working TWRP, however it looks like TWRP wasn't actually built from source, but cooked using android kitchen so we're still missing a device tree, which in my opinion is a good place to start, because you can use prebuilt kernel to build recovery and lineageos/aosp (it's deprecated but we're talking about android 6 aka cm-13.0/lineage 13.0). If I can create a most basic device tree which is capable of building recovery from scratch useing binary kernel and modules, i'd say were' good, because the next part would be adding more binary blobs from the official software, and we can skip the kernel source part for now until we have lineageos build 13 working). I started experimenting on xiaomi latte tree because it wasnt split like Z00A. It's not gonna be a proper port but it should work from now (i think)
@joesnose did you cook or compile TWRP? It's important
Ok, I'm at the stage i have two folders. The one is unpacked working TWRP, the other one is unpacked compilation i'm building, which means im able to build TWRP from source with binary kernel, but it's not working yet. The goal is make the left one look like the right one by adjusting various parts in BoardConfig.mk and copying files.. If someone has right partition sizes for BoardConfig.mk that would be really helpful, the values i calculated suck and don'y boot yet
Click to expand...
Click to collapse
Uhmmm, I've been there and took some notes with some "GNU shell Fu". What sizes are you using right now?
And regarding the WW part of the name I've noticed the recent updates are marked as WW17 opposed to WW28 which was the latest stable with any changes. Any idea why Lenovo used WW17 to update the Yoga Tab 3 Pro recently?

alquez said:
update, ive managed to boot vanilla android-x86 x64 6.0.1 build without touching the kernel yet and different TWRP (3.1.1.0) with kernel swap
Click to expand...
Click to collapse
Geez, I was excited because I read Ubuntu booted on this hardware but then I realized it was the Yoga 3 tablet but not the Yoga Tab 3, goddamnit. Keep up the good work!

alquez said:
Um Ubuntu 20.04 boots with working accelerometer so the screen rotation works + wifi, and probably audio i forgot to play youtube video, the stuff missing is battery, touchscreen and projector.
To test it you need to connect a usb hub using usb otg, put ubuntu and a keyboard in the hub, boot, and press f2 really fast if you haven't enabled slow boot yet. You can even boot
Xubuntu to ram and remove flash drive. It's a pc architecture after all and most of the processor related stuff is in the linux mainline since 4.11
Recently i was checking why the Windows 10 installer crashes on ACPI Error.
Click to expand...
Click to collapse
Oh, I will have fun doing this kind of stuff at the end of the year. It must run swiftly with i3, provided you won't get touchscreen support.

alquez said:
Geting TS and a battery running is a mandatory, the next is the projector. The rest is pretty much working. I'm building generic celadon x86 atm and the beast is huge it's like 18% now after two hours on -j8 on i7. Maybe we can give this old monster a new life
edit:
And i need to add 480gb drive ;/
Code:
/dev/sdc1 229G 210G 6,7G 97% /home/android
Click to expand...
Click to collapse
I am afraid those are the peripherals that will keep you in 3.14.55/64 Linux, at least for a while , unless you know something more (wouldn't be surprised).
Are those GB for source code or for cache? Both? Jesus... the thing is huge but reading the unpacked boot.img makes much more sense now.

It was ionioni who made the twrp for the device. I dont have the foggiest how he did it.
---------- Post added at 01:23 AM ---------- Previous post was at 01:18 AM ----------
Wow! I missed lot, looks like you have made some serious progress here. very well done.

alquez said:
I contacted my friend and he told me to compare these two folders:
https://github.com/alquez/lenovo_yt...l/cht/arch/x86/platform/intel-mid/device_libs
https://github.com/torvalds/linux/tree/master/arch/x86/platform/intel-mid/device_libs
the new files in "lenovo tree" are the modules we're after, mostly and it's a place to start
I need to ask inioni about twrp.
Click to expand...
Click to collapse
I will guess it was ported from the Yoga Tab 2. I will edit this post soon.

alquez said:
Nice! There's big chance the modules are reused somewhere. We can compare these. I think the two folders in
https://github.com/alquez/lenovo_yt3_x90_osc/tree/master/kernel/cht/drivers/input/touchscreen
which are missing from vanilla tree are two separate drivers and one is for "any pen" driver. Can you ask someone porting modules recently
to help us refresh my memory
[edit]
I've got in touch with TeamBliss of BlissRoms , they are working on cherrytrail tree
Click to expand...
Click to collapse
Nah, I couldn't confirm it was ported. A lot of posts were removed when XDA enforced the GPL measures to its developers.
About BlissRoms, it just makes sense they are working on Cherry trail. I hope you and those guys can achieve something soon. I mean, it's a 2 GB RAM device but the display, projector and dolby audio system are worth for a better fate than Lenovo's plans.

alquez said:
4GB of ram 4 cpu cores, Hardware virtualization support, fast gpu and fast emmc memory. It's a beast, way ahead of it's time.
Click to expand...
Click to collapse
Well, I have the 2 GB RAM model, so my expectations are conservative. Anyway, don't believe I'm a hardcore user, so it's plenty enough for me, considering I won't even flash Google apps. I am now settled with Lollipop, since I need apps not getting killed by damn Doze. It is a shame how OEMs can limit a device like this one. Crond, init.d, bad zRAM, shell, even busybox... frequently the OS is crippled. I read somewhere Doze can be disabled in build.prop or something but one thing I just hate is the recents screen in Marshmallow firmware (my God, is terrible!) and can't be easily changed for something like OmniSwitch. I mean, for a mobile device you have an unusual architecture, why limit it further? Damn, I wish BlissRoms come up with a working build.
Hey, @alquez, have you tried Linux 5.7 on the tablet? I saw this article and seems like the touchscreen may work with the next mainline kernel release. I mean, right now is on RC7, should be stable enough to compile and try (I'd try it, but can't get to my workstations thanks to the virus).
EDIT: Ah... I was looking into my device and it comes with a HiDeep touchscreen (cat /dev/input/event3), the linked news is for the Goodix driver / devices. At least, I guess, it will attract others to this platform... anyway, I was wondering and also confused, shouldn't touch screen work with the hideep driver using this config already?

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!

I love this device! For me it's the perfect device for vacation just because of the projector!
I am so happy that you guys are working on it again. the ram and display tweak works like a charme for me. Had to reset my background screen though
thx for all your help. As soon as you guys have light rom, i'll install it on my 2GB device.

hello how to flash your twrp please ?

can someone upload adb drivers for the yt3-x90f please ? because i try to flash in dnx fastboot mode but commands don't work, even "fastboot devices" don't show me the yoga tab 3 pro

[Discontinued] Linux on the Acer Iconia Tab A500, 2022 edition

UPDATE: I discontinued work for this tablet model, due to the lack of NEON support for the Nvidia Tegra 2 CPU used in this model. Any existing work I uploaded will remain online, but I won't be uploading anything new. I'm also considering selling my tablet to anyone interested.
I have become successful with getting postmarketOS to run on this tablet for the past 2 months, running mainline Linux (5.8.0 as of this writing). This allows us to use this tablet model for a little longer, without getting stuck on older Linux kernel versions.
postmarketOS is an experimental, touch-optimized and pre-configured Alpine Linux. It can be installed on smartphones and other devices.
About postmarketOS, from their homepage:
We are sick of not receiving updates shortly after buying new phones. Sick of the walled gardens deeply integrated into Android and iOS. That's why we are developing a sustainable, privacy and security focused free software mobile OS that is modeled after traditional Linux distributions. With privilege separation in mind. Let's keep our devices useful and safe until they physically break!
Click to expand...
Click to collapse
Wiki page for this tablet: https://wiki.postmarketos.org/wiki/Acer_Iconia_Tab_A500_(acer-picasso)
Most features should work, except for the camera and 3D acceleration. Wi-Fi and Bluetooth work only if the non-free firmware is chosen to be installed.
How to install:
Follow the installation guide at https://wiki.postmarketos.org/wiki/Installation_guide, where theses specifics have to be specified when requested (this device is now in upstream pmaports):
Vendor: acer
Device code-name: picasso
Install non-free Wi-Fi + Bluetooth firmware: y
Only the mainline kernel is available for installation now, as downstream kernels no longer successfully compile. The user interface may be freely selected, as long as it is not one that requires 3D acceleration. To use KDE Plasma 5, add these lines to /etc/security/pam_env.conf:
Code:
QT_IM_MODULE=qtvirtualkeyboard
QT_QUICK_BACKEND=software
LIBGL_ALWAYS_SOFTWARE=1
Next, run the following commands in succession, after each one finishes, assuming the working directory contains the pmbootstrap.py script:
Code:
> ./pmbootstrap.py build device-acer-picasso
> ./pmbootstrap.py build firmware-acer-picasso
> ./pmbootstrap.py build linux-postmarketos-grate
From here on out, the generated chroot can be either installed to the eMMC, or a microSD card that must be inserted at or before boot time (the latter method allows for dual-booting Android already installed to the eMMC, although it can be directly accessed from the Linux system). The boot partition always has to be flashed to the eMMC in fastboot mode, as it is not possible to boot directly off of a microSD card.
If installing to the eMMC, run
Code:
> ./pmbootstrap.py install
> ./pmbootstrap.py flasher flash_kernel --partition secboot
> ./pmbootstrap.py flasher flash_rootfs
(optional) > ./pmbootstrap.py flasher boot
If installing to a microSD card, run
Code:
> ./pmbootstrap.py install --sdcard [path to the device for installation]
> ./pmbootstrap.py flasher flash_kernel --partition secboot
Depending on what user interface was chosen earlier in the installation process, there may not be enough packages installed to get a fully-loaded GUI. Besides the built-in Wi-Fi, it is also possible to use a USB ethernet adapter, or connect to another computer with a micro-USB cable and get RNDIS access that enables using SSH to the tablet.

Using another distro in place of postmarketOS
Advanced: Using another distro in place of postmarketOS
It is possible, if using the microSD card method, to use a different distro instead of postmarketOS, for those who want more software OOTB. I use the Ubuntu MATE rootfs from https://ubuntu-mate.org/ports/raspberry-pi/ as my daily driver, but other distros may take more effort to get working. Glibc limitations no longer apply, as the kernel version is no longer stuck at 3.1.0 (unlike with my earlier attempts). Carefully follow the instructions listed below, or the resulting system will become unbootable:
Use losetup or GNOME Disks (Utility) to mount the image in read-write mode.
Run GParted with the loop image and the target microSD card as the arguments.
Copy only the larger rootfs partition to the microSD card. Resize as necessary to get it to fit on the target microSD card.
Make sure on the target microSD card the boot partition is named 'pmOS_boot' and the rootfs 'pmOS_root'. The initramfs is hard-coded to search for partitions with these names by default for microSD cards. The loop image is not needed after this point, and can be safely detached.
On the copied rootfs, edit /etc/fstab to reflect the partition layout. To get access to Wi-Fi and Bluetooth, copy the kernel modules and firmware from the pmOS rootfs on the host system to the microSD rootfs.
Let me know if something wasn't understood from my instructions, or more clarification is needed. The instructions here can be somewhat overwhelming for those who have less Linux experience, but at least we're not forced to stay on old distro versions anymore.

Premade Linux images
I finally have managed to create a premade image to make the installation process easier for other people, especially for those who don't want to go through the hassle of compiling software. Every image I make can be found at https://drive.google.com/drive/folders/1pMqaS5GaM6N9TAKlNGQZWCG8UTiRn4pK?usp=sharing.
For all images:
Kernel version: 5.15.0-rc4
Includes all compiled kernel modules from postmarketOS builds, plus nonfree firmware enabled.
The postmarketOS splash screen will appear, although the underlying OS differs based the image used.
Images available:
Ubuntu MATE 20.04.1 (ubuntu-mate-20.04.1-desktop-armhf+acer-picasso.img.xz) (size: 1.3 GiB):
Based on 'ubuntu-mate-20.04.1-desktop-armhf+raspi.img.xz', available from https://ubuntu-mate.org/ports/raspberry-pi/
Underlying OS is Ubuntu 20.04.1, which is supported for 5 years until April 2025. However, Ubuntu MATE officially has support only until April 2023.
Requires at least an 8 GB or greater size microSD card (the image is 5.6 GiB decompressed).
The setup screen will open upon the first successful boot, where a username and password have to be set.
Most extra packages for the Raspberry Pi family of computers have been removed, including the kernels.
The battery icon in MATE cannot be enabled graphically, as the preferences window has been patched to permanently hide such an option (as the Raspberry Pis lack native battery support); instead run the command
Code:
gsettings set org.mate.power-manager icon-policy 'always'
to manually enable it.
The PPA at https://launchpad.net/~grate-driver/+archive/ubuntu/ppa is pre-configured to be accessed. Most packages from this repository, including the opentegra driver, come preinstalled. They currently are enough to get 2D acceleration working, but not for 3D acceleration.
Except for what has been mentioned above, any packages shipped may have to be updated once an internet connection is established.
Arch Linux ARM (ArchLinuxARM-armv7-latest+acer-picasso.img.xz) (size: 576.6 MiB):
Based on 'ArchLinuxARM-armv7-latest.tar.gz', available from https://archlinuxarm.org/about/downloads
Rolling release distro often with the latest versions of most packages. More recent software can be acquired at a small expense of instability.
Requires at least an 2 GB or greater size microSD card (the image is 1.9 GiB decompressed). Larger size is recommended for installing more packages.
To login into system:
Login as the default user alarm with the password alarm.
The default root password is root.
Initially command-line only; contains no desktop environment installed.
Use any image writing program with these images. If such a program does not support XZ compression, the image needs to be extracted instead, and that has to be used.
I hope the images will proves useful to some people. Let me know if any issue pops up during usage of this image!

hey Worldblender,
I have flashed the premade file you shared to an sdcard but I'm unsure as to how to boot into it?

tehno said:
hey Worldblender,
I have flashed the premade file you shared to an sdcard but I'm unsure as to how to boot into it?
Click to expand...
Click to collapse
The instructions were written assuming that the user has already flashed the custom bootloader as described here: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271. Sorry for not making this clear anywhere, but that custom bootloader, along with flashing the boot image found in the first partition named "pmOS_boot" to either boot or secboot using fastboot, should get you set up to boot the SD card image.

Hi Worldblender,
Nice to see you work on this legacy device.
I definitely don't want to use android or can use it anymore on this tablet.
Nice to see some linux flavor being ported to it.
I had a look a the dedicated page on postmarketos.
Can you confirm the only GUI availbale as for now is the one called "Weston" ?
Or is MATE also working (from the screenshot) ?
Weston seem very basic, MATE more friendly.
How about performance ?
I'm considering reusing it to display a grafana dashboard in firefox for instance, maybe more if performance isn't too bad.

Worldblender said:
The instructions were written assuming that the user has already flashed the custom bootloader as described here: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271. Sorry for not making this clear anywhere, but that custom bootloader, along with flashing the boot image found in the first partition named "pmOS_boot" to either boot or secboot using fastboot, should get you set up to boot the SD card image.
Click to expand...
Click to collapse
Thank you Worldblender for your work in writing up instructions and compiling the image too.
However, I'm still a bit lost as to what to do with your Ubuntu Mate image.
I've gotten the TWRP bootloader installed onto my Acer A500 tablet, but whether I use Rufus to expand your image onto an SD card, or just copy the compressed image onto the SD card, the [ Install ] does not see any images inside of the drive. Am I supposed to decompress your image in Windows and use the 0.img and 1.img in place of the nvflash's boot.img and recovery.img?
While I can see the two partitions in Ubuntu, I'm equally lost as to what to do with them, and how to get it onto the tablet.

coluwyvurne said:
Thank you Worldblender for your work in writing up instructions and compiling the image too.
However, I'm still a bit lost as to what to do with your Ubuntu Mate image.
I've gotten the TWRP bootloader installed onto my Acer A500 tablet, but whether I use Rufus to expand your image onto an SD card, or just copy the compressed image onto the SD card, the [ Install ] does not see any images inside of the drive. Am I supposed to decompress your image in Windows and use the 0.img and 1.img in place of the nvflash's boot.img and recovery.img?
While I can see the two partitions in Ubuntu, I'm equally lost as to what to do with them, and how to get it onto the tablet.
Click to expand...
Click to collapse
Wait for me to give out an update to the image, as there likely has been a new kernel version released that I would like to have updated first.
TWRP will not be used at all for this installation process, as the image is too big to flash with fastboot. Just flash the image to a microSD card, as the boot image that will be flashed will automatically pick it up shortly after booting. The only thing that does have to be flashed is the boot.img, which can be found in the first partition, and you will be only using fastboot for this process, not anything else.

I released a new version of the premade Ubuntu MATE image just now, named 'ubuntu-mate-20.04.1-desktop-armhf+acer-picasso.img.xz'. The following changes have been made since the last image:
Kernel version upgraded to 5.10.1-rc1
Based on Ubuntu MATE 20.04.1
Everything that changed since the beta1 image
Other than these changes, there are no other differences that can be noticed right away.
Direct link: https://drive.google.com/file/d/1mr-7e29KJYeagJju0Yo1qUpT2YRb61AR/view?usp=sharing

Many thanks for your work. I've entered today this forum just curious about something new and found this!
Second life for this old machine!
For those with problems installing, I've flashed precompiled image using balenaEtcher into the sdcard.
Then, extracted .xz image, extracted .img, then extracted 0.img and copied boot file from there. After that, renamed the file to boot.img and flashed it with fastboot.
As I've the old modified skrillex bootloader, the command is fastboot flash secboot boot.img.
It boots and works well for now!

Worldblender said:
[*] Add the PPA at https://launchpad.net/~grate-driver/+archive/ubuntu/ppa to get access to updated video drivers. They currently are enough to get 2D acceleration working, but not for 3D acceleration.
Click to expand...
Click to collapse
@Worldblender
Hi, i apt updated after adding grate-driver ppa, it seems it broken xorg because X don't start anymore
Can you detail how to proceed ?

pheex79 said:
@Worldblender
Hi, i apt updated after adding grate-driver ppa, it seems it broken xorg because X don't start anymore
Can you detail how to proceed ?
Click to expand...
Click to collapse
Can you still switch to a virtual terminal with Ctrl-Alt-[F1-F7]? You will need a USB keyboard to do this. Then try, after logging in with your username and password:
Code:
systemctl stop lightdm
startx
If startx does not bring something up, could you try running journalctl, and show me any log entries relating to lightdm?
If that still fails, you can try (if ppa-purge is not installed, install that first)
Code:
ppa-purge ppa:grate-driver/ppa

@Worldblender
one binary missing but i think this error is present before adding ppa
"/sbin/prime-switch: 22: /usr/bin/gpu-manager: not found"
Xorg log:
Require OpenGL version 2.1 or later
modeset(0): Failed to initialize glamor at ScreenInit() time

pheex79 said:
@Worldblender
one binary missing but i think this error is present before adding ppa
"/sbin/prime-switch: 22: /usr/bin/gpu-manager: not found"
Xorg log:
Require OpenGL version 2.1 or later
modeset(0): Failed to initialize glamor at ScreenInit() time
Click to expand...
Click to collapse
I never received such an error, but the specific package you must install is xserver-xorg-video-opentegra. No other Nvidia driver is going to work.

Worldblender said:
I never received such an error, but the specific package you must install is xserver-xorg-video-opentegra. No other Nvidia driver is going to work.
Click to expand...
Click to collapse
It works ! Thank you
xserver-xorg-video-opentegra was not installed
when adding ppa grate i only did an "apt upgrade" cmd i thought all grate items were installed (a few are installed when upgrading apt)

Nice work thank you so much.
Is there any chance for Manjaro arm? Or is it limited to debian based distros?

Note that after following the instructions for installing the Ubuntu MATE image from @Worldblender from a starting point of just the stock image, I have Ubuntu MATE installed on the external SD card and no OS installed on the eMMC because it was wiped during the bootloader replacement. Reading back through the posts suggests this is by design.

@Worldblender, so I'm very new at rooting devices, and have a little experience with Ubuntu but feel pretty lost. Any chance you could hook me up with a step by step install of the Nov2 image (unless you've put together another new version) from a stock(not rooted or anything) A500? I apologize if I overlooked something.
Edit: I got it working after doing this thing called reading, I definitely overlooked some things after reading closer. For someone else that might find themselves in my shoes here's what I did.
I followed this link: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271 to get the bootloader installed
and then followed @whylly 's instructions:
whylly said:
For those with problems installing, I've flashed precompiled image using balenaEtcher into the sdcard.
Then, extracted .xz image, extracted .img, then extracted 0.img and copied boot file from there. After that, renamed the file to boot.img and flashed it with fastboot.
As I've the old modified skrillex bootloader, the command is fastboot flash secboot boot.img.
Click to expand...
Click to collapse

Hi there ! I have an iconia a500, rooted with lightspeed 4.8. Can I install this and then make it switch to Khali linux ? My ultimate objective is to get Khali on this tablet. I've worked my way down from ver 2.5x linuxdeploy all the way down to 2.0 lol So I'm thinking maybe if I apply your OS it will update the Kernal from 4.0.3 to 5 yes ? (That's a big jump for linuxdeploy) then I can apt-get khalifull ? Am I off base would this work ? Unless you have an image already of course in which case pleaaaaaaaaaaaaaase I'll pay for the bloody thing if I have to I've been pulling my hair out for days. Tried frikkin everything.
Unless anybody has a better method of course in which case feel free to suggest. If I have to make the image from scratch so be it
EDIT: UGhhhhhh after days of troubleshooting, I got to linuxdeploy2.0-1.16 installed kali (the native one on the app not from the repository as that gives kernel too old once you get the install working). Managed to term in and tried to start lxde, failed because lxde doesn't exist (sigh) tried to apt-get... kernel too old. game over sigh
Unless someone has a workaround I don't think it's possible to get Khali on a500.

Sound work?