Question Fastboot Flashing taking me to help menu? - Google Pixel 6 Pro

Hi,
I'm new here so forgive me if I've posted this incorrectly.
I am trying to follow the rooting guides for the Pixel 6. I've rooted many phones before and been fine with unlocking bootloaders but the Pixel 6 is giving me some grief.
I have enabled developer options > OEM unlocking.
I have rebooted to bootloader and I am connected to the device.
I have verified I can see the device through `fastboot devices`.
I have updated my platform tools to 31.0.3.
Whenever I run `fastboot flashing unlock` I simply get the fastboot help/options outputted to the console and nothing happens on the device.
If I run `fastboot oem unlock` the command fails saying it's an invalid command (as expected).
Has anybody encountered this when unlocking their bootloader? Any advice here greatly appreciated.
Thanks,
Scott

nevermind misread

If you're on Windows, are you using PowerShell by accident? Use the Command Prompt instead.

Is USB debugging turned on? I think it must be if it is detecting your device but I can't remember for sure if it will detect device without it being on.

scojac said:
Hi,
I'm new here so forgive me if I've posted this incorrectly.
I am trying to follow the rooting guides for the Pixel 6. I've rooted many phones before and been fine with unlocking bootloaders but the Pixel 6 is giving me some grief.
I have enabled developer options > OEM unlocking.
I have rebooted to bootloader and I am connected to the device.
I have verified I can see the device through `fastboot devices`.
I have updated my platform tools to 31.0.3.
Whenever I run `fastboot flashing unlock` I simply get the fastboot help/options outputted to the console and nothing happens on the device.
If I run `fastboot oem unlock` the command fails saying it's an invalid command (as expected).
Has anybody encountered this when unlocking their bootloader? Any advice here greatly appreciated.
Thanks,
Scott
Click to expand...
Click to collapse
If you are using powershell on windows you have to type ./fastboot flashing unlock

freebee269 said:
If you are using powershell on windows you have to type ./fastboot flashing unlock
Click to expand...
Click to collapse
Well I'll be damned. This worked. Thanks man.

scojac said:
Well I'll be damned. This worked. Thanks man.
Click to expand...
Click to collapse
You're welcome! Glad it was simple. I haven't investigated but some executable commands seem to work fine in PowerShell and others don't. I'm guessing there's a potential security issue with commands compiled to work specifically with Command Prompt since PowerShell is newer and likely Microsoft considers it more secure.
freebee269 said:
If you are using powershell on windows you have to type ./fastboot flashing unlock
Click to expand...
Click to collapse
Ah, thank you! Now let's see if I remember that in the future.

Good story with happy ending! Cheers to all above!

Related

Device not recognized

I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus

Trouble unlocking bootloader

Hey new to android and looking for root my pixel 2 xl.
Following this guide https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Using windows 10, ADB and fastboot version 29.0.6-6198805, android version 8.0.0 security patch level Sept 5, 2017.
OEM unlocking and USB debugging checked.
Enter command "adb reboot bootloader" takes me into the bootloader screen.
Enter command "fastboot flashing unlock_critical" gives me error "FAILED (Write to device failed (Too many links))" "fastboot: error: Command failed"
Phone resets.
Have searched past threads suggesting to use different USB ports and cables. Tried several cables and every port with no luck. Any idea whats causing the error? Thanks
ente2323 said:
Hey new to android and looking for root my pixel 2 xl.
Following this guide https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Using windows 10, ADB and fastboot version 29.0.6-6198805, android version 8.0.0 security patch level Sept 5, 2017.
OEM unlocking and USB debugging checked.
Enter command "adb reboot bootloader" takes me into the bootloader screen.
Enter command "fastboot flashing unlock_critical" gives me error "FAILED (Write to device failed (Too many links))" "fastboot: error: Command failed"
Phone resets.
Have searched past threads suggesting to use different USB ports and cables. Tried several cables and every port with no luck. Any idea whats causing the error? Thanks
Click to expand...
Click to collapse
Did you try just
fastboot flashing unlock first?
Tulsadiver said:
Did you try just
fastboot flashing unlock first?
Click to expand...
Click to collapse
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
ente2323 said:
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
Click to expand...
Click to collapse
Maybe trying to update your firmware to something closer to current. You're about 3 years out of date....
ente2323 said:
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
Click to expand...
Click to collapse
Are you using Powershell or command prompt for your interface?
Badger50 said:
Are you using Powershell or command prompt for your interface?
Click to expand...
Click to collapse
I'm using command prompt.
Tulsadiver said:
Maybe trying to update your firmware to something closer to current. You're about 3 years out of date....
Click to expand...
Click to collapse
ente2323 said:
I'm using command prompt.
Click to expand...
Click to collapse
Then i would suggest that you update your firmware via OTA as Tulsadiver suggested. Then try your unlocking command "fastboot flashing unlock"
The critical one is no longer needed after the 9.0 update. Good luck. :good:
ente2323 said:
I'm using command prompt.
Click to expand...
Click to collapse
Do you see your serial number when you type:
fastboot devices
Badger50 said:
Then i would suggest that you update your firmware via OTA as Tulsadiver suggested. Then try your unlocking command "fastboot flashing unlock"
The critical one is no longer needed after the 9.0 update. Good luck. :good:
Click to expand...
Click to collapse
Thanks I will consider upgrading the firmware if there is no other solution. I am going to see if I can solve the problem on 8.0 for now.
Tulsadiver said:
Do you see your serial number when you type:
fastboot devices
Click to expand...
Click to collapse
Entering the command "fastboot devices" gives me nothing. When I try "adb devices" my serial number is displayed.
ente2323 said:
Thanks I will consider upgrading the firmware if there is no other solution. I am going to see if I can solve the problem on 8.0 for now.
Entering the command "fastboot devices" gives me nothing. When I try "adb devices" my serial number is displayed.
Click to expand...
Click to collapse
Are you in fastboot mode or bootloader mode when your typing "fastboot devices"???
Badger50 said:
Are you in fastboot mode or bootloader mode when your typing "fastboot devices"???
Click to expand...
Click to collapse
I'm not sure of the difference. The screen I attempt to unlock reads FastBoot Mode in red. Fastboot devices is now displaying my phones serial. Adb devices no longer displays serial.
I cannot remember if I had fastboot mode loaded earlier when I attempted the command "Fastboot devices". It is now displaying serial when enter the command while in fastboot mode.
ente2323 said:
I'm not sure of the difference. The screen I attempt to unlock reads FastBoot Mode in red. Fastboot devices is now displaying my phones serial. Adb devices no longer displays serial.
I cannot remember if I had fastboot mode loaded earlier when I attempted the command "Fastboot devices". It is now displaying serial when enter the command while in fastboot mode.
Click to expand...
Click to collapse
Fastboot mode, or bootloader mode as some call it, is when you enter it when the phone is shut off with the power + volume down buttons, or from ADB reboot bootloader when your phone is on. ADB devices will not work in fastboot/bootloader mode. Conversly speaking, fastboot devices will not work while your in your OS with the phone on. All your fastboot commands must be done from fastboot/bootloader mode. :good:
I'd try out the pixel all in one tool, it makes these things dummy proof. But really, take the OTA and get your phone updated first.
Hi everyone, I recently bought a 2xl pixel and it's updated to Android 10, and I want to change rom (basically why I like to see how much can be done)but I have the problem that it is Verizon version, I have tried to unlock it with the methods I have seen, but I have seen that it depends on the Android version.I would like to know if there is a way to unlock the OEM unlock in order to unlock the bootloader. My model is the Google Pixel 2XL 128GB. Thanks in advance
Joseft1 said:
Hi everyone, I recently bought a 2xl pixel and it's updated to Android 10, and I want to change rom (basically why I like to see how much can be done)but I have the problem that it is Verizon version, I have tried to unlock it with the methods I have seen, but I have seen that it depends on the Android version.I would like to know if there is a way to unlock the OEM unlock in order to unlock the bootloader. My model is the Google Pixel 2XL 128GB. Thanks in advance
Click to expand...
Click to collapse
Sorry to say, if your device is a Verizon carrier variant (not purchased directly from Google), then you will not be able to unlock the bootloader at this time (or likely ever)....
To be sure:
after enabling "Developer Options" if you can't enable the "OEM UNLOCKING" toggle, your bootloader is not unlockable.

Question Attempting to unlock bootloader (T-Mobile). Bootloader issues.

I'm attempting to follow this guide here https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/ and I'm finding myself having issues at step #5. ADB picks up my device while it's on no issue but when I reboot into bootloader, it no longer picks up my device to get the unlock code.
Anyone know what the issue could be? Any help is appreciated.
Edit: when I use the command "fastboot oem get_unloock_code" the CMD window says "Waiting for any device"
You don't have fastboot drivers.
craznazn said:
You don't have fastboot drivers.
Click to expand...
Click to collapse
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
MushroomElm said:
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
Click to expand...
Click to collapse
Glad you figured it out

Question 'fastboot flashing unlock' just brings up command list instead of unlocking

Hey fam, hope you've been keeping well and safe.
I recently bought the Pixel 6 Pro (so happy with it!) and am currently in the process of rooting it.
It's a fairly simple process, and I've done it with all but I'm not sure what's going wrong at the initial unlocking the bootloader stage.
OEM Unlocking & USB Debugging is enabled - I've tried to deactivate/reactive it, used different ports etc. but to no avail.
It just won't unlock, and instead just gives me prompts of commands.
I've attached the screenshots.
What am I missing/doing wrong? Thanks!
are you in fastboot when you are running these commands? boot into fastboot. type the command ' fastboot --version , what version does it output?
run fastboot devices command so your devices appears, then run the unlock command again. make sure you are you using latest platform-tools (not mininal adb etc). also reinstall the driver just in case. then
you can also just go to Android's Flash Tool to unlock the device:
Android Flash Tool
flash.android.com
Alekos said:
are you in fastboot when you are running these commands? boot into fastboot. type the command ' fastboot --version , what version does it output?
run fastboot devices command so your devices appears, then run the unlock command again. make sure you are you using latest platform-tools (not mininal adb etc). also reinstall the driver just in case. then
you can also just go to Android's Flash Tool to unlock the device:
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Thankyou so much for your quick and really helpful reply!
So I've investigated further, and re-installed all the tools/as you mentioned above - still no avail.
There does seem to be some sort of an issue as the fastboot version command responds back with 'version unknown'.
The Android Flash Tool looks like the best solution (didn't even know it existed, so thanks for that!) but I'm unsure how to proceed with it in order to unlock the bootloader (from what I'm gathered you need to have an unlocked bootloader before using it?)
I'm assuming you deselect the 'lock bootloader' option so that the tool unlocks the bootloader and then doesn't relock it? I've attached a screenshot to just check as well.
rajalot said:
Thankyou so much for your quick and really helpful reply!
So I've investigated further, and re-installed all the tools/as you mentioned above - still no avail.
There does seem to be some sort of an issue as the fastboot version command responds back with 'version unknown'.
The Android Flash Tool looks like the best solution (didn't even know it existed, so thanks for that!) but I'm unsure how to proceed with it in order to unlock the bootloader (from what I'm gathered you need to have an unlocked bootloader before using it?)
I'm assuming you deselect the 'lock bootloader' option so that the tool unlocks the bootloader and then doesn't relock it? I've attached a screenshot to just check as well.
Click to expand...
Click to collapse
yeah you need to have OEM Unlocking enabled to use Google's Flash Tool. if you don't need any data, just enable these options in the flash tool: Wipe and Force Flash Partitions. That will unlock the bootloader and wipe/reflash Android. Enabling the "lock bootloader" option will re-lock the bootloader but since you are rooting it, leave it unchecked.
But you should look into why Platform-Tools isn't working on your system. Here are instructions on how to set it up (make sure to remove all other platform-tools)
there's also Nexus Tools from Github (developed my a known tech journalist)
@rajalot besides what @Alekos said, I always go straight to the source for the latest SDK Platform Tools every time I flash anything. Also, Get the Google USB Driver (this is for Windows). Note, a recent experience. I have a Samsung tablet and have the Samsung USB drivers installed. This driver worked perfectly fine for my Pixel 6 Pro too for the last two months, but for June the full factory image would error out trying to flash until I uninstalled Samsung's driver and went back to Google's. So if you have any other device USB drivers installed than Google's, you may have to uninstall those and install Google's.
But yeah, as @Alekos said, the site Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own) will get you what you need too although if there's a conflicting driver, you would still have to solve that.
I'm going out on a limb but is this a Verizon p6p?
Nergal di Cuthah said:
I'm going out on a limb but is this a Verizon p6p?
Click to expand...
Click to collapse
I hope @rajalot updates us, although they said they did enable OEM Unlocking (and seem to be indicating that they have since re-disabled and re-enabled it, although that can be interpreted differently), which would usually indicate that they're not using a Verizon device. Weird, huh? I'm guessing the Platform Tools version is the culprit, but I'd like to hear back to confirm.
rajalot said:
OEM Unlocking & USB Debugging is enabled - I've tried to deactivate/reactive it, used different ports etc. but to no
Click to expand...
Click to collapse
bump!
well i had exactly the same issue with new pixel 6a.
installed latest google driver , latest platform tools... no luck
Nexustools did the trick for me instantly
thanks @Alekos for this share!!

Bootloop issue with boot reason

hello there, I'm currently using one plus 7 T, I don't know why , but after updating the last software update my device stuck in Boot loop, i can't able to turn it on, The boot reason says that : Init_user0_Failed . Unable to parse kernel log.Could you please help me to get out from this issue. As i'm outstation from the city, so i can't able to reach the service center. I need my data so i'm trusting you that you guys will sort out the issue, Thank you so much for reading this.
"fastboot set_active other" to switch slot
I'm facing the same problem. Please find a workable solution asap. I'll thank endlessly.
HueyT said:
"fastboot set_active other" to switch slot
Click to expand...
Click to collapse
How and where do I do this?
kiranlalge said:
How and where do I do this?
Click to expand...
Click to collapse
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
HueyT said:
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
Click to expand...
Click to collapse
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
kiranlalge said:
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
Click to expand...
Click to collapse
Plug phone into windows laptop with adb installed on laptop:
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Zesotar said:
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Click to expand...
Click to collapse
15 min adb fastboot drivers, OnePlus USB drivers, Qualcomm USB 9008 drivers (msmtool)
ashuetrx said:
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Click to expand...
Click to collapse
Enable "USB debugging" in Dev.Options, Boot into fastboot mode on phone, type "fastboot devices" and it should give you a code--then your phone is ready for fastboot flashing files
Tried in another computer with Windows 10. It returns: "Slot change is not allowed in Lock State"
I get the a code with the fastboot devices, so it seems the phone is ready.
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Zesotar said:
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Click to expand...
Click to collapse
how exactly did you do it with MSM tool?
cromedo7 said:
how exactly did you do it with MSM tool?
Click to expand...
Click to collapse
5 seconds with Google.
Fastboot method is much easier and without data loss.
Download
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Reboot to fastboot mode
Start minimal ADB and fastboot
Type: fastboot devices
If you see device and something like that:1S67gz everything's ok.
Now type: fastboot set_active other
Type reboot.
Done

Categories

Resources