Greetings,
I'm attempting to dump the modem from a Sprint-flavored Galaxy Tab. We can't seem to get BML12 dumped over in the Tab forums. Unfortunately, the factory firmware updater isn't available for the Tab yet.
We are currently using the the modem from the Epic 4G (SPH-D700-DK28-8Gb-REL) which works for data, but borks GPS.
The partition map seems correct
Code:
# ls -l /dev/block/bml*
ls -l /dev/block/bml*
brw------- root root 137, 0 2010-12-18 07:47 bml0!c
brw------- root root 137, 1 2010-12-18 07:47 bml1
brw------- root root 137, 10 2010-12-18 07:47 bml10
brw------- root root 137, 11 2010-12-18 07:47 bml11
brw-rw-rw- radio radio 137, 12 2010-12-18 07:47 bml12
brw------- root root 137, 2 2010-12-18 07:47 bml2
brw------- root root 137, 3 2010-12-18 07:47 bml3
brw------- root root 137, 4 2010-12-18 07:47 bml4
brw------- root root 137, 5 2010-12-18 07:47 bml5
brw------- root root 137, 6 2010-12-18 07:47 bml6
brw------- root root 137, 7 2010-12-18 07:47 bml7
brw------- root root 137, 8 2010-12-18 07:47 bml8
brw------- root root 137, 9 2010-12-18 07:47 bml9
Code:
ls -l /dev/block/stl*
brw------- root root 138, 1 2010-12-18 07:47 stl1
brw------- root root 138, 10 2010-12-18 07:47 stl10
brw------- root root 138, 11 2010-12-18 07:47 stl11
brw------- root root 138, 12 2010-12-18 07:47 stl12
brw------- root root 138, 2 2010-12-18 07:47 stl2
brw------- root root 138, 3 2010-12-18 07:47 stl3
brw------- root root 138, 4 2010-12-18 07:47 stl4
brw------- root root 138, 5 2010-12-18 07:47 stl5
brw------- root root 138, 6 2010-12-18 07:47 stl6
brw------- root root 138, 7 2010-12-18 07:47 stl7
brw------- root root 138, 8 2010-12-18 07:47 stl8
brw------- root root 138, 9 2010-12-18 07:47 stl9
Using the following command to dump the modem on the Tab and Epic 4G produce empty files (all FF):
dd if=/dev/block/bml12 of=/sdcard/modem.bin
or
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
Questions:
1. Has anyone successfully dumped the modem on the Epic 4G?
2. What is the proper process to get the dump?
Your large-screen cousins thank you for your time
SOLUTION for LOST IMEI in Galaxy 3 / GT-i5800 / GT-i5801
1. Check that you are ROOTed (probable), insert an SD card, and connect with USB Debugging enabled.
2. Run a terminal. ("adb shell")
3. Issue the commands below:
$ su
then
# dd if=/dev/block/stl4 of=/sdcard/i5800xt.dat bs=16 skip=4
..or (ONLY if the last one failed with "/dev/block/stl4: cannot open for read: No such file or directory")
# dd if=/dev/block/mtl4 of=/sdcard/i5800xt.dat bs=16 skip=4
NOTE that if step 3 (last) fails, probably means you have a damaged NAND chip.
4. Exit terminal (ctrl-c, or more elegantly, typing 'exit' twice.
5. Copy the file 'i5800xt.dat' from the SD card with any method (reader or adb)
6. I can calculate/verify hash now - which is not checked in phone anyway - so no photo necessary anymore!
7. Create a ZIP / RAR archive with the i5800xt.dat from (5)
8. Send me a PM for a mail address to which you can send your archive. I will need the IMEI as well (in the email text is OK)
9. I will send you your repaired nv_data.bin.
DO NOT ATTACH YOUR FILES HERE. OR YOUR PHONE WILL BE BARRED.
DO NOT send me email or bump the thread for your sake of 'urgency'! Everyone has things to do for living.
NOTE that this NOT necessarily solves your problem..
That's why this service is FREE *for a period* but NO WARRANTY.
Also, i5801 processing is added now (being in alpha stage)
However, I just solved my problem.
And, it is unlikely to get any worse, definitely.
My method has the definite advantage over others (box, etc) in that - when it works - you won't overwrite your battery and RF calibration data (symptoms: weaker reception, shorter battery life).
Of course, if they are already gone, nothing can really be done about it.
what about i5801
Same device...
flores.diane02 said:
what about i5801
Click to expand...
Click to collapse
I think the i5800 ONLY! in the title might be a hint...
i5801 is the same phone as i5800.
If this method works with 00 it will work with 01 too.
lol.
They are not the same. they would be called the same if they were the same. There are differences, however minute they are. It is not true that everything that works for i5800 will work for i5801.
i5800 software works on i5801, so they are the same.
The only difference that i5801 has touch sensitive keys.
ALl custom roms and i5800 boot loader works with 01.
...has anyone tried this, and does this really work, or is he simply collating IMEI numbers
stubborn_d0nkey said:
I think the i5800 ONLY! in the title might be a hint...
Click to expand...
Click to collapse
Well, i5801 may qualify as well!!
thanks for pointing this out
But NO i5700 etc
disconsolate said:
...has anyone tried this, and does this really work, or is he simply collating IMEI numbers
Click to expand...
Click to collapse
Sorry to point this out, but I am a member here for 6 years..
Wouldn't you think this would not make sense "collecting IMEI numbers" for 6 years?
Anyway, this IMEI thing has gone WAY too far..
Anyone doing this longer than 2 years must be able to calculate checkdigit.
I just take the TAC part (first 6 digits), then I can generate as many valid IMEIs as I wish, so this does not make sense only for noobs..
Not mentioning that one forgot to read the actual procedure.
For this half-rebuild procedure, I just need the IMEI for verification purposes.
Thus I trust anyone else just that much they trust me..
But I can decode the IMEI from the dump, so IMEI is asked ONLY for comparison - anyone lying should tell a definite smelling or otherwise interesting story - or not bother at all.
I Have this:
C:\Users\xxx>adb devices
List of devices attached
xxxxxxxxx device
C:\Users\xxx>adb shell
$ su
su
# dd if=/dev/block/mtl4 of=/sdcard/i5800xt.dat bs=16 skip=4
dd if=/dev/block/mtl4 of=/sdcard/i5800xt.dat bs=16 skip=4
/dev/block/mtl4: cannot open for read: No such file or directory
then please post here your version (*#1234#) along with the output of command of "mount", and the list of "ls -a -l /dev/block".
adding a "CODE" tag here around a longer output should be wise.
(nb. mtl4 is lowercase MTL4, no big i, or similar)
My firmware is:
PDA: i5800XXJPF
PHONE: i5800XXJP4
CSC i5800OXXJPF
Build Info: 2010.12
Code:
---------------------------------------------------------
C:\Users\xxx>adb devices
List of devices attached
xxxxxxxxxxxxx device
C:\Users\xxx>adb shell
$ mount
mount
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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl6 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=cp437 0 0
/dev/block/stl4 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=cp437 0 0
/dev/block/mmcblk0p2 /system/sdext ext2 rw,noatime,nodiratime,errors=continue 0
0
/dev/loop1 /data ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/block/stl7 /system/sddata rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=cp437 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
$
$ ls -a -l /dev/block
ls -a -l /dev/block
brw------- root root 138, 5 2011-02-17 14:32 stl5
brw------- root root 138, 2 2011-02-17 14:32 stl2
brw------- root root 138, 1 2011-02-17 14:32 stl1
brw------- root root 137, 9 2011-02-17 14:32 bml9
brw------- root root 137, 8 2011-02-17 14:32 bml8
brw-r----- root root 137, 7 2011-02-17 14:32 bml7
brw------- root root 137, 6 2011-02-17 14:32 bml6
brw------- root root 137, 5 2011-02-17 14:32 bml5
brw------- root root 137, 4 2011-02-17 14:32 bml4
brw------- root root 137, 3 2011-02-17 14:32 bml3
brw------- root root 137, 2 2011-02-17 14:32 bml2
brw------- root root 137, 1 2011-02-17 14:32 bml1
brw------- root root 137, 0 2011-02-17 14:32 bml0!c
drwxr-xr-x root root 2011-02-17 14:32 vold
brw------- root root 139, 10 2011-02-17 14:32 tfsr10
brw------- root root 139, 9 2011-02-17 14:32 tfsr9
brw------- root root 139, 8 2011-02-17 14:32 tfsr8
brw------- root root 139, 7 2011-02-17 14:32 tfsr7
brw------- root root 139, 6 2011-02-17 14:32 tfsr6
brw------- root root 139, 5 2011-02-17 14:32 tfsr5
brw------- root root 139, 4 2011-02-17 14:32 tfsr4
brw------- root root 139, 3 2011-02-17 14:32 tfsr3
brw------- root root 139, 2 2011-02-17 14:32 tfsr2
brw------- root root 139, 1 2011-02-17 14:32 tfsr1
brw------- root root 139, 0 2011-02-17 14:32 tfsr0!c
brw------- root root 7, 7 2011-02-17 14:32 loop7
brw------- root root 7, 6 2011-02-17 14:32 loop6
brw------- root root 7, 5 2011-02-17 14:32 loop5
brw------- root root 7, 4 2011-02-17 14:32 loop4
brw------- root root 7, 3 2011-02-17 14:32 loop3
brw------- root root 7, 2 2011-02-17 14:32 loop2
brw------- root root 7, 1 2011-02-17 14:32 loop1
brw------- root root 7, 0 2011-02-17 14:32 loop0
brw------- root root 1, 15 2011-02-17 14:32 ram15
brw------- root root 1, 14 2011-02-17 14:32 ram14
brw------- root root 1, 13 2011-02-17 14:32 ram13
brw------- root root 1, 12 2011-02-17 14:32 ram12
brw------- root root 1, 11 2011-02-17 14:32 ram11
brw------- root root 1, 10 2011-02-17 14:32 ram10
brw------- root root 1, 9 2011-02-17 14:32 ram9
brw------- root root 1, 8 2011-02-17 14:32 ram8
brw------- root root 1, 7 2011-02-17 14:32 ram7
brw------- root root 1, 6 2011-02-17 14:32 ram6
brw------- root root 1, 5 2011-02-17 14:32 ram5
brw------- root root 1, 4 2011-02-17 14:32 ram4
brw------- root root 1, 3 2011-02-17 14:32 ram3
brw------- root root 1, 2 2011-02-17 14:32 ram2
brw------- root root 1, 1 2011-02-17 14:32 ram1
brw------- root root 1, 0 2011-02-17 14:32 ram0
brw------- root root 179, 2 2011-02-17 14:32 mmcblk0p2
brw------- root root 179, 1 2011-02-17 14:32 mmcblk0p1
brw-r--r-- radio radio 137, 10 2011-02-17 14:32 bml10
brw------- root root 138, 12 2011-02-17 14:32 stl12
brw------- root root 138, 11 2011-02-17 14:32 stl11
brw------- root root 138, 10 2011-02-17 14:32 stl10
brw------- root root 138, 9 2011-02-17 14:32 stl9
brw------- root root 138, 8 2011-02-17 14:32 stl8
brw------- root root 138, 7 2011-02-17 14:32 stl7
brw------- root root 138, 6 2011-02-17 14:32 stl6
brw------- root root 138, 4 2011-02-17 14:32 stl4
brw------- root root 138, 3 2011-02-17 14:32 stl3
brw------- root root 179, 0 2011-02-17 14:32 mmcblk0
$
Hi dear crusher
First, congratulations because you did a great job.
Second, I don't have any problem with my IMEI but somehow I'm interested in your method that is subject of my second question!
now 2 questions:
1. I did what you said now I have a i5800xt.dat file (4351KB) in my sdcard.
the problem is that when I go to /dev/block with Root Explorer there is only an empty (vold) folder. no stl4 no mtl4.
Edit: Problem solved!
It seems that we can't see stl files with Root Explorer.
used Terminal Emulator and all files are there
2. my real problem is that my phone is locked and none of the unlock methods for SGS working for me (us?) because as you know our NV_data.bin file is different from them.
Now that you are familiar with NV_data.bin do you know any way to unlock SG3?
there is no SSNV in a lot of NV_data.bin files from SG3.
Best regards
@agdag & @cadusir, your files arrived and your requests are under processing.
(Please note that due to I managed to kill my laptop (southbridge chip fried ) I work slower but I do maintain my operations)
@wai5888: please read 1st post, and if you have a particular difficulty with one given step, refer to it specifically.
@punixx: PM sent.. you may use a password-incompatible archiver like 7zip, or don't know.
crusher said:
@cadusir, your files arrived and your requests are under processing.
Click to expand...
Click to collapse
thanks crusher I don't know about the others but I can wait as long as you like meanwhile I'm thankful of you informing us about this problems.
Any news?
Not yet for me!
yep.
he he....
can someone who owns an Atrix please run the following command in adb shell, and post the output here?
ls -l /dev/block/
thanks
# ls -l /dev/block/
ls -l /dev/block/
lrwxrwxrwx root root 2011-03-12 16:53 254:1 -> ../map
per/9e9fdee1587a1f7e421c44e2a0a4f529
brw------- root root 254, 1 2011-03-12 16:53 dm-1
lrwxrwxrwx root root 2011-03-12 16:53 254:0 -> ../map
per/574105b5312bcfea832c37a35d62736f
brw------- root root 254, 0 2011-03-12 16:53 dm-0
lrwxrwxrwx root root 2011-03-12 16:52 179:18 -> ../mm
cblk0p18
lrwxrwxrwx root root 2011-03-12 16:52 179:33 -> ../mm
cblk1p1
lrwxrwxrwx root root 2011-03-12 16:52 179:32 -> ../mm
cblk1
drwxr-xr-x root root 2011-03-12 16:52 vold
brw-rw---- root mot_tcmd 179, 33 2011-03-12 16:52 mmcblk1p1
brw------- root root 179, 32 2011-03-12 16:52 mmcblk1
brw------- root root 7, 7 2011-03-12 16:52 loop7
brw------- root root 7, 6 2011-03-12 16:52 loop6
brw------- root root 7, 5 2011-03-12 16:52 loop5
brw------- root root 7, 4 2011-03-12 16:52 loop4
brw------- root root 7, 3 2011-03-12 16:52 loop3
brw------- root root 7, 2 2011-03-12 16:52 loop2
brw------- root root 7, 1 2011-03-12 16:52 loop1
brw------- root root 7, 0 2011-03-12 16:52 loop0
brw------- root root 179, 18 2011-03-12 16:52 mmcblk0p18
brw------- root root 179, 17 2011-03-12 16:52 mmcblk0p17
brw------- root root 179, 16 2011-03-12 16:52 mmcblk0p16
brw------- root root 179, 15 2011-03-12 16:52 mmcblk0p15
brw------- root root 179, 14 2011-03-12 16:52 mmcblk0p14
brw------- root root 179, 13 2011-03-12 16:52 mmcblk0p13
brw------- root root 179, 12 2011-03-12 16:52 mmcblk0p12
brw------- root root 179, 11 2011-03-12 16:52 mmcblk0p11
brw------- root root 179, 10 2011-03-12 16:52 mmcblk0p10
brw------- root root 179, 9 2011-03-12 16:52 mmcblk0p9
brw------- root root 179, 8 2011-03-12 16:52 mmcblk0p8
brw-rw---- root mot_tcmd 179, 7 2011-03-12 16:52 mmcblk0p7
brw-rw---- root mot_tcmd 179, 6 2011-03-12 16:52 mmcblk0p6
brw------- root root 179, 5 2011-03-12 16:52 mmcblk0p5
brw------- root root 179, 4 2011-03-12 16:52 mmcblk0p4
brw------- root root 179, 3 2011-03-12 16:52 mmcblk0p3
brw------- root root 179, 2 2011-03-12 16:52 mmcblk0p2
brw------- root root 179, 1 2011-03-12 16:52 mmcblk0p1
brw------- root root 179, 0 2011-03-12 16:52 mmcblk0
#
C:\Users\XXXXXXX>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ ls -l /dev/block/
ls -l /dev/block/
lrwxrwxrwx root root 2011-03-12 16:44 254:5 -> ../mapper/d1e7d6315af88c99d7041f62be26b4a9
brw------- root root 254, 5 2011-03-12 16:44 dm-5
lrwxrwxrwx root root 2011-03-12 16:44 254:4 -> ../mapper/189fde3fca1f2a406f1bb46c71f21498
brw------- root root 254, 4 2011-03-12 16:44 dm-4
lrwxrwxrwx root root 2011-03-12 16:44 254:3 -> ../mapper/37ff227b4e634dfe5edfe09651561f6b
brw------- root root 254, 3 2011-03-12 16:44 dm-3
lrwxrwxrwx root root 2011-03-12 16:44 254:2 -> ../mapper/a2a85183221e048bf099e4c8f184744c
brw------- root root 254, 2 2011-03-12 16:44 dm-2
lrwxrwxrwx root root 2011-03-12 16:44 254:1 -> ../mapper/5741055312bcfea832c37a35d62736f
brw------- root root 254, 1 2011-03-12 16:44 dm-1
lrwxrwxrwx root root 2011-03-12 16:44 254:0 -> ../mapper/91295c5c28855fb592881dd53bc30990
brw------- root root 254, 0 2011-03-12 16:44 dm-0
lrwxrwxrwx root root 2011-03-12 16:43 179:18 -> ../mmcblk0p18
drwxr-xr-x root root 2011-03-12 16:43 vold
brw------- root root 179, 18 2011-03-12 16:43 mmcblk0p18
brw------- root root 179, 17 2011-03-12 16:43 mmcblk0p17
brw------- root root 179, 16 2011-03-12 16:43 mmcblk0p16
brw------- root root 179, 15 2011-03-12 16:43 mmcblk0p15
brw------- root root 179, 14 2011-03-12 16:43 mmcblk0p14
brw------- root root 179, 13 2011-03-12 16:43 mmcblk0p13
brw------- root root 179, 12 2011-03-12 16:43 mmcblk0p12
brw------- root root 179, 11 2011-03-12 16:43 mmcblk0p11
brw------- root root 179, 10 2011-03-12 16:43 mmcblk0p10
brw------- root root 179, 9 2011-03-12 16:43 mmcblk0p9
brw------- root root 179, 8 2011-03-12 16:43 mmcblk0p8
brw-rw---- root mot_tcmd 179, 7 2011-03-12 16:43 mmcblk0p7
brw-rw---- root mot_tcmd 179, 6 2011-03-12 16:43 mmcblk0p6
brw------- root root 179, 5 2011-03-12 16:43 mmcblk0p5
brw------- root root 179, 4 2011-03-12 16:43 mmcblk0p4
brw------- root root 179, 3 2011-03-12 16:43 mmcblk0p3
brw------- root root 179, 2 2011-03-12 16:43 mmcblk0p2
brw------- root root 179, 1 2011-03-12 16:43 mmcblk0p1
brw------- root root 179, 0 2011-03-12 16:43 mmcblk0
brw------- root root 7, 7 2011-03-12 16:43 loop7
brw------- root root 7, 6 2011-03-12 16:43 loop6
brw------- root root 7, 5 2011-03-12 16:43 loop5
brw------- root root 7, 4 2011-03-12 16:43 loop4
brw------- root root 7, 3 2011-03-12 16:43 loop3
brw------- root root 7, 2 2011-03-12 16:43 loop2
brw------- root root 7, 1 2011-03-12 16:43 loop1
brw------- root root 7, 0 2011-03-12 16:43 loop0
$
__________
Is that what you were looking for?
This doesn't belong here.
Hmm I wonder why Txts try did some looping.
Mr. Clown said:
This doesn't belong here.
Click to expand...
Click to collapse
where would this belong, this is needed in order for some development for the Atrix to take place? This is not a general question and not one that would apply to the masses.
jimmydafish said:
where would this belong, this is needed in order for some development for the Atrix to take place? This is not a general question and not one that would apply to the masses.
Click to expand...
Click to collapse
Err...which is why it *should* be in the Development section instead of General?
It happened to me twice now... not sure what the heck is happening here...
I have CM7.2 installed as primary and CM9 as secondary with multiboot.
Things were running just fine in both ROMs. But one fine day, when I was booting into CM9, for no apparent reason, I get the welcome to Android thing - the screen you get when you first boot into any ROM. Finding it weird I reboot and go to my primary ROM. There again, I am greeted with the green android.
Thinking that it must be some mistake I did, I promptly restore my backup (generated by my daily backup script - Thank god for that!!). This corrects both the ROMs alright...
Today again, I faced the same thing. Only difference in previous experience and today is that I just resized CM9 images (data/cache and system). Not sure why this would have any impact on the primary ROM...
Does this happen because both ROMs share same .android_secure or something like that? If so, why does this occur randomly and not every time I switch between ROMs?
PS: I know this question really belongs here but can't post it there because of the 10 post rule
the same thing happened to me, many times. I was not able to express it the way you did.
I am posting this thread's link on the concerned thread. Thanx.
P.S.: Enjoy your 1st 'Thanks' on XDA.
brajesh.sharma87 said:
P.s.: Enjoy your 1st 'thanks' on xda.
Click to expand...
Click to collapse
whooohooooooooooooo!!!!!!!!! :d:d:d:d
It looks like multiboot randomly mount real data partition instead of virtual one in fsimages. I have real cm7 and virtual cm9 and when this happened data restore real partition is needed.
Virtual partitions mount
There's script /system/bootmenu/2nd-boot/fshook.edit_devtree.sh in the bootmenu, which replaces real devices with virtual ones from fsimages on sdcard. This script is running twice: from init.hook.rc and 2nd-boot.sh.
I change fshook.edit_devtree.sh to write log on sdcard:
Code:
#### SYSTEM
# setup virtual image as device
losetup /dev/block/loop4 /fshook/mounts/imageSrc/fsimages/system.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p21 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p21 b 7 4 2>> /fshook/mounts/imageSrc/dev.log
######## DATA
# setup virtual image as device
losetup /dev/block/loop6 /fshook/mounts/imageSrc/fsimages/data.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p25 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p25 b 7 6 2>> /fshook/mounts/imageSrc/dev.log
######## CACHE
# setup virtual image as device
losetup /dev/block/loop5 /fshook/mounts/imageSrc/fsimages/cache.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p24 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p24 b 7 5 2>> /fshook/mounts/imageSrc/dev.log
######## PDS
# setup virtual image as device
losetup /dev/block/loop2 /fshook/mounts/imageSrc/fsimages/pds.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p7 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p7 b 7 2 2>> /fshook/mounts/imageSrc/dev.log
ls -l /dev/block/mmcblk1p* >> /fshook/mounts/imageSrc/dev.log
When some of virtual partitions (in this case it was cache) isn't mounted correctly, log file is following:
Code:
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p1
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p10
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p11
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p12
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p13
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p14
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p15
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p16
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p17
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p18
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p19
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p2
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p20
brw------- 1 root root 7, 4 Feb 15 10:10 /dev/block/mmcblk1p21
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p22
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p23
brw------- 1 root root 7, 5 Feb 15 10:10 /dev/block/mmcblk1p24
brw------- 1 root root 7, 6 Feb 15 10:10 /dev/block/mmcblk1p25
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p3
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p4
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p5
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p6
brw------- 1 root root 7, 2 Feb 15 10:10 /dev/block/mmcblk1p7
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p8
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p9
losetup: /dev/block/loop4: No such file or directory
losetup: /dev/block/loop6: No such file or directory
losetup: /dev/block/loop5: No such file or directory
mknod: /dev/block/mmcblk1p24: File exists
losetup: /dev/block/loop2: No such file or directory
brw-rw---- 1 root system 179, 33 Feb 15 10:10 /dev/block/mmcblk1p1
brw------- 1 root root 179, 42 Feb 15 10:10 /dev/block/mmcblk1p10
brw------- 1 root root 179, 43 Feb 15 10:10 /dev/block/mmcblk1p11
brw------- 1 root root 179, 44 Feb 15 10:10 /dev/block/mmcblk1p12
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p13
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p14
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p15
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p16
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p17
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p18
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p19
brw------- 1 root root 179, 34 Feb 15 10:10 /dev/block/mmcblk1p2
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p20
brw------- 1 root root 7, 4 Feb 15 10:10 /dev/block/mmcblk1p21
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p22
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p23
brw------- 1 root root 179, 56 Feb 15 10:10 /dev/block/mmcblk1p24
brw------- 1 root root 7, 6 Feb 15 10:10 /dev/block/mmcblk1p25
brw------- 1 root root 179, 35 Feb 15 10:10 /dev/block/mmcblk1p3
brw------- 1 root root 179, 36 Feb 15 10:10 /dev/block/mmcblk1p4
brw------- 1 root root 179, 37 Feb 15 10:10 /dev/block/mmcblk1p5
brw-rw---- 1 root system 179, 38 Feb 15 10:10 /dev/block/mmcblk1p6
brw------- 1 root root 7, 2 Feb 15 10:10 /dev/block/mmcblk1p7
brw------- 1 root root 179, 40 Feb 15 10:10 /dev/block/mmcblk1p8
brw------- 1 root root 179, 41 Feb 15 10:10 /dev/block/mmcblk1p9
mknod couldn't create mmcblk1p24 device, although it looks like removed without warning before. And in the first run of this script mknod was create mmcblk1p24 correctly.
Most people got problem in multiboot when using CM7.2 as nandroid. You might want to revert back to CM7.1 stable. I'm using it smoothly without any single problem