Related
ich bought a 2Gb miniSD , and after I format it, it has only 1,12 Gb . Can anyone tell me , if that is normal. I think, I can have min. 1,6 Gb for a 2 Gb miniSD.
Thanks for your answer
similar happened to me
I got some files on my storage card with weird characters that I could not delete. while doing a hard reset, I decide to remove all the SC files and start from scrash. it happens that my laptop is not compatible with my micro sd then I decided to put it in a digital camra and delete files. Now I only have 1MB capacity on my 2GB any help is appreciated too.
i have found a solution. Just download this file and run it , you will get your full memory back.
*** Rename the file to .rar and unpack
Whilst on the subject
What is the largest SD capacity supported by the XDA Exec (O2 branded)?
ConnorP said:
What is the largest SD capacity supported by the XDA Exec (O2 branded)?
Click to expand...
Click to collapse
4 GB is supported. Some have tried 8 GB but without success.
itallmylove said:
i have found a solution. Just download this file and run it , you will get your full memory back.
*** Rename the file to .rar and unpack
Click to expand...
Click to collapse
Really? The problem can be fixed with software? It isn't a hardware problem (defective card)?
no nluck
itallmylove said:
i have found a solution. Just download this file and run it , you will get your full memory back.
*** Rename the file to .rar and unpack
Click to expand...
Click to collapse
i have tried this file with no luck getting the missing 1gb back from my sandisc 2gb mini sd card.
itallmylove said:
i have found a solution. Just download this file and run it , you will get your full memory back.
*** Rename the file to .rar and unpack
Click to expand...
Click to collapse
Why would someone rename a .rar file as a .zip file, and the end user has to rename it back again? What purpose does that serve?
me said:
Why would someone rename a .rar file as a .zip file, and the end user has to rename it back again? What purpose does that serve?
Click to expand...
Click to collapse
This forum only supports hosting of zip files, not rar files. I guess it was easier to change the extension rather than convert it. At least he tried to help!
Pantaloonie said:
This forum only supports hosting of zip files, not rar files. I guess it was easier to change the extension rather than convert it. At least he tried to help!
Click to expand...
Click to collapse
Thanks for the explanation. Now I understand why that was done.
Any reason why this forum doesn't support .rar files?
Hi all!
I have bought the new Huawei P6S Dual Sim (China Unicom version).
It's multilanguage and has Android 4.2.2
I rooted it successfully (bootloader is already unlocked) but I can't change files on the system directory (I need to replace the apns_conf.XML). There is a security lock? What's happen?
Thanks in advance at all
try root browser from the playstore. This automatically sets the right permissions for files and folders Hope this helps!
Sent from my P6-U00 using Tapatalk
lootjelo said:
try root browser from the playstore. This automatically sets the right permissions for files and folders Hope this helps!
Sent from my P6-U00 using Tapatalk
Click to expand...
Click to collapse
Thanks ,
I tried it, but unsuccessfully.
It seems there is a protection (by Huawei) on the system folders. I can change files in other folders (with R/W mounting) but not in the \system folder
NolanBart said:
Thanks ,
I tried it, but unsuccessfully.
It seems there is a protection (by Huawei) on the system folders. I can change files in other folders (with R/W mounting) but not in the \system folder
Click to expand...
Click to collapse
Hi
This phone is the most heavily secured phone I have ever seen. The /system partition has at least three protection methods
1) mounted as read-only
2) some files have the "immutable" bit set on the ext4 file system. #chattr -i file will remove the immutable bit
3) since KK firmware Huawei applied a new security mechanism by which the kernel seems to discard any modification done to /system even when it's remounted as RW. With this mechanism any change is rolled-back by the time /system is remounted as RW even after a reboot.
From the shell command line I have found a way to solve the first two but I still have no clue of how to solve the third one. Does anybody have any clue on how to solve it?
abequer said:
Hi
This phone is the most heavily secured phone I have ever seen. The /system partition has at least three protection methods
1) mounted as read-only
2) some files have the "immutable" bit set on the ext4 file system. #chattr -i file will remove the immutable bit
3) since KK firmware Huawei applied a new security mechanism by which the kernel seems to discard any modification done to /system even when it's remounted as RW. With this mechanism any change is rolled-back by the time /system is remounted as RW even after a reboot.
From the shell command line I have found a way to solve the first two but I still have no clue of how to solve the third one. Does anybody have any clue on how to solve it?
Click to expand...
Click to collapse
Have you found a solution for problem 3??
rs06085 said:
Have you found a solution for problem 3??
Click to expand...
Click to collapse
No I haven't. Regretfully my P6S broke last week and I'm no longer able to keep this development
hey guys, in my DCIM/.thumbnails folder are 2 files (.thumbdata3.*number*, .thumbdata3.*number*) which grow up over 500MB each.
i have like 1,5GB photos and videos on the phone, so it feels like over 1GB of thumbnail data is a bit much, right?
when deleting these files, they reeappear after some time again.
So, i googled a bit and found the solution where you delete the files, create 2 new files with the same name and 0 bytes and then take away the writing permissions so android cant overwrite the files again with the bloated big ones. but i cant change permissions with any file explorer so far, most of them tell me i might have an unsupported file system. i tried Root Browser and Solid Explorer without success. is it because i have data formatted to F2FS?
other than that, why are these files so big at all?
Infos:
FreedomOS 2.1.2 CE
bluspark kernel#151
bluspark TWRP v37 (data formatted F2FS)
EDIT:
Solid explorer classic worked.
anyway, still interested why these files have to become so big?
Download FV File Explorer
https://play.google.com/store/apps/details?id=com.folderv.file
May be this is the first APP that can visit other app’s exteral data file .
1. Open folder "/storage/emulated/0/Android"2. Click the"data" folder3. Select the application you need4. Click "Use this folder"5. Done! you can see the files.
Document in Chinese with images guide attached as PDF.
OP, I have changed this category from Question to App to fit the content.
Also, the Chinese guide link you are sharing from coolapk cannot be accessed from overseas (US or Europe IP). I think that is some settings with the host of coolapk. I print the guide page as PDF and attached it for you.
Great post. I am using OnePlus 10 Pro running official Oxygen OS 13 (Android 13).
Although the phone supports 120Hz refresh rate, PUBG Mobile (Global) doesn't show an option for 90 FPS in its settings and the game runs at 60 FPS max. In the past, I could modify the ACTIVE.SAV file using a Hex Editor to unlock 90 FPS.
I used to use MiXplorer by Hootan in the past, but it doesn't work on Android 13. I tried using FV File Manage as explained in this post, and although I am able to see the files in Data or OBB folders, I am not able to modify them (for example, open the Active.sav file in Hex Editor or even copy it to another location in internal storage). I have attached a screen recording video demonstrating the above. Would be greatly appreciated if someone could tell me what I am doing wrong.
Record_2022-09-27-12-39-00.mp4
drive.google.com
FolderV said:
Download FV File Explorer
https://play.google.com/store/apps/details?id=com.folderv.file
May be this is the first APP that can visit other app’s exteral data file .
1. Open folder "/storage/emulated/0/Android"2. Click the"data" folder3. Select the application you need4. Click "Use this folder"5. Done! you can see the files.
Document in Chinese with images guide attached as PDF.
Click to expand...
Click to collapse
thanks.
Rabin John said:
Great post. I am using OnePlus 10 Pro running official Oxygen OS 13 (Android 13).
Although the phone supports 120Hz refresh rate, PUBG Mobile (Global) doesn't show an option for 90 FPS in its settings and the game runs at 60 FPS max. In the past, I could modify the ACTIVE.SAV file using a Hex Editor to unlock 90 FPS.
I used to use MiXplorer by Hootan in the past, but it doesn't work on Android 13. I tried using FV File Manage as explained in this post, and although I am able to see the files in Data or OBB folders, I am not able to modify them (for example, open the Active.sav file in Hex Editor or even copy it to another location in internal storage). I have attached a screen recording video demonstrating the above. Would be greatly appreciated if someone could tell me what I am doing wrong.
Record_2022-09-27-12-39-00.mp4
drive.google.com
thanks.
Click to expand...
Click to collapse
Actually MiXplorer's latest version supports Android 13, tested personally
shape93 said:
Actually MiXplorer's latest version supports Android 13, tested personally
Click to expand...
Click to collapse
Huh ... That's news to me. I am running the latest version - v6.58.6-Silver. And upon checking right now as I am typing this reply, I still don't have read-write access to OBB & DATA folders. I can see the files inside OBB & Data folders but I cannot modify them in any way or copy any file.
And sorry but what you said can't be true. I commented on playstore and the I got a reply from MiXplorer Team as well saying that it's a Android 13 limitation. Attached picture below
so what about sd maid, can it fix that problem?
Rabin John said:
Huh ... That's news to me. I am running the latest version - v6.58.6-Silver. And upon checking right now as I am typing this reply, I still don't have read-write access to OBB & DATA folders. I can see the files inside OBB & Data folders but I cannot modify them in any way or copy any file.
And sorry but what you said can't be true. I commented on playstore and the I got a reply from MiXplorer Team as well saying that it's a Android 13 limitation. Attached picture below
Click to expand...
Click to collapse
Just tested it. It is working for me too.
Version: 6.58.6-silver
I am at a loss. I don't understand why it doesn't work for me.
Rabin John said:
I am at a loss. I don't understand why it doesn't work for me.
Click to expand...
Click to collapse
MiExplorer does not work for me too. Literally anything including using a PC to access the files doesn't work for me, can't paste anything into the app data folders. Pixel 6a on Android 13. I might have to root the phone to be able to access the Android folder.
My phone is rooted A13 and still can't get access in Data/OBB folder -_-
Root does not mean that you will have access to anywhere just like that. You must have some application that wants there and process that
Rabin John said:
I am at a loss. I don't understand why it doesn't work for me.
Click to expand...
Click to collapse
update the new version, the previous version has some bug.
FolderV said:
Download FV File Explorer
https://play.google.com/store/apps/details?id=com.folderv.file
May be this is the first APP that can visit other app’s exteral data file .
1. Open folder "/storage/emulated/0/Android"2. Click the"data" folder3. Select the application you need4. Click "Use this folder"5. Done! you can see the files.
Document in Chinese with images guide attached as PDF.
Click to expand...
Click to collapse
This app is good for accessing/changing/transferring files and folders within the main app folder, but you can't actually rename the main app folder. Need this feature so when you clear data on said app, it won't delete the files and folders within. Long story on why I need this. It pertains to a game I mod for. In order to keep the modified files from reverting back to the original files, you need to rename the main folder, clear data and then rename the main folder back to the original. Hope you can figure this out. For now I have to use the files app from the PlayStore.
61zone said:
My phone is rooted A13 and still can't get access in Data/OBB folder -_-
Click to expand...
Click to collapse
ZArchiever is the best file explorer I have found. I used to use Root Explorer on Android 12 and it couldn't do things that ZArchiever could
Latest Mixplorer plays up for me too, sometimes prompts for access to /Android/data folder, but the folder listed is a previously accessed /Android/data/subfolder, not the root /Android/data folder...
I gave up and copied via adb shell
This "FV File Explorer" is actually the first app that I try that is capable of seeing the Android content.
But it seems it's RO on my Pixel 6a. I needed to get some backups back in a an app folder. But pasting seems not to work. Same goes for the PC. Can see the files on PC, but not able to paste something in these folders in "Android"
Someone who knows a workaround for this on a unrooted phone?
Edit:
"FV File Explorer" shows me a warning when trying to make a folder in "android". So looks it's still RO on my phone
FolderV said:
Download FV File Explorer
https://play.google.com/store/apps/details?id=com.folderv.file
May be this is the first APP that can visit other app’s exteral data file .
1. Open folder "/storage/emulated/0/Android"2. Click the"data" folder3. Select the application you need4. Click "Use this folder"5. Done! you can see the files.
Document in Chinese with images guide attached as PDF.
Click to expand...
Click to collapse
Um, hello? Total Commander does the exact same thing.
The only way is downgrade to android 12
Since android 13
Will block your acces to data&obb
I,m on my way to downgrade to 12
Doesn matter if all my data will lost
Wish me Luck Stranger
Fix Android 13 said:
The only way is downgrade to android 12
Since android 13
Will block your acces to data&obb
I,m on my way to downgrade to 12
Doesn matter if all my data will lost
Wish me Luck Stranger
Click to expand...
Click to collapse
You can't downgrade to Android 12 unless you use the special developer build or the A13 bootloader (although things won't run well) due to the anti-rollback protection in the A13 bootloader.
All you need to do to access Android/data on A13 is to use a file explorer that supports it, e.g. MiXplorer, as mentioned earlier in this thread.
This page explains in detail how you can Transfer Files in Data and OBB folder in Android 13:
How to access Android 13 Data and OBB folder & transfer files in them
In this comprehensive tutorial, we will show you the steps to access the Data and OBB folder in Android 13 and transfer files in them.
www.droidwin.com
All you need to do is download and install Files app:
Files - Apps on Google Play
This app is a shortcut to the file manager of the settings app.
play.google.com
A quote from the Comments section on Google Play:
This is the shortcut to the default Android" Files" app you never knew you needed. Not the one with the "file cleanup" feature. The one that magically appears sometimes, and when you go back to your apps list, it's not there. It's the 'admin' one that Google doesn't really want a lot of people to use unless THEY think it's appropriate. So to repeat, this is just a shortcut, to help you find the last file manager you'll ever need, and the one that actually came stock with Android.
Hello! I just rooted my Rog 6 with Magisk to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Well you must be in os12 same issue with me but in different device
senna33 said:
Hello! I just rooted my Rog 6 to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Click to expand...
Click to collapse
did you use a file explorer that supports root and try to change the permission on the file?
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
senna33 said:
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
Click to expand...
Click to collapse
i don't understand how a device is rooted if you can't modifie system files
nadejo said:
i don't understand how a device is rooted if you can't modifie system files
Click to expand...
Click to collapse
That's kinda how I feel about it. Root Checker Pro says I have root, I can run Su in a terminal and I get a popup asking for superuser rights when I use a function that requires root. I attached some screenshots from Root Checker Pro
The problem is that the partitions (system vendor and co) are only integrated as R/O and cannot be easily integrated as R/W
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
senna33 said:
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
Click to expand...
Click to collapse
ChrisFeiveel84 said:
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
Click to expand...
Click to collapse
I converted still same
Mr Hassan said:
I converted still same
Click to expand...
Click to collapse
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
ChrisFeiveel84 said:
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
Click to expand...
Click to collapse
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
If the partitions are not converted from erofs to ext4, it remains with ro because erofs cannot be mounted as rw
Mr Hassan said:
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
Click to expand...
Click to collapse
how did you try to convert the images to ext 4 without write protection?
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
There's thread available on xda but as i told useless
What u think as i said upper if device
Dev block mapper have full root
But not possible to edit system vend or anything
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
see this
OnePlus8:/ # mount | grep "dm-0"
/dev/block/dm-0 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-19"
/dev/block/dm-19 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-3"
and still i,m not able to edit these parts
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
ChrisFeiveel84 said:
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
Click to expand...
Click to collapse
Men see upper logs its converted to ext4
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
ChrisFeiveel84 said:
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
Click to expand...
Click to collapse
But in os10 os11 is possible
But don't know how to fix this os12
Is there anyway to remove write protection?