yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Jvino:
I had a couple of boot.img to choose from. I chose the wrong one, I guess. Reflashed 28 Dec ROM and extracted the Boot.img from that. Then used Magisk Manager to patch the img, reflashed boot with it and the USB problem went away. And I have a rooted tablet. It was me trying to save time using the boot.img I had rather than extracting the real one in use.
[Nexus 7 (2013) Android Development] ud4:
After repartition you can just flash recovery, so as you wrote
[Nexus 7 (2013) Android Development] moviefirst:
Youtube playing isn't possible in 1080p?

edit: ignore above message, 1080p is working fine! My mistake!
[Nexus 7 (2013) Android Development] Jvino:
I can. Provided the stream is 1080. do you have a specific example? I Just watched a bunch of Jeep tutorials in 1080p - full screen.
[Nexus 7 (2013) Android Development] moviefirst:
1080p working fine, sorry, didn't look at 1080p video.
[Nexus 7 (2013) Android Development] adam_545:
WiFi is working on my tab, but there is no way to establish connection via first startup wizard (sees the AP, seems to be connected but no data transmitted and the WiFi network is not saved).

After exiting from the wizard, from Settings the connection can be established and a notification appears to continue the wizard.

Is there a way to enlarge the system partition to install more gapps than micro?

The assistant is not working saying not able to download voice model (even if the model is removed using other device).
[Nexus 7 (2013) Android Development] k23m:
I have created an alternative single-click re-partition script which safely and easily generates the "UA" /flox partitions...

--- Go to to the CROSS thread and run

lineage-install-2-flox.bat

CROSS2 script to install everything automatically.
[Nexus 7 (2013) Android Development] Syntax_Error_:
For those, who don't need sim-function on their deb-devices - installation works like a charme after repartitioning.

lineage-17.1-20201228-nightly-deb-no-sim.zip

But remember: Sim card support doesn't work any longer. Only Wifi !
[Nexus 7 (2013) Android Development] xbs:
Great rom coming from unofficial, had to clean install for netflix to work. Thanks for your work

Any kernel with double tap to wake support I can use?
[Nexus 7 (2013) Android Development] j4smith:
Could you please build the latest TWRP 3.5.0 for flox? Thanks!

Also, maybe add flox to TWRP official devices list?
[Nexus 7 (2013) Android Development] radiofreee:
Screen rotation is not working for me. I've done a clean install and reinstalled again, but the screen still doesn't rotate. For the rest everything seems to work fine.

At first i had problems with partitions i couldn't flash recovery flox. My fault, I had not read the final message to write to the terminal "modify" when i install flo-deb_clamor_repartition_20201203.zip. Once the partitions were modified correctly everything went well. Magisk Ok

Gapps Pico, I had to use TWRP for flox to complete the installation.
[Nexus 7 (2013) Android Development] Jvino:
Can you confirm your accelerometer is working (assuming auto rotate is indeed selected from the pull-down menu)? There are apps to read it in the Play Store.
[Nexus 7 (2013) Android Development] radiofreee:
Seems to be not working. I have installed the App: Sensor Test an I get this message: "This sensor doesn't report any readings. seems you have error with sensor service in device firmware"

It even seems that all the sensors are not working. Light sensor, Compass and Accelerometer.

I remember getting a mesage at beginning, when I was trying to install flox without partitioning the device. Something about "Vendor Error" . Could it be related?
[Nexus 7 (2013) Android Development] Jvino:
Just to ensure we are on the same page, the app I have is called sensor tool box. When I installed it, I need to approve many access permission rights, and then reboot the tablet before it functioned (many moons ago, mind you). This works quite well with the tablet and this ROM. Was the installation the same with your tablet? Your tablet is WiFi-only, right? Just need to cover all bases.
[Nexus 7 (2013) Android Development] radiofreee:
Yes is a FLO version (wifi) I just installed Sensor ToolBox and rebooted the tablet. Light sensor, GPS working fine. Accelerometer and Giroscope have no Name and Vendor ID. All the others sensors have (Gps, Light, Magnetic, Gravity, Rotation Vector, Line accelerator) have name, vendor and version.

I did not backup when I partitioning the device. I might have lost something when i formatted ? My root/mnt/vendor/ folder is empty. It is normal? I read something about Sensors Bug.

Tank You for your time
[Nexus 7 (2013) Android Development] Jvino:
Sounds like the hardware is good. There is a vendor binary in the ROM. But now this probably needs a smarter person than me to help. I would try another full clean reflash of dec 28 ROM. If there are any errors during that, they should be mentioned here.
[Nexus 7 (2013) Android Development] radiofreee:
Surely you are smarter than me in such matters. Anyway thanks for trying.

I am going to reset the tablet to the stock image, although I have not seen that it contains vendor.img and now it will be repartitioned. I hope everything works.

Thanks
[Nexus 7 (2013) Android Development] Jvino:
/vendor, itself, I believe is in the system.img partition file. There are java script and other files in Brotli compressed format for patching from one Android version to another and supporting specific platform hardware that is not part of ASOP, I think. in the LOS 17.1 ROM, you should see a number of vendor.br files for this. Factory image would not have the .Br files, only the system.img.

You should check the condition of your battery as well. Sensor Toolbox has that info. I have heard strange stuff happens when the battery is hosed. The way I learn is to try and overcome problems. But when I flashed LOS 17.1 on my Nexus 7, all went perfectly and it just worked. Well, except for SlimPort, but that seems to be a huge problem, perhaps impossible to fix. Learning the cause of your problem, when you discover it, would be a great thing to know.
[Nexus 7 (2013) Android Development] radiofreee:
Interesting information about Vendor.img and battery condition.

I restored to the Stock v. 6.1. They did't work, stuck on boot. Now I will reinstall LineageOS 17.1 and keep looking for a solution, if there is one.
[Nexus 7 (2013) Android Development] radiofreee:
Well, it already works. The problem was not software but hardware. After searching for a while I found this post https://xdaforums.com/t/accelerometer-and-compass.3383223/ and then I saw this video. Five minutes later, it was working.

Without your clarification that the accelerometer should work correctly and that vendor.img has nothing to do with the problem, it would not have occurred to me to do a more general search and not related to LineageOS.

Thanks again for your time,

a greeting
[Nexus 7 (2013) Android Development] Jvino:
Fantastic! I happy for you. I loved the video. I would not have thought of reseating that cable. I've played with it often, but not for this issue. Great lesson, thanks. And happy I could help in some way, but you found the problem and solved it.
[Nexus 7 (2013) Android Development] reddfoz:
Until I read your post I though all was fine apart from Bluetooth not working on my device, it turned out the screen wouldn't rotate and none of the sensors worked either. So back to the start and try everything over again about 15 times :) . I like you had noted in the original setup the /Vendor partition error and then noted it would not mount and the system error 7, E: footer errors and E2001 Vendor error etc.. all to do with the Vendor partition.

This time I used the TWRP recovery from ud4 instead of the custom recovery as outlined in the wiki instructions, into TWRP ADB sideload and sideloaded the clamor_repartition then followed the instructions TWRP gave on the Nexus 7 screen, go back into advanced then into the terminal on the Nexus 7 and type modify and like magic after 2 attempts it worked and vendor partition returned perfectly and mountable. Then using k23m amazing tools from the post above re-ran the script and everything re-installed and now works perfectly. So nice to see may amazing Nexus 7 back in full working order I always loved this little tablet.
[Nexus 7 (2013) Android Development] reddfoz:
Until I read your post I though all was fine apart from Bluetooth not working on my device, it turned out the screen wouldn't rotate and none of the sensors worked either. So back to the start and try everything over again about 15 times :) . I like you had noted in the original setup the /Vendor partition error and then noted it would not mount and the system error 7, E: footer errors and E2001 Vendor error etc.. all to do with the Vendor partition.

This time I used the TWRP recovery from @ud4 instead of the custom recovery as outlined in the wiki instructions, into TWRP ADB sideload and sideloaded the clamor_repartition then followed the instructions TWRP gave on the Nexus 7 screen, go back into advanced then into the terminal on the Nexus 7 and type modify and like magic after 2 attempts it worked and vendor partition returned perfectly and mountable. Then using @k23m amazing tools from the post above re-ran the script and everything re-installed and now works perfectly. So nice to see may amazing Nexus 7 back in full working order I always loved this little tablet.
[Nexus 7 (2013) Android Development] P373:
Just wanted to install Recovery, but no way.

Flashed Flox Recovery from official guide:

After that booted in fastboot and selected 'recovery mode'. But now the google screen (unlocked) is freezing and nothing happens.

Also flashed the new Flox TWRP:

But also nothing happens after selecting 'recovery mode' in fastboot.

In the guide it is called 'recovery' and not 'recovery mode'. Do I have to update anything else before flashing the recovery?

Thx in advance!
[Nexus 7 (2013) Android Development] Jvino:
Is the boot loader unlocked and USB debugging enabled in developer options?
[Nexus 7 (2013) Android Development] P373:
Yes, adb is working in Adroid. Fastboot is also working. But I can only boot into android recovery (not the flashed recovery (los or TWRP)).
[Nexus 7 (2013) Android Development] Jvino:
From what you said : " Google screen unlocked", this is the robot with the open door. Right? If so, Power off the tablet (hold the power button for a bit) and try this:

With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons. Use the volume buttons to scroll to “RECOVERY” and press Power to select

Hopefully the screen will not be frozen after that boot and the volume keys will work.
[Nexus 7 (2013) Android Development] P373:
I did this a lot of times before, but when I am in bootloader an select the menu points there is no menu entry 'recovery'. It is called 'recovery mode' in my bootloader (Version 4.23). When I select the entry 'recovery mode' the device deactivates connenction via USB an shows the "Google Logo (unlocked)". But at this time there should be loaded the flashed recovery I think.

By random in some cases (when I press a unknown key combination?) at the time where the Google Logo appears the devices goes into a mode where is shown an android with red symbol:

Now I press Power + Volume Up an release. Then the screen shows the Android system recovery:

But I have flashed already the lineage recovery in fastboot. I don't understand.
[Nexus 7 (2013) Android Development] Jvino:
AH! I understand now (I just rebooted to follow you). The Google logo with the unlocked padlock at the bottom. Yes, it should go to recovery after a few seconds, if it got that far. And yes, mine says "Recovery Mode" as well. If it hangs at that Google logo, it sounds like the recovery flash was incomplete or corrupted. Strange, since flashboot stated complete and okay. Mine takes about 10 - 15 seconds to get to the TWRP Logo from "Google unlocked", but it does get there. I currently have no idea what would cause these symptoms.
[Nexus 7 (2013) Android Development] Jvino:
Post an image of your bootloader screen.
[Nexus 7 (2013) Android Development] reddfoz:
As above is correct from the bootloader screen sometimes when you select recovery hold the Volume Up Key just before the google logo appears and keep it held until the recovery screen appears hopefully TWRP it can take a little bit of time.

I'm assuming as you are loading this version of TWRP you have followed the instructions from the Wiki page Install LineageOS on flox | LineageOS Wiki as I would have expected your recovery to either be the lineage-17.1-20201230-recovery-flox.img recovery or TWRP as above and not still the old Nexus 7 recovery which it the Android Robot. I know if flashing goes wrong you sometimes get to the Android Robot but it has no recovery options at all. Can you screen shot your bootloader, fastboot screen. Power off - Volume Up and power hold until the bootloader screen appears.

It could also be a dodgy USB cable or port which I have also experienced on one of my laptops so switch both and try again.
[Nexus 7 (2013) Android Development] ud4:
Try to use fastboot boot recoveryname.img and do what you want to do, after that flash recovery via fastboot flash recovery recoveryname.img
[Nexus 7 (2013) Android Development] P373:
Yes I tried the shown Recoveries TRWP Flox and Lineage Recovery Flox. Also different builds of them.

As shown above they will be flashed in den console, but after trying to enter recovery mode there is an issue.

My actual bootloader:

Tried to use fastboot boot Lineage Recovery Flox but bootloader is frozen.
[Nexus 7 (2013) Android Development] reddfoz:
This fastboot looks very different to mine I noticed you have Variant Tilapia which I think is a Nexus 7 2012 not 2013 this update is for Nexus 7 2013 flo to flox
[Nexus 7 (2013) Android Development] Jvino:
This does not look like a Nexus 7 - WiFi, and it appears to be cellular-capable (like debx). Can you confirm the make, model and manufacturer of this device? Flox is for WiFi only.
[Nexus 7 (2013) Android Development] moviefirst:
Correct, it's for the nexus 7 3g 2012 (Tilapia)
[Nexus 7 (2013) Android Development] Jvino:
That used a Tegra SoC, and I don't think compatible with either FLOX or DEBX. This, I think is the problem. I needs to be Nexus 7, 2013 (FLO or DEB), with the Snapdragon S4 Pro SoC.
[Nexus 7 (2013) Android Development] osm0sis:
USB was a little f*cky on TWRP 3.4.0 flo, but updating to official 3.5.0 seems to have resolved it. Presumably 3.5.0 flox will be on the way here at some point as well.
[Nexus 7 (2013) Android Development] moviefirst:
Yes indeed, it's impossible to flash a nexus 7 2013 rom on an nexus 7 3g 2012
[Nexus 7 (2013) Android Development] P373:
Thanks @All for your help.

I will try tilapia unofficial LOS ROM with my device. I hope it will be ~ stable.

https://xdaforums.com/t/rom-7-1-2-tilapia-unofficial-lineageos-14-1-2020-12-25.3978723/
[Nexus 7 (2013) Android Development] akshya11235:
@All

everything works great.

Except for trying to set up the Google Assistant "OK Google" from any screen

When I try to turn on the feature from the voice settings, I keep getting the following error:

"Trouble Connecting Check your connection and try again"

There has been a post about this in google assistant forums, but no real solution except for a ROM update

When trying to set up voice model I get a "Trouble Connecting Check your connection and try again" - Google Assistant Community
[Nexus 7 (2013) Android Development] i n f a m o u s:
Is there any plans to bring the official ROM to deb devices? I'm using unofficial ATM but would love to switch over to official.
[Nexus 7 (2013) Android Development] xbs:
Update found new build and downloaded but didn't reboot to recovery to install.

I downloaded it manually and flash it.

Where can I find the update download bluid to delete it?

Thanks
[Nexus 7 (2013) Android Development] _ck_:
there is also another TWRP 3.4.0 build here with MSI's TEN Kernel which is virtually identical to ElementalX

https://xdaforums.com/t/rom-flo-deb...8-1-2020-12-11.3569067/page-156#post-83027843

however it's just easier to clobber the old unofficial twrp with the flox twrp by just flashing from fastboot and not twrp itself

ie.

fastboot flash recovery lineage-17.1-20210104-recovery-flox.img

note that is different than just booting to the recovery image

ie.

fastboot boot lineage-17.1-20210104-recovery-flox.img

these devices are -almost- unbrickable, whew

my old eyes wishes they were 10 inches and not 7 at this point though, which is why I need the TWRP and not the lineage recovery

fastboot flash recovery twrp-3.5.0_9-0-flo.img

amazing how much life left in 2013 hardware
[Nexus 7 (2013) Android Development] ud4:
It will be fixed in the next update, you can find it after mount /data at:

/data/lineageos_updates/lineage-nameofzipfile.zip
[Nexus 7 (2013) Android Development] tdksa90:
hello and a happy new year :)

first, a big "thank you devs" for the effort to release a official lineageos rom for a 7 year old device. everything works very well with the exception of the camera.

the camera works fine until i encrypt the device. after that, the camera app disappears. when i try to open the camera from the gallery app, the camera crashes immediately.

i installed another camera app from fdroid but the app crashed when i try to open the camera.

the device is nexus 7 2013 wifi / 16 GB (no gapps). I have tried several times a clean install but the problem comes up *after encryption*.

has anyone else encountered this problem?
[Nexus 7 (2013) Android Development] Paloris:
Hi there. Came from the Pixel Experience ROM to this one, and everything's looking good so far! Thank you for your effort.

Has anyone had any issues with the Prime Video app? I get an ID error whenever I try to open it.
[Nexus 7 (2013) Android Development] Jvino:
I agree, the Devs are awesome. My N7 just keeps on going strong!

I opened and used my Amazon Prime Video app with no problem. In Canada, mind-you, The U.S. could be different. Under settings-> Accounts, do you see a "Prime Video Sync" Account? Is there an error code you could share?
[Nexus 7 (2013) Android Development] Paloris:
I opened up the app, logged in, and I was greeted by this notification. It could be roughly translated to "failure to identify you".

Makes me wonder if there's a validation process which doesn't work with Lineage OS.

PS: I'm in Argentina.
[Nexus 7 (2013) Android Development] Jvino:
If you try again, volver a intentario, will it bring you to a login page where you can enter your Amazon Credentials? Maybe try to login in first with Chrome, then the video app. This is not a LOS problem, lots of persons can use Amazon Prime Video, but might be a problem with logging into Amazon. You might ask them for help, I think.
[Nexus 7 (2013) Android Development] Aalard_:
Have same problem, but i've installed gapps. After encryption camera app disappear and i cant install or find google camera in play store. Installed open camera app, but app don't work, display message"Camera error, camera may be use by another application"
[Nexus 7 (2013) Android Development] ud4:
Can you provide me some logs in DM? Also, anyone who has this problem with encryption and camera, please do the same.
[Nexus 7 (2013) Android Development] ud4:
Yep, I'll update TWRP today. I will think about official TWRP support for flox, I think I will write to them soon

UPD: link to recovery updated
[Nexus 7 (2013) Android Development] Paloris:
If I Try again, it sends me back to the same error page. I've tried logging in from browsers, and I was able to do so. But I cannot do this from the app.

I'll have a word with their customer support. Will let you all know of any findings.

EDIT: After deleting the device from my account, I was able to log back in. Took me a day for the device to be recognized again, though. but all is well!
[Nexus 7 (2013) Android Development] ochoceros:
My camera app has also disappeared, and my N7 FLOX isn't encrypted. N7 FLOX 32Gb, Pico Gapps, Magisk. I uninstalled Magisk, but same result. I've tried with OpenCamera but it doesn't work ("camera in use - Id: 0").

The N7 is used by my son and he has a restricted user with the apps he uses. Duolingo is the only one app that has used the camera, and it was using the restricted user account .
[Nexus 7 (2013) Android Development] kartolo:
Need a little help.. My Flo was repartitioned long ago (I think, I used clamor) and currently I have LOS 17.1 Unofficial installed. I did following:

* installed modified TWRP (from Post 2) and then latest official LOS 17.1 => got Error 7

* installed LOS Recovery and then official LOS 17.1 => also Error 7

* tried to do LOS official repartition (on LOS recovery) => I got error 21 on sideloading. I ignored it and installed it. In adb shell I got " modify: inaccessible or not found"

* flashed TWRP 3.2.3_UA and then modified LOS 17.1 (without device recognition from post 9), I also got Error 7

currently with TWRP 3.2.3 UA and LOS 17.1 unofficial, I get the Flo working again. Any hint what I should try? Restocking perhaps?
[Nexus 7 (2013) Android Development] kartolo:
double post.. sorry
[Nexus 7 (2013) Android Development] k23m:
Yes...

1 RESTOCK (when "Restore original partitions?": YES)

2 CROSS +

cross-update-v2.1

and run lineage-install-2-flox.bat

When "Flash flox-TWRP?": YES

When "Repartition?": YES

Your flox will be up and running in 15 minutes.
[Nexus 7 (2013) Android Development] kartolo:
since I'm on Mac (and only have Windows as VM in VirtualBox), would it work?

after reading the .bat file, I did the steps manually on Mac and it works !!!

While restocking I got this error

Sending 'userdata' (4272 KB) OKAY [ 0.140s]
Writing 'userdata' FAILED (remote: 'Bogus size sparse and chunk header')

I need to unzip image-razor-mob30x.zip and flashing the userdata and cache manually:

fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot

Thanks
[Nexus 7 (2013) Android Development] tdksa90:
With "lineage-17.1-20210111-nightly-flox-signed.zip" the camera (with encryption) works again for me.

Thank you Devs :)
[Nexus 7 (2013) Android Development] ochoceros:
I've dirty-flashed "lineage-17.1-20210111", erasing cache & dalvik after flashing, and the camera is still missing in both users, Admin and Restricted. Open Camera keeps failing with the same message.
[Nexus 7 (2013) Android Development] morigero:
Activated "Gesture Navigation" in System > Gestures > System navigation slows down system animations and scrolling like in in browsers. Activated "3-button navigation" solves that.
[Nexus 7 (2013) Android Development] morigero:
Whats the fastes/easiest way to update when TWRP is installed instead the LOS recovery?

The LOS 17.1 updater can only download but not update with TWRP. Because of it its needed a manual boot into TWRP and do install.
[Nexus 7 (2013) Android Development] Mr.Conkel:
All update packages downloaded by the updater can be found in /data/lineageos_updates just flash the update + magisk if you plan to keep root and reboot.
[Nexus 7 (2013) Android Development] morigero:
Yes I know. I wanted to know how to do that from inside LOS (some kind of process maybe only reboot into TWRP and runs a script to make it a bit easier) without manually boot into TWRP.
[Nexus 7 (2013) Android Development] ew0k:
thank you for the build! it's been a while since I flashed anything on my device. Can anyone point me into what version of GAPPS to use? I've tried several and none work.
[Nexus 7 (2013) Android Development] ew0k:
found the Open GApps website. Thanks!
[Nexus 7 (2013) Android Development] morigero:
Use:

[IIIII] CROSS - Custom ROM Scripted Setup

Makes flashing much easier for you ;)