Samsung Galaxy Stellar SCH-I200 - System, Recovery, and Boot Images FOUND!

Search This thread

sovereign73811

Senior Member
Sep 23, 2012
54
10
We found the structure of the Samsung Stellar and we now know where the System, recovery, and boot images are!

This here is some of the file structures of the Samsung Stellar:

Code:
cat /proc/partitions
major minor  #blocks  name

 179        0    3866624 mmcblk0
 179        1      61440 mmcblk0p1
 179        2        128 mmcblk0p2
 179        3        256 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5       2048 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7      10240 mmcblk0p7
 179        8        512 mmcblk0p8
 179        9        512 mmcblk0p9
 179       10      10240 mmcblk0p10
 179       11      13952 mmcblk0p11
 179       12       3072 mmcblk0p12
 179       13       3072 mmcblk0p13
 179       14    1228800 mmcblk0p14
 179       15    1966080 mmcblk0p15
 179       16       8192 mmcblk0p16
 179       17     512000 mmcblk0p17
 179       18      10240 mmcblk0p18
 179       19      10240 mmcblk0p19
 179       20       6144 mmcblk0p20
 179       21       3072 mmcblk0p21
 179       22          8 mmcblk0p22
 179       23       5120 mmcblk0p23
 179       64       1024 mmcblk0boot1
 179       32       1024 mmcblk0boot0
 179       96    1955840 mmcblk1
 179       97    1081054 mmcblk1p1
 179       98     750000 mmcblk1p2
 179       99     124785 mmcblk1p3

To extract the images in their locations: you'll need to use these commands:

Code:
dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/Recovery.img

dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/boot.img

dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/system.img


This assumes that you have an external SD card.

System Partition: http://goo.im/devs/invisiblek/i200/stock.VRALG4.system.img.tar.md5.zip

The rest of the goodies are here: http://goo.im/devs/invisiblek/i200

BIG Thanks to Invisiblek!
 
Last edited:

wolverene13

Member
Sep 28, 2012
13
0
Romdump

Does anyone know how to use Romdump on a Samsung device? I read that Samsung has its own flashing structure which makes extracting the ROMs harder.

Is there any way to know how the file strucutre works or how to access the stock ROMs. Oh and yes we do have rooted devices.

This here is some of the file structures of the Samsung Stellar:

Code:
shell@android:/dev/block # ls
ls
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk1
mmcblk1p1
mmcblk1p2
mmcblk1p3
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9

Code:
cat /proc/partitions
major minor  #blocks  name

 179        0    3866624 mmcblk0
 179        1      61440 mmcblk0p1
 179        2        128 mmcblk0p2
 179        3        256 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5       2048 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7      10240 mmcblk0p7
 179        8        512 mmcblk0p8
 179        9        512 mmcblk0p9
 179       10      10240 mmcblk0p10
 179       11      13952 mmcblk0p11
 179       12       3072 mmcblk0p12
 179       13       3072 mmcblk0p13
 179       14    1228800 mmcblk0p14
 179       15    1966080 mmcblk0p15
 179       16       8192 mmcblk0p16
 179       17     512000 mmcblk0p17
 179       18      10240 mmcblk0p18
 179       19      10240 mmcblk0p19
 179       20       6144 mmcblk0p20
 179       21       3072 mmcblk0p21
 179       22          8 mmcblk0p22
 179       23       5120 mmcblk0p23
 179       64       1024 mmcblk0boot1
 179       32       1024 mmcblk0boot0
 179       96    1955840 mmcblk1
 179       97    1081054 mmcblk1p1
 179       98     750000 mmcblk1p2
 179       99     124785 mmcblk1p3

I tried romdump myself the other day on this, after rooting the phone, and romdump can't find /proc/mnt - I see that there is a file called /proc/mounts on the Stellar, however. I'm wondering if changing the references to /proc/mnt in the romdump script to /proc/mounts would help, but I'm a regular Linux person and am new to the way Android does things. You think this might work? I tried viewing romdump in a text editor,but it just spit out some gibberish with the word ELF at the top, which leads me to believe it is a Lua script or something. Do you know what language is being used? By the way, I'm also following your thread with moondeath on androidforums - did he ever get his situation sorted out?
 
Last edited:

sovereign73811

Senior Member
Sep 23, 2012
54
10
Yeah we're still working on it, but so far Moondeath, AGZealot, and frankly even I have been greatly...discouraged. I wish I knew what langauge was being used for Romdump.

Moondeath so far has been unable to get the screen back so I'm wondering if there's something to the bootloader LCD Density changer did? I thought LCD Density changer only changed the OS.

Lastly, I also found something on that same site for Romdump. Take a look at this:

http://android.podtwo.com/recoverymanager/

Be careful. We only want to extract the stock images and the stock recovery mode image. If it wants to put a custom recovery/bootloader in your phone STOP, or you will be like me and have a beautifully bricked phone. Only stock images will help me now.

It's a shame too. I made some kind of backup on my phone and I can't even access it.
By the way, it's good to have another person on board with this...I just wish we can get a REAL developer on this...
 
Last edited:

sovereign73811

Senior Member
Sep 23, 2012
54
10
OK people: here's a tip I've received from an XDA developer expert (thanks invisiblek):


Quote:
a quick and dirty explanation (need root)


Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/output.img
this will save the partition mmcblk0p1 to output.img

now, to determine what partitions are
on my device its:

Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
but you're scheme and directory structure there might be a little different, so adjust accordingly

Longer Version:

http://www.darkyrom.com/index.php?t...o-guide-to-dump-entire-s3-data-with-adb.8059/
 
Last edited:

wolverene13

Member
Sep 28, 2012
13
0
OK people: here's a tip I've received from an XDA developer expert:


Quote:
a quick and dirty explanation (need root)


Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/output.img
this will save the partition mmcblk0p1 to output.img

now, to determine what partitions are
on my device its:

Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
but you're scheme and directory structure there might be a little different, so adjust accordingly

Ok, I ran the ls -l /dev/block/platform/msm_sdcc.1/by-name/ command and I do see a "backup" directory and a "recovery" directory. I also see "rpm", which leads me to believe that Android runs on Red Hat. Not sure how relevant that is, but at least there's something that directly refers to what we're looking for. I do remember being asked to back up the phone when I first powered it on after I bought it. I wonder if maybe some kind of stock image is stored there?
 

sovereign73811

Senior Member
Sep 23, 2012
54
10
We think we've found the system image in mmcblk0p14.

The SYSTEM may be in

Code:
shell@android:/ # dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img bs=4096


dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img bs=4096
307200+0 records in
307200+0 records out
1258291200 bytes tra

We may also have a bootloader:

Code:
shell@android:/ #
dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.img bs=4096

dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.img bs=4096
shell@android:/ # dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.img bs=4096
256+0 records in
256+0 records out
1048576 bytes transferred in 0.130 secs (8065969 bytes/sec)
shell@android:/ # dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.img bs=4096
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.img bs=4096
256+0 records in
256+0 records out
1048576 bytes transferred in 0.129 secs (8128496 bytes/sec)
shell@android:/ #

Now all we need is to find the recovery...
 
Last edited:

sovereign73811

Senior Member
Sep 23, 2012
54
10
I have a theory:

I believe that the recovery partition is in "mmcblk0p20." This partition is about 6MB and I've seen Galaxy S3 recovery partitions size around 6MB.

Let's try adding this:

Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/recovery

or:

Code:
ls -l /dev/block/platform/msm_sdcc.1/mmcblk0p20

Can anyone help me confirm the theory? I would if I had a working phone.
 

remf4i

Senior Member
Mar 27, 2011
1,402
1,545
Parkersburg
Hey guys what's up, I have a ROM or 2 out for the skyrocket and the vzw gs3, I picked one of these up for my son and been playing with it, what is it your trying to do here? For root its easy ,but what is it your looking for and I may be able to help

Sent from my SCH-I200 using xda premium
 

sovereign73811

Senior Member
Sep 23, 2012
54
10
We're trying to make a backup of the system, recovery, and boot partitions and make them into ROMs flashable to Odin or whatever we need them to be.

If you can try to shed some light on the locations of the ROMs I'd certainly be grateful.
 

p4u191

Member
Oct 2, 2012
7
0
boot recovery

Hey you think somehow if i go into boot recovery, and click on the option that says format from sdcard.. is there a way i can transfer my root files into my sd car (8GB) then root it again? So basically do something from my sd card? instead of plugging it into the comp? And the repair option for the upgrade assistant didnt work since my computer couldnt read my device.
 

sovereign73811

Senior Member
Sep 23, 2012
54
10
I'm sure you've installed the Samsung USB drivers on there.

It takes much more to "transfer" the "root files" to your SD Card. The only thing you can "pull" from the phone in recovery mode is the Recovery image itself.

I can use that actually. Refer to my previous posts here on this very topic and see what you can do.
 

sovereign73811

Senior Member
Sep 23, 2012
54
10
DON'T DO IT! Unless you want to brick your phone. I did something similar and that's how I'm in my predicament.

Before you do anything else PLEASE backup your ROMs. Look at my past posts of this topic; I think we've found some of the ROMs.
 

wolverene13

Member
Sep 28, 2012
13
0
I have a theory:

I believe that the recovery partition is in "mmcblk0p20." This partition is about 6MB and I've seen Galaxy S3 recovery partitions size around 6MB.

Let's try adding this:

Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/recovery

or:

Code:
ls -l /dev/block/platform/msm_sdcc.1/mmcblk0p20

Can anyone help me confirm the theory? I would if I had a working phone.

a/local/bin:$PATH <
/platform/msm_sdcc.1/mmcblk0p20 <
lrwxrwxrwx root root 1970-01-13 18:02 mmcblk0p20 -> /dev/block/mmcblk0p20
/platform/msm_sdcc.1/by-name/recovery <
lrwxrwxrwx root root 1970-01-13 18:02 recovery -> /dev/block/mmcblk0p18
app_134@android:/ $
 

sovereign73811

Senior Member
Sep 23, 2012
54
10
So it's in mmcblk0p18? Hmm...can you extract anything out of it?

And I'll ask again: If any of you are successful in extracting the ROMs, please upload them. I need my Stellar back up and running soon!
 
Last edited:

wolverene13

Member
Sep 28, 2012
13
0
Sure, I can try to extract something - any tips on how to do that? I can obviously just Google it, but I'm new to the Android environment. If I could get the device to talk to my Linux box, I could probably do a lot more, but it doesn't recognize the device via MTP, which is another battle I'm working on. As a result, I have either use my work laptop, which runs Windows, or I have to do it directly from the phone.
 
Last edited:

sovereign73811

Senior Member
Sep 23, 2012
54
10
If I know the code enough, I believe that these commands through adb will extract the partitions in an image file. You can look at the very first post of the topic; I've updated it with some compiled information I've gathered.
 

gravewood

New member
Oct 6, 2012
1
0
So I too am new to android. I just attempted a rom dump using the podtwo romdump/adb method, and I am pretty sure that it did not complete as it should have. Here is the output
Code:
C:\Users\gravewood\AppData\Local\Android\android-sdk\platform-tools>adb push romdump
 /data/local
2587 KB/s (1149900 bytes in 0.434s)

C:\Users\gravewood\AppData\Local\Android\android-sdk\platform-tools>adb shell chmod
04755 /data/local/romdump

C:\Users\gravewood\AppData\Local\Android\android-sdk\platform-tools>adb shell /data/
local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
You need to be rooted to run this aplication

Device : IMM76D.I200VRALG4

Creating required files... cat: can't open '/proc/mtd': No such file or director
y
done.
Opening mtd table... Segmentation fault

C:\Users\gravewood\AppData\Local\Android\android-sdk\platform-tools>
It did not create the sub directory named after my device so what is in the zip is all I have, taking a smoke break hope someone can work with it let me know what else I can do to help.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    We found the structure of the Samsung Stellar and we now know where the System, recovery, and boot images are!

    This here is some of the file structures of the Samsung Stellar:

    Code:
    cat /proc/partitions
    major minor  #blocks  name
    
     179        0    3866624 mmcblk0
     179        1      61440 mmcblk0p1
     179        2        128 mmcblk0p2
     179        3        256 mmcblk0p3
     179        4        512 mmcblk0p4
     179        5       2048 mmcblk0p5
     179        6        512 mmcblk0p6
     179        7      10240 mmcblk0p7
     179        8        512 mmcblk0p8
     179        9        512 mmcblk0p9
     179       10      10240 mmcblk0p10
     179       11      13952 mmcblk0p11
     179       12       3072 mmcblk0p12
     179       13       3072 mmcblk0p13
     179       14    1228800 mmcblk0p14
     179       15    1966080 mmcblk0p15
     179       16       8192 mmcblk0p16
     179       17     512000 mmcblk0p17
     179       18      10240 mmcblk0p18
     179       19      10240 mmcblk0p19
     179       20       6144 mmcblk0p20
     179       21       3072 mmcblk0p21
     179       22          8 mmcblk0p22
     179       23       5120 mmcblk0p23
     179       64       1024 mmcblk0boot1
     179       32       1024 mmcblk0boot0
     179       96    1955840 mmcblk1
     179       97    1081054 mmcblk1p1
     179       98     750000 mmcblk1p2
     179       99     124785 mmcblk1p3

    To extract the images in their locations: you'll need to use these commands:

    Code:
    dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/Recovery.img
    
    dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/boot.img
    
    dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/system.img


    This assumes that you have an external SD card.

    System Partition: http://goo.im/devs/invisiblek/i200/stock.VRALG4.system.img.tar.md5.zip

    The rest of the goodies are here: http://goo.im/devs/invisiblek/i200

    BIG Thanks to Invisiblek!