Database Info

help! phone is busted

my phone seems to be in a really weird state right now - turning it on does absolutely nothing but adb does in fact detect it.
Code:
List of devices attached
HTXXX device
and if i run 'adb reboot recovery' i see the device in recovery mode.
Code:
$ adb reboot recovery
$ adb devices
List of devices attached
HTXXX recovery
also, while in recovery i can do adb shell and attempt to do a nandroid backup, but i get:
Code:
$ adb shell
~ # nandroid backup
E:unknown volume for path [/sdcard]
Can't mount /sdcard
at this point i've called htc to send it in for repair, but i would really like to get a backup before that and also return it to S-ON. i was running the latest clockworkmod and android revolution.
any help would really be appreciated.

Have you tried flashing an RUU?

yes, it keeps failing when trying to reboot into the bootloader. i've given up at this point - will be sending it back to htc and just hope they don't charge me some ridiculous amount just because i have s-off through the revolutionary script.

segfault82 said:
also, while in recovery i can do adb shell and attempt to do a nandroid backup, but i get:
Code:
$ adb shell
~ # nandroid backup
E:unknown volume for path [/sdcard]
Can't mount /sdcard
at this point i've called htc to send it in for repair, but i would really like to get a backup before that and also return it to S-ON. i was running the latest clockworkmod and android revolution.
any help would really be appreciated.
Click to expand...
Click to collapse
Is by any chance you phone connected as disk-drive? Try connecting it as charge only.

well the problem is the screen doesn't turn on so i can't see what's going on. although i'm pretty sure it's not connected as a disk drive because it doesn't automatically enable that.

[Q] Bootloader gone, only adb, not fastboot

Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?

RVexx said:
Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?
Click to expand...
Click to collapse
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate

JoinTheRealms said:
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
*
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
*
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate
Click to expand...
Click to collapse
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.

RVexx said:
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.
Click to expand...
Click to collapse
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.

JoinTheRealms said:
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.
Click to expand...
Click to collapse
Anyhow, thanks for thinking with me
I'll wait for someone who absolutely loves CWM

[Q] Display broken, trying to wipe data, ADB Shell commands not working

I dropped my phone and cracked the screen. I get nothing on the display when I turn it on. The phone is rooted with TWRP and EMBRYO 6.11 custom ROM installed. Two things I want to do: backup the internal sdcard and wipe everything.
I got ADB working and was able to copy everything from the sdcard. It was couple of days later that I found time to work on it again to try to wipe everything. I reconnected the phone and ADB sees the device, but it seems to be in some jacked up state that is preventing me from running most SHELL commands - possibly my toolbox has been deleted.
Code:
C:\AndroidSDK\platform-tools>adb shell
sh-3.2# ls
ls
sh: ls: command not found
sh-3.2# mount
mount
sh: mount: command not found
sh-3.2# su
su
sh: su: command not found
sh-3.2# wipe
wipe
sh: wipe: command not found
At this point, I just want to delete my data and the contents of the internal sdcard and somehow verify it's all deleted....without a screen. Any ideas?
Thanks.

flash stock firmware w/odin, hardest part would be to get it into dl mode, when doing the procedure feel for the vibration and release the volume keys then press the + volume button then see if odin flashes the firmware, the flash should wipe a non stock rom but not sure about embryos since its based on stock,
if I have time I might test this out or unless someone else can confirm this

I thought about that, but wasn't sure if odin would wipe the sdcard, and I was afraid it would leave me without usb debugging enabled so ADB would no longer work. I see there's an option in odin to "Re-partition", but it also says in your NEWB GUIDE: DO NOT! CHECK "REPARTITION"
Can I use the odin re-partition option for what I'm doing? I really don't care if I brick the phone, I just want to wipe it clean in case I try to sell it as-is, or trade it in or get it repaired.
Thanks for you help.

dwestall said:
I thought about that, but wasn't sure if odin would wipe the sdcard, and I was afraid it would leave me without usb debugging enabled so ADB would no longer work. I see there's an option in odin to "Re-partition", but it also says in your NEWB GUIDE: DO NOT! CHECK "REPARTITION"
Can I use the odin re-partition option for what I'm doing? I really don't care if I brick the phone, I just want to wipe it clean in case I try to sell it as-is, or trade it in or get it repaired.
Thanks for you help.
Click to expand...
Click to collapse
from ages ago I read that repartitioning will brick the phone, but yes you will lose adb, pretty sure anyways, but since you lost adb it wont matter, sdcards are not touched by odin, if you want to brick it try flashing a original s2 firmware, I think that's what newbs did by mistake, if it does flash properly and has no signs of life then you bricked it
or keep trying adb as im no expert on it
edit: maybe a usb hdmi dongle to a monitor will work,

dwestall said:
I dropped my phone and cracked the screen. I get nothing on the display when I turn it on. The phone is rooted with TWRP and EMBRYO 6.11 custom ROM installed. Two things I want to do: backup the internal sdcard and wipe everything.
I got ADB working and was able to copy everything from the sdcard. It was couple of days later that I found time to work on it again to try to wipe everything. I reconnected the phone and ADB sees the device, but it seems to be in some jacked up state that is preventing me from running most SHELL commands - possibly my toolbox has been deleted.
Code:
C:\AndroidSDK\platform-tools>adb shell
sh-3.2# ls
ls
sh: ls: command not found
sh-3.2# mount
mount
sh: mount: command not found
sh-3.2# su
su
sh: su: command not found
sh-3.2# wipe
wipe
sh: wipe: command not found
At this point, I just want to delete my data and the contents of the internal sdcard and somehow verify it's all deleted....without a screen. Any ideas?
Thanks.
Click to expand...
Click to collapse
Hit it with a hammer 5x

dwestall said:
I thought about that, but wasn't sure if odin would wipe the sdcard, and I was afraid it would leave me without usb debugging enabled so ADB would no longer work. I see there's an option in odin to "Re-partition", but it also says in your NEWB GUIDE: DO NOT! CHECK "REPARTITION"
Can I use the odin re-partition option for what I'm doing? I really don't care if I brick the phone, I just want to wipe it clean in case I try to sell it as-is, or trade it in or get it repaired.
Thanks for you help.
Click to expand...
Click to collapse
It will hard brick the phone.
Sent from my HTC One using Tapatalk 4

Try checking the path for packages used by adb.
If you've already figured out setting up the adb environment and connecting it I suggest cleaning up and re-deployment of packages.
And if you don't have time and feel like wasting a perfectly functional logic board try the "hit it with hammer x5".
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Ok, not sure I want to hard brick it or physically damage it anymore than it already is since I may try to sell it. I decided to try odin (without re-partition).
I was able to get the phone into dl mode an odin the stock firmware ATT JB 4.1.2 I727UCMC1. The phone boots now and I can actually hear the att start-up sound. Very cool!
I was hoping maybe the Kies client would see it, but no go. Oh well, I'm going to leave it at that.
This is all pretty basic stuff, but a bit of a challenge without a display. So, thanks for all your help.

Nexus 5 with dead flash memory?

I went to use my Nexus 5 (D821) earlier today but it wouldn't turn on. Holding power didn't seem to work, so I assumed the battery was flat and left it charging for a couple of hours. Now it gets stuck at the first black and white "google" logo forever. The device is unlocked and rooted, but was working fine, and nothing was changed leading up to the issue.
I'm able to access the bootloader and fastboot still, but nothing seems to work.
Attempting to flash a partition (fastboot flash recovery twrp.img):
FAILED (remote: flash write failure)
Attempting to erase a partition (fastboot erase userdata):
FAILED (remote: failed to erase partition)
I can boot TWRP by running fastboot boot twrp.img, but attempting to mount any partitions results in errors such as:
E: Unable to find partition size for /system
E: Unable to mount /system
Also, attempting to install a zip shows that internal storage is 0MB in size.
At this stage, I suspect the flash memory has died a horrible death, and I'm trying to work out how to set the tampered and unlocked flags back to false to I can return it under warranty, however this is proving difficult too. If I run 'fastboot oem lock', it appears to succeed (the bootloader even changes to 'LOCK STATE - locked'), but as soon as I reboot the device, it reverts back to unlocked, and the padlock shows up again.
I've even tried manually via:
echo -ne "\x00" | dd obs=1 count=1 seek=16400 of=/dev/block/platform/msm_sdcc.1/by-name/misc
echo -ne "\x00" | dd obs=1 count=1 seek=16404 of=/dev/block/platform/msm_sdcc.1/by-name/misc
but these don't seem to have any effect on the flags.
So now I'm out of ideas, and just hoping I can set these flags back before sending the device for warranty. Any ideas?

There's nothing you can do about it now. Just send it back. I doubt they'll blame flash memory failure on unlocking the bootloader
Sent from my Nexus 5 using Tapatalk

I was helping a guy yestreday, he had a some problem like you. When you turn on the phone, the flashchip shuts off for some reasone. I was looking for the mmc or mmcblk device in the /dev then /dev/block after I booted a twrp like you, but I could not find any device called mmcblk or mmc, even the partitions was missing like mmcblk0p1 etc...
cat /proc/partitions just give me an empty screen, that it didnt find any storage device.

rootSU said:
There's nothing you can do about it now. Just send it back. I doubt they'll blame flash memory failure on unlocking the bootloader
Click to expand...
Click to collapse
I'm just a little worried they'll refuse to honour the warranty without even bothering to check the hardware. Aren't they within their right to do this given the warranty terms? Sounds like I don't have any choice!

bitdomo said:
I was helping a guy yestreday, he had a some problem like you. When you turn on the phone, the flashchip shuts off for some reasone. I was looking for the mmc or mmcblk device in the /dev then /dev/block after I booted a twrp like you, but I could not find any device called mmcblk or mmc, even the partitions was missing like mmcblk0p1 etc...
cat /proc/partitions just give me an empty screen, that it didnt find any storage device.
Click to expand...
Click to collapse
I'm seeing a bunch of partitions listed when I run 'cat /proc/partitions', so I guess my issue might be a little different.
What I'm confused about though, is if the NAND flash is truely dead, how does the bootloader run? Isn't this stored on the same NAND flash chip? Also, aren't the lock state and tamper flags on the same chip? If so, how are these still accessible, but not writeable? I'm guessing it's not a complete failure, but only a partial one... Thoughts?

It surely isn't fully dead. It could be a corrupt partition or bunch of partitions being the issue. But the bootloader also isn't fully functional as you cannot relock it.
You definitely need to reset tamper flag for RMA, but for warranty, don't they have to prove that the hardware fault was caused by the unlocked bootloader? I know Samsung refuse warranty on modification but I don't think Google do. It is a developer phone after all.
That said, you've no choice as I can see. I'm not aware of anyone having warranty rejected or approved with an unlocked bootloader yet

sir_earl said:
I'm seeing a bunch of partitions listed when I run 'cat /proc/partitions', so I guess my issue might be a little different.
What I'm confused about though, is if the NAND flash is truely dead, how does the bootloader run? Isn't this stored on the same NAND flash chip? Also, aren't the lock state and tamper flags on the same chip? If so, how are these still accessible, but not writeable? I'm guessing it's not a complete failure, but only a partial one... Thoughts?
Click to expand...
Click to collapse
Can you post the outpot for the cat /proc/partitions command?

rootSU said:
I know Samsung refuse warranty on modification but I don't think Google do. It is a developer phone after all.
Click to expand...
Click to collapse
I'm not sure if the process is different here in New Zealand. I was under the impression LG deals with warranty issues here, and Google isn't involved?

bitdomo said:
Can you post the outpot for the cat /proc/partitions command?
Click to expand...
Click to collapse
I'll have to take a photo, as I can't find any way to run adb or save the log off. Give me a minute!

sir_earl said:
I'll have to take a photo, as I can't find any way to run adb or save the log off. Give me a minute!
Click to expand...
Click to collapse
you can do the whole thing with adb from your pc.
you need the naked usb drivers for that, and if you running windows 8 or 8.1 you have to turn off driver signiture enforcement inorder to isntall the drivers.
and then with adb shell command you can use your cmd window on the pc as a terminal window on your phone

bitdomo said:
you can do the whole thing with adb from your pc.
you need the naked usb drivers for that, and if you running windows 8 or 8.1 you have to turn off driver signiture enforcement inorder to isntall the drivers.
and then with adb shell command you can use your cmd window on the pc as a terminal window on your phone
Click to expand...
Click to collapse
adb was working with the Nexus when the rom was booted, but can't seem to find the device when running TWRP or fastboot (not sure if the server can run there?) Will the naked usb drivers resolve this issue?
Regardless, I've attached the photo with the partitions.

sir_earl said:
I'm not sure if the process is different here in New Zealand. I was under the impression LG deals with warranty issues here, and Google isn't involved?
Click to expand...
Click to collapse
google are only involved in that all this is done on behalf of them. They commission the phone. But the mandate is that it's a developer phone

rootSU said:
google are only involved in that all this is done on behalf of them. They commission the phone. But the mandate is that it's a developer phone
Click to expand...
Click to collapse
That's somewhat comforting. We shall see how it goes! Not looking forward to being without a decent phone for however long the warranty process takes though!

sir_earl said:
That's somewhat comforting. We shall see how it goes! Not looking forward to being without a decent phone for however long the warranty process takes though!
Click to expand...
Click to collapse
Please do let us know how you get on. It will be interesting to confirm how the unlocked bootloader goes down.

sir_earl said:
adb was working with the Nexus when the rom was booted, but can't seem to find the device when running TWRP or fastboot (not sure if the server can run there?) Will the naked usb drivers resolve this issue?
Regardless, I've attached the photo with the partitions.
Click to expand...
Click to collapse
Yes naked drivers will help you, but keep in mind that fi you are running windows 8 or 8.1 you have to turn of driver signiture enforcement.
Could you mount the system partition?
$ mount -o rw /dev/block/mmcblk0p25 /system
$ cd /system
and try to make folder like
$ mkdir asd
and then remove it
$ rm -rf asd
if that works we can write the flash chip, so it must be some kind of partition corruption.

bitdomo said:
Yes naked drivers will help you, but keep in mind that fi you are running windows 8 or 8.1 you have to turn of driver signiture enforcement.
Could you mount the system partition?
$ mount -o rw /dev/block/mmcblk0p25 /system
$ cd /system
and try to make folder like
$ mkdir asd
and then remove it
$ rm -rf asd
if that works we can write the flash chip, so it must be some kind of partition corruption.
Click to expand...
Click to collapse
I'm able to use adb now, so that's a start.
Trying to mount with the command you gave gives:
mount -o rw /dev/block/mmcblk0p25 /system
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument

sir_earl said:
I'm able to use adb now, so that's a start.
Trying to mount with the command you gave gives:
mount -o rw /dev/block/mmcblk0p25 /system
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
Click to expand...
Click to collapse
for me this command works.
I use twrp 2.6.3.4

bitdomo said:
for me this command works.
I use twrp 2.6.3.4
Click to expand...
Click to collapse
Running same twrp here, so I guess it's failing because it can't mount the partition due to some kind of corruption.

rootSU said:
Please do let us know how you get on. It will be interesting to confirm how the unlocked bootloader goes down.
Click to expand...
Click to collapse
Will do. I'm curious though, if random corruptions like this can occur, isn't it possible that the bootloader could appear unlocked if it's reading a corrupt piece of memory? If that's the case, they can't just assume the user has unlocked the bootloader in cases where the flash chip fails, correct? Granted, this isn't the case here, but it must have some impact!

sir_earl said:
Running same twrp here, so I guess it's failing because it can't mount the partition due to some kind of corruption.
Click to expand...
Click to collapse
I don't know what else you could do. You can try to lock and reset tamper flag by mmcblk0p15 and not with ...../by-name/misc, if it works probably you could not unlock your bl again.
Try to lock bl and reset tamperflag (adb shell):
echo -ne "\x00" | dd obs=1 count=1 seek=16400 of=/dev/block/mmcblk0p15
echo -ne "\x00" | dd obs=1 count=1 seek=16404 of=/dev/block/mmcblk0p15
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
sir_earl said:
Will do. I'm curious though, if random corruptions like this can occur, isn't it possible that the bootloader could appear unlocked if it's reading a corrupt piece of memory? If that's the case, they can't just assume the user has unlocked the bootloader in cases where the flash chip fails, correct? Granted, this isn't the case here, but it must have some impact!
Click to expand...
Click to collapse
bl lock state and tamper flag stored at the misc partition, so bl can read it but ti seems it fails to write it, i don't know the reasone why, but it seems tha path to the partitions by-name is missing

Is there a way to delete/uninstall an APK and its data from fastboot?

so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!

nextelbuddy said:
so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!
Click to expand...
Click to collapse
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.

Lethargy said:
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.
Click to expand...
Click to collapse
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.

nextelbuddy said:
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.
Click to expand...
Click to collapse
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk

rootSU said:
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully

nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
It could say "device busy" if data is already mounted. Does twrp have a "mounts and storage" menu like CWM? Where you can mount data? If so, check if it is mounted there (would typicall say "unmount data" if it was mounted, otherwise it would say "mount data" if it is unbmounted)

nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID

nextelbuddy said:
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID
Click to expand...
Click to collapse
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.

rootSU said:
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.
Click to expand...
Click to collapse
Thanks so much for your help
I ended up taking the leap and performing a Factory reset from TWRP and when I logged back into the phone I saw all my media was still present Whew.
just for posterity I went ahead and tried your code in ADB to make sure the quotes worked and it did so thank you very much and i will keep those notes handy for next time.