so i followed some debug tut to install some custom lockscreen on my sprint hero and i dont want it anymore.. the codes i followed were
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
how do i get RID of the lock screen ?????
Warrior 3000 said:
so i followed some debug tut to install some custom lockscreen on my sprint hero and i dont want it anymore.. the codes i followed were
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
how do i get RID of the lock screen ?????
Click to expand...
Click to collapse
put HtcLockScreen.apk on your c:\ drive
plug your phone into your pc and:
Code:
adb remount
adb push c:\HtcLockScreen.apk /system/app
adb reboot
where do i get HtcLockScreen.apk ?
do you still have the update.zip that you downloaded to flash your rom?
if so, open it and look in system/app. it is located there.
Warrior 3000 said:
where do i get HtcLockScreen.apk ?
Click to expand...
Click to collapse
If you've downloaded any roms there will be one inside it.
Actually NVM, here you go
View attachment HtcLockScreen.apk
Warrior 3000 said:
where do i get HtcLockScreen.apk ?
Click to expand...
Click to collapse
Almost any custom rom has it, including the one you flashed. I also attached it below if you need it.
*edit* Neb beat me.. =)
Dank,
did you post in my thread? It's on page 4 atm, I needs a bump!!
ps. the bottom line in my sig will take you to it
*edit - Thanks Dank!
Related
Thanks to FollowingInsanity for editing the build.prop file to get it working corectly, and thanks to Maxisma for the Droid dump. Thanks to everyone else who pitched in on this whole thing. Really all I did was realize the exact line that needed to be changed....everyone else did the rest
Here are instructions on how I got the new maps w/ Navigation to work via adb. I'm running the official rooted 1.6 build, but this should work for anyone.
(if you don't know how you use adb, go to the here
Next, you need to uninstall the old maps.apk file and here's how I personally did it since you can't just go to "uninstall" from the Application Settings(these instructions start already in the ADB shell):
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd system
# cd app
# rm xxxxxxx (this is whatever your maps.apk is titled. sometimes is just maps.apk, but it could also be com.android.google.maps.apk or somethin like that)
# exit
Click to expand...
Click to collapse
Now you've uninstalled the google maps. You can then do these next steps outside of adb.(for instructions purposes i'm using my own Android location):
C:\android\tools> adb pull /system/build.prop C:\Android
C:\android\tools> adb pull /system/build.sapphire.prop C:\Android
The 2nd may not be may be build.trout.prop or something to that effect...build.xxxx.prop
Click to expand...
Click to collapse
Next, change those 2 file names on your PC from build.prop to build-backup.prop and build.xxxx-backup.prop(if you have one) so that you don't lose those files in case anything stupid happens in the mean time lol.
Make a 2nd copy of build.xxxx-backup.prop and rename it is build.xxxx.prop. So now you should have a build.xxxx.prop AND a build.xxxx-backup.prop
Now you'll need the build.prop file to use
build.prop
(IF you are running a sapphire build, you can also use the build.sapphire.prop file located there and skip down to "re-loading prop files")
I saved that file to the same location that I saved my original files.
open build.xxxx.prop in notepad. look for where it says:
ro.build.description=kila-user 1.6 DRC83 14721 ota-rel-keys,release-keys
ro.build.fingerprint=xxxxxxxxxx:user/ota-rel-keys,release-keys
# end build properties
Click to expand...
Click to collapse
you'll need to delete the line that says ro.build.fingerprint=xxxxxxxxxx:user/ota-rel-keys,release-keys but DO NOT delete the line that says #end build properties
replace the line you deleted with the following:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
Reloading Prop Files
next, back in your command line window do the following:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Click to expand...
Click to collapse
then restart your phone
while the phone is restarting, go back and rename your build.prop and build.xxxx.prop files to build-update.prop and build.xxxx-update.prop, then change your build-backup.prop and build.xxxx-backup.prop to build.prop and build.xxxx.prop
After it restarts you'll want to locate your maps.apk file(the new one) and go back into your command line and type:
c:\android\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
c:\android\tools> adb install c:\android\maps.apk
(install crap...if it doesn't install correctly then don't do whats below)
Click to expand...
Click to collapse
Go check your google maps, type in two locations and click "go" and on the next screen you should see a button that says "Navigate"
go back to your command line screen and type:
Sorry if this is confusing, anyone who could make it more simple, please feel free to give it a try, but this is the best I could offer so people wouldn't have to go looking though the whole think tank thread to get everything they need to get it working
IF THE INSTALL GAVE YOU AND INVALID_UPGRADE ERROR THEN TRY THIS:
(again these instructions are using my own android sdk location, replace the
c:\android\tools with YOUR sdk location
from the command line type the following:
c:\android\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
c:\android\tools> adb pull /data/system/packages.xml c:\android\
Click to expand...
Click to collapse
BACK UP THIS FILE BEFORE EDITING IT
Once that's done, open that xml file in a text editor hit ctrl+f and search for maps, the first one will probably say auth.sitemaps, ignore that, keep searching untile you get to something to the effect of com.android.google.maps.apk or something like that. when you see that, you'll want to delete everything from "<packagename=" to "</package>" for the google maps app. BE VERY CAREFUL!!!! you don't want to accidentally delete something else, thus the reason for the back up.
after you've done that, go back to your command prompt and type:
c:\android\tools> adb push c:\android\ /data/system/packages.xml
c:\android\tools> adb install c:\android\maps.apk
Click to expand...
Click to collapse
it should then install perfectly fine. thats what I had to do to get it to work for me
I love you guys! will try this when I get home from work!
it does not appear to be 100% working....yet...
as posted by dwang, http://forum.xda-developers.com/showpost.php?p=4921655&postcount=275
dwang said:
If you push the old build.prop files back, after a while, the nav option disappears.
Click to expand...
Click to collapse
which I can confirm. About midnight last night it was working okay, and this morning it was gone.
followinginsanity says he will work on it today. http://forum.xda-developers.com/showpost.php?p=4921665&postcount=278
followinginsanity said:
Confirmed... will work on it tomorrow.....
Click to expand...
Click to collapse
may not want to rush to get it working only for it to not work a few hours later...but ..like most people here...that probably won't stop many
I edited the build.prop file...and now it will only work with Sapphire builds. For CM builds, build.prop file that FollowingInsanity created
Code:
c:\android\tools> abd push c:\android\build.prop /system/
c:\android\tools> abd push c:\android\build.xxxx.prop /system/
Should be
Code:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Takenover83 said:
Code:
c:\android\tools> abd push c:\android\build.prop /system/
c:\android\tools> abd push c:\android\build.xxxx.prop /system/
Should be
Code:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Click to expand...
Click to collapse
Changed lol. thanks
where can i get the new maps apk? the old one fails to install
i get error
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
ahronzombi said:
where can i get the new maps apk? the old one fails to install
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4921092&postcount=196
That's the one I did, it also has all the needed files just grab the files from there and you should be able to use them for these instructions
ahronzombi said:
i get error
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Click to expand...
Click to collapse
When that happens you need to:
adb push <path to>/Maps.apk /system/app
adb shell
# install /system/app/Maps.apk
# exit
hey hey hey
could you or somone who got this to work try to make a video tuturiol on this so we can all clearly see how it works!!! please someone make an post it on youtube if possible thanks!!!!!!!!!
navigation doesn't work outside of the US at the moment right?
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
seaweeduk said:
navigation doesn't work outside of the US at the moment right?
Click to expand...
Click to collapse
Nope, not until the big G says so.
mianosm said:
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
Click to expand...
Click to collapse
what rom are you using?
mianosm said:
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
Click to expand...
Click to collapse
You might have to try editing your packages.xml file even though it didn't give you an install error. Also, if you push your original build.prop's back, you lose navigation after a few hours. I guess the quick solution to that would be to keep the new build.prop's, but I'm not sure what the problems that might or might not create for other apps.
I'm using CM-4.2.3.1 with the edited build.prop and the build.sapphire.prop files.
# mount -o rw,remount /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
A quick shortcut is to drop the device from this command. As you're re-mounting, the kernel knows the device name. Like this:
# mount -o rw,remount /system
Click to expand...
Click to collapse
Wow dude your the bomb, I did it a different way but it worked perfect. I just took a dount rom extracted it, deleted the maps.apk, then I took the droid dump maps app and put it into the donut rom. Then I made the changes to the build.trout.prop so that it recognized the g1 as the verizon phone, used your downloadable build.prop, of course I just deleted the original build.prop in the donut build, I resigned the donut rom, flashed it like it was brand new, and bingo everything worked perfectly. Wow good job dude. I would upload my rom but I dont want to get into any trouble.
I am using "AOSP1.6_r1.4+ADP DRD20 ROM". Maps on here is called "GoogleMaps.apk". I also do not have just a build.prop. I have a build.sapphire.prop and build.trout.prop. I modified both and replaced according to the first post. When I rebooted, GoogleMaps.apk was reinstalled, so I had to uninstall it again.
I did get the error described in post #8, but was able to get around it with the help of post #10.
But for some reason my network is completely down so I can't do nothing. Wifi and Cellular network. Hmmmm.
Edit: Replacing the files I backed up with the originals, brought my networks back.
I already update it via fastboot (I got Amon recovery 1.5.2H).
But I need to change the font DroidSan to get correct font display.
Can anybody help me to solve it?
Thanks
so you are trying to restore the original fonts? did you back them up? if not, google droidsans.ttf and droidsans-bold.ttf and download them. or get them from a nandroid somewhere... they shouldn't be hard to find.
then, in cmd/terminal go to the folder they are in and (assuming you have all your fastboot/adb paths setup) and type the following:
fastboot push droidsans.ttf system/fonts/DroidSans.ttf
fastboot push droidsans-bold.ttf system/fonts/DroidSans-Bold.ttf
If you are just playing around with new fonts i suggest you grab the old ones first so you can easily revert:
go to a safe backup location and type:
fastboot pull system/fonts/DroidSans.ttf ./
fastboot pull system/fonts/DroidSans-Bold.ttf ./
Thank but there is no command fastboot push.
I run it and fail.
Also, I could not use adb remount because no permision.
that's weird - do any adb/fastboot commands work?
adb devices
adb shell
fastboot devices
do any of them work?
are you on a win xp/7, linux or osx machine?
I am on XP but when use adb shell it is ok
but use adb remout so have no permission.
ntphuong said:
I am on XP but when use adb shell it is ok
but use adb remout so have no permission.
Click to expand...
Click to collapse
You're using the ROM from this RUU right?
AFAIK, It's not rooted yet so those commands will not work.
Just watch that thread and wait for someone to post a rooted ROM.
If you can't wait, Cursor has put together an update to his Sense ROM.
asero said:
You're using the ROM from this RUU right?
AFAIK, It's not rooted yet so those commands will not work.
Just watch that thread and wait for someone to post a rooted ROM.
If you can't wait, Cursor has put together an update to his Sense ROM.
Click to expand...
Click to collapse
Yes.
I need the rooted ROM and I don't know how to root the ROM
Previous post is wrong...
You must use:
adb push local remote
like...
adb push droidsans.ttf /system/fonts/DroidSans.ttf
adb push droidsans-bold.ttf /system/fonts/DroidSans-Bold.ttf
march83 said:
fastboot push droidsans.ttf system/fonts/DroidSans.ttf
fastboot push droidsans-bold.ttf system/fonts/DroidSans-Bold.ttf
Click to expand...
Click to collapse
5[Strogino] said:
Previous post is wrong...
adb push droidsans.ttf /system/fonts/DroidSans.ttf
adb push droidsans-bold.ttf /system/fonts/DroidSans-Bold.ttf
Click to expand...
Click to collapse
oops, thank you for correcting me, i'm a douche...
That's right but no result because not rooted ROM
ntphuong said:
That's right but no result because not rooted ROM
Click to expand...
Click to collapse
If you've recieved - "read-only", so you can remount /system
adb remount
Thank all,
I use rooted ROM of Cursor, so everything is done now.
I am on fresh 1.1 but i dont like the clear lockscreen. Is there a way i can change it??
yes try looking
just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this
Thank You thedudejdog it worked perferct
You can take the HtcLockscreen.apk out of the /system/app dir of any ROM you like to get that rom's lockscreen going.
thedudejdog said:
just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this
Click to expand...
Click to collapse
am a newly rooted hero owner. read/re-read/followed the steps to do it on this forum and am grateful to those who lent their knowledge/expertise.
want to have the original hero lockscreen and downloaded this HtcLockScreen.apk file.
i searched online to see if i could find instructions to push this but can't seem to figure it out.
i've done the following:
- copied HtcLockScreen.apk to the root of my sd card.
- opened a command prompt
- got to "C:\android-sdk-windows\tools>"
from here am i supposed to type:
- "adb shell"
- "su"
'cause i think to push this is the command, right:
- "push /sdcard/HtcLockScreen.apk /system/app/"?
help please!
thank you.
ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.
I thought I saw on here a little while back that showed you how to remove just the image from the lockscreen so all you have is the grey bar. Does anyone know where that is because I thought that that was kinda cool.
thedudejdog said:
ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.
Click to expand...
Click to collapse
thank you! it worked...
sorry guys forgive my dumpness but i downloaded theme from the topic . after i replaced the apk files through root explorer and made restart to the device after that my x10 couldnt start i reflashed root steps but i really still want to change this stupid blue colore is there any easy way to do it . i wanna use the themes that already made from devlopers it comes like normal apk files........thanks in advance
Sent from my X10i using the XDA mobile application powered by Tapatalk
see Here *10chars*
What files do you have exactly? framework-res.apk? Phonebook.apk? Phone.apk
This thread as given above is taken that you have ADB installed on your computer.
http://forum.xda-developers.com/showthread.php?t=714288
If you do not have ADB, visit this thread first.
http://forum.xda-developers.com/showthread.php?t=532719
Feel free to ask if you have more questions
xGary said:
What files do you have exactly? framework-res.apk? Phonebook.apk? Phone.apk
This thread as given above is taken that you have ADB installed on your computer.
http://forum.xda-developers.com/showthread.php?t=714288
If you do not have ADB, visit this thread first.
http://forum.xda-developers.com/showthread.php?t=532719
Feel free to ask if you have more questions
Click to expand...
Click to collapse
i have framework-res.apk? Phonebook.apk? Phone.apk
and i know about adb commands but i wonder what is the diffrences it's all about replacing apk files and i manged that with root explorer and the guide is too hard it's all about modfications of the system files but it didn't tell us how to use an exsiting theme files ....is it all about the remount command that make us have to use adb ??? thanks in advance
h.boushi1987 said:
i have framework-res.apk? Phonebook.apk? Phone.apk
and i know about adb commands but i wonder what is the diffrences it's all about replacing apk files and i manged that with root explorer and the guide is too hard it's all about modfications of the system files but it didn't tell us how to use an exsiting theme files ....is it all about the remount command that make us have to use adb ??? thanks in advance
Click to expand...
Click to collapse
Not sure if ADB is required but thats the only method I know of. A step by step guide (Might want to double check with advanced users)
1) Install ADB and set the environment variables, etc.
2) Go to the folder (Should be c:/android-sdk-windows/tools) and open adb.exe (If it flashes and auto closes, open up cmd [Start>Run>cmd] and drag the adb.exe into the cmd and press enter)
3) Put Phone In Debugging Mode Settings>Applications>Development>USB Debugging
In ADB, type these commands
*Note that the commands are case sensitive*
Pull the files you are about to replace with the following commands:
cd c:/anrdroid-sdk-windows/tools
adb pull /system/framework/framework-res.apk framework-resk.apk
adb pull /system/app/Phonebook.apk
adb pull /system/app/Phone.apk
4) Now framework-res.apk, Phonebook.apk, and Phone.apk should be in your tools folder where your adb.exe is. Put these files somewhere safe.
5) Now drag your new framework-res.apk, Phonebook.apk, and Phone.apk into the tools folder.
6) Go back to adb and type the following command:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
7) Now these commands will move your new theme files to the sdcard:
adb push framework-res.apk /sdcard/framework-res.apk
adb push Phonebook.apk /sdcard/Phonebook.apk
adb push Phone.apk /sdcard/Phone.apk
8) Now these commands will install the new theme files in the sd card from the previous step:
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
adb shell dd if=/sdcard/Phonebook.apk of=/system/app/Phonebook.apk
adb shell dd if=/sdcard/Phone.apk of=/system/app/Phone.apk
9) Now your phone will restart (If not, manually restart) and your theme should be installed.
Gary~
thanks a lot man ... you are the best i'll try that and report back but any way you still the best.....
Sent from my X10i using the XDA mobile application powered by Tapatalk
why every time i put the mount command it tells me "the device not found"
and the pull commands don't seems to work
i tried adb devices command but it seems it doesnt found my device
Mmm...maybe its sound dumb, but I'm a noob in this. How do you change the battery icon? Thx
rein_hiryu said:
Mmm...maybe its sound dumb, but I'm a noob in this. How do you change the battery icon? Thx
Click to expand...
Click to collapse
You pull the framework-res.apk file and open it with 7-zip. Inside should be some folders and there should be a folder (forgot which one) with a bunch of pngs. Replace the battery icons with desired ones.
Gary~
i want to make a theme for my stock 2.3.6 DDKT3 thru UOT kitchen
will i be able to flash it thru stock recovery or i have to have CWM?
you will have to manually replace the apks in the output zip file you get from uot kitchen
I don't think stock recovery will work
Sent from my GT-S5670 using xda premium
i had once tried replacing framework-res.apk thru root explorer but then my mobile rebooted and wudnt start
i tried reflashing stock firmware but due to some prob in my comp it wudnt work
i had to give it for repairs then
any idea how to replace the apks safely??
abizerl123 said:
i had once tried replacing framework-res.apk thru root explorer but then my mobile rebooted and wudnt start
i tried reflashing stock firmware but due to some prob in my comp it wudnt work
i had to give it for repairs then
any idea how to replace the apks safely??
Click to expand...
Click to collapse
go to recovery connect your phone to computer mount /system and with adb push command, push previous framework-res.apk in /system/framwork/ and using adb shell set permissions to 0644
yep adb best way
adb rocks :thumbup::
Sent from my GT-S5670 using xda premium
haha i dont understand adb really well
any other method?
abizerl123 said:
haha i dont understand adb really well
any other method?
Click to expand...
Click to collapse
as you don't have CWM i think it's the only way! so here is step by step instruction:
1- copy your old (And healthy) framework-res.apk and adb files(two files that i attached to this post extract zip file ) in root of your C drive.
2- open command prompt program on your windows.
3- power on your phone and connect it to PC(make sure you already installed Gfit Drivers)
4- in command prompt type this commands:
Code:
cd c:
cd /
adb shell
wait to see # in command Prompt and type this:
Code:
mount -o rw,remount -t rfs /dev/stl12 /system
exit
adb push framework-res.apk /system/framework/
adb shell
chmod 0644 /system/framework/framework-res.apk
reboot
if you have disabled USB Debuging all of this things are useless
by old framework-res.apk do u mean the modified one?
if no where shall i keep the modified one?
and do u know any similar method to enable crt off animation?
thnx a lot man
abizerl123 said:
by old framework-res.apk do u mean the modified one?
if no where shall i keep the modified one?
and do u know any similar method to enable crt off animation?
thnx a lot man
Click to expand...
Click to collapse
i mean stock framework of your rom.
if you want modified framework you can try this:
1- copy adb files(two files that i attached to this post extract zip file ) in root of your C drive.
2- open command prompt program on your windows.
3- power on your phone and connect it to PC(make sure you already installed Gfit Drivers)
4- in command prompt type this commands:
Code:
cd c:
cd /
adb shell
wait to see # in command Prompt and type this:
Code:
mount -o rw,remount -t rfs /dev/stl12 /system
chmod 0644 /system/framework/framework-res.apk
reboot
see if it works or not.
i didnt get u
where shall i place the modified framework?
and can i use rajrocks' ics theme on my stock DDKT3 rom?
abizerl123 said:
i didnt get u
where shall i place the modified framework?
and can i use rajrocks' ics theme on my stock DDKT3 rom?
Click to expand...
Click to collapse
i don't know about rajrocks' ics theme .
but if you allready installed your modified framework just do what i said in second post. and if you don't know you have installed it or not , place modified framework on root of C: Hard drive in your PC and do what i said in my first post
and what about the systemUI.apk?
When i try opening adb through cmd i get an error saying AdbWinApi.dll is missing
oh sorry i foget about that
i attached that file to this post.
about systemUI.apk just replace it like framework... just change adresses...
and always keep orginal file just in case! maybe you did something wrong and end in bootloop
yeah thnx
and u have any idea of how to enable crt off animation?
thnx man