I'm on an s5 neo, rooted but using the same software it came with.
I decided to try a factory reset, as I had done a few things I can't undo, like removing mtp application, with a root app remover whose restore function doesn't work on this device.
I was also thinking, that instead of personalizing everything, and downloading everything, and then debloating, I thought I'd start fresh and then debloat first.
Thank *god*I had gotten brave enough to download and install twrp and make a backup, that back up is where I am coming to you from now.
I used the twrp recommended wipe for the reset, not custom wipe. Worked fine. Powered back on. All looked well until I came across a screen that said "just a sec..." For an extremely long time, like 10 minutes...
Why wouldn't it fully turn on, any ideas? As of now I can't factory reset ever again.... :/ and I'd like to be able to.
I hasn't disabled anything crazy and could reboot normally before I tried the wipe. I just don't get what went wrong?
Any help is greatly appreciated.
I cant even start off with a new rom I don't think, they're all made for the 903m or 903f versions of this phone, and I'm on the international 903w. I'm guessing some thing significant is different or else it would just be called the 903.
Sent from my SM-G903W using XDA-Developers mobile app
what did you wipe in the custom wipe?
also this http://forum.xda-developers.com/galaxy-s5/general/rom-somewhat-incomplete-edition-v0-1-t3295464
I want to say it wiped data cache and dalvik cache
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
I want to say it wiped data cache and dalvik cache
Click to expand...
Click to collapse
Well, with a bootloop you can go to recovery and recipe, then wipe data then go to advanced options in twrp and delete the Android folder in both internal and external and that should fix the issue
Recipe? I should proof read this stuff before I post it. It should have said reset, not recipe
Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Click to expand...
Click to collapse
No, go to advanced options, file manager, then to either storage, touch the Android folder, hit the check mark in the lower right, select delete, swipe to confirm. Do this with both storages. It's not the system folder and doesn't contain anything that isn't rebuilt upon boot. But it does contain stuff from your previous install that is known to cause bootloops when going from an Android version to another. Nothing to worry about when you delete those folders. It's been the source of tons of bootloops for me
So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
{
"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"
}
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
Click to expand...
Click to collapse
Don't do it from within the system. Do it from within twrp
Here, I made a little video. I'm a 100% amateur videographer, so go easy on me lol
Related
Hi, I'm not sure if this is specifically a Nexus question or a general Android question but I have both a Nexus 4 and Nexus 7 and have observed the same behaviour on both
I have posted in the General section with nor response so now I'm posting on specific forums
Basically what's happening is when I delete stuff from the SDcard the free space seems to be allocated to the system partition WTF?!
Take a look at the screenshots I'm going to try a couple of things - one of the suggested things was clearing the data in the Google Services Framework data >> Settings - Apps - All - Google Services Framework - Clear Data - which freed up some of it but not all, the next thing from here for me would be to flash the factory images again and see what I start out with
Both devices are on CM10.1 if that helps, is anyone else is having the same issue??
{
"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"
}
The discussion on Google+ http://goo.gl/lNyLW
Ok so this is my partition sizes now after flashing the factory images back onto my nexus 7. No where near 5GB anyone have any idea what's causing this?
I am guessing you have a couple of CWM back up? Maybe 3-4 of them? Maybe you tried to delete some of them?
Buggy CWM Recovery. Especially if you still hang on to the older versions. Mostly because the way CWM save the backup files.
KyraOfFire said:
I am guessing you have a couple of CWM back up? Maybe 3-4 of them? Maybe you tried to delete some of them?
Buggy CWM Recovery. Especially if you still hang on to the older versions. Mostly because the way CWM save the backup files.
Click to expand...
Click to collapse
I just use TiBU and DataSync now, stopped doing nandroids a while back now
Sent from my Nexus 7 using Tapatalk 2
It's not "system data" for sure. It's some apps with root permission saving its file to locations it shouldn't be doing.
Some how l still think it is CWM, even as you stopped using it in a distance past (which is like 1-2 months ago). I recommend flashing newest CWM and see if there're still old back up files.
If you still can't find anything, try this
bassmadrigal said:
If you are rooted and have adb set up on your computer, you can find out what folders are using the most space by using the commands below, then change into that directory and run the command again.
Code:
adb
su
cd /
du -hd 1
--find the largest folder and change directory (cd) into it - if you find you no longer want to continue in the folder you are in, you can cd .. to get to the previous folder or cd / to get back to the root of the filesystem--
Code:
cd large_folder
du -hd 1
rinse
repeat
????
profit
This will allow you to find what folders are using the most space and can eventually lead you to any large files and can then let you find out if you can delete them or if you need to keep them.
Click to expand...
Click to collapse
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
We got tired of seeing OEMs include many GB of internal storage for music, while users were still running out of space for apps and data. This approach lets us merge everything on one volume, which is way better.
-- Dan Morrill, Android engineer at Google
Click to expand...
Click to collapse
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
noobdeagle said:
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
Click to expand...
Click to collapse
I wish that was the case but it not, the space goes to the system partition and I cant access it on the sdcard
Nexus 4, rooted, CM, gravity box.
I want to update to CM11 M6 but I can't get my phone to make a nandroid (using ClockworkMod) because I keep getting an error basically saying I have insufficient storage. These are the steps I take:
Backup using titanium
Go into recovery
Backup using ClockworkMod
It's at this point where it lists backing up the system, but then it gets hung up backing up the data card. I have tried to go back in and delete everything I could possibly think of (w/out wiping the whole thing) but to no avail. I have cleared my cashe and even deleted the titanium backup which was around 1gb and still no dice.
Attached are some screenshots that may be helpful. There has to be something hidden but I just don't know where to look for it. I tried to install DiskUsage but I can't since I don't have enough room. How do I clear up this phone?! Any help would be much appreciated!!
{
"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"
}
brahmaboba said:
Nexus 4, rooted, CM, gravity box.
I want to update to CM11 M6 but I can't get my phone to make a nandroid (using ClockworkMod) because I keep getting an error basically saying I have insufficient storage. These are the steps I take:
Backup using titanium
Go into recovery
Backup using ClockworkMod
It's at this point where it lists backing up the system, but then it gets hung up backing up the data card. I have tried to go back in and delete everything I could possibly think of (w/out wiping the whole thing) but to no avail. I have cleared my cashe and even deleted the titanium backup which was around 1gb and still no dice.
Attached are some screenshots that may be helpful. There has to be something hidden but I just don't know where to look for it. I tried to install DiskUsage but I can't since I don't have enough room. How do I clear up this phone?! Any help would be much appreciated!!
View attachment 2743357
View attachment 2743358
View attachment 2743359
Click to expand...
Click to collapse
You need at least 3GB of free space to make CWM able to create backup... but you won't find that backup in /sdcard/cloclworkmod folder it's in /storage/emulated/blablabla or something like that and you won't be able to get access there from your computer
parkourz said:
You need at least 3GB of free space to make CWM able to create backup... but you won't find that backup in /sdcard/cloclworkmod folder it's in /storage/emulated/blablabla or something like that and you won't be able to get access there from your computer
Click to expand...
Click to collapse
Ok, I'm not sure I understand. I'm in the emulated folder and went into the clockworkmod folder and keep descending and come to just 1 file that is just 7.63mb called "recovery-clockwork-....img". This can't be the solution, can it?
try in /storage/emulated/legacy/clockworkmod... or flash TWRP instead of CWM... if both won't help then you can try to make a backup with toolkit for PC, for example Wug's toolkit
Twrp is showing the backup size and a poseibility to compress it. You probably have much apps or there is some .something fokder what is using much or much cache just like on an desktop. Many things can cause it.
You may want to checkout what is using so much by deleting old folders from old apps or old things yiu dint use anymore.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
When installing apps the storage manager is not registering the correct size to start off with. For instance a 1.5gb app is showing as total size of maybe 59mb. Under data for the apps it shows maybe 200kb.
Now the worse part is when uninstslling apps it does not race the data for the app. In order to remove the data and get my space back I have to boot into recovery and wipe cache.
Tried removing external SD card and trying it again and it's th deer same issue.
Also when attempting to move data to SD card it doesn't seem to really move anything but takes at least 30 seconds to do it and still requires the SD in the 0hone to run the app
Does anybody know what's up here and willing to tell me?
Thanks maybe.
Yes I'm about to smash this **** ING thing.
Nickvanexel said:
Yes I'm about to smash this **** ING thing.
Click to expand...
Click to collapse
Try Odining the stock tar from www.sammobile.com
{
"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"
}
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Nickvanexel said:
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Click to expand...
Click to collapse
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
bilgerryan said:
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
Click to expand...
Click to collapse
So that means at this point you wouldn't really need to wipe before installing wicked rom anymore?
Also decided against any over clocking now, changed to performance governors and things are working great now, especially games. No hitching, we're I was getting 10fps or less I cod strike team it's now 30.. so if I install a rom it will be wicked, especially the function on it "fix external SD write" fixes my storage management issues than that alone would be great and the debloat and performance tweaks would be a great bonus.
Thanks.
My device used to show 128gb of internal storage - with 111gb usable. But after I flashed to Android N Preview 4 with a modified boot.IMG for a decrypted storage so I could have TWRP working. It showed I only had 24.1gb usable. I already tried a factory reset, and flashing back to 6.0.1 (mtc19v), PureNexus, and other ROMs. I'm wondering how I can fix 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"
}
Edit/////////
My issue has been fixed by formatting userdata via fast boot and I'm now decrypted on Android N beta preview 4 rooted with working twrp!
Special thanks to
@SlimSnoopOS
@Sass86oh
For helping me fix it :angel:
TnT_ said:
My device used to show 128gb of internal storage - with 111gb usable. But after I flashed to Android N Preview 4 with a modified boot.IMG for a decrypted storage so I could have TWRP working. It showed I only had 24.1gb usable. I already tried a factory reset, and flashing back to 6.0.1 (mtc19v), PureNexus, and other ROMs. I'm wondering how I can fix this?
Click to expand...
Click to collapse
Looks like you flashed the userdata.img. Type this in fastboot: fastboot format userdata
This will wipe everything from your phone. It will resize back to 128 GB.
Sent from my Nexus 5X using Tapatalk
Trying this right now, will edit this with results.
// edit 1
Windows update blocked me, hopefully its not windows 10
You most likely flashed the "Userdata.img" thats included in stock Android firmaware archives. Unless you have a 32GB device, the userdata IMG does not account for storage over 32GB and if you flash it on the 64 or 128GB version, it will partiton the internal storage and only allow for you to access 32GB. I made that same mistake myself when I first got my phone. The userdata img is meant to zap the internal storage and delete all userdata on the device. Instead, just use the command "fastboot format userdata"... It will perform the same function without any loss to your overall storage space. From now on, when you flash the stock firmware make sure you steer clear of that file and instead use the command. MAKE SURE YOU BACK UP ALL OF YOUR PERSONAL FILES FIRST!! That command wipes every partition on the device!! So make sure you've saved whatever you cant afford to lose before using it. Formatting the user data is not always required when flashing roms on your device. Actually its hardly ever a requirement. Usually its used when you want to bring your phone back to the factory settings. The built in SD partition on most Android devices is isolated space. This allows you keep all of your importatnt files safe in the event that your system partition becomes corrourpt forcing you to reflash your old rom or a new one. If you need any help at all please feel free to send me a message. Hope this helps!
TnT_ said:
Trying this right now, will edit this with results.
// edit 1
Windows update blocked me, hopefully its not windows 10
Click to expand...
Click to collapse
You do know that will wipe the phone but will work I've had that lol
jaythenut said:
You do know that will wipe the phone but will work I've had that lol
Click to expand...
Click to collapse
Yes, I was and am aware.
TnT_ said:
Yes, I was and am aware.
Click to expand...
Click to collapse
Were you able to restore your storage?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Were you able to restore your storage?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I backed up all my files to my PC before I did the process in the first place - 36.8gb. Using BitTorrent sync. I was able to restore using that, therefore there was no loss.
So ill try to put all the other information that's important here.
I tried flashing the Stock rom back to this phone through TWRP and I feel like I've flashed it about 8 times now. It comes up normally and I can go through the setup wizard and when I hit the home screen I tired getting Adaway. When I tried to download the apk to my phone and I try to choose a save location it keeps saying that I can't find a save location. Then I tried opening up the file manager and tried creating a new folder it says that the operation cant be performed. I have plenty of storage available on my 6T and I cant see what I'm doing wrong. I've flashed and reflashed both TWPR and the Stock ROM both Beta and official and I still run into the same issue. Is anyone able to lend a hand? Thank you in advance!
Edit: Fixed it!
I get this anytime I try to download anything to my PHONE. SD card not found
{
"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"
}
Sent from my Mi MIX 2S using Tapatalk
Coolaaron88 said:
I get this anytime I try to download anything to my PHONE. SD card not found
Click to expand...
Click to collapse
Format Data in TWRP
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Format Data in TWRP
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Let me try that and I’ll report back
Sent from my iPhone using Tapatalk
Coolaaron88 said:
So ill try to put all the other information that's important here.
I tried flashing the Stock rom back to this phone through TWRP and I feel like I've flashed it about 8 times now. It comes up normally and I can go through the setup wizard and when I hit the home screen I tired getting Adaway. When I tried to download the apk to my phone and I try to choose a save location it keeps saying that I can't find a save location. Then I tried opening up the file manager and tried creating a new folder it says that the operation cant be performed. I have plenty of storage available on my 6T and I cant see what I'm doing wrong. I've flashed and reflashed both TWPR and the Stock ROM both Beta and official and I still run into the same issue. Is anyone able to lend a hand? Thank you in advance!
Edit: Fixed it!
Click to expand...
Click to collapse
Hi, I'm facing same issue. Flashed many times stock ROM on both slots, and can't write any file or create folder.
How did you fixed it?
2be3_80 said:
Hi, I'm facing same issue. Flashed many times stock ROM on both slots, and can't write any file or create folder.
How did you fixed it?
Click to expand...
Click to collapse
As stated before enter twrp and format data/ factory reset. Something went wrong and your date was encrypted.
bladestonez said:
As stated before enter twrp and format data/ factory reset. Something went wrong and your date was encrypted.
Click to expand...
Click to collapse
Actually my data was encrypted but accessible through twrp. I did format data, couldn't boot system, but then I wiped data and it worked.
Thanks
Thanks!
bladestonez said:
As stated before enter twrp and format data/ factory reset. Something went wrong and your date was encrypted.
Click to expand...
Click to collapse
I ran into this same issue and this fixed it for me!