Related
For some reason my Heros won't sync when Using HTC sync tried all the driver hacks and stuff It worked with my first non rooted stock Hero and Right before I rooted my 2nd one. Now it won't sync with my moms stock non rooted or my rooted one. The RUU's can't identify them. When I run ADB it finds them just fine. Also, If I run ADB I can only run it once, before I need to reboot .
chococrazy said:
For some reason my Heros won't sync when Using HTC sync tried all the driver hacks and stuff It worked with my first non rooted stock Hero and Right before I rooted my 2nd one. Now it won't sync with my moms stock non rooted or my rooted one. The RUU's can't identify them. When I run ADB it finds them just fine. Also, If I run ADB I can only run it once, before I need to reboot .
Click to expand...
Click to collapse
Try this, it helped me out today.
Forgot OS is Win7 Ultimate 32bit
*Sigh* Did you try it? Im also on Win 7 32bit.
Darkshneider said:
*Sigh* Did you try it? Im also on Win 7 32bit.
Click to expand...
Click to collapse
I copied and pasted everything already... I currently don't ahve a phoen to try it on to see if it works.
I had a issue with this as well the only way around it for me was to fast boot the phone hold volume down when you power up then hit up and then run the RUU.
gizmo0681 said:
I had a issue with this as well the only way around it for me was to fast boot the phone hold volume down when you power up then hit up and then run the RUU.
Click to expand...
Click to collapse
yup I had that issue a month back...
If you don't have the HTC PC Sync software on your phone anymore (that was one of the first things I deleted when I rooted my phone), then you can't initiate the correct debug mode with the computer... or it may be because adbd runs as root... but going to fastboot usb mode and then running the RUU will work. and yes, it works on Win7.
Sorry to be a hassle, but I just can't figure this out!!
I've rooted my phone with the "new clarified method" thread, gotten to the clockwork mod and everything, but once I've done that I just cannot get the Unrevoked 2 to work. I've tried it on Windows 7, xp, and osx, and nothing seems to work! The main issue I'm getting is that it'll do the whole process, and then I think it says "reboot to recovery" and then I just get that old phone with a red triangle error. What could I possibly be doing wrong??? It can't be driver issues, because doesn't OSX do that automatically?
I had a similar issue on windows 7 and a simple pc reboot seemed to work for me.
Nope, still no luck. Am I supposed to put these Reflash files on the phone somewhere? I just feel like I'm missing some big step or something. Why is there no good tutorial on this process yet?
Oh my god I think I'm going to go insane! Please someone, point me in the right direction! I have done this hundreds of times now, I'm gonna die. All I can get is "Done!" and then my phone is showing me a big dumb red exclamation point triangle thingy. What am I doing wrong??????
Was I supposed to do something once I first reached the clockwork on my initial root? Cuz all I did was reboot to OS. I don't know if anybody can tell, but I'm kinda desperate. hah
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
larry996 said:
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
Click to expand...
Click to collapse
I was having the same problem also until I ran reflash.exe and the command prompt both as admin. I also reran Android SDK installing all of the updates. After plugging in the phone, the SDK picked up two more updates, one of which was USB drivers. Once I did that, things seemed to have worked.
Use attn1's method. The clarified method didnt work for me properly.
I assume you never flashed a rooted rom after reaching clockwork mod. If not the phone is not yet rooted. You have to get back to clockwork recovery and flash a rooted rom (either attn1's liberated one or his stock rooted rom). Both found in his liberated thread. Then set up all the drivers for unrevoked and run it. It should work then.
When my phone is just sitting in bootloader, it is not recognized by adb devices.
You have to go through the whole loop process again booting your phone into recovery and connecting the usb cable.
gdeadfan said:
When my phone is just sitting in bootloader, it is not recognized by adb devices.
Click to expand...
Click to collapse
Thats not good, try reformatting your sd card on your pc with an external reader not with your phone and try again. I'm almost certain it needs to be recognized by adb devices when in bootloader.
Just managed to install the Liberated beta ROM, but now unrevoked can't even get past superuser privelages. it's not popping up anymore
Nevermind, it gets past superuser now, but now it just says "waiting for reboot" and completely reboots the phone to the point at which i can use it regularly
Have you installed the hboot drivers?
Re-ran unrevoked?
Edit: Does it reach "done!"?
Yes, yes, and yes. And my phone just keeps getting to the red triangle. doesn't make any sense to me! And at this point, I'm positive I have no drivers getting in the way like Sync etc., and I'm sure HBoot is installed correctly.
Go to the android market and download titanium backup. It requires root so if it installs we know that you are at least rooted.
Try this, because I had the same problem. Go into device manager with Revoked2 says waiting for reboot. Look under devices above my computer or below cant remember and right click uninstall and remove the android device. reboot your computer then see if it installs are does it automatically, if not don't do anything just plug the phone in and get to hboot/ red triangle screen, then try revoked2 again. This finally got loop to read my device then when I got to clockwork I loaded "liberated rom"
Screw revoked2, just get to clockwork recovery and have liberated rom on your SD card ready to go. Then after install I ran revoked2 for clockwork mod.
Good Luck
Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.
having trouble with ADB
i sold my nexus one, so my computer is setup for ADB devices but for some reason it doesn't find the vibrant...also tried to root using method in android developement and it didn't work
any ideas?
Going to assume that your phone is rooted. Go into settings -> applications -> development and make sure that USB debugging is enabled as well as Allow mock locations
then try it in ADB and it should detect your Vibrant.. make sure that drivers for the phone are also installed
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
fordstang99 said:
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=728929 Those drivers.
And uhm.. I don't know if it needs root to use ADB but it would make sense to be rooted so you can have ADB without any restrictions.
Was USB debugging enabled?
ok well i put the update.zip file on the root of the internal memory and hold down the volume up and down and it just boots normally
ok adb is working....i didn't see those drivers thanks
now just the update.zip, cant seem to get into recovery, i geta Downloading....Do not turn off target !!!
ok got everything working
thanks
Same Problem USB DEBUGGING
I just want to be able to use the USB Debugging feature. Is this something that is unly available with root? If so then I have no problem, if now I am not able to have the pc detect my Vibrant when in USB Debugging mode. It will connect without it so I'm curious as to my first question. I am not rooted, but plan to soon.
Thanks for any help
CRX
[EDIT]: Phone rooted and still have same problem!!!
Any help would be appreciated!!
Crx
bump for assistance
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
crxforya said:
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
lqaddict said:
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
Click to expand...
Click to collapse
I dont know what ur talking about. Nobody on this thread said anything about winblues???
ISprayCandy said:
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Click to expand...
Click to collapse
Thank you for this info, ill give it a shot
crxforya said:
I dont know what ur talking about. Nobody on this thread said anything about winblues???
Click to expand...
Click to collapse
crxforya said:
I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
you need winblues drivers for sammy, search for samsung kei software
The updating of my SDK made the difference. I was able to install the correct driver and now ADB is working smoothly again. Thanks for all your help.
Crx
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
My Evo gave me grief for a solid hour when I first got it. Followed the walkthrough here and one of the contingency plans worked like a charm.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Thanks, but it is not a driver problem as the drivers are installed correctly and ADB can see the phone connected.
I tried on 3 different PC's, replaced US cables. everything failed.
I think something is up with my unit which will be going back tomorrow.
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
So it worked fine before you rooted it?
Yes, SuperOneClick is using ADB to push the root files, so i assume ADB worked then.
I am also getting constant device reboots (random) so i think there is a hardware problem. i'll take it back tomorrow.
I had drivers installed, but the set of drivers PDAnet ended up installing for me fixed the issue. Till I get my paycheck, I won't be able to play with it
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
I am now on my 4th phone - so will be waiting for things to simmer down before I go back to modding again, but the other 3 have all had the same issue after using the superoneclick to root.
Once root is done all ADB access goes away. Something is amiss.
edit: More specifically my 4th atrix.
airbillion said:
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
Click to expand...
Click to collapse
I ended replacing the phone as I had other problems with it. Now a adb works fine even after root.
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
SNadler said:
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
Click to expand...
Click to collapse
It does not solve the problem.
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
airbillion said:
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
Click to expand...
Click to collapse
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
clubtech said:
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
Click to expand...
Click to collapse
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
airbillion said:
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
Click to expand...
Click to collapse
I tried restoring my device to factory default several times. It did not solve the ADB problem and not my random reboot problem (even with zero 3rd party apps installed).
I tried installing ADBWireless from the market - no go.
I googled and found a command to run via local terminal to force ADB to stay up - no go.
I finally came to a conclusion that a) I have bad hardware because my device was rebooting b) i can't fix the ADB problem without a full SBF file which we don't have.
Went to at&t, got it replaced. no more reboots. rooted with superoneclick and did not do the sideload fix from that app.
Then i manually edited the settings.db file to allow sideloading and been running fine ever since.
Clubtech,
Thanks for the file! It works for me!
Here is a post on the fix: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1
Can anyone explain this for a noob? i just want aRoot to work and the HDMI cable thing to work... the oneclickroot worked but nothing else will and i think it is because ADB is not recognized...
i have official gingerbread 2.3.5.
i want to root my phone but no method works.
when i follow steps indicated to use superoneclick, the program goes on till step 7 and then stops responding.
i have tried one click root but makes issue of driver. i have installed drivers from many places, even from where the one click program states. still no success.
when i try to use the boot.img method, i cant do it because when after the pressing the keys to enter the pink screen, when i connect it to the pc, no drive shows up into the computer so i cant copy the boot.img file.
i dont know what is the problem. No rooting method is working.
by the way i have installed wondershare mobilego software for android on pc.(Do you think this could make a problem). And on my phone i am using go launcher(Do you think this is making problem). By the way my phone randomly restarts and shutsdown (the reason why i am switching to cyanogen mod). Do you think i should first again do a clean install of gingerbread then do all this rooting and flashing of cyanogen. Please respond quickly.
(If there is a problem of drivers, kinldy post the link that HAS the drivers in it that will allow me to root)
A big thanks in advance!
Did you try with Z4root? I think it works well on Gingerbread. You can try to "downgrade" to your stock rom and then update to GB.
grrrMAN said:
i have official gingerbread 2.3.5.
i want to root my phone but no method works.
when i follow steps indicated to use superoneclick, the program goes on till step 7 and then stops responding.
i have tried one click root but makes issue of driver. i have installed drivers from many places, even from where the one click program states. still no success.
when i try to use the boot.img method, i cant do it because when after the pressing the keys to enter the pink screen, when i connect it to the pc, no drive shows up into the computer so i cant copy the boot.img file.
i dont know what is the problem. No rooting method is working.
by the way i have installed wondershare mobilego software for android on pc.(Do you think this could make a problem). And on my phone i am using go launcher(Do you think this is making problem). By the way my phone randomly restarts and shutsdown (the reason why i am switching to cyanogen mod). Do you think i should first again do a clean install of gingerbread then do all this rooting and flashing of cyanogen. Please respond quickly.
(If there is a problem of drivers, kinldy post the link that HAS the drivers in it that will allow me to root)
A big thanks in advance!
Click to expand...
Click to collapse
I had this problem with SuperOneClick. Happens because all steps are not done properly. Make sure you do all steps and before using SuperOneclick make sure you reboot your phone.
If that doesn't work then PM me and I will send you proper steps.
Good Luck.:good:
grrrMAN said:
i have official gingerbread 2.3.5.
i want to root my phone but no method works.
when i follow steps indicated to use superoneclick, the program goes on till step 7 and then stops responding.
i have tried one click root but makes issue of driver. i have installed drivers from many places, even from where the one click program states. still no success.
when i try to use the boot.img method, i cant do it because when after the pressing the keys to enter the pink screen, when i connect it to the pc, no drive shows up into the computer so i cant copy the boot.img file.
i dont know what is the problem. No rooting method is working.
by the way i have installed wondershare mobilego software for android on pc.(Do you think this could make a problem). And on my phone i am using go launcher(Do you think this is making problem). By the way my phone randomly restarts and shutsdown (the reason why i am switching to cyanogen mod). Do you think i should first again do a clean install of gingerbread then do all this rooting and flashing of cyanogen. Please respond quickly.
(If there is a problem of drivers, kinldy post the link that HAS the drivers in it that will allow me to root)
A big thanks in advance!
Click to expand...
Click to collapse
I had exactly same problem before, make sure that you have ADB drivers installed before using SuperOneClick
after I installed ADB i rooted my phone whitout any problem