Hey Guys,
Been lurking for a while. I want to get into some Android development. I bought a cheap Galaxy Tab s SM-T800 from ebay. It was a retail unit, so came with the usual retail protection, but that was no issue, I've reflashed it and rooted it, it is now running 6.0.1 with build number MMb29K.T800XXU1CRJ1.
The issue is, there are a bunch of apps and files that appear to be left over from the retail demo mode, and I can't remove them. The apps won't uninstall, it just says "uninstall unsuccessful", and the files, when I try to delete them, it just says "failed to delete".
Even after freshly restoring the new firmware, the storage on this device is pretty much zero, a lot of the space being taken up with the files and apps that I can't remove.
There was just about enough space remaining to install System App Remover, but that couldn't delete the files and apps either.
How are these files being write protected? How do I go about removing the write protection? I'm wondering if this device, because it was a retail demo unit, was configured with some kind of write protected partition, which is why the storage is so low, and why I can't delete the apps?
Any thoughts, this is driving me nuts.
Thanks
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
jwoegerbauer said:
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
Click to expand...
Click to collapse
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
DotNetDude said:
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
Click to expand...
Click to collapse
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
jwoegerbauer said:
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
Click to expand...
Click to collapse
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
DotNetDude said:
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
Click to expand...
Click to collapse
I realise I am responding to my own message!
Now that I am running with adb insecure, I have realisd that the USB debugging mode from developer settings is working in reverse. That is, if I enable it, the tab detaches form the PC. If I disable it, the tab reconnects to the pc. However with that setting disabled, and the pc connected, when I then run the command adb devices, it says there are no devices connected (even though I can browse to the tablet through windows explorer)
From within the adb insecure app on the tablet, when I enable the app, I can see it displays a message that says USB debugging is disabled.
I have no idea what is going on here...
Any help much appreciated?
Thanks
@DotNetDude
May be reading this helps.
jwoegerbauer said:
@DotNetDude
May be reading this helps.
Click to expand...
Click to collapse
Thanks for this. Actually, adbd insecure was just causing more problems. In the end I have resolved this by extracting the PIT file and re-partitioning. Firmware then restored correctly and all the problems are now gone, and there is plenty of free space remaining.
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
*****To all newebies(as quite a few new people are at this forum because they got their first device! (TFP)) any anyone who wants to learn, let’s get educated about our devices!*****
ADB (Android Debug Bridge) is an extremely useful tool that WILL help you in all of your customizing needs! You may see the need to use ADB commands to help root your device, change ROMS, or send your device a fix. Without the knowledge here, you could easily be left in the dark.
ADB is a necessity for developers and general consumers alike. Knowing this tool is a great advantage to you to help your device at the best quality possible.
Installation
Download Google SDK
Choose the correct operating system and install!
The installation REQUIRES Java JDK which can be downloaded from Here
If during installation it asks for JDK (and you have installed it) Press the back button and next again, sometimes that will fix the error.
**Note** The SDK installs to C:\Program Files (x86)\Android\android-sdk standard, chose any directory for you
Start the SDK and immediately, you will notice a few checkboxes. For the standard user, just make sure Android SDK Platform-tools (under Tools) and Google USB Driver package (under Extras) – the drivers are always good to have, latest ADB drviers.
Click install 2 packages and wait. Once installed go to your installation directory and find the platform-tools folder. This directory is your ADB and will be your lifeline!
**Do you want ADB accessible through any command prompt directory?**
You are in luck. (For Windows 7)
Right click on My Computer > Properties > Advanced System Settings >Advanced (Tab) > Environment Variables > Under System Variables scroll and dbl click on Path
TO THE END of the Variable value line add
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Or whatever the directory you installed to + platform-tools
Open CMD and type ADB, if you did it right, you will see proper ADB jargon regardless if you are in the correct directory or not!
Congratulations! ADB is installed!
**Make sure your device is using the latest drivers (that you just downloaded) or other ADB drivers provided by ASUS to access ADB. When connected in Debugging mode, device manager will have: ASUS Android Composite ADB Interface**
ADB Usage
**I will be talking mainly about commands/arguments that the general end-user may use or come across**
**Make sure your tablet is in USB Debugging Mode to be able to connect to ADB (Settings > Applications)**
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
ADB start-server : This command will start the server if the server is off or killed. (Normally server will auto-start when ADB command is used)
ADB kill-server : This command will close ADB server. Useful if ADB server is acting up or not connecting to any devices.
ADB remount : This command will mounts the /system/ partition Read/Writable pending the device is allow to. Stock TFP will NOT.
ADB root : This command will restart ADB with root permissions if the build allows for it. Stock TFP will NOT.
ADB usb : This command will restart ADB on device to use USB connection for ADB communication.
ADB tcpip [port] : This command will restart ADB on device to use TCPIP connection for ADB. Standard port is 5555. Again, this connect not recommended for file transfers.
ADB reboot [recovery/bootloader] : This command will restart your device. If either of the two options are given, the device will boot into that mode (sadly TFP does not support the two options.. yet)
ADB Tips/Tricks
When following ADB instructions, follow them WORD-BY-WORD in the EXACT ORDER GIVEN. If copy and pasting their commands (one line at a time) makes it easier, then do so.
If you have root access, do not mess around in ADB shell unless you know what you are doing
Connecting over IP can be beneficial for you for quick ADB access, but for file transfers, speed is slow and you ALWAYS risk corruption (check the md5!) One bad file and you have boot-loops!
ADB Logcat is an amazing command. If anything is wrong with your device, 9/10 you can see it in logcat. If you can find the exact problem, fixes can happen much easier. USE LOGCAT TO YOUR ADVANTAGE!
ADB reboot can be a quick reboot, sometimes you don’t feel like waiting!
Use the environmental variables! It helps exponentially, and keeps from having multiple instances of ADB running.
When multiple instances of ADB are running (different directories) ADB can get messed up! (ADB not up-to-date restarts, and connect problems). ASUS Sync service has and ADB setup. Turn it off if you are not using it. Try to stick to only ONE instance of ADB
Eventually, we may have root access in our recovery kernel. Then and only then can our devices be truly customizable!
The GUIDE is not finite. Please post anything you feel should be added/corrected to the guide. Please take notice from this, as the understanding of these simple commands could help save your device(s)!
Thanks and 5 star would make me feel good inside too!
Wow... Nice post. Lots of time went into this lol. Thanks can't give the five stars in the app though:-(
Sent from my Transformer Prime TF201 using xda premium
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Lock-N-Load said:
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
biggem001 said:
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
Click to expand...
Click to collapse
before you fixed it, it was trying to use this http://http://developer.android.com/sdk/index.html"
note the extra parens at the end and the double http call
i noticed that too, all i did was re-save and it worked. how weird.
Thanks! I've seen a few tutorials on this but this one was by far the easiest to follow and best organized. Short and sweet. Worked on my desktop great, I've never managed to install it right D:
Re posting to give 5 stars. Thanks again OP
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
cmat1120 said:
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
Click to expand...
Click to collapse
i can do either at once.. thats weird
GPS, Wifi and BT Testing
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Thanks - Great Info
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
theandies said:
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
Click to expand...
Click to collapse
i wont add it to the guide, because adb install is pretty self explanatory but this
make sure you can install non-market apps
Code:
adb install app.apk
jonalisa said:
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Click to expand...
Click to collapse
for GPS, use GPS Test app on the market
for BT and wifi testing, i'll just connect my device via BT or adhoc wifi and do the testing on my PC itself, more accurate and better programs
Excellent howto, thanks
I have trouble connecting to my prime with adb. In the Win7 Device Manager the correct device shows up, no exclamation mark at all, but adb just won't see the Prime.
USB debugging mode is on, no Asus Sync software on the PC. I have no clue why ADB won't see my device.
Now many of us can really shoot ourself in the foot.
by far the best and quickest adb install/setup ever. thanks OP!
neo1738 said:
by far the best and quickest adb install/setup ever. thanks OP!
Click to expand...
Click to collapse
aw shucks!
THANKS!
biggem001 said:
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
Click to expand...
Click to collapse
Just a small suggestion, adb won't accept commands if they are capitalized.
For example "ADB devices" will work perfectly, but "ADB Devices" won't.
So, in order to help the newest of newbies, you might want to put the commands in lowercase in the first post.
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
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.
Hi, I hope I am posting in the right section? I found the site really difficult to navigate having never used the site before. If its in the wrong place please can a mod move it.
Ok so I have an Android Set Top Box (STB) and I am trying to extract all the data from it. It is an mxp pro 4k. I don't want a backup of the data I want to extract full images of the device for analysing with forensic tools. The problem is I can't seem to communicate with it. I have the full SDK that is up to date, once navigated to the platform tools folder I opened a command line and typed
Code:
adb devices
after plugging in a USB cable to the OTG port. No prompts appeared on the screen to trust any connections like my iPhone does when I connect it. Adb devices returns no results. So I tried wireless adb, I typed
Code:
adb connect 192.168.x.x
and it said connected. Then when running the devices command I had the ip and port then the word device. I then get a shell by using
Code:
adb shell
Which i then elevate to root by using
Code:
su
. Then when i try an adb pull or adb backup I get a message saying error device offline.
Im new to Android so not even sure I am doing it right. I have done a lot of reading and research but seem to be stuck with the basics. To confirm USB debugging is turned on.