You could probably use cygwin to achieve this. So installing repo, and then compiling mkbootimg for windows through CM
and then use all these binaries in the same way via that
on my defy android 2.1 phone.
# cat /proc/mtd
dev: size erasesize name
nothing, where is my ramdisk?
i want to modify /init.rc
please help, and thank you.
I tried to unpack boot.img of android.. The guide says to execute this command
Code:gunzip -c name.img | cpio -i
But executing this command fromthe terminal the result is:
Code:gzip: name.img: not in gzip format cpio: premature end of archive
What am I doing wrong?
open (BOOTIMGFILE, "$bootimgfile") #....
[B]binmode (BOOTIMGFILE);[/b]
Can you teach me how to unpack repack recovery.img from qualcomm and broadcomm chipset???
tell me what the script or command to unpack and to repack recovery.img another mediatek chipsets. and what program that should i install, i use window7.
could you teach me jianC broo...
Sent from my Nexian-A895 using Tapatalk 2
Sent from my Nexian-A895 using Tapatalk 2
#cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
+-----------------+
| boot header | 1 page
+-----------------+
| kernel | n pages
+-----------------+
| ramdisk | m pages
+-----------------+
| second stage | o pages
+-----------------+
n = (kernel_size + page_size - 1) / page_size
m = (ramdisk_size + page_size - 1) / page_size
o = (second_size + page_size - 1) / page_size
0. all entities are page_size aligned in flash
1. kernel and ramdisk are required (size != 0)
2. second is optional (second_size == 0 -> no second)
./init.trout.rc
./default.prop
./proc
./dev
./init.rc
./init
./sys
./init.goldfish.rc
./sbin
./sbin/adbd
./system
./data
./res
./res/images
./res/images/progress_bar_empty_left_round.bmp
./res/images/icon_firmware_install.bmp
./res/images/indeterminate3.bmp
./res/images/progress_bar_fill.bmp
./res/images/progress_bar_left_round.bmp
./res/images/icon_error.bmp
./res/images/indeterminate1.bmp
./res/images/progress_bar_empty_right_round.bmp
./res/images/icon_firmware_error.bmp
./res/images/progress_bar_right_round.bmp
./res/images/indeterminate4.bmp
./res/images/indeterminate5.bmp
./res/images/indeterminate6.bmp
./res/images/progress_bar_empty.bmp
./res/images/indeterminate2.bmp
./res/images/icon_unpacking.bmp
./res/images/icon_installing.bmp
./sbin/recovery
gunzip -c ../your-ramdisk-file | cpio -i
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel your-kernel-file --ramdisk newramdisk.cpio.gz -o mynewimage.img
adb push ./mynewimage.img /sdcard
# cat /dev/zero >> /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/mynewimage.img
Where does boot.img flash? What is the corresponding part of the system?
For your command...
Code:cat /dev/zero >> /dev/mtd/mtd2
Do you mean
Code:cat /dev/zero > /dev/mtd/mtd2
?
The idea being that you erase flash in the version with one '>', whereas you... append to the end of a device in the version with two '>'s? I can see the utility of erasing flash with one '>' but appending seems... odd. Am I missing something?
Is this any different than using the Dalvik Debug Monitor (DDMS) file manager found the the Android SDK? I'm able to push, pull, and delete files on my G1 with no problem.