Went to do a backup to Ext Card with almost 57GB on it. Chose NORMAL and left only boot, system, data and internal storage (default) checked. Specified Ext card as location. Process appears to start correctly (fast scrolling f files, but I never get the next screen with Flashfire band across the top showing the actual backing up - screen just goes dark except for blue light in upper left corner. It stops at that stage. Never reboots. I have to remove battery to restart, and when I look for the backup there's nothing except a popup that states "no backups found" and "restore from ADB."
Don't want to attempt flashing a new ROM (e.g., Stang5litre) if I can't get it to even backup.
wedmiston said:
Went to do a backup to Ext Card with almost 57GB on it. Chose NORMAL and left only boot, system, data and internal storage (default) checked. Specified Ext card as location. Process appears to start correctly (fast scrolling f files, but I never get the next screen with Flashfire band across the top showing the actual backing up - screen just goes dark except for blue light in upper left corner. It stops at that stage. Never reboots. I have to remove battery to restart, and when I look for the backup there's nothing except a popup that states "no backups found" and "restore from ADB.". Don't want to attempt flashing a new ROM (e.g., Stang5litre) if I can't get it to even backup.
Click to expand...
Click to collapse
Questions, Concerns and Support regarding FlashFire should be posted on the following Official FlashFire thread.
[Android 4.2+][ROOT][2017.04.03] FlashFire v0.57 by Chainfire
Good Luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
wedmiston said:
Went to do a backup to Ext Card with almost 57GB on it. Chose NORMAL and left only boot, system, data and internal storage (default) checked. Specified Ext card as location. Process appears to start correctly (fast scrolling f files, but I never get the next screen with Flashfire band across the top showing the actual backing up - screen just goes dark except for blue light in upper left corner. It stops at that stage. Never reboots. I have to remove battery to restart, and when I look for the backup there's nothing except a popup that states "no backups found" and "restore from ADB."
Don't want to attempt flashing a new ROM (e.g., Stang5litre) if I can't get it to even backup.
Click to expand...
Click to collapse
Make sure you are using FF v.53, the newer versions don't work on this device.
{
"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"
}
Uninstalled v.57 and installed v .53, but now when FF starts it goes through the opening sequence but then nothing. Just my basic home screen and apps as if it shut itself off. No error messages. Just poof! Gone.
Help. The solution you proposed isn't working. See me post previous to this.
wedmiston said:
Uninstalled v.57 and installed v .53, but now when FF starts it goes through the opening sequence but then nothing. Just my basic home screen and apps as if it shut itself off. No error messages. Just poof! Gone.
Click to expand...
Click to collapse
You need to set date and time 01/01/2000 for FlashFire works on older versions...
Related
Just wondering if anybody has had this issue before. I searched around a bit but haven't found a clear answer yet. After flashing a kernel through Kernel Manager Pro, the phone rebooted, checked sdcard as usual, then popped up that there was an error and sdcard was mounted as "read only". I had made a backup right before flashing the kernel like I usually do so I restored that backup but got the same error. I booted into recovery and wiped data and cache and so on and rebooted into android. No luck with that either, so I tried a backup of a different rom I had. Still the same issue (also wiped between restoring backups for good measure). Plugging it into the computer would work because it would not recognize the sdcard as a removable drive (had the "use as disk drive" option chose on my phone to clarify). Finally I had to boot into recovery, mount usb storage, right click on the drive that my phone was, and click "check and fix for errors". After a very long wait it finished and I unmounted usb storage and rebooted into android again. That finally fixed it (whew), and now I have a folder on my sdcard that is titled "FOUND.0000", and there are text files in it with names such as "FOUND.0000CHK, FOUND.0001CHK" and so on. Do I need these files anymore or is just showing me what was wrong and fixed on my sdcard? Will it cause any issues if I delete the folder? Sorry if all this is confusing or stupid. I just have never had an issue like this before and I have rooted and used quite a few android phones and tablets. Im not a noob but I definitely do not know that much about this kind of stuff so any help would be greatly appreciated! TIA
Travis
TMYINC said:
Just wondering if anybody has had this issue before. I searched around a bit but haven't found a clear answer yet. After flashing a kernel through Kernel Manager Pro, the phone rebooted, checked sdcard as usual, then popped up that there was an error and sdcard was mounted as "read only". I had made a backup right before flashing the kernel like I usually do so I restored that backup but got the same error. I booted into recovery and wiped data and cache and so on and rebooted into android. No luck with that either, so I tried a backup of a different rom I had. Still the same issue (also wiped between restoring backups for good measure). Plugging it into the computer would work because it would not recognize the sdcard as a removable drive (had the "use as disk drive" option chose on my phone to clarify). Finally I had to boot into recovery, mount usb storage, right click on the drive that my phone was, and click "check and fix for errors". After a very long wait it finished and I unmounted usb storage and rebooted into android again. That finally fixed it (whew), and now I have a folder on my sdcard that is titled "FOUND.0000", and there are text files in it with names such as "FOUND.0000CHK, FOUND.0001CHK" and so on. Do I need these files anymore or is just showing me what was wrong and fixed on my sdcard? Will it cause any issues if I delete the folder? Sorry if all this is confusing or stupid. I just have never had an issue like this before and I have rooted and used quite a few android phones and tablets. Im not a noob but I definitely do not know that much about this kind of stuff so any help would be greatly appreciated! TIA
Travis
Click to expand...
Click to collapse
This is very interesting. I've never had a problem with the SD card. Is this the same SD card that shipped with the phone?
When you, "right click on the drive that my phone was, and click "check and fix for errors" is that a windows command? Does the picture below represent the action you took?
{
"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"
}
Did you end up deleting those files? If so, what happened?
I am having some weird errors with my SDcard myself. I went from a flashed kernel on CM7 off to another ROM. Rebooted and SDcard errors out the wazoo. I am getting MD5 mismatches on a lot of my backups at that. If I can get a ROM that fully boots, I will likely wipe the sdcard and start over to see if it isn't from a corrupt file or something.
The same exact thing happened to me. I mounted my SD card from recovery and windows auto fixed it.
If that didn't work I was going to wipe backup. wipe, and reformat.
i just received a low disk space notification and i can not get rid of it. Just yesterday I had about 6gb of free space and today it says that i have 12mb left. i have not installed anything, as a matter of fact, i deleted some apps last night. I received this false notification before and all i did was wipe cache. this time i wiped both cache and dalvik and the issue is still there. any suggestions?
How much memory do you have left this time?
slaphead20 said:
How much memory do you have left this time?
Click to expand...
Click to collapse
15mb
get the app "disk usage"........that is great for seeing what is using up disk space
Use Sdmaid which is available over play store and perform a system cleanup/app.
If youre getting the same error i have, gallery thumbnails are taking an insane amount of space without reason.
I use this app alot and it does wonders.
Hope it helps.
Inviato dal mio GT-I9300 con Tapatalk 2
sorry for bumping this but this issue is starting to annoy me. Since my last "Low on space" notification came on, i deleted a few games and that cleared the notification. ever since I have not installed any memory hogging apps then out of no where i get the "low on space" notification again, so i just left it and a couple of days the notification went away. it's happened a few times. Now the notification came back and my phone is acting up. I can not open Gallery, I can not receive SMS because it says no space. Viber force closes....arrrgh it's pissing me off. Not cool because i use this phone for work. I know for a fact that my internal memory should have free space because before the notifications i had 8-9gb of free memory. any suggestions or fixes?
i have had the same problem of missing disk space and used "Storage Analyser"
by LeveloKment, with root permissions it found what DiskUsage,Memory Map & DiskView could not find and that was thousands of logs located in system\data\log i deleted those logs and everything was fixed
this app gave the correct path size unlike the rest that i mentioned i hope that helped
iTK said:
i have had the same problem of missing disk space and used "Storage Analyser"
by LeveloKment, with root permissions it found what DiskUsage,Memory Map & DiskView could not find and that was thousands of logs located in system\data\log i deleted those logs and everything was fixed
this app gave the correct path size unlike the rest that i mentioned i hope that helped
Click to expand...
Click to collapse
thanks. but i've tried installing those apps and my phone tells me "insufficient memory". i've deleted a few files, which free'd up 125mb of space and still won't allow me to install those apps. Anyways, i checked system/data/log and i have a few files in there but not sure which to delete.
swift2fly said:
thanks. but i've tried installing those apps and my phone tells me "insufficient memory". i've deleted a few files, which free'd up 125mb of space and still won't allow me to install those apps. Anyways, i checked system/data/log and i have a few files in there but not sure which to delete.
Click to expand...
Click to collapse
i have erased the entire directory because most of it were RIL crash logs
iTK said:
i have erased the entire directory because most of it were RIL crash logs
Click to expand...
Click to collapse
i deleted more files and was able to install Storage Analyzer. It showed a hidden folder containing a lot of thumbnail pictures, so i deleted that folder. In the app it shows i now have 8.48gb but in system settings under storage it says i have 192mb free and i still have the Low Memory notification. 8.48gb is about right because i took the time to look at all the folders on my internal memory.
since i dont know what steps you took i will need you to do the following in order to get more info
i will assume you are rooted:
1. tap on the 3 dots [top right corner]
2. tap on preferences
3. tap on expert options
and the check both boxes [important!!!]
4. tap on the bottom left icon
5. tap on data, let it finish, take a screenshot
6. tap on system let it finish take a screenshot
7. tap on storage/sdcard0 let it finish take a screenshot
8. also take a screenshot of settings>storage
post the screenshots here
to take screenshots hold home+lock buttons
{
"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"
}
Here are my screen shots
just noticed that the SD card dropped another 2gb due to the hidden .thumbnail folder,(came back after i deleted it the first time) In Storage analyzer it said i had 8gib free now it's down to 6gib free and nothing the numbers didn't change in System/storage.
forgot to add Screen shot of Data
screen shot of data
swift2fly said:
screen shot of data
Click to expand...
Click to collapse
For a quick and pain free method, just factory reset the phone, and run it on a stock firmware if you use a custom firmware.
Skander1998 said:
For a quick and pain free method, just factory reset the phone, and run it on a stock firmware if you use a custom firmware.
Click to expand...
Click to collapse
As far as i know i'm using a ROM based on a stock firmware. I'm on ARHD v2.3.0 (ICS)
swift2fly said:
As far as i know i'm using a ROM based on a stock firmware. I'm on ARHD v2.3.0 (ICS)
Click to expand...
Click to collapse
your problem seems to be in "DATA"
tap on /data
then tap on folder data
take a screenshot
almost there
Despite being one of the best Androids around right now, the Samsung Galaxy S5 could always do with some additional care. Performing a reset of your device regularly can help keep your smartphone bug-free and running smoothly for years to come. We'll show you how to get everything spick and span on your S5 in a jiffy by performing a complete data wipe, returning it to factory standard :good:
{
"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"
}
Why reset a new phone?
Good question. While it makes sense that older devices get bogged down over time, it may not seem necessary for a brand new phone. But the truth of the matter is that you can accumulate all sorts of junk in a very short time, either from apps, downloads, firmware updates or any number of other sources. It's an especially good habit to get into to do a reset every time you update your Android version to avoid the usual bugs and battery drain issues.
What to do first?
The absolute most important thing to do before performing a data wipe is backup, backup, backup. Even for something as seemingly straightforward as installing an over the air firmware update can cause problems that lead to data loss. I only need to remind you of the Android 4.3 update fiasco last year that left millions of Galaxy S3 and Galaxy S4 owners with unusable phones for months. You have a few backup options:
Google backup – from within the settings menu you can head to the Backup and Restore section where you can set your backup options for Wi-Fi passwords, app data and other things to Google's servers. This is a great option and you can also check the box for automatic restore.
App backup – you can also grab an app from the Play Store that will do a backup for you. Some of these apps, like Titanium Backup, require root. Others, like Carbon Backup, can do a full Carbon backup without root by using your desktop.
The old-fashioned way – literally email yourself important things from your phone, transfer them to your computer with a USB cable, shift them to your microSD card and remove it before proceeding: all of these are perfectly fine albeit mildly paranoid things to do. But it only takes one major mess up to make it all seem worthwhile.
How to reset the Galaxy S5
Once you've backed all your essential apps, data, and so on (make sure you do it!) you're good to proceed. I'll remind you again: this process wipes all data from your device and leaves it as funky fresh as the day you unboxed it.
Option 1 – keypad
From the dialer you can simply enter the following code to do a factory reset: *2767*3855# but this doesn't work on every handset (it didn't work for me on our Galaxy S5, for example)
Option 2 – settings menu
The simplest way is to head back to the Backup and Restore section of the settings menu and look at the bottom for the Factory Data Reset section. Tap this and proceed through the warnings then sit back and enjoy a clean phone once it reboots.
Option 3 – hardware buttons
Maybe your phone is stuck in a bootloop (where you can't get past the Samsung logo when starting) or the display won't wake up or you've broken your screen. You can still perform a reset by using the physical buttons.
1. Turn your Galaxy S5 off.
2. Press and hold the Power button, Volume Up button and Home key. You'll see a blue notification in the top left of the screen and then an animated Android image until you are brought to the recovery menu.
3. It's always a good idea to clear the cache when doing a reset as well (especially when doing an update) to avoid any issues with app data on new Android versions. Use the volume down button to scroll to ''Wipe cache partition'' and hit Power button to select. You'll see a notification in the bottom left in yellow that says it has completed.:fingers-crossed:
4. Use the volume up button to scroll to ''Wipe data/Factory reset'' and hit that Power button again. Scroll down on the next screen to ''Yes'' and away you go. You'll get the same completed notification in yellow at the bottom and you can then scroll to ''Reboot system now'' and that's it: set up your Galaxy S5 from scratch and restore your apps and data.
How often do you do a reset? What are the main problems you notice after updates ? Post In Comments :highfive:
---------------------------------------------------------------------------
Warning : Dont Copy This
Hi all,
Did anyone use the advanced wipe function from within TWRP before flashing the ROM (T-Mobile original)?
{
"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'm asking because I only have about 300Mb free out of 8GB. Only have about 20 apps, nothing big.
I flashed the ROM (K33010i_00_1021.kdz) using LGUP just to test how much free space do I have and it's about 150Mb free. Don't know how a 1.2Gb ROM can occupy almost 8GB.
I'm thinking to check everything except internal storage, wipe it, turn off the phone, plug the charger and try to enter download mode and flash the ROM again. The issue is that I don't know if after the wipe I will be able to enter the download mode.
Any thoughts?
Cheers!
saphta said:
Hi all,
Did anyone use the advanced wipe function from within TWRP before flashing the ROM (T-Mobile original)?
I'm asking because I only have about 300Mb free out of 8GB. Only have about 20 apps, nothing big.
I flashed the ROM (K33010i_00_1021.kdz) using LGUP just to test how much free space do I have and it's about 150Mb free. Don't know how a 1.2Gb ROM can occupy almost 8GB.
I'm thinking to check everything except internal storage, wipe it, turn off the phone, plug the charger and try to enter download mode and flash the ROM again. The issue is that I don't know if after the wipe I will be able to enter the download mode.
Any thoughts?
Cheers!
Click to expand...
Click to collapse
Advance wiping partitions will erase the data from them.
But let me explain to you how the stock rom works. That 1.2gb is not the rom size.
It's the size of the ramdisk, which is compressed and unpacked after the rom is flashed.
* The ramdisk will always take up space as it is a copy of the /system partition.
* Then you have the current "/system" partition that contains your changes such as rooted status and debloation.
* That is about 2.5gb of "/system" data that is taken up from the 8gb total phone space.
* There's about 1-1.2gb of "/data" space where your user apps get installed to and miscellaneous other directory spaces allocated.
* Alas there is"/data/app-priv" where system apps are installed which has about 1.2gb of space to spare.
& After that it leaves internal data "/sdcard" directory.
Without having your internal data space full you keep 4gb free for storage. But when you install apps they are apart of the first 4gb of phone data.
With the symbols before the spaces above being the sides of the phones space ( * / & )
Apps go into *, and no matter how much space you have in &, it will not make a difference.
My advice for space saving is to debloat your phone with apps you don't use or features you can't use. Grab an external sdcard.
Root, install titanium backup - uninstall some apps if you cannot install it, run a full backup and start removing the red coloured apps .
Be careful what you remove as it can break certain features.
But if you do break something, you can use lg up to reflash the kdz (and you can select just a partition to reflash; such as system) that will fix anything that breaks while removing the red labelled apps without removing any personalization you've made to the device.
Debloation is your best choice to deal with such little space until we get a rom that does not utilize a ramdisk.
Everything checkmarked is what you need to keep to have a fully functional system with NO constant forceclosing.
What is red is system installed and green are data related to system installed apps.
There's a few items unchecked that are on that list; these are also unneeded items.
At minimum these items are all you need installed. Anything else that is red or green may be uninstalled.
Thank you for taking the time to answer to my post!
No problem at all. Hope this helped you tremendously on saving space.
Excellent guide. I haz root
Hi Together,
I think something went wrong, but i cant say what.
After using magisk to root (like very often before) and a confirmation that everything should be fine i had to use the ro2rw fix to get rw access. I didnt know that one but got help & a lot of cool info to solve that rw topic. I used the tutorial here: https://forum.xda-developers.com/t/how-to-root-23-and-have-full-access-to-system-partitions.4585399/
Shortly after that i get now a crazy serviceprovider-update nag screen. Crazy because it tells that something has to be updated and i have to reboot. And if i click the reboot link it just starts a notification that it cant be updated.
My phone service is fine i can call my landline without any problem. But the blocking everything nag screen still appears. So as a rooted user with android expierence since android 1 i choose my SD Maid App to find the apk that is causing this notification. And after i ended com.samsung.android.cidmanager (2.0.23) the notification on the the top disappeared. But after a reboot the One Ui updated something and there was it back again. And it was running even any autostart reason was disabled. I checked it with 2 apps. There was no autostart that i could remove. And after my next reboot it is running again.
The message in the pic translated from german tells:
"Serviceprovider-Update
Your phone have to be restarted, to setup functions and services of your provider.
. Apps and Layouts might change, after your phone was updated."
Emergency Call
Reboot"
{
"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 comes back again and again after 5-60 Min. If i force stop com.samsung.android.cidmanager (2.0.23)
its gone. Removing all "Receiver Manager"/ Autostart also doesnt work. I guess another app calls that service. But i dont know which one.
The notification just tells:
"Serviceprovider-Update
Serviceproviderfunctions could not be setup."
Any idea other than just wipe data/cache and reinstall?
===Edit===
OK a complete new flash and new root was fine until i used the ro2rw script again.
Same Error as before. I guess there is one Service that is causing that nag screen.
Thanks a lot for reading.
Greetings
4summer
4summer said:
Hi Together,
I think something went wrong, but i cant say what.
After using magisk to root (like very often before) and a confirmation that everything should be fine i had to use the ro2rw fix to get rw access. I didnt know that one but got help & a lot of cool info to solve that rw topic. I used the tutorial here: https://forum.xda-developers.com/t/how-to-root-23-and-have-full-access-to-system-partitions.4585399/
Shortly after that i get now a crazy serviceprovider-update nag screen. Crazy because it tells that something has to be updated and i have to reboot. And if i click the reboot link it just starts a notification that it cant be updated.
My phone service is fine i can call my landline without any problem. But the blocking everything nag screen still appears. So as a rooted user with android expierence since android 1 i choose my SD Maid App to find the apk that is causing this notification. And after i ended com.samsung.android.cidmanager (2.0.23) the notification on the the top disappeared. But after a reboot the One Ui updated something and there was it back again. And it was running even any autostart reason was disabled. I checked it with 2 apps. There was no autostart that i could remove. And after my next reboot it is running again.
The message in the pic translated from german tells:
"Serviceprovider-Update
Your phone have to be restarted, to setup functions and services of your provider.
. Apps and Layouts might change, after your phone was updated."
Emergency Call
Reboot"
View attachment 5920713
I comes back again and again after 5-60 Min. If i force stop com.samsung.android.cidmanager (2.0.23)
its gone. Removing all "Receiver Manager"/ Autostart also doesnt work. I guess another app calls that service. But i dont know which one.
The notification just tells:
"Serviceprovider-Update
Serviceproviderfunctions could not be setup."
Any idea other than just wipe data/cache and reinstall?
===Edit===
OK a complete new flash and new root was fine until i used the ro2rw script again.
Same Error as before. I guess there is one Service that is causing that nag screen.
Thanks a lot for reading.
Greetings
4summer
Click to expand...
Click to collapse
Remove CSC Manager from ADB or via Root.
That solves the nagging screen.
@JazonX: Thanks a lot. I found that out by removing the most likely apk and froze all of them with sd maid. But good to know that the bugger was the CSC Manager.
I finally got most stuff that i need working. Did you figure out how to delete the "RO2RW_Super" Folder? I backuped the files inside it on my dektop. But after that I cant delete, move or take the files over. And the .img files are ~23GB in size. So a lot of space. I tryed also to rm -f them in Terminal with su. No chance. Maybe with TWRP?
---edit---
OK TWRP works if you remove any lockscreen stuff. Remove fingers and Pin/Patter (...) and than
it worked on my 2nd try with the integrated filemanager. ;-) 23GB more.
Dont forget that your TWRP Backups on your internal Space wont be there. By the way without any error! I read about that topic but forgot already that it wont work. So it works only with a external device like a usb-c Stick.