Awesome, and you should clarify when you add that to the OP that to access manual input click launch under advanced utilities, it took me a minute before i looked there for it and most using the tool arent familiar with it to know that. I will uninstall the drivers that are sucessfuly working and see if the auto driver install works when using the cmd line. So you are saying just auto install but dont trust the adb check failing and when run manually you suspect it will find the device just fine?Haha. Then that is the solution. Wow. It is always the little things.
Ok. Let me explain.
So, when you start adb for the first time, it goes through all of that starting daemon blah blah...
Well my toolkit is running string checks on the output, but its looking for patterns it doesn't recognize because the first time your run it, it outputting that daemon stuff. That is why its getting stalled.
The solution: Simple. To run adb start-server in the background when you start the toolkit. That's it.
For now. Everyone who is having stalling problems. Please restart the toolkit. Open manual input, and type adb start-server
Then proceed to use the tools. I bet it works with the autodrivers that weren't working before for some people.
{{ WugFresh }}
Great news bro congrats!!!! Love seeing success through community effort and teamwork, and i love that its the little thingsI just tried :-
pluged in nexus
In the toolkit opened the manual input and type adb start-server
then went to Step 4 Tab- List All ADB devices
And it worked!
Upuntil now listing the adb devices always threw up two adb.exe's
Progress Im sure - I wish I knew what it meant
I just tried :-
pluged in nexus
In the toolkit opened the manual input and type adb start-server
then went to Step 4 Tab- List All ADB devices
And it worked!
Upuntil now listing the adb devices always threw up two adb.exe's
Progress Im sure - I wish I knew what it meant
adb start-server
I'm unlocked & rooted using this program, but I think the permanent CWM flash may have failed. After rebooting after root (verified through installation of ROM mgr), I tried to use the instructions in this post (p.25 this thread) to flash the new CWM. It didn't look like it failed, so I used ROM mgr to reboot to recovery, & I got the image of the dead alien w/the red exclamation point.
Then I held in power & up-volume, & saw the stock recovery instructions to reboot. What step do I need to take next?
Hey WugFresh - yeah, tried that 3x now w/the same result. Should I maybe try flashing the CWM included w/ROM Mgr first?
adb start-server
Victory is mine, successful ADB check using the auto install driversI know exactly what it means. Not just progress. A solution. Totally an oversight by me. But now my mind is at peace. Now I would really like people with 64bit machines to just use the auto-installed drivers and see if it still works using the
Code:adb start-sever
Solution.
{{ WugFresh }}
I know exactly what it means. Not just progress. A solution. Totally an oversight by me. But now my mind is at peace. Now I would really like people with 64bit machines to just use the auto-installed drivers and see if it still works using the
Code:adb start-sever
Solution.
{{ WugFresh }}
Hey WugFresh - yeah, tried that 3x now w/the same result. Should I maybe try flashing the CWM included w/ROM Mgr first?
Yep, SDK is installed. I saw you found the solution, but still wanted to reply.Just a hunch. For all of you who are saying that the toolkit is spawning two instances of adb for you; do you have the SDK installed on your machine?
My guess is that adb is added to your systems path variable and although my program is pointing to the local file, the globally accessible adb gets spawned as well causing the problem.
This is just a guess by the way, but if it were true, the solution would be for me to rename adb and fastboot to adb-wug.exe, and fastboot-wug.exe.
To confirm whether or not my theory is correct, temporarily rename adb.exe in your sdk folder.
This makes way more sense than drivers. Why would drivers have anything to do with the toolkit spawning two processes. My guess is that the they are fixing it because it allows the first instance to get resolved more quickly, before you get hung up.
{{ WugFresh }}
I ran into this same exact problem when I tried to flash TWRP. I ended up using the Root & CWM feature on this tool to flash CWM over the bad recovery flash.I'm unlocked & rooted using this program, but I think the permanent CWM flash may have failed. After rebooting after root (verified through installation of ROM mgr), I tried to use the instructions in this post (p.25 this thread) to flash the new CWM. It didn't look like it failed, so I used ROM mgr to reboot to recovery, & I got the image of the dead alien w/the red exclamation point.
Then I held in power & up-volume, & saw the stock recovery instructions to reboot. What step do I need to take next?
Check it out yourself! That shouldnt sound negative, its a ringing endorsement of one of IMO the best features of this tool, everything you may click comes up with a little info bulletin further outline the process that lies ahead, its safe to explore to a satisfying degree without having a device plugged in, and if you need it plugged in you can almost always just unplug while its rebooting before any processes have completed though thats unadvisable. Normally we have to worry about knowing what the next step is before we even click to be sure we are prepared for all the possibilities but this tool remains powerful yet simple enough with clarification at each step, the little clarifications are my favorite feature. Anyway when you click and then click ok to start another window comes up asking you if you have your own source locally or if you want to downlaod the stock 4.1 for the asus tablet.
Capture
I think the stock rom messes with the bootloader so you might want to try searching for - recovery-from-boot.p
Thanks for the confirmation, I'm at work, didn't want to install the toolkit on this PC, would prefer to play with it at home. But since the "official" CWM recovery is available in Rom Manager, I wanted to try it out, but wanted to verify I could revert if need be before doing so
Working on it now. Been really busy though with another project though; https://capsules.io/ks.html
I will try my best to get the toolkit updated asap in my limited free time. There are some other changes/updates I need to integrate as well, but not too many. Cheers.
{{ WugFresh }}