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!!
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
Hey guys,
is it possible to access the internal storage via adb, without having a display?
My Galaxy SII Display is broken, but the rest should work.
usually i have to lock in with the security points that have to be connected (i dont know how that is called in english),
to allow access via usb.
now that the display does not work, i can not go that way.
so is it possible to access the internal storage via adb?
or do you have another way for me to get my data back?
i am not going to buy a new galaxy s2 and replacing the motherboard,
because its not worth it.
i have cm10.1 installed with dorimanx kernel, and root is allowed for adb and apps.
i never used adb, so i dont know how to start my search.
i also have the problem that i dont know how to look for that thing,
because im not english.
it would be nice if you can give me a start,
or another way to access the internal storage.
i also thougt about accessing via recovery.
i think i can go into recovery, and by pressing volume and power keys,
i can naviagte to mount data.
but im not sure about the steps,
so if anyone have a dorimanx 7.xx kernel,
can you please write the steps down for me?
thank you.
Grandtheftman said:
Hey guys,
is it possible to access the internal storage via adb, without having a display?
My Galaxy SII Display is broken, but the rest should work.
usually i have to lock in with the security points that have to be connected (i dont know how that is called in english),
to allow access via usb.
now that the display does not work, i can not go that way.
so is it possible to access the internal storage via adb?
or do you have another way for me to get my data back?
i am not going to buy a new galaxy s2 and replacing the motherboard,
because its not worth it.
i have cm10.1 installed with dorimanx kernel, and root is allowed for adb and apps.
i never used adb, so i dont know how to start my search.
i also have the problem that i dont know how to look for that thing,
because im not english.
it would be nice if you can give me a start,
or another way to access the internal storage.
i also thougt about accessing via recovery.
i think i can go into recovery, and by pressing volume and power keys,
i can naviagte to mount data.
but im not sure about the steps,
so if anyone have a dorimanx 7.xx kernel,
can you please write the steps down for me?
thank you.
Click to expand...
Click to collapse
if you can mount in recovery then mount everything in recovery,connect your device to PC and the open command prompt and navaigate to folder where you have set up android sdk.
now do the following
1) adb shell
2) now type ls -it'll list all folder and files.
3) now navigate to your sd-card (can't tell exact name for internal sd card) by typing cd <directory name>
4) you can list all files by using ls command.
5) Once you find the exact directory name of sd card and files to be recovered then type exit
6) now type adb pull /path/to/your/folder/filename.File will be saved in working directory...
i don't have s2,just helping you with some common adb stuffs.
btw you can use adb file managers which provides GUI.Like this one http://forum.xda-developers.com/showthread.php?t=1821601
adb
Connect the phone to system, Open terminal and do adb remount then adb shell.
Now do ls, you will be able to see all the folder and everything. Go to Sd-card folder and there you should have all your data.
There is and app ADBExplorer. I have never used this tool, but you can check it is GUI.
Thanks,
The ADBFileexplorer worked very well for me.
Just booted in recovery and started the explorer.jar in the adb folder.
Thank you for the tips.
This can be closed now
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