Building system.img for a device make_ext4fs [need help] - Android Q&A, Help & Troubleshooting

I have a local phone of my career. Probably you don't know which, it doesn't matter either. One is on 4.3 and other is on 4.4 !
I have dumped 4.4's dev/block/platform/msm_sdcc.1/by-name files (system, boot, aboot, recovery, sbl1, modem, etc every partition) and flashed partitions on 4.3 one.
But system didn't get flashed. I extracted system.img which I dumped and got /system files! Now using make_ext4fs I have created a filesystem
make_ext4fs -s -S file_contexts -l 1024M -a system system.img ../output
>make_ext4fs -s -S file_context -l 1024M -a system system.img ../output
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 2360/65536 inodes and 199521/262144 blocks
Click to expand...
Click to collapse
I have got the system.img and flashed it via fastboot:
fastboot flash system system.img
target reported max download size of 301989888 bytes
erasing 'system'...
OKAY [ 21.150s]
sending sparse 'system' (294325 KB)...
OKAY [ 10.288s]
writing 'system'...
OKAY [ 26.686s]
sending sparse 'system' (285521 KB)...
OKAY [ 9.826s]
writing 'system'...
OKAY [ 26.364s]
sending sparse 'system' (202921 KB)...
OKAY [ 6.836s]
writing 'system'...
OKAY [ 16.839s]
finished. total time: 270.100s
Click to expand...
Click to collapse
System booted up but has:
No adb shell (- exec '/system/bin/sh' failed: Exec format error (8) -)
No SIM
No baseband
No IMEI
No MAC-WIFI
No MAC-Bluetooth
Could be due to file_context or selinux, anyways help plz. I am using the one which is already there in the directory. I am building image for android 4.4 (using prebuilt windows tools with cygwin x64_86)

Guys .. Any help for the reported error?!
Thanks.

Related

Android 6 firmware update failed

Hello,
Today I made an attempt to update my Nexus 5 to Android 6, manually.
So I put it into USB debugging mode, connected to my PC, and run "flash-all.bat" from firmware archive.
For some reason it ended up with message FAILED, but Android 6 was installed on my phone.
I wonder, what has failed, and should I worry about it, should I do something about it?
Update log:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
e:\Software\Android-SDK-Unlock\Android_v6>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.313s]
writing 'bootloader'...
OKAY [ 0.567s]
finished. total time: 0.880s
rebooting into bootloader...
OKAY [ 0.117s]
finished. total time: 0.117s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.812s]
writing 'radio'...
OKAY [ 3.183s]
finished. total time: 4.995s
rebooting into bootloader...
OKAY [ 0.102s]
finished. total time: 0.102s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.27
Serial Number........: 0......................8
--------------------------------------------
checking product...
OKAY [ 0.092s]
checking version-bootloader...
OKAY [ 0.101s]
checking version-baseband...
OKAY [ 0.107s]
sending 'boot' (9156 KB)...
OKAY [ 0.541s]
writing 'boot'...
OKAY [ 0.781s]
sending 'recovery' (10016 KB)...
OKAY [ 0.603s]
writing 'recovery'...
OKAY [ 0.849s]
erasing 'system'...
OKAY [ 2.142s]
sending 'system' (1019261 KB)...
OKAY [ 37.004s]
writing 'system'...
OKAY [ 86.957s]
erasing 'userdata'...
OKAY [ 38.990s]
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
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 170.121s
Press any key to exit...
Click to expand...
Click to collapse
I'm wondering if you didn't flash the img meant for the 64 and you have a 32GB? If it booted up and the system, bootloader, and radios are all updated, then nothing to be concerned about.

Nexus 5x Device state- locked and OS rebooting before boot, any ideas?

Phone started to loop through booting, crashes at different points of booting. Preformed a wipe data/factory reset and is doing the same loop though booting. Last ditch effort i want to try flashing but looks like i can't as it's locked any ideas?
error = FAILED (remote: device is locked. Cannot flash images)
bullhead LGH791 16GB
HW Version - rev_1.0
Bootloader version BHZ11m
Baseband Version - M8994F-2.6.37.2.21
Carrier info - N/A
Signing - production
Secure boot - enabled
Device - State - locked
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'bootloader' (4616 KB)...
OKAY [ 0.180s]
writing 'bootloader'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.210s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.300s]
writing 'radio'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.330s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 11773390848
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2874363
Block groups: 88
Reserved block group size: 703
Created filesystem with 11/719488 inodes and 84965/2874363 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11m
Baseband Version.....: M8994F-2.6.37.2.21
Serial Number........: 00bf02fa89e421b5
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.010s]
checking version-baseband...
OKAY [ 0.010s]
sending 'boot' (12045 KB)...
OKAY [ 0.341s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.501s
Press any key to exit...

Very hard bricked OP x

Hey Guys,
i'm having a big Problem. I hard bricked a OP x.
I think there is a problem with the partitions.
I can flash recoverys. I can't flash or wipe anything in TWRP because "Failed to mount '/system' (invalid argument)".
And flashing stock OOS via fastboot is not working too.
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.172s]
sending sparse 'system' 1/2 (524284 KB)...
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
OKAY [ 16.890s]
writing 'system' 1/2...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 23.014s
Any way to get it working again?
cat /proc/partitions
echoes an empty list :/
=> Mega Unbrick Guide

vodafone smart platinum 7 or vfd 900 stuck on boot loop

hi guys...im searching for solution already few days for this phone but i cant find anything useful...anyone had experience in repairing this phone?
how to do it..where can i find firmware or stock rom flashing software and of course manual how to do it..
same problem here
I have same problem and also bootloader loocked
any way to flash it i tried alot of firmware via fastboot but not working
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'bootloader' (32248 KB)...
OKAY [ 1.293s]
writing 'bootloader'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 1.301s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio' (57272 KB)...
OKAY [ 2.099s]
writing 'radio'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 2.105s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 26151194624
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6384569
Block groups: 195
Reserved block group size: 1024
Created filesystem with 11/1597440 inodes and 144298/6384569 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 1abbebe9
--------------------------------------------
checking product...
FAILED
Device product is 'IDOL4S_VDF'.
Update requires 'marlin' or 'sailfish'.
finished. total time: 0.016s
Press any key to exit...
magedmagdy19 said:
I have same problem and also bootloader loocked
any way to flash it i tried alot of firmware via fastboot but not working
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'bootloader' (32248 KB)...
OKAY [ 1.293s]
writing 'bootloader'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 1.301s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio' (57272 KB)...
OKAY [ 2.099s]
writing 'radio'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 2.105s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 26151194624
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6384569
Block groups: 195
Reserved block group size: 1024
Created filesystem with 11/1597440 inodes and 144298/6384569 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 1abbebe9
--------------------------------------------
checking product...
FAILED
Device product is 'IDOL4S_VDF'.
Update requires 'marlin' or 'sailfish'.
finished. total time: 0.016s
Press any key to exit...
Click to expand...
Click to collapse
where did you found the firmware?Could you send the download link?

OnePlus 7t Pro Bricked ?

Hi all, i wanted to remove my RR Rom, which was draining a lot battery.
But when i downloaded a new rom (Paranoid Android) and followed the fastboot commands i encounted an error.
7T PRO\payload_dumper-win64\payload_output> fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
So i tried to revert back to stock with this tutorial ( https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 )
But now i am getting these errors:
error: failed to load 'images.zip': No such file or directory
Press any key to exit...
But the images.zip is there , i can see it.
Also when i try other flash ables .bat files:
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.224s]
writing 'userdata'...
OKAY [ 0.003s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 7.236s
error: cannot load 'aop.img'
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'dsp.img'
error: cannot load 'dtbo.img'
error: cannot load 'dtbo.img'
error: cannot load 'modem.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'storsec.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'system.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'system.img'
error: cannot load 'vbmeta.img'
error: cannot load 'vbmeta.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'vendor.img'
"Invalid sparse file format at header magic" is not an error you need only to wait
error: cannot load 'vendor.img'
error: cannot load 'LOGO.img'
error: cannot load 'LOGO.img'
Press any key to continue . . .
I also tried to install TRWP and go from there, but then i get this error:
PS C:\Users\Raseven\Desktop\7T PRO> fastboot flash recovery_a twrp.img
target reported max download size of 805306368 bytes
sending 'recovery_a' (41796 KB)...
OKAY [ 0.899s]
writing 'recovery_a'...
OKAY [ 0.169s]
finished. total time: 1.073s
PS C:\Users\Raseven\Desktop\7T PRO> fastboot flash recovery_b twrp.img
target reported max download size of 805306368 bytes
sending 'recovery_b' (41796 KB)...
OKAY [ 0.900s]
writing 'recovery_b'...
OKAY [ 0.135s]
finished. total time: 1.039s
PS C:\Users\Raseven\Desktop\7T PRO> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.900s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.928s
PS C:\Users\Raseven\Desktop\7T PRO>
Is my phone bricked or ??
From OB8-OnePlus7ProOxygen_13.W.21_OTA_021_all_1912261255_76782007d7dbec-FASTBOOT i tried flash-all bat file :
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: bf29c267
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: require product=msmnile
Setting current slot to 'b' OKAY [ 0.003s]
extracting boot.img (96 MB) to disk... took 0.273s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.154s]
Writing 'boot_b' OKAY [ 0.372s]
extracting dtbo.img (16 MB) to disk... took 0.042s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.366s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.015s]
Writing 'vbmeta' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.197s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.203s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
And another:
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.292s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.043s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk... took 13.269s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
archive does not contain 'system_other.img'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 3.842s
Invalid sparse file format at header magic
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 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 7645ccf6-e8b0-11ea-a92e-2fe9f70f7b34
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: bf29c267
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 2.129s]
writing 'boot_b'...
OKAY [ 0.317s]
sending 'dtbo' (16384 KB)...
OKAY [ 0.361s]
writing 'dtbo'...
OKAY [ 0.069s]
sending sparse 'system' 1/5 (779514 KB)...
Ok i seemed to have fixed it, using the MSM Tool So admin u can lock this.

Categories

Resources