Storage shows 97% in use always. Cannot find files in category "Other"
47G+. Have tried several file managers. No change. 6.87G in System files. No medià, backups, or apks. New phone.
Is this that dreaded modem dump thing that happens on certain OnePlus devices?
This happens when the modem firmware is mis-flashed or defective.
You'll need to return that phone for repair or exchange.
In this condition you cannot root the phone as the unlock bootloader is greyed out and cannot be changed in dev. options to delete the dump files.
steveaudioaka said:
Storage shows 97% in use always. Cannot find files in category "Other"
47G+. Have tried several file managers. No change. 6.87G in System files. No medià, backups, or apks. New phone.
Click to expand...
Click to collapse
This solution will factory reset your device in a way that you likely have not.
Ensure you have USB debugging enabled and permissions granted for the connected device (PC,Linux, another android device) and reboot to bootloader.
While in the bootloader run the command "fastboot -w"
This will completely reformat the data and metadata partitions.
After this you can reboot system, go through the setup and check available storage.
I hope this resolves your issue.
Related
I've seen a number of requests for this functionality and recently it became necessary for one user who had a disabled Home Key to clear cache and data without the use of ClockworkMod. I have reserached two methods to address this issue. These instructions require some familiarity of android, computer and tablet terminology and usage. Feel free to ask for clarifications in comments. Here we go...
Method I - Stock Recovery Command File
Technical: Stock Recovery command file can be used to perform a few additional functions as well as to alter the path to update files. These commands will execute with all privileges available to recovery mode.
Advantages: Very easy to use. Very little technical knowledge required. No third party software is required for use.
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Prepare a text file named "command" (no file extension) with one of the following commands on a single line. The wipe data command will wipe both data and cache. Wipe cache will wipe cache only.
--wipe_data
--wipe_cache
2) Place the file in a folder named "recovery" in the root directory of your MicroSD card.
3) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
4) Allow the command to execute completely then the tablet should reboot (this may not occur automatically depending on firmware installed).
Method II - Updater Script
Technical: The attached "Updater Scripts" perform delete commands (recursively if necessary) on the named directory or file(s). The directories are mounted automatically by the system before the script executes but it could be easily revised to include that step if necessary. The partitioning, formatting and directory structure are left untouched. Only files are deleted.
Advantages: No third party software is necessary for execution. Relatively easy to modify for more surgical precision (i.e. leaving installed apps but clearing possibly corrupted system data). Included example: "Clear Battery Stats"
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Download the attached archive (ClearData.zip) to your computer.
2) Extract the files to your computer. You should then have a folder named "recovery" (which contains a file named "command") and an additional archive named "update.zip"
3) Place the recovery folder and the update.zip in the root directory of the MicroSD card.
4) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
5) Allow the script to execute completely then reboot the tablet (this may occur automatically depending on firmware installed).
This will become handy someday.
Thanks for sharing your knowledge.
You're welcome. One quick note... the new stock recovery adds a menu simiilar to ClockworkMod. These methods will still work since the recovery folder/command file are checked first but it really isn't as necessary any more.
Need Help
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Me too
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
lrgche said:
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Click to expand...
Click to collapse
That's an indication that you may have more serious problems. nvflash will be required. http://forum.xda-developers.com/showthread.php?t=861950
Once done you will likely need to install ClockworkMod and repartition your internal storage.
Loukoebel said:
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
Click to expand...
Click to collapse
If your tablet boots properly but you can't get into CWM then it probably isn't installed properly (or at all). http://forum.xda-developers.com/showthread.php?t=865245
Keep in mind that CWM is NOT compatible with all ROMs. Make sure the developer for your chosen ROM recommends it before installing it.
Does your method in opening post have to be run from external micro sdcard?
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
K J Rad said:
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
Click to expand...
Click to collapse
so your method is a simple way to replace one of the main uses of Clockword MOD?--Plus you stay stock more or less.
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
K J Rad said:
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
Click to expand...
Click to collapse
Wipe data does what--remove the apps installed?
And the partitions?
Your post is very interesting. It implies that you have a knowledge of the g-tabs partition structure. I have played with Linux off and on for the last 10+ years. When I began, I used Slackware and when you set it up you had to manually create partition tables using fdisk. You were only required to create two - the data partition and a swap partition but it was often recommended that you create several others - one to contain the home directory to prevent users from using all the disk space (in the days of small disks) for example. It appears that there are a lot of partition on the g-tab. Up to now, I have used various wiping tools like clockwork or calkulins wipe all on faith. I would really like to know what all the partitions are and what is in them. I have used terminal to get to the root folder and tried to do an fdisk to display the partitions but try as I might everything remains hidden. It would seem that a script like yours could be adapted to do many things but I would certainly want to understand the structure a little better before I did anything. I have searched and been unable to find that information. Can you point a way for the curious to learn more about the partition structure on the g-tab?
Wish I had a direction I could point you in. What I've found so far has mostly been stumbled upon while looking for something else. What I can tell you is this...
1) When using fdisk in Android you must specify the device to look at. Try something like: fdisk /dev/block/mccblk3 That should list the current partitions as defined by CWM or whatever was used originally.
2) Within one of those partitions in the list generated above are sub-partitions holding the bootloader, system, data, etc partitions. You can see how they're described in the .cfg files in the nvflash restores that are lying about.
lsu205 said:
Wipe data does what--remove the apps installed?
Click to expand...
Click to collapse
Removes user apps and their associated data as well as system related data and settings.
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
CodeNamePapa said:
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
Click to expand...
Click to collapse
I'm looking for a solution to that problem. Unfortunately these methods still require the ability to get into recovery mode which likely won't work if you're having trouble getting CWM installed.
If, however, you can get into recovery... then it is theoretically possible to create a script that would accomplish that. As soon as I have one I'll be adding it to the mix ;-)
Edit: I've found something I think will work. Will do some testing tonight. It will still require access to recovery.
I wasn't sure if you saw my other post but I am seeing no partition 0 when I NVFlash with a verifypartition.
http://forum.xda-developers.com/showpost.php?p=13059520&postcount=57
I haven't yet but I will. Let's try to keep this thread on topic. Thanks.
More thoughts:
because I went w/ cyan7 is it possible i have a "bad" kernel and that the stock bekit-1105 or the roebeet-3588 files are crashing w/ the kernel in place already?
I know custom ROMs can have a custom kernel applied separately, but I have no idea whether cyan7 loads it's own kernel...
I have yet to try the nvflash_gtablet_46 version, as I see the img files w/in are different from the original 1105 .zip
Also:
read on another thread that part 2 and part 3 aren't loading for other users when doing nvflash - I did notice that it pauses, runs some stuff, then starts loading part 4 through to the last part, then success. - do part 2 and 3 run for you?
edit: I see a 4349 downgrade.zip in another thread for those who got the OTA update but want to go back to stock 3588 prior to jumping off somewhere else - I can't expect that would help me as I can't do squat w/ recovery yet, but could that possibly "reset" any bad kernel problems? - again, I'm just thinking out loud.
This is well outside the scope of this thread but I find some of what you mention interesting so I'll address it and then end any further off topic discussions.
I did not build nor have I ever used Cyan7 so I have no basis for an opinion on the matter other than this... Each ROM comes with a kernel installed so if properly done an nvflash should overwrite any "bad" kernel.
Part2 and Part3 do indeed load, they are just displayed differently than the other Parts. Just minutes ago I flashed down from Mountain Laurel (4349 based with the new bootloader and recovery) with absolutely no trouble. I can, and have, read back those partitions after an nvflash to prove that point.
The 4349 downgrade will only work for you if recovery is working. Having never used it I don't know that it would "reset" the kernel but any subsequent flashing of a new ROM image would.
I am working on a stock recovery solution for partitioning but it isn't likely to help anyone who is stuck in an APX loop. I do have some ideas on what might help for that condition but I haven't been able to get my hands on one for testing and trying to help people here is like being a consulting mechanic for a car repair that's in someone else's shop having work done on it that you're not being told about.
I'll be happy to address any further comments or questions regarding your specific issue in an appropriate thread or via PM. Thanks.
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
spencerj2001 said:
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
Click to expand...
Click to collapse
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
no adb does not see my device but i can access the internal sd card
Swiftks said:
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
spencerj2001 said:
no adb does not see my device but i can access the internal sd card
Click to expand...
Click to collapse
If you can access the internal card, its weird that adb can't see your device... oh well... try reverting to a earlier/different firmware via a blob. See thread in dev section.
Sent from my CM7 Atrix 4G
i did exactly the same mistake: i uninstalled some system apps (the asus preinstalled apps, with titanium) without unlocking the bootloader, and after a wipe from the stock recovery i'm not able to go beyond setup configuration, it always stops. but i can see and use internal and external memory from my computer. did you find a solution?
Soooo... Does flashmode or fastboot let you read the files? AFAIK whenever I have flashed a rom and selected format data, it selects a file called "userdata.sin". So I guess that the /data directory is being flashed over, without the ability to read the files.
However, is there a way to *just* flash the data/system/gesture.key(yup, you know it. Forgotten pattern and phone doesn't recognize username and password, tried multiple times)?
Another, more device specific question: The phone with me now is a 4.3 Xperia T. Whenever I connect it with my computer without unlocking the lockscreen, it doesn't allow access to the internal storage. Is that functionality something that can be easily bypassed, or is it a more "hardcoded" basic functionality that blocks even through flashmode/fastboot?
Hi everyone, forgive me for my bad english...in this day i'm freaking out because it happend an unexpected thing. 4 days ago in the evening i looked that was an error message about whatsapp in the home screen, then i open the app and appeared that chat list got problem and to solve that i need to restore backup or i get lost chat. The device was connected to wifi house, but i had whatsapp backup on my phone. I searched on internet and on official whatsapp page i red it was possible as an error. To solve that need to restore last backup. I done it but while the loading has started, after a few minutes the devices shut down and reboot. It's arrived to the logo of the ROM and then shut down again and reboot. i undestand it was a bootloop. Two years ago i install android kitkat because the device can't received android 4.4 and i don't want stay with 4.3. Everything fine. After an year the device goes in the bootloop, but i don't know why, so i decided to format data ad restore kitkat again. Before that i can transfered some data because i saw that if device was connected on the pc it not gone in bootloop. This year another problem but more little. The device sometimes reboots so i do a backup with titanium backup and then wipe everything including internal storage because on the boot after flashing the ROM the device can't memorized anything. In that occasion i don't reboot the device because i wiped internal storage so everything. Connected usb-device to the phone, copy gapps, rom, twrp and super su. Reboot and the smartphone was reborn. Whit titanium backup i restored all data. This time the thing is very very different and more difficult. In my opinion probably i could download a virus with whatsapp, usually it is connected to a link into a message sended by a contact in whatsapp, or happened something during the restore of backup of whatsapp. The device goes constantly in bootloop but i can entry in recovery mode. i noted that can't see the gapps, rom e supersu file in the sdcard like the other times. They are only in the data\media\0 folder. Everythime i try to copy something not in the sdcard, it goes on an error about a netstat file i found in the data\system\netstats folder. It's a file short, different by the others. I red that netstat files can be deleted but this file can't be deleted by using twrp>advanced mode>file manager>name of the file>delete. Before try to do another format data or again a total format of internal storage like the other time, i need to know if this procedure can resolve the problem. This time i was not prepared so the last backup is about six months ago. In this months i inserted new contacts and this time i don't sincronized my contact list with my google account like the other times because i couldn't image to be in this situation. I try to delete the file using adb but my phone is not recognized so the serial number doesn't appear. List of deviced attached is empty. In this case i can't activate the developer funcstions by tipping in the device information into the phone because it goes in bootloop. On the pc i have usb-drivers, but now into the phone there's android 4.4 not 4.3 like the first time i do the procedure to unlock the device. So with adb don't see serial number but the pc just see the device like google nexus adb interface. Copying file as contact or dialer or data about apps because are all in the data folder, appears an always an error about netstat and the red failed written. just copy from sdcard folder to usb external device this not happen, what can i do?
I done a nandroid backup because i know that with titanium backup i can restore data i want to restore, but also in this case could appear the same message error about netstat file? All data are been copied on the external usb deviced and then on the pc, but i don't know if the problem will be present again. so if i try to restore data with titanium backup and the problem reappers i don't know what to do.
Here we are some information about my phone. I hope someone in this fantasctic and big community about android developers can help me to solve this very big problem. if i thinking about i've done i feel so stupid because probably i could avoid this problem.
i forget to say also i tried to fix permission, wipe davilk cache and cache, copy log to sd (to see if there's another error but i don't know how to do). After all of this passages, everytime appears the same error.
Fastboot Mode:
Product name: tuna
Variant: maguro 16gb
hw version: 9
Bootloader version: primemd04
basedband version: i9250xxlji
carrier info: none
serial numeber: xxxxxxxxxxxx
signing: production
lock state: unlocked
Rom: omnirom maguro nightly 4.4.2, kernel stock of omnirom. gapps stock 4.4.2
Error: E: unable to stat ' /data/system/netstats/dev.1480018034937_' appears then "updating partition details..."
after error: ....done Full SELinux support is present. Mtp enabled
Update
pc see the device in fastboot mode launching cmd fastboot devices. Get out the serial number. It doesn't work launching cmd adb devices. List of device is empty. On the pc i have two file about usb drivers downloaded by samsung support site. If i change the usb driver folder in sdk with the new samsung usb driver i just download, may i permit to see the phone with adb? or should i try to unistall device recognized as google galaxy nexus adb interface and repeat the installation of google usb drivers with an unknown device?
update
i'm losting hope. I tried also nexus root toolkit (NRT) by wugfresh. Before the programme i can't see the phone with adb, after unistall and reinstall the driver i can se the device. But here the bad news... i can't copy from the pc into the sd folder using windows and i don't know why because pc see the device, i can see the folder inside sdcard internal storage but can't copy from the pc to the phone. Fastboot and adb mode work. I've done a flash stock + unroot using NRT. Everything fine but then phone goes in bootloop and not with the stock logo so Nexus, with the Rom logo intalled instead. The NRT message says that the bootloop could appen so wait. After 20 minutes power off the device. So i try to do format data from TWRP; procedure works with blu written succesfull but there's the same problem E (encrypted or error?) unable to stat data/system/netstat file and the number of the file. So i try to wipe the internal storage. Succesfull but again red written E: same up. Everything i try to do nothing change. Internal storage stuck always the same MB, TWRP 2.8.7 always present, i can't flash 3.0.2. Can't also remove enctrypted data with NRT because is uncheck. Have i throw away the phone? The E unable to stat data/system/netstat with the number of the file goes out everytime because during the process for example about format data check out updating data partition and then E: blablabla also with succesfull written, not failed.
I have a Razer Phone 2 rooted with magisk. I use GPS Joystick. I decided to select the "disable system GPS" setting in its options. I rebooted as the app requested and now my phone loads to the point where it wants me to enter my pin and I see my wallpaper for a split second then the screen goes black and it loads up the status bar about ever 10 seconds for a split second then it repeats. Like it is stuck in a loop. After a couple minutes phone reboots and I get this message...
Android Recovery
razer/chery12/aura
9/P-MR1-RC003-RZR-190305/3110
user/release-keys
Use volume up/down and power
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Click to expand...
Click to collapse
So I reached out to the dev of GPS Joystick and he explains that the option disables the location services called "fused location provider" and I have to re-enable it to fix the problem. He sent me a post here explaining that I need to pull an .xml file from the phone, change the code, and push it back. Simple right? Well maybe if I have TWRP, but I don't. I can however boot into the phones recovery options and there is an option there to "apply update from adb" but I cannot seem to pull anything using that interface. My Windows computer recognizes the device using Minimal ADB and Fastboot but it shows it as a whole bunch of numbers then the word "sideload" which I guess is a limited form of adb just for side loading? Maybe someone could make me a script that I can sideload that changes the file back to normal? Here is the code from the dev of GPS Jostick that is used to disable and enable the fused lcoation provider.
It calls this code to disable:
ComponentName component = new ComponentName("com.android.location.fused", "com.android.location.fused.FusedLocationService");
getActivity().getPackageManager().setComponentEnabledSetting(component, PackageManager.COMPONENT_ENABLED_STATE_DISABLED, 0);
And similar code to re-enable it:
ComponentName component = new ComponentName("com.android.location.fused", "com.android.location.fused.FusedLocationService");
getActivity().getPackageManager().setComponentEnabledSetting(component, PackageManager.COMPONENT_ENABLED_STATE_ENABLED, 0);
Click to expand...
Click to collapse
So my question is, can I pull this /data/system/users/0/package-restrictions.xml file from my phone and push it back without using TWRP? But instead using the phones recovery option and its various selections? I'd prefer to exhaust the resources to recover the phone since I have spent weeks personalizing it. I am not fluent in adb but I am hoping someone can throw some ideas or even a solution at me that I am missing. All I got to do is pull a file, change a word, push it back and reboot. I can't imagine there isn't a way to do this by just using what the phone has to offer. Any help would be greatly appreciated.
Another idea that came to mind is in its current condition could I install TWRP? Is fastboot an option at this point? Maybe if I can flash TWRP in its current state I can then make the appropriate modifications.
I ended up fixing the problem. I installed arter97's kernel that had TWRP baked into it. I then used TWRP to copy over the .xml file, change the code as mentioned above, and then copied it back to the phone. Problem solved. It is amazing how one simple word in a .xml file can prevent a phone from functioning properly. It simply amazes me.