Database Info

HTC Navigation.apk

anyone have this please id like to have it ...... and how do i remove the other nav please ( like to save it incase i dont like the HTC NAV )

I don't have the .apk for HTC Navigation, but when/if you do get it, just to to system/app and rename your current nav application (i.e. navigation.apk.old) if you don't want it to show up in your app list, but don't want to uninstall.

http://forum.xda-developers.com/showthread.php?t=700448 At the bottom of post #1 Flip was nice enough to zip all the apks into one zip file. Hope that helps.

Stunna4life888 said:
http://forum.xda-developers.com/showthread.php?t=700448 At the bottom of post #1 Flip was nice enough to zip all the apks into one zip file. Hope that helps.
Click to expand...
Click to collapse
yea i pulled that from the SDcard but it wont install i might have to push it

Sporkman said:
yea i pulled that from the SDcard but it wont install i might have to push it
Click to expand...
Click to collapse
Thats what I had to do, know how do that?

Stunna4life888 said:
Thats what I had to do, know how do that?
Click to expand...
Click to collapse
hmm, could you kindly explain what "pushing" is, and how to do it?

my android pushing and pulling files.
for those of you new to android and adb.

ok here is the real answer
pulled directly from android developer tools.
----------------------------------------------------------------------
Copying Files to or from an Emulator/Device Instance
You can use the adb commands pull and push to copy files to and from an emulator/device instance's data file. Unlike the install command, which only copies an .apk file to a specific location, the pull and push commands let you copy arbitrary directories and files to any location in an emulator/device instance.
To copy a file or directory (recursively) from the emulator or device, use
adb pull <remote> <local>To copy a file or directory (recursively) to the emulator or device, use
adb push <local> <remote>In the commands, <local> and <remote> refer to the paths to the target files/directory on your development machine (local) and on the emulator/device instance (remote).
Here's an example:
adb push foo.txt /sdcard/foo.txt

How to push the file via your sd card
So for an example on pushing a file from a computer to phone make sure you are in recovery mode. And assuming you have the apk somewhere on your sd card. Open command prompt and navigate to your sdk-tools to use adb. THIS EXAMPLE IS STRAIGHT FROM FRESH THATS WHY I SAYS ..../FRESH-REMOVED-APKS/. That is just the location on your sd card so this is where you need to type where the file is. WHATEVERAPP.apk thats what the apk name is. Make sure that it is the same spelling and spacing/no spacing as well. notice the space after .apk as well. Now you are ready simply type the following commands (enter at the end of each line.) Last line is simply where your file is on your sdcard then the file name as it appears in the file on your sd card. Hope this helps!
adb shell mount /sdcard
adb shell mount /system
adb shell
cp /sdcard/fresh-removed-apks/WHATEVERAPP.apk /system/app

[Q] How to install 3338 for newbies?

I am sorry I am such a newbie, but I couldn't find the answer by searching.
Thanks in advance for anyone's help!

trevoc said:
I am sorry I am such a newbie, but I couldn't find the answer by searching.
Thanks in advance for anyone's help!
Click to expand...
Click to collapse
If you are running clockwork. Download it and put on internal sdcard under roms. Load it like you would a zip of any other rom.
If you are still on stock rom. Follow the directions under TNT thread to load using stock rom.

Thanks. I am using stock so my assessment is that all I need to do is copy and rename zip file to root on sdcard, call it update.zip, then use the command file from any other rom rar and create the appropriate directory (ie recovery) to put it in, then flash?
Sent from my DROIDX using XDA App

Yes, that is pretty much it.
1) Create a directory on your computer called viewsonic
2) Create a directory under that called recovery
3) Create a text file under the recovery directory called command (no file suffix, just command), then put this in that file and save: --update_package=SDCARD:/update.zip
4) Download the smb 3338 zip file from viewsonic, rename it to update.zip and put it in the viewsonic directory (at this point you have an update.zip file, a recovery folder with the command file in it)
5) Hook up your tablet to your computer via usb and when it mounts, it will give the contents of the /sdcard area on the tablet
6) Go to your viewsonic directory on your computer, copy all contents (zip file, recovery directory), then paste into the tablet's /sdcard area
7) Verify the contents on your tablet under the /sdcard area, you should have the update.zip, the recovery folder, and under that the command file that has one line in it
8) Turn off the tablet, press the Vol+ button, then press the power and hold both down until you see the viewsonic splash screen and it says in the corner that recovery was detected
Hope this helps, this is how I did it based on the directions provided by others.

Thanks TeamSpeed and dragonstalker for this great information. I hope it helps other newbs--it sure helped me!
It worked:
FYI: the command file filename must be "command" not "command.txt"

trevoc said:
Thanks TeamSpeed and dragonstalker for this great information. I hope it helps other newbs--it sure helped me!
It worked:
FYI: the command file filename must be "command" not "command.txt"
Click to expand...
Click to collapse
Correct, I tried to make that a bit clearer by italicizing the file name with no suffix (I will update above though too).

ADB issues

Okay, so i trying to push a file to my SGS4G... I thought i got it to work but when i went to find the file it was just some random file with no extension.
e.g. I typed (adb push FFFFFF.FFF /sdcard/download) it says the file was copied but when i go to my phone ffffff.fff is not there, instead a file called /sdcard/download
I followed these instructions....
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
What am i missing?

i see you are trying to push a file to your download folder on the sd card...
you can just drag and drop for stuff like this.

true true, not sure why i didnt think of that, i do it all the time... But would i use those instructions if i wanted to move a file say a recovery file to the bin directory?

i have never seen the need to use adb for this phone. it is not a nand locked device, so there is no real use for it (im speaking for users, not devs). if you want to push a file, jsut use root explorer or similar. thats all you need.
also, it seems to me like you are trying to get krylons cwm. just flash bali instead. no need for the recovery file or update.zip.

[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989

If your phone shuts straight down after pressing the power button and your have no lock screen, read below for solution. Before you do any of this, please note that this was caused by the note radio, aka uclc5, and if u still have it, please remove it! Also causes include a corrupt efs partition. This guide will help to restore key files important to the operation of your phone
There are three methods available. The first and second one are recommended. If you are uncomfortable with adb and command prompt please use method one
UPDATE: This has been confirmed as working on T989!
WARNING!
Method 3 is only to be used if one and two fail, or if you are positive your efs is corrupt!
Original source for solution, with a few method changes by me:
http://forum.xda-developers.com/showthread.php?t=1438451
METHOD ONE
1.) Use busy box installer from the market and re-install even if u have it working
2.) If step one doesn't work, install super su updater, and update it, then try step one again.
3.) Boot into cwm and dark side wipe 3x
4.) Flash rooted 2.3.5 from thread below
5.) Boot into rom and install root explorer
6). Navigate to /efs/imei/
7.) Press menu and select new file
8.) Name it "keystr" exactly as in quotes
9.) Long press keystr and select edit in text editor
10.) Type "ON" and press back, selecting save.
11.) Reboot and make sure keystr file is still present.
12.) Now u have a few options. U can flash ics back using either Odin one click (UCLA4 or UCLD2), but I don't recommend this. Flash one of the ics roms from the development section, we have great devs!
Rooted 2.3.5 zip:
http://d-h.st/ce75z460t847
METHOD TWO
1.) You must have the Samsung drivers installed for the skyrocket, available from here:
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
2.) Once installed, download the attached zip, its a copy of ADB with the needed file inside
3.) Unzip to any location
4.) Boot phone into cwm
5.) Go into Mounts and Storage, and select "mount /efs". Once done connect usb cable to phone and computer
6.) Open command prompt and navigate to the unzipped adb. Issue the following command "adb devices" it should list phone
7.) Now issue the following command "adb push keystr /efs/imei"
8.) Reboot phone and check presence of keystr file in /efs/imei directory with Root Explorer
METHOD 3
Flash attached EFSFix.zip in cwm and reboot.
A SPECIAL THANKS AND SHOUT OUT TO:
mahausrath and Colombiano80 for providing the efs dumps i needed
cmbrown for being a faithful tester!

No download link at thread for Rooted 2.3.6
---------- Post added at 04:03 PM ---------- Previous post was at 03:32 PM ----------
Found a mirror
http://d-h.st/ce75z460t847
---------- Post added at 04:50 PM ---------- Previous post was at 04:03 PM ----------
Still not working. It wont let me write the file keystr to the directory, just says failed, but I can write other things to it. I'm really really confused please help.

I found the error Confusing
instead of putting "NO" put "ON"

Dwolf16 said:
I found the error Confusing
instead of putting "NO" put "ON"
Click to expand...
Click to collapse
typo, main op edited

This may be just me, but I still can't get this method to work. I can't make a file called keystr. I've tried several times using a multitude of Root exploring programs (EStrong, Root Browser, Root Explorer, Astro, ect.) I make sure it's mounted as write and do the works and it just don't work.

did u try the stuff in the pm I sent?

yea im having the same problem its not saving after shut down..

ConfusingCurve said:
This may be just me, but I still can't get this method to work. I can't make a file called keystr. I've tried several times using a multitude of Root exploring programs (EStrong, Root Browser, Root Explorer, Astro, ect.) I make sure it's mounted as write and do the works and it just don't work.
Click to expand...
Click to collapse
I can't create the file either, any help would be appreciated.

i've updated the op with a new method. since efs won't allow you to write from inside android, i've used adb with the push command.

icenight89 said:
i've updated the op with a new method. since efs won't allow you to write from inside android, i've used adb with the push command.
Click to expand...
Click to collapse
Do we need the android sdk for this?

mimart7 said:
Do we need the android sdk for this?
Click to expand...
Click to collapse
nope, I included EVERYTHING u need

Yo ice nthn is working i did everything that it says plus what you've sent me and still nothing

Still nothing

Dwolf16 said:
Still nothing
Click to expand...
Click to collapse
What's the problem? You can't use adb?

Ok so here's the break down
i flashed the efsfix.zip
i go into mounts and storage, and mount /efs ( a error saying Cant Mount /efs!)
i go to cmd.exe and find the Adb folder that has been unzipped
i detect devices with adb devices
i then adb push keystr /efs/imei
it says
C:\ADB>adb push keystr /efs/imei
0 KB/s (2 bytes in 0.002s)
I then reboot go into root explorer and nothings in efs/imei/ and theres nothing in there but the parent folder

Dwolf16 said:
Ok so here's the break down
i flashed the efsfix.zip
i go into mounts and storage, and mount /efs ( a error saying Cant Mount /efs!)
i go to cmd.exe and find the Adb folder that has been unzipped
i detect devices with adb devices
i then adb push keystr /efs/imei
it says
C:\ADB>adb push keystr /efs/imei
0 KB/s (2 bytes in 0.002s)
I then reboot go into root explorer and nothings in efs/imei/ and theres nothing in there but the parent folder
Click to expand...
Click to collapse
alright, that's it. ur efs partition is corrupt, but I need a dump from a fresh stock untouched phone to make sure its fixed properly. In the mean time, I have made a zip of my efs. So change the instructions and do this.
Make a new folder I'm the same folder as adb.exe and name is efs. Extract the contents of attached zip inside efs folder. When u use adb inside cmd, type "adb push efs /". Then reboot. Report back on if that works or not

ok so i rebooted what should i be looking for? when i was in root explorer nothing changed. When i went back into cwm it's still saying "Can't mount efs!" But in the cmd prompt it showed the "adb push efs /" worked

do u have a keystr right in /efs? does ur lock screen work, or power button? If not ur gonna have to wait til I get an efs dump from someone

icenight89 said:
do u have a keystr right in /efs? does ur lock screen work, or power button? If not ur gonna have to wait til I get an efs dump from someone
Click to expand...
Click to collapse
yea i got nothing....also when i did method one originally i would make the file
keystr
type in "ON"
Saved
and it would work until i rebooted...i just there was a way to save it after boot

The push worked, but there is nothing in the imei directory.

[Completed] [Q] Trouble with getting back on stock with Stock Nandroid Backups

I ran into bit of a problem with my HTC One m7 and I have to return to a stock ROM. There are a couple issues with this as there are no RUU files for a Bell Mobility (Canada) phone but there is a stock nandroid backup http://forum.xda-developers.com/showthread.php?t=2428276
So I downloaded the nandroid backup and attempted to restore it through CWM. Problem is I cannot seem to locate the unzipped folder in CWM restore when running the recovery on my phone. I have a mac so adb commands are slightly different and I am unsure to how to properly push the folder into the CWM backups. I also tried in Android File Transfer but the backups folders are hidden. Could anyone possibly direct me on how to properly attempt to do so? It would be much appreciated.
Thanks

RobotRob said:
I ran into bit of a problem with my HTC One m7 and I have to return to a stock ROM. There are a couple issues with this as there are no RUU files for a Bell Mobility (Canada) phone but there is a stock nandroid backup http://forum.xda-developers.com/showthread.php?t=2428276
So I downloaded the nandroid backup and attempted to restore it through CWM. Problem is I cannot seem to locate the unzipped folder in CWM restore when running the recovery on my phone. I have a mac so adb commands are slightly different and I am unsure to how to properly push the folder into the CWM backups. I also tried in Android File Transfer but the backups folders are hidden. Could anyone possibly direct me on how to properly attempt to do so? It would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Too bad the M7 doesn't come with a card slot. If it did, you could have made a "last known bad" backup with CWM to make CWM create the appropriate backup folders on the MicroSD and then dump the right backup into that folder. Ah well.
I would adb push the backup files, one by one to internal storage (something like /sdcard, can "adb shell" to poke around for the right path), and then "adb shell" in to copy/move the files to the right CWM backup folder (I used TWRP for so long, I forget the full path).
But then again, i looked for the guide you may have followed:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [GUIDE] Return to stock for Canadian HTC One Users
You need to have TWRP, not CWM, to read this nandroid.
Follow the steps in the first post, and you should be good to go (any questions can go in that thread as well). Hope this helps.

joel.maxuel said:
Hello, and welcome to XDA!
Too bad the M7 doesn't come with a card slot. If it did, you could have made a "last known bad" backup with CWM to make CWM create the appropriate backup folders on the MicroSD and then dump the right backup into that folder. Ah well.
I would adb push the backup files, one by one to internal storage (something like /sdcard, can "adb shell" to poke around for the right path), and then "adb shell" in to copy/move the files to the right CWM backup folder (I used TWRP for so long, I forget the full path).
But then again, i looked for the guide you may have followed:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [GUIDE] Return to stock for Canadian HTC One Users
You need to have TWRP, not CWM, to read this nandroid.
Follow the steps in the first post, and you should be good to go (any questions can go in that thread as well). Hope this helps.
Click to expand...
Click to collapse
Hey man thanks for replying. So I flashed the TWRP (which I actually had previously) and now I am just having trouble locating the actual backup folder, it seems to be no existent. I did step 4 so the Backup folder should be created then right? Now im on step 6 but I cant find the folders. Maybe im missing soemthing..

RobotRob said:
Hey man thanks for replying. So I flashed the TWRP (which I actually had previously) and now I am just having trouble locating the actual backup folder, it seems to be no existent. I did step 4 so the Backup folder should be created then right? Now im on step 6 but I cant find the folders. Maybe im missing soemthing..
Click to expand...
Click to collapse
If you are on a custom ROM, your /sdcard/ folder may be called something else. Trace your steps by doing this from a console on your PC (with the cable connected between, and ADB debugging enabled):
Code:
adb shell
cd /sdcard
ls
cd TWRP
ls
cd BACKUPS
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
You may get stuck on line two, maybe along the lines of "No such file or directory". If so, replace step two with:
Code:
cd /storage
ls
cd <OUTPUT FOLDER of LAST COMMAND - should start with sdcard>
All this will give you the path in which to push the files to.
Also, don't be afraid to use the experts found in that guide by posting there. I don't have an M7 so I am basing my thoughts off different devices.
Hope this helps.

joel.maxuel said:
If you are on a custom ROM, your /sdcard/ folder may be called something else. Trace your steps by doing this from a console on your PC (with the cable connected between, and ADB debugging enabled):
Code:
adb shell
cd /sdcard
ls
cd TWRP
ls
cd BACKUPS
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
You may get stuck on line two, maybe along the lines of "No such file or directory". If so, replace step two with:
Code:
cd /storage
ls
cd <OUTPUT FOLDER of LAST COMMAND - should start with sdcard>
All this will give you the path in which to push the files to.
Also, don't be afraid to use the experts found in that guide by posting there. I don't have an M7 so I am basing my thoughts off different devices.
Hope this helps.
Click to expand...
Click to collapse
Hey man, thanks for your help. I was able to find the correct path by doing a backup, just of boot.img in recovery and that shows where the file is stored /data/media/0/TWRP/BACKUPS/serial number/backup#.
So now I am trying to access the path through adb shell (so I can push the stock files) but I am geting "Permission denied".
Do I need S-Off to go about doing this??

RobotRob said:
Hey man, thanks for your help. I was able to find the correct path by doing a backup, just of boot.img in recovery and that shows where the file is stored /data/media/0/TWRP/BACKUPS/serial number/backup#.
So now I am trying to access the path through adb shell (so I can push the stock files) but I am geting "Permission denied".
Do I need S-Off to go about doing this??
Click to expand...
Click to collapse
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.

joel.maxuel said:
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.
Click to expand...
Click to collapse
I entered shell. Then entered su , but it still says Permission denied..?

joel.maxuel said:
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.
Click to expand...
Click to collapse
Sorry I... I uninstlaled supersu app by accident so that makes sense... Re-installed it and will try to push files.

joel.maxuel said:
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.
Click to expand...
Click to collapse
I can reach the path no problem now in su with adb shell /data/media/0/TWRP/BACKUPS/serial#/backupfolder/
but what is the proper command to copy the unzipped nandroid backup files to the phone?

RobotRob said:
I can reach the path no problem now in su with adb shell /data/media/0/TWRP/BACKUPS/serial#/backupfolder/
but what is the proper command to copy the unzipped nandroid backup files to the phone?
Click to expand...
Click to collapse
Hi,
That would be (while outside of the unzipped folder):
Code:
adb push <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
e.g: (example partially modified for my smartwatch)
Code:
adb push 2015-11-09-LCA43 /data/media/0/TWRP/BACKUPS/04a0e5ac02a27e76/
Then when you are in TWRP, look for the name of the unzipped folder.
EDIT: BTW, you may have permission errors this way like you did before in the exploring phase. So you may need to:
Code:
adb push <name of unzipped folder> /data/media/0/
adb shell
su
mv <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/

joel.maxuel said:
Hi,
That would be (while outside of the unzipped folder):
Code:
adb push <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
e.g: (example partially modified for my smartwatch)
Code:
adb push 2015-11-09-LCA43 /data/media/0/TWRP/BACKUPS/04a0e5ac02a27e76/
Then when you are in TWRP, look for the name of the unzipped folder.
EDIT: BTW, you may have permission errors this way like you did before in the exploring phase. So you may need to:
Code:
adb push <name of unzipped folder> /data/media/0/
adb shell
su
mv <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
Click to expand...
Click to collapse
I still get permission errors when trying to push it to /data/media/0/
Ill try doing it to /sdcard/ , then adb shell , su , mv <name of unzipped folder>/data/media/0/TWRP/BACKUPS/<serial#>/

joel.maxuel said:
Hi,
That would be (while outside of the unzipped folder):
Code:
adb push <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
e.g: (example partially modified for my smartwatch)
Code:
adb push 2015-11-09-LCA43 /data/media/0/TWRP/BACKUPS/04a0e5ac02a27e76/
Then when you are in TWRP, look for the name of the unzipped folder.
EDIT: BTW, you may have permission errors this way like you did before in the exploring phase. So you may need to:
Code:
adb push <name of unzipped folder> /data/media/0/
adb shell
su
mv <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
Click to expand...
Click to collapse
Thanks so mucb man! I had to adb push to /sdcard/, for some reason pushing to /data/media/0/ was still giving me permission denied. Once pushed, I did the following to move it to the correct path;
adb shell
su
mv 'nandroid backup unzipped folder' /data/media/0/TWRP/BACKUPS/serial#/
Then ran recovery and restored the stock backup.
Worked.
One big problem... I had to restore because my IMEI was gone when I flashed custom ROM. So after all of this, my IMEI is still unkown and lost. I do know what my IMEI nukber is though because I wrote it down. Is there anway I can get it back??

RobotRob said:
Thanks so mucb man! I had to adb push to /sdcard/, for some reason pushing to /data/media/0/ was still giving me permission denied. Once pushed, I did the following to move it to the correct path;
adb shell
su
mv 'nandroid backup unzipped folder' /data/media/0/TWRP/BACKUPS/serial#/
Then ran recovery and restored the stock backup.
Worked.
One big problem... I had to restore because my IMEI was gone when I flashed custom ROM. So after all of this, my IMEI is still unkown and lost. I do know what my IMEI nukber is though because I wrote it down. Is there anway I can get it back??
Click to expand...
Click to collapse
So your EFS partition got borked. That's not good.
Unfortunately, even with the IMEI number known on paper, there is very little you can do to get that repaired. I will suggest this thread:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [Q] No IMEI or Baseband
Read it head-to-toe before adding a post, so you have an idea as to which are the right questions to ask. EFS is unique to the device, and once it's gone, (in almost all cases) it can only be rebuilt through a warranty service unfortunately. Which is why I do full block backups before I really mess around with a device. But, hindsight is 20/20.
Sadly there is nothing else I can suggest. Glad you made it this far though.
Best of luck!

joel.maxuel said:
So your EFS partition got borked. That's not good.
Unfortunately, even with the IMEI number known on paper, there is very little you can do to get that repaired. I will suggest this thread:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [Q] No IMEI or Baseband
Read it head-to-toe before adding a post, so you have an idea as to which are the right questions to ask. EFS is unique to the device, and once it's gone, (in almost all cases) it can only be rebuilt through a warranty service unfortunately. Which is why I do full block backups before I really mess around with a device. But, hindsight is 20/20.
Sadly there is nothing else I can suggest. Glad you made it this far though.
Best of luck!
Click to expand...
Click to collapse
Ok thanks for all your help. I had only wanted to get it back to stock so I could unlock the phone from the carrier and put a new im card in it.