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.
Related
I don't understand 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"
}
(IMG tag doesn't seem to work so see this link instead) https://lh5.googleusercontent.com/-...9bQ3HKvY/s800/possible%20Android%20bug-01.png
If you look at the image above, my sgy-data (fat32) partition totals 843.8MB but the system reports 928.4MB used. Where did the 84.6MB go? Now that's ignorable…
But for my sgy-ext (ext3) partition that is linkd with link2sd, the total size of all the files is 246.7MB but the system reports 686.6MB used. A total of 439.9MB is missing! And that is not ignorable anymore.
In fact, if you look at the second image, according to link2sd, my sgy-ext partition is using up 601MB (as compared to 686.6MB reported by Linux, a difference of 85.6MB still in the range of 'ignorable' missing space).
(IMG tag doesn't seem to work so see this link instead) https://lh5.googleusercontent.com/-...Kh4pphYo/s800/possible%20Android%20bug-02.png
My questions are:
1) What's happening? and Why?
2) What's with Android OS as compared to Linux? Or putting it another way, why can't Linux see what Android 'supposedly' sees? Assuming that Android is seeing something that Linux can't, which could explain the missing MBs.
3) If it isn't normal at all, what is the best way to reclaim those missing MBs without resetting and starting from scratch? This is like the last resort if all else fails (although I don't mind since for some weird reason, everytime I plug-in my SGY to Linux, it reboots automatically).
Other info:
1) Using stock ROM
2) Using LA1
3) Samsung Galaxy Y
4) Rooted
5) I use Link2SD
6) regular SD card partition is FAT32
7) SD card partition for Link2SD is ext3
8) and a little bit of story, see next:
I rebooted after installing an app yesterday, and for some weird reason all of the installed apps that exists in Link2SD partition disappeared even though the said partition was mounted properly. I checked Link2SD and yes, it was mounted at boot, Link2SD can read the said partition. However, this is where it starts to get weird - Link2SD can not see any of the apps.
When I check the storage via Link2SD's, it reports that I have "used" space in the partition. True enough, the apps were not deleted, it was just that, Link2SD or maybe the phone itself failed to read those apps. Could this be a Link2SD bug and not Android related?
I tried rebooting, remounting, soft restart, all to no avail. I ended up reinstalling everything. Then trying the relink lib and relink cache. Some successfully relinked, the rest did not.
Then rebooted to see if anything changed. Works fine. However nothing changed. Finally I cleared the "trash", those files that lost its connection to its respective apps (via Link2SD's options). Nope nothing, because as Link2SD reported, these trash files have a total of 0kB! All empty files.
I rebooted once more. And then the problem repeated again. Then I rebooted again, and the problem stopped… finally.
However, the missing space are still there.
As you can see in my screenshots above, I have "all hidden files shown" enabled. The total size of all files is too low compared to the "used" size, which I can not reconcile anyway I looked at it.
And that's where I need help or an explanation… Android, Link2SD, possible bug?
Or is this another case of base-10 and base-2 space naming? My Linux OS uses base-10, is Android and Link2SD using base-2? (ie MB vs. MiB)
Thank you very much.
Same Problem have you found a solution?
I am having this same problem now... except I'm missing 1.90GB after a botched install and i know it's there on the sd cause link2sd is showing that it's being used even though I haven't linked anything to it yet after a fresh install of everything even wiping my sd and recreating the fat32 and the ext2 the missing GB are still gone.
Has anyone figured out what is happening or how we can get it back?
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!
Why share it :
I wrote this for my own MediaTek device because there were no EBR with 32GB internal storage nor there is any tool to achieve the goal.
How it works :
The program is simple as entering how much of space you need in your internal storage. The tool also let you know current size of your EBR partition size.
Why no full tutorial :
If you didn't know, there is also some tutorial on this forum to replace your EBR files. That's why I'm not discussing more off-topic.
Ok, I'm willing to use this tool :
Download and unzip the attachment and COPY your original EBR1/EBR2 files inside program folder and then start it.
Screenshot :
{
"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've had to edit EBR files on my old MTK phone, I just got another a couple of weeks ago. Old phone had phone 4GB phone memory, .99GB (internal storag) allocated for apps and the remaining was called phone storage. I was able to get 2.5GB to work on the 4GB phone. Funny thing, new phone is supposed to have 16GB phone memory, it also came with a very same space for apps, only .99 or .98 GB. I was able to experiment using your script, I was initially tried 12GB, everything seemed to sync up okay, but then after one day, services started to stop. I went back to 6GB and everything seems okay. One curious thing with my new phone, if I define 6GB or 12GB for the internal storage, the phone storage never changes. The phone is Cubot S308 with MTK6582 processor.
New revision EBR-Editor 1.0a
Small improvements
- Small comsetic changes
- Overwrite backup file by default
https://mega.co.nz/#!PAATzCwC!kBhIFpyTjwMlMecOYfVPsjghEGbVw0E_GRy3EYhsHts
bovirus said:
New revision EBR-Editor 1.0a
Small improvements
- Small comsetic changes
- Overwrite backup file by default
https://mega.co.nz/#!PAATzCwC!kBhIFpyTjwMlMecOYfVPsjghEGbVw0E_GRy3EYhsHts
Click to expand...
Click to collapse
No more manual resizing!! Thanks bro :highfive:
Any way to resize the system partiton? Also your tool shows my current storage is 1gb, which is false, its actually 2gb. Whats up with that?
@-iHackerz-
Wht do you need to resize system partition?
Thank you very much
A million thanks for you...
I searched all over the internet for repartitioning my A210 and ended up in softbricking it...
I just thought I would end up being a noob....
With your EBR editor and a little knowledge about SP Flash Tools, I just achieved 7.37GB (created as 7.5GB using your editor and was 2.5GB before) of apps storage and 5.01GB of Internal Storage from my 16GB internal storage.
I already own a 32GB SD and so there is no space problem for me now.
I don't have any more words to thank you.
I really never thought that i could do this in a day.:angel:
bovirus said:
New revision EBR-Editor 1.0a
Small improvements
- Small comsetic changes
- Overwrite backup file by default
https://mega.co.nz/#!PAATzCwC!kBhIFpyTjwMlMecOYfVPsjghEGbVw0E_GRy3EYhsHts
Click to expand...
Click to collapse
Link is dead. Can you reupload?
I suggest a (newer & more powerfull) alternative
EBR Changer by becar - http://www.needrom.com/download/ebr-changer/
-iHackerz- said:
Any way to resize the system partiton? Also your tool shows my current storage is 1gb, which is false, its actually 2gb. Whats up with that?
Click to expand...
Click to collapse
To resize ur system partition u need flash any rom whith SpFlash Tool, modding the sccater.txt file
is the same for recovery, boot, cache, data partitions etc
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!
I've been trying tons of app and software on my pc? I cant seem to find them ? it happened few days ago should be still recoverable right ?? No I normally wouldn't delete anything unless I knew for sure it was backed up too cloud but some reason It wasn't connected or syncing files ugh Its work related idk what to do Please help me TY
Please anyone ??
Not sure how it is on your phone, in the gallery app on my phone, there is a 'Recently deleted' folder. From here, we can recover photos that were accidentally deleted within 30 days. I will upload a screenshot about this later.
{
"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"
}
Ty for reply, and I have the Samsung Galaxy S21 Ultra. And I emptied the recycling on accident because bi thought the files where uploaded to cloud like they usually are but for some reason my syncing got turned off somehow? So the files are completely gone I tried tons apps but allot of them won't go very deep scanning unless I'm rooted
Bump
So nothing can be done ? Im screwed
brianadam78 said:
I've been trying tons of app and software on my pc? I cant seem to find them ? it happened few days ago should be still recoverable right ?? No I normally wouldn't delete anything unless I knew for sure it was backed up too cloud but some reason It wasn't connected or syncing files ugh Its work related idk what to do Please help me TY
Click to expand...
Click to collapse
If you're talking about the mobile phone the best solution would be to root your phone and use DiskDigger.
dedq said:
If you're talking about the mobile phone the best solution would be to root your phone and use DiskDigger.
Click to expand...
Click to collapse
K well I was hoping I didn't have to root it, I won't be able to get OTA updates and use certain apps
brianadam78 said:
K well I was hoping I didn't have to root it, I won't be able to get OTA updates and use certain apps
Click to expand...
Click to collapse
I don't think you will be able to do anything if you don't root your phone.
I will try finding a way to hide the root for the sake of keeping the OTA.
dedq said:
I don't think you will be able to do anything if you don't root your phone.
I will try finding a way to hide the root for the sake of keeping the OTA.
Click to expand...
Click to collapse
Hmm how would I hide root ? And what about the apps that won't work while rooted ?
brianadam78 said:
Hmm how would I hide root ? And what about the apps that won't work while rooted ?
Click to expand...
Click to collapse
I suggest you search something about it on this forum because I haven't been hiding root for a very long time now. I think Magisk can help with that.
When files are wiped / deleted, the corresponding entry in the MFT ( the Master File Table is where a file's name and the chain of allocation units assigned to the file are stored ) is marked as re-useable, though the wiped / deleted files may still be physically present if the freed space has not been overwritten in the meantime.
IMO a forensic software is needed to extract physical content of the wiped / deleted files, will say to do a bitwise copy of this freed storage space Android's dd command typically is used what requires relevant Android's directories are mounted as RW what requires Android is rooted before.
Rooting Android is nothing else than to add su binary to Android's filesystem, preferredably to /data/local/tmp directory, what can get achieved via ADB.