Hi there,
I'm programming something for Windows Mobile 2003. It basically removes and creates files around. One of the files it deletes is special file.reg, which is normally picked up during the hard-reset.
The file gets deleted using "DeleteFile" and very soon after, I force a hard-reset.
The problem is, the special file.reg is deleted from the file system tree, but it is apparently still available from the hard-reset.
I was wondering if there was another function I had to call to "flush" the file system? If not, I need to find a good trick to 1) enforce the file deletion (like rename first, then delete) and to 2) flush current ghost files left around.
The file system on those persistent drives are fat12 and/or fat16.
Thanks in advance for any input,
Simon
The hard reset returns the machine to its first power up state. If 'file.reg' was part of the original build, then the hard reset will restore it from ROM.
Also any programs you have installed to run on startup, will also be lost, so it is going to be a little difficult, if not impossible, to get rid of this file programatically.
Right, but I'm not talking about the ROM.
I'm talking about the persistent memory which are mounted as \Platform and \Application on this device. Those are FAT12 and/or FAT16, and files deleted (normally) do not come back.
In this case, the files are not coming back, they are not hidden either, but the hardreset process is able to pick them up somehow.
I mean, I call it the problem of the "Ghost files", because they are supposed to be nowhere, but they are found during during the hardreset.
(The files are not recreated, they are still not there, but their contents gets loaded. The info in them cannot be placed in ROM as it contains stuff that changes often)
They come back after a hard reset because during cold boot, they're being copied there from the rom or being created by the system. You may be able to delete them afterwards, but the only way to prevent them from being formed will be to re-cook the rom and stop them from being copied/created during boot-up.
The files DO NOT come back, it's gone, I cannot re-delete it. But somehow it is "read" by a program during the hard-reset.
This file is not part of the ROM, it's part of the persistent memory that doesn't get wiped out upon hardreset but is read-write.
I need to wipe out the ghost file that is stuck on the read/write partition... and I need a way to avoid these being created!
I understand that, but clearly the file is being created (or copied from rom) during cold re-boot, otherwise you wouldn't see it coming back. There isn't going to be any easy way to prevent that, unless you can re-cook the rom, or include some sort of user customization that would delete the files prior to using the device. There are lots of ways that the rom could create the files and put them onto persistant storage.
Hi Farmer Ted,
this is not a ROM issue, recooking the ROM will not help. The problem is a FAT12 or FAT16 filesystem that has bogus data in it.
The problem is most likely a bug in the program that reads the persistent folders... It probably reads it in a way that goes around the change made by DeleteFile()...
Changing that program is not possible (in ROM and I don't have the source, it's also necessary). I just need to make sure it can't find the file I've deleted on the persistent directory (not in ROM).
After 24 hours of search through the web I could not find a solution, many ideas but nothing seems to work, cause I can't find the exact reason:
What is the case? I try to copy a .zip to my device, the process starts and finishes after around 60%, I see the file on PC and device but the size does not fit (it is BIGGER!), md5 also. After a while the file vanishes completely and there is nothing......
R/W permissions should not be the prob, cause I can install apk, can delete files also and paste SMALL files unto the device (as it seems).
Someone with a little help, even without solution I would solve it by myself if I only knew, what's going on. THX :good:
Edit: Tried to connect with Kies3 and it started an update to latest firmware and Kies also failed to install something to storage
Update External storage
Well, internal works fine, but all files copied to ext sd still vanish after reboot and even after disconnecting usb from pc.
Hi,
I need to make an exact copy of a clean Nexus 5x motherboard's (mobo) memory. My phone was infected and I have not been able to get it clean. I know that there are many other file areas besides those copied in TWRP. I have used adb pull and push to copy /dev/block (All mmcblk0XX into mmcblk0XX.imgh files) from the clean phone mobo, and pushed them to the old infected one (mmcblk0 is supposed to be the wholeflash). It copied but it doesn't appear anything has changed. There was a bootup password on the old phone (mobo) but copying those files did not remove it. I then flashed all partitions in the google firmware download and it booted up like a clean new phone, but later went back to the password at bootup. I have had something like this happen a few times. I flash new firmware and somehow the old infected files are still there.
How can I REALLY wipe this phone (manually EVERY file from root / ) and copy over all the clean data from the new phone motherboard? I suspect that the infecter changed my bootloader and is making it persistent somehow. I have used TWRP and copied over the partitions many times. Not good enough.
Thank you.
The bootloader version is still an old one even though I have updated the firmware many times. it is BHZ10i and current one is BHZ11e!
I'M here just because of random, but maybe this unbrick method could help to fully reflash the phone?
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740/post63889395#post63889395
Use this tutorial to fix your phone.
Cheers!
I noticed a rather strange thing when trying to copy files to my 5T on my Mac with Android File Transfer. I was unable to create folders, and trying to write data resulted in errors (like again "can't create folder"). Some files present on the phone and visible in e.g. TotalCommander (or any other file manager) would not show up on my Mac. I then switched to my Win10 PC just to find out that creating folders was also giving me grief. /data lists most of the files, but some are missing. Also, there are a lot of devices (like HDDs) present (icon-wise). I thought the file structure might be knackered or there might be something going on with an app (I am rooted and use Magisk), so booted to TWRP to restore boot and system to find out if this would happen with a plain install as well. What can I say... TWRP also comes with MTP and this is working correctly. Booting into a clean OB3 again produces errors. This leads me to the conclusion that either something "broke" when upgrading e.g. OB2 to OB3, or OB3 (at least) is knackered when it comes to MTP.
Does anyone have similar/the same issues?
Hi Good day.
A few days ago I noticed that spotify started downloading my music into the SD memory instead of the external SD. Yesterday I did a couple of tests verifying that my apps had the permission (which they had, no change was made, it just stopped working that).
Both spotify and a file manager that I have indicated that everything was correct with the appropriate permissions.
I decided then to restore the Android to factory factory and it turns out that everything is the same. I can not delete or copy files to the external SD. Of course, I re-granted the permit as requested by the S.O. and nothing.
In fact, when I want to delete a file, for example, it does not send me an error message, everything seems to indicate that it is correct and done. When I return to the same folder, the deleted file is there.
In general, what I did was to restart the tablet between each step described.
If I do the same with the factory file manager, it works as it should.
Any ideas?
Thank you very much for the help
Details:
Model: SM-P600 (Galaxy
Android 5.1.1
Patch level 2016-07-01
Kernel 3.4.39-8544649
Build LMY47X.P600UBSDSB1
SE for Android status Enforcing SEPF_SM-P600_5.1.1_0052
I had at least one sd card becoming read-only.
It was near new and it happend during custom rom installation on a mobile, as the latest time stamps on files indicated. I think it was failure if the card's write state engine, which can happen any time, while failure of some of the internal 4kbyte blocks is more age related.
At least the device or rom didn't have the habit of destroying sd cards, which i initially feared...