Database Info

[APP][CWM Flashable] Touchwiz Program Monitor Widget (deodexed)

I have created a flashable zip to install the Touchwiz Program Monitor Widget into any deodexed SGS2 Skyrocket ROMS (running Touchwiz) which are missing it such as boneSTOCKeteer.
Make sure you have /system/app/JobManager.apk installed, and are running Touchwiz prior to flashing the zip file.
This is my first go at deodexing and creating a CWM flashable zip, you can always extract the zip and push the .apk into /system/app via Root Explorer if you are nervous.
Hope you enjoy.
promiseofcake

i'm pretty sure that this widget can only be used on the twlauncher. is there another widget that is similar?

jnicks510 said:
i'm pretty sure that this widget can only be used on the twlauncher. is there another widget that is similar?
Click to expand...
Click to collapse
You are correct, this is for people who are running touchwiz but do not have the widget as per it missing from boneSTOCKeteer.

Thanks for making this!
I'm new to all this. I found that I couldn't install the apk just by opening it, but the zip installs via clockwork mod. I don't really know why but has something to do with deodexing, right? Is there a tutorial for learning about deodexing and creating flashable zips?

purgatoroid said:
Thanks for making this!
I'm new to all this. I found that I couldn't install the apk just by opening it, but the zip installs via clockwork mod. I don't really know why but has something to do with deodexing, right? Is there a tutorial for learning about deodexing and creating flashable zips?
Click to expand...
Click to collapse
System apps are not installed, they just need to be placed in /system/app with the correct permissions (644). You can use something like Root Explorer and you wouldn't have to flash. An odexed rom just means that for each APK there is a corresponding .odex file so: Phone.apk and Phone.odex for example. I think it would also work if I made a flash with ____.apk,_____.odex but well deodex is the trend for portability. A deodexed APK just has the .odex file basically placed inside of it.
I would start with ADB first and then once you are familiar with everything you can move on to flashing. Flashing is really only good if you want to share your changes, it's much easier to just push the file via ADB.
http://www.madteam.co/forum/tutorials/how-to-deodex-an-odex-file/

[Q] Take an app from a custom rom

Hi!
I used for a couple of week a custom rom, the Galnet Miui.
Now I like to try an other rom, but I'd like to keep the Galnet's dialer and browser.
How can I get that apps? Is it easy?
Can I just copy the .apk in system/app in the zipped rom from a zip file to other?
And again... the browser is easy... browser.apk... but how can I recognize the dialer?
Thank you all!

Yes copy the apk to system/app, backup First cause the apk may not work properly, that's why I say backup, experiment all you want but once something goes wrong you have a backup plan , so just get the apk you want and push to system/app and install
NookColor Cyanogenmod 7.1 "Overclocked"

Thank you.
But what's the name of the dialer's apk?

make a backup of whole system folder, then you can test one by one =) DialerTabActivity may be?

Installing .apk at ROM install

Hiya,
Just a quick one, and I could be making this up (but im sure I read it on XDA somewhere)...
Can I drop my .apk's into a folder and then install a ROM and the .apk's will be installed automatically when I flash a new ROM...I'm sure I read that somewhere....Sorry if im wrong on that one,
Any help welcome - Cheers guys!
Martin

RCMix and V6-Maniac S-O-M ROM's have this
Sent from my Sensation using xda premium

Unzip the ROM file, place the APK in "/System/app" rezip the file and flash it.
Or open the ROM file in Winrar, navigate to "/System/app/" drag and drop the apk file there and save it. Then flash it.

you need ROM Cleaner
http://forum.xda-developers.com/showthread.php?t=1217664

How to create your own tw rom on your phone using root explorer

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.

Need some help regarding Odex Files and corresponding apks

Hi guys, I got this problem in my odexed stock rom, I have this problem in sysui, gallery and calculator.
I downloaded 4.2.2 style sysUI, pushed it in the respective folder by replacing with its stock sysUI.
I rebooted my core, the statusbar was gone, so I deleted 'SystemUI.odex" file, then rebooted it worked!
In the same way, I replaced stock gallery with note3 gallery, and stock SecCalculator2
Luckily note3 gallery worked, but it doesn't support Sim2 so I can't change Sim2's wallpaper or make it same as Sim1's.
In the statusbar, I can't see most notification cuz its completely transparent, and also its a bit laggy.
Calculator never worked
So I wanted to replace these with stock, when I pushed it in system>apps> I noticed that there were no .odex files for .apks
I replaced them with their stock odex files, none of 'em worked, I guess cuz of the odex thing, so I again deleted odex files and rebooted, nothing worked..
Now, I need some developer's advice, plz don't tell me to "Flash Stock Rom via Odin" I can't do it...
Is there any other left way to make them work plz I need help..

You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--

M_E_G_A_T_R_O_N said:
You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--
Click to expand...
Click to collapse
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...

Well, it seems to me that you have messed up your phone alot.. Flashing stock rom via odin would've been the correct solution to this problem. It's not as difficult as you think, and you're capable of doing it. Follow thecoreguy's tutorial for that.

CoreGuy said:
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...
Click to expand...
Click to collapse
Then you have done wrong.
Not every apk can be used by just deleting the .odex file.
You need to deodex the apps in system/app and system/framework folder then you can easily replace the apks.
1.First restore back to any working backup.
2.Download xUltimate Tool.
3. Run it.
4. Then just run commands with options 1,2,3,4 (You just need to type 1 and then enter, then 2 and then enter, so on upto option 4.)
5. Exit after executing 4th option.
6. Download ADB tool(don't download the complete package, you will get a 1-2MB ADB.exe from the from itself) - Use it to push the deodexed files made from xultimate.
---------- Post added at 09:47 AM ---------- Previous post was at 09:22 AM ----------
If you find it difficult then Better you upload the apks with their respective odex file. I will deodex those apks

M_E_G_A_T_R_O_N said:
Not every apk can be used by just deleting the .odex file.
Click to expand...
Click to collapse
Not even the stock apks? I want to replace the ported/modded apks with the stock ones..

No you can't because almost all stock apks have their respective odex files and every odex file contains resources that are needed to run those apks. Also there exists dependencies in system/framework folder. So just deleting odex file won't work all time.

Finally got it! Special thanks to megatron
Solution if u r screwed in my situation: don't panic, what I found why I cant do it was bcuz my phone has dat "newest" update of samsung ota. So b4 u take someone's apk and odex file always cross check this(image)
And then you are gud to go!!! U wont even need to restart it'll come automatically(my dad has same phone and same updated version as mine so I copied everything needed frm his phone to mine) @AnsleyC at times, the answer should not be "flash stock rom via ODIN" if u have a crappy pc, u can either repair faulty parts(easier and efficient) or buy a new one(bullcrap)
Have fun everyone!
Sent from my GT-I8262 using XDA Premium 4 mobile app