NAND Partitioning - Defy Android Development

Hey I just tried to repartition my NAND for some testing but it seams something don't like that I'm doing that. first the fdisk-log of my changes:
Command (m for help): n
First cylinder (13-122496, default 13):
Using default value 13
Last cylinder or +size or +sizeM or +sizeK (13-16, default 16):
Using default value 16
Since here I had a a new partition(mmcblk1p26) at the end of the table
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
After that the kernel only showed me 21 partitions instead of 26. Seems something really went wrong. A reboot ended in bootloader failure-message. Had to flash an sbf...
Click to expand...
Click to collapse
Is it just some configuration-problem or is the partition-table signed?

If there was a 'tag' feature like facebook here on xda, I would have tagged Epsylon3 in this thread
bdw, what will be the benefit of partitioning NAND.

It was just an experiment. If it would work we could resize the system-partition to a minimum and create a new one in ext4-format and toys like that
But it takes much time to test this because if it does not work you have to flash an sbf

m11kkaa said:
It was just an experiment. If it would work we could resize the system-partition to a minimum and create a new one in ext4-format and toys like that
But it takes much time to test this because if it does not work you have to flash an sbf
Click to expand...
Click to collapse
I have seen something like this in wildfire forum a long ago.
http://forum.xda-developers.com/showthread.php?t=1233340

just to archive:
Original Partition-Table(Normal-Mode):
Code:
Disk /dev/block/mmcblk1: 1958 MB, 1958739968 bytes
16 heads, 16 sectors/track, 14944 cylinders
Units = cylinders of 256 * 512 = 131072 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 2 2 128 83 Linux
/dev/block/mmcblk1p2 5 8 512 83 Linux
/dev/block/mmcblk1p3 9 12 512 83 Linux
/dev/block/mmcblk1p4 13 122496 15677952 5 Extended
/dev/block/mmcblk1p5 17 20 512 83 Linux
/dev/block/mmcblk1p6 21 24 512 83 Linux
/dev/block/mmcblk1p7 25 56 4096 83 Linux
/dev/block/mmcblk1p8 57 60 512 83 Linux
/dev/block/mmcblk1p9 61 64 512 83 Linux
/dev/block/mmcblk1p10 65 72 1024 83 Linux
/dev/block/mmcblk1p11 73 88 2048 83 Linux
/dev/block/mmcblk1p12 89 92 512 83 Linux
/dev/block/mmcblk1p13 93 96 512 83 Linux
/dev/block/mmcblk1p14 97 128 4096 83 Linux
/dev/block/mmcblk1p15 129 192 8192 83 Linux
/dev/block/mmcblk1p16 193 256 8192 83 Linux
/dev/block/mmcblk1p17 257 368 14336 83 Linux
/dev/block/mmcblk1p18 369 372 512 83 Linux
/dev/block/mmcblk1p19 373 376 512 83 Linux
/dev/block/mmcblk1p20 377 408 4096 83 Linux
/dev/block/mmcblk1p21 409 3024 334848 83 Linux
/dev/block/mmcblk1p22 3025 3028 512 83 Linux
/dev/block/mmcblk1p23 3029 3032 512 83 Linux
/dev/block/mmcblk1p24 3033 4632 204800 83 Linux
/dev/block/mmcblk1p25 4633 122496 15086592 83 Linux
Original Partition-Table(Expert-Mode):
Code:
Disk /dev/block/mmcblk1: 16 heads, 16 sectors, 14944 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 0 1 1 15 16 1 256 256 83
2 00 0 1 4 15 16 7 1024 1024 83
3 00 0 1 8 15 16 11 2048 1024 83
4 00 0 1 12 15 16 639 3072 31355904 05
5 00 0 1 4 15 16 7 1024 1024 83
6 00 15 16 7 15 15 11 2047 1024 83
7 00 15 15 11 15 14 43 3070 8192 83
8 00 15 14 43 15 13 47 11261 1024 83
9 00 15 13 47 15 12 51 12284 1024 83
10 00 15 12 51 15 11 59 13307 2048 83
11 00 15 11 59 15 10 75 15354 4096 83
12 00 15 10 75 15 9 79 19449 1024 83
13 00 15 9 79 15 8 83 20472 1024 83
14 00 15 8 83 15 7 115 21495 8192 83
15 00 15 7 115 15 6 179 29686 16384 83
16 00 15 6 179 15 5 243 46069 16384 83
17 00 15 5 243 15 4 355 62452 28672 83
18 00 15 4 355 15 3 359 91123 1024 83
19 00 15 3 359 15 2 363 92146 1024 83
20 00 15 2 363 15 1 395 93169 8192 83
21 00 15 1 395 14 16 963 101360 669696 83
22 00 14 16 963 14 15 967 771055 1024 83
23 00 14 15 967 14 14 971 772078 1024 83
24 00 14 14 971 14 13 523 773101 409600 83
25 00 14 13 523 14 12 627 1182700 30173184 83
And I think there is an signature in the table, because a little thing like changing system-id will brick the phone. but if I write back the table without changes that's no problem.

Excuse me... but why this thread under "dev section"?
I don't want to be annoying (like others i know), but this wouldn't be at General Section?

espaciosalter20 said:
Excuse me... but why this thread under "dev section"?
I don't want to be annoying (like others i know), but this wouldn't be at General Section?
Click to expand...
Click to collapse
LOL, this is developement of course.
@m11kkaa: I seriously think that u shud not go ahead with this project. This thing is really dangerous and we all want ur device to be alive.

two points:
1) you don't have todo everything which is possible (I read over the word "your", thanx anyway )
2) I have the theory that the partition-table is completely ignored by the bootloader and that he uses his own hardcoded table.
BTW, I should let repair my Defy as long as it's under warranty because the ear-piece is dead since months...

Related

[PARTITION LIST] Partition Information and RUU/OTA Files,Work In Progress, 01/10/2013

Hi Everyone!
Attached to this post I have created an excel file which contains what I know to date about the various partitions on the HTC One S (as you will see its not a lot). It includes brief and more lengthy descriptions, as well as what img and other files flash to those partitions from RUUs and OTA updates. It also includes some information I have gathered by viewing various partitions with a hex editor.
As you can see, this file is far from complete (as my own knowledge of these matters is similarly lacking). Some information may also be incorrect. I wanted to share this file in the hopes that developers and other members who may have more knowledge than I can contribute to making this file better, so that we can all understand our HTC One S's and what makes it tick.
If you want to assist this project, please feel free to post updated versions of this file to this thread. I will then merge those updates onto a master file and update the Original Thread with that info for easy access for others.
First I want to thank SneakyGhost who has already shared a basic text file with some information about some of the partitions on his public dropbox. (Sneaky, let me know and I can share that public dropbox on this link too if you see fit). We can let this post evolve with more development information too based on peoples suggestions.
Original Version 01/10/2013
-First draft with good info from SneakyGhost and very basic n00b stuff from AKToronto
Developers & Members Who Contributed:
SneakyGhost
[others to follow i hope]
Just wondering, is there any different between mmpcblk0p* and mmcblk0p* because when getting file from phone we type dd if=/dev/block/mmcblk0p* not mmpcblk0p*.... thx
Hello,
Here is some information I recieved from touch of jobo. Some of it might help.
1 emmc: (no) ruu: sbl1-?.img
2 emmc: (no) ruu: sbl2.img
3 emmc: (no) ruu: (no) data: PGFS, securoty, simlock, simunlock
4 emmc: (no) ruu: (no) data: htc-board-info, cid, imei
5 emmc: (no) ruu: (no) data: htc-board-info, cid, imei
6 emmc: (no) ruu: (no) data: macaddr, devid, imei, ..
7 emmc: (no) ruu: (no) data: PGFS, sbl2_update, sbl3, rpm,tz, ..
8 emmc: (no) ruu: (no) empty
9 emmc: (no) ruu: sbl3.img
10 emmc: (no) ruu: rpm.img
11 emmc: (no) ruu: tz.img
12 emmc: (no) ruu: hboot.nb0
13 emmc: (no) ruu: (no) data: htc-security-rec
14 emmc: (no) ruu: splash1.nb0 data: raw rgb565 540x960x2
15 emmc: (no) ruu: (no) empty
16 emmc: dsps ruu: (no) empty
17 emmc: radio ruu: radio.img mount: /firmware/radio vfat (fat16)
18 emmc: adsp ruu: adsp.img mount: /firmware/q6 vfat (fat16)
19 emmc: wcnss ruu: wcnss.img mount: /firmware/wcnss vfat (fat12)
20 emmc: radio_config ruu: rcdata.img @+0x10018C
21 emmc: boot ruu: boot_signed.img, bootable
22 emmc: recovery ruu: recovery_signed.img, bootable
23 emmc: misc ruu: (no) mostly empty, FNOC, FNOC
24 emmc: modem_st1 ruu: (no) data looks compressed or encrypted
25 emmc: modem_st2 ruu: (no) data looks compressed or encrypted
26 emmc: devlog ruu: (no) mount: /devlog ext4
27 emmc: (no) ruu: (no) empty
28 emmc: pdata ruu: (no) empty
29 emmc: (no) ruu: (no) empty
30 emmc: local ruu: (no) empty
31 emmc: extra ruu: (no) empty
32 emmc: (no) ruu: (no) empty
33 emmc: system ruu: system.img mount: /system ext4
34 emmc: cache ruu: (no) mount: /cache ext4
35 emmc: data ruu: (no) mount: /data ext4
36 emmc: fat ruu: (no) mount: /mnt/sdcard fat32
Rsotbiemrptson
cat2115 said:
Just wondering, is there any different between mmpcblk0p* and mmcblk0p* because when getting file from phone we type dd if=/dev/block/mmcblk0p* not mmpcblk0p*.... thx
Click to expand...
Click to collapse
No difference. Just a type-o on my part. Thx for the correction!
Rsotbiemrptson said:
Hello,
Here is some information I recieved from touch of jobo. Some of it might help.
1 emmc: (no) ruu: sbl1-?.img
2 emmc: (no) ruu: sbl2.img
3 emmc: (no) ruu: (no) data: PGFS, securoty, simlock, simunlock
4 emmc: (no) ruu: (no) data: htc-board-info, cid, imei
5 emmc: (no) ruu: (no) data: htc-board-info, cid, imei
6 emmc: (no) ruu: (no) data: macaddr, devid, imei, ..
7 emmc: (no) ruu: (no) data: PGFS, sbl2_update, sbl3, rpm,tz, ..
8 emmc: (no) ruu: (no) empty
9 emmc: (no) ruu: sbl3.img
10 emmc: (no) ruu: rpm.img
11 emmc: (no) ruu: tz.img
12 emmc: (no) ruu: hboot.nb0
13 emmc: (no) ruu: (no) data: htc-security-rec
14 emmc: (no) ruu: splash1.nb0 data: raw rgb565 540x960x2
15 emmc: (no) ruu: (no) empty
16 emmc: dsps ruu: (no) empty
17 emmc: radio ruu: radio.img mount: /firmware/radio vfat (fat16)
18 emmc: adsp ruu: adsp.img mount: /firmware/q6 vfat (fat16)
19 emmc: wcnss ruu: wcnss.img mount: /firmware/wcnss vfat (fat12)
20 emmc: radio_config ruu: rcdata.img @+0x10018C
21 emmc: boot ruu: boot_signed.img, bootable
22 emmc: recovery ruu: recovery_signed.img, bootable
23 emmc: misc ruu: (no) mostly empty, FNOC, FNOC
24 emmc: modem_st1 ruu: (no) data looks compressed or encrypted
25 emmc: modem_st2 ruu: (no) data looks compressed or encrypted
26 emmc: devlog ruu: (no) mount: /devlog ext4
27 emmc: (no) ruu: (no) empty
28 emmc: pdata ruu: (no) empty
29 emmc: (no) ruu: (no) empty
30 emmc: local ruu: (no) empty
31 emmc: extra ruu: (no) empty
32 emmc: (no) ruu: (no) empty
33 emmc: system ruu: system.img mount: /system ext4
34 emmc: cache ruu: (no) mount: /cache ext4
35 emmc: data ruu: (no) mount: /data ext4
36 emmc: fat ruu: (no) mount: /mnt/sdcard fat32
Rsotbiemrptson
Click to expand...
Click to collapse
Really helpful. Will add in to the file. Do you know what he is refering to with the (no) tag?
AKToronto said:
Really helpful. Will add in to the file. Do you know what he is refering to with the (no) tag?
Click to expand...
Click to collapse
Hello,
I have no Idea what the (no) means.
Rsotbiemrptson
AKToronto said:
Really helpful. Will add in to the file. Do you know what he is refering to with the (no) tag?
Click to expand...
Click to collapse
* emmc: (no) means the partition is not listed in /proc/emmc. otherwise it states the parition name from /proc/emmc
* ruu: (no) means it does not contains an image from a ruu. otherwise it states the filename of the image from the ruu.
* data: something interesting or recognizable
* mount: /mount/point/when/booted/ filesystemtype
-Jobo
EDIT: /proc/partitions lists the number of blocks for each.
Hi guys!
Nice thread. Just found it cuz i had no partition list, no complete one at least. Good work.
Credits for the initial few partitions should go to Tecardo though, i think i got the numbers from him.
I have just finished a Script that dumps all partitions to PC, well, all but Radio, System, Kernel, Data, Cache and the empty ones.
I will make a Dump of my two devices (normal Ville and Taiwan Ville 64gb) so you can maybe add a partition list for the SE variant here too.
Since Tec has a RIFF Box now and my old bricked device, we can maybe work some stuff out.
If we find out more information on the Partitions we could input it here too if you like. Just let us know.
regards,
Sneaky
Sneakyghost said:
Hi guys!
Nice thread. Just found it cuz i had no partition list, no complete one at least. Good work.
Credits for the initial few partitions should go to Tecardo though, i think i got the numbers from him.
I have just finished a Script that dumps all partitions to PC, well, all but Radio, System, Kernel, Data, Cache and the empty ones.
I will make a Dump of my two devices (normal Ville and Taiwan Ville 64gb) so you can maybe add a partition list for the SE variant here too.
Since Tec has a RIFF Box now and my old bricked device, we can maybe work some stuff out.
If we find out more information on the Partitions we could input it here too if you like. Just let us know.
regards,
Sneaky
Click to expand...
Click to collapse
That works for me! Im happy for you guys to edit the file and post, and then I can update the OP with that file too! Whatever works! Thanks again!
One S SE Partitions
I've got the cat /proc/emmc readout now, which is surprisingly only showing a few partitions on the One S SE.
I am unsure if that is a reliable readout. There is no mention of an SD or hboot partition. The device might need to run an insecure boot and be rooted for a complete readout.
If anyone can tell me how to obtain a complete listing i would be grateful. Thanks.
Find the listing attached.
AKToronto: you might be willing to integrate that excel sheet into the existing as a second sheet? Thanks.
Let me know if i can do anything to obtain more info. I've got a normal and an SE here so no worries doing some messing about. I just need precise infos what to do because my time is very limited. Sorry.
One Notice concerning the use of Excel: i hope you guys are aware that you need to set cell formatting to text only before inserting any hex or decimal values as excel loves to reformat them for you and hence mess them up! I'd recommend a different program to collect this data. Can't imagine if anything goes wrong when flashing raw stuff because someone read the wrong numbers from the sheet lol. There's guys with linux and a RIFF Box out here who might go by the partition offsets lol...
Sneakyghost said:
I've got the cat /proc/emmc readout now, which is surprisingly only showing a few partitions on the One S SE.
I am unsure if that is a reliable readout. There is no mention of an SD or hboot partition.
Click to expand...
Click to collapse
That is normal. See my list. The ones that say "emmc: (no)" are not listed in /proc/emmc on the OneS. The ones that say: "ruu: something.img", I mapped out by dumping the partitions from the device and comparing to images extracted from a RUU. The one labeled 'fat' is the sdcard partition.
-Jobo
Thanks.
Please specify compare dump to RUU. Are the dumps identical to the images in a RUU? So a hash compare would do the trick?
Or how do you go about? I have UltraEdit with UltraCompare. I could also compare line-by-line...
Sneakyghost said:
Thanks.
Please specify compare dump to RUU. Are the dumps identical to the images in a RUU? So a hash compare would do the trick?
Or how do you go about? I have UltraEdit with UltraCompare. I could also compare line-by-line...
Click to expand...
Click to collapse
You can't do a hash compare, as the dump from your device is typically bigger than the image from the RUU, so it won't match. If you know exactly from which RUU the images on the device come (and you haven't flashed any special/extra partitions, you could do a byte-for-byte or line-by-line compare.
I did it a bit more 'visually'. If you see roughly the same stuff in roughly the same place, it is (most probably) the same kind of image. For example, these are not identical, but similar enough to know it's the same kind of thing, just a different version:
Code:
rpm.img from a RUU:
00006d00 40 30 06 00 70 b5 a8 20 06 f0 ff fd 1d 4c 07 23 |@0..p.. .....L.#|
00006d10 21 68 1d a2 05 f0 40 ff 21 68 1b 25 ad 01 49 19 |[email protected]!h.%..I.|
00006d20 c8 61 a8 20 06 f0 f1 fd 61 68 01 23 1a a2 05 f0 |.a. ....ah.#....|
00006d30 33 ff 61 68 49 19 c8 61 a8 20 06 f0 e6 fd a1 68 |3.ahI..a. .....h|
00006d40 09 23 19 a2 05 f0 28 ff a1 68 49 19 c8 61 a8 20 |.#....(..hI..a. |
00006d50 06 f0 db fd e1 68 03 23 17 a2 05 f0 1d ff e1 68 |.....h.#.......h|
00006d60 49 19 c8 61 a8 20 06 f0 d0 fd 21 69 05 23 16 a2 |I..a. ....!i.#..|
00006d70 05 f0 12 ff 21 69 49 19 c8 61 70 bc 08 bc 00 20 |....!iI..ap.... |
00006d80 18 47 00 00 24 a3 03 00 61 70 70 73 20 68 61 6e |.G..$...apps han|
00006d90 64 6c 65 72 00 00 00 00 6d 6f 64 65 6d 20 68 61 |dler....modem ha|
00006da0 6e 64 6c 65 72 00 00 00 6c 70 61 73 73 20 68 61 |ndler...lpass ha|
00006db0 6e 64 6c 65 72 00 00 00 72 69 76 61 20 68 61 6e |ndler...riva han|
00006dc0 64 6c 65 72 00 00 00 00 64 73 70 73 20 68 61 6e |dler....dsps han|
00006dd0 64 6c 65 72 00 00 00 00 70 b5 80 20 06 f0 95 fd |dler....p.. ....|
00006de0 1d 4c 08 23 21 68 1d a2 05 f0 f6 fb 21 68 1b 25 |.L.#!h......!h.%|
00006df0 ad 01 49 19 08 62 80 20 06 f0 87 fd 61 68 02 23 |..I..b. ....ah.#|
00006e00 1a a2 05 f0 e9 fb 61 68 49 19 08 62 80 20 06 f0 |......ahI..b. ..|
00006e10 7c fd a1 68 0a 23 19 a2 05 f0 de fb a1 68 49 19 ||..h.#.......hI.|
00006e20 08 62 80 20 06 f0 71 fd e1 68 04 23 17 a2 05 f0 |.b. ..q..h.#....|
00006e30 d3 fb e1 68 49 19 08 62 80 20 06 f0 66 fd 21 69 |...hI..b. ..f.!i|
00006e40 06 23 16 a2 05 f0 c8 fb 21 69 49 19 08 62 70 bc |.#......!iI..bp.|
00006e50 08 bc 00 20 18 47 00 00 24 a3 03 00 61 70 70 73 |... .G..$...apps|
00006e60 20 63 68 61 6e 67 65 72 00 00 00 00 6d 6f 64 65 | changer....mode|
00006e70 6d 20 63 68 61 6e 67 65 72 00 00 00 6c 70 61 73 |m changer...lpas|
00006e80 73 20 63 68 61 6e 67 65 72 00 00 00 72 69 76 61 |s changer...riva|
00006e90 20 63 68 61 6e 67 65 72 00 00 00 00 64 73 70 73 | changer....dsps|
00006ea0 20 63 68 61 6e 67 65 72 00 00 00 00 06 28 12 d2 | changer.....(..|
00006eb0 78 44 00 79 00 18 87 44 02 04 06 08 0a 0c 07 a0 |xD.y...D........|
00006ec0 70 47 08 a0 70 47 09 a0 70 47 0a a0 70 47 0b a0 |pG..pG..pG..pG..|
00006ed0 70 47 0c a0 70 47 0d a0 70 47 00 00 41 50 53 53 |pG..pG..pG..APSS|
00006ee0 00 00 00 00 4d 50 53 53 5f 53 57 00 4c 50 41 53 |....MPSS_SW.LPAS|
00006ef0 53 00 00 00 52 49 56 41 00 00 00 00 44 53 50 53 |S...RIVA....DSPS|
00006f00 00 00 00 00 4d 50 53 53 5f 46 57 00 3c 75 6e 73 |....MPSS_FW.<uns|
mmcblk0p10 from my device:
00006d00 bc 08 bc 00 20 c0 43 18 47 a9 00 08 18 04 62 70 |.... .C.G.....bp|
00006d10 bc 08 bc 00 20 18 47 a4 a3 03 00 40 30 06 00 70 |.... [email protected]|
00006d20 b5 a0 20 06 f0 d3 fd 1d 4c 07 23 21 68 1d a2 05 |.. .....L.#!h...|
00006d30 f0 14 ff 21 68 1b 25 ad 01 49 19 c8 61 a0 20 06 |...!h.%..I..a. .|
00006d40 f0 c5 fd 61 68 01 23 1a a2 05 f0 07 ff 61 68 49 |...ah.#......ahI|
00006d50 19 c8 61 a0 20 06 f0 ba fd a1 68 09 23 19 a2 05 |..a. .....h.#...|
00006d60 f0 fc fe a1 68 49 19 c8 61 a0 20 06 f0 af fd e1 |....hI..a. .....|
00006d70 68 03 23 17 a2 05 f0 f1 fe e1 68 49 19 c8 61 a0 |h.#.......hI..a.|
00006d80 20 06 f0 a4 fd 21 69 05 23 16 a2 05 f0 e6 fe 21 | ....!i.#......!|
00006d90 69 49 19 c8 61 70 bc 08 bc 00 20 18 47 00 00 70 |iI..ap.... .G..p|
00006da0 94 03 00 61 70 70 73 20 68 61 6e 64 6c 65 72 00 |...apps handler.|
00006db0 00 00 00 6d 6f 64 65 6d 20 68 61 6e 64 6c 65 72 |...modem handler|
00006dc0 00 00 00 6c 70 61 73 73 20 68 61 6e 64 6c 65 72 |...lpass handler|
00006dd0 00 00 00 72 69 76 61 20 68 61 6e 64 6c 65 72 00 |...riva handler.|
00006de0 00 00 00 64 73 70 73 20 68 61 6e 64 6c 65 72 00 |...dsps handler.|
00006df0 00 00 00 70 b5 80 20 06 f0 69 fd 1d 4c 08 23 21 |...p.. ..i..L.#!|
00006e00 68 1d a2 05 f0 f4 fb 21 68 1b 25 ad 01 49 19 08 |h......!h.%..I..|
00006e10 62 80 20 06 f0 5b fd 61 68 02 23 1a a2 05 f0 e7 |b. ..[.ah.#.....|
00006e20 fb 61 68 49 19 08 62 80 20 06 f0 50 fd a1 68 0d |.ahI..b. ..P..h.|
00006e30 0a 23 19 a2 05 f0 dc fb a1 68 49 19 08 62 80 20 |.#.......hI..b. |
00006e40 06 f0 45 fd e1 68 04 23 17 a2 05 f0 d1 fb e1 68 |..E..h.#.......h|
00006e50 49 19 08 62 80 20 06 f0 3a fd 21 69 06 23 16 a2 |I..b. ..:.!i.#..|
00006e60 05 f0 c6 fb 21 69 49 19 08 62 70 bc 08 bc 00 20 |....!iI..bp.... |
00006e70 18 47 00 00 70 94 03 00 61 70 70 73 20 63 68 61 |.G..p...apps cha|
00006e80 6e 67 65 72 00 00 00 00 6d 6f 64 65 6d 20 63 68 |nger....modem ch|
00006e90 61 6e 67 65 72 00 00 00 6c 70 61 73 73 20 63 68 |anger...lpass ch|
00006ea0 61 6e 67 65 72 00 00 00 72 69 76 61 20 63 68 61 |anger...riva cha|
00006eb0 6e 67 65 72 00 00 00 00 64 73 70 73 20 63 68 61 |nger....dsps cha|
00006ec0 6e 67 65 72 00 00 00 00 06 28 12 d2 78 44 00 79 |nger.....(..xD.y|
00006ed0 00 18 87 44 02 04 06 08 0d 0a 0c 07 a0 70 47 08 |...D.........pG.|
00006ee0 a0 70 47 09 a0 70 47 0d 0a a0 70 47 0b a0 70 47 |.pG..pG...pG..pG|
00006ef0 0c a0 70 47 0d a0 70 47 00 00 41 50 53 53 00 00 |..pG..pG..APSS..|
00006f00 00 00 4d 50 53 53 5f 53 57 00 4c 50 41 53 53 00 |..MPSS_SW.LPASS.|
out of thanks already...
Gotcha. Thanks.
Did it for testing purposes with mmcblk0p1 from JB One SSE and mmcblk0p1 from ICS One S and they both are fairly similar so i can tell by using UltraCompare that it is the same partition type.
I now dumped all One SSE partitions successfully apart from the SD and the UserData got stuck, it never finished. But all others dumped fine. Will start looking into them when i get time.
For now, Partition 1 is same. That's what i can already say lol.
[EDIT]
Userdata (0p35) didn't get stuck. I aborted it and then found an image on the SD which was already 7,5 GB big. I believe the Data Partition is quite large on the SE.
Will update the OP soon. Sorry Ive been a bit busy with kernels
Nevermind.
Tecardo's gonna help me with doing a writeback-script, just in case you already read my request here. Thanks.
Sneakyghost said:
Nevermind.
Tecardo's gonna help me with doing a writeback-script, just in case you already read my request here. Thanks.
Click to expand...
Click to collapse
I was going to suggest you take a bootsplash zip and modify it .. but got ninja'd.
AW: [PARTITION LIST] Partition Information and RUU/OTA Files,Work In Progress, 01/10/
On the One S special edition the sdcard is mapped to /data/media. It's mounted differently, also the recovery can't mount the sdcard as mass storage or partition.
Interesting. A very minor difference in the otherwise totally identical partition layout...
sent from viper 2.1

Internal Memory Data Recovery by cygwin64 possible?

https://www.aesonlabs.ca/blogs/android-internal-storage-sector-by-sector-copy-clone/#comment-131
that was very useful
i have HTC11U, i want to make an entire backup of all sectors to recover lost data by Recuva or any other recovery progs on windows
the blocks i see for my phone when i apply this command " cat /proc/partitions "
is :
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
253 0 2928884 zram0
8 0 124280832 sda
8 1 40 sda1
8 2 65536 sda2
8 3 65536 sda3
8 4 3915776 sda4
8 5 57344 sda5
8 6 61440 sda6
8 7 120102912 sda7
8 8 4012 sda8
8 80 57344 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 4096 sdf5
8 86 24256 sdf6
8 87 10240 sdf7
8 88 4 sdf8
8 89 10240 sdf9
8 90 1024 sdf10
8 91 5116 sdf11
8 48 458752 sdd
8 49 1024 sdd1
8 50 512 sdd2
8 51 512 sdd3
8 52 2048 sdd4
8 53 512 sdd5
8 54 512 sdd6
8 55 512 sdd7
8 56 512 sdd8
8 57 512 sdd9
8 58 128 sdd10
8 59 1024 sdd11
8 60 65536 sdd12
8 61 107520 sdd13
8 62 5120 sdd14
8 63 1024 sdd15
259 7 256 sdd16
259 8 20480 sdd17
259 9 256 sdd18
259 10 16384 sdd19
259 11 2048 sdd20
259 12 128 sdd21
259 13 229376 sdd22
259 14 2772 sdd23
8 32 4096 sdc
8 33 4052 sdc1
8 16 4096 sdb
8 17 4052 sdb1
8 64 163840 sde
8 65 1024 sde1
8 66 2048 sde2
8 67 2048 sde3
8 68 8 sde4
8 69 32768 sde5
8 70 128 sde6
8 71 4 sde7
8 72 46080 sde8
8 73 1024 sde9
8 74 20480 sde10
8 75 30720 sde11
8 76 1284 sde12
8 77 64 sde13
8 78 1024 sde14
8 79 512 sde15
259 0 10240 sde16
259 1 32 sde17
259 2 4 sde18
259 3 1024 sde19
259 4 8192 sde20
259 5 2048 sde21
259 6 3040 sde22
252 0 120102912 dm-0
7 64 65536 loop64
but what i saw on the internet is different blocks like:
major minor #blocks name
7 0 98304 loop0
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
[...]
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
i know how to change the command according to the busybox installation path.
but for my blocks there, i am not able to retrieve any of these blocks, as it gives me
dd: writing 'standard output': Connection reset by peer
347+0 records in
i tried to retrieve the largest one and random partitions, but the file i get in the NEXUS folder is 0 KB
this is driving me crazy
please i need your help
Any Luck?
Hey OP any luck yet? I have the same problem

Moving Pictures to PC failed, Data now lost, how to recover

Today I wanted to move the pictures of my family holiday on the computer like I always do. But somehow the files on the PC are corrupted and not able to be viewed.
I used "move" and not "copy", so now the files are deleted on the OnePlus 6 internal sd card.
Total it's about 700 pictures and 30 videos that are lost
Common recovery do not work with MTP, so I found an instruction and tried to extract the user partition sda17 as .img to the computer and searched for files with photorec, but did not find anything. All files have kind of crypted names. I thought that this is the user partition, but I am not sure.
Can anyone tell me which which partition below I should extract or is the method the correct one at all?
Thank You for your help.
OnePlus6:/ # cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
8 32 4096 sdc
8 33 3584 sdc1
8 34 128 sdc2
8 48 32768 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
8 64 3145728 sde
8 65 512 sde1
8 66 2048 sde2
8 67 512 sde3
8 68 122880 sde4
8 69 1024 sde5
8 70 4096 sde6
8 71 32768 sde7
8 72 8192 sde8
8 73 32768 sde9
8 74 512 sde10
8 75 65536 sde11
8 76 512 sde12
8 77 512 sde13
8 78 128 sde14
8 79 64 sde15
259 0 1048576 sde16
259 1 64 sde17
259 2 8192 sde18
259 3 128 sde19
259 4 16384 sde20
259 5 2048 sde21
259 6 2048 sde22
259 7 2048 sde23
259 8 2048 sde24
259 9 2048 sde25
259 10 2048 sde26
259 11 2048 sde27
259 12 2048 sde28
259 13 512 sde29
259 14 2048 sde30
259 15 512 sde31
259 16 122880 sde32
259 17 1024 sde33
259 18 4096 sde34
259 19 32768 sde35
259 20 8192 sde36
259 21 32768 sde37
259 22 512 sde38
259 23 65536 sde39
259 24 512 sde40
259 25 512 sde41
259 26 128 sde42
259 27 64 sde43
259 28 1048576 sde44
259 29 64 sde45
259 31 8192 sde46
259 33 128 sde47
259 34 16384 sde48
259 35 2048 sde49
259 36 2048 sde50
259 37 2048 sde51
259 38 2048 sde52
259 39 2048 sde53
259 40 2048 sde54
259 41 2048 sde55
259 42 2048 sde56
259 43 102400 sde57
259 44 65536 sde58
259 45 102400 sde59
259 46 16 sde60
259 47 4 sde61
259 48 1024 sde62
259 49 256 sde63
259 50 256 sde64
259 51 8192 sde65
259 52 33424 sde66
259 53 4 sde67
259 54 1024 sde68
259 55 8192 sde69
259 56 2048 sde70
259 57 65536 sde71
259 58 2048 sde72
8 80 32768 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 2048 sdf4
8 85 128 sdf5
8 0 121749504 sda
8 1 8 sda1
8 2 32768 sda2
8 3 1024 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 512 sda6
8 7 262144 sda7
8 8 10240 sda8
8 9 10240 sda9
8 10 8096 sda10
8 11 16192 sda11
8 12 512 sda12
8 13 2928640 sda13
8 14 2928640 sda14
8 15 102400 sda15
259 30 102400 sda16
259 32 115344108 sda17
8 16 4096 sdb
8 17 3584 sdb1
8 18 128 sdb2
254 0 1031948 dm-0
7 64 294912 loop64

How to pull recovery/boot/system img via adb shell ?

Hi all,
How do we extract boot/system/recovery img files from adb shell ?
My U12+
Locked bootloader
Unroot
Hong Kong variant
Below are the partitions description
htc_imedugl:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
254 0 2908592 zram0
8 0 122142720 sda
8 1 104 sda1
8 2 8 sda2
8 3 32768 sda3
8 4 24256 sda4
8 5 4096 sda5
8 6 1024 sda6
8 7 1024 sda7
8 8 10240 sda8
8 9 10240 sda9
8 10 30720 sda10
8 11 20480 sda11
8 12 128 sda12
8 13 32 sda13
8 14 512 sda14
8 15 1284 sda15
259 0 46080 sda16
259 1 61440 sda17
259 2 4263936 sda18
259 3 4263936 sda19
259 4 113369088 sda20
259 5 1280 sda21
8 16 4096 sdb
8 17 3924 sdb1
8 18 128 sdb2
8 32 4096 sdc
8 33 3924 sdc1
8 34 128 sdc2
8 48 4096 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 3820 sdd3
8 80 8192 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 1024 sdf4
8 85 2048 sdf5
8 86 2048 sdf6
8 87 708 sdf7
8 64 2805760 sde
8 65 512 sde1
8 66 2048 sde2
8 67 512 sde3
8 68 512 sde4
8 69 112640 sde5
8 70 1024 sde6
8 71 4096 sde7
8 72 32768 sde8
8 73 1024 sde9
8 74 32768 sde10
8 75 512 sde11
8 76 512 sde12
8 77 65536 sde13
8 78 32768 sde14
8 79 512 sde15
259 6 512 sde16
259 7 128 sde17
259 8 64 sde18
259 9 1048576 sde19
259 10 64 sde20
259 11 8192 sde21
259 12 512 sde22
259 13 2048 sde23
259 14 512 sde24
259 15 512 sde25
259 16 112640 sde26
259 17 1024 sde27
259 18 4096 sde28
259 19 32768 sde29
259 20 1024 sde30
259 21 32768 sde31
259 22 512 sde32
259 23 512 sde33
259 24 65536 sde34
259 25 32768 sde35
259 26 512 sde36
259 27 512 sde37
259 28 128 sde38
259 29 64 sde39
259 30 1048576 sde40
259 31 64 sde41
259 32 8192 sde42
259 33 16 sde43
259 34 4 sde44
259 35 1024 sde45
259 36 256 sde46
259 37 256 sde47
259 38 4 sde48
259 39 33424 sde49
259 40 4 sde50
259 41 1024 sde51
259 42 8192 sde52
259 43 2048 sde53
259 44 65536 sde54
259 45 128 sde55
259 46 16 sde56
259 47 3224 sde57
253 0 4196572 dm-0
253 1 1040248 dm-1
253 2 113369088 dm-2
htc_imedugl:/ $
Any help will be gladly appreciated

Please help restoring the partitions

Safe to say I have messed up badly. This morning, I was trying to update EvolutionX build (by dirty flashing) and I received an error: Cannot mount /product (invalid argument). After few tries, I still couldn't flash anything and neither could I now boot into the system. So I decided to wipe the data as well as system partition and then try to install the ROM zip. It failed again, but now the error said that it didn't find the /system and /vendor as well.
From the TWRP Recovery > Mount section, I verified that I could not check the system, vendor, and product partitions. I could select the rest. Recovery seems to be working fine.
I checked the partitions on phone:
>adb shell cat /etc/fstab
/system_root ext4 ro 0 0
/vendor ext4 ro 0 0
/product ext4 ro 0 0
/dev/block/sda10 /metadata ext4 rw 0 0
/dev/block/sda16 /data f2fs rw 0 0
/dev/block/sda11 /cache ext4 rw 0 0
/dev/block/sde4 /firmware vfat rw 0 0
/dev/block/sda7 /cust ext4 rw 0 0
/dev/block/sda2 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
/dev/block/mmcblk0p1 /external_sd vfat rw 0 0
>adb shell cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
8 0 120479744 sda
8 1 8 sda1
8 2 32768 sda2
8 3 1024 sda3
8 4 512 sda4
8 5 512 sda5
8 6 131072 sda6
8 7 1048576 sda7
8 8 131072 sda8
8 9 64 sda9
8 10 16384 sda10
8 11 393216 sda11
8 12 393216 sda12
8 13 16384 sda13
8 14 8192 sda14
8 15 8388608 sda15
259 0 109918092 sda16
8 16 8192 sdb
8 17 7168 sdb1
8 18 128 sdb2
8 32 8192 sdc
8 33 7168 sdc1
8 34 128 sdc2
8 64 4194304 sde
8 65 512 sde1
8 66 4096 sde2
8 67 512 sde3
8 68 262144 sde4
8 69 1024 sde5
8 70 4096 sde6
8 71 32768 sde7
8 72 8192 sde8
8 73 32768 sde9
8 74 512 sde10
8 75 512 sde11
8 76 512 sde12
8 77 128 sde13
8 78 64 sde14
8 79 2048 sde15
259 1 2048 sde16
259 2 512 sde17
259 3 4096 sde18
259 4 512 sde19
259 5 4096 sde20
259 6 32768 sde21
259 7 8192 sde22
259 8 512 sde23
259 9 512 sde24
259 10 512 sde25
259 11 2048 sde26
259 12 2048 sde27
259 13 4 sde28
259 14 1024 sde29
259 15 256 sde30
259 16 8192 sde31
259 17 33424 sde32
259 18 4 sde33
259 19 1024 sde34
259 20 8192 sde35
259 21 2048 sde36
259 22 65536 sde37
259 23 128 sde38
259 24 32 sde39
259 25 32 sde40
259 26 512 sde41
259 27 28 sde42
259 28 512 sde43
259 29 1024 sde44
259 30 64 sde45
259 31 131072 sde46
259 32 24576 sde47
8 48 131072 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
8 80 131072 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 10240 sdf4
8 85 128 sdf5
179 0 7761920 mmcblk0
179 1 7757824 mmcblk0p1
It seems that system_root, vendor and product do not have any block (?) assigned to them. Is there a way to identify what were the original assigned blocks to these partitions and assign them through fastboot/adb/recovery?
Any help is appreciated thanks!!
UPDATE: Flashed the fastboot rom and it solved the issue. Got the stock MIUI and flashed the custom recovery/rom from there on. See last reply for details.
Not what you asked but the standard rescue procedure: flash MIUI stock ROM (~2.4GB) with MiFlash and start again...
pnin said:
Not what you asked but the standard rescue procedure: flash MIUI stock ROM (~2.4GB) with MiFlash and start again...
Click to expand...
Click to collapse
This worked!! I literally thought that the phone was toast. But this worked. Downloaded the fastboot rom for IN variant (filename: surya_in_global_images_V12.0.9.0.QJGINXM_20210202.0000.00_10.0_in_8...) and ran the flash_all script while the phone was in fastboot mode. Got the stock MIUI on the phone and then flashed the recovery and the custom rom.
Also, one of the issues I was getting when running flash_all script was that the pathname where I had extracted the fastboot rom had space in it (eg. "path/to/A B/rom"). Copied it to another drive so that path didn't have any space.
vjsa said:
This worked!! I literally thought that the phone was toast. But this worked. Downloaded the fastboot rom for IN variant (filename: surya_in_global_images_V12.0.9.0.QJGINXM_20210202.0000.00_10.0_in_8...) and ran the flash_all script while the phone was in fastboot mode. Got the stock MIUI on the phone and then flashed the recovery and the custom rom.
Also, one of the issues I was getting when running flash_all script was that the pathname where I had extracted the fastboot rom had space in it (eg. "path/to/A B/rom"). Copied it to another drive so that path didn't have any space.
Click to expand...
Click to collapse
Did you manage to install a custom ROM again? I got the same error a few weeks ago and rescued my phone with the fastboot ROM but whenever I try to install a custom ROM since then, I keep getting the same error.
Srivihar said:
Did you manage to install a custom ROM again? I got the same error a few weeks ago and rescued my phone with the fastboot ROM but whenever I try to install a custom ROM since then, I keep getting the same error.
Click to expand...
Click to collapse
Yep, installed the latest EvolutionX build (one that caused the issue in first place). Everything is working fine till now.

Categories

Resources