yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7a] mxz55:
There's no added benefit for TWRP if you're on LOS, its own recovery can do all tasks and you can do the only advanced thing you'd maybe be interest in using TWRP for, through ADB/fastboot; clearing Dalvik and deep caches, a process that will only take 40 seconds in total when done manually.

* Preferably, install an app cache cleaner app like 1Tap Cleaner, that clears all apps' caches before clearing Dalvik cache and proceeding with the following (make sure to have enabled "include system and unopenable apps")

Attach USB cable, open prompt in the folder your adb/fastboot binaries are

Commands/steps:

adb root

adb shell > su

rm -r /data/dalvik-cache

logcat -c

adb reboot bootloader // Depending on device, reboots into Fastboot-Bootloader mode

adb reboot fastmode // Depending on device, reboots into Fastboot-FastbootD mode

fastboot erase cache

The last command (fastboot erase cache) above is to be entered depending in which of the 2 modes it accepts this command, it's device dependent: either Fastboot-Bootloader mode or Fastboot-FastbootD mode.

No, TWRP isn't available for 7a, its actually generally out of support in the Android world and not actively maintained for new devices. But you won't need it. TWRP recovery also allows you to skip invalid/missing signatures on "Apply update" (adb sideload) btw, that's another misconception of why people believe they need TWRP.

Using LineageOS's own support is straightforward, if you are used to TWRP you won't have any difficulties.
[Google Pixel 7a] d0udQu0i:
hello @xinouch

TWRP for Pixel 7a is not supported, at least not on the official TWRP website at the moment (fingers crossed)...

for my part, i'm looking for a Pixel 7a compatible altenative or custom recovery that lets you make a full backup and recovery of the phone like TWRP... does anyone have any leads?

thank's

bye
[Google Pixel 7a] mxz55:
@d0udQu0i This allows to clone-backup apps with all data folders (so all apps are still logged in, have your data, configs etc): https://github.com/NeoApplications/Neo-Backup so you'd only ever have to transfer your photo's etc

I saw a similar project on XDA recently (it was started not long ago) but i forgot its name and can't find it. There is also some Android apps (requiring root) that can restore a Nandroid backup (full device recovery image) as normally TWRP recovery would have, but since i lack experience with them i won't be naming worthwhile ones.
[Google Pixel 7a] xinouch:
Thanks a lot! I feared that TWRP was becoming deprecated, I'll have to update my brain ^^

I'll give LOS recovery a try
[Google Pixel 7a] android4me:
Hi @nicknitewolf,

thanks for maintaining LineageOS for this great device. I installed it and it is working very well since a few weeks.

I have one question though: is it possible to implement/activate charging control for the user so I can select at which level (e.g. 80& or 90%) the charging process is being stopped? This would be a very useful feature and it is already active in other LineageOS21 build like Xiaomi Mi8 (dipper) for example.

Thanks!
[Google Pixel 7a] xinouch:
Installed LOS on my Pixel, it went fine. LOS recovery is a step back from TWRP, being able to reinstall a ZIP file from the phone memory without computer was a big plus IMHO.

I have a question: I guess that flashing boot, dtbo and / or vendor_kernel_boot updates the firmware. How often should I do it?
[Google Pixel 7a] AluminumAnemone:
I use the 80% script here on my P7a: https://xdaforums.com/t/mod-magisk-root-set-charging-limit-to-80-85-90-95-v2.4482011/
[Google Pixel 7a] gnarf49:
AFAIK this can't work with encrypted data partition, not even with TWRP(?)

Lineage recovery allows installing from _external_ storage. Sadly Pixel7a does not support MicroSD, but you can use an OTG USBC memory stick.
[Google Pixel 7a] xinouch:
On my previous phone (Samsung A52), TWRP was asking to unlock the phone, the same way Android unlocks it, to decrypt the partitions.

At the beginning it wasn't the case, and it took time for TWRP to support encryption.

I'd say it came with this version: https://twrp.me/site/update/2022/10/10/3.7.0-released.html

> Android 12 Encryption Support
[Google Pixel 7a] godlich:
My Pixel 7A does not connect anymore to the mobile internet network. I can call someone, but get no internet connection. I am on lineage-Lynx_userdebug 14 AP1A.240505.005 351d1751a4

I did an update to this version, but version before had some issue. Restarted several times, still persists for some days now.

I use a physical sim + esim. Bot contracts are still active.

It says status of mobile connection: Not connected

Service: in Operation

Anyone with similiar issues?
[Google Pixel 7a] V.L.:
Hi, installs and runs like a charm, thanks.

But the reserved space on the system partition is too low to install a decent version of microG including the playstore. Seems to be quite common because microG is quite large now.

Any chance to enlarged the reserved space?

See https://github.com/FriendlyNeighborhoodShane/MinMicroG/issues/19#issuecomment-918548245

On my crosshatch microG installs, I believe its made possible in https://github.com/LineageOS/android_device_google_crosshatch/blob/lineage-21/BoardConfigLineage.mk

Thanks for looking and considering.
[Android Q&A, Help & Troubleshooting] aileennathan24:
HELLO FREINDS I HAVE AN OPPO AX7 CPH1903 I TRIED DOWNLOAD THE FIRMWARE AND AND FLASH IT USING CRACKED MSM TOOL & CODE METER BUT NO INTERNET CONNECTION. I TRIED WITH UNLOCK TOOL BUT STILL GET "SAHARA FAIL" .......AT LAST I TRIED QUACOMM FLASH STILL GETTING SAME ERROR MESSAGES......NOW I WANT TO BUY MSM FLASH TOOL USER NAME AND PASSWORD, IF ANYONE WILLING TO HELP ME PLEASE
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, @aileennathan24 Welcome to XDA! I hope you'll always get the support you require.

However, prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved your thread to Android Q&A.

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 7] weinbers:
Here's an interesting one...

I found the android 14 beta just too buggy, so (per procedure) withdrew from the beta program, downloaded the latest stable 13 os via system setup, installed it and restarted when prompted. Similar to a factory reset, when the phone rebooted, the setup program ran.

But early in the process when offered to copy data from a phone (which I obviously had just blown away) I choose "don't copy", but nothing happens. Choose it again and I get an error message "settings keeps stopping" offering app info (no help there), close app, or send feedback (no way to do that at that point). Dead in the water, can't proceed..

I tried the copy data option from wife's 6a but that didn't work. Doesn't recognize the cable is connected - using the official google cable that came with the phone.

Notes:

I've got a case open with google (level 2) but so far nothing.

Adb doesn't recognize the phone so I can't sideload the rom.

Bought at Best Buy last October. I may take it back there to see if the Geek Squad can do something but I'm not optimistic.

I can get into bootloader, recovery, etc. (via buttons, not ABD). But I don't see where that helps.

Any suggestions?
[Google Pixel 7] Tulsadiver:
I'm not sure what you mean about system setup unless you mean system update but try using the firmware from here.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

You went from one version of firmware to another so ADB might have to be enabled again in developer options once you get it booted up again.

I like to put fastboot "--slot all" in front of the bootloader and radio in the flash-all.bat so they install to both slots.
[Google Pixel 7] weinbers:
System setup as in a brand new phone.

Can't use abd or alternative software - no way to load it as abd doesn't recognize the phone. Fastboot doesn't work, can't sideload, etc.
[Google Pixel 7] Tulsadiver:
Okay, I thought you said you could get into bootloader.....
[Google Pixel 7] weinbers:
I can, but since adb doesn't recognize the device, sideloading doesn't work.
[Google Pixel 7] Tulsadiver:
The files I linked are fastbooted files, not adb.
[Google Pixel 7] weinbers:
Ah, I see. So I get this right, what is the full syntax for the fastboot command I should use, please. - a lot of switches needed. I've downloaded the rom and I'm ready to flash... Using windows.

Slot a is the active slot now.

Do I need to do the radio separately?

BTW, I have a locked bootloader...

Thanks for the help!
[Google Pixel 7] Tulsadiver:
Sorry, this won't help you then. It requires that the bootloader be unlocked.
[Google Pixel 7] weinbers:
thanks anyway!
[Google Pixel 7] simplepinoi177:
Have you tried going into Recovery Mode and factory resetting/wipe data there?

You wouldn't need an unlocked bootloader...

Also, you can try to sideload OTA images (using adb) and that also can be done in a locked bootloader...

you can find it below...

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

getting the computer to "recognize" the device for adb commands usually is just a matter of installing and applying the proper usb drivers (also found below)

https://dl.google.com/android/repository/usb_driver_r13-windows.zip

*if you are running Linux or MacOS, there's different resources for that...

If you need help, getting your computer to recognize your device, you can be walked through it relatively easily -- at least I can assist if using Windows...
[Google Pixel 7] weinbers:
Reset from recovery doesn't get past the error.

Can't use adb as device isn't recognized

USB drivers are up to date

But thanks anyway 😊
[Google Pixel 7] simplepinoi177:
You haven't mentioned otherwise, so I'm just going to have to assume you are running a Windows machine...

Usually, the issue isn't that the USB drivers are up to date, but whether the Device Manager is correctly identifying the device (P7) and/or using the proper Google driver (rather than the repository Microsoft insists on using).

If you open Device Manager (when your device is connected to the computer and are in Recovery Mode [since having it connected in the initial Setup without USB Debugging probably is not going to allow it to show up in Device Manager]), is there any device that is "unknown" or has a yellow triangle, or even a mobile device but it is identified as anything other than "Android ADB Recovery Interface" (possibly under LeMobile Android Device)? If it is like that, then that identifies why your P7 is not being detected by adb; or if you

do

see it, then you know it's something other than a device driver issue....
[Google Pixel 7] bobby janow:
@weinbers How did you roll back from A14? Have you tried another computer?
[Google Pixel 7] simplepinoi177:
Yeah...I had the same wonder...I'm curious on how he did it with a locked bootloader...

As I recall, there are certain points or beta versions where that's the only time you can opt out of the "beta program"; I just figure it was that situation. A bit of research shows that it flashes/installs OTA from non-beta to rollback.

I'm pretty sure it's a driver issue (adb device not being recognized), so maybe another computer might have some luck...
[Google Pixel 7] weinbers:
yes
[Google Pixel 7] bobby janow:
How did you rollback? OTA from Beta? Did you at least flip the OEM toggle? Fastboot devices shows what? When you say in the OP "downloaded the latest stable 13 os via system setup" what exactly do you mean?
[Google Pixel 7] weinbers:
Checked/tried all that (drivers installed and fine) - nada
[Google Pixel 7] weinbers:
Yes, OTA from exiting the beta program, basically just like a factory reset from a stable operating system. Fastboot devices shows my device but can't do anything.
[Google Pixel 7] Lughnasadh:
Try using an A to C cable using a USB 2.0 port and see if your computer recognizes the device so you can sideload an OTA.
[Google Pixel 7] bobby janow:
What do you mean can't do anything? Have you looked at all these fastboot commands? https://technastic.com/fastboot-commands-list/ ? I'm assuming you never toggled the OEM switch, correct? If that was not available to you why did you install an unstable beta as per all the reports currently knowing you might not be able to recover? Nonetheless, there are a ton of fastboot commands you can use to recover your system so forget adb for now since your adb debugging is not available to allow adb commands. So what does the fastboot unlock command report back?
[Google Pixel 7] weinbers:
tried that, nope.
[Google Pixel 7] Lughnasadh:
You can opt out at any time. However, if you want to keep your data there are only certain points in time when you can opt out. This really applies to the QPR betas. When opting out and rolling back from A14 to A13 your device will be wiped as there is no way around this, but you can do it at any time.
[Google Pixel 7] weinbers:
BTW, Google tech support level 2 has a case open...

And I have an appt. today with the geek squad @best buy (where I bought it) hoping they deem it a defect and I can get another phone.
[Google Pixel 7] bobby janow:
Interesting. I think at this point he should at least find a computer that recognizes a P7 and plug into that one. Maybe BB will help him out but I don't think he's tried everything yet. He does sound extremely frustrated, however. At the end of the day I hope this thread will help someone else out who's thinking of installing an early beta without the OEM unlock available. I even flip the switch when doing a manual OTA just cause you never know.
[Google Pixel 7] bobby janow:
You're frustration is palpable but I (and most here) do think the phone is recoverable. I hope they know what they're doing and if not give you another device.
[Google Pixel 7] weinbers:
I'm familiar with fastboot and correct, I didn't unlock the bootloader - not needed to install the beta nor return from the beta (risk is normally loss of data which I knew).

FAstboot doesn't allow me to unlock at this point, says:

C:\Users\Stu\AppData\Local\Android\Sdk\platform-tools>fastboot oem unlock

FAILED (remote: 'Invalid oem command unlock')

fastboot: error: Command failed

The problem is in google's setup procedure from a factory reset/system reinstall.
[Google Pixel 7] Lughnasadh:
I've seen several other people run into this problem when opting out and downgrading from A14 to A13. There is a Reddit thread here about it and one of the suggestions was to use this method. Seems it has worked for some but not for others. May be worth a shot.
[Google Pixel 7] simplepinoi177:
You're right; I forget that it is about saving your data at certain points opting out that is beta version conditional, but can opt out at anytime -- for me, losing data was a deal breaker so that's what stuck in my head.

I think the main issue is the fact that it is a locked bootloader, so even if fastboot is detected and functional (even though adb isn't), it is really limited what can be done in any case.

I simply don't understand how fastboot (drivers and executable) functions but not adb! they run pretty much parallel with each other....

I apologize in advanced if I further bother you, but I just want to make sure (as you have not explicitly stated) that it actually shows up in your Device Manager as "Android ADB Recovery Interface" (when in Recovery Mode [where you would flash the OTA image]). Many times it's not enough that "drivers [are] installed", many times (at least Windows users) have to re-classify/re-identify a device from a random "Unknown" or "MTP device" to the proper "Android ADB Recovery Interface" or other Google ADB driver.

But, as I stated before, if it in fact does correctly identify & show up as that, then it is not a driver issue and is something else.

@weinbers OP, I believe it's just as everyone else on the thread has stated that your device does seem to be recoverable, if you are willing to stick through it until all troubleshooting steps are made to resolve the issue. But it is unfortunate that Google has decided that only OTAs can be flashed with a locked bootloader, but not Full Factory images -- if you were able to do that, I doubt you'd be having these issues (apparently, other OEM devices allow factory images to be flashed on a locked bootloader).
[Google Pixel 7] Lughnasadh:
What version of Platform Tools are you using? Should be 33.0.3. Also, are you opening up your command prompt from the Platform Tools folder when running the command adb devices in recovery mode?
[Google Pixel 7] weinbers:
Thanks, but neither worked for me.
[Google Pixel 7] weinbers:
Update...

Best Buy was no help, saying it was Google's issue although they confirmed there was a problem (duh!).

There are people suggesting things and asking questions so:

On platform tools 33.0.3 (tried 34.0.1 also).

Using a usb A to C cable in usb 2.0 (and tried a usb c to c also)

Neither of the hacks mentioned above work

In Windows device manager, there are no unrecognized devices, but there is "LeMobile Android Device" heading with "Android Bootloader device", the properties showing the device is working properly (when the phone is in fastboot and bootloader modes but not in recovery mode.

yes, I am opening up your command prompt (as admin) from the Platform Tools folder when running the command adb devices while in recovery mode - phone not found/recognized.

Anything I try to flash via fastboot tells me it fails - "not allowed when locked"

I appreciate the help and will try other suggestions - until google tells me to return the phone. In all the years of rooting, flashing and modding phones and tablets, I've always been able to recover from crashes/issues.
[Google Pixel 7] Lughnasadh:
Just to be clear, I know you said your drivers are up-to-date, but did you actually try (or already did) installing this?
[Google Pixel 7] weinbers:
yes, I installed those from that site - just to be sure...
[Google Pixel 7] bobby janow:
Can you do a quick video of exactly what's happening on startup? Do you know anyone that has a Pixel that has it working with adb on your computer? Doesn't your wife have a Pixel? Can she do an adb devices and have it show up?

As much as I hate to tell you to throw in the towel, they are offering about $300 for a P7 to trade for a 7a. Might be an option.
[Google Pixel 7] weinbers:
I know abd worked on my P7 before and it works fine on my wife's 6a, once I toggled usb debugging, which I can't do on my 7.

I can't get a video small enough so here is a Pic of the error. It occurs while selecting "don't copy files" after choosing a network, which is the first action taken after start. BTW, I tried using my wife's phone to copy files but that failed too (didn't recognize the cable - and I tried several).

And I did see that sale on the 7a. It appears that as long as my phone screen turns, I can trade it in.
[Google Pixel 7] bobby janow:
What about now? Your wife's P6a?
[Google Pixel 7] weinbers:
It does work
[Google Pixel 7] simplepinoi177:
If you are in Recovery Mode and "LeMobile Android Device" is not heading with "Android Recovery ADB Interface", that's a problem and most likely the reason why adb states "device not recognized".

As I've mentioned before...

If this is the case, we need to

First, make sure you download the Google Windows USB drivers .zip file (link to download it found in multiple posts above) and extract it to a folder (so you can point the driver to the right folder that holds the .inf file).

Then, find any "unknown" device, device with a yellow triangle on it, or a device that looks like it should be a "mobile device" or "android device", and right click on it and click on "update driver". You will then need to browse and point it to that folder that you just extracted that has the Google Windows USB drivers. Hopefully, doing this will correctly get your computer to connect to your device well enough that adb can recognize it and you can run adb command in Recovery.

If not, there are deeper methods to update the driver pointing to the specific .inf file to choose the right device/model the system is to use the driver of.

Spoiler content hidden.

Finally, in one instance, "uninstall device" (while also deleting driver software) and removing the associated .dll files (to be reinstalled) was necessary for one member to get it all to work.

Spoiler content hidden.

Hopefully, if any of these works, you can apply the OTA via ADB, factory reset it -- so it applies what the OTA can/will correct -- and you will finally get passed any issues and/or it re-establish the system proper....

I hope you seriously consider these suggestions and follow through trying them and it ends up working. Good luck to you!
[Google Pixel 7] 41rw4lk:
Have you tried just skipping past setup completely? If you can, skip it all and get to the playstore and do an app update and restart. Should prompt you to complete setup after the restart.
[Google Pixel 7] weinbers:
I didn't see how that is possible, or else I would. It's there a way?
[Google Pixel 7] 41rw4lk:
Not sure, used to be something you could do, skip through most things. I was just throwing out an idea. Maybe pull your sim and not connect to wifi and try doing an offline setup to get past the troubled area. Then hit the playstore to update the apps. I'm hoping that an update to google services and app will fix the issue and allow you to resume setup afterwards.
[Google Pixel 7] weinbers:
i have followed these instructions exactly.

When in recovery mode on my phone, (or other modes too) in Device manager I get "Unknown USB Device (Device Descriptor Request Failed) - has a yellow triangle as expected in the section Universal Serial Bus controllers.

I uninstalled the device, and reinstalled the drivers pointing to the folder with the new extracted files. It failed saying I already had the best drivers installed. I then manually replaced the dlls in system32, confirmed by the dates that they were there and rebooted...

In device manager, I get exactly the same thing as before. And no adb recognition.

Other thoughts? And thanks for the help.

update:

I re-downloaded everything, uninstalled the drivers and started from scratch. All the same, except when I go to install the new drivers, it says I don't have the compatible files - make sure they are compatible with 64 bit systems (which I have).

update 2:

moved around cables, switched ports. no change in recovery mode. but in fastboot mode, entry changes to android device/android bootloader interface. Feels like I'm getting closer... Tried to update via fastboot but failed due to device being locked and I'm not allowed to unlock it (fails).
[Google Pixel 7] manjaroid:
Try this with the phone connected and USB debugging enabled:

1) Remove Pixel drivers in Windows Device Manager and don't let them reinstall automatically.

2) Put the phone in fastboot mode, locate the unknown device in Device Manger, then remove it and reinstall by pointing to your USB driver directory.

3) Restart Android normally and check Device Manger for the proper adb driver. If it's working running adb devices should request permission from the phone along with terminal output.

That command failed because it's legacy. For when you do decide to unlock the bootloader use fastboot flashing unlock for this phone. Once unlocked it would be interesting to know if you're able to get back to Android 13 with flash-all.bat.
[Google Pixel 7] weinbers:
Can't toggle usb debugging as device fails to run through os setup for me to get there.
[Google Pixel 7] manjaroid:
Yeah, sorry. I jumped around this thread and now see where you mentioned that before. So OEM unlock isn't an option either and your predicament is more complicated than I thought. Double sorry.
[Google Pixel 7] weinbers:
That command didn't work either.