Develop Bugs

Busybox?

Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help

It comes with A2SD - but you can push the busybox binary to /system while the phone is in recovery.
If you pushed bb yourself, use its absolute path (like /data/somewhere/busybox) or put its path in your $PATH to get it going. I personally, without root, put busybox in the free-to-write-to /sqlite* directory (I put * because I don't recall the full name) and it runs fine from there.

do you have a link to apps2sd & does it come with a guide as to how to install it so noobs can understand?

A2SD was taken down "temporarily".
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
Sorry

Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/

LeszekSwirski said:
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
Click to expand...
Click to collapse
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.

GANJDROID said:
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
Click to expand...
Click to collapse
You didn't read to the end of that thread
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Click to expand...
Click to collapse
By what I've read, though, Metamorph dies on its arse because of the lack of system rw access.

Loccy said:
You didn't read to the end of that thread
Click to expand...
Click to collapse
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)

jayshah said:
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
Click to expand...
Click to collapse
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'

GANJDROID said:
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
Click to expand...
Click to collapse
Yeah, hence it's hopefully only temporary.

GANJDROID said:
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
Click to expand...
Click to collapse
Install Titanium. Then get your phone into recovery using Paul's Linux ISO. In the Linux console (i.e. where you'll have typed ./step2.sh to get the recovery up), you should be able to do adb shell from there. Then follow my instructions from mount /system onwards.

I didn't follow Pauls guide as I only have access to Windows, so I used the lanarchy guide, which I think might have been taken from The Unlockr.
Maybe fill me in w/ bb according to that?

i am a bit ashamed to ask this but:
....
* boot into recovery
* adb shell from my Mac
* mount /system
....
boot into recovery -> ok
adb shell from mac.. ok? hm, i have macos as a seperate installation and i used it for rooting, so there is a pushfiles folder with recovery-mac.sh.. sudo ./recovery-mac.sh?
How do i mount /system then? Don't know where to navigate to find access to the sdcard . @volumes there are only my harddrive partitions, can't see the sdcard?
No idea, sorry, first time (ok, second time after root) i get in touch with adb, mac, sudo wtf?

Ok, all you need is some kind of environment where adb actually works.
Get your phone into recovery (the green menu screen) using whatever means or method you have.
Then, if you have Windows, you'll need the Android SDK. Ditto on a Mac. Anything with adb so that you can plug your device into your computer, do adb shell, and get a shell window up. Then
mount /system
onwards.
The key is that your phone needs to be in recovery before you do adb shell, otherwise you have no r/w access to /system.

ah! ok, perfect. The android sdk is on my windows computer, the push-files on my mac, that's the problem
thanks for your help!
the recovery is not the problem, but mount /system did nothing because there is no android sdk on my mac.. got it now i think.

mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?

same problem as watercool. Loads of "No such file or directory" messages.
But, I rebooted and it went through as normal, booted the OS fine.

hm, dont want to wipe again, pff..
flashed AhmgskMod mod again without wiping, everything ok now

watercool said:
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
Click to expand...
Click to collapse
Sounds like you missed the . off of the end of the
./busybox --install -s .
command.
You need that . if you're following my instructions.

ok, i did it with and without the "."
With the dot there was no response (so probably it installed correctly?).
Anyway it didn't boot afterwards. i will try it again
edit: ok, tried again and my phone stucks @ htc screen
i think busybox is installed but for some reason it doesn't boot (using the ahmgsk mod)
anyway, thanks for your kind help!

[HOWTO] Complete Linux rooting guide (from stock to custom and back)

This post will no longer be updated and is pretty much for the archives at this point. It detailed the rooting process for Linux users right after the Slide was first rooted. Since then, newer, more foolproof methods have been devised. For those rooting their phones today (or any point since T-Mobile's OTA update), please see this link: http://forum.xda-developers.com/showthread.php?t=780213. It says it's Ubuntu-specific, but the instructions there should apply to any GNOME desktop and any other desktop with slight modification. Thanks for the comments on this thread. I hope it helped.
Most of this is not new information, but it's all in one post for the first time. I post it in case Linux (and probably MacOS) users need clarification on the process. It should keep people from having to dig in deep threads to find all the info needed. I only added the loop.sh for Linux and the partitioning information.
For all the following, I assume that the reader knows how his computer works, but not necessarily Android rooting.
Preliminary Information
1. As always, make backups and take notes. You might want to make a list of installed apps you want to reinstall later, for example.
2. Install adb. Download it here: http://developer.android.com/sdk/index.html. adb is a little program distributed as part of the Android software development kit (SDK). Its job is to communicate with the phone from a shell (terminal). To install adb, I strongly suggest you copy the adb file from the tools directory into your system's /usr/local/bin directory. This way, it will always be in your path. If you don't intend to do development work on Android applications, feel free to delete the rest of the SDK after installing adb.
3. Start adb as root. In more traditional Linux distros, this can be done by typing "adb devices" in a root terminal ("su" then "adb devices"). In Ubuntu-based distros, "sudo adb devices" followed by your password should do the trick. You'll get a message about the adb daemon being started. If not, sometimes typing "adb root" or "adb start-server" as root will do the trick.
4. Make sure your phone has "USB Debugging" checked off in Settings > Application > Development
5. It may not make any difference, but I turn off the "disk drive" option, so that my SD card doesn't mount when the phone is plugged in via USB (unless I need it to).
Partitioning the SD Card (Optional)
This is an optional step, as ROMs are coming out now that allow swapsace (virtual memory) and apps2sd (installing applications to the SD-card rather than on the phone's internal memory). Right now, most Slide ROMs support apps2fat32, so the whole card can be left as is (one, big, fat32 partition). If your desired ROM supports apps2sd using an ext2 or ext3 partition, you can save some headache later by doing this step first. If you don't want it, just skip to the next section.
1. Using the package manager for your Linux distro, install parted. GNOME users have a great, graphical frontend to this utility called gparted. KDE users have the KDE Partition Manager available to them. I only have gparted, but the instructions should be similar for all variants. The graphical frontends take a lot of the pain away from using parted (automatically formatting for ext4, for example). For the braver souls, there is a much more detailed tutorial for using vanilla parted from the command line here: http://forum.xda-developers.com/showpost.php?p=4098568&postcount=1.
2. Mount your sd-card, either using the "disk drive" function of the phone, or in an external card reader.
3. Make a backup of your sd-card by simply copying and pasting to a new folder.
4. Start up the partition manager of your choice with root permissions (using gksu or kdesu).
5. Make sure your desktop environment (KDE or GNOME) or a terminal doesn't have a file manager window open to the sd-card partition. You can't unmount a partition that's being accessed.
6. Find out which device node is assigned to the partition by typing "dmesg" in a terminal. The last few lines should tell you how it's assigned. Mine was /dev/sdg1, for example.
7. Using the dropdown menu, select your sd-card partition in parted.
8. Right-click on the partition in the bottom pane of the window and select "unmount".
9. Delete the partition using the same, right-click menu.
10. Now you're left with free space to configure as you see fit. You use the same right-click menu to create partitions.
11. When done, click "apply" and the partition manager will create and format the partitions you've selected.
12. When done, the computer should mount two partitions from the card, one for apps, the other for user data. Copy your backed-up files to the larger partition.
NB: Android phones can work with a smallish ext* partition at the beginning of the card for apps (around 512MB should be more than enough for almost anyone), a super-small swapspace in the middle (no more than 32MB, if any at all--it's up for debate whether the Slide benefits from swapspace at all), and the rest of the card formatted as FAT32 for the "normal" partiton. I'll leave those decisions to those who have the need and desire. Also, whether to use ext2,3, or 4 for the apps partition is a matter for debate, and some kernels for other phones didn't support the newer versions at all. All that is beyond the scope of this howto, mainly because I won't be trying it out.
NB2: Eugene has released Koushik Dutta's recovery scripts that can help automate the partitioning process. It can be done directly from recovery, rather than on the computer. I much prefer the old way, as it gives more flexibility. For reference, the post with instructions is found here: http://forum.xda-developers.com/showpost.php?p=6993132&postcount=1.
Getting root (original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1)
The following instructions are "the old way" to gain root. There is a new method found at: http://forum.xda-developers.com/showpost.php?p=7658764&postcount=1 that seems to be a saner process, but I have not tested it as of yet.
1. Download the Slide Root package: http://outboundlink.us/anxo/dr_ta_1...ttp://www.4shared.com/file/IfrPbWG7/Root.html
2. Extract it somewhere convenient (I'm using the Desktop folder here. I'm also renaming the folder "slideroot" to keep things simple).
3. Open a terminal and cd to the slideroot folder you just created.
4. The "loop.bat" file here is of no use to you. Use a text editor to make your own loop.sh file, or edit loop.bat and rename it when you're done. It should contain the following:
Code:
#!/bin/sh
watch -n .50 adb devices;
done
5. Power on the slide while holding down the Volume-down button. This will bring you to the bootloader screen (three droids on skateboards). Plug the Slide in via USB.
6. Just to make sure everything is working correctly, type "adb devices" in the terminal to make sure the system is seeing your phone properly. If so, run your loop.sh by typing "sh loop.sh".
7. Use the Volume-down button on the phone to select "recovery" and press the power button to enter. The terminal will flash a few messages like "offline" and "recovery". When the phone's screen shows an icon of a phone with a red triangle, you know it worked.
8. Press Volume-up and Power together to enter the recovery menu on the phone.
9. Now, back in your terminal, hit "ctrl-C" to cancel the loop.sh script.
10. Type "adb push ota.zip /sdcard/update.zip" and hit enter.
11. Type "adb push update.zip /sdcard" but DO NOT hit enter yet.
12. This step requires some coordination and timing. On the phone, select "run update.zip" and press the power button. When you see a little greenish progress bar at the bottom in the background, hit enter in your terminal.
13. If it worked as planned, the phone will see the keys from the first file you pushed, and then use the file you're pushing now to run clockwork recovery. If not, don't worry. Just repeat. I haven't had to do it more than once yet.
14. Once this is done, reboot the phone from the menu system and wait. You can use "adb devices" in the terminal to see if the phone is detected.
15. Type "adb shell" and look for the "$" prompt. If you type "su" you should get a "#" (root) prompt. Give yourself a pat on the back.
Installing the Engineering ROM (original HOWTO at http://forum.xda-developers.com/showpost.php?p=6821968&postcount=1)
A. Now that your phone is rooted, you can "downgrade" it to the Engineering ROM. This gives a better recovery environment that allows other ROMs to be installed (custom ROMs are signed with the test keys; the original recovery will not install them since it looks for your carrier's keys.)
B. Download two files: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/OsmF_ZD7/ESPRIMG.html and http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html.
C. I extracted the SlideEng-package.zip, copied the contents inside loose to the Desktop, and copied the ESPRIMG file to my sd card.
1. cd to the Desktop and type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
3. Start an adb root shell as above ("adb shell" then "su")
4. Type "cd /data/local"
5. Type "chmod 04755 mtd0.img" and "chmod 04755 flash_image". I didn't change any permissions on the other files in that folder, just in case.
6. Type "./flash_image misc ./mtd0.img" and hit enter.
7. Power off the phone.
8. Holding Volume-down, power the phone back up. The recovery will scan the sd card and automatically detect the update file (from step "C" above) and prompt to install it. Hit Volume-up to install.
9. You're done. Just reboot the phone after the update and you're good to go. The boot process will be a little longer this time around.
Updating the Radio (May be optional) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6856313&postcount=1)
I leave this section here for archive purposes. Since switching the ROM to ChiefzReloaded's OTA in the "Installing a custom ROM" section below, this step is no longer necessary, as it contains the newest radio. Unless you're installing a custom ROM released before the last T-Mobile over-the-air update, feel free to skip this section.
When we downgraded the system to the Engineering ROM, we downgraded our radio as well. The following instructions will bring us back to the stock radio version.
1. Download the following file: http://files.androidspin.com/downloads.php?dir=chiefzreloaded/ROM/&file=Newest_Slide_Radio.zip and copy it to your sd-card.
2. Remember that update.zip way back in the rooting section? The one found in the slideroot package? Copy it to your sd-card as well, if it's not already there. I deleted the one on my sd-card and re-copied it, just in case. It contains the clockwork recovery and can be left on your sd-card for future upgrades.
3. Reboot the phone into recovery (should be easy now.)
4. Select "apply update.zip from sd card" to start clockwork recovery. No looping necessary anymore!
5. From the clockwork menu system, apply the Newest_Slide_Radio.zip file you just copied over.
6. Once that's done, just reboot. The boot process will take longer and you'll see a few crazy icons before the system finally loads up. When all is finished and you're back to the home screen, the phone will pop up a dialog telling you the update was successful.
Installing a Custom ROM (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6827968&postcount=1)
For this install, I'm using the new OTA update rooted by ChiefzReloaded. Complete information on this ROM is here: http://forum.xda-developers.com/showpost.php?p=7534163&postcount=1. Like the older SLIDEMEROOT2 I had here before, I picked it because it's mainly the same, stock ROM the phone shipped with, but with root. I had way too many "fast, stable, feature-packed" custom ROMs on other phones that really weren't that fast or stable. I don't want to lose the use of my camera/camcorder to have live wallpapers, for example. These instructions will work for any custom ROM (adjusting for the new ROM in step 1 and 4.)
1. Download the following file: http://db.androidspin.com/androidspin_filedownload.asp?release=330&type=1 and copy it to your sd card.
2. Boot the phone into recovery mode.
3. From the recovery menu, select "apply update.zip from sd card". As stated earlier, this update.zip file contains the clockwork recovery. Applying it like an update will always load clockwork from now on.
4. In the clockwork menu, select "apply any zip from sd card" and select CR_Mod_1.35.531_OTA.zip.
5. Let the update take its course, reboot, wait, and enjoy.
Going Back to Stock (Just in case) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6994424&postcount=1)
There may come a time when you might need your phone just the way it came from the store. It could be that you're tired of custom ROMs, a feature you find you can't live without is broken, or you need to return the phone for warranty purposes. If it gets to that point, here's how:
1. Download the following file: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/x7HRRsbM/ESPRIMG_2_.html and copy it to your sd-card.
2. Reboot the phone into recovery (just the regular one, not clockwork). The file will be automatically detected.
3. After checking the file, you'll have to hit Volume-Up to confirm the flash.
4. Once done, reboot and the Slide will be good as new.

Very nice!
I kind of wish I would have seen this before I rooted this morning!

I just rooted mine this afternoon. Figured I'd put it up while I still had it in my head.

Excellent summary!
I also wish I'd seen this before muddling through the other guides myself. Thanks for posting it!

Quick question. I plan on rooting my MyTouch Slide within the next couple days. I was just reading over your list and thought I'd try to move the adb file first. After I moved it to /usr/local/bin, and then opened a root terminal. I typed "adb", but nothing came up about a dameon being started. It looked like I had asked for the man page. Any idea why? Or if it started it anyway?

The first time you run adb, do so as root "sudo adb devices", "sudo adb root" or the equivalent. It will start the daemon. A normal user (ie, not superuser) will not have the permissions to start a daemon.
When you run just "adb" without any options, it shows you the command-line options you can use with adb. Most Linux command-line apps work the same way when run without options.

beartard,
huge props to you. this is, by far, the best guide for rooting anything that i have ever used, and certainly for the slide.
as mac osx is a *nix system, this worked great. none of the steps were missing, everything was a normal sized font, and left justified, and took me from the stock to a custom rom flawlessly.
thanks a bunch.
really.

I'm very glad it worked for you. Thanks! Did you have to do anything differently under MacOS? I used to use it before OS X came out. I know the newer versions are based on *nix, but I didn't know how similar they were underneath.

I didn't do very much differently.
I started with "How to get Root" section, as I didn't want to partition my sdcard and already had the SDK installed (obviously, though I really need to look into working with it more, as right now it scares the bejesus out of me).
I used a "do while [1]" style (I love accidentally rhyming) loop.sh file though, mostly because my terminal couldn't understand "watch" for some silly reason.
Your guide was just the one that felt the least like a tween myspace page (no offense to the other guides).

Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.

sultan.of.swing said:
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
Click to expand...
Click to collapse
I'm not sure what the problem is, man. I've never had to try more than once using the process above. You're using a new install of ubuntu. Do you have adb from the latest sdk?

Just added the link to a new method for rooting and updated a few minor points.

Updated partitioning info to reflect what's actually going on in the MT3GS world.
Changed custom ROM to ChiefzReloaded's OTA, eliminating the need for the "updating the radio" section.

Beartard, I want to say thank you for taking the time for typing this all out. It worked like a charm with not one problem. I have spread your link to others so they can get the same satisfaction I got from this thread. Thanks again

Broke my screen & need to copy files HELP

I dropped my phone, and the screen now is a steady grey.Glass is fine, but just a grey screen when its on. I have insurance so getting a new phone. The problem is I have photo's and videos that I really want to keep, but cause my screen is broke, I can't mount the drive to copy it over.
How do I copy the files if I can't mount it in disk mode? Is there a way to mount the the phone storage on my PC via adb so that I can copy mile files off. They are on the phone storage so I can't just pull the SD drive and copy them. HELP!

go to setting and change the default connection type.

are you savvy with ADB?
If so, then all you need to know is what clicking pattern during bootup will get you to a position to use adb from your PC.

zeke1988 said:
go to setting and change the default connection type.
Click to expand...
Click to collapse
??? As I said, the screen is grey, completely greyed out. looks like a fuzzy TV. there in no way to choose anything.

luvit said:
are you savvy with ADB?
If so, then all you need to know is what clicking pattern during bootup will get you to a position to use adb from your PC.
Click to expand...
Click to collapse
Clicking pattern? you can't use ADB with the screen locked. The screen is completely non fuctional. no way to do any pattern., but I did not have a lock pattern anyway. I didn't think you needed the phone unlocked like that to use adb?

No. Sorry. I ment the click pattern to booting to recovery.. I think ADB from recovery will be useful if you can explain the following:
-Are you rooted?
-What recovery do you have installed? (clockwork mod?)
-and do you have the android SDK on your pc which contains the ADB files? (this is why I asked if your experienced with ADB)

adb works while phone is locked to me. of course maybe that's because usb debugging is enabled. well anyway here are a few ways I can think of to help:
1:
adb pull /emmc/DCIM/ .
That will copy all internal pictures/videos to the location where adb is on your computer ("tools" folder). Do NOT forget the period at end of command!
2:
Get into ADB, either from normal power on, or in recovery.
adb shell
cp -r /emmc/DCIM/* /sdcard/DCIM/
That will copy internal pictures and videos to sdcard

Cracked Screen.

Ok long story short i was getting the Power button mishaps. So i banged my phone to fix it worked great a few times but last night while doing so i cracked my screen Stupid move ever lol. KIDS DONT TRY IT !!!!
Its all black now and i want to be able to retrieve my pics on the phone.Cause when i connect it to my PC it does nothing just charge.
How can i so since i cant see nothing?

Broken screen
Colombia81er said:
Ok long story short i was getting the Power button mishaps. So i banged my phone to fix it worked great a few times but last night while doing so i cracked my screen Stupid move ever lol. KIDS DONT TRY IT !!!!
Its all black now and i want to be able to retrieve my pics on the phone.Cause when i connect it to my PC it does nothing just charge.
How can i so since i cant see nothing?
Click to expand...
Click to collapse
Did you save your photo's on your internal storage or on an external SD? If you saved them externally you can put your Micro SD in a flash drive and pull it up that way.

Or if for some reason you do not have access to an sdcard adapter you could use adb and pull them from the phone from a terminal.
Sent from my SGH-T989 using xda premium

bseager said:
Did you save your photo's on your internal storage or on an external SD? If you saved them externally you can put your Micro SD in a flash drive and pull it up that way.
Click to expand...
Click to collapse
codecaine21 said:
Or if for some reason you do not have access to an sdcard adapter you could use adb and pull them from the phone from a terminal.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Most of the are on my internal SD ... How would i go using ADB method ?

Colombia81er said:
Most of the are on my internal SD ... How would i go using ADB method ?
Click to expand...
Click to collapse
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
This will pull all files ending with the jpg extensions. You can of course pull whole folders.
I just wrote that off the top of my head and it wasnt tested. I have to get to bed. I have to get up at 4:30am for work and it is now 11:30. Damn computer is so addicting! The one liner might not work but you get the point. Google adb pull and adb push.

codecaine21 said:
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
This will pull all files ending with the jpg extensions. You can of course pull whole folders.
I just wrote that off the top of my head and it wasnt tested. I have to get to bed. I have to get up at 4:30am for work and it is now 11:30. Damn computer is so addicting! The one liner might not work but you get the point. Google adb pull and adb push.
Click to expand...
Click to collapse
Thanks the issue will be to see if im on recovery mode since i cant see nothing

Colombia81er said:
Thanks the issue will be to see if im on recovery mode since i cant see nothing
Click to expand...
Click to collapse
A friend had the same issue a few weeks ago and I just popped her battery out and popped it back in. Then held the power + vol up + vol down till i felt vibration and held on for another 2 seconds. Then waited 20 seconds just to be safe. I connected my phone. I ran sudo adb devices in a terminal to make sure it was connected. Which is was and then ran the necessary commands.
Sent from my SGH-T989 using xda premium

codecaine21 said:
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
Click to expand...
Click to collapse
Yeah that didnt work its in recovery now. Im trying to figure this out i just dont want to d/l the pics. I dont mind backing up the whole entire thing. How would i go on doing that.

Colombia81er said:
Yeah that didnt work its in recovery now. Im trying to figure this out i just dont want to d/l the pics. I dont mind backing up the whole entire thing. How would i go on doing that.
Click to expand...
Click to collapse
That's a tough one... for me at least. I mean you are able to reboot into recovery but I am unaware of a method that will allow you to back your system up from a terminal. Adb has a backup command but you need to be able to see your screen to use it.
You could use the dd command over ssh ->
Code:
[B]sudo adb shell dd if=/dev/block/mmcblk0 | sudo ssh [email protected] "dd of=/~/Documents/recovery.img"[/B]
and check the progress with
Code:
[B]while true; do readarray -t array < <(pgrep -l '^dd$'); var=$(echo "${array[@]}" | sed 's/ dd//g'); kill -USR1 $var &>1 && sleep 5; done[/B]
but I "think" the FAT32 FS is limited to 4GB file transfers. So you will receive an error after 4GB's and the transfer will abort. Also, I am unsure of the t989's pit layout. Which blks you would need to backup if you did decide to dd single partitions. Like cache, system, recovery, boot, etc.
Maybe some computer whiz will be able to help you. I am sorry I couldn't help. Maybe one of the more experienced Linux/android users/devs can help you if you haven't already figured this out.
If someone did know, it would be cool if you could post the solution. I am curious as how to one would go about doing this.
Sent from my SGH-T989 using xda premium

codecaine21 said:
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
Click to expand...
Click to collapse
Im hoping you are still around for some more assistance. Im actually in the middle of the same issue as OP, except possibly that the phone was completely stock with android debugging disabled, and the touch interface is also non-functional. You'd think that would be great for getting stuff off the phone, but I was unable to use the on screen menu to actually turn on usb mass storage.
I decided to try and use push / pull from recovery, however I found out that the directories I want arent available in recovery mode (DCIM / Download with a very very important 0000001.vcf in it).
I was able to get into recovery and use "adb reboot download" and Odin'd "recovery-cmw-hercules.tar" to the phone to give me a working CMR environment (v5.0.2.6). I thought I could feel my way through the menus after another "adb reboot recovery" to blindly guess - Vol Down x 6, Pwr x 1, Vol Up x 2, Pwr x1 - type thing, to navigate"mounts and storage" and then find "mount sdcard".
However, I have been unsuccessful. I did manage to mount system / data / cache , just not sdcard, and I dont know why.
TLR No screen, no touch. Odin'd CMR. Am sitting in Command Prompt with ADB Shell / Pull working. Still can't access ~/DCIM folder on internal SDCard. Hoping for some help. What am I missing? Bonus: A screen shot of the CWR mounts and storage menu would be very helpful!

Ok so i got it....
So I first used this comand:
Code:
adb shell find / -name "*jpeg"
It gave me this
/sdcard/Download/155546_394801767258170_1181721421_n.jpeg
Then i used this command to pull everything from my internal sd-card
Code:
adb pull sdcard C:/Docs
Worked like a Charm

[Q] Samsung GT-I5510 display cracked, trying to recover files

Hello fellas,
I've ran out of ideas at what to do. My old GT-I5510 got screen cracked and in order to recover my files, memo app and calendar app data in particular (both stock), I tried to root it with KERUK to gain access to /data where it should be stored, but it's no use when I don't see what I'm doing in recovery mode. ADB does communicate but only in recovery mode, otherwise I believe USB debugging is needed, which I did not enable before it got screen cracked. In fact, /data is not accessible at all ("opendir failed, Permission denied"). The backup command from ADB does not work (supposedly without root) either ("adb: unable to connect to backup"). I also tried to copy everything with "adb pull / C:/recovered-files/" which started copying all the files from accessible folders but aborted as soon as it tried to open a restriced path/file. I checked all of the subfolders and none seemed to have write permissions. /sdcard seems to be accessible but inside there are no files shown through the ADB shell although the SD card definitely has stuff on it.
What should I do? Thank you so much in advance!

I'm not quite sure, but am I even posting in the right forum? Seems that noone knows even a tip for this. After all, my "guest thread" (http://forum.xda-developers.com/general/xda-assist/samsung-gt-i5510-display-cracked-trying-t3132014) was answered right away. Sorry for double post, but I thought this possible misunderstanding needed a push for people to see.

I think the forum is correct, there are only a few people using a Galaxy 551 left now, and I presume all of them have rooted their device at an earlier stage.
If you canNOT "su" in an "adb shell" in normal operation mode, you could still attempt to find the mount points, and run the necessary mount commands when rebooted into (CWM; or TWRP - I'm pretty sure stock recovery won't do anything you'll need) recovery. Check that you're having superuser status by running "id" (which should return UID zero).
You probably will be more successful if you could copy everything to the SDcard (which has to be mounted by hand), either using "tar" or "rsync" (that one can be found in several places).