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

[OFFICIAL] LineageOS 18.1 for the Nexus 7 (2013, Wi-Fi) - Repartition Only (flox)

Search This thread

Kaar3l

Senior Member
Oct 4, 2011
92
36
Tried and it doesn't work.
Could you compile kernel with emmc patch?
I compiled the kernel and got eMMC 5.1 work.
 

mathiraj

Member
Apr 24, 2009
12
0
Nexus 7 (2013)
Moto E6
Thank you very much for this ROM. This has given a new lease of life to my Nexus 7 tablet.

I installed the July 12th build. It is working just fine.
Now, it shows there is an update (July 19th, build). If i install it via the updater, the tablet just reboots to TWRP and nothing happens after that. I've searched for information and didn't find anything relevant. How to get this update installed via updater?
 

ssauger

Senior Member
Aug 12, 2010
1,369
657
Thank you very much for this ROM. This has given a new lease of life to my Nexus 7 tablet.

I installed the July 12th build. It is working just fine.
Now, it shows there is an update (July 19th, build). If i install it via the updater, the tablet just reboots to TWRP and nothing happens after that. I've searched for information and didn't find anything relevant. How to get this update installed via updater?
Think its cause TWRP, the updater needs linage recovery. After you downloaded it you can move it, but for me i dont know the location after that. So i donload it via browser, then i can see the download location and update it with TWRP recovery.
 

Topster77

Member
Dec 18, 2016
24
3
Good to hear.

Old tablet, is your battery original? Cause it has to be really old at this point lol.

Nah, 8.1 kernel has 0% chance of working here - our kernel built-in is pretty well tuned...

*dirty-upgrades - and it's noted on the wiki upgrade guide that you must format on upgrade from 17.1 to 18.1.

Sad fact of a device this old BUT 18.1 to 19.0 (if flox lives that long) should be fine on the affected devices.
Well, this is the original battery, but only with few charging cycles. Note, when switched off, the battery only loosed 6% over 44 days. I assume this is not too bad.

Is there any method to get a closer view to the battery status?
 

sunny1981

New member
Aug 7, 2021
1
0
I can't get Hulu app to work. I keep getting a notification that says "Hulu keeps stopping". I have tried downloading the app from the app store, and downloading the latest apk with the same results. Any help or guidance would be greatly appreciated. Thanks in advance.
 

mirkoPigna77

Member
Nov 4, 2014
20
1
Hi All,

I am following the official instructions with twrp recovery but it always fails at
Code:
fastboot -w

with the error:

Code:
Erasing 'userdata'                                 OKAY [ 16.879s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 6997491 4k blocks and 1749664 inodes
Filesystem UUID: 3aefeccf-2820-4120-be54-ecc505992ea3
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done   

Sending 'userdata' (180 KB)                        OKAY [  0.012s]
Writing 'userdata'                                 FAILED (remote: 'Bogus size sparse and chunk header')
fastboot: error: Command failed

I am able to go back to stock with the original Google images, getting the same error but by manually flashing the stock images with
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot

I get it working fine.

However, those .img are not found in the lineage zip archive so any suggestions?


Many thanks
 

npjohnson

Recognized Developer
Hi All,

I am following the official instructions with twrp recovery but it always fails at
Code:
fastboot -w

with the error:

Code:
Erasing 'userdata'                                 OKAY [ 16.879s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 6997491 4k blocks and 1749664 inodes
Filesystem UUID: 3aefeccf-2820-4120-be54-ecc505992ea3
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000

Allocating group tables: done                          
Writing inode tables: done                          
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done  

Sending 'userdata' (180 KB)                        OKAY [  0.012s]
Writing 'userdata'                                 FAILED (remote: 'Bogus size sparse and chunk header')
fastboot: error: Command failed

I am able to go back to stock with the original Google images, getting the same error but by manually flashing the stock images with
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot

I get it working fine.

However, those .img are not found in the lineage zip archive so any suggestions?


Many thanks
instead of fastboot -w just do fastboot erase userdata.

Proceed with install. For some reason your fastboot binary is being weird.
 
  • Like
Reactions: mirkoPigna77

MbareJack

Member
Apr 12, 2020
23
4
Hi all.. I'm on LOs nougat, the tablet is fast and smooth but the problem is the battery, i have a huuuge battery drain, i can see the "%" go down while i simply scroll on browser or playstore.. How is this rom for battery? Do you reccommend this or the old android MM stock rom? Somone say that the problem can be caused by the google play services.. Any suggestion?
 

BLewis4050

Member
Apr 18, 2014
38
13
Just updated again:
  • TWRP 3.5-90Flox
  • LineageOS 18.1 2021.08.02
  • OpenGAPPS 11 Arm Nano
  • Magisk 23.0
Working smooth as butter!!
Dirty flash update to Aug 30 build - working great!
Just updated again:
  • TWRP 3.5-90Flox
  • LineageOS 18.1 2021.08.02
  • OpenGAPPS 11 Arm Nano
  • Magisk 23.0
Working smooth as butter!!
Just updated again:
  • TWRP 3.5-90Flox
  • LineageOS 18.1 2021.08.02
  • OpenGAPPS 11 Arm Nano
  • Magisk 23.0
Working smooth as butter!!

Screenshot_20210830-111846_Trebuchet.png
 
  • Like
Reactions: zeromega

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Hi ! Anyone else having trouble installing some apps from Google Play? They download to 99% and after it should go to install the app, it fails. But that is not the case for other apps. I have attached 4 screenshots. I have tried force stop and clearing data and cache for Download Manager, Google Play, Google Play Services, Google Services Framework, Package Installer and removing my google account and rebooting my flo. I have tried to repartition back to stock and then go back to flox partition . I am on 09.09 build . I have tried flashing LineageOS 18.1 with twrp 3.5 for flox and with Lineage Recovery. I have tried combinations with MindTheGapps and latest OpenGapps ARM Nano. I can't seem to install some apps from the Google Play Store no matter what I do. I can successfully install and run the .apk of the problematic apps from a different source just fine. The device is not rooted. Can you guys help? Thanks in advance !
    You can search flox kernel on the androidfilehost,and flash the latest kernel with twrp.
    2
    @npjohnson, any chance of adding any other tweaks from the EX Kernel base like GPU OC, etc.? The list from @kiraryu's last unofficial EX build (P.S. @kiraryu, where is the source hosted? And new security patches would be nice..) are as follows:

    Code:
    Flox kernel Changelog(2021/09/14):
    Based on ElementalX-N7 kernel 3.4.113
    Update to 2019-07-05 Kernel security patch level
    Fix wifi driver to scan the hidden SSID
    Remove BFQ I/O Scheduler,it causes kernel panic.
    Set CFQ I/O Scheduler to Default when Magisk 23 is installed
    Disable s2w by default when Magisk 23 is installed
    Enable zram by default when Magisk 23 is installed
    Fix wlan: RX Low resource when download large files
    Disable 802.11d to prevents 5ghz wifi change to wrong crda country based on AP.
    Update ext4 fs driver
    Update fuse fs driver
    Update msm crypto driver
    Update sdcardfs fs driver from kernel 4.4
    Fix install app with obb file on google play.
    prima: add FragAttacks WiFi vulnerabilities patch
    Disable Qualcomm Crypto accelerator to fix battery drain.

    Also would you be able to add the Nexus Qualcomm Preview/Beta GPU firmware blobs?

    I've kept them archived here: https://androidfilehost.com/?w=files&flid=312875

    They have V145 firmware instead of the stock V127, and the last stable one for deb/flo from my (years of) testing was Adreno-Nexus7-MMB29Q from adreno_nexus_feb2016. After that they went buggy on N7, and of course Qualcomm ended up closing the Preview program before pushing any updated drivers to Google. The feb2016/MMB29Q N7 firmware is solid and increase benchmarks quite nicely last time I checked, for what that's worth, and made things smoother on all ROMs I've tried, including your current flox. 🤞


    > Update to 2019-07-05 Kernel security patch level

    Not sure what this means, if it's kernel ASB stuff, please push to gerrit, would love to merge it.

    > Fix wifi driver to scan the hidden SSID

    Point me at the commit

    > Remove BFQ I/O Scheduler,it causes kernel panic.

    Uhhh, what?

    > Set CFQ I/O Scheduler to Default when Magisk 23 is installed

    I mean, eh, schedulers can help but not sure which is better here

    > Disable s2w by default when Magisk 23 is installed

    No, this won't be enabled.

    > Enable zram by default when Magisk 23 is installed

    Push it to gerrit

    > Fix wlan: RX Low resource when download large files
    > Disable 802.11d to prevents 5ghz wifi change to wrong crda country based on AP.
    > prima: add FragAttacks WiFi vulnerabilities patch
    Show me the commits?

    > Update ext4 fs driver
    > Update fuse fs driver
    > Update msm crypto driver
    > Update sdcardfs fs driver from kernel 4.4
    Probably not...

    > Disable Qualcomm Crypto accelerator to fix battery drain.

    Explain this one?

    > Preview blobs - sorry, probably not - if we have a different device we want to kang from we /can/ but I'd want to see good reason to do so for sure.
    2
    @npjohnson Here are relevant logcat and dmesg from trying to connect to a valid WPA2-PSK/WPA3-SAE Mixed Mode network (i.e. all my other current devices work, including my wife's finicky old MacBook Pro) in case it helps fix:

    logcat:
    Code:
    D/WifiNl80211Manager(  574): Scan result ready event
    D/WifiNative(  574): Scan result ready event
    W/wificond(  404): Copy constructor is only used for unit tests
    W/wificond(  404): Failed to get NL80211_ATTR_EXT_FEATURES
    W/wificond(  404): Copy constructor is only used for unit tests
    W/wificond(  404): Failed to get NL80211_ATTR_EXT_FEATURES
    W/wificond(  404): Copy constructor is only used for unit tests
    W/wificond(  404): Failed to get NL80211_ATTR_EXT_FEATURES
    W/wificond(  404): Copy constructor is only used for unit tests
    W/wificond(  404): Failed to get NL80211_ATTR_EXT_FEATURES
    D/WifiClientModeImpl(  574): CMD_START_CONNECT  my state DisconnectedState nid=2 roam=false
    W/LastMileLogger(  574): Failed to open free_buffer pseudo-file: /sys/kernel/debug/tracing/instances/wifi/free_buffer: open failed: ENOENT (No such file or directory)
    W/LastMileLogger(  574): Failed to arm fail-safe.
    I/WifiClientModeImpl(  574): Connecting with [*redacted*] as the mac address
    E/wificond(  404): Received error messsage: Operation not supported on transport endpoint
    E/wificond(  404): NL80211_CMD_ABORT_SCAN failed
    W/wificond(  404): Abort scan failed
    D/SupplicantStaIfaceHal(  574): connectToNetwork "[*redacted*]"WPA_PSK
    D/SupplicantStaIfaceHal(  574): Network is already saved, will not trigger remove and add operation.
    I/WifiService(  574): connect uid=10156
    D/WifiConfigManager(  574): Enable disabled network: "[*redacted*]" num=0
    E/WifiPermissionsUtil(  574): isDeviceOwner: packageName is null, returning false
    D/WifiConfigStore(  574): Writing to stores completed in 14 ms.
    D/WifiClientModeImpl(  574): connectToUserSelectNetwork netId 2, uid 10156, forceReconnect = false
    I/WifiClientModeImpl(  574): connectToUserSelectNetwork already connecting/connected=2
    D/WifiNl80211Manager(  574): Scan result ready event
    I/wpa_supplicant(  813): wlan0: Trying to associate with SSID '[*redacted*]'
    D/WifiNative(  574): Scan result ready event
    I/wpa_supplicant(  813): wlan0: Association request to the driver failed
    E/wlan    (    0): [813:E :HDD] wlan_hdd_set_akm_suite: Unsupported key mgmt type 1027078
    E/wlan    (    0): [813:E :HDD] wlan_hdd_cfg80211_set_privacy: failed to set akm suite
    E/wlan    (    0): [813:E :HDD] wlan_hdd_cfg80211_connect: failed to set security params
    D/WifiClientModeImpl(  574): CMD_START_CONNECT  my state DisconnectedState nid=2 roam=false
    W/LastMileLogger(  574): Failed to open free_buffer pseudo-file: /sys/kernel/debug/tracing/instances/wifi/free_buffer: open failed: ENOENT (No such file or directory)
    W/LastMileLogger(  574): Failed to arm fail-safe.

    dmesg:
    Code:
    [57628.922302] wlan: [404:E :HDD] wlan_hdd_get_station_stats: SME timeout while retrieving statistics
    [57629.684722] cfg80211: Calling CRDA to update world regulatory domain
    [57629.685150] ieee80211 phy0: info: cfg80211 reg_notifier callback for country 00
    [57629.685180] ieee80211 phy0: country: WS set by driver
    [57629.685180] cfg80211: World regulatory domain updated:
    [57629.685241] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [57629.685363] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [57629.685455] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [57629.685577] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [57629.685638] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [57629.685729] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [57629.686096] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [57630.045806] wlan: [796:E :SME] csrNeighborRoamIndicateDisconnect: 3742: Disconnect indication on session 0 in state 2
    [57630.046020] wlan: [796:E :TL ]  ----> CRegion 0, hRSSI -47, Alpha 5
    [57630.046203] wlan: [796:E :TL ]  ----> CRegion 0, hRSSI -47, Alpha 5
    [57630.046661] wlan: [796:E :HDD] hdd_tdlsStatusUpdate: DEL_ALL_TDLS_PEER_IND staIdx 0 00:00:00:00:00:00
    [57630.046661]
    [57630.047668] wlan: [796:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
    [57630.047790] wlan: [796:E :PE ] limSendDisassocCnf: 3511: FT Preauth Session (de760000,0) Cleanup
    [57630.059570] wlan: disconnected
    [57630.059661] wlan(0) 00:00:00:00:00:00 Standalone
    [57630.068084] wlan: [813:E :HDD] wlan_hdd_set_akm_suite: Unsupported key mgmt type 1027078
    [57630.068267] wlan: [813:E :HDD] wlan_hdd_cfg80211_set_privacy: failed to set akm suite
    [57630.068359] wlan: [813:E :HDD] wlan_hdd_cfg80211_connect: failed to set security params
    [57630.134124] wlan: [813:E :HDD] wlan_hdd_set_akm_suite: Unsupported key mgmt type 1027078
    [57630.134216] wlan: [813:E :HDD] wlan_hdd_cfg80211_set_privacy: failed to set akm suite
    [57630.134338] wlan: [813:E :HDD] wlan_hdd_cfg80211_connect: failed to set security params

    Can confirm the same issue on 20210920 stock Lineage kernel as well.
    Try reverting this by hand https://review.lineageos.org/c/LineageOS/android_device_asus_flox/+/296493

    If this works pls let me know.
  • 21
    lineage-os-logo.png

    Nexus 7 (2013, Wi-Fi)

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 18.1 thread for the Nexus 7 (2013, Wi-Fi).

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • None.
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
    • This device _must_ be repartitioned before installation, the only supported repartition package is the one listed in the Wiki linked above - please make sure you followed it before attempting to install!
    • `debx` support may come at some point in the future, but considering neither I or the other maintainer have one, it is unlikely, feel free to step up and do it! If you do, feel free to reach out to [email protected] and I'll help you get official builds rolling.
    Kernel Source: https://github.com/LineageOS/android_kernel_google_msm
    3
    Hi ! Anyone else having trouble installing some apps from Google Play? They download to 99% and after it should go to install the app, it fails. But that is not the case for other apps. I have attached 4 screenshots. I have tried force stop and clearing data and cache for Download Manager, Google Play, Google Play Services, Google Services Framework, Package Installer and removing my google account and rebooting my flo. I have tried to repartition back to stock and then go back to flox partition . I am on 09.09 build . I have tried flashing LineageOS 18.1 with twrp 3.5 for flox and with Lineage Recovery. I have tried combinations with MindTheGapps and latest OpenGapps ARM Nano. I can't seem to install some apps from the Google Play Store no matter what I do. I can successfully install and run the .apk of the problematic apps from a different source just fine. The device is not rooted. Can you guys help? Thanks in advance !
    You can search flox kernel on the androidfilehost,and flash the latest kernel with twrp.
    2
    I upgraded this device and I can't seem to go through a smooth 17.1 upgrade to 18.1 because I have a lock screen pin/pattern and every time I tried, the lock screen would crash as soon as I entered my pin. I saw that some other users had this problem on other devices, just thought I might want to bring that forward here on the new thread.