Ok - it was all going good, then something went wrong. Can you repeat the steps, but don't do sh /tmp/pulse_root.sh. Instead, please do "busybox md5sum /tmp/pulse_root.sh" and reply back with what it says (should be a md5 hash).helousn wrote:cj_000 wrote:helousn wrote:Any chance of a walkthru for us noobs to root the pulse? I've used three different adb's and can adb connect thru the lan to the ip address of the pulse but the next step of adb root gives a device not found error. Even thought the adb connect show connection on port 5555, the adb devices command show nothing.
Thanks!
On the pulse, go to All Applications, Settings, then Applications. Hit development. Check off "Enable Remote Debugging", a message will pop up saying "your files can be modified", press ok.
Then, go to the option below that, says "Remote Debugger IP", go back, and enter your PC's local IP address, then try to re-connect with adb!
Thanks! Definitely closer.. but still not there yet..
N:\adt-bundle-windows-x86_64\adt-bundle-windows-x86_64\sdk\platform-tools>adb connect 192.168.2.11
connected to 192.168.2.11:5555
N:\adt-bundle-windows-x86_64\adt-bundle-windows-x86_64\sdk\platform-tools>adb root
restarting adbd as root
N:\adt-bundle-windows-x86_64\adt-bundle-windows-x86_64\sdk\platform-tools>adb connect 192.168.2.11
connected to 192.168.2.11:5555
N:\adt-bundle-windows-x86_64\adt-bundle-windows-x86_64\sdk\platform-tools>adb push pulse_root.sh /tmp/pulse_root.sh
382 KB/s (1177929 bytes in 3.010s)
So I'm sure I'm missing something but for the life of me I don't know what it is... I redownloaded the pulse_root.sh file but no difference..
Any hints would be great!
Thanks!