Re: Hisense Pulse Root For Dummies by Yellowmann
Posted: Wed Apr 02, 2014 8:19 pm
I can't get ADT to talk to my device.
My HiSense Pulse just arrived. It has firmware version 3.2. It did ask if I wanted to take the update and I refused. Looking at the Network settings, it shows the assigned IP as 192.168.1.7/24 (I have no idea what the /24 means, but my router also shows 192.168.1.7 assigned to the same Wi-Fi MAC address as shown on the Pulse).
When I go into the platform-tools folder and type in: "adb connect 192.168.1.7" I get back "unable to connect to 192.168.1.7:5555"
I've tried pinging the IP and it works great. I tried connecting an ether cable and deleting the wi-fi password. The ether info showed up on the Pulse and in my router setup. It pinged great, but adb is unable to connect.
I tried using the adb kill-server followed by adb start-server. I get the message:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
I tried typing "adb connect 192.168.1.7:5037" I got back "unable to connect to 192.168.1.7:5037:5037"
I'm not sure what I'm doing wrong, but I can't seem to get the pulse talking to adb. It'll ping just fine, though, and my router knows it's out there. Things work great as long as I don't want to root.....but I do want to root!!!!
Please help.
My HiSense Pulse just arrived. It has firmware version 3.2. It did ask if I wanted to take the update and I refused. Looking at the Network settings, it shows the assigned IP as 192.168.1.7/24 (I have no idea what the /24 means, but my router also shows 192.168.1.7 assigned to the same Wi-Fi MAC address as shown on the Pulse).
When I go into the platform-tools folder and type in: "adb connect 192.168.1.7" I get back "unable to connect to 192.168.1.7:5555"
I've tried pinging the IP and it works great. I tried connecting an ether cable and deleting the wi-fi password. The ether info showed up on the Pulse and in my router setup. It pinged great, but adb is unable to connect.
I tried using the adb kill-server followed by adb start-server. I get the message:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
I tried typing "adb connect 192.168.1.7:5037" I got back "unable to connect to 192.168.1.7:5037:5037"
I'm not sure what I'm doing wrong, but I can't seem to get the pulse talking to adb. It'll ping just fine, though, and my router knows it's out there. Things work great as long as I don't want to root.....but I do want to root!!!!
Please help.