Database Info

[Q] Data.img bigger than 1 GB

I recently installed 4.3 MoKee ROM on my At&t's Atrix 2, System 3. Everything works flawlessly.
I'm a bit concerned about size of data.img partition, It's only 1 GB and BMM didn't allow me a greater size.
Is there any way to resize Data.img partition, to make it capable for more apps to be installed? 1 GB sooner or later will be an insufficient space.
Tnx in advance!

I have the same problem, but with PA. I'd love to see a solution.
Sent from my MB865 using XDA Premium 4 mobile app

iNitrox said:
I recently installed 4.3 MoKee ROM on my At&t's Atrix 2, System 3. Everything works flawlessly.
I'm a bit concerned about size of data.img partition, It's only 1 GB and BMM didn't allow me a greater size.
Is there any way to resize Data.img partition, to make it capable for more apps to be installed? 1 GB sooner or later will be an insufficient space.
Tnx in advance!
Click to expand...
Click to collapse
There is a 2000 mb option when u enter BMM click on it make sure u don't have too many systems coz there won't be enough space in the ROM...
Here is a screen shot .......
{
"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"
}
Doesn't seem to be a problem for me ................
Just see if ur BMM recovery version is the same as mine 0.3.4..........

darth_nihar said:
There is a 2000 mb option when u enter BMM click on it make sure u don't have too many systems coz there won't be enough space in the ROM...
Here is a screen shot .......
Doesn't seem to be a problem for me ................
Just see if ur BMM recovery version is the same as mine 0.3.4..........
Click to expand...
Click to collapse
Thanks darth_nihar!, in my case, when i try to create the 2000 mb partition for data.img, this is shown:
This will take some time
(fat32 don't support sparse file)
-
Allocating disk space to image file..
Then, nothing more happens
I'm using System 3, all system/cache/data partitions are destroyed in System 4, 5, and 6.
System 2 is already 'activated'. BMM is v0.3.4
What I am doing wrong? Please help me!

iNitrox said:
Thanks darth_nihar!, in my case, when i try to create the 2000 mb partition for data.img, this is shown:
This will take some time
(fat32 don't support sparse file)
-
Allocating disk space to image file..
Then, nothing more happens
I'm using System 3, all system/cache/data partitions are destroyed in System 4, 5, and 6.
System 2 is already 'activated'. BMM is v0.3.4
What I am doing wrong? Please help me!
Click to expand...
Click to collapse
Same exact problem. Something I found at least helps conserve space is I moved all the apps that I could to my SD card. This saved me about 500 mb of space, so like half.
Sent from my MB865 using XDA Premium 4 mobile app

CreativeSin said:
Same exact problem. Something I found at least helps conserve space is I moved all the apps that I could to my SD card. This saved me about 500 mb of space, so like half.
Click to expand...
Click to collapse
I think that there must be a solution for our problem,
Maybe we need install an earlier version of BMM,
or install those Roms on System 1 (I tried this but didn't work)
I hope somebody may help us!

[Q] Why Just 1Gb Of Data Partition?

Hi Guys! I know this is a question that many of you wondered, if in specs sensation is mentioned with four Gigabytes why we just got one?
I used Z test and search for memory on it, and look a this
{
"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"
}
I wanna anybody explain me this. Seriously. What are those 2.25 Gigabytes doing there? Nothing, are not sytstem storage, are not cache partition, then, what that? I'd appreciate know it and another question, is there any tool or method to get this space into data partition?
ATTACHED THUMBNAILS

migui0401 said:
Hi Guys! I know this is a question that many of you wondered, if in specs sensation is mentioned with four Gigabytes why we just got one?
I used Z test and search for memory on it, and look a this
I wanna anybody explain me this. Seriously. What are those 2.25 Gigabytes doing there? Nothing, are not sytstem storage, are not cache partition, then, what that? I'd appreciate know it and another question, is there any tool or method to get this space into data partition?
ATTACHED THUMBNAILS
Click to expand...
Click to collapse
2.25GB is devided by data,system,cache some other minor partitions..That app just sums them up in a stupid way.
Just forget about it, you got what you got and there is no way for you to change it!

ivicask said:
2.25GB is devided by data,system,cache some other minor partitions..That app just sums them up in a stupid way.
Just forget about it, you got what you got and there is no way for you to change it!
Click to expand...
Click to collapse
Is not just this app, i've seen it by other ways and that is not just data, sytem and cache partition. There are some others partition that app doesnt show apart of those 128 and 256 megabytes, if that MBs where doing something i would care about but are lost doing nothing.

migui0401 said:
Is not just this app, i've seen it by other ways and that is not just data, sytem and cache partition. There are some others partition that app doesnt show apart of those 128 and 256 megabytes, if that MBs where doing something i would care about but are lost doing nothing.
Click to expand...
Click to collapse
if i remember well there is a fastboot command which shows you all partitions and their sizes
some partitions are completely empty

rzr86 said:
if i remember well there is a fastboot command which shows you all partitions and their sizes
some partitions are completely empty
Click to expand...
Click to collapse
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.

migui0401 said:
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
Click to expand...
Click to collapse
AFAIK we can't repartition emmc as we want
i think it is impossible

migui0401 said:
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
Click to expand...
Click to collapse
There is NO space lost, those are "fake" partitions, just kernel mount points, try running same command when phone is not booted from recovery and it will show you real stats, also regardless of all of this we CANT re-partition Sensations nand even if we wanted...So discussion is pointless.

question about backup true twrp

Stupid question,
I normally use root essentials to make a system backup but I think with op6 it will not backup al the required files anymore I think.
So I want to make the backup true twrp but can someone list the files to backup. As there are also vendor partition listed. So please let me know what to backup exactly to make the correct backup.
Thanks in advance.
Regards ysco..

Bump,
Anyone?

I think you need to backup all partitions.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546

Bradden1 said:
I think you need to backup all partitions.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546
Click to expand...
Click to collapse
For a successful nandroid you need following partitions:
boot
system image
vendor image (not sure, if image is really needed, haven´t tested) yet
data
Separately an efs-backup is highly recommended which should be copied to an external storage.

Flying Fox said:
For a successful nandroid you need following partitions:
boot
system image
vendor image (not sure, if image is really needed, haven´t tested) yet
data
Separately an efs-backup is highly recommended which should be copied to an external storage.
Click to expand...
Click to collapse
ysco said:
Stupid question,
I normally use root essentials to make a system backup but I think with op6 it will not backup al the required files anymore I think.
So I want to make the backup true twrp but can someone list the files to backup. As there are also vendor partition listed. So please let me know what to backup exactly to make the correct backup.
Thanks in advance.
Regards ysco..
Click to expand...
Click to collapse
the reply is not correct you explicitly don't need exactly those two image partitions to backup because they remain stock intact at all times, they only make your backup huge, up to 14GB instead of only 7-9GB once unchecking them.
of course as always you HAVE TO backup system and vendor, just not the system and vendor images, they serve to keep a clean stock
system available to recover from a soft brick, you can test that by re-locking and re-unlocking the bootloader and/or by formating all partitions
including user data on both slots. it will boot directly into a clean system (setup wizzard) like on first unboxing and this what you boot into then is exactly vendor and system image which remains untouched no matter what you do (except intentionally killing everything with brute force which is not even so easy)
{
"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"
}
i shall attach a screenshot to illustrate and much more important ist that if you ever opened parallel apps settings you'd have to delete all
999 folders in root > data > (all 3 misc + all 3 system + both user) folders else you get a 255 error.

Thank you.. i did wonder whether backing up image files was the right way.

magnamentis said:
the reply is not correct you explicitly don't need exactly those two image partitions to backup because they remain stock intact at all times, they only make your backup huge, up to 14GB instead of only 7-9GB once unchecking them.
of course as always you HAVE TO backup system and vendor, just not the system and vendor images, they serve to keep a clean stock
system available to recover from a soft brick, you can test that by re-locking and re-unlocking the bootloader and/or by formating all partitions
including user data on both slots. it will boot directly into a clean system (setup wizzard) like on first unboxing and this what you boot into then is exactly vendor and system image which remains untouched no matter what you do (except intentionally killing everything with brute force which is not even so easy)
i shall attach a screenshot to illustrate and much more important ist that if you ever opened parallel apps settings you'd have to delete all
999 folders in root > data > (all 3 misc + all 3 system + both user) folders else you get a 255 error.
Click to expand...
Click to collapse
That's absolutely correct. I was not precise enough in my post. I recommend a backup of the system image, at least I do it so, because I can not know in advance, whether later a factory set or a clean install will be necessary. So it does not bother me that the backup is a bit bigger then. It does not hurt and costs nothing.
As I said, the thing is, if I wipe system, then I need to flash it again if I did not back up system image - that's my experience.
Or am I wrong; I like to be corrected, especially your knowledge interests me.

magnamentis said:
the reply is not correct you explicitly don't need exactly those two image partitions to backup because they remain stock intact at all times, they only make your backup huge, up to 14GB instead of only 7-9GB once unchecking them.
of course as always you HAVE TO backup system and vendor, just not the system and vendor images, they serve to keep a clean stock
system available to recover from a soft brick, you can test that by re-locking and re-unlocking the bootloader and/or by formating all partitions
including user data on both slots. it will boot directly into a clean system (setup wizzard) like on first unboxing and this what you boot into then is exactly vendor and system image which remains untouched no matter what you do (except intentionally killing everything with brute force which is not even so easy)
i shall attach a screenshot to illustrate and much more important ist that if you ever opened parallel apps settings you'd have to delete all
999 folders in root > data > (all 3 misc + all 3 system + both user) folders else you get a 255 error.
Click to expand...
Click to collapse
why i can not find 999 folders from root ? even i have opened parallel apps

Question Leave data unencrypted

Hello! Is there any possibility now to leave data partition unencrypted?
Tried to install miui.eu with PBRB with dfe toggles enabled - no result.
Tried to install same through TWRP + latest dfe - no result
Tried to install havoc treble + dfe - no result.
Am I missing something?
UPD
I've created DFE patch for 12.0.6.0 xiaomi.eu firmware
Original firmware is hosted here
xiaomi.eu_multi_POCOX3Pro_V12.0.6.0.RJUMIXM_v12-11.zip | by Xiaomi.eu for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Patch is here.
Яндекс
Найдётся всё
disk.yandex.ru
You should replace files in original firmware with files from patch and flash it through recovery
I also flashed latest DFE(may be not beeded)
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
And latest stable magisk(may be also not needed)

If your data partition is encrypted right now, you have to format it first, then flash DFE to prevent encryption. I'm guessing that's what you did?

kamild_ said:
If your data partition is encrypted right now, you have to format it first, then flash DFE to prevent encryption. I'm guessing that's what you did?
Click to expand...
Click to collapse
Yes, i did it and it was not helpfull. Seems that i've found something. Looks like I should repack vendor image with patched fstab.qcom and then reflash it through fastbootd. Because of superimage dfe patch cannot replace this file(vendor is RO even in recovery mode)
For now i've found this project, seems exactly what I need
®Unpacker Kitchen for Android(UKA). - 4PDA
®Unpacker Kitchen for Android(UKA)., Перепаковка и монтирование образов на телефоне.
4pda.ru

Aaaaand I've done it. Works perfectly. Now uploading

What's the pros of leaving data unencrypted?

Do we have to do this unpacking and repacking process for every new version of stock ROM?

qwert8988 said:
What's the pros of leaving data unencrypted?
Click to expand...
Click to collapse
The only real benefit I know of is being able to switch between different ROMs without having to format data - it would still be recommended to wipe it, but you would be able to preserve your internal storage between ROMs.
Theoretically there's also some performance that you could reclaim by getting rid of encryption, but on such powerful SoC any gains would not be noticable maybe outside of benchmarks.

qwert8988 said:
What's the pros of leaving data unencrypted?
Click to expand...
Click to collapse
Minor CPU performance and NAND lifetime gain. Also if you somehow clear contents of /metadata partition - you will loose all of your files on /data partition ( and internal sd as /data/media too).
Also several years earlier days I've faced a problem when new firmware can't decrypt data after previous one(it was in lolipop times as I can remember). So, if I can preserve /data unencrypted - I'll try to do so.
qwert8988 said:
Do we have to do this unpacking and repacking process for every new version of stock ROM?
Click to expand...
Click to collapse
Seems yes, at least for now. Not for every rom, just for vendor part.
You can apply this patch to any rom based on 12.0.6.0 vendor. You'll only have to edit original dynamic_partitions_op_list file from rom archive - replace "resize vendor" string with
resize vendor 1563119616

Thanks for the work. Confirmed worked on ArrowOS build 2021.05.04. Flashing dfe and masgisk are not necessary

Thanks !!! It works !!! This is what I have been looking for...
{
"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"
}

vodkinagdan said:
Yes, i did it and it was not helpfull. Seems that i've found something. Looks like I should repack vendor image with patched fstab.qcom and then reflash it through fastbootd. Because of superimage dfe patch cannot replace this file(vendor is RO even in recovery mode)
For now i've found this project, seems exactly what I need
®Unpacker Kitchen for Android(UKA). - 4PDA
®Unpacker Kitchen for Android(UKA)., Перепаковка и монтирование образов на телефоне.
4pda.ru
Click to expand...
Click to collapse
So.... To get an unencrypted phone on Android 12 Custom ROMS you still need to flash patched Vendor?
Twrp 3.6 for 12 can't encrypt System/User data.
So to create backups one would need an unencrypted phone. Correct?
To switch between different Android 12 Custom ROMS with Userdata and system ready to flash back.

Haldi4803 said:
So.... To get an unencrypted phone on Android 12 Custom ROMS you still need to flash patched Vendor?
Twrp 3.6 for 12 can't encrypt System/User data.
So to create backups one would need an unencrypted phone. Correct?
To switch between different Android 12 Custom ROMS with Userdata and system ready to flash back.
Click to expand...
Click to collapse
If rom is based on OSS vendor - for android 11 this patch working well now. You can try it on A12

Flashing wrong recovery killed all of my partitions — Help!

Hi all,
I'm going to make a long story short and say that my brother's phone has a cracked screen, so I tried to use TWRP to backup everything through ADB. But googling SM-J530F TWRP brings 'j5lte' as one of the first results, I went and flashed it under the wrong assumption that j5lte was SM-J530F's code name (it was not) and that caused severe bootloops.
I flashed correct TWRP, but USERDATA would not mount. I panicked and the crystal bleeding was progressing fast, so I pulled the entire mmcblk0 to dump a raw image of the phone's NAND.
This was the right move, as the phone is completely dead now. Crystal bleeding has made the screen completely dead, but the phone still works.
All I'm left with is the raw NAND backup.
The first thing I did was inspect the image with fdisk. It can recognize the GPT partition table and structure. The USERDATA partition is at the very end.
{
"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"
}
GDISK is also recognizing it no problem. It seems like the partition table is in good condition:
GPARTED is also recognizing partitions, but it does not look good:
Looking at more information:
For the record, e2fsprogs is installed. It's always installed by default. GPARTED here is complaining about the superblock, but I can see that its looking to open the partition through /dev/loop0p24 which is no good. The kpartx tool is giving me access to all the partitions of the image through /dev/mapper/loop0p24, so that explains the errors.
Superblocks seem to be present in USERDATA:
I tried mounting the partition with a backup superblock, but...
I was at a loss at this point, so I tried mounting the SYSTEM partition just to see what happens and... it worked?
This proves what I said: This partition is fine, GPARTED was complaining simply because its trying to target them through the wrong device path.
But this raised the question: What the heck is wrong with the USERDATA partition? Why is it ext2 (Isn't that SUPER old?) and could it be that its not corrupted at all, and I'm just trying to mount it the wrong way or something? TWRP couldn't mount it though (Why?).
Being at a loss, I tried repairing the ext2 USERDATA partition using `fsck.ext2 /dev/mapper/loop0p24` and it found so many errors (including a corrupted journal) the file I redirected stdout to (console output) ended up being 78MB. Here it is if you want it (obviously can't post here).
So anybody knows what I can do? Is there any hope? I'm positive that the recovery image couldn't have corrupted the USERDATA partition (How could it? I still can't find a possible explanation). And even if it did, it couldn't overwrite the files. The file data should STILL be in that partition completely in-tact (There's NO WAY the recovery image overwrote them) though the journal is gone, so I can't use a tool like extundelete to recover them.
I tried to flash the phone with a stock rom through download mode to reconstruct everything with a healthy structure. This was so I could flash TWRP again and pull another NAND raw dump to have as a healthy reference I could use, but this doesn't work. Odin fails and I don't know why because the screen on the phone is dead.
Is there some place where I could get this maybe?
Is there something you can suggest I do?
Thanks!