FORUMS

Analysis & Opinion

Top Forum Discussions

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

40 posts
Thanks Meter: 7
 
By sovereign73811, Member on 29th September 2012, 02:06 AM
Post Reply Subscribe to Thread Email Thread
4th October 2012, 08:40 PM |#11  
Junior Member
Thanks Meter: 0
 
More
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.
 
 
4th October 2012, 11:15 PM |#12  
OP Member
Thanks Meter: 7
 
More
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.
5th October 2012, 12:15 AM |#13  
remf4i's Avatar
Senior Member
Parkersburg
Thanks Meter: 1,564
 
More
Has anyone tried any cwm recoveries yet?

Sent from my SCH-I200 using xda premium
5th October 2012, 12:23 AM |#14  
OP Member
Thanks Meter: 7
 
More
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.
6th October 2012, 06:43 AM |#15  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by sovereign73811

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:/ $
6th October 2012, 07:32 AM |#16  
OP Member
Thanks Meter: 7
 
More
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 by sovereign73811; 6th October 2012 at 09:19 AM.
6th October 2012, 06:52 PM |#17  
Junior Member
Thanks Meter: 0
 
More
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 by wolverene13; 6th October 2012 at 07:07 PM. Reason: Pasted entirely wrong text the first time.
6th October 2012, 07:12 PM |#18  
OP Member
Thanks Meter: 7
 
More
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.
7th October 2012, 11:12 PM |#19  
Junior Member
Thanks Meter: 0
 
More
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.
Attached Files
File Type: zip potential romdump.zip - [Click for QR Code] (4.0 KB, 84 views)
8th October 2012, 03:13 AM |#20  
OP Member
Thanks Meter: 7
 
More
ROMDump doesn't work because of Samsung's proprietary partitioning. Try looking around here instead.
8th October 2012, 08:37 AM |#21  
Member
Thanks Meter: 2
 
More
From my phone:

Code:
major    minor    #blocks    name            type
-----    -----    -------    ------------    --------
  179        0    3866624    mmcblk0         ?
  179        1      61440    mmcblk0p1       ?
  179        2        128    mmcblk0p2       sbl1
  179        3        256    mmcblk0p3       sbl2
  179        4        512    mmcblk0p4       sbl3
  179        5       2048    mmcblk0p5       aboot
  179        6        512    mmcblk0p6       rpm
  179        7      10240    mmcblk0p7       boot
  179        8        512    mmcblk0p8       tz
  179        9        512    mmcblk0p9       pit
  179       10      10240    mmcblk0p10      param
  179       11      13952    mmcblk0p11      efs
  179       12       3072    mmcblk0p12      modemst1
  179       13       3072    mmcblk0p13      modemst2
  179       14    1228800    mmcblk0p14      system
  179       15    1966080    mmcblk0p15      userdata
  179       16       8192    mmcblk0p16      persist
  179       17     512000    mmcblk0p17      cache
  179       18      10240    mmcblk0p18      recovery
  179       19      10240    mmcblk0p19      fota
  179       20       6144    mmcblk0p20      backup
  179       21       3072    mmcblk0p21      fsg
  179       22          8    mmcblk0p22      ssd
  179       23          2    mmcblk0p23      grow
  179       64       1024    mmcblk0boot1    boot1
  179       32       1024    mmcblk0boot0    boot0
  179       96    1931264    mmcblk1         ?
  179       97    1930240    mmcblk1p1       ?
I got the following, do you want anything else?

Code:
mkdir /mnt/extSdCard/backup
dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/recovery.img bs=4096
dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/boot.img bs=4096
dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/system.img bs=4096
dd if=/dev/block/mmcblk0boot1 of=/mnt/extSdCard/backup/boot1.img bs=4096
dd if=/dev/block/mmcblk0boot0 of=/mnt/extSdCard/backup/boot0.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/mnt/extSdCard/backup/sch-i200.pit bs=4096
Also, this will be a rooted image. Does the SuperUser app update su in /system/bin? If I want the latest version of SuperUser.apk in the image, do I execute the following after updating?

Code:
mount -o remount,rw /system
cp /data/app/com.noshufou.android.su-1.apk /system/app/Superuser.apk
mount -o remount,ro /system

Read More
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes