Related
Hi, how can I delete a file in \Windows folder? it seems complaining that the file is in ROM, I had tried many way even using other File Explorer or via ActiveSync. None of them work.
How can I delete a file in \Windows folder in my Microsoft Windows Mobile 6?
Maybe Resco Explorer or Total Commander CE will help.
if it's built in the rom, you might be unable to delete that file.
Please be more specific: which file do you wish to delete?
Maybe you'd have to recook the ROM without that file.
Regards,
EquinoXe
Things built into the rom are "READ ONLY MEMORY" therefore cannot be deleted. if the file is only marked as system and readonly though you can change its atributes using total commander. just long click on item to bring up menu and go to properties. there you need to uncheck everything and delete
I had downloaded Total Commander and installed it, the checked file attributes are 'read only' and 'in rom'; so I guess the file shall be consider undeleteable.
Now I had to learn how to recook, any good guide how can I recook the ROM that I have?
similar problem
I downloaded some software and it came up as being faulty software. The file was a zip folder titled : res_ppc-custom.icons
I tried through my windows mobile device center to uninstall it, but it was never actually installed completely in the first place.
I then tried to delete the file a few times. Once directly from my pda, once through the device center and again through my pc windows explorer. All three attempts were unsuccessful.
How can I get rid of this thing?
Thanks in advance
perhaps you may want to check if the file being accessed by other software, easiest way is to soft reset and try to delete it.
That did the trick! Thanks so much
Move files to storage card
OK I want to move some files (not ROM) in Windows and keep getting error. For example Opera.exe is not marked as anything in properties yet I can't seem to delete the file. I did copy it to my storage card without any issue but can't delete the original from Windows directory. Any suggestions since Total Commander won't delete it. Will edit registry to find it on the Storage Card.
Deleting files in Windows folder
mynullvoid said:
Hi, how can I delete a file in \Windows folder? it seems complaining that the file is in ROM, I had tried many way even using other File Explorer or via ActiveSync. None of them work.
How can I delete a file in \Windows folder in my Microsoft Windows Mobile 6?
Click to expand...
Click to collapse
I have the same problem - I have colpilot.wm6ppc.cab in my Windows directory. It's 12.6mb, I don't want it, and it's taking up a lot of storage space. My phone is a T-Mobile MDA and it obviously came with CoPilot as an option, but I think it's really unfair that the cab is right there in the Windows dir and I can't get rid of it....
Any help gratefully received....
Cheers,
Ed.
The cab is cooked in as part of the rom; there's nothing you can do about it, except flash a custom rom (this is one of the main reasons people flash custom roms). Be glad it was installed as a cab and not as a full package-at least cabs are compressed are a single file.
Farmer Ted said:
The cab is cooked in as part of the rom; there's nothing you can do about it, except flash a custom rom (this is one of the main reasons people flash custom roms). Be glad it was installed as a cab and not as a full package-at least cabs are compressed are a single file.
Click to expand...
Click to collapse
I think the issue is not on the files in ROM.
I have the same problem. I've copied a file under Windows folder and after that I'm unable to delete it.
Strangely I'm able to rename it, which should mean that file is not in use, however deletion is not possible.
I've used TotalCommander, the built-in Explorer and also connected the phone via ActiveSync, but still nothing happens and access seems to be denied.
The exact message is "deletion error".
Any idea?
Thanks.
Cheers...
-nOra-
A very common problem with Windows explorer is reported on all Windows help forums. I've seen people complaining about problem with long path files deletion.
Some common problems with Windows Explorer people talk about:
- Doesn't allow to delete files with long path names
- Pops up error while deleting unwanted files or unnecessary files
- Errors like: Access denied, sharing violation, source in use etc.
I've found a very simple but smart solution for all these above mentioned common problems. A very simple but powerful tool to overcome these problems. Everyone who plays with the files must have this tool. Its compatible with all versions of Microsoft Windows.
johnylog.software said:
A very common problem with Windows explorer is reported on all Windows help forums. I've seen people complaining about problem with long path files deletion.
Some common problems with Windows Explorer people talk about:
- Doesn't allow to delete files with long path names
- Pops up error while deleting unwanted files or unnecessary files
- Errors like: Access denied, sharing violation, source in use etc.
I've found a very simple but smart solution for all these above mentioned common problems. A very simple but powerful tool to overcome these problems. Everyone who plays with the files must have this tool. Its compatible with all versions of Microsoft Windows.
Click to expand...
Click to collapse
Could you please tell us the name of this wonderfull tool, and how to have?
djulen said:
Could you please tell us the name of this wonderfull tool, and how to have?
Click to expand...
Click to collapse
Based on how he said it, I have to really wonder if he really does have such a tool...
badbwoydes said:
Based on how he said it, I have to really wonder if he really does have such a tool...
Click to expand...
Click to collapse
Use Total Commander to modify the contents of the \Windows directory.
Yes, but you won't be able to delete a ROM file anyway.
In the \Windows folder, you commonly encounter three kinds of files :
- Pure ROM files (can't be deleted nor renamed nor moved, nor even copied, but can be overwritten, consuming internal storage memory space in the process to store the new copy, that will become used instead) ;
- Files put there by installation CABs or else (can be freely deleted, renamed or moved, provided they're not currently used by a running process) ;
- Files put on top of previously existing ROM files, wearing the same name (deleting, renaming or moving them will thus make the original ROM file undertneath to reappear with its original contents and attributes).
Once you've understood that, you'll be more aware of what's cooking there.
ROM files can't even be copied, but you can use ROMExtractor to copy them elsewhere, in case you want to study them, or use them in your own ROM (useful to get up-to date versions from another HTC device to cook your own ROM).
Since ROMExtractor is a very minimalistic tool (you have to type in all the files names with their path, same for the target copy, all one by one !) manually extracting hundreds (even thousands) of files is a very tedious taks, I made a MortScript to automate the process in order to extract all those DLLs, EXEs, MUIs, etc. files that can't be directly copied from a phone's ROM.
On the other hand, you absolutely can't delete a ROM file to make room. Overwriting it with a file wearing the same name will jut result in actually adding the new file, thus consuming even more room. The new file will just be used instead of the original one (so you can still update or personalize the ROM).
As a direct consequence, the only way to get rid of unwanted ROM files or permanently replacing them with up-to-date ones is to cook a ROM and flash it to the device to replace the old one.
That's way how operating systems can become better and better, and save space at the same time.
And no, Windows Mobile isn't dead : I'm not quite finished with fixing it until it's perfect, so it's not over yet. LOL
if i edit my build.prop with astro, on a reboot the changes are lost, the file is marked r-w, so something altering it on bootup, anybody know where the source comes from??
Download Root Explorer and use that. Trust.
tried that, it keeps getting overwritten with some king of backup.
mallard729 said:
tried that, it keeps getting overwritten with some king of backup.
Click to expand...
Click to collapse
If that's the case, then it's a problem specific to the ROM. I haven't tried it on my TP2 but it worked flawlessly on my G1.
Lemme take a look once I get a second.
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
norpan111 said:
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
Click to expand...
Click to collapse
Because it does not excist in winmo. It only excists in android.
I tried Root Explorer and it workers . I use latest froyo build with lower incall volume kernel .
Can somebody tell me when I delete apps in system/apps folder I delete from data.img or from system.ext2 ?
Same here, I change my build.prop file or replace it and it gets overwritten.
Using the build.prop for protected apps but can't get it to stay.
I am using the latest BLAZEN build from PPCGEEKS/Reefer.
Being an Ext2 file instead of sqsh I figure this would have worked flawless.
I'd really like to download logmein, gbahours, paypal and a few other protected apps. I can't without fixing this build.prop file....
OR
Find some way to get a working fingerprint Google has already approved.
Glad to see I'm not the only one looking into this I have the same problem in my android OS - different phone, but same custom OS. Hopefully this thread won't die - if I ever figure it out I'll be sure to post here as well
Hey, guys. I dropped my phone recently and got a new one from Asurion and I am trying to extract my game save files from Gun Bros because my back-up with Titanium restored me to level 12 and I was almost at level 40 before I got my new phone. I know.....I'm a f*cking nerd.
Anyway, here's where I'm at:
I downloaded unyaffs and the cygwin1.dll and was was able to successfully extract the data.img contents into the desired folder on my computer. Upon navigating through the data folder, I find two folders titled com.glu.android.gunbros_free and com.glu.android.skob2_free both of which contain a folder inside of it called "app_save" that has a number files.
I thought it would be as easy as finding the same folders on my phone and simply replacing the contents with the files I just pulled from my NAND. However, when I navigate to the data folder in my phone, I can't find these file names. I tried searching for them using control-F by typing the name of the file and searching the the entire SD card, but it turned up empty.
I'm sure I am missing a step here somewhere. Can any of you advanced users point me in the right direction? Sorry if my question is missing info, but honestly, I don't know wtf I'm doing. I'm trying to make something out of nothing here.
I REALLY don't want to start over in the game. lol Any help would be greatly appreciated.
Edit: I'm using these as guides:
http://www.htcblaze.com/how-to-extractingaccessing-nandroid-backup-img-files/
http://dus.org.pl/forum/t-219620/recovering-data-from-nandroid-backup
In the second link, the last step says:
- you can list content of this database using sqlite3 command line tool or presumably (haven't tried it myself and it may depend on what application data you are recovering) copy it back to your Android device running current ROM (rooted phone may be needed).
However, I can't get that command to work. I'm not sure if that helps any, but I thought I'd throw it out there to offer more info.
Oh, I thought of something I wanted to add in case it will be easier. The phone that created the NAND I am trying to pull the files from is still available to me with the game at the stage that I left it in. Maybe I should try replacing the game files on my phone with the ones from that phone?
In theory, it sounds easier than what I'm trying to do here, but does anyone know if that will work?
bumpity-bump.....
Anyone?
So I am trying to port ICS to our kaisers, but the problem is I have very limited developer knowledge (actually none). As a result I am trying to port the HTC Wildfire's ics builds. But the only things I can do, is:
extract the system file out of the Wildfire build
delete a couple of files to get in down in size (the wildfire has more RAM than the Kaiser)
add the sysinit.rc file to the system file
recompress the system file to androidinstall.tar
And the furthest I have come with this method is seeing the boot logo flikkering while I still saw some of the white code on the screen.
The matter of the fact just is, I REALLY WANT TO LEARN HOW TO BUILD MY ANDRIOD BUILDS, but I don't have the knowledge or time to exactly learn the java code. So as a result I really just want to know what the keypoints are? CAn somebody please point me in the right direction?
** As an example: when you open the system file of an android build you get all kinds of folders, and from most of them I don't know what they mean, like from bin, etc, framework, lib, usr and xbin I haven't got the slightest clue of what they are there for.**
**Also I don't know what there should be changed in the build.prop and the sysinit.rc when you are trying to a build of another device on the kaiser. Are the build.prop and sysinit.rc dependent from the version of Android you are giong to run or are the dependant of the kind of device you're gonna run it or are they dependant of both??**
hom.hom said:
So I am trying to port ICS to our kaisers, but the problem is I have very limited developer knowledge (actually none). As a result I am trying to port the HTC Wildfire's ics builds. But the only things I can do, is:
extract the system file out of the Wildfire build
delete a couple of files to get in down in size (the wildfire has more RAM than the Kaiser)
add the sysinit.rc file to the system file
recompress the system file to androidinstall.tar
And the furthest I have come with this method is seeing the boot logo flikkering while I still saw some of the white code on the screen.
The matter of the fact just is, I REALLY WANT TO LEARN HOW TO BUILD MY ANDRIOD BUILDS, but I don't have the knowledge or time to exactly learn the java code. So as a result I really just want to know what the keypoints are? CAn somebody please point me in the right direction?
** As an example: when you open the system file of an android build you get all kinds of folders, and from most of them I don't know what they mean, like from bin, etc, framework, lib, usr and xbin I haven't got the slightest clue of what they are there for.**
**Also I don't know what there should be changed in the build.prop and the sysinit.rc when you are trying to a build of another device on the kaiser. Are the build.prop and sysinit.rc dependent from the version of Android you are giong to run or are the dependant of the kind of device you're gonna run it or are they dependant of both??**
Click to expand...
Click to collapse
ICS on Kaiser? Big mistake...
I know see that you have gotten it right about ics on the kaiser, but I still want to develop my own builds for the kaiser, gingerbread builds, then. So can anyone shed their light on helping me into the right direction of creating my own build from the source or porting a build from another (htc) phone??
if you want to port android start from this - take system from similar device (example click or wildfire) and follow directions from this thread http://forum.xda-developers.com/showthread.php?t=996431. Method from post #3 definitely works for Froyo and Gingerbread. If you find problem really helpful is using logcat and DDMS.
In my opinion porting AOSP ICS for Kaiser at the moment is a waste of time. Will be more problematic and you never will achieve a fast, fully operational system. BUT with Cyanogenmod9 situations can be change...
Almost there....
I have used the Official Cyanogenmod Stable release from the HTC Wildfire to port (as a test) and I have used Scoot CyanogenMod 7.1.0 RLS3 (Gingerbread 2.3.5) [07/08/11] to paste the files from into the CM for the buzz.
Michga said:
i have this one...
I'll look into the specs of wildwire and let you know if my steps would work. Just kinda busy this holiday season. But my steps were pretty simple. We have to know if this is an odex'd or deodexed version. If it is odexed version, it would be nice to deodex it first. I use Android kitchen from dsixda. The only part we need is the system folder. It has apps, etc, lib, bin and the rest...basically under the system we need to put Fresh Froyo (FF) files build.prop and sysinit.rc and move it to wildfire's system folder (these two files are required for booting)then under /system/etc you need to grab vold.conf(1) from (FF) and move it to wildfire's /system/etc. Ooops..I'll have to get back to you. Dinner time BTW, vold.conf is what loads SD card. I looked at the specs of wildfire and not sure if it works since it has a 7225 processor and 5 megapixel but it's worth a try. Then /system/etc, copy ppp and passwd from liquid's kernel and put it in that folder (like permissions)(2). Compare the folders with Fresh Froyo and if something is missing from Fresh Froyo to wildfire. Copy wifi folder (don't copy ppp folder, delete it if wildfire ROM has it). Now lets go to system/lib. Copy the following files from Fresh Froyo to wildfire libaudio.so, libaudiopolicy.so (audio drivers) libcamera.so libcamera_client.so libcameraservice.so (camera drivers) libgps.so (gps driver) libhtcgeneric-ril.so (phone driver) libicudata.so. Then copy egl folder to hw folder and bluez-plugin folder. Now go to system/modules and delete all files and get modules from l1q1d's latest kernel(3) and put it in the system/lib/modules folder. Then go to system folder and copy bin folder, media folder, xbin and usr folder to wilfire system. That's it. Save the system folder as androidinstall.tar and see how it goes. Goodluck.
Click to expand...
Click to collapse
So I have tried the method of post 3 of the link, but all I get is the kaiser to boot in Android, but it never stops booting, the infinite bootloop. I believe the cause for this bootloop to be the sheer size of the androidinstall.tar(as jholtom already explaines in his post in this thread). It at its least becomes 150 mb. I can't get it any smaller, because I need to add the xbin file of Scoot's Cyanogenmod 7.1 for Kaiser, which is 67 mb of size. While the official Cyanogen Wildfire rom also is about 67 mb of size.
Also some other problems
(1)vold.conf: I can only find vold.fstab does this matter?
(2)how do i extract passwd from liquid's kernel? And do I need to put this in the permissions folder?
(3)Instead of the latest files as posted by Michga, I have used the files from the update.zip provided by Scoot in his kernel with separate cache thread: http://forum.xda-developers.com/showthread.php?t=1152219
You need strip the system as much as possible. cut out the unnecessary applications that take space and are not required to work (example: radiofm, rom manager, thememanager), tts voices, rings even some libraries - try to compare catalogs from Scoot_CyanogenMod_7.1.0_RLS3 and wildfiresystem. Strip unnecesary files, copy all the missing files. If your androidinstall.tar reach size below 100mb should be ok with standard partitions. But you can always enlarge the partitions in atools.
What do you mean that xbin have 67mb? It have about 7mb
As you can see Michga wrote this for Froyo so some files will vary. (1) copy only volf.fstab (2) may be unneeded for scoot's kernel- i'm not copy this and system works (3) you can use files from scoot 7.1 RLS3 - these are the same modules as in the update.
Install the android sdk on computer, run DDMS and plug the Kaiser. You will then be able to see what at the time the phone is doing and what is causing the problem.
Sorry for my english
Well, also the strangest thing is that I redownloaded Scoot_CyanogenMod_7.1.0_RLS3 build from this thread, http://forum.xda-developers.com/showthread.php?t=948134, and extracted the file to my desktop and the file is 148 mb in size of which the xbin folder is 69.6 mb in size. How is that possible? I am using Windows 7 x64 and I am extracting the file with Winrar. And when I use 7-zip to get the system file back to androidinstall.tar, this file is also 148 mb, BUT THIS FILE I AM ABLE TO INSTALL....
I am using 7zip only (also Win 7 x64) and extracted RLS3 have 84.3MB. Strange...
hom.hom said:
Well, also the strangest thing is that I redownloaded Scoot_CyanogenMod_7.1.0_RLS3 build from this thread, http://forum.xda-developers.com/showthread.php?t=948134, and extracted the file to my desktop and the file is 148 mb in size of which the xbin folder is 69.6 mb in size. How is that possible? I am using Windows 7 x64 and I am extracting the file with Winrar. And when I use 7-zip to get the system file back to androidinstall.tar, this file is also 148 mb, BUT THIS FILE I AM ABLE TO INSTALL....
Click to expand...
Click to collapse
Impossible, you can't install 148 MB file because System partition on Kaiser is just 120 MB!
So my first problem with the immens build sizes have been solved by using 7zip for every step in my android adventure instead of Winrar.
But know the real problem the booting problem. I ran ddms and the conclusion I get is:
system_process Audiosystem AudioPolicyService not published, waiting....
....
....
HTC Acoustic can't open /dev/htc-acoustic -1
AudioHardware Could not set acoustic parameters to share memory -1
I already googled this problem and the solution is supposed to be to create an android dummy audio driver, but as I said already my knowledge is really limited. So i don't know how to create an android dummy audio driver.
**I also uploaded the warn screen of the ddms...**
did you copy libaudio.so, libaudiopolicy.so (and i'm not sure now - libaudioflinger.so?) from scoots build?
First of all, THANK YOU!!!!
**I just needed to copy all the libaudioxxxx.so files from Scoot's build to the Wildfire's build.**
I am able to boot Zerorom 1.0 from the HTC kaiser now. But there are still a couple of quirks in the build, like the missing statusbar, the not working wifi and the screen looks like it has the wrong panel type in this build. While with Scoot's build it's A-ok.
Do you have logs from ddms?
Maybe you cut too much. Of course you adjust build.prop to our phone. To resolve graphic problems make sure that you still have SystemUI.apk and replaced folders hw and egl from scoot's build. To wifi make sure that you replaced in etc: firmware and wifi folder. If this not help swap libhardware-legacy.so
These are the files of the ddms log and the files which I used to port the official Cyanogenmod release of the HTC Wildfire to the HTC Kaiser. The problems are a flikkering screen it goes on and off all the time, improper (or actually none proper) detection of touch and no wifi.
**I needed to separate the files I copied into two separate folder, system1 and system2, because otherwise I couldn't upload it to the site. I hope that this gives a proper insight in what I have exactly done. Before I copied this files, I deleted the original ones from the Wildfire's build.**
well... What am I to do with it? Download zerorom, merge with this and see what's wrong? I dont know what you do to get tar smaller and what contains folders from porting system. Im think that You better create a new thread called example Zerorom alpha port 0.1 and upload androidinstall.tar to mediafire or somewhere. Then I or someone else see or flash this to phone and tell you what is missing and why libskia.so and launcher still crashing
I've been watching the progress here and I have a few things to point out.
What if the panel size in the kernel is correct, but the screen is "over-drawn"? Maybe ICS doesn't have an option to draw to a screen with a 320x240 resolution? This would explain the status bar and launcher issues. Try rewriting the kernel with the highest resolution (480x328 I think?).
And about the WIFI issue, did you remember to copy the .ko file over to the new build and add the update?
I Know I'm pissing in the wind; I had less luck getting Honeycomb ported from the Wildfire to the Kaiser, so this is looking interesting. You could strip to the basics and just replace things one at a time like I did and see what happens.
PoXFreak, if I good understand this
hom.hom said:
I am able to boot Zerorom 1.0 from the HTC kaiser now. But there are still a couple of quirks
Click to expand...
Click to collapse
he wants to port zerorom from wildfire. And this is just 2.3.7(cyanogenmod) with few applications changed to only looks like ICS. So it shouldn't be these problems with porting gingerbread...
Same rules apply: If the original rom's apps require a resolution higher than what's provided, there could be overscan or "over-shoot" of the original screen into unseen parts of the screen.
As far as the WiFi issue, the wifi.ko file from Scoot's 2.3.5 CM "should" work, but I have not tested it myself.
I do have an unused Kaiser witha good screen and only 2 bad blocks if he wants help with it. I would need all the files he's working with in a tarball posted to mediafire or some other file hosting site.
Im not sure whats in the guide you are looking at and quite frankly I dont feel like looking, but a few of us many moons ago were working on Sense Roms. One trick we used was stripping the system folder of its apps and placing them in a new folder "app_s" in data then symlinking /data/app_s to system/app at boot time. This was one way of shrinking you system files. I also managed onced instead of using data/app_s I used sdcard/app_s however this slows things down a tad but it worked. We eventually gave up on sense roms cause the sense widgets would not work properly and the entire rom was extremely laggy. Good luck with ICS If you happen to get it running I will install it for ****s and giggles however I no longer use this phone, and havent for several years but I still have it and it still boots up
hom.hom:
What is the total size of this build?
Could you not move apps from /system/apps to /data/apps?
What about swapping libskia.so and install a different Launcher from another build?
Ive been trying forever to figure this out, so here is my problem.
I'm trying to modify the The textures (atlas.png) and the sounds of the popular game Flappy Bird but every time i try to install the newly modified apk i get the Application is not installed message and i am trying everything possible i find on this forum but i cant find a solution.
The way i modified to apk:
1. open the apk in 7zip
2. make the new files it Photoshop and audacity (made sure i saved in the right file type)
3. replaced the old files with the new ones
4 saved the apk and tried to install it on my phone (didn't work got the application not installed)
How i got the apk
1. went to android/data/apps/Flappybird.apk
Second way i tryed to install it:
1 copied the new apk to the directory i used above
2 restarted my phone
3. the app got automatically "deleted"
I need help plz
PizzaBelly said:
Ive been trying forever to figure this out, so here is my problem.
I'm trying to modify the The textures (atlas.png) and the sounds of the popular game Flappy Bird but every time i try to install the newly modified apk i get the Application is not installed message and i am trying everything possible i find on this forum but i cant find a solution.
The way i modified to apk:
1. open the apk in 7zip
2. make the new files it Photoshop and audacity (made sure i saved in the right file type)
3. replaced the old files with the new ones
4 saved the apk and tried to install it on my phone (didn't work got the application not installed)
How i got the apk
1. went to android/data/apps/Flappybird.apk
Second way i tryed to install it:
1 copied the new apk to the directory i used above
2 restarted my phone
3. the app got automatically "deleted"
I need help plz
Click to expand...
Click to collapse
try to decompile the apk with Toolalite
Hey guy !
Basically i've an other problem, i also want to modify Flappy Bird, but i succeed to install the midified apk, in fact it's very simple you just have to sign the apk with apk multi tools for instance tell me if it works please
Bye
Thanks
Hi
Thanks for the info submitted
Regards
Decompile the apk and recomple it