Database Users

[Q] Trying to get back to stock

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:

[Q] Bricked phone, any way to fix it?

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.

[Q] Nexus 4 Bootloop Troubles!!

There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.

saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
It would have saved you a lot of problems of you had of done it manually, without a toolkit
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk

Same problem !
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
---------- Post added at 01:19 PM ---------- Previous post was at 01:02 PM ----------
priyab said:
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
Click to expand...
Click to collapse
Hey the flash-all.bat worked !!!! .. I just waited for like 15 mins after the flash-all.bat was done and viola! its back

This is great find
Those who face this issue can go to safe mode and backup their data while on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.

Nexus 7 2012 Retrieve data without USB debugging, Bootloop. Solved !!

Hi hope I have come to the right place for help. My Nexus 7 16GB 2012 wifi is freezing after the google logo during the boot animation of the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kitkat, but not sure which version, and have a locked bootloader, not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app

alscott51 said:
High hope I have come to the right place for help. My daughters Nexus 7 16GB 2012 wifi is freezing after the google logo when booting at the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kit kat, but not sure which version, and have a locked bootloader, and not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull command

Ok Im not familiar with this programme but have read a bit about it. I will try and venture into this alien world of abd and see what happens.
Sent from my GT-I9100 using XDA Free mobile app

Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app

You can't use adb in fastboot mode. It seems possible to pull files with fastboot, but it isn't fun.
Maybe you can flash something via fastboot to make it boot again? That would be the best way imho.

alscott51 said:
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Go to recovery and try adb commands. In bootloader you can use only fastboot commands.

Ok I booted to the bootloader, from here selected recovery where the little Android is laying on its back. Now device manager showed nothing connected. Used the power + volume-up combo to get to the four recovery options, still nothing in device manager. Selected side load adb option and bingo welcome sound of device being connected. Windows didn't find a driver so downloaded adb driver from Asus but device manager refused to use it. Did some reading and downloaded Koush's universal driver and now device manager showed device connected and driver installed. The ADB devices command now shows the Nexus info. Now to learn the pull command. ....
Sent from my GT-I9100 using XDA Free mobile app

Done lots if reading on this and think I am beat. From what I have read the with the Nexus 7 in its current state (stock, locked bootloader, unrooted, no usb debugging) the sdcard is not reachable through the stock recovery sideload option in any way. I had a ray of hope from the above link to pull files via fastboot but I have read the thread and it seems the person says it was misleading information that they posted. I followed information in another thread and tried extracting boot, recovery and system files from a nexus factory image and flash them via fastboot but it fails stating the bootloader is locked. If I unlock the bootloader I will lose the sdcard data I want, as I will have to perform a factory reset. So as suggested I could install a CWM/TWRP recovery, but to do this via fastboot I need to unlock the bootloader......
I am thankful for people taking the time to help and for all suggestion posted but unfortunately I can not find a fix. I would be sooo grateful if someone could prove my finding wrong....
Off to do some reading about mounting the sdcard via adb shell but don't think this will work via stock recovery
Sent from my GT-I9100 using XDA Free mobile app

Install and configure any ftp/sftp/ssh server from Google play and download data wireless.

jkkk88 said:
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
Click to expand...
Click to collapse
Can't get the nexus to boot up, just bootloader and recovery accessible so don't think I'll be able to do this.
Sent from my GT-I9100 using XDA Free mobile app

Fixed it and saved all data.
Sent from my GT-I9100 using XDA Free mobile app

Sideload fix
Managed to fix this without losing anything (sdcard, docs, pictures, apps, setting etc). Took a while mostly due to lack of understanding of fastboot and ADB sideload from the recovery options.
Lots of posts advising to boot into the bootloader and use adb and fastboot. Everything I read to do with using fastboot commands via the nexus bootloader (insatalling boot/system/recovery etc) involved having an unlocked bootloader or having to unlock it as in my situation. This of course involves a factory reset of the Nexus resulting in a loss of the data that I was trying to retrieve, so i ruled this option out.
As suggested I should try the ADB pull command, but because I had not previosly enabled the USB debugging option via the setting menu everything I read said this was not an option. Read in one forum post something like "As you have not enabled USB debugging ADB is dead to you, just flash a factory image via recovery".... and lose all your data... this is not what I wanted to hear so I abandoned this option aswell.
Then I discovered sideloading. With this you can manually install an OTA update (the ones that pop up in your notification window saying something like "System update available") via the Nexus recovery option "apply update from adb". This does not invlove wiping any data , apps etc as it would just install the differences between what you are currently running eg. 4.4.2 and the updated android you want to go to eg 4.4.3. This is different to flashing a full factory image via fastboot were everything would be erased/formatted and an entirely new install would be flashed. Of course... simple when you know what the option is for and what you are doing. Of course I had had no clue what sideloading was all about.
So with my new knowledge I downloaded an OTA update from here:
http://forum.xda-developers.com/showthread.php?t=1745781&highlight=4+23
but wasnt sure what version of KitKat was running prior to the bootloop. I knew it was somewhere around 4.4.2.. so took a chance and tried KTU48L from KOT49H (4.4.3 from 4.4.2) and copied it to the Minimal ADB folder.
I booted the Nexus to the recovery mode and selected "apply update from adb". The tablet then conected to the PC (windows) as shown by Device manager. (I used Koush's universal ADB driver as windows failed to find anything of use). https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I opened Minimal ADB downloaded from here
http://forum.xda-developers.com/showthread.php?t=2317790
and typed "adb devices" which showed the Nexus was connected.
I then typed "adb sideload nexus OTA file name.zip"
Lots of sending files messages appeared in the adb window the Nexus disconnected from the PC and showed this...
Finding update package...
Opening update package...
Verifying update package...
Insatlling update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image....
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions..
Patching remaining system files...
script succeeded: result was [/system]
Install fromADB complete.
All looked good so I rebooted the Nexus but I was still stuck in a bootloop at the four spinning circles. I tried clearing the cache from the recovery menu several times powering it down and leaving it to boot but after half an hour accepted failure.
So I tried downloading KTU84P from KTU84L (4.4.4 from 4.4.3) and repeated the procedure. this time not as much files seemed to be sent to the Nexus, I guess this was just a small update. Again it showed "script succeeded" but still failed to get past the spinning circles of the boot animation.
Thinking I was defeated again I was going to give up but tried downloading LRX21P from KTU84P (5.0 from 4.4.4). This time when I sideloaded a mass of files were sent to the Nexus much much more then the other two updates, obviously KitKat 4.4.4 to lollipop 5.0 was a big update. Again I got the "script succeeded" but this time I got the new Lollipop boot animation and the Nexus fully booted.
I can only guess that the big update to Lollipop removed or replaced files or did something to replace the faultly part of my install that other OTA updates did not change.
Anyway I did not find any other fix that advised sideloading an OTA update to fix a bootloop, maybe I just looked in the wrong places. I tried to write this in laymans terms for non techie people in the hope that it may help someone else in the same situation who like me knows very little about android.
Thanks to the forum for the information...
Also link here with some info about half way down page on effects of usb debugging being enabled for sideloading, and near the bottom of the page a good link to a sideload pdf guide.
https://productforums.google.com/forum/#!topic/nexus/Fhl6VVb0kio

I just bought a used 6p it keeps saying to log in with previous gmail.how do I fix.

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.