I helped my friend update her Nexus 5 (D820 16GB) to a custom ROM years ago. Then at some point, the phone started boot looping. She wants to have a usable backup phone so I offered to take a look. Right now, I'm trying to flash the phone back to stock. I used the all in one tool and flashed it to stock and while it's successful, I'm stuck on the Google splash screen and it just boot loops. Any suggestions? The ultimate goal is to flash Lineage 18.1 and I understand I need to repartition. But flashing it back to stock and having the phone boot up comes first.
I've never heard of the situation where someone flashes stock ROM to end up in bootloop. Did you wipe everything accordingly including data?
dedq said:
I've never heard of the situation where someone flashes stock ROM to end up in bootloop. Did you wipe everything accordingly including data?
Click to expand...
Click to collapse
Yeah Tool All In One should have wiped it. Then I flashed the M4B30Z stock image using the program. Even if the partitions were messed up, flashing the stock image should fix the partitions shouldn't it? There's no Recovery with the stock image either so I ended up flashing TWRP on it. Still bootloops though.
Code:
Sending 'bootloader' (3124 KB) OKAY [ 0.309s]
Writing 'bootloader' OKAY [ 0.527s]
Finished. Total time: 1.040s
Rebooting into bootloader OKAY [ 0.107s]
Finished. Total time: 0.109s
Sending 'radio' (45489 KB) OKAY [ 1.639s]
Writing 'radio' OKAY [ 3.131s]
Finished. Total time: 4.968s
Rebooting into bootloader OKAY [ 0.113s]
Finished. Total time: 0.115s
--------------------------------------------
Bootloader Version...: HHZ20h
Baseband Version.....: M8974A-2.0.50.2.30
Serial Number........:
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.098s]
Checking 'version-bootloader' OKAY [ 0.098s]
Checking 'version-baseband' OKAY [ 0.098s]
extracting boot.img (8 MB) to disk... took 0.019s
archive does not contain 'boot.sig'
Sending 'boot' (9156 KB) OKAY [ 0.498s]
Writing 'boot' OKAY [ 0.782s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (9 MB) to disk... took 0.021s
archive does not contain 'recovery.sig'
Sending 'recovery' (10014 KB) OKAY [ 0.528s]
Writing 'recovery' OKAY [ 0.830s]
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product_services.img'
extracting system.img (996 MB) to disk... took 3.908s
archive does not contain 'system.sig'
Sending 'system' (1020657 KB) OKAY [ 32.182s]
Writing 'system' OKAY [ 69.243s]
archive does not contain 'vendor.img'
Erasing 'userdata' OKAY [ 6.460s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 3351034 4k blocks and 838832 inodes
Filesystem UUID: ca34c81e-004a-11ec-9447-47d46c854d1d
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (3400 KB) OKAY [ 0.241s]
Writing 'userdata' OKAY [ 0.413s]
Erasing 'cache' OKAY [ 0.528s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 179200 4k blocks and 44832 inodes
Filesystem UUID: cb4472c2-004a-11ec-9cb6-b71c39fcd71a
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (252 KB) OKAY [ 0.189s]
Writing 'cache' OKAY [ 0.202s]
Rebooting OKAY [ 0.099s]
Finished. Total time: 120.421s
Press any key to exit...
Flashing should have sorted everything out but check whether data was wiped once more since I haven't used wipe mechanism you use here for ages so I have forgotten.
dedq said:
Flashing should have sorted everything out but check whether data was wiped once more since I haven't used wipe mechanism you use here for ages so I have forgotten.
Click to expand...
Click to collapse
I wiped data and now can get into the Google boot up animation screen but gets stuck there. Can't make it to "Welcome to Android"
Do you get UI elements?
dedq said:
Do you get UI elements?
Click to expand...
Click to collapse
Nope. I just flashed the stock Google image to restore it back to stock. Ultimate goal is to flash Lineage 18.1 but it looks like I have to repartition first.
It's very interesting because flashing ROM should return everything to default. Try with Lineage.
dedq said:
It's very interesting because flashing ROM should return everything to default. Try with Lineage.
Click to expand...
Click to collapse
Trying to but the repartition isn't working. I must be doing something wrong...
geokilla said:
Trying to but the repartition isn't working. I must be doing something wrong...
Click to expand...
Click to collapse
Have you tried flashing the stock factory image via fastboot (flash-all) instead of the all-in-one tool? Might be worth a shot.
Lughnasadh said:
Have you tried flashing the stock factory image via fastboot (flash-all) instead of the all-in-one tool? Might be worth a shot.
Click to expand...
Click to collapse
Yep. It didn't work even though the drivers are installed.
You should restore it using fastboot (don't rely on all-in-one solutions too much).
The flash-all tool by Google, pointed out by Lughnasadh, is the way to go.
Post whatever driver error/problem you may be facing
Related
Hi all,plz plz Help!!:crying:
I got my nexus 5 and tried rooting + custom recovery installation.
Found this tool on XDA
http://forum.xda-developers.com/showthread.php?t=2517802
after installing drivers and unlocking the bootloader I moved to download twrp + flash
(did not boot between steps)
the flash was successful when done, it booted into a boot loop, went back to recovery to do some wipe (dalvick, cache, data) got msg saying unable to mount storage. (pic 1,1-2)
Trying to backup got me the same result (I can tell it recognized sys partition (pic 2) , going to file manager and to sdcard showed empty folder (pic 3).
I can browse the root dir (pic 4) and can still send adb/fastboot commands to device.
Tried flashing stock using the image on Google's site
https://developers.google.com/android/nexus/images?hl=iw&csw=1#hammerheadkrt16m
using this manual
http://www.droid-life.com/2013/11/05/how-to-flash-nexus-5-factory-images/
and got this
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
sending 'bootloader' (2506 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 0.479s]
finished. total time: 0.769s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
sending 'radio' (42033 KB)...
OKAY [ 1.566s]
writing 'radio'...
OKAY [ 2.894s]
finished. total time: 4.461s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot -w update image-hammerhead-krt16m.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: 0317e48a213e71ea
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.030s]
sending 'boot' (8620 KB)...
OKAY [ 30.240s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9202 KB)...
OKAY [ 33.380s]
writing 'recovery'...
OKAY [ 0.770s]
erasing 'system'...
OKAY [ 1.270s]
sending 'system' (692940 KB)...
OKAY [ 23.312s]
writing 'system'...
OKAY [ 47.394s]
erasing 'userdata'...
OKAY [ 17.182s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
critical error: extent_create_backing: calloc: Not enough space
sending 'userdata' (0 KB)...
FAILED ()
finished. total time: 156.080sa
I don’t know what else to do
Also tried flashing stock back using
[TOOLKIT] Wug's Nexus Root Toolkit v1.7.5 [Updated 11/08/13]: Nexus 5 Thread
http://forum.xda-developers.com/showthread.php?t=2517778
tiking the soft-bricked/bootloop and flashing got me this
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
and times out..
plz help me mount the internal storage (sdcard)
and flash stock once again on my device.
eyalinc said:
Hi all,plz plz Help!!:crying:
I got my nexus 5 and tried rooting + custom recovery installation.
Found this tool on XDA
http://forum.xda-developers.com/showthread.php?t=2517802
after installing drivers and unlocking the bootloader I moved to download twrp + flash
(did not boot between steps)
the flash was successful when done, it booted into a boot loop, went back to recovery to do some wipe (dalvick, cache, data) got msg saying unable to mount storage. (pic 1,1-2)
Trying to backup got me the same result (I can tell it recognized sys partition (pic 2) , going to file manager and to sdcard showed empty folder (pic 3).
I can browse the root dir (pic 4) and can still send adb/fastboot commands to device.
Tried flashing stock using the image on Google's site
https://developers.google.com/android/nexus/images?hl=iw&csw=1#hammerheadkrt16m
using this manual
http://www.droid-life.com/2013/11/05/how-to-flash-nexus-5-factory-images/
and got this
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
sending 'bootloader' (2506 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 0.479s]
finished. total time: 0.769s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
sending 'radio' (42033 KB)...
OKAY [ 1.566s]
writing 'radio'...
OKAY [ 2.894s]
finished. total time: 4.461s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot -w update image-hammerhead-krt16m.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: 0317e48a213e71ea
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.030s]
sending 'boot' (8620 KB)...
OKAY [ 30.240s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9202 KB)...
OKAY [ 33.380s]
writing 'recovery'...
OKAY [ 0.770s]
erasing 'system'...
OKAY [ 1.270s]
sending 'system' (692940 KB)...
OKAY [ 23.312s]
writing 'system'...
OKAY [ 47.394s]
erasing 'userdata'...
OKAY [ 17.182s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
critical error: extent_create_backing: calloc: Not enough space
sending 'userdata' (0 KB)...
FAILED ()
finished. total time: 156.080sa
I don’t know what else to do
Also tried flashing stock back using
[TOOLKIT] Wug's Nexus Root Toolkit v1.7.5 [Updated 11/08/13]: Nexus 5 Thread
http://forum.xda-developers.com/showthread.php?t=2517778
tiking the soft-bricked/bootloop and flashing got me this
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
and times out..
plz help me mount the internal storage (sdcard)
and flash stock once again on my device.
Click to expand...
Click to collapse
Try to reflash the factory image from here https://developers.google.com/android/nexus/images in fastboot, read this http://forum.xda-developers.com/showthread.php?t=2513701 for a how to and DO NOT USE TOOLKITS ANYMORE!
The missing .Sig files is normal when flashing the stock images and nothing to be concerned about
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:39 PM ---------- Previous post was at 01:36 PM ----------
Do you have a 16gb or a 32.
It looks like it's trying to create a 32gb and erroring because there isn't enough free space
Sent from my Nexus 4 using xda app-developers app
10x guys so solved!
Sent from my Nexus 5 using Tapatalk
what did you end up doing?
eyalinc said:
10x guys so solved!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have same problem but the thread doesn't seem to have the solution on it. Can you tell me how you fixed the problem please?
I'm freakin losing it!!!!
Thanks
roguecomic said:
I have same problem but the thread doesn't seem to have the solution on it. Can you tell me how you fixed the problem please?
I'm freakin losing it!!!!
Thanks
Click to expand...
Click to collapse
gee2012 said:
Try to reflash the factory image from here https://developers.google.com/android/nexus/images in fastboot, read this http://forum.xda-developers.com/showthread.php?t=2513701 for a how to and DO NOT USE TOOLKITS ANYMORE!
Click to expand...
Click to collapse
guess its hard to read.
Hi all,
I recently rooted my Pixel and was plagued by the 15% battery issue. I found in the Pixel XL forum to fix it i should flash boot_a boot.img but that erased all my data.
I figured I'd start fresh and looked up a few websites who had instructions (androidcentral being one of them) and it seems like any other google phone, except i started getting FAILED to flash. so i ended up doing the following and now my device is encrypted.
fastboot flash bootloader bootloader-img
fastboot reboot bootloader
fastboot flash radio radio-img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot flash userdata userdata.img
fastboot flash vendor_a vendor.img
fastboot format userdata (have to do this in order to get phone to read as 128GB)
---
so now when i boot up, it goes through the setup but it's encrypted.
I guess my question is, with the way Pixel's will be handling updates, what are all of the extra .img files from the factory image and should i be flashing them in a particular order?
here are the contents:
aboot.img
apdp.img
boot.img
bootlocker.img
cmnlib32.img
cmnlib64.img
devcfg.img
hosd.img
hyp.img
keymaster.img
modem.img
pmic.img
rpm.img
system_other.img
system.img
tz.img
userdata.img
vendor.img
xbl.img
Any assistance would be greatly appreciated!
Thanks!
EDIT #1: I just locked and then unlocked the bootloader to see if that allows me to setup as unencrypted. It's taking a while to boot so I doubt it.
EDIT #2: Still encrypted after set up.
Wellp... i wonder what flashing these after the initial order above will do...
EDOT#3:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
... still encrypted, it booted up a bit quicker (or maybe i'm going nuts)
EDIT #4:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash keymaster_a keymaster.img
andddd.... still encrypted... can anyone help out?
updating android sudio/sdk
So on the newest SDK, the fastboot flash system system.img will automatically detect and erase system_a.
probably a good idea to be on the latest sdk platform-tools
lockd / unlocked bootloader
bash update-all.sh
CRUD... still encrypted.
here's the output if anyone would like:
Code:
Marcs-MacBook-Pro:sailfish-nde63p root# bash flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32820 KB)...
OKAY [ 1.404s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
OKAY [ 1.040s]
finished. total time: 2.444s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'radio_a' (57048 KB)...
OKAY [ 2.457s]
writing 'radio_a'...
OKAY [ 0.869s]
finished. total time: 3.326s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: NOPE :)
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (25073 KB)...
OKAY [ 0.982s]
writing 'boot_a'...
OKAY [ 0.600s]
erasing 'system_a'...
OKAY [ 1.201s]
sending sparse 'system_a' 1/4 (518936 KB)...
OKAY [ 29.084s]
writing 'system_a' 1/4...
OKAY [ 5.336s]
sending sparse 'system_a' 2/4 (506887 KB)...
OKAY [ 28.523s]
writing 'system_a' 2/4...
OKAY [ 13.352s]
sending sparse 'system_a' 3/4 (491777 KB)...
OKAY [ 28.733s]
writing 'system_a' 3/4...
OKAY [ 6.808s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 1.732s]
writing 'system_a' 4/4...
OKAY [ 0.619s]
erasing 'system_b'...
OKAY [ 1.181s]
sending sparse 'system_b' 1/4 (517263 KB)...
OKAY [ 30.183s]
writing 'system_b' 1/4...
OKAY [ 4.555s]
sending sparse 'system_b' 2/4 (513954 KB)...
OKAY [ 25.261s]
writing 'system_b' 2/4...
OKAY [ 5.386s]
sending sparse 'system_b' 3/4 (523846 KB)...
OKAY [ 33.335s]
writing 'system_b' 3/4...
OKAY [ 4.485s]
sending sparse 'system_b' 4/4 (88422 KB)...
OKAY [ 7.907s]
writing 'system_b' 4/4...
OKAY [ 1.348s]
erasing 'vendor_a'...
OKAY [ 0.520s]
sending 'vendor_a' (234137 KB)...
OKAY [ 7.342s]
writing 'vendor_a'...
OKAY [ 6.647s]
Setting current slot to 'a'...
OKAY [ 0.400s]
erasing 'userdata'...
OKAY [ 28.688s]
sending 'userdata' (145102 KB)...
OKAY [ 4.998s]
writing 'userdata'...
OKAY [ 2.393s]
rebooting...
finished. total time: 282.030s
Marcs-MacBook-Pro:sailfish-nde63p root#
tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/
spunks3 said:
tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/
Click to expand...
Click to collapse
Thanks friend!:laugh:
Modifiy the kernel
omegear said:
Modifiy the kernel
Click to expand...
Click to collapse
How?
Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!
Oface82 said:
Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!
Click to expand...
Click to collapse
I think it'll just be a waiting game... This happened to me when I flashed the original boot image using an out of date SDK.
Can you point me in the direction of the factory images? I need to start over
Why are you so desperate to decrypt? It's encrypted by default, and stops you from nothing at this moment, and likely won't be a road block in the future either.
Sent from my Pixel using Tapatalk
I had a similar issue. I tried to unroot in order to install the new OTA, because it failed. So I tried to flash the factory boot image via
Code:
fastboot flash boot boot.img
fastboot flash boot_b boot.img
After the next boot I got the nice "erasing" screen...
My phone was unencrypted before (dunno why) and now all my data is gone and it is encrypted... Maybe there are some devices, which are not encrypted by default and factory resetting after updates...
Yesterday I flashed the NMF26U factory image on my Pixel using flash-all. I didn't remove the '-w' because I wanted a clean install. I saved the terminal output and there are several things that have me quite concerned even though my phone appears to be working fine.
Note the two places where it says "FAILED". Am I in trouble but don't know it yet?
Code:
E:\MobileDevices\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.154s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.255s]
finished. total time: 17.410s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.047s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.919s]
writing 'radio'...
OKAY [ 1.092s]
finished. total time: 3.026s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for device >
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: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FA6C10300677
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ 0.031s]
checking version-baseband...
OKAY [ 0.047s]
sending 'boot' (24821 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.655s]
sending sparse 'system' (516459 KB)...
OKAY [ 18.018s]
writing 'system'...
OKAY [ 6.802s]
sending sparse 'system' (520631 KB)...
OKAY [ 18.470s]
writing 'system'...
OKAY [ 10.998s]
sending sparse 'system' (517487 KB)...
OKAY [ 18.096s]
writing 'system'...
OKAY [ 7.597s]
sending 'vendor' (235186 KB)...
OKAY [ 7.956s]
writing 'vendor'...
OKAY [ 6.599s]
erasing 'userdata'...
OKAY [ 6.848s]
sending 'userdata' (138957 KB)...
OKAY [ 4.696s]
writing 'userdata'...
OKAY [ 1.342s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 109.403s
Press any key to exit...
because flash all is bat file, it contains many items which maybe not included in the factory image to be fashed.
Almost, I got same information.
by the way, how can we save or input the flash all results. I am on windows
bush911 said:
by the way, how can we save or input the flash all results. I am on windows
Click to expand...
Click to collapse
Right click the menu bar in the command box and select edit then 'selec all's. Right click again, edit then copy. Paste it into a document.
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Your fastboot binary is out of date. Make sure you're using the latest version.
wbxp99 said:
Your fastboot binary is out of date. Make sure you're using the latest version.
Click to expand...
Click to collapse
Thank you! It's nice to receive a definitive answer on this. I flashed again with the latest fastboot version and the log output is very different from the first time. I am confident now that everything is in its proper place.
pstgh said:
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Click to expand...
Click to collapse
This a thread about fastboot error messages. There are guide in the SU and TWRP threads. Very easy I don't personally think you need anything like boot to root. Just follow the instructions and make sure you use TWRP RC1 and SU 2.79 SR 2
Hi all. it's been a while since I've posted on xda
I'm having a problem with my newly acquired Pixel,
Today, I received an OTA notification for Android 8.1, tried to have it install but the when the phone restarts to install, it just flash to google logo like 3 times and them boot back to 8.0.
I looked it up on google, people say I should factory reset before restarting and install 8.1. Tried that but same thing happens.
Then I decided to download the factory image and flash it myself. With OEM unlocking and Android debugging enabled, the 8.1 image flashed successfully. However, the phone doesn't boot, it shows a dead Android and a "No command" error. Same thing happen when I try to sideload the OTA file...
I had to flash the 8.0 factory image for the phone to boot successfully again...
Now I have no idea how to get 8.1... Do you guys have any idea of what can be done or what's happening?
Thanks in advance!
Did you update your fastboot tools? That is needed for 8.1
TonikJDK said:
Did you update your fastboot tools? That is needed for 8.1
Click to expand...
Click to collapse
I used the latest version of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
It flashed successfully without any error, so I assume my fastboot is fine...
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Thanks, I'll try and report back
roirraW "edor" ehT said:
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Click to expand...
Click to collapse
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
cnkhanh said:
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
Click to expand...
Click to collapse
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
nine7nine said:
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
Click to expand...
Click to collapse
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
cnkhanh said:
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
Click to expand...
Click to collapse
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
nine7nine said:
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
Click to expand...
Click to collapse
Sorry, I meant the issue was that in my original post, the phone doesn't boot and stuck on the "No command" screen...
When the flash all script runs, my phones was on fastboot mode, rebooting to bootloader several times during the process (this is expected i guess). When the script finishes successfully, the phone tries to boot into the OS, but it shows a google logo and turns off, several times (like a bootloop), then eventually shows the "No command" screen.
Currently, I'm on 8.0, build number OPR3.170623.013
cnkhanh said:
Currently, I'm on 8.0, build number OPR3.170623.013
Click to expand...
Click to collapse
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Click to expand...
Click to collapse
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks for pointing out, but the version I was trying to flash was correct, sailfish 8.1.0 (OPM1.171019.011, Dec 2017)
I'll try another PC and cable later, I'm running on Windows 10 Fall Creator Update.
I don't think warranty is a viable option for me
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
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 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
Click to expand...
Click to collapse
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
cnkhanh said:
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
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 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
Click to expand...
Click to collapse
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
cnkhanh said:
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
Click to expand...
Click to collapse
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Click to expand...
Click to collapse
You're welcome, hey, you can up with the good suggestion!
Another idea is at least on 8.0 with SuperSU, I was able to flash the entire 8.1 firmware with @Chainfire 's FlashFire app, every partition.
Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
nine7nine said:
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Click to expand...
Click to collapse
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
cnkhanh said:
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
Click to expand...
Click to collapse
My theory is that it is updating the secondary system partition but failing to switch partitions. I could be wrong.
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Code:
C:\Users\XXXX>fastboot flash bootloader "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\bootloader-sargo-b4s4-0.2-5736883.img"
target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.2-5736883
(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.586s]
finished. total time: 0.865s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\XXX>fastboot flash radio "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\radio-sargo-g670-00025-190805-b-5781381.img"
target reported max download size of 268435456 bytes
sending 'radio' (73196 KB)...
OKAY [ 1.673s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_b
OKAY [ 0.555s]
finished. total time: 2.244s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.053s
C:\Users\XXX>fastboot -w update "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\image-sargo-qp1a.191105.003.zip"
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'
W/ (15016): Zip: unable to truncate file to 485105848: File too large
failed to extract 'vendor.img': I/O Error
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b4s4-0.2-5736883
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: 97AAY1041S
--------------------------------------------
checking product...
OKAY [ 0.053s]
checking version-bootloader...
OKAY [ 0.063s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot' (65536 KB)...
OKAY [ 1.520s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.006s
Thank you in advance!
Simon
simhagen said:
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Thank you in advance!
Simon
Click to expand...
Click to collapse
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Horgar said:
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Click to expand...
Click to collapse
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Code:
[[email protected] MyApplication]$ sudo fastboot flash bootloader /home/XXXX/Downloads/sargo-pd2a.190115.029/bootloader-sargo-b4s4-0.1-5262905.img
Sending 'bootloader_b' (8349 KB) OKAY [ 0.340s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b4s4-0.1-5262905
(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.541s]
Finished. Total time: 1.074s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot flash radio /home/XXXX/Downloads/sargo-pd2a.190115.029/radio-sargo-g670-00011-190213-b-5306579.img
Sending 'radio_b' (72988 KB) OKAY [ 2.230s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g670-00011-190213-B-5306579
(bootloader) Flashing partition modem_b
OKAY [ 0.880s]
Finished. Total time: 3.315s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot update -w /home/XXXX/Downloads/sargo-pd2a.190115.029/image-sargo-pd2a.190115.029.zip
--------------------------------------------
Bootloader Version...: b4s4-0.1-5262905
Baseband Version.....: g670-00011-190213-B-5306579
Serial Number........: xxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.051s]
Checking 'version-bootloader' OKAY [ 0.052s]
Checking 'version-baseband' OKAY [ 0.052s]
Setting current slot to 'b' OKAY [ 0.063s]
extracting boot.img (64 MB) to disk... took 0.284s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.990s]
Writing 'boot_b' OKAY [ 0.729s]
extracting dtbo.img (8 MB) to disk... took 0.056s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.340s]
Writing 'dtbo_b' OKAY [ 0.133s]
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.064s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2271 MB) to disk... took 11.015s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/9 (262140 KB) OKAY [ 7.389s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 2/9 (262140 KB) OKAY [ 7.840s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 3/9 (262140 KB) OKAY [ 7.830s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 4/9 (262140 KB) OKAY [ 7.760s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 5/9 (262140 KB) OKAY [ 7.870s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 6/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 7/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 8/9 (258620 KB) OKAY [ 7.690s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 9/9 (232288 KB) OKAY [ 7.020s]
Writing 'system_b' OKAY [ 1.920s]
archive does not contain 'system_ext.img'
extracting system_other.img (391 MB) to disk... took 1.914s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/2 (262140 KB) OKAY [ 7.850s]
Writing 'system_a' OKAY [ 0.370s]
Sending sparse 'system_a' 2/2 (138668 KB) OKAY [ 4.200s]
Writing 'system_a' OKAY [ 1.380s]
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
sic0048 said:
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Click to expand...
Click to collapse
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Horgar said:
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Click to expand...
Click to collapse
Thanks,
link does not work for me though...
simhagen said:
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
Click to expand...
Click to collapse
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
For example, if you have ADB installed on your C: drive and your C: drive doesn't have several GB of storage space available, you will get this error. It won't help if you have space available on other drives, because ADB only interacts with the folder it is installed on. So having 100 GB free on another drive won't help as an example.
sic0048 said:
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
Click to expand...
Click to collapse
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
simhagen said:
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
Click to expand...
Click to collapse
No. As long as that space is available on your main drive (see my edit above), 30 GB should be plenty of space. I'm thinking it takes around 5 GB if I remember correctly.
simhagen said:
Thanks,
link does not work for me though...
Click to expand...
Click to collapse
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Try this
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
Code:
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
under Windows I didn't get this problem. So system is up and running again.
Thank you!
simhagen said:
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
under Windows I didn't get this problem. So system is up and running again.
Thank you!
Click to expand...
Click to collapse
Glad to hear you're sorted. It took me a while to work out I just needed to update fastboot. Someone on XDA helped me with it.
simhagen said:
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Click to expand...
Click to collapse
I had the exact same problem as you did. I tried different versions of the stock ROM, I tried different versions of the fastboot tool (including sdkmanager --update to get to the latest, etc.). It failed at the same time, every time: "Sending sparse 'vendor_a'"
What actually worked for me was plugging the USB cable into a port directly on the laptop, instead of a hub built into the docking station.
**** you not, worked perfectly. Same cable, same fastboot binary, same laptop, same OS, just switching to a different port did the trick. Don't plug the cable into a USB hub.