Database Info

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

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.

16 gb - repatition

I've erased all of my partitions and need to creat new partitions.. but i don't know which partitions was in my phone.
Can anyone post partition list from fdisk please?
Instructions:
1. adb shell
2. fdisk /dev/block/mmcblk0
3. p
4. take a screenshot
5. post it here
Thank you very much

READ THE RULES!!! Wrong section completely
Sent from my HTC VLE_U using xda app-developers app

1. Wrong section, which really makes me mad.
2. Can't repartition without S-OFF, don't even get me started on that.
So before you get all "But I'm a noob, help me" or "dude it was a simple question, don't flame ME!", remember this - this happens too much and us users here don't like a dirty forum. Read the rules before you make another useless post on XDA.

I think you guys dropped it on him too badly he still hasn't replied on the thread lol
Sent from a man, using a mobile phone

Moved To Q&A​
Do not start Q&A threads in the dev section! This just clutters up our great forum and irritates other users. Also cleaned this thread, there is no need to keep telling this user of his mistake. Please just report and let us mods sort it. Thanks.​

Well it is impossible to erase partitions without S-OFF as the NAND write protection will prohibit him from doing that.
Sent from my locked, tampered ville

Maybe this is useful info:
major minor #blocks name
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 32 mmcblk0p13
179 14 6144 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 46080 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 8190 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 16383 mmcblk0p22
179 23 1022 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 4096 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 4 mmcblk0p27
179 28 256 mmcblk0p28
179 29 16 mmcblk0p29
179 30 1280 mmcblk0p30
179 31 64 mmcblk0p31
179 32 99752 mmcblk0p32
179 33 1703935 mmcblk0p33
179 34 262143 mmcblk0p34
179 35 2490367 mmcblk0p35
179 36 10418176 mmcblk0p36
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"

Possible to dump the stock recovery

Hey guys.
Is there a way to extract the stock recovery from the one mini?

Yes using adb shell command: "dd if=PARTITION_OF_RECOVERY of =/sdcard/recovery.img" then copy recovery.img from sdcard to your PC.
It will have 13mbs, if you extract it with cygwin and then repack it will have 4mb.
To know the partition of recovery, adb shell "cat /proc/partitions"
xpirt

xpirt said:
Yes using adb shell command: "dd if=PARTITION_OF_RECOVERY of =/sdcard/recovery.img" then copy recovery.img from sdcard to your PC.
It will have 13mbs, if you extract it with cygwin and then repack it will have 4mb.
To know the partition of recovery, adb shell "cat /proc/partitions"
xpirt
Click to expand...
Click to collapse
Okay i will get the partition name with this cmd?
"adb shell "cat /proc/partitions"
And the result i fill in the name here for this term: "PARTITION_OF_RECOVERY " ?

johnsk said:
Okay i will get the partition name with this cmd?
cat /proc/partitions
And the result i fill in the name here for this term: "PARTITION_OF_RECOVERY " ?
Click to expand...
Click to collapse
Open cmd into adb path, type "adb shell" then type "cat /proc/partitions", save recovery partition.
Then type "dd if=XXXXXXXXX of=/sdcard/recovery.img".
xpirt

xpirt said:
Open cmd into adb path, type "adb shell" then type "cat /proc/partitions", save recovery partition.
Then type "dd if=XXXXXXXXX of=/sdcard/recovery.img".
xpirt
Click to expand...
Click to collapse
Ui nice.
And now?
Code:
major minor #blocks name
7 0 45770 loop0
7 1 16664 loop1
7 2 5229 loop2
7 3 12506 loop3
7 4 27059 loop4
7 5 9387 loop5
7 6 24980 loop6
7 7 26019 loop7
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 46080 mmcblk0p16
179 17 10240 mmcblk0p17
179 18 5120 mmcblk0p18
179 19 8190 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 1022 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 20480 mmcblk0p24
179 25 4 mmcblk0p25
179 26 256 mmcblk0p26
179 27 16 mmcblk0p27
179 28 1280 mmcblk0p28
179 29 64 mmcblk0p29
179 30 32767 mmcblk0p30
179 31 16384 mmcblk0p31
179 32 16383 mmcblk0p32
179 33 2195455 mmcblk0p33
179 34 688127 mmcblk0p34
179 35 11927552 mmcblk0p35
254 0 45769 dm-0
254 1 16663 dm-1
254 2 5229 dm-2
254 3 12505 dm-3
254 4 27058 dm-4
254 5 9387 dm-5
254 6 24979 dm-6
254 7 26019 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 24980 loop9
254 9 24979 dm-9
7 10 2111 loop10
254 10 2110 dm-10
7 11 22901 loop11
254 11 22900 dm-11
7 12 2111 loop12
254 12 2110 dm-12
[email protected]:/ $

johnsk said:
Ui nice.
And now?
Code:
major minor #blocks name
7 0 45770 loop0
7 1 16664 loop1
7 2 5229 loop2
7 3 12506 loop3
7 4 27059 loop4
7 5 9387 loop5
7 6 24980 loop6
7 7 26019 loop7
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 46080 mmcblk0p16
179 17 10240 mmcblk0p17
179 18 5120 mmcblk0p18
179 19 8190 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 1022 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 20480 mmcblk0p24
179 25 4 mmcblk0p25
179 26 256 mmcblk0p26
179 27 16 mmcblk0p27
179 28 1280 mmcblk0p28
179 29 64 mmcblk0p29
179 30 32767 mmcblk0p30
179 31 16384 mmcblk0p31
179 32 16383 mmcblk0p32
179 33 2195455 mmcblk0p33
179 34 688127 mmcblk0p34
179 35 11927552 mmcblk0p35
254 0 45769 dm-0
254 1 16663 dm-1
254 2 5229 dm-2
254 3 12505 dm-3
254 4 27058 dm-4
254 5 9387 dm-5
254 6 24979 dm-6
254 7 26019 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 24980 loop9
254 9 24979 dm-9
7 10 2111 loop10
254 10 2110 dm-10
7 11 22901 loop11
254 11 22900 dm-11
7 12 2111 loop12
254 12 2110 dm-12
[email protected]:/ $
Click to expand...
Click to collapse
Sorry was "cat /proc/emmc"
xpirt

xpirt said:
Sorry was "cat /proc/emmc"
xpirt
Click to expand...
Click to collapse
Code:
cat /proc/emmc
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 85fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 29fffe00 00000200 "cache"
mmcblk0p35: 2d8000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 01fffc00 00000200 "reserve"
[email protected]:/ $
Is this right?
dd if=mmcblk0p32 of=/sdcard/recovery.img

johnsk said:
Code:
cat /proc/emmc
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 85fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 29fffe00 00000200 "cache"
mmcblk0p35: 2d8000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 01fffc00 00000200 "reserve"
[email protected]:/ $
Is this right?
dd if=mmcblk0p32 of=/sdcard/recovery.img
Click to expand...
Click to collapse
Now type "dd if=mmcblk0p32 of=/sdcard/recovery.img" then copy recovery.img from sdcard to pc.
xpirt

xpirt said:
Now type "dd if=mmcblk0p32 of=/sdcard/recovery.img" then copy recovery.img from sdcard to pc.
xpirt
Click to expand...
Click to collapse
Now i get this error
Code:
127|[email protected]:/ $ dd if=mmcblk0p32 of=/sdcard/recovery.img
dd if=mmcblk0p32 of=/sdcard/recovery.img
mmcblk0p32: cannot open for read: No such file or directory
1|[email protected]:/ $

johnsk said:
Now i get this error
Code:
127|[email protected]:/ $ dd if=mmcblk0p32 of=/sdcard/recovery.img
dd if=mmcblk0p32 of=/sdcard/recovery.img
mmcblk0p32: cannot open for read: No such file or directory
1|[email protected]:/ $
Click to expand...
Click to collapse
Sorry again xD This is correct; "dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img".
xpirt

xpirt said:
Sorry again xD This is correct; "dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img".
xpirt
Click to expand...
Click to collapse
No problem.
Permission denied...
[email protected]:/ $ dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img
/dev/block/mmcblk0p32: cannot open for read: Permission denied
1|[email protected]:/ $
Click to expand...
Click to collapse
The Device is running in Android, S-OFF!, Bootloader is locked and USB Debugging is on.

johnsk said:
No problem.
Permission denied...
The Device is running in Android, S-OFF!, Bootloader is locked and USB Debugging is on.
Click to expand...
Click to collapse
Type "su" and then "dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img".
xpirt

xpirt said:
Type "su" and then "dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img".
xpirt
Click to expand...
Click to collapse
Is su possible without root on the device?

johnsk said:
Is su possible without root on the device?
Click to expand...
Click to collapse
You have to be rooted... I thought if you s-offed you rotted too.. Btw it's not possible to backup stock recovery without root.
xpirt

johnsk said:
Is su possible without root on the device?
Click to expand...
Click to collapse
su is to run dd as root. sudo would work as well.

xpirt said:
You have to be rooted... I thought if you s-offed you rotted too.. Btw it's not possible to backup stock recovery without root.
xpirt
Click to expand...
Click to collapse
This device is a test device from htc for the press.
It arrived with S-Off and without root offcourse.
I want to flash TWRP to root the device but before i want to backup the stock recovery.

johnsk said:
This device is a test device from htc for the press.
It arrived with S-Off and without root offcourse.
I want to flash TWRP to root the device but before i want to backup the stock recovery.
Click to expand...
Click to collapse
OK so download TWRP.img, reboot into fastboot mode and into folder with adb type "fastboot boot twrp_downloaded.img".
It will boot into TWRP so backup partitions you want
xpirt

xpirt said:
OK so download TWRP.img, reboot into fastboot mode and into folder with adb type "fastboot boot twrp_downloaded.img".
It will boot into TWRP so backup partitions you want
xpirt
Click to expand...
Click to collapse
Ok i will try and report in a few minutes.

xpirt said:
OK so download TWRP.img, reboot into fastboot mode and into folder with adb type "fastboot boot twrp_downloaded.img".
It will boot into TWRP so backup partitions you want
xpirt
Click to expand...
Click to collapse
Okay next error ^^
C:\Android>fastboot boot Twrp-2.6.0.0.img
downloading 'boot.img'...
OKAY [ 1.103s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.106s
Click to expand...
Click to collapse

johnsk said:
Okay next error ^^
Click to expand...
Click to collapse
Look here: http://forum.cyanogenmod.com/topic/...flash-recovery-not-allowed-error/#entry394354
A solution of your problem.. But I don't know if you have PD98IMG.zip or other name, make sure you know the name of this file than proceed.
And use fastboot boot recovery.img not flash!
xpirt

[Q] NAND flash error, cant mount EMMC but my phone work nice

Hi guys I've had some problems with my lollipop 5.1 android, mtk 6582.
something happen, now when I try do a test in spflash tools, it says ERROR: NAND Flash was not detected, y cant mount emmc in my twrp... I can flash all and my phone load the lollipop, but says "the internal storage has error" then ask me if i want format the internal partition....
the Titanium backup can recognize the storage and says that the internal storage have 2.07GB (wtf?) and ROM system have 914MB (nice)... But my phone have 8 GB...
Can someone help me, What should i do?
Thank you very much
Code:
cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00004800 00005000 "protect_f"
emmc_p3: 00009800 00005000 "protect_s"
emmc_p4: 0001ec00 00003000 "sec_ro"
emmc_p5: 00028c00 001c2000 "android"
emmc_p6: 001eac00 0003f000 "cache"
emmc_p7: 00229c00 00400000 "usrdata"
emmc_p8: 00629c00 0085a000 "fat"
~ # cat /proc/partitions
major minor #blocks name
179 0 7609856 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 921600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 2097152 mmcblk0p7
179 8 4378624 mmcblk0p8
179 96 512 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 15114240 mmcblk1
179 129 15113216 mmcblk1p1

How to identify userdata partition on an unrooted Android device?

Hi all,
I was trying to identify userdata partition after
- adb shell
- cat /proc/partitions
on an unrooted Oneplus 2.
Here below was the result.
How to identify which one is userdata partition?
Thanks in advance.
Cheers,
Wen
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 81920 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 128 mmcblk0p3
179 4 128 mmcblk0p4
179 5 1 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 128 mmcblk0p7
179 8 1536 mmcblk0p8
179 9 1 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 1 mmcblk0p14
179 15 1 mmcblk0p15
179 16 8 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 8096 mmcblk0p22
179 23 16192 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 96 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 500 mmcblk0p31
259 0 500 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 65536 mmcblk0p35
259 4 65536 mmcblk0p36
259 5 32768 mmcblk0p37
259 6 1024 mmcblk0p38
259 7 512 mmcblk0p39
259 8 512 mmcblk0p40
259 9 262144 mmcblk0p41
259 10 2621440 mmcblk0p42
259 11 11980783 mmcblk0p43
179 32 4096 mmcblk0rpmb

If you have an eMMC internal storage you can see names and partitions at same time:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/

xXx yYy said:
If you have an eMMC internal storage you can see names and partitions at same time:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
Click to expand...
Click to collapse
Thanks for your reply.
After
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
It returns
Code:
/dev/block/platform/msm_sdcc.1/by-name/: Permission denied
How to resolve it?
Thanks.

Android must be root to successfully run the cmd.

xXx yYy said:
Android must be root to successfully run the cmd.
Click to expand...
Click to collapse
Thanks for your reply.
I just rooted the device.
But after
Code:
adb root
It returns
Code:
adbd cannot run as root in production builds
How to solve it?
Thanks in advance.

No way.