I don't know why, but it is easy for me to flash the unofficial lineage os 18.1. But for the flox 17.1 I could not do! I am facing with a touch sensitivity issue with the 18.1, so I switched to the unofficial 17.1 rom of ipdev (no need to do repartition as it was already done for the 18.1). My flo is working smoothly.
[ROM][DISCONTINUED][10] LineageOS 17.1 [deb][flo]
- Thread starter ripee
- Start date
Can anyone share the last unofficial build's link? it's been taken down from the source
@pitrus-The Clamor's partitioning scheme is really perplexing considering the number of EMMC scripts involved.
I have simplified it to just one sysrepart-flox.zip script available from the CROSS page.
I really hope Wickenberg restores the UNOFFICIAL LOS17.1 downloads. Wickenberg - can you do it? We do not like the OFFICIAL LOS17.1 POS
Server side issues again ?
Cheers.
@pitrus- Server side issues again ? Cheers.
Online again! Wickenberg - thank you
All CROSS scripts are fully operational, lineage-install-2.bat downloading lineage-17.1-20210101-UNOFFICIAL-flo.zip ATM...
Brief summary of LOS17.1 options and solutions...
LOS17.1 UNOFFICIAL
- very easy to install
- needs simple repartition, eg. sysrepart-max, no internal storage wipe, no custom TWRP necessary
- if using CROSS, run lineage-install-2.bat for single-click automatic installation
LOS17.1 OFFICIAL
- very difficult for manual install, many complaints and issues on the official thread
- needs complex repartition, eg. Clamor UA or somewhat easier sysrepart-flox, internal storage is wiped, custom TWRP is necessary!
- if using CROSS, run lineage-install-2-flox.bat for single-click automatic installation
Hi I am coming from android official version 6.0.1 and I just prepared my n7 flo for rom flashing with all instructions followed. My question is can I flash this directly or can I flash the flox version directly coming from 6.0.1. Pardon me I just bought back a nexus7. I sold mine years ago. Thanks in advance
well shoot, got all excited that I moved to the official flox build but despite using MSI's elementalX or their own ten/eleven kernel I've lost tap2wake and otg-usb-host external storage ability, even using the kernel tweak apps
is this a build thing? should I go back to unofficial?
took awhile to get magisk stable and edxposed+gravitybox is a mess now, don't upgrade/switch unless you've got a day to kill on this
is this a build thing? should I go back to unofficial?
took awhile to get magisk stable and edxposed+gravitybox is a mess now, don't upgrade/switch unless you've got a day to kill on this
moved back to unofficial vs flox official
btw I've seen "kernel auditor" mentioned several times in this and other flo threads to enable tap2wake and fastcharge for OTG
note it's no longer developed, instead use SmartPack kernel manager which is open source on github and maintained, built on the original source
had both installed, switching to smartpack only to see if that brings back tap2wake
btw I've seen "kernel auditor" mentioned several times in this and other flo threads to enable tap2wake and fastcharge for OTG
note it's no longer developed, instead use SmartPack kernel manager which is open source on github and maintained, built on the original source
had both installed, switching to smartpack only to see if that brings back tap2wake
No idea what I've done but asking this in case someone comes across it in the future and knows the answer.
I had a working 17.1 with msi's ElementalX with a dual charge and OTG usb storage Y cable for months early in 2020. Now no matter what I do the usb storage will not work again. I know the tablet port is working because it not only charges from the Y cable, if I move the tablet to my windows usb connection I can go into dev adb mode just fine and transfer files. I know the usb stick works just fine because I can read/write it on my windows machine.
As far as I know the elementalX kernel does not need any OTG activation that would be lost with repeated rom upgrades and even if I roll back the rom to an older build that I know worked, it doesn't work anymore.
On very rare occasion the usb symbol will appear in the statusbar and I can go quickly into storage and see it there. But it will disappear, especially if the screen turns off with timeout.
Feels like a kernel or rom thing but I can't figure it out.
I had a working 17.1 with msi's ElementalX with a dual charge and OTG usb storage Y cable for months early in 2020. Now no matter what I do the usb storage will not work again. I know the tablet port is working because it not only charges from the Y cable, if I move the tablet to my windows usb connection I can go into dev adb mode just fine and transfer files. I know the usb stick works just fine because I can read/write it on my windows machine.
As far as I know the elementalX kernel does not need any OTG activation that would be lost with repeated rom upgrades and even if I roll back the rom to an older build that I know worked, it doesn't work anymore.
On very rare occasion the usb symbol will appear in the statusbar and I can go quickly into storage and see it there. But it will disappear, especially if the screen turns off with timeout.
Feels like a kernel or rom thing but I can't figure it out.
Does usb file transfer work in TWRP? Not sure what else I could suggest, considering the explanation you gave its probably not something to do with the hardware you have just the setup.
any idea why I can't see file in /sdcard/ while in recovery? I put files in folders in that location and while under the "install" to flash something the files are hidden.
I can go into the file manager from within recovery advanced/file manager and they show up there.
I can go into the file manager from within recovery advanced/file manager and they show up there.
i n f a m o u s
Senior Member
Online again! Wickenberg - thank you
All CROSS scripts are fully operational, lineage-install-2.bat downloading lineage-17.1-20210101-UNOFFICIAL-flo.zip ATM...
Brief summary of LOS17.1 options and solutions...
LOS17.1 UNOFFICIAL
- very easy to install
- needs simple repartition, eg. sysrepart-max, no internal storage wipe, no custom TWRP necessary
- if using CROSS, run lineage-install-2.bat for single-click automatic installation
LOS17.1 OFFICIAL
- very difficult for manual install, many complaints and issues on the official thread
- needs complex repartition, eg. Clamor UA or somewhat easier sysrepart-flox, internal storage is wiped, custom TWRP is necessary!
- if using CROSS, run lineage-install-2-flox.bat for single-click automatic installation
I thought it wasn't possible for Nexus LTE owners to install Nexus WiFi ROM's and vise versa?
I notice the phone app was available for download in the app store but I wasn't able to get the app working because Android wouldn't allow me to set the app to the default phone app. Does anybody know how to get the app working?
yup, I can do ADB and file transfer in TWRP no problem
either my Y-cable has given up and broken somehow (which is remotely possible, though it still charges) or like you say there is a setting buried somewhere or the dirty upgrades have broken OTG
frustrating because internal storage is so small on these older tablets
guess I will search for another Y cable but hard to find one with the
special 3-way wiring without messy DIY
(special Y cable from my ancient notes if it helps anyone someday)
If you can transfer files through twrp its likely not your cable but rather something to do with software, it wouldn't work either way if it was your cable or the computer connection. I'd recommend just doing a clean install, not sure how else you would fix it as I've never had this issue..
Any chance someone has the best version of the 17.x ROM laying around? The hosting site seems to have died and can't find it elsewhere. I specifically need the deb version. Thank you.
Do I need to repartition/reset the device in order to "upgrade" from this unofficial 17.1 to the official 17.1? I tried to install the ZIP in a usual way, but I got an error message like "This ROM is for flox. This device is flo."
I don't know about any underlying stuff but at the average user level it all seems the same to me apart from SELinux is enforcing on the official but not on the unofficial. I'm running the official no problems with latest Google security updates.
I've read a few posts on the flox thread suggesting that people successfully did a dirty upgrade from the unofficial rom (having repartitioned in the past using clamour for unofficial ROMs) they seem to indicate the opposite and all that was required was:
1. Flash the TWRP flox recovery
2. Flash official flox signed zip
3. (Possibly optional) Flash LOS flox recovery if you want to use the internal updater to automatically install downloaded updates.
So is the above possible? I'd rather not have to reflash magisk and do a Migrate backup just to move to the official build which only seems to provide SELinux support above this one. AFAIK it can't repetition without erasing all existing data. Netflix and a few other things were working on the unofficial build when I last checked although I don't use them on here much anyway so not quite sure what advantages the move to official actually would bring. Are the unofficial builds going to stop which will make this necessary?.
Thanks.
i n f a m o u s
Senior Member
Was anyone able to flash the OTA successfully without their tablet bootlooping? My device is on an endless bootloop on startup and it eventually returns to TWRP recovery. FYI: I've never had an issue with install OTA updates on my deb device.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
54
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:* [B][U]Your warranty is now void.[/U][/B] * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or your getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you.
FREQUENTLY ASKED QUESTIONSQ: Whenever I try flashing any lineage-17.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
(Please read them BEFORE posting anything in the thread!)
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.3. Simply flash the linked below version 3.3 or higher, reboot back into recovery, and flash the rom zip again.
Q: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: There are no plans to submit these builds for official LineageOS support, but it should not matter. What is most important is that these unofficial builds be stable enough for daily usage, which they are, thanks to followmsi's tireless work in porting Android 10 to these venerable old tablets.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: Even if neither dev nor flo will ever receive official LineageOS support, just out of curiosity, what are some of the differences be between unofficial and official builds?
A: The following technical changes are in effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Tablet status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed, as per followmsi's advice.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 17.1, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2020-01-21
Created 2020-01-21
Last Updated 2020-04-1410
https://forum.xda-developers.com/showpost.php?p=81555475&postcount=2938
Lineage-17.1
Like mentioned before .. I did plan to handover Lineage-17.1 beginning of 2020.
That's done now.
@ripee will continue to build regular lineage-17.1 builds for flo/deb.
If there are some code changes in the next time .. we test on AEX first and apply changes to Lineage sources later on.
Thanks to @ripee for taking over !
Cheers6
Try this one
https://drive.google.com/file/d/17XhZZwKDYJsaKSn0fS9a-c4wWze-2u5a/view?usp=drivesdk
Regards
Sent from my OnePlus7Pro using XDA Labs5
Along those lines, you can also add the folder of your variant to your own Google Drive. That way, all future builds will sync down to your account automatically.
