Hello,
My vibrant got recently run over by a car and the screen doesn't work anymore However, I know that it still can function because I can see the 4 capacitive keys on the bottom light up when I touch them. Is there anyway for me to be able to view the Vibrant's harddrive on my computer without having to switch to USB mode (since my screen doesn't work)?
if you have adb installed and know some basic linux commands you can use ADB to view the contents of your vibrants storage via command prompt and should be able to copy most of your data over. As far as a graphical solution i think there was something being developed called screen cast at some point but i dont think that will be much use to you as i believe it has been abandoned
I am familiar with adb but I can't see my device for some reason when I connect my phone to my computer and run 'adb devices'. I've used adb in the past to push / pull files but I remember having to mount the device from the dropdown menu before it would be recognized. Is there any way to force the phone to be connected? Thank you for your help!
isyiwang said:
I am familiar with adb but I can't see my device for some reason when I connect my phone to my computer and run 'adb devices'. I've used adb in the past to push / pull files but I remember having to mount the device from the dropdown menu before it would be recognized. Is there any way to force the phone to be connected? Thank you for your help!
Click to expand...
Click to collapse
are you on a stock rom? ever since i started using custom roms ive always had ADB debugging enabled, unfortunately you may be SOL if you need to enable ADB debugging as both the adb method and screen cast require ADB to work,the other option is to take apart your vibrant and have the internal memory chip read that way tho your stand a good risk of damaging the internal memory chip
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.
Recover files from phone with a broken screen, no USB debugging and set as "Charge"
Hey,
So, I'm trying to recover files from my previous phone, a Xiaomi Redmi Note 5 Pro. It can boot Android and also get into recovery mode, but I can't see anything on the screen (it's completely black) and I think it doesn't register touches either.
The big problem is, USB debugging is off and USB mode is set to charging only (no MTP).
If I enter TWRP, adb recognizes it (it's listed when you type "adb devices"), but what can I do from there? Is there a way to enable MTP through TWRP adb? I tried some commands like "adb shell" or "adb shell <command>" but it says these commands don't exist or just gives me a list of some other commands.
Is there just no way to recover my files?
Thanks for your help regardless.
@Ulfys
From your description it seems like you already have ADB access from the recovery ROM and it looks like you have access to your data partition. Therefore you can backup your data and migrate it to a new phone
Note: Being in Recovery mode you can only use adb pull, adb push and adb reboot
That doesn't help if I want to recover my files in the internal storage, though. And I don't have any other rooted device with TWRP - even if I had one, flashing another phone's data partition isn't a great idea.
Enabling MTP somehow would be a lot more convenient.
Ulfys said:
Enabling MTP somehow would be a lot more convenient.
Click to expand...
Click to collapse
Enabling MTP requires to have access to Android terminal: adb shell
EDIT:
IMO the only option you have is to pull data from device: adb pull
Hi! I have a problem with my DZ09 Smartwatch. I am trying to install the APLUS firmware like said on this ht tps://roon by.com/ 2016/10 /02 /update- dz09-fir mware/ website. So I do not know if that would work anyway, but it won't even connect! It connects, shows charging symbol, disconnects, connects again, then shows me SD card contents. I try this without the SD card and it does the same thing, but without showing me SD card contents. Any help is appreciated.
@JBJesseBarryJB
Seems the watch's ADB mode is set to MTP, hence you get shown contents of its SD-card
jwoegerbauer said:
@JBJesseBarryJB
Seems the watch's ADB mode is set to MTP, hence you get shown contents of its SD-card
Click to expand...
Click to collapse
How do I set that otherwise?
JBJesseBarryJB said:
How do I set that otherwise?
Click to expand...
Click to collapse
If your watch's Android is rooted
To get the list of current USB mode
Code:
adb shell "svc usb getFunction"
To set USB mode to adb
Code:
adb shell "svc usb setFunction adb"
jwoegerbauer said:
If your watch's Android is rooted
To get the list of current USB mode
Code:
adb shell "svc usb getFunction"
To set USB mode to adb
Code:
adb shell "svc usb setFunction adb"
Click to expand...
Click to collapse
I'm not rooted. And I do not know how to root a DZ09 Smartwatch, is there another way?