since we s-off any change for a mod to hide /remove the blasted clock in the taskbar ?
I can do it. give me a few mins....
Here, Try this. (Back up your SystemUI.apk first) and install this to the /system/app directory on your rooted device. Rename as SystemUI.apk
You may have to wipe your Dalvik cache and reboot.
if it blows up revert to your backed up version
"adb push <backup>.apk /system/app/SystemUI.apk"
townsenk said:
I can do it. give me a few mins....
Here, Try this. (Back up your SystemUI.apk first) and install this to the /system/app directory on your rooted device. Rename as SystemUI.apk
You may have to wipe your Dalvik cache and reboot.
if it blows up revert to your backed up version
"adb push <backup>.apk /system/app/SystemUI.apk"
Click to expand...
Click to collapse
i got it to work at first it was messing up bad but do this.
6 simple steps.....
1. copy framework-res.apk to your sdk\tools folder
2. C:\Users\Ken>cd c:\sdk\tools (or wherever your sdk\tools is)
3. c:\SDK\tools>adb reboot recovery
4. c:\SDK\tools>adb shell mount /system
5. c:\SDK\tools>adb push systemUI.apk /system/app/SystemUI.apk
6. c:\SDK\tools>adb reboot
{
"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"
}
Yeah, Kaos is correct. I get in a hurry sometimes and forget to mention "little things"
..like mounting the /system partition b4 trying to write to it.
townsenk said:
I can do it. give me a few mins....
Here, Try this. (Back up your SystemUI.apk first) and install this to the /system/app directory on your rooted device. Rename as SystemUI.apk
You may have to wipe your Dalvik cache and reboot.
if it blows up revert to your backed up version
"adb push <backup>.apk /system/app/SystemUI.apk"
Click to expand...
Click to collapse
Since this is a modified SystemUI, It must be Rom specific right? and if you have a theme this wont work with it right, the theme atleast?
It's the SystemUi from the latest stock Rom. Any of the HTC themes should work fine.
It would probably work with most 3rd party builds as well provided that they haven't added their own Status Bar customizations
sounds good I'll check it out then.
Can anyone make a zip that we can flash in recovery?
steal25 said:
sounds good I'll check it out then.
Click to expand...
Click to collapse
think you can make this work with chod/miks rom
supers2k said:
Can anyone make a zip that we can flash in recovery?
Click to expand...
Click to collapse
+1 ..... This!
supers2k said:
Can anyone make a zip that we can flash in recovery?
Click to expand...
Click to collapse
Any flashaholics want to give this a try? Enjoy Let me know if something needs to be fixed.
*EDIT* Re-doing with a new .zip so I don't kill your root
ranger61878 said:
Any flashaholics want to give this a try? Enjoy Let me know if something needs to be fixed.
Click to expand...
Click to collapse
I'll give it a shot in a bit. Can you put up the stock one too, in case I hate it? Yes I'm lazy and don't want to pull the apk
ranger61878 said:
Any flashaholics want to give this a try? Enjoy Let me know if something needs to be fixed.
Click to expand...
Click to collapse
I tried it. It works. Thank you greatly
Edit: it doesn't work it takes away root in sense but recovery still works. So I used temp root, and over clock and everything works but if you restart the phone the issue happens again
il Duce said:
I'll give it a shot in a bit. Can you put up the stock one too, in case I hate it? Yes I'm lazy and don't want to pull the apk
Click to expand...
Click to collapse
For you Duce, anything I'll throw it up in a few...
--Sent from my 3D Shooter --
ranger61878 said:
For you Duce, anything I'll throw it up in a few...
--Sent from my 3D Shooter --
Click to expand...
Click to collapse
You hobag. Killed root. Use a different zip than SU next time
So there is still some "kinks" to work out before we get a good flashable no clock zip?
il Duce said:
You hobag. Killed root. Use a different zip than SU next time
Click to expand...
Click to collapse
lol... i was in the mood to flash something and wanted to get rid of my clock.. but after that, i will hold off til i am home and can focus in case i lose root.. lol.. poor duce..
@knowledge, no it would be easy, ranger used a silly zip and forgot to remove some of the SU commands in the script.
@pstevep, it removes clock fine, all you need to do is go back into recovery from the bootloader and reflash the "fixed" SU zip that toast made.
here's that fixed zip in case you don't have it:
EDIT: also, I would imagine that in twrp, you could flash the borked noclock.zip then immediately flash SU_fixed.zip and reboot with no issues at all
il Duce said:
@knowledge, no it would be easy, ranger used a silly zip and forgot to remove some of the SU commands in the script.
@pstevep, it removes clock fine, all you need to do is go back into recovery from the bootloader and reflash the "fixed" SU zip that toast made.
here's that fixed zip in case you don't have it:
EDIT: also, I would imagine that in twrp, you could flash the borked noclock.zip then immediately flash SU_fixed.zip and reboot with no issues at all
Click to expand...
Click to collapse
So I would flash Rangers zip, then flash this su zip right after to keep my root and everything intact?
il Duce said:
@knowledge, no it would be easy, ranger used a silly zip and forgot to remove some of the SU commands in the script.
@pstevep, it removes clock fine, all you need to do is go back into recovery from the bootloader and reflash the "fixed" SU zip that toast made.
here's that fixed zip in case you don't have it:
EDIT: also, I would imagine that in twrp, you could flash the borked noclock.zip then immediately flash SU_fixed.zip and reboot with no issues at all
Click to expand...
Click to collapse
alright i am going to try this in a minute.. just thought about it, but i am not on stock.. but it shouldnt matter a whole lot since everything is practically the same right now. so going to throw it down in like 15 minutes after i make a phone call.. will post results..
Related
I would love it if someone could tell me how this can be done. Please and thank you. Done research and all I find is removed clock completely. Well, I like the clock, alot, for when im online n such. Just want am/pm gone cause I know when its night and day :-D. T Y I A.
http://board.teamwhiskey.com/viewtopic.php?f=27&t=1350
thegreatcity said:
http://board.teamwhiskey.com/viewtopic.php?f=27&t=1350
Click to expand...
Click to collapse
Thanks for the link. Where do I push it to? What file. She doesn't give support.. im assuming /system/ then where??
/system/framework
Sent from my SGH-T959 using Tapatalk
that didn't work... :-\ rebooted and pm still there.?
Nope. Nothin .. would it be dumb to just delete am.jar and pm.jar? But Idk why this isn't working...
bdubs4200 said:
Nope. Nothin .. would it be dumb to just delete am.jar and pm.jar? But Idk why this isn't working...
Click to expand...
Click to collapse
Hi,
First, I'm Jocelyn, that was my thread linked earlier.
Second, what phone do you have, and what rom version do you currently have installed?
Third, I highly recommend not deleting the am.jar and pm.jar, but if you want to try it, go right ahead, just please be sure you know how to fix your phone if and when it messes up.
Anyway, the mod linked was made specifically for TeamWhiskey Bionix-v, so if you're using a different rom, there's no guarantee that it will work. It will NOT work on odexed rom's, sorry.
That's also why I posted the code necessary to make the change, so that people can mod their services.jar themselves if they wanted to.
Lastly, anytime you push a system framework file to the phone, its a good idea to wipe your dalvik-cache and reboot, though the next boot will take several minutes since it will be rebuilding the dalvik-cache against the new framework files.
Cheers, =)
Hey thanks for the reply! I have bionix 1.2 installed. dragon kernel which might not matter. I didn't delete am/pm.jar because id have no idea how to repair lol... the only think I didn't try was wipe dalvik cache.
Well just wiped dalvik-cache and still, no luck.. :-( im flustered... any other factors that could be hanging it up??
bdubs4200 said:
Well just wiped dalvik-cache and still, no luck.. :-( im flustered... any other factors that could be hanging it up??
Click to expand...
Click to collapse
Hi,
Wiping the dalvik-cache is pretty much the only thing I can suggest aside from trying it again. Re-download the file, and unzip the services.jar to /desktop or somewhere you're comfortable working with.
Reboot your phone (to make sure the bionix init scripts run and the /system partition is remounted r/w)
Then open a terminal/command line/etc., and do
adb kill-server
connect the phone, and try to push the file again
adb push ~path_to_modified_services.jar /system/framework
then manually wipe the dalvik cache
adb shell
su
cd data
rm -r dalvik-cache
exit
exit
adb reboot recovery
wipe the cache partition from recovery, then do one final reboot.
Hope that works, cheers =)
Why don' t you switch to 24 hour clock?
Sent from my SGH-T959 using XDA App
livbean said:
Why don' t you switch to 24 hour clock?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Because android is all about options mate.
s0niqu3 said:
Hi,
Wiping the dalvik-cache is pretty much the only thing I can suggest aside from trying it again. Re-download the file, and unzip the services.jar to /desktop or somewhere you're comfortable working with.
Reboot your phone (to make sure the bionix init scripts run and the /system partition is remounted r/w)
Then open a terminal/command line/etc., and do
adb kill-server
connect the phone, and try to push the file again
adb push ~path_to_modified_services.jar /system/framework
then manually wipe the dalvik cache
adb shell
su
cd data
rm -r dalvik-cache
exit
exit
adb reboot recovery
wipe the cache partition from recovery, then do one final reboot.
Hope that works, cheers =)
Click to expand...
Click to collapse
Jocelyn thank you! It worked perfectly. Just needed to sleep on it lol. Thank you! And don't leave android!!
{
"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"
}
Jocelyn, you're always awesome!
We need more of your cool themes over at TW forums! I wish I had a tenth of your skills to make what you make ...
Sent from my SGH-T959 using XDA App
I think I have finished my first Black Bar for the Bell Atrix, I need some other people to try it out as well now, and make sure it works for others.
PHONE MUST BE DEODEX
I used the icons from [THEME] Gingerbread Theme V2 (NO ATT)+Black Browser
http://forum.xda-developers.com/showthread.php?t=974112 so thanks to synergye for the icons.
This is a framework-res.apk and services.jar. I don't recommend trying these unless you are confident you can recover yourself from a possible brick (I had many while making this, but it should work now).
BACK UP YOUR FILES BEFORE YOU INSTALL THIS.
I am not responsible for any bricking that occurs.
Please let me know if it works for you. Thanks
Note: I am getting that black signal bar, but I assume its because I am in a basement apartment, it should have green bars when you have a signal.
{
"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"
}
looks nice!
Thanks a lot, works great! I tried to do the same myself but after soft bricking a couple times I gave up. I installed it like this:
adb push framework-res.apk /sdcard/
adb push services.jar /sdcard/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp -f /sdcard/framework-res.apk /system/framework/
cp -f /sdcard/services.jar /system/framework/
sync
reboot
Click to expand...
Click to collapse
can you guys explain how to do this in a safe mode...i've just rooted my phone with aRoot and don't really know how to recover from a soft-brick !
Silent8Strike said:
Thanks a lot, works great! I tried to do the same myself but after soft bricking a couple times I gave up. I installed it like this:
Click to expand...
Click to collapse
Awesome. I figured it should work for everyone but since I learned how to do this while doing this, I couldn't be sure. I know what you mean about the soft bricks, I must have bricked mine a dozen times. You can notice the time in the picture. I refused to give up until I got it.
Thanks for the info on installing, I didn't want to give anyone advice on that, since I was relying on a script kenneth gave me.
I have a Honeycomb Port almost finished, I figure I will try to port most of the ones other people have made for ATT. (all credit goes to them obviously)
aliafi90 said:
can you guys explain how to do this in a safe mode...i've just rooted my phone with aRoot and don't really know how to recover from a soft-brick !
Click to expand...
Click to collapse
You will need to ADB pull your framework-res.apk and services.jar from system/framework as backups in case of a brick. I know I read a good tutorial on this in another thread, I will find it and post a link
thanks ! and another silly question all i have to do is to rename the zip files to .apk and .jar ?
No unzip them. The apk and jar are there, the apk was to big to upload without zipping it
EDIT: as for the backup, if you run backup.bat in this file it should create your backups for you and then if you run installer it should revert back to those backups. I say Should. It did on mine.
EDIT 2: Figured I would upload an installer as well. The code is messy, but it should work. You just need to run installer, it already has the framework-res.apk and services.jar included.
Sent from my MB860 using XDA App
thanks a lot for your help...it's just that when i run backup.bat it says do you see you device listed above ? it's not recognizing my device for some reason...do i have to run it in another folder or it wouldn't make a difference?
aliafi90 said:
thanks a lot for your help...it's just that when i run backup.bat it says do you see you device listed above ? it's not recognizing my device for some reason...do i have to run it in another folder or it wouldn't make a difference?
Click to expand...
Click to collapse
hmmm, thats odd, it should be fine running in that folder. Do you have the phone plugged in via USB and the options set to NONE and USB DEBUGGING ON?
toughbax said:
hmmm, thats odd, it should be fine running in that folder. Do you have the phone plugged in via USB and the options set to NONE and USB DEBUGGING ON?
Click to expand...
Click to collapse
yea and it's still not showing the device...do i need to have adb or anything installed on my computer for this?
aliafi90 said:
yea and it's still not showing the device...do i need to have adb or anything installed on my computer for this?
Click to expand...
Click to collapse
I think all the adb files you needed were in the folder, I think by you seeing the list of attached devices (even if there is none there) it means adb is working.
I am not really sure what could be causing the problem... I would try a Reboot first if you haven't then maybe you could try booting into "Enable USB enumeration early." by holding vol- and power and see if it picks it up then. After it says "Reading ODM fuse: 1" wait 10 seconds or so and run the backup.
Sorry my knowledge of the finer workings of android is still a ways off
It works here as well.
Nice job!
EDIT: Just so you know, I didn't use your install scripts.
NFHimself said:
It works here as well.
Nice job!
EDIT: Just so you know, I didn't use your install scripts.
Click to expand...
Click to collapse
Thanks, couldn't have done it without your deodex.
Sent from my MB860 using XDA App
don't know whats wrong but still not showing anything under devices....is there another way i can do it manually?
aliafi90 said:
don't know whats wrong but still not showing anything under devices....is there another way i can do it manually?
Click to expand...
Click to collapse
if you use command prompt you can enter:
Code:
adb devices
adb pull /system/framework/services.jar services.jar
adb pull /system/framework/framework-res.apk framework-res.apk
That should pull the files into the folder you are in. ex. C:\backup\
When you do the adb devices it should list yours in the list. I don't think that will make much difference in it working though, since that's the same thing the bat does.
Maybe someone who actually knows something can be more use then me.
Kenneth gave me these recommendations if it wasn't working when I was first stuck:
If it isn't listed... you need to check the following:
USB plugged into back of computer
Restart computer
kill-server adb or task manager >> Processes >> end "adb.exe" processes
maybe that will help?
I'm never sure about this but are these files compatible on a mac?
ChongoDroid said:
I'm never sure about this but are these files compatible on a mac?
Click to expand...
Click to collapse
I don't know about the scripts, I would say no just to be safe. The framework-res.apk and services.jar would work though (the first post). I am not sure how you would push them to the device, but I'm sure its been covered in another thread somewhere.
k so i finally did it,though the time on the top right side is not showing anymore
That means the services.jar didn't get pushed. it is still the black font
Sent from my MB860 using XDA App
toughbax said:
That means the services.jar didn't get pushed. it is still the black font
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
if you could add to the first post the you DEFINITELY need to be deodexed for this to work, that would be appreciated
The services.jar file will not work if services.odex is still on the phone, likewise - if you don't deodex correctly, and just delete the services.odex file you will end up bricked.
Prerequisites:
1. You need an unlocked boot loader.
2. You need root.
3. You need a PC with adb that can see your phone
4. Your phone needs to have USB debug enabled
All of these are well documented here in the forum.
On the PC grab the two apk files that the UOT kitched needs:
Code:
adb pull /system/framework/framework-res.apk
adb pull /system/app/SystemUI.apk
Now go to the UOT kitchen and choose your battery style from the battery tab.
Next click on the "File Upload" tab and upload your two files.
Then submit your work to the kitchen and wait.
When the kitchen is done processing, you have a download called UOT-*.zip. download that. And extract it somewhere on your PC. Now you need to push the files to your phone.
Code:
adb push SystemUI.apk /data/local/SystemUI.apk
adb push framework-res.apk /data/local/framework-res.apk
Next you need to adb shell to the phone to remount the system partition as read-write and copy the files to their correct location. From the PC run "adb shell" Then, on the phone:
Code:
su
mount -o remount,rw /dev/block/mmcblk0p29 /system
cp /data/local/SystemUI.apk /system/app/SystemUI.apk
cp /data/local/framework-res.apk /system/framework/framework-res.apk
cd /data/dalvik-cache
rm *
Then reboot the phone. When it comes back up you should have your customized battery.
NOTE: This is all from memory so there may be some minor inconsistencies but the general concept is sound. The main thing you MUST do is unlock the bootloader and you MUST have root (temp-root should be fine)
NOTE 2: There are a lot more things that you can customize using the UOT Kitchen. I've only changed the battery but you should be able to change icons, taskbar, lockscreen and more. So, if you are comfortable doing so, have at it.
And one final note. This is the brute-force method. Once a CWM recovery is created for the Amaze then most (all?) of this is unnecessary and you can just flash the UOT zip file from recovery.
-xdadevelopers-user
after i do the adb pull, where can i find the files it pulled????
Should be in the same adb folder
Sent from my HTC_Amaze_4G using XDA App
what exactly are the inconsistencies? cause i cant get it to stick although i follow your instructions to a "t"
Enzopreme said:
what exactly are the inconsistencies? cause i cant get it to stick although i follow your instructions to a "t"
Click to expand...
Click to collapse
Is your bootloader unlocked?
I try doing this framework but it work's it force close's alot i restored firmware then i tryed it went good then i restarted my phone & now i'm on a black screen the button's show up but no display , what the hell ?
Revolution said:
I try doing this framework but it work's it force close's alot i restored firmware then i tryed it went good then i restarted my phone & now i'm on a black screen the button's show up but no display , what the hell ?
Click to expand...
Click to collapse
bricked again huh?? you building a skyscraper with all those bricks??
Here's a thought-let's all be patient and take one step at a time.
We need recovery before we start buggering around.
Sent from my HTC_Amaze_4G using xda premium
TheSneakerWhore said:
Here's a thought-let's all be patient and take one step at a time.
We need recovery before we start buggering around.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I agree 100% with this.
We need to be able to do backups with Clockwork as well as use other scripts such as fix_permissions, clear dalvik-cache, etc to prevent bricks, FC errors, etc.
Let's work on getting a recovery first.
I fixed it last night
Sent from my HTC Ruby using XDA App
Here you go guys.. If you have CWM Recovery installed, just install my zip.
This.is what I've been looking for. Thx man..
Sent from my phone.
by any chance, do you have a screenshot for this battery percentage update?
what rom does this work on? quiksense? bliss sense?
-FuRBz- said:
what rom does this work on? quiksense? bliss sense?
Click to expand...
Click to collapse
It's only been tested on the 1.36.531.5 stock ROM(My Phone) but I imagine it will work on most all Sense 3.0 ROMS.
Screenshots of an identical mod I released can be found in my other thread here:
http://forum.xda-developers.com/showpost.php?p=11848512&postcount=1
{
"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"
}
Working on enegrys rom w/o issues.
Sent from my phone.
Wonder if it will work on bliss sense....?
Sent from my HTC Amaze 4G using xda premium
I flashed the stock kernel so that wifi could work on Android revolution rom. Wifi works now, but I'm unable to sync my phone with HTC sync, so that I can use adb. Any suggestions to what I can do to set up adb again? (I'm using a windows 7 laptop btw)
dharvey4651 said:
It's only been tested on the 1.36.531.5 stock ROM(My Phone) but I imagine it will work on most all Sense 3.0 ROMS.
Screenshots of an identical mod I released can be found in my other thread here:
http://forum.xda-developers.com/showpost.php?p=11848512&postcount=1
Click to expand...
Click to collapse
holy thread revival...anyone test this out on 1.43 stock?
mrmako777 said:
holy thread revival...anyone test this out on 1.43 stock?
Click to expand...
Click to collapse
you can take Stock statusbar with percentage battery from V2T section in this post, extract framework-res.apk from it and replace battery graphics in it for any you like. You can use a Graphics replace from the same post for that.
4 in 1 Reboot Menu with Extended Power Menu Options
First off, a HUGE thanks goes out to chingy51o for always being a help on whatever it is I may need.
Also, thanks to -sqn and chingy51o for the source in which I ported this from. As well as Nilsp, for taking the time to test with me.
Instructions:
1. This file can either be installed via adb or compiled with your ROM.
2. If you are a developer, I REQUIRE that thanks be given where its due.
3. You are using this file at your own risk. No-one else can be held responsible other than yourself.
This mod is for 1.02.605.6 deodexed and rooted ROM's only
{
"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"
}
DOWNLOAD HERE
FLASHABLE ZIP HERE
Great mod, makes it even easier to flash all these fantastic roms coming our way!
So is this something anyone can apply to any ROM they're currently running just by pushing it via adb ? If so, where do we push it to?
will work on any 1.02.605.6 rom that is deodexed and rooted
So I dig through Root Explorer a bit and found android.policy.jar in /system/framework, I assume we just push it to there then do a reboot and we should be good to go?
rboddy said:
So is this something anyone can apply to any ROM they're currently running just by pushing it via adb ? If so, where do we push it to?
Click to expand...
Click to collapse
Yes, push it to /system/framework/
The question of how to adb push files comes up alot.
A long time ago I made it easy for myself since I do it often by creating the 2 scripts in the attached. Extract them to a folder and all you have to do is drag and drop the files over the appropriate batch file.
Just boot into recovery, mount system, and do this.
For example this jar file would be dragged and dropped on the
2_FRAMEWORK-Push_(Drop Here).cmd
This assume adb is in your system path. If it is not you will find out quick.
Do we need to be in recovery to push via adb on the Rezound? I tried doing it and kept getting this:
c:\sdk\platform-tools>adb push c:/sdk/platform-tools/android.policy.jar /system/framework
failed to copy 'c:/sdk/platform-tools/android.policy.jar' to '/system/framework/android.policy.jar': Permission denied
Am I doing something wrong or is the Rezound just a bit funky? I made sure to set everything to R/W in Root Explorer, since I was originally getting a "Read-only file system" error.
rboddy said:
Do we need to be in recovery to push via adb on the Rezound? I tried doing it and kept getting this:
c:\sdk\platform-tools>adb push c:/sdk/platform-tools/android.policy.jar /system/framework
failed to copy 'c:/sdk/platform-tools/android.policy.jar' to '/system/framework/android.policy.jar': Permission denied
Am I doing something wrong or is the Rezound just a bit funky? I made sure to set everything to R/W in Root Explorer, since I was originally getting a "Read-only file system" error.
Click to expand...
Click to collapse
you must be rooted... make sure the jar is either in your adb folder or you have adb in your path
adb remount
adb push android.policy.jar system/framework
adb reboot
I am rooted, and was trying to do this via adbWireless, so maybe the connection was wonky even though adb said my phone was connected. So I dunno what's happening, so instead I just Dropbox'd it over and moved it via Root Explorer, phone is rebooting now so we'll see if that worked, I'm assuming it should. Maybe the adb remount command would have helped. I'll give it a whirl with that for ****s and grins.
EDIT: Moving inside Root Explorer worked, thanks for supplying this file man! Sooo much better than the damn battery pull lol
How does one make this flashable? I did move it via rootexplorer but it's not showing the extra settings after boot.
Sent from my ADR6425LVW using XDA App
make sure adb is in your enviromental path....
then open cmd
type
adb remount
adb push android.policy.jar system/framework
adb reboot
Thanks bored! Great work! The entire community appreciates you sharing this! Its just in time for another build of CleanROM! Timing could not have been better.
Here is a flash-able zip version of the file. You can add it to OP if you want and can pull it from this post. Eitherway...
Thanks again for this!
-Scott
thanks.... added to op.... i was gonna make one but trying to focus on my rom instead... the 4 in 1 was a must though
That looks great! I always thought the quick settings menu had weird choices on stock.
Wondering if there's any reason you took out bluetooth though? I guess I don't use it that much but I turn it off whenever I leave my car at the shop cuz otherwise my phone calls/music go to the car if I'm hanging out and they have it turned on. lol.
lllboredlll said:
thanks.... added to op.... i was gonna make one but trying to focus on my rom instead... the 4 in 1 was a must though
Click to expand...
Click to collapse
I totally understand how that goes. Thats also a generic flashable that I use. You can add /app/ to it. I use it for testing changes....
So now we can just flash this through recovery?
Evo4gLI said:
So now we can just flash this through recovery?
Click to expand...
Click to collapse
the one scott attached yes
feralicious said:
That looks great! I always thought the quick settings menu had weird choices on stock.
Wondering if there's any reason you took out bluetooth though? I guess I don't use it that much but I turn it off whenever I leave my car at the shop cuz otherwise my phone calls/music go to the car if I'm hanging out and they have it turned on. lol.
Click to expand...
Click to collapse
it wasnt working properly... once i get my rom done i'll back up and try to lay it to rest
Thanks for the flashable zip!!! Worked nice & easy with CWM.
Sent from my ADR6425LVW using Tapatalk
Just as the title suggests this removes the e911 location icon from the status bar and doesn't leave any gaps. Wasn't gonna make a separate thread but it appears that quite a few people are asking questions regarding it in the other thread. For those curious how I did it all I did was grab the LocationController.smali file from the AT&T S4 and put it in are SystemUI and compiled.
{
"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"
}
Download: http://goo.gl/yvOcm
If you are on an odex build then you need to rename the SystemUI.odex to SystemUI.odex.back before flashing.
For those that want the white battery and data indicators just flash this (works for odex and deodexed). http://goo.gl/HHQHt
Any shot of an ODEX version?
wingdo said:
Any shot of an ODEX version?
Click to expand...
Click to collapse
You could try something like this to odex it yourself http://forum.xda-developers.com/showthread.php?t=1879128
Since you only changed the smali, we should only need the .odex portion once that is done, correct?
I would love an odexed version of this as well. I did try to do it myself but failed.
Just flash a deodexed ROM. I won't mess with odex.
ilkevinli said:
I would love an odexed version of this as well. I did try to do it myself but failed.
Click to expand...
Click to collapse
This version works fine on odexed roms. Your entire System doesn't have to be one way or the other, as long as you first remove the original odex file. I installed it this way and it works fine.
adb shell
cd /system/app
mv SystemUI.apk SystemUI.apk.backup
mv SystemUI.odex SystemUI.odex.backup
exit
adb push SystemUI.apk /system/app
adb reboot
spy890 said:
This version works fine on odexed roms. Your entire System doesn't have to be one way or the other, as long as you first remove the original odex file. I installed it this way and it works fine.
adb shell
cd /system/app
mv SystemUI.apk SystemUI.apk.backup
mv SystemUI.odex SystemUI.odex.backup
exit
adb push SystemUI.apk /system/app
adb reboot
Click to expand...
Click to collapse
I figured it would work, I can update the zip to delete the .odex when I get a minute so that way you don't have to do it manually.
One problem with this ... If you try to push in regular mode it says access restricted. If you try to push in Shell SU it says device not found. Thoughts?
dumb question, just rooted fully stock rom is deodexed right?
Sparatan117 said:
One problem with this ... If you try to push in regular mode it says access restricted. If you try to push in Shell SU it says device not found. Thoughts?
Click to expand...
Click to collapse
Reboot into recovery and do it, worked great for me.
sgtakase said:
dumb question, just rooted fully stock rom is deodexed right?
Click to expand...
Click to collapse
Stock ROM (as in, from the factory) is odexed. So, this mod won't work without following the instructions a couple posts back.
you could use a file manager that has root like ES to delete the .odex file too.
mbh87 said:
Just as the title suggests this removes the e911 location icon from the status bar and doesn't leave any gaps. Wasn't gonna make a separate thread but it appears that quite a few people are asking questions regarding it in the other thread. For those curious how I did it all I did was grab the LocationController.smali file from the AT&T S4 and put it in are SystemUI and compiled.
Download: http://goo.gl/yvOcm
If you are on an odex build then you need to rename the SystemUI.odex to SystemUI.odex.back before flashing.
For those that want the white battery and data indicators just flash this (works for odex and deodexed). http://goo.gl/HHQHt
Click to expand...
Click to collapse
I just tried it on a rooted stock machine. All I had to do was delete SystemUI.odex like the OP says and - VOILA!!!
Thank You for making this mod - that icon was driving me nuts!
flatulence said:
I just tried it on a rooted stock machine. All I had to do was delete SystemUI.odex like the OP says and - VOILA!!!
Thank You for making this mod - that icon was driving me nuts!
Click to expand...
Click to collapse
How do I remove this file? I'm having a bit of trouble. I found the file with ES File Explorer, but I can't rename or delete. I also don't see any setting to change read/write properties. Any guide for a noob like me?
scosher said:
How do I remove this file? I'm having a bit of trouble. I found the file with ES File Explorer, but I can't rename or delete. I also don't see any setting to change read/write properties. Any guide for a noob like me?
Click to expand...
Click to collapse
Go into ES settings and enable root (dont use the app so dont remember how exactly). You might run into issues though as I think ES has some conflicts with the stock kernel.
How do I exactly rename the file? Where is it located?
izink said:
How do I exactly rename the file? Where is it located?
Click to expand...
Click to collapse
You have to use a file explorer with root access, then go to /system/app, find SystemUI.odex and rename it to SystemUI.odex.back
Worked like a charm Thanks!
Sent from my SCH-I545 using Tapatalk 2
Do I need a custom recovery (CWM, TWRP) to apply this mod? Or do I just need to be rooted and follow the additional odex instruction in the OP?
Thanks!
Could we manually replace the file using Root Explorer then reboot? Won't that do the same thing?