Disclaimer: Flashing is fun, but get irritating when softbrick, bootlooooooooop etc happens. Nandroid back up and use tb101 themer! [im not selling it enough, this will save u from dead end troubleshooting. I didnt flash YOUR phone but i will help in anyway i can if you run into trouble.
IC.JeLLY_oNGB.BeAN.S [WIP]
[Based off EG04]
[screens]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is it? It is a starter pack. [all other releases will be in form of starter and update packs]
Deodexed and zip-aligned
ALL TB101 mods (-TW4-Havent played with that one yet)
ICS Boot Ani & Sounds [working on boot/bootsound, had this trouble w/ec07]
My ICS/JB Theme [Latest Release [00] (still beta, havent heard back from yall)]
-No xml mods yet, ie. Horizontals and text colors [see Patch]
Gps.config mod
DeBloated_Pro (cleaned most that i was i aware i could, so if anything is gone u want, they are in deodex.zip)
SuperSU [must install after 00]
BusyBox (update if you need to)
More to come....
ICS SOFTKEYS?
In the past with my themes the initial rom flash doesnt boot softkey mods correctly so... YOU will need to patch them. [For Alphas]
Download the attached zip and [unzip&] put in TB101 themer with other softkey imgs, then pull your frameworks in and mod.
MAKE A ZIP WITH YOUR OG FRAMEWORKS WITH DEFAULTS AS MODS [flash if bootloop]
How to install? [updated:10.25]
Download 00&SuperSU [attachment] and put on sdcard root
BACKUP [nandroid via cwm, contacts, sms, apks via TiBU etc]
Flash [install] 00.zip in CWM
Wipe Cache/Dalvik
Reboot (Should boot now )
-if bootloop Flash SuperSU.zip
Reboot
Reboot
Enjoy!
Initial Alpha_00 Release: Here [10.24.12] [will WIPE DATA] [updated:10.25]
-should boot now
Patch_00: Here [must have 00_release installed, you will need to patch this framework again for ics keys etc]
+XMLs now editted
+ICS Tasker skin [hold home]
+ICS 5 bar network pngs now
+build.prop tweaks
Patch_00 Screens
My Goal:
I wish this to be a starter rom for all to own. So input is needed and support will be in form of patch [you can also patch and post] until all system are go. This forum has been best supported over my 3 devices, let learn and continue.
Thank YOU!
credits:
trailblazer101 (everything as always)
dsixda (rom kitchen, updaterscript)
Vertemus (og Domination themer)
and YOU!
As well as credit given in theme thread.
...
DEODEXed ROM [will WIPE DATA, back up nandroid, flash, restore data]
[CWM]: here (thank the poster too!)
debloated
rooted (superuser)
busybox
stock zImage (placeholder)
OG STOCK DEODEX FILES: Here
(just put into cwm zip to add or drag into Trailblazer101s framework maker)
Working on a ROM myself... Will be my first ever.
added oneclick method to deodex ROOTED, BUSYBOX, EG04 STOCK ROM.
Any idea why when I mount cache.rfs in MagicISO there is no recovery folder?
jaizero said:
Any idea why when I mount cache.rfs in MagicISO there is no recovery folder?
Click to expand...
Click to collapse
What are u trying todo?
Extract csc?
Sent from my SPH-M580BST using Tapatalk 2
im in irc
What is the name of the room in IRC? Yup trying to extract the recovery folder.
ciscogee said:
MANUAL or ONECLICK!!! added [10.17.2012]
Requirements:
Rooted device (google "Super One Click" and then when rooted, dl latest SU or superSU)
Busybox installed (via market after root)
ADB installed and working properly (added to path is optimal) ADB added to zip (for one click method)
Flashed and working EG04 rom
EG04_STOCK_DEODEX.zip
and just enough adb knowlege to follow directions
ONECLICK
Download zip, follow README.txt (windows only atm)
MANUAL
Step 1:
Download EG04_STOCK_DEODEX.zip, Unzip and place folders done_app and done_frameworks on root of sdcard.
Step 2:
Open cmd prompt (in sdk/platform-tools/ or any folder if in path)
and copy and past each cmd line. (if any errors occcur, post them).
Code:
$ adb shell
$ su
[you may need to accept permissions by superuser on phone, if 1st time shelling)
# stop
# mount -o rw,remount /system/ /system/
# cp /sdcard/done_app/* /system/app/
# rm /system/app/*.odex
# cp /sdcard/done_frame/* /system/framework/
# rm /system/framework/*.odex
# mount -o ro,remount /system/ /system/
# reboot
[$ & # are showing you root access]
BAM! deodexed!,
use titanium back up to delete bloat you do not want.
Im working on a rom after homework.
Yay we're active again!
Click to expand...
Click to collapse
Nevermind Got it working.
The one click isn't working for me.
The cp command isn't found
Confused
Im a little confused about how to flash this as its different from when I was flashing on ec09. So if someone could provide me detailed steps that would be great
---------- Post added at 02:39 AM ---------- Previous post was at 02:15 AM ----------
Ok so I understand what to do and I rooted successfully. However when I try to update my su binary it fails every time and I cant figure out what to do to get it to become successful so for now I unrooted.
Who here was wanting a way to get the call screen in the ticker working on different launchers? Well, I just figured it out Go to my new thread in theming for new info heh
lets stay on topic!!!!!
jus bs-ing yas!
since we are off topic, when decompiling your modded apks, am i using stock or your modded frameworks to install?
Jaggar345 said:
Im a little confused about how to flash this as its different from when I was flashing on ec09. So if someone could provide me detailed steps that would be great
---------- Post added at 02:39 AM ---------- Previous post was at 02:15 AM ----------
Ok so I understand what to do and I rooted successfully. However when I try to update my su binary it fails every time and I cant figure out what to do to get it to become successful so for now I unrooted.
Click to expand...
Click to collapse
I dont recommend flashing things just to flash them because they are there. Thats how phones get bricked. Read some tutorials on ADB and the Android SDK before diving into code etc... Just my .02
cwm up
lost it if someone has it can u upload, if not ill make another soon.
New rom added
xml patch up...
anyone using these?
Just getting ready to flash cwm and get started, just want to make sure I've got the order right... Flash 00.zip then the patch, both in cwm. Then if I want ics softkeys download the zip and use tb themer to mod framework, make zip and flash from cwm... Right? Maybe... I have yet to use TB's themer.
Sent from my SCH-I400 using xda app-developers app
roaddog665 said:
Just getting ready to flash cwm and get started, just want to make sure I've got the order right... Flash 00.zip then the patch, both in cwm. Then if I want ics softkeys download the zip and use tb themer to mod framework, make zip and flash from cwm... Right? Maybe... I have yet to use TB's themer.
Sent from my SCH-I400 using xda app-developers app
Click to expand...
Click to collapse
Back up you stuff first. Nand and apks etc
Flash rom_00.zip then supersu.zip.
(I don't have too much time to script, I'm way behind in classes due to gb fun) then patch_00.zip
Clear caches
Reboot.
Then when boots legit restore your data nand and apks etc.
And yes for ics keys use tb themer, it will do it for you, just add the png folder in themer dirs
Sent from my SPH-M580BST using Tapatalk 2
Having technical difficulties at the moment, can't get into download mode... Trying another comp now.
Oops... Operator error... Flash after supper.
Sent from my SCH-I400 using xda app-developers app
any idea why it would be stuck at the installing update step? I can't get by that
Related
Credits to Ateisti for this http://forum.xda-developers.com/showthread.php?t=779803
Notes:
I'm posting this for those who are in JM8 and want a vanilla lockscreen but are stuck
UPDATE: and JPH (froyo)
UPDATE: then JPK (froyo)
UPDATE: then JM9 (eclair)
UPDATE: then JPM (froyo)
Current setup when I made this
when JM8:
JM8 of Richthofen http://forum.xda-developers.com/showthread.php?t=780867
Voodoo3 of supercurio http://project-voodoo.org (tho i don't think it's a requirement for this to work, perhaps i could promote it )
when JPH: of Richthofen and Aery http://forum.xda-developers.com/showthread.php?t=783596
when JPK: of Aery http://forum.xda-developers.com/showthread.php?t=790686
when JM9: of Richthofen http://forum.xda-developers.com/showthread.php?t=802909
when JPM: www.samfirmware.com
Always good idea to backup the file first before doing this
Highly recommend enable USB Debugging just so when something goes wrong you can restore from backup using ddms
Disclaimer: DO IT AT YOUR OWN RISK (haven't tried it on other 2.1 roms that's why I specified JM8 on the title. You might want to test it on other 2.1 rom tho if you know what you're doing, just DIAYR)
To install:
Need Root
Need Root Explorer (or similar caliber)
Navigate to /system/framework
Backup existing android.policy.odex (.jar for those using deodexed mods) to PC (either bluetooth, or SD then PC)
Before proceeding...
If you're using a deodexed firmware (applied DocRambone's or Tayutama's or other deodex mod), or you can't find the android.policy.odex file in your framework folder, use the .jar rar
If you're using an untouched firmware (you can see the android.policy.odex file) in the framework folder, use the .odex rar
Extract the rar, put to sd, copy or overwrite inside /system/framework
Reboot
Update 2: Added for JPH
Update 3: Added for De-odexed jar versions
Update 4: Added "menu button" fix for all attachments except android.policy.odex.jm8.rar (sorry guys, you understand how tedious it is to flash back to jm8 just to do this don't you?). You could perhaps do this step yourself to re-odex them yourself and patch the signature. dexopt-wrapper and busybox (from market, or built-in from latest BackfireNL root) needed.
rename your original odex file you backed up to "android.policyo.odex" and copy that to /system/framework
rename your original .jar file you backed up to "android.policyo.jar" and copy to /system/framework
extract android.policy.jar from deodexed-jm8.android.policy.jar.rar and copy to /system/framework
extract and copy dexopt-wrapper to /system/framework
delete patched.odex and existing android.policy.odex if it exists in /system/framework
do this in ADB or terminal app
$ su
# cd /system/framework
# ./dexopt-wrapper android.policy.jar patched.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policyo.jar:/system/framework/services.jar
# bb dd if=android.policyo.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
rename patched.odex to "android.policy.odex"
delete existing android.policy.jar (this is deodexed, greather than 100k size)
rename android.policyo.jar to android.policy.jar
reboot
if it's working (it should), send it to this thread as attachment so i can add it to the first post with your name
Update 5: JPK .odex for "untouched" versions, and .jar for deodexed rom mods
Update 5.1: with the trouble of new JPK kernel "feature" that render current SGS rooting methods (as of this update, Sept. 24) to have read-only access to /system, please see these posts
http://forum.xda-developers.com/showpost.php?p=8305284&postcount=92
http://forum.xda-developers.com/showpost.php?p=8307050&postcount=101 <-- thanks jodue
Update 5.2: Stock Lockscreen for untouched JPK with Recovery 2e as update.zip with Autobackup
http://forum.xda-developers.com/showpost.php?p=8308233&postcount=160 <-- thanks Aery
Update 5.3: Aery--"And now? What will come next? Maybe: How can i go back to Samsung Lockscreen?"
Stock Lockscreen Remover for untouched JPK
Download: http://www.multiupload.com/0KP69HOTIK ;-)
Update 6: JM9 versions added
Update 7: JPM versions added
Update 8: JPA versions added, JP6 odex only
Update 9: added emphasis on JPA being not the official version.
*shot from AdamDowning http://forum.xda-developers.com/showpost.php?p=8204826&postcount=24*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JPM Update
android.policy.odex.jpm.rar
deodexed-jpm-android.policy.jar.rar
JPA Update by Mike.sw (warning: this is for the first leaked JPA version[the one that came around the same time with JP6], not the officially released November JPA version[the one that came around JPO] that everyone has gotten confused with, and please take time to read the whole post if you haven't read them yet [specially the very small disclaimer], thanks for understanding guys)
http://forum.xda-developers.com/showpost.php?p=8615457&postcount=179 <-- odex and deodexed
JP6 Update
http://forum.xda-developers.com/showpost.php?p=8619042&postcount=183 <-- odex by Dirhael
http://forum.xda-developers.com/showpost.php?p=8624410&postcount=194 <-- deodexed by DocRambone
I don't have android.policy.odex in system/framework I have android.policy.jar
Should I rename the .odex to jar?
same here.. a deodexed version would be nice!
Worked perfectly on my JPH!
Thank you!
Works nice on JPH
Works on JPH, too.
Thank you.
added the deodexed jars
Can we use the same method to get epic 4g/fascinate lockscreens?
see topic: http://forum.xda-developers.com/showthread.php?t=770727
I've overwritten both files and rebooted with Root Explorer, but still standard lock screen?
EDIT, Just added the other file again and it works fine, must not have overwritten it! Great!
@AdamDowning
if you're using a de-odexed version of the firmware (applied docrambone's or tayutama's mods or other), or you can't find a android.policy.odex file in your framework folder, use only the .jar rar attachment.
if you're using an untouched firmware or you can see the android.policy.odex file, you need to use ONLY the .odex rar attachment as it depends on the original .jar file.
now if you could restore from your backups please and start it again, i'm updating the first post instructions
EDIT: cool! B-)
I've got it now, I am using an untouched firmware with Ryanza's Lag Fix and Root. Works fine now. I will make a video on ''how to'' later on.
nice looking forward to see it
oswade said:
Can we use the same method to get epic 4g/fascinate lockscreens?
see topic: http://forum.xda-developers.com/showthread.php?t=770727
Click to expand...
Click to collapse
this method isn't about extracting the lockscreen, but instead replacing it with the vanilla one
Could You add this:
If you want to disable the menu key then do this while you still are working on the .smali files:
1. Open LockScreen.smali and find the .method shouldEnableMenuKey()
2. Change "return v4" so it reads "return v6"
3. Save file
Click to expand...
Click to collapse
I <3 this lock screen. Is there any other ones?
i'm sharing the lockscreens I patched on the f/w that I used at the time of build. It's tedious to build for each of all of the leaked releases, so those who aren't in the f/w i mentioned might have to run to the credited threads on the first post and do it themselves
AdamDowning said:
I <3 this lock screen. Is there any other ones?
Click to expand...
Click to collapse
+1 i'm one of those who's been waiting for this since day 1
Excellent work mate! I love it!
Sadly that there's no player controls on it ...
deodexed version worked like a charm, thank you!
Is it incompatible with Circle Battery Mod, right?
*WORKS ON ALL GALAXY NEXUS VARIANTS
*Thanks to MWALT2, seriously go to his page and thank him
*ALL ROMS
*MUST HAVE INSECURE KERNEL!
(Keep in mind official CM9 doesn't have insecure kernel)
* If for any reason this program soft bricks your phone
you are able to flash the rom without wiping data
and it'll all be back to the way it was.(just in case)
* Use at your own risk.
* Please Click the ADS !!!
This program changes your build.prop which overrides any boolean values in your framework-res.apk,
to allow softkeys to be shown or hidden
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CREDITS:
MWalt2 - Insight/expertise
Halfcab123 Project Lead / Batch scripting
DaRooter Project advisor / GUI programming/debugging
JerryFan2000 Button Savior
Galaxy Nexus Forums - apk compiling tutorials
mrx8836350 - originator of mod / inspiration
[VIDEO EXPLANATION]
[INSTRUCTIONS]
Code:
adb remount
adb pull /system/build.prop
echo qemu.hw.mainkeys=1 >>build.prop
adb push build.prop /system/build.prop
adb reboot
DOWNLOAD FOR WINDOWS
Very cool, thanks!
Sent from my Galaxy Nexus using Tapatalk
Wow!!! It's amazing how many advertisements there are!!!
Terror_1 said:
Wow!!! It's amazing how many advertisements there are!!!
Click to expand...
Click to collapse
man.. i thought i was the only one.... x.x
but does it work and will it blend?
I'll probably end up removing them
Sent from my Galaxy Nexus using xda premium
Isn't it easier to just edit the build prop to remove them?
[email protected] said:
Isn't it easier to just edit the build prop to remove them?
Click to expand...
Click to collapse
Pretty sure the build.prop has nothing to do with it.
I'd try this but it looks like there are more ads there than on a porn site! Holy Jesus man!
So far I'm at the reboot step..
"Update Complete...Please Wait For Your Phone To Reboot...Very Important"
I think I'm in a boot loop... been here for a wile its just looping and looping... is that normal?
GinoSylum said:
So far I'm at the reboot step..
"Update Complete...Please Wait For Your Phone To Reboot...Very Important"
I think I'm in a boot loop... been here for a wile its just looping and looping... is that normal?
Click to expand...
Click to collapse
No that definetely shouldn't happen. You'll have to reflash your rom. I'm thinking of taking this down, it works for most, but some people are having problems..
Ya, its just stuck... if i go back to the program and hit the button again, it reboots and just loops again..
---------- Post added at 12:04 PM ---------- Previous post was at 11:50 AM ----------
tried reflashing my rom, still boot looping.. going to have to factory reset.. its cool, happened to run titanium backup and Nova launcher backup yesterday... I know what "Use at your own risk" means... its all good. If you can sure this up, i'll try again.. Thanks
GinoSylum said:
Ya, its just stuck... if i go back to the program and hit the button again, it reboots and just loops again..
---------- Post added at 12:04 PM ---------- Previous post was at 11:50 AM ----------
tried reflashing my rom, still boot looping.. going to have to factory reset.. its cool, happened to run titanium backup and Nova launcher backup yesterday... I know what "Use at your own risk" means... its all good. If you can sure this up, i'll try again.. Thanks
Click to expand...
Click to collapse
Well it should still work, i'm trying to figure out what could have caused a boot loop. what rom are you running ?
halfcab123 said:
Well it should still work, i'm trying to figure out what could have caused a boot loop. what rom are you running ?
Click to expand...
Click to collapse
IMM30B 4.0.4 Stock,rooted with Franco M2 kernel...
GinoSylum said:
So far I'm at the reboot step..
"Update Complete...Please Wait For Your Phone To Reboot...Very Important"
I think I'm in a boot loop... been here for a wile its just looping and looping... is that normal?
Click to expand...
Click to collapse
Takes long? more than 5five minutes?
Its not normal.... Do 4 wipes and recovery you Rom.
Do it manually.
Firs´t make sure u have all driver´s installed on your pc.
Gnex must be Rooted. Unlock is not needed.
Install Java Runtime Environment
Make sure you have LMT 0.96 or Button Savior installed otherwise you will be unable to navigate.
This is how you would edit your framework-res.apk yourself to hide Nav Bar:
Google: Donwload Apktool.
(Make sure apktool and framework-res.apk from your own ROM are in the same folder)
Extract apktool and open command line
1) Type: apktool if framework-res.apk in Command Prompt
2) Type: apktool d framework-res.apk in Command Prompt
3) Locate and edit bools.xml in folder location: framework-res/res/values/bools.xml
(Open with Notepad ++ and edit to "false" : "config_showNavigationBar">false)
4) Type: apktool b framework-res new.apk in Command Prompt
5) Open both original "framework-res.apk" and "new.apk" with WinRar/7Zip
6) Delete "resources.arsc" from "framework-res.apk" and replace it with the
"resources.arsc" from "new.apk"
7) Paste "framework-res.apk" into system/app using Root Explorer and reboot device. Should be ok! I if not, go to Root Explorer system/app find framework-res.apk go to permissions and change to rw-r-r-- Reboot and enjoy!
Cheers!
GinoSylum said:
IMM30B 4.0.4 Stock,rooted with Franco M2 kernel...
Click to expand...
Click to collapse
Here you go:
Reflash your rom like halfcab123 said or do a recovery with cwm if u have a backup.
Take this framework here and paste it with Root Explorer to you system/app
Install LMT 0.96 or Button Savior befora this step!!!
Gnex should reboot automatic.
After reboot, go to Rom Control on setting´s and change hide nav bar. Enable/Disable Nav Bar.
Tell me if work for you.
ChaseRxx said:
Here you go:
Reflash your rom like halfcab123 said or do a recovery with cwm if u have a backup.
Take this framework here and paste it with Root Explorer to you system/app
Install LMT 0.96 or Button Savior befora this step!!!
Gnex should reboot automatic.
After reboot, go to Rom Control on setting´s and change hide nav bar. Enable/Disable Nav Bar.
Tell me if work for you.
Click to expand...
Click to collapse
The rom I'm using doesn't have any rom controls in setting.. its stock, no real mods built in.
GinoSylum said:
The rom I'm using doesn't have any rom controls in setting.. its stock, no real mods built in.
Click to expand...
Click to collapse
Ohh i didn´t see "stock"
Here you go:
4.04 CDMA (Using IMM30B 4.0.4 Framework)
Unthemed:
http://goo.gl/JvcQj MD5: 119159DB001CF408913E4583B3699DF6
With Advanced Power Options, WITH Native Tether(I would still flash the ROM version of this option BEFORE you flash this as I am not sure if the ROM version turns something on/off):
http://goo.gl/v4VUQ
With Advanced Power Options, WITHOUT Native Tether As Far As I KNOW, UNTESTED (I would still flash the ROM version of this option BEFORE you flash this as I am not sure if the ROM version turns something on/off):
http://goo.gl/rWNEq
Enjoy!!! press thank´s button
u guys r trying awfully hard just to get 96 pixels back... how bout we just not use button savior and remap the volume keys as home and back buttons?? xDD
halfcab123 said:
Pretty sure the build.prop has nothing to do with it.
Click to expand...
Click to collapse
Sure it does. There's more than one way to skin a cat. Just add the following to your build.prop and install something like LMT Launcher.
Code:
qemu.hw.mainkeys=1
For the Gingerbread version of this fix, click here!
Greetings and Salutations, Epic 4G Touch Owners and other curious parties!
Disclaimer: Just reading this may cause your head to burst, your phone to catch fire, dogs and cats may do the tango! I am not responsible for any bad stuff that happens from you reading or acting on the information in this thread.
If any ROM authors want to use this fix in their ROMs, I'm completely cool with that. A quick kudos in your credits section would be nice, though.
Background: One of the things that really peeves me off about Sprint is that they want us to think we always have 3G service. I know that I don't have 3G in all of the areas I travel, and I also don't when I am roaming.
Thankfully, the fix is quite simple! It was a bit more difficult than the fix for HTC Sense ROMs as the smali edit was not quite as simple.
This was my primary reason for rooting my phone, that's how aggravating it is for me.
Let's change this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To this:
Credits
Calkulin, sextape, sfhub, Other brave folks - For providing the leaked ROMs for me to fiddle with.
Calkulin - (indirectly) helped me find how to fix this for Sense ROMs which I wrote up here.
Samsung - for a relatively good phone. Hopefully the weird auto-brightness and battery life will be fixed next update.
The brave XDA members who try these instructions and report their success or failure!!!
XDA for being a great source of information!!!
XDA members for thinking outside of the box!!!
The fix:
This fix requires editing your SystemUI.apk file. If you are using one of the fine custom ROMs on XDA, be aware that the you or the author may have already made changes to the SystemUI.apk file, so using my file IS NOT RECOMMENDED.
If you are using Calk's E4GT 2 v1.6 ROM, you can safely use my attached SystemUI.apk file. It may work with other "stock-ish" ROMs, but this is the one I based it on. The attachment will NOT work on stock FF18.
This mod relies on the assumption that your ROM developer has not deleted any of the 1x graphic files in the ROM. The developer CAN theme or otherwise change the images as long as the file names remain the same.
What you need to perform this mod:
1. An Epic 4G Touch ROM ZIP file, or a phone running a Epic 4G Touch ROM -- AOSP ROMs already have the correct indicators.
2. The Java SDK -- So you can run Smali.
3. Smali/Baksmali -- So you can decompile/compile the classes.dex file.
4. Android SDK -- To push/pull files from your phone (adb only).
5. Some sort of archive tool (such as WinRAR, 7zip, etc).
5. A text editor capable of editing UNIX-formatted files. I recommend Notepad++, personally.
Ease Of Use Tips: Install Java SDK first, then Android SDK (if you need adb). Download the smali files (smali-1.3.2.jar and baksmali-1.3.2.jar at the time of this writing) to a new "working" folder where we can do our magic.
KEEP A COPY OF YOUR PRE-EDITED SYSTEMUI.APK FILE, just in case!
Instructions:
1a. [If you are using a ROM ZIP File]: Use 7zip/WinRAR/WinZip to open the ROM ZIP file. Navigate to system\app and extract SystemUI.apk to your "working" folder.
1b. [If you want to grab SystemUI.apk from your running phone]: Use adb to pull SystemUI.apk to your working folder. Example: adb pull /system/app/SystemUI.apk C:\Working\SystemUI.apk
To avoid problems, ONLY USE adb to pull/push SystemUI.apk. Phone apps may cause unknown issues.
2. Go to a command prompt in your "working" folder and run the following command: java -jar baksmali-1.3.2.jar -o SystemUI/ SystemUI.apk
3. Browse to your "working" folder and see that there is now an SystemUI folder inside, with other subfolders. Browse to SystemUI\com\android\systemui\statusbar\policy.
4. Edit the file called NetworkController.smali with your favorite UNIX-format compatible text editor and look for the following text. The key is to search for .line 751. Edit the line below that is in BOLD.
Code:
.line 751
:pswitch_e8
iget-boolean v3, p0, Lcom/android/systemui/statusbar/policy/NetworkController;->mShowAtLeastThreeGees:Z
[B]if-nez v3, :cond_103[/B]
5. Change that line to say #if-nez v3, :cond_103 (add the # at the beginning to comment it out)
6. Save NetworkController.smali
7. Go back to your command prompt, change to your "working" folder and issue the following command: java -jar smali-1.3.2.jar SystemUI/ -o newclasses.dex
8. If there weren't any errors, go ahead and rename the original classes.dex to classes.old and rename newclasses.dex to classes.dex.
9. Open SystemUI.apk in your favorite archiver (if you closed it earlier).
10. Drag the file called classes.dex from your "working" folder into SystemUI.apk and replace the one already in there.
11. Run the following commands to get the file on your phone:
Code:
adb remount
adb push SystemUI.apk /system/app/SystemUI.apk
adb shell stop
adb shell start
You should hear your bootup sound and then the changes should be instantly applied.
To Test:
1. Dial ##DATA# (##3282#) on your phone.
2. Enter your MSL (can be found by typing getprop ril.MSL from Terminal Emulator or adb shell).
3. Scroll to Others at the bottom of the list.
4. Click on HDR/1X Selection
5. Change from Hybrid Mode to CDMA Only Mode. This puts your phone in 1X only mode.
6. Press OK.
7. Verify 1X icon comes within 30 seconds, if you have service.
8. Repeat steps 4-7, substituting Hybrid Mode for CDMA Only Mode to switch back.
How I found this: The files in ICS are different than Gingerbread. Looking for 1x led me to NetworkController.smali. There is a lookup called mShowAtLeastThreeGees (which I thought was hilarious). There are 6 locations that reference this boolean value. The correct one is the a couple of lines before a reference to DATA_1X. I wish I noticed that earlier as I was commenting out each one at a time until I found the last one, which coincidentally was right before DATA_1X. That's what happens when you've got too many things going on at once.
Please let me know whether or not this worked for you. I'd like to make a list of ROMs (with applicable mods) this works for or doesn't work for.
I will do whatever I can to help if you are struggling. If there's something you don't understand, please let me know. I can update the instructions if I accidentally wrote something wrong.
Great work once again
Sent from my SPH-D710 using Tapatalk 2
Finally!!! I will give it a go right now... mShowAtLeastThreeGees - that IS pretty funny. I guess Google programmers do have a sense of humor.
EDIT: Works like a charm. Here's modded SystemUI.apk from Calkuin's newest FE22 ROM, for those who don't want to mess with SMALI edits.
Awesome work! Now help us find where they've buried the lines to hide AM/PM in there
datajosh said:
Awesome work! Now help us find where they've buried the lines to hide AM/PM in there
Click to expand...
Click to collapse
i'll +1 that. Its one of the main reasons I can't stand TW.
nice work
Thanks Nivron. Here is the systemUI.apk for the stock deodexed rom.
Nice work.
Haven't tested it just yet but it looks like they changed it from line 752 to 751 in FF02 for anyone wanting to make the change in the latest build.
Is it possible for someone to update this for the new FF02 build?
DevalB said:
Is it possible for someone to update this for the new FF02 build?
Click to expand...
Click to collapse
Here it is for stock FF02.
dtm_stretch said:
Here it is for stock FF02.
Click to expand...
Click to collapse
To install, I just ADB push?
DevalB said:
To install, I just ADB push?
Click to expand...
Click to collapse
Yeah, or you can use a file explorer and drop it in system/app, then reboot.
dtm_stretch said:
Yeah, or you can use a file explorer and drop it in system/app, then reboot.
Click to expand...
Click to collapse
I tried dropping it into system/app, which caused the device to lock up and FC systemui. I did a battery pull, and now I'm left with no UI icons, etc.
I think it's due to no space left in my /system/ folder. I deleted the failed install of S-voice, which cleared up 20MB, and now it works!
---------- Post added at 04:59 PM ---------- Previous post was at 04:46 PM ----------
So I tried changing my mode from Hybrid to CDMA only, and waited about a minute, and my device stayed on 3G. I even rebooted just to be sure.
Thoughts?
I downloaded the modified FF02 systemui.apk file, and used ES File Explorer to paste it into /systemUI/app/, after backing up (adb pull) the stock systemUI.apk
DevalB said:
I tried dropping it into system/app, which caused the device to lock up and FC systemui. I did a battery pull, and now I'm left with no UI icons, etc.
I think it's due to no space left in my /system/ folder. I deleted the failed install of S-voice, which cleared up 20MB, and now it works!
---------- Post added at 04:59 PM ---------- Previous post was at 04:46 PM ----------
So I tried changing my mode from Hybrid to CDMA only, and waited about a minute, and my device stayed on 3G. I even rebooted just to be sure.
Thoughts?
I downloaded the modified FF02 systemui.apk file, and used ES File Explorer to paste it into /systemUI/app/, after backing up (adb pull) the stock systemUI.apk
Click to expand...
Click to collapse
Are you stock and deodexed? Also have you tried changing the permissions of systemUI.apk to match the other apks in system/app?
dtm_stretch said:
Are you stock and deodexed? Also have you tried changing the permissions of systemUI.apk to match the other apks in system/app?
Click to expand...
Click to collapse
Stock FF02, rooted: http://forum.xda-developers.com/showthread.php?t=1694695
Let me try the permissions, see what it does.
DevalB said:
Stock FF02, rooted: http://forum.xda-developers.com/showthread.php?t=1694695
Let me try the permissions, see what it does.
Click to expand...
Click to collapse
That isn't deodexed and this is a smali edit, so I don't think it will work.
Sent from my SPH-D710 using Tapatalk 2
dtm_stretch said:
That isn't deodexed and this is a smali edit, so I don't think it will work.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You can use a odex rom and with root explorer delete both SystemUI files and replace it with the SyetemUI.apk posted in this thread, it will work I have tried it.
now I'm assuming that you can do the same thing if you know how to take out the systemUI from your odex rom and deodex it and then do the mod.
OP updated for FF18, small change (.line 752 to .line 751). Note that the attachment is still for Calk's E4GT 2 v1.6 ROM and won't work right with FF18.
Deodexed FH13
Here it is for FH13 Deodexed
Hello.
I am running this ROM, and my lockscreen looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to replace the white circle around the icon (displayed when hovering the icon, before releasing the finger from the screen). It just needs to be transparrent.
The developer of the ROM wrote this to me:
final Drawable activeBack = mResources.getDrawable(com.android.internal.R.draw able.ic_lockscreen_target_activated);
...
So change icon ic_lockscreen_target_activated.png
Click to expand...
Click to collapse
The commit to the Git is here: https://github.com/IceColdJelly42/frameworks_base/commit/f1971285b709593873bf8c3effd144087b710104
Question: So far, i understand that i must replace the PNG in the system, but where would it reside? I dont think its in an APK as such, as its the system itself (though that could be apk's aswell...?). I was pointed to this tutorial that should have info on how to do it, but the guide refers to APK-filenames, and again, whats the APK filename? I have no APK in data/app or in system/app that matches "com.android.internal" - so im quite out of luck....?
Any advice on how to proceed is welcome. I have downloaded the PNGs attatched in the ZIP, from the source (git), those are the ones i want to replace with (they are all transparrent as they should be, for my project).
Kind Regards
TwinAdk
The image that you're looking for, is in "framework-res.apk\res\drawable-xhdpi.
When you have changed the image, push framework or copy/paste it in system\framework and reboot!
For security, make a nandroid backup
Okay, so framework-res.apk, and then follow the guide i linked to, and just mirror the structure of the folders in the apk (\res\drawable-xhdpi) - correct?
Or should i unpack the apk, replace pics, resign the apk and push instead?
Also, xhdpi, hdpi, etc.. Whats the difference except the size of the images (resolution)? Is it if i have a phone with lower res, i will need the lower res images?
Thanks so far!
EDIT: You made me laugh there sir..! ALWAYS a nandroid backup! Rather 10 useless backups, than one missing..! :victory:
TwinAdk said:
Okay, so framework-res.apk, and then follow the guide i linked to, and just mirror the structure of the folders in the apk (\res\drawable-xhdpi) - correct?
Or should i unpack the apk, replace pics, resign the apk and push instead?
Also, xhdpi, hdpi, etc.. Whats the difference except the size of the images (resolution)? Is it if i have a phone with lower res, i will need the lower res images?
Thanks so far!
Click to expand...
Click to collapse
With winrar or similar, open the apk, go to res\drawable-xhdpi and change image.
Now, you can push framework in rom and see results
I know that change only resolution of icons in that folder
Here you go. Push to /system/framework/ and set permissions.
Don't know if it will work 'cause I don't have ICJ flashed at the moment. Make a backup before trying it.
I had to compress it before uploading because the limit was 8mb.
Sv: [Q][THEME] Replacing PNG in system file
TToivanen said:
Here you go. Push to /system/framework/ and set permissions.
Don't know if it will work 'cause I don't have ICJ flashed at the moment. Make a backup before trying it.
I had to compress it before uploading because the limit was 8mb.
Click to expand...
Click to collapse
Wow, will try that! If it fails ill investigate tomorrow.
Kind Regards
TwinAdk
- Via the XDA app
Hello.
How can i push it to system/framework? I tried adb shell when in recovery, but i cannot access the framework folder.. /system/ nothing (only bin?)
Also, adb push gave this:
C:\fastboot>adb push framework-res.apk system/framework/framework-res.apk
failed to copy 'framework-res.apk' to 'system/framework/framework-res.apk': No s
uch file or directory
Click to expand...
Click to collapse
Output from shell, while in recovery (only place adb shell works, except from when the phone is booted, but i tried renaming the apk via a file explorer, the system crashed, lol).
~ # whoami
whoami
root
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 488.2M 48.0K 488.1M 0% /dev
/dev/block/mmcblk0p13
315.0M 5.2M 309.7M 2% /cache
Click to expand...
Click to collapse
Any advice?
Put / in front of system. It should be /system/framework/
Sent from my One X
adb works in android, not in recovery
Guich said:
adb works in android, not in recovery
Click to expand...
Click to collapse
It does work in recovery too. You should try it.
Sent from my One X
TToivanen said:
It does work in recovery too. You should try it.
Sent from my One X
Click to expand...
Click to collapse
Ill try to add / in recovery. When i did so in android, i got an error that the filesystem was read only.. I am rooted.
Update: It pushed correctly, but i only see that one file..... After reboot the file was not modified.. Verified with solid explorer.
ls while in recovery:
/system/framework # ls -lah
ls -lah
drwxrwxr-x 2 root root 0 Jan 29 20:28 .
drwxr-xr-x 4 root root 0 Jan 29 20:28 ..
-rw-rw-rw- 1 root root 8.6M Jan 29 16:09 framework-res.apk
Oh well, moved the apk with solid explorer, from sd to system/framework (overwrite exsisting) - phone is rebooting now..
UPDATE: Didnt boot up.. Trying to clear cache and dalvik, then well se.. Think ill have to revert to my dear nandroid
Well, damn it. I replaced the pngs with the files you provided, built and signed without an error. It should be OK but as I said I don't have ICJ installed so troubleshooting is a bit difficult.
Try to do it yourself with apktool.
Sent from my One X
Sv: [Q][THEME] Replacing PNG in system file
Will do. Your apk was considerably smaller than my original, also it struck me that you cannot have guessed my version of the custom rom, and thus the correct apk to use as source. I guess it is modified on each version?
Kind Regards
TwinAdk
- Via the XDA app
Hello.
I tried recreating the APK, using my own framework-res.apk as source.
I also found out how to push to system from CWM - you need to mount /system - DOH!
But it fails.... The phone never boots, i even chmodded the apk with 644, so the permissions are the correct ones..
Back to nandroid backup, and drawing table....
Anyone have any clue as to why the new apk failed? Followed this guide, and loaded the sources to UIsystem,apk and framework-res.apk before editing the APK.
When building the APK i got this output, and it does however not match the output in the guide - the "Could not find sources" does worry me a bit, should it..?
Found the reason for the "could not find sources":
A framework-res.apk is itself the source of other apks( when you install it - apktool if...). So the message that you got is normal.
Click to expand...
Click to collapse
Ref: http://forum.xda-developers.com/showpost.php?p=31832660&postcount=12
The .apk I started with was from 1.5.9 and it was 12mb in size.
Apks tend to lose weight when they are de/recompiled and that's why the finished product was only 8mb.
If the apk method fails, you could build the whole ROM yourself on a linux PC.
Keep me posted!
Sent from my One X
Well, though i used unix before, i dont wish to put the effort into building from source It seems building in a VM fails for many, and it requires quite alot of space...
My apk also lost weight, 8 mb after rebuild.. If the image is there, it does not matter what bitdepth and other fancy settings it was saved with, right? Aslong as the apk was build correctly, and chmodded correctly, the phoen should boot, right (and display an ugly image, if it wants - but at least boot!)
Did you sign the package?
Sent from my One X
No, according to the guide i followed:
Now, final step is signing the apk file.
Remember don't sign the apk if it's a SYSTEM app, unless you have edited the AndroidManifest.xml.
Click to expand...
Click to collapse
I suppose its a system app, as it resides in /system/framework...?
Hi everybody
Since I learned how to use ZipThemer in order to change and apply mods with my Nexus 4, I've made a little How To, it might help some of you. ZipThemer is a very simple app that allows you to create theme files (.zip), ready to be flashed with your favorite custom recovery. It supports ZipThemer and Metamorph files and it is very easy to use so let's start!
As always, you make those changes at your own risks. I can't be responsible for any brick or death of your phone. Be sure to make a Nandroid Backup before any changes.!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Be sure to have :
- A Rooted Nexus 4 (or any smartphone)
- 5 minutes
- The .zip files of the update from 4.2.1 to 4.2.2 that you can download here :
OR
- The .zip files of the update from 4.2.2 to 4.3 that you can download here :
OR
- The .zip files of the update from 4.4.1 to 4.4.2 that you can download here :
(be sure to know what version you're using, it's in red :laugh
- The theme you have choosen in a .zip file
0- If you're using a KitKat Rom and want to instal SoftKeys, go to that step that @bigwavedave25 showed us, else, continue to step 1
1- Begin by downloading Android App ZipThemer right there or directly from your phone.
[font=Arial, Verdana, sans-serif]
[/font]
2- Right after the installation, launch ZipThemer for the first time
3- A little window appears, asking you to Update Edify (the window is missing in the screenshot above because that's not the first time I launch Zipthemer.). For this, simply press the menu button and Update Edify
4- Press Browse in order to find and select the convenient file chosen in this thread above, that you have downloaded and copied in your phone. Then press Configure, wait a moment (few seconds) and then go back to the principal window by pressing your "Back" button.
5- Pick a theme you like in any website/forum and copy it to your cellphone, and then select it by pressing +Theme and choosing it in the file explorer (I use here a new lockring found in XDA). It appears now over the menu and, you can choose its destination with +Output and then press Build it!
6- ZipThemer is taking care of the file, usually not very long, and will notify you when it is done !
7- Flash your theme with your favorite Recovery (there are many How To to learn how to do it ) but don't forget to systematically Wipe Cache/Wipe Dalvik Cache (recommended !) and reboot your phone. You just have to enjoy the result!
If you have found that useful, don't forget the
button
Remove gradient..
So if I wanted to flash something that removes the gradient in settings/menus/etc, so it's all black, how would I do that?
ace7196 said:
So if I wanted to flash something that removes the gradient in settings/menus/etc, so it's all black, how would I do that?
Click to expand...
Click to collapse
Just change the background_holo_dark.png in framework-res.apk/res/drawable-nodpi to black.
I tried this method on my Gnex (you posted over on this thread:http://forum.xda-developers.com/showthread.php?t=1413582), but I still have the boring white stock softkeys. I downloaded the zip file from here https://www.dropbox.com/sh/eglqkhlw33clfhz/FQ7oMslrI8/Softkeys/Airbrush Blue and did the edify part, then configure. Then I did unzip part on a MMZT file. After that I went into recovery and flashed the new "update" zip file. Did I miss a step? I'm not sure what I'm doing wrong. Nothing stopped working which is good, but not nothing changed either.
Which zip file did you use to 'Update Edify' ?
The zip file that was provided in the first post from the dropbox link. This one: de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip.
azertguigui said:
Which zip file did you use to 'Update Edify' ?
Click to expand...
Click to collapse
Re: [How To] Use ZipThemer to flash your themes in 4.2.2 stock !
edit: I derped, move along.
Sent from my Nexus 4
Thanks alot man, I have added a link to my softkey thread!
I can't seem to download the zip file to update edify that's in the op. All I get is a photo of the box icon? I tried typing the link in my chrome browser myself but it says the page cannot be opened? Am I missing something?
Sent from my Nexus 4 using xda premium
I've just try with my nexus 4 and it work perfectly...
I'll reupload as soon as I go back from holidays.
This exactly what I needed. Big thanks mate! Very good job!
EDIT. I tried, but when I select the theme it says:
Can't find a theme control file in /storage/emulated/0 in Nameofmytheme.zip
Any ideas?
Yes, I think your .zip is already a theme file. Try to flash it directly
is there a place to get themes in .zip form? I cant find any.
proper69 said:
is there a place to get themes in .zip form? I cant find any.
Click to expand...
Click to collapse
Yes the Nexus 4 locking and softkeys threads that you can find there
http://forum.xda-developers.com/showthread.php?t=2005937
http://forum.xda-developers.com/showthread.php?t=2082138
Need ZipThemer. Also, most of the mods available in this section need this app
I am not really sure why in the instructions it says to use that zip file from his box.net account. You should be able to simply use the exisiting rom file that you are on to update edify, then follow the remainder of the steps to build a flashable zip. I personally used my nightly for linaro tackleberry rom to update edify and then built my zip worked great and no need to download an additional file for zipthemer.
Stroid01 said:
I am not really sure why in the instructions it says to use that zip file from his box.net account. You should be able to simply use the exisiting rom file that you are on to update edify, then follow the remainder of the steps to build a flashable zip. I personally used my nightly for linaro tackleberry rom to update edify and then built my zip worked great and no need to download an additional file for zipthemer.
Click to expand...
Click to collapse
Yes it is quite easy to update edify with a custom rom because they are all .zip files. When you're are stock, the rom files are .tar.gz (some kind of Linux) files. So I decided to test it with an update file (from 4.2.1 to 4.2.2) for the Nexus 4, which is the .zip file in the Box account (this Box account t is mine and I use it for all my Android files)
That's why the title of the thread shows it as a tutorial for stock rom
Sadly enough I get the following on CWM 6.0.3.1
"Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by google in android 1.5.
Please switch to Edify scripting to create working update zip packages.
Click to expand...
Click to collapse
----
I followed all the steps. Didn't you specify "edify" in one of the steps then?
Any hint on how to bypass this or what I did wrong? (was trying to make a pokeball lockring )
Ibkevin said:
I can't seem to download the zip file to update edify that's in the op. All I get is a photo of the box icon? I tried typing the link in my chrome browser myself but it says the page cannot be opened? Am I missing something?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Here, try this
Foxnov1990 said:
Sadly enough I get the following on CWM 6.0.3.1
----
I followed all the steps. Didn't you specify "edify" in one of the steps then?
Any hint on how to bypass this or what I did wrong? (was trying to make a pokeball lockring )
Click to expand...
Click to collapse
I' ve never had such a message.I have to admit that I use the TWRP recovery and it works perfectly. Are you sure you used a N4 file and not a GNex file (i was guessing it was the same but i'm not sure)
Apart from that I've no idea, sorry
azertguigui said:
I' ve never had such a message.I have to admit that I use the TWRP recovery and it works perfectly. Are you sure you used a N4 file and not a GNex file (i was guessing it was the same but i'm not sure)
Apart from that I've no idea, sorry
Click to expand...
Click to collapse
Ah I'm using CWM, maybe it has purely something to do with that...
Foxnov1990 said:
Ah I'm using CWM, maybe it has purely something to do with that...
Click to expand...
Click to collapse
That would be surprinsing...
Send me your softkey file, I'll try do do it on my N4 and send you it back