Develop Bugs

How to use *.zip to change the boot/ devtree/ recovery

I have written a updater-script to do this, but I am not sure whether it works. Can anybody give me some suggestion?
Code:
ui_print("Changing Moto Rom");
ui_print("Updating boot");
show_progress(0.330000,2);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk1p15"),
delete("/tmp/boot.img"));
ui_print("Updating devtree");
show_progress(0.330000,2);
assert(package_extract_file("devtree.img", "/tmp/devtree.img"),
write_raw_image("/tmp/devtree.img", "/dev/block/mmcblk1p12"),
delete("/tmp/devtree.img"));
ui_print("Updating stock recovery");
show_progress(0.340000,2);
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "/dev/block/mmcblk1p16"),
delete("/tmp/recovery.img"));
ui_print("Changed");
And are the three img files generated only by change names of CG35.smg/ CG61.smg/ CG47.smg?
After we extract the smg files from a sbf file, we have many CG??.smg.
CG35.smg refers to the partition of boot.
CG61.smg refers to the partition of devtree.
CG47.smg refers to the partition of recovery.
Now I have two problems.
1. Does the boot&devtree&recovery in zip file have the same format as CG35&CG61&CG47? Such as the yaffs or ext?
2. Shall we use the code above to replace the partitions successfully considering the not-open bootloader and the secure signature?

i will try!

CG35.smg and CG47.smg are different. CG47 is Recovery and contains recovery software does not boot system, CG35 is boot and does not have ny recovery stuff only boots the system.
But I don't know anything about devtree and devtree_backup. but the name indicate that devtree_backup is a exact copy of devtree.
EDIT: CG35 and CG47 have different SHA1 hash and different signatures when extracted from the same (original) SBF file. if CG47 would have been a copy of CG35 the SHA1 hash would have been the same.

Febernacke said:
CG35.smg and CG47.smg are different. CG47 is Recovery and contains recovery software does not boot system, CG35 is boot and does not have ny recovery stuff only boots the system.
But I don't know anything about devtree and devtree_backup. but the name indicate that devtree_backup is a exact copy of devtree.
EDIT: CG35 and CG47 have different SHA1 hash and different signatures when extracted from the same (original) SBF file. if CG47 would have been a copy of CG35 the SHA1 hash would have been the same.
Click to expand...
Click to collapse
I am afraid you misunderstood me. I know that CG35 and CG47 are different.
After we extract the smg files from a sbf file, we have many CG??.smg.
CG35.smg refers to the partition of boot.
CG61.smg refers to the partition of devtree.
CG47.smg refers to the partition of recovery.
Now I have two problems.
1. Does the boot&devtree&recovery in zip file have the same format as CG35&CG61&CG47? Such as the yaffs or ext?
2. Shall we use the code above to replace the partitions successfully considering the not-open bootloader and the secure signature?

iaio72 said:
i will try!
Click to expand...
Click to collapse
I am waiting for your good news!

Just a warning guys, those CGXX.smg files are not the same as the .img files. SBF files pad the partitions with nulls so they reach multiples of 1024 bytes. The image files themselves can be extracted from the .smg files by removing the extra padding nulls from the end. Hex editors are your friend.

[Q] is there anyway to manually make a md5?

i've backuped, but when I tried to restore, the md5 was gone..
Is there anyway I can cheat on cwm or make a md5 ?

You can copy the file on your computer and use tools like MD5summer to create the MD5 file and then copy the *.md5 to your phone.

I dont know for which file I need to make the md5.. there is 7 files..(boot, cache, system.. etc)

the MD5 file looks like this one:
XXXXXXXXXXXXXXXXXXXXXXXXXXX boot.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX cache.yaffs2.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX data.yaffs2.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX recovery.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX sd-ext.ext3.tar
XXXXXXXXXXXXXXXXXXXXXXXXXXX system.yaffs2.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX .android_secure.vfat.tar
you have to calculate the MD5 for each img or tar file and the replace xxxx with the obtained MD5
---------- Post added at 02:50 PM ---------- Previous post was at 02:48 PM ----------
forget to tell that:
you can save the above text using notpad in a file named nandroid.md5 and put it in your backup folder

From a terminal emulator
Code:
cd /sdcard/clockworkmod/backup/backupname
Where backupname is the name of your backup and this is the location of your backup.
Then:
Code:
md5sum *img > nandroid.md5

[dev]How to Un/Re/Pack a Boot.blob and unyaff a boot.img

Technically i have to give credit to scott crossler
www.scottsroms.com
for showing me the method
and then i came upon turges
faq
Thanks Turge and Scott and whomever created these blobpacktools
but since i keep getting pms
and im sure you do to
scott
Here are the steps for repacking the boot.img. Some involve running the commands via cygwin, others involve running them via the Windows Command Prompt.
The instructions for installing cygwin, extracting and repacking the boot.img were found here: http://www.freeyourandroid.com/guide...ot-img-windows
Once you have setup cygwin, extract the attached files in a folder under your "home" folder in cygwin.
Also unzip blob tools into the same folder as your boot.blob
1.
Code:
copy boot.blob to the same folder and run the following via
the Windows Command Prompt to extract the boot.img from the boot.blob:
BlobUnpack.exe boot.blob
ren boot.blob.LNX boot.img
which will create boot.img
2.
Code:
From the cygwin bash terminal window,
switch to the same folder and run the following
to extract the ramdisk from the boot.img:
./extractboot boot.img
You now have an out/ramdisk folder
that contains the files you want to edit.
3.
Code:
Once done, repack the ramdisk and kernel into boot_new.img
with the following command (via cygwin once again):
./packboot
4.
Code:
then from the Command Prompt repack boot_new.img
into boot2.blob using the following:
blobpack -s boot2.blob LNX boot_new.img
5.
Code:
You can now flash the boot.blob to the staging
partition via a command in updater-script:
Code:
package_extract_file("/boot.blob", "/dev/block/mmcblk0p4");
or by using adb while in recovery/android:
Code:
dd if=/sdcard/boot2.blob of=/dev/block/mmcblk0p4

Lastly the rundown is like this
if you want to take a ota blob
and extract the contents for a raw base
and a raw kernel
1
take the ota and extract the blob file and place
in your folder with blobtools
2. then run
Code:
blobunpack.exe blob
Which now creates
Blob.APP =System.img (can be renamed system.img and unyaffed in the kitchen)or straight cygwin
Blob.sos=Recovery Img
Blob.Ebt=Bootloader information
Blob.Lnx=kernel (can also just be renamed boot.img and unyaffed in kitchen)
Blob.pt=Partition info
so to repack lets say your custom remade image
and your custom kernel
and a recovery of your choice
run
Code:
blobpack.exe -s blob lnx boot.img sos twrp.blob app system.img
then simply take the blob replace in the ota file
and flash in recovery
and it should flash a rom packed as a blob

Hi!
...also you can flash the new boot.blob via fastboot mode
>fastboot-i 0x0B05 flash boot boot.blob
:good:

Call me stupid, but what does repacking the boot.img do? I never pm'ed you, but what would we gain from this. a lil lost

unpacking a boot.img allows you to take a stock already built kernel
and make specific changes to the ramdisk
more specifically
default.prop
can make kernel insecure
debuggable
bootanimation enabled
blah blah blah
and init.rc
but also
cardhu
and goldfish.rc
and init.trace
and init.usb
then repacked and good to flash

seanzscreams said:
Lastly the rundown is like this
if you want to take a ota blob
and extract the contents for a raw base
and a raw kernel
1
take the ota and extract the blob file and place
in your folder with blobtools
2. then run
Code:
blobunpack.exe blob
Which now creates
Blob.APP =System.img (can be renamed system.img and unyaffed in the kitchen)or straight cygwin
Blob.sos=Recovery Img
Blob.Ebt=Bootloader information
Blob.Lnx=kernel (can also just be renamed boot.img and unyaffed in kitchen)
Blob.pt=Partition info
so to repack lets say your custom remade image
and your custom kernel
and a recovery of your choice
run
Code:
blobpack.exe -s blob lnx boot.img sos twrp.blob app system.img
then simply take the blob replace in the ota file
and flash in recovery
and it should flash a rom packed as a blob
Click to expand...
Click to collapse
Hi!
For a linux (Ubuntu) machine you can easily unpack blob.APP
> sudo mkdir mnt
> sudo mount -o loop blob.APP mnt
- now in your mnt directory , you will have /system ! :good:

Hi,
My TF300tl can't unlock bootloader. so can I use this way to pack custom ROM ( cm11, liplop...) as official ROM to flash for my tablet ?

konnichiwa said:
Hi,
My TF300tl can't unlock bootloader. so can I use this way to pack custom ROM ( cm11, liplop...) as official ROM to flash for my tablet ?
Click to expand...
Click to collapse
I wouldn't think so, as the ROM would have to be signed to be official

Need stock 4.3.1 kernel

I need the official tmob noteII jb 4.3.1 kernel in tar or zip can anyone give me a link please
or latest official kernel

(Assuming you're running under Windows.)
Download the complete stock ROM from sammobile or the like. You could also get the boot.img from a repacked zip here, but YMMV.
Extract boot.img from the .tar.md5 file with a compression utility that handles tar archives, 7-Zip works well for this. (The error message about the end of the file is normal, that's because the MD5 hash isn't part of a normal tar archive.)
Get cygwin, namely its tar.exe command. With boot.img in your Cygwin home directory, from the Cygwin shell run:
tar -H ustar -cf youroutputfilename.tar boot.img
As an aside, my Windows-based setup to make Odin-flashable images is fancier than that. I've added the Cygwin binaries to my PATH environment variable (jury is still out on whether that's a good idea overall, but it works for a number of tricks) and I've created a script named tarodin.cmd in that directory which contains the following command:
tar -H ustar -cf %1 sboot.bin tz.img md5.img efs.img m9kefs1.bin m9kefs2.bin m9kefs3.bin param.bin boot.img recovery.img system.img modem.bin tombstones.img cache.img hidden.img userdata.img
The missing files just cause an error to show but the file itself works perfectly. I haven't bothered adding the MD5 hash, but it could be done.
The other way is to take a working t0lte kernel zip and substitute the boot.img in it then flash through recovery.
Good luck,
Darkshado

Got Kernel working
Darkshado said:
(Assuming you're running under Windows.)
Download the complete stock ROM from sammobile or the like. You could also get the boot.img from a repacked zip here, but YMMV.
Extract boot.img from the .tar.md5 file with a compression utility that handles tar archives, 7-Zip works well for this. (The error message about the end of the file is normal, that's because the MD5 hash isn't part of a normal tar archive.)
Get cygwin, namely its tar.exe command. With boot.img in your Cygwin home directory, from the Cygwin shell run:
tar -H ustar -cf youroutputfilename.tar boot.img
As an aside, my Windows-based setup to make Odin-flashable images is fancier than that. I've added the Cygwin binaries to my PATH environment variable (jury is still out on whether that's a good idea overall, but it works for a number of tricks) and I've created a script named tarodin.cmd in that directory which contains the following command:
tar -H ustar -cf %1 sboot.bin tz.img md5.img efs.img m9kefs1.bin m9kefs2.bin m9kefs3.bin param.bin boot.img recovery.img system.img modem.bin tombstones.img cache.img hidden.img userdata.img
The missing files just cause an error to show but the file itself works perfectly. I haven't bothered adding the MD5 hash, but it could be done.
The other way is to take a working t0lte kernel zip and substitute the boot.img in it then flash through recovery.
Good luck,
Darkshado
Click to expand...
Click to collapse
Thanks bud used the Kernel and subbed it in zip that did the trick God Bless

[How to] Fix md5 mismatch on nandroid backup/restore

Hi all,
Is anybody got stuck their nandroid recovery due to md5 mismatch ???
I have some solutions .Before that let's check why the mismatch came .
You are getting the MD5 mis-match error because the MD5 checksums in the nandroid.md5file do not match the checksums of one or more of the system.img,data.img, orboot.img etc. files in your Nandroid's backup directory.
Solutions :thumbup:
1 . Open Terminal emulator and put the following code
adb shell
_______________________________________________
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53//change this by your backup folder name .
# rm nandroid.md5
# md5sum *img > nandroid.md5
_________________________________________________
2 . Open nandroid.md5 using text editor .Just edit the values in nandroid backup by original value of each .tar or .zip files
Remember Changing values of nandroid.md5 will affect your backup .
It is something like
_________________________________________________
xxxxxxxxxxxxxxxxxx
recovery.img
xxxxxxxxxxxxxxxxxxx
boot.img
xxxxxxxxxxxxxxxxxxx
system.ext4.tar
xxxxxxxxxxxxxxxxxxx
_________________________________________________
Edit xxxxxx with the currect md5 value of each .
3 . Still the problem is there or there is no nandroid.md5 just clear the values of nandroid.md5 using text editor or create a empty nandroid.md5 .
Your problem is now solved . :sly:
Sent from my GT-S7562 using XDA Premium 4 mobile app

Still not working...
I tried the first an the third one and nothing worked... I can't try the second because i deleted my original md5 file and don't have those numbers.
The first solved that problem but created a "error while restoring /data" message every time so i replaced it with a blank file and now it says md5 mismatch
I have no idea, and need this backup
Thanks!

dmanmatt10 said:
I tried the first an the third one and nothing worked... I can't try the second because i deleted my original md5 file and don't have those numbers.
The first solved that problem but created a "error while restoring /data" message every time so i replaced it with a blank file and now it says md5 mismatch
I have no idea, and need this backup
Thanks!
Click to expand...
Click to collapse
Use advanced restore option and restore all files except data .
Hope I helped
Sent from my GT-S7562 using XDA Premium 4 mobile app