Dear friends,
I didn't find Lenovo IdeaTab S6000 related discussion, and all threads related problems similar to mine - didn't help resolve my problem. That's why I post here. Anyone with advice what else to try, how to proceed - is welcome.
My tablet is Lenovo IdeaTab S6000-H, with 3G modem, 16GB memory and MT8389 processor.
My problem is - when I turn on tablet, Lenovo logo is dispalyed, I hear some sound, logo is animated, then - it gets silent, logo gets static. It may last like this as long as battery lets.
What I did - I wanted this tablet to be a gift, and I really needed needed multiuser profiles enabled. So the only changes were towards reaching this functionality. Here's what I did step by step:
I rooted the device as this instruction says: http://rootinghub.com/root-lenovo-ideatab-s6000-h/
I used Framaroot 1.6.1 for rooting, downloaded from here: http://forum.xda-developers.com/showpost.php?p=37508806&postcount=1
I wanted to connect the device with laptop (Windows Enterprise 64 bits), but the device wasn't recognized by Windows. This instruction helped me: http://stackoverflow.com/questions/...ct-a-lenovo-ideapad-s6000-to-windows-7-64-bit. I updated [Google.NTx86] and [Google.NTamd64] sections with following:
;IdeaTab S6000
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_75E2&REV_0255&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_75E2&MI_01
Once I connected tablet to laptop, message popped up informing IdeaTab S6000 has been connected
What I really wanted was multiuser support. I followed this instruction and it worked like a charm: http://mlagerberg.com/post/56229890887/no-multiple-user-profiles-on-your-android-4-2-2-yes-we
I added second user, and I was able to switch from one profile to another
However, once I rebooted tablet - multiuser support was missing (pm get-max-users command returned 1). I realized I had to add fw.max_users=8 line to the build.prop file, as this instruction says: http://forum.xda-developers.com/showthread.php?t=2275350. I added fw.max-users=8 as the last line (hit enter afterwards) to build.prop, editing the file as this instruction says: http://forum.xda-developers.com/showthread.php?t=1948558
Then I faced the issue I can't overcome:
Once rebooted - Android freezes when the initial logo is displayed
When I try to connect the device to laptop and use ADB - HTC Desire is detected, not the IdeaTab S6000; I can't use adb, I can't get to the device with adb shell, adb kill-server did not help
I tried hard reset (factory reset), cache reset - with no success
When I put tablet into adb recovery mode - the device is detected (by adb.exe, windows) with 0123456789ABCDEF id, but adb.exe can't connect - and the device is shown as HTC Desire under Windows' Device Manager
I tried sdcard update with Update Zip Packager 3.0 I found here: http://www.mediafire.com/download/7j9z6c75mycqll3/Update-Zip-Packager+3.0.zip with no success - I get installation error with updates as simple as doing nothing but printing welcome message
I think the issue is with build.prop file - either the extra line I added, or file's permissions - I didn't verify file's permissions once I updated the file - but I can't find a way to mount Android's file system so I could fix it from my laptop
Thanks in advance for any help how to recover my tablet...
Related
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.
I've tried following various steps in the AIO thread in the developers section and believe I have a similar problem to pjc007. I have tried foloowing his steps in http://forum.xda-developers.com/showpost.php?p=27548839&postcount=1179 but I'm still stuck on getting the drivers installed when the tablet is in recovery mode. Am I right in trying to install the mtp driver from the AIO/files directory?
I have tried running AIO on two win 7 machines and a virtual xp machine and get the same problem on all machines. Please help
Is anybody able to help at all?
Or if anybody has a UK 16GB Wifi ICS Rom ready to run from recovery, that would be very much appreciated
you mean you háve your tablet already updated or rooted?., and the drivers aren't installed for ICS?
could you be more specific "D
---------- Post added at 09:45 PM ---------- Previous post was at 09:39 PM ----------
1. Update your SDK Manager
- In SDK Manager expand Extras then search for Google usb Driver if not already installed then do this,
2. Open the google-usb_driver folder that you will find inside your Android SDK folder.
- Example C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\
3. Open the android_winusb.inf file in notepad or any text editor to edit it.
- If you can't change this then try to change permissions in that folder
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&MI_01
4. Open a command prompt window and enter this command:
echo 0x054C >> "C:\Users\Cinquk\.android\adb_usb.ini"
5. Make shure you have USB Debugging enabled.
- Menu > Settings > Applications > Development and enable ‘USB Debugging’.
6. Connect your tablet to pc and let the pc install the drivers some will faill but thats okay.
7. Right-click Computer and click Manage and search your device from the list, right-click it and click Update Driver Software.
8. Choose to browse your pc,
- Choose to view all devices.
- Click Have Disk.
- Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
---- It might say that its not compitable but just proceed.
9. Once the drivers have been installed, you should be able to use ADB with your device.
10. to check that,
- Press Windows button + R
- Then type CMD and press enter.
- cd.. back to your Harddiskdrive.
- cd to your Platform-tools folder Example C:\Program Files (x86)\Android\android-sdk\platform-tools
- then type:
adb kill-server
adb start-server
adb devices
- you should see your devices listed ( Serial Number )
and you can comfirm that you have a working adb with you sony tablet s.
Thanks for the above info, my ADB is working fine in normal boot, but not in recovery mode.
I originally had my tablet rooted and updated to the first US ICS rom about a month ago using AIO tool v2.7
All was fine until I started poking around to find out why my titanium backup kept failing and found this was due to the SD card being set to read only. I followed a guide in these forums to enable read/write (before this fix was available in AIO) and somehow managed to wipe my permissions file.
I decided to start from scratch, flash back to hc and start again, but since doing this I have been unable to install an adb driver for when the tablet is in the recovery mode. ADB is working fine in normal operating mode and I could use AIO fine, until the point where it was waiting for a response in recovery mode as no drivers are installed...
I got impatient yesterday and have now updated a stock, non rooted US ICS as I've been going in circles for a couple of weeks trying to make a pre-rooted update file and I've been missing my ICS I would ideally like to be on a proper UK rom, but will live with US version if there's nothing I can do for now.
Alright that means end of this topic
Hello everyone,
it's been over 20 hours I'm trying to root a Polaroid MID2407 tablet that my mother received to be able to use a USB 3G Vodafone Mobile Broadband dongle and I immediately understood that it was necessary to root the tablet...
Information about my tablet:
Polaroid 7 " MID2407PCE02
Hardware: gs702c
Model: MID2407
Build number: MID2407-user 4.4.2 KOT49H eng.cx.20140623.100409 release-keys
Build UTC date: 20140821-100653
Android v 4.4.2
Baseband v: Haier
Kernel v: 3.4.0+ (huangyingyuan @ srv-fw-compile3) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70)) # 1 SMP Mon Jun 16, 2014 2:15:58 p.m. CT
SYSTEM (Android 4.4.2)
Model: MID2407
Manufacturer: POLAROID
Device: MID2407
Product: MID2407
Brand: Haier
Android Version: 4.4.2 (Kit Kat)
API Level: 19
Build ID: KOT49H
Fingerprint: Haier/MID2407/MID2407:4.4.2/KOT49H/eng.cx.20140623.100409:user/release-keys
PROCESSOR (ARMv7)
Processor: ARMv7 Processor rev 1 (v7l)
Cores: 2
Max Frequency: 1308 Mhz
Instruction Sets: armeabi-v7a, armeabi
SIMD Instructions: NEON
I already tested without success (and after ten malware!):
- All "onle Click Root App" as Kingo & co.
- RootGenius
- Impactor
- Bin4ry
- CF-Auto-Root (*)
- VRoot
- Odin (*)
- towelroot
- ...
(*) I have not found a file that works on my tablet model.
What works: adb, but I have that as a result of a "adb shell id"
Code:
uid = 2000 (shell) gid = 2000 (shell) ...
And then I don't know what to do .... ?script? where find script?
Mtk Droid Tools gives me this:
"In system already available: Android Debug Bridge Version 1.0.32
Code:
--- >>> <<< --- Connect to device
--- ERROR: --- TotalBytesPerChunk Not Found. Set default page / Spare = 2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
Again I am lost ...
I ask not fit all, but just tracks on where and what to look for to keep moving forward...
All suggestions are welcome, thank you!
Note: I'm on Windows, but I've also Linux, so if there are tools for Linux, I'm interested also ...
*edit*
Important note: I do not know how to access to the boot menu of my tablet ... I have a power button and a large volume +/- button, but nothing happens unless a "reset"! And I also have in the back a small hole but it's just a "reset" and there is no information on the website of polaroid.
Updates:
iRoot V1.7.9.2 => Fail
SRS One Click Root 4.7 => Fail
Root Genius 1.8.7 => Fail
But with SRS there is an ADB utility with I can reboot in recovery mode! So, I continue to search...
worked for me same tablet
androidxda com/download-root-genius
GolgothBe said:
Updates:
iRoot V1.7.9.2 => Fail
SRS One Click Root 4.7 => Fail
Root Genius 1.8.7 => Fail
But with SRS there is an ADB utility with I can reboot in recovery mode! So, I continue to search...
Click to expand...
Click to collapse
otij said:
worked for me same tablet
androidxda com/download-root-genius
Click to expand...
Click to collapse
Hello,
Fail for me :crying:
With me, at 27%, 47%, 50%, 80% ... My tablet reboot each time... Same for you?
Wich drivers use you? I use AdbDriverInstaller (Windows 7) and I have in device management:
Android Phone
---- Android Composite ADB Interface
It's strange that don't work for me
GolgothBe said:
Hello,
Fail for me :crying:
With me, at 27%, 47%, 50%, 80% ... My tablet reboot each time... Same for you?
Wich drivers use you? I use AdbDriverInstaller (Windows 7) and I have in device management:
Android Phone
---- Android Composite ADB Interface
It's strange that don't work for me
Click to expand...
Click to collapse
you must first remove /uninstall kinguser ( kingroot) from your phone
or the combination of two make it reboot perhaps? .
verify your removed any other thing that installed root (busybox supersu?) .
then retry .
i don't have reboot problem only with other tools like foldermount
that is not really fit to this kitkat 4.4.2 ...
you need let windows install the drivers hit start in windows then in the search field
type exactly
device installation settings
(if your windows is in another language you need to find out how to let windows
install drivers automatically) .
click on top result and let windows install drivers automatically
otij said:
you must first remove /uninstall kinguser ( kingroot) from your phone
or the combination of two make it reboot perhaps? .
verify your removed any other thing that installed root (busybox supersu?) .
then retry .
i don't have reboot problem only with other tools like foldermount
that is not really fit to this kitkat 4.4.2 ...
you need let windows install the drivers hit start in windows then in the search field
type exactly
device installation settings
(if your windows is in another language you need to find out how to let windows
install drivers automatically) .
click on top result and let windows install drivers automatically
Click to expand...
Click to collapse
It does not work with my tablet (are they really the same, I have a European model based on ARMv7) when installing drivers on Windows, I have an error "invalid data.".
It is certainly the problem, I'll try to find a solution without going through the ADB drivers ...
Thank you anyway
GolgothBe said:
It does not work with my tablet (are they really the same, I have a European model based on ARMv7) when installing drivers on Windows, I have an error "invalid data.".
It is certainly the problem, I'll try to find a solution without going through the ADB drivers ...
Thank you anyway
Click to expand...
Click to collapse
YEs our tablet are slightly different (mid2407cje01.133)
named "polaroid infinite" 7 inches
i am using win7 64 bits
but i think 32 will do same result.
you are using the wrong drivers.
(under android phone)
you need "ROMaster composite adb interface"
look in settings/storage/ 3 dots on top right /usb computer connection
if you are in usb large storage you need see 2 drives letters
if you are in mtp then you need see (under portable devices) mid2x07pj
(you can try change to MTP to root but
first let windows install the good drivers
As mentioned before)
the "root genius" here it goes to 15% then reboot then finish to
root .
= reboot only one time.
remove all drivers set windows to install drivers auto .
then plug tablet to a new usb port.
good luck
otij said:
YEs our tablet are slightly different (mid2407cje01.133)
named "polaroid infinite" 7 inches
i am using win7 64 bits
but i think 32 will do same result.
you are using the wrong drivers.
(under android phone)
you need "ROMaster composite adb interface"
look in settings/storage/ 3 dots on top right /usb computer connection
if you are in usb large storage you need see 2 drives letters
if you are in mtp then you need see (under portable devices) mid2x07pj
(you can try change to MTP to root but
first let windows install the good drivers
As mentioned before)
the "root genius" here it goes to 15% then reboot then finish to
root .
= reboot only one time.
remove all drivers set windows to install drivers auto .
then plug tablet to a new usb port.
good luck
Click to expand...
Click to collapse
Thank you so much! You gave me some good information!
1. I do not know why, but in my mind, when I put in "debuging" mode, I desactived systematically the MTP mode ... So I left the MTP activated with the debugging mode.
2. I have uninstalled all the drivers ...
3. I have downloaded "ROMaster composite adb interface" ...
4. I connected my tablet and Windows has recognized the MTP mobile devices ... but not for the "Android Phone / Tablet", then I have not found how to install the downloaded drivers ... I 've tested RootGenius 1.8.7, but has not found the right drivers ... I tested iRoot V1.7.9.2 (ex VRoot) and there it automatically installed the drivers ROMaster ... But the root procedure failed again ... I uninstalled the apps added by iRoot and rebooted my tablet.
5. I then launched RootGenius 1.8.7, reboot @ 34% @ ... Installation complete reboot ... 37% ... 41% ... 44% ... 63% ... reboot @ 67 % .... 70% ... 73% ... 76% ... 83% ... reboot ... what a thrill! Failed Root ... ... ... :crying:
I do not despair! I would have even if it takes me a year!
Note: in devices manager (with MTP + Debugging), I have:
- Android Phone
+ ROMaster Composite ADB Interface
- Mobile devices
+ MID2407
MID2407 give me access to SD in my tablet...
But with "ROMaster Composite ADB Interface", ADB doesn't work anymore... :silly:
once again do not try download drivers yourself .
let windows do it automatically .
Open Devices and Printers by clicking the Start button Picture of the Start button, and then, on the Start menu, clicking Devices and Printers.
Right-click the name of your computer, and then click Device installation settings.
Click Yes, do this automatically (recommended), and then click Save changes. Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
If Yes is already selected, click Cancel to close the dialog box.
A friend of mine has a tablet very similar to this and asked me to help root it because it has only 1.3ish gb of internal storage and because it has kitkat 4.4.2 apps cannot be installed on the sdcard... so please help us. rootgenius and towelroot can't root it so what should i try next?
Gracias
Hi
I have IUNI U3
I wanted it to support google services, so i've followed some guide from this forum
According to the guide, I had to change the ro.product.model
Since then, the phone is not starting..even not fastboot : /
I have a backup of the file inside the phone, but there are 2 main problems:
1. adb has issues connecting the device..
When I connect the device to the computer, it starts searching for drivers
During the search the device is connected, but when it fails, the adb sees the device as offline
Do you have any idea how can I get the drivers? I don't know chinese, so I have problems searching the official site
2. if I do manage to get inside with adb, it doesn't have permissions on the files
Please HELP : ///
Thanks
I dont no .........!!!!!
Almighty! lets get started,
I have a 64 bit computer running Windows 7 professional.
First let me mention I tried to fix this on my own. darn I tried.
Just plugging the tablet into computer shows a windows explorer page named Autoplay that let me view pictures on device on a folder named
Computer\Trio HD Elite 7.85 Tablet
Installed android-studio-bundle-141.1903250-windows in
Error- SDK required.
Downloaded jdk-7u79-windows-x64 (java development kit)-install reboot PC
Open C:\Andriod in windows explorer, open SDK Manager
A command prompt window flashes briefly, then closes.
click start, search for run key in sysdm.cpl go to advanced, environment variables create new path named JAVA_HOME that does directly to the java .exe file
(this was checked by reinstalling the java development kit, then opening Java typing where java it tells me C:\Windows\System 32 even though the path is
C:\Program Files\Java\jdk1.7.0_79
opening ADB works!
Download Extras- Android USB Driver
open CMD key in
cd C:\Andriod\platform-tools
this brings me to the directory where Android ADB is.
abd devices
no devices detected.
Installed Samsung Kiles.
TRIED to install PDAnet.. failure.
tried to open Device manager, where a entry marked Trio HD Elite 7.85 Tablet sits, and update the driver to the C:\Andriod\extras\google\usb_driver
it complains about driver being unsigned. Using This guide I used step Two downloaded Driver Signature Enforcement Overrider (DSEO) and ran it.
went into the C:\Andriod\extras\google\usb_driver folder and manually keyed in every title in the folder.
each time program stated had signed successfully. The computer is now saying test mode in the bottom right hand corner. however trying to update driver gives same error.
I'm amusing the device needs to be in developer mode, which it cant be put into because it's locked.
The Trio Support is useless there steps do not open any settings. Also tried a list of alternate ways to open tablet recovery. and since ADB isn't reconizing the device I can't run adb reboot recovery
So. end result, im here with coffee and no milk,
A generic tablet cobbled together from who knows where,
and a locked screen.
Think you can help?
ANY assistance is appreciated.
So i have a cheap generic tablet that says Trio Stealth G4X 7.85