Related
rooted via ubuntu and have recovery
i tried doing stuff in windows, but it wont install the drivers properly.
SO I NEED HELP!
what do i do to get this to work?
i want to be able to install 3rd party apps and get rid of att bloatware.
i have no idea where to start.
HELP!!!!!!!!!
thanx
ubuntu or windows...
download the Android SDK for Windows
http://developer.android.com/sdk/index.html
install and download ONLY THE USB DRIVERS
open cmd window, connect usb cable, navigate to the <folder>\tools where you installed, ie. c:\android\tools
paste the following into a small batch file, call it anything you want dot bat,
ie. c:\android\tools\yourname.bat
---cut here--
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot
-- cut here--
ok i'll try right now
still must be missing something
what setting is my phone on when i plug it in? recovery? or just regular charge only or hard disk mode?
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
when i run that .bat file it says a bunch of things, but basically says device not found.
please start from step #0.
there is no one place that has every single step we need to do.
it makes it next to impossible to get this to work.
dh4645 said:
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
Click to expand...
Click to collapse
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
ocswing said:
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
Click to expand...
Click to collapse
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
dh4645 said:
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
Click to expand...
Click to collapse
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Shad0wguy said:
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Click to expand...
Click to collapse
so what is the point of the sdk...other than to have the tools folder to run that .bat? so i'm the only one that can't get the sdk usb drivers to work?
and by good to go, u mean i can install 3rd party apps?
how do i get rid of the the at&t bloatware?
There are other threads explaining how to install third party apps and remove ATT bloatware.
Sent from my HTC Liberty using XDA App
The problem with trying to do a step-by-step guide is that things like rooting, removing bloatware, and sideloading apps are all separate processes that require different steps and can be done in multiple ways. Some stuff requires you to be in recovery, some stuff doesn't, and other methods may require additional software. That's why there are specific separate threads that discuss them.
You've rooted your phone already, yay! Now you decide what you want to do next. Remove the bloatware? It's important that you don't lump everything together when trying to figure out what you need to do.
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
ocswing said:
....
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
Click to expand...
Click to collapse
thanks for the reply.
yeah i rooted via the ubuntu disc, but then all the other steps people were telling me were using the sdk, getting the drivers, htc sync, yada yada. via windows. so thats the method i've been trying.
is there a step-by-step guide on how to allow 3rd party apps using the ubuntu disc? or... removing bloatware?
is it the same steps, but you just dont have to worry about the drivers?
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
ocswing said:
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
Click to expand...
Click to collapse
ok cool thanks a lot!
i didn't even think to go back to linux to try this stuff until today at work.
i'll check it out later tonight after i mow the lawn and eat dinner....priorities...
i tried in windows one last time. it actually found the htc sync drivers (i in/uninstalled htc snyc earlier...i guess thats what did it)
adb devices command finds my phone, but when i try and run that .bat file, it goes through a bunch of things, but basically says:
remount failed: operation not permitted
failed to copy...
permission denied
all those types of things. then it says to hit enter and then it restarts my phone
???
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
b_atman said:
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
Click to expand...
Click to collapse
i said i did that above...that was the only way i got the usb drivers to work/recognize my phone...the sdk ones didnt work)
my phone is recognized when i run adb devices command
i'm having issues when i run the .bat file as i said in my last post
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
b_atman said:
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
Click to expand...
Click to collapse
uuu, no, whats that?
i thought i just had to open cmd and run the .bat file
so what did i miss now? ha
thanks for your help!
i ran this .bat file
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
I would take the time to learn ADB or wait until a one click is out. Learning ADB while rooting your phone could easily break it.
what os are you using?
svalle713 said:
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
Click to expand...
Click to collapse
Honestly just take the time to read the procedure, other help topics on these forums, and take your time when actually going through the procedure.
I had never used ADB either or rooted an android phone for that matter, and I gotta say, rooting the TBolt was cake.
I just took my time with it ensuring I typed in the commands properly.
But if you need a video, here you go: http://www.droid-life.com/2011/03/22/video-rooting-the-htc-thunderbolt/
what drivers do we need for the process, are they only the htc sync drivers? where can these be found?
Android SDK should be extracted/installed straight onto the C:\ directory to make it easy. Open the android-sdk folder and in it is a program sdkmanager.exe, open that and you can reject all of the downloads but scroll down and install one called the "google usb driver package" which may be necessary, I'm not sure (you should also have the htc sync drivers installed)
The contents from the "exploit.zip" should be extracted into the folder "platform-tools" within the android-sdk folder. Plug in your phone to the usb and open the command prompt. To get started open the command prompt (like a dos prompt) and get the prompt into the folder 'platform-tools' and type "adb devices" then hit enter. If your phone is connected and you have "usb debugging" enabled on your phone from the settings, your phone should appear and you can begin the instructions from jcase
*****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.
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.
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.