Develop Bugs

[ROOT] Request for tester

Hi all,
I've generated root-ing boot.img for Pixel C, based on my root ( http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ):
Based on latest factory image (MXB48K)
The boot.img is available at http://superuser.phh.me/nexus/ryu/MXB48K/
There are three interesting variants: eng, noverity, nocrypt.
- eng is "standard" version with crypted /data, and dm-verity enabled for /vendor and /system
- noverity only has dm-verity on /vendor and /system disabled
- nocrypt has both dm-verity and crypted /data disabled.
The process to flash it is:
- Go in Settings, Developer settings, tick "Allow OEM Unlock"
- Reboot to fastboot mode
- fastboot oem unlock
- fastboot boot boot-su-eng.img
- install phh's Superuser from Play Store ( https://play.google.com/store/apps/details?id=me.phh.superuser ) (or FDroid)
- And if it works, to really install it, do fastboot flash boot boot-su-eng.img
This is working, thanks to everyone here, especially @cheep5k8

I might be getting my usb type c cable today! If I do I'll definitely test this out!

Potential tester
phhusson said:
Hi all,
I've generated root-ing boot.img for Pixel C, based on my root ( http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ):
Based on latest factory image (MXB48K)
The boot.img is available at http://superuser.phh.me/nexus/ryu/MXB48K/boot-su-eng.img
The process to test it is fastboot oem unlock, fastboot boot boot-su-eng.img and then install phh's Superuser from Play Store ( https://play.google.com/store/apps/details?id=me.phh.superuser )
And if it works, to install it, do fastboot flash boot boot-su-eng.img
Can someone test it for me on a Pixel C?
Thanks
Click to expand...
Click to collapse
I take it you don;t have a Pixel C to test yourself? Just got one yesterday and a type c cable today, adb working fine. Not sure I want to be guinea pig though :-\

the unlock command on the pixel c is the same as the 6p

CharlesW123 said:
I take it you don;t have a Pixel C to test yourself? Just got one yesterday and a type c cable today, adb working fine. Not sure I want to be guinea pig though :-\
Click to expand...
Click to collapse
You can do fastboot boot nameoffile.img
It won't change anything .. Fastboot flash flashes to memory
Sent from my Nexus 6P using Tapatalk

I wish this device came with a data cable. I would've already tested this if it wasn't for that.
Sent from my Pixel C using Tapatalk

This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.

ericvh said:
This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.
Click to expand...
Click to collapse
Tried flashing to recovery image and booting from that, but also didn't seem to work - I think ultimately it just dumped me into normal boot.
Maybe part of the problem is the double-clutch bootloader, what loads first isn't fastboot -- its something else. Looking at headers in the recovery image, seems like maybe a chromeos loader?
Also tried to just go ahead and flashboot flash boot boot-su-eng.img, but its complaining about multiple of block size:
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.047s]
sending 'boot' (9413 KB)...
OKAY [ 0.257s]
writing 'boot'...
(bootloader) writing flash
FAILED (remote: image not multiple of block size)
finished. total time: 0.342s
I got around this with some rounding, but maybe that's what is screwing up for me.

Well you weren't supposed to flash it until you booted it first to make sure it worked.
The obvious fix would be to flash the stock boot and recovery then factory reset in recovery. Then try again from a clean slate with encryption turned off.
Sent from my iPhone using Tapatalk

ericvh said:
This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.
Click to expand...
Click to collapse
Interesting.
Have you done the fastboot flashing unlock? (some devices might allow fastboot boot without fastboot flashing unlock)
(Or oem unlock?)
Did the unlock forced factory reset?
I guess flashing back stock boot.img made everything back working?
What have you done to go past the rounding error?
Please note that this boot.img is signed, so rounding it shouldn't be just appending zeros to the end (though it might be interesting to test withotu signing)
This bootloader is really interesting.
It shows the bootloader has been done by Chrome team, which is amazing news compared to N9's HTC crappy bootloader.
This means that actually most (all?) of the source of the bootloader is available in chromium os tree, to better understand what happens.
Thanks for your tests
Edit 1: Ok, the bootloader is:
git clone https://chromium.googlesource.com/chromiumos/third_party/coreboot -b firmware-smaug-7132.B
Edit 2: I'm not seeing anywhere where fastboot could be handled...

If this isnt tested and what not when I get mine I'm sure I could try it
But...google screwed me and sent it overnight tonight but fedex is saying its not coming until tuesday...

superchilpil said:
Well you weren't supposed to flash it until you booted it first to make sure it worked.
The obvious fix would be to flash the stock boot and recovery then factory reset in recovery. Then try again from a clean slate with encryption turned off.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Indeed, I tried the vanilla boot first following the instructions exactly, I just did the flash to see if that made a difference after the 'test' boot failed. It was easy enough to reflash with a recovery image. It does seem to be the case that booting with fastboot somehow messes with whatever encyrption is being used on the user data. Although perhaps the 'flashed' boot just didn't get far enough to trip over it.
---------- Post added at 06:13 AM ---------- Previous post was at 06:09 AM ----------
I have not tried fastboot flashing unlock yet, oem unlock is done however - that did force a factory reset, but from what I can tell Marshmellow always enforces an encrypted image. I got past the rounding error by appending zeros as you suggest. flashing back stock boot.img restored the device to normal use.
There appears to be a two stage boot, when I boot into the bootloader it has an option to enter fastboot, enter android recovery (which doesn't work), enter usb recovery (which doesn't work) and continue with the boot process. Neither fastboot nor ADB interact with the system when its in this state. Once I'm in fastboot mode on the tablet, I can see interact with fastboot. Its also worth noting that despite enabling developer mode, I can't see the tablet with adb when running.
phhusson said:
Interesting.
Have you done the fastboot flashing unlock? (some devices might allow fastboot boot without fastboot flashing unlock)
(Or oem unlock?)
Did the unlock forced factory reset?
I guess flashing back stock boot.img made everything back working?
What have you done to go past the rounding error?
Please note that this boot.img is signed, so rounding it shouldn't be just appending zeros to the end (though it might be interesting to test withotu signing)
This bootloader is really interesting.
It shows the bootloader has been done by Chrome team, which is amazing news compared to N9's HTC crappy bootloader.
This means that actually most (all?) of the source of the bootloader is available in chromium os tree, to better understand what happens.
Thanks for your tests
Edit 1: Ok, the bootloader is:
git clone https://chromium.googlesource.com/chromiumos/third_party/coreboot -b firmware-smaug-7132.B
Edit 2: I'm not seeing anywhere where fastboot could be handled...
Click to expand...
Click to collapse

ericvh said:
[/COLOR]I have not tried fastboot flashing unlock yet, oem unlock is done however - that did force a factory reset, but from what I can tell Marshmellow always enforces an encrypted image. I got past the rounding error by appending zeros as you suggest. flashing back stock boot.img restored the device to normal use.
There appears to be a two stage boot, when I boot into the bootloader it has an option to enter fastboot, enter android recovery (which doesn't work), enter usb recovery (which doesn't work) and continue with the boot process. Neither fastboot nor ADB interact with the system when its in this state. Once I'm in fastboot mode on the tablet, I can see interact with fastboot. Its also worth noting that despite enabling developer mode, I can't see the tablet with adb when running.
Click to expand...
Click to collapse
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)

I am welcome to testing. Just got my Pixel C and would love to help achieve root thank you for your work thus far and if needed let me know what I can do!

Okay, will give unsigned a shot. About to jump on a plane to Europe so I may not be as responsive (and less likely to want to factory reset) for about a week.
I was speaking of android developer mode, not aware of any chromeos development mode. Depending on level of "commitment" I may consider just going for coreboot to Linux and ditching android all together. I'm assuming I can probably prototype that on my JTX1 which has a serial port and then prep images for the Chromebook -- but that would mean ditching android altogether which in some ways would be a shame. Dual boot is definitely the preference for me at the moment.
phhusson said:
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)
Click to expand...
Click to collapse

ericvh said:
Okay, will give unsigned a shot. About to jump on a plane to Europe so I may not be as responsive (and less likely to want to factory reset) for about a week.
Click to expand...
Click to collapse
Ok no problem.
I was speaking of android developer mode, not aware of any chromeos development mode. Depending on level of "commitment" I may consider just going for coreboot to Linux and ditching android all together. I'm assuming I can probably prototype that on my JTX1 which has a serial port and then prep images for the Chromebook -- but that would mean ditching android altogether which in some ways would be a shame. Dual boot is definitely the preference for me at the moment.
Click to expand...
Click to collapse
That's unrelated, but I think I'll probably buy a Pixel C when we'll see first non-Android development (Or I might jump straight to it, I already did it for good old Toshiba AC100)
I almost expect Google to publish a ChromeOS image for Pixel C, or at least see an official Chromium OS....
Considering you definitely sound like the hacker-type. How does the keyboard feel? Do you feel you could code hours-long on it?
Also, since there is "usb recovery" mode, I think you could always dual-boot back to Android with a usb stick (ok, there is no usb type c usb stick yet, that means ugly cable ATM)
Linux4Tegra should make porting full-blown Linux very easy, including OpenGL/GLX

phhusson said:
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)
Click to expand...
Click to collapse
boot-tmp.img has the same behavior.
My theory is fastboot is just there for reflashing via otg, not for actual booting and we'll need a chromeos wrapper + the payload burned to flash in order to get anywhere. I need to do some reading up on chromeos and coreboot and probably go thorugh and setup a chromeos enviornment.

ericvh said:
boot-tmp.img has the same behavior.
My theory is fastboot is just there for reflashing via otg, not for actual booting and we'll need a chromeos wrapper + the payload burned to flash in order to get anywhere. I need to do some reading up on chromeos and coreboot and probably go thorugh and setup a chromeos enviornment.
Click to expand...
Click to collapse
What has to be tested first is building from AOSP (i assume aosp tree is available for ryu?)

Not sure. I briefly looked for the kernel source, but wasn't sure I found the right one. There's some stuff in there for Smaug, but I assume the android kernel is probably bit different (although it doesn't seem to be the same as the one on the JTX1 or the Nvidia Shield TV -- so google must be doing something a bit more aggressive than Nvidia is in their products).
phhusson said:
What has to be tested first is building from AOSP (i assume aosp tree is available for ryu?)
Click to expand...
Click to collapse

I'm still in hope to find who implements fastboot...
Can someone give me the result of:
fastboot getvar product
fastboot getvar kernel
This doesn't require oem unlock, and doesn't have any risk, so anyone with working fastboot can do that

Can't send fastboot flash commands to Pixel C

fastboot devices shows the Pixel C, but any fastboot flash commands (or fastboot flashall) fail due to unsupported command errors. Any ideas what's going on? I tried reinstalling drivers and rebooting Windows 10. Those didn't help. What's wrong? Is there a fix I can make?
This device used to have a rooted copy of Marshmallow from xceed along with a TWRP installation. But those are gone. The system partition is now blank (probably along with the user and data partitions).

I had a similar issue as the device being not detected. I used Nexus Root Toolkit v2.1.8 to flash TWRP and push supersu so I could flash them.

could the partitions just be unmounted which would show as empty

Mother_Teresa said:
I had a similar issue as the device being not detected. I used Nexus Root Toolkit v2.1.8 to flash TWRP and push supersu so I could flash them.
Click to expand...
Click to collapse
My problem is different from yours. fastboot detects the device and can perform thinks like locking and unlocking. What it can't do is flash. I did try NRT. But it can't flash either as it appears to use the same driver and fastboot that I was using--just buried.

dkryder said:
could the partitions just be unmounted which would show as empty
Click to expand...
Click to collapse
Not sure who you were replying to. But the partitions (except for bootloader and recovery) are empty as they've been wiped. I wiped the system partition myself with TWRP once. Turning on and off the bootloader lock seems to have done the rest. Besides, what would that have to do with the unsupported command I got?

I misread.

Will Pittenger said:
My problem is different from yours. fastboot detects the device and can perform thinks like locking and unlocking. What it can't do is flash. I did try NRT. But it can't flash either as it appears to use the same driver and fastboot that I was using--just buried.
Click to expand...
Click to collapse
If I recall correctly--but it's been a number of months, I had a sort of similar problem with my Pixel C trying to flash a system image after unlocking the bootloader. This thread http://forum.xda-developers.com/pixel-c/help/fastboot-pixel-c-t3328635 was helpful. Selecting some generic Google driver in Win 10 did the trick, but I do not recall which driver.

tbcpn said:
If I recall correctly--but it's been a number of months, I had a sort of similar problem with my Pixel C trying to flash a system image after unlocking the bootloader. This thread http://forum.xda-developers.com/pixel-c/help/fastboot-pixel-c-t3328635 was helpful. Selecting some generic Google driver in Win 10 did the trick, but I do not recall which driver.
Click to expand...
Click to collapse
Their drivers didn't help either.

Well, I'm getting a different error. I moved the USB cable to a different port on the PC. The first port was on a hub as the 3.0 ones built into the computer were in use. I only have one on the PC itself that's on the front. The others I have to crawl under the desk and behind the computer for--and those are in use to. The new error is that it didn't like the raw file size of the img files I tried. Seems i need something that's a multiple of the block size which is 4096.

I finally have Nougat on my device.

[SOLVED] HELP -- Issues unlocking bootloader

I've tried fastboot flashing unlock, fastboot OEM unlock and a couple others All In bootloader mode. I've used a couple different versions ADB fastboot. A lot of people have been using the minimal ADB 1.4.2 which is the most current. But i ended up getting them from googles platform-tools. Fastboot flashing unlock always responds with
FAILED (command write failed (no error))
Then the device reboots.
Developer settings is on OEM unlocking is checked and USB debugging is also checked.
I don't know what else to do other than start from scratch entirely including deleting all ADB and fastboot files and maybe factory resetting the device although I've only had it for a day. It's amazing sitting at my home with my computer and a phone and being pissed off for 3 hours no one understands this unlike us. I know a lot of other people had the same issue. Anyone have any ideas they would be greatly appreciated. This is a pixel XL 2 from Google

Different and and fastboot...

Just to confirm:
Is this a Verizon version?
Have you followed all of the steps for flashing a system image from https://developers.google.com/android/images
adb otherwise works (e.g., adb devices lists the phone)
fastboot otherwise works
I realize you already covered some of this. Unlocking will wipe anyway, so factory reset can't hurt.

foosion said:
Just to confirm:
Is this a Verizon version?
Have you followed all of the steps for flashing a system image from https://developers.google.com/android/images
adb otherwise works (e.g., adb devices lists the phone)
fastboot otherwise works
I realize you already covered some of this. Unlocking will wipe anyway, so factory reset can't hurt.
Click to expand...
Click to collapse
This is not a Verizon version. ADB is working and ADB devices works correct. Fastboot devices respond with the device serial number so it appears to be working properly. I've never had issues like this, don't know why flashing a factory would do anything but I probably will. And maybe fastboot flashing unlock from a 'fresh' device as I have my apps on it from a Google restore.

dontbeweakvato said:
I've tried fastboot flashing unlock, fastboot OEM unlock and a couple others All In bootloader mode. He called me I've used a couple different versions ADB fastboot. A lot of people have been using the minimal ADB 1.4.2 which is the most current. It always responds with
FAILED (command write failed (no error))
Then the device reboots.
Developer settings is on OEM unlocking is checked and USB debugging is also checked.
I don't know what else to do other than start from scratch entirely including deleting all ADB and fastboot files and maybe factory resetting the device although I've only had it for a day. It's amazing sitting at my home with my computer and a phone and being pissed off for 3 hours no one understands this unlike us. I know a lot of other people had the same issue. Anyone have any ideas they would be greatly appreciated. This is a pixel XL 2 from Google
Click to expand...
Click to collapse
It's one command. Did you get it?
Sent from my Pixel 2 XL using Tapatalk

danon.brown said:
It's one command. Did you get it?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
fastboot flashing unlock
C:\Users\Robert\Downloads\platform-tools>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
Im using the latest platform-tools from google, developer settings is ticked along with oem unlocking and usb debugging.
this is super frustrating

dontbeweakvato said:
fastboot flashing unlock
C:\Users\Robert\Downloads\platform-tools>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
Im using the latest platform-tools from googles.
this is super frustrating
Click to expand...
Click to collapse
The latest minimal adb/fastboot work fine. Is usb debugging turned on? When you type fastboot devices do you see your phone?
The easiest way would be to re install minimal adb. At the end it ask do you want to re it. Say yes and it starts in the correct command prompt. Type fastboot reboot bootloader just to make sure it's communicating. If it doesn't reboot try another cable.
Sent from my Pixel 2 XL using Tapatalk

danon.brown said:
The latest minimal adb/fastboot work fine. Is usb debugging turned on? When you type fastboot devices do you see your phone?
The easiest way would be to re install minimal adb. At the end it ask do you want to re it. Say yes and it starts in the correct command prompt. Type fastboot reboot bootloader just to make sure it's communicating. If it doesn't reboot try another cable.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
usb debugging is on and fastboot devices returns correct with the serial number. guess ill reinstall tomorrow. im running command prompt and directing it to platform-tools folder that has adb.exe and fastboot.exe. It doesnt make sense. when in doubt redo EVERYTHING

did you enable OEM unlock from Developers Options ?
make sure you are using the latest ADB & fastboot

dontbeweakvato said:
I've tried fastboot flashing unlock, fastboot OEM unlock and a couple others All In bootloader mode. I've used a couple different versions ADB fastboot. A lot of people have been using the minimal ADB 1.4.2 which is the most current. But i ended up getting them from googles platform-tools. Fastboot flashing unlock always responds with
FAILED (command write failed (no error))
Then the device reboots.
Developer settings is on OEM unlocking is checked and USB debugging is also checked.
I don't know what else to do other than start from scratch entirely including deleting all ADB and fastboot files and maybe factory resetting the device although I've only had it for a day. It's amazing sitting at my home with my computer and a phone and being pissed off for 3 hours no one understands this unlike us. I know a lot of other people had the same issue. Anyone have any ideas they would be greatly appreciated. This is a pixel XL 2 from Google
Click to expand...
Click to collapse
I had the same problem as you. I kept trying for about 2 hours over and over. I was about to throw the phone against the wall when it finally just worked. I didn't do anything different when it worked than the previous 200 times it didn't.

awe.. never mind...

murphyjasonc said:
I had the same problem as you. I kept trying for about 2 hours over and over. I was about to throw the phone against the wall when it finally just worked. I didn't do anything different when it worked than the previous 200 times it didn't.
Click to expand...
Click to collapse
I've tried with maybe three or four different fast boots like minimal ADB a couple different versions and also Google on platforms-tools. I unchecked and rechecked developer options and oem unlocking and USB debugging. It's kind of pissing me off because last night I spent a good four hours trying every possible configuration. And I've never had this much problem on any phone ever it usually works the first time or second if I made an easy mistake but not after multiple hours and multiple command prompt checks and fastboot ADB checks. Yes I was about ready to throw this phone against the wall and return it which is unheard of in my world of Google perfection.
I was thinking "Fu***************************k!!"

It took me about 8 tries before I had success.

Just got mine. Not gonna unlock yet. Want to keep Android Pay for now. Actually if AdClear and Fake GPS work, I may stay stock unrooted.
Default backups seem to work good these days, even remembering passwords for apps.
Glad I didn't waste 4 hours trying to unlock. I spend way too much time flashing, updated and trying to trick SafetyNet. But it's all working great now with Magisk 14.3 on OG Pixel.
Can't wait to get the OTA notification and not start stressing out about ADB and fastboot....
Sent from my marlin using XDA Labs

akenis said:
Just got mine. Not gonna unlock yet. Want to keep Android Pay for now. Actually if AdClear and Fake GPS work, I may stay stock unrooted.
Default backups seem to work good these days, even remembering passwords for apps.
Glad I didn't waste 4 hours trying to unlock. I spend way too much time flashing, updated and trying to trick SafetyNet. But it's all working great now with Magisk 14.3 on OG Pixel.
Can't wait to get the OTA notification and not start stressing out about ADB and fastboot....
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I've honestly never stressed about anything going back to Nexus 4 on launch day. But this...... Fuuuuuuuccccckkkkk

dontbeweakvato said:
I've honestly never stressed about anything going back to Nexus 4 on launch day. But this...... Fuuuuuuuccccckkkkk
Click to expand...
Click to collapse
Feel your pain. Wasted a whole day a few weeks ago trying to switch from Super Su to Magisk and get Oct updates. Wound up trying to flash factory in ages using Crouton in a Chromebook.
Just saw that custom kernel is avail....so we can unlock and pass safety net. So TEMPTING. Just say NO. Gonna drink wine and watch Orville till these evil thoughts disperse.
Sent from my marlin using XDA Labs

I download the latest version of minimum tool from https://developer.android.com/studio/releases/platform-tools.html. That one has stamp date of 05/12/2017, which I'm not sure if it supports Pixel 2 XL yet. adb devices does see the phone.
adb devices
List of devices attached
710KPCA0237899 device
doing fastboot flashing unlock just yields nothing.
fastboot flashing unlock
< waiting for any device >

dyingearth said:
I download the latest version of minimum tool from https://developer.android.com/studio/releases/platform-tools.html. That one has stamp date of 05/12/2017, which I'm not sure if it supports Pixel 2 XL yet. adb devices does see the phone.
adb devices
List of devices attached
710KPCA0237899 device
doing fastboot flashing unlock just yields nothing.
fastboot flashing unlock
< waiting for any device >
Click to expand...
Click to collapse
Restart the phone and hold Volume down. Then run the fastboot command again if it doesn't work right away.
Sent from my Pixel 2 XL using Tapatalk

First of all, thanks Deuces and Northmendo for the idea to help people.
I have created a pretty easy all in one that will install the lasted adb and fastboot system wide and fastboot flash unlock and unlock_critical. It will install the latest 8.1 developer preview for the Pixel 2 XL for you as well with all the necessary files included. I did not inlcude the lock and lock_critical function as most do not use it.
As the instructions state, please use a usb 2.0 port and and usb-c to usb-a cable that supports data. Also enabling debugging and oem unlock is a must.
It includes a menu driven batch file that is super easy to use.
For those that want to use this same batch file on the pixel 2 itself, please extract the zip from google and then extract the zip within the zip. Next pull the bootloader and radio img file from the root of the zip to the FILES folder included in this program. Then copy all the contents from the zip within the zip to the same FILES folder. It should contain about 22 files in total. We really don't need the android-info.txt file.
I will also be including a batch file with a semi empty FILES folder that does not include any Google related 8.1 files for those that want to download it quicker and copy their own contents to it for flashing. Like Pixel 2 owners that already have the 8.1 preview downloaded.
If anyone needs any help please feel free to ask. This post was rushed so please excuse my grammatical errors.
FOR PIXEL 2 and PIXEL???? ----NO IMG's inlcuded
http://www.mediafire.com/file/eksn04aiaeqvvia/PXEL_2_&_PIXEL_SAUCE_NO-IMGS.zip
FOR PIXEL 2 XL ---- IMG's included
http://www.mediafire.com/file/1wde39mj7ssbxb3/PIXEL_2_XL_SAUCE_V1.zip
dontbeweakvato said:
usb debugging is on and fastboot devices returns correct with the serial number. guess ill reinstall tomorrow. im running command prompt and directing it to platform-tools folder that has adb.exe and fastboot.exe. It doesnt make sense. when in doubt redo EVERYTHING
Click to expand...
Click to collapse
dyingearth said:
I download the latest version of minimum tool from https://developer.android.com/studio/releases/platform-tools.html. That one has stamp date of 05/12/2017, which I'm not sure if it supports Pixel 2 XL yet. adb devices does see the phone.
adb devices
List of devices attached
710KPCA0237899 device
doing fastboot flashing unlock just yields nothing.
fastboot flashing unlock
< waiting for any device >
Click to expand...
Click to collapse

danon.brown said:
Restart the phone and hold Volume down. Then run the fastboot command again if it doesn't work right away.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
OK that works.

ADB and fastboot cannot detect the phone

Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?

binarnh said:
Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?
Click to expand...
Click to collapse
Most likely the culprit is either out of date platform-tools or TWRP...
What version of adb, fastboot, & TWRP are you using? Also, how are you booting TWRP -- there have been many cases where people would use the command "fastboot flash boot twrp.img" instead of booting temporarily...
Hope this ends up being helpful as that means it resolves it...

Are you able to fastboot boot the latest twrp.img?
Might want to give Deuces script a whirl. I've seen this fix situations like yours.

ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...

binarnh said:
ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...
Click to expand...
Click to collapse
This might sound crazy, but, at least try another USB A to C cable, and other ports on your pc. The P2XL is notorious for being finicky when it comes to cables and ports. What might work for one phone, doesn't necessarily mean it will for the other. Make sure it's a 2.0 USB cable as well :good:

I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same

binarnh said:
I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same
Click to expand...
Click to collapse
Then it's likely a hardware/port issue would be my guess.

Meh, so I will look for a workshop nearby that will exchange the port for me and check later

I would also suggest that you re-download EVERYTHING...
You may be stuck with a "buggy" TWRP image file or platform tools....and/or go against conventional thinking and download and try an older version of TWRP to see if it does it at that point as well...
In either case, hopefully you get it figured out and good luck to you...hope this ends up being helpful!

There were a number of Pixel 2 XL's that did suffer from charging port issues, including my original. Luckily I was still under warranty and was issued a replacement. The phones would charge fine but data did not transfer as with adb/fastboot, nor would Android Auto work.
https://forum.xda-developers.com/pixel-2-xl/help/pixel-2-xl-charging-port-damaged-t3783638

Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"

binarnh said:
Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"
Click to expand...
Click to collapse
What fastboot command did you give?

Badger50 said:
What fastboot command did you give?
Click to expand...
Click to collapse
I use flash all script

binarnh said:
I use flash all script
Click to expand...
Click to collapse
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?

Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables

binarnh said:
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Not running platform-tools through power shell either are you?
What happens when you try double clicking on the flash-all.bat file with your mouse?

binarnh said:
Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Based on your error, I'm guessing all the files in the Full Factory .zip file (all 6 of them) aren’t residing there with the adb & fastboot .exe files within the platform-tools folder. Make sure you’re seeing those 6 files (you will have a two .sh files, two .img files, one .zip file, etc.) with the .exe adb & fastboot file.
Then, also make sure that you are directing your powershell or command prompt to the correct “platform-tools” folder, because many other people seem to have multiple “platform-tools” folders and they end up directing to a wrong folder…
Hope this ends up being helpful…

I fixed it! The error in fastboot mode probably came from a file that I extracted from winrar, when I downloaded the factory image again and extracted the files this time through 7zip and copied them to the platform-tools folder and double-clicked flash-all.bat fastboot started and the installation was successful! Thanks to everyone who wanted to help me solve this problem <3
ps. btw, I haven't replaced this broken port on the phone... just started working again...

Question I'm stumped - Fastboot mode LE2125 not responding to ADB commands

When I updated my LE2125 Oneplus 9 pro 5G to C.63 I lost root ( I tried the Magisk way when I previously updated and it allowed me to update and then preserve my root) and couldn't get it back.
So I decided to downgrade using MSM Tool and now I am on Oxygen OS build 11.2.2.2.LE15AA and I can no longer use any ADB commands when in Fastboot mode (the device does not respond), my laptop does not acknowledge using ADB Device (but it does when NOT in Fastboot mode).
The device shows Device State Locked.
When booting my phone up, I made sure in Developers options to set OEM Unlocking checked ON, as well as USB debugging checked ON.
When on Oxygen OS build 11.2.2.2.LE15AA and reboot into Recovery , I have the "Advanced" option, but not if I upgrade to LE2125_11.C.48_1480_202204082113 and rebooting into Recovery, choosing English, the next screen does not show the "Advanced" option as an available choice..
Laptop on Windows 10, have used MSM tool with my LE2125 with no issues. Anybody have any ideas?

LormaD said:
When I updated my LE2125 Oneplus 9 pro 5G to C.63 I lost root ( I tried the Magisk way when I previously updated and it allowed me to update and then preserve my root) and couldn't get it back.
So I decided to downgrade using MSM Tool and now I am on Oxygen OS build 11.2.2.2.LE15AA and I can no longer use any ADB commands when in Fastboot mode (the device does not respond), my laptop does not acknowledge using ADB Device (but it does when NOT in Fastboot mode).
The device shows Device State Locked.
When booting my phone up, I made sure in Developers options to set OEM Unlocking checked ON, as well as USB debugging checked ON.
When on Oxygen OS build 11.2.2.2.LE15AA and reboot into Recovery , I have the "Advanced" option, but not if I upgrade to LE2125_11.C.48_1480_202204082113 and rebooting into Recovery, choosing English, the next screen does not show the "Advanced" option as an available choice..
Laptop on Windows 10, have used MSM tool with my LE2125 with no issues. Anybody have any ideas?
Click to expand...
Click to collapse
You can't use adb commands in fastboot. You can only use fastboot commands. fastboot devices

jamescable said:
You can't use adb commands in fastboot. You can only use fastboot commands. fastboot devices
Click to expand...
Click to collapse
i meant to say fastboot commands...
i.e. fastboot devices, fastboot oem unlock, fastboot boot boot.img

LormaD said:
i meant to say fastboot commands...
i.e. fastboot devices, fastboot oem unlock, fastboot boot boot.img
Click to expand...
Click to collapse
Then it's a driver issue

jamescable said:
Then it's a driver issue
Click to expand...
Click to collapse
So you think it's a driver issue when the phone responds to my laptop when "Not" in Fastboot mode, and then no longer responds to commands when in Fastboot mode?...
Will try that...

LormaD said:
So you think it's a driver issue when the phone responds to my laptop when "Not" in Fastboot mode, and then no longer responds to commands when in Fastboot mode?...
Will try that...
Click to expand...
Click to collapse
Yes. A lot of people say adb works but fastboot doesn't. Usually there's a driver update in windows. Google it man. Very common

I had the same problem. After messing around with some drivers it finally started working

GeminiRx said:
I had the same problem. After messing around with some drivers it finally started working
Click to expand...
Click to collapse
Damn Drivers...
I did a system restore to an earlier point in Windows 10... I then redownloaded and installed oneplus USB drivers and it worked.