|
I had similar frustrations with the process today. I ended up rooted after many hours of trying the same things over and over. While it was annoying to get the initial ADB up and running that was hardly the problem. After running ratc.bin ADB was never running despite trying over and over again. Sometimes I could get another ADB $ prompt if I kept trying the web page (over and over).
Finally I saw the # prompt but I was disconnected almost instantly. That is when I realized it was allowing an ADB connection for only a few seconds, I had to connect and then send the push command within a few second time span. There was no time to run the command adb shell to see the # and I had the push command pretyped in another window just waiting. Either the push command would fail with a permissions problem (indicating that ADB was enabled without root and would persist so ratc.bin could be run again) or I would get root access for less than five seconds. There was no chance to look and see, just try the push command the moment you obtain a connection. I must have had 1000 failed adb connections while loading the web page over and over (after of course having run ratc.bin). Rebooting will force you to start the whole process over again as ratc.bin seems to be deleted during the boot sequence.
Hope this helps.
|