• Login:

Welcome to the Toshiba Thrive Forum.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.

Page 1 of 4 123 ... LastLast
Results 1 to 10 of 40
Like Tree19Likes

Thread: Got ADB working...

  1. #1
    Thrive Tech
    Member #
    98
    Join Date
    Jun 2011
    Location
    IL, USA
    Posts
    1,861
    Liked
    404 times

    Got ADB working...

    Contrary to what may have been rumored before, ADB does work post OTA. I have my Win 7 x64 notebook recognizing the Thrive and can issue many of the basic ADB commands with a successful reponse. Executing "ADB devices" responds as expected by listing the device ID. I was able to pull / push files to / from the device as well as enter the shell command prompt. My Thrive was updated and was running on latest OTA that was pushed out July 7th before attempting the below.

    There's probably a less nuclear option but...

    Any uninstallation of anything is entirely optional and may be potentially unecessary in your case

    I uninstalled any other Samsung / HTC / Motorola, etc software for ADB management / syncing or similar.

    I then uninstalled the SDK, re-installed it with the latest API Level (12) and the latest Google USB driver (4).

    After that, I followed these instructions: Enable ADB USB Drivers for Nvidia Tegra based Android Tablets

    While it doesn't say to do so, I selected "ADB Composite Device" from the 3 choices I was given and it worked!

    This means it's open season for me to develop what I want on this device now. It also means that Toshiba has not blocked ADB or tried to make it a closed device aside the from typical locked bootloader. While more information on how to get it working via ADB would have been appreciated, it actually wasn't terribly dissimilar from how to get the HC Tegra 2 tablets to do the same. So, I really deserve no credit for this.
    Last edited by epakrat75; 07-17-2011 at 12:50 PM.
    revco, drum747, batfish and 9 others like this.

  2. Ads


  3. #2
    Thrive Pursuant
    Member #
    76
    Join Date
    Jun 2011
    Location
    Missoula, MT
    Posts
    686
    Liked
    263 times
    Nice! I was a little dubious when it was reported that the OTA update disabled ADB access entirely...that just seemed like an extraordinary effort to try & keep us out. Thanks for your attention to this...hopefully we can figure something out as far as the bootloader goes, but that's way beyond my abilities and I just don't have time to learn.

  4. #3
    Thrive Conveyor
    Member #
    77
    Join Date
    Jun 2011
    Location
    Socal for now, Oregon later
    Posts
    466
    Liked
    148 times
    Nice! Im glad to hear this. Thanks for the update!

  5. #4
    Thrive Pursuant
    Member #
    27
    Join Date
    Jun 2011
    Location
    NC
    Posts
    603
    Liked
    69 times
    Great work. Seems it's only a matter of time until we have root.

  6. #5
    Thrive Conveyor
    Member #
    199
    Join Date
    Jul 2011
    Location
    Ga, USA
    Posts
    374
    Liked
    61 times
    Thank god

  7. #6
    Thrive Conveyor
    Member #
    199
    Join Date
    Jul 2011
    Location
    Ga, USA
    Posts
    374
    Liked
    61 times
    Well I still can't get it working but on XP you don't have the option to choose ADB composite interface, I'll wait till I get home to try it on my Windows 7 computer.

  8. #7
    Thrive Conveyor
    Member #
    199
    Join Date
    Jul 2011
    Location
    Ga, USA
    Posts
    374
    Liked
    61 times
    Uh... I chose Android Sooner Composite Device as my driver and the ADB shell can see the thrive when it is booted up but not when it is in fastboot mode so no attempt to unlock until I can get it to recognize

  9. #8
    Thrive Informant
    Member #
    223
    Join Date
    Jul 2011
    Posts
    66
    Liked
    11 times
    Dumb question. We have Recovery built in, why not just create a Update.zip with su and the other utilities needed, put it on a SD, get into Recovery and flash the update? I tried moving su off another phone but lost the rwsrwxrwx's s bit when I did so. I would imagine a update.zip wouldn't have this issue.

    Told you it was a dumb question.

  10. #9
    Thrive Conveyor
    Member #
    199
    Join Date
    Jul 2011
    Location
    Ga, USA
    Posts
    374
    Liked
    61 times
    Our Bootloader can't be unlocked as easily as Xoom apparently.

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.


    C:\Users\Nate>fastboot oem unlock
    ...
    FAILED (remote: (00120000))
    finished. total time: 0.001s

  11. #10
    Thrive Tech
    Member #
    98
    Join Date
    Jun 2011
    Location
    IL, USA
    Posts
    1,861
    Liked
    404 times
    Great job, Tribute! Glad to see you got fastboot working. ADB too, I assume? That's the same result I got. Once the bootloader is unlocked, the rest of the path to being rooted should be easier for you.


 
Page 1 of 4 123 ... LastLast


Remove Ads

Ads

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Search tags for this page

(remote: (00120000))
,

adb drivers for toshiba thrive

,
adb toshiba thrive
,
at100 adb driver
,

failed (remote: (00120000))

,
failed (remote: oem unlock failed!)
,
failed remote 00120000
,
fastboot failed (remote: (00120000))
,
remote 00120000
,

toshiba at100 adb driver

,
toshiba at100 adb drivers
,

toshiba thrive adb

,

toshiba thrive adb driver

,
toshiba thrive adb drivers
,
toshiba thrive at100 adb
Click on a term to search our site for related topics.