• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][UNOFFICIAL] LineageOS 14.1 for Lenovo Tab 3 8/TB3-850F

Search This thread
I respect such ROM devs who respect Google's directive and concession (that originally saved CM) that proprietary GApps should be loaded separately by end user (with licensed device) and not distributed with any ROM.

I'm not sure if there's any benefit from pre-rooted builds. They often cause difficulty / issues updating Magisk / ROM (see Magisk Discussion thread) especially when unpatched boot image is not available, and because John didn't design Magisk to be part of system.

It'll be very happy to see / interested in any development you produce! Many thanks in advance. 👍 PW
I dislike pre-rooted builds myself. When I say a rooted build, I am speaking of a build in which the TWRP ROM installer includes a script to install Magisk systemless root as soon as the ROM installation is complete. That way, boot image patching takes place at the time of installation and future Magisk updates won't be buggy or problematic. It's an option for the lazy guy more or less. I always like to make builds without GApps, without root, and without any modifications not already baked in. You and I are on the same page there. The rooted build with Magisk script installer included is nothing more than a lazy man's/woman's convenience, but never technically a pre-rooted build. As you pointed out, those are always problematic in some respect.
 
  • Like
Reactions: pndwal

pndwal

Senior Member
I dislike pre-rooted builds myself. When I say a rooted build, I am speaking of a build in which the TWRP ROM installer includes a script to install Magisk systemless root as soon as the ROM installation is complete. That way, boot image patching takes place at the time of installation and future Magisk updates won't be buggy or problematic. It's an option for the lazy guy more or less. I always like to make builds without GApps, without root, and without any modifications not already baked in. You and I are on the same page there. The rooted build with Magisk script installer included is nothing more than a lazy man's/woman's convenience, but never technically a pre-rooted build. As you pointed out, those are always problematic in some respect.
Interesting. Does script allow user to choose unrooted? PW
 
I'll post a bare-bones, GAppless and unrooted ROM this week, with a more current security patch level. From there I can release builds as bugs are ironed out and instabilities are improved. For the most part, the ROM seems to be pretty stable. I see from the source code that it was originally ported to the 850M by the guys at 4PDA. Good group of devs over there. So, some WiFi-only changes need to made and the telephony settings layer removed.
 
Interesting. Does script allow user to choose unrooted? PW
Sure. It's based on an Aroma installer. Root or non-root. If rooted is chosen there is an insecure boot support option, init.d support option, adbd option, su.d, BusyBox, etc. You can opt for exactly what you want. But the top default option is simply unrooted and unmodified.
 
  • Like
Reactions: pndwal

pndwal

Senior Member
Sure. It's based on an Aroma installer. Root or non-root. If rooted is chosen there is an insecure boot support option, init.d support option, adbd option, su.d, BusyBox, etc. You can opt for exactly what you want. But the top default option is simply unrooted and unmodified.
Thanks for enlightenment. All sounds good if can be implemented w/o issues. 👍 PW
 
  • Like
Reactions: Viva La Android
Thanks for enlightenment. All sounds good if can be implemented w/o issues. 👍 PW
I've used the setup for years on

Thanks for enlightenment. All sounds good if can be implemented w/o issues. 👍 PW
If you have ever installed any ElementalX custom kernels on Android devices, the TWRP installer is outfitted in Aroma format. The installer walks the user through multiple options like Overclocking, DT2S, Thermal Control, CPU Governor, Fast Charging, SELinux Permissive, etc. The kernel is installed with all of your choices preset. Some custom audio installers like some Dolby Atmos builds use Aroma installers as well. They're very handy.
 

pndwal

Senior Member
If you have ever installed any ElementalX custom kernels on Android devices, the TWRP installer is outfitted in Aroma format. The installer walks the user through multiple options like Overclocking, DT2S, Thermal Control, CPU Governor, Fast Charging, SELinux Permissive, etc. The kernel is installed with all of your choices preset. Some custom audio installers like some Dolby Atmos builds use Aroma installers as well. They're very handy.
Sounds great!

I've read about ElementalX, but only in relation to old fixes for f2fs loopback bug etc.

I use Xiaomi devices currently. Are there ElementalX implementations for these now? PW
 
Sounds great!

I've read about ElementalX, but only in relation to old fixes for f2fs loopback bug etc.

I use Xiaomi devices currently. Are there ElementalX implementations for these now? PW
Good question. The dev maintains a website that lists all supported devices. I'll check it out. I've been interested in Xiaomi for some time, but to date I've never owned one. What is a good solid Xiaomi you wouid recommend for an affordable price?
I checked the ElementalX site. The Xiaomi Redmi Note 3 is supported for the ElementalX kernel.
Three kernel builds are available for the Redmi Note 3, one for Marshmallow, one for Nougat and one for Oreo. The build is chosen in accord with your Android version.
 
Last edited:
  • Like
Reactions: pndwal

pndwal

Senior Member
Good question. The dev maintains a website that lists all supported devices. I'll check it out. I've been interested in Xiaomi for some time, but to date I've never owned one. What is a good solid Xiaomi you wouid recommend for an affordable price?
I checked the ElementalX site. The Xiaomi Redmi Note 3 is supported for the ElementalX kernel.
Three kernel builds are available for the Redmi Note 3, one for Marshmallow, one for Nougat and one for Oreo. The build is chosen in accord with your Android version.
I use Redmi Note 8T and older Mi Pad 4, both old but response enough for me.

Great hardware for pricepoint, easily to unlock, just not a fan of MIUI. So check specs / XDA custom support, choose Qualcomm soc and take a punt.

Be aware Emergency download mode is only available for a few agents with "authorized account" if you hardbrick, but this is generally only an issue on MediaTek models which are extremely easy to brick - I did it twice on Redmi 6 just flashing a TWRP and was able to pay a technician in Vietnam to fix via Team Viewer (@ $20 a pop). Haven't modded those MTek devices since as that tech service and most others first had to start paying Xiaomi per use (requires users account and techs authorized account to be logged in to Xiaomi server while performing Emergency Download flash), and later lost or let authorized status lapse. They're like hen's teeth now.

But I've never Hard Bricked Qualcomm. 😉 PW
 
I use Redmi Note 8T and older Mi Pad 4, both old but response enough for me.

Great hardware for pricepoint, easily to unlock, just not a fan of MIUI. So check specs / XDA custom support, choose Qualcomm soc and take a punt.

Be aware Emergency download mode is only available for a few agents with "authorized account" if you hardbrick, but this is generally only an issue on MediaTek models which are extremely easy to brick - I did it twice on Redmi 6 just flashing a TWRP and was able to pay a technician in Vietnam to fix via Team Viewer (@ $20 a pop). Haven't modded those MTek devices since as that tech service and most others first had to start paying Xiaomi per use (requires users account and techs authorized account to be logged in to Xiaomi server while performing Emergency Download flash), and later lost or let authorized status lapse. They're like hen's teeth now.

But I've never Hard Bricked Qualcomm. 😉 PW
So on a development standpoint and the less common phenomenon of hard bricking, go for a Qualcomm SoC. So does Xiaomi provide official bootloader unlocking support? Thanks for the info. I'm.also not a MIUI fan.
 

pndwal

Senior Member
So on a development standpoint and the less common phenomenon of hard bricking, go for a Qualcomm SoC. So does Xiaomi provide official bootloader unlocking support? Thanks for the info. I'm.also not a MIUI fan.
Yup. In fact development on Xiaomi MTek devices has often ground to a halt / not started because of this fixing issue. You can appreciate Devs want to recover brick w/o paying or visiting Xiaomi service dept. every time. 😬. Unmodified SP Flashtool simply won't work in power off or battery disconnected (Emergency Download) mode on Xiaomi devices.

It's the same for QCom in fact, but in practice seldom an issue.

Xiaomi cite security concerns (correctly in fact) as hack tests have demonstrated that using certainly vulns, the wipe data requirement when unlocking bootloader can be completely bypassed and then data is accessable on stolen devices, hence their insistence on logged in emergency download flashing use.

Bootloader unlock is easy and official using their unlock tool. Requires registering device with a Mi account and logging in for unlock ticket, then generally a 168 hour mandatory wait period, log in again after this expires and you can immediately unlock. 😜 PW
 
  • Like
Reactions: Viva La Android
Yup. In fact development on Xiaomi MTek devices has often ground to a halt / not started because of this fixing issue. You can appreciate Devs want to recover brick w/o paying or visiting Xiaomi service dept. every time. 😬. Unmodified SP Flashtool simply won't work in power off or battery disconnected (Emergency Download) mode on Xiaomi devices.

It's the same for QCom in fact, but in practice seldom an issue.

Xiaomi cite security concerns (correctly in fact) as hack tests have demonstrated that using certainly vulns, the wipe data requirement when unlocking bootloader can be completely bypassed and then data is accessable on stolen devices, hence their insistence on logged in emergency download flashing use.

Bootloader unlock is easy and official using their unlock tool. Requires registering device with a Mi account and logging in for unlock ticket, then generally a 168 hour mandatory wait period, log in again after this expires and you can immediately unlock. 😜 PW

Thank you so much for the valuable info. This week coming im making my first Xiaomi purchase. You have me very excited to take the jump.
 
Hey @pndwal, I was just looking over the bootloader unlock, TWRP & root instructions for the 850F. @comfortable brought my attention to it as he is preparing to root his tablet. Looks like we could be overdue for an updated thread. The guide still uses SuperSU. What do you think? I think Magisk should be used on current root guides since it's technically the only supported and maintained root strategy nowadays.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    LineageOS 14.1 Port ROM
    Lenovo Tab 3 8"/TB3-850F


    •WARNING:
    You are installing this custom Android ROM at your own discretion and risk. If you are unclear on anything, please stop and do some research before proceeding further. This is not a Q & A thread, so please post comments on topic with subject matter relating directly to this ROM. I will not be held responsible for devices which become bricked or damaged as a result of installing this ROM. You are encouraged to read and re-read the OP prior to installing this ROM on your device. Please visit this thread for now to make general inquiries about this ROM or about any other questions or issues you may have regarding the 850F. Either myself or XDA Senior Member @pndwal, who is very knowledgeable about this device and Android in general, will try to address your questions. https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 User input and feedback are essential in making improvements, fixing bugs, and in helping development for this device to continue to evolve.
    Any skilled devs interested in contributing in any way to development for the 860F, please use the above thread to contact @pndwal and coordinate with him in that area.

    I am not a developer, nor did I contribute to the porting of this LineageOS 14.1 custom ROM for the TB3-850F. I merely packaged up the files, added GApps Pico, made a few minor tweaks, and created a TWRP flashable zip installer for this ROM. Please do not request updates or make ETA type inquiries on this thread. Whether or not this ROM will be maintained is still up in the air. Please give any and all credit to the individuals I have listed below under Mentions & Credits.

    LineageOS 14.1 is a free, aftermarket distribution of Android 7.1.2 Nougat, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many individuals within the Android community. Although this particular LineageOS build does have GApps Pico preinstalled, it can be used without any need to have any Google application installed. LineageOS does still include various hardware specific code, which is nonetheless slowly being open-sourced anyway.

    SOURCES:
    LineageOS Source Code: https://github.com/LineageOS

    Kernel Source Code: https://support.lenovo.com/us/en/downloads/ds112711

    LineageOS Gerrit Code Review: https://review.lineageos.org/q/status:open

    FEATURES & SPECS:
    •LineageOS Version: 14.1
    •Android Base Version: 7.1.2_r8 Nougat
    •Build ID: N2G470
    •SDK Version: 25
    •Build Date: May 15, 2017
    •Security Patch Level: May 5, 2017
    •Kernel Version: 3.18.19 (mods by @wezroot2k)
    •LineageOS API Level: Guava (7)
    •GApps Pico Pre-installed
    •Insecure Boot Image Support
    •Force Encryption Disabled (Opt-Encrypt)
    •AVB/dm-verity Disabled
    •Fully Deodexed
    •Fully Zip-aligned
    •User Opt Root or Non-Root
    •Status: Unofficial/Stable

    WORKING:
    •Booting
    •WiFi
    •Bluetooth
    •Graphics/Video Playback
    •Audio
    •GPS/Location Services
    •GApps
    •Magisk Universal Systemless Interface

    BUGS:
    I am presently working on Settings UI to omit the mobile networks/telephony entries. These are present because this ROM was originally a smartphone port. Otherwise, please feel free to submit a proper bug report or, at a minimum, a clear description of the bug or instability, including screenshots if possible.
    A bug has been reported for apps that require superuser permissions (Greenify, root file managers, etc), and I have determined that installing the latest Magisk systemless root will alleviate that bug.
    Upon initial boot, during setup, you may experience an issue with Setup Wizard force closing. I have posted a quick workaround for this below under the Installation Instructions heading.

    REQUIREMENTS:
    You need an unlocked bootloader and TWRP custom recovery installed. If you need help with either of these topics, please visit this thread for guidance: https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786

    INSTALLATION INSTRUCTIONS:
    1. Download the ROM zip from the below download link and save it to your device storage...
    2. Boot your device into TWRP recovery mode...
    3. Wipe Data, Cache & Dalvik/ART (my installer automatically formats the /system partition)...
    4. Select Install, navigate to saved location of the ROM zip, select it and swipe the action bar to begin installation...
    5. Reboot system (installation will take around three minutes).

    *Because this ROM is fully deodexed, first boot can take several minutes to complete while the Dalvik/ART directories are being written for the first time. The second and subsequent boot times will be much faster. Also, on first boot, select your language then choose SKIP on the Insert SIM Card screen. You will then be prompted to set up your device as new or copy data from another device as part of setup. At this stage, if the Setup Wizard force closes, swipe down from the top of the screen to access Quick Settings and go ahead and connect to a WLAN/WiFi network. Now, go back to the previous screen and Setup Wizard should function normally and allow you to proceed with setup of your device. I am presently working on removing SIM/Mobile Network settings on this device, so hopefully this will be fixed soon, and a true WiFi-only tablet port will be yielded.

    **As mentioned supra, this ROM is packaged with GApps Pico, which provides the bare bones minimum for Google Play functionality. If you want a GApps package other than the one preinstalled, visit https://opengapps.org/, choose ARM64, Android 7.1, and select your preferred package. Simply install the GApps package after Step 4 above. If you want root, visit the official Magisk release & announcement thread here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, and download the latest Magisk Manager apk. Install the apk, go to Developer Options and enable Apps & ADB in the root options menu. Open Magisk Manager, select Install, pick the direct install option, and systemless root will be installed via patched boot image. Reboot and systemless root should be properly installed & stable. Be sure and hit the Thanks button on @topjohnwu's thread if you use Magisk.


    MENTIONS & CREDITS:
    This port was made possible by a number of individuals both here at XDA and abroad:
    - Credit goes to 4PDA (Russian Development site) member chipa76 for the original TB3-850M port, and to 4PDA member al_rus for his contributions to, and for posting that port.
    - Credit and thanks for the breakthrough moment for TB3-850F users must go to XDA member @wezroot2k who, after others tried for many months, was finally able to stabilise this ROM for our device by recompiling the ported boot image with TB3-850F stock kernel. Also, he has worked on tweaks to streamline the ROM for TB3-850F.
    - TWRP flashable ROM package as well as some tweaks to streamline the ROM for TB3-850F have been made by the OP, @AeonFlux1603, who will continue to work on a few further improvements, insomuch as spare time will allow
    - Thanks to XDA Senior Member @pndwal for his dedication to this device and for passing on suggestions from the 4PDA Devs regarding the adopted method of stabilising ROM for TB3-850F.
    - Last but not least, thanks and credit goes to the entire LineageOS Dev Team for making this custom aftermarket distribution of Android possible for low-grade, mid-grade & flagship devices alike.

    DOWNLOAD LINK:
    LineageOS 14.1 for TB3-850F: https://drive.google.com/file/d/1bbpwyvP_S4k1PJaLa6RN3dFDF8UYEcNj/view
    3
    Update on the Settings UI. I now realize that my issues were due to my failure to properly encode my edits of the relevant .XML files with UTF-8 encoding prior to repackaging. As I may have mentioned previously, I am interested in bringing this port up to date with the latest upstream sources. So my next build release will hopefully include current LOS sources and have the Settings UI ironed out. While progress is not nearly as quick as I'd like, I am working on it.
    3
    App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
    I've found even if it times out, or can't connect when sending, things are generally handled properly by Labs app, a message appears that 'send failed', and text is all still there allowing further attempts.

    However, the space-substituted-for-*-symbol problem (when copying and pasting) will truncate the post and successful send in one operation. This means a large portion of text is often lost and irretrievable. (Also, the * symbol still shows as a space while editing, so one doesn't realise that the space has been substituted until its too late.)

    Great advice to copy all before sending. PW

    ---------- Post added at 06:17 AM ---------- Previous post was at 05:22 AM ----------

    @wezroot2k, @AeonFlux1603

    TB3-850F users are privileged, blessed, ecstatic, proud, happy and very thankful to have two budding (though clearly possessed of valuable experience and practical knowledge) developers on board the Good Ship TB3-850F, and its been a long time coming!

    Thank you both especially for Stable and Virtually Bug Free Port to LOS14.1 for TB3-850F, as well as for other valuable resources we are gaining - including this new thread for our brand new Lineage Operating System!

    Your sincere expressions of thanks / praise for helpful posts are also much appreciated.

    Just a small heads-up (and sorry to spell it out) - Please don't neglect the 'thanks' (thumb up) button when a post is useful, or a sincere attempt to help is made. This is kind of the expected / default expression of thanks around here, and is possibly the most sincere form of flattery as it also elevates a members XDA profile. It's a simple and immediate way to say 'thanks', and often makes further comment unnecessary. (Incidentally, thanked posts are indexed, and are often perused for helpful information.)

    Many thanks, and loving your work! PW :good::good::good::good::good:
    3
    I still saw some mention about bugs, but I'm not understand what they are because of Google translate. Besides, Can I flash this on 850M? I don't have intention of using any SIM-related service.
    Yes, I read about LOS14.1 TB3-850M bugs on 4pda too, but I think most are gone in ver. 3. I was just wondering what bugs you have found remaining with latest build on 850M.

    Not a good idea to flash on 850M as kernel is different, which is why we had bootloops and instability before we got boot.img for 850F, so I think you will have similar problems using ROM with 850F boot.img on 850M.

    However, if you really want to try this ROM, you could extract boot.img from TB3-850M LOS14.1 ROM, then flash TB3-850F ROM immediately followed by boot.img from 850M.
    About the Zirene, I also see that on the thread and looks like the app cannot work reliably on android version bigger than 6, the dev also said that Zirene is too old.
    I see. That may be the problem then. PW
    3
    Hey there.
    Thanks a lot to @AeonFlux1603 for this LOS ROM.
    I would like to try it out but would like to know if there are any known bugs/annoyances that might detract me from installing it.
    Also, this tablet is my daughter's tablet. Her being 'minor aged' I would like to have a kid's mode for her where she can only use the apps/games that I approve and prevent her from browsing the web, etc. Is there such a kids mode in LOS 14.1?
    Hope @pndwal or anybody using the rom can clarify these two issues.
    And, by the way @AeonFlux1603, are you planning on releasing security updates for this ROM? Is a LOS 15 in the works? LOS 14.1 should now stop receiving security updates, right?
    Thanks in advance.
    Cheers

    In terms of annoyances, I would have to say that reduced battery life is my #1 pet peeve. I have been trying to track it with GSam Battery Monitor, and it seems to arise because the OS is constantly trying to power the phone radio for an LTE connection that doesn't exist on the TB3-850F tablet. The "phone radio" category of the battery monitor shows a significant power draw, even after I switch to Airplane Mode. This must be a legacy from the origin of this ROM in the TB3-850M hardware.

    I tried using the dialer to enter *#*#4636#*#* and then bring up "Phone Information", which does give an option to switch off "Cellular Radio Power". But that is only temporary, and the slider switch goes back to "On" immediately as soon as you leave the testing app.

    Early in this thread (post #16), @AeonFlux1603 mentioned that he was updating the rom to remove all the LTE vestiges of the TB3-850M that exist, but I'm not sure that he actually got to that point. It's possible that he did, and that I'm accidentally running an obsolete version of this ROM that still contains all the LTE phone radio stuff. But I don't see any reference to that issue in this thread after post #16.

    Could someone please clarify the most current version of this ROM? Mine shows security patch dated May 5, 2017, and LOS version 14.1-20170515-UNOFFICIAL-TB3-850M.

    As for "Kids' Mode", that is no longer a category that you set up through the settings app on the tablet. You can add new users with their own apps & content, or set up a restricted profile, or download an app for this purpose from the Playstore. But the stock "Kids' Mode" from the stock rom is gone.