Database Info

[Q] USB through recovery?

Just wondering, is there any way to access the internal sd card on your computer when in recovery mode? i know in older cwm recoveries this was possible by just mounting usb storage... why has this feature been removed?
I downloaded experimental build #4 of cm9 in the short while that it was released for and ended up being stuck on the boot animation forever so i cannot access usb by booting up the system. also, i deleted the old experimental build #3 off of my sd card before flashing so i can't flash back to that unless its on the card! Being stupid and too trustworthy of the build that it would work, i made no backup and that has left me in my current predicament.
Any help is appreciated and all ideas are welcome! i can still boot into fastboot mode and i have an old nandroid system backup on my computer and i can boot into recovery (either cwm or twrp, i have been able to install both at separate times so am willing to use either to fix the problem).
Thanks!

Use adb to push it.
adb push rom.zip /sdcard/rom.zip
Sent from my Incredible 2 using Tapatalk 2 Beta-5

prototype7 said:
Use adb to push it.
adb push rom.zip /sdcard/rom.zip
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
i am in cwm recovery, but when i try this, it just says device not found. any specific way to start adb once in recovery?
EDIT: i can access adb from the boot screen, but when i try and push, it says error: read-only file system

klinkdawg said:
i am in cwm recovery, but when i try this, it just says device not found. any specific way to start adb once in recovery?
EDIT: i can access adb from the boot screen, but when i try and push, it says error: read-only file system
Click to expand...
Click to collapse
Try going into fastboot and use "fastboot flash zip rom.zip"
Sent from my Incredible 2 using Tapatalk 2 Beta-5

Nexus S touchscreen died - how to get data off the phone?

My daughter's Nexus S touchscreen has died. It died slowly in that on the first few occasions she couild pop the battery and it would come back. Now it won't come back at all and is stuck on the pattern lock screen.
Before we send the phone for repair under warranty she is keen to get the photos off the phone since a repair might reset the phone. I was thinking we could mount the phone as a USB device but it doesn't show up perhaps because it won't until the pattern lock is entered else anybody could get data off your phone bypassing security.
Any other things we could try before giving up and hoping the repair doesn't delete all the data?
Thanks

Boot into recovery, make a nand then extract data through adb?

adb pull /sdcard/path-to-whatever

Can you explain the path to whatever? Like if I want it in folder "A" on the desktop.
Sent from my Galaxy Nexus using Tapatalk 2

Check this thread
http://forum.xda-developers.com/showthread.php?t=1573744

treUse said:
adb pull /sdcard/path-to-whatever
Click to expand...
Click to collapse
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)

lchiu7 said:
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)
Click to expand...
Click to collapse
ADB "thought" you meant to copy a file.
To copy the entire sdcard directory you should do something like this:
Code:
adb pull /sdcard/ sdcard/backup/on/pc/
The command parameters are "adb pull <source> <destination>"
Just make sure source ends with a /

Maybe a Windows based software?? Droid Explorer, very useful.. http://de.codeplex.com/ :good:

Well I finally got the phone to play with. The screen indeed dead. I installed the Google USB drivers from the SDK and also the Samsung drivers.
When I boot the phone into the recovery menu I can run fastboot devices and see the following
????0AC4B09900?? fastboot (of course the ? are not there but I wanted to anonmyuse the serial)
So far so good.
In device manager under Android Phone it show Samsung Android ADB Interface
But if I try adb devices I get nothing.
Forgot to mention my daughter said USB Debugging was turned off but I am not sure that makes any difference and anyway, we can't boot Android to turn it on
So I select Recovery and see the Android with the exclamation mark. Windows beeps to indicate that some sort of devices has been installed,
But in Device Manager no phone shows which explains why adb can't fidn the phone but not why.
I can bring up the recovery menu but still no adb
Any suggestions?
Thanks

Boot into Fastboot and flash CWM Recovery.

RL77LUC said:
Boot into Fastboot and flash CWM Recovery.
Click to expand...
Click to collapse
But it looks like I have to unlock the bootloader to do that and the phone is still under warranty so that would invalidate the warranty wouldn't it? She would like to get the data off the phone. A screen fix shouldn't zap the memory but you never know.

what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage

cukdus said:
what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage
Click to expand...
Click to collapse
The phone is stock

lchiu7 said:
The phone is stock
Click to expand...
Click to collapse
If you unlock the bootloader to flash CWM your memory will also be wiped, so you will loose all the photos you want to save, so don't do that.
Also if you have the USB debugging off, the ADB commands won't work. I'm afraid you're SOL, since you have the bootloader locked you can't flash a kernel with USB host, that would allow you to use a mouse to navigate in the phone and since you don't have USB debug you can't pull files from the "SDcard"... Better take it to the store and try to ask them if they can save the photos before they do anything to the phone, but i guess if it's a digitalizer problem, they won't mess with the NAND.

Check out http://www.moborobo.com/ and see if it works for you.
If you have root you have extended functionality, like control the device from the PC. But if i recall correctly, even without root you should be able to get your files.

[Q] Nexus S touchscreen unresponsive, need to recover files

Hi there,
I have already checked following post in order to get files of my phone:
http://forum.xda-developers.com/showthread.php?t=1775148&highlight=touchscreen
I am currently running CM10.1 (nightly 2013-03-23) with a lock screen pattern.
Connecting the phone to the computer via USB doesn’t show the content in windows explorer.
Mounting USB storage in recovery (CWM 6.0.2.5) fails.
In ADB the device shows as offline due to Android 4.2.2 security system.
The only chance I see is using fastboot command and pull the corresponding folder from the sd-card.
Your help would be much appreciated.
Thanks
Daniel

ddsouza said:
Hi there,
I have already checked following post in order to get files of my phone:
http://forum.xda-developers.com/showthread.php?t=1775148&highlight=touchscreen
I am currently running CM10.1 (nightly 2013-03-23) with a lock screen pattern.
Connecting the phone to the computer via USB doesn’t show the content in windows explorer.
Mounting USB storage in recovery (CWM 6.0.2.5) fails.
In ADB the device shows as offline due to Android 4.2.2 security system.
The only chance I see is using fastboot command and pull the corresponding folder from the sd-card.
Your help would be much appreciated.
Thanks
Daniel
Click to expand...
Click to collapse
I hope I don't sound too noobish, but can't u just pull battery, go to recovery & flashback to an older ROM that didn't have lock screen so u can retry both USB Mount and ADB?
Good luck
Vs Nexus S4G using tapatalk2

[Q] I've really messed up my phone, can't seem to install stock ROM now

How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!

Euskadi said:
How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!
Click to expand...
Click to collapse
Disclaimer : I have not used TWRP recovery on Moto G. So may have errors in my post
You have 2 options.
1. On some versions of TWRP, under advanced you have an option to mount USB. You can the access the phone as a drive from a computer.
2. Use ADB to push file to the phone. Install drivers and ADB works in recovery,

Thanks I actually found out about the adb push thing just after making this thread. I was able to push Beanstalk onto the device and install it through TWRP, however it's just stuck on the Beanstalk bootscreen forever. I tried installing it again and the same thing is happening. This also happened earlier when I tried to install Cyanogenmod

Once when i wanted to flash Stock 4.3 i got also stuck in bootanimation.
To restore Stock i had to execute flashall.bat /eu. The option /eu erases userdata. Once i did this my phone booted without any issues.
So what you can try is to erase userdata via fastboot or cwm
fastboot erase userdata
Click to expand...
Click to collapse

onyinly made
I tried one final Hail Mary before going to be last night, erased all data and installed Cyanogenmod again and I'm pleased to say it worked!
Only downside is I've lost all my apps & data. Now I did back these up using Titanium, and stored them on Google Drive, however the reason I got into this mess in the first place is because I manually flashed the 4.4.2 update, which worked ok, but then when I restored my apps/data with Titanium my soft buttons (back button etc) disappeared!
I guess I'll just play it safe and not try to restore the back up this time.

M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Sent from my HTC Desire C using XDA Premium 4 mobile app

the sarge said:
M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Click to expand...
Click to collapse
Not exactly an expert myself but look for a download of 'Fastboot', it should have a program called adb.exe or abd-windows.exe. Turn on your phone while holding the Volume Down button and it should start into the bootloader screen, plug in the USB and it will say it's connected.
Then you go to the folder (on your PC) that has adb.exe - put your ROM .zip into this folder - then hold shift and right-click somewhere inside the folder (not on a file) and choose "Open command window here".
Then you just type "adb push ROM.zip /sdcard" where ROM.zip is the name of the zip file. note: you might have to type adb-windows instead, depends what .exe you have
Then just wait until it finishes transferring. Will take 30 secs or so for a 200mb ROM.
I'm sure if you google "adb push" you'll get some better instructions, with downloads etc

While reverting to stock it's important to use mfastboot(moto-fastboot) instead of normal fastboot. Download mfastboot.exe and place in adb folder, and replace 'fastboot' commands with 'mfastboot'
Sent from my XT1032 using XDA Premium 4 mobile app

Or try supertool on root junkies download site worked for me to get o t a kit kat
Sent from my Moto G using XDA Premium 4 mobile app

Someone smashed my phone with a rock. (data recovery ?s)

Greetings et al,
Backstory: I climb large granite walls and my phone was left part way up and a party following found my phone and decided to smash the crap out of the screen. They left it on prominently displayed along a trail on a rock and someone else I knew found it and returned it to me.
Device: Google Pixel 3
Status: Screen smashed to bits, but I can power it on and see it in "adb devices" etc...
So it was this past Sunday that the scalawags smashed my phone. Saturday I had taken my daughter and son-in-law on their first ever large/multi-pitch rock climb, 600ft. plus. Unfortunately I had no downloaded the pictures of that event nor the videos.
* I don't know how to get this device in MTP mode so I can transfer the data w/o a screen
* I tried to shell to it and I get "error: insufficient permissions for devices"
* Does anybody have any suggestions on what path I should head down to attempt to pull the files off this thing?
-Thanks in bunches for any and all replies...

nemanator said:
Greetings et al,
Backstory: I climb large granite walls and my phone was left part way up and a party following found my phone and decided to smash the crap out of the screen. They left it on prominently displayed along a trail on a rock and someone else I knew found it and returned it to me.
Device: Google Pixel 3
Status: Screen smashed to bits, but I can power it on and see it in "adb devices" etc...
So it was this past Sunday that the scalawags smashed my phone. Saturday I had taken my daughter and son-in-law on their first ever large/multi-pitch rock climb, 600ft. plus. Unfortunately I had no downloaded the pictures of that event nor the videos.
* I don't know how to get this device in MTP mode so I can transfer the data w/o a screen
* I tried to shell to it and I get "error: insufficient permissions for devices"
* Does anybody have any suggestions on what path I should head down to attempt to pull the files off this thing?
-Thanks in bunches for any and all replies...
Click to expand...
Click to collapse
Since you don't have USB debugging enabled and can't swipe the screen to unlock the lockscreen, there aren't really any options for you other than replacing the screen or sending the device to a professional shop to see if they can retrieve the data from the hardware by pulling it directly from the chip.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Since you don't have USB debugging enabled and can't swipe the screen to unlock the lockscreen, there aren't really any options for you other than replacing the screen or sending the device to a professional shop to see if they can retrieve the data from the hardware by pulling it directly from the chip.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do have USB debugging enabled.

nemanator said:
I do have USB debugging enabled.
Click to expand...
Click to collapse
Ok then, you might have an option. If there is a TWRP custom recovery for your specific model number, TWRP natively supports adb so it should work. You don't have to root but you can try flashing TWRP recovery on your device and then boot into TWRP then connect to PC and use adb with the "adb backup" command to backup all user data then extract the data that you want from the backup.
To find instructions for adb backup, do a google search for:
"ADB backup/restore"
Find the command to backup user data.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Ok then, you might have an option. If there is a TWRP custom recovery for your specific model number, TWRP natively supports adb so it should work. You don't have to root but you can try flashing TWRP recovery on your device and then boot into TWRP then connect to PC and use adb with the "adb backup" command to backup all user data then extract the data that you want from the backup.
To find instructions for adb backup, do a google search for:
"ADB backup/restore"
Find the command to backup user data.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I'm getting device unauthorized at this point so now adb doesn't work. I'm not sure what changed to cause that. It was working. I had/have twrp installed. I tried a "flashboot boot twrp.img". I had to temp boot like this when I was rooting this thing. The fastboot flash w/ twrp.img bricked the phone. Anyway, after a flashboot boot twrp.img. adb devices lists nothing. So either it's not booting twrp.img successfully or I'm missing something.

nemanator said:
I'm getting device unauthorized at this point so now adb doesn't work. I'm not sure what changed to cause that. It was working. I had/have twrp installed. I tried a "flashboot boot twrp.img". I had to temp boot like this when I was rooting this thing. The fastboot flash w/ twrp.img bricked the phone. Anyway, after a flashboot boot twrp.img. adb devices lists nothing. So either it's not booting twrp.img successfully or I'm missing something.
Click to expand...
Click to collapse
Ah, your bootloader is locked, that is probably why you previously had to boot a TWRP .img instead of flashing it. Now, I'm not sure it will boot anything. Try flashing a copy of stock recovery, then try the fastboot boot TWRP again.
Other than that, I think you might be at the end of your rope.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Ah, your bootloader is locked, that is probably why you previously had to boot a TWRP .img instead of flashing it. Now, I'm not sure it will boot anything. Try flashing a copy of stock recovery, then try the fastboot boot TWRP again.
Other than that, I think you might be at the end of your rope.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
The device unauthorized was from the windows machine. I'm back on the linux box and adb can see the device again. I've tried oodles of ways of getting mtp enabled.
When in adb shell and trying to find my photos/videos, I'm getting funky filenames.
sargo:/storage/emulated/0 # ls
+dn0VjXCwXIGBTRlAAdSqA NKZ4osL+U6zJbQICkOBoOB VqEBnQxs1hu4ncv3woVfCB kmOAbyd,bVAJDnQSbomLyA wXQ6rmjvahUKbZQtHof35D
7CdpRTZ8PchPMx4DOUvlLD OuATvxF3HNScfmEIoaabiB Ya0QbX5aki6BstVDxMXi5LRPcRD nZETC6WByAa5h7jO2tDyqC
I didn't have much success with mtp when my phone was screen was operational but at least I could see and navigate to the DCIM folder. I'm not sure why adb shell is rendering the files as such.

nemanator said:
The device unauthorized was from the windows machine. I'm back on the linux box and adb can see the device again. I've tried oodles of ways of getting mtp enabled.
When in adb shell and trying to find my photos/videos, I'm getting funky filenames.
sargo:/storage/emulated/0 # ls
+dn0VjXCwXIGBTRlAAdSqA NKZ4osL+U6zJbQICkOBoOB VqEBnQxs1hu4ncv3woVfCB kmOAbyd,bVAJDnQSbomLyA wXQ6rmjvahUKbZQtHof35D
7CdpRTZ8PchPMx4DOUvlLD OuATvxF3HNScfmEIoaabiB Ya0QbX5aki6BstVDxMXi5LRPcRD nZETC6WByAa5h7jO2tDyqC
I didn't have much success with mtp when my phone was screen was operational but at least I could see and navigate to the DCIM folder. I'm not sure why adb shell is rendering the files as such.
Click to expand...
Click to collapse
If adb is working, try this:
https://stackoverflow.com/questions/54959259/enable-mtp-using-adb
Or this:
https://forum.xda-developers.com/showthread.php?t=2786395
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If adb is working, try this:
https://stackoverflow.com/questions/54959259/enable-mtp-using-adb
Or this:
https://forum.xda-developers.com/showthread.php?t=2786395
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Well I believe I mucked it up worse. I used the command line to do a set persistent mode to mtp and forgot to add adb e.g. "mtp,adb"
I forget the specific syntax but it worked. I'm in MTP mode persistently but I'm not able to mount the device from windows or linux and both operating systems see the device.
I have no idea how I'm going to get back to adb mode.
Anybody have a clue as to why I cannot see the proper file names in /storage/... ?
Does MTP mode do some magic and decrypt the files or something?
They file names looked to be encrypted when I was able to get at the file system with adb.