Related
mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordere
d 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow
_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.eamobile.nfsshift_na_wf-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,re
latime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.fridgecat.android.atilt-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/pl.idreams.skyforcereloaded-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.ArtInGames.AirAttackHD-1 vfat ro,dirsync,nosuid,no
dev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
proc list:
Code:
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p27: 12bffe00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p28: 014bfe00 00000200 "devlog"
mmcblk0p29: 00040000 00000200 "pdata"
dev block list:
Code:
brw------- root root 254, 4 2011-04-27 16:25 dm-4
brw------- root root 254, 3 2011-04-27 16:25 dm-3
brw------- root root 254, 2 2011-04-27 16:25 dm-2
brw------- root root 254, 1 2011-04-27 16:25 dm-1
brw------- root root 254, 0 2011-04-27 16:25 dm-0
brw------- root root 179, 65 2011-04-27 16:24 mmcblk1p1
brw------- root root 179, 64 2011-04-27 16:24 mmcblk1
brw------- root root 179, 28 2011-04-27 16:24 mmcblk0p28
brw------- root root 179, 27 2011-04-27 16:24 mmcblk0p27
brw------- root root 179, 26 2011-04-27 16:24 mmcblk0p26
brw------- root root 179, 25 2011-04-27 16:24 mmcblk0p25
brw------- root root 179, 24 2011-04-27 16:24 mmcblk0p24
brw------- root root 179, 23 2011-04-27 16:24 mmcblk0p23
brw------- root root 179, 22 2011-04-27 16:24 mmcblk0p22
brw------- root root 179, 21 2011-04-27 16:24 mmcblk0p21
brw------- root root 179, 20 2011-04-27 16:24 mmcblk0p20
brw------- root root 179, 19 2011-04-27 16:24 mmcblk0p19
brw------- root root 179, 18 2011-04-27 16:24 mmcblk0p18
brw------- root root 179, 17 2011-04-27 16:24 mmcblk0p17
brw------- root root 179, 16 2011-04-27 16:24 mmcblk0p16
brw------- root root 179, 15 2011-04-27 16:24 mmcblk0p15
brw------- root root 179, 14 2011-04-30 08:09 mmcblk0p14
brw------- root root 179, 13 2011-04-30 10:53 mmcblk0p13
brw------- root root 179, 12 2011-04-27 16:24 mmcblk0p12
brw------- root root 179, 11 2011-04-27 16:24 mmcblk0p11
brw------- root root 179, 10 2011-04-27 16:24 mmcblk0p10
brw------- root root 179, 9 2011-04-27 16:24 mmcblk0p9
brw------- root root 179, 8 2011-04-27 16:24 mmcblk0p8
brw------- root root 179, 7 2011-04-27 16:24 mmcblk0p7
brw------- root root 179, 6 2011-04-27 16:24 mmcblk0p6
brw------- root root 179, 5 2011-04-27 16:24 mmcblk0p5
brw------- root root 179, 4 2011-04-27 16:24 mmcblk0p4
brw------- root root 179, 3 2011-04-27 16:24 mmcblk0p3
brw------- root root 179, 2 2011-04-27 16:24 mmcblk0p2
brw------- root root 179, 1 2011-04-27 16:24 mmcblk0p1
brw------- root root 179, 0 2011-04-27 16:24 mmcblk0
brw------- root root 7, 7 2011-04-27 16:24 loop7
brw------- root root 7, 6 2011-04-27 16:24 loop6
brw------- root root 7, 5 2011-04-27 16:24 loop5
brw------- root root 7, 4 2011-04-27 16:24 loop4
brw------- root root 7, 3 2011-04-27 16:24 loop3
brw------- root root 7, 2 2011-04-27 16:24 loop2
brw------- root root 7, 1 2011-04-27 16:24 loop1
brw------- root root 7, 0 2011-04-27 16:24 loop0
drwxr-xr-x root root 2011-04-27 16:24 vold
drwxr-xr-x root root 2011-04-27 16:24 platform
For those of us that dont have this information to hand
yeah thats usefull ;-)
thx dude... so i didn´t have to open the 100. terminal window to check something
i´m to lazy to save this in a txt file... now it´s bookmarked ;-)
regards
i am s-on !
i did this :
i put clockworkmods recovery on my SD root.
then temp root with gingerbreak1.2.
then in a adb shell i type su klik allow, and get temproot
#
then i backup my ori recovery just incase we overwrite it ..
dont worry about phone saying SD not mounted its cached.
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/part21.img
now i flash clockworkmods recovery
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p21
it finish without errors
but when i reboot its not been flashed, allthoe it have made a backup of ori recovery on sdcard.
hope someone can use this info
THX
marsdroid
brokenworm said:
i am s-on !
i did this :
i put clockworkmods recovery on my SD root.
then temp root with gingerbreak1.2.
then in a adb shell i type su klik allow, and get temproot
#
then i backup my ori recovery just incase we overwrite it ..
dont worry about phone saying SD not mounted its cached.
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/part21.img
now i flash clockworkmods recovery
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p21
it finish without errors
but when i reboot its not been flashed, allthoe it have made a backup of ori recovery on sdcard.
hope someone can use this info
THX
marsdroid
Click to expand...
Click to collapse
did you tried to flash the unsecured boot.img i posted in that way? perhaps, if thats work, with that one you are able to root permantly (but still with S-ON). like on the wildfire...
this is a high risk operation... do it on your own risk... it´s just an idea i´ve had while reading your commend. can´t test it myself, cause i don´t have a s-on device here...
loveboatcaptain said:
did you tried to flash the unsecured boot.img i posted in that way? perhaps, if thats work, with that one you are able to root permantly (but still with S-ON). like on the wildfire...
this is a high risk operation... do it on your own risk... it´s just an idea i´ve had while reading your commend. can´t test it myself, cause i don´t have a s-on device here...
Click to expand...
Click to collapse
didnt try with partition 22 "boot" yet..
brokenworm said:
didnt try with partition 22 "boot" yet..
Click to expand...
Click to collapse
it´s a possibility... with that boot.img you are able to get root access in adb.
so you can mount /system r/w and push su files to it. so i think then would be a way to flash recovery after changing boot.img
loveboatcaptain said:
it´s a possibility... with that boot.img you are able to get root access in adb.
so you can mount /system r/w and push su files to it. so i think then would be a way to flash recovery after changing boot.img
Click to expand...
Click to collapse
G:\adb>adb shell
$ su
su
# dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/22.img
dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/22.img
8192+0 records in
8192+0 records out
4194304 bytes transferred in 0.452 secs (9279433 bytes/sec)
# dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p22
dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p22
5676+0 records in
5676+0 records out
2906112 bytes transferred in 0.906 secs (3207629 bytes/sec)
# sync
sync
#
i did not brick
can you plz post some adb mounting commands.. im rusty
nice trying bro, but we been there, and i done that
and failed ;/ i tried every possible way so far...
so if you would like to try something, it has to be something new not done so far
oh for others, yes ppl from unrevoked looked and where like ok thats not gonna work...
bin4ry is still busy with stuff... whenever hes done with it, and it will succeed all the newer devices will be rooted, but we never know if he will succeed
Lets Hope So...
Sent from my HTC Desire S using XDA Premium App
MarylandCookie said:
mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordere
d 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow
_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.eamobile.nfsshift_na_wf-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,re
latime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.fridgecat.android.atilt-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/pl.idreams.skyforcereloaded-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.ArtInGames.AirAttackHD-1 vfat ro,dirsync,nosuid,no
dev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
proc list:
Code:
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p27: 12bffe00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p28: 014bfe00 00000200 "devlog"
mmcblk0p29: 00040000 00000200 "pdata"
dev block list:
Code:
brw------- root root 254, 4 2011-04-27 16:25 dm-4
brw------- root root 254, 3 2011-04-27 16:25 dm-3
brw------- root root 254, 2 2011-04-27 16:25 dm-2
brw------- root root 254, 1 2011-04-27 16:25 dm-1
brw------- root root 254, 0 2011-04-27 16:25 dm-0
brw------- root root 179, 65 2011-04-27 16:24 mmcblk1p1
brw------- root root 179, 64 2011-04-27 16:24 mmcblk1
brw------- root root 179, 28 2011-04-27 16:24 mmcblk0p28
brw------- root root 179, 27 2011-04-27 16:24 mmcblk0p27
brw------- root root 179, 26 2011-04-27 16:24 mmcblk0p26
brw------- root root 179, 25 2011-04-27 16:24 mmcblk0p25
brw------- root root 179, 24 2011-04-27 16:24 mmcblk0p24
brw------- root root 179, 23 2011-04-27 16:24 mmcblk0p23
brw------- root root 179, 22 2011-04-27 16:24 mmcblk0p22
brw------- root root 179, 21 2011-04-27 16:24 mmcblk0p21
brw------- root root 179, 20 2011-04-27 16:24 mmcblk0p20
brw------- root root 179, 19 2011-04-27 16:24 mmcblk0p19
brw------- root root 179, 18 2011-04-27 16:24 mmcblk0p18
brw------- root root 179, 17 2011-04-27 16:24 mmcblk0p17
brw------- root root 179, 16 2011-04-27 16:24 mmcblk0p16
brw------- root root 179, 15 2011-04-27 16:24 mmcblk0p15
brw------- root root 179, 14 2011-04-30 08:09 mmcblk0p14
brw------- root root 179, 13 2011-04-30 10:53 mmcblk0p13
brw------- root root 179, 12 2011-04-27 16:24 mmcblk0p12
brw------- root root 179, 11 2011-04-27 16:24 mmcblk0p11
brw------- root root 179, 10 2011-04-27 16:24 mmcblk0p10
brw------- root root 179, 9 2011-04-27 16:24 mmcblk0p9
brw------- root root 179, 8 2011-04-27 16:24 mmcblk0p8
brw------- root root 179, 7 2011-04-27 16:24 mmcblk0p7
brw------- root root 179, 6 2011-04-27 16:24 mmcblk0p6
brw------- root root 179, 5 2011-04-27 16:24 mmcblk0p5
brw------- root root 179, 4 2011-04-27 16:24 mmcblk0p4
brw------- root root 179, 3 2011-04-27 16:24 mmcblk0p3
brw------- root root 179, 2 2011-04-27 16:24 mmcblk0p2
brw------- root root 179, 1 2011-04-27 16:24 mmcblk0p1
brw------- root root 179, 0 2011-04-27 16:24 mmcblk0
brw------- root root 7, 7 2011-04-27 16:24 loop7
brw------- root root 7, 6 2011-04-27 16:24 loop6
brw------- root root 7, 5 2011-04-27 16:24 loop5
brw------- root root 7, 4 2011-04-27 16:24 loop4
brw------- root root 7, 3 2011-04-27 16:24 loop3
brw------- root root 7, 2 2011-04-27 16:24 loop2
brw------- root root 7, 1 2011-04-27 16:24 loop1
brw------- root root 7, 0 2011-04-27 16:24 loop0
drwxr-xr-x root root 2011-04-27 16:24 vold
drwxr-xr-x root root 2011-04-27 16:24 platform
For those of us that dont have this information to hand
Click to expand...
Click to collapse
THIS SHOULD GET STICKIE.
Sent from my HTC Desire S using XDA Premium App
brokenworm said:
G:\adb>adb shell
$ su
su
# dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/22.img
dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/22.img
8192+0 records in
8192+0 records out
4194304 bytes transferred in 0.452 secs (9279433 bytes/sec)
# dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p22
dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p22
5676+0 records in
5676+0 records out
2906112 bytes transferred in 0.906 secs (3207629 bytes/sec)
# sync
sync
#
i did not brick
can you plz post some adb mounting commands.. im rusty
Click to expand...
Click to collapse
try flashing over Rom manager. it support desire s, i have done with rom manager. it works. (i have s-off)
but rom manager doesn't works with s-on cause it's "destroying" the sdcard mount so rom manager doesn't recognize it
What is the Development Section For?
Things that are NOT development are:
Basic questions
Requests for ETAs
Themes
Posting apps you find on the internet
Comparing ROMs or expressing your opinion, that's what the General Section is for.
Development Section is for:
ROM
KERNEL
RECOVERY
ROOT
HBOOT
RADIO
TWEAKS
etc...
It is more than likely that a thread will already exist covering the ROM that you're intending to post about, whether you're asking for general advice, posting a bug report or making a general observation, please try to use the existing thread rather than creating a new one.
If you are unsure as to whether a thread exists then first look in the Development INDEX in an attempt to identify the thread where your comment, questions or post should possibly be directed.
If you don't yet have enough posts to post within the DEVELOPMENT section, unfortunately these are the rules, please don't spam other threads, there are plenty of other forums within XDA which cover a wide range of topics and these should enable you to make several posts easily, repeating spamming others posts just simply annoys other users - which is something that you don't want to do.
You can always create a question in the GENERAL section and it will be answered. Users will understand why your questions appear to be in the wrong place as we've all been there once, the post count rule is created for a sensible reason, so that new users appreciate that the development section is meant for development only topics and to encourage users to put back into the forum before they take out - as that's how this community works.
Anyone who is unsure what the XDA Forum rules are, should take a few minutes to have read.
[MANDATORY][12 SEP 11] New development naming conventions
Hello, as we're all happily aware, our Forum has recently exploded with development! Which is a wonderful thing, so it would greatly assist everyone (especially the person who maintains the INDEX thread, me ).
If ALL threads, whether they be a RECOVERY, MOD, KERNEL, ROM, RADIO, INDEX, HBOOT or a TWEAK etc. Could have their thread title named in a similar, meaningful, consistent and helpful way.
If you are releasing a thread whether it be a ROM or somethings else or you already have existing threads which do not follow these conventions, it would be very much appreciated if you'd take a moment to ensure that your thread title conforms to this standard. Thanks
[ROM][DATE] [Name] [Version][KERNEL]
[ROM] of course meaning that your release is a ROM
[DATE] must be in the [Day Month Year] format [DD MON YY] ie [09 SEP 11]
[Name] is of course whatever your ROM is called. Try to make it meaningful and unique
[Version] is the version of both your ROM and the ANDROID build. Please be specific.
[KERNEL] what Kernel your ROM uses. Please be specific.
An example a ROM title would be as follows:
[ROM][05 SEP 11] DESIRE S Super Sense 3.0 ROM v1.1 | Working Camera! [v2.3.5] [STOCK v2.6.35.10]
Info from STOCK DESIRE S HBOOT 98.xx.xxxx
Output from following commands on STOCK Desire S
Code:
adb shell mount
adb shell cat proc/emmc
adb shell ls -l /dev/block
mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.eamobile.nfsshift_na_wf-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,re
latime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.fridgecat.android.atilt-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/pl.idreams.skyforcereloaded-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.ArtInGames.AirAttackHD-1 vfat ro,dirsync,nosuid,no
dev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
proc list:
Code:
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p27: 12bffe00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p28: 014bfe00 00000200 "devlog"
mmcblk0p29: 00040000 00000200 "pdata"
dev block list:
Code:
brw------- root root 254, 4 2011-04-27 16:25 dm-4
brw------- root root 254, 3 2011-04-27 16:25 dm-3
brw------- root root 254, 2 2011-04-27 16:25 dm-2
brw------- root root 254, 1 2011-04-27 16:25 dm-1
brw------- root root 254, 0 2011-04-27 16:25 dm-0
brw------- root root 179, 65 2011-04-27 16:24 mmcblk1p1
brw------- root root 179, 64 2011-04-27 16:24 mmcblk1
brw------- root root 179, 28 2011-04-27 16:24 mmcblk0p28
brw------- root root 179, 27 2011-04-27 16:24 mmcblk0p27
brw------- root root 179, 26 2011-04-27 16:24 mmcblk0p26
brw------- root root 179, 25 2011-04-27 16:24 mmcblk0p25
brw------- root root 179, 24 2011-04-27 16:24 mmcblk0p24
brw------- root root 179, 23 2011-04-27 16:24 mmcblk0p23
brw------- root root 179, 22 2011-04-27 16:24 mmcblk0p22
brw------- root root 179, 21 2011-04-27 16:24 mmcblk0p21
brw------- root root 179, 20 2011-04-27 16:24 mmcblk0p20
brw------- root root 179, 19 2011-04-27 16:24 mmcblk0p19
brw------- root root 179, 18 2011-04-27 16:24 mmcblk0p18
brw------- root root 179, 17 2011-04-27 16:24 mmcblk0p17
brw------- root root 179, 16 2011-04-27 16:24 mmcblk0p16
brw------- root root 179, 15 2011-04-27 16:24 mmcblk0p15
brw------- root root 179, 14 2011-04-30 08:09 mmcblk0p14
brw------- root root 179, 13 2011-04-30 10:53 mmcblk0p13
brw------- root root 179, 12 2011-04-27 16:24 mmcblk0p12
brw------- root root 179, 11 2011-04-27 16:24 mmcblk0p11
brw------- root root 179, 10 2011-04-27 16:24 mmcblk0p10
brw------- root root 179, 9 2011-04-27 16:24 mmcblk0p9
brw------- root root 179, 8 2011-04-27 16:24 mmcblk0p8
brw------- root root 179, 7 2011-04-27 16:24 mmcblk0p7
brw------- root root 179, 6 2011-04-27 16:24 mmcblk0p6
brw------- root root 179, 5 2011-04-27 16:24 mmcblk0p5
brw------- root root 179, 4 2011-04-27 16:24 mmcblk0p4
brw------- root root 179, 3 2011-04-27 16:24 mmcblk0p3
brw------- root root 179, 2 2011-04-27 16:24 mmcblk0p2
brw------- root root 179, 1 2011-04-27 16:24 mmcblk0p1
brw------- root root 179, 0 2011-04-27 16:24 mmcblk0
brw------- root root 7, 7 2011-04-27 16:24 loop7
brw------- root root 7, 6 2011-04-27 16:24 loop6
brw------- root root 7, 5 2011-04-27 16:24 loop5
brw------- root root 7, 4 2011-04-27 16:24 loop4
brw------- root root 7, 3 2011-04-27 16:24 loop3
brw------- root root 7, 2 2011-04-27 16:24 loop2
brw------- root root 7, 1 2011-04-27 16:24 loop1
brw------- root root 7, 0 2011-04-27 16:24 loop0
drwxr-xr-x root root 2011-04-27 16:24 vold
drwxr-xr-x root root 2011-04-27 16:24 platform
Info from DESIRE S HBOOT 2.xx.xxxx
Output from following commands on STOCK Desire S
Code:
adb shell mount
adb shell cat proc/emmc
adb shell ls -l /dev/block
mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxdapre.activity-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
proc list:
Code:
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p29: 002ffc00 00000200 "local"
mmcblk0p27: 090ffe00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p30: 014bfe00 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p28: 09800000 00000200 "lib"
dev block list:
Code:
brw------- root root 254, 0 2011-09-11 14:49 dm-0
brw------- root root 179, 65 2011-09-11 14:48 mmcblk1p1
brw------- root root 179, 64 2011-09-11 14:48 mmcblk1
brw------- root root 179, 31 2011-09-11 14:48 mmcblk0p31
brw------- root root 179, 30 2011-09-11 14:48 mmcblk0p30
brw------- root root 179, 29 2011-09-11 14:48 mmcblk0p29
brw------- root root 179, 28 2011-09-11 14:48 mmcblk0p28
brw------- root root 179, 27 2011-09-11 14:48 mmcblk0p27
brw------- root root 179, 26 2011-09-11 14:48 mmcblk0p26
brw------- root root 179, 25 2011-09-11 14:48 mmcblk0p25
brw------- root root 179, 24 2011-09-11 14:48 mmcblk0p24
brw------- root root 179, 23 2011-09-11 14:48 mmcblk0p23
brw------- root root 179, 22 2011-09-11 14:48 mmcblk0p22
brw------- root root 179, 21 2011-09-11 14:48 mmcblk0p21
brw------- root root 179, 20 2011-09-11 14:48 mmcblk0p20
brw------- root root 179, 19 2011-09-11 14:48 mmcblk0p19
brw------- root root 179, 18 2011-09-11 14:48 mmcblk0p18
brw------- root root 179, 17 2011-09-11 14:48 mmcblk0p17
brw------- root root 179, 16 2011-09-11 14:48 mmcblk0p16
brw------- root root 179, 15 2011-09-11 14:48 mmcblk0p15
brw------- root root 179, 14 2011-09-11 17:58 mmcblk0p14
brw------- root root 179, 13 2011-09-11 19:29 mmcblk0p13
brw------- root root 179, 12 2011-09-11 14:48 mmcblk0p12
brw------- root root 179, 11 2011-09-11 14:48 mmcblk0p11
brw------- root root 179, 10 2011-09-11 14:48 mmcblk0p10
brw------- root root 179, 9 2011-09-11 14:48 mmcblk0p9
brw------- root root 179, 8 2011-09-11 14:48 mmcblk0p8
brw------- root root 179, 7 2011-09-11 14:48 mmcblk0p7
brw------- root root 179, 6 2011-09-11 14:48 mmcblk0p6
brw------- root root 179, 5 2011-09-11 14:48 mmcblk0p5
brw------- root root 179, 4 2011-09-11 14:48 mmcblk0p4
brw------- root root 179, 3 2011-09-11 14:48 mmcblk0p3
brw------- root root 179, 2 2011-09-11 14:48 mmcblk0p2
brw------- root root 179, 1 2011-09-11 14:48 mmcblk0p1
brw------- root root 179, 0 2011-09-11 14:48 mmcblk0
brw------- root root 7, 7 2011-09-11 14:48 loop7
brw------- root root 7, 6 2011-09-11 14:48 loop6
brw------- root root 7, 5 2011-09-11 14:48 loop5
brw------- root root 7, 4 2011-09-11 14:48 loop4
brw------- root root 7, 3 2011-09-11 14:48 loop3
brw------- root root 7, 2 2011-09-11 14:48 loop2
brw------- root root 7, 1 2011-09-11 14:48 loop1
brw------- root root 7, 0 2011-09-11 14:48 loop0
drwxr-xr-x root root 2011-09-11 14:48 vold
drwxr-xr-x root root 2011-09-11 14:48 platform
Read before posting
This is the development section for the Desire S.
Things that are NOT development are:
Basic questions
Requests for ETAs
Themes
Posting apps you find on the internet
Development IS for:
ROMs
Kernels
Recovery
Rooting info
etc...
It's good to remind of the functioning of this thread, and subjects.
Same problem are in all forums, it's necessary to make recalls every so often for good functioning.
Developers this is aimed at you.....
Hello ALL,
This is an attempt from me to put something back into the development community from which I take so much. I'm very grateful for the time and effort that you all put into this forum and the ROMS that you develop/re-write and port and I'd very much appreciate it if you would read this post #1 (above) and tell me if you agree/disagree with any of it? If you think that it's missing any keys elements that would be useful or spot any errors then please say, as soon this post will be re-CLOSED.
Apology for the my "first website" look at feel to the thread I'm clearly not a HTML writter as you've now seen for yourselves!
If anyone has has any comments then please PM me.
Thanks
Ben
hi, all!
Modify /init.rc configure file is my plan, in android(linux) box, /(rootfs) locate RAM.
So, modify ramdisk.img(initrd.img) is aim, However, I find any image file except recovery backup image:
[email protected]:/ # /system/xbin/busybox find / -name '*.img'
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/boot.img
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/recovery.img
/system/etc/firmware/modem.img
Did the partition that ramdisk.img save in not mount by kernel ?
My phone information:
all partition:
[email protected]:/ # ll /dev/block/
brw------- root root 254, 0 2012-11-30 22:08 dm-0
brw------- root root 7, 0 2012-11-30 22:07 loop0
brw------- root root 7, 1 2012-11-30 22:07 loop1
brw------- root root 7, 2 2012-11-30 22:07 loop2
brw------- root root 7, 3 2012-11-30 22:07 loop3
brw------- root root 7, 4 2012-11-30 22:07 loop4
brw------- root root 7, 5 2012-11-30 22:07 loop5
brw------- root root 7, 6 2012-11-30 22:07 loop6
brw------- root root 7, 7 2012-11-30 22:07 loop7
brw-rw---- root system 179, 0 2012-11-30 22:07 mmcblk0
brw------- root root 179, 32 2012-11-30 22:07 mmcblk0boot0
brw------- root root 179, 64 2012-11-30 22:07 mmcblk0boot1
brw------- root root 179, 1 2012-11-30 22:07 mmcblk0p1
brw------- root root 179, 2 2012-11-30 22:07 mmcblk0p2
brw------- root root 179, 3 2012-11-30 22:07 mmcblk0p3
brw------- root root 179, 4 2012-11-30 22:07 mmcblk0p4
brw------- root root 179, 5 2012-11-30 22:07 mmcblk0p5
brw------- root root 179, 6 2012-11-30 22:07 mmcblk0p6
brw------- root root 179, 96 2012-11-30 22:07 mmcblk1
brw------- root root 179, 97 2012-11-30 22:07 mmcblk1p1
drwxr-xr-x root root 2012-11-30 22:07 platform
drwxr-xr-x root root 2012-11-30 22:07 vold
mounted partition:
[email protected]:/ # mount|/system/xbin/busybox grep mmc
/[email protected] /system ext4 ro,noatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
had be linked partition:
[email protected]:/ # ll / |/system/xbin/busybox mmc
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 08:00 [email protected]_ro -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p5
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
[email protected]:/ #
My phone do not use mtd ?
what other technology my phone used? and, what can I locate recovery and boot partition ?
Ramdisk is inside boot.img, you must use dsixda's kitchen to decompile it.
Sent from my PC36100 using xda app-developers app
Yes, the ramdisk is inside the boot.img. The recovery.img contains its own ramdisk. The partition is a basic format created just for android. The first 0x30ish bytes contain offsets and sizes for the kernel image, ramdisk, kernel command line, and stuff like that. And no, the ramdisk is not compiled; you do no decompile it. It is compressed. You can pull the ramdisk out of the partition and decompress it using standard commandline tools.
i have a boot.img with a size of 13mb, when i unpack it , it produce two files the boot.im-kernel and boot.img-ramdisk.cpio.gz,and it became much less in size, together they where 5.3mb and when i repack it using mkbootimg and flash it it wont flash. .
what i do to repack is , on the folder containing the ramdisk and kernel and the mkbootimg ' i typed mkbootimg --kernel "the kernel" --ramdisk "the disk" -o boot.img . .then i got an output boot.img
now when i flash it using fastboot
i type fastboot device.. then it shows my device.. and then i typed fastboot boot 'the boot.img i repack after i unpack'
then its says it been copied and rebooting. .but the device is still in downloading mode. .so i try again typed fastboot boot 'the boot.img' and now it says fastboot waiting for device. .so i think it was disconnected
now again i repack the kernel and ramdisk but with different command
i typed mkbootimg --kernel 'kerne' --ramdisk 'ramdisk' and i include other commands like --base --cmdline then -o boot.img
then i get the results boot.img again the flash it using fastboot
but this time it vibrates and turn off but didnt light up and in computer it mounts different partitions like sd mode
now they say there is a specific procedure of compiling a boot.img base on different boot.img
they also say that when i unpack it the command just discarded the garbage or other files
now my question is if theres any how would i know and where would i find the specific procedure of repacking my boo.imgs
and the missing files i think they were neccessary if there any missing file. how would i get it and how would i know what it is
my devices is running ics , cpu msm825, kernel 3.0..
this is my partition table and i dont understand any of it or which is which
i use abootimg and in boot.cfg this is whats written might be helpful
bootsize = 0xd42000
pagesize = 0x1000
kerneladdr = 0x208000
ramdiskaddr = 0x1508000
secondaddr = 0x1100000
tagsaddr = 0x200100
name =
cmdline = androidboot.hardware=qcom loglevel=1
in adb shell i ran
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 150 mmcblk0p2
179 3 40960 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 13576 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 466666 mmcblk0p12
179 13 1970176 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 102400 mmcblk0p15
179 16 13576 mmcblk0p16
179 17 20 mmcblk0p17
179 18 1048576 mmcblk0p18
179 19 1000 mmcblk0p19
179 20 111441 mmcblk0p20
179 32 1927168 mmcblk1
179 33 1926144 mmcblk1p1
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
debugfs /mnt/debugfs debugfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 ro,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:18 /mnt/emmc vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=continue 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=continue 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=continue 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 170.7M 64.0K 170.7M 4096
/mnt/asec 170.7M 0.0K 170.7M 4096
/mnt/obb 170.7M 0.0K 170.7M 4096
/system 448.5M 375.4M 73.1M 4096
/data 1.8G 181.5M 1.7G 4096
/persist 9.8M 4.0M 5.8M 4096
/cache 98.4M 4.0M 94.4M 4096
/mnt/emmc 1013.6M 658.5M 355.1M 4096
/mnt/sdcard 1.8G 1.8G 9.1M 4096
/mnt/secure/asec 1.8G 1.8G 9.1M 4096
[email protected]:/ # ls -la
drwxr-xr-x root root 2013-12-23 18:04 acct
drwxrwx--x system cache 1970-01-01 08:00 cache
-rwxr-x--- root root 190772 1970-01-01 08:00 charger
dr-x------ root root 2013-12-23 18:04 config
lrwxrwxrwx root root 2013-12-23 18:04 d -> /sys/kernel/debug
drwxrwxr-x system system 2013-12-23 18:04 data
-rw-r--r-- root root 151 1970-01-01 08:00 default.prop
drwxr-xr-x root root 2013-12-23 18:08 dev
lrwxrwxrwx root root 2013-12-23 18:04 emmc -> /mnt/emmc
lrwxrwxrwx root root 2013-12-23 18:04 etc -> /system/etc
-rwxr-x--- root root 182020 1970-01-01 08:00 init
-rwxr-x--- root root 2344 1970-01-01 08:00 init.goldfish.rc
-rwxr-x--- root root 8772 1970-01-01 08:00 init.qcom.class_core.sh
-rwxr-x--- root root 4529 1970-01-01 08:00 init.qcom.class_main.sh
-rwxr-x--- root root 16886 1970-01-01 08:00 init.qcom.rc
-rwxr-x--- root root 4570 1970-01-01 08:00 init.qcom.sh
-rwxr-x--- root root 27316 1970-01-01 08:00 init.qcom.usb.rc
-rwxr-x--- root root 5512 1970-01-01 08:00 init.qcom.usb.sh
-rwxr-x--- root root 24437 1970-01-01 08:00 init.rc
-rwxr-x--- root root 2680 1970-01-01 08:00 init.target.rc
drwxrwxr-x root system 2013-12-23 18:04 mnt
-rwxr-x--- root root 67104 1970-01-01 08:00 nv_set
drwxrwx--x system system 1970-01-01 08:00 persist
dr-xr-xr-x root root 1970-01-01 08:00 proc
drwxr-xr-x root root 1970-01-01 08:00 res
-rwxr-x--- root root 63472 1970-01-01 08:00 rmt_storage_recovery
drwx------ root root 2013-01-22 10:18 root
drwxr-x--- root root 1970-01-01 08:00 sbin
lrwxrwxrwx root root 2013-12-23 18:04 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-12-23 18:04 sys
drwxrwxr-x root root 2013-12-22 06:15 system
-rw-r--r-- root root 272 1970-01-01 08:00 ueventd.goldfish.rc
-rw-r--r-- root root 9232 1970-01-01 08:00 ueventd.rc
lrwxrwxrwx root root 2013-12-23 18:04 vendor -> /system/vendor
can anyone help me with this?
First how to find location of boot image in device? I want to take current boot image. Do modifications and later flash that boot image back to device.
I have searched correct block device and did some image files with dd command but they were not boot images. I tried with several tools.
Here is some listing from the phone with adb shell commands.
Code:
[email protected]:/proc # cat partitions
major minor #blocks name
179 0 30512256 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 665600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 1572864 mmcblk0p7
179 8 28077696 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
Code:
[email protected]:/ # ls -l /emm*
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p7
[email protected]:/ #
Code:
[email protected]:/dev/block # ls -al
brw------- root root 7, 0 2014-03-12 12:54 loop0
brw------- root root 7, 1 2014-03-12 12:54 loop1
brw------- root root 7, 2 2014-03-12 12:54 loop2
brw------- root root 7, 3 2014-03-12 12:54 loop3
brw------- root root 7, 4 2014-03-12 12:54 loop4
brw------- root root 7, 5 2014-03-12 12:54 loop5
brw------- root root 7, 6 2014-03-12 12:54 loop6
brw------- root root 7, 7 2014-03-12 12:54 loop7
brw-rw---- root system 179, 0 2014-03-12 12:54 mmcblk0
brw------- root root 179, 32 2014-03-12 12:54 mmcblk0boot0
brw------- root root 179, 64 2014-03-12 12:54 mmcblk0boot1
brw------- root root 179, 1 2014-03-12 12:54 mmcblk0p1
brw-r----- root system 179, 2 2014-03-12 12:54 mmcblk0p2
brw------- root root 179, 3 2014-03-12 12:54 mmcblk0p3
brw------- root root 179, 4 2014-03-12 12:54 mmcblk0p4
brw------- root root 179, 5 2014-03-12 12:54 mmcblk0p5
brw------- root root 179, 6 2014-03-12 12:54 mmcblk0p6
brw------- root root 179, 7 2014-03-12 12:54 mmcblk0p7
brw------- root root 179, 8 2014-03-12 12:54 mmcblk0p8
drwxr-xr-x root root 2014-03-12 12:54 platform
[email protected]:/dev/block #
/dev/block/mmcblk0boot0 looked promising but I made image of it by by command dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot.img
But the image was not boot image.
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /storage/sdcard0 vfat rw,dirsync,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ #
I can make full image by dding /dev/block/mmcblk0 but it would be better to get the parts separately.
Is there easy way to find where the boot image is located?
I checked block device sizes
/dev/block/mmcblk0p8 is the internal flash area for user, about 28G. Boot image boot loader etc must be in mmcblk0p1 - mmcblk0p7
Size of the block devices
Code:
/dev/block/mmcblk0 31244550144
/dev/block/mmcblk0boot0 2097152
/dev/block/mmcblk0boot1 2097152
/dev/block/mmcblk0p1 1024
/dev/block/mmcblk0p2 10485760
/dev/block/mmcblk0p3 10485760
/dev/block/mmcblk0p4 6291456
/dev/block/mmcblk0p5 681574400
/dev/block/mmcblk0p6 132120576
/dev/block/mmcblk0p7 1610612736
/dev/block/mmcblk0p8 28751560704
/dev/block/mmcblk1 8178892800
I got these with script
Code:
#!/system/bin/sh
command="/sdcard/busybox blockdev --getsize64"
for f in /dev/block/mm*
do
result=`$command $f`
result="$f \t $result"
echo $result
done
Via Terminal Emulator:
"su
cat /proc/partitions"
When again other command: dd if=/dev/block/(boot_partition_which_showed under /proc/partitions) of=/sdcard/boot.img
Root your device and try MtkDroidTools.
Use MTK SP_Flash_tool to flash image back.
In proc partitions there were two boot related devices listed
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
I made images from both of those but there was nothing inside the images which looked like boot image.
I found that there is /dev/bootimage
Code:
[email protected]:/ # ls -l /dev/boo*
crw-r----- root system 234, 10 2013-01-01 06:30 bootimg
I made image from that. The image is 4.3G. Very large. Anyway I found bootimage inside that. Then I made another smaller one with
Code:
# dd if=/dev/bootimg of=/sdcard/testboot.img count=12000
I can unpack that image in linux with tool unpack-MT65xx.pl. I tried to repack the exact same files without modifying. But repacking the image with repack-MT65.pl generates file which is different.
cnexpat said:
Is there easy way to find where the boot image is located?
Click to expand...
Click to collapse
Looking for same