Related
Hallo. I have a trouble with my new Moto G XT1032 Falcon. I bought one in Germany with Android 4.4.2 and no German language on-board. So, I tried to flash this ROM:
Retail Germany – XT1032_FALCON_RETDE_5.1_LPB23.13-56_cid7
c:\XT1032_FALCON_RETDE_5.1_LPB23.13-56_cid7_CFC>fastboot.exe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.068s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.366s]
finished. total time: 0.439s
c:\XT1032_FALCON_RETDE_5.1_LPB23.13-56_cid7_CFC>fastboot.exe flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.160s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.114s]
finished. total time: 1.277s
c:\XT1032_FALCON_RETDE_5.1_LPB23.13-56_cid7_CFC>fastboot.exe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.109s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.208s
At the next step failed the procedure:
c:\XT1032_FALCON_RETDE_5.1_LPB23.13-56_cid7_CFC>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.452s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.917s
Now I can not flash any other parts from this this firmware an also no one part from some others (I have already tried). I Also tried to unlock the bootloader. No successes:
c:\XT1032_FALCON_RETDE_5.1_LPB23.13-56_cid7_CFC>fastboot oem get_unlock_data
...
(bootloader) 3A95030745372821#54413932393048
(bootloader) 38323100585431303332000000#7369
(bootloader) 128F9495879D6C5F7AED0E1EF56C707
(bootloader) 4C9E6#B778C6020F000008000000000
(bootloader) 0000000
OKAY [ 0.163s]
finished. total time: 0.165s
I got:
“Your device does not qualify for bootloader unlocking.”
on the motorola-webpage (with this code:
3A95030745372821#5441393239304838323100585431303332000000#7369128F9495879D6C5F7AED0E1EF56C7074C9E6#B778C6020F0000080000000000000000).
“Factory reset” and “Recovery” from bootloader-menu are already done. No changes: the device stuck at bootloader.
Please, help me to de-brick it.
Sorry, no Idea? I'll be glad of any help.
Thank you in advance.
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader:
Code:
sending 'bootloader_a' (38728 KB)...
OKAY [ 2.095s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 2.099s
This happened both trying to flash the original .010 factory image and the .018 November update (haven't tried .025 yet). I had problems getting .010 to work (I was trying to downgrade, long story, it seemed to get stuck at the G logo, I gave up). But .018 worked fine, even with the flash of the bootloader failing. In fact, the bootloader version is the same as in .010, the September factory image, so I guess for .018 it just did not matter that the bootloader did not flash.
But anyway, I'm worried about this "Command Flash Error." What does it mean? If a new bootloader really can't be flashed on my device that seems like a problem.
I saw a mention of this problem in these two places: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ (in the comments) and https://www.reddit.com/r/AndroidPre...one_unlock_the_pixel_2_bootloader_without_an/. But there's no real explanation or solution.
[Edit: Just tried flashing just the bootloader manually, from the .018 and .025 factory images, and it failed in the same way. It's the identical bootloader in both images so it's not surprising. So, indeed, the bootloader cannot be flashed on my device. Or at least the one that comes in .010, .018, and .025 cannnot: bootloader-walleye-mw8998-002.0059.00.img.]
[Edit, 12/7/17: The December update solves this problem. If you sideload the December OTA image, using adb, it updates the bootloader. After that it is possible to flash a bootloader image directly using fastboot as expected. So something was just wrong with the original bootloader on this device or how it was installed. The only situation in which this solution will not work, I think, is if you have a custom recovery, i.e. TWRP. I think then you cannot sideload an OTA image. You would need, I believe, to restore the stock recovery first, by flashing the stock boot.img that goes with you current version of Android.]
@CB74 hi, did you find a way to solve this ?
Bumping this thread as I'm in the same boat: "Command Flash Error" when flashing any bootloader.
Really annoyed with Google rn, because now that I recovered my phone to a previous factory image, I am now getting FC's on Pixel Setup and cannot even set up my phone again.
I never found a solution. But I just saw this thread where someone says he found a way to fix it: https://forum.xda-developers.com/showpost.php?p=74728097&postcount=8
It does require locking the device and unlocking the bootloader again, which of course wipes it. I am hesitant to do that. I do wonder from what's said in that thread if there is just something weird about the original bootloader that came with the device and that once the person in that thread got a a new version of the bootloader by signing up for the developer preview of Android that solved the problem. If that's the case then it would seem that sideloading the December OTA update might accomplish the same thing, without locking and unlocking the bootloader. I think the December OTA ought to also update the bootloader. I haven't tried this yet though. Just don't have time to mess with updates right now.
I did find with the November update that the OTA worked fine, even though the factory image would not flash the bootloader.
Can confirm sideloading the OTA according to Googles instructions on the download page also updates the bootloader.
kendong2 said:
Can confirm sideloading the OTA according to Googles instructions on the download page also updates the bootloader.
Click to expand...
Click to collapse
I managed to update to 8.1.0 through a bit of a Frankenstein method.... but not without a ton of stress. I tried side-loading the OTA, which updated the bootloader, but then something failed later about 95% of the way in.
Apparently, the phone switched itself to the B system partition, and I was able to the 8.1.0 factory image without a problem. 8.1.0 boots and everything works fine, but I am getting a warning message to contact the manufacturer when booting up.
I think there is an issue with the bootloader slot in my A system partition, because I had some other random errors when unlocking etc. Hopefully Google will send me a new replacement phone because this one has been a headache.
I posted the solution here...
https://www.reddit.com/r/GooglePixel/comments/7ht2tr/failed_remote_failed_to_loadauthenticate_boot/
I had this issue when trying to flash 8.1 Factory Image over 8.0.
I fixed it by flashing back stock boot.img and then ADB sideloading 8.1 OTA update.
Bootloader/8.1 updated successfully.
peikojose said:
I posted the solution here...
https://www.reddit.com/r/GooglePixel/comments/7ht2tr/failed_remote_failed_to_loadauthenticate_boot/
Click to expand...
Click to collapse
The problem in your thread at reddit seems to have to do with flashing the boot.img, which is not the same issue here. This thread is about problems flashing the bootloader. The boot.img and the bootloader image are not the same thing.
Okay, so I did my own experiment and I was right. I sideloaded the December OTA image. That updated the bootloader, as others have reported. After that whatever the problem was with flashing the bootloader from a factory image went away. I extracted the bootloader image from the December factory image zip, rebooted into the bootloader, and flashed the bootloader .img file using fastboot without a problem. So I assume going forward it should be possible to flash factory images, rather than sideoading OTA images, without issues regarding the bootloader.
Seems like sideloading the December OTA is the only solution here.
** So this is how I fixed my issue.
I used Deuces v4 script to flash all 8.1, after it was done was stuck in bootloader and wouldnt reboot out.
So then I used Google's flash-all.bat, then at the end I got a error missing boot.img, check folder and it was there.
So I re-used Deuces v4 script and flashed it again.
This time after it was done I was in 8.1 and all good.
Hope this helps!
I started that reddit thread. I'd try to sideload the OTA but I can't even get into recovery. It just goes right back to the bootloader.
---------- Post added at 09:52 AM ---------- Previous post was at 08:56 AM ----------
razrlover said:
** So this is how I fixed my issue.
I used Deuces v4 script to flash all 8.1, after it was done was stuck in bootloader and wouldnt reboot out.
So then I used Google's flash-all.bat, then at the end I got a error missing boot.img, check folder and it was there.
So I re-used Deuces v4 script and flashed it again.
This time after it was done I was in 8.1 and all good.
Hope this helps!
Click to expand...
Click to collapse
This worked! Thanks! I was able to get it to erase through recovery and it booted!
I received my Pixel2 (not XL! Europe free version) today. It came with Android 8.0 (November). I tried to flash 8.1 factory image (walleye-opm1.171019.011-factory-f74dd4fd.zip) via fastboot. But same "Command Flash Error" here while update bootloader. My bootloader version was 0059. The update requires 0066. (See Code 1).
The "Deuces v4 script" DIDN'T help me. It installed 8.1 on system-partition without update bootloader and some other partitions. uuh. I was scared of it for a moment, but the device starts Android 8.1 but bootloader stay at 0059.
My solution
- i added my google account to the phone
- i registered my pixel 2 for beta program via android.com/beta (with computer)
- i checked systemupdates, downloaded & installed 8.1 beta (round about 1.1GB)
- phone reboots and stucked 30 minutes at the G-logo
- i pressed power and volume-down till it reboots into bootloader
- i saw, that now the bootloader is version 0066!
- now i could run flash-all.sh without problems (i started the flash-all.sh commands manually, see Code 2)
- i was in Slot B, i switched to Slot A with: fastboot --set-active=_a; adb reboot-bootloader
- i saw, the Slot A bootloader was the old version 0059, i tried to flash it, without success, same error
- i switched to Slot B again and flashed the A bootloader: fastboot flash bootloader_a bootloader-walleye-mw8998-002.0066.00.img (see Code 3).
- now both bootloader are version 0066
I hope it will help you.
Code 1:
Code:
# fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 1.594s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.598s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
# fastboot flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 2.420s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 2.964s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
# fastboot -w update image-walleye-opm1.171019.011.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: xxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.004s
Code 2:
Code:
# fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.768s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.889s]
finished. total time: 2.658s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
# fastboot flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 2.727s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.545s]
finished. total time: 3.272s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.101s
# fastboot -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.202s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.033s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 11.869s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 4.173s
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 (347 MB) to disk... took 2.423s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: 9c0d344d-4d88-428e-99a4-ccef9c9cf298
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: xxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 1.495s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.679s]
writing 'dtbo_b'...
OKAY [ 0.000s]
erasing 'system_b'...
OKAY [ 0.396s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 22.653s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 26.109s]
writing 'system_b' 2/4...
OKAY [ 0.000s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 25.569s]
writing 'system_b' 3/4...
OKAY [ 0.000s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 20.279s]
writing 'system_b' 4/4...
OKAY [ 0.000s]
erasing 'system_a'...
OKAY [ 1.999s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 23.680s]
writing 'system_a' 1/2...
OKAY [ 0.000s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 5.069s]
writing 'system_a' 2/2...
OKAY [ 0.000s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.269s]
writing 'vbmeta_b'...
OKAY [ 0.000s]
erasing 'vendor_b'...
OKAY [ 0.141s]
sending 'vendor_b' (355428 KB)...
OKAY [ 16.130s]
writing 'vendor_b'...
OKAY [ 0.000s]
Setting current slot to 'b'...
OKAY [ 1.682s]
erasing 'userdata'...
OKAY [ 0.942s]
sending 'userdata' (4669 KB)...
OKAY [ 0.224s]
writing 'userdata'...
OKAY [ 0.000s]
rebooting...
finished. total time: 147.489s
Code 3:
Code:
# fastboot --set-active=_a
Setting current slot to 'a'...
OKAY [ 0.016s]
finished. total time: 0.016s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.251s
# fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 1.812s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.724s
# fastboot flash bootloader_a bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.733s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.737s
# fastboot --set-active=_b
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.015s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.051s
# fastboot flash bootloader_a bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.735s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.890s]
finished. total time: 2.625s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
depii said:
I received my Pixel2 (not XL! Europe free version) today. It came with Android 8.0 (November). I tried to flash 8.1 factory image (walleye-opm1.171019.011-factory-f74dd4fd.zip) via fastboot. But same "Command Flash Error" here while update bootloader. My bootloader version was 0059. The update requires 0066. (See Code 1).
The "Deuces v4 script" DIDN'T help me. It installed 8.1 on system-partition without update bootloader and some other partitions. uuh. I was scared of it for a moment, but the device starts Android 8.1 but bootloader stay at 0059.
My solution...
Click to expand...
Click to collapse
You really made that hard on yourself.
If you had read the whole thread you would have seen that simply sideloading the December OTA image, with adb, updates the bootloader and solves the problem. After that you can flash the bootloader with fastboot successfully (though it's unnecessary for now, since it has already been updated--but in the future should hopefully mean there will be no more problems flashing bootloaders).
I have the same problem.
But I solved it.
This is a bug,it already fixed in 2017/12 OTA File.
use adb sideload otafile.zip
or
check system update
Bug will fix after update.
Bootloader version is mw8998-002.0066.00 .
good luck.
cb474 said:
If you had read the whole thread you would have seen that simply sideloading the December OTA image, with adb, updates the bootloader and solves the problem.
Click to expand...
Click to collapse
cb474 said:
The only situation in which this solution will not work, I think, is if you have a custom recovery, i.e. TWRP.
Click to expand...
Click to collapse
Hm okay. Sideload didn't work for me. How can i sideload the ZIP to a stock system without TWRP?
In bootloader:
# adb sideload test.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
In "download mode" the phone display says: "ERROR: Operation Denied"
In "recovery mode" the phone display says: "No command"
depii said:
Hm okay. Sideload didn't work for me. How can i sideload the ZIP to a stock system without TWRP?
In bootloader:
# adb sideload test.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
In "download mode" the phone display says: "ERROR: Operation Denied"
In "recovery mode" the phone display says: "No command"
Click to expand...
Click to collapse
The steps are right on Googles OTA images page. Need to hold power button and press volume up when in recovery. Then a list of options will appear, one being Apply update from ADB.
Ra6idr0y said:
The steps are right on Googles OTA images page. Need to hold power button and press volume up when in recovery. Then a list of options will appear, one being Apply update from ADB.
Click to expand...
Click to collapse
EDIT: aaah i found my error I had overlooked that I have to press Power and Vol-Up, when i see the red exclamation mark (with "No command"). Thanks!
1) adb reboot recovery
2) The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
3) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
depii said:
EDIT: aaah i found my error I had overlooked that I have to press Power and Vol-Up, when i see the red exclamation mark (with "No command"). Thanks!
1) adb reboot recovery
2) The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
3) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Click to expand...
Click to collapse
Yeah, the stock recovery is a little confusing. You get to the image of the Android lying on its back with the red exclamation mark and no menus and you think: OMG what happened?! Did I brick my device?
I don't know why it doesn't just boot to the menu, rather than hiding it behind a secret set of key presses. I guess that's to keep people who don't know what they are doing from messing things up? But then, wouldn't such people never boot to the recovery anyway? You already have to have gone out of your way to figure that out, so hiding the menu at that point seems a bit silly.
i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated
xsanikax said:
i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated
Click to expand...
Click to collapse
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.
Diesel_Jeremiah said:
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.
Click to expand...
Click to collapse
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s
xsanikax said:
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.
Diesel_Jeremiah said:
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.
Click to expand...
Click to collapse
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them
xsanikax said:
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them
Click to expand...
Click to collapse
You probably have already done it, but ensure you have the newest ADB, that's what screwed me up.
I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html
iamnotreallyhere said:
I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
thanks a lot dude this is what im getting at the minute
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.818s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.825s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.270s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.815s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: FA7AK1A08325
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.009s
Press any key to exit...
however i have found a problem when i tried just reflashing the recovery by itself
C:\Unified_Android_Toolkit\recovery\GooglePixel2>fastboot flash recovery recovery-twrp-3.2.1.0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
OKAY [ 0.689s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.691s
seems my partitions are all jacked up, is there a way to sort that out?
oh as a side note my problems are all the same as yours i can only access the bootloader and adb will not recognize my device but fastboot will
this is what happens if i try to flash the version with the same bootloader as the one that it says is on the device
target reported max download size of 536870912 bytes
sending 'bootloader' (38728 KB)...
OKAY [ 0.815s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.821s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.271s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.816s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA7AK1A08325
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (32768 KB)...
OKAY [ 0.690s]
writing 'boot'...
OKAY [ 0.300s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.668s]
writing 'system'...
OKAY [ 4.745s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.632s]
writing 'system'...
OKAY [ 4.755s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.597s]
writing 'system'...
OKAY [ 4.732s]
sending sparse 'system' (322348 KB)...
OKAY [ 7.126s]
writing 'system'...
OKAY [ 2.915s]
sending 'vendor' (346992 KB)...
OKAY [ 7.342s]
writing 'vendor'...
OKAY [ 3.169s]
erasing 'userdata'...
OKAY [ 0.736s]
sending 'userdata' (140906 KB)...
OKAY [ 2.954s]
writing 'userdata'...
OKAY [ 1.502s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 75.881s
Press any key to exit...
It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.134s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.020s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
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 (347 MB) to disk... took 1.721s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip
iamnotreallyhere said:
It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.134s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.020s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
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 (347 MB) to disk... took 1.721s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip
Click to expand...
Click to collapse
im doing exactly what i'm being told to but i'm still getting the same remote command flash error and the boot slot is set to a it won't let me change it to b
okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input
Nice! Now that I think of it I did try flashing Oreo 8.0 before I tried flashing 8.1. 8.0 didn't work by itself tho. So then I flashed 8.1. Maybe that's the trick to fix the partitions.
Thanks a lot
xsanikax said:
okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input
Click to expand...
Click to collapse
Thank you for the idea of using an older version of fastboot. I somehow screwed up my Pixel 2 and loaded bootloader 59 on it and couldn't update it back to 66. I had the right image but was still using the newest version of fastboot. Ended up with 26.0.2 which was the first version with Pixel 2 support. It can be found here: https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
Thanks again! :good:
Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...
jzablocki15 said:
Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...
Click to expand...
Click to collapse
My dude, you would not believe the hell I went through to figure this out. So it started with me getting the Verizon Pixel 2's bootloader unlocked. I downloaded TWRP onto it, rooted it, and then downloaded a ZIP that would add various modifications to my version of android. Well, I downloaded it, flashed it , and of course it didn't work as intended. Tried finding a way to undo what I'd done (absolutely imbecilic me, I didn't back up my phone WHEN THERE WAS NO SYSTEM IMAGE FOR A VERIZON PHONE YET). I figured the Google images would work fine, but they put you through hell and highwater before they do. I attempted to revert to the current stock image. It screwed my whole system up. Couldn't boot into android, couldn't boot into ANY recovery, etc. It was essentially bricked. I went through countless different errors and threads and forums and files, until I found this one right here. Tried reverting to the old version of Oreo with old ADB and fastboot. Progress, no more error popping up. Then I tried booting up and it stayed in fastboot. Tried then updating to the latest version available from Google as you had and got the exact same line of code. With the OLD ADB AND FASTBOOT and with a file I had downloaded and tinkered with earlier and with the LATEST IMAGE FROM GOOGLE (after your step), I tried it, came up with several "faileds" and other errors, but after the script was done, I rebooted and it got to the boot animation (as it had done before) and FINALLY brought my phone to the setup wizard.
The file I used was this one: https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778
Recap:
Download old ADB and Fastboot
Download the latest Android 8.0 Oreo Stock Image
Flash all bat
Download latest Android 8.1 Oreo Stock Image
From there, put the downloaded script in with the image file of the latest available Android 8.1 Oreo Stock Image and run the script.
Should show errors
Reboot once it's finished
Should be fine.
Keep in mind, this was a Verizon Pixel 2 and it worked fine for me. Couldn't guarantee it'd work for you, and there may have even been precursor steps before this post that I took and didn't keep track of that might have contributed to an extremely lucky brick save.
Long story short folks, if you're on an unlocked bootloader Verizon, don't do anything you can't live with for a while until we've got a proper backdoor developed for us.
Read my message right above your original post. Get the image for oreo 8.0 (nov) and use the fastboot version fron the site I linked to. Should have the 59 bootloader. After it boots, just do the OTA update twice. Check the build number and then get that image from Google to root the boot.img file. All good.
Yupp, just used the tool and saved a couple hundred bucks and a pair of underwear. Really is phone saver. And I'm for sure going to wait until a less risky root is available. I was able to flash the tool with factory image 66 version bootloader, just make sure to have tool in the same folder as the unzipped bootloader and files.
I haven't posted in at least 2 years. Wanted to thank everyone in this thread for the detailed troubleshooting. I locked my bootloader without doing the prep work and this saved me from a fiasco the week before my vacation.
I just found this. I haven't tried it yet.
https://developer.android.com/preview/download.html
same here
don't want to lose root, twrp and xposed.
i'm fine not having xposed but i need root and twrp
TheUndertaker21 said:
same here
don't want to lose root, twrp and xposed.
i'm fine not having xposed but i need root and twrp
Click to expand...
Click to collapse
I'm guessing twrp won't work. But topjohnwu supposedly has rooted it.
jd1639 said:
I'm guessing twrp won't work. But topjohnwu supposedly has rooted it.
Click to expand...
Click to collapse
Have you read this: Android Q - Magisk
any idea?
Code:
sudo ./flash-all.sh
< waiting for any device >
Sending 'bootloader_b' (8501 KB) OKAY [ 0.170s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b1c1-0.2-5260815
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
(bootloader) Flashing partition logfs
OKAY [ 0.200s]
Finished. Total time: 0.610s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 1.701s
Sending 'radio_b' (71164 KB) OKAY [ 0.740s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g845-00017-190123-B-5251681
(bootloader) Flashing partition modem_b
OKAY [ 0.414s]
Finished. Total time: 1.352s
Rebooting into bootloader OKAY [ 0.054s]
Finished. Total time: 1.657s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5260815
Baseband Version.....: g845-00017-190123-B-5251681
Serial Number........: 89HY07A6G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.060s]
Checking 'version-bootloader' OKAY [ 0.060s]
Checking 'version-baseband' OKAY [ 0.060s]
Setting current slot to 'b' OKAY [ 0.076s]
extracting boot.img (64 MB) to disk... took 0.280s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.680s]
Writing 'boot_b' OKAY [ 0.320s]
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.170s]
Writing 'dtbo_b' OKAY [ 0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.063s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.060s]
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Homeboy76 said:
Have you read this: Android Q - Magisk
Click to expand...
Click to collapse
You should read this!
Sieh dir den Tweet von @topjohnwu an: https://twitter.com/topjohnwu/status/1105968107011665920?s=09
Gesendet von meinem Pixel 3 XL mit Tapatalk
b0uNz said:
You should read this!
Sieh dir den Tweet von @topjohnwu an: https://twitter.com/topjohnwu/status/1105968107011665920?s=09
Gesendet von meinem Pixel 3 XL mit Tapatalk
Click to expand...
Click to collapse
I couldn't, no Twitter account. Thanks for the link.
Well, that changes my outlook on Android Q.
y2kbugleung said:
any idea?
Code:
sudo ./flash-all.sh
< waiting for any device >
Sending 'bootloader_b' (8501 KB) OKAY [ 0.170s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b1c1-0.2-5260815
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
(bootloader) Flashing partition logfs
OKAY [ 0.200s]
Finished. Total time: 0.610s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 1.701s
Sending 'radio_b' (71164 KB) OKAY [ 0.740s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g845-00017-190123-B-5251681
(bootloader) Flashing partition modem_b
OKAY [ 0.414s]
Finished. Total time: 1.352s
Rebooting into bootloader OKAY [ 0.054s]
Finished. Total time: 1.657s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5260815
Baseband Version.....: g845-00017-190123-B-5251681
Serial Number........: 89HY07A6G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.060s]
Checking 'version-bootloader' OKAY [ 0.060s]
Checking 'version-baseband' OKAY [ 0.060s]
Setting current slot to 'b' OKAY [ 0.076s]
extracting boot.img (64 MB) to disk... took 0.280s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.680s]
Writing 'boot_b' OKAY [ 0.320s]
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.170s]
Writing 'dtbo_b' OKAY [ 0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.063s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.060s]
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
I have got it fixed.
Thanks.
Are you serious? Couldnt you tell how you fixed it???
i have the same damn issue ple halp
y2kbugleung said:
I have got it fixed.
Thanks.
Click to expand...
Click to collapse
Are you serious? Couldnt you tell how you fixed it???
i have the same damn issue ple halp
Click to expand...
Click to collapse
Classic DenverCoder9!
I ran into the same issue and had the same response as you. But then I reran the script a second time, without moving anything and the setup was successful. So if you didn't, give it a second try before giving up.
y2kbugleung said:
I have got it fixed.
Thanks.
Click to expand...
Click to collapse
how did zou get fixed?
Stelsinki said:
how did zou get fixed?
Click to expand...
Click to collapse
Sorry too long time ago. I forget.
Try using latest ADB and Fastboot:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Make sure the driver on computer is update.
i m able to send some flashing command but when i try to boot in fastbood with command fastboot reboot fastboot i get the error message. i dont think the problem is drivers
Yesterday I was trying to install CalyxOs on my Pixel4a. I followed the instructions on the website and then got stuck when the screen switched to fastbootd and the device was no longer recognised. The phone got stuck in `<waiting for any device >.
Prior to entering fastbootd, I am able to recognise my device by running `fastboot devices` but not `adb devices`.
The end of the logs from running `sudo ./device-flasher.linux `:
Bash:
sudo ./device-flasher.linux
Android Factory Image Flasher version 1.0.3
Extracting sunfish-factory-2.8.0.zip
Verifying platform-tools_r30.0.4-linux.zip
Extracting platform-tools_r30.0.4-linux.zip
1. Connect to a wifi network and ensure that no SIM cards are installed
2. Enable Developer Options on device (Settings -> About Phone -> tap "Build number" 7 times)
3. Enable USB debugging on device (Settings -> System -> Advanced -> Developer Options) and allow the computer to debug (hit "OK" on the popup when USB is connected)
4. Enable OEM Unlocking (in the same Developer Options menu)
Press ENTER to continue
Detected sunfish <serialnumber>
Devices to be flashed:
sunfish <serialnumber>
Press ENTER to continue
Unlocking sunfish <serialnumber> bootloader...
5. Please use the volume and power keys on the device to unlock the bootloader
Flashing sunfish <serialnumber> bootloader...
Sending 'bootloader_a' (8357 KB) OKAY [ 0.330s]
Writing 'bootloader_a' (bootloader) Flashing Pack version s5-0.3-7357976
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition logfs
OKAY [ 0.234s]
Finished. Total time: 0.836s
Rebooting into bootloader OKAY [ 0.076s]
Finished. Total time: 0.126s
Sending 'radio_a' (72372 KB) OKAY [ 1.970s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7150-00047-210319-B-7220401
(bootloader) Flashing partition modem_a
OKAY [ 0.353s]
Finished. Total time: 2.547s
Rebooting into bootloader OKAY [ 0.064s]
Finished. Total time: 0.114s
Erasing 'avb_custom_key' OKAY [ 0.217s]
Finished. Total time: 0.304s
Sending 'avb_custom_key' (0 KB) OKAY [ 0.140s]
Writing 'avb_custom_key' OKAY [ 0.225s]
Finished. Total time: 0.564s
Rebooting into bootloader OKAY [ 0.061s]
Finished. Total time: 0.111s
--------------------------------------------
Bootloader Version...: s5-0.3-7357976
Baseband Version.....: g7150-00047-210319-B-7220401
Serial Number........: <serialnumber>
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.070s]
Checking 'version-bootloader' OKAY [ 0.070s]
Checking 'version-baseband' OKAY [ 0.070s]
Setting current slot to 'a' OKAY [ 0.085s]
extracting boot.img (64 MB) to disk... took 0.152s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 2.050s]
Writing 'boot_a' OKAY [ 0.235s]
extracting dtbo.img (8 MB) to disk... took 0.017s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.360s]
Writing 'dtbo_a' OKAY [ 0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_a' OKAY [ 0.077s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_system_a' OKAY [ 0.077s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.070s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Rebooting into bootloader FAILED (Status read failed (No such device))
fastboot: error: Command failed
Locking sunfish <serialnumber> bootloader...
6. Please use the volume and power keys on the device to lock the bootloader
Failed to lock sunfish <serialnumber> bootloader
Things I have tried:
- Different USB port (2.0 and 3.0)
- MacOs install
- Ubuntu 20.04 install
- Flashing Sunfish from flash.android.com (same issue - phone goes to fastbootd and is unrecognised)
- Running as root
TLDR;
- `fastboot devices` in bootloader mode recognizes device but `adb devices` does not
- Entering fastbootd mode `fastboot devices` no longer recognizes my device
- CalyxOs install and stock android install get stuck waiting for device in fastbootd mode
Solved: The issue was the USB cord I was using.
Tried another and it worked