[BOOTANIMATION][APK] N5 BIOS Boot - Added some smoothness. (Sep. 13th)

[BOOTANIMATION][APK] N5 BIOS Boot - Added some smoothness. (Sep. 13th) - Nexus 5 Themes and Apps

Heavily influenced by existing BIOS boot animations, I decided to try my hand at one for the Nexus 5. Credit for original design goes out to the original authors, without whom, I wouldn't have this thread. :highfive:
You can use ANY of these animations with ANY Nexus 5, but animations paired with the wrong phone will just display incorrect information. These animations are timed with my personal device's boot time very carefully. I run a 32GB D820 on Cataclysm ROM with ART enabled, so let me know if the timing is too fast for other devices, and I'll slow it down.
Still need GPS and camera model numbers!
Also, I can customize the text for you for a donation of your choosing. Send me a PM.
I provide a StockBoot.zip in case anything goes wrong or you'd like to revert, but if you prefer the stock boot animation, check out this awesome modified stock boot by @dankoman here.
CHANGELOG
09.13.14: Fixed theme, locked screen to portrait, and added feedback for root check.
08.31.14: Finalized N7 2012 animation and updated app with more multi-threading for a smoother experience.
08.23.14: Updated installer to version 1.0.0-rc. Beta release for Nexus 7 2012 animation, also updated build and root tools and started preliminary support for Android 'L'.
06.23.14: Updated installer to version 0.3.1. Updated imaged for KitKat 4.4.4.
06.13.14: Updated installer to version 0.3.0. Added Nexus 10 animations.
06.08.14: Updated installer to version 0.2.7. Updated images for KitKat 4.4.3.
01.25.14: Updated installer to version 0.2.6. Switched 7zip decompression library, fixes files not extracting for hopefully everyone. I'm new to the native code thing, so if for some reason, it doesn't work, please let me know!
01.24.14: Updated installer to version 0.2.4. Fixed apparent BusyBox requirement. I hope, need testers on this one.
01.22.14: Updated installer to version 0.2.3. Fixed versioning to reflect the fact that the app isn't considered finished until I have all Nexus devices back to the Galaxy included. Fixed some minor bugs. Most importantly: TINY FILE SIZE! Whoo! Update pushed to Play Store.
01.13.14: Updated installer to version 2.2. New option to force animation to play at least once before boot is finished, that way if you like a slower boot, you're guaranteed to see the whole thing, even if your device is technically done booting. Pretty cool feature Google added back in Jelly Bean, apparently. Was news to me, so thanks to @Harrysoon from over in the Nexus 7 2013 thread! :good: Also, more bug fixes and I changed the end of the animation to loop an ellipsis after "Starting Apps" so it's not just static.
01.12.14: Updated installer to version 2.1. Pertains to you guys because it fixes some visual bugs. DevHost link updated, Play Store update pushed.
01.06.14: Updated the installer to version 2.0. Finally managed to reduce the file size by a decent amount. So much so, that even including the Nexus 7 2013 animations, the app remains roughly the same size! The only real benefit to you guys is a smaller bootanimation.zip. So after this update, I probably won't update this thread anymore. Thanks for your tremendous support, and don't forget to come by my threads for the other Nexus devices once I get around to them.
01.04.14: Updated the installer to version 1.0. Tried to reduce file size (didn't work very well), implemented a better way to copy files (thanks, @overhauling), implemented a pretty new icon, and changed package names to reflect that I'll do animations for other devices in the future. This means you need to manually uninstall the old version (if you don't want clutter), as this version will NOT overwrite it. Overall, this means the app is ready for full release. I'll add a Play Store link when it gets uploaded.
12.21.13: Updated the installer. Added non-root options, fixed typos, cleaned up the code. I have no idea if the non-root options work, since /data/local isn't writable for normal users on the N5. So test at your own peril, I suppose.
12.18.13: Uploaded updated installer. Adds installation options (/data/local or /system/media), as well as cache cleanup, uninstallation, and revert to stock. Make sure to read everything carefully!
12.16.13: Uploaded beta APK installer. Please understand this is very, very beta! Also understand this is my very first Android app. I've done my best to ensure it won't mess up your device (it never killed my N5, even the big bad bugs (hello infinite loop)), but I can offer absolutely no guarantee. Note this is far from the final version. I plan on implementing save location choosing, in-app cache clearing, and a revert to backup option. Please report any and all bugs.. Sadly, in my haste to provide this for you, I neglected to do a lot of logging, so please be as descriptive as you can.
12.15.13: Added 4.4.2 animations, now flashing to /data/local and using PNGs (smaller files!). Enjoy.
12.09.13: Replaced "Have a nice day!" with "Starting Apps.", and finished the colored Nexus logo versions! (Been neglecting my studies just for you guys )
12.08.13: Added flashable versions of all 4.4.1 animations! This means no more manual file management!! This also means I've officially deprecated the 4.4 animations. The colored variations will only be 4.4.1.
12.06.13: Fixed D820/16GB flashing old hardware information in certain frames, finished 4.4.1 versions.
12.05.13: Finished D821/16GB, updated hardware information for all.
Downloads:
APK: here (free) or on the Play Store as "[Root] BIOS Boot for Nexus".
Flashable 4.4.1 and 4.4.2 animations: here.
Old, non-flashable 4.4 animations (white logo only): here.
As always, I am not responsible for your phone's well being!
Instructions for flashable animations:
Download, flash in recovery. That simple!
Instructions for old, 4.4 animations:
DO NOT FLASH - CWM/TWRP probably won't let you anyway
Push to /system/media*
Rename to bootanimation.zip
Set permissions to -rw-r--r--**
*Use a file explorer/browser app with root access (needs to be able to mount /system as read-write), or adb push. I recommend using CM App Installer to install CyanogenMod's File Manager, it's by far one of the best free file explorer/managers you can come by.
**Either use a file explorer/browser app to do this or a custom recovery (I know TWRP can, don't know about CWM). If what you use uses chmod to change permissions, then you want "chmod 644".
Installer App (Click for full gallery)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D820/32GB - 4.4.1 - Colored Nexus
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you liked my post or I helped you, consider buying me a beer!
BTC: 1NMfhcdWTpDEgUNB2nWUzwjvraBcHzDj7d
[QRCODE]bitcoin:1NMfhcdWTpDEgUNB2nWUzwjvraBcHzDj7d?label=Main%20Wallet[/QRCODE]

Nice. Thanks!
Sent from my Nexus 5 using Tapatalk

Can't lie this looks pretty awesome! I didn't see your earlier animations, can you really push vol down+power during the boot animation to enter the recovery or boot loader? Or is it just for show?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Thanks, looks nice!
Use Cataclysm with Dalvik here, on my opinion, it should be 3-4 sec. slower.

RhinoShock said:
Can't lie this looks pretty awesome! I didn't see your earlier animations, can you really push vol down+power during the boot animation to enter the recovery or boot loader? Or is it just for show?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is only my second animation. I say that this is based on earlier animations because I saw a Nexus 4 version of this and felt the need to try my own. That's also the reason my inaccuracies tend towards Nexus 4 device info.
Also, that depends on your definition of show . Technically speaking, holding volume down and power will take you to the bootloader no matter what your device is doing. But also technically speaking, once the boot animation starts, the device has to power down before it can boot to the bootloader. So, I'm sure your question is asking if Vol_down+Power will take you straight from the boot animation to the boot loader, and that answer is no, but if you hold the buttons long enough, it will power down and the boot the boot loader.
MoJo said:
Thanks, look nice!
Use Cataclysm with Dalvik here, on my opinion, it should be 2-3 sec. slower.
Click to expand...
Click to collapse
Okay, thanks for the report, I'll get a slower version up shortly.

My 32gb black N5 is on Omnirom (running dalvik, due to Xposed), and the boot animation timing was PERFECT! Thanks so much.

MoJo said:
Thanks, looks nice!
Use Cataclysm with Dalvik here, on my opinion, it should be 3-4 sec. slower.
Click to expand...
Click to collapse
Slower version in OP. Went with DropBox temporarily.

BrianAllred said:
This is only my second animation. I say that this is based on earlier animations because I saw a Nexus 4 version of this and felt the need to try my own. That's also the reason my inaccuracies tend towards Nexus 4 device info.
Also, that depends on your definition of show . Technically speaking, holding volume down and power will take you to the bootloader no matter what your device is doing. But also technically speaking, once the boot animation starts, the device has to power down before it can boot to the bootloader. So, I'm sure your question is asking if Vol_down+Power will take you straight from the boot animation to the boot loader, and that answer is no, but if you hold the buttons long enough, it will power down and the boot the boot loader.
Okay, thanks for the report, I'll get a slower version up shortly.
Click to expand...
Click to collapse
Ah yeah I thought so haha. Still really awesome anim though! Will be downloading when I get home
Sent from my Nexus 5 using XDA Premium 4 mobile app

So, I'm not going to reveal how I was editing these for the different versions in case any Photoshop gurus are here to point and laugh, but it was really silly, and multiple /facepalms would be in order. Now that both D820 and D821/32GB versions are up, I'm going to take a break and re-factor my editing process while I do D821/16GB, that way I can pump the versions with the colored Nexus logo out faster.

So freaking awesome thank you thank you thank you, I have been looking for this for so long. Works like a charm too.
Sent from my Nexus 5 using Tapatalk

32GB - stock ROM, faux kernel here. The slower version timing was absolutely PERFECT.
Thanks so much! Great work!

ksong12 said:
32GB - stock ROM, faux kernel here. The slower version timing was absolutely PERFECT.
Thanks so much! Great work!
Click to expand...
Click to collapse
What version of Faux's are you on, and are you using Dalvik or ART? I'm just wondering, since I also use Faux's kernel. I'm interested in which of these three things (ROM, runtime, and kernel) makes the boot times different.

Actually, turns out that on the second and subsequent reboots, it rebooted faster for some reason. Made it so that the original one was actually timed quite nicely.
I am on Faux 004m, Dalvik.

Stock version and stock kernel the base version works great and I totally love it !

This is what exactly i was looking for. Thanks!

Does system/media get wiped with a ROM upgrade?

Ronaldo Forenucci said:
Does system/media get wiped with a ROM upgrade?
Click to expand...
Click to collapse
yes.. u can put the boot animation in /data/local if u want it to persist across rom upgrades..

Just got some new information regarding the display and touch screen. Updates (and D821/16GB version) forthcoming.

16gb one works unbelievably flawlessly. Nice work OP
Sent from my Nexus 5 using Tapatalk

got this working today, it's all good, except, it feels too slow....
what i mean is, it gets through the first screen normally, but when it changes to the next screen, with the big grey box at the top, that lasts maybe a quarter of a second and then the phone is already on, it's impossible to even read it at all.
maybe make it a bit faster so the first screen doesnt take as long? maybe i just have a faster n5 or something

Related

LG G Stylo (T-Mobile/MetroPCS) ROOT (5.0.2 & 5.1.1 ) - TWRP Recovery - Unbrick Guide

LG G Stylo (T-Mobile/MetroPCS) ROOT (5.0.2 & 5.1.1 ) - TWRP Recovery - Unbrick Guide
DO THIS AT YOUR OWN RISK
WARRANTY IS NOW AVOID IF YOU PROCEED WITH ROOT AND TWRP
Windows Machine/OS Only
----------- Lets Proceed on to Rooting LP 5.1.1 (One Click Method) -----------1- Click Here and Download LGGSTYLO_LP511_OneClickRoot.zip File
2- Click Here and Download LG USB Drivers ( Thanks @GameTheory. )
"NOTE: skip Drivers if you have them already install"
4- Enable USB Debugging via Developer Option.
5- Decompress LGGSTYLO_LP511_OneClickRoot.zip on Root C: drive for easy access or any convenient location.
6- Now lets head over where we decompress that zip file and just double " LG_Root_Script.bat "
7- LET the script run to FULL COMPLETION, Your Device will Reboot twice so be patient.
IF YOU HAVE YOU DEVICE WITH LOCKSCREEN CODE / SWIPE CODE NEED TO UNLOCK SCREEN ON EACH REBOOT FOR THE SCRIPT TO PROCEED
Check Image for the whole process - CLICK TO SHOW CONTENT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8- when the process say
Code:
ui_print - Done !
press Ctrl+C
press N then ENTER
( Check Image - CLICK TO SHOW CONTENT )
- And you are done your device is now Rooted
- Phone will Reset and you need to wait till phone is fully Rebooted to system it may take a few minutes so be patient.
NOW YOU CAN PROCEED TO FLASH CUSTOM RECOVERY (TWRP)
-----------------------------------------------------------------------------------------------------------------------
THIS METHOD ONLY WORKS IF YOU ARE IN LP 5.0.2
----------- Lets Proceed on to Rooting LP 5.0.2 -----------

First of all Thank you @avicohh for LG One Click Root GUI/Script base on his Guide I Have successfully Rooted the Stylo using and Following some steps from there just adding some thing you may see in the progress of rooting:
Original LG One Click Root Guide and File Download -CLICK HERE-
After getting all necessary files this is what i did
1- Install LG drivers if they are not installed yet. (VERY IMPORTANT)
2- Download the LG One Click Script Root file above and extract to some folder. (double click on the 7z exe file)
3- Enable Usb debugging on your phone. (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (THIS IS VERY IMPORTANT STEP)
4- Connect your phone to pc. (it will install driver when connected just wait till is done)
5- Switch to MTP when drivers are full install
6- Double click on the LG Root Script.bat file (the Script will run)
7- Follow the instructions.
*Please leave your feedback if it worked for you
Many Many Thanks to @avicohhfor the LG One Click Root
P.S. I'm not a Dev. I just followed the original guide and the only thing i haven't install is Custom Recovery.
If you came across some Fail attend messages just wait a few more seconds, if that doesn't work try again in my case the first try work and 2 fail attends messages came up so just wait a few sec. if that happen
BE PREPARED. First boot can take a while!!! can stay on logo for up to 3 to 5 minutes or sometimes little more before it goes into Optimizing Apps. Have patience. Subsequent boots a pretty speedy.
------------------------------------------------------------------------------------------------------------
TWRP (Custom Recovery) for LG G Stylo T-Mobile (H631) and Metro (MS631) Variant ONLY
------------------------------------------------------------------------------------------------------------
- Download Custom Recovery File from TWRP 2.8.7.0 v10j Click HERE (Thank you @Unjustified Dev and @fix-this! )
After Rooting your device (T-Mobile or Metro Variant)
1- Check -Enable OEM Unlock- under Developer Option (Skip this part if you are 5.0.2)
2- download Flashify from Google Play Store
3- Open Flashify.
4- Do a Stock Recovery Back-up (Recommended)
5- Flash Recovery Image.
6- Will ask to Reboot System and will take you to TWRP Custom Recovery.
7- Now you are done just Reboot System from Recovery or do a FULL BACK-UP
NOTE : This New TWRP (Custom Recovery) have the new fix (Showing Half Screen only) for the new LG G Stylo Hardware Panel.
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
LG G Stylo Update Firmware | Unbrick Guide by @GameTheory.
IF YOU ARE USING @GameTheory. v10i UPDATE ZIP DON'T FLASH v10j UPDATE ZIP , I REPEAT DON'T FLASH v10j UPDATE ZIP YOU'LL END UP WITH BOOTLOOPS/SOFT BRICK
-------------------------------------------------------------------------------------------------------------
Just Follow step from link below - Thank you @GameTheory.
http://androidcreations.weebly.com/lg-g-stylo.html
------------------------------------------------------------------------------------------------------------
Every KDZ Release for T-Mobile and Metro can be found here :
http://forum.xda-developers.com/android/development/read-trying-to-root-kdz-files-kdz-tmo-t3152531
------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
Full v10j Stock Restore / Update
Use this guide if you are on @GameTheory. v10i or want to deleted all trace of root and twrp (Back to Stock)
Full v10j Stock Restore / Update
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------

i just picked up the tmob version yesterday, nice device. not the greatest screen ive had but not bad. im also rooted, we just need twrp so we can use xposed.

waiting on TWRP
As previously posted, I am also waiting on a conduit to get xposed installed.. a device without it and all the benefits it brings feels unreal to me..

i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.

fix-this! said:
i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.
Click to expand...
Click to collapse
+100 on that (Battery life + dedicated section for the phone) i have to agree with the battery life pretty neat and i'm sure is because CPU is doesn't have higher clock and screen is not so power hunger, other thing i'm satisfied is the memory management no matter what i do i haven't seen going lower than 1gb of ram always i been having between 1.2gb to 1gb free never had that before so pretty neat and i do have a lot of apps install most of them run in the background,
How can be make a request about making a Dedicated Section for the LG G STYLO? where do i need to sign if that happen i'll be posting some Bootanimations for this phone porting some old ones i created for the G2 and probably making some new ones.

I am pretty impressed with the device. I just bought it for my wife, which she doesn't care what phone I give her as long as it doesn't break the bank. Not able to do that with any of the flagships. Decided to give it a try risking not having the dev support. Hopefully more people takes the risk so we can have custom roms to play for. (not sure if my wife would like that) LOL

Ah, good, a T-Mobile Stylo thread. I just posted my thoughts in the thread for the Boost (Sprint) version, but anyway, I'm mostly liking this phone (except that the camera app doesn't offer manual exposure controls). I'm not sure I'm going to root mine just yet (hell, I still haven't rooted my Avant!), but it's nice to see that a root is available.

i'll leave this here First Custom Boot Animation for the Stylo
https://www.youtube.com/watch?v=wP5EZfmE-oQ

This is really a Lollipop issue, rather than a problem with the phone itself, but I found that the Embware call blocker (which disappeared from Google Play, go figure) doesn't work on the Stylo. It turns out, most of the call blockers out there aren't working on Lollipop.
What I particularly want is a pickup/hangup type of block, so Rachel from Card Services can't even leave a voicemail. I had this capability with the Embware blocker on the KitKat-equipped Galaxy Avant, even before I got around to rooting it. It looks like Google tweaked Lollipop to prevent pickup/hangup blockers from working. #&^%$%^!!!
Extreme Call Blocker claims to work on L, but I'm wary of forking over the cash for it.
There is a built-in reject list under the Call Settings menu, but it's just a straight-to-voicemail reject. I don't want to waste my time deleting spam voicemails, though Visual Voicemail is at least quicker than calling in.
I suppose I could just call T-Mobile and see if they could turn off voicemail entirely. That would at least make the native call blocker useful.

Timberwolfhusky said:
,
Click to expand...
Click to collapse
i found this post to open a new phone section if we show support for the STYLO we may get a Section for it and people can just go there for Q&A, Themes,Dev work and so on, i know the Phone still brand new in everyone eyes but early support doesn't hurt
http://forum.xda-developers.com/show....php?t=1660354
P.S. @Timberwolfhusky you are the only person not in Boost Mobile thread so

I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?

guest_2011 said:
I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?
Click to expand...
Click to collapse
is to early to say it but i have seen a lot of activity and a lot of people are interested on this device, some user with the Zmax are going to be upgrading to the Stylo, we have a pretty good start phone is 100% Rootable as you can see on the 1st post and @fix-this! is working getting the TWRP (Custom Recovery) so i would say we are getting good support so far, Not a lot of support but good.
P.S. this Device is Brand new just got release.

I've also seen some articles that indicate that outside of North America, it's being marketed as the "G4 Stylus" - and also in the international market there's also a G4c model with similar specs; like the Stylo, it has a 720p screen, but it has a smaller form factor than the flagship G4, no stylus, and an 8MP camera.
The T-Mobile G Stylo seems to be the best of the bunch, though: double the RAM and double the storage of the Boost version. Having been a T-Mobile subscriber for a while now, I'm glad to see that they bumped up the specs. It also has the unlock app baked-in, so if you're eligible to unlock it, there's no need to call in or fumble around with unlock codes. I used the unlock app on my Avant before I bought the Stylo, and it worked smoothly and easily. If you're not eligible to permanently unlock it, you can still get a 30-day unlock for international travel.
I'm finding that I like this phone a LOT, in spite of the lack of manual camera settings and the Lollipop-related call blocker issues. The HDR mode seems to be able to handle backlit subjects well enough that the lack of manual exposure control isn't as big a deal as I was thinking it would be.
So far, battery life looks to be in the "outstanding to exceptional" range. It reminds me of the F3 in that respect, but this is a vastly better phone than the F3 could ever hope to be. At least somebody is listening when it comes to battery life!
I'm going to hold off on rooting mine for now, though, at least until I can SIM-unlock it. In any case, I've always been a bit cautious about modding my primary phone.

How's the battery life compared to the tmo zte zmax?(for those that had the zmax)
Also, does this have the "feature" that when the phone reaches certain temps it lowers and prevents you from turning up screen brightness?
Sent from my Z970 using XDA Free mobile app

Will it work (root guide) with Metropcs? I just ordered one. Is metro also the same model LG-H631? I see LS770 on the web, not sure if same phone or something else. Anybody tested USB OTG with Stylo?

Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.

fix-this! said:
Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.
Click to expand...
Click to collapse
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.

guest_2011 said:
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.
Click to expand...
Click to collapse
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.

Is it possible to unroot?

fix-this! said:
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.
Click to expand...
Click to collapse
agree with you this phone needs his own section i'm sure will be good success from LG i have friend that have the Zmax and they are going to be getting the Stylo, we just need someone with the MetroPCS Variant to verified if is rootable the same way the T-mobile variant is.
guest_2011 said:
Is it possible to unroot?
Click to expand...
Click to collapse
the SU app have an Option to Unroot, i personally haven't try it but maybe someone else know if that works.... never had the need to unroot a phone so i have no idea about that

[WIP/TBD][5.0.1][LRX22C][YT2-830F][SleepyBear 830F: Feedback Needed!]

**NOTICE: Due to unforeseen circumstances - my car's starter died, and I had to return my Yoga 2 for emergency cash - ROM development is on hiatus. Best Buy has put back a brand new Yoga 2 for me when payday comes again, provided I can eek it out.
I thought of a GoFundMe to help pick one up, but I didn't feel comfortable doing this.
Updates will come as available. Again, I am so sorry.
This ROM is for the **LENOVO YOGA TABLET 2-830F ONLY!**. You are responsible for your device and its warranty, health, happiness, sanity, love and abuse. The initial release will come over the next couple of weeks. I wanted to throw up this post to get your feedback and get a few folks to beta test. I have been using it as my daily driver for over a week, and all has been well
Android Lollipop source (provided via Lenovo's Open Source documentation):
http://support.lenovo.com/us/en/products/tablets/yoga-series/yoga-tablet-2-830/downloads/DS102874/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SleepyBear - A gently modified and streamlined Lollipop ROM for the YT-830F This ROM is based off of Lenovo's stock Lollipop ROM for the YT-830F (.LRX22C.YT2-830F_USR_S100067_1507101258_WW52_ROW)
Introduction
Last year, I spent a lot of time pouring over the Dell Venue 7840, one of the first "mainstream" Intel x86-based Android tablets to hit the market (Intel Z3580 - Mooresfield). There was nothing in the way of custom ROMs available, so I maintained a KitKat 4.4.4 ROM for the handful of XDA folks that were using it. Fast forward - I have been using the Yoga Tab 2-830F for about a month, and its story is quite familiar - Intel Z3745 Baytrail, 64-bit Android, also one of Intel's premier devices pushed to devs for its foray into the Android market.
I have been using Android-based devices since 2010, and it's been nothing but fun - handsets, smartphones, tablets, media centers, USB system-on-a-chip and a couple of those tiny set top boxes that go well with XBMC/Kodi. I can't much deal with vendor UI overlays, bloat and the like. Thanks for the work of so many XDA comrades, I have received so much. In return, I'm trying to give some back.
Features
This ROM is based on Lenovo's stock Lollipop 5.0.1 update for the YT-830F (LRX22C/.YT2-830F_USR_S100067_1507101258_WW52_ROW). The image can be flashed via ClockworkMod using the Tethered CWM method. For now, I would all but recommend that you already have the Lenovo Lollipop OTA already in place and are comfortable. The finer points of that process might be malleable later.
ROM Details:
SleepyBear v1 - TBD December 2015
* Android 5.0.1 (modified Lenovo Lollipop stock ROM)
* ROOTed via SuperSU 2.52
* Xposed Framework v78
* NTFS/CIFS filesystem support
* Debloated (Nova Launcher beta instead of Lenovo's UI. The uptick in responsiveness is almost absurd)
* Deodexed
* Zipaligned
* BusyBox
* Init.d
* SD card write fix
* Stock kernel optimized (Interactive governor, cfq scheduler, 512KB read-ahead - Best balance of multitasking, performance and battery life)
* AdAway
* YouTube AdAway (Xposed module)
* YouTube Background Playback (Xposed module)
* Android Terminal Emulator
Installation
1. SleepyBear v1 COMING LATER THIS DECEMBER. LINK WILL BE HERE.
2. Copy the folder to the microSD device of your YT-830F - more than likely /clockworkmod/backup
3. Boot the device to ClockworkMod Recovery using the instructions for the Tethered CWM method.
4.

:good:
From my LG-G4, Rooted running Stock 5.1

Nice stuff. I'm on the Yoga 10 inch (1050F) so I can't really test this ROM, but hopefully this is the start of custom ROMs for the Yoga range.

Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?

1subw00fer1 said:
Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?
Click to expand...
Click to collapse
@1subw00fer1 - correct, there is not yet a download link. I'd like to get some Yoga Tab 2 8-inch owners (YT-810F only for now) to test this out.
Now that I've gotten some sleep, I'm going to put my device back on KitKat, firmware and all, and flash this ROM to make sure both firmware and OS load correctly. It *should*, given that I am using a full ClockworkMod backup that contains boot, recovery, data and a couple of low-level partitions. If that works, then you could do the clean flash via tethered CWM.
I am also using NAndroid Manager to build a full, flashable ZIP that I'll be testing with tethered CWM. I don't see any impediments to doing this. We shall see.
I'll try this with both locked and unlocked bootloader. Details will be added to the main post.
@workdowg - care to test it on the 1050? - we could tweak the partition layout if need be.
Does that answer your questions?

F1Fanatic27 said:
Nice stuff. I'm on the Yoga 10 inch (1050F) so I can't really test this ROM, but hopefully this is the start of custom ROMs for the Yoga range.
Click to expand...
Click to collapse
@F1Fanatic27 - do you have unlocked bootloader on your 1050F? Are you you versed on using the Tethered CWM and doing system image backups, etc.? If so, I'd like some folks to try with this model.

1subw00fer1 said:
Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?
Click to expand...
Click to collapse
I have updated the Installation section with mention of ETA for the first release.

jumpup said:
@F1Fanatic27 - do you have unlocked bootloader on your 1050F? Are you you versed on using the Tethered CWM and doing system image backups, etc.? If so, I'd like some folks to try with this model.
Click to expand...
Click to collapse
Oh yes definitely willing to try it out. I reflashed Lollipop a few days ago so my bootloader's not unlocked at the moment, but I know how to do it so I can get it done in a jiffy. As for CWM, I've been using TWRP for a while now, but a few minutes with CWM and I should be re-accustomed.

F1Fanatic27 said:
Oh yes definitely willing to try it out. I reflashed Lollipop a few days ago so my bootloader's not unlocked at the moment, but I know how to do it so I can get it done in a jiffy. As for CWM, I've been using TWRP for a while now, but a few minutes with CWM and I should be re-accustomed.
Click to expand...
Click to collapse
@F1Fanatic27 - EXCELLENT! Here are a couple of preliminary tasks that will verify CWM:
1. Make a full CWM backup of your device.
2. Reboot and make sure your Android instance is still functioning
3. Perform a full restore of the CWM backup from Step 1.
4. Reboot once more, and make sure Android is still good.
Let me know if that's good.

jumpup said:
@F1Fanatic27 - EXCELLENT! Here are a couple of preliminary tasks that will verify CWM:
1. Make a full CWM backup of your device.
2. Reboot and make sure your Android instance is still functioning
3. Perform a full restore of the CWM backup from Step 1.
4. Reboot once more, and make sure Android is still good.
Let me know if that's good.
Click to expand...
Click to collapse
Well, almost good. The backup was fine, but after the restore the tablet hung on boot and after about 30 seconds loaded recovery instead. :crying:

F1Fanatic27 said:
Well, almost good. The backup was fine, but after the restore the tablet hung on boot and after about 30 seconds loaded recovery instead. :crying:
Click to expand...
Click to collapse
Really? Download and flash the your model's LL OS Loader from the first post.
Damn!
@F1Fanatic27
Was your bootloader locked or unlocked when testing this?

jumpup said:
Really? Download and flash the your model's LL OS Loader from the first post.
Damn!
@F1Fanatic27
Was your bootloader locked or unlocked when testing this?
Click to expand...
Click to collapse
Unlocked.

F1Fanatic27 said:
Unlocked.
Click to expand...
Click to collapse
I would reflash the OS loader for your device. Let's see if that fixes the issue. If this does not fix it, follow that up by locking your bootloader.
In the interim, download your device's last Lenovo OTA update and the Intel Flash utility

jumpup said:
I would reflash the OS loader for your device. Let's see if that fixes the issue. If this does not fix it, follow that up by locking your bootloader.
In the interim, download your device's last Lenovo OTA update and the Intel Flash utility
Click to expand...
Click to collapse
Well reflashing the OS loader and locking the bootloader haven't put me back on track. You mentioned the Intel flash tool and the OTA update which I already have. Anyway I can flash the update without losing data? I tried with stock recovery but it basically told me the build number was wrong (i.e. you're supposed to flash from KitKat to Lollipop, not Lollipop to Lollipop!!) and restoring the Kitkat bios hasn't changed the situation.

F1Fanatic27 said:
Well reflashing the OS loader and locking the bootloader haven't put me back on track. You mentioned the Intel flash tool and the OTA update which I already have. Anyway I can flash the update without losing data? I tried with stock recovery but it basically told me the build number was wrong (i.e. you're supposed to flash from KitKat to Lollipop, not Lollipop to Lollipop!!) and restoring the Kitkat bios hasn't changed the situation.
Click to expand...
Click to collapse
You mentioned previously that you had been using TWRP. For the sake of redundancy, I'd suggest making a full backup with it as well.
With either CWM/TWRP, try restoring only SYSYEM and DATA partitions. See if that help.
If you end up having to restore stock via Intel Flash utility, you can use an app called Online NAndroid Backup and NAndroid Manager to open up the image and manually choose which apps (and data) you want to restore.
You would restore this data after you reapplied the stock image to your system. The apps require root.
Moving forward, I'd also suggest investing in Titanium Backup. Always do a full backup of user, system apps and data. With that, you'd just root your fresh stock and restore with the TB app. I do that for multilayered protection.
I will post the app links later this morning. Gotta get in to the office right quick
Lastly, with the Intel flash util, have you tried restoring just boot and recovery? A partial restore. Don't forget the 'Sparcing' setting.

Thanks again. I already reflashed KitKat and then updated to Lollipop before I saw your post, but the online Nandroid Manager thing sounds shockingly useful!! I'll see about restoring the apps from the backup.
Meanwhile I should probably start using Titanium Backup with this tablet, somehow never thought of doing so as I am with my LG G4.

F1Fanatic27 said:
Thanks again. I already reflashed KitKat and then updated to Lollipop before I saw your post, but the online Nandroid Manager thing sounds shockingly useful!! I'll see about restoring the apps from the backup.
Meanwhile I should probably start using Titanium Backup with this tablet, somehow never thought of doing so as I am with my LG G4.
Click to expand...
Click to collapse
So, you were able to restore your Yoga tablet with the Intel flasher and OWA. Is that correct?
Thanks for boldly going where no Yoga user has gone before.
I am keeping notes on everything and will update you all after I test a few scenarios and options.
For all reading, the following are important prerequisites for a project like this where no custom recovery and the like make the scenario different:
- Titanium Backup: Make a full apps+data backup in Android with this app
- Make a full backup with tethered CWM
-Make another backup with tethered TWRP
I still need direct 830F testers or models close to this.

jumpup said:
So, you were able to restore your Yoga tablet with the Intel flasher and OWA. Is that correct?
Click to expand...
Click to collapse
Yep, Intel flasher for Kitkat and then standard OTA update for Lollipop. Can't wait for the ROM!!

F1Fanatic27 said:
Yep, Intel flasher for Kitkat and then standard OTA update for Lollipop. Can't wait for the ROM!!
Click to expand...
Click to collapse
And, to confirm, you were running Lollipop at the beginning of all this, right?
Sent from my SM-N910T3 using Tapatalk

Status Update: I am working with a few of the better deodex/zipalign/etc dev apps to find one that's a good feel for the Yoga. Things like the following:
http://forum.xda-developers.com/showthread.php?t=2360670
Anyone familiar with these tools that prefer any one over the other?

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

[Root][FIX][S8+]Root Green Screen/Corruption FIXED with AQI1 COMBINATION Boot Firm

Greetings!
Allow me to present to you:
How to Dramatically improve your Rooted S8 Display Quality
And Eliminate the Green/Garbled Screen bug
NOTE: Some users are still experiencing the green/garbled screen issue after flashing.
However all reports of this have indicated that it is happening noticeably less frequently.
Update:
I am looking into this and will have some changes out shortly that will hopefully help. It is difficult for me to troubleshoot because I literally can not get it to happen to my phone anymore so it is difficult to verify improvements before shipping them out to you, but I am doing my best.

WHAT?!
I found the following today while digging around chinese phone firmware sites via baidu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In case you can't tell what that is, it is a BRAND NEW "Combination" Firmware with the label AQI1. The combination firmware is a special factory image used by service workers and XDA members who want to do things like change their CSC or bypass a FRP lock. meaning its almost completely brand new! AQI1 stands for "September 2017", which means this is a brand spanking new image only a few days old!
WHO CARES?
Why is this important? Well it just so happens that the Combination firmware boot image (boot.img) is what we all flashed as part of the SamPWND root. The boot.img file contains the kernel and root filesystem ramdisk. We were running one from sometime around April, which is very old compared to the modern builds most of us flashed after rooting. Furthermore, the image we all are currently running is likely one of the first kernels rolled out for the phone, so its no wonder there was an issue like this that was not fixed (who cares if you get greenscreen in 5m of CSC update).
So all it takes is a simple flash in FlashFire of the AQI1 boot.img (provide at the bottom of this post), an operation that does NOT require a wipe of /system, /data, or anything really (although I recommend a cache wipe in recovery for good measure, but it is very likely not necessary). Your phone will just come back up with a slicker modern kernel and most of all NO MORE ANNOYING DISPLAY BUGS!!!
WHAT IT IS NOT:
Now that I have explained what this thread is about, I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN UPGRADED OS.
This is ONLY the special factory / Combination CSC and diagnostic ROM that has been floating around forever, just a modern build.
It is also the ONLY AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE
I tested this on my S8 G950U but I don't have an s8+ to test with. I imagine that it will work the exact same way but I can't be sure. Hopefully some of you early adopters can share your results with the thread so that we can build some confidence here
NOTE: This is for the s8+ G955 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it. See the other thread if you have a regular S8 US Snapdragon model.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere as I don't have an s8+
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: G955USQU1AQI1 BOOT.IMG
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and factory reset your device tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I will be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: There is an s8 thread in the s8 forums, if you have one of those use that method. There absolutely are binary diffs between versions so SOMETHING is different, and Id rather not have your briked phone on my concious.
SPECIAL THANKS TO:
@elliwigy and @stf_TimelessGoD and the rest of the SamPWND crew for getting us this awesome root in the first place
@elliwigy again for turning me on to the fact that this was a thing at all
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, the tons of you out who have made so many awesome mods, themes, apps, workarounds, tools, etc etc etc. What you have made I use every day and all of it makes me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
BONUS: Here is a link to the entire combination image if you want to take a look at the rest of it. Don't flash the rest of it if you don't know what it is, as it wipes everything and you will have to root from scratch again!
http://goo.gl/pYyg7s

@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again

This can be flashed over AQH3, right ?.

jawonder said:
This can be flashed over AQH3, right ?.
Click to expand...
Click to collapse
why not? as long as its not incremented you are good.. u could prolly even dd it if u want

Working ok for me .

mopartonyg said:
@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again
Click to expand...
Click to collapse
Good idea I will post a rollback tar in case anyone has issues

All seems to be working well, if not, things are more fluid for me. No green screen yet either. Thanks, will continue to report in.

Glad to hear it's working out!
I thought the screen looked better too but I thought it was likely I was seeing things lol

The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.

Great job @wildermjs8 - thanks for the upload ?????

patmorris said:
The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.
Click to expand...
Click to collapse
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img

elliwigy said:
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img
Click to expand...
Click to collapse
I'm perfectly content. It's definitely much better than it was.

Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk

Araltd said:
Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk
Click to expand...
Click to collapse
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol

It's early days with new firmware so we will see

Quickvic30 said:
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol
Click to expand...
Click to collapse
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Sent from my SM-G955U1 using Tapatalk

Araltd said:
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Click to expand...
Click to collapse
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point

elliwigy said:
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point
Click to expand...
Click to collapse
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm

wildermjs8 said:
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm
Click to expand...
Click to collapse
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today

elliwigy said:
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today
Click to expand...
Click to collapse
Except that isn't always the case. Having run pre-release engineering kernels from cupcake-marshmellow I have a little experience in this area, and outside of VERY early days G/Nexus/Pixel never exhibited a problem like this so I find it a bit surprising.
Forgive me for putting the thread in the wrong place, I guess I deserved that for trying putting related things together. Why does it feel like I'm being dragged into a pissing contest?
I was just trying to help people out, maybe I just shouldnt bother.
Mods can move the threads wherever it doesn't matter to me.

Lenovo X606F LineageOS 19.0 GSI Upgrade

Hey Everyone,
Just got my hands on an X606F and as usually I could not stand the stock Android 10 OS.
I eventually took a chance and tested flashing the LineageOS 19 GSI from Andy Yan (Android 12), and it worked out extremely well. Everything worked out of the gate, I installed the version with Gapps preloaded and that worked as well. I basically follow this guide, but swapped the custom rom with the one linked below from Andy Yan.
Use this guide:
https://forum.xda-developers.com/t/...d-11-android-12-and-root-with-magisk.4376127/
only difference is DO NOT INSTALL MAGISK AS THIS ROM IS ALREADY ROOTED.
But Swap CAOS11 rom with the one below here. I personally find LineageOS my favorite of all the alternative ROMs out there so I am happy i got this to work.
Andy Yan's LineagOS GSI build (Use this one)
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
Link to folder with other builds (No Gapps...etc)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
IF anyone has any questions let me know.
Cheers,
SniperFox

Thanks for your post, it is a good news. After reading your post I’m tempted to try this on my X606X. I will probably do when I find some time. Meanwhile, have you observed any issue ?

This sounds like Great News, as I, too, really don't enjoy the Lenovo UI. And... I cannot get OTAs, as I am already rooted with TWRP and Magisk from this forum: httrecovery-tb-x606f-tb-x606fa-unofficial-twrp-3-6-x-for-lenovo-tab-m10-fhd-plus
However, to be certain:
I 'should' be able to then Install LineageOS by copying from the Link Provided above to an ExtSD, along with GApps, and just wipe, and install from TWRP ?
Also, I'm not familiar with the .xz file compression, do I need to convert it to a .zip file ?
Thanks !

Hi, would this version work on TB-X704F ?
Thx.

I’ve tried LineageOS on X606X (LTE version) and I was not lucky. Settings app was crashing each time I went to network settings. Screen was always on or always off. Only way to switch from one to another was to connect or to disconnect USB cable. Any option in settings for screen was not working.
I can confirm that TWRP for TB-X606F/TB-X606FA is working fine on this model.
I tried also CAOS11 but it was a bit laggy. Everything worked, but when I started to mess with Magisk it didn’t want to boot anymore. So I’m back to stock, and confident that one day I will find working Android 12 for this model.

I'm going to plop this question down here, but it's only sort of relevant: what is going on with the navigation bar? My home/back/recents button are all in the bottom right corner of the bar and in the centre are icons for play store, camera, and something else.
How do I go back? I can't find any of the options. I tried this ROM, CAOS11, and an AOSP flavour, and they all had the navbar set up that way. All the other ROMs also crashed the Phh-Treble UI Tuner whenever I tried to change the navbar. I went back to stock, and it returned to normal. Is this an Android 11+ thing? It's awful.

SniperFox22 said:
Hey Everyone,
Just got my hands on an X606F and as usually I could not stand the stock Android 10 OS.
I eventually took a chance and tested flashing the LineageOS 19 GSI from Andy Yan (Android 12), and it worked out extremely well. Everything worked out of the gate, I installed the version with Gapps preloaded and that worked as well. I basically follow this guide, but swapped the custom rom with the one linked below from Andy Yan.
Use this guide:
https://forum.xda-developers.com/t/...d-11-android-12-and-root-with-magisk.4376127/
only difference is DO NOT INSTALL MAGISK AS THIS ROM IS ALREADY ROOTED.
But Swap CAOS11 rom with the one below here. I personally find LineageOS my favorite of all the alternative ROMs out there so I am happy i got this to work.
Andy Yan's LineagOS GSI build (Use this one)
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
Link to folder with other builds (No Gapps...etc)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
IF anyone has any questions let me know.
Cheers,
SniperFox
Click to expand...
Click to collapse
Thanks so much.
Everything worked out without a hitch.
But how do I edit or get rid of those apps in the navigation bar??? They're an eyesore and pretty useless to me.

sirp0p0 said:
I'm going to plop this question down here, but it's only sort of relevant: what is going on with the navigation bar? My home/back/recents button are all in the bottom right corner of the bar and in the centre are icons for play store, camera, and something else.
How do I go back? I can't find any of the options. I tried this ROM, CAOS11, and an AOSP flavour, and they all had the navbar set up that way. All the other ROMs also crashed the Phh-Treble UI Tuner whenever I tried to change the navbar. I went back to stock, and it returned to normal. Is this an Android 11+ thing? It's awful.
Click to expand...
Click to collapse
Holy crap. You read my mind.
What a waste!

Nice to see so many people experimenting with this tablet. It would be nice if we had a dedicated subforum for this device.
I have been trying out several ROMs/GSIs with Android 11 and 12, but all of them are performing really laggy after a couple of days. Overall system perfomance and latency seems slow and choppy.
Especially YouTube is very laggy and shows heavy artifacting on almost every video making me think a lot of ROMs cant make proper use of hardware codec acceleration.
Another problem is getting Netflix to work, whereas on the stock ROM I had 1080p playback with a modded apk, on other custom ROMs I cant even launch the app, sadly no success with the Kodi Netflix add-on either.
My plan was to see if I could improve perfomance by removing Lenovo's bloat and using microg to replace gapps, but it turned out perfoming worse than before.
Maybe this device is just too weak for this kind of modding.
Thoughts on these issues? And which ROMs have you personally enjoyed? I think I might go back to stock for now, give the roms some time to develop further and try again at the end of the year.

Zelodos said:
Nice to see so many people experimenting with this tablet. It would be nice if we had a dedicated subforum for this device.
I have been trying out several ROMs/GSIs with Android 11 and 12, but all of them are performing really laggy after a couple of days. Overall system perfomance and latency seems slow and choppy.
Especially YouTube is very laggy and shows heavy artifacting on almost every video making me think a lot of ROMs cant make proper use of hardware codec acceleration.
Another problem is getting Netflix to work, whereas on the stock ROM I had 1080p playback with a modded apk, on other custom ROMs I cant even launch the app, sadly no success with the Kodi Netflix add-on either.
My plan was to see if I could improve perfomance by removing Lenovo's bloat and using microg to replace gapps, but it turned out perfoming worse than before.
Maybe this device is just too weak for this kind of modding.
Thoughts on these issues? And which ROMs have you personally enjoyed? I think I might go back to stock for now, give the roms some time to develop further and try again at the end of the year.
Click to expand...
Click to collapse
Hi @Zelodos, thank you so much for the feedback about custom ROMs you've been messing around with.
I'm the owner of a Lenovo TB-X606F tablet (Lenovo Tab M10 FHD Plus) experiencing the Netflix issue that prevents me from watching content at 1080p resolution. With DRM Info app, I've checked that the Security Level of mine is L3, whereas yours and some others' tablets (which are exactly the same model: TB-X606F) are L1...
Could you tell me which FW version is running your tablet? I've been reading on Lenovo Forums for a while and I've picked up the two most relevant posts relating this issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://forums.lenovo.com/topic/findpost/1088/5020213/5502643
GitHub Link for the Netflix modded apk: https://github.com/longseespace/netflix_patch/releases
https://forums.lenovo.com/topic/findpost/1088/5050995/5294237
I wonder if flashing the TB-X606F_S300429_211101_BMP firmware version can make a difference for me to get L1 Security Level, instead of L3... Or maybe the FW version your tablet is running currently can sort it out, I don't know. Just let me know, please. Thanks in advance.

SniperFox22 said:
Hey Everyone,
Just got my hands on an X606F and as usually I could not stand the stock Android 10 OS.
I eventually took a chance and tested flashing the LineageOS 19 GSI from Andy Yan (Android 12), and it worked out extremely well. Everything worked out of the gate, I installed the version with Gapps preloaded and that worked as well. I basically follow this guide, but swapped the custom rom with the one linked below from Andy Yan.
Use this guide:
https://forum.xda-developers.com/t/...d-11-android-12-and-root-with-magisk.4376127/
only difference is DO NOT INSTALL MAGISK AS THIS ROM IS ALREADY ROOTED.
But Swap CAOS11 rom with the one below here. I personally find LineageOS my favorite of all the alternative ROMs out there so I am happy i got this to work.
Andy Yan's LineagOS GSI build (Use this one)
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
Link to folder with other builds (No Gapps...etc)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
IF anyone has any questions let me know.
Cheers,
SniperFox
Click to expand...
Click to collapse
Hello I have a problem installing custom ROMs on this specific tablet mate. When CAOS 11 or any other custom ROM is installed and I want to reboot, TWRP brings a message that OS is not installed do you want to reboot? Then sticks twice at Lenovo logo and boots to TWRP.... It doesn't boot at the custom ROM...

vassiliszacharis said:
Hello I have a problem installing custom ROMs on this specific tablet mate. When CAOS 11 or any other custom ROM is installed and I want to reboot, TWRP brings a message that OS is not installed do you want to reboot? Then sticks twice at Lenovo logo and boots to TWRP.... It doesn't boot at the custom ROM...
Click to expand...
Click to collapse
My suggestion is to use the Lenovo recovery tool linked here. (Lenovo's tool is very good and its hard to brick these, so good job there at least)
Rescue and Smart Assistant (RSA) - Lenovo Support CA
pcsupport.lenovo.com
Then use this tool to reset the tablet to the stock OS. Most likely what happened is you tried to flash an OS that was built on a different version of Android. Make sure that your using a build that is based on the right version of Android. After you do that recovery you should be up to Android 10, as it uses the latest image for the tablet. This means you need to use a CAOS 10 not CAOS 11. You will need to reinstall TWRP first again, as this will be removed when you recover. Let me know if you have issues and Ill keep an eye out for any new posts.
Cheers,
Sniper Fox

SniperFox22 said:
My suggestion is to use the Lenovo recovery tool linked here. (Lenovo's tool is very good and its hard to brick these, so good job there at least)
Rescue and Smart Assistant (RSA) - Lenovo Support CA
pcsupport.lenovo.com
Then use this tool to reset the tablet to the stock OS. Most likely what happened is you tried to flash an OS that was built on a different version of Android. Make sure that your using a build that is based on the right version of Android. After you do that recovery you should be up to Android 10, as it uses the latest image for the tablet. This means you need to use a CAOS 10 not CAOS 11. You will need to reinstall TWRP first again, as this will be removed when you recover. Let me know if you have issues and Ill keep an eye out for any new posts.
Cheers,
Sniper Fox
Click to expand...
Click to collapse
Cheers Sniper. Indeed I returned back to stock ROM by using Lenovo tool that is very easy to install it. I installed TWRP 3.6.x for Lenovo Tab M10 FHD Plus which is suitable for Android 11 and Android 12. Can I ask you please what was your procedure of installing Android 12 custom ROM on that tablet?

vassiliszacharis said:
Cheers Sniper. Indeed I returned back to stock ROM by using Lenovo tool that is very easy to install it. I installed TWRP 3.6.x for Lenovo Tab M10 FHD Plus which is suitable for Android 11 and Android 12. Can I ask you please what was your procedure of installing Android 12 custom ROM on that tablet?
Click to expand...
Click to collapse
I would try Andy Yan’s Lineage OS GSI builds. Those are generally where you want to start as those are more likely to be compatible. Also make sure when you flash the custom rom you follow the directions from that original link closely. If you miss a step it’s easy to screw it up where it does what you said and either boot loops or doesn’t see the OS. I think you might be limited to lineage OS version 19 with this tablet. Newer OS might not work.

Added comment. I have also tried Ubuntu Touch and it works well on this tablet. Wifi, Bluetooth, audio all work, as does charging. Although the app market for Ubuntu touch is not great it seems to be getting better.

SniperFox22 said:
Added comment. I have also tried Ubuntu Touch and it works well on this tablet. Wifi, Bluetooth, audio all work, as does charging. Although the app market for Ubuntu touch is not great it seems to be getting better.
Click to expand...
Click to collapse
How did you manage this mate? Also when I am trying this command after install TWRP: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is not recognised... How can you overpass this? Maybe this is my problem. I just installed vbmeta without disable it .. Any ideas?

vassiliszacharis said:
How did you manage this mate? Also when I am trying this command after install TWRP: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is not recognised... How can you overpass this? Maybe this is my problem. I just installed vbmeta without disable it .. Any ideas?
Click to expand...
Click to collapse
I think your problem is related to this part of the instructions
"After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data."
If you don't boot directly back into TWRP after installing and wipe -> format data you will get that error.
As far as the installation of the Ubuntu Touch, you NEED to be on Android 9 to install it. So you have to downgrade to the original firmware that was Android 9. When you do the Lenovo recovery unfortunately it only give you the newest Android 10 rom. So you need to download the historic ROM for this tablet that is Android 9. Then its as easy as running the Ubuntu Touch installer on your PC. If you try to do it with Android 10 on the device to start it will fail. Ubuntu touch is pretty cool.

cheers mate for your help! respect. Is there any android 12 custom ROM we can use on this tablet?

been using lineage 19.1 on my tb-x606f and is really smooth, but I don´t know what SU app could use. I tried flashing magisk but it creates a conflict with the rom itself.

Does anyone have a download for the boot.img? I would love to do this but cant find a boot image to use for the vbmeta.img

Database Users

welcome