Database Develop

[Q] getting error 226 (Flash Write)

I'm getting error 226 (Flash Write) when flashing the first rom at about 6% through.
using DeepShining Mango.7720.68 v1.2 what do i do ?

ERROR [226] : FILE WRITE
This could indicate that the downloaded image (.nbh file) is corrupt, re-download the image.

Tab Wont Boot

Hi Guys,
Was going to try a custom rom from here (Cyanogen Mod), and followed the link in the post to here....
I cant post URLS so *Cyanogen wiki galaxy tab GSM instructions *
I uploaded the kernel without issue. until it rebooted..... Then all i get is the Samsung galaxy tab screen... and it sticks there (the one you see when you turn your tab on).
I can get into DL mode... (power/volumedown). So I tried to load the [ROM][4.1.1] CyanogenMod 10 Preview [Build 3] via clock work... it faield... (Buildprop GT-1000 error?).
So I went to samfirmwares, got my O2 stock rom and DLed it... which comes (as you know) in a uselss... .md5 file. After much searching I found out about splitfus2... installed it and though good.. easy street.... Not it would seem....
Code:
$ ./splitfus2.exe P1000XWJQ8_P1000O2UJQ3_P1000XXJPZ_HOME.tar.md5
SplitFUS2 by Doky v2.11.120625GA
Checking prerequisites...
...tar, md5sum, zip found, ready to go!
Processing file: P1000XWJQ8_P1000O2UJQ3_P1000XXJPZ_HOME.tar.md5
MODEL: P1000
PDA: XWJQ8
CSC: O2UJQ3
MODEM: XXJPZ
mkdir: cannot create directory `P1000_XWJQ8_O2UJQ3': File exists
Temporary workfolder: P1000_XWJQ8_O2UJQ3\
[ P1_add_hidden.pit ] --- Size: 2008 bytes
Checking wipe data file: _base\P1000_userdata.img [NOT FOUND]
Wipe data file not found: _base\P1000_userdata.img
Your device not supported for wipe package
Now creating nonwipe package
tar: boot.img: Cannot stat: No such file or directory
tar: param.lfs: Cannot stat: No such file or directory
tar: system.img: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: csc.*: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: BcmCP.img: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
adding: CSC_P1000_O2UJQ3.tar.md5 (deflated 99%)
adding: MODEM_P1000_XXJPZ.tar.md5 (deflated 99%)
adding: PDA_P1000_XWJQ8.tar.md5 (deflated 99%)
adding: readme.txt (deflated 34%)
Output file: P1000_XWJQ8_O2UJQ3_XXJPZ_by_SplitFUS2.zip
Removing work folder
SplitFUS2 finished
It wont extract....
So can you guys please assist me in recovering my tab with any suggestions other than 'send it to samsung'!.. ive been at this for hours, I don't care what ROM is on it as long as it works now... !
Its a GT-p1000 7 Inch GSM UK tab bough on the O2 network.
It was rooted and unlocked via a tutorial I found on here .
Thanks in advance.
Corpse.

Why you called a tar.md5 useless?
It is still a tar file and works right with Odin.
Follow my post here and you will be fine.
http://forum.xda-developers.com/showthread.php?p=30422534
Sent from my GT-I9300 using xda app-developers app

.tar.md5's are useless on their own... they require splitting for odin to use....
However thanks to your post/link I have managed to ressurect my tablet so thank you
C.

corpseslayer said:
.tar.md5's are useless on their own... they require splitting for odin to use....
However thanks to your post/link I have managed to ressurect my tablet so thank you
C.
Click to expand...
Click to collapse
Err...not true.. you can use the tar.md5 directly in Odin.
Anyway....
glad you resurrected your tab after all!

Update libraries?

Which are the libraries and baseband for G800F?
On my i9515 I extracted aboot.mbn, modem.bin, non-hlos-bin, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn and tz.mbn from the firmware file.
In the G800F firmware file, I can't find all of these. Just the modem.bin, most other files img files...

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=g800f ??????

Odin: FAIL! LZ4 is invalid

I have a ROM that I can flash on Samsung S10 5G(Qualcomm) successfully. My goal is to check whether I can modify `system.img` file of the ROM or not but before modification, I just want to verify that the AP file can be flashed after unpacking and packing of the `system.img`. To check this I have tried following:
Unpack-Pack AP file:
A) `tar` flashing:
1. Extracted AP file using `tar -xf AP...tar.md5` command.
2. Compress the extracted files using `tar -cvf AP...tar *`
3. Flash it with Odin3 v3.13.
B) `tar.md5` flashing:
- Get tar by following steps in A) and then run `md5sum -t AP...tar >> AP...tar` and `mv AP...tar AP...tar.md5`
Both `Ap...tar` and `AP...tar.md5` flashed successfully.
Unpack-Pack `system.img.ext4.lz4`
1. Extracted AP file using `tar -xf AP...tar.md5` command. Extracted files are "*boot.img.lz4*, *meta-data*, *userdata.img.ext4.lz4*, *carrier.img.ext4.lz4*, *persist.img.ext4.lz4*, *vbmeta.img.lz4*, *dqmdbg.img.ext4.lz4*, *recovery.img.lz4*, *vendor.img.ext4.lz4*, *dtbo.img.lz4*, *system.img.ext4.lz4*".
2. Extract system file using `unlz4 system.img.ext4.lz4` command. This is giving me a `system.img.ext4` Android sparse image.
3. Tried following commands to compress `system.img.ext4` without doing any modification:
lz4 system.img.ext4 system.img.ext4.lz4 - Default Compression
lz4 -9 system.img.ext4 system.img.ext4.lz4 - High Compression
lz4 -l system.img.ext4 system.img.ext4.lz4 - Default Compression in Legacy format
lz4 -l -9 system.img.ext4 system.img.ext4.lz4 - High Compression in Legacy format
lz4 -0 -l system.img.ext4 system.img.ext4.lz4 - No Compression in Legacy format
lz4 -B4 system.img.ext4 system.img.ext4.lz4 - Default Compression with Block size 4
lz4 -B5 system.img.ext4 system.img.ext4.lz4 - Default Compression with Block size 5
lz4 -B6 system.img.ext4 system.img.ext4.lz4 - Default Compression with Block size 6
lz4 --no-frame-crc system.img.ext4 system.img.ext4.lz4 - Default Compression with no crc frame
Click to expand...
Click to collapse
and make an AP file by replacing the original `system.img.ext4.lz4` file with the compressed file from above command(one at one time) and tried to flash it but every time it fails with **"Odin FAIL! LZ4 is invalid"**
LZ4 command detail:
1. Working on Ubuntu 18
2. Using "LZ4 command line interface 64-bits r128, by Yann Collet (Apr 3 2018)"
Tried with "LZ4 command line interface 64-bits v1.9.2, by Yann Collet" but get the same result.
`file system.img.ext4.lz4` output:
- Original file: `system.img.ext4.lz4: LZ4 compressed data (v1.4+)`.
- My version with both LZ4 (r128 and v1.9.2):
1. For file compressed with legacy flag(-l): `system.img.ext4.lz4: LZ4 compressed data (v0.1-v0.9)`
2. For file compressed without legacy flag(-l): `system.img.ext4.lz4: LZ4 compressed data (v1.4+)`
So, I think it means the file should be compressed without legacy flag.
Size
1. With `-9` flag i.e. High Compression the output file is of 3.3 GB.
2. Without `-9` flag i.e. Default Compression the output file is of 3.6 GB.
The Original file is of size 3.6 GB so, I think high compression should not be used.
But still the same error throws by Odin.
Any suggestion why it is happening?

having the same problem here.anyone have a solution?

Why Ya dont use "lz4 -m *.lz4" command after Extract with tar, its Decompress all Files in one Process!!
But iam have the same Problem i would a Existing Package tar.md5 Extract and Replace the system.img.lz4 with a newer Version, so i have Compress the IMG to LZ4 with these Command
"lz4 -B6 --content-size system.img system.img.lz4" and then Pack all to tar and add md5sum!! and Flash the Package it would like ya Failed at System Flash Process!!!

Question S21 Ultra 5G stuck after flashing customized boot.img

I am trying to do some customization on S21 Ultra 5G SM-G998B
The source code is obtained from Samsung open source (SM-G998B_RR_Opensource.zip - G998BXXS2AUBB)
Firmware G998BXXS2AUBB_G998BOXM2AUBB_.zip is downloaded from sammobile
Step 1) Extract boot.img from firmware
The boot.img is extracted from the firmware's AP_G998BXXS2AUBB_CL20701476_QB38432109_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar (using 7-zip and unpack with lz4)
The boot.img is then unpacked as follows:
$ ./unpack_bootimg.py --boot_img ./sambootimg/boot.img --out ./out
boot_magic: ANDROID!
kernel_size: 28807680
ramdisk size: 697174
os version: 11.0.0
os patch level: 2021-03
boot image header version: 3
command line args: androidboot.selinux=permissive
This step will output the following files: kernel, ramdisk and mkbootimg_args.json
Step 2) Building kernel
After building the samsung open source kernel (no changes have been made to Kernel code), the Image is obtained at arch/arm64/boot
I understand that Android 11 is based on ver 3 header. The boot.img only consists of Kernel and ramdisk
Step 3) Make boot.img
This kernel image (Image) together with ramdisk is created as follows:
$ ./mkbootimg.py --kernel ./myBootimg/Image --ramdisk ./out/ramdisk --header_version 3 --os_version 11.0.0 --os_patch_level 2021-03 --cmdline androidboot.selinux=permissive --out ./myBootimg/boot.img
$ tar -cvf boot.img.tar boot.img
This created boot.img.tar
Step 4) Magisk patch
After tar, this boot.img.tar is patched according to the magisk procedure which gives magisk_patched-22006_CjCUM.tar
The patched download to phone via the Odin utility successfully
After phone restart, it hang at Samsung screen (with the Android robot)
May I checked if I missed out any other steps?

mhc009 said:
I am trying to do some customization on S21 Ultra 5G SM-G998B
The source code is obtained from Samsung open source (SM-G998B_RR_Opensource.zip - G998BXXS2AUBB)
Firmware G998BXXS2AUBB_G998BOXM2AUBB_.zip is downloaded from sammobile
Step 1) Extract boot.img from firmware
The boot.img is extracted from the firmware's AP_G998BXXS2AUBB_CL20701476_QB38432109_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar (using 7-zip and unpack with lz4)
The boot.img is then unpacked as follows:
$ ./unpack_bootimg.py --boot_img ./sambootimg/boot.img --out ./out
boot_magic: ANDROID!
kernel_size: 28807680
ramdisk size: 697174
os version: 11.0.0
os patch level: 2021-03
boot image header version: 3
command line args: androidboot.selinux=permissive
This step will output the following files: kernel, ramdisk and mkbootimg_args.json
Step 2) Building kernel
After building the samsung open source kernel (no changes have been made to Kernel code), the Image is obtained at arch/arm64/boot
I understand that Android 11 is based on ver 3 header. The boot.img only consists of Kernel and ramdisk
Step 3) Make boot.img
This kernel image (Image) together with ramdisk is created as follows:
$ ./mkbootimg.py --kernel ./myBootimg/Image --ramdisk ./out/ramdisk --header_version 3 --os_version 11.0.0 --os_patch_level 2021-03 --cmdline androidboot.selinux=permissive --out ./myBootimg/boot.img
$ tar -cvf boot.img.tar boot.img
This created boot.img.tar
Step 4) Magisk patch
After tar, this boot.img.tar is patched according to the magisk procedure which gives magisk_patched-22006_CjCUM.tar
The patched download to phone via the Odin utility successfully
After phone restart, it hang at Samsung screen (with the Android robot)
May I checked if I missed out any other steps?
Click to expand...
Click to collapse
Hmm... Maybe you have to do a factory reset / wipe data in recovery.
Just guessing ...