Stuck in the Fastboot/ Recovery - Google Pixel 2 XL Questions & Answers

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.

Related

Problem whith official rom

Exuse me for my bad English, because A'm from Russia ...I want to return to the offiсial rom of HTC ONE X. But i have any problems... When I do
cd c:\Android \Android>fastboot flash recovery recovery.img
sending 'recovery' (5742 KB)...
FAILED (remote: (00120000))
finished. total time: 0.002s \Android>fastboot oem lock ...
FAILED (unknown status code)
finished. total time: 0.000s \Android>fastboot oem lock ...
OKAY [ 0.000s]
finished. total time: 0.000s \Android>
Then i run official rom and it has problem...mistake [140] Wrong version of loader. Is it anybody help me what to do with it?
http://forum.xda-developers.com/showthread.php?t=1660807

[Q] m8 possibly corrupt hboot

Hi
I am not really sure what i have done wrong here, but i have got myself to a stage where i can get to fastboot, but i cannot get to the recovery, if i select hboot then i get the following:
TWRP: teamwin screen flashes a couple of times then the device reboots
CWM: black screen the the device reboots
Stock recovery: android driod with a red exclamation mark then the device reboots
I have tried multiple recovery's as you can see.
I know that i am currently in a state where i have NO os on the phone.
**TAMPERED***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.14.2133156.UA24G
OpenDSP-v26.2.2-00538-M8974.0106
OS-
eMC-boot 2048MB
Feb 26 2014,21:38:56.14307
This all started when i somehow got in a reboot loop when SuperSU tried to push the su binary to TWM.
Any help or directions to get me back ontrack would be appreciated.
Thanks
Darren
--
addition, just following some instructions about restoring to stock boot, recovery and rom from android reolution, output below:
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (8262 KB)...
OKAY [ 0.971s]
writing 'boot'...
OKAY [ 0.666s]
finished. total time: 1.638s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash recovery recovery
mg
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.605s]
writing 'recovery'...
OKAY [ 0.992s]
finished. total time: 2.599s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.020s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash update update.zip
target reported max download size of 1830711296 bytes
sending 'update' (1387053 KB)...
OKAY [ 59.626s]
writing 'update'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 137.319s
Try fastboot erase cache

Bricked -unable to use Wug tool kit to revive it

i can only get to fastboot mode. My nexus Bootloader version - FLO- 04.04, and it's unlocked. I've tried to use Wug tool kit but got stuck at "erasing cache". See log below. I've tried different cables and different USB ports. Any tips or guidance is greatly appreciate. Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.742s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
sending 'boot' (7448 KB)...
OKAY [ 0.245s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.166s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
erasing 'cache'...
i have the same problem
the nand flash is broken, change your mainboard and you will be happy again
i will never buy a asus device

HELP Can't flash system.img

Hey
when i want to flash the factory image from google with the "flash-all.bat" i got this Error.
failed to allocate 2008772888 bytes
error: update package missing system.img
i tried to flash manualy dosent work too.
J:\fastboot\bullhead-mmb29p>fastboot flash system system.img
load_file: could not allocate 2008772888 bytes
error: cannot load 'system.img'
this comes when i run the "flash-all.bat"
sending 'bootloader' (4382 KB)...
OKAY [ 0.213s]
writing 'bootloader'...
OKAY [ 0.137s]
finished. total time: 0.352s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.012s
sending 'radio' (56614 KB)...
OKAY [ 1.807s]
writing 'radio'...
OKAY [ 0.506s]
finished. total time: 2.315s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2008772888 bytes
error: update package missing system.img
Press any key to exit...
please help me:crying:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
many many thanks :good:
you safed the life from my 5x ♥
Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
Hello, sorry for my English, i've download the Minimal fastboot and adb file and i've installated it. but it styll doesn't work, when i try to type te command: fastboot flash system system.img, the result is error: cannot load system.img. what can i try to do?
Download and install SDK Manager. Later, install SDK tools, SDK Platform Tools, Android support library and Google USB driver. Then try again.

Pixle 2XL stuck in fastboot loop

Hi all, really annoying problem where my phone is stuck in a fastboot loop. The phone loads into fastboot and if it is plugged into the PC via USB it keeps rebooting into fastboot. I can use this command 'fastboot oem fb_mode_clear' when it's about to load and it sometimes causes it to stop rebooting. As soon as I input another command like fastboot devices, it begins the loop again. It also only shows ?????? as the device name.
Is there anything I can do if I do manage to get it to stop rebooting while it's connected to the PC? Thanks.
An example of the rebooting -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Here's what happens when I try and flash the factory image:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
W/ziparchive(133904): Unable to open 'image-taimen-opd1.170816.010.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.010.zip': I/O error
Press any key to exit...
This is the best I've done I think...
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.009s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.009s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.199s
target didn't report max-download-size
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1866 MB) to disk... took 9.931s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (341 MB) to disk... took 2.077s
archive does not contain 'vendor.sig'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.012s
Press any key to exit...
Hi, in case you stumble on this self-rambling thread looking for an answer, it turns out changing the port fixed it. In my case I plugged it into a usb-c hub that had usb-a ports and that allowed it to work properly. God knows why, but worth a shot if anybody is having issues with their PC's usb ports.

Categories

Resources