hi New user - Sony Tablet S

hi New user - Sony Tablet S

hi just got my new tablet to day and Id like a bit of info as I dont what to brick it already
im from uk it came with honneycomb 3.2 all ready installed kernal 2.6.36.3 build10 #1 can it still be rooted as I wana play modern combat 3
thanks

As far as I know it can. Have a look in the development section. Probably better to wait until ics is released and then root.

you've got a build 10 kernel so your device is not rootable right now you have to wait for ICS or if some devs make it rootable for your kernel version
10# and above is not rootable
Maby it is possible already but just like Vinny1967 says just have a look in the development section
Landgenoot

rickwyatt said:
hi just got my new tablet to day and Id like a bit of info as I dont what to brick it already
im from uk it came with honneycomb 3.2 all ready installed kernal 2.6.36.3 build10 #1 can it still be rooted as I wana play modern combat 3
thanks
Click to expand...
Click to collapse
try to check for OTA update - if you've got 3.2, then probably you will get 3.2.1 with vulnerable kernel.
br
condi

ah yeah missread that one xD lol

It's okay no need to root a mo as I can play modern combat 3 and sims freeplay sweet

Dose upgrading wipe the tablet

No
Sent from my iPhone using Tapatalk

ived upgraded and now have build 8 kernal but for some resion I cant get my xp to see the tablet in developer mode adb

rickwyatt said:
ived upgraded and now have build 8 kernal but for some resion I cant get my xp to see the tablet in developer mode adb
Click to expand...
Click to collapse
Did you echo'd something
Did you ad the driver text from Sony tablet s / p in the google/extras etc.
Or are you unprepared
Edit » lol your more prepared then me i see xD tought you where a newbi xD

I'm just a newbie with the Sony s and I have plenty of experience with Android but for some reason when I plug it into xp it only see it as sony tablet and if I try and install the adb drivers from the auto install folder it say this driver doesn't contain information about my device

rickwyatt said:
I'm just a newbie with the Sony s and I have plenty of experience with Android but for some reason when I plug it into xp it only see it as sony tablet and if I try and install the adb drivers from the auto install folder it say this driver doesn't contain information about my device
Click to expand...
Click to collapse
Do you have USB debugging on?
Your device is not listed after adb devices?
Try
adb kill-server
adb start-server
adb devices
But I think you already know that
And if that didn't work than the next thing you could check if you have not already done that to check if you have your driver installed proper
1.You have Android SDK installed Make sure you have downloaded the Google USB Driver Package.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;SONY Sony Tablet P
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_04D2&MI_01
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Userprofile isn't by your Program Files ! Another example C:\Users\Mahaco\.android etc.
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and confirm again that ‘USB Debugging’ is enabled.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, just ignore that.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Browse Files’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, also just ignore, choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands again:
Quick launch > Start button + R then type CMD and push enter and cd to your working folder
( For example: C:\Program Files (x86)\Android\android-sdk\platform-tools\ )
cd.. [Enter] < type that until you only have your harddiskdrive shown.
cd program files (x86) [Enter]
cd Android [Enter] etc.
adb kill-server
adb start-server
adb devices
Boot Tablet S into recovery:
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives you the MTP device driver.

Could someone uploaded a zip up drivers and all that need to get sony s in adb
Thanks

rickwyatt said:
Could someone uploaded a zip up drivers and all that need to get sony s in adb
Thanks
Click to expand...
Click to collapse
I can't just copy my winusb.inf because if you replace it you will loose other drivers, so this is 'the' correct way to do it,
Edit> And you are working on a Windows XP system which can give allot more issue's if you do, after I tought about it I don't know if everything will be compitable in Windows XP so that would be something you need to find out. and if someone can confirm if it can!
I hope I helped, and hope that I didn't tell you anything you already knew, and on top of that respect my not always that smooth English lol
Like condi always says Br.
Mahaco.

rickwyatt said:
ived upgraded and now have build 8 kernal but for some resion I cant get my xp to see the tablet in developer mode adb
Click to expand...
Click to collapse
If you manage to get it to work, let me know. Ive had issues since day 1, and sony are absolutely useless. After numerous phone calls with them, they told me to contact Android about the issue

confuserr said:
If you manage to get it to work, let me know. Ive had issues since day 1, and sony are absolutely useless. After numerous phone calls with them, they told me to contact Android about the issue
Click to expand...
Click to collapse
I get your point but Sony would rather see their customers not to change their devices unless it is something official,
Android -> Google : Has made it like this that everyone with a little knowlege can add their toughts by making their own roms which is very smart because all the problems that will be solved bij non official developers can be used in next firmwares, and that just for free the fact is, if you brick your device it will loose warranty. if you have root access your warranty is also not more then a piece of paper,
Samsung Galaxy S2 shows up an /!\ Warning sign at start up if its rooted, because if you will brick the phone Samsung could easily see if it was bricked by the user, so I understand the reaction from Sony,
No hard feelings, but I just think that this is how it is
I can only recommend you an upgrade to a newer Windows version to either
Windows Vista or Windows 7 because I can confirm that these are compitable if you follow all the steps for rooting (Drivers etc.)

Mahaco said:
I get your point but Sony would rather see their customers not to change their devices unless it is something official,
Android -> Google : Has made it like this that everyone with a little knowlege can add their toughts by making their own roms which is very smart because all the problems that will be solved bij non official developers can be used in next firmwares, and that just for free the fact is, if you brick your device it will loose warranty. if you have root access your warranty is also not more then a piece of paper,
Samsung Galaxy S2 shows up an /!\ Warning sign at start up if its rooted, because if you will brick the phone Samsung could easily see if it was bricked by the user, so I understand the reaction from Sony,
No hard feelings, but I just think that this is how it is
I can only recommend you an upgrade to a newer Windows version to either
Windows Vista or Windows 7 because I can confirm that these are compitable if you follow all the steps for rooting (Drivers etc.)
Click to expand...
Click to collapse
I am on Windows 7 and am a Java developer, didn't want ADB for rooting, want it for testing my apps. No offence but I have already had this conversation with Sony, hopefully the ICS update will make a difference. What would really help is if they just released official drivers like they do for their phones.

confuserr said:
I am on Windows 7 and am a Java developer, didn't want ADB for rooting, want it for testing my apps. No offence but I have already had this conversation with Sony, hopefully the ICS update will make a difference. What would really help is if they just released official drivers like they do for their phones.
Click to expand...
Click to collapse
Yeah must admit that.

Related

Installing ADB USB driver for HTC Hero on Windows 7

Hi,
I recently bought my first Android phone, an HTC Hero, from a helpful eBayer here in the UK. When I got the phone, it had already been rooted and had a custom ROM, v4 RC1 of EzHero, installed.
I want to update this custom ROM to v5.1, because there are some problems with the current version that's installed. (For example, the phone doesn't ring because there are no ringtones installed! Also, the camera doesn't work, and the phone crashed and rebooted whilst I was in the middle of a call last night.)
So, after some reading around on these forums, I tried following the instructions on this thread: http://cleanimport.xda/index.php?threads/709220/. The basic first step is to download the SDK from Google and instruct it to download the USB driver. So far so good. (I am using Windows 7 BTW.)
However, I have been unable to get the USB driver installed correctly, such that when I run the command:
Code:
adb devices
I get nothing back. (Not strictly true -- the first time I ran it it said it was starting a daemon, then said something like "devices list", but listed no devices. The second time I ran it, it didn't mention the daemon, but still didn't list my device.)
When I connect the phone to my computer (via USB, and with USB debugging enabled), I basically get a balloon at the bottom right of the screen to say that it is installing drivers, and then it says it had some problems. It lists out several devices, each with a green tick or a red cross against them. Invariably, one of the devices listed is called simply "ADB", and it always has a red cross against it. I am not specifically prompted to point the system towards any drivers for the device.
If I go into Device Manager, I currently see, under "Other devices", three devices:
- ADB
- Multimedia Controller
- Multimedia Video Controller.
The icon for each of these has a little yellow exclamation mark. If I double-click on ADB, I am given the chance to Update driver. Doing this gives me two options, and I choose "Browse my computer for driver software". This prompts me to "search for driver in this location" and I choose "C:\android-sdk-windows\usb_driver". (I have also tried pointing it to the subfolder "i386", but this gives the same result. I am on a 32-bit Intel system.) There is also a checkbox "Include subfolders", again I have tried both options, and both lead to the same outcome.
I then click Next and receive this error message:
Windows was unable to install your ADB
Windows could not find driver software for your device.
[...]
Click to expand...
Click to collapse
If, instead of clicking Next, I click "Let me pick from a list of device drivers on my computer" and then select "Mobile devices" and click Next, I am presented with a blank list and a button reading "Have Disk". Clicking on this lets me browse, this time, for an .inf file. But selecting the android_winusb.inf file gives the following error message:
---------------------------
Select Device
---------------------------
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a
driver, make sure it is designed to work with Windows for 32-bit systems.
---------------------------
OK
---------------------------
Click to expand...
Click to collapse
This is about as far as I have got! I have tried experimenting with a couple of things, but with ultimately the same result:
Running (as administrator) USBDEview and uninstalling anything that starts with HTC, or ADB, or Android, or USB Mass Storage device
Editing the .inf file using the modifications described below:
The first modification I tried is described in comment 44 of issue 1039 on the Android Google Code forum (link removed because I don't have permission to post external links!):
Code:
;HTC Hero
%USB\VID_0BB4&PID_0FFE.DeviceDescRelease%=androidusb.Dev, USB\Vid_0bb4&Pid_0ffe&Rev_0100
You can find / adapt those description with your material manager (look in advanced tabs)
To have a nice name of device, add at the end of file something like
USB\VID_0BB4&PID_0FFE.DeviceDescRelease="HTC Hero rev 0100"
The second modification I tried is described in comment 99:
Code:
[Google.NTx86]
; HTC Hero
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
And the third is described in post 2 of a recent Android Developers Google
Groups thread entitled "cannot install USB drivers for HTC Slide, Android 2.1, Windows Vista 32 bit" (link removed because I am not allowed to post external links!). For this one, I consulted the information displayed when I go into Device Manager > ADB > Properties > Details > Hardware Ids, so the actual lines I added to the .inf file are as follows:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&REV_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
I also tried a slight twist on this:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
since all the other devices in the .inf file didn't include the &REV_0100&MI_01 parameters for the %SingleAdbInterface% line.
Finally, I also tried various times to uninstall devices from Device Manager, e.g. ADB, the two multimedia controllers with exclamation marks against them, and USB Mass Storage Device (which does indeed have three lines on the Properties > Details > Compatible Ids screen, as advised by a blog post I found on the Android Simplicity blog entitled "How-To #0: How to Install Usb Driver on Your Computer" (link removed because I do not have permission to post external links!).)
I really can't think of much more to try, so would really appreciate any pointers, however small, from the experts!
Another option might be to give up on Windows and try doing the whole process under Ubuntu Linux, which I have installed under dual-boot. However, the instructions for updating ROMs/making backups/recovery/etc. appeared to rely on some Windows executables so I figured that could be a risky approach (especially given I know very little about how to work Linux...!).
Thanks for reading
Michael

Don't need them. Get the latest HTC Sync and install the My HTC driver and adb will work.

Thanks for such a quick reply btdag!
Really? That would certainly make things a lot easier, however dreamersipaq does make a point of reinforcing how important it is not to have HTC Sync installed in his instructions:
At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done)
Click to expand...
Click to collapse
[...]
HTC Sync does not like to play nice with the reflash tool
Click to expand...
Click to collapse
[...]
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it)
Click to expand...
Click to collapse
Does this not matter after all?

To get adb working I just installed the latest HTC Sync and drivers and then added ;C:\Path\To\SDK\Tools to my Windows Environment Variables as described in this guide:
http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735&sid=d1d70142a6264965b8c370bf1afa64d0
no problems with adb since

As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!

Thanks for all the help.
I'm pleased to say I've now managed to install the update, and my phone is now ringing!
In the end I worked out that I did not in fact need ADB at all. Since the phone had already been rooted and had a custom ROM installed, it dawned on me that it must already have the requisite recovery image installed. And indeed it did. So all I had to do was install Titanium Backup, back up my apps and settings, also take a nandroid backup just to be on the safe side, and then factory reset/wipe and install the update. (And then restore apps and settings using Titanium Backup.) Problem solved!
As an aside, I think there is certainly scope for more 'newbie' documentation. (Or would this be on the Wiki, currently down?) I'm certainly very grateful to those who have taken the trouble to set out what they have learnt already, for the benefit of others. For example though, even after spending several hours searching and reading up all the newbie guides I could find, I still had to read between the lines quite a lot to work out what a 'radio' was, what purpose the recovery image serves, how ADB fits into the whole picture, why there are multiple custom ROMs available for the same version of Android and how to choose one, etc. Perhaps one day I will be advanced enough to attempt that myself!

CyberWalrus said:
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
Click to expand...
Click to collapse
Thank you very much! I was reading this trying to get my G1 to work and it did. Windows 7 x64 won't allow me to install the android_winusb.inf driver but droid explorer did.

Phone nor computer will recognize adb/usb
First of all, my is rooted but somehow the superuser.apk file is missing. When trying to activate wifi tethering it asks if the device is rooted. The answer is, yes! I can boot into recovery mode but I do not have a way to get the superuser to open without adb. Can anyone help me?

Unable to Instal ADB Drivers
I'm having similar issues trying to root my MyTouch 4G. I've been following steps on the cyanogen wiki website for this device, which refers you to their site's instructions for setting up SDK & ADB drivers.
I've downloaded the SDK zip file, extracted to the C drive and made sure file paths are all the same as per the instructions. When following the instructions under Windows, I've added to variable values ;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools (and double checked these folders on C drive to be sure they're accurate).
When trying to manually update device drivers for ADB, I select the file android_winusb.inf and get error: "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
My device has USB debugging enabled and is in mass storage mode (I've read on other forums that this can fix).
Not really sure what else to try? Any way I can change the .inf file to make Windows recognize it? Running Windows Vista 64.

My quest to root my Vizio VTAB108 Tablet and how I enabled ADB access

I am new to the Android platform so please excuse any silliness on my part…
Below are the steps I took to successfully allow my Vizio Tablet (VTAB108) to connect via USB using the generic Google ADB driver as Vizio does not include ADB access for the tablet.
History:
I am trying to Root my tablet and from what I read throughout the forum, the easiest steps to root a tablet is using the SuperOneClick method.
Since SuperOneClick requires ADB access and the Vizio does not include the ADB driver (and the generic Google) do not work out of the box I was at a loss to how I would run SuperOne Click.
This article are the steps I took to get ADB access working with Windows 7 x64 and the Vizio Tablet.
I am hoping my steps here can further lead to root access for this tablet.
As an FYI, I was still unsuccessful in getting SuperOneclick to completely run after following these steps, but maybe someone has an alternate method of rooting now that ADB access is available? /me crosses fingers
It would stop at Step #6 at which time I would disconnect and reconnect the tablet. It would contine to step #8 but then finally fail. If anyone has an alternative to SuperOneClick, I would gladly try it.
IMPORTANT:
The instructions below assume you have already put your Tablet into USB debugging mode.
The instructions below assume you are running Windows 7 x64. If you are running x32 versions of your OS, modify the below settings as apporopriate for your OS[/B].
1. Download and install the Google Android SDK.
(Being this is my first post, I cannot post a URL so google the following topic exactly and click the first link):
what-is-adb-and-how-to-install-it-android
2. When you get to the USB driver install you will have to manually modify your android_winusb.inf settings file to allow Windows to recognize your Vizio Tablet using the generic Google ADB-USB driver.
3. Find the "usb_driver" folder in your sdk directory. (Mine was: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver).
4. Right-click "android_winusb.inf" and open it with notepad or your favorite text editor.
Under the [Google.NTamd64] section, paste the following:
Code:
;Vizio Tablet
%SingleAdbInterface% = USB_Install, USB\VID_0489&PID_E040&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0489&PID_E040&REV_0227&MI_01
then, open a command prompt and type the following:
Code:
echo 0x489 >> "%USERPROFILE%\.android\adb_usb.ini"
5. Right-Click the unknown device in Windows Device Manager (Under Other devices) and manually install the driver for your Tablet.
NOTE: Originally my tablet connected to the computer and installed the regular Windows 7 Mass Storage driver. I had to remove this driver before I could see the device listed under "Other Devices". Follow these instructions if you need to remove your generic Mass Storage driver:
Code:
A. Unplug all removable devices (USB drives, Thumb Drives, SD Cards, Etc...) but leave the Android phone plugged in.
B. Open Windows Device Manager.
C. Select "Universal Serial Bus Controllers"
D. Select USB Mass Storage Device.
IMPORTANT: Click on the details tab and select "Compatible Ids" under the Property drop-down. You should see three items listed under Value. If not, you are looking at the wrong Mass Storage Controller.
E. Select Uninstall Driver
F. Close the window.
G. Right-Click your computer name at the top of device manager and select "Scan for Hardware Changes".
H. Your new "Android Phone USB device" with a Yellow Exlamation mark! will appear under Other Devices.
I. Click on the "Android Phone USB device"
J. Select "Update driver software"
J. Select "Browse my computer for driver doftware"
K. Browse for the location that you have unzipped the android_usb_windows ( Mine is: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver )
6. Now test to make sure you can access your device in USB Debug mode:
Type the following from a command prompt:
adb kill-server
adb devices
You should see your device serial number at the command prompt and in Windows Device Manager if everything worked.

drivers
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?

USB Drivers Not Installing
[email protected] said:
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
Click to expand...
Click to collapse
I grabbed those drivers a couple of days ago and could not get Win7 or WinXP to install them with the vtab1008.
I can use adb to interface with the vtab008 (using Linux and Win7), but GingerBreak and SimpleOneClick (which uses GingerBreak) are unable to root the vtab1008.

I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.

Agreed
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
This is my thinking EXACTLY!

[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
Yes, I agree. If there's no root, the tablet is not worth it.

The drivers worked for me.

I downloaded the drivers from the Vizio site and when I plugged the VTAB into my computer I manually installed the driver. I just used adb to grab a bunch of screenshots.

OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.

You can get to recovery mode by holding down both volume buttons and the power button. Details

I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark

Mark0266 said:
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Click to expand...
Click to collapse
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.

marvin02 said:
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
Click to expand...
Click to collapse
Thats the problem the prompt never comes up. Running Windows 7

Well I got the driver for adb to install but it still will not show up when I do adb devices

Bootloader?
the.joeba said:
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
Click to expand...
Click to collapse
Did you actually get into the bootloader? adb reboot bootloader simply reboots the device for me.

So whats with gingerbreak? No love with it? I thought this thing was rooted already prior to shipping? Hmmm. My bro just ordered one for me and I am curious about getting it rooted. Lets get this thing rooted and overclocked and get it some love. Also, whats the word on honeycomb on this beast? anything?....

Mark0266 said:
Well I got the driver for adb to install but it still will not show up when I do adb devices
Click to expand...
Click to collapse
Same here.

Rooting help
I have some coding knowledge, but have never worked on rooting a device. I did not pay for mine, so if anyone has references to some info I can look at about obtaining root then I will work on mine without fear of bricking it.

I have been at this for weeks, to no avail.. tried changing params in Gingerbreak, tried running it under every condition possible, and the only thing I haven't tried is changing how GingerBreak is using the /sdcard/ mount point, as that's where the internal memory is mounted to.. It's a pretty odd move to make, and I don't like having my true sdcard in /sdcard/external. what a crock :/

This tablet has to have a way to be rooted, I tried an older version of gingerbreak 1.1 just kept running, never failed, but didn't root the tablet just kept running, like it was gonna root the tablet, kinda weird, I do know that the bootloader is not locked down, my wife works for vizio, the company gave there employees a tablet for free

ADB now working Windows 7 64 Bit SOLVED GUIDE

Thanks to a good link from Vanto to read here is the instructions as to how I got it to work,
This solved it for Winblows 7 64 bit. For others having the same problem on Winblows 7 64 bit (should be the same for 32 bit miuns the X86 Directory)
1. Go into settings on the prime and make sure USB debugging has a check in it in under SYSTEM > Developer options > USB Debugging
2. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers. If you see at the top of device manager ASUS Android devices and when you expand it you see ASUS Android Composite ADB Interface you already have the ADB drivers installed and can skip down to #6
3. Go to ASUS website and download the USB drivers for the TF201. Download Vipermod Primetime 4.6 here for the ADB drivers http://goo.im/devs/viperboy/Prime/viperMOD_PrimeTime_v4.6.zip then extract the zip file to a normal file. You only need the drivers from the tool.
4. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers.
5. You should see the prime listed under portable devices. Uninstall the driver then update the driver manually. Browse to the folder you created from the Vipermod primetime zip. Make sure there is a check in check sub folders. Winblows should detect the drivers and then convert the prime to a ASUS Android Device.
6. Go into settings on the prime and make sure there is no check in Launch ASUS Sync under PERSONAL > Accounts & Sync > Launch ASUS Sync
7. Press Control, Shift, Escape at the same time and make sure there are no instances of ASUS Sync or Splashtop runnung in services in Winblows 7.
8. Download and Install the latest Android SDK. I installed all the libraries and such just to be on the safe side. http://developer.android.com/sdk/index.html
9. DISCONNECT YOUR PRIME FROM THE USB AND REBOOT YOUR PRIME AND YOUR WINBLOWS LAPTOP. After both devices reboot plug in your tablet into your Winblows laptop.
10. Navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools and click on the ADB file. A command prompt will open and spool up a bunch of stuff then close. All the stuff spooling I am assuming was the ADB server starting.
11. Hold down shift then right click inside platform-tools folder and select open command prompt here. You should be in a command prompt window showing the directory C:\Program Files (x86)\Android\android-sdk\platform-tools
12. type adb devices. You should see your primes serial number pop up.
13. make a test file in the platform-tools directory, i just used a simple text file to test then type:
adb push test.txt /sdcard/
It would be easier to just put the Rom you are going to flash in this directory so when it is time to push the rom it would be:
adb push nameofrom.zip /sdcard/
If SDCARD not recognized try:
adb push nameofrom.zip /system/media/
14. browse to your sdcard and you should see your file there. If you are already in the sdcard folder window on your prime, leave the folder then come back and it should be there.
15. You should be able to push files now after superwiping. You may need to push to /system/media/ if /sdcard/ is not found. Make sure you have all the / in the directory structure when pushing.
16. From inside recovery select install zip from sdcard and browse to the folder you pushed it to then flash away.
If anything seems incorrect or out of order please let me know so I can correct it. If this helps you congrats but if not I'm sorry. This is how I got it to work.

As you have stated that prior to your windows re-install, everything had worked, thus I highly doubt that this could be the issue... but just to double check, you do have usb debugging enabled, right?
If you can, connect your transformer prime, and try executing {install directory}/android/platform-tools/adb.exe -devices and let us know what kind of output you get.

Lostsorrow said:
OK looking for a little help here. I am planning on doing the Super mega wipe in the dev section however ADB has not recognized my prime. I wanted to verify I could push to it a test file before I did the wipe. Under device manager it shows the whole Asus ADB interface device and that the device is "working properly" I also have a listing down in portable media devices where it states Transformer TF201. I have disabled Asus sync and do not have splashtop. When I connect my prime I can explore the internal SD and copy files back and forth over USB. I have also installed and updated the latest Android SDK. I am at a total loss here. I recently did a fresh install of windows and beforehand it used to work. Any ideas or help would be greatly appreciated. Thanks in advance :cyclops:
Click to expand...
Click to collapse
make sure your adb files are the most updated once,
i had this problem before but thats just cause my adb was not updated

I recently battled with this and concluded that adb just doesn't work on Windows 64bit for the TFP. My advice, try to find an XP pc and do it through that. I posted in Prime_Full_Wipe thread in Dev section about this.
Wasted several hours trying to get adb to see the device. Tried so many device drivers.... Latest adb versions etc....
Sent from my EPAD using Tapatalk 2

tangiers said:
I recently battled with this and concluded that adb just doesn't work on Windows 64bit for the TFP. My advice, try to find an XP pc and do it through that. I posted in Prime_Full_Wipe thread in Dev section about this.
Wasted several hours trying to get adb to see the device. Tried so many device drivers.... Latest adb versions etc....
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
thats weird... im on window 7 64 bit and it works for me ;o

lil-devil said:
thats weird... im on window 7 64 bit and it works for me ;o
Click to expand...
Click to collapse
Mine did too when I unlocked but once I had a custom rom on it, it stopped working. I think the driver gets messed up by the custom rom making the pc see the TFP as something different to an Asus TFP.....
Sent from my EPAD using Tapatalk 2

http://forum.xda-developers.com/showthread.php?p=28021373 is my post or you can try read the whole thread, it helped me a lot
Just did my Full-Wipe part on a brand new Win7 Ultimate-SP1 x64 machine
Sent from my GT-I9000 using Tapatalk 2

unlocking phone from one network
hae guyz i have my htc s620 upgraded from dash have tried to generate network unlock code and for 3days of hard work and going through almst all threads nothing has been fruitful......i need someone who will help me generate unlock code...my pc is window 7 and my phones imei is 35155301530476202........i will be so greatful..email me the unlock code via [email protected]
waiting for u reply guyz

HKC p771a 7 inch Tablet Root

I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.

I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment Rockusb.rar
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon

New approach
Ok I cannot get the drivers to install on my computer. Window 7 seems to default to its own driver and will not let me install the rockusb drivers.
With that said, I have the system Update.img and was wandering if the img itself can be rooted and then updated to the tablet. If this is possible and anyone with the knowledge is willing I will upload it. Or if someone is really patient and would like to walk me through the process and I will attempt to do this myself

No Help
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.

tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
Can't tell your level of PC knowledge so if you already know this don't get offended. The .inf is editable and there are areas in there that allow manufacturers to prevent installation on some OS's to prevent conflicts. Make a system restore point or better yet a backup and then post the contents of the INF somewhere and point the folks here to it and they may be able to help you edit it to install. Regardless, you'll have to use the "have disk" option instead of letting windows search for a driver even if you get the edits right. And the usual disclaimers about me not being responsible for any issues with your equipment as a result of this are in effect.

tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
I was able to root using the instructions above although i don't think you need the rockusb drivers. You just need the usb drivers that come with the android sdk. I am on Win 7. Thanks for the above info for rooting.
I was able to install ROM manager and now proceeding to backup ROM and upgrade using this guide: cant post link as forum is preventing, but search for rom flash guide on androidpolice com.
Hope this helps.
Big thanks to this thread to get me going...!!!

?
could someone please, Barney style, Explain how I am supposed to select the android_winusb.inf because my steps are as follows. Right click on device p771a in device manager, browse my computer, let me pick from a list of device drivers, have disk, point to the google usb driver (C:/Android/android-sdk/extras/google/usb_driver) select the android_winusb.inf open. Hit ok, (The folder you specified doesn't contain a compatible software driver for you device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems). Hope this helps explain my troubles. Glad that my thread is helping others to root this device but it does not work for me.

Could it really be that simple?
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on

tannerjames said:
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
Click to expand...
Click to collapse
Glad you could figure it out...
I was not able to use the ROM Manager to backup the ROM since the device is not supported on this tool, but see below for how you can obtain the stock image.
I've tried to flash multiple different ROMs using RKAndroid to the tablet, spending days on this, with no success. The tool itself works great and I am able to flash the ROMs since it supports the RK29 chipset which I believe this tablet has. The stock ROM for this device is available from the manufacturers web site (the link is available when you go to Settings => About Device => System Update, hkcdigital dot com slash update slash update.img), if anyone would like to take the stock rom and upgrade it to Android 4.2/JB.
I was able to unpack/repack the stock image using the wendal image tools and modify / cook the ROM using Android kitchen method described elsewhere in this forum. Rockchip Batch Tool is another great utility to flash custom ROMs to this device. Also, If you put the ROM as update.zip or update.img file on the microSD card, the tablet will take it and flash the image as long as it is in the right format. Ofcourse you can put the tablet into recovery and restore from there as well. I've found that the stock image (update.img) has the following file/folder format when unpacked: /RK29xxLoader(L)_V2.27.bin, /package-file, /parameter, /recover-script, /update-script, /Image/boot.img, /Image/system.img, /Image/recovery.img and /Image/misc.img.
Is it possible to upgrade this tablet to Android 4.2 or atleast Jelly Bean? Would be very helpful if someone is able to do this. The most success I've had so far is with the custom ROM Oma_Odys_Loox_JB_4.1.1_v1.2.2a flashed using RKAndroid. It flashed the tablet fine, updated the boot etc. On tablet boot I am able to see the new logo, but then the it doesn't go anywhere from there. I think customizing this ROM or the stock ROM we should be able to get the new OS on to the HKC tablet. I've given up for now since I don't have the time to spend on this anymore. If someone is able to do this, please post the instructions or upload the custom ROM, as I am sure it will benefit a lot of people and will be much appreciated. Happy cooking!
Thanks!

jawadshaik- rom manager
If you have successfully flashed rom manager on this device could you post the steps you took to do so. What version? Manual flash? The program itself says there is no recovery for this device.

Sorry jumped the gun on that last post. Thanks for the info

What's the secret to keeping the battery from draining so quickly while it's idle? I just got this and see it drained about 40% in about 2 hours I think and I wasn't using it.
tannerjames said:
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
Click to expand...
Click to collapse

@jawadshaik
Just out of curiosity, when you were flashing that Rom that brought up the boot screen, did you do a wipe/factory reset from recovery mode before flashing? I have no idea if that would help or not, but most if not all roms require a data wipe before flashing... Just curious if you had tried this as I have heard of this happening on other devices because a data wipe wasn't done first. Might be worth a shot if you haven't tried it already, just a thought
Sent from my Huawei u8651s using xda app-developers app

Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
So after doing working on this a while, I've finally figured it out. Here are some caveats:
1. You can't do this on a Mac or Linux box. Don't ask me why, you just cant.
2. You have to turn on USB debugging, change the Security to allow Unknown sources and MOST IMPORTANT: when you plug it in, you have to change it to "Connected as a Camera". Putting it in storage mode doesn't work!
HOW TO INSTALL THE PROPER DRIVER & ROOT THE DEVICE:
1. Follow the steps quoted above and download the Google Android SDK, and the Java JDK (from oracle.com/java).
2. When you first plug it in (use the USB plug labeled USB not the HOST one), it complains and will discover a P771A device. When it does, right click on your computer, choose Manage my computer, go to the device manager and then right click on the P771A device. Click "Update Device Driver". Choose "Browse my computer for Driver software". Then choose, "Let me pick from a list of drivers on my computer". Browse to the \adt-bundle-windows-x86_64\sdk\extras\google\usb_driver folder which you would have if you had downloaded and installed the Google Android SDK. A list of 3 drivers will appear when you click OK. CHOOSE THE "ANDROID BOOTLOADER INTERFACE" as the driver. None of the others work.
3. Run the root script batch file mentioned above which can be found here at: sourceforge.net/projects/androidroot
4. The root script isn't really great at explaining so I'll try. When you first run it, make sure your device is unlocked and on the home screen.
5. The first thing it will do is reboot your machine. Don't press enter until your machine comes back up.
6. After your machine boots unlock it and then press Enter again. Your machine will reboot. This time it won't seem to come up but the backlight will remain on.
7. Wait about 30-45 seconds then press enter again. You should get: uid=0(root) gid=0(root) in the command prompt window.
8. Press Enter. You should get:
remount succeeded
727 KB/s (22364 bytes in 0.030s)
Removing changes except ROOT...
Installing superuser...
2288 KB/s (843503 bytes in 0.360s)
9. After about 30-60 seconds, your device should reboot. You'll see a box briefly saying "Android is Upgrading" and you'll arrive at the lock screen. Press Enter to exit the command prompt.
Your device is now rooted and you should see "SuperUser" installed. I promptly installed "root uninstaller" to get rid of Facebook, Skype, and Youtube which my little kids don't need access to. This device doesn't have a bootloader or recovery mode so rooting it doesn't get you much besides the ability to uninstall the system software. Have fun.

This may help someone but on step 2 of the guide on the second page, after you right click your device and go to "Let me pick from a list of drivers on my computer". You then click "Show All Devices" then "Have Disk..." Direct it to the root of the adt-bundle folder you downloaded then you can select from the three drivers. I'm on windows 7 32bit and the drivers didn't show up for me like how it was suppose to..

I also could NOT get any of the drivers in the "manufacturer USB" packet to install... I WAS able to install the google drivers, but that also would not allow ADB to see the device... So still stuck with everyone else...

P771A possible problem
I'm having a similar problem where the USB driver downloaded through Android SDK's -> Extras -> Google USB Driver, tells me that the file contains no information about my device. I noticed in the Sources of SDK, there wasn't an API for 4.0.4, only 4.0.3 then 4.1, so i downloaded 4.0.3 repo.
============================================
my devices is on 4.0.4, and my Kernal is as follows:
3.0.8+
[email protected] #8
Wed Aug 29 09:59:19 PDT 2012
Build Number:
P771A-user 4.0.4 IMM76D user.v402.007 release-keys
============================================
I've also made sure weather Unknown Sources is on, as well as USB debugging.
Might the Kernal be the problem? Also, does it matter weather its MTP or CTP?

Now HKC is telling me that they don't support the ability to jail break their devices
Sent from my P771A using xda app-developers app

Root for HAOQIN H7 PRO

Hi everyone, I recently purchased a tablet on Amazon, which is slowly gaining a lot of fame for its really affordable price .Unfortunately I was unable to find information on the specific rooting procedure for this device. I hope someone knows how to recommend a way to solve the problem, thanks to everyone anyway
PS: I have already tried several OneClickRoot applications like Kingo Root, KingRoot, Framaroot and 360 Root.
Tablet information:
Tablet name : H7 pro
Brand name : Haoqin
Device model : H7_EEA
Android version : 9
Android security patch level : August 5, 2019
Kernel version : 4.4.189
Build number : Winnovo_H7_V1.7_20200406

nubrox99 said:
Hi everyone, I recently purchased a tablet on Amazon, which is slowly gaining a lot
...
Kernel version : 4.4.189
Build number : Winnovo_H7_V1.7_20200406
Click to expand...
Click to collapse
Hi,
Unfortunately I didn't even found the firmware file for your tablet so I doubt someone will be able to root it successfully without those files.
Have a good day

nubrox99 said:
PS: I have already tried several OneClickRoot applications like Kingo Root, KingRoot, Framaroot and 360 Root.
Click to expand...
Click to collapse
My POV: Those so-called One-Click-Rooters all are crap. Most of them are heavily outdated, not applicable on devices with newer versions of Android as with Android 9 GO what is installed on your device. For example KingRoot you tried only may work on devices with Android versions up to version 5 & Framaroot you also tried only may work on device's with Android version less then Pie.
And worst: They may even inject trackers as it's reported in WEB.
In short: You have to root your device's Android manually by yourself, of course only if supported by OEM/Carrier. To verify this boot into device's Recovery and look for option "apply update from adb".
If NOT present then simply stop further reading.
How-To:
In Android's Settings->Developer options enable "USB debugging"
Install ADB-driver on your computer and make it systemwide accessible, means add its location to PATH environment variable and re-boot computer
Download SuperSU Pro
Rename the downloaded ZIP-file to update.zip and move it to folder where ADB-driver is housed
Make sure your Android is charged over 60%
Connect your Android device with computer via USB-cable
On computer open command prompt: [Win]+[R], input cmd and press Enter-key
Run commands - one by one
Code:
adb devices
adb reboot recovery
Don't close command prompt window!
In Android's Recovery menu select option " apply update from adb" and confirm by pressing power button
On computer run command
Code:
adb sideload update.zip
The zip.file will be sideloaded and written in your Android. The process will take quite a long time, so please enjoy yourself with something during the period. When it completes, you can see something like "Install from ADB complete" on the screen.
As last step on computer run command
Code:
adb reboot
Close command prompt window
You also may delete file update.zip: it's no longer needed
I hope I've made it clear to you.

jwoegerbauer said:
Code:
adb sideload update.zip
Click to expand...
Click to collapse
Hi jwoegerbauer , thank you very much for your timely and detailed reply, sorry if I did not answer immediately.I tried with your suggestions, but when I do this step, it gives me an unrecognized device error (in fact the adb devices command give me an empty list) .Checking on google, I noticed that it is a driver problem and then the phone is not recognized in recovery mode but, always on google I was unable to find a guide to solve the problem. On the android developer site I downloaded a file zip called "usb-driver", but when I update the drivers and set this folder as a directory it gives me this error: "The specified folder does not contain a software driver compatible with the device. if there is a driver in the folder, make sure it is designed to work with windows for x64 systems "
I hope it is not my mistake or that it is something resolvable anyway, I wait and trust in your further clarification if possible

@nubrox99
The driver package usb_driver_r12_windows.zip you downloaded isn't the expected one, it's only meant to be explicitely used with Google devices. Typically the USB-driver gets downloaded from OEM's/Carrier's website. If not provided by them, then the Universal ADB Driver should get installed.

Better Mobile App

welcome