yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Petsku:
I just got a 32 GB Nexus 7 2nd gen. 2013 WIFI and decided to put LineageOS in it. I followed the instructions on Lineage's wiki at https://wiki.lineageos.org/devices/flox/install

But not everything went as in the instructions. First, only LineageOS 18.1 is available now. Secondly I got some errors during the installation steps. I try to describe them here in case it's useful for someone else.

So I followed the wiki page up until the re-partition part. The zip file installed fine but running it didn't go as it should have. The first time I ran the command 'modify' I got errors during the mke2fs lines: all of them said no such device exists, 4 times for all of the mmcblock0p* devices. After that the script continued and after the 'dd' lines hung up and not exiting properly (yes, I waited like 15 minutes). No errors though.

I decided to give it another try so I sideloaded the zip again and ran the 'modify' command again. This time the mke2fs lines actually created the filesystems but still the script hung right in the end and did not reboot to bootloader. Again force exited the script and continued with the installation.

Next was fastboot -w, which did not run properly but gave an error: "FAILED (remote: 'Bogus size sparse and chunk header')"

After some googling I found some threads that suggested that my platform tools were out of date. But they were not, I had just downloaded the latest tools. Then I found a reddit thread that suggested to use TWRP recovery instead. So I did: fastboot boot twrp-3.5.0_9-0-flox.img. I used the image found somewhere on this forum. When in the TWRP recovery, go to "Wipe" and "Format Data", then type yes. That completed successfully.

Next I continued with the installation by booting into LOS recovery and formatting system partition and then flashing the LineageOS recovery: fastboot flash twrp-3.5.0_9-0-flox.img. Everything after that went smoothly, installed the LineageOS 18.1 weekly, which was

lineage-18.1-20220328-nightly-flox-signed.zip and the corresponding recovery image.

The only weird thing with LOS 18.1 was that in the first boot wizard, wifi wouldn't connect but did connect later when installing software. Oh and I also installed OpenGapps Nano v. 11 for ARM before booting up LOS for the first time.
[Nexus 7 (2013) Android Development] GJW1972:
Just thought I'd mention Slimport (hdmi via usb) doesn't work on this ROM: the Nexus 7 2013 just freezes (it does, however, work on a LG G2 with Lineage 17.1)
[Nexus 7 (2013) Android Development] na6cet:
Can anyone share flo-deb_clamor_repartition_20201203.zip with me? android file host tells me there are no mirrors available.

I found flo-deb_clamor_repartition.zip but I don't think it's the same
[Nexus 7 (2013) Android Development] artigasperez:
Just posting to say thanks the developers. My flox is celebrating 10 years, and now is running LineageOS 18.1 build from may 2023. I use it almost everyday, and it is, no doubt, the best tech purchase for longevity, price, and community support. I wish other devices could reach half this support.
[Nexus 7 (2013) Android Development] glitchers:
Here's a mirror: flo-deb_clamor_repartition_20201203.zip

Its md5sum should match the one listed on the old d/l page.
[Nexus 7 (2013) Android Development] na6cet:
Thanks, I feel slightly bad now because I tried the next day and the download worked but I didn't update this thread.

I had all sorts of trouble installing though with various 'error' messages about missing things and commands seemingly hanging and never ending. But in the end I just ploughed on through and ignored all that and it somehow is working now 🤷‍♂️. It helps that I wasn't overly concerned about bricking it.
[Nexus 7 (2013) Android Development] glitchers:
No worries. The main d/l page has continued to be unreliable, so I'm happy to provide a mirror (flo-deb_clamor_repartition_20201203.zip for people just arriving).

Glad it worked out for you.
[Nexus 7 (2013) Android Development] Gene August:
Is a TWRP variation for FLOX recommended and/or available?
[Nexus 7 (2013) Android Development] skezza:
Is this still the best ROM to go with? That's what I've read recently....

Any Download links?
[Nexus 7 (2013) Android Development] DrSnowHR:
Hi, I accidentally did a "fastboot flash recovery twrp-3.4.0-0-flo.img" instead of using "lineage-17.1-20201217-recovery-flox.img".

After that I retry "fastboot flash recovery lineage-17.1-20201217-recovery-flox.img" but

i get an error message saying that the size is not enough.

Now when i hold "Volume Down + Power Button" and trying to access "RECOVERY", i get a weird image like this below and i cannot access "RECOVERY".

Only way i can access "RECOVERY" is by typing each time "fastboot boot lineage-17.1-20201217-recovery-flox.img" or "fastboot boot twrp-3.4.0-0-flo.img".

Is It normal ? Is there something wrong ? How can i make the "RECOVERY" Permanent ?

I succeed to do the "EFS/Persist Backup", but how can i get the file to save them somewhere else ?

Thank you very much.
[Nexus 7 (2013) Android Development] pedritopl:
Have You tried booting the TWRP and flashing the recovery (whichever one) from TWRP (Install, select image)? If it doesn't work, I suppose You have not repartitioned yet in which case You should still be able to flash the standard TWRP (not the modified one).
[Nexus 7 (2013) Android Development] Christobaldi:
I finally managed to install this rom.

Essential is using the flo-deb_clamor_repartition.zip to avoid the "image is larger than target" error and then flash twrp 3.4.0-0 flox version. I needed to reformat /system and /vendor with ext4 and to do a standard wipe to be able to flash lineage.

Thanks a lot
[Nexus 7 (2013) Android Development] ud4:
So, I re-uploaded my TWRP build, users who can't install it due to an image size error can do it now!
[Nexus 7 (2013) Android Development] MartinX3:
Came from unofficial November los.

First the flox twrp.

Then the los, pico gapps & magisk.

Then wiped dalvik and cache.

Dirty upgrade was successful.

Thank you!
[Nexus 7 (2013) Android Development] leetripper:
Install without problems. Could also install Netflix. But App crashes. Any advice?
[Nexus 7 (2013) Android Development] DrSnowHR:
I succeed to install TWRP correctly with the "twrp-3.4.0-0-flox.img" (Modified), now "RECOVERY" is working fine with TWRP.

I cannot flash the lineage recovery still due to size issue.

But i can boot it if needed with "fastboot boot lineage-17.1-20201217-recovery-flox.img "

I want to do a repartition but the tutorial is saying to "EFS/Persist Backup", but after running the command asked.

How can i backup the file in my computer ? My Nexus is not detected.

/sdcard/modemst1.img

/sdcard/modemst2.img

/sdcard/persist.img

Thank you.
[Nexus 7 (2013) Android Development] ud4:
As a temporary solution, you can use my TWRP or fastboot boot *name of lineage recovery file* (if you use that, reflash recovery after repartition, but use fastboot flash recovery *name of recovery file*) , we are currently solving the problem with the size of recovery
[Nexus 7 (2013) Android Development] anivegmin:
Downloaded and installed twrp-3.4.0-0-flox.img using Official TWRP app.

Dirty flashed official lineage-17.1-20201214-nightly-flox-signed.zip over previous unofficial version.

All working fine. Although the LineageOS updater returned an error when trying to install 20201221, so I downloaded manually and flashed in TWRP which has worked fine.

Otherwise this is great having an official version, all working perfectly, December security patch, and SELinux is now enforcing, which it wasn't on the unofficial version.

Thanks very much for all the work and making this available.

(all I need now is an official 17.1 for my Nexus 5..... currently running an unofficial maintained 14.1 on Nexus 5 as 17.1 has problems for me).
[Nexus 7 (2013) Android Development] pedritopl:
I suppose You have working adb, right?

If so, use adb pull command to get the files transferred to your PC.

It's all described on the Wiki:

"Install LineageOS on flox | LineageOS Wiki" https://wiki.lineageos.org/devices/flox/install
[Nexus 7 (2013) Android Development] ChrisAG:
Open Gapps:

No matter which of the smaller packages I install, it loads the older AOSP mail, gallery, etc., (which nobody wants or uses), ending up with Google versions alongside the AOSP versions, taking up extra space.

What package doesn't include AOSP apps?
[Nexus 7 (2013) Android Development] DrSnowHR:
Lol:ROFLMAO:, i understand why the command "adb pull" did not work. (I was in Directory C:\Windows\System32)

Once moved to another directory, i succeed to pull the backup of "EFS/Persist".

But now i have another issue with "Repartition", when i try installing it i got an Error:21 (see attached screenshot)

It seems to be similar to this person on reddit :

https://www.reddit.com/r/LineageOS/comments/kgl2y7

I try to search for more detail in forum there:

https://xdaforums.com/t/repartition-nexus-7-2013-repartition-flo-deb-16gb-32gb-ua-twrp.3844386/

Any idea to avoid this error ? and what error : 21 means ?

Thank you so much
[Nexus 7 (2013) Android Development] weresgyufa:
Hello.

I have the same issue Error 21 :( I try it several times from the begining, maybe I did something wrong, but I always get the same Error 21.

Is there any solution for thís, because I'm stuck on the repartition now and I can't do that with the described steps/tools.

Thank you for the help.

BR.
[Nexus 7 (2013) Android Development] Jvino:
I did a dirty flash from the unofficial Los 17.1 and have the same issue. I think there is a firmware problem or mis-match, and it needs a clean install to fix. Everything is working well, but the Slim Port still does not work and Netflix is broken. I hope, after Christmas, when I do the clean install all is fixed.
[Nexus 7 (2013) Android Development] Loader009:
WiFi seems to be broken for me...

The weird thing is - it doesn't even try to connect to the AP.

I see my AP, I put in my password, but nothing happens when I tap on connect.

I will try to debug that further and I might provide a logcat later.
[Nexus 7 (2013) Android Development] Loader009:
@ud4

First off - thank you for your effort!

Here is a part of my logcat, if my wifi problem is unknown to you:

dogbin - ebighecewu

12-24 17:13:17.203 279 279 I WifiHAL : Initializing wifi 12-24 17:13:17.204 279 279 E WifiHA

del.dog

If you have some idea I could test, tell me.

If you have telegram, to conversate easier, tell me.

edit:

Another thing I noticed is below.

I will look at it further - but I think some feature is missing (though, my AP has 802.11r disabled).

[ 44.036895] wlan: [759:E :HDD] wlan_hdd_set_akm_suite: Unsupported key mgmt type 1027078
[ 44.037017] wlan: [759:E :HDD] wlan_hdd_cfg80211_set_privacy: failed to set akm suite
[ 44.037109] wlan: [759:E :HDD] wlan_hdd_cfg80211_connect: failed to set security params

edit2: Might be an upstream bug - I also have problems with my recently flashed Samsung Galaxy S2.

edit3: Definitely an LOS or android upstream bug - it is the 802.11w Management Frame Protection for wifi. No matter if it is on 'optional' or 'required', both of my LOS 17.1 devices don't connect with those settings.

I might do a bugreport - as soon as I've figured out where and how.
[Nexus 7 (2013) Android Development] Gorilla Daddy:
Netflix & Disney. Netflix crashes/stops at startup, and Disney fails to play any videos.

Both worked great on last unofficial. Tried to go back to the unofficial, but now TWRP refuses and says my device is flox and the unnofficial build is for flo.
[Nexus 7 (2013) Android Development] Gorilla Daddy:
Was able to flash back to unofficial 17 by deleting the first line in the install script (inside the unofficial lineage 17 zip), an "assert" which checks the device type. Wiped system, cache, & dalvik; then reinstalled the unofficial build & magisk & gapps. Everything works again.

If anyone has the official 17 working with Netflix & Disney, please respond to let me know which or how. Thanks in advance.
[Nexus 7 (2013) Android Development] patria o muerte:
Good morning and nice xmas to all here.

I'm not able to download that twrp,servers seem to be down. Could someone upload that please? Thanks.
[Nexus 7 (2013) Android Development] makjim:
Trying to move from the unofficial LOS 17.1 to the flox. Installed the TWRP 3.4.0 flox recover from the original TWRP 3.4.0.

After reboot the modified flox TWRP and install the 1214 flox image, encountered the following error.

”Failed to mount ‘/vendor’ (Invalid argument)”

Fall back to the original flo for the time being.
[Nexus 7 (2013) Android Development] makjim:
Problem fixed after repartitioning. My fault for not following the instructon.

Merry X'mas everybody.
[Nexus 7 (2013) Android Development] ud4:
Who can test netflix or other widevine stuff, please write me in DM
[Nexus 7 (2013) Android Development] makjim:
Netflix "The application needs to be restated. Please launch it again (502-1019)."
[Nexus 7 (2013) Android Development] thedanniel:
Thank you, my old nexus is like new again.

With the update I hear the difference of high-resolution audio over usb otg, it's perfect and a big difference from the old ROM.

https://source.android.com/devices/audio/highres-effects

I can't wait for new improvements to the 17.1 rom, I'm looking for improved battery usage, because as soon as the screen turns off spotify immediately stutters.

I have tried everything but can't solve it now, someone else has an idea or help.

Thank you so much.
[Nexus 7 (2013) Android Development] patria o muerte:
Hi all,

I went from unofficial los 17.1. Do i have to perform repartitioning again?

Thanks.
[Nexus 7 (2013) Android Development] sdadaf:
It was hard to install this rom.

Anyway i succedd

First of all, Flo ≠ Flox

ud4 who is maker of this lineage rom? said,

"We use name Flox to show the difference between installation method in new versions of LineageOS on this device, which is not compatible with older versions. "

----------------------------------------------------------------------------------------------------------------------

① if you have any problem, restore it (if you are fine, go to ② directly)

[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix

RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...

xdaforums.com

② Install Flox twrp (modified twrp)

https://androidfilehost.com/?fid=17248734326145694244

③ Do repartition

flo-deb_clamor_repartition_20201203.zip | by The Muppets for Nexus 7 (2013)

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

install "repartion.zip" in twrp → go "Advanced→Terminal" in twrp → enter "modify"

④ Install Flox lineage rom
[Nexus 7 (2013) Android Development] weresgyufa:
So, I think i got the solution for those, whohas ERROR 21.

First when you install the flo-deb_clamor_repartition_20201203.zip to make the repartition, first do the partition job with the comand :"stock"

This will set up all the things to the stock, I really dont know why I cant do this installation from the Last Official 6.0.1 ROM...

After this do the repartition job but now with the vomand:"modify"

After doing this I could install the repartition job it was runing down with any issues and after this I copy the FLOX image to the Nexus and Install it, after this I could instal GAPPS nano and now I'm start to run my Nexus az a FLOX with this new Image.

Make a Try, I hope It will help.

BR.
[Nexus 7 (2013) Android Development] weresgyufa:
It's runing quiet smooth, thank you guys for the job!
[Nexus 7 (2013) Android Development] GeekyTanuj:
Unable to understand the new repartition guide (used the CROSS and RESTOCK utilities before) to use the unofficial LOS 17.1 builds before.

Also, always end up with TWRP error 7 and ”Failed to mount ‘/vendor’ (Invalid argument)” when flash using the twrp used in the tabbed reply on page 1.
[Nexus 7 (2013) Android Development] ud4:
No, just change your recovery to lineage recovery or to my TWRP build
[Nexus 7 (2013) Android Development] ud4:
First, use recovery for flox, after that format the vendor partition and install the ROM. And finally, make sure that you have performed repartition!
[Nexus 7 (2013) Android Development] GeekyTanuj:
Is it okay if I used CROSS utility to repartition before?
[Nexus 7 (2013) Android Development] ud4:
I have not tested this method, anyway, you can try it
[Nexus 7 (2013) Android Development] DrSnowHR:
Where do you type the command "Stock" or "modify", Is it from our PC Powershell with "ADB shell" first ?

I'm also doing it from stock 6.0.1 Official ROM.

Thank you.
[Nexus 7 (2013) Android Development] ud4:
From stock — modify
[Nexus 7 (2013) Android Development] DrSnowHR:
Stock did not work for me but i did directly modify by bypassing the error 21.

I sucessfully install Lineage OS (and i can boot to it) but when trying to install GAPPS even with Pico packages, it is always saying "insufficient space".

Any idea on how to unlock the situation ?

Thank you.
[Nexus 7 (2013) Android Development] ud4:
Use TWRP as a temporary solution, in the next build of recovery (should be tomorrow along with the main build) it will be fixed
[Nexus 7 (2013) Android Development] weresgyufa:
Hello.

I used the modifyed TWRP from the post Nr.:46. When the TWRP was on the tab I run the repartition.zip from the same post under TWRP and when the installation was done then First I gon in TWRP → go "Advanced→Terminal"→ and enter "stock" when it was done then I I stall the repartition.zip ágán but in this time I type to the terminal the command "modify".

When this runs down then copy from the PC to the tab the LOS and install it, and install GAPPS too. When it's done clear dalvik and cache, reboot and it's done.
[Nexus 7 (2013) Android Development] DrSnowHR:
Hello,

it is working now with TWRP, i did installation of Gapps nano.

But me i just bypass error 21 with normal modify command and everything seems to be fine.

Only netflix is having error 502.1019, Will it be correct with an OTA update or do i need to reinstalled everything again ?

Thank you so much
[Nexus 7 (2013) Android Development] RunnersFoot:
I was using elementalX on the regular 17.1 but since switching to FLOX it doesn't seem it works anymore. Also looking for a overclocking kernal.
[Nexus 7 (2013) Android Development] Mr.Conkel:
Elemental X works perfectly however you need to flash in this order. Twrp (flox build) > Lineage official > Twrp Official build from website > Kernel of your choosing elemental X in this case > Twrp (flox build) this way you don't have any issues with updates.

The reason this works as far as ik are pretty simple when using flox TWRP the device isn't considered as flo and therefore aren't any kernels for flox but if you use the official twrp to change back to flo the kernel will pass. Then switch recoveries again to assure no issues with updates in the future. Good luck!!
[Nexus 7 (2013) Android Development] weresgyufa:
I updated to the 2020.12.28. Build and I have a strange Languag bug... I use the tab as Hungarian, the etup was one on this language, but if I want to change to English then it looks like this☹️

This is a bit strange... I think this is not normal.
[Nexus 7 (2013) Android Development] weresgyufa:
And another strange issue...the swipe right to see google news are also not working. It says : there is some issue during login to account, please try again. If I known right, then this app is integrated to the Launcher. I installed google news but is it possible to change it to it or there is no chance for this.
[Nexus 7 (2013) Android Development] Mr.Conkel:
Have you tried a clean flash? Take a data back up first then try clean. Dunno why dirty wouldn't work but there may be unique issues. I'm going to update myself rn and report back.

EDIT - I did the update and everything is working fine for me. Unfortunately it could be related to your setup. I'd recommend starting over however everything works as normal for me.
[Nexus 7 (2013) Android Development] pedritopl:
Is it only me or the Magisk addon.d survival doesn't work on flox? It's the second weekly update I did (2020-12-14->2020-12-21->2020-12-28) and both times I had to re-install Magisk (21.1) manually after update.

I'm using the flox TWRP (from post #2).

There seems to be something wrong with backuptool.sh.

Is it a problem with my flox or a common/known issue?

Full recovery log: https://del.dog/lelagoghoc

Most interesting parts:

1) before flash of lineageos zip:

Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted file "/tmp/install/bin/resize2fs_static"
Extracted 3 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
grep: /tmp/gapps.prop: No such file or directory
Patching system image unconditionally...

2) after flash of the zip:

about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Segmentation fault
xargs: /data/adb/magisk/busybox: No such file or directory
[Nexus 7 (2013) Android Development] osm0sis:
Try latest canary
[Nexus 7 (2013) Android Development] pedritopl:
That was a quick & easy fix ;-)

Thanks. Confirmed to be working properly with current Magisk Canary.
[Nexus 7 (2013) Android Development] JohnDovas:
anybody knows why I can't update to the 28th version? error comes up after I click ok to boot into recovery.
[Nexus 7 (2013) Android Development] anivegmin:
Same here for the last two updates.

I download the updates manually from LineageOS and install with TWRP.

(you can then go to the updater, if you tried that first, and delete the update file to save storage space).
[Nexus 7 (2013) Android Development] ultramaximum:
Which version of ElementalX do you use?

I tried your method but I only get a bootloader loop after installing the kernel.

I used ElementalX-N7-6.17 from https://elementalx.org/devices/nexus-7-2013/
[Nexus 7 (2013) Android Development] Mr.Conkel:
I am using the latest A10 Kernel. This is NOT my work nor do I have any affiliation with the files created I am only providing easy access to them.

Direct link (gDrive here) - ElementalX-N7-7.02-TEN-20201005-AK3.zip - Google Drive

Followmsi's original Gdrive here - Folder - Google Drive

If you use followmsi's link make sure you grab the latest A10 Elemental it can be a bit tricky to find but let me know if you need help. Because the files are not in order.

Cheers 🥂
[Nexus 7 (2013) Android Development] ultramaximum:
Thank you! Now it works perfectly.
[Nexus 7 (2013) Android Development] Mr.Conkel:
Just apply your update manually. I normally never use the updater I usually do them myself all lineage os updates can be found in /data/lineageos_updates
[Nexus 7 (2013) Android Development] leetripper:
Yes, it's fixed (Netflix)! Thank you devs!
[Nexus 7 (2013) Android Development] Vincent_40:
Hi all,

I'm on 21/12 build and i can't see internal storage with my PC (W10).

Do you have an advice ?
[Nexus 7 (2013) Android Development] jota29:
Can the the 'fastboot flash *name of recovery file*' be done without problems after

or what is it that fixes the 'size to large' error?
[Nexus 7 (2013) Android Development] Jvino:
My USB was rock-solid. Until I tried to root the tablet and install Magisk. I likely did something wrong, and the USB is now very flaky. I can get i to work, but it is unstable. So, is your tablet rooted? If so try to get to internal storage through recovery. If it's solid there, like mine, then the rooting is the problem. At least there is still a way to move files outside of adb push/pull.
[Nexus 7 (2013) Android Development] Vincent_40:
Yes exactly, my tablet is rooted to use Viper.

So if it's the problem, i'll uninstall Magisk to check if problem disappears.

Thx for your reply 👍
[Nexus 7 (2013) Android Development] Jvino:
I uninstalled magisk, and it didn't help. I needed to reflash Dec 28 Rom to fix it.