Soft Brick recovery help
So my Pixel 3 is soft bricked and I can't seem to rescue it this time. I am bootloader unlocked and rooted on the stock rom. I was trying to update through fastboot to the April update and the flash all batch file wasn't working, I kept getting the following error
"target reported max download size of 268435456 bytes
sending 'bootloader' (8493 KB)...
OKAY [ 0.261s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(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_a
(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 storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.213s]
finished. total time: 0.475s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
sending 'radio' (71132 KB)...
OKAY [ 1.742s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.407s]
finished. total time: 2.151s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.049s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1999310544 bytes
error: update package missing system.img
Press any key to exit..."
I tried updating all my ADB and SDK tools. Formatting slot a and b and boot a and b then ran the batch file again and same error. Tried flashing each image file individually and the same error. I'm stuck in Fastboot. Any help would be greatly appreciated!
Try redownloading the .img and check CRC to make sure it's good, shouldn't be missing stuff
Sorry to resurrect a dead thread, but did you ever figure out how to fix your issue?
I've got the same problem over here.
Kandern97 said:
Sorry to resurrect a dead thread, but did you ever figure out how to fix your issue?
I've got the same problem over here.
Click to expand...
Click to collapse
Are you using the latest SDK platform tools, fastboot?
Related
Hi,
Sorry form my English.
I have problem with moto g (xt1039). I try to flash new firmware, but I writed firmware for different models, wright now phone stuck at recovery mode. When I write new firmware I always have error. My bootloader is unlocked. I try to write this two firmware ( first: (Moto_G_LTE_XT1039)_RET-GB-SS_4.4.4_KXB21.14-L1.46_cid7_CFC_1FF.xml, second: (Moto_G_LTE_XT1039)_TESCO-GB_4.4.4_KXB21.14-L1.46_cid7_CFC_1FF.xml) and I have this error:
C:\Users\kacpe_000\Desktop\RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.x
ml.modaco.r3>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.033s]
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.384s]
finished. total time: 0.421s
C:\Users\kacpe_000\Desktop\RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.x
ml.modaco.r3>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.110s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash rpm
FAILED (remote failure)
finished. total time: 11.124s
I do everythings from this topic: http://forum.xda-developers.com/showthread.php?t=2542219
This phone had firmware from tesco GB.
Stock recovery?
me_is_rushin said:
Stock recovery?
Click to expand...
Click to collapse
Yes, I don't change recovery. I always write stock firmware using that guide.
I was on latest stock German retail firmware and unlocked the bootloader and then tried to flash twrp via fastboot. Somehow the recovery didn't boot
and I've tried to reflash stock 5.1 firmware. Now the partition table or bootloader seems broken:
It reports Bootloader 41.1A in fastboot and "Device is UNLOCKED. Status Code: 3"
Using the stock flash method every partition seems to be gone:
All partitions report back: "(bootloader) has-slot:xxx: not found", I can still format system partition.
Code:
[email protected]:/.../stock # fastboot flash partition gpt.bin
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.046s]
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.326s]
finished. total time: 0.372s
[email protected]:/.../stock # fastboot flash motoboot motoboot.img
(bootloader) has-slot:motoboot: not found
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.141s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.081s]
finished. total time: 1.222s
[email protected]:/.../stock # fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.089s]
writing 'logo'...
OKAY [ 0.102s]
finished. total time: 0.192s
I only have Linux systems around to play with adb and fastboot. No chance to use blankflash windows tools. Any idea how I can unbrick the phone?
Depending on the distro, root is required to run fastboot properly. For example, in Ubunutu the command is: sudo fastboot devices
"root" is in front of the command line
Hi!
I just finished sideloading the latest image for Pixel 3 (9.0.0 (PQ3A.190505.002, May 2019)
I did everything correct by following all the steps:
- unlocked bootloader
- executed flash_all.bat
- locked bootloader
At the end, after I rebooted the phone, I got into the system and checked the version.. it's still PD1A from september 2018!
Everything is wiped out as a result of unlocking the bootloader so something did work.. but the system isn't PQ3A.
Here is the flash_all.bat log:
Code:
E:\android\blueline-pq3a.190505.002>flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.288s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5343672
(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_a
(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 storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.220s]
finished. total time: 0.510s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.684s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.420s]
finished. total time: 2.114s
rebooting into bootloader...
OKAY [ 0.067s]
finished. total time: 0.067s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.223s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2196 MB) to disk... took 10.381s
archive does not contain 'system.sig'
extracting system_other.img (421 MB) to disk... took 1.999s
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 (445 MB) to disk... took 2.062s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5343672
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8ATX0Z2PL
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.363s
Press any key to exit...
Can you help me understand what I did wrong?
change active slots
Use this command:
fastboot getvar current-slot
This will return the active slot ( either a or b)
then use this command:
fastboot set_active (enter a or b here)
If the first command gives you a enter b and vice versa into the command above, then reflash.
Hi!
Thank you for your suggestion! Before I try it, I want to understand what I did wrong.
First, I realised I was using the 27.0.0-4455170 version of ADB so the first thing I did was to update it to 28.0.3-5475833.
Ok, so from what I understand, there are two boot slots, a and b; a being the one in which the stock image came and b the one which I flashed yesterday.
Because I had an outdated fastboot version, the flashing was successful but the slot wasn't automatically changed (this explains the "remote: variable not found" error at the end of my log).
So the system still used slot a to boot and, of course, I returned to the same stock image the phone came with. Am I correct?
So now, in order to use the second image, I simply need to do "fastboot set_active b" and reboot my phone so it uses that slot instead.
This is where I don't understand why you wrote "[...] into the command above, then reflash", Is that a typo and you actually meant "then reboot"? why should I reflash if slot b is already flashed?
Also, if I were to repeat the flashing sequence with the new adb tool, then I think I don't need to set slot b active manually as this will be done automatically now.
SOLVED
Hi
I tried to flash the original image for my blueline. The flash-all script flashes the bootloader and radio ok but it fails to flash the last file
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8493 KB)...
OKAY [ 0.295s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.1-5578427
(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_a
(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 storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.509s]
finished. total time: 0.804s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.049s
target reported max download size of 268435456 bytes
sending 'radio' (71132 KB)...
OKAY [ 1.694s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.416s]
finished. total time: 2.112s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
error: failed to load 'image-blueline-pq3a.190705.003.zip': Not enough space
Press any key to exit...
Flashing the files individually restult with: ERROR: cannot load ".\system.img" etc.
I'm on the latest platform tools for windows.
I was able to manually flash Pixel device - but Pixel 3 gives me issues. I had TWRP prior to that and Magisk running. Any suggestions appreciated
Edit:
After running flash-all with -s flag instead of -w I noticed that the sequence stops after modem_a and the device reboots into Error reason: error booting boot.img
That space error almost always means you have the wrong version of the toolkit.
TonikJDK said:
That space error almost always means you have the wrong version of the toolkit.
Click to expand...
Click to collapse
That's what I thought of at first but I'm on r29.0.1 from this link.
solved
I don't know how or why but looks like my ADB installation has been corrupted. As soon as I tried a new PC everything worked the 1st time.
Hi,
I wanted to use the method described here to flash the last update to my Pixel3a, stuck to the october update : https://forum.xda-developers.com/t/...ut-twrp-take-ota-updates-once-rooted.3929053/
I did everything described, but the update doesn't work.
Here what I have in the end of the flash process on the CMD window :
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8373 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.3-6863017
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.235s]
finished. total time: 0.525s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.053s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.734s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00084-201008-B-6891501
(bootloader) Flashing partition modem_b
OKAY [ 0.550s]
finished. total time: 2.309s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.074s
target reported max download size of 268435456 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'
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00084-201008-B-6891501
Serial Number........: [HIDDEN FOR THIS POST]
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.055s]
sending 'boot' (65536 KB)...
OKAY [ 1.519s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.982s
Press any key to exit...
I see that the "fail" happens while writing 'boot' but I ignore while it does fail. *
Could you please help me ?
Thanks in advance.
oldbear3 said:
Hi,
I wanted to use the method described here to flash the last update to my Pixel3a, stuck to the october update : https://forum.xda-developers.com/t/...ut-twrp-take-ota-updates-once-rooted.3929053/
I did everything described, but the update doesn't work.
Here what I have in the end of the flash process on the CMD window :
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8373 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.3-6863017
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.235s]
finished. total time: 0.525s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.053s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.734s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00084-201008-B-6891501
(bootloader) Flashing partition modem_b
OKAY [ 0.550s]
finished. total time: 2.309s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.074s
target reported max download size of 268435456 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'
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00084-201008-B-6891501
Serial Number........: [HIDDEN FOR THIS POST]
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.055s]
sending 'boot' (65536 KB)...
OKAY [ 1.519s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.982s
Press any key to exit...
I see that the "fail" happens while writing 'boot' but I ignore while it does fail. *
Could you please help me ?
Thanks in advance.
Click to expand...
Click to collapse
Did you try flashing the system image instead of the OTA? Also did you try a different cord?
MoistPicklez said:
Did you try flashing the system image instead of the OTA? Also did you try a different cord?
Click to expand...
Click to collapse
Sorry, in fact I use the factory image because there is no flash_all.bat in the OTA zip.
I will try with another cord but I'd be surprised it would change anything, as all other operations worked well with this cable...
Also, I can't enter in recovery mode : when I enter into recovery mode, I don't have any options : it says "No Command"... I don't know why.
Ok i tried the other way with OTA updates via recovery.
Thanks for yout help !