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~!
Related
I am new to android and this is my new first android.
I saw postings yesterday says OTA 4.0.2 rolled out, and people got it already and there are manual way to get it, so I decided try to work on it. I followed the guide how to unlock bootloader and how to root, the first steps went through, but I can get through the last steps because it isays 'waiting for device', i tried everything. somehow I see the bootloader is unlocked.
I installed the stripped 4.0.2 update from here . I used odin mode. now my battery is dropping 1% every few minutes.
I want to flash restore stock image see if I can fix the problem. I trie flash it with odin, but oding crashed.
can anybody help?
Are you running Linux??
Edit:
From Windows or Linux (only tested by myself of Debian Linux) with fastboot in your PATH:
Reboot into bootloader (adb reboot bootloader)
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
windows.
USB driver is installed when phone is normal mode. but in orin the usb driver does not show.
Moved. Please don't post in the wrong forums.
this is GSM version.
where do you get the image files? also why I can't do in orin?
is there a simple way to flash the factory image directory or any gui tool to do it?
Files are here: http://code.google.com/android/nexus/images.html
Make sure to pick the right one: yakju is GSM and mysid is CDMA
Download the tgz file and extract it (might need winrar on windows IDK)
All the Radio,Bootloader,Recovery and system files are included. The only way I know how to flash these files is fastboot, which imo is a safer way than odin - though I have not really used odin before.
can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.
citrix80 said:
can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.
Click to expand...
Click to collapse
You need the android sdk installed on your computer. Read this guide:
http://www.xda-developers.com/android/adb-easy-tutorial/
There are also a handful of threads in this very forum answering your same question. A few of which I have given step by step guides myself. Do a quick search.
I downloaded file from
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
and used fastboot, all steps worked out.
here is the log
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-primekj1
0.img
error: cannot load 'bootloader-toro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
j10.img
error: cannot load 'bootloader-maguro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
k15.img
sending 'bootloader' (2308 KB)... OKAY [ 0.296s]
writing 'bootloader'... OKAY [ 0.604s]
finished. total time: 0.900s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools>fastboot flash radio radio-maguro-i9250xxkk6.img
sending 'radio' (12288 KB)... OKAY [ 1.545s]
writing 'radio'... OKAY [ 2.375s]
finished. total time: 3.920s
C:\android-sdk\platform-tools> fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools> fastboot update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0146882D0601C00A
--------------------------------------------
checking product... OKAY [ 0.007s]
checking version-bootloader... OKAY [ 0.007s]
checking version-baseband... OKAY [ 0.008s]
sending 'boot' (4074 KB)... OKAY [ 0.517s]
writing 'boot'... OKAY [ 0.492s]
sending 'recovery' (4406 KB)... OKAY [ 0.562s]
writing 'recovery'... OKAY [ 0.789s]
sending 'system' (317594 KB)... OKAY [ 39.809s]
writing 'system'... OKAY [ 36.250s]
rebooting...
finished. total time: 78.476s
C:\android-sdk\platform-tools>
the phone reboot automatically after the last step.
the battery is still dropping.
is there a way to reset to 4.0.1? I am not sure what is causing the problem.
I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE
You dont put the files on your phone. They go in the same folder on your computer as fastboot.exe
trilogee said:
I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE
Click to expand...
Click to collapse
put files in ur tools folder inside sdk and you fastboot -w update image-yakju-itl41f.zip and get an invalid command error ,,,should of been ,,, fastboot flash -w
oh god didnt realize i got any replies.
so ive gotten past that part now i have a more frustrating problem...installed platforms-tools from the sdk manager, that enable me to get this:
c:\sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >
but when i open the image zip the boot recover and system are there.
the waiting for devices deal, in device manager Android Phone is listed with sub Android ADB interface...driver is installed and device is recognized...why does it still say waiting for device...thank you guys so much.
If I get this working today I promise I will make a small donation to both xda and those that help me.
you need open the zip then extra the tar inside it with 7 zip, then copy all 4 extracted file into sdk folder, or same folder with fastboot. then run fastboot. you can use my output in page 1. type exact same thing.
trilogee
How sure are you that the phone is in bootloader mode at the time of flashing? Try executing fastboot devices first to confirm that fastboot can see the phone...Then what the OP has suggested above or do what you were doing.
Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)
trilogee said:
Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)
Click to expand...
Click to collapse
If fastboot is showing a blank command line, then it means that it can't see your phone. Anything done after that is not going to work. It could then be one of two things, i.e. either your setup is not correct or your phone is not in bootloader mode. Can adb see the phone normally from your PC, i.e. can it see it when you call 'adb devices' or can you see the logcat output?
With the former, I can suggest that you check if the installation is correctly done? As with the latter, I tend to get adb to reboot the phone in bootloader by issuing a 'adb reboot bootloader' and is far quicker than the button-press option.
did you install sdk and driver? when your phone in normal mode, plug in usb to pc, in device manager, you see android driver?
I tried again. whe I get here
C:\android-sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
but the files are actually in the zip file.
the process still finished.
did it skip those files?
I think that has something to do with the .sig verification settings
..same thing happened to me but image flashed fine and everything seems to be running smoothly. Crazy how I struggled with this so much at first its actually an extremely simple process.
Sent from my Galaxy Nexus using XDA App
I waked up this morning and checked time on my Pixel XL, about 30 mins after I checked my phone which has been powered off. I tried to power on, it screens off right after the google logo showed on, and loop.
Then I entered bootloader, it shows:
Code:
BL: N/A
Baseband: N/A
Product/Variant: marlin-ROW-PVT
Serial Number: HT69Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
My Pixel XL is now on Dec 2016 7.1.1 (NMF26O). I tried to flash bootloader from NMF26O and NMF26U, it failed, showing:
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (32728 KB)...
OKAY [ 0.735s]
writing 'bootloader'...
FAILED (remote: Verify bootloader image failed on production device.)
finished. total time: 1.338s
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
Code:
>fastboot boot twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
creating boot image...
creating boot image - 9072640 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.653s
Does anyone here know how to fix this without wipe my data? I have super super important data on my phone.
-------edit--------
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
ghovik said:
I waked up this morning and checked time on my Pixel XL, about 30 mins after I checked my phone which has been powered off. I tried to power on, it screens off right after the google logo showed on, and loop.
Then I entered bootloader, it shows:
My Pixel XL is now on Dec 2016 7.1.1 (NMF26O). I tried to flash bootloader from NMF26O and NMF26U, it failed, showing:
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
Does anyone here know how to fix this without wipe my data? I have super super important data on my phone.
Click to expand...
Click to collapse
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
aholeinthewor1d said:
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
Click to expand...
Click to collapse
Yes I can boot into bootloader, 'fastboot devices' shows my device correctly. But any 'fastboot flash' or 'fastboot root' returns failure. for example, I tried to flash boot.img, returns:
Code:
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (26229 KB)...
OKAY [ 0.611s]
writing 'boot'...
(bootloader) Flashing active slot "_b"
FAILED (remote: flash write failure)
finished. total time: 0.866s
@ghovik,
Try putting it on the charger for a while. I'm not saying your battery is dead, but it sure can't hurt.
Thanks. I have charged it for about 30mins. You remind me of another strange thing, when it is powered off and connected to the charger, the charging battery logo shows up for 1 sec and screens off. It loops for few times and the phone starts booting itself. So I put it into bootloader mode now while charging.
ghovik said:
It can't boot into recovery mode. I tried to temporarily boot into twrp-pixel-installer-marlin-3.0.2-0-RC1 it returns:
>fastboot boot twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
creating boot image...
creating boot image - 9072640 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.653s
Click to expand...
Click to collapse
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
^^^ What he said.
Too many links usually means a bad filename or bad path to the file.
muzzy996 said:
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
Click to expand...
Click to collapse
Oh this is my fault. Now I tried 'fastboot flash twrp-3.0.2-0-RC1-fastboot-marlin.img', it worked but, first the google logo shows up and immediately screens off, then root loop as the same as I boot my device.
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
TonikJDK said:
^^^ What he said.
Too many links usually means a bad filename or bad path to the file.
Click to expand...
Click to collapse
muzzy996 said:
When you noted that you were trying to boot to TWRP via commands my first expectation was to see a fastboot command like this instead:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
I'm not sure why you are trying to boot the flashable ZIP instead.
Click to expand...
Click to collapse
cam30era said:
@ghovik,
Try putting it on the charger for a while. I'm not saying your battery is dead, but it sure can't hurt.
Click to expand...
Click to collapse
aholeinthewor1d said:
So you can at least get into bootloader right? Does "fastboot devices" show your serial?
Click to expand...
Click to collapse
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
ghovik said:
I asked a friend who is using Pixel to show me his bootloader info. I noticed his boot-slot is a, mine is b.
Any idea that I can switch the boot-slot back to a? Do you think switching back will work?
Click to expand...
Click to collapse
Fastboot set_active _a
TonikJDK said:
Fastboot set_active _a
Click to expand...
Click to collapse
It seems this is not a correct command because I tried this commend and it returns the usage help.
ghovik said:
It seems this is not a correct command because I tried this commend and it returns the usage help.
Click to expand...
Click to collapse
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
TonikJDK said:
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
Click to expand...
Click to collapse
I think you are right. I googled this command, all the websites said the same command as you told. It might be my fastboot version problem. May I ask what version are you using?
ghovik said:
It seems this is not a correct command because I tried this commend and it returns the usage help.
Click to expand...
Click to collapse
Try updating your ADB and fastboot. From here > https://plus.google.com/+ElliottHughes/posts/U3B6H3Sejvv
ghovik said:
I think you are right. I googled this command, all the websites said the same command as you told. It might be my fastboot version problem. May I ask what version are you using?
Click to expand...
Click to collapse
https://developer.android.com/studio/releases/platform-tools.html
@TonikJDK,
FWIW: the link that I posted above allows one to download just ADB and fastboot directly from Google. Tiny little package.
TonikJDK said:
It's right. You either typed it wrong or have an older version of fastboot, or are using minimal fastboot.
From mine two seconds ago:
C:\Users\xxx\Desktop\SDK Tools\platform-tools>fastboot set_active _a
Setting current slot to 'a'...
OKAY [ 0.089s]
finished. total time: 0.091s
C:\Users\xxx\Desktop\SDK Tools\platform-tools>
Click to expand...
Click to collapse
I've installed Minimal Adb and Fastboot just now. I tried the command it returns:
Code:
>fastboot set_active _a
error: Could not get suffixes.
cam30era said:
@TonikJDK,
FWIW: the link that I posted above allows one to download just ADB and fastboot directly from Google. Tiny little package.
Click to expand...
Click to collapse
My link is the link on the page he directs you to. Saves a click.
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
ghovik said:
I've installed Minimal Adb and Fastboot just now. I tried the command it returns:
Code:
>fastboot set_active _a
error: Could not get suffixes.
Click to expand...
Click to collapse
Dang it, stop using Minimal. It is old...from like March of last year. Our Pixels are different...they have dual partitions, they need the newer fastboot and adb.
TonikJDK said:
My link is the link on the page he directs you to. Saves a click.
Click to expand...
Click to collapse
Cool. Thanks.
---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------
TonikJDK said:
My link is the link on the page he directs you to. Saves a click.
Click to expand...
Click to collapse
Well, all I see is the SDK package (which is a lot smaller than the full Studio). Unless I'm missing something, I don't see any link to just the ADB and fastboot....
I have my Pixel 2 XL currently running on the December update (8.1) and Magisk installed, stock recovery. Downloaded the January OTA file (multiple times, actually) and when I run the command to Sideload the OTA zip in Stock Recovery, I get the following error messages:
Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does not match framework matrix 1.0 Installation aborted.
Click to expand...
Click to collapse
Never seen that before and Google/XDA search came up empty or bad results. I also tried to update my adb/tools using Android Studio, still no dice.
The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.
ilal2ielli said:
The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.
Click to expand...
Click to collapse
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.
WorldOfJohnboy said:
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.
Click to expand...
Click to collapse
Might be able to try restoring images option in Magisk Manager too before installing full image.
I just install the full images each update though, less problems that way.
OK, so I fixed it by going back to stock (December) Boot and DTBO images, then Sideloaded the OTA which worked fine. Worst case, I'll flash the full System without wipe if I have issues. So it looks as if @ilal2ielli was right! Also, credit to THIS post by @sn0warmy for the steps.
Yep, I had the same issue last night and couldn't find anything on Google. Drove me crazy for a good 30 minutes! Then I recalled that you have to be 100% stock to take updates so I flashed stock boot.img and it took the update just fine afterwards. I did not need to flash dtbo.img.
I'm all flashed, but having issues with the Magisk Patched Boot image. Flashed stock back in since it would only boot to recovery or bootloader. I may revert to booting to TWRP and flashing the Magisk that way.
I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?
seckelg said:
I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?
Click to expand...
Click to collapse
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.
WorldOfJohnboy said:
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.
Click to expand...
Click to collapse
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.
seckelg said:
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.
Click to expand...
Click to collapse
Then flash the full image minus the -w from fastboot.
v12xke said:
Then flash the full image minus the -w from fastboot.
Click to expand...
Click to collapse
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...
fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...
Click to expand...
Click to collapse
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.
fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
Click to expand...
Click to collapse
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
ilal2ielli said:
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.
Click to expand...
Click to collapse
v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Thanks guys! I'm sure I critical unlocked it BUT I did mess around with so much stuff since this happened I probably did something I wasn't supposed to I'm gonna redo the crictical unlock and start over...thanks again!
v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance
km00000 said:
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance
Click to expand...
Click to collapse
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.
ilal2ielli said:
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.
Click to expand...
Click to collapse
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?
km00000 said:
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?
Click to expand...
Click to collapse
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.
v12xke said:
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.
Click to expand...
Click to collapse
I was able to force it to go to the adb I downloaded and got it installed. I actually just changed the flash-all.bat script to use the correct adb version by point it to the freshly downloaded platform-tools. I'm not sure where this old ADB is located. It's not in my PATH when I look at environment variables. I don't have any other ADB or platform-tools downloaded, that I know off.
Anyway I got it to work and I'll just make sure to point it to the correct platform-tools whenever I flash something in the future. Can't believe I've been on the developer preview 2 since like November.
So while flashing an update, my Pixel 3XL turned off and now it only loads in fastboot (every other options goes to black screen). On the fastboot screen I get "Device state: error!" not locked or unlocked. When trying flash-all.bat, here's the read out. When I exit, nothing has changed. I can still only turn on the phone in fastboot and no other options. If anyone has any ideas, I would greatly appreciate it!
Sending 'bootloader_b' (8489 KB) OKAY [ 0.399s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.746s
rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.052s
< waiting for any device >
Sending 'radio_b' (71148 KB) OKAY [ 2.501s]
Writing 'radio_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 11.845s
rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
Checking product OKAY [ 0.060s]
Checking version-bootloader OKAY [ 0.058s]
Checking version-baseband OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.735s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.075s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 3.284s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2158 MB) to disk... took 27.091s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 5.520s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.421s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_b' (65536 KB) OKAY [ 2.338s]
Writing 'boot_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 76.748s
Press any key to exit...
Do you have the current platform tools? Also, use a C>A USB cable and not a C>C.
Yup, using a C to A cable. Downloaded the tools today so I'm pretty sure it's more of the device state error! problem and the error of no response error during flash.
sal-paradise said:
Yup, using a C to A cable. Downloaded the rooms today so I'm pretty sure it's more of the device state error! problem and the error of no response error during flash.
Click to expand...
Click to collapse
The exact
same thing happened to me. I had to sideload and install the ota. zip and all is good again.
sal-paradise said:
Yup, using a C to A cable. Downloaded the rooms today so I'm pretty sure it's more of the device state error! problem and the error of no response error during flash.
Click to expand...
Click to collapse
No answer about the platform tools, but had you updated the phone before this way? If not, different computer, cable, port, etc. The platform tools haven't changed since a few months before nd of last year, so if you had done this before that part should be safe...
Did you confirm the file download and make sure that it was not corrupted when you unzipped the D/L? Otherwise, the above post about using the OTA through recovery is a good option.
P.S. It helps if you quote the person trying to help so that they know there is an answer.
Patch7 said:
The exact
same thing happened to me. I had to sideload and install the ota. zip and all is good again.
Click to expand...
Click to collapse
How do I sideload the ota if I can't get into recovery? All the menu option through the volume rocker in fastboot leads to the device turning off.
Every now and then I have to swap ports on my computer because I'll get weird errors, not sure if I've seen this one specifically though. Swap ports, swap cables, mix and match until it works or you go through every option you've got.
Speak gentle words of encouragement too.
Seamonkey79 said:
Every now and then I have to swap ports on my computer because I'll get weird errors, not sure if I've seen this one specifically though. Swap ports, swap cables, mix and match until it works or you go through every option you've got.
Speak gentle words of encouragement too.
Click to expand...
Click to collapse
Unfortunately this is a bigger problem than just cables, ports, and gentle words
sal-paradise said:
How do I sideload the ota if I can't get into recovery? All the menu option through the volume rocker in fastboot leads to the device turning off.
Click to expand...
Click to collapse
You can't.
sliding_billy said:
No answer about the platform tools, but had you updated the phone before this way? If not, different computer, cable, port, etc. The platform tools haven't changed since a few months before nd of last year, so if you had done this before that part should be safe...
Did you confirm the file download and make sure that it was not corrupted when you unzipped the D/L? Otherwise, the above post about using the OTA through recovery is a good option.
P.S. It helps if you quote the person trying to help so that they know there is an answer.
Click to expand...
Click to collapse
Right, but that's not an option because all options beyond fastboot lead to a black screen.
Homeboy76 said:
You can't.
Click to expand...
Click to collapse
Exactly.
sal-paradise said:
Exactly.
Click to expand...
Click to collapse
Try this:
On your Computer:
- Open a Command Prompt in the Platform-tools folder
- Make sure these files are in the Platform-tools folder:
bootloader-crosshatch-b1c1-0.1-5191736.img
radio-crosshatch-g845-00009-181130-b-5157073.im
image-crosshatch-pq2a.190305.002.zip
- Boot the phone to fastboot mode
- Connect the phone to the computer with the A to C USB cable
The type these commands (one at a time) at the Command Prompt and press enter after each command:
fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5191736.img
fastboot reboot-bootloader
fastboot flash radio radio-crosshatch-g845-00009-181130-b-5157073.img
fastboot reboot-bootloader
fastboot update image-crosshatch-pq2a.190305.002.zip
sal-paradise said:
Right, but that's not an option because all options beyond fastboot lead to a black screen.
Click to expand...
Click to collapse
Have you tried the flash-all besides since the initial try? If not, I would definitely retry. Perhaps try changing slots from fastboot and see if you can boot to system or recovery (for OTA or factory reset) or run the flash-all from the other slot.
fastboot --set-active=a
---------- Post added at 03:09 PM ---------- Previous post was at 02:57 PM ----------
sliding_billy said:
Have you tried the flash-all besides since the initial try? If not, I would definitely retry. Perhaps try changing slots from fastboot and see if you can boot to system or recovery (for OTA or factory reset) or run the flash-all from the other slot.
fastboot --set-active=a
Click to expand...
Click to collapse
If that doesn't work, you should be able to change slots with the fastboot boot [twrp].img version of TWRP (run from fastboot) and then reboot to system.
sliding_billy said:
Have you tried the flash-all besides since the initial try? If not, I would definitely retry. Perhaps try changing slots from fastboot and see if you can boot to system or recovery (for OTA or factory reset) or run the flash-all from the other slot.
fastboot --set-active=a
---------- Post added at 03:09 PM ---------- Previous post was at 02:57 PM ----------
If that doesn't work, you should be able to change slots with the fastboot boot [twrp].img version of TWRP (run from fastboot) and then reboot to system.
Click to expand...
Click to collapse
When I try this, here's what I get:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.219s
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002>
And yes, everytime I try flash-all I get the same at my original post with the same error:
FAILED (remote: 'error getting device locked state No Response')
Homeboy76 said:
Try this:
On your Computer:
- Open a Command Prompt in the Platform-tools folder
- Make sure these files are in the Platform-tools folder:
bootloader-crosshatch-b1c1-0.1-5191736.img
radio-crosshatch-g845-00009-181130-b-5157073.im
image-crosshatch-pq2a.190305.002.zip
- Boot the phone to fastboot mode
- Connect the phone to the computer with the A to C USB cable
The type these commands (one at a time) at the Command Prompt and press enter after each command:
fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5191736.img
fastboot reboot-bootloader
fastboot flash radio radio-crosshatch-g845-00009-181130-b-5157073.img
fastboot reboot-bootloader
fastboot update image-crosshatch-pq2a.190305.002.zip
Click to expand...
Click to collapse
I have an older bootloader version, so when I try this, it tells me:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot update image-crosshatch-pq2a.190305.002.zip
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 85HY008F7
--------------------------------------------
Checking product OKAY [ 0.062s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-5034669'.
Update requires 'b1c1-0.1-5191736'.
fastboot: error: requirements not met!
sal-paradise said:
I have an older bootloader version, so when I try this, it tells me:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot update image-crosshatch-pq2a.190305.002.zip
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 85HY008F7
--------------------------------------------
Checking product OKAY [ 0.062s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-5034669'.
Update requires 'b1c1-0.1-5191736'.
fastboot: error: requirements not met!
Click to expand...
Click to collapse
¯\_(ツ)_/¯
sal-paradise said:
When I try this, here's what I get:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.219s
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002>
And yes, everytime I try flash-all I get the same at my original post with the same error:
FAILED (remote: 'error getting device locked state No Response')
Click to expand...
Click to collapse
Sorry, but I just got back online (been one of those nights). Looking at all the back and forth, I feel like there is a communication gap between you and those of us helping. There are questions and suggestions unanswered. For one, I never saw a reply to if this is the first time you are attempting to update via a flash-all on the same computer/port/cable/etc. That will answer a bit about your knowledge and the hardware functionality. If all that is a go, the only thing that jumps out at me is the possibility of a bad download or something easy to remedy like a command problem or file location/path issue. Have you checked with Google? I know that getting a replacement sucks, but you may need to start over. The folks here have done this tons of times and got back from bricks probably more severe than yours. I have never seen a device that could get to fastboot not be recoverable if all of the things we are talking about are being executed properly, but there is always a first like a serious phone hardware failure that nothing is going to solve except for a replacement.
One thing I see is the PS location. I know there are some commands that don't play nice in PowerShell, so type 'cmd' from PS and get to a standard command prompt.
sal-paradise said:
How do I sideload the ota if I can't get into recovery? All the menu option through the volume rocker in fastboot leads to the device turning off.
Click to expand...
Click to collapse
I had the exact thing happened to me on my Pixel 2 XL but nothing worked,
not even the "Duce Script". I decided to use the "Skip Soft" tool as my last resort
and to my surprise it worked and fixed it in less than 10 minutes!
Unfortunately the Dev hasn't added the Crosshatch yet. I suggest you download it
and ask him to add it in the "Device Support" section, he''ll add it once he sees more requests.
Good luck.
sliding_billy said:
Sorry, but I just got back online (been one of those nights). Looking at all the back and forth, I feel like there is a communication gap between you and those of us helping. There are questions and suggestions unanswered. For one, I never saw a reply to if this is the first time you are attempting to update via a flash-all on the same computer/port/cable/etc. That will answer a bit about your knowledge and the hardware functionality. If all that is a go, the only thing that jumps out at me is the possibility of a bad download or something easy to remedy like a command problem or file location/path issue. Have you checked with Google? I know that getting a replacement sucks, but you may need to start over. The folks here have done this tons of times and got back from bricks probably more severe than yours. I have never seen a device that could get to fastboot not be recoverable if all of the things we are talking about are being executed properly, but there is always a first like a serious phone hardware failure that nothing is going to solve except for a replacement.
One thing I see is the PS location. I know there are some commands that don't play nice in PowerShell, so type 'cmd' from PS and get to a standard command prompt.
Click to expand...
Click to collapse
My apologies, I thought a previous comment mentioning computer/port/cables that I responded to clarified this. This is not the issue as I've done it with multiple desktops and multiple USB A to C cables. Even when attempting to change from slot B to A I get the device state error, which I've copied in another post on here. Isn't that the problem here? If I can't figure out a way to get around the fact that there's no response when trying to determine the lock state, I don't think we can fix the problem here. I don't see how this would have to do with being in powershell or not or being a bad download. Since most things fail in fastboot because of this error, this is what I was trying to get more info on to get corrected as it clearly seems to be the heart of the failure.
Unfortunately a lot of the back and forth is because of the repetition about cables and ports or asking me to recover which I appreciate, but I stated choosing recovery sends me to a black screen. When there's been actual commands to try in fastboot, I've posted the results they've given, but it still comes back to " FAILED (remote: 'error getting device locked state No Response') "
sal-paradise said:
My apologies, I thought a previous comment mentioning computer/port/cables that I responded to clarified this. This is not the issue as I've done it with multiple desktops and multiple USB A to C cables. Even when attempting to change from slot B to A I get the device state error, which I've copied in another post on here. Isn't that the problem here? If I can't figure out a way to get around the fact that there's no response when trying to determine the lock state, I don't think we can fix the problem here. I don't see how this would have to do with being in powershell or not or being a bad download. Since most things fail in fastboot because of this error, this is what I was trying to get more info on to get corrected as it clearly seems to be the heart of the failure.
Unfortunately a lot of the back and forth is because of the repetition about cables and ports or asking me to recover which I appreciate, but I stated choosing recovery sends me to a black screen. When there's been actual commands to try in fastboot, I've posted the results they've given, but it still comes back to " FAILED (remote: 'error getting device locked state No Response') "
Click to expand...
Click to collapse
I appreciate the reply. Some of the things are just things that take no real effort (like downloading/extracting the factory image again to be safe), while the PS thing was just to make sure that if folks are sending commands to try that they are sending the right ones. The question about whether you were using a Mac or Linix (that I think has been deleted since I read it) got me thinking about that and not that running the flash-all batch would react differently.
Last thing, have you tried anything with the TWRP .img version like changing slots or even doing a factory reset?
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Thank you very much. I will try it.
BL1ND4D0 said:
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Click to expand...
Click to collapse
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
[email protected] said:
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
tys0n said:
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
Click to expand...
Click to collapse
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
[email protected] said:
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
Click to expand...
Click to collapse
Did you follow all instructions from twrp thread. like flashing modified vbmeta and wipe data before booting twrp?
Also take a look at the original thread for one vision as it has a newer zip that contains only one modified vbmeta.img instead of two different ones in the older zip that is posted in one action's twrp thread.
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
goofball2k said:
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
Click to expand...
Click to collapse
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
[email protected] said:
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
Click to expand...
Click to collapse
You don't need to modify vbmeta.img. I am using the older version of the root Moto Vision package, which has a vbmeta.img file, and a patched vbmeta.img file.
For the modified boot img, I downloaded the full image from https://mirrors.lolinet.com/firmware/moto/troika/official/
Extract, and then take the boot.img file, you will want that saved to a phone that has Magisk installed.
Follow these instructions to patch
https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Once you have that, you will want that patched file into the fastboot directory on your computer. You will also want the vbmeta and the patched vbmeta img files (from the root moto vision package) in this directory. I have not used the updated version, I am using the older. I don't know about using the newer package which only has 1 vbmeta file.
Put your phone into fastboot mode.
Flash the vbmeta.img file, then the magisk patched boot file, then the vbmeta patched file. Then do a fastboot wipe of the phone.
Reboot the phone.
Set it up again, install magisk manager, then open it, and it should ask to configure. Let it do that, it should reboot and after that, you should be rooted.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Thank you
binary**# said:
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Click to expand...
Click to collapse
Thank you very much for your input.
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Polnareff said:
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Click to expand...
Click to collapse
You aren't flashing, your command is trying to boot from vbmeta.img. You are missing the flashing command.