Related
Hi everyone,
I am trying to update my (unrooted and unlocked) Nexus 7 2013 wi-fi to Marshmallow via OTA. I have installed adb on my system and download the update package file.
When I connect my Nexus to Windows 10, the system recognizes the device as Android ADB Composite and everything seems to be working as it should. I open a command prompt and type:
Code:
adb devices
and the device along with its id is correctly shown. At this point I reboot to bootloader, so I type
Code:
adb reboot bootloader
the Nexus reboots, enters in the bootloader and the following happens:
adb can't find the device anymore
the device manager puts the Nexus among the Other devices and so it appears no driver has been installed for it.
As suggested on numerous tutorials, I right-click on the device and choose to manually install an appropriate driver. And I expect to find Android ADB Composite in the list and instead the only possible choice is Samsung Android ADB Interface — which does not work, because, naturally, Nexus 7 is not a Samsung device.
I have tried to solve this issue by installing the google usb drivers using the 15 seconds install and it didn't help at all.
What can I do to overcome this issue?
Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk
UncleMike said:
Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?
haunted85 said:
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?
Click to expand...
Click to collapse
I'm only familiar with flashing images while at the bootloader. I've never had to side load anything, so I don't really have an answer for you.
Sent from my Moto X using Tapatalk
I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app
haunted85 said:
What can I do to overcome this issue?
Click to expand...
Click to collapse
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
jslanger said:
I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.
nhizzat said:
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.
Click to expand...
Click to collapse
If I am just accessing my Nexus 7 in Windows, yes, the tablet is normally recognized. However, once you send it into bootloader and recovery, the computer recognizes the tablet, but it knows it is not in its normal setup...I guess. It just needs some prodding to install the driver at each stage. The only reason I knew how to do this is because I followed directions on this online somewhere.
Hey guys I suggest using this tool called universal adb driver it will install all the drivers for the n7, I had problems sideloading marshmallow because of the recovery mode not being recognized by windows however this tool fixed it right up. It installs drivers for I believe the Galaxy nexus? But they work perfectly fine for the n7.
TL;DR: drivers fail in recovery mode this fixes it.
Here is the link: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Sent from my Nexus 7 2013 using Tapatalk
Long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I installed TWRP and erased all my device information without making a backup. During intallation something happened with the toolkit(I believe the program froze or I just got too impatient, so I disconnected the USB). Mind you at this point I had not installed any third party roms yet resides TWRP which I don't even know if it installed completely because after I disconnected the screen turned into bright static.
So after mindlessly disconnecting my phone the entire screen went blank or was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without an operating system because I wiped it when I had TWRP and I now see this after it loads https://goo.gl/photos/pNZz2XgpQ2oA3SMN6 I don't know what else they did over there because I no longer have TWRP. I also have a locked bootloader now. I attached some screen shots of what options I get when I turn on the phone and the other options I see. which include the bootloader and recovery screen.
https://goo.gl/photos/w7QnfuqtbNGirQuE9
https://goo.gl/photos/58XmdAiMwmdvGfr29
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. I also tried fastboot oem unlock, but it says failed. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am seeing; Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB (I am now able to do this thanks to some help in the forum)
EDIT: I fixed the driver issues, This involved manually assigning drivers TWICE through device manager. I had to assign them when I was in the bootloader and again when I went into recovery on my android device. Windows 8.1 recognized the device as 2 different devices based on what screen (bootloader vs recovery). Thus make sure to manually update your drivers twice. Once in bootloader and again in recovery. I am also using the latest android SDK platform tools.
I am now having trouble doing "adb sideload file.zip"... My device keeps rejecting googles OTA files saying signature verification failed https://goo.gl/photos/9UURn9To33YdZM7B7
I also get this error in CMD https://goo.gl/photos/dRvUS3bB5saGehX1A
EDIT: added more details
Last edit: Solved!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
So none of the OTA roms from google worked in ADB sideload etc, but for whatever reason when I sideloaded a custom ROM it installed just fine... No sig verifications errors in recovery mode... I used http://forum.xda-developers.com/nexus-5x/development/rom-pure-nexus-layers-fi-wifi-calling-t3244601 <---- After downloading this custom rom file, I moved it over to my SDK platform tools folder (you could also use the adb folder in your C drive if you went about installing those adb drivers)
Next, I started bootloader on my android device by pressing power and volume down buttons. I then navigated to recovery by using the volume keys. once in recovery, I selected apply update from ADB. I am now done with the phone.
I opened up command prompt from my PC using shift/right click from the appropriate folder (c/adb or platform tools folder). further, I opened command prompt and typed in "adb sideload pure_nexus_bullhead-6.0-20151109.zip" the flash was successful.
The first boot was not perfect. I recieved a error in regards to something about a manufacture error, but it was enough for me to get into the OS and enable OEM unlocking. I am now able to move forward and unlock the bootloader with rootkit or fastboot. After unlocking the boot loader I went back to a factory ROM which now installed with no problem.
Holly crap. Anyways huge thanks to everyone on this thread you guys are awesome I could not have done it without you.
XDA 4 life
Can you be a little more specific? what were you flashing and what steps did you follow?
Bootloader
metpage said:
Can you be a little more specific? what were you flashing and what steps did you follow?
Click to expand...
Click to collapse
ideaman924 said:
Please include:
Details of what you were doing
A screenshot (or a camera shot from another phone)
What things you flashed
What the phone was running prior to flashing
Your device model (just in case we need to recommend tot files)
If possible, a recent backup from TWRP
We cannot help without these things. Thanks!
Click to expand...
Click to collapse
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
more pics
Nebula666 said:
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
Click to expand...
Click to collapse
I do get these options by holding down the power key and volume down
Nebula666 said:
I do get these options by holding down the power key and volume down
Click to expand...
Click to collapse
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So I tried using fastboot devices and nothing comes up.. I am going to try reinstalling all the SDK/drivers on a different computer. Maybe that will help.
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Ok I think I am connected now...
Device manager is showing my device as
Android Devices
---Android Bootloader Interface
It is also now recognized in CMD.. before it would not show up.
jd1639 said:
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok I am not sure what to do now as the google directions advise me to use ADB reboot recovery and that doesnt work...
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Ok so I tried running in recovery mode... I selected apply update from from ADB.... Than I ran the following command adb sideload (ota file.zip) from CMD and I got this error
"ERROR: DEVICE '(NULL)' NOT FOUND"
jd1639 said:
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
See above, I get this message "ERROR: DEVICE '(NULL)' NOT FOUND"
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
jd1639 said:
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I get that error message from cmd after imputing adb sideload "ota file"
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
---------- Post added at 06:01 PM ---------- Previous post was at 05:43 PM ----------
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The OTA updates Google is supplying us are not simply delta updates. They are the full package. Google is doing it this way because the developer preview OTA was borking locked devices. The OP indicated that he is still locked. Oddly since he was flashing TWRP when this ****uation started. But that's the info we were given.
Sent from my SM-G930V using Tapatalk
Half way solved
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
PiousInquisitor said:
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Ok here is what is going on.... It was definitely a driver issue. I had the drivers successfully installed when I was in bootloader, but as soon as I went to recovery mode on android my computer would no longer recognize the drivers, so I had to manually reinstall them again for recovery mode. Now I have access... I did another attempt at adb sideload "ota.zip" that I downloaded from googles OTA site , but I am getting a signature error on my android and abort message on android here
Am i suppose to unzip this file or leave it zip? When I unzip all I see is a bunch of .img files not zny zips so maybe I am missing something here.
So google has two download links for the OTA, I am trying the other one now without unzipping it.
Alright so the second file I downloaded is giving me the same verification errors in recovery... I am going to try one last thing before I try blending the phone.
There is hope ahead! i think I downloaded the wrong OTA from the google website. The nexus 5x and 6p have the same descriptions. Hopefully this solves the problem. I am literally ready to throw this phone in the blender and call it a day
I will send you $50 via paypal if you can either instruct me how to fix it, or if i can mail you the phone and you return it back to me in working order.
I just got the phone. And i have spent the whole weekend reading and following what others have suggested in this forum to no avail.
I wanted to install TWRP onto it. I followed the instruction to unlock the bootloader first int the dev settings, then in the fastboot screen. When i unlocked it i got the yellow triangle, telling me to relock it, that the system cannot check for corruption, etc. It would not move past this screen. I had to reboot. It would not enter any recovery.
I tried flashing back the stock recovery from fastboot, from the stock images, i would not go past this screen. It would not boot into the system.
I then went to try to get back to stock with the instructions from this thread:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Phone will not boot, it hangs at the "google" start screen. I can not unlock bootloader from fastboot now. It gives a "DENIED" message, unable to oem unlock bootloader.
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load. Under download mode, the LG drivers will work. I can only get in download mode on a Windows machine. I can only get to fastboot on a MacOS machine through terminal.
Please help, i am going to throw this phone in the trash otherwise. I will answer any questions you may have that will help solve this.
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
since you have installed TWRP do as written HERE.
It is confirmed that is working for nexus 5x too, read the whole thread anyway!
Caligula36 said:
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load.
Click to expand...
Click to collapse
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Sent from my Nexus 9 using Tapatalk
ritchea said:
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Click to expand...
Click to collapse
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
Which stock image should i be using? The .tot file? The OTA or factory image?
Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
NO PROBLEM NOT SOLVED.
I cannot get a connection to fastboot on Windows. Only on Mac through terminal. I can only get into download mode on windows. When i try to unlock bootloader on my Mac, it give a DENIED error.
Stevica Smederevac said:
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Thank you, i will take you up on that offer.
This is the only thing that comes up when i connect via fastboot, this and a drivers not installed alert. I CAN NOT install them manually, the dialog just says the Windows could not find the drivers.
Issue resolved. Mods can remove this thread.
Caligula36 said:
Issue resolved. Mods can remove this thread.
Click to expand...
Click to collapse
Nice:good:
Sent from my Nexus 5X using XDA Labs
Great!
Sent from my Nexus 9 using Tapatalk
What did you do to fix this?
Sent from my Nexus 5X using Tapatalk
I looked everywhere and tried all i could find but my phone wont be recognized in fastboot.
Sideload works though.
Device is recognized as "bootloader device" which seems good, but the fastboot devices gives nothing...
I am on windows 10, tried different drivers, force driver, uninstall and then reinstall with driver verification disabled.
Almost gave up on rooting for this device, never had this much trouble since galaxy S1!
I checked windows updates and got nothing.
Really lost here, anybody have more suggestions?
After looking at other options it seems windows 7 install is the way to go... Really freaking annoying, will try on a vm first. Not really in the mood of doing a second OS just to root the phone lol..
Sent from my ONEPLUS A3003 using Tapatalk
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
Gugus38 said:
I looked everywhere and tried all i could find but my phone wont be recognized in fastboot.
Sideload works though.
Device is recognized as "bootloader device" which seems good, but the fastboot devices gives nothing...
I am on windows 10, tried different drivers, force driver, uninstall and then reinstall with driver verification disabled.
Almost gave up on rooting for this device, never had this much trouble since galaxy S1!
I checked windows updates and got nothing.
Really lost here, anybody have more suggestions?
Click to expand...
Click to collapse
You can try to live boot Ubuntu on your PC with a USB drive and attempt it with that. I haven't had any issues with adb or fastboot on the newest Ubuntu. It would be worth a shot before downgrading your OS or installing an alternative.
mapolidori said:
You can try to live boot Ubuntu on your PC with a USB drive and attempt it with that. I haven't had any issues with adb or fastboot on the newest Ubuntu. It would be worth a shot before downgrading your OS or installing an alternative.
Click to expand...
Click to collapse
Seems like a good idea, thanks ! Will try that
Sent from my ONEPLUS A3003 using Tapatalk
Hello,
I seemed to have ran into a problem. I went to install a custom rom; have done it many of times before on a regular Pixel. Tried on the Pixel 2 XL with my Linux PC and it worked then rebooted and now it's gone. All I can do is access my bootloader and TWRP Recovery. I've looked everywhere on every thread on how to go back to stock. 'flash-all.bat' method doesn't work. Along with the fact that my Windows PC doesn't have drivers to the Google Pixel and it comes up as a unrecognized device.
When trying to do 'flash-all.bat'
it comes up with '< waiting for any device >' and nothing happens. Theres no devices listed on adb or fastboot.
Please help..
Thank you!
ImHazyDayz said:
Hello,
I seemed to have ran into a problem. I went to install a custom rom; have done it many of times before on a regular Pixel. Tried on the Pixel 2 XL with my Linux PC and it worked then rebooted and now it's gone. All I can do is access my bootloader and TWRP Recovery. I've looked everywhere on every thread on how to go back to stock. 'flash-all.bat' method doesn't work. Along with the fact that my Windows PC doesn't have drivers to the Google Pixel and it comes up as a unrecognized device.
When trying to do 'flash-all.bat'
it comes up with '< waiting for any device >' and nothing happens. Theres no devices listed on adb or fastboot.
Please help..
Thank you!
Click to expand...
Click to collapse
Google adb driver:
https://developer.android.com/studio/run/win-usb.html
ImHazyDayz said:
Hello,
I seemed to have ran into a problem. I went to install a custom rom; have done it many of times before on a regular Pixel. Tried on the Pixel 2 XL with my Linux PC and it worked then rebooted and now it's gone. All I can do is access my bootloader and TWRP Recovery. I've looked everywhere on every thread on how to go back to stock. 'flash-all.bat' method doesn't work. Along with the fact that my Windows PC doesn't have drivers to the Google Pixel and it comes up as a unrecognized device.
When trying to do 'flash-all.bat'
it comes up with '< waiting for any device >' and nothing happens. Theres no devices listed on adb or fastboot.
Please help..
Thank you!
Click to expand...
Click to collapse
If its Linux you need to do flash-all.sh
---------- Post added at 08:27 AM ---------- Previous post was at 08:26 AM ----------
And this is the thread you want to follow
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
ImHazyDayz said:
Hello,
I seemed to have ran into a problem. I went to install a custom rom; have done it many of times before on a regular Pixel. Tried on the Pixel 2 XL with my Linux PC and it worked then rebooted and now it's gone. All I can do is access my bootloader and TWRP Recovery. I've looked everywhere on every thread on how to go back to stock. 'flash-all.bat' method doesn't work. Along with the fact that my Windows PC doesn't have drivers to the Google Pixel and it comes up as a unrecognized device.
When trying to do 'flash-all.bat'
it comes up with '< waiting for any device >' and nothing happens. Theres no devices listed on adb or fastboot.
Please help..
Thank you!
Click to expand...
Click to collapse
Flash This and make sure to thank the OP he's a lifesaver.