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
Related
So after an incident saturday, my Thunderbolt screen is in a trillion pieces. The phone still boots up fine, receives text messages (much to my chagrin) and receives calls. In fact, it's still paired with my bluetooth in my car so I can make and receive calls when in my vehicle.
However, my replacement should be here tomorrow. I missed several important text messages (the source of its destruction).
Unfortunately, I did not have the phone in PC Mode prior to its destruction, so I cannot see it with adb devices. Is there a way to get it into PC Mode without seeing the screen? As in, a certain key press on bootup that would allow the PC to see it properly?
Upon that, I could use ddms to capture the screen, or download the text database (it is rooted).
On the other hand, the Verizon tech at the corporate store says they can transfer texts as well as contacts (I have Exchange so that's not an issue) if the phone boots. I am very skeptical that this is the case, but she insisted. If they can, then this isn't a big issue to me.
Thanks!
I *think* I might have solved part of the problem.
This is a new PC and I never installed the HTC drivers.
Before I installed them, nothing showed up in adb devices.
Now, my device is listed... but it says "offline" or "error: device offline" when trying to use adb shell.
ddms also doesn't allow me to get a screen shot.
Did you not have USB Debugging checked? That's all you need for ADB to work. It doesn't have to be in PC mode if that's checked.
I'm positive I did have USB Debugging checked as I rooted the phone and did a lot of hacking. Good to know I don't have to put it in PC mode though.
However, I can't seem to get by the "offline" message I get with adb devices or "error: device offline" when I do an adb shell. doing a kill-server and start-server has no effect.
I think I might be on the right track.
I was able to boot into recovery somehow by using power and vol down.
Then I hit something (Power I think) and it vibrated.
Now adb devices lists my device, followed by recovery.
I can connect via adb and list the directory, but only the recovery partition is mounted.
I was able to mount the system via mount -t ext3 /dev/block/mmcblk0p25 /system, but I don't know what the mmcblk is for the data partition.
GOT IT!
Using ddms, I was able to see that I had booted into Clockwork. I then was able to navigate to the mount section and mount /data.
From there, I was able to use adb pull to get the mmssms.db file and use Root Explorer on my Xoom to view those text messages. Then I was able to see why I threw my phone in the first place
Phew, it's amazing what you can do in the Android world.
Bodero said:
Then I was able to see why I threw my phone in the first place
Phew, it's amazing what you can do in the Android world.
Click to expand...
Click to collapse
lol funniest thing i heard all day... maybe there is an android app to fix those anger issues!!
I'm having issues with my laptop detecting attached adb devices (Thunderbolt specifically). I can get my main computer to recognize/detect an adb device. I will then disconnect my phone from my main computer and plug it into my labtop, and yet my laptop will not recognized there's an adb device attached. Regardless of the following, i still can not get it to work on my laptop: Closing CDM, disconnecting the phone from the computer, plugin the phone back then pull up cmd (or pull up cmd and then plug in phone -ive tried every common sense trick there is).
Whats going on with my laptop that will not allow it/android sdk to recognize the device? How do I fix this?
PS in case it needs to be mentioned, yes i have USB Debugging selected (thats why i am able to get the one computer to recognize it).
never mind i'm an idiot, since i manually add the script in for the USB drivers i forgot to select where to pull the drivers from in device manager. Sorry about this post, please delete it.
Hello All,
This is my first post so here goes.
I simply need to get rid of the USB Mode notification when Nook Tablet is connected via USB to my Windows 7 PC so I can navigate device.
I have done a ton of research to get ADB working on the Nook and was having tons of problems with Windows XP and drivers. Moved to Windows 7 32-bit PC. Now I have Nook Tablet provisioned for USB Debugging and ADB sees the device. Now all I need to be able to do is plug the Nook Tablet into my PC via USB and not have the USB Mode notification appear. I need to be able to navigate the device while it is connected to PC via USB and recognized by ADB. Does anyone have any insight on how to remove this USB Mode notification when I plug my NT to my PC?
What I have:
NON-ROOTED Nook Tablet Software version 1.4.3
Provisioned for USB Debugging
ADB recognizes device and I can see it with no problems.
Thanks,
Maybe you can try this?
Well here goes a reply, since a lot of the questions are answered with rooted nt and that is why there is not a hole bunch of replies.
You could try sshdroid app, it said root is optional. No usb needed for this one. Hope that works for ya.:fingers-crossed:
p.s. Use terminal in winscp and type or paste your commands in the field. Make sure you exit the app corrrectly, you don't want the ssh service to be running when you are not using it.
zero2toy said:
Hello All,
This is my first post so here goes.
I simply need to get rid of the USB Mode notification when Nook Tablet is connected via USB to my Windows 7 PC so I can navigate device.
I have done a ton of research to get ADB working on the Nook and was having tons of problems with Windows XP and drivers. Moved to Windows 7 32-bit PC. Now I have Nook Tablet provisioned for USB Debugging and ADB sees the device. Now all I need to be able to do is plug the Nook Tablet into my PC via USB and not have the USB Mode notification appear. I need to be able to navigate the device while it is connected to PC via USB and recognized by ADB. Does anyone have any insight on how to remove this USB Mode notification when I plug my NT to my PC?
What I have:
NON-ROOTED Nook Tablet Software version 1.4.3
Provisioned for USB Debugging
ADB recognizes device and I can see it with no problems.
Thanks,
Click to expand...
Click to collapse
As Vector said, it's more difficult due to you not being rooted and on the stock OS. On ICS/JB you can simply change the storage connection type.
Have you tried just pressing the 'n' key? I don't remember myself, but it seems logical that since pressing Home on an Android phone when that screen pops up will take you back to the home screen that the 'n' key would do the same.
Why do you need to navigate the device when connected to your PC? What are you trying to do over ADB when not rooted? Most of the commands I'm aware of (while extremely limited) center entirely around typing 'su' as the very first thing you do. You must have root for that to work, though.
Jedi mind reading
Something that my significant other is still trying to teach me that I haven't fully grasp yet. I'm still at if you tell me to get you a "German Poodle" then I will get you a "German Poodle"
liquidzoo said:
As Vector said, it's more difficult due to you not being rooted and on the stock OS. On ICS/JB you can simply change the storage connection type.
Have you tried just pressing the 'n' key? I don't remember myself, but it seems logical that since pressing Home on an Android phone when that screen pops up will take you back to the home screen that the 'n' key would do the same.
Why do you need to navigate the device when connected to your PC? What are you trying to do over ADB when not rooted? Most of the commands I'm aware of (while extremely limited) center entirely around typing 'su' as the very first thing you do. You must have root for that to work, though.
Click to expand...
Click to collapse
liquidzoo said:
As Vector said, it's more difficult due to you not being rooted and on the stock OS. On ICS/JB you can simply change the storage connection type.
Have you tried just pressing the 'n' key? I don't remember myself, but it seems logical that since pressing Home on an Android phone when that screen pops up will take you back to the home screen that the 'n' key would do the same.
Why do you need to navigate the device when connected to your PC? What are you trying to do over ADB when not rooted? Most of the commands I'm aware of (while extremely limited) center entirely around typing 'su' as the very first thing you do. You must have root for that to work, though.
Click to expand...
Click to collapse
Yes I have tried pressing the n Key, no dice. I am trying to use screencast.jnlp to project my nook onto my PC monitor. Then show people how to use the Nook on a big screen. But when I am plugged into my PC USB port, this notification prevents me from doing anything on the device until I unplug the USB cable.
So I rooted my NT with Brianf21's root process. Thank You Brianf21! I thought these rooting processes were going to get rid of the BN operating system and turn it into a standard tablet. It did not and I was able to keep the BN modified OS and have another OS that looks just like a phone.
So I Tapped the Home icon in lower left hand corner(looks like 4 houses), selected Quick Switcher, then Selected ADW Launcher. This brought up a typical Android phone type home screen. I then pressed apps, scrolled to NT Hidden Settings and tapped it. I then selected Run ADB Daemon As Root/Turn Off Auto Mount For Session. This turned on USB Debugging and allowed me to get rid of the USB Mode notification while USB is connected to PC.
Issues with displaying nook screen on PC:
Trying to display nook screen on my PC with screencast.jnlp:
I'm trying to screen cast the nook's display screen with screencast.jnlp, I am connected via ADB and ADB sees the device. When I start screencast.jnlp is sees the devices but all I get is a white screen? I can click on the White screen and it selects whatever app or icon is in that part of the screen on the device and I can control my nook from my PC. I just cannot get the display from the nook to show on my PC. :crying:
Trying to display nook screen on my PC with Android Screen Capture:
ADB starts and sees device. I start Android Screen Capture and it sees device but I get nothing, just a Android green guy icon. :crying:
Is there anyone out there that has successfully displayed a Nook Tablets screen on their Windows 7 or XP machine? Any help is greatly appreciated.
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