[SOLUTION] i5800 ONLY! Check here if you lost your IMEI

[SOLUTION] i5800 ONLY! Check here if you lost your IMEI - Galaxy 3 General

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....

Related

[help neded] I need a dump of a /dev/ on a stock captivate rooted

Hello guys,
Can you please post a ls -al /dev/block/
and if you can provide a .tar.gz of the entire thing.
Thanks!

how do I do this on droid explorer, I tried opening the folder with usb debug on, but it won't open.

Hello,
You need root.
Code:
adb shell
su
cd /dev/block/
ls -al

I already did this somewhere around the forum, likely in one of the lagfix threads...

max_warheads said:
I already did this somewhere around the forum, likely in one of the lagfix threads...
Click to expand...
Click to collapse
I did a quick search. Please post here.
Thanks!

Code:
bash-4.1# ls -al /dev/block
total 0
drwxr-xr-x 3 0 0 1360 Aug 21 06:48 .
drwxr-xr-x 10 0 0 13580 Aug 21 06:48 ..
brw------- 1 0 0 137, 0 Aug 21 06:48 bml0!c
brw------- 1 0 0 137, 1 Aug 21 06:48 bml1
brw------- 1 0 0 137, 10 Aug 21 06:48 bml10
brw------- 1 0 0 137, 11 Aug 21 06:48 bml11
brw-r--r-- 1 0 0 137, 12 Aug 21 06:48 bml12
brw------- 1 0 0 137, 2 Aug 21 06:48 bml2
brw------- 1 0 0 137, 3 Aug 21 06:48 bml3
brw------- 1 0 0 137, 4 Aug 21 06:48 bml4
brw------- 1 0 0 137, 5 Aug 21 06:48 bml5
brw------- 1 0 0 137, 6 Aug 21 06:48 bml6
brw------- 1 0 0 137, 7 Aug 21 06:48 bml7
brw------- 1 0 0 137, 8 Aug 21 06:48 bml8
brw------- 1 0 0 137, 9 Aug 21 06:48 bml9
brw------- 1 0 0 7, 0 Aug 21 06:48 loop0
brw------- 1 0 0 7, 1 Aug 21 06:48 loop1
brw------- 1 0 0 7, 2 Aug 21 06:48 loop2
brw------- 1 0 0 7, 3 Aug 21 06:48 loop3
brw------- 1 0 0 7, 4 Aug 21 06:48 loop4
brw------- 1 0 0 7, 5 Aug 21 06:48 loop5
brw------- 1 0 0 7, 6 Aug 21 06:48 loop6
brw------- 1 0 0 7, 7 Aug 21 06:48 loop7
brw------- 1 0 0 179, 0 Aug 21 06:48 mmcblk0
brw------- 1 0 0 179, 1 Aug 21 06:48 mmcblk0p1
brw------- 1 0 0 179, 2 Aug 21 06:48 mmcblk0p2
brw------- 1 0 0 1, 0 Aug 21 06:48 ram0
brw------- 1 0 0 1, 1 Aug 21 06:48 ram1
brw------- 1 0 0 1, 10 Aug 21 06:48 ram10
brw------- 1 0 0 1, 11 Aug 21 06:48 ram11
brw------- 1 0 0 1, 12 Aug 21 06:48 ram12
brw------- 1 0 0 1, 13 Aug 21 06:48 ram13
brw------- 1 0 0 1, 14 Aug 21 06:48 ram14
brw------- 1 0 0 1, 15 Aug 21 06:48 ram15
brw------- 1 0 0 1, 2 Aug 21 06:48 ram2
brw------- 1 0 0 1, 3 Aug 21 06:48 ram3
brw------- 1 0 0 1, 4 Aug 21 06:48 ram4
brw------- 1 0 0 1, 5 Aug 21 06:48 ram5
brw------- 1 0 0 1, 6 Aug 21 06:48 ram6
brw------- 1 0 0 1, 7 Aug 21 06:48 ram7
brw------- 1 0 0 1, 8 Aug 21 06:48 ram8
brw------- 1 0 0 1, 9 Aug 21 06:48 ram9
brw------- 1 0 0 138, 1 Aug 21 06:48 stl1
brw------- 1 0 0 138, 10 Aug 21 06:48 stl10
brw------- 1 0 0 138, 11 Aug 21 06:48 stl11
brw------- 1 0 0 138, 12 Aug 21 06:48 stl12
brw------- 1 0 0 138, 2 Aug 21 06:48 stl2
brw------- 1 0 0 138, 3 Aug 21 06:48 stl3
brw------- 1 0 0 138, 4 Aug 21 06:48 stl4
brw------- 1 0 0 138, 5 Aug 21 06:48 stl5
brw------- 1 0 0 138, 6 Aug 21 06:48 stl6
brw------- 1 0 0 138, 7 Aug 21 06:48 stl7
brw------- 1 0 0 138, 8 Aug 21 06:48 stl8
brw------- 1 0 0 138, 9 Aug 21 06:48 stl9
brw------- 1 0 0 139, 0 Aug 21 06:48 tfsr0!c
brw------- 1 0 0 139, 1 Aug 21 06:48 tfsr1
brw------- 1 0 0 139, 10 Aug 21 06:48 tfsr10
brw------- 1 0 0 139, 11 Aug 21 06:48 tfsr11
brw------- 1 0 0 139, 12 Aug 21 06:48 tfsr12
brw------- 1 0 0 139, 2 Aug 21 06:48 tfsr2
brw------- 1 0 0 139, 3 Aug 21 06:48 tfsr3
brw------- 1 0 0 139, 4 Aug 21 06:48 tfsr4
brw------- 1 0 0 139, 5 Aug 21 06:48 tfsr5
brw------- 1 0 0 139, 6 Aug 21 06:48 tfsr6
brw------- 1 0 0 139, 7 Aug 21 06:48 tfsr7
brw------- 1 0 0 139, 8 Aug 21 06:48 tfsr8
brw------- 1 0 0 139, 9 Aug 21 06:48 tfsr9
drwxr-xr-x 2 0 0 100 Aug 21 06:48 vold
bash-4.1#

Actually, sorry, that was for the JH2 ROM.

[Q] Dump CDMA Modem

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

Can You Please, phone information needed

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?

[Q] multiboot: whats happening?

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

T590 boot.img clarification

Trying to get the boot image I've run into difficulties. If someone knows, I would be greatful if they point out the boot partition.
first I've found different references to pulling from the device.
They seem to pulling via linux dd command or cat
Trouble is my dev directory does not have the device they reference nor does the proc directory
Pages That ... gave me ... a little but not enough
no such directory
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
not sure this really helps
https://androidforums.com/threads/where-is-my-boot-img.892350/
again...maybe just phone? still no /proc/mtd
https://forum.xda-developers.com/showthread.php?t=443994
no dump command
https://forum.xda-developers.com/showthread.php?t=2146077
maybe from the mount command... blk37 or blk38 both are vfat mounted on /firmware-modem and /firmware respectively.
no mtd and I don't want the entire rom...plus I'd rather not download a command, currently
https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/
...? recovery on blk13..for this one
https://androidforums.com/threads/c...-recovery-for-the-lg-viper-4g-lgls840.566507/
Code:
gta2xlwifi:/ $ ls /dev
ls: /dev/event-log-tags: Permission denied
__properties__ coresight-stm fd i2c-2 kmsg msm_amrnb msm_multi_aac psaux ramdump_smem smd1 smem_log tzic v4l-subdev12 video0
adsprpc-smd cpu_dma_latency fscklogs i2c-3 knox_kap msm_amrnb_in msm_qcelp pta ramdump_venus smd11 snd uhid v4l-subdev13 video1
android_mbim cpuctl fsdbg i2c-4 loop-control msm_amrwb msm_qcelp_in ptmx ramdump_wcnss smd2 socket uinput v4l-subdev14 video2
android_rndis_qc cpuset full i2c-5 mdsprpc-smd msm_amrwb_in msm_rtac pts random smd21 stune uio0 v4l-subdev15 video32
apr_apps2 dbmdx-0 fuse i2c-6 mdss_rotator msm_amrwbplus msm_sps qce rfkill smd22 subsys_a506_zap uio1 v4l-subdev16 video33
ashmem dbmdx-1 graphics i2c-7 media0 msm_ape msm_thermal_query qseecom rmnet_ctrl smd3 subsys_adsp urandom v4l-subdev17 vndbinder
at_usb0 dcc_sram hbtp_input i2c-8 media1 msm_audio_cal msm_wma radio0 rmnet_ctrl1 smd36 subsys_modem usb-ffs v4l-subdev2 wcnss_ctrl
at_usb1 dek_evt hbtp_vm i2c-9 media2 msm_evrc msm_wmapro ramdump_a506_zap rmnet_ctrl2 smd4 subsys_venus usb_accessory v4l-subdev3 wcnss_wlan
avtimer dek_log hw_random icd memory_bandwidth msm_evrc_in ncm_dev ramdump_adsp rmnet_ctrl3 smd5 subsys_wcnss usb_mtp_gadget v4l-subdev4 xt_qtaguid
binder dek_req hwbinder icdr mobicore msm_g711alaw network_latency ramdump_adsp_rh rtc0 smd6 sw_sync usb_ncm v4l-subdev5 zero
block device-mapper hyst_bias icesdcc mobicore-user msm_g711alaw_in network_throughput ramdump_memshare sdp_dlp smd7 tima_uevent usf1 v4l-subdev6
ccic_misc diag i2c-0 input msm-rng msm_g711mlaw null ramdump_memshare_DIAG sdp_mm smd8 tty v4l-subdev0 v4l-subdev7
ccid_bulk dpl_ctrl i2c-1 ion msm_aac msm_g711mlaw_in pmsg0 ramdump_memshare_FTM sdsprpc-smd smd_pkt_loopback ttyGS0 v4l-subdev1 v4l-subdev8
ccid_ctrl dun i2c-10 jpeg0 msm_aac_in msm_hweffects power_on_alarm ramdump_memshare_GPS sec_misc smdcntl0 ttyHSL0 v4l-subdev10 v4l-subdev9
console ear_mic_adc i2c-11 kgsl-3d0 msm_alac msm_mp3 ppp ramdump_modem smd0 smdcntl8 tun v4l-subdev11 vga_arbiter
Code:
gta2xlwifi:/proc $ ls -d [a-z]*
asound cgroups crypto dmverity_odin_flag fs irq kpagecount meminfo mounts reset_reason self stlog_pipe sysrq-trigger tsp_cmoffset_main tty uptime vmstat
avc_msg cmdline debug driver interrupts kallsyms kpageflags meminfo_extra net reset_summary slabinfo stlog_version thread-self tsp_cmoffset_sdc uid_cputime usblog zoneinfo
boot_stat config.gz device-tree execdomains iomem key-users last_kmsg memsize pagetypeinfo reset_tzlog softirqs store_lastkmsg tima_debug_log tsp_cmoffset_sub uid_io user_fault
buddyinfo consoles devices fb ioports keys loadavg misc partitions schedstat stat swaps timer_list tsp_msg uid_procstat version
bus cpuinfo diskstats filesystems iostats kmsg locks modules reset_klog scsi stlog sys timer_stats tsp_raw_data uid_stat vmallocinfo
Code:
gta2xlwifi:/proc $ mount
rootfs on / type rootfs (ro,seclabel,size=1302672k,nr_inodes=325668)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1415200k,nr_inodes=353800,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/dm-0 on /odm type ext4 (ro,seclabel,relatime,i_version)
/dev/block/dm-1 on /system type ext4 (ro,seclabel,relatime,i_version)
/dev/block/dm-2 on /vendor type ext4 (ro,seclabel,relatime,i_version)
none on /acct type cgroup (rw,relatime,cpuacct)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1415200k,nr_inodes=353800,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,size=1415200k,nr_inodes=353800,mode=700)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/mmcblk0p44 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,i_version)
/dev/block/mmcblk0p31 on /persist type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,i_version)
/dev/block/mmcblk0p16 on /efs type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,i_version)
/dev/block/mmcblk0p36 on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,i_version,data=ordered)
/dev/block/mmcblk0p38 on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p37 on /firmware-modem type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p46 on /omr type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1415200k,nr_inodes=353800,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/dm-3 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,resgid=5555,i_version)
/data/knox/secure_fs/enc_user on /data/enc_user type ecryptfs (rw,seclabel,nodev,relatime,ecryptfs_fnek_sig=696678df255664c9,ecryptfs_sig=696678df255664c9,userid=0,sdp_enabled,partition_id=0,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,base=,label=)
/data/knox/secure_fs/enc_media on /data/knox/secure_fs/enc_media type ecryptfs (rw,seclabel,nodev,relatime,ecryptfs_fnek_sig=696678df255664c9,ecryptfs_sig=696678df255664c9,userid=0,sdp_enabled,partition_id=1,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,base=,label=)
/data/knox/secure_fs/enc_media on /mnt/shell/enc_emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1000,fsgid=1000,gid=9997,multiuser,reserved=20MB)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,reserved=20MB)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,reserved=20MB)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,reserved=20MB)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,reserved=20MB)
Code:
gta2xlwifi:/proc $ ls -larth /dev/block/mmc*
brw-rw---- 1 root system 179, 22 2017-12-31 18:02 /dev/block/mmcblk0p22
brw------- 1 root root 259, 11 2018-03-03 15:50 /dev/block/mmcblk0p43
brw------- 1 root root 259, 10 2018-03-03 15:50 /dev/block/mmcblk0p42
brw------- 1 root root 259, 9 2018-03-03 15:50 /dev/block/mmcblk0p41
brw------- 1 root root 179, 32 2018-03-03 15:50 /dev/block/mmcblk0rpmb
brw------- 1 root root 179, 9 2018-03-03 15:50 /dev/block/mmcblk0p9
brw------- 1 root root 179, 8 2018-03-03 15:50 /dev/block/mmcblk0p8
brw------- 1 root root 179, 7 2018-03-03 15:50 /dev/block/mmcblk0p7
brw------- 1 root root 179, 6 2018-03-03 15:50 /dev/block/mmcblk0p6
brw------- 1 root root 179, 5 2018-03-03 15:50 /dev/block/mmcblk0p5
brw------- 1 root root 259, 13 2018-03-03 15:50 /dev/block/mmcblk0p45
brw------- 1 root root 259, 8 2018-03-03 15:50 /dev/block/mmcblk0p40
brw------- 1 root root 179, 4 2018-03-03 15:50 /dev/block/mmcblk0p4
brw------- 1 root root 259, 6 2018-03-03 15:50 /dev/block/mmcblk0p38
brw------- 1 root root 259, 5 2018-03-03 15:50 /dev/block/mmcblk0p37
brw------- 1 root root 259, 4 2018-03-03 15:50 /dev/block/mmcblk0p36
brw------- 1 system system 259, 3 2018-03-03 15:50 /dev/block/mmcblk0p35
brw------- 1 root root 259, 2 2018-03-03 15:50 /dev/block/mmcblk0p34
brw-rw---- 1 system system 259, 1 2018-03-03 15:50 /dev/block/mmcblk0p33
brw------- 1 root root 179, 30 2018-03-03 15:50 /dev/block/mmcblk0p30
brw------- 1 root root 179, 3 2018-03-03 15:50 /dev/block/mmcblk0p3
brw------- 1 root root 179, 29 2018-03-03 15:50 /dev/block/mmcblk0p29
brw------- 1 root root 179, 28 2018-03-03 15:50 /dev/block/mmcblk0p28
brw------- 1 root root 179, 27 2018-03-03 15:50 /dev/block/mmcblk0p27
brw------- 1 root root 179, 26 2018-03-03 15:50 /dev/block/mmcblk0p26
brw------- 1 root root 179, 25 2018-03-03 15:50 /dev/block/mmcblk0p25
brw------- 1 root root 179, 24 2018-03-03 15:50 /dev/block/mmcblk0p24
brw------- 1 root root 179, 23 2018-03-03 15:50 /dev/block/mmcblk0p23
brw------- 1 root root 179, 21 2018-03-03 15:50 /dev/block/mmcblk0p21
brw------- 1 root root 179, 20 2018-03-03 15:50 /dev/block/mmcblk0p20
brw------- 1 root root 179, 2 2018-03-03 15:50 /dev/block/mmcblk0p2
brw------- 1 root root 179, 19 2018-03-03 15:50 /dev/block/mmcblk0p19
brw------- 1 root root 179, 18 2018-03-03 15:50 /dev/block/mmcblk0p18
brw------- 1 root root 179, 17 2018-03-03 15:50 /dev/block/mmcblk0p17
brw------- 1 root root 179, 13 2018-03-03 15:50 /dev/block/mmcblk0p13
brw------- 1 root root 179, 12 2018-03-03 15:50 /dev/block/mmcblk0p12
brw------- 1 root root 179, 11 2018-03-03 15:50 /dev/block/mmcblk0p11
brw------- 1 root root 179, 10 2018-03-03 15:50 /dev/block/mmcblk0p10
brw------- 1 root root 179, 1 2018-03-03 15:50 /dev/block/mmcblk0p1
brw------- 1 root root 179, 0 2018-03-03 15:50 /dev/block/mmcblk0
brw------- 1 root root 259, 14 2018-03-03 15:50 /dev/block/mmcblk0p46
brw------- 1 root root 259, 12 2018-03-03 15:50 /dev/block/mmcblk0p44
brw------- 1 root root 179, 31 2018-03-03 15:50 /dev/block/mmcblk0p31
brw------- 1 root root 179, 16 2018-03-03 15:50 /dev/block/mmcblk0p16
brw-rw---- 1 system system 259, 0 2018-03-24 13:20 /dev/block/mmcblk0p32
brw------- 1 root root 259, 15 2019-03-24 13:22 /dev/block/mmcblk0p47
brw------- 1 root root 179, 15 2019-03-24 13:32 /dev/block/mmcblk0p15
brw------- 1 root root 179, 14 2019-03-24 18:41 /dev/block/mmcblk0p14
brw------- 1 root root 259, 7 2019-03-25 13:31 /dev/block/mmcblk0p39
Code:
gta2xlwifi:/ $ ls /system/bin|grep dump
crash_dump32
dexdump
dumpstate
dumpsys
oatdump
tima_dump_log

I believe, I downloaded the(?) boot image from https://www.sammobile.com
but even here it wasn't completely straightforward.
it has a whole list of countries but not the U.S. and there is PDA and CSC.
I found some sites mentioning a /system/csc directory containing an xml... no such directory on T590
Seems like PDA is the last portion of the build number
https://forum.xda-developers.com/showthread.php?t=1801022
but that still leaves too many ...
so
based on
https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones
seems like the service provider sw contains the csc based on method two
This is slightly confusing because the picture has 3 numbered ..numbers but under that his 1-3 appear to refer to only the last (number 3 or portions thereof) so if I'm guessing correctly..my CSC=XAR
which... sammobile.com says is "Cellular south (XAR)"...well weird it should be a wifi only tablet but I am in the "South" ... so I dunno, I guess so?
So this should be the link
https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T590/XAR/download/T590XXU2ARK2/248008/
well I'm still somewhat confused but this looks right
Model SM-T590
Model name Galaxy Tab A
Country Cellular south (XAR)
Version Android 8.1.0
Changelist 14876204
Build date Thu, 29 Nov 2018 01:48:25 +0000
Security Patch Level 2018-12-01
Product code XAR
PDA T590XXU2ARK2
CSC T590OXM2ARK2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've found sites talking about enabling features by editing the csc xml...file but... that seems like either old info or just not for my tablet...
I would love if anyone has links or anything that would make this more clear... I think I fumbled enough to download the right image but..I would have rather gotten it of the phone..and I'm still not sure.

Here u go, extracted from the full rom, not the device. But it's the right one.
https://drive.google.com/file/d/1j83zhWSQkt_Rj4mK9H8yqzeZFlvT2okO/view?usp=sharing

AsItLies said:
Here u go, extracted from the full rom, not the device. But it's the right one.
https://drive.google.com/file/d/1j83zhWSQkt_Rj4mK9H8yqzeZFlvT2okO/view?usp=sharing
Click to expand...
Click to collapse
Thank You

AsItLies said:
Here u go, extracted from the full rom, not the device. But it's the right one.
https://drive.google.com/file/d/1j83zhWSQkt_Rj4mK9H8yqzeZFlvT2okO/view?usp=sharing
Click to expand...
Click to collapse
first try flashing with heimdall failed with verification failure... :crying:
So... I'm using
https://forum.xda-developers.com/galaxy-tab-a/how-to/root-samsung-galaxy-tab-10-5-2018-root-t3887848
I didn't do step 3 because I don't think heimdall see's anything but .img
I did do step 4 but I'm unsure what that is...
"Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen. "
I can't do
Flash the patched boot image with Odin in the AP-slot
I don't know what the AP-slot is...I don't think heimdall has the equivalent?
I used the flash tab and selected a pid..I downloaded previously from the device selected boot and picked the patched img..
"verification failed" ... erasing
I dunno... any suggestions/help appreciated.

larrys_ said:
first try flashing with heimdall failed with verification failure... :crying:
So... I'm using
https://forum.xda-developers.com/galaxy-tab-a/how-to/root-samsung-galaxy-tab-10-5-2018-root-t3887848
<snip>
I dunno... any suggestions/help appreciated.
Click to expand...
Click to collapse
I haven't done this, yet. But, first and foremost, you can't ** skip ** any steps. They are ** all ** there for a reason. Skipping one will result in the next ones not working, it's just that simple.
I'd also suggest that if the directions you are following use Odin (on windows obviously), then find a way to boot windows and follow what it says. Yes, it's a pain, I hate windows, but I have dual boot to 8.1, just for purposes like this. Heimdall should have similar capabilities but I've never used the gui front end, only the command line, and don't know all the options available.
Again though, don't skip any steps, it's definitely not going to work if you do that.
good luck, Cheers

NVM... I guess the boot image you gave me was pre-patched... I just flashed it... and ROOT!
Thanks!
Now, I'll guess I'll have to wait for both TWRP and LineagOS to come out with T590 versions but that's a good problem!
AGAIN, THANK YOU!
root achieved!

larrys_ said:
NVM... I guess the boot image you gave me was pre-patched... I just flashed it... and ROOT!
Thanks!
Now, I'll guess I'll have to wait for both TWRP and LineagOS to come out with T590 versions but that's a good problem!
AGAIN, THANK YOU!
root achieved!
Click to expand...
Click to collapse
Well it's good that you have root, but I can guarantee you that the image you got from me was not patched. That image came right out of the stock OEM ROM. So there's something, somewhere, somehow, that you did that you ended up with a patched boot image. Cheers.

AsItLies said:
Well it's good that you have root, but I can guarantee you that the image you got from me was not patched. That image came right out of the stock OEM ROM. So there's something, somewhere, somehow, that you did that you ended up with a patched boot image. Cheers.
Click to expand...
Click to collapse
Lol quite possibly,
Anyway in-case someone else wants to extract the boot.img or recovery.img...
heimdall gave me the blocks... I don't think you can extract without root..but either way....info
Code:
--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 133120
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 26
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 198656
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:

Database Users

welcome

[SOLUTION] i5800 ONLY! Check here if you lost your IMEI - Galaxy 3 General

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

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)

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....

Related

[help neded] I need a dump of a /dev/ on a stock captivate rooted

[Q] Dump CDMA Modem

Can You Please, phone information needed

[Q] multiboot: whats happening?

T590 boot.img clarification

Categories

Resources