Related
I currently have a mytouch 3g and am running a slide rom on it, problem is there is no keyboard, how do I manually install an apk file preferrably from the computers console such as swype or astro both of which apk files are currently on my sd card. Any help is much appreciated, I started using this forum in 2008 but have never once posted, sad really. ive been trying to install it via adb commands but I keep getting device not recognized errors, feel free to flame my noobishness
Once you have a file explorer you can just click on APKs to install them. If you don't have access to the market to get a file explorer you will have to install them using the ADB method. I found a forum post that gives some rough instructions, but it sounds like you don't have ADB set up correctly. Also I believe the path used with the adb install command is the location of the apk on the PC.
http://androidcommunity.com/forums/f4/how-to-install-apps-using-adb-4482/
The following is a response to someone having a similar problem on another site:
http://www.androidkit.com/steps-to-install-and-uninstall-apk-file-on-android-g1-device
The message is coming because the drivers for the G1 Android device are not properly installed.
If you are running windows, Check so:
Right click on My Computer, and click Manage, then go to the device manager
If you see an “ADB Interface” category at/near the top, with “HTC Dream” under it, then you’re good to go.
Else, you need to install the drivers by pointing to the driver location to the usb_driver folder under the android sdk folder installed by you, while the device is connected, and the system prompts for it.
Click to expand...
Click to collapse
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
bump. i also need this. btw have you tried using a script to do it?
danboard said:
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=698059
and especially did you install this driver?
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I do have read the thread and I have installed that driver. While in recovery mode using GOT's or OpenRecovery I notice that under device manager it says my phone is listed as "Android Phone" and if my phone is on and I connect it to my computer with USB debugging it lists it as "ADB interface". I can't get the phone to appear under adb devices while in recovery mode.
USB-Debugging active? (Settings-->Development)
It is when the phone is on, but what I am trying to do is push a file to the phone while its "off" in recovery mode so the usb debugging is irrelevant or so i believe.
Yes, sorry, you are right.
As I can remember, I have had a similar problem a year ago...
Try to copy adb into another directory and use it from there. Sounds stupid, but helped me in the past.
Sent from my Milestone using XDA App
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
danboard said:
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
Click to expand...
Click to collapse
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
micdim said:
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
Click to expand...
Click to collapse
Seems OK now. I just reinstalled official SDK.
dl.google.com/android/installer_r08-windows.exe
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Hi - Would really appreciate your help here. Thanks for the tip on turning debugging off to get to the phone so I could install the USB drivers. Problem now is that ADB just refuses to connect to it. It shows up asa disk drive in Devices, but when I do a kill-server then start-server then adb devices, it doesn't list any devices, and an adb shell just says device not found.
Do I need to reboot Windows, or the phone? Seems unlikely. I can open a window to the phone, but can't get access to install the Gingerbreak and su files I need to root it. Going crazy!
Thanks,
Eric
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Black-Falcon said:
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
ClarkSt said:
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Click to expand...
Click to collapse
Try downloading busybox from the market, or downloading titanium backup and hit the "problems" button when you open it and select get busy box
Black-Falcon said:
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Tried GingerBreak. No good. "permission denied".
Good idea - I got Busybox installed this way, but still no joy from Gingerbreak.
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
DroidXcon said:
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
ClarkSt said:
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
Click to expand...
Click to collapse
Check the development thread for the Charge. There's a thread on how to rollback to ED1 with root using Odin.
Edit: Direct link: http://forum.xda-developers.com/showthread.php?t=1085190
droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Dude - THANK YOU!!!! I could not get those drivers to install!!!
Please - Stickie!!!
If you want the drivers and don't trust the sources posted anywhere (we're not trustworth ?) you can get them from the phone itself. They are located in the file /system/etc/autorun.iso and you can extract them from it.
i need help with rooting the pantech burst 4.0.4 i found a website but i lost the link soooo can anyone help me
mustafa.ali61 said:
i need help with rooting the pantech burst 4.0.4 i found a website but i lost the link soooo can anyone help me
Click to expand...
Click to collapse
found the website: http://pantechburst.blogspot.com/2012/10/rootrecovery-pantech-burstprestop9070.html
i cannot connect adb device
Have you turned on USB debugging in settings?
Yeah usb debugging is on but the computer doesnt recognize it as a adb device
Make sure you have the right drivers installed on your computer. Try removing and re-adding them. Also, try a different USB cable.
i connect adb device,but i stuck at
fastboot boot cwm-5.0.2.7-presto.img
and after i press enter i get
cannot load 'cwm-5.0.2.7-presto.img
someone help pleaseeeee!!!!!! :crying:
Did you put the cwm-5.0.2.7-presto.img file on the SD card? Also, if you're sure that's the correct CWM for your device, you can use Android Flash Recovery to flash it.
OK I'll try that yhanks
Sent from my PantechP9070 using xda app-developers app
Not Working
I have no clue what I'm doing because I have never had to use ad before. Everything I have read about rooting the pantech burst says I have to use it. I have downloaded the files and I click "run" then all the other stuff I have to, open the command promt and type in "dir" and it shows it in the directory but when I try to put all the stuff It says that it "is not recognized as an internal or external command, operable program or batch file" I downloaded the 64 bit version of adb and I'm running windows 7 that's 64 bit, can anyone help me?
I have a new Pantech Element on the latest ROM. I spent all day trying to root - the latest one-click seemed to work, but when it rebooted it failed.
I was able to finally succeed with this one here:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
Download the latest adb_restore_rooting and with developer mode enabled run "post.bat". Worked for me and SuperSU actually stuck through reboot for once.
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend
Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?
You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly
Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.
Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.
this is what I pasted:
;c:\adb_fastboot
?
iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.
Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...
Oy vey
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse
OK so my path is broken so I won't be able to run adb commands?
Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands
Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?