Hi!
I have a problem - ADB see my device as offline on PC. I tried many solves but no one helped me.
My configuration:
PC - Win7 (32), ADB v.1.0.31
Device - Android 4.0.3, ADB v.1.0.29
I don't know what happened but one morning couldn't connect to my device. Please, help!!
Before you lost USB connection, had you connected to it over Wi-Fi using the "adb connect (your IP address here)"? If so, try using [adb disconnect (Your IAP address)]
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
Before you lost USB connection, had you connected to it over Wi-Fi using the "adb connect (your IP address here)"? If so, try using [adb disconnect (Your IAP address)]
Click to expand...
Click to collapse
I rebooted PC and device and nothing changed after this.
And I restored System Restore Point (when the problem didn't exist), but my device still offline. :'(
Now exactly know that something wrong on my device. How make my device to work?
VJVS said:
Now exactly know that something wrong on my device. How make my device to work?
Click to expand...
Click to collapse
If device is detected on your PC, goto to Device Manager, check vendor id of ADB device, then edit adb_usb.ini (%HOMEPATH%/.android/) and add them e.g."0x2207" is vendor id for Rockchip. Restart adb.
lolet said:
If device is detected on your PC, goto to Device Manager, check vendor id of ADB device, then edit adb_usb.ini (%HOMEPATH%/.android/) and add them e.g."0x2207" is vendor id for Rockchip. Restart adb.
Click to expand...
Click to collapse
I have 2 strings:
USB\VID_0BB4&PID_0C03&REV_0255&MI_01
USB\VID_0BB4&PID_0C03&MI_01
In adb_usb.ini I must add just 0x0BB4. Is it right?
I added 0x0BB4 in adb_usb.ini and restart adb on PC. Nothing changed.
I was wrong, my device is OK, because it works on another PC. So I need restore working state my PC.
How to do it?
Well, I have new njuans. I reinstall PC drivers for device, I reinstall Android SDK and ... my device is still offline, though another device ara online and work perfectly. I installed "WiFi ADB Pro" on my device and it's work. My device is online, but it's via WiFi.
What can I do to work via wire?
Related
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
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
craterib said:
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
Click to expand...
Click to collapse
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
sz_gergo said:
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
Click to expand...
Click to collapse
Code:
[email protected]:/etc/udev/rules.d$ more 51-android.rules
# Sony Ericsson Mobile Communications AB
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="6168", MODE="0600", OWNER="kuisma"
Using this, you don't have to run the adb server as root. Use the "lsusb" to get Vendor and Product id for your device.
Also, change "kuisma" to your user, of course, unless toy happen to be me.
Restart udev (/etc/init.d/udev restart) once you've edited this.
sz_gergo said:
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Click to expand...
Click to collapse
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
bronzext said:
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
Click to expand...
Click to collapse
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
I did not see anybody here mention Knives-And-Forks Tools which is easiest way to Install adb and Fastboot on multiplatform computer. I did it and works like a charm
sz_gergo said:
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
Click to expand...
Click to collapse
hello i have question how to insert vid in hex notation...
digitized007 said:
hello i have question how to insert vid in hex notation...
Click to expand...
Click to collapse
Well therefor you will need an editor. I have used vi , but it is possible to use any editor.
2. step open the file in the editor
3. in a terminal window type " lsusb -v " that will give you the information of all the usb devices
look for the line beginning with idVendor of your device
for me it looks like: " idVendor 0x12d1 Huawei Technologies Co., Ltd."
4. copy the hexcode: 0x12d1 (yours may be another number) into the file
5. save the file
6. restart the server
only that number is needed nothing else
for every device you will get such a code , and each device code should came into a separate line
Hope that helps
br
sz_gergo
Hi all. What I need is a way to control Android device (s) from PC via Wi-Fi. I found a lot of apps (and Desktop programs) to do it, but I didn't found a way to View OR control the Android device WITHOUT ROOT. I work on the company which asked me to find a way to do this without root with their Android devices. After googling a lot I started to think that where is no way to do this, because either way I need to root them . Is it true or maybe there is somewhere an app which could do this? It doesn't care if it's paid or not.
I have downloaded and tester these apps:
MyMobiler - Doesn't work because when I restart Android device, app doesn't start WiFi, just keyboard mode only. I need that when the app starts it should run itself and start WiFi automatically.
VMLite VNC Server - Don't know why but it didn't worked for me. Just cannot start server from the browser.
Thank you for any responses and appreciate any help.
What error messages do you get from vmlite vnc server? Make sure you enable USB debugging. We have tens of thousands of users using our app, and your device should work.
Well, actually now I tried to launch VMLite VNC one more time and IT WORKED (don't know how, because earlier I tried it and I was unable to enter to VNC Viewer in the Browser). So yeah, in this case it works perfectly now, but I just realized, that I have no way of connected more Android devices. Because what I need to do is to connect multiple Android devices to computer with USB (as I understand it's required for the first time) and when use it with WiFi. For now I see that I only capable of connecting single Android device with desktop program and everytime I want to connect to Android deice from computer, I need to connect it via USB (where is no way to save Android devices to use it any time I want to via WiFi). Or am I wrong? And it is a problem because in my company all Android devices are far away from each other. Anyway, thank your for such an awesome app, I really don't know how it is capable of connecting to my Android device WITHOUT ROOT (because I found like 10 apps, read a lot of forums, and every solution was with ROOTED devices, I am very interseting of the actual app functionality), but thank you.
You can connect to multiple devices using multiple USB cables. There is a drop down list to display devices, and you choose one by one to start the server. Alternatively, you can write some scripts to auto start the vnc servers.
There are quite some testing companies using our app this way to automate regression tests.
Alternatively, you can write some scripts to auto start the vnc servers.
Click to expand...
Click to collapse
Can I get more information about it? Thank you.
Basically you can automate the starting process using adb command:
adb shell "am start -a android.intent.action.MAIN -n com.vmlite.vncserver/.MainActivity"
adb shell /data/data/com.vmlite.vncserver/files/vmlitevncserver
Deimantas007 said:
Can I get more information about it? Thank you.
Click to expand...
Click to collapse
Thank you for this script (it's very cool, I didn't know this kind of stuff before), but it requires USB connection as well.
I googled a few things and found this app - ADB Wireless (no-root) on Google Play Store. Basically it connects ADB via WiFi and I don't need no USB cable and connection with it. But VMLite Android App Controller program on my Desktop doesn't recognize it (it requires USB connection). Can I actually connect Android device with PC with this method or I am missing something and there is no way of doing it with this method? Thank you (I promise, this is the last question from me, no more dumb questions).
I don't think it will work for you. You mentioned your android device will reboot, right?
If your device gets rebooted, you will have to use a USB connection to a PC. the ADB wireless app has same requirement.
Steps to get it working: (from ADB Wireless app page)
1. Enable USB Debugging on your phone.
2. Connect your phone via usb cable to your PC.
3. Run adb tcpip 5555.
4. Run ADB Wireless (no root).
5. Connect to the IP address.
Deimantas007 said:
Thank you for this script (it's very cool, I didn't know this kind of stuff before), but it requires USB connection as well.
I googled a few things and found this app - ADB Wireless (no-root) on Google Play Store. Basically it connects ADB via WiFi and I don't need no USB cable and connection with it. But VMLite Android App Controller program on my Desktop doesn't recognize it (it requires USB connection). Can I actually connect Android device with PC with this method or I am missing something and there is no way of doing it with this method? Thank you (I promise, this is the last question from me, no more dumb questions).
Click to expand...
Click to collapse
huisinro said:
I don't think it will work for you. You mentioned your android device will reboot, right?
If your device gets rebooted, you will have to use a USB connection to a PC. the ADB wireless app has same requirement.
Steps to get it working: (from ADB Wireless app page)
1. Enable USB Debugging on your phone.
2. Connect your phone via usb cable to your PC.
3. Run adb tcpip 5555.
4. Run ADB Wireless (no root).
5. Connect to the IP address.
Click to expand...
Click to collapse
What's right. It needs to connect my phone via USB. But I thought that maybe there is a way to automate this process, I mean maybe there is a solution to TURN DEBUGGING MODE between phone and pc programs via WiFi connection (not USB) and communicate with VMLite VNC Server program on startup. Either way, again, thank you for your software (app). I will say to my boss that we need to stay where we are at the moment. It's just awesome to have an app which doesn't require ROOT.
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Added English version manual on Lenovo-Forums.ru
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
Do this root apply to the s8-50F ?
EDIT: This method indeed does work on the S8-50F variant. Was having problems with device staying in adb while running program, but a reboot of pc fixed that and gained root effortlessly. THanks!
Glad It Helped !!!
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
The download isn't working for me. It's not downloading as a zip? Any suggestions?
If youre using windows, download a program called 7-zip and downoad the file. right click the root software and click extract here. or open with 7-zip. You could also use winrar. The format of the file is in .7z right ? that means search up http://www.7-zip.org/
Any idea how to unroot?
Not sure. Have you tried the full unroot method in the su app?
__McB__ said:
Any idea how to unroot?
Click to expand...
Click to collapse
SuperSU.apk.....in the setting, unroot, cleanup...
icanttinkofaname said:
Not sure. Have you tried the full unroot method in the su app?
Click to expand...
Click to collapse
jazzespresso said:
SuperSU.apk.....in the setting, unroot, cleanup...
Click to expand...
Click to collapse
Thanks both of you. I ended up returning it, root and all, but I'm sure your suggestion would have worked.
After rooting, has there been anything anybody's been able to do about battery life? I don't imagine there's been any Roms built for this device yet, but didn't know if maybe someone's figured out something that's helped extend their battery life, because when playing certain games like clash of clans for instance, I'm lucky to get an hour and a half of game play, and that's with my brightness turned all the way down. Any suggestions would be greatly appreciated. Thanks
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
This root guide works on s8-50f! thanks Xakep
This is a very easy and usefull root instruction, i rooted my tab s8-50f with no problems.
I followed the steps described and got instant root without any issues.
My machin is windows pc with windows 8.1 pro 32bit. Plug your tab and windows recognized the drivers just make sure your device mngr shows lenovo s850 and you are all set. Then just run the flash tool and it will run in less than a minute your tablet will reboot and your tab will be rooted.
Yes this is probably the easiest I've ever rooted any device in the past. If at first it doesn't take, don't worry it will. Just repeat the process till it does. Thanks Hash.h for putting up this thread and passing along the info
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Where can I download the ADB drivers for S8-50 from?
I think drivers come with tablet. Try to connect the tablet and it will show CD drive on which is the driver.
error: device offline?
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Worked great. Thank you.
Awesome little tablet.
Jirbo said:
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Tried on another computer and succeeded.
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
moogthedog said:
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
Click to expand...
Click to collapse
Same problem here. Lost root after the last update and now I can't get either root method to work.
hello,
I previously was using HTC explorer and had many great experience of rooting and changing custom ROMs setting up of adb was easy with it but currently I own a dell venue 7 3740 LTE tablet which is having KitKat 4.4.4 I have a HP laptop with windows 7 ultimate I want to start using adb in command prompt so that I can do lagcat and capture ota updates link also I want to use adb so that some apps which needs root but can be used via some tweaks done in adb eg.helium,screen shot ultimate etc.
please help me how to setup adb in my laptop.
Have you tried installing the Intel Android USB Drivers?
xBIGREDDx said:
Have you tried installing the Intel Android USB Drivers?
Click to expand...
Click to collapse
That one works amazingly well fixed my fastboot driver on windows 10
social-design-concepts said:
That one works amazingly well fixed my fastboot driver on windows 10
Click to expand...
Click to collapse
But Its not working for me.
http://forum.xda-developers.com/general/xda-assist/dell-venue-7-3740-mtp-usb-debug-problem-t3173463
xBIGREDDx said:
Have you tried installing the Intel Android USB Drivers?
Click to expand...
Click to collapse
yes I have installed the v1.9.0 setup in device manager in laptop when I connect my tab with debugging enabled it shows in portable device my tab name,and other device mtp is shown with yellow exclamation.
mtp drivers for tab are not getting installed.
in cmd when I hit adb devices I don't get my tab details
Does it show like the pictures in my link ????
Dipyaman said:
Does it show like the pictures in my link ????
Click to expand...
Click to collapse
yes its shows yellow error in mtp but I am able to transfer files from laptop and tablet only thing is I can't use cmd and adb but after going thru your link I come to know that my adb was too old which is of my HTC explorer so I downloaded adb (platform.zip) from the thread given in your post and then for mtp I manually selected driver installed in my laptop I.e adb interface >Samsung adb and then I tried cmd in new platform.zip which had updated adb files for jellybean+ version and now its working fine.
Dunno how you did that. I'm a newbie.
Could you plz help me out ?
I don't have any sort of "Adb" connection in device manager (which you can see in my image), which was supposed to be there.
Can you give me a detailed explanation of what you did ????
Dipyaman said:
Dunno how you did that. I'm a newbie.
Could you plz help me out ?
I don't have any sort of "Adb" connection in device manager (which you can see in my image), which was supposed to be there.
Can you give me a detailed explanation of what you did ????
Click to expand...
Click to collapse
so you too also want adb to work for you right?
I can't say exactly what made it work for me cause I have s duos 2 also n so its drivers are also installed in my lappy.
but you do one thing
1.install Intel android driver from above post v1.9.0
2.enable debugging in tablet and connect and then goto device manager where you have mtp error,right click on mtp,update drivers select from folder will appear below that must be some option select from installed drivers goto that see Intel android driver after that you will be getting multiple option android adb interface, adb composite interface select any one preferably android adb interface and install.after that uncheck debugging and again check it and see if mtp error is gone from device manager.
3.download platform.zip from your given thread link unzip it and in that folder open cmd by holding shift and right click do open cmd here and check if all is OK by typing adb devices,if its OK it will list your device.
I'll give it a try, then i'll inform you. Till then, please stick to the post ! Thank you for the info BTW.
Dipyaman said:
I'll give it a try, then i'll inform you. Till then, please stick to the post ! Thank you for the info BTW.
Click to expand...
Click to collapse
today I tried changing from samsung adb driver with Intel adb driver and it worked
djmacpro said:
today I tried changing from samsung adb driver with Intel adb driver and it worked
Click to expand...
Click to collapse
The problem is, Installing Intel USB drivers does not do anything. Its does not show up in my device manager.
Dipyaman said:
The problem is, Installing Intel USB drivers does not do anything. Its does not show up in my device manager.
Click to expand...
Click to collapse
if still yellow error is shown on device manager right click on it update driver,then browse from folder or look for installed driver some where is must be there search something related to Intel or adb and select that else forget it cause what's the use of adb for us as there is no custom ROM or other things to do.
other way is download helium app on PC and tablet and in ptp mode you can get adb working