Related
Dear XDA Geniuses,
I have a 16gb Nexus 7 WI-Fi. I was using Nexus 7 toolkit 2.0.0 to try and flash my nexus 7 back to the the stock google rom (option 9 in the toolkit.) It seems as if it wiped out cyanogen mod 10, which i had been using, as well as clockwork recovery. My nexus 7 now boot up with the google logo and the unlocked padlock on the bootom. using the volume rocker i can select the bootloader option and get an android figure with his chest open.
this is the only option i can select. my attempts have been:
1)connect it to computer. Windows 7 and Windows 8 will not recognize it, nor let me access it from the command line.
2. Use nexus 7 toolkit, which DOES recognize it in fastboot mode, to flash a new recovery on there. it says that a command failed, and won't let it write to it.
3) install adb and android sdk tools. my tablet won't show up under devices, and I am not sure if it is still in usb debugging mode. command line will not recognize it as an adb device and will not control tablet.
when i looked at this thread it was dealing with a locked bootloader, while mine is unlocked. it also wanted command line operations from the computer, which does not seem to work for me.
i was attempting to do something like this (laptop mag blog how to hard reset a bricked nexus 7) but without my nexus 7 showing up under devices I am not sure what my options are.
TLDR: Nexus 7 16gb WIFI only boots into boot recovery. Using nexus 7 toolkit to recognize as fastboot. otherwise will not show up on computer. no recovery, no boot image.
Thank you for reading.
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
JerryMc88 said:
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
Click to expand...
Click to collapse
latest progress can be found at imgur slash TAikq
now it is say data transfer failure - too many links. 146.84 seconds.
it was my cable. the cable mounted it in fastboot mode, but would not allow writing. switched out the cable, and we are up and running again. thanks!
Um.... Glad we could help?
Sent from my Nexus 7 using xda app-developers app
Sticky?
Man, I would love to see this sticky posted, or at least a list of errors and fixes stickied. I have been looking for an answer to the same issue for two days. Finding out it was just a lousy cable really really really pissed me off... I'm glad someone figured it out and actually posted their solution, most of these wind up with nothing.
OMG, I've tried to flash my N7 with a new lollipop 5.1 today and got the same issue as described here http://forum.xda-developers.com/showthread.php?t=2724273 then, after 5 or 6 hours of thinking what is going on, I finally found this very old thread and guess what? Changing this sh***ty cable I was using solved the problem.
Use USB ports on the back of your computer, not the front.
SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.
Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!
So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.
I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance
not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?
usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:
almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.
Hi guys,
first of all my problem:
After I recovered my build.prop to the original one I'd backuped and the next reboot my nexus 10 won't start anymore.
There had to be an error when copying or something I don't know but that's not the point!
The Nexus is starting until the google logo and then there's only a lightened up black display.....
starting in fastboot is possible and also the toolkit is noticing it.
The recovery mode is not possible to open (after the lying droid with the "!" i press power+volume up but only lightened up black...)
The biggest problem I have is that the USB debugging mode is deactivated
So i couldn't find out how to flsh the factory image on the device or "reanimate" it in any way.
Every trys with the toolkit end up in questions about the debugging mode.....
So I hope there's anyone out there who can help me with my problem
Thanks, dermokles
You don't need debugging on to use fastboot. Download the factory image from Google and extract the file until you see the images.
Boot into the bootloader and connect the N10 to your PC. Then run the flash-all script. It will flash all the images in sequence. You should be good to go after that.
Sent from my Nexus 10 using xda premium
El Daddy said:
You don't need debugging on to use fastboot. Download the factory image from Google and extract the file until you see the images.
Boot into the bootloader and connect the N10 to your PC. Then run the flash-all script. It will flash all the images in sequence. You should be good to go after that.
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Don't work for me here..
The Terminal does not accept the fastboot command...
Make sure your drivers are installed correctly
Sent from my Nexus 10 using Tapatalk 4 Beta
El Daddy said:
Make sure your drivers are installed correctly
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
As far as I can say it they are installed propperly but i'm almost new to android and so perhaps you could give me a really short "tutorial"
would be really thankful for that
Got it.....
Just had to rename the fastboot-windows.exe into fastboot.exe and then run "fastboot oem unlock"
I have the afore mentioned Nexus 7. Have all the toolkits and proficient in adb. Get to the unlock prompt for the bootloader and press power over the yes option. It comes back up in bootloader locked every time.
I am in an endless loop otherwise. I can load to safe mode also.
Have the 4.23 bootloader and was trying to take the ota to 4.4.3.
Used two different aio toolboxes both with no luck. Tried to force load a stock rom. No luck. It just keeps booting back to how the tablet was before the update then reboots before you can do anything.
Sent from my SGH-M919 using Tapatalk
rigel1326 said:
I have the afore mentioned Nexus 7. Have all the toolkits and proficient in adb. Get to the unlock prompt for the bootloader and press power over the yes option. It comes back up in bootloader locked every time.
I am in an endless loop otherwise. I can load to safe mode also.
Have the 4.23 bootloader and was trying to take the ota to 4.4.3.
Used two different aio toolboxes both with no luck. Tried to force load a stock rom. No luck. It just keeps booting back to how the tablet was before the update then reboots before you can do anything.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
If you are proficient in adb like you state,then drop the toolkits.
What commands are you using? Does adb recognize your device?
Toolkits or cmd prompt the result is the same. Bootloader acts like it is going to unlock but doesn't.
Sent from my SGH-M919 using Tapatalk
dareino said:
If you are proficient in adb like you state,then drop the toolkits.
What commands are you using? Does adb recognize your device?
Click to expand...
Click to collapse
I too have this same issue.....
Once I get the unlock screen (using tool kit) and select yes.... it goes to reboot, but the tablet never comes back on...
Once I turn it back on, I never get passed the "Google" screen....
The tool kit ADB see's the tablet and runs through the "unlock" yet it never takes....
I assume that USB debugging is not turned on... but I can't get the tablet to start it up to turn it on...
Been trying SKIPSOFT ANDROID TOOLKIT.
Can anyone help?
Try the other toolkit.
Sent from my Nexus 4 using XDA Free mobile app
@rigel1326 , @Legobricke: Have you tried to unlock and flash stock images with fastboot? Just follow this guide: http://forum.xda-developers.com/showthread.php?t=1907796
Erovia said:
@rigel1326 , @Legobricke: Have you tried to unlock and flash stock images with fastboot? Just follow this guide: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Yes... I have attempted to unlock the device 3 times...
I have used 2 different tool kits and adb fast boot....
They attempt to unlock the device.... but as the unit goes to unlock, it goes to reboot and the unit doesn't come back on... If I manually turn it on, it still shows the unit as locked...
When using abd, the unit does try and unlock and then when it reboots it shows that it unlocked the device yet the device still shows locked..
I'm at a loss right now as to what I should do....
That's a problem. (Not being able to unlock with fastboot can be a sign of corrupted bootloader/partition/emmc)
Have you tried to factory reset your N7?
Erovia said:
That's a problem. (Not being able to unlock with fastboot can be a sign of corrupted bootloader/partition/emmc)
Have you tried to factory reset your N7?
Click to expand...
Click to collapse
Yes... I tried a factory reset..... but, as of now, I can't get to that option... If I try to get into recovery, it just goes to an image of the android with a red "!".......
In that case, it's most likely a hardware failure.
Legobricke said:
Yes... I tried a factory reset..... but, as of now, I can't get to that option... If I try to get into recovery, it just goes to an image of the android with a red "!".......
Click to expand...
Click to collapse
That's normal
I got the Same thing when I try to boot to stock recovery
I have a Nexus 6P running stock android, with a locked bootloader and I've only ever installed OTA updates. After installing an OTA update to NRD09U from my phone, I got the "Your Device is Corrupt. It can't be trusted and may not work properly," message. Attempting to press the power button to continue simply reboots the phone starting the process again. Obviously, because I can't even boot into android proper, I'm unable to enable developer mode or the other necessary settings in order to unlock my bootloader, so I'm stuck in a loop. I've tried sideloading a rescue OTA but I'm unable to flash an image because my phone isn't being recognized as an ADB device, even though the Android Bootloader entry shows up in my device manager as it's supposed. Even more puzzling is the fact that my phone shows up correctly as a fastboot device; typing "adb devices" returns an empty list, while typing "fastboot devices" lists the serial number of my phone as expected. I've tried a number of troubleshooting methods to fix this, including uninstalling the drivers from the device manager, and reinstalling them manually from a .zip obtained directly from google, but I still can't get my phone to be recognized as an ADB device so I'm still stuck.. I've tried contacting Google directly to get them to service my phone, but because the device is corrupted, they're telling me that my phone was rooted and that it wouldn't be covered under warranty, so they wanted to charge me almost $400 to fix it. I've read on some posts here and elsewhere that using the "fastboot format ***" works for some users with locked bootloaders, but it fails due to my bootloader being locked when I tried it myself.
So the way I see it in order to fix my phone I either need to find a method to unlock the bootloader manually using ADB/Fastboot/some other method that doesn't require OEM unlock or USB debugging, or I need to find away to get my device to be recognized as an ADB device so I can sideload the image. Anyone have any ideas how I can do this? Or some alternate solutions?
When I enter recovery mode, my system version is as follows: angler/angler/7.0/NRD09U
Thanks in advance.
Make sure you are using Android SDK tools and is up to date
Sent from my Nexus 6P using Tapatalk
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
Have you tried factory reset?
Sent from my Nexus 6P using Tapatalk
Enter stock recovery with the lying down Android. Use to side buttons to enter the menu. That's when ADB will work only.
gjkrisa said:
Make sure you are using Android SDK tools and is up to date
Click to expand...
Click to collapse
Everything should be up to date. I installed the SDK today, and I installed USB drivers from both the SDK manager and manually.
Factory reset fails, taking me back to the corrupted screen, which in turn brings me back to a bootloop.
Gazontop said:
Enter stock recovery with the lying down Android. Use to side buttons to enter the menu. That's when ADB will work only.
Click to expand...
Click to collapse
As soon as I enter recovery mode, my computer completely stops recognizing that the 6P is plugged in. It makes a sound like the device has been disconnected and there is nothing in the device manager.
If you're u don't OEM Unlocking or Bootloader unlocked then your at a lose...sell it for parts
Sent from my Pixel XL using Tapatalk
I think Google should fix this it's a defect in the memory most likely or a ****ty update
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
I think Google should fix this it's a defect in the memory most likely or a ****ty update
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is it still under warranty?
tech_head said:
Is it still under warranty?
Click to expand...
Click to collapse
It was supposed to have been, but Google basically accused me of having rooted my phone even though the bootloader is still locked, and OEM is still locked too and I've never touched any of these settings.