Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

NextBook 7P S (Resistive Screen) Ice Cream Sandwich - STOCK ROM

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    The Next7s and the Next7 Premium s are the same tablet.

    Sent from my Next7S using Tapatalk 2

    Comment


      #32
      abd devices command shows empty list

      Originally posted by MaxMagic View Post
      I am about ready to give up on the ADB driver for this device (next 7s resistive screen). I have already rooted the device with Bob's rom. It works fine and I have had no problems with it. Item 1 of Bob's reply obviously works since I was able to flash the device. As I mentioned in a previous post, Item 3 is also showing the next 7s as disk drives...... But Item 2, adb enabled mode??????? I have followed the link that Bob posted (oh.. about 30 times.) and I still cannot get adb to recognize that the device exists. I have also loaded, removed and reloaded android sdk nearly 10 times. What could I possibly be doing wrong? I'm sure it is something simple but after 5 days, I still cannot figure it out. I know it can be done because I see many people have been able to do it. Any last ideas before I give up completely?

      Thanks
      I just spent 4 weeks trying to get abd to recognize my Next7s. I finally got it.
      At command prompt in platform-tools, enter the following commands:

      abd kill-server

      abd start-server

      abd devices

      My device showed up, which means all the other abd commands should work. Almost all the procedures I have found on the internet don't mention kill and start server. They go straight to abd devices, which gives an empty list. I must have tried it 100 times with 30 different drivers.

      isitmondayyet

      Comment


        #33
        Originally posted by isitmondayyet View Post
        I just spent 4 weeks trying to get abd to recognize my Next7s. I finally got it.
        At command prompt in platform-tools, enter the following commands:

        abd kill-server

        abd start-server

        abd devices

        My device showed up, which means all the other abd commands should work. Almost all the procedures I have found on the internet don't mention kill and start server. They go straight to abd devices, which gives an empty list. I must have tried it 100 times with 30 different drivers.

        isitmondayyet

        isitmondayyet,

        Yup! You are correct, I was able to figure it out myself a few months ago. Thanks for your reply though.

        Max
        Max

        Comment

        Working...
        X