Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
HTML:
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.bat
Do you wish to wipe the device when flashing?(Y/N): Y
sending 'partition' (34 KB)...
OKAY [ 0.020s]
writing 'partition'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'sbl1' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
OKAY [ 0.021s]
finished. total time: 0.057s
sending 'sbl1bak' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1bak'...
OKAY [ 0.021s]
finished. total time: 0.059s
sending 'aboot' (701 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 0.021s]
finished. total time: 0.055s
sending 'abootbak' (701 KB)...
OKAY [ 0.030s]
writing 'abootbak'...
OKAY [ 0.021s]
finished. total time: 0.056s
sending 'rpm' (188 KB)...
OKAY [ 0.020s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'rpmbak' (188 KB)...
OKAY [ 0.020s]
writing 'rpmbak'...
OKAY [ 0.021s]
finished. total time: 0.047s
sending 'tz' (561 KB)...
OKAY [ 0.030s]
writing 'tz'...
OKAY [ 0.020s]
finished. total time: 0.056s
sending 'tzbak' (561 KB)...
OKAY [ 0.030s]
writing 'tzbak'...
OKAY [ 0.020s]
finished. total time: 0.055s
sending 'hyp' (93 KB)...
OKAY [ 0.020s]
writing 'hyp'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'hypbak' (93 KB)...
OKAY [ 0.020s]
writing 'hypbak'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'sdi' (28 KB)...
OKAY [ 0.020s]
writing 'sdi'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmic' (37 KB)...
OKAY [ 0.020s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmicbak' (37 KB)...
OKAY [ 0.020s]
writing 'pmicbak'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'hwcfg' (1 KB)...
OKAY [ 0.020s]
writing 'hwcfg'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'bluetooth' (450 KB)...
OKAY [ 0.020s]
writing 'bluetooth'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'keymaster' (148 KB)...
OKAY [ 0.020s]
writing 'keymaster'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'cmnlib' (165 KB)...
OKAY [ 0.020s]
writing 'cmnlib'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'splash' (6075 KB)...
OKAY [ 0.141s]
writing 'splash'...
OKAY [ 0.020s]
finished. total time: 0.166s
sending 'splash2' (6075 KB)...
OKAY [ 0.141s]
writing 'splash2'...
OKAY [ 0.020s]
finished. total time: 0.167s
sending 'persist' (4673 KB)...
OKAY [ 0.120s]
writing 'persist'...
OKAY [ 0.020s]
finished. total time: 0.144s
sending 'modem' (78615 KB)...
OKAY [ 1.729s]
writing 'modem'...
OKAY [ 0.013s]
finished. total time: 1.746s
sending 'cust_nv' (301 KB)...
OKAY [ 0.030s]
writing 'cust_nv'...
OKAY [ 0.021s]
finished. total time: 0.053s
sending 'systeminfo' (4 KB)...
OKAY [ 0.020s]
writing 'systeminfo'...
OKAY [ 0.021s]
finished. total time: 0.043s
sending 'KEY_INFO' (1 KB)...
OKAY [ 0.020s]
writing 'KEY_INFO'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'hidden' (9319 KB)...
OKAY [ 0.211s]
writing 'hidden'...
OKAY [ 0.020s]
finished. total time: 0.235s
sending 'sutinfo' (1 KB)...
OKAY [ 0.020s]
writing 'sutinfo'...
OKAY [ 0.021s]
finished. total time: 0.044s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
sending 'recovery' (12794 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
< waiting for device >
sending 'boot' (11746 KB)...
OKAY [ 0.281s]
writing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.306s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.011s
< waiting for device >
simu_flash:971f0dec:system
sending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers
vampire_8_7 said:
Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.batDo you wish to wipe the device when flashing?(Y/N): Ysending 'partition' (34 KB)...OKAY [ 0.020s]writing 'partition'...OKAY [ 0.021s]finished. total time: 0.049ssending 'sbl1' (479 KB)...OKAY [ 0.030s]writing 'sbl1'...OKAY [ 0.021s]finished. total time: 0.057ssending 'sbl1bak' (479 KB)...OKAY [ 0.030s]writing 'sbl1bak'...OKAY [ 0.021s]finished. total time: 0.059ssending 'aboot' (701 KB)...OKAY [ 0.030s]writing 'aboot'...OKAY [ 0.021s]finished. total time: 0.055ssending 'abootbak' (701 KB)...OKAY [ 0.030s]writing 'abootbak'...OKAY [ 0.021s]finished. total time: 0.056ssending 'rpm' (188 KB)...OKAY [ 0.020s]writing 'rpm'...OKAY [ 0.021s]finished. total time: 0.045ssending 'rpmbak' (188 KB)...OKAY [ 0.020s]writing 'rpmbak'...OKAY [ 0.021s]finished. total time: 0.047ssending 'tz' (561 KB)...OKAY [ 0.030s]writing 'tz'...OKAY [ 0.020s]finished. total time: 0.056ssending 'tzbak' (561 KB)...OKAY [ 0.030s]writing 'tzbak'...OKAY [ 0.020s]finished. total time: 0.055ssending 'hyp' (93 KB)...OKAY [ 0.020s]writing 'hyp'...OKAY [ 0.021s]finished. total time: 0.049ssending 'hypbak' (93 KB)...OKAY [ 0.020s]writing 'hypbak'...OKAY [ 0.021s]finished. total time: 0.045ssending 'sdi' (28 KB)...OKAY [ 0.020s]writing 'sdi'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmic' (37 KB)...OKAY [ 0.020s]writing 'pmic'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmicbak' (37 KB)...OKAY [ 0.020s]writing 'pmicbak'...OKAY [ 0.021s]finished. total time: 0.046ssending 'hwcfg' (1 KB)...OKAY [ 0.020s]writing 'hwcfg'...OKAY [ 0.021s]finished. total time: 0.045ssending 'bluetooth' (450 KB)...OKAY [ 0.020s]writing 'bluetooth'...OKAY [ 0.021s]finished. total time: 0.046ssending 'keymaster' (148 KB)...OKAY [ 0.020s]writing 'keymaster'...OKAY [ 0.021s]finished. total time: 0.046ssending 'cmnlib' (165 KB)...OKAY [ 0.020s]writing 'cmnlib'...OKAY [ 0.021s]finished. total time: 0.045ssending 'splash' (6075 KB)...OKAY [ 0.141s]writing 'splash'...OKAY [ 0.020s]finished. total time: 0.166ssending 'splash2' (6075 KB)...OKAY [ 0.141s]writing 'splash2'...OKAY [ 0.020s]finished. total time: 0.167ssending 'persist' (4673 KB)...OKAY [ 0.120s]writing 'persist'...OKAY [ 0.020s]finished. total time: 0.144ssending 'modem' (78615 KB)...OKAY [ 1.729s]writing 'modem'...OKAY [ 0.013s]finished. total time: 1.746ssending 'cust_nv' (301 KB)...OKAY [ 0.030s]writing 'cust_nv'...OKAY [ 0.021s]finished. total time: 0.053ssending 'systeminfo' (4 KB)...OKAY [ 0.020s]writing 'systeminfo'...OKAY [ 0.021s]finished. total time: 0.043ssending 'KEY_INFO' (1 KB)...OKAY [ 0.020s]writing 'KEY_INFO'...OKAY [ 0.021s]finished. total time: 0.045ssending 'hidden' (9319 KB)...OKAY [ 0.211s]writing 'hidden'...OKAY [ 0.020s]finished. total time: 0.235ssending 'sutinfo' (1 KB)...OKAY [ 0.020s]writing 'sutinfo'...OKAY [ 0.021s]finished. total time: 0.044srebooting into bootloader...OKAY [ 0.006s]finished. total time: 0.006s< waiting for device >sending 'recovery' (12794 KB)...OKAY [ 0.291s]writing 'recovery'...OKAY [ 0.020s]finished. total time: 0.320srebooting into bootloader...OKAY [ 0.003s]finished. total time: 0.003s< waiting for device >sending 'boot' (11746 KB)...OKAY [ 0.281s]writing 'boot'...OKAY [ 0.019s]finished. total time: 0.306srebooting into bootloader...OKAY [ 0.010s]finished. total time: 0.011s< waiting for device >simu_flash:971f0dec:systemsending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers
Click to expand...
Click to collapse
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader
AnierinB said:
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader
Click to expand...
Click to collapse
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.
vampire_8_7 said:
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.
Click to expand...
Click to collapse
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.
HeaDekBatHblu said:
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.
Click to expand...
Click to collapse
hey mate these 2 commands don't exist in the fastboot
fastboot reboot system
fastboot reboot-system
I have also tried the adb shell and it gave me "error : no devices found". I had to reboot in recovery and choose apply update via adb so I can see the listed devices.
HTML:
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe devices -l
List of devices attached
NBQGLMB660203876 sideload product:ether model:Robin device:ether
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader
error: closed
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader -i 0x2c3f
error: closed
No luck bro.
This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol
soulife said:
This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol
Click to expand...
Click to collapse
Hey mate so sorry for the late reply, for some reason I didn't see the notification of your reply.
Yeah fastboot and Stock recovery are working fine, but remember bootloader is still locked and the USB debugging isn't enabled. I thought it should be recoverable but I am not able to recover it and tried too many ways but they all have failed. I will appreciate some advise/help to sort this phone. Thanks
That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue
soulife said:
That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue
Click to expand...
Click to collapse
I bought 2 Robins at the time, 1 I used straight away and the other is the 1 that had the issue and I started using it like 3 months later. By default the OEM isn't toggled on I have confirmed that 100%, after the 2nd Robin got bricked. I picked up the working one and looked at it and sure enough the OEM toggle was off so I had to turn it on myself also enabled USB debugging in case this one breaks for some reason.
So yeah, basically if I tried to flash anything via fastboot it says "remote device is locked" and can't sideload anything via ADB also because USB debugging isn't enabled.
I managed to get the OTA.zip for Robin, Nougat update and half way through updating around 47% to 51% it fails, because the boot image is different off course, cause my phone still running 6.0.1, and the OTA find unmatched release keys. I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.
Find 6.0.1?
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
vampire_8_7 said:
I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.
Click to expand...
Click to collapse
soulife said:
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
Click to expand...
Click to collapse
Hey mate yeah I meant flashable.zip, and nope the images won't work via sideload. Definitely the OEM wasn't checked I got 2 Robins and both weren't toggole on.
Related
i can only get to fastboot mode. My nexus Bootloader version - FLO- 04.04, and it's unlocked. I've tried to use Wug tool kit but got stuck at "erasing cache". See log below. I've tried different cables and different USB ports. Any tips or guidance is greatly appreciate. Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.742s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
sending 'boot' (7448 KB)...
OKAY [ 0.245s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.166s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
erasing 'cache'...
i have the same problem
the nand flash is broken, change your mainboard and you will be happy again
i will never buy a asus device
My Nexus 7 2013 LTE was rooted and updated to stock Android 6.0 a year ago, no 3rd party ROM/recovery is installed. Last week while checking emails, it rebooted suddenly then remained at Google letters and unlock icon, I can enter fastboot mode by pressing power and volume- buttons together, the last line shows status unlocked; then if select "Recovery mode", it reboots then shows a dead robot with an exclamation mark only. I downloaded the latest factory image "razorg-mob30x", connect it to my PC and enter adb command "flash-all.bat" (I modified the bat file by removing -w, so it won't wipe the user data), then it shows: FAILED (remote: flash write failure)
sending 'bootloader' (3915 KB)...
OKAY [ 0.135s]
writing 'bootloader' ...
FAILED (remote: flash write failure)
finished. total time 90.811s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time 0.012s
sending 'radio' (76038 KB)...
OKAY [ 2.393s]
writing 'radio' ...
FAILED (remote: flash write failure)
finished. total time 92.549s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
----------------------------------------------------
Bootloader Version...: FLO-04.08
Basedband Version...: DEB-Z00_2.44.0_0213
Serial Number................: 0879222a
----------------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.006s]
checking version-baseband...
OKAY [ 0.006s]
sending 'boot' (7422 KB)
OKAY [ 0.243s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. total time 90.151s
Press any key to exit...
Click to expand...
Click to collapse
What else I can do to resuce my pad? Does this mean the memory is physically damaged?
Please advise. Your help is much appreciated.
Bad motherboard, just had to replace mine with exact issue.
Trying to flash to updated to android 10... Used deuces scrips, used factory script, used 10 different ota image files, several different programs like winzip/winrar etc.... Keep getting stuck wtih your device is corrupt... Any suggestions? Lemme know anything you need to know cause right now i'm f'd
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?n
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 0.021s
Sending 'bootloader_a' (36356 KB) OKAY [ 0.836s]
Writing 'bootloader_a' OKAY [ 0.293s]
Finished. Total time: 1.416s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_a' (60372 KB) OKAY [ 1.583s]
Writing 'radio_a' OKAY [ 0.817s]
Finished. Total time: 3.026s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.003s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' OKAY [ 0.016s]
Finished. Total time: 0.022s
Sending 'bootloader_b' (36356 KB) OKAY [ 0.936s]
Writing 'bootloader_b' OKAY [ 0.266s]
Finished. Total time: 1.778s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_b' (60372 KB) OKAY [ 1.303s]
Writing 'radio_b' OKAY [ 0.828s]
Finished. Total time: 2.221s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.003s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 0.020s
Sending 'abl_a' (540 KB) OKAY [ 0.012s]
Writing 'abl_a' OKAY [ 0.009s]
Finished. Total time: 0.037s
Sending 'aes_a' (48 KB) OKAY [ 0.002s]
Writing 'aes_a' OKAY [ 0.004s]
Finished. Total time: 0.017s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 0.884s]
Writing 'boot_a' OKAY [ 0.377s]
Finished. Total time: 1.326s
Sending 'cmnlib_a' (224 KB) OKAY [ 0.005s]
Writing 'cmnlib_a' OKAY [ 0.022s]
Finished. Total time: 0.041s
Sending 'cmnlib64_a' (296 KB) OKAY [ 0.007s]
Writing 'cmnlib64_a' OKAY [ 0.024s]
Finished. Total time: 0.044s
Sending 'devcfg_a' (60 KB) OKAY [ 0.002s]
Writing 'devcfg_a' OKAY [ 0.015s]
Finished. Total time: 0.031s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.178s]
Writing 'dtbo_a' OKAY [ 0.284s]
Finished. Total time: 0.484s
Sending 'hyp_a' (264 KB) OKAY [ 0.006s]
Writing 'hyp_a' OKAY [ 0.017s]
Finished. Total time: 0.036s
Sending 'keymaster_a' (312 KB) OKAY [ 0.007s]
Writing 'keymaster_a' OKAY [ 0.006s]
Finished. Total time: 0.028s
Sending 'laf_a' (29800 KB) OKAY [ 0.681s]
Writing 'laf_a' OKAY [ 0.130s]
Finished. Total time: 0.874s
Sending 'modem_a' (60364 KB) OKAY [ 1.383s]
Writing 'modem_a' OKAY [ 1.303s]
Finished. Total time: 2.790s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.001s]
Writing 'pmic_a' OKAY [ 0.004s]
Finished. Total time: 0.019s
Sending 'rpm_a' (232 KB) OKAY [ 0.005s]
Writing 'rpm_a' OKAY [ 0.006s]
Finished. Total time: 0.026s
Sending 'tz_a' (1868 KB) OKAY [ 0.041s]
Writing 'tz_a' OKAY [ 0.013s]
Finished. Total time: 0.070s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.018s
Sending 'vendor_a' (360032 KB) OKAY [ 8.197s]
Writing 'vendor_a' OKAY [ 1.520s]
Finished. Total time: 9.923s
Sending 'xbl_a' (2624 KB) OKAY [ 0.058s]
Writing 'xbl_a' OKAY [ 0.020s]
Finished. Total time: 0.094s
Flashing System A
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 11.730s]
Writing 'system_a' OKAY [ 2.231s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 11.741s]
Writing 'system_a' OKAY [ 2.222s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 11.837s]
Writing 'system_a' OKAY [ 2.215s]
Sending sparse 'system_a' 4/5 (521180 KB) OKAY [ 11.666s]
Writing 'system_a' OKAY [ 2.204s]
Sending sparse 'system_a' 5/5 (186148 KB) OKAY [ 4.158s]
Writing 'system_a' OKAY [ 0.783s]
Finished. Total time: 66.619s
Flashing System B
Sending 'system_b' (329560 KB) OKAY [ 7.172s]
Writing 'system_b' OKAY [ 1.396s]
Finished. Total time: 8.774s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' OKAY [ 0.012s]
Finished. Total time: 0.018s
Sending 'abl_b' (540 KB) OKAY [ 0.012s]
Writing 'abl_b' OKAY [ 0.009s]
Finished. Total time: 0.034s
Sending 'aes_b' (48 KB) OKAY [ 0.001s]
Writing 'aes_b' OKAY [ 0.003s]
Finished. Total time: 0.014s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_b' (40960 KB) OKAY [ 0.898s]
Writing 'boot_b' OKAY [ 0.975s]
Finished. Total time: 4.287s
Sending 'cmnlib_b' (224 KB) OKAY [ 0.005s]
Writing 'cmnlib_b' OKAY [ 0.011s]
Finished. Total time: 0.028s
Sending 'cmnlib64_b' (296 KB) OKAY [ 0.006s]
Writing 'cmnlib64_b' OKAY [ 0.037s]
Finished. Total time: 0.059s
Sending 'devcfg_b' (60 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.009s]
Finished. Total time: 0.021s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.188s]
Writing 'dtbo_b' OKAY [ 0.317s]
Finished. Total time: 1.015s
Sending 'hyp_b' (264 KB) OKAY [ 0.006s]
Writing 'hyp_b' OKAY [ 0.013s]
Finished. Total time: 0.030s
Sending 'keymaster_b' (312 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.029s]
Finished. Total time: 0.051s
Sending 'laf_b' (29800 KB) OKAY [ 0.662s]
Writing 'laf_b' OKAY [ 0.186s]
Finished. Total time: 3.118s
Sending 'modem_b' (60364 KB) OKAY [ 1.325s]
Writing 'modem_b' OKAY [ 0.812s]
Finished. Total time: 5.371s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_b' (52 KB) OKAY [ 0.002s]
Writing 'pmic_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'rpm_b' (232 KB) OKAY [ 0.005s]
Writing 'rpm_b' OKAY [ 0.007s]
Finished. Total time: 0.024s
Sending 'tz_b' (1868 KB) OKAY [ 0.041s]
Writing 'tz_b' OKAY [ 0.014s]
Finished. Total time: 0.082s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.013s
Sending 'vendor_b' (360032 KB) OKAY [ 8.128s]
Writing 'vendor_b' OKAY [ 1.541s]
Finished. Total time: 11.953s
Sending 'xbl_b' (2624 KB) OKAY [ 0.062s]
Writing 'xbl_b' OKAY [ 0.050s]
Finished. Total time: 0.163s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.013s]
Finished. Total time: 0.022s
Format Userdata[Y/N]?
What's the problem?
Download stock firmware from Google. Then run
flash-all.sh on Mac
flash-all.bat on Windows.
krabban said:
What's the problem?
Download stock firmware from Google. Then run
flash-all.sh on Mac
flash-all.bat on Windows.
Click to expand...
Click to collapse
I did... Download factory images from google... Did flash-all.bat as well as deuces, both give me the same result
Zooandbio4me said:
I did... Download factory images from google... Did flash-all.bat as well as deuces, both give me the same result
Click to expand...
Click to collapse
Tried format data ?
You'll need to select "Y" when the prompt to format userdata comes up. Formatting the internal storage is I believe the only way to resolve the device corruption issue. A much easier way to go than by using a script is to simply download a factory image (NOT AN OTA), unzip it and run the flash-all command. Deuces should only be used as a weapon of last resort.
I had issues using win zip. 7zipper works though.
In case you were unaware, do not unzip the folder inside. Flash all looks for that zip file and extracts it automatically.
Larzzzz82 said:
I had issues using win zip. 7zipper works though.
In case you were unaware, do not unzip the folder inside. Flash all looks for that zip file and extracts it automatically.
Click to expand...
Click to collapse
WinZip has had problems for some time now, so I mostly use WinRAR, although I have 7-Zip on my PortableApps flash drive.
Strephon Alkhalikoi said:
WinZip has had problems for some time now, so I mostly use WinRAR, although I have 7-Zip on my PortableApps flash drive.
Click to expand...
Click to collapse
This is my ammo too!! Never fails...
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
This is my ammo too!! Never fails...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Yeah I only used 7zip as a means to rule out potential problems
Fastboot boot twrp
Format data and flash/adbsideload the OTA and TWRP installer zip in twrp. I use a type c thumbdrive, mount it in twrp and flash **** from there
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
The only thing I see is that it is only flashing to slot_a. It is my understanding that you need to flash to both partitions a and b before the process will work. For me it has only worked when I flashed to both partitions. Also adding .\ before the command may help. For some reason it only flashes for me when I add it.
Sent from my Pixel 3 XL
Does the AOSP build process generate full OTA images similar to what are found here: https://developers.google.com/android/ota?
If so, try flashing just the bootloader in fastboot, boot into recovery, and sideload the full OTA.
sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
I had this exact error running fastboot from shell on a Chromebook. Simply booting into the full Ubuntu installation I had installed on the Chromebook allowed me to flash.
I believed in my case the error was due to running out of memory. Though using an old fastboot version or a c -> c cable could also cause trouble.
You can also manually flash partitions instead of using the script. Remember, to get to fastbootd, you have to "fastboot reboot fastboot" from the bootloader.
ktmom said:
Though using an old fastboot version or a c -> c cable could also cause trouble.
Click to expand...
Click to collapse
Both of these are good points. You wouldn't think a USB-C to USB-C cable could cause fastboot problems but I've experienced this first hand. I can't quite remember the error I had, but I couldn't flash the stock factory images while using a USB-C to C cable. Switching to a USB-A to C cable (USB 2.0) resolved it.
I was using phh-treble gsi before and I always has been unable to flash anything to boot partition. Today I am trying to flash the factory image, and it also failed at flashing boot. But now because it also flashed to other parition, my phone cannot boot anymore. Tried the official oreo and pie image, both the same thing. Also tried flashing lineage recovery, also failed.
The error message is either
Code:
FAILED (Write to device failed (Invalid argument))
or
Code:
FAILED (Status read failed (Too many links))
.
I tried using different platform tools, including the ones provided by lineage tutorial, and this one [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows. Same thing. I also tried using Linux and using other cables and using USB2.0 and 3.0 ports. Nothing helps so far.
Full log flashing the official android pie firmware
Code:
D:\cheryl-pie>flash_all.bat
D:\cheryl-pie>set fastboot_cmd=fastboot
D:\cheryl-pie>fastboot flash partition:0 gpt_both0.bin
< waiting for any device >
Sending 'partition:0' (44 KB) OKAY [ 0.002s]
Writing 'partition:0' OKAY [ 0.085s]
Finished. Total time: 0.098s
D:\cheryl-pie>fastboot flash partition:1 gpt_both1.bin
Sending 'partition:1' (44 KB) OKAY [ 0.001s]
Writing 'partition:1' OKAY [ 0.100s]
Finished. Total time: 0.121s
D:\cheryl-pie>fastboot flash partition:2 gpt_both2.bin
Sending 'partition:2' (44 KB) OKAY [ 0.001s]
Writing 'partition:2' OKAY [ 0.096s]
Finished. Total time: 0.113s
D:\cheryl-pie>fastboot flash partition:3 gpt_both3.bin
Sending 'partition:3' (44 KB) OKAY [ 0.002s]
Writing 'partition:3' OKAY [ 0.088s]
Finished. Total time: 0.107s
D:\cheryl-pie>fastboot flash partition:4 gpt_both4.bin
Sending 'partition:4' (44 KB) OKAY [ 0.001s]
Writing 'partition:4' OKAY [ 0.100s]
Finished. Total time: 0.125s
D:\cheryl-pie>fastboot flash partition:5 gpt_both5.bin
Sending 'partition:5' (44 KB) OKAY [ 0.002s]
Writing 'partition:5' OKAY [ 0.170s]
Finished. Total time: 0.188s
D:\cheryl-pie>fastboot flash xbl_a xbl.img
Sending 'xbl_a' (2629 KB) OKAY [ 0.074s]
Writing 'xbl_a' OKAY [ 0.015s]
Finished. Total time: 0.104s
D:\cheryl-pie>fastboot flash xbl_b xbl.img
Sending 'xbl_b' (2629 KB) OKAY [ 0.066s]
Writing 'xbl_b' OKAY [ 0.036s]
Finished. Total time: 0.112s
D:\cheryl-pie>fastboot flash tz_a tz.img
Sending 'tz_a' (1868 KB) OKAY [ 0.054s]
Writing 'tz_a' OKAY [ 0.017s]
Finished. Total time: 0.086s
D:\cheryl-pie>fastboot flash tz_b tz.img
Sending 'tz_b' (1868 KB) OKAY [ 0.047s]
Writing 'tz_b' OKAY [ 0.017s]
Finished. Total time: 0.073s
D:\cheryl-pie>fastboot flash rpm_a rpm.img
Sending 'rpm_a' (228 KB) OKAY [ 0.008s]
Writing 'rpm_a' OKAY [ 0.003s]
Finished. Total time: 0.028s
D:\cheryl-pie>fastboot flash rpm_b rpm.img
Sending 'rpm_b' (228 KB) OKAY [ 0.006s]
Writing 'rpm_b' OKAY [ 0.004s]
Finished. Total time: 0.018s
D:\cheryl-pie>fastboot flash hyp_a hyp.img
Sending 'hyp_a' (264 KB) OKAY [ 0.008s]
Writing 'hyp_a' OKAY [ 0.003s]
Finished. Total time: 0.027s
D:\cheryl-pie>fastboot flash hyp_b hyp.img
Sending 'hyp_b' (264 KB) OKAY [ 0.007s]
Writing 'hyp_b' OKAY [ 0.005s]
Finished. Total time: 0.021s
D:\cheryl-pie>fastboot flash pmic_a pmic.img
fastboot: error: cannot load 'pmic.img': No such file or directory
D:\cheryl-pie>fastboot flash pmic_b pmic.img
fastboot: error: cannot load 'pmic.img': No such file or directory
D:\cheryl-pie>fastboot flash keymaster_a keymaster.img
Sending 'keymaster_a' (373 KB) OKAY [ 0.011s]
Writing 'keymaster_a' OKAY [ 0.006s]
Finished. Total time: 0.034s
D:\cheryl-pie>fastboot flash keymaster_b keymaster.img
Sending 'keymaster_b' (373 KB) OKAY [ 0.009s]
Writing 'keymaster_b' OKAY [ 0.003s]
Finished. Total time: 0.021s
D:\cheryl-pie>fastboot flash cmnlib_a cmnlib.img
Sending 'cmnlib_a' (221 KB) OKAY [ 0.007s]
Writing 'cmnlib_a' OKAY [ 0.005s]
Finished. Total time: 0.028s
D:\cheryl-pie>fastboot flash cmnlib_b cmnlib.img
Sending 'cmnlib_b' (221 KB) OKAY [ 0.006s]
Writing 'cmnlib_b' OKAY [ 0.002s]
Finished. Total time: 0.017s
D:\cheryl-pie>fastboot flash cmnlib64_a cmnlib64.img
Sending 'cmnlib64_a' (292 KB) OKAY [ 0.009s]
Writing 'cmnlib64_a' OKAY [ 0.005s]
Finished. Total time: 0.031s
D:\cheryl-pie>fastboot flash cmnlib64_b cmnlib64.img
Sending 'cmnlib64_b' (292 KB) OKAY [ 0.008s]
Writing 'cmnlib64_b' OKAY [ 0.003s]
Finished. Total time: 0.020s
D:\cheryl-pie>fastboot flash devcfg_a devcfg.img
Sending 'devcfg_a' (56 KB) OKAY [ 0.002s]
Writing 'devcfg_a' OKAY [ 0.002s]
Finished. Total time: 0.020s
D:\cheryl-pie>fastboot flash devcfg_b devcfg.img
Sending 'devcfg_b' (56 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.001s]
Finished. Total time: 0.012s
D:\cheryl-pie>fastboot flash abl_a abl.img
Sending 'abl_a' (204 KB) OKAY [ 0.007s]
Writing 'abl_a' OKAY [ 0.004s]
Finished. Total time: 0.028s
D:\cheryl-pie>fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.003s
D:\cheryl-pie>timeout /t 10
Waiting for 0 seconds, press a key to continue ...
D:\cheryl-pie>fastboot flash abl_b abl.img
< waiting for any device >
Sending 'abl_b' (204 KB) OKAY [ 0.006s]
Writing 'abl_b' OKAY [ 0.003s]
Finished. Total time: 0.018s
D:\cheryl-pie>fastboot erase ddr
Erasing 'ddr' OKAY [ 0.114s]
Finished. Total time: 0.118s
D:\cheryl-pie>fastboot flash persist persist.img
Sending 'persist' (32768 KB) OKAY [ 0.870s]
Writing 'persist' OKAY [ 0.598s]
Finished. Total time: 1.488s
D:\cheryl-pie>fastboot flash modem_a modem.img
Sending 'modem_a' (105572 KB) OKAY [ 2.857s]
Writing 'modem_a' OKAY [ 0.944s]
Finished. Total time: 3.820s
D:\cheryl-pie>fastboot flash modem_b modem.img
Sending 'modem_b' (105572 KB) OKAY [ 2.658s]
Writing 'modem_b' OKAY [ 0.948s]
Finished. Total time: 3.612s
D:\cheryl-pie>fastboot flash dsp_a dsp.img
Sending 'dsp_a' (16384 KB) OKAY [ 0.464s]
Writing 'dsp_a' OKAY [ 0.164s]
Finished. Total time: 0.645s
D:\cheryl-pie>fastboot flash dsp_b dsp.img
Sending 'dsp_b' (16384 KB) OKAY [ 0.430s]
Writing 'dsp_b' OKAY [ 0.149s]
Finished. Total time: 0.586s
D:\cheryl-pie>fastboot flash boot_a boot.img
Sending 'boot_a' (25797 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
D:\cheryl-pie>fastboot flash boot_b boot.img
< waiting for any device >
i cant even get my razer phone to recognize in fastboot (it shows adb devices when powered on normally) but never when in bootloader mode fastboot.
you should use the command
fastboot flash:raw boot_a boot.img
fastboot flash:raw boot_b boot.img