Hello! Hope one of you strapping young lads could assist me with this unbearably agonizing problem:
Following these instructions, everything goes smoothly until I run the rageagainstthecage-arm5.bin exploit. It runs successfully, and after it is completed, it kicks me out of the shell. At this point, the next step would be to enter "exit" to exit the shell but the shell has already been exited so that would just close my command window. So, I move on and use adb kill-server and adb start-server, but whenever i try to push or enter the shell I get the error "error: device not found"
The device is on, connected, shows USB Debug enabled, charging, charge only, etc. However, my computer will not communicate with the device until the device is rebooted which I can only assume ends the exploit and halts my progress.
Steps I have taken already:
Restarted computer and device and started over
Changed usb port (went from front USB port to rear)
After exploit runs and stops the adb service, tried unplugging USB, reinserting, unchecking USB Debug and rechecking
I'd like to know if there is either a solution to this specific problem or if there is an alternative to rooting and completing the procedure. Thoughts?
I recently had the same problem. For me, the USB connection stayed up if I the exploit ran from /data/local instead of a temporary directory.
Past that, the official CyanogenMod installation instructions for the HTC myTouch 3G Slide are either obsolete or sloppy bad. I never got the RageAgainstTheCage exploit really working and the posted `flash_image` binary always failed with "illegal instruction".
I ended up using GingerBreak 1.20 to get a working su installation and a `flash_image` binary from an unrelated LG package.
Related
Background:
Phone OS:
Evo 4G, unrooted, latest OTA update.
Computer OS:
Fedora 13
Just noticed that issuing an 'adb reboot recovery' seems to load the correct screen on the phone - the red triangle/exclamation point.
'adb devices' shows the HTC* offline.
adb kill-server / adb start-server shows the same thing.
Going into recovery mode 'manually' (aka Vol Up / Power at boot, then loading to recovery) adb devices still shows nothing.
Will try from a Windows PC on Monday just to verify it's not a Linux issue, but curious if anyone else has run into this? Hoping this isn't something else the OTA screwed - already pissed that my stock Android Launcher was removed (running LauncherPro now, so eh - thanks HTC?)
this is something the update *fixed*
btw wrong section.
Sorry for that. So the update 'fixed' this? No way around it, I suppose?
That happens to me occasionally. Usually I remedy it by some combination of switching between disk drive mode and back to charge only, or rebooting the phone, and sometimes switching usb ports.
sorry thats all I can offer
It seems many of us are affected by this "adb devices offline" trouble :
http://www.google.com/cse?q=adb+off...ub-2900107662879704:fs7umqefhnf&ie=ISO-8859-1
I had to plug the usb cable again to put the device online,
but do you know a way to reset the usb bus of a linux box ?
http://forum.xda-developers.com/showthread.php?t=735994
http://stackoverflow.com/questions/7322843/reboot-offline-android-device-remotely/7685184#7685184
http://android.stackexchange.com/questions/12491
--
http://rzr.online.fr/q/android
Originally Posted by nicbennett
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
Originally Posted by snovvman
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
Click to expand...
Click to collapse
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.
The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!
Thanks.
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
DGreen1 said:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
Click to expand...
Click to collapse
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
snovvman said:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
Click to expand...
Click to collapse
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
My problem was Windows
snovvman said:
The error occurs when no device device connected. Same error when device IS connected.
. . .
I am really interested in a solution and would like to understand what is causing the problem.
Click to expand...
Click to collapse
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Yellowcard8992 said:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
Click to expand...
Click to collapse
Interesting, but I haven't been able to find any other service that is bound to adb and I have no other USB devices connected. Thanks for chiming in though.
tgi007 said:
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Click to expand...
Click to collapse
For me, I have been able to get two Vista and one Windows 7 computer to work with ADB and HTC drivers the first time. I also have an Epic, and the Samsung drivers installed fine as well (even though they are known to have issues).
Unfortunately, ADB just "broke" one day.
I keep thinking that the Evo community has enough brains and knowledge to sort this out quickly...
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
lovethyEVO said:
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
Click to expand...
Click to collapse
Thanks for replying. I had already updated ADB (in platform-tools) before started having this problem. I had also uninstalled HTC sync (reboot, launch ADB w/o HTC sync, same problem) and reinstalled HTC sync, same problem. I updated Java JVM, no change. I then re-downloaded the SDK to a different directory, no dice.
I usually open a command prompt "as Administrator" and run ADB from the directory. Even with a device disconnected, I get the same error. I test this way because if I issued "ADB devices" and it returns nothing, I know it's working. It appears that ADB doesn't even start to the point to poll for devices.
I have, just for laughs, connected my device (USB debugging/charge only), but no joy.
I won't have much time to poke around more until the weekend. If I don't come up with anything, I will take you up on the gtalk. Thanks again.
Windows Vista just makes it all that much harder to fix things...
lovethyEVO said:
If you have installed htc sync before uninstall it and the htc driver installer.
. . .
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
. . .
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
Click to expand...
Click to collapse
In my case, I tried all these things and many more (lived with this problem since first getting my EVO on release date in June). No dice, as Windows Vista, once it installs a device driver, doesn't give the user the option to uninstall it (by Microsoft's expressly-stated intent -- a design decision I vehemently disagree with). At least the user could repair such problems in prior versions of Windows by simply uninstalling a device, choosing "yes" to the "remove driver files from the disk" question, and (after the obligatory and ubiquitous Windows reboot) re-connect the USB device. That would start fresh with that device's driver.
I never invested the time to learn how the USB subsystem registers devices and their drivers (in Windows Vista) in order to determine how to manually remove a driver from the Windows Registry adequately that it would treat the device as "new hardware detected" upon the next connection.
Once Windows Vista has scrambled some internals in the database/registry controlling the USB subsystem's driver knowledge, you're toast. Nothing I could find in Microsoft's Knowledge Base nor MSDN shed any light on how to tackle the removal-and-recreation-from-scratch of the USB system configuration.
Microsoft's stock answer was invariably "re-install Windows". Yeah, thanks for that. Windows, even more than 26 years later, is still not a real operating system, and still has bugs dating back to Windows 3.1.
Sigh.
Check Windows Firewall service.
In my case I just turned off the Windows Firewall and it started working.
regards
Gaurav
i had this problem.
disable any program like Proxifier and firewall
I accidently figured it out
so i was trying to find my cid number because i was flashing ICS firmware and stuff, and the adb deal in the prompt kept giving me the exact same error, and thus would'nt work. after trying everything (such as: installing drivers, killing the process, restarting my comp, reinstalling adb, etc.) for about an hour and a half, i just stumbled upon a page that was linked to in the ICS flash guide, that had a different adb folder download. this download has an entirely different effect on the command prompt and worked so i could get my cid number and rewrite superCid. here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=872134&d=1327512033
Download it, click "start here", then treat it like normal
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
orangeipod1gb said:
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
Click to expand...
Click to collapse
your solution is
netsh advfirewall set currentprofile firewallpolicy allowinbound,allowoutbound
I had it all set up correctly and it worked fine both by USB and TCPIP. At some point in the last day or two this stopped working. I've done a complete reinstall of the SDK on my desktop and followed the instructions here https://devs.ouya.tv/developers/docs/setup
When I do adb devices I just get nothing. adb connect xx.xx.xx.xx gives nothing as well.
When I try to run adb from a terminal emulator on the unit I can start or stop the server but any other adb command results in a 'device not found' message. This message is preceded by some two or three digit word but since my TV crops the image I cannot tell what it says. so it is something like '##r: device not found'
Does anyone have any idea on what I need to do to get ADB working again?
Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2
TadeoNYC said:
Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
There aren't any drivers involved here yet. Nothing happens at all when I plug the system in. No devices are detected, correctly or otherwise.
I'm starting to think the micro usb port is just physically broken. I've tried multiple cables, restarting. Connecting other android devices to my desktop which work fine.
could be the port. I have a heck of a time plugging mine in sometimes. it's like the hole in the casing is just a bit bigger than the actual plug, and I have to fumble around for it. I mostly leave the microusb connected all the time now.
Oh!lol.
That happened to me as well. The micro usb port is deeper than normal. My Samsung plugs did not work,I was able to use one from my Kodak pocket video cam.
Sent from my SCH-I535 using Tapatalk 2
Ok, so I'm trying to just adb tcpip working now to bypass the usb issue. I installed an SSH server and I'm getting this
[email protected]:/ $ adb kill-server
[email protected]:/ $ adb tcpip 5555
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.
beowolfschaefer said:
Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.
Click to expand...
Click to collapse
If you have wireless adb enabled the way to control it so it does not shut down the micro usb port debugging , find the wireless adb .Apk here on xda in the nook color general section and install it then you will beable to open the app and toggle it back and forth to get micro usb debugging back.
My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?
Broomfundel said:
My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?
Click to expand...
Click to collapse
Did you set up adb over wireless?
tcollum said:
Did you set up adb over wireless?
Click to expand...
Click to collapse
I had done but. But it stopped working some time after, and I have not managed to get it going since. Would it stop wired at the same time? Even so would it not have been reset by the factory reset?
Either way, Ill set it with an ethernet cable and see if the flaky wifi was why adb over wifi did not work.
I'm sure a workable solution will turn up. Just disappointed.
Ill report back.
Thanks
Update: Thanks for your help. I tried over wifi and no joy. But ethernet is working. So just got to sort out the flakey wifi now.
Thanks again.
Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta
For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!
HaYNigloo said:
For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!
Click to expand...
Click to collapse
It's also available through the f-droid app.
Sent from my GT-P3113 using Tapatalk 4 Beta
TadeoNYC said:
Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
My wifi works great. unless i try to login to google.
Look here: https://devs.ouya.tv/developers/docs/setup
They changed the device ID, you need to do step 5-6.
More info here: http://www.ouya.tv/devnews.html
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
vbrtrmn said:
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
Click to expand...
Click to collapse
I don't know too much about adb, but I'll try to help
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
I just turned on my console and have come to the conclusion that the automatic update broke su. How, i'm not sure, but it would seem that possibly you'll have to restart the process from scratch, redo adb and reload su.
lets just hope this isn't a sign that all future automatic updates will break su.
*EDIT* So it would seem that there is problems with the drivers. I have gotten ADB to work once again by deleting all the OUYA drivers from my computer and following the steps found at https://devs.ouya.tv/developers/docs/setup HOWEVER this presents a problem in that the system is only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know). Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
After getting ADB back, I got SU back by running through the steps found here: http://forum.xda-developers.com/showthread.php?t=2272266 under how to install busybox, superuser, and su binaries. You should only have to go from step 1 to 4 on that one (only 4 if you still have the files on your computer).
I will note that the steps to get ADB on that second link did NOT work this second time. I'm not sure what this is due to. I'll be starting a new thread with this info, too.
JLCollier2005 said:
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Click to expand...
Click to collapse
Nope.
JLCollier2005 said:
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
[/QUOTE[
No drivers, running OSX & Linux.
Click to expand...
Click to collapse
Hard boot the OUYA and laptop, adb via USB seems to work again.
So far every OTA has removed su.
Sent from my GT-P3113 using Tapatalk 4 Beta
Hi there, I've recently tried rooting my lgg3 but im running into a few problems.
Just to clarify:
I've installed the drivers
Enabled USB de-bugging
Used task manager to end abd.
Tried MTP and PTP
But when ever I run the Oneclick root, it failes to start abd, then fails daemon, and then 'successfully' starts demon only to fail it again. It does this about 3 times before re-booting the phone into download mode.
From there, it asks me to wait for SuperSU to install, which it never does.
I'm really stuck here and could use any help. I've also tried using the GUI and .bat rooting tools, the .bat gets further into it than the actual, updated GUI, rebooting the phone, whereas the gui fails at the start as it cant start abd nor daemon.
For starters, please update with:
Your variant (model number)
Current Android software version
Which one-click root tool you are trying to use
The output from 'adb devices' entered into ADB