I need to know more about ADB I guess, like how to get it to stay open when I double click the app if thats even how I open it. Instead the window keeps closing as soon as it opens.
My friend (the one who owns this forum account) just downgraded my G1 from RC33 to 29 and now its asking me to sign in but I can't. Apparently my girlfriend can't either on her phone and we didn't do anything with hers but I just signed her in through wifi since it wasn't on the setup screen like mine was. I on the otherhand am stuck at the beginning and need a way to get around it, I don't know why we lost the data plan we had all of a sudden but I'm not going to bother with that and instead will keep moving forward with an alternative.
I'm completely noob to all things command promp so I don't know what an SDK is, just found out what the ADB is and dled that and the drivers but can't start anything up as of yet. I know my android is at RC29 because of the reboot test on the how to bypass the registration thread.
EDIT: Lmfao I guess I picked a bad time to modify my G1, at the time of this post there is a global outage of T-mobile's internet, everything west of the mississippi river is out so thats why I couldn't sign in before, if this thread gets locked or ignored then its ok, I can just wait it out, but just goes to show murphy's law is the real deal, the day I decide to finally start editing stuff this happens.
I'm not really an expert and I had to learn as I went, but here's how I went through the same problem.
Basically, you don't run ADB as a normal program, you open a command prompt (for vista and xp go to run and type cmd) and then you have to navigate to the folder that ADB is in, so if you have the SDK on your desktop youd type something like
"cd c:\users\yourusername\desktop\SDK\tools" (for vista)
yours will probably differ, but use "cd" to navigate to the folder ADB is in. Then assuming you have your phone and the drivers setup properly, when you're navigated to that folder you can type commands that start with adb or whatever and they should work.
If that doesn't work then your phone may not be setup properly, in which case you need to follow the steps in the registering without a data plan thread, although I had a sim so I skipped the disabling of the insert sim screen. The rest is fairly simple, assuming you've got past the insert sim screen somehow you need to type on your phone
<enter>setprop persist.service.adb.enable 1<enter>
I did this in the email box of the signup so you can actually see what you've typed because you won't know if it's worked until you actually try it. After that again type
<enter>telnetd<enter>
which will allow you to get root access to the phone temporarily, then we connect to your phone from your computer.
In a command prompt on your computer do what I said up top by navigating to the folder ADB is in (c:\users\yourname\desktop\sdk\tools or whatever depending on which version of windows you're on and where the SDK is) and type
adb shell
this will probably say the daemon is not currently running, start the daemon etc.... this is good. If it then gives you a hash (#) at the start of the line you are now accessing your phone from your computer. If not, type
adb devices
and see if it gives you anything under where it says "List of devices attached" in the command prompt. If not it's not recognising your phone so you need to get it to do that first.
Last step when you have this, on your computer type
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
which should bring up the page on your phone to enable and manage wifi connections... Connect to your wifi like normal, check it says connected on the settings page and press back and you can register over your wifi.
Hope this helps, I'm no pro but this is how I did it and it worked fine.
Related
It took me forever to piece together how to do this will all the pc forums so I decided to write up one specifically for mac.
First your phone has to be rc29 or rooted. please go to http://androidandme.com/2009/05/gui...r-rooting-your-android-g1-to-install-cupcake/ for the best way to do this. To find out if your phone has this hit enter type reboot and hit enter again. If it reboots you are in go shape.
Second you need download a couple of this to your computer.
Android-sdk-mac http://developer.android.com/sdk/download.html?v=android-sdk_r3-mac.zip
and adb http://android.googlecode.com/issues/attachment?aid=2845842048498102014&name=adb.zip
Unzip both files and then place adb in android-sdk-mac/tools folder
Now back to your phone. press enter then setprop persist.service.adb.enable 1 and then enter again.
It should say something like this is not an emergency number.
Now back to your computer. Open your terminal and then go to you finder and find android-sdk-mac. Click tools and then drag adb to your terminal and type shell after it and hit enter. If you get a permission denied type sudo and then drag adb over again.
You should get daemon started successfully and then next line $
type am start -a android.intent.action.MAIN -n com.android.settings/.Settings and hit enter.
Now look at your phone. It should have popped up a screen letting you in to wireless connections.
I hope this helps
nice work ;]
Ok so I started this thread about 3 months ago. I got one nice work...yay for me....but that was it I would really like to know if this is working everyone. I know it is mac based and you can probably figure it out from the windows based ones but I do want to make sure it is working for everyone so if you use this please let me know if it worked or any that should be added to it by posting a reply. Thank you
this is exactly the same as jf's tutorial...
i am not as good with computers and trying to figure out the mac steps using a windows guide took me forever. I was just trying to help anyone else in my same situation.
Awesome!
It works great! After spending 2 days uninstalling, reinstalling and generally fighting with Windows 7's automatic driver installation I borrowed my room-mate's mac and got this done in less than 15 minutes! Incredibly refreshing. Thanks!
...
Wonderful! It worked like a charm.... I just have a problem with the Cupcake interface, I like the Donut much better, is there a way to do this on that interface? And if not is there a way to get the Donut market place?
I've been trying to get Droidcam (and other apps like it to work) but it seems that my phone is "invisible" on my wifi... I can't ping my phone from my computer it says host isn't available, even though I'm successfully connected to my wifi..
Any help?
Aldieri said:
I've been trying to get Droidcam (and other apps like it to work) but it seems that my phone is "invisible" on my wifi... I can't ping my phone from my computer it says host isn't available, even though I'm successfully connected to my wifi..
Any help?
Click to expand...
Click to collapse
Though this is not a long-term fix, you can test whether pinging helps by opening adb shell (if you have the Android SDK installed) and issuing this command:
echo "0" > /proc/sys/net/ipv4/icmp_echo_ignore_all
That will allow pings. That probably gets reset at reboot, though, so if you want to fix it long term I would have to look into where that gets set up or you'd have to put it in a startup script.
I rebooted my phone after doing this and it seems the setting stayed.
How to find the MSL for your Photon Q
chrisngrod posted a tool for getting the MSL from logcat (http://forum.xda-developers.com/showthread.php?p=31765156) but is in the form of a .bat script, which isn't very useful for Mac or Linux users. I'm a decently regular reader, but I guess I've never posted. So sorry that this isn't in the dev section.
I'm assuming a couple things here
You have the android SDK installed, or at least adb available to you
You have a Motorola Photon Q (on Sprint?) plugged into your computer and appropriate drivers installed (if needed--not sure)
USB Debugging is enabled on your device
You know what a terminal is, or at least how to use one
You are in the current directory of adb. If it's in your path, omit the "./"
Make sure your computer sees your phone
Code:
./adb devices
You should see something like
Code:
List of devices attached
T*******Y device
where *'s are numbers. If you don't see any devices, make sure nothing else is interfering (tethering apps on computer, etc)
Now, go to the dialer on your phone, and dial ##DATA#. A menu should pop up, tap on Data Profile, then the three dots at the top right, and finally Edit. Enter 6 random digits, and click Verify.
Now go back to your computer and run this
Code:
./adb logcat -b radio -d | grep "grde"
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Test it out by going back to your phone and typing it in.
This worked for me, and I haven't found anywhere else that talked about doing it for the Photon Q, so please correct any incorrect information.
asinginglamp said:
How to find the MSL for your Photon Q
Now go back to your computer and run this
Code:
./adb logcat -b radio -d
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Click to expand...
Click to collapse
I was able to do this with only the phone and connectbot. Putting in a false code and then looking over logcat for the NV Read 32, Mine was also hanging out with a group of 3s.
KitsunePaws said:
I was able to do this with only the phone and connectbot. Putting in a false code and then looking over logcat for the NV Read 32, Mine was also hanging out with a group of 3s.
Click to expand...
Click to collapse
Nice. I tried doing it with aLogcat, but didn't see anything. Didn't think to try connectBot.
with me it was between the 3's, i copied the msl.bat to the ADB-platform tools folder what i use for compiling-decompiling apk's, and it worked.
This Is Cray
Gojira-r32 said:
with me it was between the 3's, i copied the msl.bat to the ADB-platform tools folder what i use for compiling-decompiling apk's, and it worked.
Click to expand...
Click to collapse
err
i tried this method the only thing i see on the transcript using adb logcat is checksubsidylockpasswrdcomplete<>errorno=RIL_OEM_CDMA_GENERIC_FAILURE..
Like ive tried everything, any suggestions..besides call sprint
batzluminatti said:
err
i tried this method the only thing i see on the transcript using adb logcat is checksubsidylockpasswrdcomplete<>errorno=RIL_OEM_CDMA_GENERIC_FAILURE..
Like ive tried everything, any suggestions..besides call sprint
Click to expand...
Click to collapse
Do you get anything with adb logcat?
???
asinginglamp said:
How to find the MSL for your Photon Q
chrisngrod posted a tool for getting the MSL from logcat (http://forum.xda-developers.com/showthread.php?p=31765156) but is in the form of a .bat script, which isn't very useful for Mac or Linux users. I'm a decently regular reader, but I guess I've never posted. So sorry that this isn't in the dev section.
I'm assuming a couple things here
You have the android SDK installed, or at least adb available to you
You have a Motorola Photon Q (on Sprint?) plugged into your computer and appropriate drivers installed (if needed--not sure)
USB Debugging is enabled on your device
You know what a terminal is, or at least how to use one
You are in the current directory of adb. If it's in your path, omit the "./"
Make sure your computer sees your phone
Code:
./adb devices
You should see something like
Code:
List of devices attached
T*******Y device
where *'s are numbers. If you don't see any devices, make sure nothing else is interfering (tethering apps on computer, etc)
Now, go to the dialer on your phone, and dial ##DATA#. A menu should pop up, tap on Data Profile, then the three dots at the top right, and finally Edit. Enter 6 random digits, and click Verify.
Now go back to your computer and run this
Code:
./adb logcat -b radio -d | grep "grde"
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Test it out by going back to your phone and typing it in.
This worked for me, and I haven't found anywhere else that talked about doing it for the Photon Q, so please correct any incorrect information.
Click to expand...
Click to collapse
The first command works..Recognizes dev, then the logcat command works ONLY when i leave off at the -d. When i do the process i see the RI-MOTEXTem Hook header type 0, requestcode 0x2000016...blah blah blah..how do i write the second part of the comand..?
msl
I ran into that error- OEMRequestunlock thingy.... I tried looking through myself with alogcat, but nothing... at the time I thought I fixed it by downgrading the android OS... then the .bat still didn't work... I figured out that that was because of the path statement not including the location of findstr.exe (grep in this linux example) but now I think that maybe the .bat file didn't work originally because of the path statement and I maybe didn't have to downgrade the OS, but if you're straight up doing it by typing the command into terminal and with grep no less and encountering the problem, then I'll bet it was necessary to downgrade the OS.
So what I'm saying is- you probably have to downgrade the Android OS to one that has the MSL in the ril. Also, it might not be showing up in aLogcat because you'd have to tell it to read the radio log (which is what the -radio switch does)
Hope this helps
I made one phone call to Sprint tech support and simply asked for my MSL, and the lady gave it to me. No questions asked.
As many of you may know, there's currently no native way to screenshot an Android Wear device, and at this point it's pretty cumbersome to need to get to a computer to run ADB just to get a screenshot.
I've managed to at least remove the need for a computer, as long as your phone (or whatever your watch is paired with) is rooted (your watch does NOT need to be rooted), through a simple script I threw together, wearcap. It properly loop-back connects to your device and then connects to the watch over ADB. I'm sure this can be made into an actual app, but I don't care enough or have the time to do it. All you need to do is run it as root with whatever terminal app you desire. Wearcap assumes you've done all the necessary USB debugging settings, which can be found below. Screenshots are saved in /sdcard/Pictures/Screenshots/ on your device and then removed from the watch.
Everything else is pretty self-explanatory, just push the script onto your device, give it executable permissions and be on your way. As noted in the script itself, make sure your screen is on during the connection process, my Moto 360 would typically fail to connect if it was off.
For a reminder of how to setup USB debugging for the devices: http://www.androidpolice.com/2014/0...nlock-the-bootloader-and-root-the-lg-g-watch/
And here is the Google+ thread: https://plus.google.com/u/0/113601948978986762347/posts/6dD6xBrvpjs
"This paste has been removed"
Spere said:
"This paste has been removed"
Click to expand...
Click to collapse
Sorry about that, it's been attached as a text file now.
an apk will be wonderful
I can wrap it into app tomorrow if CEnnis91 is OK with it, I'm thinking to add change of the density as well through adb.
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Kyocera-E4710 - T-Mobile Tethering
I too have purchased one of these excellent flip phones. I really want to be able to tether using T-Mobile's service. Has anyone risen to the challenge yet?
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Rooting Kyocera E4710
Is it possible to root this phone? I would like to install an Android SIP client, the operator said it's not possible to install anything on it. Even though I enabled apps from Unknown Sources.
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
david11717 said:
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
Click to expand...
Click to collapse
Thanks for posting your solution above.
Unfortunately for me I got as far as installing the adb drivers on my PC, reconnecting the phone, and no prompts came up, neither on the phone nor the PC.
I opened a command prompt window and typed "adb devices" and got the following message:
adb devices is not recognized as an internal or external command,
operable program or batch file.
Any suggestions?
As long as ADB driver isn't made system-wide accessible ( i.e. got added to PATH environment variable of Windows OS ) you get the message mentioned.
My Kyocera E4710 outer screen has an alarm that I can't get to go away. I can't see who is calling me because the alarm blocks the caller info. I have a few alarms but they are all turned off and there is not a way to delete them. I've gone through the user manual and it doesn't show how to get rid of this alarm (which shouldn't show since there isn't one enabled). Does anyone know how to get rid of this alarm on the outer screen? Thanks.