Database Users

[Q] N7, 4.3 "signature verification fail" (previously rooted device.

Hello, my name is noob. I have an addiction...
...to my Nexus 7! Unfortunately, I have not been able to update to 4.3!
My device was previously rooted (it no longer is) and I have tried everything I know and more. When it was rooted, I did not install a custom ROM or anything. I essentially just used root capabilities to get some apps and mess around with some apps a little.
When I try to update to 4.3 automatically as Google has me do it, I get the "signature verification failure".
I also tried to update it manually by downloading the update from androidpolice.
Then, I disabled system verification and tried to install the update and got a different error:
"Warning: No file_contextsVerifying current system... assert failed: apply_patch_check("/system/lib/libSR_AudioIn.so", "9c386ff759d8553e312e5ffc5773449ae6634748", "bcc09f67f497c6a6edece202942bc4c45f712f62"
E: Error in /sdcard/0/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip
(Status 7)
Installation aborted.
What can/should i do?
Any help is greatly appreciated! Also, given my noob status, the simpler you can put things, the better. I am good at following step by step instructions, but give me some acronyms and use fancy language and I might fail.
Thank you!
Edit 1: I forgot to mention that I also did a factory reset and tried to update to 4.3, but that didn't help either.

I am also having the same problem. an error like this. any ideas why and how to fix it? and after it aborted when my n7 booted up and i check for updates it says ur n7 is up to date, but then the version is stil 4.2.2 not 4.3. so any solution guys? is it because i'm using custom kernel? i'm using franco kernel rite now.

There are many threads dealing with these problems ... Please use the search function before starting a new thread.
To answer your question: you have a non stock system so the OTA update is failing. You need either return to stock or do the update manually. Btw. in my blog there is an article how to do so.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
There are many threads dealing with these problems ... Please use the search function before starting a new thread.
To answer your question: you have a non stock system so the OTA update is failing. You need either return to stock or do the update manually. Btw. in my blog there is an article how to do so.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well, I did search the forums and didn't find anything that helped. And, like I said, I tried doing it manually and it didn't work.
Tomorrow I will check out your blog though and see if the instructions are any different than what I found elsewhere. Maybe i did a step wrong or something?

Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!

ItsDare said:
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!
Click to expand...
Click to collapse
Hi! I am having the same problem and getting Status 7 error in CWM Touch.
Can you please let me know as well which method did you use? Thanks

ItsDare said:
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!
Click to expand...
Click to collapse
Could you provide the detailed step-by-step instruction? I'm on the same (noob) level as you were just before you started this thread.

pawelzielak said:
Could you provide the detailed step-by-step instruction? I'm on the same (noob) level as you were just before you started this thread.
Click to expand...
Click to collapse
http://anddisa.blogspot.de/
You can use the instructions here (although he left a bit out)
1. install http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/
2. install https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
3. install http://www.7-zip.org/download.html
4. download https://developers.google.com/android/nexus/images#nakasijwr66v
5. open the folder fastboot/adb installed to
6. open the image (#4) with 7zip (#3)
7. extract bootloader.img, boot.img and system.img into fastboot folder(#5)
8. run fasboot (should be in start menu), brings up command prompt)
9. type at command prompt "fastboot flash bootloader bootloader-*********.img" *** = use the file name that you extracted (#7)
10. type at command prompt "fastboot reboot-bootloader"
11. type at command prompt "fastboot flash boot boot.img"
12. type at command prompt "fastboot flash system system.img"
13. type at command prompt "fastboot reboot"
14. enjoy 4.3

gallahad2000 said:
You can use the instructions here (although he left a bit out)
1. install
....
14. enjoy 4.3
Click to expand...
Click to collapse
Oh, so you did it via PC.
I still would like to try with OTA. My problem is checksum on build.prop. I modified it and now I reverted changes but there still may be some white character difference. Could anyone attach build.prop file (along with its checksum) of stock n73g a4.2.2? I'll give it one more try.
With N73G

What I found most helpful in fixing my issue was this thread!
http://forum.xda-developers.com/showthread.php?t=1907796
It is a guide to flashing the factory image to return it to stock, but can be used to update to 4.3 as well!
What I did to fix my specific problem was:
Download the 4.3 update files from androidpolice.
Extracted these three files from it as suggested on AndDiSa's blog:
bootloader-grouper-4.23.img
boot.img
system.img
Plugged my N7 into my computer and since my device doesn't show up in my computer in MTP mode, but does in PTP, I switched to PTP and typed the following code into a command window:
> adb reboot-bootloader
I personally found it necessary to erase boot, cache, recovery, system and userdata to get my update to work. However, if it works without erasing those, that is definitely preferable, and you can skip these commands:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
Then type these commands:
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot flash boot boot.img
> fastboot flash system system.img
Then I rebooted my N7 and Voila, I was using 4.3!

Verification fail on 4.3 update
I am using the galaxy nexus, i had rooted it and was using another custom ROM - ParanoidAndroid 3.60. I currently have the 4.2.2 and i'm trying to update it through my system update but it loads and then gives the error message "verification failed"
I've tried it using the OTA RootKeeper procedure too but the same error turns up. Please help!

[Q] Help: No OS installed message after lastest OTA update

Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?

Double_U said:
Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?
Click to expand...
Click to collapse
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.

blankit said:
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.
Click to expand...
Click to collapse
Wow, followed your advice and am now running CM 10.1.3.. Will see whether I keep it or try to return to stock but I'm so relieved that at least my phone is working again. Thanks ever so much!!

Your welcome.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Please help soft-bricked

Hello Everyone. I need some help with restoring my shield because I seem to have soft-bricked it. Last week I rooted and installed a custom recovery file and all was well but this past weekend I was messing around with it trying to install the custom rom for full android and I think I accidentally deleted the boot file and the recovery file because all I get is the android on his back with the red triangle. Also, when I try to connect to the unit using fastboot nothing is found but I DO get a hit if I put the unit in stock recovery, it gives me the option to click apply update from adb.
From what I have been reading it sounds like I should be able to sideload the recovery and/or the stock firmware. Can anyone confirm or provide me with instructions on how to get this unit back up and running.
Any help is greatly appreciated

Wow I expected people to jump on this one. I guess I'll just keep messing around with it

Hy, here is the firmware and the instructions:
FW:
https://developer.nvidia.com/gameworksdownload (here you will have to scroll down to your console version PRO/non-PRO
Instructions:
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt

Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.

So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?

hpric said:
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
Click to expand...
Click to collapse
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?

gffmac said:
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
Click to expand...
Click to collapse
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.

Beefheart said:
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
Click to expand...
Click to collapse
Correct. I can only use sideload at this time. Yesterday I was messing around with it a little more trying to sideload the recovery but I kept getting a message saying "The footer was incorrect" and it would cancel the install. I tried different files to make sure I wasn't dealing with a corrupted zip file but they all gave the same message.
I'm trying to figure out how to sideload the recovery

Beefheart said:
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Click to expand...
Click to collapse
Correct

Hello, I am facing the exact issue. Please let me know if you figured a way to debrick?
All I can do is ADB sideload and E:footer error keeps coming up.
Help is appricated,
Thanks

Max Pro M1 Stuck at Zenfone Logo During Boot - Can still access Fastboot and Recovery

Need help - there was a Google Chrome issue earlier that made it crash or not work on ASUS devices apparently (you can google "Zenfone Max Pro M1 Chrome" for the issue)
I followed the steps outlined by the Google representative to do:
Open your device's Settings app. Tap Apps & notifications.
Tap Chrome. If you don't see it, first tap See all apps or App info.
In the overflow menu, tap Uninstall updates.
Open the Play store and update Chrome.
However, my Phone froze a few minutes after step 3 Uninstall updates, and so I had to hard shutdown. However after booting again, it is now merely stuck in the Zenfone logo, and does not go past it at all. It isn't stuck in the ASUS logo beforehand but it's definitely bootlooping (Just stays in the animated Zenfone logo nonstop).
To give more info, my phone is not rooted nor does it have custom rom/recovery. However it is able to load fastboot and the stock ASUS recovery mode (Power + Volume Up and Power + Volume Down respectively). Any advice on how I can fix this without wiping data/factory reset (or if I have to, how can I backup my data beforehand)

ArkFord said:
Need help - there was a Google Chrome issue earlier that made it crash or not work on ASUS devices apparently (you can google "Zenfone Max Pro M1 Chrome" for the issue)
I followed the steps outlined by the Google representative to do:
Open your device's Settings app. Tap Apps & notifications.
Tap Chrome. If you don't see it, first tap See all apps or App info.
In the overflow menu, tap Uninstall updates.
Open the Play store and update Chrome.
However, my Phone froze a few minutes after step 3 Uninstall updates, and so I had to hard shutdown. However after booting again, it is now merely stuck in the Zenfone logo, and does not go past it at all. It isn't stuck in the ASUS logo beforehand but it's definitely bootlooping (Just stays in the animated Zenfone logo nonstop).
To give more info, my phone is not rooted nor does it have custom rom/recovery. However it is able to load fastboot and the stock ASUS recovery mode (Power + Volume Up and Power + Volume Down respectively). Any advice on how I can fix this without wiping data/factory reset (or if I have to, how can I backup my data beforehand)
Click to expand...
Click to collapse
Go to recovery mode, select sideload option, on computer, install adb, open cmd and type "adb sideload "C:\Path\to\zipfile". The zip file must be version you running. After done, reboot phone.
Sent from my ZenFone Max Pro M1 using Tapatalk

RedGreenBlue123 said:
Go to recovery mode, select sideload option, on computer, install adb, open cmd and type "adb sideload "C:\Path\to\zipfile". The zip file must be version you running. After done, reboot phone.
Sent from my ZenFone Max Pro M1 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, will give it a try when I can.

RedGreenBlue123 said:
Go to recovery mode, select sideload option, on computer, install adb, open cmd and type "adb sideload "C:\Path\to\zipfile". The zip file must be version you running. After done, reboot phone.
Click to expand...
Click to collapse
I have the same problem. Tried uninstalling chrome and this problem happened. I am unable to follow the solution suggested above. Would someone be kind enough to direct me to detailed guide/instructions. Would i be able to recover my data?
Thanks

rahi20 said:
I have the same problem. Tried uninstalling chrome and this problem happened. I am unable to follow the solution suggested above. Would someone be kind enough to direct me to detailed guide/instructions. Would i be able to recover my data?
Thanks
Click to expand...
Click to collapse
What is the problem that makes you unable to do that?
Sent from my ZenFone Max Pro M1 using Tapatalk

RedGreenBlue123 said:
What is the problem that makes you unable to do that?
Click to expand...
Click to collapse
Sorry, i didn't mean to offend. I am have to admit that i need a kind of hand holding with detailed instructions at every step.
As per solution provided above, i am able to go to recovery mode and after that i don't know what to do and how to do. For example.. From where i can install adb and where do i find the zip file and how do i find out which version i need. Do i need to connect my phone to computer all the time? Do i run adb sideload command on my computer?
Sorry for being noob but i am technological handicapped. Mobile repair centres are suggesting to factory reset but that would result in data loss. Would you be kind enough to help me.
Regards
---------- Post added at 10:15 AM ---------- Previous post was at 09:51 AM ----------
I have gone through one post regarding ADB and its installation. I have done the installation.

1. Just Download Stock rom from asus site ( your current version )
2. copy to external memory card
3. Go to recovery mode
4. click update via external storage
5. slect your zip
6. flash
Personally Tested Method ?

midhun.akd said:
1. Just Download Stock rom from asus site ( your current version )
2. copy to external memory card
3. Go to recovery mode
4. click update via external storage
5. slect your zip
6. flash
Personally Tested Method
Click to expand...
Click to collapse
I got the version number from my recovery screen. I am downloading it right now. I hope the above method doesn't wipe my data. OR does it???
Regards

In my case there was no problem bro, But i dont know, Hope well in your case, Please ask senior members more.
---------- Post added at 06:19 PM ---------- Previous post was at 06:11 PM ----------
please search more about This in xda.
in my case i cant get any working Method without unlocking bootloader ( that means data wipe ) so i took the risk and finally succeed without data wipe. currently my device is BL unlocked and running a Custom Rom

After lots of reading of the different detailed posts, finally mustered all courage. Connected my phone which is in recovery mode and with 'adb devices' it returned the 'List of devices' only and not my phone details. I further, tried running command adb sideload "zip file" as suggested above but it returned the following error:
C:\Users\Ossn\Desktop\adbtools>adb sideload UL-ASUS_X00T-WW-16.2017.2004.063-user.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload ULconnection failed: no devices/emulators found
Checked my device manager and there is not yellow exclamation sign. I am running Windows 10 Enterprise edition. (I checked adb with my other working phone and it worked).
How do i solve this.. I am at my wits end now...
Regards

Asus Zenfone Max Pro M1 not booting
Hello,
I'm facing the same problem as described. Initially the Chrome crashed along with Gmail. I just deleted some Cache for chrome and few other application.s After restarting, it did not boot, just got stuck to the Asus icon with four colored balls moving vertically.
After going in recovery mode it shows an error as ''couldn't load bitmap fill_ball..error -7 Supported API: 3.
If anyone could help in this with detailed steps would be highly obliged . It has paralysed me for all ongoing activities.

rahi20 said:
After lots of reading of the different detailed posts, finally mustered all courage. Connected my phone which is in recovery mode and with 'adb devices' it returned the 'List of devices' only and not my phone details. I further, tried running command adb sideload "zip file" as suggested above but it returned the following error:
C:\Users\Ossn\Desktop\adbtools>adb sideload UL-ASUS_X00T-WW-16.2017.2004.063-user.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload ULconnection failed: no devices/emulators found
Checked my device manager and there is not yellow exclamation sign. I am running Windows 10 Enterprise edition. (I checked adb with my other working phone and it worked).
How do i solve this.. I am at my wits end now...
Regards
Click to expand...
Click to collapse
Choose sideload optiob in recovery then retry
Sent from my ZenFone Max Pro M1 using Tapatalk
---------- Post added at 17:55 ---------- Previous post was at 17:53 ----------
midhun.akd said:
1. Just Download Stock rom from asus site ( your current version )
2. copy to external memory card
3. Go to recovery mode
4. click update via external storage
5. slect your zip
6. flash
Personally Tested Method [emoji4]
Click to expand...
Click to collapse
How do you copy zip without os / twrp?
Sent from my ZenFone Max Pro M1 using Tapatalk

RedGreenBlue123 said:
Choose sideload optiob in recovery then retry
Sent from my ZenFone Max Pro M1 using Tapatalk
---------- Post added at 17:55 ---------- Previous post was at 17:53 ----------
How do you copy zip without os / twrp?
Click to expand...
Click to collapse
In my case i can enter to stock recovery, Then i flashed stock zip ( from asus site)
Zip downloaded from pc and copied to Sd card
*sorry for bad english

RedGreenBlue123 said:
Choose sideload option in recovery then retry
Click to expand...
Click to collapse
As you suggested, i tried again with the same result:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload ULconnection failed: no devices/emulators found
PS: when i connect my phone in recovery, the device manager shows LeMobile Android Device and under that shows Android ADB Recovery Interface. I hope that means all the usb drivers are okay and my computer recognize my android phone but still adb sideload command give the above error.
I am running out of patience now as i have been struggling with this for 3 days and by tomorrow morning i would be needing my phone. So I have to factory reset and lose all my data which is depressing.
Regards

rahi20 said:
As you suggested, i tried again with the same result:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload ULconnection failed: no devices/emulators found
PS: when i connect my phone in recovery, the device manager shows LeMobile Android Device and under that shows Android ADB Recovery Interface. I hope that means all the usb drivers are okay and my computer recognize my android phone but still adb sideload command give the above error.
I am running out of patience now as i have been struggling with this for 3 days and by tomorrow morning i would be needing my phone. So I have to factory reset and lose all my data which is depressing.
Regards
Click to expand...
Click to collapse
In recovery mode type "fastboot devices" and see if your phone is listed. (Also, try using CMD from platform tools instead of Minimal ADB and see if it helps)
Further, do you have access to Windows 7 ? Some people have reported errors on Windows 10 but they have been successful on Windows 7 + USB 2.0

Tianhe said:
In recovery mode type "fastboot devices" and see if your phone is listed. (Also, try using CMD from platform tools instead of Minimal ADB and see if it helps)
Click to expand...
Click to collapse
No my phone is not listed on executing 'fastboot devices' and i am trying running cmd from platform tools.
Further, do you have access to Windows 7 ? Some people have reported errors on Windows 10 but they have been successful on Windows 7 + USB 2.0
Click to expand...
Click to collapse
Is it so? Unfortunately i don't have access to Windows 7.
But thanks anyway for pitching in.
Regards

rahi20 said:
No my phone is not listed on executing 'fastboot devices' and i am trying running cmd from platform tools.
Is it so? Unfortunately i don't have access to Windows 7.
But thanks anyway for pitching in.
Regards
Click to expand...
Click to collapse
If your phone is not listed in fastboot devices (or adb devices although that works when you are booted to system) then the phone is probably not being recognized by PC.

rahi20 said:
As you suggested, i tried again with the same result:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload ULconnection failed: no devices/emulators found
PS: when i connect my phone in recovery, the device manager shows LeMobile Android Device and under that shows Android ADB Recovery Interface. I hope that means all the usb drivers are okay and my computer recognize my android phone but still adb sideload command give the above error.
I am running out of patience now as i have been struggling with this for 3 days and by tomorrow morning i would be needing my phone. So I have to factory reset and lose all my data which is depressing.
Regards
Click to expand...
Click to collapse
if you are going to factory reset, try my method

midhun.akd said:
if you are going to factory reset, try my method
Click to expand...
Click to collapse
Yes. I did try that at a last resort but after verification of zip file, it threw some error and aborted. Then i had enough and i choose factor reset. Now setting up everything.
Thanks for all the help..
PS: is there any utility to backup my data and contacts/messages from this phone.
Regards

rahi20 said:
Yes. I did try that at a last resort but after verification of zip file, it threw some error and aborted. Then i had enough and i choose factor reset. Now setting up everything.
Thanks for all the help..
PS: is there any utility to backup my data and contacts/messages from this phone.
Regards
Click to expand...
Click to collapse
Use google account to backup contacts. Use partition backup app to backup data (u cant use 056 data for 061, etc)
Sent from my ZenFone Max Pro M1 using Tapatalk

Google Pixel 3a (sargo) brick - error boot prepare

Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.

GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?

Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux

Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)

GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...

GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.

WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.

GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.

WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!

GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com

I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon

I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.

If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.