Database Info

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

[Q] Fastboot and locking problems

hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?

Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?

The USB connector socket at the phone might not make a proper contact with the USB plug. Make sure they connect properly. You may try another cable, or have a look at your USB socket and compare it to another. Check out particularly the little horizontal part in the USB socket.
Make sure you're in bootloader/fastboot mode before attempting to connect in fastboot. Fastboot cannot detect your phone, make sure your udev related settings are appropriate. Check on a Linux PC: https://source.android.com/source/initializing.html Configuring USB Access section.
If after this your phone will not be recognized by fastboot, please post the output of the following command (as root), after seconds after connecting the phone in fastboot mode:
Code:
tail /var/log/messages

Harbb said:
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
Click to expand...
Click to collapse
fastboot does not show my device. I go into bootloader using adb reboot bootloader because my stupid power button wont work, thats why i want to sent it in to get fixed.

If drivers are properly installed this might not be working because the power button is stuck in or something. Not sure what to try to sort it out if that's the case.

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!

bjuderas said:
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
Click to expand...
Click to collapse
if you read the first post it says that fastboot doesnt work

mikeydubbs said:
if you read the first post it says that fastboot doesnt work
Click to expand...
Click to collapse
Sorry, didn't read it right!
And I'm sorry, but I don't know the solution for your problem!

have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g

p1gp3n said:
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
Click to expand...
Click to collapse
yeah i have and i tried using my laptop, and ubuntu 11.10
this sucks so much

i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.

shahravi94 said:
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
Click to expand...
Click to collapse
so do you think as long as its not rooted they wont care?

yup! i flashed a stock image so it was unrooted and sent it in. they fixed it up for me

If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Hi, I know this thread is old but I was having the same problem relocking my nexus 4 after installing stock Android 4.4.3 KitKat.
I'm using Nexus Root Toolkit, I don't know what tools you're using to lock your nexus S boblem ut this very easy to use it downloads the drivers and what ever you need to lock, unlock or flash stock and custom roms for any Nexus device.
So my problem was that I would launch OEM Lock on Nexus Root Toolkit and it would detect the device, reboot in Fastboot mode and it would proceed just fine but after saying "Launching TWRP.... something" it would reboot the phone and say to me "Waiting for device" untill it would time out.
I found out that when the program(NEXUS ROOT TOOLKIT) asked me to download a TWRP IMG files, I said no everytime because I didn't think I'd need it. So after trying 5 times, I allowed it to download it and i retryed to OEM Lock it and MAGIC!
Somewhere in the process of Locking the rom it is going to need the TWRP File so allowing the program to download it solved it for me.
I don't know if this will help you or if you still have the same phone, but if you do have use Nexus Root Toolkit and download all it asks and you'll be fine.
Good Luck.

"waiting for device" forever when "fastboot oem unlock:
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
I have the same exact problem.
ADB works fine when the phone is up & running, so I am suspecting a driver compatibility problem when the phone is in "FASTBOOT MODE".
I tried to install the "Universal Naked Driver 0.73 (Compatible with Nexus 5, 4, 7, 10 and S)" but Windows 7 64-bit refuses to pick it up. I use the Device Manager method which shows (when the phone is in "FASTBOOT MODE"):
Code:
"Other Devices
> Android 1.0"
When the phone is up & running, Device Manager shows it as:
Code:
"Android USB Devices
> SAMSUNG Android Composite ADB Interface"
Any idea how to proceed from here?
-----
Update: After a day went by, I searched Google some more and found a thread that describes exactly my problem:
http://forum.xda-developers.com/nexus-s/help/nexus-s-root-windows-requests-android-1-t878579
Which led me to:
http://forum.xda-developers.com/nex...oader-nexus-s-t875580/post9861928#post9861928
Which led me to:
http://pdanet.co/a/
I am rushing to try this now...
-------
Success!
~> fastboot oem unlock
...
OKAY [ 18.734s]
finished. total time: 18.734s
Click to expand...
Click to collapse

nunojpg said:
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
Click to expand...
Click to collapse
It helped. Thanks!

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks

[Q] Stuck in bootloop but don't have USB Debugging enabled

So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!

When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?

th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Yes, it does.

What I would do if I was stuck in a bootloop (well thats what I did when I soft bricked my phone "NO OS INSTALLED" now it works again )
is go here https://cyngn.com/products/oneplusone/ download the cm-11.0-XNPH38R-bacon-signed-fastboot.zip extract it in your fastboot folder (make sure you have the latest sdk tools from google or else with an older version it will say that system.img is too large when you flash the zip), open a cmd (run as administrator). check if your bootloader is still unlocked (mine got locked so I was facing a similar situation) type fastboot oem device-info ....it should say unlock true.... then
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
hope it works

hermunn123 said:
So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!
Click to expand...
Click to collapse
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
And voila you are good to go.:good:

vamshi88 said:
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
And voila you are good to go.:good:
Click to expand...
Click to collapse
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?

hermunn123 said:
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?
Click to expand...
Click to collapse
What is your phones status now?

vamshi88 said:
What is your phones status now?
Click to expand...
Click to collapse
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.

hermunn123 said:
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.
Click to expand...
Click to collapse
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Fastboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.

vamshi88 said:
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Flashboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.
Click to expand...
Click to collapse
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon

timmaaa said:
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon
Click to expand...
Click to collapse
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.

vamshi88 said:
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.
Click to expand...
Click to collapse
He could try unlocking the bootloader, but my guess is that it will fail with his phone in the current state. Failing to uncheck the 'update cm recovery' option in Developer Options shouldn't pose a problem until an update is taken.
Transmitted via Bacon

Stuck in bootloop
th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Hey there,
My OPO is stuck in bootloop and believe me, i just took it out of the box (though it was 4 months without charge).
I cannot put it in to fast boot and I tried power cycling too by discharging it for 12 hours & charging for 6+1 hour. Its just the same.
Can you help?

[Q] PC won't recognise phone, but Moto Tool will

I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!

If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.

Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?

audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.

Adb commands won't work when the phone is in fastboot mode from what I have seen.

audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.

Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.

flashing pixel 2 without usb debugging

Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.

If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.

Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.

mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.

Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.

mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/

Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.

mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache

Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.