So I've been cruisin' around the threads here and on rootzwiki looking to mod my newly rooted Gnex and I see most of the mods are using lingo I'm not familar with. Like systemui.apk dropping files here and there. I've used root explorer and I know how to mount r/w or whatever but I don't understand what to do and how to flash these mods. is there a tutorial somewhere?
First - an .apk file is just a compressed container that contains files just like a .zip file. In fact it is a zip file with certain Android specific folder structures, files, and "signatures".
Disclaimer - I don't mod or code on the Android platform and the following is based on my understanding of how Android works.
The SystemUI.apk is an Android system file that contains Android system ui code, layouts, and ui related content such as images and etc. What the modders have done is made changes to these code, layouts, and images to modify how the Andoid UI looks.
This SystemUI.apk file resides in a specific location on your phone. What most of the modders have done is made it easy for you and packaged this file into a zip file (which is usually what they give to you as a download) that you can flash via ClockworkMod recovery to automatically replace your stock SystemUI.apk copy with their modified copy.
If you are not familiar ClockworkMod recovery is the standard for flashing Mods, ROMs, and kernels onto your phone. Since you are rooted and want to tinker with your phone you should flash the CWM recovery to your phone if you haven't already. You can look up the many guides that show you how to do this.
To flash most of the mods you would download the .zip file to the internal storage on your phone. Then you would boot into CWM recovery (there are a couple of ways to do this - do a search) and choose the "Install zip from sdcard" and navigate to the file you downloaded. Flash the zip file and the mod should be installed for you.
Note: Many of the modders that make changes to the SystemUI.apk will have packaged this file into flashable zips. By flashing these zip files they overwrite the current SystemUI.apk on your phone. What this means is that if you flash a mod on top of another mod they will overwrite each other.
ok that clears some things up for me. I do have CWM flashed (currently sporting the touch version which is sweet by the way). So when a modder talks of the systemui.apk they are not asking for the user to do anything with the files, they are just explaing how the .zip file works? I guess I got confused because I thought that's what the modder was wanting me to do (change the Systemui.apk). I would simply flash the .zip then on reboot something crazy would happen like I'd lose my softkeys or the status bar would disappear. Thank God for Nandroid but after a while you get tired of trying to flash different mods because I have to go back and restore. I am currently running Android Revolution 2.1.2 but I don't know if that makes a difference or not.
automaddux said:
ok that clears some things up for me. I do have CWM flashed (currently sporting the touch version which is sweet by the way). So when a modder talks of the systemui.apk they are not asking for the user to do anything with the files, they are just explaing how the .zip file works? I guess I got confused because I thought that's what the modder was wanting me to do (change the Systemui.apk). I would simply flash the .zip then on reboot something crazy would happen like I'd lose my softkeys or the status bar would disappear. Thank God for Nandroid but after a while you get tired of trying to flash different mods because I have to go back and restore. I am currently running Android Revolution 2.1.2 but I don't know if that makes a difference or not.
Click to expand...
Click to collapse
They probably want you to change the systemui.apk and then push it to your phone. If this is not done correctly your system ui will disappear. Happened to me when I was trying to mod my softkeys.
automaddux said:
ok that clears some things up for me. I do have CWM flashed (currently sporting the touch version which is sweet by the way). So when a modder talks of the systemui.apk they are not asking for the user to do anything with the files, they are just explaing how the .zip file works? I guess I got confused because I thought that's what the modder was wanting me to do (change the Systemui.apk). I would simply flash the .zip then on reboot something crazy would happen like I'd lose my softkeys or the status bar would disappear. Thank God for Nandroid but after a while you get tired of trying to flash different mods because I have to go back and restore. I am currently running Android Revolution 2.1.2 but I don't know if that makes a difference or not.
Click to expand...
Click to collapse
Most modders will not ask you to modify the SystemUI.apk yourself. This requires knowledge of how to package and sign the apk so it will work with Android. Most likely if the modder gives you specific details about files in the SystemUI.apk package they are just distributing information about how the modification works.
The current rom you're on is 4.0.2. I suspect the mod you flash is only compatible with 4.0.3 (most people tinkering with their phones have flashed to 4.0.3 ROMs now) and that's what caused your issues.
You don't necessarily have to nandroid - although it is very good practice. Before you flash mods if you either know files are being flashed or use a zip utility (i highly recommend 7zip) to inspect the .zip file provided by the modder you can use Root Explorer or ADB to backup the files that will be replaced. This way it would be an easy restore if something screws up. Note that this isn't 100% bulletproof since it really depends on what the mod is and what it's changing in the Android system.
silow said:
Most modders will not ask you to modify the SystemUI.apk yourself. This requires knowledge of how to package and sign the apk so it will work with Android. Most likely if the modder gives you specific details about files in the SystemUI.apk package they are just distributing information about how the modification works.
The current rom you're on is 4.0.2. I suspect the mod you flash is only compatible with 4.0.3 (most people tinkering with their phones have flashed to 4.0.3 ROMs now) and that's what caused your issues.
You don't necessarily have to nandroid - although it is very good practice. Before you flash mods if you either know files are being flashed or use a zip utility (i highly recommend 7zip) to inspect the .zip file provided by the modder you can use Root Explorer or ADB to backup the files that will be replaced. This way it would be an easy restore if something screws up. Note that this isn't 100% bulletproof since it really depends on what the mod is and what it's changing in the Android system.
Click to expand...
Click to collapse
Well i guess im gonna hafta upgrade then wont I
Related
Hi guys. Thinking of installing the Leedroid ROM on my phone. Currently have Android Revolution HD and as you might know a few hours ago I went through some troubleshooting that had me praying to God Almighty because I'm a bit of a noob and I got really worried. Lol
Anyway, I know how to flash ROM's and Radios but how do I flash kernels and ROM "Extras"?
It was flashing an "Extra" that got me in the problem into the mess in the first place so I just wanted to confirm how to do it properly. Also, is flashing the kernel as simple as flashing a ROM? ie:
-Boot into CWM
-Nandroid Backup
-Wipe All
-Install new ROM
-Make sure it all works
-Back into CWM
-Install kernel zip from SD card
?
Thanks very much guys.
When I installed leedroid I installed rom then straight after the kernal without even rebooting. Worked fine for me.
I'll give it a shot later. But still how do I flash extras? Like a Sense 3.0 lockscreen for Leedroid?
Put it on your ssd and open it up in a file explorer (think leedroid has astro) and just run it and it will install.
If that doesn't work for an extra then boot into CMW and install it via zip, but if I recall correctly that won't work for the lock screen and has to be done via opening it up in a file explorer.
If the addon or kernel you've downloaded is a zip file, the easiest way to be sure it's flashable in CWM is to open it up in 7zip, WinRar, etc. and see what's inside. If there is a folder called "META-INF" then you know it can be flashed by CWM.
Most zips are CWM flashable, but some won't be, especially fonts, bootanimations or splash screens. There are usually instructions in the threads for these, though.
Kernels are often built in to the ROM zip, but if you want to change your kernel I recommend jkoljo's tool:
http://forum.xda-developers.com/showthread.php?t=852357
I'd also suggest doing a nandroid backup after flashing the ROM and making sure it all works, before flashing anything else, especially with some of the addons that are still in development. It just gives you a bit more security if you need to roll back.
I have attached the offending boot animation....
If someone could please point me in the right
direction on what im doing wrong...
And if someone else is having the same
problem, maybe this might show/help show
them the right way as well....
I have tried it in system/media as well as
system/customize/resource...and still a no
go...Is the internal file settings correct?
I can use other boot screens and it works
but this modded version doesn't work
what kind of rom? sense or asop. cause you missing the correct file stucture either way.
Im sorry Im using Sense and I am trying
to work it in a stock ROM that I have
been working on for a week
here try one of these. i put the correct files in both and zipped it and made it for either one(asop or sense)
these are for flashing in recovery, if you want to just add it to a rom unzip and take out the bootanimation.zip and you can replace it in the rom before flashing the rom or use root explorer
so would you know how to integrate it in
so there is no need on flashing? It has the
boot screen already "pre-loaded" when
you flash the ROM
but other then that...AWESOME THANKS!
in a sense rom you have to goto system\customize\resource and just replace the bootanimation.zip with the one you want to use. when zipping up the rom you zip the whole thing with 7zip(or whatever you use) using normal and you have to sign it using autosign(or whatever you use)
hope that helps you out, good luck with the rom
works BEAUTIFULLY!! You may use it if you like!
I am new to rooting so I dont know how to install mods on a Rom . I have ARHD 6.3.1 . Already downloaded required mods just wanna know how to install them . Thanks in advance.
Most mods are designed to be flashed in Recovery, just like the ROM itself.
It's a good idea to backup the ROM in recovery first, as there's no "uninstall" option for these mods. So if you decide you don't want the mod, you can restore your backup to get everything back to the way it was before you flashed it.
Depending on what mods you've downloaded, most of them are usually just flashable .zips, just like the ROM itself. So you simply install them by rebooting to recovery and flashing the .zip files you've downloaded and then rebooting afterwards.
I have downloaded CRT mod , advanced power manager mod , honeycomb icons + % battery mod , beats audio(music box) mod . should i just flash them from recovery just like i flashed rom . Thanks
There's a fairly easy way to check for yourself if a ZIP file is meant to be flashed in Recovery, like a ROM.
Just open the zip file (don't extract it, just open it in your favourite ZIP program). Have a look inside and if you can see a folder called "META-INF" then you know it's a flashable ZIP file.
See the attached screenshot for an example. There might be lots of other folders inside the zip (system, data), but as long as there is one called "META-INF" then you know you can flash it in Recovery.
Hey guys, I am new to the android os (just switched from ios) and I have read most of the tuts and have been successful flashing a few roms testing them out getting a feel for the one I want. However after my third flash I began to see a "0" directory show up on my internal sd root and inside that directory it contains all the folders that are in the same root directory as "0". Has anyone else had this occurance and if so what can I do to eliminate the unnecessary directory? I make sure to do a complete wipe of my phone between flash and follow the instructions to the T. If anyone could help me out I would greatly appreciate it. Thanks guys
Lukkaz said:
Hey guys, I am new to the android os (just switched from ios) and I have read most of the tuts and have been successful flashing a few roms testing them out getting a feel for the one I want. However after my third flash I began to see a "0" directory show up on my internal sd root and inside that directory it contains all the folders that are in the same root directory as "0". Has anyone else had this occurance and if so what can I do to eliminate the unnecessary directory? I make sure to do a complete wipe of my phone between flash and follow the instructions to the T. If anyone could help me out I would greatly appreciate it. Thanks guys
Click to expand...
Click to collapse
The "0" is a part of Android 4.2's file system setup, so if your current ROM is 4.2-based, leave it alone.
If you're not currently running 4.2, you can safely move the entire contents of the /0 directory up a level (i.e. to wherever the 0 directory is located) and remove the /0 directory.
smelenchuk said:
The "0" is a part of Android 4.2's file system setup, so if your current ROM is 4.2-based, leave it alone.
If you're not currently running 4.2, you can safely move the entire contents of the /0 directory up a level (i.e. to wherever the 0 directory is located) and remove the /0 directory.
Click to expand...
Click to collapse
Thank you for the quick response, yeah I have messed with a couple 4.2 roms so I have a few levels. I'm debating flashing a 4.1 just to clean it up I have about 3 levels lol
Lukkaz said:
Thank you for the quick response, yeah I have messed with a couple 4.2 roms so I have a few levels. I'm debating flashing a 4.1 just to clean it up I have about 3 levels lol
Click to expand...
Click to collapse
Just flashing a 4.1 ROM won't solve the problem.
If you're going to stick to 4.2, you can move everything up to the top "level" of /0 and delete the other /0s.
Incidentally, the stacked /0s is caused by repeatedly flashing 4.2 ROMs with a recovery that isn't designed to handle them. I know TWRP 2.3.2.0 and newer handle 4.2 properly - can't speak for anything else.
Updating your recovery will eliminate problems with the creation of /0 folders when flashing 4.2 ROMs.
I currently use cwm not sure the version but not entirely sure if it is up to date, what recovery do you guys personally recommend?
Lukkaz said:
I currently use cwm not sure the version but not entirely sure if it is up to date, what recovery do you guys personally recommend?
Click to expand...
Click to collapse
TWRP (which I mentioned earlier) is available over in this thread.
Lukkaz said:
I currently use cwm not sure the version but not entirely sure if it is up to date, what recovery do you guys personally recommend?
Click to expand...
Click to collapse
I strongly prefer TWRP. I don't recall the exact version number but it been be easily downloaded by downloading the app entitled "goo manager." Once in the app, tap the capacitive menu button and select install recovery script. TWRP is easy to use, completely touch based, and even themable.
Thanks guys, I'm at work now but I'll take a look and see what I got to do to get that recovery straightened out. Thanks again
CWM 6.0.2.3 is now 4.2 capablie just flas with that version and copy the 0 directorys to the root directory and remove the 0 directorys afterword
pe4nut6666 said:
CWM 6.0.2.3 is now 4.2 capablie just flas with that version and copy the 0 directorys to the root directory and remove the 0 directorys afterword
Click to expand...
Click to collapse
Some poking suggests the 4.2 issues with CWM were fixed as of 6.0.1.6.
I think I might fo the TWRP route you guys suggested earlier looks pretty stable nice UI and few added features that I look foward to using, I dont have much time atm being at work but does anyone have a quick and easy way to remove the old recovery and add the new? I know there are prob tuts I'm just short of time and would like to get it flashed at the office. It's fine if not I'll just do some reseach tomorrow
Lukkaz said:
I think I might fo the TWRP route you guys suggested earlier looks pretty stable nice UI and few added features that I look foward to using, I dont have much time atm being at work but does anyone have a quick and easy way to remove the old recovery and add the new? I know there are prob tuts I'm just short of time and would like to get it flashed at the office. It's fine if not I'll just do some reseach tomorrow
Click to expand...
Click to collapse
Just install the new recovery normally; it'll replace whatever was there before.
When I try to flash a new Zip file, it disappears from the directory, both on SD internal and EXTsd card.......Goo manager FC and Rom manager says it's not there?
Any ideas to check for?
Re-installed Goo.im, Rom manager, still no luck.
Is there a way to manually Unzip and install without rebooting in recovery?
Tried to fix permissions, got "an error occurred while attempting to run privileged commands."?
What are you trying to flash?
Also, if you constantly moved from TW to AOSP, you were supposed to flash the zip to restore your SD card AFTER you flash the TW rom. This may be your issue as starting with android 4.2 Google added multi user and moved your files to a folder named /0 (or legacy).
Most of the time I had issues with not locating the zip it was due to this error. My recommendation, download and move the file to the root of your extSD before going in to recovery.
Also, remember Goo.im downloads are saved on the gooim folder in your internal SD card, not the downloads folder.
jibust said:
What are you trying to flash?
Also, if you constantly moved from TW to AOSP, you were supposed to flash the zip to restore your SD card AFTER you flash the TW rom. This may be your issue as starting with android 4.2 Google added multi user and moved your files to a folder named /0 (or legacy).
Most of the time I had issues with not locating the zip it was due to this error. My recommendation, download and move the file to the root of your extSD before going in to recovery.
Also, remember Goo.im downloads are saved on the gooim folder in your internal SD card, not the downloads folder.
Click to expand...
Click to collapse
Thanks. Haven't run any roms on this one. Running stock and rooted with Aviate. I've tried dloading directly to extsd, transfering from my laptop to extsd and SD.
I was trying to flash the Dark Ink lockscreen v2 and 16 ink lockscreen. I'm stumped.....I was able to flash Bravia Engine, Exposed Framework, Multi-Window Mod......it's just the Lockscreen zips. And the only reason I was doing it was because I wanted the ink to work without the S-Pen.....Not that big of a deal I guess. It has to be something simple I am overlooking...
EDIT: Fixed....sort of.... It wouldn't install from any other folder than the CWM Backup folder?? If anyone has an idea as to why, I would love to know?
dmxinc said:
Thanks. Haven't run any roms on this one. Running stock and rooted with Aviate. I've tried dloading directly to extsd, transfering from my laptop to extsd and SD.
I was trying to flash the Dark Ink lockscreen v2 and 16 ink lockscreen. I'm stumped.....I was able to flash Bravia Engine, Exposed Framework, Multi-Window Mod......it's just the Lockscreen zips. And the only reason I was doing it was because I wanted the ink to work without the S-Pen.....Not that big of a deal I guess. It has to be something simple I am overlooking...
EDIT: Fixed....sort of.... It wouldn't install from any other folder than the CWM Backup folder?? If anyone has an idea as to why, I would love to know?
Click to expand...
Click to collapse
Alot of your problems are because you're trying to flash mods on a stock odexed system. If you want to flash rom mods you need to flash a rom that is deodexed. Basically a stock just rooted system breaks up the app in your system. This allows faster boot times. An deodexed system compiles the split up apps together. This will allow you to flash mods and easily modify your system. When you flash a mod you replace the original app. If it's odexed you don't replace the whole app.
Sent from my phone
210euser said:
Alot of your problems are because you're trying to flash mods on a stock odexed system. If you want to flash rom mods you need to flash a rom that is deodexed. Basically a stock just rooted system breaks up the app in your system. This allows faster boot times. An deodexed system compiles the split up apps together. This will allow you to flash mods and easily modify your system. When you flash a mod you replace the original app. If it's odexed you don't replace the whole app.
Sent from my phone
Click to expand...
Click to collapse
Thank You. :good: I thought I flashed the "Stock_rooted_deodexed CALK7," But I used the "back to stock thread" which includes the Odexed version, and what you're saying makes sense.
I live, I learn.....:fingers-crossed:
dmxinc said:
Thank You. :good: I thought I flashed the "Stock_rooted_deodexed CALK7," But I used the "back to stock thread" which includes the Odexed version, and what you're saying makes sense.
I live, I learn.....:fingers-crossed:
Click to expand...
Click to collapse
I've flashed the wrong zip before and it sucks trying to fix mistakes. But after awhile you just backup once a week lol.
Sent from my phone