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.
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!
I know you had to push a reboot file to get it working on some Hero ROMs. What about the EVO version?
The Hero way works.
FIRST, install Quickboot from the market. Run it and enable it in the superuser permissions screen.
Download the reboot.txt file I attached and rename it to "reboot" (take off the ".txt"). Move it to where ever your "android-sdk-windows/tools" folder is.
Connect your phone to your computer (make sure it is "charge only") and boot into recovery...
Code:
adb shell
reboot recovery
Start your "Windows-recovery.bat" (if using windows) and let it do it's thing in the CMD prompt. Keep that prompt open.
In a CMD prompt OTHER THAN the one opened by recovery.bat type...
Code:
adb shell
mount /dev/block/mtdblock4 /system
exit
This will keep your system mounted but get you out of shell. Now type...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
Once you're back up, run Quickboot and choose either reboot or recovery (both will now work). It takes about 5 seconds to start rebooting but it does work.
What does this do? does it make recovery stick?
watzone69 said:
The Hero way works.
Download the reboot.txt file I attached and rename it to "reboot".
Once you're in recovery...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
EDIT: It takes about 5 seconds to start rebooting but it does work.
Click to expand...
Click to collapse
Woo! Thanks!
Edit: Didn't seem to work for me. Damn.
joeavery2 said:
What does this do? does it make recovery stick?
Click to expand...
Click to collapse
No, this just lets you use the QuickBoot app from the Market to reboot your phone.
TheBiles said:
Didn't seem to work for me. Damn.
Click to expand...
Click to collapse
Code:
adb shell
cd /system/bin/
ls
See if the reboot file actually got pushed to the directory. If so, try this:
Code:
chmod 755 /system/bin/reboot
The only other thing I can think of is that I installed Quickboot BEFORE doing all of this. Did you get the SU permission screen when you tried to run it?
Any luck??
Did I mention that the Quickboot "recovery" button works also? Much easier than opening a shell and typing it in.
Of course you still have to run the recovery.bat to get the custom recovery but at least it's one less step.
Still no dice. I also already had QuickBoot installed and granted it root permission prior to pushing the reboot file.
any update to this?
thanks
joey3002 said:
any update to this?
thanks
Click to expand...
Click to collapse
It doesn't work for you?
I updated my earlier post to give more instructions for getting into recovery and pushing the "reboot" file. I hope it helps!
I have a ROM ready to go that changes a couple icons and quickboot works with no probelm. Wifi tether is the only thing I don't have working. I can post it if you would like. I also removed sprint apps and some widgets
I made an update zip that got Quickboot working for me. This is using watzone69's reboot file.
Run from Toast's recovery. http://forum.xda-developers.com/showthread.php?t=690762
watzone69 said:
It doesn't work for you?
Click to expand...
Click to collapse
yes i got it working last night by reading this thread from top to bottom.. then repeated.. thanks
I have a problem with white notification bar, I put the black and then I came back to white and now I have white bar but white text. Any solutions? I pulled white framework-res.apk and services. Jar both picked from a stock deodexed
frf50
if you have spare parts on your phone change those colors with that, newest CM has spare parts in the settings menu, complete with import and export of an xml with color settings
Look up-right, white bar and white font and time http://i782.photobucket.com/albums/yy101/mrnameless151/2e48aaef.png
I have froyo not cyanogen mod
spare parts is the only way i know how to modify that without modifying the services.jar itself
Push the original framework-res.apk and the services.jar to your /system/framework folder.
Originale black or white?
MrNameless said:
Originale black or white?
Click to expand...
Click to collapse
Original services.jar for black text.
adb remount
adb push services.jar /system/framework/
adb reboot
djmcnz said:
Original services.jar for black text.
adb remount
adb push services.jar /system/framework/
adb reboot
Click to expand...
Click to collapse
it doesn't work, and i pushed this http://www.myhangoutonline.com/inde...allfib_top/leonnib4/blackonwhite-services.jar
MrNameless said:
it doesn't work, and i pushed this http://www.myhangoutonline.com/inde...allfib_top/leonnib4/blackonwhite-services.jar
Click to expand...
Click to collapse
It doesn't work means what? Did you get an error?
If not, then it did work, you just must be pushing the wrong file.
it works, but the font was not changed
MrNameless said:
it works, but the font was not changed
Click to expand...
Click to collapse
The fonts are all in /system/fonts/
sorry, i didn't want to say font but time and writes
http://i782.photobucket.com/albums/yy101/mrnameless151/2e48aaef.png
it is always the same
Okay, try extracting the one in the attachment..
And use these commands (case sensitive):
adb remount
adb shell rm /system/framework/services.jar
adb push services.jar /system/framework/services.jar
adb shell ls -l -a /system/framework/
Make sure a services.jar - all lower case - is listed and only one is listed.
adb reboot
If you want to make sure it is the correct one, then use adb to pull it back off your phone and compare it to the source file attached here.
there are 2 .
service.jar
services.jar
No, its not.
Thats the result of your work.
You've pushed it as service.jar.
Now its clear, why your fontcolour doesn't change^^
MrNameless said:
there are 2 .
service.jar
services.jar
Click to expand...
Click to collapse
Simply add the following command to the series above, above the other "rm" command and below the "remount" command.
adb shell rm /system/framework/service.jar
and remember to push services.jar this time...
thanks to both!!!1
THanks to TEAMWIN!!!!!!!!!!!!!!
UPDATE to UPDATE- advanced users only that can understand my instructions please. I tried to make it newb friendly but this takes alot more time than I ever imagined ... (PROPS to ALL DEVS and POSTERS taking the time to share with us that which they spent hours testing!!!!)
so,
also download build.prop
place it in /data/bin
chown to root.root
chmod to 644
you only have to do this once, of course
Now reboot and run (updated and attached here at same time as the build.prop; so if you don't have the build.prop, you need to redownload daddy'stemproot.bat s it has been updated) daddy'stemproot.bat from wherever you downloaded it to.
http://dl.dropbox.com/u/7393616/build.prop
good luck!
UPDATE:
Just wanted to upload what I have been using since the original instructions are out of date.
have tested the following Windows script for 2 days without rebooting and retain full functionality on all root apps.
Instructions:
instead of doing copy/paste, once you have put fre3vo,su,busybox,and sqlite3 into /data/bin and set permisions/ownership, as per original instructions below,
if you have been using another script, just move everything to /data/bin and set permissions/ownership as per below;
and after every reboot, (or after doing the set-up for the first time users)
simply run this script:
(personally, after plugging my phone into my PC, and opening a command prompt, I always do "adb reboot"
then wait until the soft keys at bottom of screen light up (this means the phone is finishing all start up processes but for all extents and purposes the phone has booted) and then double click the file below. the command prompt will open and close itself, when closed, you are good to go until reboot)
Download and save this .bat to anywhere you want and run from anywhere you wish(mine is on my desktop for easy access):
LATEST VERSION Directly below:
http://dl.dropbox.com/u/7393616/daddy%27stemproot.bat
ORIGINAL Instructions:
Just wanted to give back so I will share how I have been getting functional su for on phone term apk and visible /data on root explorer and Superuser prompts for every root app (just because you allow at the prompt and Superuser allows an apk, doesn't mean it will alwasy work; if you open SetCpu more then once a boot it stops working. Bloatware Remover, though given root priveledges, doesn't work, I think becasue when trying to mount system, the apk uses the wrong partition in its script. etc.)
anyways
first get fre3vo, then the latest versions of su, busybox, sqlite3.
via shell from PC:
cd (directory where your 4 files are located)
push above files to /data/local/tmp (follow instructions in other threads)
get temp root via fre3vo
now with temp root do :
adb remount
adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
adb shell mkdir /data/bin
adb shell chown root.shell /data/bin
adb shell chmod 755 /data/bin
adb push (all 4 files, one at a time, to /data/bin)
adb shell chown root.shell /data/bin/su
adb shell chown root.shell /data/bin/busybox
adb shell chown root.shell /data/bin/sqlite3
adb shell chmod 6555 /data/bin/su
adb shell chmod 4555 /data/bin/busybox
adb shell chmod 755 /data/bin/sqlite3
adb shell chmod 755 /data/bin/fre3vo
now, set up is done, you don't have to do any of that again (unless you mesed up of course)
copy and paste the following lines into shell on PC and viola!
adb shell /data/bin/fre3vo
adb wait-for-device
adb remount
adb shell mount -o remount,suid /dev/block/mmcblk0p23 /data
adb shell ln -s /data/bin/su /system/xbin/su
adb shell ln -s /system/xbin/su /system/bin/su
adb shell ln -s /data/bin/busybox /system/xbin/busybox
adb shell ln -s /data/bin/sqlite /system/xbin/sqlite
adb shell mkdir /system/xbin/bb
adb shell /data/bin/busybox install /system/xbin/busybox /system/xbin/bb/
adb shell sync
So, everytime you reboot,
open a shell on your PC and copy and paste, and then you are free to live with root, until you reboot, and of course with limitations; but I personally can live with this until Fre3dom is complete.
Take your time boys(TEAMWIN) we love you!!!!
hope this helps somebody. I don't have much bandwith to check back to answer questions, but I am confident if any arise, that the community will step up as always. enjoy your root apps
Can somebody please explain to me what he means by latest version of su, busybox, and sqlite3? Apk or like files if anybody would be kind enough to post a zip file of all three?
xSunny said:
Can somebody please explain to me what he means by latest version of su, busybox, and sqlite3? Apk or like files if anybody would be kind enough to post a zip file of all three?
Click to expand...
Click to collapse
You can pull them files out of any rooted android phone.......
Why doesnt the OP just create a script and have it run with one click from the phone??
Thanks..
Sent from my HTC Sensation Z710e using XDA App
Mikey1022 said:
You can pull them files out of any rooted android phone.......
Why doesnt the OP just create a script and have it run with one click from the phone??
Click to expand...
Click to collapse
Commands to pull please?
xSunny said:
Commands to pull please?
Click to expand...
Click to collapse
Try the "Search" command here, if that fails hit Alt+f4.
KillaHurtz said:
Try the "Search" command here, if that fails hit Alt+f4.
Click to expand...
Click to collapse
How about you stop being a prick and answer the question if u dont want to answer then stop running your mouth like a little 2 years begging your mommie for ice cream.. Thank you.. Maybe you should hold the Alt+F4 button =] And dont come attacking me again please..
xSunny said:
How about you stop being a prick and answer the question if u dont want to answer then stop running your mouth like a little 2 years begging your mommie for ice cream.. Thank you.. Maybe you should hold the Alt+F4 button =] And dont come attacking me again please..
Click to expand...
Click to collapse
Wow your general lack of knowledge despite having a long list of devices is disturbing and sad. I guess referring you to the best, and most timely manner to find an answer is an attack ? LOL
xSunny said:
Commands to pull please?
Click to expand...
Click to collapse
adb pull /sdcard/yourfile /whereveryouwantit
or setup an FTP server on your phone (https://market.android.com/details?id=org.swiftp) and download what you're looking for through that.
xSunny said:
How about you stop being a prick and answer the question if u dont want to answer then stop running your mouth like a little 2 years begging your mommie for ice cream.. Thank you.. Maybe you should hold the Alt+F4 button =] And dont come attacking me again please..
Click to expand...
Click to collapse
KillaHurtz said:
Wow your general lack of knowledge despite having a long list of devices is disturbing and sad. I guess referring you to the best, and most timely manner to find an answer is an attack ? LOL
Click to expand...
Click to collapse
What is it with this forum??!??!?! I used to have a HD2 and the forum there was awesome! So many helpful and friendly people creating a productive and welcoming community! But here in the Sensation forum every second thread is full of people *****ing at each other and behaving like children! What the hell is wrong with you guys???
KillaHurtz said:
Wow your general lack of knowledge despite having a long list of devices is disturbing and sad. I guess referring you to the best, and most timely manner to find an answer is an attack ? LOL
Click to expand...
Click to collapse
Lmao.. Thats all im going to say to end this conversation anyways thanks for posting the commands to pull via adb
How do you push more than one file at a time?
adb push (all 4 files, one at a time, to /data/bin)
Click to expand...
Click to collapse
Thanks
Thanks Daddyroot ! the commands have really worked for me. Now I have a sensation with Temp root till I restart. All other scripts in the forum was not helping me.
Best solution I found so far. Not losing root till reboot anymore.
A++ would install again
Really glad to be able to give back to the community.
I wish I had more time when I posted this to check back and reply but I'm a single parent and time is short. After playing for a couple hours and finally seeing and being able to edit the /data folder, I knew it would be with it to make the time if I could help just one person to not waste the time figuring out what I could share. Nothing quite like the feeling you get on an unrooted phone when you first see the superuser prompt to allow or deny!!!
Thank you all who hit the thanks button!
And God bless TEAMWIN and (insert your favorite dev here)!!!
I will try to check back at least once a day...
Wisefire said:
How do you push more than one file at a time?
Click to expand...
Click to collapse
You don't... that's why he said "ONE, at a time"...