Related
1st post here.
Seems like basic problem but I cannot get adb connected to my G1.
I started off on process of upgrading to CM 6.1 but when I was about to put recovery image on phone I discovered flash_image program was not found. Then set off on the adb route but am now stuck. Tried searching but not found answer. Here is what I have done/tried so far:-
PC is XP Pro SP3
G1 V1.6 rooted via Universal method (su works ok via Term)
Downloaded and installed latest SDK in c:\Android-sdk
USB debugging is enabled on phone
SD card is not mounted
When I run "adb devices" (from C:\android-sdk\platform-tools) it fails with
msg "error: protocol fault (no status)"
The basic usb connection to PC is known to be working ok (have copied files to phone sd card etc. no problem if I mount it)
The installation of usb drivers seemed to go ok although I had to do it manually from folder \android-sdk\google-usb_driver
When I look at usb devices with USBDeview there are 3 related to Android phone (all enabled).
1. HTC Android phone usb device (connected)
2. USB Mass storage device (not connected)
3. Android composite ADB interface (not connected)
Further info...
I see other people have had the same problem (with other phones as well) but cannot find any specific reason or fix that works.
I have reinstalled latest sdk rev08
Unintsalled and reinstalled latest google usb drivers (ver 4) endless times
Usb driver install appears to all go ok
In XP Device Manager I get Android Phone device which expanded shows single Android Composite Interface Device which has staus enabled and working ok
I have no "Other" usb devices etc. showing up in Device Manager
USBDeview shows 3 usb devices for Android phone. The connected one shows the htc serial no. The ADB composite interface is not connected and has no serial number.
I have tried different usb ports, cables, and another standard G1 phone - all gives same results
I noticed the adb_usb.ini file had no device id in it, I ran "update adb" as per comment note at top of adb_usb.ini but still got not entries in file.
Someone surely must have solution to this. I cannot believe a G1 phone does not work/been tested with sdk adb.
Maybe some source code guru can tell me under what conditions adb gives the "protocol error: no status" msg.
Or could someone with a working G1 adb usb connection post their adb_usb.ini etc.
Have spent 2 days on and off fiddling with this sdk now. :-(
Thanks
Shame you didn't spend some of that two days reading the site rules and the fact that not only is there Q&A section but also try posting in the ADB threads that are littered around these forums.
Catch me on irc, link in sig and I'll see what can be done.
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
So what does helping you get adb setup help android G1 Developmet?
Sent from my HTC Dream using XDA App
lolmensch said:
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
Click to expand...
Click to collapse
fastboot uses fastboot.exe, not adb.exe. Adb works while in recovery or while booted.
Computer Hardward: Windows Vista 32 Bit
Phone: HTC Hero-Sprint
Ultimate Goal: Putting Android 2.2 on my phone
I'm not a programmer or have any in-depth developing knowledge . However, I follow directions precisely. I feel like I've tried following several different directions on XDA and I start completely over each time trying a different one(uninstalling SDK and re-installing per particular directions) and they have all came to no avail.
The following link I will use as an example set of directions:
droidoholics.com/forum/viewtopic.php?f=20&t=187
BUT, when i get to this section in the directions:
" When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android-sdk-windows\google-usb_driver) and install the adb driver"
I follow the directions and I've verified the folder and contents are there. I unfortunately ALWAYS get the following message:
"Windows was unable to install your ADB"
"Windows could not find driver software for your device"
I need help getting past this beginning step and feel like I've looked everywhere and followed all directions. Any help out there?? I'm drooling in anticipation of getting 2.2 for my device that the carrier will not be updating. This small step is stumping me severely.
I am a c++ programmer by trade who is just now looking into android phones not only for communication but also for development. I picked up the Samsung Galaxy from Boost Mobile in order to first learn how to root, flash ROMs, and then get into dev.
My first goal is to root the phone so i can use it as a wifi hotspot. I first tried to download quick settings to see if i could get the wifi hopspot that way. I can see the hidden option for wifi hotspot but everytime I press it to turn it on, the phone disables the wifi totally. I then tried z4root, not root. I tried gingerbreak and it did not work. I would try to use superoneclick but cannot find usb drivers that will work with the galaxy prevail while its in usb debugging mode.
Any advice on how to get this phone rooted would great. Can you also list the prevail as one of the device supported on this site to spur development?
Not sure if you've come across the Prevail source code, the file name is SPH-M820_OpenSource_Froyo.zip
I can not post an actual link because I'm new to this site, but you can find the file here:
opensource dot samsung dot com/reception/reception_main.do?method=reception_search&searchValue=m820
replace "dots" with a period
I have not been able to get mine rooted either, but I did find these drivers seem to work for the phone with win7 and xp.
http://dl.dropbox.com/u/12826399/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
Try Z4root app I think this might work considering there arent any nam locks on this phone go to 4 shared and look for the apk files as this app is no longer available in the market! I have used this app on the following devices, htc hero, sprint zio, samsung moment, droid 1, droid 2, &droid global!
I tried Z4Root it did not work.
recovery mode
recovery mode is vol up + power
says
Android system recovery (3e)
EATH /data/update_sucess
E:Update logfile dose not exsist
#MANUAL MODE#
navigate with vol keys and camera button to select
z4 root and super one click
i tried z4 and the app closed at acquiring root shell
super one click also failed with psneuter and ginger break
fails at running psneuter and at running gingerbreak
also fail with shell root in same way
unrevoked
ps the unrevoked roots just do not detect the phone
odd recover style screen
if you hold down vol + and vol - and camera then tap power a screen comes up that starts with little kernel
vol - and camera makes the phne show "downloading..."
this is shown in windows as "samsung usb compsite device"
and "samsung mobile modem"
on linux
dmesg output of the "downloading..." screen
[ 77.031415] usb 1-1: USB disconnect, address 2
[ 84.590135] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 84.748548] cdc_acm 1-1:2.0: This device cannot do calls on its own. It is not a modem.
[ 84.748762] cdc_acm 1-1:2.0: ttyACM0: USB ACM device
********-laptop:~$
i have tried all known roots to my knowledge: z4 (rageagainstthecage), psneuter, and gingerbreak. none work. so im with you, out of luck.
same here i tired a bunch and no luck
I've been trying too, no luck at all, been at it since last Friday, but my knowledge is not nearly as good as most of you, so I assumed I just didn't know what I was doing.
I tell ya, I'd love to see root on this thing. Sweet little device. Greatly appreciate all who are working on this task
I have not found a way to root this phone but i did accomplish USB tethering. Install Samsung Kies (for usb driver for prevail), install PDAnet on computer and phone, and away you go. I am looking for a windows 7 bluetooth driver for the prevail that way i could tether via bluetooth DUN. Does anyone have any success finding a prevail bluetooth windows driver?
how to root
Is there someone who can direct me to a good place on how to develop the root, I would be willing to spend some time working on this. In particular is there any work that I can do to help a developer to create the root.
themonkeymixer said:
Is there someone who can direct me to a good place on how to develop the root, I would be willing to spend some time working on this. In particular is there any work that I can do to help a developer to create the root.
Click to expand...
Click to collapse
I wish google could help for that lol. I want to move my apps from the internal memory onto a sd. 164mb internal memory come the **** on
Any1 root this thing yet??????????
Same experience here, z4root required phone reboot as it kept setting off the vibrate function (permanent root) and eventually locked up the phone. z4root temporary root didn't work either. SuperOneClick failed as well with both exploits and locked up on Windows 7 x64 while running exploits. Can't find any information on Google. However, I am a 4th year Software Engineering student and would be willing to work with others to find a fix.
The Samsung Galaxy Prevail is a pretty cool little phone for the money and worth the exploitation effort. For those interested in working on this issue with me know that I am both a Windows (7 x64) and Linux (Slackware x64) user with a Java programming background. Look me up (email) on my profile.
From what I understand... We'd have to set up a rom manipulation environment (cooker?). Unfortunately the only tutorial I can find is the one for manipulating HTC roms. I'm not experienced enough to know if it could be used for all Android roms and too much of a chicken to try it out and risk bricking my phone.
Once the rom manipulation environment is set up you can go and add root support, take out unwanted apps, etc.
I'd also be willing to put in some effort into learning this if someone is willing to put in some time to show me the ropes... or point me in the right direction.
So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.
is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.
shansmi said:
is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.
Click to expand...
Click to collapse
I have not changed anything since the first success of my Skyrocket root. It's weird that it would root the first Skyrocket but not the second one.
I used this one.
http://androidadvices.com/root-samsung-galaxy-s2-sky-rocket-4g-sgh-i727-tutorial/
Solution for "Files not found" and "permission" when trying to run ZergRush
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!
trying to root
ashque01 said:
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!
Click to expand...
Click to collapse
I still get errors "system cannot find the path specified" and it doesn't work.
ashque01 you put "D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat"
I didn't get that to work until I switch the > to a \ the arrow instead of a backslash makes a difference, beg pardon but I don't know dos very well and I did use the arrow with no success, lol...
Once in the command prompt (you get there by typing exactly that "command prompt" in search bar, after clicking the start button in windows 7) Right click on command prompt to run as administrator.
I put D:\DooMLoRD_v3_ROOT-zergRush-busybox-su\runme.bat because that's where I used 7zip to extract it to, in the root of hard drive partition. It ran but with errors and announced done! press any key to continue.
I tried it again by creating a subfolder on the D: partition named android like you did, tried it again, same thing,
Still hoping to get a superuser icon so I can download my root explorer app from the market.
YAY!
I got root.
I told all of about it in that thread I started titled s#%rocket. I did admire what Entrophy remarked about it's hardware being disagreeable, but that was in the i777 thread. I had no business there (mod moved my thread, thank you) as my handset is i727.
I coulda swore that's what about phone said before I started but sure enough when you pull the battery it says i727 right there, can't argue with that, I was just being "elevator up, but door not open"
Beg pardon
androiduser1 said:
So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.
Click to expand...
Click to collapse
use 2.3 not 2.2
Sent from my SAMSUNG-SGH-I727 using xda premium
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.