Develop Bugs

[Q] Error flashing factory images 5.0.2

Hello everyone.
I am having this error while trying to flash the latest factory image.
Adb and fastboot seem propoerly configured as I have adb devices and fastboot devices working.
sending 'bootloader' (3911 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time 5.011s
rebooting into bootloader...
FAILED (status read failed ( Too many links))
finished. Total time: 117.384s
Any help would be appreciated, because I am lost on this one.
SDK is fully updated and doing everything as I did to flash 5.0.1
Thanks in advance.

Can't help with ADB or Fastboot but I can suggest dirty flashing this stock, rooted rom by scrosler found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Worked great for me. Good luck!

Mine failed the first couple of times too, but on the third attempt it went through. However, it turns out that I had failed to turn on the ADB bridge on the first one, and I guess it was still coming up on the second.

Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?

yosmokinman said:
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
Click to expand...
Click to collapse
Very true, except that it uses adb to initially reboot the tablet into fastboot mode.
It would probably skip that step if you were already in fastboot mode, but if the OS is running, the flash-all script will attempt to restart the device by running adb reboot bootloader.
That said, if ADB isn't working, checking the cable and drivers is the next step.

Getting into the bootloader doesn't require adb. Use the hardware buttons.

Softbricked Nexus5x with bootloader locked and factory images

When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated

nvrpunk said:
When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated
Click to expand...
Click to collapse
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.

ulxerker said:
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.
Click to expand...
Click to collapse
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s

nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.

ulxerker said:
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.
Click to expand...
Click to collapse
Thanks, I am going to try the sideload of the OTA.zip And see if that works.

nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I'm curious if you did anything other than what you listed, because Allow OEM unlocking that was set from Developer Options should still be one given what your described actions.

Completely Bricked?

All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work.
Device state is unlocked.
Reinstalled Google Drivers.
I will use taimen-opm1.171019.013-factory-6d9954c3
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version eac51f2bb6a8-android
Unified Android Toolkit:
Booting TWRP recovery-twrp-3.2.1.0-taimen.img ..
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.007s
Click to expand...
Click to collapse
Cannot flash TWRP
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot flash recovery twrp.img
sending 'recovery' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.009s
Click to expand...
Click to collapse
ADB sideload
PS C:\adb> adb sideload C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip
loading: 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip'
* cannot read 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip' *
Click to expand...
Click to collapse
If I use flash-all.bat:
sending 'bootloader' (36344 KB)...
FAILED (unknown status code)
finished. total time: 343.328s.
Click to expand...
Click to collapse
If I use flash-all command in cmd:
PS C:\Users\tiger\Desktop\tamien> flash-all
error: cannot load 'bootloader-taimen-tmz10n.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
error: cannot load 'radio-taimen-g8998-00122-1708311414.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
W/ ( 9820): Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.025.zip': I/O Error
Click to expand...
Click to collapse

Do you have the latest adb downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.

azntiger said:
All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work. Device state is unlocked.
Unified Android Toolkit:
Cannot flash TWRP
ADB sideload
If I use flash-all.bat:
If I use flash-all command in cmd:
Click to expand...
Click to collapse
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical

ilal2ielli said:
Do you have the latest are downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
Click to expand...
Click to collapse
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot boot twrp.img
downloading 'boot.img'...
Click to expand...
Click to collapse

azntiger said:
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
Click to expand...
Click to collapse
Why are you trying to flash the November build?

Badger50 said:
Why are you trying to flash the November build?
Click to expand...
Click to collapse
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.

azntiger said:
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
Click to expand...
Click to collapse
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/

Badger50 said:
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Click to expand...
Click to collapse
I'll take a look if I can get my phone working again lol.
Badger50 said:
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
Click to expand...
Click to collapse
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
PS C:\Users\tiger\Desktop\Pixel> fastboot devices
711KPVH0902199 fastboot
PS C:\Users\tiger\Desktop\Pixel> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
PS C:\Users\tiger\Desktop\Pixel> fastboot flashing unlock
...
Click to expand...
Click to collapse

azntiger said:
I'll take a look if I can get my phone working again lol.
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
Click to expand...
Click to collapse
You may have to use this to get back on track my friend.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

I'm not entirely sure what the issue is (it could be a couple of things), but here are some issues that I see to help you troubleshoot:
1. Adb commands don't work in bootloader mode, only fastboot commands, which is why your device is visible to fastboot and not adb.
2. The file that you tried to adb sideload was a factory image, not an OTA. Adb sideload can only be used with OTA images. And even if you were using an OTA image, OTA images cannot be used to downgrade to a previous firmware version.
3. The latest version of adb is 1.0.39. You are using an older version. That fact itself doesn't really matter since adb will not help you in this situation, but fastboot will and if your adb is obsolete, I'd be willing to bet that your fastboot is too. Pixel 2 support was added in the October 2017 release of adb and fastboot. If yours is older than that, you're gonna have a bad time.
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
5. You do not have driver issues. The fact that fastboot devices worked means that your drivers/connection are/is working fine.
PS: Get the latest adb and fastboot here: https://developer.android.com/studio/releases/platform-tools.html
UPDATE: I did a Google search for adb/fastboot version eac51f2bb6a8-android. I found a reference to it in a forum post dated mid-2016. There's your problem. Or one of them, anyway. If you do adb --version or fastboot --version on the latest releases, they will tell you that they are version 0.0.1-4500957.

TheSt33v said:
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
Click to expand...
Click to collapse
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...

azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Click to expand...
Click to collapse
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.

Badger50 said:
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Click to expand...
Click to collapse
All the platform-tools and the stock rom are together in folder.

azntiger said:
All the platform-tools and the stock rom are together in folder.
Click to expand...
Click to collapse
Did you extract the factory image first, or just put the whole zip file in platform-tools?

azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
Click to expand...
Click to collapse
Hmm. Fastboot is definitely having issues communicating with your phone. "Failed to identify current slot" is a bad sign. If I were you, I would try flashing the most recent factory image (not the November 8.0 image you're trying to flash) first just to see if you can get everything up to date again and clear out any mismatched files that may have been flashed during your attempts. Once you manage that, then try to downgrade. If you can, try a different computer too, preferably one with a type C input that you can use the stock USB cable with.
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
Badger50 said:
Did you extract the factory image first, or just put the whole zip file in platform-tools?
Click to expand...
Click to collapse
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.

The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.[/QUOTE]
Thanks man. I learned something new today :good:
Wonder if his transfer cable. I've seen that cause headaches as well ?

It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.

azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
Oh nice! Glad you got it figured out. This stuff can be a bit tricky at times. I know I've lost some hair from pulling it out when things didn't go right! ?

azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
I was on edge just reading this! I would also look into Deuce's script. It can save the 'device can't boot' issue once and for good.
Kudos on not having a faulty device~!

Taimen Bootloader Unlock Unexpectedly Regressing/Re-Locking

Days past I successfully unlocked the bootloader on my girlfriend's Taimen handset, flashed TWRP etc etc. No hitches whatsoever. I bought another for myself via the Google Store.
I booted it up today. As was on hers, OEM Unlock is prevented until I allow the handset to update to 8.1.
Done. OEM unlock then accessible and enabled.
I used my girlfriend's same PC with the same Minimal ADB and Fastboot, rebooted to fastboot and execute
Code:
fastboot flashing unlock_critical
Are you sure? ...volume up/down and power button to commit. Done. The unlock appeared successful as it rebooted to the out of box setup routine again.
I transferred the TWRP zip to the handset and rebooted to fastboot. Upon executing the command to temp boot TWRP from the IMG file fastboot
Code:
boot path "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.2.1-2-taimen.img"
I got the following response...
Code:
downloading 'boot.img'...
OKAY [ 0.870s]
booting...
FAILED (remote: Can not boot in Lock State)
finished. total time: 0.873s
Sure enough I look down at the handset and the fastboot menu reflects it's locked again. Weird.
I reboot and check OEM unlock. It reflects OEM unlock still toggled on. I go back to fastboot and again execute
Code:
fastboot flashing unlock_critical
Code:
FAILED (remote: Device already : unlocked!)
finished. total time: 0.002s
This is despite fastboot clearly showing "device state - locked"
I regress to dev options and toggle OEM unlock off. Reboot. Toggle OEM Unlock back on.
Same ill behavior.
Am I missing something??

try fastboot flashing unlock
depending on bootloader version you no longer need to fastboot flashing unlock_critical
see here.

@uicnren You a gentlemen and a scholar. Simple as that. Thanks.

Pay_It_Forward_Pete said:
@uicnren You a gentlemen and a scholar. Simple as that. Thanks.
Click to expand...
Click to collapse
:good:

No valid OS and can not connect to adb, briked??

So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
Cant find valid operating system
The device will not start
Click to expand...
Click to collapse
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you

When you say 'adb', do you mean you're trying to use the command 'adb' when you're in fastboot? At the risk of stating the obvious, you need to use 'fastboot' command when you're in fastboot mode. 'adb' is only used when you're in recovery or in the actual android system. Otherwise you may wish to try a different fastboot version (sometimes that matters).

Javi22 said:
So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you
Click to expand...
Click to collapse
TOOL_ALL_IN_ONE_1.1.1.3.zip it's the solution,Block again from here and you can start over

Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
So my problem now is to unlock the bootloader

Javi22 said:
Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
So my problem now is to unlock the bootloader
Click to expand...
Click to collapse
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:

Badger50 said:
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:
Click to expand...
Click to collapse
Thank you! But still the same...:
Code:
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock_critical
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>

Javi22 said:
Thank you! But still the same...:
Click to expand...
Click to collapse
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.

Badger50 said:
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.
Click to expand...
Click to collapse
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk

Javi22 said:
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk
Click to expand...
Click to collapse
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota

Badger50 said:
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Thanks but I can not get into recovery, the same screen:

Javi22 said:
Thanks but I can not get into recovery, the same screen:
Click to expand...
Click to collapse
Can you get into fastboot mode? If so you can then run deuces bootloop tool.
https://www.google.com/url?sa=t&sou...AxAB&usg=AOvVaw02czE3zeVK5sKbCe6V9L2v&ampcf=1