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"

[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

TWRP Bug Corrupted Partitions

Well I have my phone soft-bricked right now and my partitions are extremely messed up, I was wondering if anyone was so kind to run the print command for parted and show me the image, since I need to know what the partition numbers are so I can delete them then recreate, thanks.

flare4000 said:
Well I have my phone soft-bricked right now and my partitions are extremely messed up, I was wondering if anyone was so kind to run the print command for parted and show me the image, since I need to know what the partition numbers are so I can delete them then recreate, thanks.
Click to expand...
Click to collapse
here is a more detailed layout from the gingerbread firmware.
Here is from mine with hboot 1.29.xxxxxx with 3.33 firmware
Code:
[email protected]:/ $ cat proc/emmc
cat proc/emmc
dev: size erasesize name
mmcblk0p32: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffc00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p24: 077f5c00 00000200 "cache"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p25: 00008000 00000200 "extra"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p19: 01000000 00000200 "adsp"
mmcblk0p18: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
[email protected]:/ $
Hope this helps.

heavy_metal_man said:
here is a more detailed layout from the gingerbread firmware.
Here is from mine with hboot 1.29.xxxxxx with 3.33 firmware
Code:
[email protected]:/ $ cat proc/emmc
cat proc/emmc
dev: size erasesize name
mmcblk0p32: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffc00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p24: 077f5c00 00000200 "cache"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p25: 00008000 00000200 "extra"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p19: 01000000 00000200 "adsp"
mmcblk0p18: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
[email protected]:/ $
Hope this helps.
Click to expand...
Click to collapse
Thanks for that but that is not what I need I need someone to run the print command using parted, the thing that I really need to know is the partition numbers, because there are no resources for the sensation I would be taking a wild guess when removing the partitions and may delete a valuable partition such as the radio. This is the website that I am currently referring to http://ananthgs4geeks.blogspot.co.uk/2012/10/s2-soft-brick-bug-fix-mmccaperase-brick.html The reason that I cannot run the command myself is because my partitions are extremely messed up. Thanks again for the help.

flare4000 said:
Thanks for that but that is not what I need I need someone to run the print command using parted, the thing that I really need to know is the partition numbers, because there are no resources for the sensation I would be taking a wild guess when removing the partitions and may delete a valuable partition such as the radio. This is the website that I am currently referring to http://ananthgs4geeks.blogspot.co.uk/2012/10/s2-soft-brick-bug-fix-mmccaperase-brick.html The reason that I cannot run the command myself is because my partitions are extremely messed up. Thanks again for the help.
Click to expand...
Click to collapse
every time i run the command i get
Code:
error: cant have overlapping partitions
here is a cat proc/partitions if its any use :/
Code:
cat proc/partitions
major minor #blocks name
179 0 2359296 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 32367 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 20442 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 256 mmcblk0p16
179 17 40960 mmcblk0p17
179 18 8190 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16383 mmcblk0p21
179 22 819199 mmcblk0p22
179 23 1223409 mmcblk0p23
179 24 122839 mmcblk0p24
179 25 32 mmcblk0p25
179 26 4096 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 4 mmcblk0p29
179 30 256 mmcblk0p30
179 31 16 mmcblk0p31
179 32 1022 mmcblk0p32
i couldnt get past the print issue.

heavy_metal_man said:
every time i run the command i get
Code:
error: cant have overlapping partitions
here is a cat proc/partitions if its any use :/
Code:
cat proc/partitions
major minor #blocks name
179 0 2359296 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 32367 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 20442 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 256 mmcblk0p16
179 17 40960 mmcblk0p17
179 18 8190 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16383 mmcblk0p21
179 22 819199 mmcblk0p22
179 23 1223409 mmcblk0p23
179 24 122839 mmcblk0p24
179 25 32 mmcblk0p25
179 26 4096 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 4 mmcblk0p29
179 30 256 mmcblk0p30
179 31 16 mmcblk0p31
179 32 1022 mmcblk0p32
i couldnt get past the print issue.
Click to expand...
Click to collapse
Well got past the print issue but that doesn't help so I'm trying this now http://android-revolution-hd.blogspot.ca/2013/10/fix-data-htc-one.html if you are using 4ext as your recovery can you tell me what it says in info as I want to know how big each partition is. Thanks again for your help.

flare4000 said:
Well got past the print issue but that doesn't help so I'm trying this now http://android-revolution-hd.blogspot.ca/2013/10/fix-data-htc-one.html if you are using 4ext as your recovery can you tell me what it says in info as I want to know how big each partition is. Thanks again for your help.
Click to expand...
Click to collapse
{
"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"
}
Sent from my HTC Desire S using Tapatalk

heavy_metal_man said:
View attachment 2855506
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Well thanks for the help but I think I finally hit a stump, my phone is now mounting the system and cache but no matter what I do the data will not mount.

flare4000 said:
Well thanks for the help but I think I finally hit a stump, my phone is now mounting the system and cache but no matter what I do the data will not mount.
Click to expand...
Click to collapse
Does the formatting finish without any errors?
Sent from my HTC Desire S using Tapatalk

heavy_metal_man said:
Does the formatting finish without any errors?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
The data partition? The formatting works most of the time, but yeah it does finish without errors, right now in 4ext the info is showing that all 3 partitions is mounted but I cannot flash any roms.

flare4000 said:
The data partition? The formatting works most of the time, but yeah it does finish without errors, right now in 4ext the info is showing that all 3 partitions is mounted but I cannot flash any roms.
Click to expand...
Click to collapse
in 4ext go try tools/wipe or format ext4/ data and see what happens. post any errors please

heavy_metal_man said:
in 4ext go try tools/wipe or format ext4/ data and see what happens. post any errors please
Click to expand...
Click to collapse
Well, can't do that now, pretty sure my device is bricked.

flare4000 said:
Well, can't do that now, pretty sure my device is bricked.
Click to expand...
Click to collapse
totally not powering on anymore bricked?
Damn. Im sorry to hear that

heavy_metal_man said:
totally not powering on anymore bricked?
Damn. Im sorry to hear that
Click to expand...
Click to collapse
Yup no power what so ever... got any recommendations for a cheap phone? lol

flare4000 said:
Yup no power what so ever... got any recommendations for a cheap phone? lol
Click to expand...
Click to collapse
The motorola moto g is a good price for the specs at hand
Im on a desire s at the moment. its quite good second hand, has revolutionary s-off but its a hacked hboot s-off and not radio s-off so no sim unlocking etc.
htc wildfire s is okay if you can find it at a good price, it will do to tide you over but it has no s-off and rom development has slowed considerably.
im not sure where you can get second hand phones in Canada but i imagine there is a market for it similar to what we have in the uk, like here

flare4000 said:
Yup no power what so ever... got any recommendations for a cheap phone? lol
Click to expand...
Click to collapse
I thing Samsung Galaxy S3 is good variant. But you can buy Sensation again, lol.
Sent from my HTC Sensation using XDA Premium 4 mobile app

[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