Related
Alright this is 3 really quick and easy questions.
I have infused 2.2.3 and i wanna know:
1) if i install a theme, or probably any mod or something like that, how would i take it off?If i wanted to change the theme im on, do i simply go into cwm and apply a different theme? Or do i have to do something to remove the other one?
2)Do i need the old zips i applied to the phone or should i just delete them?
3) and if i were to put allll my zips in there could i just install them from there or do they need to be in the main part of my internal sd card? Basically does it matter where in my internal sd card they are or not?
joeym11 said:
Alright this is 3 really quick and easy questions.
I have infused 2.2.3 and i wanna know:
1) if i install a theme, or probably any mod or something like that, how would i take it off?If i wanted to change the theme im on, do i simply go into cwm and apply a different theme? Or do i have to do something to remove the other one?
2)Do i need the old zips i applied to the phone or should i just delete them?
3) and if i were to put allll my zips in there could i just install them from there or do they need to be in the main part of my internal sd card? Basically does it matter where in my internal sd card they are or not?
Click to expand...
Click to collapse
1) To revert your theme back to the original you would either need to flash the rom again or the theme developer SHOULD have a revert for you to flash.
2)I keep them around just because, I always keepat least two roms and two kernels and a whole bunch of mods and modems. I mean the infuse has 16gb internal storage so memory isnt really that big of a deal. But no you dont NEED them.
3)Nope I've flashed from all sorts of places on my SD card. Root of the SD is probably the easiest though because then you dont have to do all the navigating through files etc in CWM.
Reynaldinho111 said:
1) To revert your theme back to the original you would either need to flash the rom again or the theme developer SHOULD have a revert for you to flash.
2)I keep them around just because, I always keepat least two roms and two kernels and a whole bunch of mods and modems. I mean the infuse has 16gb internal storage so memory isnt really that big of a deal. But no you dont NEED them.
3)Nope I've flashed from all sorts of places on my SD card. Root of the SD is probably the easiest though because then you dont have to do all the navigating through files etc in CWM.
Click to expand...
Click to collapse
Thank you SOOO much... got so tired of seeing 30+ views and no replies... thank you
joeym11 said:
Thank you SOOO much... got so tired of seeing 30+ views and no replies... thank you
Click to expand...
Click to collapse
Haha, no problem man
joeym11 said:
Thank you SOOO much... got so tired of seeing 30+ views and no replies... thank you
Click to expand...
Click to collapse
I just went to look for the revert but he didn't have it
This is the thread here
http://forum.xda-developers.com/showthread.php?p=17642552#post17642552
If you see it then lemme know, otherwise, do i reflash infused??
joeym11 said:
I just went to look for the revert but he didn't have it
This is the thread here
http://forum.xda-developers.com/showthread.php?p=17642552#post17642552
If you see it then lemme know, otherwise, do i reflash infused??
Click to expand...
Click to collapse
Yeah I dont see it. You can reflash infused. Make sure to back up everything you're gonna need though.
joeym11 said:
I just went to look for the revert but he didn't have it
This is the thread here
http://forum.xda-developers.com/showthread.php?p=17642552#post17642552
If you see it then lemme know, otherwise, do i reflash infused??
Click to expand...
Click to collapse
One of the "tricks" I usually do is this:
- make a copy of the .zip you're going to install -- rename it with 'revert' or 'undo' or something
- open the copy with 7zip, navigate to see what files are in it... (*don't touch the META-INF folder)
(themes usually contain /system/framework/framwork-res.apk and /system/app/SystemUI.apk)
- extract the same files from your current ROM
(either from the original zip, or directly from the phone -- I like to use 'Android Commander')
- replace those same files in the 'revert' zip -- and Bingo -- you now have a backup to restore if you don't like the theme
Reynaldinho111 said:
Yeah I dont see it. You can reflash infused. Make sure to back up everything you're gonna need though.
Click to expand...
Click to collapse
gwbard said:
One of the "tricks" I usually do is this:
- make a copy of the .zip you're going to install -- rename it with 'revert' or 'undo' or something
- open the copy with 7zip, navigate to see what files are in it... (*don't touch the META-INF folder)
(themes usually contain /system/framework/framwork-res.apk and /system/app/SystemUI.apk)
- extract the same files from your current ROM
(either from the original zip, or directly from the phone -- I like to use 'Android Commander')
- replace those same files in the 'revert' zip -- and Bingo -- you now have a backup to restore if you don't like the theme
Click to expand...
Click to collapse
Thanks ryan very much
And gwbard... i dont exactly understand that
Edit: Alright i got to the part where i extract the same files wiht my current rom... but how do i do that?... i just opened the zip from infused and all i see was the meta and then a folder with updates... what do i do? Im on infused 2.2.3 if that helps
joeym11 said:
Thanks ryan very much
And gwbard... i dont exactly understand that
Edit: Alright i got to the part where i extract the same files wiht my current rom... but how do i do that?... i just opened the zip from infused and all i see was the meta and then a folder with updates... what do i do? Im on infused 2.2.3 if that helps
Click to expand...
Click to collapse
Just browse through the "update-infused-v2.2.3-full.zip" -- get familiar with the filesystem.
At the root you should see META-INF, system, and updates.
'META-INF' contains the scripting to run the update itself.
'updates' contains the modem & kernel.
'system' is what you should be looking at. Inside 'system' (amongst other stuff) are 'app' and 'framework' folders. "SystemUI.apk" is in 'app'. "framework-res.apk" is in 'framework'. 99% of the time these are the only two files changed in themes.
Now, not all developers follow the same folder structure in their CWM zips, for example they might just have a folder 'framework' where the scripting copies framework-res.apk to /system/framework, and so on...
sorry but it appears my building is on fire gotta go
edit: all is well (sorta) -- seems lightning has fried one of the A/C units on the roof!
gwbard said:
Just browse through the "update-infused-v2.2.3-full.zip" -- get familiar with the filesystem.
At the root you should see META-INF, system, and updates.
'META-INF' contains the scripting to run the update itself.
'updates' contains the modem & kernel.
'system' is what you should be looking at. Inside 'system' (amongst other stuff) are 'app' and 'framework' folders. "SystemUI.apk" is in 'app'. "framework-res.apk" is in 'framework'. 99% of the time these are the only two files changed in themes.
Now, not all developers follow the same folder structure in their CWM zips, for example they might just have a folder 'framework' where the scripting copies framework-res.apk to /system/framework, and so on...
sorry but it appears my building is on fire gotta go
edit: all is well (sorta) -- seems lightning has fried one of the A/C units on the roof!
Click to expand...
Click to collapse
Lol Glad youre aight man
Sent from my friggin huge Samsung Infuse
So if i was to flash infused but wanna keep my kernel and modem id just remove the update folder from the zip and run it as usual?
Sent from my SAMSUNG-SGH-I997 using XDA App
If you upload the framework and twframework files to the kitchen to create a new battery icon, for example, are those newly created apk files going to work with that same ROM if you reinstall that same ROM after using another ROM?
Just wondering if you have to get a new zip file from the kitchen each time you go back and install a ROM you may have had before the current ROM you may be running.
Sent from my SGH-I997 using XDA App
MaverickCoast said:
If you upload the framework and twframework files to the kitchen to create a new battery icon, for example, are those newly created apk files going to work with that same ROM if you reinstall that same ROM after using another ROM?
Just wondering if you have to get a new zip file from the kitchen each time you go back and install a ROM you may have had before the current ROM you may be running.
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Ahh, the anwser to the first question would be Yes.
The answer to the second non-question would be No.
Simpler: Install "ABC Rom" flash changes made from "ABC Rom" framework files.
Thanks, TG.
Tired of trying out a new ROM, going back to the other ROM and re-creating the ZIP file all over again.
MaverickCoast said:
Thanks, TG.
Tired of trying out a new ROM, going back to the other ROM and re-creating the ZIP file all over again.
Click to expand...
Click to collapse
Here's an easier way to go back: Before flashing a different Rom, while in Red Recovery, make a backup.
That way all you have to do is run Restore from recovery. It will automatically name the backup by the date.
I then use root explorer and rename it to the rom that you were using.
Then when I have the time, I'll copy the backups to my external SD card and to my computer.
There you go. No more reinstalls. Just remember to back up your contacts or you'll wind up with the list from when you backed up last.
I'm interested in flashing the Sabsa Prime rom, http://forum.xda-developers.com/showthread.php?t=1839004 , but there are currently reported issues with the camera not working correctly. It's said (by the dev himself) that you can change the current camera apk with a previous one but I'm not exactly sure how to do this. I already have the camera.apk from the earlier version that works great, can I just extract the current rom and replace the camera.apk with the working one and rezip it as a .zip file and flash it? Or would I need to do something else to make it flashable or a different step all together? Thanks!
That sounds about right. Just keep the originals in case there are additional steps. Flash and test.
However, using that other cam apk, if it's the one I'm thinking, not sure if it's allowed. For personal use without re-distributing it, maybe but not quite sure.
Sent from a dream.
Unzip replace and rezip. I do this with all roms I use. There are apks I like to add and delete as well as system audios and bootani. You can alter the rom to your liking just remember not all apks work for a rom in other words you can not use sense apks on a aokp rom for example. And second if you do alter a rom you can not ask the Dev for help if something goes wrong with it, you altered it. With that said alter at your own risk and enjoy the learning.
Sent from my Ice Cold Inspire 4G
In this tutorial I will show you how to create your own T.W. rom using your GS3 and Root Explorer. There are many ways you can create a rom but not everyone has the time to sit at a computer every night. However, your phone is always on you and can find a few minutes here and there to create your own masterpiece.
For the sake of this tutorial, we will name our new rom "SLICK".
Here are a few things you will need...
1. The rom base from Scottsroms. I'm NOT talking about Cleanrom but the unmodified stock rooted rom.
2. Root Explorer.
3. Script Manager
4. Any mod you can flash or come up with on your own.
1. GET STARTED!
Download the base rom to your phones EXT-sdcard and extract it using Root Explorer. After it's extracted the new unziped rom will be located in /storage/sdcard0/SpeedSoftware/Extracted. The extracted rom is now your new base. At this point it would be a great idea to move it to your EXT-sdcard and create a new project folder for it and label the folder "Project SLICK". inside the folder is your rom. lets rename that rom "SLICK".
Lets open your new SLICK rom. You should have some folders...
BOOT IMAGE
DATA
META-INF
SYSTEM
3. THE SYSTEM FOLDER
/SYSTEM/APP
Most of your work will done in the System folder so lets open that up. This is the heart of your rom! There are many folders here but lets start with the app folder. This folder has every app installed in your rom. This is a good time to remove the bloat you don't want in your rom. Go ahead and delete the apk's you don't want or need.
/SYSTEM/BIN
Here you can speed up your system or make it more battery efficient by deleting things like "mpdecision" and things like that. Be careful what you delete though. In general you won't do much in here.
/SYSTEM/BUILD.PROP
Here you can change values or add values. The one value we are concerned with is "ro.build.display.id" This build property's value will be displayed in the end users settings menu under "about phone". So let's give this property the correct value "ro.build.display.id=SLICK ROM v1.0" The rest of the build properties you can do as you wish. Build.prop is simply a text file. You can use the text editor built into Root Explorer.
/SYSTEM/CSC
Open this file and you will see more files. Listed is "feature.xml". Here you can edit values for various items for texting and mms.
/SYSTEM/ETC
Here is where you will find a folder called "init.d". Located in this folder are various text files. The text files are scripts that are told to run when your phone boots. You can add or modify to the existing scripts or create a new text file.
So we went over a few of the basics of modding your new rom and molding it into something you can call your own but does it work??
4. TESTING YOUR NEW BASE.
So we have already modified our rom a considerable amount and should have a good solid base. Before we go any further we should really test things out first. If we did something wrong earlier we will at least have an idea where to look. So lets flash our new rom. Go to you EXT-sdcard and find our project folder. you should still have your SLICK file. Zip this file with Root Explorer. Make sure you have a good battery and a cool environment because it's going to take your GS3 about 30min of hard work to zip this file. When that is finally completed, flash your new rom located in /storage/sdcard0/SpeedSoftware/Archives. Flash it just like you would any other rom.
Test your new rom out on your GS3 and see how things are running. Check your existing modifications you did earlier. If everything looks good, we can continue modding. If not you will need to go back to your base to see where you went wrong. This is also a great time to check your init.d scripts. One way to do this is to download "Script manager" from the market and click on your init scripts to read there log. It will tell you if something went wrong.
If everything is looking good, we can continue modding...
5. THE MODS
So we have that nice clean base but what about all them mods in the roms we download and flash everyday? There are a few different ways we can do this and we will start with the easiest but first, do a nandroid backup of your new base. If one of your mods you perform next goes bad it's simply quicker to recover. Now, If you have flashable zips of some of the mods you like then you can flash them now and make sure they are working the way they should in your rom. Remember, just cause we have the d2vzw does not mean mods from the sprint or T-mobile won't work on our devices. Sometimes it's worth a try. It's all about which firmware they are on and what has changed with the firmware.
So we flashed a few mods but don't have everything we wanted. At this point you are left with only one option and that is to get on that PC of yours and learn to decompile a APK. I may touch on this subject later as it is a bit more involved for someone new to this sort of thing.
6. UNDERSTANDING THE FLASHABLE ZIP
The alternate method of a flashable zip is to extract your flashable using Root Explorer and picking it apart. For example we will use "Lean Kernel" and kill 2 topics with one stone. If you unzip the kernel you will see...
BOOT.IMG
META-INF
SYSTEM
As you can see there are some familiar files to us just like when we extracted our base rom in the beginning. Basically when you flash a mod like this or any flashable for that matter, it installs files into your rom in certain places. In this example we will be installing in BOOT.IMG and SYSTEM. But what? And what is that META-INF file for? Well this META-INF file is what tells your rom what files and what to do with those files. Inside META-INF is a text file called an "updater script".
Here is what it looks like...
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 0777, "/system/etc/init.d/00leanKernel");
unmount("/system");
assert(package_extract_file("boot.img", "/cache/boot.img"),
write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7"),
delete("/cache/boot.img"));
show_progress(0.100000, 0);
Line 2 shows it mounting the system so we can write to it.
Line 3 shows us extracting the entire directory of the system file in the flashable into the system file of our rom.
Line 4 shows we are setting permissions for one of the system files we just installed in the rom. In this case it is an INIT.D file.
Line 5 shows us returning the system to an un-writable state.
Line 6 shows we are now installing the other file called BOOT.IMG.
So we installed BOOT.IMG and the SYSTEM file. The BOOT.IMG file is usually only found in a rom or kernel zip so most of the time you won't see this file in a flashable but I wanted to use this as an example to show a bit about the kernel side of things.
Ok, so lets get back to the original files of this flashable zip. The updater script stated we installed a new system file into the rom so whats in there? If we open the SYSTEM file from our flashable with Root Explorer you will find a file hierarchy...
SYSTEM
-- ETC
--- INIT.D
---- "00LEANKERNEL"
-- LIB
--- MODULES
---- Listed here are a bunch of ".ko" modules and i'm not listing them all.
So whats the point of all this? Well lets say when we originally debloated our rom in the begining we could of included some of our flashable mods like a custom kernel before we zip the rom to test the base. So in this case we can manually install this kernel before we zip the base. We can take the BOOT.IMG from our extracted kernel and replace the BOOT.IMG in our extracted rom. We only need the files from the flashable so we need to copy and paste the "00LEANKERNEL" file from our flashable to our roms /system/etc/init.d folder. We can also take those ".ko" files from the flashable and dump those into the /system/lib/module folder and we are done. You have now manually installed a kernel into your base rom before you zipped it. Now when you zip your rom and flash it, your new base rom will boot with your custom kernel. Since we manually installed the kernel we don't need the META-INF file provides an auto install script for installing through recovery. Technically we could take all of our flashable mods, extract them, look at the file hierarchy and copy and paste the those files to our extracted base rom. That way we can zip our rom and test it with the mods right off the bat. You can really make things quicker this way and is in general the way to go.
I think it's rather important to fully understand a flashable zip. How it's built and how it completes it's task. It's used so often and makes mods so incredibly easy to install but it is also what installs our rom! One of the files we see when we open "slick" is a META-INF and there inside is the updater script to flash the rom. Again we are doing the same thing as we do with the flashable mod but this time we are installing a lot more files with a lot more permissions. It is the exact same thing as shown above just a bit more extensive.
7. PUT THE PIECES TOGETHER
Ok so we have our base rom running on our phone and possibly a few mods installed. We also have our extracted and debloated "slick" rom on the EXT-sdcard inside our project folder. The next part is rather easy if you understand how those flashable mods were installed. If you understand the whole flashable and its files, your better off just extracting them and then copy and paste them where they need to go. After you have all your mod files in place you can now zip your official "Slick" rom using Root Explorer of course. Prepare yourself for another 30 minutes for it to zip. After it's zipped your done. You have now created your first fully modded rom! However...
Lets say you don't get the whole flashable thing and or you had made some other changes to the rom while you were testing. Lets say you flashed some mods and created a few init.d scripts or the build.prop along the way. NO WORRIES! We can put the rom together another way. A lot of the mods you flash will install files in some usual areas of the rom like your Framework folder and such. Lets just say we don't know though. You can actually copy complete folders from the rom you are running right there and now and paste them into your extracted "Slick" base rom using Root Explorer. So you can take "/system/framework" from your currently running rom, copy it, and paste it in "/storage/EXT-sdcard/project folder/slick/system/framework". In short just take your copy of the framework file and put it in your extracted base and paste it. Root Explorer will then ask you if you want to replace this file and click yes. You have just transferred any modded file that might have been in framework to your extracted rom. Any folder you may think was modded, simply copy and paste it to your extracted base rom on your EXT-sdcard. Once you think you have it all the modded files transferred you can zip your new "Slick rom! Flash and enjoy!!
FINISHED
So we have now completed our own rom on the device itself. It's really not too difficult just a bit more time consuming with zipping and that. However, you may need to do a bit more research on how to decompile and recompile an APK. This is one of things that can really be a pain to setup. It's again the basics that will kill you. The whole PITA is not decompiling or making changes to a framework file, it's setting up the environment that sucked for me. You have to get the Java and files in order and all the little crap to get it to work. IMO, if you haven't decompiled an APK yet it's really not difficult at all. Like I said. It's the basics. I encourage you to learn this because it's so freakin easy after it's all setup and you will be able to do so much more with your rom. Once you get this APK thing down don't be afraid to take someone elses work and reverse engineer it. Try to figure out what that developer did to accomplish what he wanted. It's a great way to learn and thats what it's about.
I may add to this somewhere down the road but for now it's all I have. I hope this helped and motivated someone to create a rom and begin there journey to become developer someday! We can all use fresh ideas for development. There is so much more to come for Android so get your hands dirty and share!
Thanks guys!
Ha never really thought of doing this on the fly with my phone. Even though all the right stuff was sitting in my face thanks for opening my eyes razz1
Sent from my SCH-I535 using Tapatalk 4 Beta
dincdoes.me said:
Ha never really thought of doing this on the fly with my phone. Even though all the right stuff was sitting in my face thanks for opening my eyes razz1
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's another way. May not be the fastest way but it's another option. I also wanted to write this as a general rom creation and learning some basics. It's always the basics that will kill a project and motivation. I would like to see a complete newb to be able to complete a rom with this tutorial. Then I accomplished something. Going to have to finish this tomorrow though. It's taking longer than I thought lol.
Yea I mean I'm a newb at doing it from my phone if that counts =) .. What explorer do you like to use to repack the zips. I'm sure I'll try this method soon to play while bored at work. Rom tool box will help with boot animations, fonts and transition animations too take care thanks for giving our community some new skills I'm sure it will help out down the road.
Sent from my SCH-I535 using Tapatalk 4 Beta
Thank you for this post. This will definitely get me to try and make my own ROM the way I like, also I might just learn some new stuff. Great post thanks again
Sent from my SCH-I535 using xda app-developers app
Nice tutorial.
It's a great way to show what can be done just from your phone.
:good:
Right on man. Been waiting for this. Thank you.
Sent from my SCH-I535 using xda app-developers app
dincdoes.me said:
Yea I mean I'm a newb at doing it from my phone if that counts =) .. What explorer do you like to use to repack the zips. I'm sure I'll try this method soon to play while bored at work. Rom tool box will help with boot animations, fonts and transition animations too take care thanks for giving our community some new skills I'm sure it will help out down the road.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I use androzip man.
Sent from my SCH-I535 using xda app-developers app
More added
So would I make, say ROM manager a system app? Just copy the apk into the /System/App folder?
Evil Genius Jr. said:
So would I make, say ROM manager a system app? Just copy the apk into the /System/App folder?
Click to expand...
Click to collapse
Yes, but not all apps you download from google play work in /system/app. Some want to be installed into /data/app. However /data/app doesn't exist till after the rom is booted. You would need to add the folder to your extracted rom and modify the updater script.
razz1 said:
Yes, but not all apps you download from google play work in /system/app. Some want to be installed into /data/app. However /data/app doesn't exist till after the rom is booted. You would need to add the folder to your extracted rom and modify the updater script.
Click to expand...
Click to collapse
You are the fu**ing man razz1.
Sent from my SCH-I535 using xda app-developers app
That's about all I have for now. OP completed!:sly:
Hello. Ok so I created a ROM what I call MyTWGE (Tuchwiz Google Edition). Followed the instructions, unzipped the stock Verizon OS went into the -app- folder deleted all the Verizon, Samsung and Google apps (only the ones that are download able from Google Play). Replaced the stock launcher with the 5x6 version that I extracted from another zip, replaced the camera with the Google edition camera (download able from GP), replaced the keyboard with the Note2 keyboard (also unzipped from another zip). Looked around and deleted a few more files I found that were connected to some Samsung apps and zipped it up. Flashed the zip yesterday onto the phone and it's ALIVE working.
Thank you for your patience to write up all these instructions. I previously used TB to debloat my phone and that was it, learned a few thing thanks again
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
Hello. Ok so I created a ROM what I call MyTWGE (Tuchwiz Google Edition). Followed the instructions, unzipped the stock Verizon OS went into the -app- folder deleted all the Verizon, Samsung and Google apps (only the ones that are download able from Google Play). Replaced the stock launcher with the 5x6 version that I extracted from another zip, replaced the camera with the Google edition camera (download able from GP), replaced the keyboard with the Note2 keyboard (also unzipped from another zip). Looked around and deleted a few more files I found that were connected to some Samsung apps and zipped it up. Flashed the zip yesterday onto the phone and it's ALIVE working.
Thank you for your patience to write up all these instructions. I previously used TB to debloat my phone and that was it, learned a few thing thanks again
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Lol the whole time I was reading this I was waiting for you to say something didn't work out for you but it all did I guess. Nice!!
Yeah running for the past 24h no problems everything works. Thanks
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 02:24 AM ---------- Previous post was at 02:07 AM ----------
Only thing that that's annoying is the wifi in the taskbar. I read in one of the posts that I have to go into systemui and some other files within n delete lines 12 through 21 but that didn't work , am guessing I need to decompile systemui to do that. The person in the post didn't clarify and I'm not ready to do that yet. Reason is I don't know anything about programming or linux or decompiler or anything like that. Deleting files I can do replacing some sure. But I'm happy my first attempt to mix something together worked and I'll keep doing it till I actually figure out what it is that I am doing. Thanks again for the post
Sent from my SCH-I535 using xda app-developers app
Yea. Follow Didacts write ups to get you through it. It's all in framework res apk.
Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!
michalurban said:
Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!
Click to expand...
Click to collapse
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up
anerik said:
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up
Click to expand...
Click to collapse
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).
michalurban said:
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).
Click to expand...
Click to collapse
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way
anerik said:
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way
Click to expand...
Click to collapse
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?
michalurban said:
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?
Click to expand...
Click to collapse
Put faux's boot.img on the rom first, then on updater script go to the line that refers to extracting boot.img (should be like the last one) and replace that with the command on faux's updater script. That means it will extract it in that directory, nothing else. Be sure to copy modules aswell and set the perms
Q&A threads should be created in the Q&A forum... not the Development forum.
Thread moved.
One more question - is there a special way how to pack the ZIP file? Cause I unpacked a ROM, added some apks, packed it but it didnt work (no error, just ended at "opening rom" or what the CWM message is) ... but when I modified existing ZIP it went fine ...