Database Develop

n7000 partition help

keep getting blank IMEI and unknow baseband, so i run ~ # parted /dev/block/mmcblk0 and noticed efs is not EXT4 file system as it should be. Could you please help how to fix mine partition. here how it looked now.
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 msftres
12 15.2GB 15.8GB 537MB ext4 HIDDEN

Wrong section and there is a topic related to your issue already here:
[Guide]How to revive your bricked Gnote
EFS IS EXT4 DON'T MESS WITH IT IF YOU DON'T HAVE A DUMP OF YOUR EFS PARTITION!
If you don't have a dump of your EFS i wouldn't mess with it!
With 7 posts and you are messing with parted?
Btw, use the topic that i quoted... you will find help there!
Reported!

Thread moved and closed
Do not post questions in Development, and since you've been given good advice, thread closed.

[SOLVED] How to restore damaged Internal SD card partition layout? Tried everything.

I did something really bad to my INTERNAL SD CARD partition layout, so now I have
I have the i8190N model
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 7634936 mmcblk0p1
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 3866624 mmcblk1
179 97 3862528 mmcblk1p1
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 411756 48 411708 0% /dev
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No?
As you can see, there is no /system, /cache and other stuff, that should be there.
My ClockWorkMod recovery tool can't mount anything (/cache, /system, nothing)
I really did everything I could. I tried: restore from backup (I have one, made with recovery tool), install new ROM (With recovery tool), install stock firmware and stock kernel in ODIN mode. I even tried some PIT file: nothing did absolutely nothing to my status.
Frankly I miss some important part in understanding of filesystem, partitions, images, what is ROM, what is stock kernel etc ...
What should I do?
UPDATE:
Short answer: user right PIT file and burn it with Odin3. Long answer in post below.

Found interesting file:
Code:
~ # tail ./etc/recovery.fstab
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25 length=-16384
/efs ext4 /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
/modem ext4 /dev/block/mmcblk0p12
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
~ # tail ./etc/fstab
/dev/block/mmcblk0p23 /cache ext4 rw
/dev/block/mmcblk0p25 /data ext4 rw
/dev/block/mmcblk0p22 /system ext4 rw
/dev/null /sdcard datamedia rw
And here is more info
Code:
~ # ls -la /dev/block/mmcblk*
brw------- 1 root root 179, 0 Jan 1 10:30 /dev/block/mmcblk0
brw------- 1 root root 179, 32 Jan 1 09:28 /dev/block/mmcblk0boot0
brw------- 1 root root 179, 64 Jan 1 09:28 /dev/block/mmcblk0boot1
-rw-rw-rw- 1 root root 16777216 Jan 1 10:07 /dev/block/mmcblk0p20
-rw-r--r-- 1 root root 0 Jan 1 10:07 /dev/block/mmcblk0p22
brw------- 1 root root 179, 96 Jan 1 09:28 /dev/block/mmcblk1
brw------- 1 root root 179, 97 Jan 1 09:28 /dev/block/mmcblk1p1

This is what kind of stuff I get in CWM:
Code:
-- Wiping cache...
Formatting /cache...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p23
Cache wipe complete.
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
W:Can't unlink /cache/recovery/command
Formatting /data...
warning: get_file_size: Computed filesystem size less than 0
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error formatting /data!
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log

Have you tried to flash stock firmware again with re partition ticked and the pit file? Using the pit file make sense only if you flash the whole firmware with it
Inviato dal mio GT-I8190 con Tapatalk 2

Byteater said:
Have you tried to flash stock firmware again with re partition ticked and the pit file? Using the pit file make sense only if you flash the whole firmware with it
Click to expand...
Click to collapse
As I wrote in initial post - yes, I did. But maybe I used wrong pit file =\
Btw, looks like I have everything in console buffer (full history of distraction actions)
In the beginning I had this:
Code:
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 3872256 mmcblk1
179 97 3868160 mmcblk1p1
254 0 2110 dm-0
Code:
/ $ df
Filesystem Size Used Free Blksize
/dev 402.1M 84K 402M 4096
/mnt/asec 402.1M 0K 402.1M 4096
/mnt/obb 402.1M 0K 402.1M 4096
/dev/shm 402.1M 0K 402.1M 4096
/system 1.2G 414.5M 766.6M 4096
/modemfs 15.7M 4.3M 11.4M 4096
/cache 826.8M 84.8M 742M 4096
/efs 15.7M 4.5M 11.2M 4096
/preload 315M 64.2M 250.8M 4096
/data 4.6G 4G 699.2M 4096
/mnt/.lfs: Function not implemented
/storage/sdcard0 4.6G 4G 699.2M 4096
/mnt/asec/com.spruds.transport.pro.tallin-1 2M 888K 1.1M 4096
/storage/sdcard1 3.7G 905.7M 2.8G 32768
Even before everything went wrong I tried to use parted command and get an error
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) list
list
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
.....
.....
copyright information of GNU Parted
(parted) print
print
Error: Unable to satisfy all constraints on the partition.
This is fdisk print before disaster
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
And then I deleted it
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Command (m for help): d
Selected partition 1
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

To be honest, I've never seen a problem like that. In Odin there's an option to erase all nand. I don't know if this would help you, since you should have an efs backup and I don't know if it will bring consequences.
Inviato dal mio GT-I8190 con Tapatalk 2

Try firmware posted here, with pit-file.
It's worth a try. It has saved me a few times, but from other problems.

tys0n said:
Try firmware posted here, with pit-file.
It's worth a try. It has saved me a few times, but from other problems.
Click to expand...
Click to collapse
I have "some" goldenxx.pit file already. And I took original firmware from some semi-official sources. Though I didn't have this CSC file. Also In original article (on 4pda.ru) they say NOT TO use this firmware with I8190N (which I have) ...

soswow said:
I have "some" goldenxx.pit file already. And I took original firmware from some semi-official sources. Though I didn't have this CSC file. Also In original article (on 4pda.ru) they say NOT TO use this firmware with I8190N (which I have) ...
Click to expand...
Click to collapse
Oh sorry. My mistake. I missed it was i8190N.
Sent through time and space from my s3mini/CM10.

Found it!
I found it!
The answer was in PIT file, because as it says here:
you will only need to use this if a firmware update needs to change your partition layout (very very unlikely) or if you mess up you partition table (you don’t want to do this)
Click to expand...
Click to collapse
Which is definitely my case.
So, I tried that GT-I8190N and GT-I8190 should be used with different PIT files (I tried to use for GT-I8190 one). So I found long list of PIT files here
Thank you everyone for help.

[INFO] Partition List Nexus 5

Here is the partition list of all Nexus 5 partitions with parted:
Code:
C:\Users\cargo\tools>adb shell
~ # umount /cache
umount /cache
~ # umount /system
umount /system
~ # umount /data
umount /data
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
(parted)
Here is a simple list:
Code:
C:\Users\cargo\tools>adb shell
cat /proc/partitions~ #
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ #

Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )

przemo_li said:
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
Click to expand...
Click to collapse
You won't get much speed out of a hosed phone. No you can't.

jd1639 said:
You won't get much speed out of a hosed phone. No you can't.
Click to expand...
Click to collapse
Meaning, kernel must support F2FS otherwise it wont boot? Obvious (for me at least) Just wanted to know if I can find such kernels (already build), and if there are tools to convert existing partitions. (So that changes performed are not too invasive )
Or if there are some mods that already employ F2FS.
(Moto G is my inspiration here, btw)

Any info and specs on the MMC model?

eng.stk said:
Any info and specs on the MMC model?
Click to expand...
Click to collapse
Do not know what MMC is, but if it was question for me I will just assume its hw question about storage specs for my phone.
1) I do not have that phone yet
2) It will be internetional version of Nexus 5 (16GB or 32GB).

eng.stk said:
Any info and specs on the MMC model?
Click to expand...
Click to collapse
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf

rootSU said:
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
Click to expand...
Click to collapse
404 error

przemo_li said:
404 error
Click to expand...
Click to collapse
Because the url has [1] in it. Try and copy / paste

rootSU said:
Because the url has [1] in it. Try and copy / paste
Click to expand...
Click to collapse
Did that before I posted 404
No [1], and still 404

przemo_li said:
Did that before I posted 404
No [1], and still 404
Click to expand...
Click to collapse
It works, don't forget [1].pdf in the end.

przemo_li said:
Did that before I posted 404
No [1], and still 404
Click to expand...
Click to collapse
OK I fixed the link.

rootSU said:
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf
Click to expand...
Click to collapse
Sustained Read:15 MB/s​Sustained Write:9 MB/s​
Biggest bottleneck of this great device
"Why Google?" or "Why LG?"

przemo_li said:
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
Click to expand...
Click to collapse
Lol, i do
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486

dennes544 said:
Lol, i do
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
Click to expand...
Click to collapse
I know you're trying to be helpful but why revive and answer a thread that's been dead for 3 months?
Sent from my Nexus 5 using Tapatalk

Partition Stock
Hi I have a problem a wipe system VOL, I have /sdcard/ /sdcard/0/ /sdcard/0/0/ When I use usb have to goo /sdcard/0/0/ to much problem my question .. How I cant reset all partitions? and leave my fone like new..?? So I have 28 Gb free but I didnt put any file.. I wanna clean all fone and start with OEM partition, Thx ...sorry for english

how do you get parted on your N5? I only get sh: parted: not found lol

Can you please post the table again using bits or sectors as units? That will be very helpful.

jd1639 said:
You won't get much speed out of a hosed phone. No you can't.
Click to expand...
Click to collapse
Formatting cache and data DOES provide a speed boost but not with system. System should stay EXT4 because F2FS improves the performance of write operations the most and, typically, system is read only. Stick LineageOS 13 and 14.1 support data and cache as F2FS. Be aware though that switching data to F2FS WILL wipe internal storage so back it up. If you wish to keep your data the backup the data partition in TWRP and then backup the entire internal storage directory to a computer. After you've backed up everything you can go to wipe, advanced wipe and select data and hit repair or change and change it to F2FS. Once that is done you should reboot back into TWRP, open settings and enable "use rm -rf instead of formatting". When in recovery you can copy your entire internal storage back to your phone, ensure you copy it right, the TWRP directory should be in the root of your internal storage, this is important because it contains your precious data backup. After that reboot back into TWRP and you may have to enable rm -rf in settings, make sure that is enabled! These reboots are for good measure, it's best to just do them. After that you can go to restore and restore your data backup. After it is fully restored you may disable rm -rf in settings and format cache as F2FS. Then reboot to system and enjoy!
Sent from my Pixel using XDA Labs

[Dualboot] i9082 {Stock 4.2.2/AOSP 4.4.2 and AOSP 4.4.2} 23032014 V2

Hi guys,
finally I found a way to make dualboot on our beloved i9082 working!!
This way isn't as much easy as on other devices like the desire HD where
you have just to install an app and everything is done by itself, so follow this
guide at your own risk!!
THIS IS WORST RISK YOU TAKE FOR YOUR PHONE>>>>
IT MAY BRICK YOUR PHONE.....
DONT DO IT IF YOU DONT KNOW WHAT YOU DOING...
How to dual boot your I9082...
1. Make a backup of your internal sdcard to your PC!! All your data on the sd card will be gone!
2. Reboot to cwm-recovery
3. connect your phone to your pc.
4, open up cmd or a terminal and type:
PHP:
adb shell
5. type:
PHP:
cd /dev/block
parted mmcblk0
print
This looks like following
Code:
print
Model: MMC M8G1WA (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 14.7MB 15.7MB 1049kB cal
2 15.7MB 16.0MB 262kB sysparm_dep
3 16.0MB 16.3MB 262kB parm-spml_dep
4 16.3MB 16.5MB 262kB RF_CAL_FILE
5 16.5MB 24.9MB 8389kB KERNEL
6 24.9MB 33.3MB 8389kB RECOVERY
7 33.3MB 53.0MB 19.7MB modem
8 53.0MB 86.2MB 33.3MB reserved
9 86.2MB 88.3MB 2097kB SBL1
10 88.3MB 90.4MB 2097kB SBL2
11 90.4MB 98.8MB 8389kB PARAM
12 98.8MB 99.4MB 524kB DTSBK
13 99.4MB 99.9MB 524kB DTS
14 99.9MB 108MB 8389kB VC-FirmwareBK
15 108MB 117MB 8389kB VC-Firmware
16 117MB 117MB 262kB FOTA_SIG
17 117MB 138MB 21.0MB ext4 efs
18 138MB 1212MB 1074MB ext4 CSC
19 1212MB 2822MB 1611MB ext4 system
20 2822MB 3409MB 587MB ext4 HIDDEN
21 3409MB 7813MB 4404MB ext4 data
The last partiton i.e data partion which is our internal SD card to be re partitioned .
6. Type
PHP:
rm 21
7. Note the start and end of the data partiton. In my case its 3409 and 7813
Firstly we have to create data partition. See the size of system partition i.e 1024 MB. So the new partion will be as follows
PHP:
mkpartfs primary ext2 3409 4433
second is system 2 partition
PHP:
mkpartfs primary ext2 4433 6044
next is cache2 partion
PHP:
mkpartfs primary ext2 6044 6744
next is data2 partion
Code:
mkpartfs primary ext2 6744 7813
Code:
quit
It will say
Code:
quit
Information: You may need to update /etc/fstab.
Ignore the warning Reboot into recovery again on pc type
Code:
adb shell
mke2fs /dev/block/mmcblk0p21
tune2fs -j /dev/block/mmcblk0p21
mke2fs /dev/block/mmcblk0p22
tune2fs -j /dev/block/mmcblk0p22
mke2fs /dev/block/mmcblk0p23
tune2fs -j /dev/block/mmcblk0p23
mke2fs /dev/block/mmcblk0p24
tune2fs -j /dev/block/mmcblk0p24
This will create ext3 partition from ext2
Now convert them to ext4
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p21
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p22
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p23
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p24
Now lets check everything is ok
Code:
cd /dev/block
parted mmcblk0
print
This should look like following
Code:
print
Model: MMC M8G1WA (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 14.7MB 15.7MB 1049kB cal
2 15.7MB 16.0MB 262kB sysparm_dep
3 16.0MB 16.3MB 262kB parm-spml_dep
4 16.3MB 16.5MB 262kB RF_CAL_FILE
5 16.5MB 24.9MB 8389kB KERNEL
6 24.9MB 33.3MB 8389kB RECOVERY
7 33.3MB 53.0MB 19.7MB modem
8 53.0MB 86.2MB 33.3MB reserved
9 86.2MB 88.3MB 2097kB SBL1
10 88.3MB 90.4MB 2097kB SBL2
11 90.4MB 98.8MB 8389kB PARAM
12 98.8MB 99.4MB 524kB DTSBK
13 99.4MB 99.9MB 524kB DTS
14 99.9MB 108MB 8389kB VC-FirmwareBK
15 108MB 117MB 8389kB VC-Firmware
16 117MB 117MB 262kB FOTA_SIG
17 117MB 138MB 21.0MB ext4 efs
18 138MB 1212MB 1074MB ext4 CSC
19 1212MB 2822MB 1611MB ext4 system
20 2822MB 3409MB 587MB ext4 HIDDEN
21 3409MB 4433MB 1024MB ext4
22 4433MB 6044MB 1611MB ext4
23 6044MB 6744MB 700MB ext4
24 6744MB 7813MB 1069MB ext4
Then
Code:
quit
Now flash your first stock ROM..ofcource custom one from recovery.
Now You can flash your desired AOSP rom as primary and dualboot enabled secondary rom.
Scripts to switch roms has been updated.
Download following dualboot enabled AOSP rom by me CosmicCm
http://www.androidfilehost.com/?fid=23329332407579496
Download following tool kit and extract on your External sd card for AOSP rom and in Internal SD for your stock rom.
http://www.androidfilehost.com/?w=files&flid=12981
Install smanager (os.tools.scriptmanager-1.apk) in zip.
Instructions on ROM switching:
1. Go to Play Store and install SManager (or included in dualboot-k2wl-V2.zip)
2. Run SManager, browse to your DualBoot folder and select "StockPrimary.sh/AOSPprimary.sh" or "AOSPSecondary.sh". depending upon which rom you want to boot into.
3. Mark favourite and su options and run the script.
4. Optional - SManager has a homescreen widget system. It lets you add buttons in your homescreens that will directly run the linked script (it has to be put in favourites first).
AGAIN this is a nuclear level risky procedure and is for ADVANCE users only....
DO NOT TRY IF YOU DONT KNOW WHAT YOU ARE DOING.......
Bugs:-
Your data partitions will be small about 1 GB.
External SD card not working in stock rom.
More?>..... You telll me...
HAPPY FLASHING.....
Credits:-
dreccon
berni987654321
51dusty
and for best inspiration and beta tester....
xenon92

Reverting
To revert
Boot into recovery
start
Code:
adb shell
Code:
cd /dev/block
parted mmcblk0
print
rm 24
rm 23
rm 22
rm 21
Code:
mkpartfs primary ext2 3409 7813
Code:
quit
Reboot into recovery again
on pc type
Code:
adb shell
mke2fs /dev/block/mmcblk0p21
tune2fs -j /dev/block/mmcblk0p21
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p21
now you reverted back.

another one

Awesome work bro
Thanks man
Sent from my GT-I9082 using Tapatalk

Awsm work bro..keep up the good wrk..stay blessed..
Sent from my GT-I9082 using Tapatalk 2

Does this method works with only cosmiccm ROM or it works with all aosp based ROM ?
Sent from my GT-I9082 using Tapatalk

Right now only CosmicCm but if developers willing for making their dualboot compatible rom, it wil.

k2wl said:
Right now only CosmicCm but if developers willing for making their dualboot compatible rom, it wil.
Click to expand...
Click to collapse
@k2wl
Please update your signature for awesome Rom "CosmicCm":good:

OMG!! REallyy Superb workk man:angel::angel:

good work mate but how to undo ..these all changes ? any procedure?

himuslg123 said:
good work mate but how to undo ..these all changes ? any procedure?
Click to expand...
Click to collapse
Flashing PIT file probably.
Sent from my GT-I9082 using Tapatalk

himuslg123 said:
good work mate but how to undo ..these all changes ? any procedure?
Click to expand...
Click to collapse
akiratoriyama said:
Flashing PIT file probably.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
@himuslg123 @akiratoriyama
Look into the second post...
reverting changes...

thanks for the tutorials k2wl
but I have a doubt
suppose ..I have installed 2 roms
now if I want to flash a mod zip( i.e pagapps or so) file for a specific rom via CWM recovery ...ll they be installed on a specific partition for a specific rom ?

for second rom its a problem, i.e AOSP.
thats why i included gapps core in CosmicCM dual boot rom.
for original primary rom stock, you can flash any mods you want.
Give me links for the mods and gapps you wanted.
i will change them into dual boot...

aahh ..that's all I want ..you rock \m/

k2wl said:
for second rom its a problem, i.e AOSP.
thats why i included gapps core in CosmicCM dual boot rom.
for original primary rom stock, you can flash any mods you want.
Give me links for the mods and gapps you wanted.
i will change them into dual boot...
Click to expand...
Click to collapse
Well ..first thanks for this procedure..the more i thank u , the less it would be mahn!..
Now, as u say that u will help guys for mods to dual boot too, the only thing i flash after ur roms is ur kernel ... I dont think its already in there in cosmic rom,And cant live without evolution kernel mahn :|..but i think kernel flashing will screw things up right??

yes it might screw things up..
bt dont worry i will add option for evaluation dualboot kernel soon.
this is work in progress.
will add more options...

k2wl said:
yes it might screw things up..
bt dont worry i will add option for evaluation dualboot kernel soon.
this is work in progress.
will add more options...
Click to expand...
Click to collapse
general question plss..y kernel is not put as a default in ROM( I mean ur kernel and ur ROM).
Though it will not allow users of RR and carbon to use this kernel. just of curosity

Any possibility for a GUI apps or flashable zip to do all this procedure of dual boot in future development? What I mean is like GUI apps of EFS backup

wiryawang said:
Any possibility for a GUI apps or flashable zip to do all this procedure of dual boot in future development? What I mean is like GUI apps of EFS backup
Click to expand...
Click to collapse
No...not so soon...
firstly this is risky procedure
and second
i like commandline better.
better control and fast..
so i cant help you with this.

Lost 11 GB while upgrading Galaxy S Advance to Jelly bean 4.1.2(India)

Hi,
I have lost almost 11gb because of using incorrect PIT file while I was trying to update my S Advance to official jelly bean firmware. After that I don't know but it was not booting up at all and it was almost bricked. I had to approach local vendor to repair it. They repaired but now I am struggling to get the lost space back.
I installed a software called DiskInfo which shows following output.
internal storage(MMC)
mmcblk0p1 /mnt/.lfs 16mb
(Unknown size)
mmcblk0p2 /modemfs 16mb
System mmcblk0p3 /system 612mb
Cache mmcblk0p4 /cache 306mb
Data mmcblk0p5 /data 2GB
mmcblk0p6 not mounted 1.5mb
mmcblk0p7 /efs 10mb
SD card
mmcblk0p8 3.9GB
mmcblk0p9 /preload 320mb
mmcblk0p10 not mounted 1mb
mmcblk0p11 not mounted 50mb
mmcblk0p12 not mounted 2mb
mmcblk0p13 not mounted 16mb
mmcblk0p14 not mounted 2mb
mmcblk0p15 not mounted 16mb
mmcblk0p16 not mounted 2mb
mmcblk0p17 not mounted 2mb
mmcblk0boot1 not mounted 2mb
mmcblk0boot0 not mounted 2mb
TMPFS MOUNT POINTS
/dev 312mb
/mnt/asec 312mb
/mnt/obb 312mb
/dev/shm 312mb
Is there any way to get it back without flashing it?

Hi,
I will have your thread moved to your device section. You will need to register on XDA to respond to any replies.
Good luck!

XDA Visitor said:
Hi,
I have lost almost 11gb because of using incorrect PIT file while I was trying to update my S Advance to official jelly bean firmware. After that I don't know but it was not booting up at all and it was almost bricked. I had to approach local vendor to repair it. They repaired but now I am struggling to get the lost space back.
I installed a software called DiskInfo which shows following output.
internal storage(MMC)
mmcblk0p1 /mnt/.lfs 16mb
(Unknown size)
mmcblk0p2 /modemfs 16mb
System mmcblk0p3 /system 612mb
Cache mmcblk0p4 /cache 306mb
Data mmcblk0p5 /data 2GB
mmcblk0p6 not mounted 1.5mb
mmcblk0p7 /efs 10mb
SD card
mmcblk0p8 3.9GB
mmcblk0p9 /preload 320mb
mmcblk0p10 not mounted 1mb
mmcblk0p11 not mounted 50mb
mmcblk0p12 not mounted 2mb
mmcblk0p13 not mounted 16mb
mmcblk0p14 not mounted 2mb
mmcblk0p15 not mounted 16mb
mmcblk0p16 not mounted 2mb
mmcblk0p17 not mounted 2mb
mmcblk0boot1 not mounted 2mb
mmcblk0boot0 not mounted 2mb
TMPFS MOUNT POINTS
/dev 312mb
/mnt/asec 312mb
/mnt/obb 312mb
/dev/shm 312mb
Is there any way to get it back without flashing it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2096093