As the title says, I gets notifications almost daily that I have limited space left on my internal storage, and it seems to be getting worse, no matter how many apps I delete or photos I get rid of. I have a GT-I9505 running the 5.0.1 GPE ROM. Does anyone know how I can fix this? I cant move the apps to my SD card either. This is from my phone.
{
"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"
}
What recovery are you using?
Philz Touch I believe.
There's your problem. Philz and Clockworkmod both write protect the portion of internal storage where the nandroid images are stored due to the fact those two recoveries make incremental backups. To resolve the issue, do the following.
1. Download TWRP 2.8.7.2 from the Optimized CM12.1 thread in I9505 Original Android Development and place it in your internal storage.
1. Go into Philz and delete all nandroid backups. Philz nandroid backups aren't compatible with TWRP.
2. Go into the nandroid menu and free all unused space. This will restore the missing storage space.
4. Flash the recovery you downloaded in step 1.
5. Reboot into TWRP.
6. Make a new nandroid backup.
The reason I mention switching to TWRP is that TWRP doesn't make incremental backups like Philz and Clockwork mod, and therefore doesn't need to write protect the nandroid backup storage space. Also, some ROMs will not install with Philz or Clockworkmod installed, so switching to TWRP is a good idea.
Strephon Alkhalikoi said:
There's your problem. Philz and Clockworkmod both write protect the portion of internal storage where the nandroid images are stored due to the fact those two recoveries make incremental backups. To resolve the issue, do the following.
1. Download TWRP 2.8.7.2 from the Optimized CM12.1 thread in I9505 Original Android Development and place it in your internal storage.
1. Go into Philz and delete all nandroid backups. Philz nandroid backups aren't compatible with TWRP.
2. Go into the nandroid menu and free all unused space. This will restore the missing storage space.
4. Flash the recovery you downloaded in step 1.
5. Reboot into TWRP.
6. Make a new nandroid backup.
The reason I mention switching to TWRP is that TWRP doesn't make incremental backups like Philz and Clockwork mod, and therefore doesn't need to write protect the nandroid backup storage space. Also, some ROMs will not install with Philz or Clockworkmod installed, so switching to TWRP is a good idea.
Click to expand...
Click to collapse
When you say go into the nandroid menu and free all unused space, is this still on philz? I used that option on philz and flashed the recovery, hopefully that works!
Edit: Having trouble flashing TWRP on using Odin. I downloaded TWRP from where you said, but it cant load onto Odin as it doesnt have the right file type?
The copy of TWRP is a flashable zip. Flash it using Philz, or extract the image file from the zip and flash it through Odin. And yes, freeing all unused space applies to both Philz and Clockworkmod.
Strephon Alkhalikoi said:
The copy of TWRP is a flashable zip. Flash it using Philz, or extract the image file from the zip and flash it through Odin. And yes, freeing all unused space applies to both Philz and Clockworkmod.
Click to expand...
Click to collapse
That did the trick, I think! Thanks a lot. I ended up wiping cache, Dalvik and internal storage for a complete new build. will make a backup once I have everything back to normal.
Related
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
k1ng0fqu33n5 said:
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
Click to expand...
Click to collapse
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
TheSproker said:
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
Click to expand...
Click to collapse
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
k1ng0fqu33n5 said:
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
Click to expand...
Click to collapse
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
TheSproker said:
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
Click to expand...
Click to collapse
If i do a factory reset with TWRP, will it wipe any of the internal data? (pictures, messages etc.)
because the factory reset screen says that it's not included:
{
"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"
}
Well, i just tried a factory reset and that fails too. Unable to mount /data.
k1ng0fqu33n5 said:
Well, i just tried a factory reset and that fails too. Unable to mount /data.
Click to expand...
Click to collapse
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
EasyAndroidPro said:
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
Click to expand...
Click to collapse
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
k1ng0fqu33n5 said:
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
Click to expand...
Click to collapse
I see.. if that file did not fix the bootlooping then I'm afraid the only fix is like the previous poster said
Either flash stock again with Odin
Or format data in twrp
Ok, i somehow made it so the phone booted up and initialized. Now i got the problem that the google play store keeps crashing.
Edit: I also can't download my whatsapp backup data (says insufficient storage, which is not the case)
I also can't download files with the chrome browser (it says no sd-card found). If i use the stock samsung browser it works though.
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
remus1101 said:
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
Click to expand...
Click to collapse
I've had problems with Aroma installers and TWRP abode the last 2.x.
Regarding system, try to format it via TWRP.
I know there are issues with Aroma installer. LineageOs does not require it so I think this is not the problem. Anyway I used TWRP 2.3 but I have the same problem. Installing process does not success.
{
"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"
}
Inviato dal mio SM-G900F utilizzando Tapatalk
remus1101 said:
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
Click to expand...
Click to collapse
TWRP getting a fail on mounting the system partition is strange. So I suggest you re-flash a stock samsung rom first and make sure it is working properly. Meaning it boots up ok and does not hang / freeze whatever during a good few minutes of use (maybe 15 min or so).
Then I would flash the img.tar of TWRP 3.0.2-0 from here. That is the version I use. It works just fine (with aroma too). Reboot to recovery and go from there.
Thanks for your response.
After a system wipe the mounting fail is gone.
I already flashed the stock ROM with Odin and it works fine. Then trying to install lineage from recovery (making the for wipes) I got the same results.
So I decided to flash a ported ROM (that uses Aroma installer) and installation was fully functional.
So I think this problem shows up only with LineageOs and also RR.
Is it possible that there are still some files from a previous installation of LO that cause a conflict and make the installation just not to continue?[emoji28]
Hello all,
I recently bought a brand-new ZE552KL and have since unlocked the bootloader, flashed TWRP 3.2.1, flashed ViperOS 7.1.2, flashed Magisk 15.3, flashed Xposed v89r5-v90b2, and made several backups. However, each time I restore one, I lose all progress in the most evil manner I've encountered to date: Any time I try to back up my install after restoring from a backup, it fails, claiming my system partition is only 7MB in size.
Now, at first I thought this was simply a bug in the latest TWRP- 3.2.1 is so new, after all- so I flashed back to 3.1.1, reflashed ROM/GApps, went through first boot, and began making backups as normal. Only, when I tested one of them by restoring, booting to system, changing things, booting back into recovery, and attempting to back up, well, you guessed it... 7MB system partition. I have no idea what's causing this, but it kinda invalidates the point of having backups in the first place. Any help would be appreciated.
Hi, i never find a solution for backup / restore with TWRP. Always doing all from begining.
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?
auroraPLG said:
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?
Click to expand...
Click to collapse
Try to flash twrp 3.1.1 (20171023) from here https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA
[email protected]@ said:
Try to flash twrp 3.1.1 (20171023) from here
Click to expand...
Click to collapse
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Code:
Restoring Data (excl. storage)...
extractTarFork() process ended with ERROR: 255
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?
auroraPLG said:
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?
Click to expand...
Click to collapse
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?
[email protected]@ said:
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?
Click to expand...
Click to collapse
1. No. No bootloop. I don't understand where you got this idea. As I said, old TWRP failed to restore Data. However, I'm pretty sure it was the Data partitions in my latest backups, due to making files immutable- not the recovery itself.
2. No, I want to restore ViperOS.
wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Hi, this is the right configuration for a backup ?
Please confirm me
{
"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"
}
Picture from howtogeek.com
@dekson9
Yes, that is the correct. System partition is the OS, and the data partition is your apps and config data.
So, when you make a backup, can you confirm the size of the backup files, should be something like system.ext4.win000, 001, 002.
Maybe try unmounting and remounting the system partition while in twrp before the restore? You can toggle the button at the bottom right (4 horizontal lines) to see if there were any errors.
wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Well, I tried it your way. Not gonna lie, I don't understand why a full backup would cause that problem. But it turns out you're right. I've gotten that kink worked out thanks to you. Now if I could just fix the hardware clock... but that's another adventure for another party, I'm sure. I'm off to press that thanks button.
@auroraPLG
Glad you got it sorted, happy flashing!
@wang1chung
Thank you! I think I'm gonna play around with backups and pull logs and see if I can't figure out what causes this particular bug.
{
"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"
}
This guide is for your twrp to recognize your internal memory and the available memory that is in it since we all face this problem that presents twrp in internal storage.
Warning: This procedure will erase all the data of your device such as google accounts, messages, root, that is to say it will remain factory mode, so you will need to reconfigure the device, I add images of the steps so that it is as comprehensible as possible to understand.
When you install twrp and start it for the first time we will get the following information we just need to confirm the action Swipe to Allow Modifications.
So we visualize the following menu with the options offered by twrp, we will only focus on the option Wipe.
We choose the option Advanced Wipe.
Check the Data box and we choose the option Repair or Change File System
We choose the option Change File System
We choose the option EXT4
We choose the option Swipe to Change, When confirming the action your device will erase all your data stored in the internal storage
Twrp will recognize your internal storage and capacity
Warning: You must re-flash Drm-fix.zip. magisk.zip to be root on your device
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
omaison said:
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
Click to expand...
Click to collapse
No you have do it again after fresh installation
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
omaison said:
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
Click to expand...
Click to collapse
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
awadnisar said:
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
Click to expand...
Click to collapse
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
omaison said:
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
Click to expand...
Click to collapse
Means updating OmniROM is wiping data partition?
awadnisar said:
Means updating OmniROM is wiping data partition?
Click to expand...
Click to collapse
Not automatically. But it seems that I don't have the choice to format it manually to have the possibility to flash the new version of the ROM.
Otherwise TWRP generate an error with saying that the data partition is encrypted.
I will try again on the next week when the new version of the OmniIROM is released.
redundant
I was debloating my phone and some deleted wrong file in the system. And now when I restored System using Skyhawk TWRP Recovery my phone got stuck into a bootloop. I had to flash the ROM again and got all the bloatware back.
Is there any way to get this fixed? None of the tutorials have helped me so far.
Hello, Have you seen this?
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Buckythereporter said:
I was debloating my phone and some deleted wrong file in the system. And now when I restored System using Skyhawk TWRP Recovery my phone got stuck into a bootloop. I had to flash the ROM again and got all the bloatware back.
Is there any way to get this fixed? None of the tutorials have helped me so far.
Click to expand...
Click to collapse
Use TWRP / OrangeFox in the future. I recommended TWRP but I use OrangeFox because of password protection feature.
sercari said:
Hello, Have you seen this?
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Click to expand...
Click to collapse
I have everything working right now. But the phone goes into a bootloop if I restore the System. I used to just flash the rom again if something goes wrong. This was the first time I tried to restore a system backup.
Recovering Data partition works properly tho.
KineSight said:
Use TWRP / OrangeFox in the future. I recommended TWRP but I use OrangeFox because of password protection feature.
Click to expand...
Click to collapse
Does the backup and restore feature work for you? Do I need to flash something else to restore the System?
Buckythereporter said:
Does the backup and restore feature work for you? Do I need to flash something else to restore the System?
Click to expand...
Click to collapse
Yes. Backup's and Restore's work perfectly for me. I highly doubt either one can restore the other's backup data. (Yes, OF is based on TWRP.)
KineSight said:
Yes. Backup's and Restore's work perfectly for me. I highly doubt either one can restore the other's backup data. (Yes, OF is based on TWRP.)
Click to expand...
Click to collapse
So no one fixed this even in modded recoveries. Maybe they didn't face any issue and it's only my phone.
Just found this guide here, trying this.
Backup and Restore - a Hybrid Method (Android 9) | XDA Developers Forums (xda-developers.com)
restoring system.img is not recommend since it might trigger dm-verity. they say it better to flash the full stock rom
ineedroot69 said:
restoring system.img is not recommend since it might trigger dm-verity. they say it better to flash the full stock rom
Click to expand...
Click to collapse
Doesn't flashing a GSI do the same?
Buckythereporter said:
Doesn't flashing a GSI do the same?
Click to expand...
Click to collapse
here's the list of partition that is supposed to be dm-verity protected https://source.android.com/security/verifiedboot
"to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions"
my phone has already dm-verity trigger i don't see much difference except i need to deal with 2 boot animation on start lmao
{
"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"
}
ineedroot69 said:
here's the list of partition that is supposed to be dm-verity protected https://source.android.com/security/verifiedboot
"to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions"
my phone has already dm-verity trigger i don't see much difference except i need to deal with 2 boot animation on start lmao
Click to expand...
Click to collapse
Seems like there's no permanent solution for this. Buying Mi next time.
Buckythereporter said:
Seems like there's no permanent solution for this. Buying Mi next time.
Click to expand...
Click to collapse
if you can start twrp get dmesg.log upload that file see if we can help you.