Can someone load up a stock GSM 4.0.4 systemUI? I put this mod on my phone last night that was suppose to ONLY be a battery percentage mod but ended up changing all my UI buttons. I hate it. And like a dumbass, I didn't backup before I flashed it.
So if anyone can upload a zip file of the stock 4.0.4 systemUI that I can apply via CWM would be great. ( I have the GSM nexus so I need the systemUI from it a verizon or sprint UI wont help me)
Thanks!
Hi,
Here it is:https://rapidshare.com/files/500812190/Stock_SystemUI.zip
Sweet! Thanks so much. I shouldn't need the systemui.odex file should I? If I do could you load that up for me as well?
Re,
Heu...You're on a stock rom rooted?Or a custom rom,which one?
Because,yes the SystemUI.apk I've posted is from a stock rom but deodexed...
Awesome. It works. I gave you some thanks.
Re,
Ah ok,good to hear!
I answered,but were answered at the same time ,but it works,so...
Im on stock rom. So it should have been an odex. But i flashed it in CWM and everything works fine. I had always though that if you flashed a deodex on an odex ROM it wouldnt boot, but it seems eveything is fine.
Re,
In case of issue,maybe test this:http://forum.xda-developers.com/showthread.php?t=1514576&highlight=odex...
Just for re-odex your SystemUI.apk?I've tested this on a deoxeded rom with no issue,but on also an odexed rom with just an app deodexed,I don't know...Backup before,if you want to test
I do not know if I was clear...?
Instead of trying to re-odex the file, why not just grab it directly from the stock image?
Download the factory images from here, extract the system.img from within, convert it to an .ext4.img by using this and then (for Windows users) use this to mount the .ext4.img and extract the file.
Know you've learned how to grab any file from the stock images in case you mess up any of your files...
Related
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!
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
Well i am soon going to start building a rom along with a friend of myne, and anyway i have everything set besides one key component.. i cant find a link for a stock 4.0.4 (ICS) ROM.
& if anyone could provide a link for one that would be great.
Thanks, MrModMan
try this Thread.
This is the .ftf which doesn't contain the system, META-INF etc. folders in the .zip
EDIT: if i don't have the necessary folders like: system in the .zip it won't work with Cygwin.
This is not my work. I did not create this. I only attempted to make it work on stock zvc odex.
Thanks to Scotty_Two for originally creating this for deodexed zvb roms.
http://forum.xda-developers.com/showthread.php?t=2198755
Adhvanlt helped me to get it to work on my locked but rooted lgog.
Since the release of the zvc update, it didn't work anymore. I loved the look, so I decided to sit down and redo what was done before. This time I was unlocked, but still needed to create an odex file for it. So following the steps I did before with adb I was able to make it work on my stock odex zvc phone.
The link to the zip file is below if you want to try it out on your phone. Again, this was done on a stock ROM.
Install at your own risk
I am NOT responsible for any damages or any bricks.
Make a nandroid backup before using.
Copy the stock LGSystemUI.apk and LGSystemUI.odex files from /system/app folder to your sdcard in case you want to revert back.
To use:
Download the zip file
Extract the files.
Copy the extracted files to: /system/app folder
Change permissions on both files to rw-r-r
Reboot
Enjoy
This is NOT flashable
https://db.tt/GOy768CI
Sent from my phone.
Here another screenshot
Sent from my phone.
Anyone try this? How bout a flashable link?
idk how i got here...
treezy26 said:
Anyone try this? How bout a flashable link?
idk how i got here...
Click to expand...
Click to collapse
I tried it on the stock rom unlocked and it works great. Well done. It only takes about two minutes to unzip and replace the original files in system/app. Btw, I would move the original files to your SD card to keep in case you want to go back to the stock look.
Sorry I don't have a flashable version as I don't have the knowledge to create it. If someone wants to either show me or do it, have at it. But a quick swap with a root explorer takes no time at all.
Sent from my phone.
I installed this onto the optimus ROM. I extracted the apk from the deodexed original Scotty_Two thread and pushed it into system just as it says in Scotty's thread and it worked on reboot. Just over write and when system starts failing just reboot FTW.
Sent from my LG-LS970 using Tapatalk
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