Related
My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
i jus got my elocity a7
i tried to mod mine with the dexter mod 1.41 and mines wont work,
1st- i download the file didn't unzip it then i sent it to the SD card and rename it "update.zip".
2nd- i did the factory wipe/reset then i select to wipe all data
3rd- i select update.zip but i notice an message saying( E. can't read from SD card). i dont know if that is apart of the mod or what.
4th- when it is finish then i select reboot option and when it is done rebooting i get nothing new. can you help me out are do you know something that i might be doing wrong. i also did do the 1.42 patch aswell didn't work. are is there another mod that you can tell me how to get it.
hasn't been tested for application on dexter's rom, though i don't know of reason they shouldn't work. gapps can be flakey like that; actually, the files are all stock as they come from cyanogen, minus my patched market, which doesn't have any reason not to work on dexter's rom and has nothing to to with the installation of the rest of google applications, including the calendar and text messaging services; i introduced no signature issues else it wouldn't install on stock firmware.
what i can suggest, is that if you're doing this under wiped conditions; is that you need to do a "factory reset" in recovery AFTER applying my gapps update.
if you don't do the factory reset, there will be settings put in place by the provision.apk in dexter's rom (not sure if this has changed in 1.42) that may conflict with the setup of google-apps. it didn't w/ the gapps in v1 i ported from dexters rom in previous tests, but i was going for a vanilla install w/out mixed signatures/versions/dates. provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
sorry if that was too much info. i do that.
EDIT: i reviewed my original post, its step *2B*. i did update it to underline it, and provide explanation for its probable necessity.
bestialbub said:
provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
Click to expand...
Click to collapse
SetupWizard.apk replaces "provision.apk".
bestialbub said:
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
Click to expand...
Click to collapse
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
SetupWizard.apk replaces "provision.apk".
Click to expand...
Click to collapse
thanks for the tip. i did concede i could be wrong, and you're right, i could find that small detail that setupwizard is known to replace functions for provision.apk. the same posts i'm finding on xda and cyanogenmod don't say anything about googlepartnersetup, however, yet its provided with gapps packages..
i also learn from demonstrated and practiced examples..
demonstrated examples i learned from, including your 1.2 rom shows your remove provision.apk and provide googlepartnersetup.apk, then reverse the decision in 1.4, i ASSUME based on signiture issues you had stated (i generally don't have those as i know i can re-use existing containers without having signature issues).
i also learned/ported from various sdk's, including google's sdk for gapp imports, and neither is required, but what is provided is sdksetup.apk.. me seeing a relation from sdksetup for an sdk/emu android device kinda indicates one might want googlepartnersetup as a counterpart on a physical device. (your 1.4 example does prove that doesn't have to be true).. but the google sdk shows that i don't need setupwizard.apk for google services either.
thought i'd relate, since most the general posted information i've seen on xda and cyanogenmod seem like vague gueses at best. though i suspect the people posting this information aren't necessarily the devs working closely with the files. just hobbists and modders making educated guesses like me.
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
Click to expand...
Click to collapse
i was refering to MY gsm provided build prop information, i wasn't ragging on your build prop or rom addons. i followed suit to the gtab tnt modrom and added DIFFERENT gsm provider information than yourself (service provider id, not google client information). but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
i do concede to the thread discussion, tho, DEXTERS ROM IS THE BEST AND ONLY FULL ROM MOD FOR THE A7 TABLET!!!
my gapps mod is only intended to provide google applications ommitted by the manufacture. nothing more.
thanks for the indirect market patching instructions!
thanks am going to retry and see what happends
bestialbub said:
but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
Click to expand...
Click to collapse
Had the same issues, so i found the trick to be adding it in the boot.img using the default.prop, and it is added during bootup.. but now we're OT! so let's leave it at that.
a7 installation problem
these are the exat message i got (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
why post the same thing every 10 minutes?
.............................
demamalu said:
My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
Click to expand...
Click to collapse
That is not a mod it's the factory firmware with a patch to get market, I don't see in what way it is better than Dexter mod.
kevinppk said:
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
Click to expand...
Click to collapse
When this happen I remove the .zip from file name or just rename the file but most time removing. .zip does the job...
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
EncryptedCurse said:
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
Click to expand...
Click to collapse
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Eclipsys said:
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Click to expand...
Click to collapse
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
jimyv said:
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
Click to expand...
Click to collapse
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Eclipsys said:
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Click to expand...
Click to collapse
I didn't have any problem doing the modifications myself and I'm no Pro that's for sure. Never written a line of code in my life. I just tend to thoroughly research and understand before I attempt things and I've been practicing here for a while if you go to the, rollback .0.1 and safestraped thread there is quite detailed instructions serval times throughout the thread I would skim it.you will just be substituting version numbers and kind of a inverse idea compared to what we were doing there but it should accomplish it. I used rOM Toolbox lite I believe as an editor and saved each timeI didn't have any problems with the permissions getting screwed up while tampering with it rOM Toolbox took care of that issue. I have seen tons of people brick trying to make these modifications. But I don't think they understood completely what they were attempting to do it's actually very simple and as long as you do it thoroughly and get all of them changed I have not seen any problems other than maybe having to repeat the process.there are a couple of lines that only use the last section of your version numbers I even changed those back then.
Eclipsys said:
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Click to expand...
Click to collapse
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
p1gl3t said:
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
Click to expand...
Click to collapse
https://mega.co.nz/#!wlQl2bZD!Kk-rcWtcMPWxoEH5VcHrtZb7nOsJet9si1pm5FYhT44
5.2 build prop file
Hello!
Normally when I come on the XDA forums, I am asking a question, because I end up making a silly mistake in Android. I never like to put out promotional content for attention, and that is surely what I am not doing here, I am simply putting my work out there to see if the community would like it and if we do like, we can begin setting it up for other devices immediately. Now, I am not a skilled programmer at all, but I know SOME Visual Basic with Windows Forum Applications, so I thought "why not give it a shot." I just wanted to say that.
So I made this simple little application called Lineage OS Installer. Now, reading through some of the comments on the Lineage OS Reddit page, some people were asking if there would be an installer for Lineage OS, and there was a good amount of people who did not want one, which makes sense; people should know what they are getting into, and understanding ADB and Fastboot is indeed important. However, sometimes, there is a person who is not involved with ROMS, who is fine with OEM Android, who does not want to use root and what not, however, they want the latest version of android possible for their device, and that was a main point of CyanogenMod; users could get the latest version of android on their phone and tablet when their manufacturer/carrier stopped supporting it. However, the installation can be intimidating, and for the user that I just described earlier, the user who does not want root and what not, that could mean they won't bother attempting to install a custom ROM. However, this application automates the process; all the user needs to do is click some buttons, and press Enter a few times to install LineageOS.
I understand I don't need "permission" to distribute this program, however, I am just asking if the overall community would support the use of this program.
NOTICE: The applicaton may fail to start properly. I am investigating this issue. In the meantime, ensure you have the latest .NET Framerwork([url]https://www.microsoft.com/en-us/download/details.aspx?id=55170&desc=dotnet47[/URL]). If that doesn't work, try building from the source ([url]https://github.com/PJBeans/LineageOS-Installer/wiki/How-to-build-from-the-source[/URL])
This is a simple graphical and command-line based installer designed to make it easier to install LineageOS; this program is aimed at beginners. It is not the prettiest program ever, but it still works with my Nexus 7 2013 WiFi just fine
Possible support for flashing root may become available in the future.
If you notice a bug (an issue with the application), please submit it here: https://github.com/PJBeans/Lineage-OS-Installer/issues
Features:
[ADB and Fastboot is required, but NOT included.]
- Instructions for enabling Developer Options, USB Debugging, and OEM Unlocking (if required)
- Embedded browsers to download TWRP, GApps, and LineageOS
- Automatically creates a backup with TWRP.
- Flashes TWRP, LineageOS, and GApps with minimal user interaction; no TWRP interaction required! (The most they really do is confirm they want to unlock the bootloader)
If you have a secondary device that supports LineageOS, perhaps you could try out this program and report your results [in a reply to this thread]! In order to make this as stable as possible, it would require lots of testing, and I do not plan on buying each and every Android phone anytime soon. If you want to test this program, use the prebuilt version, as the Source version may contain undocumented bugs blocking one from their goal. Note that:
- It may screw up your device. No automatic restore process is implemented yet, so make sure to have some sort of recovery tool handy.
- When you report back, please include the version of the program you used (as identified in the Downloads section), along with your device.
- CURRENTLY ONLY FOR NEXUS (AND PROBABLY ONEPLUS) DEVICES! HTC, LG, AND OTHERS THAT REQUIRE A BOOTLOADER UNLOCK SITE OR DEVICES WITH A DIFFERENT INSTALLATION PROCESS ( *cough cough* SAMSUNG) ARE NOT SUPPORTED!!
Screenshots:
Coming Soon
Downloads:
Prebuilt
Prebuilt [VB.NET]: (Version 2.0) https://github.com/PJBeans/LineageOS-Installer/releases (Tested on Nexus 7 2013 WiFi)
CURRENTLY FOR TESTING PURPOSES! - "-development" will be removed in the program once the program is known to be stable.
VB.NET is primarily developed by chompy33 (PJBeans), and C# is primarily developed by Evilarceus. Each branch's source can be found below.
Source
Source: (Version 2.0-development) https://github.com/PJBeans/Lineage-OS-Installer (I encourage absolutely anyone to contribute, even if you would like to make just a minor change!)
Updates:
Past:
UPDATE 1.4.0 and 1.4.1(VB.NET)
(I never published 1.3.0, so here's 1.4.0)
- Scripts have been updated; the user no longer needs to interact with TWRP.
- There is one button to install.
- The script automatically backs up data, cache, and dalvik prior to wiping for installation (no backup before unlocking the bootloader, however)
- (1.4.1) Fix issue with application failing to start (Thanks, @dinesh_redhawk for pointing out this bug that I somehow missed!)
- (1.4.1) Update Installer
UPDATE 1.2.0 (VB.NET)
- User must type "yes" before starting the process to ensure they know to read everything and follow all instructions given.
- Support for GApps
- More messages for user instructions.
- Scripts should be working correctly.
UPDATE 1.1 (VB.NET)
- More Material Design
- 3 step installation (Unlock Bootloader, Flash Recovery, install LineageOS)
- Added a beautiful background image (IMO) of New York City on First Form
Current:
UPDATE 2.0 (VB.NET)
- Check out the release notes on GitHub (Prebuilt Download link)
What is your viewpoint on this? Would you actually want an installer to exist for those who are inexperienced with flashing ROMS?
Sorry for such as long post, and I did not put this in DevDB because it is not directly an Android project.
chompy33 said:
Hi,
---
Normally when I come on the XDA forums, I am asking a question, because I end up making a silly mistake in Android. I never like to put out promotional content for attention, and that is surely what I am not doing here, I am simply putting my work out there to see if the community would like it and if we do like, we can begin setting it up for other devices immediately. Now, I am not a skilled programmer at all, but I know SOME Visual Basic with Windows Forum Applications, so I thought "why not give it a shot." I just wanted to say that.
So I made this simple little application called Lineage OS Installer. Now, reading through some of the comments on the Lineage OS Reddit page, some people were asking if there would be an installer for Lineage OS, and there was a good amount of people who did not want one, which makes sense; people should know what they are getting into, and understanding ADB and Fastboot is indeed important. However, sometimes, there is a person who is not involved with ROMS, who is fine with OEM Android, who does not want to use root and what not, however, they want the latest version of android possible for their device, and that was a main point of CyanogenMod; users could get the latest version of android on their phone and tablet when their manufacturer/carrier stopped supporting it. However, the installation can be intimidating, and for the user that I just described earlier, the user who does not want root and what not, that could mean they won't bother attempting to install a custom ROM. However, this application automates the process; all the user needs to do is click some buttons, and press Enter a few times to install Lineage OS.
I understand I don't need "permission" to distribute this program, however, I am just asking if the overall community would support the use of this program.
---
This is a simple graphical and command-line based installer to make it easier to install LineageOS; this program is aimed at beginners. It is not the prettiest program ever, but it still works with my Nexus 7 2013 WiFi just fine
I did not add support for flashing google apps (gapps) yet, just because I do not know if we will use the same open-gapps package that was used in CyanogenMod, or if we would switch to something different.
Features:
[ADB and Fastboot is required, but NOT included.]
- Instructions to enabling Developer Options, USB Debugging, and OEM Unlocking (if required)
- a file called setup.bat, that will set up the directory where all the required files live
- Embedded browsers to download TWRP and LineageOS*
- Included script that runs `adb devices` to ensure device is recognized
- Installation script that sets up the device to install Lineage OS, and pushes LineageOS to the device.
- Gives instructions for steps that must be completed on the device (Wiping, flashing, etc.)
The program's installation script is finished; it does its job to install a ROM to a device; it will unlock the bootloader, flash TWRP, and push the lineageos image. (I substituted LineageOS for CyanogenMod 13 while testing). *The only thing unfinished it the embedded browser to download LineageOS.
I would not recommend using it currently as it is still in early development
Downloads:
Prebuilt: https://drive.google.com/file/d/0B70zQND1cM1WQVFjYi0yZy1BVnc/view?usp=sharing
Source: https://github.com/PJBeans/Lineage-OS-Installer
I understand that the main focus with LineageOS right now is to set up the website, servers, and images, and I do not want to distract those users. But this is what I would like to ask anyone: Would you actually want an installer to exist for those who are inexperienced with flashing ROMS?
Sorry for such as long post, and I did not put this in DevDB because it is not directly an Android project.
Click to expand...
Click to collapse
Ill be honest. This is most dangerous for inexperienced users. If something goes wrong then they have no idea how to fix or find out how to fix it.
If used it would be best suited for someone that does rom testing where they flash multiple times a day, but as you are required to use a pc I really dont see much use for it.
just my thoughts.
zelendel said:
Ill be honest. This is most dangerous for inexperienced users. If something goes wrong then they have no idea how to fix or find out how to fix it.
If used it would be best suited for someone that does rom testing where they flash multiple times a day, but as you are required to use a pc I really dont see much use for it.
just my thoughts.
Click to expand...
Click to collapse
Thank you for your reply! I completely see what you mean; an inexperienced user could possibly freak out, perhaps disconnect the device while something was going on. Perhaps I/anyone else who contributes could add a support section clearly marked for troubleshooting, complete with a guide to reflash stock. If I/someone else did this, would that make it more friendly for beginners in your eyes?
chompy33 said:
Thank you for your reply! I completely see what you mean; an inexperienced user could possibly freak out, perhaps disconnect the device while something was going on. Perhaps I/anyone else who contributes could add a support section clearly marked for troubleshooting, complete with a guide to reflash stock. If I/someone else did this, would that make it more friendly for beginners in your eyes?
Click to expand...
Click to collapse
Yes that make it more friendly for beginners.
I'd be happy to help this project. I could maybe create a UI for this if all goes well.
Also, you should try learning C# if you already know Visual Basic. It's more widely supported and requires less typing. I can still contribute, since I do know both C# and Visual Basic
I wonder if it would be too much to ask to have this program automatically make a NANDROID backup before starting. Incase an inexperienced user disconnected the device or did something to disrupt the install, and caused a soft brick or similar, the NANDROID backup could be restored, and the user could re-attempt, with no harm done.
evilarceus said:
I'd be happy to help this project. I could maybe create a UI for this if all goes well.
Also, you should try learning C# if you already know Visual Basic. It's more widely supported and requires less typing. I can still contribute, since I do know both C# and Visual Basic
Click to expand...
Click to collapse
Thanks! The source is in the original post. The only thing that does not have a UI is the installation (although the current UI is pretty bad) I will try to learn C# as time goes on. If you would like to make part of the program in C#, feel free!
Doofitator said:
I know Visual Basic, and I'd be happy to help with the development of this application, too.
I also wonder if it would be too much to ask to have this program automatically make a NANDROID backup before starting. Incase an inexperienced user disconnected the device or did something to disrupt the install, the NANDROID backup could be restored, and the user could re-attempt, with no harm done.
Click to expand...
Click to collapse
Thanks for your reply! The source is above. Creating a NANDROID back is a great idea, perhaps we could create an automatic restore option too.
I am worried by the usage by inexperienced users. They are more prone to panic and destroy their phone, which could lead to a bad name for lineageOS on many forums where they will complain that lineageOS just killed their phone, while they did'nt understand the simplest part of the process.
BUT
This can be a tool very useful for experienced users who serially update phones of their many inexperienced friends.
I am doing just that (with around 50 differents phones to date) with my many friends of friends, and a tool like yours would simplify my job. For the moment, i keep a directory of directorys containing rooter scripts, recoverys, roms, gapps, utilities (adb, fastboot, odin, heindall,...) and have a multi-gigabyte library of those.
A utility who prepare a directory for a phone model, download rom, twrp/cwm, gapps, and do the phone rooting for every phone is a very desired thing, but it is a hell of a project to achieve.
So good luck with your project, and dont hesitate to ask me for help if you need, i would be proud to help you achieve your goal.
mlsoftlaberge said:
I am worried by the usage by inexperienced users. They are more prone to panic and destroy their phone, which could lead to a bad name for lineageOS on many forums where they will complain that lineageOS just killed their phone, while they did'nt understand the simplest part of the process.
BUT
This can be a tool very useful for experienced users who serially update phones of their many inexperienced friends.
I am doing just that (with around 50 differents phones to date) with my many friends of friends, and a tool like yours would simplify my job. For the moment, i keep a directory of directorys containing rooter scripts, recoverys, roms, gapps, utilities (adb, fastboot, odin, heindall,...) and have a multi-gigabyte library of those.
A utility who prepare a directory for a phone model, download rom, twrp/cwm, gapps, and do the phone rooting for every phone is a very desired thing, but it is a hell of a project to achieve.
So good luck with your project, and dont hesitate to ask me for help if you need, i would be proud to help you achieve your goal.
Click to expand...
Click to collapse
I see what you mean, and I/other contributors will (hopefully) try to make this process very user friendly, so they won't need to panic. I guess developers could use this if they needed to install the ROM on multiple devices, though currently the installation is kind of slow. I appreciate your response!
chompy33 said:
I see what you mean, and I/other contributors will (hopefully) try to make this process very user friendly, so they won't need to panic. I guess developers could use this if they needed to install the ROM on multiple devices, though currently the installation is kind of slow. I appreciate your response!
Click to expand...
Click to collapse
I would suggest that such a tool should be VERY wordy about telling the user what it is doing, and should NEVER suspend its apparent activity.
My experience (and it is commercial experience, with genuine products in the marketplace) is that the user will get nervous, and may do something unfortunate, if they fear that something has gone wrong...and they WILL fear this if there is no obvious activity for a long time...and "long time" might be only a few seconds.
So, to make this tool "safe", it should be continually reassuring the user that it is doing something. There should be a progress bar, that keeps moving. There should also be a text section that keeps updating what is going on. If the operation under way will take awhile, then this text session should (every few seconds) remind the user "I'm still working on this...estimated time to completion is XX seconds" (or some such).
This operation IS dangerous, particularly if the user does something wrong. So keep reassuring the user that everything is fine.
jiml8 said:
I would suggest that such a tool should be VERY wordy about telling the user what it is doing, and should NEVER suspend its apparent activity.
My experience (and it is commercial experience, with genuine products in the marketplace) is that the user will get nervous, and may do something unfortunate, if they fear that something has gone wrong...and they WILL fear this if there is no obvious activity for a long time...and "long time" might be only a few seconds.
So, to make this tool "safe", it should be continually reassuring the user that it is doing something. There should be a progress bar, that keeps moving. There should also be a text section that keeps updating what is going on. If the operation under way will take awhile, then this text session should (every few seconds) remind the user "I'm still working on this...estimated time to completion is XX seconds" (or some such).
This operation IS dangerous, particularly if the user does something wrong. So keep reassuring the user that everything is fine.
Click to expand...
Click to collapse
Good idea! Thanks for the suggestion, we will definitely incorporate this.
Two thumbs up for a LineageOS installer, plz develop it
Definitely having a LineageOS installer is a great idea!
Unquestionably, it will permit people who are not experienced with flashing custom roms(which accounts for a lot of people), nor do they have an interest in learning about that(e.g. my mom) to easily get the latest Android build on their Android phone (which may no longer be supported by the OEM; an e.g. AT&T LG G2).
44alexsmith said:
Definitely having a LineageOS installer is a great idea!
Unquestionably, it will permit people who are not experienced with flashing custom roms(which accounts for a lot of people), nor do they have an interest in learning about that(e.g. my mom) to easily get the latest Android build on their Android phone (which may no longer be supported by the OEM; an e.g. AT&T LG G2).
Click to expand...
Click to collapse
This is exactly what I am trying to achieve. Provided I/contributors make a stable build by the time a stable build of LineageOS comes out (or at least around there, it's an open source project so there is no official date), it could give LineageOS a reputation of being a very easy ROM to install. Thanks for the reply.
Creating an installer for users who don't event know what's going on from the inside is useless IMO.
If the installer fail to flash they get stuck with a bricked device and don't know what to do.
I added a .gitignore to reduce cloning size and keeping things clean: https://github.com/PJBeans/Lineage-OS-Installer/pull/1
If you want, add me as a collaborator on the GitHub project so I don't have to keep on making pull requests.
p4rot said:
Creating an installer for users who don't event know what's going on from the inside is useless IMO.
If the installer fail to flash they get stuck with a bricked device and don't know what to do.
Click to expand...
Click to collapse
Just FYI, I did say earlier that this installer should have an automatic NANDROID backup take place, so phones would be safe if something happened.
Doofitator said:
Just FYI, I did say earlier that this installer should have an automatic NANDROID backup take place, so phones would be safe if something happened.
Click to expand...
Click to collapse
We will attempt to add this (or at least guide the user) later on. Thanks for your response!
evilarceus said:
I added a .gitignore to reduce cloning size and keeping things clean: https://github.com/PJBeans/Lineage-OS-Installer/pull/1
If you want, add me as a collaborator on the GitHub project so I don't have to keep on making pull requests.
Click to expand...
Click to collapse
I set up a live chat on Telegram, the link is on the Repository's Readme. I appreciate your commitment to this project!
I sent an invite at https://github.com/PJBeans/Lineage-OS-Installer/invitations
chompy33 said:
We will attempt to add this (or at least guide the user) later on. Thanks for your response!
Click to expand...
Click to collapse
If possible, I think making this a mandatory step would be better - we don't want people skipping it and then complaining later.
Since many people seem to ask continuously if magisk work with nougat and why supersu sr3 flashable zip by chainfire doesn't work ill try to explain it here.
Since M huawei has updated the kernel to work with nougat they seemed to break some important stuff. Or disabled it. I cannot tell for sure. And since sources aren't out we can't tell for sure if it's disabled or just broken.
Supersu and magisk is relying on loop to get it system less. This requires a .img which is being mounted to the path which is being executed on boot. But with loop being broken or disabled the phone will for some reason not handle this well.
But this is the reason why supersu and magisk isn't working when trying to install it reboots twrp notice that even if you manually patch boot so it contains all info related to magisk or supersu images it won't help you. Because you'll not be able to use magisk since the system will not boot. Due to loop is broken or disabled.
So there will be no magisk for nougat? And when will it come if it'll be working?
Wait until kernel sources are dropped.
So can we get magisk working?
Well yes.
Our best shot is to actually create a folder in /data which is being symlinked to / or if we do a similar approach on how supersu works on nougat. But for now we can't mount images and that's why everything fails.
Hope this sum up things for you.
Sent from my CUBOT_MANITO using Tapatalk
You're far more competent with Android development than me -- is it possible to fork Magisk and modify it to use a ramdisk instead of loop mounting? The Honor 8 has plenty of free RAM, we would probably do a 256MB ramdisk with no issue. Ramdisks don't require loop mounting so conceptually we should just be able to modify the mount / unmount, flash, and image update sections of the script.
Telperion said:
You're far more competent with Android development than me -- is it possible to fork Magisk and modify it to use a ramdisk instead of loop mounting? The Honor 8 has plenty of free RAM, we would probably do a 256MB ramdisk with no issue. Ramdisks don't require loop mounting so conceptually we should just be able to modify the mount / unmount, flash, and image update sections of the script.
Click to expand...
Click to collapse
Hmm maybe. As said we could do a similar approach on how supersu and phh works on nougat. The only downside would be placing all in ramdisk due to lack of storage space. Since it'll be filled too fast.
It could work in theory but not sure if it'll actually work properly
Sent from my CUBOT_MANITO using Tapatalk
LastStandingDroid said:
Hmm maybe. As said we could do a similar approach on how supersu and phh works on nougat. The only downside would be placing all in ramdisk due to lack of storage space. Since it'll be filled too fast.
It could work in theory but not sure if it'll actually work properly
Sent from my CUBOT_MANITO using Tapatalk
Click to expand...
Click to collapse
Has anyone from XDA (or elsewhere) actually got a "contact" at Honor/Huawei that has ever done anything positive for them (in the engineering/development realm)?
It doesn't appear that Honor 8 nougat is supported at all to me, but some things that could easily done with their "private source" of the Nougat kernel would be of great use and would not cause them to look as if they were being generous with their code. (I don't know why they're such dorks about it, but they are).
For example: IF you have some "insider" at Honor, please ask them for the stock emui loadable module (via modprobe or lsmod) for mount.loop support. That would solve the problem as there's not some reason why we can't find a way to load it during startup. If you guys get that, then you probably won't care about them probably never releasing the kernel source. I have no expectations for this company. Nice phone, but they lied about their development support. Too bad, because Kirin 9xx's are becoming nicer and nicer and in some ways are nicer than the heavily supported SD's, which are supported to a much larger extent.
Oh hell. We have working TWRP, so in theory, (and if we get the magical module for loop mount) we could root edit from TWRP and add the modprobe {modname-loop.ko) to whatever is the equivalent of rc.local or one of the startups (rc1.d, etc).
Getting someone to fork, develop and test the magik (sp?) code for one case and one kernel seems like a lean chance.
hachamacha said:
Has anyone from XDA (or elsewhere) actually got a "contact" at Honor/Huawei that has ever done anything positive for them (in the engineering/development realm)?
It doesn't appear that Honor 8 nougat is supported at all to me, but some things that could easily done with their "private source" of the Nougat kernel would be of great use and would not cause them to look as if they were being generous with their code. (I don't know why they're such dorks about it, but they are).
For example: IF you have some "insider" at Honor, please ask them for the stock emui loadable module (via modprobe or lsmod) for mount.loop support. That would solve the problem as there's not some reason why we can't find a way to load it during startup. If you guys get that, then you probably won't care about them probably never releasing the kernel source. I have no expectations for this company. Nice phone, but they lied about their development support. Too bad, because Kirin 9xx's are becoming nicer and nicer and in some ways are nicer than the heavily supported SD's, which are supported to a much larger extent.
Oh hell. We have working TWRP, so in theory, (and if we get the magical module for loop mount) we could root edit from TWRP and add the modprobe {modname-loop.ko) to whatever is the equivalent of rc.local or one of the startups (rc1.d, etc).
Getting someone to fork, develop and test the magik (sp?) code for one case and one kernel seems like a lean chance.
Click to expand...
Click to collapse
Many people probably have but won't try get people fired because of leaks
Their working on to get in touch though
Sent from my CUBOT_MANITO using Tapatalk
Perhaps @MishaalRahman can push on behalf of all of us as a representative of XDA to get the kernel source released faster, and built correctly for once.
Telperion said:
Perhaps @MishaalRahman can push on behalf of all of us as a representative of XDA to get the kernel source released faster, and built correctly for once.
Click to expand...
Click to collapse
I'm not sure how much clout I would have, but it wouldn't hurt to ask.
I think @svetius is more into this.
You should ask him about it tbh
Afaik he's the on that handles this
Sent from my CUBOT_MANITO using Tapatalk
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing a modded boot.img created by @HassanMirza01 and by setting selinux to permissive
big thanks to @Paolo83 because he found this method
@simo255 lol
simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing a modded boot.img created by @HassanMirza01 and by setting selinux to permissive
big thanks to @Paolo83 because he found this method
Click to expand...
Click to collapse
please state more info about which image you use, whether you have stock firmware installed and which steps you took in twrp to install supersu and consecutively, magisk.
Hey guys,
since I dont get neither Netflix nor Disney+ to work on my TB-X704F after having flashed LOS 16, I want to go back to stock rom. I've already tried to use Lenovo Smart Assistant but the flashing procedure always fails. I also tried QComLoader but also fails at 5%.
Is there a working way on going back to stock rom having TRWP ans LOS 16 installed???
Due to the fact that Netflix and Disney+ arent working (already tried Magisk module to change the tablets' fingerprint), I need to go back to stock rom.
Thanks in advance!!!!
Please use this tool to flash the stock rom: https://qfiltool.com/qfil-tool-v2-0-2-3
need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?
I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.
rhchia said:
need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?
Click to expand...
Click to collapse
I've got the same problem. What did you do in the end?
K14_Deploy said:
I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.
Click to expand...
Click to collapse
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?
boomhaueruk said:
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?
Click to expand...
Click to collapse
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.
K14_Deploy said:
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.
Click to expand...
Click to collapse
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
Is this going to be a problem?
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.
K14_Deploy said:
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.
Click to expand...
Click to collapse
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.
boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
Click to expand...
Click to collapse
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.
Click to expand...
Click to collapse
K14_Deploy said:
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
Click to expand...
Click to collapse
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
They are Magisk modules, you go to there the puzzle piece is and search for them.
boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
OK, found 'root checker' on the play store. And Termux.
so I have root.
K14_Deploy said:
They are Magisk modules, you go to there the puzzle piece is and search for them.
Click to expand...
Click to collapse
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.
boomhaueruk said:
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.
Click to expand...
Click to collapse
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer, as you have to wipe internal storage and use ADB.
K14_Deploy said:
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer.
Click to expand...
Click to collapse
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.
boomhaueruk said:
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.
Click to expand...
Click to collapse
Yeah of course, but you will have to start over if / when you upgrade
Ah. Hit a snag.
You said "Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)"
I've got the TB-8704L, the 10 inch.
Let me see if anythings listed.