Database Info

Nandroid Backup, HELP

Hello everyone,
I have succesfully rooted my Sprint Hero, I am even using a cache app that you have to be rooted to use so I KNOW I am rooted. The only problem is NO MATTER WHAT I try I can not successfully flash the recovery img. It shows as flashing ok but when I go to boot in recovery it either flashes the HTC sign real quick then dies or stays on the HTC screen and doesnt do anything. Ive literally been trying this for 2 days now! Ive rerooted 10 times, Ive tried as many different recovery imgs for CDMA that I could find and I STILL get the same result. I even switched sd cards!! Could there be a problem with my phone thats not allowing it to work? Someone please help this is driving me nuts! Im ready to return the phone and get a new one just to try it,LOL!!PPlease help??

What images have you tried?

Just ones Ive found around the internet. Most of them were recovery-RA-heroc-v1.2.3.img

How are you trying to install it?
Flashrec?
flash_image?

Anyone??? Please?????Im about to return it and try again Id hate to find out it was something simple cuz this Hero has been perfect except for this problem, which is pretty useless to have it rooted if I cant flash, And I wont be able to update if sprint has an update also correct??

packetlss said:
How are you trying to install it?
Flashrec?
flash_image?
Click to expand...
Click to collapse
I follow f directions online that I go into cmd and get to the root and type" flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img, when I hit enter all that happens is it shows exactly what I typed AGAIN then just #
So it will look like this:
#flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
#
Then when I type reboot recovery it just reboots and shuts off, so Ill pull the battery and try the hardware method power volume down and it does THE SAME thing or it will just stay stuck on the HTC screen.

Do it like that.
then then use the:
"reboot recovery" command on the # prompt. See if that helps.

packetlss said:
Do it like that.
then then use the:
"reboot recovery" command on the # prompt. See if that helps.
Click to expand...
Click to collapse
Ya I did that, same thing happened. ):

One last try.
Redownload the the image from this post: http://forum.xda-developers.com/showthread.php?t=581521
Download md5sum.exe from this site: http://www.etree.org/md5com.html
Save it in them in same folder as you have the adb command in.
Then from the command line run:
md5sum recovery-RA-heroc-v1.2.3.img
It should output something like this:
0bdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img (Don't forget to copy it to the sdcard again )
Bolded text is the checksum of the file, it should match perfectly or your image is damaged.
If the checksum is the same, try flashing it again.

ahh i see clearer now.....
yes as suggested in the last thread you posted in... do a sprint RUU and try agian... this will put you at a known good baseline.... follow steps exactly...
as a added measure to cancel the option of bad sd card, get an external micro sd card reader and format it in windows as fat32

johnsongrantr said:
ahh i see clearer now.....
yes as suggested in the last thread you posted in... do a sprint RUU and try agian... this will put you at a known good baseline.... follow steps exactly...
as a added measure to cancel the option of bad sd card, get an external micro sd card reader and format it in windows as fat32
Click to expand...
Click to collapse
I actually already formatted to fat32,lol. How do I flash RUU??? To start over?

packetlss said:
One last try.
Redownload the the image from this post: http://forum.xda-developers.com/showthread.php?t=581521
Download md5sum.exe from this site: http://www.etree.org/md5com.html
Save it in them in same folder as you have the adb command in.
Then from the command line run:
md5sum recovery-RA-heroc-v1.2.3.img
It should output something like this:
0bdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img (Don't forget to copy it to the sdcard again )
Bolded text is the checksum of the file, it should match perfectly or your image is damaged.
If the checksum is the same, try flashing it again.
Click to expand...
Click to collapse
Where do I input that? Once I get in root?
I did adb shell
$su
#md5sum recovery-RA-heroc-v1.2.3.img
it says md5sum not found

No, md5sum in run before you do the adb shell command (it's a normal PC program).

aaron130 said:
Where do I input that? Once I get in root?
I did adb shell
$su
#md5sum recovery-RA-heroc-v1.2.3.img
it says md5sum not found
Click to expand...
Click to collapse
windows command line not adb shell.... make sure you are in the directory in which you downloaded md5sum

obdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img
thats what happened Good??

That is the correct checksum.
Try and flash that one.

Nope Same DAM thing it gets stuck at htc or htc then quits and shuts off

I'm out of ideas then. Could be that it's broken, unless someone else has the same problem. (Haven't seen any of that though).

packetlss said:
I'm out of ideas then. Could be that it's broken, unless someone else has the same problem. (Haven't seen any of that though).
Click to expand...
Click to collapse
Thx Im flashing the RUU now. Thx for your help though I appreciate it alot!!

Recovery Problem.

I have problem with CWM v5.8.3.4, while i flash, restore, back, everything it still back to recovery mode, can`t do nothing.

CWM v5.8.3.4 -- Here is your problem, you used ROM manager to update recovery. There are red flags on this pretty much everywhere Dx
You've gotten into the bootloop, see my PERI tool (Link in sig) and try and run the bootloop-fix there, if you can get adb working. You can also try it manually (Again, adb permitting) in roach2010's recovery touch thread, he provides the fix there.
If you can't get adb working at all, you need to NvFlash back to stock, wheelie thread is again in my signature.
Good luck.
--
By the way, you can get back into Android by Cold-booting the system. Hold volume-down, then press power and keep holding volume-down till it boots. Don't press volume-up or anything else, that'll put you back into recovery.

I was tryin` but while i want to flash someting apx turning off and can`t do nothing :/ Erm, how to fix can`t use my tablet about 1 month

Hi,
have you tried coldbooting ?
Hold power and volume down. Should get you out of recovery.

Yes, i do mate, and can`t do nothing. It dont see sd card and tablet memory :/

Okay I have the same problem, i used the cursed Rom Manager and now im stuck in the endless boot cycle, I can cold boot and I have tried to flash roachs cwm but nothing. Ive read where roach gives a code that might fix it, but i have no ideal what to do with that code or how to use it, and i see where thing o doom said the fix is in his signature but im not having much luck with that either. If you could maybe explain to me how im supposed to use roaches code or post the link that explains it here, I would sure appreciate it. Thank you.
Sent from my Transformer TF101 using XDA Premium HD app

Any ideas please? :/

Start an adb shell session with your computer connected, or in a terminal app on your tf, then run roaches fix (type it in) to the terminal app/adb shell session.

"then run roaches fix" u mean write app/adb shell session ?
And now i got another problem:
"E: Can`t mount /sdcard/
Biggest problem for now, i can`t turn on debuging :/

okay I opened terminal emulator on my tablet and typed in roaches fix exactly like it says
adb shell dd if=/dev/block/mmcblk0p3
and this popped up
*daemon not running. starting it now on port 5038*
*daemon started successfully*
error: device not found
255 [email protected]:/ $
what am i doing wrong? thank you so much for your continued help
Ive also tryed the peri and easy recovery with no luck, I think my bigest problem is i dont understand the adb thing, ive tryed searching about it and im lost.

That's the wrong dd command, dd consists of an if=/ then an of=/
Try this.
adb kill-server
adb start-server
adb devices
(you should see the tf, if not, bad drivers/not working connection, fix that first)
adb shell
su (Grant superuser permissions, if you can, and you'll see a # sign)
dd if=/dev/zero of=/dev/block/mmcblk0p3
reboot
Then flash a new recovery by:
Download and extract recoveryblob from recovery.zip
adb kill-server
adb start-server
adb devices
adb push C:\path\to\recoveryblob /sdcard/
adb shell
su (you'll get # sign again)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot

I have to thank you for your patience and continued help with my problem, but with that being said I must inform you that I am still completely lost. Im not a developer and I would not even consider myself remotely knowledgeable in the subject. I was just wanting a nice custom ROM and I had found one with cyanogen mod 9 but I messed up by using the Rom manager and now I'm screwed.
I can cold boot into my tablet, and on my tablet I have this computer emulator program, which i can type in the codes you mentioned, but I'm pretty sure that is not correct. what i need is a program like that on my computer, so far I found this link regarding adb, but I'm not sure if it is right direction.....
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
if this is the wrong direction, can you please point me in the right direction? again I am sorry for my ignorance and when this is all done I will be sure to buy you a freaking case of beer. Thank you

You can run the adb commands on your TF using the emulator app, but you'll need to directly download the recoveryblob used to flash.
Open terminal and run roach's fix (except instead of typing adb shell, you just start from su, then run the dd command from there, since you're already in the tf's 'shell')
so
su
dd if of etc
reboot
Then you'll need to reflash a recovery, so download Team Rouge's Recovery.zip then use ES file explorer app (download that) to extract the file called 'recoveryblob'. Take that file called 'recoveryblob' then copy it out of the downloads folder (still using ES file explorer) hit the favorites button then hit /sdcard/ (You don't need a microSD card to do this, /sdcard/ [For whatever reason ..] is the Internal storage. [/removable/microSD/ is the external]) then paste the recoveryblob right in /sdcard/.
Open up the terminal emulator and run
su
dd if=/sdcard/recoveryblob/ of=/dev/block/mmcblk0p4
reboot
That should give you recovery! (Then you can reflash a ROM or do whatever you need/Enjoy not having to cold-boot everytime)
Sent from my Tf101atron9000 using XDA Premium HD

Im stuck w8ing for You at Skype: )

Thanks for your info. TF now up and running without the need to cold boot. For information, I did not use a Rom Manager to flash the rom, I used CWM to flash the Gummy Rom.

I finally got my tf101 fixed and I learned something new. I just wanted to thank Thing of Doom for all of the help he offered me and without ever asking anything in return. Thanks.....

If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere

Thing O Doom said:
If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere
Click to expand...
Click to collapse
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.

datfinedude said:
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.
Click to expand...
Click to collapse
Sure if you'd like.

My Skype name is Datfinedude
Sent from my Triumph using xda premium

[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.

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.

Need to flash a TWRP backup with fastboot

Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks

eReader Fan said:
Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks
Click to expand...
Click to collapse
You would probably have better luck flashing the stock firmware or have someone with the same device create an adb backup then restore it via adb.
Or if you know which individual .img files you need, have them pull a copy of whichever individual .img files you need(for example: system, boot, etc) then fastboot flash them or use adb shell to dd the .imgs back onto your device in the partitions they belong in.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?

eReader Fan said:
@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?
Click to expand...
Click to collapse
Is USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Yes, debuggind mode is on. In PTP mode, adb sees my device correctly, in MTP mode appears like ???????

I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!

eReader Fan said:
I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!
Click to expand...
Click to collapse
This command in adb shell or Terminal Emulator should give you your partitions and names(obviously you'd type "su" then press enter then run this command)
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The part with "msm.sdcc.1" might be different for your device. If that command doesn't work I'll help you find what needs to go in that part of the command for your device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

su is not found inside the adb shell, and I found this is cause is not rooted. I have to do it through TWRP in android 6.
As I said, I have two devices of my model so I hope I find time tomorrow for doing it. I also hope to can flashing it to the other device in fastboot mode or some way it doesn't need the main screen (remember I have a LCD screen and a eInk)
I will say something when I do the root. Thanks

Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?

eReader Fan said:
Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?
Click to expand...
Click to collapse
adb shell should work to dd, you just need to make absolutely certain that you are dd-ing the correct .img to the correct partition(mmcblk0xx), the partition number would go where the xx is.
For example, my recovery.img would be flashed to mmcblk018(the number of my recovery partition.
If you dd an .img to the wrong partition, you'll brick the device, the command has to be exactly correct, no margin for error or easy fix if you get it wrong.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I know all this stuff, but first I need to make the .img of each partition, and I though with adb shell I could do a dd to outside the phone. The TWRP backup I have isn't .img files, they are .win files.
I searched again if its possible to do that and all I found is the xda thread about doing a workaround with adb forward and busybox. If there is no more options I will do that.
What I thought to do is create a backup of the needed partitions and save them in the userdata free space. I think this have to be possible, but as I cannot use the LCD screen I have to do the backup where I do not have to pass thorugh the first boot configuration, cause it is did in the LCD screen. Which partitions have I to backup? Only system and boot? Or there is another tool for creating .img backups?
EDIT: Also found the twrp adb possibilities (http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html) but have the same problems than with dd

I frequently modify boot and recovery partitions from within terminal app. Here's what I do to grab the boot partition for example(you likely want BusyBox installed first)
cat /dev/block/bootdevice/by-name/boot >boot.img
or
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Make changes, then reverse the commands to write back. I think cat gives you a more verbatim copy for initially cloning a partition. I have had success with both.
The question that brought me here is what happens if i flash all partitions from a firmware archive and attempt to upgrade a whole system this way from twrp recovery.....