'adb devices' returns '034111..... device' so i know adb sees it correctly. and adb reboot bootloader reboots into bootloader but isnt recognized fastboot reboot bootloader is unresponsive. In device manager for fastboot device it has the yellow exclamation and I right click to instal from the nvidia family drivers extracted download and it says "windows was unable to install your fastboot- windows could not find driver software for your device".
Im kinda lost as to how to get it to work, im also on a new computer.
what am i doing wrong?
Here is a package with the tools and drivers i use. They have worked flawless for me on 2 Windows 10 PC's.
Maybe your fastboot.exe needs to be changed so try with the one in the package.
https://bit.ly/satvtools
Enviado desde mi Moto X via Tapatalk!
Latest ADB and Fastboot directly from Google: https://developer.android.com/studio/releases/platform-tools.html
SHIELD USB drivers directly from Nvidia here: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Note that Nvidia haven't updated the INF file for the 2017 SHIELD TV devices yet so if you have one of them you'll need to manually add the USB device IDs to the INF file (and install with driver signing disabled if on Windows 10).
lavero.burgos said:
Here is a package with the tools and drivers i use. They have worked flawless for me on 2 Windows 10 PC's.
Maybe your fastboot.exe needs to be changed so try with the one in the package.
https://bit.ly/satvtools
Enviado desde mi Moto X via Tapatalk!
Click to expand...
Click to collapse
i got it it going guess fastboot was messed up somewhere. its booting twrp but not flashing. were you booting twrp or flashing?
dontbeweakvato said:
i got it it going guess fastboot was messed up somewhere. its booting twrp but not flashing. were you booting twrp or flashing?
Click to expand...
Click to collapse
There are 2 commands to run twrp:
fastboot boot recovery.img
fastboot flash recovery recovery.img
You can use whichever you prefer but if you pick boot command, everytime you want to boot into twrp you'll have to use your pc/laptop to run the fastboot command.
I use boot command because i just use it to flash supersu.
https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544
Enviado desde mi Moto X via Tapatalk!
lavero.burgos said:
There are 2 commands to run twrp:
fastboot boot recovery.img
fastboot flash recovery recovery.img
You can use whichever you prefer but if you pick boot command, everytime you want to boot into twrp you'll have to use your pc/laptop to run the fastboot command.
I use boot command because i just use it to flash supersu.
https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544
Enviado desde mi Moto X via Tapatalk!
Click to expand...
Click to collapse
Yes boot temporarily boots the .IMG and flash permanently flashes to the recovery partition. I tried flashing but nothing I even pull the cable after the command. I think we can only boot TWRP because the recovery partition upon boot fixes itself because of the two partition check it runs. Maybe I'll try to run su command first
Su
#Fastboot flash recovery recovery.img
Looking for help on this
Note that Nvidia haven't updated the INF file for the 2017 SHIELD TV devices yet so if you have one of them you'll need to manually add the USB device IDs to the INF file (and install with driver signing disabled if on Windows 10).[/QUOTE]
Can you elaborate on this. I have a couple 2017's i want to root and i am not having much luck updating firmware for ADB driver. Anyone know if there is a new shield INF or how to edit and add USB Device ID's?
Related
Hi all im new to this forum. I am having a problem with my N7 im trying to unbrick it with nexus tool kit but at the flashing stage its says FAILED write failed unknown error for all partitions and when I try to flash a rom in twrp it hangs on patching system unconditionally. Has any one come across this problem before.
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
gavster26 said:
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
Click to expand...
Click to collapse
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
yaro666 said:
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
Click to expand...
Click to collapse
I can boot to bootloader and thats it that tool can't write to any partitions thats what I tried in the first place it erased the partitions but then could not write to them so im left with no system no kernel or recovery
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
yaro666 said:
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
Click to expand...
Click to collapse
Ok thanks I've got twrp to boot and I fastbooted aosp mm system and kernel but it won't boot up and twrp cant mount storage data or cache where to go from here it wont fastboot any stock img
Could someone help me unbrick a ZTE Trek 2 K88? All I've got is QHSUSB_BULK .
Or point me in the direction of a guide? Thx
footwork* said:
Could someone help me unbrick a ZTE Trek 2 K88? All I've got is QHSUSB_BULK .
Or point me in the direction of a guide? Thx
Click to expand...
Click to collapse
t restarts in QHSUSB_BULK mode or forces itself to pay for the power-on button, installs the driver with zadig, then installs the driver, now restarts the tablet connects to the PC and now comes the most uncomfortable part, reboots the PC with the tablet connected and use jasminetool.
You can only use a command in the jasmin tool if you use the command again, you must restart the tablet or computer. I leave you with the recovery of stock B15.
https://drive.google.com/file/d/1hjDm6rR3vvc2wd-AmkuecPo4gXmpPKGb/view?usp=sharing
you must extract the jasminetool tool and then execute cmd, I leave the link
https://drive.google.com/file/d/1iexvAypXJNYXyWAWLzqI95wT0LUlTAHJ/view?usp=sharing
cmd paste it in the folder extracted from the jasmine tool, now run cmd inside the folder jasminetool and then copy the file recovery.img in the folder jasminetool, with the connected tablet run the following: command jasminetool-win64 write recovery recovery.img
Ready only have low stock ROM of Android 7.1.1 https://drive.google.com/file/d/123qLAC8XwfRHMIMl2wr97y8eLHjWuPea/view?usp=sharing
http://code.nwwn.com/files/android/k88/jasminetool.zip
http://zadig.akeo.ie/
and a video tutorial in Spanish:https://www.youtube.com/watch?v=i7_osOgWd5U&t=6s
and if it does not work, try another pc
Instead of installing using Jasmine (which technically I can't access right now) could I do a ADB sideload from recovery?
juniorgerman said:
t restarts in QHSUSB_BULK mode or forces itself to pay for the power-on button, installs the driver with zadig, then installs the driver, now restarts the tablet connects to the PC and now comes the most uncomfortable part, reboots the PC with the tablet connected and use jasminetool.
You can only use a command in the jasmin tool if you use the command again, you must restart the tablet or computer. I leave you with the recovery of stock B15.
https://drive.google.com/file/d/1hjDm6rR3vvc2wd-AmkuecPo4gXmpPKGb/view?usp=sharing
you must extract the jasminetool tool and then execute cmd, I leave the link
https://drive.google.com/file/d/1iexvAypXJNYXyWAWLzqI95wT0LUlTAHJ/view?usp=sharing
cmd paste it in the folder extracted from the jasmine tool, now run cmd inside the folder jasminetool and then copy the file recovery.img in the folder jasminetool, with the connected tablet run the following: command jasminetool-win64 write recovery recovery.img
Ready only have low stock ROM of Android 7.1.1 https://drive.google.com/file/d/123qLAC8XwfRHMIMl2wr97y8eLHjWuPea/view?usp=sharing
http://code.nwwn.com/files/android/k88/jasminetool.zip
http://zadig.akeo.ie/
and a video tutorial in Spanish:https://www.youtube.com/watch?v=i7_osOgWd5U&t=6s
and if it does not work, try another pc
Click to expand...
Click to collapse
ev1lchris said:
Instead of installing using Jasmine (which technically I can't access right now) could I do a ADB sideload from recovery?
Click to expand...
Click to collapse
Yes too.link firmware https://drive.google.com/file/d/123qLAC8XwfRHMIMl2wr97y8eLHjWuPea/view?usp=drivesdk
You must extract and then do the adb sideload
Enviado desde mi K88 mediante Tapatalk
Adb
Adb does not work in qdloader
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
fastboot flash boot_a/boot_b yourTWRP.img
The above command worked for me. Use boot_a or boot_b depending on what you have. In addition use a separate type C cable to your PC instead of stock type C cable and remove all USB accessories plugged in the PC. I know its crazy but working with this phone may require you to do some unexplainable stuff.
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
droidstyle said:
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
Click to expand...
Click to collapse
I am semi new to this community, so I am unsure if it's doing this because I am rooted or not but I've got twrp permanently installed... So from my understanding Slot a can hold your os and slot b basically hold your twrp you just need to remember when you need to switch back.... How I installed was fast booted twrp to slot a, then in twrc switched to slot b to install rom, then switch back to slot a and did a reboot to recovery... Boots into twrp, I switched back to slot b to flash gapps, then restart system... Once inside os and everything is set up if you are rooting reboot to bootloader and flash the patched boot. Img with fastboot on pc... Then reboot system... Now when you want to use twrp all you have to do is reboot bootloader, fastboot to switch to slot a, and then boot recovery... Then Twrp will load then switch to slot b and you are good to go!
barteringram said:
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
Click to expand...
Click to collapse
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
A_Pac1 said:
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
Click to expand...
Click to collapse
Worth a try I guess but I am maintaining a solid connect to my PC and all other commands seem flawless. My problem has evolved now. I have installed twrp but now the touchscreen wont work.
rignfool said:
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
Click to expand...
Click to collapse
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
MackHoncho said:
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
Click to expand...
Click to collapse
It's not persistent as in it won't survive the flashing of the stock boot.img.
MackHoncho said:
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
Click to expand...
Click to collapse
I had the same issue with using an older version of Mata TWRP... You need to install TWRP-MATA_11
Solved
My Windows 10 machine isnt set to show file extensions.
was trying to fastboot twrp-11 as I named it; recovery.img
fastboot wanted recovery.img.img
please laugh hardily
aer0zer0 said:
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
Click to expand...
Click to collapse
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
vonstarr said:
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
Click to expand...
Click to collapse
So op6t is easier (I just bought one)
Fastboot boot nameoftwrp.img
It'll boot twrp without flashing it to the phone. Makes life easier. Mata doesn't have this option.
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.
Hello
Phone is in fastboot mode after updating magisk.
I can not reboot it with minimal ADB and Fastboot. It says waiting for any device. I installed usb driver manually following guidelines from https://gsmusbdriver.com/xiaomi-mi-9t and restarted computer and tried again with no success. any help would be much apreciated.
thanks in advance
zuy said:
Hello
Phone is in fastboot mode after updating magisk.
I can not reboot it with minimal ADB and Fastboot. It says waiting for any device. I installed usb driver manually following guidelines from https://gsmusbdriver.com/xiaomi-mi-9t and restarted computer and tried again with no success. any help would be much apreciated.
thanks in advance
Click to expand...
Click to collapse
Extract boot.img from the correspinding recovery/zip or fastboot/tgz firmware and flash from Fastboot to boot
zgfg said:
Extract boot.img from the correspinding recovery/zip or fastboot/tgz firmware and flash from Fastboot to boot
Click to expand...
Click to collapse
i extracted boot.img, put it in minimal ADB and Fastboot and tried to flash with fastboot flash boot boot.img but no success. IT says waiting for any device. fastboot devices doesnt show any device. the cable is fine, there s usb driver , I dont know what s wrong
zuy said:
i extracted boot.img, put it in minimal ADB and Fastboot and tried to flash with fastboot flash boot boot.img but no success. IT says waiting for any device. fastboot devices doesnt show any device. the cable is fine, there s usb driver , I dont know what s wrong
Click to expand...
Click to collapse
fastboot devices
does not respond?
Then something should be wrong with PC, cables or device hardly bricked
PS: Is it really in Fastboot mode, did you successfully unlock Fastboot preciously?
yes I did succesfully unlock Fastboot previously. Now fastboot devices not respond.
It looks like it s hardly bricked. Is there anything I can do with hard bricked phone?