Hi all,
I'm trying to unroot and relock my Pixel 2 XL because I need to send it in for warranty for an issue with the phone's microphone.
when I try to run the flash-all command in adb I get errors during each step. Could somebody help me figure out what's going on?
Here is what adb is kicking back at me:
Code:
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot devices
712KPRW1212070 fastboot
C:\platform-tools>flash-all
Sending 'bootloader' (36336 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Too many links))
Finished. Total time: 0.040s
Sending 'radio' (60388 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.035s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...
Chelseablue said:
Hi all,
I'm trying to unroot and relock my Pixel 2 XL because I need to send it in for warranty for an issue with the phone's microphone.
when I try to run the flash-all command in adb I get errors during each step. Could somebody help me figure out what's going on?
Here is what adb is kicking back at me:
Code:
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot devices
712KPRW1212070 fastboot
C:\platform-tools>flash-all
Sending 'bootloader' (36336 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Too many links))
Finished. Total time: 0.040s
Sending 'radio' (60388 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.035s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
By the way, I am flashing image 9.0.0 (PQ1A.181205.002, Dec 2018)
I tried flashing the most recent one and got the same errors so I tried an older image.
Chelseablue said:
Hi all,
I'm trying to unroot and relock my Pixel 2 XL because I need to send it in for warranty for an issue with the phone's microphone.
when I try to run the flash-all command in adb I get errors during each step. Could somebody help me figure out what's going on?
Here is what adb is kicking back at me:
By the way, I am flashing image 9.0.0 (PQ1A.181205.002, Dec 2018)
I tried flashing the most recent one and got the same errors so I tried an older image.
Click to expand...
Click to collapse
What version of platform-tools are you using?
And, if your already on stock rom, just do a factory reset and send it back. An unlocked bootloader doesn't void your warranty.
Badger50 said:
What version of platform-tools are you using?
And, if your already on stock rom, just do a factory reset and send it back. An unlocked bootloader doesn't void your warranty.
Click to expand...
Click to collapse
I'm running r28.0.1. Really? I thought it had to have the bootloader locked for warranty. If that's the case, it would save me the time...
Chelseablue said:
I'm running r28.0.1. Really? I thought it had to have the bootloader locked for warranty. If that's the case, it would save me the time...
Click to expand...
Click to collapse
Just reset it and send it in. Many have done so including myself with the 6p. Question, have you tried a different cable, and are using the command...fastboot flashing lock....?
And, have you run the magisk uninstaller zip to fully get rid of root?
Related
My phone stuck while using so as usual I pulled out the battery and it was his end. From then on bootanimation glitched and the phone restarted all over again. Sth like a bootloop but with complete phone restart. Then I tried to full wipe but with no luck, recovery hung and rebooted the phone. Even now restoring/zip installing etc suddenly restarts the phone. I also tried to flash new recovery/rom via fastboot as well as via Nexus Root Toolkit but everytime I got 'too many links error'
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2308 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.404s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.005s
sending 'radio' (12288 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.004s
archive does not contain 'boot.sig'
error: out of memory
Click to expand...
Click to collapse
I used two different cables that I use for every flashing so far, and different usb slots... I have no idea what else I can do.
Sth has changed, I tried to flash TWRP instead of CWM via fastboot and again, got 'too many links' error BUT it flashed the new recovery anyway . So now I have TWRP, managed to flash cm 10.2.1+gapps. I have a recovery log for sb to analyze. Could you check if my emmc is corrupted telling ftom this log?
i9250 recovery log http://pastebin.com/4Yx0ZwJK
Thanks
EDIT/
A second ago it booted to system in a normal way, then a sudden restart and the phone is stuck while boot animation, like a catch 22...
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
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.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
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.005s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.
Hello i tried to unlock the Bootloader but i get an error every Time
C:\Users\kilia>adb reboot bootloader
C:\Users\kilia>cd C:\adb
C:\adb>fastboot flash unlock unlock.bin
sending 'unlock' (1 KB)...
FAILED (remote: unknown command)
finished. total time: -0.000s
sometimes i get this error message and my phone just restarts
C:\adb>fastboot flash unlock unlock.bin
sending 'unlock' (1 KB)...
FAILED (status read failed (Too many links))
finished. total time: 5.905s
Hi, I rooted my Pixel 2XL a couple of weeks ago and just recently decided to remove the root and lock the bootloader. So I just locked the bootloader, which I thought would only delete all data and reset it back to normal. But instead the whole operative system got removed. When I noticed that I tried to install the factory image. But that only gave me errors...
This is what happens every times:
Code:
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
--------------------------------------------
Bootloader Version...: TMZ12a
getvar:version-baseband FAILED (remote: 'unknown command')
getvar:serialno FAILED (remote: 'GetVar Variable Not found')
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (remote: 'unknown command')
Checking 'product' FAILED
Could not getvar for 'product' (remote: 'GetVar Variable Not found')
fastboot: error: requirements not met!
Press any key to exit...
And this happens a second time:
Code:
Sending 'bootloader' (55680 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Sending 'radio' (60428 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Unknown error))
getvar:serialno FAILED (Write to device failed (Unknown error))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Unknown error))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...
Anyone who has any idea what to do?
Sadly, 99% chance you have created a very expensive coaster for your beer... Hopefully you can RMA it.
The phone NEEDS to be returned to 100% factory stock BEFORE locking the botloader or it bricks the phone. There MAY had been a few cases of folks sideloading an OTA afterwards but it might just be chatter like Bigfoot sightings...
CyberpodS2 said:
Sadly, 99% chance you have created a very expensive coaster for your beer... Hopefully you can RMA it.
The phone NEEDS to be returned to 100% factory stock BEFORE locking the botloader or it bricks the phone. There MAY had been a few cases of folks sideloading an OTA afterwards but it might just be chatter like Bigfoot sightings...
Click to expand...
Click to collapse
Thanks for the response. I will make sure I think of that next time. Fortunately it was only the cable that needed switching for it to be able to send the files.
You did the one thing that you must not do. Good luck with unbricking.
On a Saturday midnight, I thought I wanted to revert back to Android 8.1 on my Pixel. However, I made a big mistake doing it at midnight, mistakenly flashing the user debug AOSP instead. My phone is now corrupted and will always stuck at the white Google logo with me unable to undo the damage. What I have tried so far is flashing the factory images via ADB update and Fastboot, but it seems like the software is failing to register the phone as a Pixel.
I keep getting fail messages with ADB updates reporting
E: footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: error: 21
Click to expand...
Click to collapse
And fastboot reporting
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.002s
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: 'unknown command')
getvar:serialno FAILED (remote: 'GetVar Variable Not found')
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvarroduct FAILED (remote: 'unknown command')
Checking 'product' FAILED
Could not getvar for 'product' (remote: 'GetVar Variable Not found')
fastboot: error: requirements not met!
Click to expand...
Click to collapse
I would really appreciate any help because I'm in a really desperate situation, or in case the situation can't be fixed, would replacing the hardware revive the phone. Thank you in advance.