What is the preload folder for? Most of the APKs in it are also in the system folder. But the system folder has the corresponding odex files that come with the APKs. Is it safe to delete the ones in the preload folder?
Sent from my GT-N7000 using Tapatalk 2
I delete multiple applications preload before installing the ROM and never had any problem, I have done over 10 ROMs. You can delete without fear.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And you can delete to system/app too :good:
I have no intentions of un installing any of my apps. I'm just wondering if deleting the APKs in the preload folder won't affect what's already installed in my phone.
Sent from my GT-N7000 using Tapatalk 2
l0rd_almighty said:
I have no intentions of un installing any of my apps. I'm just wondering if deleting the APKs in the preload folder won't affect what's already installed in my phone.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
There will not.
l0rd_almighty said:
What is the preload folder for? Most of the APKs in it are also in the system folder. But the system folder has the corresponding odex files that come with the APKs. Is it safe to delete the ones in the preload folder?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
It could be mostly because you came from a rom that used preload partition and before installing the new rom, you did not format preload partition.
nokiamodeln91 said:
It could be mostly because you came from a rom that used preload partition and before installing the new rom, you did not format preload partition.
Click to expand...
Click to collapse
I did. Formatted systems folder as well. Even used philz cleanup tool via his kernel just to make sure.
Came from the Ultimate rom based of the JB leak. Formatted the system folder, the preload folder. Wiped dalvik and cache. Then did the clean up using philz kernel.
I then installed the official German JB using PC odin and rooted once more using philz kernel.
i have not installed the stock rom.. so you mean to say on stock rom the apps are there in both preload and system folder?
nokiamodeln91 said:
i have not installed the stock rom.. so you mean to say on stock rom the apps are there in both preload and system folder?
Click to expand...
Click to collapse
Not all but some of them are. One example is the SecGallery2_Galaxy.apk. I can see it in both the preload and the system folders. A couple more examples are SecSettings.apk, the SecEmail.apk and a few more.
Reason I'm asking is I wanted to install a few mods like the Airview and the Lockscreen shortcuts, both of which were excluded in the official JB release for some reason. Instructions that were mentioned in thier respective threads here in XDA is to install either the preload or the system version of the zip files via cwm. I have to choose one or the other "depending" on where the original APKs are. That's where my problem comes in. For the Airview mod, I have the SecGallery in both the preload and the system folders. So I want to know how to figure out which one of those folders I should be using for the mods that I mentioned.
I installed the stock odexed rom and used the xml to permissions folder and the gallery apk to system. Change permissions and air view works.
nokiamodeln91 said:
I installed the stock odexed rom and used the xml to permissions folder and the gallery apk to system. Change permissions and air view works.
Click to expand...
Click to collapse
I'm going to try it out when I get home.
They are in preload as the system partition is no longer big enough to handle jb roms efficiently. Preload is now just an extension of system without the need to repartition tue phone
The equivilant app in system folder is jusy a placeholder apk its 1kb and contains a link to the preload app.
You can move some to system if you wish but you may face issues as the partition becomea fuller.
Sent from my GT-N7000 using xda premium
But that's not what I see in the stock odexed rom. In that there are 2 gallery apk one in system/app of 12.07MB and one in preload of the same size.
nokiamodeln91 said:
But that's not what I see in the stock odexed rom. In that there are 2 gallery apk one in system/app of 12.07MB and one in preload of the same size.
Click to expand...
Click to collapse
Same with me. 2 of the same size in each of the folders.
Sent from my GT-N7000 using Tapatalk 2
Re: Preload and system foderPreload and system foder
To understand this better,you need to know about symlink in linux os.
Symlink is like shortcut to a certain file in windows.Symlink actually creates a path to original file in a specific directory.
In roms,preload/symlinks/ is symlinked to /system/apps.Linux(also android) shows symlinked files in both source directory and also the destination directory creating an *illusion* that the file exists in both the directories.But in reality,the file exists only in source directory which is /preload/symlinks in this case.The symlinked files in /system/app are just a generic pointer to the files in preload.
Deleting symlinked file in /system/app will also delete original file in /preload and vice-versa.
Long story shortreload is just an place holder for extra apps which is accessed via shortcut in system/apps.(This not an absolute/accurate answer)
Sent from my GT-N7000 using xda app-developers app
Thanks Vijai for the explanation.. i understand that these are pointers.. but should be of the same size as the one in preload ? In deodexed roms there is only one file but in odexed .. there are 2
nokiamodeln91 said:
Thanks Vijai for the explanation.. i understand that these are pointers.. but should be of the same size as the one in preload ? In deodexed roms there is only one file but in odexed .. there are 2
Click to expand...
Click to collapse
It is not two files of same size actually.After symlink,the os mirrors the atributes and properties of the file from preload to system.So we feel that the file actually exists in two places of same size.But it is not.It only exists in preload.
Sent from my GT-N7000 using xda app-developers app
Ok this makes sense.. But if I pull the one from system/app using adb, should I get the link or the entire app? I currently get the app.
nokiamodeln91 said:
Ok this makes sense.. But if I pull the one from system/app using adb, should I get the link or the entire app? I currently get the app.
Click to expand...
Click to collapse
The app.You get a file(which represents error) only if the symlinked file/directory goes missing.That means,if 2 dir are symlinked and the source dir goes missing,the symlink turns into a file which is not the case if a file is missing inside the directory.But if the symlink is between files,Symlink is broken if the source file goes missing.
Have you got ubuntu on your pc?When try symlinking and experiment with it,It will answer most of your doubts .Actually ubuntu shows it more graphically than android which does gets u confused
Sent from my GT-N7000 using xda app-developers app
Related
Although I admit I have not yet fully grasped the concept of creating custom roms, the fact that all ROMS has a PDA file (collection of the rfs files and bins),
is there any way to edit the PDA file and remove any unwanted apps contained before flashing it to my phone?
I would recommend to pm a developer, with preinstalled thanks and apologies, they are all very helpful if you are polite, articulate, and appreciative
Sent from gt i9000 insanity 8.5/fugumod
Customs Roms are zip files. open them with winzip/wanrar.
Remove and add apk files to system folder if they are system apk files, remove/ add
files to data folder. They are your files to be installed automatically.
Put things in sdcard folder, these will be copied diecetly to sdcard. I flashed more than 100 times this way, no problem until now. I remove nearly 40-50 files from system folder, and my launcher, alarm, office...user apk files to datat folder. When the flashing ends, i have a fresh rom with installed many programs.
There is even a script file you can edit and change your language lets say.
Phonesetupwizard begins with your language.
@yken wow thanks a lot for that detailed instruction, it never occurred to me that you can modify it to that extent, i will be trying that asap ^^
Sent from my GT-I9000 using XDA App
lockzackary said:
@yken wow thanks a lot for that detailed instruction, it never occurred to me that you can modify it to that extent, i will be trying that asap ^^
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
All that happens if something is wrong is usually phone fails to boot or boot loops .
Update zip tool to zip and sign custom roms .
http://forum.xda-developers.com/showthread.php?t=717437&page=21
jje
Flashing new ROM use CWM!
But some update (~ 3-4MB), can i use Root Explorer to copy and replace old file (in "app", "system => lib",...)?
Hate flash must wipe all!
Is replace file is safer than flash ? (flash not wipe cause bootlop)!
xenv1 said:
Flashing new ROM use CWM!
But some update (~ 3-4MB), can i use Root Explorer to copy and replace old file (in "app", "system => lib",...)?
Hate flash must wipe all!
Is replace file is safer than flash ? (flash not wipe cause bootlop)!
Click to expand...
Click to collapse
Yeah you can do it via root explorer but, why u told flash cause bootloop?? if u flash a Rom u MUST wipe data.. but if it's only a patch (like beats audio) you don't
What do the root explorer show is ROM or internal memory?
Sent from my GT-S5570 using XDA
No need to wipe always.. if the update is small, just flash it without wipe. You can also wipe cache if needed.
Sent from my GT-S5570 using XDA
What different between ROM and internal memory?
Sent from my GT-S5570 using XDA
xenv1 said:
What different between ROM and internal memory?
Sent from my GT-S5570 using XDA
Click to expand...
Click to collapse
Rom: system rom like folders system, bin etc..
Internal: your apps data that are stored in internal memory of phone
Inviato dal mio GT-S5570 con Tapatalk 2
suppose you are copying some files and there are some critical file being replaced and while copying mobile restart and copying was not done then there are chance of bootloop
in some update packages permission commands are written which cannot be done by just copying (an example of this is while updating su binary with superuser app it shows the progress, in somewhere there it is written that changing permission of file, and if you do not do this and just copy the su binary to /system/xbin you will loose your root access
odexed app cannot be installed just by copying they need to be flashed
so flashing is better than copying
always use cwm that is safer than copyng and replacing files or folders
My Galaxy Note is running Classic Rom V6 ICS and I just downloaded a .zip theme pack. How do I go about?
Usually you run the pack and it installs, if it's third party, you need to extract and place into the system file.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Usually you run the pack and it installs, if it's third party, you need to extract and place into the system file.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I tried exploring the zip file and for every type of theme, there is an app folder and a framework folder filled with .apks. Does that mean I can run
the apks in any order for a chosen theme?
No. usually there are 2 folders
apps = you hve to place these apks in system/apps folder a d change permission to rw-r--r--
framework = place the *-res.apk in system/framework folder and change permission as above.
but. make sure if you replace any file, you keep a backup of that so that it something does not work, you can revert back
nokiamodeln91 said:
No. usually there are 2 folders
apps = you hve to place these apks in system/apps folder a d change permission to rw-r--r--
framework = place the *-res.apk in system/framework folder and change permission as above.
but. make sure if you replace any file, you keep a backup of that so that it something does not work, you can revert back
Click to expand...
Click to collapse
Thanks you
Hi folks,
an other very short tutorial for the people (cooks), who do not know how to use the preload (hidden) partition and symlink system apps to it.
Some basics on preload-partition and why you should use it:
We have the so called 'hidden/preload partition' (mmcblk0p12) on our device. Besides the system partition with around 840 mb space, this hidden partition has additional 500 mb...this 500 mb were thought from sammy in the beginning mainly for their own crap like gamehub apps or learning hub and so on. But as system partition is on the edge right now with jelly bean they also use it for placing system apps inside --> the reason is that 840 mb in system is far to less for all files!
Usually most cooks just transfered system apps to data partition (located on your usb storage) to get out of this mess. This method with using hidden partition just gives great opportunity to keep your system partition smaller and you can transfer apps to it which you can not move to data! Your device will probably also perform faster with less space used inside system-partition. Our kernel dev Phil also made it possible now to backup/restore preload-partition within nandroid on his newer CWM-recoveries --> so now you can do a full backup/restore including this preload-partition....before it was not possible!
How to symlink system-apps to preload-partition:
just take the app 'Notepad++' (google for it) on your PC/Laptop, open it, create a new file and put the following inside ('nameofapp.apk' is just an example for any app you wanna symlink):
Link: /preload/symlink/system/app/nameofapp.apk
Click to expand...
Click to collapse
save and close as 'nameofapp.apk' --> this is the one to put inside /system/app to symlink to the original one you put inside /preload/symlink/system/app.
Now do this steps with every system app you wanna symlink...
This is the manual way to this, though I know scripts can be used to do these steps automatically... But this way you at least get a basic understanding how it works!
I won't tell you how to push apps to preload-partition inside CWM-flashable ROM in general, cause this is basic knowledge when you wanna cook a ROM - but you could download any ROM already using this method and look inside 'META-INF\com\google\android\updater-script' and you will know how to do this.
Thanks for the guide mate. I'm sure this will help a lot of us out
In dsixda's Kitchen the symlinks are automatically generated with a few lines of code in updater-script.
I'll will try to extract them when continuing to work with my Rom/Tutorial, so non-kitchen-builders can user it in their updater-scripts.
Have to say: it's very nice that you share your knowledge and experience with us, eybee. Thanks for that.
Thanks for the knowledge.
You're the man..
Sent from my GT-N7000 using Tapatalk 2
Hey eybee. Nice guide.
One question. I'm using dsixda kitchen to build a rom but the zipaligning falls over when it reaches the nameofapk.apk text file. Anyway round this?
Sent from my GT-N7000 using xda premium
maskerwsk said:
Hey eybee. Nice guide.
One question. I'm using dsixda kitchen to build a rom but the zipaligning falls over when it reaches the nameofapk.apk text file. Anyway round this?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
What do you mean by "nameofapk.apk"?
Maps.apk? (Then I know what you mean).
eybee won't give explanations for that because he doesn't use the kitchen.
ThaiDai said:
What do you mean by "nameofapk.apk"?
Maps.apk? (Then I know what you mean).
eybee won't give explanations for that because he doesn't use the kitchen.
Click to expand...
Click to collapse
yeah for example i moved MusicPlayer.apk to preload and created notepad++ file for MusicPlayer.apk which i put in system/app.
but when zipaligning apks in kitchen, when it reached the system/app/MusicPlayer.apk it fails
maskerwsk said:
yeah for example i moved MusicPlayer.apk to preload and created notepad++ file for MusicPlayer.apk which i put in system/app.
but when zipaligning apks in kitchen, when it reached the system/app/MusicPlayer.apk it fails
Click to expand...
Click to collapse
of course i fails...you can not zipalign a symlink
just zipalign before, when all apps are still in /system/app and move to /preload afterwards
eybee1970 said:
of course i fails...you can not zipalign a symlink
just zipalign before, when all apps are still in /system/app and move to /preload afterwards
Click to expand...
Click to collapse
The problem is explained in the kitchen itself. You get a warning to move all apps first before de-odexing.
But I didn't get any mistake like this when zipaligning - I think the related script checks if there are symlinks. I move the apps before the de-odexing step in the Advanced options but not when zipaligning. So maybe he has some other problems.
ThaiDai said:
The problem is explained in the kitchen itself. You get a warning to move all apps first before de-odexing.
But I didn't get any mistake like this when zipaligning - I think the related script checks if there are symlinks. I move the apps before the de-odexing step in the Advanced options but not when zipaligning. So maybe he has some other problems.
Click to expand...
Click to collapse
As explained: he is trying to zopalign the symlink in /system/app which of course fails (it is just a link named .apk!)...the original app he already moved to preload
eybee1970 said:
of course i fails...you can not zipalign a symlink
just zipalign before, when all apps are still in /system/app and move to /preload afterwards
Click to expand...
Click to collapse
Awesome. Thats what I was after
Sent from my GT-N7000 using xda premium
This is excellent! We can now take control of an extra 500mb that Samsung thought we would never have access to
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
This is excellent! We can now take control of an extra 500mb that Samsung thought we would never have access to
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
this partition is well known since Galaxy S2 (paulobrien was talking about it back in Aug 2011)....but was not really needed til now
eybee1970 said:
As explained: he is trying to zopalign the symlink in /system/app which of course fails (it is just a link named .apk!)...the original app he already moved to preload
Click to expand...
Click to collapse
Using a simple more powerfull line in update script
Code:
symlink("/preload/symlink/system/app", "/system/app");
this symlinks the whole folder to system/app so all that is in preload is also visible and active in a linked system/app folder.
This removes the whole functionality of the /system/app folder though but you have a very fast and clean system saves a lot of typing/ copypasting though
Robbie Hood said:
Using a simple more powerfull line in update script
Code:
symlink("/preload/symlink/system/app", "/system/app");
this symlinks the whole folder to system/app so all that is in preload is also visible and active in a linked system/app folder.
This removes the whole functionality of the /system/app folder though but you have a very fast and clean system
Click to expand...
Click to collapse
yes, I saw in your script already
eybee1970 said:
yes, I saw in your script already
Click to expand...
Click to collapse
Always finding ways to improve :highfive:
So there is NO /system/app folder in my rom
@RobbieHood. How would you do in user space? Using linux commands in terminal for example?
Sent from my GT-N7000 using xda app-developers app
Robbie Hood said:
Always finding ways to improve :highfive:
So there is NO /system/app folder in my rom
Click to expand...
Click to collapse
for all: but there will be one after installation, but just containing symlinks...
eybee1970 said:
for all: but there will be one after installation, but just containing symlinks...
Click to expand...
Click to collapse
well not exactly
The folder is linked so when you open it via /system/app or any browser you are virtually in /preload/symlink/system/app with the real apks
its somewhat the same principle as the sdcard on galaxy s3 which is linked to /data/media and does not have its own partition
Robbie Hood said:
well not exactly
The folder is linked so when you open it via /system/app or any browser you are virtually in /preload/symlink/system/app with the real apks
its somewhat the same principle as the sdcard on galaxy s3 which is linked to /data/media and does not have its own partition
Click to expand...
Click to collapse
Ok...this is the correct way to say it
Just did not want anybody coming in here then and say "hey, when i open with Root Explorer i still can see /system/app and all apps inside..."
I want to save some space on the internal storage, and since tha system partition is enormous, on 4.3 I integrate the updates into system/app. For example If Facebook gets an update I delete "facebook-xhdpi.apk" and I just move the new facebook from data/app to system/app and voila! Even after a factory reset I have no problems...
But on Kit Kat this is almost impossible. Even after signing the apks, renaming them like the old ones and giving the correct permissions via root explorer they force close. Even Google+ gives a "reinstall-loop" as I call it :crying:
What can I do? Fixing permissions by TWRP doesn't work either.
Open the APK using 7zip, extract the libraries there(the files inside the lib folder), place the extracted libraries inside /system/lib/, delete the libs folder inside the apk, move the apk to /system/app/ or /system/priv-app/ depending what type it is.
Just a warning though... Be careful with replacing already existing libraries in /system/lib/ sometimes they break stuff so if that happens just don't replace them.
Doesn't titanium offer this kind of switch? Have never done it but if it's automated then it's worth a look.
It does... But once you wipe data of the app you moved to system it force closes again. Thing is... System apps doesn't extract libraries in /data/data/ folder hence they force close.
Riyal said:
It does... But once you wipe data of the app you moved to system it force closes again. Thing is... System apps doesn't extract libraries in /data/data/ folder hence they force close.
Click to expand...
Click to collapse
Would it be possible to change the path via titanium or even shift the files via a file explorer? Again haven't done it myself before either.
Also could the apps be added to the ROM you're installing prior to the initial flash?
Sent from my C6903 using XDA Premium 4 mobile app