I was wondering if someone can pull their config file? I don't have the phone yet but already starting on a kernel.. Only thing is I need the confi file from a working phone.
Post the config file here.
First one pulls the config the other gives us the config. Thanks guys
Code:
./adb pull /proc/config.gz
gunzip config.gz
Gimmie a sec...
EDIT: Here you go.
https://docs.google.com/open?id=0Byr5K8BpE_yQMlFnVWROd0wtQ2c
Sent from my EVO 4G LTE
---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------
You kernel building?
david279 said:
Gimmie a sec...
EDIT: Here you go.
https://docs.google.com/open?id=0Byr5K8BpE_yQMlFnVWROd0wtQ2c
Sent from my EVO 4G LTE
---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------
You kernel building?
Click to expand...
Click to collapse
Yup Might need some testers till I get the phone. Waiting for the white one and still saving up..
MikeC84 said:
Yup
Click to expand...
Click to collapse
Cool. I've been able to build but i don't know how to get it into a boot.img so i can boot it. Im a noob at that part.
david279 said:
Cool. I've been able to build but i don't know how to get it into a boot.img so i can boot it. Im a noob at that part.
Click to expand...
Click to collapse
I need the emmc partition info so I know what block to use for flashing. I have to go pick up the old lady so if someone can find a link for me till I get one that would be nice.
I already have a build kernel with lulzactive governor
cat /proc/partitions?
Sent from my EVO 4G LTE
david279 said:
cat /proc/partitions?
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
Yea try it.
I need the system and boot.img block names
[email protected]:/ $ cat /proc/partitions
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 256 mmcblk0p32
179 33 256 mmcblk0p33
179 34 99239 mmcblk0p34
179 35 1277951 mmcblk0p35
179 36 229375 mmcblk0p36
179 37 2260991 mmcblk0p37
179 38 10418176 mmcblk0p38
179 64 30657536 mmcblk1
179 65 30653440 mmcblk1p1
Mount output
https://docs.google.com/document/d/1moR9C9iOpFTvZXGEH8s9bnBtexyQ3VPO4Yl1RU8WyQ8/edit
Sent from my EVO 4G LTE
david279 said:
[email protected]:/ $ cat /proc/partitions
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 256 mmcblk0p32
179 33 256 mmcblk0p33
179 34 99239 mmcblk0p34
179 35 1277951 mmcblk0p35
179 36 229375 mmcblk0p36
179 37 2260991 mmcblk0p37
179 38 10418176 mmcblk0p38
179 64 30657536 mmcblk1
179 65 30653440 mmcblk1p1
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
Thanks that helps now I need toknow which one of those is the system and which one is boot.img
I'll see if I can find another way to grab em..
CHeck the link i added to the post above
david279 said:
CHeck the link i added to the post above
Click to expand...
Click to collapse
Boot img not in there. Try partition table from Google play.
Try this too
cat /proc/mtd
cat /proc/mtd gave no results and no partition table app in the market.
david279 said:
cat /proc/mtd gave no results and no partition table app in the market.
Click to expand...
Click to collapse
http://db.tt/QEWboCNP
{
"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"
}
No go.
Sent from my EVO 4G LTE
david279 said:
No go.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
Found it!
Cool
Sent from my EVO 4G LTE
david279 said:
Cool
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
I'll have a kernel to test later today if any one wants to test...
Does anyone know the partition which stores the baseband?
cat /proc/partitions doesn't give me the required information:
Code:
major minor #blocks name alias
7 3 314624 loop3
179 0 15564800 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 1 mmcblk1p4
179 5 512 mmcblk1p5
179 6 512 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8 utags
179 9 1024 mmcblk1p9
179 10 2048 mmcblk1p10
179 11 512 mmcblk1p11
179 12 512 mmcblk1p12
179 13 4096 mmcblk1p13
179 14 8192 mmcblk1p14 boot
179 15 9216 mmcblk1p15 recovery
179 16 217088 mmcblk1p16 cdrom
179 17 512 mmcblk1p17 misc
179 18 512 mmcblk1p18 cid
179 19 4096 mmcblk1p19 kpanic
179 20 793600 mmcblk1p20 system
179 21 737280 mmcblk1p21 cache
179 22 9216 mmcblk1p22 preinstall
179 23 1364992 mmcblk1p23 webtop
179 24 3989504 mmcblk1p24 userdata
179 25 8401792 mmcblk1p25 emstorage
179 26 128 mmcblk1p26
179 64 2048 mmcblk1boot1
179 32 2048 mmcblk1boot0
179 96 31166976 mmcblk0
179 97 31162880 mmcblk0p1
[email protected]:/ #
THX!
dmesg and search for kernel boot line, it contains association with partition number and name
Before
Code:
major minor #blocks name
7 0 48888 loop0
7 1 16664 loop1
7 2 5229 loop2
7 3 2111 loop3
253 0 409600 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 31166976 mmcblk1
179 33 31162880 mmcblk1p1
254 0 48888 dm-0
254 1 16663 dm-1
254 2 5229 dm-2
254 3 2110 dm-3
After
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 4190 loop0
7 1 16664 loop1
7 2 2111 loop2
7 3 8348 loop3
7 4 19782 loop4
7 6 5229 loop6
7 7 5229 loop7
253 0 409600 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 31166976 mmcblk1
179 33 31162880 mmcblk1p1
254 0 4189 dm-0
254 1 16663 dm-1
254 2 2110 dm-2
254 3 8347 dm-3
254 6 5229 dm-6
254 7 5229 dm-7
7 8 48888 loop8
254 8 48888 dm-8
254 4 19782 dm-4
Surge1223 said:
Before
Code:
major minor #blocks name
7 0 48888 loop0
7 1 16664 loop1
7 2 5229 loop2
7 3 2111 loop3
Click to expand...
Click to collapse
These are loopbacks. What that means is that a file somewhere is mapped by /dev/loop0 to look like a disk.
Between earlier and now, something changed in what's loopback mounted.
The important partitions - those on your internal MMC memory, are unchanged.
Surge1223 said:
Code:
254 0 48888 dm-0
254 1 16663 dm-1
254 2 5229 dm-2
254 3 2110 dm-3
Click to expand...
Click to collapse
The dm-0, -1, -2 are purchased applications, mounted on /mnt/asec if I remember right. Where they're mounted will tell you the app name.
Hi there
I want to recovery data from a phone that has been reseted.
So far I have extracted the partition mmcblk0p36 to my computer using dd.
I'm trying to recovery the photos using PhotoRec but it's not working at all.
Some advice?
List of partitions:
Code:
[email protected]_umtsds:/ # cat /proc/partitions
major minor #blocks name
253 0 262144 zram0
179 0 15388672 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 678016 mmcblk0p33
259 2 999424 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 13545344 mmcblk0p36
179 32 512 mmcblk0rpmb
here is the proc/partition output
126|NS-P11A8100:/ $ cat /proc/partitions
major minor #blocks name
254 0 485312 zram0
179 0 30310400 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 256 mmcblk0p6
179 7 384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 6144 mmcblk0p10
179 11 512 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 5120 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 36224 mmcblk0p19
179 20 2621440 mmcblk0p20
179 21 434176 mmcblk0p21
179 22 27049472 mmcblk0p22
179 23 16384 mmcblk0p23
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 7776256 mmcblk1
179 129 7775232 mmcblk1p1
253 0 2580508 dm-0
253 1 27049472 dm-1
thanks guys.
Which device?
Scatter file is different for each device, even if they have the same SOC.
Which model is?. It's best if someone has the scatter file for your tablet.
Also, it is possible, but dangerous, take the scatter and a preloader file for a similar device and perform an memory EMMC_BOOT1 & EMMC_USER backup with SP Flash Tool. But it is easy to make a mistake and brick the tablet. This trick only works to make a backup, but as the preloader and scatter file does not correspond to the device, you have to be very careful with using them only to perform the backup and once acomplished, delete these files.
Then with the backup and the Wwr MTK tool you can generate an scatter file for your device.
The EMMC_BOOT1 partition is the device preloader.
Best Regards