Related
From being used to a Linux PC with everything on a couple of partitions, trying to suss out how Android works has baffled me a bit what with having so many things hidden away in so many different places. I couldn't find a partition map for our phone so I made one by looking at /proc/partitions, using the mount command, analysing s5830i ODIN pit files and searching the internet. I realise that this isn't new information in that I'm pretty sure this stuff is known by some people but I still thought that this was worth putting out there.
I've listed the information in the following format:
#blocks <device file name> <partition name> (<flash file name> <Odin part>) <information>
Mount points are given where relevant. Partition name and flash file name are from the Odin pit file. To get the 'Odin part' I looked inside my “Full Firmware Backup To Odin Format”, which is a CWM script by Rafael.Baugis.
I've tried to be as accurate as possible and make it clear where I'm not 100% sure but please help me improve it if you can as I done this as a learning exercise in the first place!
Figures from /proc/partitions (also see the mount command):
#blocks name
31166976 mmcblk0 – sdcard (entire device)
29179904 mmcblk0p1 – sdcard partition 1 *
1945600 mmcblk0p2 - sdcard partition 2 *
513024 bml0/c – All bml partitions (figures add up to 513024)
256 bml1 – bcm_boot (BcmBoot.img – BOOT) – Bootloader
2048 bml2 – loke (sbl.bin - PDA) - Secondary bootloader
2048 bml3 – loke_bk (no flash file) - Presumably SBL backup
256 bml4 – systemdata (totoro.pit) – A copy of the Odin pit file by the looks of it
12800 bml5 – modem (BcmCP.img – PHONE) - baseband/modem
5120 bml6 – see stl6 **
5120 bml7 – boot (boot.img - PDA) - The kernel and ramdisk
5120 bml8 – boot_backup (no flash file) – Presumably boot.img backup
235520 bml9 – see stl9 **
40960 bml10 – see stl10 **
201984 bml11 – see stl11 **
256 bml12 – efs (?) (no flash file) – Not sure why this is called 'efs' as efs is well documented as being on bml15 and the number of blocks isn't even the same
256 bml13 – sysparm (sysparm_dep.img – BOOT) – part of the bootloader?
256 bml14 – umts_cal - (HEDGE_NVRAM8_RF_LE.bin – BOOT) – part of the bootloader?
1024 bml15 – cal (no flash file) - Not sure about the name but this is the EFS partition containing IMEI + network/region lock info
1280 stl6 – param_lfs (param.lfs – PDA) - mount point: /mnt/.lfs – SBL data including settings and images such as Samsung S5830i boot logo.
227840 stl9 – system (system.img - PDA) - mount point: /system – Operating System / ROM
36864 stl10 - cache (csc.rfs - CSC) - mount point: /cache – App/system cache storage but apparently CSC (region specific) data is also flashed here which seems odd but true!
194816 stl11 - userdata (userdata.img) - mount point: /data
- (dm-0 to dm-18) - Each app that is stored via SD card has its own virtual partition. I have 19 applications stored via traditional apps2sd, hence dm-0 to dm-18. Mount Point: /mnt/asec/<app's Java package name>
- (loop0 to loop18) – Loop devices. Each numbered loop is directly related to its dm counterpart, filesystem size is practically identical. I don't really understand loop devices that well so I can't say more than that!
* SD card partitions have other block device files, from which they are mounted via, at:
/dev/block/vold/179:1 - sdcard 1st partition – mount points: /mnt/sdcard and /mnt/secure/asec
/dev/block/vold/179:2 - sdcard 2nd partition – mount point: /data/sdext2
** This is from XDA user Darkshado in the following post:
“From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size”
http://forum.xda-developers.com/showpost.php?p=16963172&postcount=1
In actual fact bml and stl counterparts don't differ very much at all in size. From what I've read elsewhere the reason for the availability of stl interfaces on only some partitions may be related to the need for regular read-write access.
*** stl* and bml* interfaces can be accessed through device files such as /dev/stl*, dev/bml*, /dev/block/stl* and dev/block/bml*.
Of course just because they can be doesn't mean it's necessarily a good idea!
Dear Moderators!
Since I had top stop being active in the development the threads that I started with having a master directory and thus that are left here has become totally stale since they have not been updated in a long time nor do I have current plans to continue.
I don't track this forum and the wonders done with this phone but this post has some real potential danger.
The post is outdated and the information in it could therefore be wrong, faulty or even harmful. And I see it mostly harmful in my point of view, since this was the baby steps taken a long time ago.
Looking at the contents it compares several parts of partition tables and even brave (and foolish) tries of me testing philz recoveries. Now Philz has put some safety code since the Note II/S3 melds but for a less experienced user that look at the names.
"hlte and jflte", sound pretty close that we know is not the case but they reeeely want so badly into the "world" of S4 they could try to alter the partition tables, that we serve them on a platter and that there are easy utils for, to TRY make it look like the "real" S4 and really hard brick the phone, or even worse try TWRP of the hlfe "since it was so long time ago" and look at their screen melting away.
Proper scientific rules dictates that if any information is unknown and therefore in a volatile state it should fall under the principle of caution until verified of its validity and safety. I have no insight into that validly and the current development but I highly doubt this post is needed any longer and since this is accessible to the public the "not doing any harm" comes into place and thus this thread should be deleted since if anything useful came out of it it has already been taken into current development and it can cause harm. A lock will not suffice.
Since I know that many posts are not considered being "device specific enough" (like a discussion about lowering the voltage of the kernel) or "cluttering" (explaining the booting process of a kernel works) this post should absolutely fall under some of those rules (or some other that I've yet not encountered) and I strongly think a deletion of this would be more proper then just moving it to the trashcan "General"?
So at least I try to make you see that this post should not be in the trashcan but deleted for the safety of less experienced users.
You can say that they are then stupid. I call them inexperienced. I tried to so many times to post and raise the level of knowledge and we all know where those writing for 8 hours posts went, right?
But this is not about being ignored from "higher devs" about my finding of a side channel attack in the bootloader in 4.3.
This post is just not a safe for those unlucky who got this ****ty phone on their warranty (I got one too). They feel cheated and I understand them.
It's useless, can't use the S4 and not the N9005 stuff. The guys here did an amazing job with it but I had leave. But someone can really do something stupid and and this post gives false "hope". I got some "Pit"-file. Lets try that one...
Since this is also a stub for a "collection" that I also could not finish and I don't recall if I did something more of those but I know you are pros of finding nonsense like this and could you please remove that "clutter" as well?
All the best,
Absie
Abstract
This thread is about testing and finding similarities and differences between the currently two Snapdragon 800 Samsung smartphones, namely the I9506 and Galaxy Note 3 (SM-N9005, hltexx). What we know so far is that they use the same hardware and production line and are separated quite late where they diverge. The theory is therefore that the Samsung Note 3 LTE binaries should work since the development here is non-existent and the similarities are larger between those two then with the previous S4, I9505. The work seem not as straight forward and so far binaries from Note 3 have been incompatible and this thread is about finding our just WHY this is so and how we can try to overcome those problems and have some porting of available ROMs from the major project branches. Similarities with the previous S4 (I9505) will be investigated along the progress of this thread. Since this device is shipped with Android v4.2.2 and without KNOX activated we also need to investigate what activates KNOX and how to avoid that.
Collection of findings
This is a stub of the different pages that will be updated as the progress is ongoing and will be updates as we move along and collect the findings.
General Findings
Stub
Custom Recoveries
Stub
Kernels
Stub
Roms
Stub
Other (KNOX, modems, bootloaders etc)
Stub
.
General Findings
Things we know
The I9506 and Note 3 (int) are based on the same board and therefore they should be interchangeable.
The Pit-files (Partition information) are identical for the both devices except for the obvious, larger screen, more mem and bigger internal data partition. All other partitions are exactly the same and lies on the same place in the Flash which should porting much easier since the core partition layout is the same and makes it much easier and safer to try different versions.
The initial tests done with trying different Custom recoveries has not worked.
Things we don't know
Are the kernel interchangable? Here we have note yet had a 4.3 for I9506 to compare but Samsung has started to roll out that. Knox is then activated.
Differences between other partitions and their content
Questions that need answers (volunteers are needed!)
Now that we have at least 2 versions of the 4.3, we need to hunt for the same releases made on Note 3 and compare them.
Why is not Custom recovery working? Is it something simple?
Does anything from the I9505 work? Are there any similarities there?
.
Custom Recovery
So far we hare 2 custom recoveries (links will be provied).
No custom recoveries from Note 3 has yet been working.
The following recoveries from Note 3 have been tested and found not been working my normal replacement in Odin
Philz_touch_6.04.1 - (Give the first BSOD! Blue! Blue!)
Philz_touch_6.08.9 - (Seems like the screen is melting)
Openrecovery-twrp-2.6.3.0 - (Black screen. Nothing happens)
You can all try, those who has 4.3 and Knox 0x01 could test those. It seems a bit scary, but at least for the the "pull the battery and reinstall a normal one with Odin" worked,
but as usual, this is work that need to be done and nobody here can promise anything. Brick/unbrick, but you might be the hero if you get stuff to work from over Note (like a kernel).
So I have something to fill the next post with?
Who initially provided the working custom recoveries and what was done to make them work?
Please PM me if you don't want to write it here.
.
Kernels
Roms
Other (KNOX, modems, bootloaders etc)
Reserved
Absolon said:
Custom Recovery
So far we hare 2 custom recoveries (links will be provied)
No custom recoveries from Note 3 has yet been working.
The following recoveries from Note 3 have been tested and found not been working my normal replacement in Odin
Philz_touch_6.04.1
Philz_touch_6.08.9
Openrecovery-twrp-2.6.3.0
.
Click to expand...
Click to collapse
Hi Absolon.
Probably because a different portion table. Our is even different from the GT-I9505.
I'll post our full partion table, as it looks on our phone. Just need to get home and fire up my Ubuntu/Linux.
See ya'
Sent from my GT-I9305 using XDA Premium 4 mobile app
I made the Pit files yesterday from the two devices and the are the same.
Same size, same memory adresses.
DeHAWK said:
Hi Absolon.
Probably because a different portion table. Our is even different from the GT-I9505.
I'll post our full partion table, as it looks on our phone. Just need to get home and fire up my Ubuntu/Linux.
See ya'
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you see the PIT-files I sent you yesterday?
Those where the same. Exactly the same. So how can it differ?
I posted them above this reply
Absolon said:
Did you see the PIT-files I sent you yesterday?
Those where the same. Exactly the same. So how can it differ?
I posted them above this reply
Click to expand...
Click to collapse
Just received them. I put the files up in a moment.
Sent from my GT-I9506 using XDA Premium 4 mobile app
Ok, now back on my PC, look at this..
[email protected]:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2013-06-28 18:24 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-06-28 18:24 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-06-28 18:24 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-06-28 18:24 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-06-28 18:24 cache > /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-06-28 18:24 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-06-28 18:24 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-06-28 18:24 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-06-28 18:24 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-06-28 18:24 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-06-28 18:24 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-06-28 18:24 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-06-28 18:24 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-06-28 18:24 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-06-28 18:24 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-06-28 18:24 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-06-28 18:24 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-06-28 18:24 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-06-28 18:24 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-06-28 18:24 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-06-28 18:24 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-06-28 18:24 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-06-28 18:24 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-06-28 18:24 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-06-28 18:24 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-06-28 18:24 userdata -> /dev/block/mmcblk0p26
Mount Point Number Filesystem name
/dev/block/mmcblk0p1 anphlos
/dev/block/mmcblk0p2 modem
/dev/block/mmcblk0p3 sbl1
/dev/block/mmcblk0p4 dbi
/dev/block/mmcblk0p5 ddr
/dev/block/mmcblk0p6 aboot
/dev/block/mmcblk0p7 rpm
/dev/block/mmcblk0p8 tz
/dev/block/mmcblk0p9 pad
/dev/block/mmcblk0p10 param
/dev/block/mmcblk0p11 ext4 efs
/dev/block/mmcblk0p12 modemst1
/dev/block/mmcblk0p13 modemst2
/dev/block/mmcblk0p14 boot
/dev/block/mmcblk0p15 recovery
/dev/block/mmcblk0p16 fota
/dev/block/mmcblk0p17 backup
/dev/block/mmcblk0p18 fsg
/dev/block/mmcblk0p19 fsc
/dev/block/mmcblk0p20 ssd
/dev/block/mmcblk0p21 persist
/dev/block/mmcblk0p22 ext4 persdata
/dev/block/mmcblk0p23 ext4 system
/dev/block/mmcblk0p24 ext4 cache
/dev/block/mmcblk0p25 ext4 hidden
/dev/block/mmcblk0p26 ext4 userdata
Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
I had to find some info in XDA, but it should look like this. One thing is sure, and thats the first part, the last 2 parts I made myself...
Try to run the command: ls -al /dev/block/platform/msm_sdcc.1/by-name
Do it in a terminal.
Btw. Does anybody know why I can't upload screenshots and other stuff???
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Absolon said:
I made the Pit files yesterday from the two devices and the are the same.
Same size, same memory adresses.
Click to expand...
Click to collapse
Got your mail, looking at them right now and comparing with my own files.
See ya'
---------- Post added at 08:09 PM ---------- Previous post was at 08:01 PM ----------
DeHAWK said:
Got your mail, looking at them right now and comparing with my own files.
See ya'
Click to expand...
Click to collapse
Ok, this looks nice. Have to look more into them.
---------- Post added at 08:21 PM ---------- Previous post was at 08:09 PM ----------
xenix96 said:
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Click to expand...
Click to collapse
My dear friend, please zip your files, I don't use rar in Ubuntu.
Have to switch to Windows and back...lol
Somethings wrong with my account here, it log out out after a few minutes, can't add pics etc...
But at least I can get in now on my laptop. Might have to cantact the Mod.
See ya'
DeHAWK said:
Got your mail, looking at them right now and comparing with my own files.
See ya'
---------- Post added at 08:09 PM ---------- Previous post was at 08:01 PM ----------
Ok, this looks nice. Have to look more into them.
---------- Post added at 08:21 PM ---------- Previous post was at 08:09 PM ----------
My dear friend, please zip your files, I don't use rar in Ubuntu.
Have to switch to Windows and back...lol
Somethings wrong with my account here, it log out out after a few minutes, can't add pics etc...
But at least I can get in now on my laptop. Might have to cantact the Mod.
See ya'
Click to expand...
Click to collapse
Added Mappe1.zip to http://forum.xda-developers.com/showpost.php?p=49182714&postcount=12
Cheers
Nice thread, i already have the i9506, and i will get my Note 3 as a company phone on wednesday. I'd ble glad to help!
I created my I9506 files from my phone.
All XDA related content will be placed here for reference and PM me your gmails and I give you r/w there.
(changed the link since someone tried to read INSIDE a rar file in gdocs. There is a zip there now as well)
So, as you see, I got the same values, just that you didn't give you any?
We do have exactly the same layout
We know it's the same board
We have recovery that is working
N9005 recoveries are NOT?
Any idea?
Who had the "mended" Philz from start? What was changed so it would work?
Because if we can figure this out it looks promising. If we can't then we need to start trying (need that anyway) compiling stuff and go from there.
But I thought it would be interesting just to check if it would work or not. Damn it...
/Abs
Edit: OMG, I outed myself
xenix96 said:
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Click to expand...
Click to collapse
I created the PIT-file from my phone.
Will place all further things
xenix96 said:
Added Mappe1.zip to http://forum.xda-developers.com/showpost.php?p=49182714&postcount=12
Cheers
Click to expand...
Click to collapse
Yes, I will use the algorithm that was invented in 1978 (ok 1989 and I have NO IDEA why Google chose that when there are so many more effective alg that are OS)...
I can use LHA, or even a C64 cruncher just to get you start working dammit
And btw, unrar if freeware
/Absie
This thread will list and link to all core device essential stuff.
PM me if there is new stuff please
STOCK ASUS FIRMWARE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
Seperate Sd update for WW versions to recover from wrong released OTA, when unzipped place it on MicroSdcard and reboot:
WW_10_26_1_18_SDupdate.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
TW_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
US_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_42_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
Altered CWM Recovery V6.0.3.7. for 4.2.2.*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery CWMrecovery4.2.2.img [where CWMrecovery4.2.2.img is the name of the file image you downloaded]
There is at the moment no CWM-Recovery or TWRP-Recovery for 4.3. version yet!!!
* With thanks to Drgravy for his work on that.
CUSTOM ROM'S
None available yet.
Will be released by Sbdags when there is a custom recovery for 4.3. available.
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!
Odd that you just started this thread and it's outdated ;P
Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/showthread.php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/showthread.php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/showthread.php?t=2621028
Sorry folks. Thread closed as it already exists in the General Forum.
MD
I wrote this How-To several months ago and published in a spanish forum.
Now I've recovered to share here as it may interest someone.
This was originally written in spanish and now, our friendly companion @nachordez
has been kind enough to translate it to english. Thank you very much for your help. :good:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'll try to explain here how to change the size of our device partitions.
Though the presented data are referred to a 16 GB, a p5110 in this case, they are easy to adapt to a 8 GB one, and/or any other model, with some light corrections.
There can be other ways, but this one has the advantage that depends only on not writing wrong data, and that's easily achieved with a little extra concentration during our work.
Anyway, it's needed to follow very strictly this how-to.
In case of total failure, we should restore the tab through the flashing of a Stock version using the pit file.
ALL the data not saved in the external MicroSD card WILL BE LOST, 'cause we'll delete the /system, /data and /cache partitions.
What is needed:
A computer.
A properly running adb program.
Recovery installed.
External MicroSD card installed and with available space.
Connection cable.
Full Battery.
For 3G (GSM) models, the original “modem.bin” file, obtained from a stock ROM.
The modem.bin file is not really needed as we can get it from our tablet with next command
dd count=40960 bs=512 if=/dev/block/mmcblk0p8 of=/external_sd/modem.bin
All process is done from computer, except a short intervention at end, done from tablet.
This how-to is planned for a AOSP-like ROM, such as CyanogenMod (for example).
In the case of a Stock ROM, the partition sizes we are adjusting will be too short for it.
Before starting:
We have to check that there is enough free space in the MicroSD card, and we have to do a backup through recovery, choosing EXTERNAL SDcard.
If the internal one is used, IT WILL BE LOST DURING PROCESS.
This step is very important, to recover the ROM without re-install from zero.
So, let me say it again: EVERY USER DATA that has being not COPIED to the EXTERNAL SDcard, WILL BE LOST.
After next steps, ONLY the external MicroSD will be conserved without erasing.
So, we check once again that everything is saved, and copy to the external MicroSD (if our tab is a 3G model) the “modem.bin” file that will be needed afterwards.
So... Let's start hacking!:
We always wrote in our PC.
We reboot our tab in recovery mode, and connect the cable.
To enter the tab from our computer:
> adb shell
Once entered correctly on the tablet, we like more clear ls command:
> alias ls='ls -an'
Now we access the partition table:
> parted /dev/block/mmcblk0
We'll get something like:
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)
The command line for parted is (parted), so, every time a line starts so, that what follows this is a command.
We ask for information about current partitions:
(parted) p
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number... Start... ....End......... Size...........File system...... Name.... Flags
1............4194kB.... 25.2MB.... 21.0MB...... ext4................ EFS
2........... 25.2MB.... 27.3MB....2097kB............................... SBL1
3........... 27.3MB.....29.4MB....2097kB............................... 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...789.0MB.. 734.0MB....... ext4................CACHE
8......... 789.0MB.. 810.0MB.... 21.0MB.............................. MODEM
9......... 810.0MB.., 2278MB... 1468MB....... ext4............... FACTORYFS
10........ 2278MB.... 15.2GB.... 12.9GB........ext4............... DATAFS
11......... 15.2GB..... 15.8GB.... 537MB....... ext4............... HIDDEN
Comments:
Analizing the current partitions we can see this tablet is a 16 GB one:
/cache (CACHE) has 734 MB assigned
/system (FACTORYFS) has 1468 MB assigned
/data (DATAFS) has 12,9 GB assigned
There's also a funny 537 MB partition called HIDDEN: that's where the Samsung video, musical theme and demo pictures are stored.
If I don't mistake, I think I extracted them time ago, and they were just about 14 MB. In our case, we'll opt for destroying that!
In this how-to we'll assign:
/cache (CACHE) 400 MB
/system (FACTORYFS) 600 MB
/data (DATAFS) the sum of: its current size + 394 MB from CACHE + 868 MB from FACTORYFS + 536 MB from HIDDEN.
So, we'll grow our /DATAFS space in 1798 MB, which will mean more than 14 GB free space.
I use in this example 600 MB for /system was what I did in my tab.
In real world, 240 MB /cache and 500 MB /system are more than enough.
As we'll see later, all this numbers are just aproximations, not completely exact, and probably you're thinking: “My maths do not agree with this numbers”. Mine do not, also, as a fact.
Let's see all that more slowly:
21+2+2+8+8+8+21+1 (for the 'hidden' partitions) give us 71 MB.
If we add 71 + 400 +600 we'll get 1071 MB.
If we have 16 GB and we use 1 GB, more than 15 GB should rest.
On one hand: 1 GB are 1048 MB. So, 16 GB should be 16768 MB, but we have just 15709.
That has a easy explanation: The hard disk makers started to measure 1 GB as 1000 MB (kind of a commercial trick). So, just beginning with that, 768 MB have disappeared in thin air.
On the other hand, we have 34 initial sectors to sustain the partition table, alternative sectors for errors recovering, rounding of numbers in sectors to partitions assignations, etc.
We have 11 partitions just now:.............................................. And they should get like that:
01 00021 MB...........................................................................01 00021 MB
02 00002 MB...........................................................................02 00002 MB
03 00002 MB...........................................................................03 00002 MB
04 00008 MB...........................................................................04 00008 MB
05 00008 MB...........................................................................05 00008 MB
06 00008 MB...........................................................................06 00008 MB
07 00734 MB...........................................................................07 00400 MB *
08 00021 MB...........................................................................08 00021 MB
09 01468 MB...........................................................................09 00600 MB *
10 12900 MB...........................................................................10 14638 MB *
11 00537 MB...........................................................................11 00537 MB
.....15709 MB................................................................................15709 MB
The difference can seem small compared to the original partitioning, nevertheless will allow us to get all our usual apps installed and, even so, preserve a free space higher than we had previously, even before than start to install anything. That's saying: even more than with a pure CM just installed and not even configured.
Obviously, if we translate all that to a 8 GB model, the proportional gain is much higher.
Also, consider that an AOSP rom like CM is not bigger than 460 MB in /system, and that cache will need just 60 MB for dalvik and what we can download from google-play at a certain time. 170 MB should be enough, unless we want to download an app bigger than 100 MB. The bigger ones I've saw are around 90-105 MB.
In this moment, we'll have to decide if we want to follow on or not.
Till now, I was just fun, but nothing has being 'broken'.
Disclaimer: If you continue reading next post, and you do what's there exposed, it will be ONLY under YOUR RESPONSIBILITY. You've being warned...
CopyRight Tuxafgmur - Dhollmen 2013-2014. You can copy and distribute this post only if you mentions Author and references this XDA theread.
:
You have chosen to continue (you're a risky guy...)
We change the info into number of sectors (512 byts each one)
(parted) u s
(parted) p
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 30777344s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Num... Start................ End............ Size........ Fs....... Name
1............ 8192s.......... 49151s....... 40960s... ext4....EFS
2.......... 49152s.......... 53247s......... 4096s............... SBL1
3.......... 53248s.......... 57343s......... 4096s............... SBL2
4.......... 57344s.......... 73727s....... 16384s............... PARAM
5.......... 73728s.......... 90111s....... 16384s............... KERNEL
6.......... 90112s........ 106495s....... 16384s............... RECOVERY
7........ 106496s...... 1540095s... 1433600s.... ext4... CACHE
8...... 1540096s...... 1581055s....... 40960s................MODEM
9...... 1581056s...... 4448255s... 2867200s.... ext4... FACTORYFS
10.... 4448256s.... 29728733s..25280478s.... ext4... DATAFS
11...29728734s.... 30777309s... 1048576s.... ext4... HIDDEN
(From here onwards, I'll omit the heading, so that it's always the same)
We can see easily the ratio between MB and sectors: 4096 sectors equal 2 MB, so 1 MB are 2048 sectors.
Now, we'll delete the last partition, 'cause starting with it will make work easier at end.
(parted) rm 11Now, we create it again, but with different data, specifying the sector where it begins (30775263) and sector where it finishes (30777310)
(parted) mkpart 11 30775263 30777310
(parted) p
Num...... Start................ End............ Size..... Fs....... Name
1............ 8192s.......... 49151s....... 40960s... ext4......EFS
2.......... 49152s.......... 53247s......... 4096s............... SBL1
3.......... 53248s.......... 57343s......... 4096s............... SBL2
4.......... 57344s.......... 73727s....... 16384s............... PARAM
5.......... 73728s.......... 90111s....... 16384s............... KERNEL
6.......... 90112s........ 106495s....... 16384s............... RECOVERY
7........ 106496s...... 1540095s... 1433600s.... ext4...CACHE
8...... 1540096s...... 1581055s....... 40960s................MODEM
9...... 1581056s...... 4448255s... 2867200s.... ext4... FACTORYFS
10.... 4448256s.... 29728733s..25280478s.... ext4... DATAFS
11... 30775263s... 30777310s......... 2048s
So, we have a 1 MB partition that previously was a 537 MB one
Yes, you're right. I've changed last sector from 30777309 into 30777310. I haven't added one new sector to disk, it was yet there, but unassigned.
This is so 'cause I want the total to be an even number of sectors, and also this partition sectors number has to be even.
Previously, this partition had a name. So, let's be polite with it:
(parted) name 11 HIDDEN
(parted) p
Num...... Start................ End............ Size..... Fs....... Name
1............ 8192s.......... 49151s....... 40960s... ext4.....EFS
2.......... 49152s.......... 53247s......... 4096s............... SBL1
3.......... 53248s.......... 57343s......... 4096s............... SBL2
4.......... 57344s.......... 73727s....... 16384s............... PARAM
5.......... 73728s.......... 90111s....... 16384s............... KERNEL
6.......... 90112s........ 106495s....... 16384s............... RECOVERY
7........ 106496s...... 1540095s... 1433600s.... ext4....CACHE
8...... 1540096s...... 1581055s....... 40960s................MODEM
9...... 1581056s...... 4448255s... 2867200s.... ext4... FACTORYFS
10.... 4448256s.... 29728733s..25280478s.... ext4... DATAFS
11... 30775263s... 30777310s......... 2048s............... HIDDEN
Done. Now, we can forget it, and not even format it.
So that it is the last partition, and will not be used, all this work was really unnecessary, but, preventing the case that any process could count partitions, we keep home tidy.
OK. By now we have:
Deleted partition
Created partition
Named partition
If we have a previously calculated chart, we'll just have to do next steps for each partition and we don't need even to look at it, just to check at end if the obtained result was the one expected.
Anyway, in this How-To we'll do things one by one.
We shrink the CACHE partition
We calculate: 400 x 2048 = 819200 (400 MB x 2048 sectors = 819200 sectors)
106496 + 819200 = 925696 -1 = 925695
Our new partition starts in sector 106496 and finishes in sector 925695
(parted) rm 7
(parted) mkpart 7 106496 925695
(parted) name 7 CACHE
(parted) p
Num...... Start................ End............ Size..... Fs....... Name
1............ 8192s.......... 49151s....... 40960s... ext4.....EFS
2.......... 49152s.......... 53247s......... 4096s............... SBL1
3.......... 53248s.......... 57343s......... 4096s............... SBL2
4.......... 57344s.......... 73727s....... 16384s............... PARAM
5.......... 73728s.......... 90111s....... 16384s............... KERNEL
6.......... 90112s........ 106495s....... 16384s............... RECOVERY
7........ 106496s........ 925695s..... 819200s.... ext4... CACHE
8...... 1540096s...... 1581055s....... 40960s................MODEM
9...... 1581056s...... 4448255s... 2867200s.... ext4... FACTORYFS
10.... 4448256s.... 29728733s..25280478s.... ext4... DATAFS
11... 30775263s... 30777310s......... 2048s............... HIDDEN
We just move the MODEM partition : 925696 + 40960 -1 = 966655
(parted) rm 8
(parted) mkpart 8 925696 966655
(parted) name 8 MODEM
Now, let's go for the FACTORYFS one
(parted) rm 9
(parted) mkpart 9 966656 2195455
(parted) name 9 FACTORYFS
(parted) p
Num...... Start................ End............ Size..... Fs....... Name
1............ 8192s.......... 49151s....... 40960s... ext4.....EFS
2.......... 49152s.......... 53247s......... 4096s............... SBL1
3.......... 53248s.......... 57343s......... 4096s............... SBL2
4.......... 57344s.......... 73727s....... 16384s............... PARAM
5.......... 73728s.......... 90111s....... 16384s............... KERNEL
6.......... 90112s........ 106495s....... 16384s............... RECOVERY
7........ 106496s........ 925695s..... 819200s.... ext4... CACHE
8........ 925696s...... . 966655s....... 40960s................MODEM
9........ 966656s.......2195455s....1228800s................FACTORYFS
10.... 4448256s.... 29728733s..25280478s.....ext4....DATAFS
11.. 30775263s.... 30777310s..........2048s................HIDDEN
There only rest DATAFS.
For it, no calculations are needed: it starts in the sector following FACTORYFS and ends in the previous to HIDDEN.
(parted) rm 10
(parted) mkpart 10 2195456 30775262
(parted) name 10 DATAFS
(parted) p
Num...... Start................ End............ Size..... Fs....... Name
1............ 8192s.......... 49151s....... 40960s... ext4.....EFS
2.......... 49152s.......... 53247s......... 4096s............... SBL1
3.......... 53248s.......... 57343s......... 4096s............... SBL2
4.......... 57344s.......... 73727s....... 16384s............... PARAM
5.......... 73728s.......... 90111s....... 16384s............... KERNEL
6.......... 90112s........ 106495s....... 16384s............... RECOVERY
7........ 106496s........ 925695s..... 819200s.... ext4... CACHE
8........ 925696s...... . 966655s....... 40960s................MODEM
9........ 966656s...... 2195455s....1228800s................FACTORYFS
10.... 2195456s.... 30775262s..28579807s................DATAFS
11.. 30775263s.... 30777310s......... 2048s............... HIDDEN
So, that's what we got. It seemed difficult, but it's done!
Finishing:
We exit parted, for the end of feast using quit command
(parted) q
In this moment, we've returned to recovery.
Now, and only if our tab is a 3G/GSM one, we have to recover the modem:
dd count=40960 bs=512 if=/external_sd/modem.bin of=/dev/block/mmcblk0p8
Format:
Remember that we are in recovery. So, let's go to tablet and we select:
- mounts and storage
Search for and click on:
- format system
- format cache
- format /data and /data/media (/sdcard)
Just and only this options.
To check, now click on:
- mount /system
- mount /cache
- mount /data
If everything is OK, each one of the 3 options will change into unmount
If you are an expert user, surely you know how to format from shell, without using recovery options.
WE HAVE FINISHED. HURRAY!
Now, we have two options to reinitialize:
We install our favourite Rom, boot, configure, restore data, etc.
Or we restore the backup we did with the recovery in the external MicroSD card and we remain as if nothing had happened (but with lot more free space).
NOTE: I've wrote this how-to using CWM recovery, On others recovery, mount options can be slightly different
Disclaimer: If you have read this post, and did what is told in it, it will be ONLY under YOUR RESPONSIBILITY. You've being warned...
CopyRight Tuxafgmur - Dhollmen 2013-2014. You can copy and distribute this post only if you mentions Author and references this XDA theread.
I insert below partitions data from a p3110 tablet.
This data was attached by the user Saitoh00 from spanish HTCmania forum. This user resized partitions following this How-To.
Model: MMC M8G2FB (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.........4194kB..........25.2MB............21.0MB.......ext4.......EFS
2........ 25.2MB..........27.3MB...........2097kB......................SBL1
3.........27.3MB..........29.4MB...........2097kB..................... 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...........474MB............419MB.......ext4........CACHE
8..........474MB...........495MB...........21.0MB......................MODEM
9..........495MB...........914MB............419MB.......ext4........FACTORYFS
10........914MB.........7817MB..........6903MB.......ext4........DATAFS
11......7817MB.........7818MB...........1049kB......................HIDDEN
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 15269888s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1............8192s..........49151s.........40960s.........ext4......EFS
2..........49152s..........53247s...........4096s......................SBL1
3..........53248s..........57343s...........4096s......................SBL2
4..........57344s..........73727s.........16384s......................PARAM
5..........73728s..........90111s.........16384s......................KERNEL
6..........90112s........106495s.........16384s......................RECOVERY
7........106496s........925695s.......819200s.........ext4......CACHE
8........925696s........966655s.........40960s......................MODEM
9........966656s........785855s.......819200s.........ext4......FACTORYFS
10....1785856s....15267806s...13481951s.........ext4......DATAFS
11..15267807s....15269854s...........2048s......................HIDDE
I have cyanogenmod installed over tab 2 7 inches 16 gb which I want to change but flashing stock firmware is not possible as it gives error....I feel something is wrong at partition table. I want to repartition for stock rom. ...can u guide
Sent from my SM-A500H using XDA Free mobile app
Did you ever edit partition table of your tab? If you haven't, then nothing is wrong with partition table and no need to repartition it. Installing custom roms don't change partition structure.
You should start a new thread and post exact problem there only.
If we resized the partitions, maybe all custom rom would not boots?
Sent from my GT-I9300 using XDA Premium 4 mobile app
bangdes said:
If we resized the partitions, maybe all custom rom would not boots?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't worry, as long as the rom sticks on the partition (specially system partition)
bangdes said:
If we resized the partitions, maybe all custom rom would not boots?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you set the correct path for Partitions and available space/filesystem is correct, you can play with partition table as long as you want.
Deleted
@prav3955 what does it has to do with this thread? Use the Q&A section please.
Send from OnePlus One using Tapatalk
I request moderator to remove this post plz....
Sent from my SM-A500H using XDA Free mobile app
Not exactly, just move to 'hardware hacking' thread. This is a bleeding edge and too highrisk for newbie like me
Sent from my GT-I9300 using XDA Premium 4 mobile app
hooray! I've made it on my 8gb p3110 Here is my table if you want:
Number Start End Size File system Name Flags
1 8192s 49151s 40960s ext4 EFS
2 49152s 53247s 4096s SBL1
3 53248s 57343s 4096s SBL2
4 57344s 73727s 16384s PARAM
5 73728s 90111s 16384s KERNEL
6 90112s 106495s 16384s RECOVERY
7 106496s 925695s 819200s ext4 CACHE
8 925696s 966655s 40960s MODEM
9 966656s 2195455s 1228800s FACTORYFS
10 2195456s 15267806s 13072351s DATAFS
11 15267807s 15269854s 2048s HIDDEN
Click to expand...
Click to collapse
but it's nothing special, it uses OP's values adapted to 8gb model. I'm very happy with results: https://www.dropbox.com/s/haq4j16shfcdf9q/Screenshot_2015-04-27-21-46-12.png?dl=0
btw I had strage issue. After whole process I couldn't format my cache partition. I tried to remove it and add again but it didn't help. Hopefully solution was easy: I had to reboot my recovery. Now everything is fine
Thanks for great guide
p.s.
repartitionig is preatty easy but i've spent more than hour trying to fix adb drivers
btw some ot
If you repartitioned your galaxy tab it doesn't mean that you can repartition every other android device. I made that mistake and I've just hardbricked my xperia phone trying to repartition it (I belive it's somehow protected). My bootloader died so it's impossible to fix it at home. Keep it in mind before you try to repartition your other device.
Repartition system might cause issue flashing some/most lollipop roms because of blockbased implementation.
Android-Andi said:
Repartition system might cause issue flashing some/most lollipop roms because of blockbased implementation.
Click to expand...
Click to collapse
So, how to revert. I want to flash your rom and I cannot.
Do I have to revert to stock? Or is someone having the original partition?
cantabro said:
So, how to revert. I want to flash your rom and I cannot.
Do I have to revert to stock? Or is someone having the original partition?
Click to expand...
Click to collapse
Omni 5.1 and AOSP 5.1 should work i think. Or stay on KK.
Theres a different way too, let me see if i find it.
---------- Post added at 03:26 PM ---------- Previous post was at 03:19 PM ----------
cantabro said:
So, how to revert. I want to flash your rom and I cannot.
Do I have to revert to stock? Or is someone having the original partition?
Click to expand...
Click to collapse
Start Reading here on page 69 (and the following Pages) http://forum.xda-developers.com/showthread.php?t=3060319
They had same issue on ZMod rom and solved it.
Android-Andi said:
Omni 5.1 and AOSP 5.1 should work i think. Or stay on KK.
Theres a different way too, let me see if i find it.
---------- Post added at 03:26 PM ---------- Previous post was at 03:19 PM ----------
Start Reading here on page 69 (and the following Pages) http://forum.xda-developers.com/showthread.php?t=3060319
They had same issue on ZMod rom and solved it.
Click to expand...
Click to collapse
Thanks. But where can I find the system.tar for this?
And the last Omni founds no mirrors for download on your AndroidFileHost
I do like Lollipop
I flased omni 5.1 on my repartitoned tab and it works but 600 mb system partiton is too small for heavy lp rom and some of my favourite gapps so I decided to change partition layout again. I think that 400mb for cache it too much, my new moto e has 8 gb of storage too and only 256 mb of cache. So I changed my layout to: 256mb cache, 800mb system and rest for data. So I lost only 56mb of my data partiton while boosted by system by 200 mb so I think it is worth. Here are my commands (I think that they looks more clear than table):
I have 7'' 8 gb model
Code:
(parted) rm 7
(parted) mkpart 7 106496 630783
(parted) name 7 CACHE
(parted) rm 8
(parted) mkpart 8 630784 671743
(parted) name 8 MODEM
(parted) rm 9
(parted) mkpart 9 671744 2310143
(parted) name 9 FACTORYFS
(parted) rm 10
(parted) mkpart 10 2310144 15267806
(parted) name 10 DATAFS
It looks like that: https://dl.dropboxusercontent.com/u/37270614/Screenshot_2015-07-11-13-16-54.png
cantabro said:
So, how to revert. I want to flash your rom and I cannot.
Do I have to revert to stock? Or is someone having the original partition?
Click to expand...
Click to collapse
I solved the very same problem by flashing stock AND the special .PIT file for my version (beware: there are a 8GB and a 16GB pit files)
I looked on the partition layout of the OP3 and noticed that
1. the free space in the system partition is only about 200 MB (with OOS 3.5.1) so at some point there may be not enough space, is it possible to change the partition layout?
2. sde23 (/bt_firmware) is 1 GB large but uses only a few KiB i.e. its a waist of 1 GB :/
3. The flash seams to be divided into 6 devices and each of those partitioned, the last block device sdf has apparently 1.5 GB of unpartitioned space :/ what a waist!
What are you thoughts on the matter?
Code:
sda 57.940.115.456 55.256,00
sda1 8.192 ssd 0,01
sda2 33.554.432 persist 32,00 /persist
sda3 268.435.456 cache 256,00 /cache
sda4 1.048.576 misc 1,00
sda5 524.288 keystore 0,50
sda6 131.072 devcfg 0,13 /devcfg.mb
sda7 131.072 devcfgbak 0,13 /devcfg.mb
sda8 524.288 frp 0,50
sda9 10.485.760 oem_dycnvbk 10,00
sda10 10.485.760 oem_stanvbk 10,00 /static_nvbk.bin
sda11 1.048.576 param 1,00
sda12 8.290.304 reserve1 7,91
sda13 16.580.608 reserve2 15,81
sda14 524.288 config 0,50
sda15 57.588.297.728 userdata 54.920,48 /data
0
sdb 4.194.304 4,00
sdb1 4.149.248 xbl 3,96 /xbl.elf
0,04
sdc 4.194.304 4,00
sdc1 4.149.248 xblbak 3,96 /xbl.elf
0,04
sdd 134.217.728 128,00
sdd1 32.768 reserve 0,03
sdd2 4.096 cdt 0,00
sdd3 1.048.576 ddr 1,00
126,96
sde 4.294.967.296 4.096,00
sde1 524.288 rpm 0,50 /rpm.mbn
sde2 524.288 rpmbak 0,50 /rpm.mbn
sde3 2.097.152 tz 2,00 /tz.mbn
sde4 2.097.152 tzbak 2,00 /tz.mbn
sde5 524.288 hyp 0,50 /hyp.mbn
sde6 524.288 hypbak 0,50 /hyp.mbn
sde7 2.097.152 fsg 2,00
sde8 16.384 sec 0,02
sde9 524.288 pmic 0,50 /pmic.elf
sde10 524.288 pmicbak 0,50 /pmic.elf
sde11 99.614.720 modem 95,00 /firmware /NON-HLOS.bin
sde12 16.777.216 dsp 16,00 /dsp /adspso.bin
sde13 1.048.576 dip 1,00
sde14 33.554.432 mdtp 32,00
sde15 8.388.608 abootbak 8,00 /emmc_appsboot.mbn
sde16 8.388.608 aboot 8,00 /emmc_appsboot.mbn
sde17 16.777.216 LOGO 16,00
sde18 67.108.864 boot 64,00 /boot.img
sde19 67.108.864 boot_aging 64,00
sde20 3.154.116.608 system 3.008,00 /system
sde21 67.108.864 recovery 64,00 /recovery.img
sde22 4.096 devinfo 0,00
sde23 1.048.576 bluetooth 1,00 /bt_firmware /BTFM.bin
sde24 524.288 keymaster 0,50 /keymaster.mbn
sde25 524.288 keymasterbak 0,50 /keymaster.mbn
sde26 262.144 cmnlib 0,25 /cmnlib.mbn
sde27 262.144 cmnlibbak 0,25 /cmnlib.mbn
sde28 262.144 cmnlib64 0,25 /cmnlib64.mbn
sde29 262.144 cmnlib64bak 0,25 /cmnlib64.mbn
sde30 262.144 apdp 0,25
sde31 262.144 msadp 0,25
sde32 4.096 dpo 0,00
sde33 34.226.176 splash 32,64
sde34 2.097.152 sti 2,00
673
sdf 1.610.612.736 1.536,00
sdf1 2.097.152 modemst1 2,00
sdf2 2.097.152 modemst2 2,00
sdf3 4.096 fsc 0,00
sdf4 524.288 md5 0,50
1.531,50
63.988.301.824
the nexus 5 has marshmallow on a 1gb /system, I think 3gb in OP3 will be fine especially since there's still empty space in it now.
My thoughts are that this is in the wrong section
Best Regards,
Taker
Taker18 said:
My thoughts are that this is in the wrong section
Click to expand...
Click to collapse
And which one would be the right one?
Also does anyone here know what what all this different small partitions do?
for example what is boot_aging apparently its some sort of boot image but its needier a backup of boot.img nor of the recovery.
I also wonder why xbl is so important to have the backup xblbak located with an own partition table in a separated flash section?
Q and A section evidently this has nothing to do with dev
And frankly don't begin to mess with partitions, nothing good can come up from this.
Well, isn't understanding the partitions not part of development? IMHO one could learn something useful out of that.
Development is programming. Building Rom and kernels.
This isn't dev add you don't propose anything related to a script, a program. You're just asking.
You can not program without understanding how the underlying system works. Respectively the better you understand the system the more you can get out of the hardware, for example here: http://forum.xda-developers.com/optimus-4x-hd/development/rom-mahdi-rom-2-7-unofficial-beta-t2867590 this ROM apparently exploits a existing but unused partition of the p880 to add a new encryption feature which was not present in the stock OS.
Given how many partitions and unused space the OP3 has I'm sure someone can come up with a nice feature to exploit them. Possibly for a different approach on multi boot or may be some virtualization 1 Gig of space is more than enough for a hyper-visor.
> You're just asking.
Nope I'm finding out stuff and trying to find out more stuff....
I looked into the binaries and found something worrisome in XBL partitions contained in the 2nd and 3rd block device:
Code:
##This flag enables booting to UEFI Shell on LA devices.
##This UEFI in the current form should not be used for
##retail purpose. Fuse check will be added to avoid any
##possible security implications.
Also I'm wondering what the boot_aging partition does, apparently its some sort of boot image. But its needier a backup of the kernel (boot.img) nor of the recovery, I wonder what it is...
I'm not discussing that. It belongs to Q&A until a practical thing comes up, then it can be in dev section.
So a sub forum called: OnePlus 3 ROMs, Kernels, Recoveries, & Other Development
is not intended to talk about development, that's so odd.
What sub forum than is intended to talk about source and hardware and boot loaders on a nun user level?
@DavidXanatos
No offense, Sir... but I guess OnePlus 3 ROMs, Kernels, Recoveries, & Other Development is more for like releases and stuff made by devs.
Maybe your thread belongs in OnePlus 3 Guides, News, & Discussion where you can discuss hat topic and find out stuff, as there are other threads a bit like yours.
Maybe ask a mod to move your thread? Just a suggestion.
Striatum_bdr said:
I'm not discussing that. It belongs to Q&A until a practical thing comes up, then it can be in dev section.
Click to expand...
Click to collapse
This thread does not belong in Q&A either. General maybe, but development could be right if it's about adding more space to /system.
I think debating on whether this thread should be in QA section or Dev section why not keep this decision on moderator.
why not just provide proper answer ( of course, if you know ).
I agree this question is more suited in QA section but i think this question can be asked in Dev section because it's very closely related to development.
Hello,
I've moved it to Guides, New, Discussion, please discuss away.
This where it will reside unless someone comes up with a compelling argument as to why it belongs in "Other Development". I don't really believe it does.
Also please be civil to each other.
Cheers Sloth
I think a practical case has come up with OOS 9.0.3 with no space left in partition. Adblock and Ifont are not able to write files. Please suggest
-Amateur Dev
Delete play music and play movies from system partition. Should free up enough space for our mods.