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

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!

Romdump
sovereign73811 said:
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:
[email protected]:/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
Click to expand...
Click to collapse
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?

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

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/

sovereign73811 said:
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
Click to expand...
Click to collapse
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?

There is. See if you can extract the system image and the recovery image.

We think we've found the system image in mmcblk0p14.
The SYSTEM may be in
Code:
[email protected]:/ # 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:
[email protected]:/ #
dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.img bs=4096
dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.img bs=4096
[email protected]:/ # 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)
[email protected]:/ # 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)
[email protected]:/ #
Now all we need is to find the recovery...

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.

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

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.

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.

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.

Has anyone tried any cwm recoveries yet?
Sent from my SCH-I200 using xda premium

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.

sovereign73811 said:
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.
Click to expand...
Click to collapse
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
[email protected]:/ $

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!

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.

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.

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.

ROMDump doesn't work because of Samsung's proprietary partitioning. Try looking around here instead.

Related

[Q] Which /dev/block is /system? P5100

All,
When I explore the device for the system image to pull using DD, I am not sure which one contains the fs to be mounted as /system. Basically trying to extract system.img from the stock Rom..
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 27787247 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
Code:
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name

[Q]how to dump boot.img from huawei ascend G330 (u8825-1)?

sorry if I'm wrong section but I have a bad English.
I'm trying to do the dump file boot.img most beautiful gi others from a huawei ascend G330 (u8825-1) and do not know what these files contain what it helpful. who can help me to understand what they contain and to identify the boot thanks
Code:
[email protected]:~$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # su
130|[email protected]:/ # cat /proc/mtd
dev: size erasesize name
[email protected]:/ #
127|[email protected]:/ # cat /proc/emmc
/proc/emmc: No such file or directory
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 300 mmcblk0p2
179 3 133120 mmcblk0p3
179 4 1 mmcblk0p4
179 5 12288 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 20480 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 196608 mmcblk0p15
179 16 81920 mmcblk0p16
179 17 524288 mmcblk0p17
179 18 655360 mmcblk0p18
179 19 2154496 mmcblk0p19
179 32 7822336 mmcblk1
179 33 7818240 mmcblk1p1
sorry again for my bad English.
boot.img is the kernel of ur phone..
Sent from my GT-B5512 using xda app-developers app
pavan_19 said:
boot.img is the kernel of ur phone..
Sent from my GT-B5512 using xda app-developers app
Click to expand...
Click to collapse
excuse can be more clear and explain how to make the dump file to img
Sorry dude no idea about that..
Sent from my GT-B5512 using xda app-developers app

Internal memory screwed up

Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
~ # ←[6nfdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
fdisk: can't open '/dev/block/mmcblk0p2': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p3
fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p4
fdisk -l /dev/block/mmcblk0p4
fdisk: can't open '/dev/block/mmcblk0p4': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
fdisk: can't open '/dev/block/mmcblk0p5': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p6
fdisk -l /dev/block/mmcblk0p6
fdisk: can't open '/dev/block/mmcblk0p6': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p7
fdisk -l /dev/block/mmcblk0p7
fdisk: can't open '/dev/block/mmcblk0p7': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p8
fdisk -l /dev/block/mmcblk0p8
fdisk: can't open '/dev/block/mmcblk0p8': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p9
fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p10
fdisk -l /dev/block/mmcblk0p10
fdisk: can't open '/dev/block/mmcblk0p10': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p11
fdisk -l /dev/block/mmcblk0p11
fdisk: can't open '/dev/block/mmcblk0p11': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p12
fdisk -l /dev/block/mmcblk0p12
fdisk: can't open '/dev/block/mmcblk0p12': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p13
fdisk -l /dev/block/mmcblk0p13
fdisk: can't open '/dev/block/mmcblk0p13': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p14
fdisk -l /dev/block/mmcblk0p14
fdisk: can't open '/dev/block/mmcblk0p14': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p15
fdisk -l /dev/block/mmcblk0p15
fdisk: can't open '/dev/block/mmcblk0p15': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p16
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
fdisk: can't open '/dev/block/mmcblk0p17': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p18
fdisk -l /dev/block/mmcblk0p18
fdisk: can't open '/dev/block/mmcblk0p18': I/O error
mounting /data in recovery:
Code:
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
E:Unable to mount '/data'
Same error on all recoverys CWM / TWRP
Perhaps someone can give an advice
Try formatting system, data and cache then install broodROM RC5 again, it might work.
Did you use the correct recovery while changing roms? you need to use cwm 5.0.0.4 atleast
Flash recovery through ODIN...
Sent from my GT-I9001 using Tapatalk 2
broodplank1337 said:
Try formatting system, data and cache then install broodROM RC5 again, it might work.
Did you use the correct recovery while changing roms? you need to use cwm 5.0.0.4 atleast
Click to expand...
Click to collapse
How can i format data with adb?
I used CWM 6.0.2.7
recovery stucks always at formating data... until i kill by pressing power button
In recovery all functions where mounting /data is not needed are working.
Works
format system
format cache
wipe android secur
Fails
mount data
wipe dalvik
fix permissions
buffo1987 said:
Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
~ # ←[6nfdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
fdisk: can't open '/dev/block/mmcblk0p2': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p3
fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p4
fdisk -l /dev/block/mmcblk0p4
fdisk: can't open '/dev/block/mmcblk0p4': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
fdisk: can't open '/dev/block/mmcblk0p5': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p6
fdisk -l /dev/block/mmcblk0p6
fdisk: can't open '/dev/block/mmcblk0p6': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p7
fdisk -l /dev/block/mmcblk0p7
fdisk: can't open '/dev/block/mmcblk0p7': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p8
fdisk -l /dev/block/mmcblk0p8
fdisk: can't open '/dev/block/mmcblk0p8': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p9
fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p10
fdisk -l /dev/block/mmcblk0p10
fdisk: can't open '/dev/block/mmcblk0p10': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p11
fdisk -l /dev/block/mmcblk0p11
fdisk: can't open '/dev/block/mmcblk0p11': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p12
fdisk -l /dev/block/mmcblk0p12
fdisk: can't open '/dev/block/mmcblk0p12': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p13
fdisk -l /dev/block/mmcblk0p13
fdisk: can't open '/dev/block/mmcblk0p13': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p14
fdisk -l /dev/block/mmcblk0p14
fdisk: can't open '/dev/block/mmcblk0p14': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p15
fdisk -l /dev/block/mmcblk0p15
fdisk: can't open '/dev/block/mmcblk0p15': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p16
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
fdisk: can't open '/dev/block/mmcblk0p17': I/O error
~ # ←[6nfdisk -l /dev/block/mmcblk0p18
fdisk -l /dev/block/mmcblk0p18
fdisk: can't open '/dev/block/mmcblk0p18': I/O error
Perhaps someone can give an advice
Click to expand...
Click to collapse
did you use TWRP recovery ??
zikozoko said:
did you use TWRP recovery ??
Click to expand...
Click to collapse
cwm 6.0.2.7
Now i tried several recoverys TWRP and CWM but they are all working same without /data
flased broodrom rc5 again, stuck on boot. Can not factory reset, /data still not mountabel
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Or u can flash a stock rom via Odin and after booting install another recovery (ex 5.5.0.4 the most stable for me) and another costum rom.
VEREY IMPORTANT make sure u have the right AriesVE.ops. Try to download from SamMobile.
broodplank1337 said:
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Click to expand...
Click to collapse
Looks quite interesting.
I#m not sure what i have to do:
connect phone to ubuntu vm
Terminal:
Code:
$ adb busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
$ cd /sdcard/
$ tar -c data.img.ext4 > fix.tar
$ md5sum -t fix.tar >> fix.tar
$ mv fix.tar fix.tar.md5
2. Flash fix.tar.md5 as one package with odin
right?
broodplank1337 said:
I think your solution must be this:
You need to flash an empty data.img.ext4 to your phone using odin, I did it once, and it succeeded! But you first need to make it:
busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
1gb empty data.img.ext4 file, which can be flashed to restore the paritition
pack the file for odin:
tar -c data.img.ext4 > fix.tar
md5sum -t fix.tar >> fix.tar
mv fix.tar fix.tar.md5
So you either need cygwin or a native linux shell.
Click to expand...
Click to collapse
Hi , TNX
What about this script should run on recovery :
Code:
cat /dev/zero > /dev/block/mmcblk0pX
Code:
[email protected]:~$ adb shell
~ # busybox dd if=/dev/zero of=/sdcard/data.img.ext4 bs=1M count=1024
phone crashes -> data.img.ext4 is only 661 MB
will retry...
I think you did not meant me to do this on the phone.
Code:
[email protected]:~$ cd resc/
[email protected]:~/resc$ busybox dd if=/dev/zero of=^Cata.img.ext4 bs=1M count=1024
[email protected]:~/resc$ busybox dd if=/dev/zero of=data.img.ext4 bs=1M count=1024
1024+0 records in
1024+0 records out
[email protected]:~/resc$ tar -c data.img.ext4 > fix.tar
[email protected]:~/resc$ md5sum -t fix.tar >> fix.tar
[email protected]:~/resc$ mv fix.tar fix.tar.md5
I got the file now
Odin
Code:
Check MD5 FileName...
MD5 File Name : fix.tar
Open File Name : fix.tar
Check MD5 ...
Tail MD5 : 5654164EA05D41668D50F97731E2EB5A
Image MD5 : 5654164EA05D41668D50F97731E2EB5A
Check MD5 ... ok
<1> Added!!!
<1> Detected!!!
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> e - unknown file - "data.img.ext4"
<1> set download environment.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
Problem still exits
buffo1987 said:
Hallo guys,
got a little problem with my phone
it crashed while restoring an backup, now internal memory seems to be messed up.
1. Download Mode is working (flashed StockRom and Broodrom rc5)
2. I can reboot to recovery (I can flash other recovery, from internal sdcard, mounting USB works)
3. Mounting /system /data -> Recovery crashes
4. Factroy Reset does not work
3. When i try to flash a rom.zip it seems that only kernel is changed.
4. Factory Reset is not working
5. I can connect with adb
Perhaps you can have a look on the following outputs
fdisk -l
mounting /data in recovery:
Code:
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
E:Unable to mount '/data'
Same error on all recoverys CWM / TWRP
Perhaps someone can give an advice
Click to expand...
Click to collapse
Hey Buffo,
I have the same problem after trying your test-versions. I could "revive" all partitions but data by downgrading recovery to 5.5.04 and formating system and cache then. But also data could not be formatted via 5.5.04 so I also will try broods proposal...
btw. this does not work to solve it.
Code:
cat /dev/zero > /dev/block/mmcblk0pX
magicw said:
Hey Buffo,
I have the same problem after trying your test-versions. I could "revive" all partitions but data by downgrading recovery to 5.5.04 and formating system and cache then. But also data could not be formatted via 5.5.04 so I also will try broods proposal...
btw. this does not work to solve it.
Code:
cat /dev/zero > /dev/block/mmcblk0pX
Click to expand...
Click to collapse
Sad to here that,
removed all cwm 6.0.2.7 downloads from my post.
At least flashing a stock rom makes the phone look untouched, so i will send it for repair...
I already tried to format data with adb: mke2fs -L data -b 4096 -m 0 -F /dev/block/mmcblk0p17, but also just works with /system + /cache
When exactly did it happen for you?
hey here i found something
i do not know if it helps but read it and decide it looks like your problem in a way
for another device but maybe helpful
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
krislibaeer said:
hey here i found something
i do not know if it helps but read it and decide it looks like your problem in a way
for another device but maybe helpful
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
Click to expand...
Click to collapse
interesting. I've run parted via adb and mmcblk0p17 shows 1447 MB - shouldn't this be 1024 MB only?
magicw said:
interesting. I've run parted via adb and mmcblk0p17 shows 1447 MB - shouldn't this be 1024 MB only?
Click to expand...
Click to collapse
Code:
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5120 mmcblk0p8 //boot
179 9 7000 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 532480 mmcblk0p15 //system
179 16 102400 mmcblk0p16 //cache
179 17 1413120 mmcblk0p17 //data
179 18 204800 mmcblk0p18 //preload
179 19 500 mmcblk0p19 // These
179 20 3596 mmcblk0p20 // partitions
179 21 5120 mmcblk0p21 // are
179 22 20000 mmcblk0p22 // either
179 23 5120 mmcblk0p23 // empty
179 24 7000 mmcblk0p24 // or
179 25 5120 mmcblk0p25 // backup
179 26 5120 mmcblk0p26 // partitions
179 27 5120 mmcblk0p27 //efs
179 28 5228544 mmcblk0p28 //internal sdcard
Xistance said:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
Click to expand...
Click to collapse
wtf your internal sdcard is 4gb? (if you look at the total blocks)
check my output with 8gb internal
Code:
cat proc/partitions
major minor #blocks name
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5228544 mmcblk0p28
broodplank1337 said:
wtf your internal sdcard is 4gb? (if you look at the total blocks)
check my output with 8gb internal
Code:
cat proc/partitions
major minor #blocks name
179 0 7755776 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5228544 mmcblk0p28
Click to expand...
Click to collapse
Oh yeah sorry. I took it from arco on his Galaxy W and forgot they had different sizes =.=.
Edit : Fixed ^^
Code:
(parted) check
check
check
Error: Can't have a partition outside the disk!
Code:
major minor #blocks name
179 0 [COLOR="Red"]7552000 [/COLOR]mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 [COLOR="Red"]5024768 [/COLOR]mmcblk0p28
buffo1987 said:
Code:
(parted) check
check
check
Error: Can't have a partition outside the disk!
Code:
major minor #blocks name
179 0 [COLOR="Red"]7552000 [/COLOR]mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 [COLOR="Red"]5024768 [/COLOR]mmcblk0p28
Click to expand...
Click to collapse
the partition has a shift of 203776 (both have same size )
that is weird

Shield Partition Map For Kernel?

Hello all!
Say, I've noticed the 2.55Ghz Overclock Kernel has been essentially abandoned && no longer works on the latest update.. I've been looking into creating my own custom Kernel that apply's the same essential overclock but supports the latest updates (91~).
My question is if anyone either knows which partition the kernel is on, or how I can go about figuring that out.
If anyone has a updated Rooted Kernel they are willing to dump and post i'd be more than happy to have a go at it; rather than have me figure it out.
Anyways, I've learned that the /proc/ folder lacks both emmc and mtd partition tables... So after doing some digging i've got all the mmcblk partition names and sizes, but god only knows which one is the Kernel. All I really need is the Kernel, but any other information is more than welcomed.
Thank you to anyone who can help!
Code:
major minor #blocks name
179 0 15267840 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 786432 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 786432 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 32768 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 13551616 mmcblk0p12
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 7761920 mmcblk1
179 49 7757824 mmcblk1p1
Second question:
Is it safe to install Cyanogenmod on the shield? I can't seem to really find anything about the shield with CM on it. I know there is a built in ROM dumper that labels all the partitions so if that works it would also solve the first question.
Thanks.

[Q] How to dump files from a bootloader-locked Moto G ?

OK, so I found this post http://forum.xda-developers.com/showthread.php?t=2450045 and thought I would make the attempt. Even though the prerequisites say " Rooted Device " I went thru the steps. This is what I ended up with :
1|[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 512 mmcblk0p19
179 20 8 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 10240 mmcblk0p32
259 1 546944 mmcblk0p33
259 2 1130496 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 5791616 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
[email protected]:/ $
For background info, this device is a Cricket XT1045. Not unlockable thru Motorola site.
I see on another site that someone managed to dump a ROM from this device : CRICKET_XT1045_4.4.4_KXB21.14-L1.45_cid16_CFC.xml.zip - FileFactory.
What partition from those listed above do I pull from the device ?
Any guidance will be greatly appreciated.
CRICKET_XT1045_4.4.4_KXB21.14-L1.45_cid16_CFC.xml.zip was not dumped by someone - it's a Motorola Factory Firmware Image.
The following command will dump the entire system partition.
adb pull /system​
If you want Kernel or Recovery you need root, but those are included in the above factory firmware image.
Thanks for the help, but that command < adb pull/system > only gave me a list of other adb commands.
Now, if I follow you, with the ROM mentioned being directly from Motorola, does that mean that an individual cannot dump his/her personal ROM ?
My goal in all of this is to compare a stock ROM with the bootloader locked against that same ROM having an unlocked bootloader.
And I want to dump my specific ROM to search thru it in an attempt to find my unique " unlock data " string.
I got my feet wet in hex editing during my FTA days. This is quite a bit more detailed, but with Motorola unable to unlock Cricket-branded devices, I have to try.
Hell-On-Wheels said:
Thanks for the help, but that command < adb pull/system > only gave me a list of other adb commands.
Click to expand...
Click to collapse
There should be a space between pull and /system.
lost101 said:
There should be a space between pull and /system.
Click to expand...
Click to collapse
Thanks, but holy moly ! that is alot of output.
I saw a few files that look promising > /firmware, /permissions, /DeviceAuthApp. I saw peregrine mentioned a couple times.
Which of these folders contains the actual 4.4.4 operating system ?
You just dumped the 'System' partition - you are looking at the operating system. There are other partitions that relate to the functioning of Android, and your 'holy grail' could well be located there. More info here: http://forum.xda-developers.com/showthread.php?t=2540799

Categories

Resources