whyyyyy - the wiki works for this - you added so much stuff that doesn't need to be done lol.For those who don't have stock Android on this device anymore and want to switch to official LineageOS 18.1:
I had some problems installing official LineageOS 18.1 after I had tried out other unofficial ROMs. After several repartioning and wiping, I figured out a solution that worked for me. Strangely, only specific TWRP versions where able to work for this. For instance, I needed a custom TWRP version from user followmsi in order to run the repartition script from CROSS correctly, but needed another to be able to flash LineageOS (TWRP version must be compatible with the demand of "flox" from the LineageOS install script, in case you want to flash via updater).
So here are the steps:
- boot into bootloader (fastboot mode) by pressing Volume Down + Power button
- boot TWRP recovery via fastboot: "fastboot boot twrp-3.7.0_9-0-flo_followmsi.img"
- in TWRP: wipe all partitions + format data "yes"
- in TWRP: go to "Advanced" > "ADB sideload"
- on PC: "adb sideload sysrepart-ultimate.zip" (for 32GB version)*, wait until finished
*"adb sideload sysrepart-ultimate-2.zip" (for 16GB version)
- from TWRP, reboot to bootloader
- flash recovery: "fastboot flash recovery twrp-3.5.0_9-0-flox.img"
- boot recovery: choose "Recovery mode" via Volume Up/Down, confirm with Power button
- in TWRP > Wipe > Advanced Wipe > wipe all partitions (except Vendor), format data "yes"
(wipe several times to make sure partitions will be okay; I had some issues with this before)
- trim system: "adb sideload k23m-fstrim.zip" (optional)
- reboot into TWRP
- flash latest LineageOS: "adb sideload lineage-18.1-xxxxxxxx-nightly-flox-signed.zip"
- flash OpenGapps (optional): "adb sideload open_gapps-arm-11.0-pico-xxxxxxxx.zip"
- reboot into system
Magisk can be installed right after setting up LineageOS:
- in TWRP, flash Magisk.zip and reboot
- install Magisk.apk in LineageOS, start Magisk and follow instruction and reboot
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 Stock to Android 13 [GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 LTE/deb or Wi-Fi-only/flo to Android 13 / LineageOS 20 with Netflix/Disney+ working This detailed step-by-step guide helps you transform...forum.xda-developers.com
sysrepart-ultimate.zip (for 32G device) / sysrepart-ultimate-2.zip (for 16GB device)
Nexus 7'13 CROSS - Custom ROM Scripted Setup (c)2020-2021 k23m CROSS works on PC with Windows, or WinPE if you do not have Windows installed, or VirtualBox with a Windows guest. Currently supported ROMs: - Android 10 LineageOS 17.1 - Android...forum.xda-developers.com
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your warranty is now void. * * I am not...forum.xda-developers.com
k23m-fstrim.zip (extracted from CROSS zip)
OpenGapps, size "Pico" (Android 11, ARM):
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.opengapps.org
Thanks again -- I just installed the May 1 build with Open G-Apps PICO successfully!I think this should fix the next build: https://review.lineageos.org/c/LineageOS/android_device_asus_flox/+/353324
lol on the 13 gb system partition - as for AFH - try now?@npjohnson I was unable to download the recommended repartitioning script. AFH says Oops! No mirrors found. I have noticed that this has been happening recently on files that have been there for years. Can you upload it elsewhere?
The other ones I tried didn't work and/or are dangerous.
I tried the one on Clamor's github and it didn't recognize my eMMC (16GB HAG2e). Then I tried sysrepart-ultimate.zip from another thread. It left me with a 13GB system partition and no data partition! I thankfully could manually fix this using parted, but it freaked me out and most people would not be able to fix it themselves.
AFH has been flaky. Here's a mirror. (The md5sum matches the one listed on the AFH page.)
You are not following the guide. Your device is in fastboot, boot to recovery.hi, I'm following the instructions to upgrade my nexus 7. after a fastboot the recovery image, I them enter recovery mode and now I have a broken android.
I can see the device in fastboot but not adb
adb.exe: no devices/emulators found
I've done the following
You do have the nexus 7 2013 right?I've done the following
C:\Users\georg\Downloads\nexus7>fastboot boot lineage-18.1-20230505-recovery-flox.img
Sending 'boot.img' (10962 KB) OKAY [ 1.418s]
Booting OKAY [ 0.016s]
Finished. Total time: 1.496s
The nexus 7 just sits there. I restart, select recover, then just get the Broken Android image.
I dont have an option to go into advanced, enable ADB.
so stuck at the EFS backup step
You probably need to reseat the cable. See this video.
I was about to comment this, that cable comes loose really often on this device and it sucks.
I haven't tried it on Stock 6.0.1 but other users have reported strong performance on the latest builds. However you will lose split screen multitasking but I'm looking into thatCan someone please confirm how is the performance on these builds?
I am currently running the official build which was the last 6.0.1.
I mainly use this device for YouTube and watching streaming stuff. The performance is pretty slow while browsing in chrome.
Can I expect better performance then stock?
Let me concur that proper seating of the ribbon cable is critical. Replacing a broken screen can lead to this problem, but it's also quite possible for the ribbon cable to lose proper connection all on its own.
- Your warranty is now void. - You have been warned. - Use at your own risk.
You can search flox kernel on the androidfilehost,and flash the latest kernel with twrp.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 !
All of these patches are now merged - the OOB file issues should now be fixed!Pick below three patches will fix the mount point of obb. https://github.com/LineageOS/androi...dd5c3139de87400a6c6601ad3f54621e9d238fb.patch