Database Info

flashing a different lock screen

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!

Discussion/Problems/Requests for Morphs.

This is a thread where you can post questions, concerns, requests, problems or general discussion for the morphs for the Nexus One that are contained in the Morphs for the Nexus One thread.
This thread will serve more of a purpose once more morphs are posted in that thread, and there morphs don't have a "home" thread.
When the need arises, I will place how-to's in here.
How to make .xml file for MetaMorph
http://bit.ly/dnFtwF

[REQUEST] Morph that enables 7 screens?
Basically what helixlauncher2 does. I love the 7 screens and the 180 screen rotation but the lag to me was way too much. Is there just a plain morph for this. I dont want a theme or anything. searched and no luck

Why not just replace Launcher2 with its modded version (aka HelixLauncher2) ?

britoso said:
Why not just replace Launcher2 with its modded version (aka HelixLauncher2) ?
Click to expand...
Click to collapse
how do i do that. forgive me, these things have to be broken down in tard terms so i understand. I am rooted with cyanogen 5.0.5.3 if that helps.

Buck Shot said:
how do i do that. forgive me, these things have to be broken down in tard terms so i understand. I am rooted with cyanogen 5.0.5.3 if that helps.
Click to expand...
Click to collapse
Its posted on the Helix2 thread.
http://forum.xda-developers.com/showpost.php?p=5776045&postcount=1
1) Download v0.6 SYSTEM APP: Here -> 565KB
2) rename to Launcher2.apk
3) run the following adb commands: (dont run the lines with #, those are comments)
Code:
#clear up the old stock Launcher2 data, because it may cause problems with the mod, you WILL lose all icons and widgets from your screens.
adb shell rm -r /data/data/com.android.launcher2
#backup old
adb shell cp /system/app/Launcher2.apk /system/app/Launcher2.apk.stock
#copy new
adb push Launcher2.apk /system/app/Launcher2.apk

Problem he had was Telia was way too slow. He's looking for a way to add 7 screens to the native launcher.

You can get Helix Launcher in the Market that will enable 7 screens!
I ment the home replacement version.

kitsunisan said:
Problem he had was Telia was way too slow. He's looking for a way to add 7 screens to the native launcher.
Click to expand...
Click to collapse
Exactly what I'm looking for

djdarkknight96 said:
You can get Helix Launcher in the Market that will enable 7 screens!
I ment the home replacement version.
Click to expand...
Click to collapse
The current Helix launcher(Nexus one version) is very laggy. Native launcher is very smooth, no lag or stutter to it, no force closes. I get force closes several times a day with Helix. He wants some way to get 7 screens on the native launcher.

Maybe a dumb question....
Can I use Terminal Emulator (the one in the newest cyan mod) to push things like .apk's?
I need a way around not having sdk here at work. I can d/l the .zip's no problem, bit what can I do from there?
I've managed to get cyan, kernels, radios and morph mods etc - so I'm not THAT dumb, but I've searched all over these forums and I can't seem to find a straight forward answer to this. Also, is there like a terminal emulator guide I can read somewhere? I'm assuming it's just like the adb stuff just slightly different?
I'm pretty new to this stuff so any help would be great. THX

Green Selection
Would it be possible to have the green selection like on the hero roms and keep the notification bar the stock color?

Delaneyd said:
Can I use Terminal Emulator (the one in the newest cyan mod) to push things like .apk's?
I need a way around not having sdk here at work. I can d/l the .zip's no problem, bit what can I do from there?
I've managed to get cyan, kernels, radios and morph mods etc - so I'm not THAT dumb, but I've searched all over these forums and I can't seem to find a straight forward answer to this. Also, is there like a terminal emulator guide I can read somewhere? I'm assuming it's just like the adb stuff just slightly different?
I'm pretty new to this stuff so any help would be great. THX
Click to expand...
Click to collapse
you can use root explorer to install .apk to /system/ or even replace files on the /system/ that need root

Yes terminal commands are fairly equal to adb commands. Here is a simple run down.
adb shell is the same thing as entering a command into the terminal.
adb shell reboot
to
reboot
adb shell followed by a series of commands
adb shell
xxxxx xxxxxxxx xxxx
yy yyy yyyyyyyy yy
zzzzz zzzz zzzzzz
to
xxxxx xxxxxxxx xxxx
yy yyy yyyyyyyy yy
zzzzz zzzz zzzzzz
adb push would be like so
adb push Mms.apk /system/app/Mms.apk
to
cp location-of-file/Mms.apk /system/app/Mms.apk
adb pull would be like so
adb pull /system/app/Mms.apk desktop
to
cp /system/app/Mms.apk location-to-put-file
finally
adb remount
to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /systems
Those are basic adb commands to terminal commands. Sorry for the crappy layout of my post. I may fix it later but all the info is there.
Also, I am going to request a mod to move the posts to the general discussion thread as per the first post.

jluna1 said:
Would it be possible to have the green selection like on the hero roms and keep the notification bar the stock color?
Click to expand...
Click to collapse
I can work on one later on, but yes it is easily possible.

deleted. (was a request to clean up teh Morph release topic)

just letting you know,
Im actually in the works of a theme with green selection effects and a stock status bar, among other things, as in more white acccents including white lockscreen tabs. (david already knows) thanks again!
Just letting you know, however i dont have a nexus which makes it extremely hard to test my theme out

try using the 0.5 version, its faster than 0.6
the 0.7beta standalone pushed to /system/apps/ is definitly faster than 0.6 as well, never have had FC issues from helixlauncher2 personally, but i only use it as /system/app/ and not standalone

[REQUEST] clear status bar
I can't seem to find any threads about it...
I would like a clear status bar for Modacos Alpha 19 Desire Rom Any ideas??

jluna1 said:
Would it be possible to have the green selection like on the hero roms and keep the notification bar the stock color?
Click to expand...
Click to collapse
Where all do you want the green selection? Do you want every green image from framework-res.apk or just the buttons, hightlights/selected/pressed buttons?

http://forum.xda-developers.com/showthread.php?t=625881
about 3 pages back. But i dont see modaco on it
i use glass staus bar. modaco friendly. better notifications IMO.
http://forum.xda-developers.com/showthread.php?t=638659

[WIP-Tutorial] Installing AOSP apps in your favorite ROM

Myself and apparently many others like the AOSP apps better than the sense apps. I find the interface for the AOSP messaging, calendar, browser, calculator, and dialer/contacts applications to be more attractive and in some cases more usable. I really liked Bugless Beast 0.4 since it featured these applications, but I have had a hard time with the bug that keeps disk drive from working, and there are various reports of some syncing and battery issues. The EVO-NonSense series has been great too, but I use HDMI out sometimes and like having some of the sense stuff installed. Big thanks to both BuglessPete and tjohnsonjr for their AOSP work.
(7/18/2010) I have attached some of the files I have been using, see descriptions at the bottom of the post.
So since it took a little digging for me to figure out how to do this (even though to advanced users this is easy) I thought it might come in handy for other new users. Additionally I'm hoping by posting this someone can help me figure out how to get the dialer/contacts stuff working, I have the others working fine.
I've done the below on DamageControl, and I think another (baked snack maybe, can't remember). I'll probably throw together an update.zip that can patch these in place later, but I'd rather get the dialer/contacts part figure out first.
Setup:
1. You will need a fully rooted (toast root part 2, NAND unlocked) phone, and adb up and running. There are several explanations for both parts, but the ones listed in the "useful threads" sticky are joeykrim's for adb and toast's part 1 and part 2 for root.
2. I have been using the apk's from BuglessPete's bugless beast 0.4 ROM. The thread for it is available here.
Once you unzip the file, you will find the needed apks in the /system/app folder.
Note: Please donate to pete, he doesn't even have an EVO yet and is doing some great work. Hopefully if he has a phone to work on he can get some of these small bugs squashed and keep the development for BB going.
3. Backup your phone. If you don't know how to reboot into recovery and restore from a nandroid backup, you do not want to do this yet, especially if you want to try help me figure out how to get the dialer running. The idea with the dialer is to try different things until something works. In all likelihood you will hit a point where things are FCing so much you can't do anything. You will almost certainly need to restore from a Nandroid backup at some point.
Important: More than likely anything I list here can't break a phone in a way that a nandroid restore won't fix, but I can not and will not be accountable for any problems with your phone.
Which files:
One nice thing about adding files this way is you can pick and choose what to use. If you like the stock messaging but want the AOSP calendar, you can do just that.
Calculator: Calculator.apk
Calendar: CalendarProvider.apk and Calendar.apk
Default "Navigator" application: CarDock.apk <- you can keep both
Internet: Browser.apk and HTMLViewer.apk <- doesn't show previews of each tab, but allows up to 8 instead of 4. There may be other functionality gained or lost, I dunno.
Clock: DeskClock.apk (can exist beside HTC clock, and can be installed without this procedure)
Messaging (SMS, Text): Mms.apk <- Many people have trouble with this one.
####### Not Working! See post #2 ########
# Phone: Phone.apk, ContactsProvider.apk, Contacts.apk
###################################
To install:
I think you can use adb to do this install with the files still on the computer, but I go ahead and throw all the needed apks onto my sdcard, typically in a folder. Also, if you need to be in the Android SDK's /tools directory to use adb (this depends on your configuration) do that. Connect your phone, and make sure it is in "Charge Only" so the sdcard stays mounted. To make sure adb sees the phone properly issue:
Code:
adb devices
and you should get a return listing the device ID. If so we will mount the /system partition as read-write:
Code:
adb remount
Log into the phones local shell:
Code:
adb shell
you are now on the phones command line and file system, not on your local machine. Now we can start installing files. I'll use Calculator in this example, and I have the apk in a folder on the sdcard called AOSP_apks:
Code:
install /sdcard/AOSP_apks/Calculator.apk /system/app
You can do a couple at a time, and you must do more than one at a time when installing a provider like CalendarProvider.apk and Calendar.apk.
Once you are done, exit the phone's shell, and reboot the phone:
Code:
exit
adb reboot
The change may show up immediately, but the phone and applications aren't designed to change these core functions on the fly, so make sure to reboot the phone. Once it reboots you will probably notice the AOSP icon has replaced the former, and you have the AOSP skin and/or functionality.
Post #2 will deal with progress so far on the dialer/contacts.
(added 7/17) Notes on different apks: The BB Launcher2.apk has his skin on the google search widget, or grab the apk from something else like DC for stock. Launcher.apk from BB is the one with the wide drawer and (I think) 9 screens.
Music.apk from DC is the modded music app from Cyanogen. It has some very nice UI tweaks.
Attached:
- Music.apk used in Cyanogenmod from DC
- Calendar, CalendarProvider, Browser and HTMLViewer from BB 0.4
- CarDock, Calculator, and MMS from AOSP EVO-NonSense

Contacts/Dialer Progress: I'm sure some of the more advanced developers know the answer to this, so ideally someone can fill me in. In the meantime I'll report my findings here, and if others can add feedback to the thread on what they have done, I'll update this post. Hopefully in the long run there will be a straightforward explanation for this I can add to the above post.
I have installed the three files listed above (ContactsProvider.apk, Contacts.apk, and Phone.apk) which seems to install the right bits, but I get FCs.
Later on I added Telephony.apk and FutureDialService.apk, which didn't improve anything. Finally I noticed that Bugless Beast didn't have HTCDialer.apk, so I removed that as well. I think this was the point things went from the dialer and contacts applications FCing to non-stop FCs that kept me from doing anything on the phone.
Attached are the three apps I'm sure are involved for the Contacts/Dialer, pulled from tjohnsonjr's AOSP EVO. More files may be needed, but I'm still trying to figure out which.

The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.

I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.

I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.

RikusHaven said:
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
Click to expand...
Click to collapse
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
warmachine69 said:
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
Click to expand...
Click to collapse
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
MikeBrWade said:
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
Click to expand...
Click to collapse
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?

laydros said:
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
Click to expand...
Click to collapse
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.

84th hour of a battery duration test? details please?

MikeBrWade said:
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
Click to expand...
Click to collapse
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?

davebu said:
84th hour of a battery duration test? details please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7154719&postcount=993
This is my post talking about it.. I am on hour ~91 of the test.. still running with 8% battery left... BBv3 rocks!

laydros said:
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
Click to expand...
Click to collapse
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.

MikeBrWade said:
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
Click to expand...
Click to collapse
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?

If you have the AOSP apps available, could you please post them all in .zip folder in the OP?

MikeBrWade said:
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
Click to expand...
Click to collapse
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't run at all . Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.

MikeBrWade said:
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't. Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
Click to expand...
Click to collapse
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back

I[E said:
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
Click to expand...
Click to collapse
Interesting that you say that, since I had some MMS texts in my cache. Wondering if when the AOSP version couldn't deal with them so it just FC'ed instead.
So I tried that, deleting ALL my texts so it wouldn't have some MMS collision or something. But that didn't work either, HTC Mms.apk works fine.. the AOSP.apk FC's. Could the OP or something with a working AOSP Mms.apk post it maybe it's my copy. Mine has an MD5 of : 441e3b8863bc3ab88ce6ad9bc1671f22

I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App

I going to upload all the AOSP apks that I include in my ROMs when I get home tonight.

Can you tell us how you got contacts.apk to work? I'm trying with FreshRom and I pulled the Contacts.apk from your Rom and it won't recognize the file when I push it using adbshell. The file is in the app folder but android ignores it.

I[E said:
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Does does your md5 match mine?

[Temp] Fix for missing apps on froyo

in your build.prop replace the current text with this: you can get things like tv.com back
Code:
ro.build.description=passion-user 2.2.1 FRG83 60505 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
i would upload one for people to flash but as some many people are on diff roms/kernels it would just cause more issues then its worth best way to go about fixing it is pulling the file from your phone (or the zip from teh rom your on). swapping out the text and pushing it back to /system
all credit goes to Decad3nce for the fix

Didn't s work for me...
Sent from my SPH-D700 using XDA App

you may have to reboot

Worked for me! Thanks.
Sent from Froyo!

Thanks worked great!!

shabbypenguin said:
in your build.prop replace the current text with this:
Click to expand...
Click to collapse
Wouldn't you like to be more specific? Your current instructions technically mean to replace the entire file with just those three lines...
Sent from my SPH-D700 using XDA App

Please note that users of Quantum Rom already have this fix applied, since 1.3
(Used the epic 2.1 key in 1.3, 1.4+ use the nexus one key)
Thanks shabby xD
Sent from my SPH-D700 using Tapatalk

Here's what I did from my PC with adb. (I have adb in my PATH so adjust the commands for wherever you might have adb.exe)
adb pull /system/build.prop
Then I edited the 2 lines on my PC with notepad++ and saved. Then I put it on my sdcard, remounted /system readwrite and copied it over to /system/build.prop and then rebooted.
adb push build.prop /sdcard/build.prop
adb shell
su (if your ROM didn't already drop you in to root, and check your phone for the superuser popup)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cat /sdcard/build.prop > /system/build.prop
reboot
Sent from Froyo!

didnt work for me. I been trying to get the PayPal 2.2 to show up on the market but its a no go.
Im using Froyo also.
anyway we could just get the paypal.apk??

This didn't work for me either. Trying to get Pocket Blu installed, but it isn't working. TV.com isn't showing either. FWIW I have the new Market app if that means anything.
Any ideas?

Milkman00 said:
This didn't work for me either. Trying to get Pocket Blu installed, but it isn't working. TV.com isn't showing either. FWIW I have the new Market app if that means anything.
Any ideas?
Click to expand...
Click to collapse
Did you reboot your phone?

yes, and after rebooting a rechecked my build.prop file to make sure it took, and it was correct

Nevermind, I got it to work...
The end of the second line was missing the s. Put the s in, and it works perfect.

Can I get some clarification on this? I am using Mammon 1.0.3.1 and cannot get my sprint football ap to work.
Would this be an example of what this would fix?

Could the MSID number in my phone being different from my phone number be the reason it doesn't think this is a SPrint phone?

Thanks for posting a fix but it also didn't seem to work for me. I have been trying to load a program called Laser Appraiser from maket with no avail. Can anyone find it in their market?

worldlyinquirer said:
Thanks for posting a fix but it also didn't seem to work for me. I have been trying to load a program called Laser Appraiser from maket with no avail. Can anyone find it in their market?
Click to expand...
Click to collapse
Laser Appraiser shows up for me.

Milkman00 said:
Laser Appraiser shows up for me.
Click to expand...
Click to collapse
Thanks, Hmm I think I'll just wait for the latest froyo release and see if that helps

I tried downloading it and saving it to my SD card, but it's a protected app. I use AppMonster, which backs up all the apps for when I do flashing, but it doesn't do protected ones. Sorry man, I tried.

sorry i havent replied, most of the roms out there SHOULD have this baked in... i know acs and quantum do and the cm rom should but ill ask noob just to be sure.

[q] heeeeelllllpppp meeeeeeee pleaaasseeeeeeeee!!!!!!!

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.