yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] MrAdamH:
Really great to see official supported builds for such an old device, but are there any plans on supporting the "deb" version of the device - i'd love to sign up as a tester if needed?

EDIT: Just installed the "flox" version on my deb (I'm not using LTE anyway), and it works great so far.

EDIT2: And Netflix also works! Thank god - this is why my Nexus 7 has been in a drawer for a very long time..
[Nexus 7 (2013) Android Development] frankusb:
I've got lineage-17.1-20210104-recovery-flox.img and lineage-17.1-20210104-nightly-flox-signed.zip installed. I got a notification of an update available, it downloads but on install gives a status notification of "LineageOS 17.1 - Jan 11, 2021 Install error"

If I reboot into recovery I cannot navigate to /data/ to apply the update.

I'm sure I can apply with adb but would like to work out how to do so without adb. What should I look at?
[Nexus 7 (2013) Android Development] Jvino:
If I am not mistaken, the device needs to be rooted to be able to navigate to /data/lineageos_updates. You likely do not have root permissions.
[Nexus 7 (2013) Android Development] LV198:
You can export the Update from LOS Updater to a custom directory. Then you can Install the update via TWRP Recovery.
[Nexus 7 (2013) Android Development] Jvino:
Well... Look at that! Just long press on the update and export! Learn something new everyday...
[Nexus 7 (2013) Android Development] frankusb:
Thanks, that works around the problem. For the record, I'm using LOS Recovery.
[Nexus 7 (2013) Android Development] oTeMpLo:
could someone PLEASE check if ANT+ is working ?!
[Nexus 7 (2013) Android Development] Jvino:
USB OTG works with memory sticks. Is the issue the ANT+ dongle or apps to support ANT+ (Radio Service, USB Service and plugin)? Who manufactured the dongle and what support have you added from the playstore?
[Nexus 7 (2013) Android Development] ayenzel:
Hello. I've managed to install this Rom successfully on my DEB. I'm so impressed with this Rom. I think it's the best rom I've ever used. It's fluid and smooth. My deb feels like a new tab now. Thanks for this awesome rom.
[Nexus 7 (2013) Android Development] bambou:
Hi,

I need some help please as I just tried to update from unofficial to official following the guide but I must have done something wrong as the repartition didn't work (says unable to mount /cache partition).

I'm stuck there and I'm not able anymore to install any ROM.

Someone may give me some help ?

Edit: so I managed to get out from this situation formating data, then did the repartition through the Custom TWRP and everything looks good right now.
[Nexus 7 (2013) Android Development] MorpheusUK:
I have just dirty flashed from Pitrius' December unofficial build. Seems to have gone without a hitch. (I had previously partitioned via Clamor's script for the unofficial builds, used DiskInfo to confirm the 1.5gb System partition).

I followed the first three steps below (will decide if I need step four when I try to update for the next monthlybsecurity update as I have read the Updater doesn't install with TWRP but it didn't seem to be confirmed)

1. Flash the TWRP flox recovery

2. Flash official flox signed zip

3. Flash Open GApps

4. (Optional) Flash LOS flox recovery

SELinux is now enforcing under Trust and the Netflix and Disney+ said have updated from the play store to the current versions. I previously had to sideload both with a specific Netflix build to run on the unofficial build.

Thanks for creating an official build.

Edit:

Lost the camera app from my home screen and drawer on reboot, fixed it by going into settings->apps finding the camera app in the list and clearing the cache and storage.
[Nexus 7 (2013) Android Development] morigero:
The Auto Flash app makes flashing updates easier if TWRP is installed ;)
[Nexus 7 (2013) Android Development] AxelGom:
First of all, thanks for all the work to get working LineageOs 17.1 in nexus 7 2013.

I want to report an issue:

- Screen mirroring via slimport HDMI adapter doesn't work.

When i connect slimport to my tablet charging from adapter works properly but when i plug hdmi screen freezes and the only way to respond is restarting it vía power button.
[Nexus 7 (2013) Android Development] Jvino:
Yes. This is a known issue and extremely difficult to correct. The slimport can only function with the OEM ROM, for now. As far as I know, all attempts to get it going have failed.
[Nexus 7 (2013) Android Development] mow4cash:
Thanks for all your hard work to make an official version.
[Nexus 7 (2013) Android Development] Jvino:
@ud4 is indeed awesome for this. I use my Nexus 7 daily.
[Nexus 7 (2013) Android Development] C Karthik:
The ROM is great. Is there a way to boot this rom with bootloader locked? I ask this as I don't want my files to be accessed by flashing a recovery like TWRP. Also, is there a way to get exFAT OTG support in this rom?
[Nexus 7 (2013) Android Development] johndaog:
I am having trouble with my touchscreen especially the three bottom buttons. The home, back and apps buttons. They often glitch and are extra sensitive. I will try return to stock android to see if it is my device.
[Nexus 7 (2013) Android Development] ajthecat:
I have been running the official flox ROM for a few weeks now and updating weekly. Using this ROM has been remarkably smooth considering the age of the device. I encountered no issues during installation and I had previously repartitioned to run unofficial ROMs. I used both Lineage recovery and ROM this time. Just a couple of observations I wanted to mention.

First off, the weekly update downloads but fails to install using Lineage recovery. I just sideloaded as a workaround. Secondly, and more strangely, I get significant battery drain of 2-3% per hour with the screen off. Same result for all releases. The only way I can mitigate this is through using an app like Naptime to force the OS to doze. When that is active, the screen off drain reduces to 0.7% per hour. has anyone else experienced this behaviour and if so are they aware of any solutions? Thanks.
[Nexus 7 (2013) Android Development] morigero:
I had this battery drain in my last LOS with Android 7.1. Now with this its gone. After 7h I have 97% after wake up in the morning. So I expect, that have something todo with flashing. Maybe something isn't done well.
[Nexus 7 (2013) Android Development] Spanking Time:
Except no HD streaming :( but that's Netflix's fault, not the devs. I tried it and I definitely see 480p at best.

Google Nexus 7 may no longer be able to watch Netflix in HD

The original Nexus series is now further in the grave with the second-generation Nexus 7 tablet appearing to lose support for HD videos on Netflix.

9to5google.com
[Nexus 7 (2013) Android Development] ajthecat:
Yes I understand what you're saying. I did however do a clean installation of everything. I formatted everything, wiped data etc. to make it as clean as possible. Maybe just bad luck on my part. I was running Android 9 before without the screen off drain and the same apps installed. I actually have fewer apps installed now and my battery health seems okay for a device of its age.

I've been using GSAM Battery Monitor with enhanced stats enabled, but nothing jumps out. Just seems like something is preventing deep sleep or doze. Maybe I'll try resetting the battery using ADB.
[Nexus 7 (2013) Android Development] C Karthik:
I am not well versed with encryption. So I wanted to know how exactly does encryption protect my data? I know that custom recoveries cannot access the data partition if it is encrypted. But what if someone flashes a custom ROM using adb or usb-otg? Any newly flashed ROM won't be having a lock screen. So won't it be possible to access my data?
[Nexus 7 (2013) Android Development] LV198:
No, the only thing the newly installed ROM sees is data-rubbish.
[Nexus 7 (2013) Android Development] bertans:
Hi, I am a very happy owner of a Flo(x) device... brought back to life thanks to the Lineage official builds! Thank you for your efforts.

I would like to confirm the automatic update problem by referring to these previous posts:

I never installed the modded TWRP (second post of this tread) but

I always updated Lineage Recovery at every build

and even with the last build of Jan. 25th, "update found new build and downloaded but didn't reboot to recovery to install".

In the previous builds I also experienced a problem with Trebuchet in landscape mode:

But

it has been fixed with the last build

!

Lineage mantainers, you're the best! Thank you again

A
[Nexus 7 (2013) Android Development] ud4:
Thanks! I'll take a look at it (updates)
[Nexus 7 (2013) Android Development] Eguy:
Is there a plan to make a deb version (debx?)? This is working great on my Flo.
[Nexus 7 (2013) Android Development] makjim:
Look forward for the debx too.
[Nexus 7 (2013) Android Development] Morgs___:
Hello all,

Love the ROM and works almost perfectly, having the same issue as johndaog above, top and bottom edges of the screen are incredibly unstable.

Attached a vid with pointer location enabled to help show it off. Would there be an easy way of determining whether this is a software or hardware issue?

Thanks in advance
[Nexus 7 (2013) Android Development] user602:
I just enabled pointer location to test this. I cannot replicate the issue; the entire screen responds as expected.

For reference, I'll note that I was previously using unofficial 17.1 (also without any touchscreen issues), and performed a full wipe before switching to official. I am currently running the latest build.

Good luck.
[Moto E5 Questions & Answers] dogplant:
please help i used the file from lenovos own website and did it myself and now theres no network
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Tufanianda0000055:
I need a custom rom for redmi k20 pro with 80hz screen refresh rate...please anyone suggest me..
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] sfairmm:
You can use any rom. Screen OC is set by kernel.

Candy, Yuki, Marisa and others.

Becarefulle, screen OC dont is recommended.
[Moto G Power Questions & Answers] skddin:
Hello all,

After a lot of searches and trying multiple combinations of steps I was unable to decrypt my G8 Power. Has anyone tried and successfully decrypted their Moto G/G8 power. If Yes I would kindly need their advice. Thanx in advance.
[Moto G Power Questions & Answers] skddin:
How do you guys switch ROMs? I was unable to do so because my memory is encrypted and restoring a twrp backup doesn't seem to work (TWRP Asks password and doesn't accept the right one) and I have to do a format data to start using the backup Rom which is kind of useless. It used to work before(with Sammy S6 Edge) I tried using Disable_Dm-Verity_ForceEncrypt_01.19.2020. But doesn't seem to work. Suggestions Appreciated.
[Moto G Power Questions & Answers] Quantumstate:
Forget twrp. Reinstall stock and then Havoc.
[Moto G Power Questions & Answers] Jcth1:
I used vbmeta.img in fastbootd
[Moto G Power Questions & Answers] skddin:
I Too tried using an empty vbmeta as well as vbmeta from Havoc. But drive is still encrypted. Need to format to boot.
[Moto G Power Questions & Answers] skddin:
How do you move apps, data sms, logs etc across ROMs?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] umetnic:
Hi!

I am eager to find .cab file for Crystal Blue White KB Skin, like the one in c_shekhar's latest ROMs. I tryed forum search, but no luck.... ://

Please Anyone?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] bajok!:
...you can try here:

www.buzzdev.net
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] umetnic:
Found at download section.. 10x! ;D
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] bgank:
i can't crystal blue white keyboard skin....i need the user id and password too..because i can't login after register.....
[ZTE Axon 10 Pro Questions & Answers] ccraze:
After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.

Did anyone else faced similar issues on A2020U pro?

Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.

I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.

For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
[ZTE Axon 10 Pro Questions & Answers] bobthenormal:
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.

Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.

Here's the tools: https://xdaforums.com/t/axon-10-pro-non-5g-expanded-edl-tools-new-fixes-general-tips.4174667/

And here's the Android 9 firmware: https://xdaforums.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/

Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
[ZTE Axon 10 Pro Questions & Answers] ccraze:
I tried clearing the dalvik cache after resetting all apps settings. That also didn't work.

Thanks for the links. I will give it a try to downgrade to previous release and will post how it goes.
[ZTE Axon 10 Pro Questions & Answers] ccraze:
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.

Now, I am having issues with sensors.

Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.

If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
[ZTE Axon 10 Pro Questions & Answers] bobthenormal:
I think you're past what I know... I can only guess. Do you have a backup of your phone before installing any ROMs/firmware changes?

The other thing I would try is flashing the stock bootloader (you'll get that annoying warning on boot is the only downside). A pretty desperate leap of an idea, but I did have a problem that was only resolved by doing this. Sorry I can't be of more help!
[ZTE Axon 10 Pro Questions & Answers] ccraze:
Thanks for getting back. I am able to recover. After updating to v1.11 and v1.13 via OTA, sensors started working. But after sometime GPS again started giving issue. So I had to reflash again. Strange thing noticed that when I flash first to Partition B and then A, I see the issue of sensors not working. If I flash B later then it is working. I had to disable auto update otherwise it was updating automatically via OTA to A10. Because of that I re-flashed almost 3-4 times.

To disable auto update I had to stop all networks otherwise it downloads OTA and does not show settings menu. Sometimes it went into boot loop, but setting the correct bootable partition using your tool helped. Finally I am on A9 v1.10 and managed to disable auto update and everything is working fine. GPS is locking in 3-5 secs and no issues with notifications getting stuck when on Wifi. I have kept a backup_all after things are setup, in case required in future.

Your tool is amazing, thank you for sharing and providing detailed steps.(y)
[ZTE Axon 10 Pro Questions & Answers] karlovac:
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.

Just to be clear, what you did was this:

1. Run Load Programmer.ps1 - phone should now be connected

2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS

3. Ran Write Firmware v1.1.0 to B.ps1

4. Ran Set Bootable Partition0 Slot B.ps1

Is that right?
[ZTE Axon 10 Pro Questions & Answers] ccraze:
@karlovac The sequence you mentioned is correct. But later I noticed that there is no set sequence which can cause this issue and no specific sequence which can fix it. After my previous post, I tried installing OTA and sensors worked. Then I reflashed it and it worked again. Later by mistake I took the OTA again and saw GPS issues. So reflashed, and then ran into sensor issue again. Again reflashing worked and AFAIK it was not in the sequence mentioned above in your post.

I would say just a matter of luck, I couldn't find exact sequence which can cause this issue. Just try flashing again, most probably you will not see sensor issues. If you still see sensor issues then try installing all OTA till your system is back to A10, meanwhile checking if the sensors are back after every OTA. If you see sensors working, then no need to install all OTAs and reflash with this image to go back to A9 and disable auto updates. Good Luck!
[ZTE Axon 10 Pro Questions & Answers] karlovac:
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11

The way I'm testing the sensors is:

1. Open dialer

2. Enter *983*673636# -> this enables EMODE

3. Enter *983*0# -> this opens the testing app

4. Go to sensor test

They all say CTS Fail. (I got that from this thread BTW).

Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
[ZTE Axon 10 Pro Questions & Answers] karlovac:
@ccraze success! I did the following:

1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.

2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13

After that, my sensors worked again. Thanks for the tips.
[ZTE Axon 10 Pro Questions & Answers] ccraze:
Even that is not consistent. Once, I have seen it worked fine till I got all A9 updates. But in one run GPS went bad in first OTA itself. Definitely A10 is bad, but there something else wrong with the A9 OTAs also which mess up the drivers. I would recommend to not take any OTA after flashing with this image.
[ZTE Axon 10 Pro Questions & Answers] ccraze:
Great! just make sure that OTA is not messing up GPS again. otherwise you might need to reflash and disable auto updates immediately after booting.
[ZTE Axon 10 Pro Questions & Answers] karlovac:
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.

I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.

Is there a different place you disabled OTA updates?
[ZTE Axon 10 Pro Questions & Answers] ccraze:
After you flash the OS, immediately turn off all data (Mobile + Wifi). Then go to Settings->System->System Update->Click 3dots on the top right -> Settings -> Disable all options.

Its easy to see those options if you have all data sources turned off. It will download and will show that update is ready to install but will not install automatically.
[ZTE Axon 10 Pro Questions & Answers] karlovac:
I think I did what you're describing, right after I flashed:

View attachment 5338875

However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:

View attachment 5338877

I'm afraid to reboot now since I can't afford to lose GPS reliability now.
[ZTE Axon 10 Pro Questions & Answers] ccraze:
You are not following the menu items that I mentioned before. You should see following screens. Developer options system update is different setting.

View attachment 5339067View attachment 5339065
[ZTE Axon 10 Pro Questions & Answers] karlovac:
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!

Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.

Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
[ZTE Axon 10 Pro Questions & Answers] pl1992aw:
Your phone seems to have A/B partition.

So the update is written into the inactive slot.

Check which slot it's using and which slot is inactive.

Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.

So the update will fail and the update in the inactive slot will not boot.

Then it will return back to the previous active slot with the old system.

Risk it yourself though. I never had an A/B slot, so can't make sure if it works.
[ZTE Axon 10 Pro Questions & Answers] karlovac:
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?

Also, to check which slot is inactive, according to this doc, it seems I should run:

fastboot getvar all | grep “current-slot”

Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
[ZTE Axon 10 Pro Questions & Answers] pl1992aw:
I never had ZTE phones, so can't really be sure about the flashing process.

You don't need to corrupt the whole ROM, you can rather just corrupt the boot partition of the inactive slot with update. Or even just flash a wrong version of boot partition into that inactive slot can corrupt it as well.

Either

fastboot flash boot_a wrong_boot_file.img

Or

fastboot flash boot_b wrong_boot_file.img

The corrupt can be done with root or in fastboot, EDL should be not needed.

About which slot is inactive, since your case is complicated that it's going to do an update, the fastboot command to check inactive slot is hard to distinguish.

You may need to use rather command

fastboot getvar all

It will show like this:

With this, you will be able to see the system version.

eg. ro.build.version (find the correct one yourself, I don't know this phone.)

Before power off, you first find out your current version, so then in fastboot, you check if it's the same as read from fastboot.
[ZTE Axon 10 Pro Questions & Answers] ccraze:
@karlovac If you are fine with resetting your phone and data, then easiest way would be to reflash with the same process as you did before. After first boot, immediately stop all network (LTE/5G, and Wifi) and disable auto download and updates. After that you are good to enable network and configure your phone.