if this is a repost, sorry, but i cant seem to find my original...
after flashing fresh 1.1 and gumbo kernel last week, i flashed a new lock screen from here (http://geekfor.me/kitchen/lockscreens/). i found a new lockscreen today and flashed it, but it superimposed the new image over the old. (the lockscreen did function properly tho, it simply had 2 pictures/droids superimposed over each other) for now, i did a back up and i'm good but...
is there any EASY way around this? the hard way, i believe, is i can just reflash fresh then flash another lockscreen right? but if i reflash fresh, do i need to reflash gumbo kernel too?
SOOO confused when dealing with this stuff!
thanks all!
I havent ever seen this but one thing you could try doing is downloading Freshs pre kitchen, plug your phone up, start the kitchen, go to tools and there should be a button to clear wallpaper cache. Once you clear the cache, try flashing the lockscreen you want again.
kbizzle said:
I havent ever seen this but one thing you could try doing is downloading Freshs pre kitchen, plug your phone up, start the kitchen, go to tools and there should be a button to clear wallpaper cache. Once you clear the cache, try flashing the lockscreen you want again.
Click to expand...
Click to collapse
but is the lockscreen image itself "wallpaper cache"? because i did use prekitch to clear a personal pic i had on there as wallpaper...but i'm talking about the image that actually slides down when you unlock the phone.
kbizzle said:
I havent ever seen this but one thing you could try doing is downloading Freshs pre kitchen, plug your phone up, start the kitchen, go to tools and there should be a button to clear wallpaper cache. Once you clear the cache, try flashing the lockscreen you want again.
Click to expand...
Click to collapse
Yeah, I had some problems too when I went to a diff rom. I couldn't even get the pre-kitchen to clear it properly. I ended up having to make my filesystem read/write again, and then I manually deleted all of the default wallpapers used for the lock screen.
However, it looks like Noj has created a lock screen zip that will take care of it for you (see post #47 in the comments)
http://geekfor.me/kitchen/lockscreens/
Just flash that zip from recovery, and then flash your new lockscreen you want. I found some cool ones at the top of that page too
kmartburrito said:
Yeah, I had some problems too when I went to a diff rom. I couldn't even get the pre-kitchen to clear it properly. I ended up having to make my filesystem read/write again, and then I manually deleted all of the default wallpapers used for the lock screen.
However, it looks like Noj has created a lock screen zip that will take care of it for you (see post #47 in the comments)
Just flash that zip from recovery, and then flash your new lockscreen you want. I found some cool ones at the top of that page too
Click to expand...
Click to collapse
i was having this issue on gumbo before and after a complete wipe. This fixed it from overlaying the default lockscreen. I still cannot get the lockscreen background to go away. I have cleared the cached lockscreen numerous times with the kitchen and nothing works.
I couldn't get it to go away either with the TTG Rom and another one after flashing on top of Fresh 1.0-1.1 I had to do this through ADB
Adb Remount
Adb Shell
rm -r /data/misc/lockscreen
reboot
and if that doesn't work then try this
ADB Remount
ADB Shell
rm -r system/etc/lockscreen/port
reboot
Lessthantito said:
ADB Remount
ADB Shell
rm -r system/etc/lockscreen/port
reboot
Click to expand...
Click to collapse
this worked!
Thanks so much!
Related
I am using Modaco 2.0 Beta
I would love to remove the curved grey bar in the lockscreen apk, which I am led to believe is com.htc.resources.apk and is located in system/framework
within that is a folder res/drawable-port-480x320, which contains the 4 .png files.
Thing is, if I simply remove them, it throws the phone in a continuous loop when booting up, so obviously it is looking for something to go int here.
Is there any way anyone can tell me what should be there if I simply want to remove the grey bar ?
grifforama said:
I am using Modaco 2.0 Beta
I would love to remove the curved grey bar in the lockscreen apk, which I am led to believe is com.htc.resources.apk and is located in system/framework
within that is a folder res/drawable-port-480x320, which contains the 4 .png files.
Thing is, if I simply remove them, it throws the phone in a continuous loop when booting up, so obviously it is looking for something to go int here.
Is there any way anyone can tell me what should be there if I simply want to remove the grey bar ?
Click to expand...
Click to collapse
I am not sure what Modaco's lockscreen looks like but you can get a clear lock screen from fresh and push it in with the pre-kitchen. I dunno exactly what you are wanting to remove though. Just removing pictures isn't a good idea, open it in photoshop or something and make it transparent.
If you don't know how to do that, you can give me your file and Ill see what I can do.
I was wondering the same thing. I moved from fresh 1.1 to test this out, but I liked having one of Noj's lockscreens. I tried to use the kitchen to push it and it worked but that stock gray bar was still there blocking it. any help would be appreciated
wtphoto said:
I was wondering the same thing. I moved from fresh 1.1 to test this out, but I liked having one of Noj's lockscreens. I tried to use the kitchen to push it and it worked but that stock gray bar was still there blocking it. any help would be appreciated
Click to expand...
Click to collapse
Griff emailed me earlier saying he had figured that out. Maybe we can get him to post back his fix.
OK, what you need to do if you are running Modaco is
go here
http://geekfor.me/kitchen/lockscreens/
and download one of the first 2 lockscreens, either (ClearLock w/ 1.1 icons) or (ClearLock w/ Stock icons)
Once you;ve installed the clear lockscreen, you can then update the wallpaper.
grifforama said:
OK, what you need to do if you are running Modaco is
go here
http://geekfor.me/kitchen/lockscreens/
and download one of the first 2 lockscreens, either (ClearLock w/ 1.1 icons) or (ClearLock w/ Stock icons)
Once you;ve installed the clear lockscreen, you can then update the wallpaper.
Click to expand...
Click to collapse
tried this and it got rid of the bar but when I push one of the other lockscreens it doesnt have the bar any more but it shows a wallpaper behind the lockscreen. I tried useing the fresh kitchen to clear the lockscreen cache but still does it.
any ideas?
Maybe try using the lockscreen cache removal tool on the kitchen ?
grifforama said:
Maybe try using the lockscreen cache removal tool on the kitchen ?
Click to expand...
Click to collapse
tried it and still shows the stock wallpaper behind it. I also tried just running it through recovery as an update.zip and still came up that way. im kinda confused on it lol fresh kitchen has worked for stuff like this every other time I have tried it.
edit:ok got it I had to manualy go into system/etc/lockscreen/port/ and clear everything out of it
grifforama said:
OK, what you need to do if you are running Modaco is
go here
http://geekfor.me/kitchen/lockscreens/
and download one of the first 2 lockscreens, either (ClearLock w/ 1.1 icons) or (ClearLock w/ Stock icons)
Once you;ve installed the clear lockscreen, you can then update the wallpaper.
Click to expand...
Click to collapse
wtphoto said:
tried it and still shows the stock wallpaper behind it. I also tried just running it through recovery as an update.zip and still came up that way. im kinda confused on it lol fresh kitchen has worked for stuff like this every other time I have tried it.
edit:ok got it I had to manualy go into system/etc/lockscreen/port/ and clear everything out of it
Click to expand...
Click to collapse
I was gonna say post a screenshot, but I see you got it fixed.
let me know if you need any help with my lockscreens, I can always make a patch to clear just about anything up.
wtphoto said:
tried it and still shows the stock wallpaper behind it. I also tried just running it through recovery as an update.zip and still came up that way. im kinda confused on it lol fresh kitchen has worked for stuff like this every other time I have tried it.
edit:ok got it I had to manualy go into system/etc/lockscreen/port/ and clear everything out of it
Click to expand...
Click to collapse
NM Got it myself.
I am having this same problem I can't seem to get rid of the lockscreen background image I have done:
rm -r /data/misc/lockscreen
and flashed every clear lockscreen .zip I could find if I do what Wtphoto did with system/etc/lockscreen/port/ would I do something like:
rm -r system/etc/lockscreen/port/
I am so used to the clear lockscreen I can't do without it now and it's been so easy to get rid of with Fresh Roms but for some reason any other Rom that I flash will not let me remove the stock backgroung image
Lessthantito said:
I am having this same problem I can't seem to get rid of the lockscreen background image I have done:
rm -r /data/misc/lockscreen
and flashed every clear lockscreen .zip I could find if I do what Wtphoto did with system/etc/lockscreen/port/ would I do something like:
rm -r system/etc/lockscreen/port/
I am so used to the clear lockscreen I can't do without it now and it's been so easy to get rid of with Fresh Roms but for some reason any other Rom that I flash will not let me remove the stock backgroung image
Click to expand...
Click to collapse
im not sure if that command would work or not. I just went into /system/etc/lockscreen/port and manually remonved all the files in it there are 6 wallpaper.jpg's and 1 wallpaper.png. its really not that much work to just go in and remove them all
wtphoto said:
im not sure if that command would work or not. I just went into /system/etc/lockscreen/port and manually remonved all the files in it there are 6 wallpaper.jpg's and 1 wallpaper.png. its really not that much work to just go in and remove them all
Click to expand...
Click to collapse
Sounds like you used Droid Explorer or similar to do so
Is it possible to add the clear lockscreen to AOSP 1.6 after it's on the phone?
athlet1c said:
Sounds like you used Droid Explorer or similar to do so
Click to expand...
Click to collapse
no on the droid explorer I was in adb but I dont know all the different commands that are available in it so I just used the ones that I know. might be the long way but hey it works. lol
I cant seem to get rid of the back round screen behind the clear lock. I might just make a transparent one but i was wondering how you were able too Ill try another thing
Ecit NVM I FInally got it to work... installed the clear lock screen zip from Geeksfor.me and Removed the screens in /system/etc/lockscreen/port then reboot .In Business now
I have never had a problem getting rid of the background lock image before with Fresh's Pre-Kitchen or rm -r /data/misc/lockscreen but on the TTG1.6 Rom and MoDaCo 2.2 I could not remove the image but rm -r system/etc/lockscreen/port worked after looking through about 10 different threads on removing this image thanks to whoever figured that out
wtphoto, how did you remove those images? I am using root explorer but the images say they are read only. did you have to put a command in the terminal? I have better terminal installed so I could use that if I need to, just need the command code. Thanks in advance.
corybucher said:
wtphoto, how did you remove those images? I am using root explorer but the images say they are read only. did you have to put a command in the terminal? I have better terminal installed so I could use that if I need to, just need the command code. Thanks in advance.
Click to expand...
Click to collapse
I wasnt using a terminal I was using adb but I would assume it would be the same in the terminal you need to remount the system as read/write
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
wtphoto said:
I wasnt using a terminal I was using adb but I would assume it would be the same in the terminal you need to remount the system as read/write
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Awesome, got it thanks for the help. Wish I knew more about commands and such but I am trying to learn.
SO, let me give you a little story.
One day i came up with the lovely idea to use NinjaMorph on my stock rooted BLUR ROM. after experiencing some cool mods, i tried to make my lockscreen back to stock... bad idea. after finding some of what appeared to be stock lockscreen pngs in my framework i changed my lockscreen into what now looks like a peice of ****. i tried to get them back through like a back up but i didnt have a backup made...
SOOOOO.... does anyone have a fix for my issue OR have .PNG'S for the stock android lockscreen i could use????? I wud really appreciate it
P.S. Because of my issues i have sadly been forced into the stupidity of gummyJAR and my phone wont let me install liberty 1.5
bretth18 said:
SO, let me give you a little story.
One day i came up with the lovely idea to use NinjaMorph on my stock rooted BLUR ROM. after experiencing some cool mods, i tried to make my lockscreen back to stock... bad idea. after finding some of what appeared to be stock lockscreen pngs in my framework i changed my lockscreen into what now looks like a peice of ****. i tried to get them back through like a back up but i didnt have a backup made...
SOOOOO.... does anyone have a fix for my issue OR have .PNG'S for the stock android lockscreen i could use????? I wud really appreciate it
P.S. Because of my issues i have sadly been forced into the stupidity of gummyJAR and my phone wont let me install liberty 1.5
Click to expand...
Click to collapse
Ok a couple of things here. When you mess your own phone up because of user error, it's not polite to bash on other's work for no reason, at least that's how your last comment comes across. I'll be nice and help you out but don't be surprised if a little flammage comes your way.
Second, people aren’t going to have random .png files laying around, it would be a long shot for what you are asking for, just being realistic. You are more then likely going to have to back up all your files and do a factory reset in the event someone does not have the .png you need.
If you want to give it a try with Root Explorer or transferring the stock res.apk file to your computer, the file you need will be in your update zip file. Once you find it, go to system, framework, framework-res.apk and find the file name you need. If you are using Root Explorer to find, it will need to be extracted.
sorry i didnt mean to be insulting. i have tried a factory reset but because changed the framework.res.apk it wont change back. im actually now taking some of the pngs from gummyjar and trying to give my blur a gingerbread notification bar
bretth18 said:
sorry i didnt mean to be insulting. i have tried a factory reset but because changed the framework.res.apk it wont change back. im actually now taking some of the pngs from gummyjar and trying to give my blur a gingerbread notification bar
Click to expand...
Click to collapse
You can always sbf and factory reset don't play with things until you know the full extent of ur own actions
Sent from my DROIDX using XDA App
bretth18 said:
sorry i didnt mean to be insulting. i have tried a factory reset but because changed the framework.res.apk it wont change back. im actually now taking some of the pngs from gummyjar and trying to give my blur a gingerbread notification bar
Click to expand...
Click to collapse
here is another way to fix your issue....
Take the attached framework-res.apk (taken from an unmodded gummyjar 2.5) and copy it to the root of your sdcard.
Connect your phone to your computer and put it in charge only mode. Next, do the following from a command prompt in windows. At the end of each line, press enter (not trying to be insulting, just for clarity sake).
adb shell
su
mount -o rw,remount /dev/block/mtdblock4 /system
cp /mnt/sdcard/framework-res.apk /system/framework/framework-res.apk
cd /system/framework
chmod 644 framework-res.apk
next open another command prompt (done to keep the one with shell access open).
Type from 2nd command prompt:
adb remount
adb reboot
Your phone will then reboot, and you should have all your original framework... Note that any theming you have done to the framework images will be undone, but your phone will be fixed.
PS having your phone in a bad state on one ROM should not prevent you from using another ROM. When you install a ROM, most times the new ROM's will format the existing /system partition to ensure that remnants of an old ROM are gotten rid of.
And as stated above, please don't bash on the devs. Kejar31 gives a lot of his time to developing his ROMS (as does any other dev), and they give out their work for free! =)
Hope these steps work for you, post back if you have issues/questions.
This is the "OP" or the Original Post #1....read it before asking any questions that my be answered in this post or in any of the following links!
Background: I started this thread because of the explosive growth of MikFroyo's Roms. The thread got so clogged with total new user's questions that it became difficult to find real answers to real problems. Not that new users can't learn, but I wanted to try and create a place for people who don't depend upon RomManager to control their lives!
Look, the way I see it, if you were smart enough to root your phone and start flashing new ROMs (that is the correct way to spell it btw, not roms, it is an acronym after all!), then you deserve concise answers to your issues based upon my experience in flashing phones that I have gathered in the past 3 years since I first started flashing things for my Razr phone.
I will assume you know how to use, and have properly setup, adb on your home computer. Yes, many of the commands you may see me or others post could be done through a terminal window on your phone, but your life will be much easier and more efficient if you have adb setup and working correctly on your home computer or laptop!
Here as a begining are some of the more useful posts I and others have made regarding flashing MikFroyo ROMs and some of the issues associated with this endeavor:
No touch tone recognition using MikZ?? Check solution here!
Thread that deals with changing the Power Control Widget in Notification Bar
Nick's repost of Mitchellvii's solution to Market D/L problems
Stopping your Market from Updating and losing it's skin
Nick's updated adb installation guide
joeykrim's adb getting started links
My "How to make apps2sd work" on your phone guide
The most recent repository of Netarchy Kernels
How to "flash_image" a recovery image to your phone
Pushing "Removed apps" from MikFroyo to your phone
Having "Wifi scans constantly but cannot connect" issues with MikFroyo?
Using a2sd "Sysinfo" command to learn alot about your phone's current status
Info about different Kernel types here
General statement I posted about different hardware versions
A Hardware Engineer (me ) view on "Color vs Black and White" Themes and battery useage
Much more to follow, but I thought this would get the ball rolling!
Tapatalked from my SUpersonic...
You said razr Mr. Link man
sent from Kings Ultra UNleashed
Could you post how to get adb working? I tried it a while ago but havnt given it another shot
Fr3sh2De4th said:
Could you post how to get adb working? I tried it a while ago but havnt given it another shot
Click to expand...
Click to collapse
This is not my work, but a good starting point is provided at: http://forum.xda-developers.com/showthread.php?t=694250
Browse the entire thread if you like, but the download links are in the 1st post. Thanks for the guide goes to joeykrim.
I just flashed mikfroyo, got it working, then flashed the kernal that you suggested.
My wifi turns on for a second, does not connect, then turns off and says unable to scan for wifi??? I did do a full wipe, cache and dalvik before flashing mikfroyo.
Any suggestions?
chefdrew said:
I just flashed mikfroyo, got it working, then flashed the kernal that you suggested.
My wifi turns on for a second, does not connect, then turns off and says unable to scan for wifi??? I did do a full wipe, cache and dalvik before flashing mikfroyo.
Any suggestions?
Click to expand...
Click to collapse
All in one blow flash the rom and kernel back to back. Then reboot and enjoy!
thank you I will give it a try. do I need to wipe anything before or after the flash?
Sent from my PC36100 using XDA App
chefdrew said:
thank you I will give it a try. do I need to wipe anything before or after the flash?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do the regular wipe of everything and then just flash the rom n kernel all on the same time n reboot
I just tried it and nothing has changed?
Sent from my PC36100 using XDA App
Nice thought to start this thread ! Kudos my man!
"Walk by Faith-not by Sight"
chefdrew said:
I just tried it and nothing has changed?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do u have the formatall.zip?
Not sure I know what that us, so maybe not...
Sent from my PC36100 using XDA App
chefdrew said:
Not sure I know what that us, so maybe not...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I want u to flash this zip ima link u too.
Flash the zip and then wipe everything again twice then from there flash the rom n kernel all in one recovery visit..
So
One- flash the formatall.zip
Two- wipe cache dalvik n data n sd ext two times
Three- flash rom
Four- flash kernel
On the same recovery session.
By the way what kernel u using?
Heres the formatall.zip link
http://db.tt/VKtEHjt
flash cache after format all......i don't think so...... i always boot into ROM before i do the kernel just in case, but i am paranoid haha
luckylui said:
I want u to flash this zip ima link u too.
Flash the zip and then wipe everything again twice then from there flash the rom n kernel all in one recovery visit..
So
One- flash the formatall.zip
Two- wipe cache dalvik n data n sd ext two times
Three- flash rom
Four- flash kernel
On the same recovery session.
By the way what kernel u using?
Heres the formatall.zip link
http://db.tt/VKtEHjt
Click to expand...
Click to collapse
I did a full wipe, cache/dalvik, system & boot wipe. Flashed mikfroyo then the kernal, reboot...viola!!! Everything is up & running...
Sent from my PC36100 using XDA App
chefdrew said:
I did a full wipe, cache/dalvik, system & boot wipe. Flashed mikfroyo then the kernal, reboot...viola!!! Everything is up & running...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
:-D
Good Luck buddy! Enjoy your time w the rom, its a beauty.
Installing ADB
First off I am not the originator of this guide, it can be found here and was created by nephron. I just updated it with some updated links and instructions. The newer version seemed to do a lot of the steps that were in his guide therefore I didn't need to do them to get adb to work.
Another guide I borrowed some stuff from can be found here and was created by joeykrim. If you are using a mac or linux machine go to this thread for the download links.
Again I want to give credit to those guys because they really created the original threads and I just borrowed some from both of them to create an updated install guide. This is only an install guide and if you have ADB command questions you will be better off going to those threads and asking in there or searching XDA for your answers.
Link to the Android SDK site, you might check here to see if there is an updated version of the SDK that I have link below(installer_r10)
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
7-zip - Download
Win 7 Drivers- Download-thanks shep 211
HTC Sync-The one that is in the SD card that came with your phone will work
Windows PC
USB Cable
A Rooted HTC EVO
--------------------------------------------------------------------------
Setting up the Android SDK
I installed the drivers and htc sync first, I am not sure if that matters or not.
Download the file SDK file from above and accept defaults to install it.
Once installed make sure the box is checked that says "Start SDK Manager" and hit finish.
Once SDK Manager opens click on the accept all radio button and hit install. Be patient it will take awhile.
Any problems or questions go here.
Once completed take the "android-sdk" folder and move it to the root of your hard drive (C:\).
It will be located in c:\program files(x86)\android, it's large folder so it might take a little while.
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
On the bottom half (system variables)
go to PATH and edit it to include C:\android-sdk\platform-tools
Make sure to separate it from the rest of the ones in there by a semicolon
Hit Ok
*The reason for this is so that you can run adb from any folder on your drive so that you don't have to copy your files to the tools folder. Big thanks to jadeboy and coiledwire for helping me figure this out.
--------------------------------------------------------------------------
Preparing your phone for ADB
If you are running MikFroyo it should be checked by default but you can double check it if you want.
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and it should automatically install the drivers. I've done this 4 times and every time it finds the phone just fine.
If not check out this thread here.
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands. Go here if you want to learn/test some of the basics, it's in joeykrim's thread. His push/pull of test.apk won't work because that file isn't in there. However you can just create a test.txt file on your c:\ and push/pull that to your phone. That's what I did to test that.
Easiest one to test is
Code:
adb reboot
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
Widget Text edit
Hey you might stick this in your popular solutions OP.
Link
Slow Market.
Thanks to Mitchellvii
JK you can just link to his post on this if you want since he actually found it. Here's the link
POSSIBLE SOLUTION TO SLOW MARKET:
As you use your Market, your /cache appears to fill up with .apk files call Download-1, Download-2, etc. Why Market chooses to just continually add these without deleting the older ones is beyond me. It eventually just eats up your /cache and slows Market Updates.
From what I can tell, there is absolutely no harm whatsoever in deleting these. You can delete them using Root Explorer + Multi-select or you can boot into Recovery and Wipe Cache. I am not sure if wiping /cache also clears Dalvik Cache if it is on /cache. However, if your phone takes a long time to reboot after wiping /cache then I would assume it does since your phone has to rebuild Dalvik. Either way, nothing is damaged.
I have looked at the various "cache cleaners" on the Market and have not found one that clears out these "Download-#.apk" files. If someone knows of one, please share it with the room.
The act of going into Applications and clearing MikMarket Data & Cache does NOT delete these extraneous files.
CONCLUSION:
If your Market is being unresponsive, use:
1. Root Explorer to delete all of the "Download-#.apk" files from your /cache (root), or
2. reboot into recovery and wipe cache.
After this, your Market should become much more responsive. Option #1 is easier.
I decided that I didnt like the default CircleBattery in the TPC v3 ROM, so I set out to change it to one i liked better. This would be it. I also hated that the vibrate icon on the status bar was always on. I made it go away. My phone is on vibrate in both the attached screenshots.
THIS HAS ONLY BEEN TESTED ON TPC v3
It may work on other ROMs, but FLASH AT YOUR OWN RISK.
At the very least, you should be on a deodexed ROM! Otherwise funky things WILL happen!
Removing the Vibrate icon SHOULD work on most ROMs, but i have never tried it and have no information telling me either way. The battery mod may work on most Rogers-based rom, but it will almost definitely mess with other things in ROM. I would not install recommend installing it on a different ROM.
How to install
Using flashable zips:
Code:
[LIST=1]
[*]Backup current rom, just in case
[*]Download the zip file you want to flash (attached below)
[*]Flash in CWM recovery
[*]clear dalvik cache
[*]reboot system, wait for long reboot (system is rebuilding dalvik cache, every boot afterwards will be back to normal speeds)
[/LIST]
With adb:
For the Battery Mod:
Code:
[LIST=1]
[*]Create a backup of your current Framework-res.apk
[LIST][*]either make a nandroid or "adb pull /system/framework/framework-res.apk"[/LIST]
[*]Download the attached framework-res.apk
[*]reboot your phone into recovery
[LIST][*]either in terminal enter "reboot recovery" or use "adb reboot recovery"
[*]this MAY not need to be done, but i have never tried it any other way. better safe than sorry[/LIST]
[*]on your phone in recovery, mount the system partition
[LIST][*]mounts and storage > mount /system[/LIST]
[*]on your pc, enter this command, replacing [DOWNLOAD PATH] with the path to where ever you downloaded the framework-res.apk
[LIST][*]adb push [DOWNLOAD PATH]/framework-res.apk /system/framework
[*]there is a space between the .apk and /system
[/LIST]
[*]Clear your dalvik cache and fix permissions
[LIST][*]advanced > clear dalvik cache
[*]advanced > fix permissions
[*]again, this may not need to be done, but i have never tested it without doing it[/LIST]
[*]reboot your phone
[LIST][*]this will take a long time, as your phone is rebuilding the dalvik cache.
[*]each boot after the first will be much faster[/LIST][/LIST]
For the No Vibrate icon
Code:
[LIST=1]
[*]Create a backup of your current SystemUI.apk
[LIST][*]either make a nandroid or "adb pull /system/app/SystemUI.apk"[/LIST]
[*]Download the attached SystemUI.apk
[*]reboot your phone into recovery
[LIST][*]either in terminal enter "reboot recovery" or use "adb reboot recovery"
[*]this MAY not need to be done, but i have never tried it any other way. better safe than sorry[/LIST]
[*]on your phone in recovery, mount the system partition
[LIST][*]mounts and storage > mount /system[/LIST]
[*]on your pc, enter this command, replacing [DOWNLOAD PATH] with the path to where ever you downloaded the SystemUI.apk
[LIST][*]adb push [DOWNLOAD PATH]/SystemUI.apk /system/app
[*]there is a space between the .apk and /system
[/LIST]
[*]Clear your dalvik cache and fix permissions
[LIST][*]advanced > clear dalvik cache
[*]advanced > fix permissions
[*]again, this may not need to be done, but i have never tested it without doing it[/LIST]
[*]reboot your phone
[LIST][*]this will take a long time, as your phone is rebuilding the dalvik cache.
[*]each boot after the first will be much faster[/LIST][/LIST]
These can both be done at the same time if you want to save time and use both. Steps 1, 2, and 5 should be done at the same time, and it doesnt matter which order.
Enjoy!
Great job, but a flashable zip would be so much easier.
True... Well I created flashable zips. only problem is I'm not sure if they work. I tested all of them, they all flash and my phone is still completely usable, so I dont think they are dangerous. But, since my phone already had these installed, I cant tell if they actually changed anything. If someone could test this, it would be quite awesome. Dont want to put it on the main post if it doesnt actually work.
Thanks,
I tested BatteryMod and NoVibrate.zip and it work like a charm,
Great job.
The battery was not exactly my taste then I changed it for this
Thanks for testing it! I'll put the zips on the main post now. What rom were you using? If this works on other roms, I'd like to let people know. That is a cool icon. I personally think any circle mod clashes with the touchwiz theme, which I actually like.
Thanks dude! this was my only gripe with TPCv3! I'll try the zip in the morning. Thanks!
Hey man how did you get the battery percentage to be off-centered like that within the battery icon? And did you use UOT?
Sent from my SAMSUNG-SGH-I727 using XDA App
I use TPCv3
and yes I used UOC to build the new battery.
plwalsh88 said:
Hey man how did you get the battery percentage to be off-centered like that within the battery icon? And did you use UOT?
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
well i manually edited the framework-res.apk file. did not use any software besides 7zip. the battery icons are just pictures, so the text isnt overlayed text, its just a .jpg with a number in it. i didnt actually make the battery icons, i took them from a galaxy s2 rom from somewhere.
Pseudonym117 said:
well i manually edited the framework-res.apk file. did not use any software besides 7zip. the battery icons are just pictures, so the text isnt overlayed text, its just a .jpg with a number in it. i didnt actually make the battery icons, i took them from a galaxy s2 rom from somewhere.
Click to expand...
Click to collapse
Ohhh interesting, thank you! Since I'm not running TPC, I wouldn't want to take your framework-res, but I guess I could use the battery images you used and swap them inside my framework-res. I've been wanting to learn how to decompile/recompile those apks, so I guess this would be good practice. I'd have to read up more about where the images go and all though. But that's doable right?
Sent from my SAMSUNG-SGH-I727 using XDA App
its definitely doable! really, all you need to do is open the framework-res from here in 7zip (not extract, just open) and copy all the files that include "stat_sys_battery" from "res/drawable-hdpi" and put them inside your framework-res (same folder, opened in 7zip). then you need to copy "stat_sys_battery.xml" and "stat_sys_battery_charge.xml" from the "res/drawable" into your framework-res.
if i didnt properly explain that, let me know. you definitely should make a backup of your rom before flashing a custom framework-res, just in case you break something.
Wow awesome! That doesn't sound bad at all. I will give it a shot for sure. And will definitely backup everything. I would then just adb push it back to /system/framework as you described in your OP right? That could also be done with root explorer right?
Sent from my SAMSUNG-SGH-I727 using XDA App
i would do it like i said in my original post. you may be able to do it with root explorer, but i wouldnt personally do it, as files are constantly being read from framework-res.apk. dont think it would work, like deleting a file in windows doesnt work when you have in open in another program. i could be wrong, but i think adb at the recovery menu would be much safer.
Yeah that makes perfect sense. I'll let you know how it goes when I finally find the time to do it. Thanks for your help!
zip worked as stated. TPCv3
thanks again
zip working on stock too, only power buttons are not in order..
norbarb said:
zip working on stock too, only power buttons are not in order..
Click to expand...
Click to collapse
full stock or deodexed stock? if it isnt deodexed, i am extremely surprised that it worked. what do you mean by the power buttons being out of order?
Pseudonym117 said:
full stock or deodexed stock? if it isnt deodexed, i am extremely surprised that it worked. what do you mean by the power buttons being out of order?
Click to expand...
Click to collapse
Full stock. When you press power to turn off phone you got Sound off where Power off should be also when Flight mode should be is Sound off. When you press volume buttons you got message something about Text settings, but icons are correct so you know what is for what...
norbarb said:
Full stock. When you press power to turn off phone you got Sound off where Power off should be also when Flight mode should be is Sound off. When you press volume buttons you got message something about Text settings, but icons are correct so you know what is for what...
Click to expand...
Click to collapse
very strange... it may do less things wrong if you were to have a deodexed rom (probably would still have somewhat funky behavior, but not as much). but if youre happy with how it works, by all mean keep it how it is.
floppy__ said:
Thanks,
I tested BatteryMod and NoVibrate.zip and it work like a charm,
Great job.
The battery was not exactly my taste then I changed it for this
Click to expand...
Click to collapse
Just an FYI to you or anyone else that might not be aware (since there are no pics for the Sky ICS ROM additional downloads). This is also available as one of the extra downloads in the Sky ICS ROM thread (post #2). Its the Digital Circle Battery mod.
I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!
ned4spd8874 said:
I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!
Click to expand...
Click to collapse
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app
ajrty33 said:
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.
I am have execet same issue please help
ned4spd8874 said:
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.
Click to expand...
Click to collapse
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!
MyMymusicIsSoHard said:
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!
Click to expand...
Click to collapse
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.
Had to flash the fireware
ned4spd8874 said:
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.
Click to expand...
Click to collapse
So my Debugging mode was off so I could not use adb push command, I had to do a complete firmware flash, that got my phone to work but lost all my data on the phone. but still a happy camper.
Thank you for prompt response, all your help it's much appreciated.
I had the same problem but with an ASUS memo pad hd7. I downloaded a bootanimation.zip that was the wrong orientation, so I unzipped it, rotated all the pictures rezipped and placed it back in /system/media/. Mistake! After that the device would not boot! At least that's what I thought until a quick google search led me here, thanks for your help! My situation was a little different, i'll explain my journey below in case it helps others with similar situations.
Installed minimal ADB and Fastboot from here http://forum.xda-developers.com/showthread.php?p=42407269 . I already had the device drivers installed on my computer so I skipped that step. Luckily I had USB debugging selected, however, I had never used ADB and had not given it SU permissions on the tablet. I input the following code into adb:
adb shell
cd /system/media/
ls
This verified that the offending bootanimation.zip was in there. I then tried to remove the offending bootanimation.zip with this command
rm bootanimation.zip
It failed because system was mounted as Read Only and I could not change it because I did not have SU permissions so I hit the power button on my tablet to wake it up, blindly swiped to get through the lock screen, and typed this into ADB to request Super User permissions
su
I then blindly tapped near the middle of my screen. After a few tries I successfully hit the right spot at the right time and granted SU to ADB
Once that was done I remounted system as read write and deleted the offending file with this code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
rm bootanimation.zip
ls
After verifying that bootanimation.zip was gone, I rebooted the tablet and was greeted with success in the form of some generic Android boot animation.
Same thing with my Panasonic p11 and I have a password for SuperSU so I am stuck pls help
I would suggest flashing a backup from before the custom boot animation. Then taking more cautious steps the next time you try.
To avoid this kind of unpleasantness, whether for changing the boot animation or anything else, here's a few tips:
always root your phone
It's your phone, you should have access to everything, shouldn't you? That's like buying a new car and the dealer won't give you a key for the trunk.
always use a custom ROM
Stock ROMs are usually bloated with apps you don't need and can't uninstall. Also, stock ROMs often disable features and access either "for your own good" or to keep the interface simpler. Case in point, neither of the stock ROMs that came with my Galaxy S4 or my Atrtix HD allowed me to customize the LED notification light. Whatever defaults they picked, that's what I got. A flashing green light meant I received "something" (text or email). There are a variety of 3rd party ROMs out there ready to flash for a specific device, find one that you like.