I just bought a used 6p it keeps saying to log in with previous gmail.how do I fix.
I do not have this info
Reset the phone so all data is wiped
Sent from my Nexus 6P using Tapatalk
I did factory reset through recovery and that did not work
pospower said:
I just bought a used 6p it keeps saying to log in with previous gmail.how do I fix.
I do not have this info
Click to expand...
Click to collapse
That's kinda like the iCloud for iPhones. You need to log in the old Gmail used on that phone to make it work.
So no way around it?
pospower said:
So no way around it?
Click to expand...
Click to collapse
I don't know if installing a custom rom will work. Don't you have anymore contact with the seller?
You can still get in it. Load up your PC and use Nexus Root Toolkit to completely restore the phone to its fresh out of box state. That should clear it up. It'll be like a brand new device that's never been used.
No root so no
Find the person who sold you the phone snd have them put in the credentials, then remove the account from the phone. If not possible then get a refund.
pospower said:
No root so no
Click to expand...
Click to collapse
You don't need root to get there. Fastboot flash the factory image per Heisenberg's pinned guide in Nexus 6p General at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and refer to section 10. The only thing you need to do is install ADB/Fastboot drivers on your machine or use on of the toolkits (though command line is actually faster and safer).
I'd suggest doing it so it's new, as in out of the box. It can't preserve any previous account data this way and then after you set up the device, you can just keep it stock or modify/customize as you want.
I mean it's kinda smart that they did this because let's say the phone is stolen. If the phone was robbed or so you just have a useless brick lol but maybe the toolkit should help.
ultyrunner said:
You don't need root to get there. Fastboot flash the factory image per Heisenberg's pinned guide in Nexus 6p General at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and refer to section 10. The only thing you need to do is install ADB/Fastboot drivers on your machine or use on of the toolkits (though command line is actually faster and safer).
I'd suggest doing it so it's new, as in out of the box. It can't preserve any previous account data this way and then after you set up the device, you can just keep it stock or modify/customize as you want.
Click to expand...
Click to collapse
Tried that. It doesn't recognize the phone when it restarted as its not in developer mode. You have to have the phone in USB debugging checked I believe is the issue. Correct me if I'm wrong please. I want this phone to work.
pospower said:
Tried that. It doesn't recognize the phone when it restarted as its not in developer mode. You have to have the phone in USB debugging checked I believe is the issue. Correct me if I'm wrong please. I want this phone to work.
Click to expand...
Click to collapse
USB debugging (it's a setting within the OS) is not required to flash files via fastboot. If you are able to boot into bootloader but your computer isn't recognizing the phone, you likely need to update the ADB/fastboot drivers.
Sent from my Nexus 6P using Tapatalk
pospower said:
Tried that. It doesn't recognize the phone when it restarted as its not in developer mode. You have to have the phone in USB debugging checked I believe is the issue. Correct me if I'm wrong please. I want this phone to work.
Click to expand...
Click to collapse
So go to settings click were it says your version of android at the bottom find build number and tap it about 10 times it will say you are now a developer back out and go into developer options find USB debugging and click it and then flash the factory IMG you can download it from the Google developer website were all the image files are stored download your required image android 7.0 for your phone (angler) I believe is the 6p there is instructions on there too it'd easy and you won't have the problem after you flash it back to factory state I think it has something to do with the data partition as the previous account will be stored in data just go and flash it and enjoy your phone
Mikeybray16 said:
So go to settings click were it says your version of android at the bottom find build number and tap it about 10 times it will say you are now a developer back out and go into developer options find USB debugging and click it and then flash the factory IMG you can download it from the Google developer website were all the image files are stored download your required image android 7.0 for your phone (angler) I believe is the 6p there is instructions on there too it'd easy and you won't have the problem after you flash it back to factory state I think it has something to do with the data partition as the previous account will be stored in data just go and flash it and enjoy your phone
Click to expand...
Click to collapse
Thank you but with the activation lock. I can't get past the sign in to the previous account on this phone screen. Let alone to the settings.
ultyrunner said:
USB debugging (it's a setting within the OS) is not required to flash files via fastboot. If you are able to boot into bootloader but your computer isn't recognizing the phone, you likely need to update the ADB/fastboot drivers.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I tried on a fresh build of windows 10 using latest drivers I thought but worth another try thanks.
Oh the boot loader is locked. Too. Hense the need for USB debugging. I believe this needs to be on to unlock the boot loader. So I go into recovery. The I use the toolbox ap or what ever its called. Wigs. When I go to unlock boot loader. Adb recognises the phone and it fastboots up the phone to on. That's where I get stuck. This is where USB debugging needs to be on to unlock the phone. Is my guess. So to be clear so nobody tells me how to go to settings and do this again. I can only get two steps past the welcome screen. Step one pick WiFi connection, then it asks for previous account info. Google really has this locked down.
pospower said:
Oh the boot loader is locked. Too. Hense the need for USB debugging. I believe this needs to be on to unlock the boot loader. So I go into recovery. The I use the toolbox ap or what ever its called. Wigs. When I go to unlock boot loader. Adb recognises the phone and it fastboots up the phone to on. That's where I get stuck. This is where USB debugging needs to be on to unlock the phone. Is my guess. So to be clear so nobody tells me how to go to settings and do this again. I can only get two steps past the welcome screen. Step one pick WiFi connection, then it asks for previous account info. Google really has this locked down.
Click to expand...
Click to collapse
Not sure if you're serious or just trolling. It was said a couple times in the thread already. ADB option once the phone is on has nothing to do with fastboot. Boot to bootloader (hold volume down while starting phone) and unlock bootloader and flash a factory image. You said you have Wugs toolkit, I'm not sure if it can be any easier. If problems persist you can sell the phone to me since it's unusable
This is FRP that cannot be bypassed as of Android N. Bootloader can't be unlocked so you can't flash anything. There's simply no way around it. Without the previous owner's Google login, you have a brick.
Nothing you can do you have to have an unlocked bootloader to flash it back to stock. The option to allow the bootloader to be unlocked is within the developer settings "OEM Unlocking". You're only option is to try and track down the owner of this Gmail account.
Related
I rooted as soon as I got my N7 because I wanted to be able to use USB OTG to watch movies during my long flights a few weeks ago. Now I'm using mskip's tool kit to get back to stock (sending it to Asus because of the screen flicker and touchscreen issues).
I tried to download, extract and flash the stock rom and then re-lock the bootloader. After doing this, it wouldn't load. I can get to the bootloader, and managed to unlock it again, but I can't get it to flash the stock rom and thus it won't boot. When I select "Start", it says "booting failed". It also won't let me flash any of the recovery images included in the utility. I'm not exactly well versed in rooting and now I'm stuck.
Please help if you can. Thank you.
If You Have SuperUser Or SuperSU I believe, you could easily unroot it from the settings. As to locking the bootloader, there is a toolkit program and the link is: http://forum.xda-developers.com/showthread.php?t=1766475 With this you could go back to stock if you wish. You could also use a SDK Command prompt thing to lock the bootloader.
EDIT: I forgot you can't boot up. But you could still use the Toolkit program.
Ryan35310 said:
If You Have SuperUser Or SuperSU I believe, you could easily unroot it from the settings. As to locking the bootloader, there is a toolkit program and the link is: http://forum.xda-developers.com/showthread.php?t=1766475 With this you could go back to stock if you wish. You could also use a SDK Command prompt thing to lock the bootloader.
EDIT: I forgot you can't boot up. But you could still use the Toolkit program.
Click to expand...
Click to collapse
I tried that toolkit several times, but it doesn't work. Everytime I try to flash stock+ unroot I get this message:
"md5sum.exe- System Error
The program can't start because libintl3.dll is missing from your computer. Try reinstalling the program to fix this problem."
No idea what that means.
Use wugfreshs toolkit much better. IMO and i don't use toolkits normally but it was a snap. Also for locking the boot loader its fastboot OEM lock.
Sent From My Toro+ via White Tapatalk
ÜBER™ said:
Use wugfreshs toolkit much better. IMO and i don't use toolkits normally but it was a snap. Also for locking the boot loader its fastboot OEM lock.
Sent From My Toro+ via White Tapatalk
Click to expand...
Click to collapse
I was able to get Wugfresh's toolkit working after re-downloading it for the 3rd time and it is able to flash the bootloader but the next lines of text say:
EOCD not found, not zip error..... and then a bunch of nonsensical symbols.
Tried again this morning... still stuck at the same point. Any ideas guys?
Did you install the drivers for it? Did you try using the PDAnet drivers? Can you post a screenshot or picture of the error? Also are you making sure the device is on with USB Debugging enabled? I never got any errors try following this Video.
He can't go to USB Debugging because he can't boot up I think.
Ryan35310 said:
He can't go to USB Debugging because he can't boot up I think.
Click to expand...
Click to collapse
That is correct. I've attached a screenshot of what I was describing earlier. It looks like what I would imagine Transformer language in written form to look like.
Great googly moogly I got it to work! I had to download the stock image directly from Google... again and select the file manually along with inputting the MD5 checksum. So if you're having issues like I was, try this!
Thank you to everyone that tried to troubleshoot my problems and a big Thank You to WugFresh for his toolkit :good:
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
CM9onmyMoPho said:
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
Click to expand...
Click to collapse
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
gee2012 said:
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
Click to expand...
Click to collapse
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
CM9onmyMoPho said:
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
Click to expand...
Click to collapse
Look in my signature line 2 and 3.
gee2012 said:
Look in my signature line 2 and 3.
Click to expand...
Click to collapse
thanks. will i lose any personal things such as photos?
CM9onmyMoPho said:
thanks. will i lose any personal things such as photos?
Click to expand...
Click to collapse
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
theblackrose666 said:
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
Click to expand...
Click to collapse
You need to be in the bootloader for fastboot to work. Reboot to bootloader and try flashing a recovery.img using this command.
fasboot flash recovery recovery.img
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
mitchdickson said:
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
Click to expand...
Click to collapse
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
estallings15 said:
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
Click to expand...
Click to collapse
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
theblackrose666 said:
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
Click to expand...
Click to collapse
adb push nameofrom.zip /sdcard/
Sent from my Nexus 4 using xda premium
ran sdk tools tried adb shell and nothing it wont read the device. we tried to push the .tar files to the phone using samsung galaxy nexus tool kit. it didnt work so hes going to take it to a repair but i think the device is toast on the account that usb debugging mode is no where in sight. if it does get fixed ill be sure to report how it got fixed. so anyone else who runs into the problem can get this fixed without a 20 dollar repair bill.
heat361 said:
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
Click to expand...
Click to collapse
will my computer even detect my phone? usb debugging is off and i can't see the phone's storage from my pc.
Hi, I have a fully stock nexus 7 1st gen which is stuck on a boot loop, I am able to get it into fast boot mode where I've tried the wipe data/factory reset and wipe cache partition but it just freezes. I've searched around for solutions I've even tried flashing the stock images with wugfresh toolkit with no luck, most fixes it seems need the debugging enabled on the device which I can't do because I can't get into the menu. If anyone can help me it would be fantastic
mikebolton said:
Hi, I have a fully stock nexus 7 1st gen which is stuck on a boot loop, I am able to get it into fast boot mode where I've tried the wipe data/factory reset and wipe cache partition but it just freezes. I've searched around for solutions I've even tried flashing the stock images with wugfresh toolkit with no luck, most fixes it seems need the debugging enabled on the device which I can't do because I can't get into the menu. If anyone can help me it would be fantastic
Click to expand...
Click to collapse
Hey Mike, it sounds like you have no other option than to restore back to factory using the official Google Factory Images. That will completely wipe your N7, SDCard and all
Go ahead and download the nakasi image of your choice from Google: https://developers.google.com/android/nexus/images#nakasi... make sure that you don't accidentally get the nakasig firmware as it is for the Tilapia 3G model.
Extract it with 7-zip or WinRar (or whatever) and with your tablet plugged in and in Fastboot Mode, (you will also need the fastboot/ADB drivers installed) run the flash-all.bat batch file. (You may need to enable the Windows function "Show File Extensions" to see the .bat part after the file name. There is also a flash-all.sh in the folder as well but that one is for Linux users so you wont be able to use it unless you're on Linux.
Good Luck! :good:
Hi Tim, Thanks for replying,
I'm not too worried about losing data I'm just desperate to get it working again.
I have downloaded the flash image but where would I find the download for the fast boot drivers?
mikebolton said:
Hi Tim, Thanks for replying,
I'm not too worried about losing data I'm just desperate to get it working again.
I have downloaded the flash image but where would I find the download for the fast boot drivers?
Click to expand...
Click to collapse
They should be included in the Wugfresh Toolkit that you downloaded. Just follow the steps to install the device drivers and I believe that the Fastboot drivers installs with it.
How weird, I am fixing my Dad's tonight, exact same issue! Have had it a week or so but just found time to do it now... I will do with you if you like. I already downloaded the wugfresh NRT and worked through the steps, obviously missing out the debug mode parts. Currently downloading the nakasi kot49h which is taking a while, so came on here to see what to do if this fails and saw your post!
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 11:29 PM ---------- Previous post was at 11:24 PM ----------
If you download the nexus root kit v1.8.2 from www.wugfresh.com follow the steps on there to uninstall various drivers, then click the initial setup - full driver installation to get the correct driver for your device.
Sent from my Nexus 5 using xda app-developers app
In the wug toolkit when installing drivers step by step guide to configure MTP drivers you need to disable USB debugging then disable MTP mode then re enable debugging all of which I can't do because I can't get into the menu to do anything
Hi Tom,
I can't seem to figure it out ive tried the wug toolkit a number of time with no results it seems most fixes need you to be able to enable debugging, if you find out how to do it let me know and if I by some miracle get it working I'll let you know
I have just run the flash stock and unroot option on wugfresh in the log everything has been erased but when it has tried to send bootloader is says failed<remote: bootloader is locked.>
Yes, you are up to where I got to. I fixed mine last night eventually. Next I tried a risky extra step which I won't tell as I don't think it did anything, then directly on the left of Flash and unroot there is a button to unlock bootloader. Run that, it gave me an error message but appeared to do the trick because the next time I ran flash + unroot it worked finally. Let us know how you get on!
Sent from my Nexus 5 using xda app-developers app
No it still isn't working everything I try doesn't work it all comes down to the locked bootloader and no matter what I do I can't find a solution to open it
Has anyone come across the same problem and found a solution?
mikebolton said:
No it still isn't working everything I try doesn't work it all comes down to the locked bootloader and no matter what I do I can't find a solution to open it
Has anyone come across the same problem and found a solution?
Click to expand...
Click to collapse
Open a command prompt in the folder with Fastboot. Type in "fastboot oem unlock" without quotes. That will unlock the bootloader and also you to flash factory image.
Doesn't work I've tried it before it just comes up with unlock bootloader screen where you have a choice yes (may void warranty) or no I click yes then I am directed back to fastboot mode with a message at the top left corner saying unlocking now....... but nothing ever happens, I restart device and I'm back to where I started.
Someone must know how to fix this
Somehow when updating twrp for my girlfriend lost rewrite rights. Have the dreaded lockout without a password even though she was never locked down. Suggested default password does not work. Wug-fresh tool kit is able to connect but gets stuck. Cant boot to enable usb debugging.
sully112277 said:
Somehow when updating twrp for my girlfriend lost rewrite rights. Have the dreaded lockout without a password even though she was never locked down. Suggested default password does not work. Wug-fresh tool kit is able to connect but gets stuck. Cant boot to enable usb debugging.
Click to expand...
Click to collapse
You should be able to go into fastboot and flash a complete factory image. I had the exact same problem. Using flash-all.bat command and image from Google website fixed phone but that also erased everything. Maybe someone else has a less drastic solution.
sully112277 said:
Somehow when updating twrp for my girlfriend lost rewrite rights. Have the dreaded lockout without a password even though she was never locked down. Suggested default password does not work. Wug-fresh tool kit is able to connect but gets stuck. Cant boot to enable usb debugging.
Click to expand...
Click to collapse
So at this point you have only written to the recovery partition? Is her phone stock 7.1.1? Encrypted? Rooted? Kernel? Try to provide as much information as you can. Have you just tried wiping the recovery partition and installing the stock recovery? You can also use NRT to install the previous version of TWRP you started with. That may get you back into the OS. Before wiping data, I would try the flash-all.bat method jhs39 suggests, but removing the -w switch to preserve data. Either that, or use NRT to flash stock + unroot (but select preserve data).
Got it back up and running. Could not get anything to connect through USB. Not even adb. Found a thread where someone had the same problem and tried skipsofts tool so gave that a go and low and behold it work. Got a little nervous for a bit plus had a few adults beverages. Hence the panic thread. Haha. Thanks for the response guys! She's back up and running on pure Nexus.
sully112277 said:
Got it back up and running. Could not get anything to connect through USB. Not even adb. Found a thread where someone had the same problem and tried skipsofts tool so gave that a go and low and behold it work. Got a little nervous for a bit plus had a few adults beverages. Hence the panic thread. Haha. Thanks for the response guys! She's back up and running on pure Nexus.
Click to expand...
Click to collapse
OK good, but are you out of the dog house? :laugh:
v12xke said:
OK good, but are you out of the dog house? :laugh:
Click to expand...
Click to collapse
Haha! That I am.
Ok, so I have nexus 6p that has entered into the dreaded bootloop right before i was able to upload my photos from my recent vacation. I am able to get into fastboot and recovery mode and was wondering if there is a way to get my photos off of it. I have been trying to use NRT pull command but it is giving me ABD Recovery device was not found. (phone is on bootloader) and I have no idea how to fix this. Any help would be greatly appreciated.
Edit:locked bootloader and no USB Debugging
brenster21 said:
Ok, so I have nexus 6p that has entered into the dreaded bootloop right before i was able to upload my photos from my recent vacation. I am able to get into fastboot and recovery mode and was wondering if there is a way to get my photos off of it. I have been trying to use NRT pull command but it is giving me ABD Recovery device was not found. (phone is on bootloader) and I have no idea how to fix this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hello... What happened to your phone? Maybe it's yet time to fix your bootloop. Since you have access to recovery, it's not totally dead...
I guess you have the stock recovery?
Boot into recovery and select: apply update from ADB. From here, see if your device is recognized: ADB devices. Maybe you can try to pull your files from here. I'm not sure it will works, but worth to try!
Good luck...
5.1 said:
Hello... What happened to your phone? Maybe it's yet time to fix your bootloop. Since you have access to recovery, it's not totally dead...
I guess you have the stock recovery?
Boot into recovery and select: apply update from ADB. From here, see if your device is recognized: ADB devices. Maybe you can try to pull your files from here. I'm not sure it will works, but worth to try!
Good luck...
Click to expand...
Click to collapse
Ok so I booted into recovery mode and managed to get into apply update from ADB, now what do i? sorry i am total noob to this.
brenster21 said:
Ok so I booted into recovery mode and managed to get into apply update from ADB, now what do i? sorry i am total noob to this.
Click to expand...
Click to collapse
Try:
adb devices
Do you have a serial number displayed?
About adb pull, I'm not sure about the syntax, you'll have to find d it yourself.
Good luck...
brenster21 said:
Ok, so I have nexus 6p that has entered into the dreaded bootloop right before i was able to upload my photos from my recent vacation. I am able to get into fastboot and recovery mode and was wondering if there is a way to get my photos off of it. I have been trying to use NRT pull command but it is giving me ABD Recovery device was not found. (phone is on bootloader) and I have no idea how to fix this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
BLOD is usually indicated when you have no recovery mode. Is your bootloader unlocked? Even if you are locked you can still apply an OTA and maybe fix your phone. Side loading an OTA will not wipe your data but may help recover your phone.
v12xke said:
BLOD is usually indicated when you have no recovery mode. Is your bootloader unlocked? Even if you are locked you can still apply an OTA and maybe fix your phone. Side loading an OTA will not wipe your data but may help recover your phone.
Click to expand...
Click to collapse
My bootloader is locked and I dont have usb debugging enabled, I already got the RMA approved by google so now i am just trying to save my pictures. Also I have been having little luck getting NRT working with my phone(driver issues)
brenster21 said:
My bootloader is locked and I dont have usb debugging enabled, I already got the RMA approved by google so now i am just trying to save my pictures. Also I have been having little luck getting NRT working with my phone(driver issues)
Click to expand...
Click to collapse
Locked bootloader and no usb debugging would have been useful information in your OP. Good luck to you.
v12xke said:
Locked bootloader and no usb debugging would have been useful information in your OP. Good luck to you.
Click to expand...
Click to collapse
Sorry, my last 3 phones i had usb debugging for pdanet back when I was on verizon, now on google fi i just never enabled it. Do I have any hope?