[GUIDE] Backing up a phone with broken display

[GUIDE] Backing up a phone with broken display - Sprint Samsung Galaxy S III

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Hellua nice guide :thumbup:
TEAM MiK
MikROMs Since 3/13/11

Man Cnexus! You are everywhere! Lol.
Nice guide. This will save lots of people :thumbup:
------------------------
Sprint Galaxy S3 "Supernexus" Thanks To Cyanogenmod
Whiplashh Rom
Look it up.

Is this method specific to the S3? I have an old S2 that I need to recover some photos from.

Hmm...boot your S2 into recovery, then connect it to your computer, run the following command and post the output for me.
Code:
adb shell ls

Hopefully I never need this guide but I think it should be a sticky. Good job!

This seems very helpful thank you.
This is a good option as well
https://code.google.com/p/androidscreencast/

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Click to expand...
Click to collapse
Thanks so much for the how-to.
I have a rooted Sprint Galaxy S3 with a broken display. I'm having a problem with getting it into recovery mode.
I believe when I hold down VolUp+Home+Power and reboot, it's loading a menu that's prompting me to select one of the boot options. It otherwise just sits there and never actually boots.
I've tried to use adb to boot it into recovery mode, but it also just sits there until I press the home key, at which point it just boots into normal mode.
Is there a way I can bypass any menus or does anyone with a working system know which option I should select at the menu?
Thanks,
Alex

Is your display broken? What does "adb devices" show when you're in that mode?

Related

[GUIDE WITH VIDEO] ADB/Fastboot Easy 5 minute setup (Great for nOObs)

Ok there are some other guides here on the forums for this but they all require you to download the Android SDK. That can be very time consuming and confusing if you run into issues. I have been looking at a way to have the capability to push and pull files using my laptop but i really didnt want to go through downloading and setting up the whole SDK just to use adb.
If anyone has followed any of my threads, you know I am all about trying to get things done in the easiest way possable to help the people that are new to Android. This method has worked for me but there is no guarentee that it will work for you and I am no way responsable for anything that happens to anything unless it works great for you. Then I will take all credit j/k. With that being said:
The first method is for Windows based OS. I have tested it on XP but I would imagine it will work on any Windows OS. If I am informed of something different I will update it here. The Mac version is in post #2 and takes less than 1 minute to do. Much thanks to kwbdc and stlouie65 for the help on this.
Instructions for setting up Adb/Fastboot (windows)
1. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
2. Install drivers on your PC. This is done on the MT4G/HTC devices by going onto your sd card and clicking on the HtcDrivers.exe file while viewing the files on your PC. It should automaticly install them to your PC. If you are using another phone or have trouble installing the ones from your sd card you can try pda.net or HTC Sync for the drivers. Here are links for pda.net 32-bit Windows 7/Vista/XP and for 64-bit Windows 7/Vista. Install the program by hitting "Run" and follow the instructions. You can remove it at a later time.
3. Download the file at the bottom of these instructions to your desktop and extract the contents. There is 1 folder and a install note (these instructions) that should extract. You can use a program called 7-ZIP (google it, its free and a great tool).
4. Open your "Start" menu and click on "My Computer". Then choose "Local Disk C:".(You can now click and drag the adb folder you extracted to the C: drive.
5.Open a command prompt and type cd\adb and hit enter. You should now see something that looks like this C:\adb>
6.Type adb devices then hit enter in the command prompt and it should list your device.
7. You can also type fastboot devices then hit enter in the command prompt an it should list your device. (you must be in the bootloader for fastboot to recognize your device)( adb command= adb reboot bootloader )
You should now be ready to send commands to your phone via ADB or Fastboot. You will need to repeat steps 5-6 anytime you want to use ADB/Fastboot. To send a file using Adb or fastboot make sure to put the file in your "adb" folder before giving the command to send it to your device.
If this helped you please use the "Thanks" button to show your gratitude.
____________________________________________________________________
Please feel free to ask any questions you want and I will help in any way I can.
DOWNLOAD MIRROR
Here are some commands for Adb/Fastboot.
DO NOT USE ANY COMMANDS THAT YOU ARENT SURE OF OR DONT KNOW WHAT THEY DO. I AM NOT RESPONSABLE FOR ANYTHING THAT YOU DO TO YOUR PHONE.
ADB Commands
adb devices - list all connected devices
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections forward specs are one of: tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed
Click to expand...
Click to collapse
.
Fastboot Commands
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Click to expand...
Click to collapse

Mac Instructions
Download THIS FILE Extract the 2 files inside it and place them on your Macintosh HD root. Plug in your phone to the usb, open terminal and type /adb devices.
It should now give u a serial #
To send a file using adb/fastboot the file must be placed in your mac HD Root or you must give the location in your command path.

Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again

92drls said:
Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again
Click to expand...
Click to collapse
Not a prob...Please let me know if this works good for you.

Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?

92drls said:
Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?
Click to expand...
Click to collapse
Put the file you are trying to push in the same folder you created.
ReName it bootanimation.zip
To push your file use this command after you cd into the folder you created.
You also need to be in recovery with your system mounted.
adb push bootanimation.zip system/customize/resource/bootanimation.zip
That is the location of the bootanimation on that rom.
Hope this helped

Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again

92drls said:
Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again
Click to expand...
Click to collapse
I do know how to change it but would rather you have the fulfillment of learning how to do it yourself You can find a great guide and splashscreens in the thread by Iriscience. Make sure to thank him for it.
Back on topic, I'm glad this worked good for you. It really is pretty simple. I dont have have a donation link (I do this for the love of helping people mod their phone) but I would appreciate it if you hit the "Thanks" button at the bottom of any post that have helped you.

Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.

@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.

30Glock said:
@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.
Click to expand...
Click to collapse
geoffott said:
Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.
Click to expand...
Click to collapse
Thanks Guys, I appreciate the kind comments! My whole intention of this thread is to help people that couldnt or didn't want to set up the Android SDK have a good solid way of pushing and pulling files to their phone.

Great guide Drew! I'll finally be giving adb a shot! I've always been intimidated by it.
This helps for sure.
Sent from my HTC Glacier using XDA App

thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?

dominicanman912 said:
thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?
Click to expand...
Click to collapse
You must be in fastboot (bootloader) for fastboot to recognize your device. You can get there by by turning off your phone then holding down the volume down button and the power button at the same time. Our you can use this command via adb (usb plugged in):
adb reboot bootloader
Your device should automatically go into fastboot from the bootloader. If it doesn't you can scroll to fastboot using the volume button and hit the power button.

Thank you for answering my question! I have been reading a lot about adb over the past few days and I feel more comfortable with this way than the pain in the ass sdk method! When I get back on the pc, I will be sure to hit that thanks button because you have been a great help.
Sent From my ICE COLD HTC Glacier aka MyTORCH4G!

How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153

koolkid09 said:
How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153
Click to expand...
Click to collapse
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img

TrueBlue_Drew said:
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you so much!! I have been trying to do this for the past hour now! lol

Awesome post! Saved me a (potentially painful) convo with a friend who's just getting into modding his MT4G.

error
I feel like an idiot, idk what im doing wrong, in command prompt i get this message, 'adb' is not recognized as an internal or external command, operable program or batch file......what am I doing wrong?

[Q] Temporary Nand Unlock

How do you gain temporary nand unlock? All i wanted to do is copy 2 files into the /system/xbin/bb which doesnt seem to work with root explorer despite super user permission, copy paste just wont work.
Any ideas how to copy paste these 2 files without going to full s-off? Would the adb method work? or any other apk that can do the job?
Thanks in advance for those who can help and any tips is very much appreciated.

In recovery with adb.

TheGhost1233 said:
In recovery with adb.
Click to expand...
Click to collapse
any links to it? a guide perhaps? thanks for the tip.

Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.

TheGhost1233 said:
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
Click to expand...
Click to collapse
btw, how do i get to adb with recovery?

You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.

TheGhost1233 said:
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
Click to expand...
Click to collapse
many thanks! i will try this tommorow.

Use the update.zip I attached in this thread, you don't need to worry about adb then.
http://forum.xda-developers.com/showthread.php?t=885506&page=2
Sent from my HTC Desire using XDA App

Ghettonine said:
many thanks! i will try this tommorow.
Click to expand...
Click to collapse
Ok I did my best, read alot about adb and followed some tips but I just cant seem to get these things working. I need a DETAILED step by step procedure.
I feel such a noob today, can anyone please help?
Basically, I just wanted to copy "ifconfig" and "route" from "/system/xbin" to "system/xbin/bb" and thats it! Im s-on by the way and dont want a full s-off just to copy paste 2 files.
I tried rebooting in recovery with adb and run some commands on "adb shell", many things came out and I have no idea what it ment.

Well many things came out is not such a great description. So i have no idea if something is wrong or something happened which you did not expect.
Boot again in to recovery and connect adb.
The type "adb devices" this should output something like:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT##########
If this does not happen you don't have a connection and most likely have driver issues (only if you are on windows). If you do get a connection next thing to do is mount the system partition as read/write. To do this type "adb remount".
The output should be "remount succeeded"
Next type "adb shell"
This should give "#" as output .
Since you know where the files are and where you want them to go type "mv /system/xbin/ifconfig /system/xbin/bb" and hit enter, you don't get any conformation about this. Next type "mv /system/xbin/route /system/xbin/bb"
To check if they go moved correctly type " ls /system/xbin/bb", now you should see the files listed.
Next type "exit" to end the adb shell.
Then type "adb reboot".
If this doesn't work you need to give more info about the errors you get or maybe someone else has a better description.
A completly other method is, if you are able to copy the files to your computer, useing the .zip mercianary linked to, just make sure the system/app folder is empty and that you make the system/xbin/bb folder and place the files in there. Then just follow the instructions.

[Tutorial] Rooting Your Device in Linux

Root Galaxy Nexus (Either GSM or LTE) in Linux (Personally in Ubuntu)
Disclaimer: I am not at fault for anything you have done to your phone (ie. Brick, break, etc.). You are doing this at your own discression. I am merely stating what I did to unlock/root my phone.
Tutorial Broken Down Into Three Sections
I. Unlocking the bootloader
II. Installing Clockwork Mod Recovery
III. Installing SuperUser
Resources
1. Super User (used by flashing in Clockwork): http://download.clockworkmod.com/test/su.zip
You can get the latest version here: SuperUser by ChainsDD
2. Clockwork – based by carrier
1. Verizon (CDMA) version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.4-toro.img
MD5:*b2d31c29b7ef785f9c0802a12264d322
File size:*5,263,360*(bytes)
2. GSM version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.2-maguro.img
MD5:*445887336a863573997ccbaeedddc984
File size:*5,427,200*(bytes)
Unlocking Bootloader
Part 1: Unlock
1. First off, you need to download the adb drivers. There have been mentions of just getting the drivers, but I actually have the entire SDK. You can download it here. http://developer.android.com/sdk/index.html
2. Plug in your device, then open up Terminal (Ctrl + Alt + T) and type in: “lsusb” (without quotes). This will pull up all the devices plugged into your usb slots. Look for the one that says samsung (others have found google, but please make note).
3. Find the device, then find where it says ID. After where it says ID, it should have a number/letter mix such as “04e8” or such. Make note of that for later.
4. Go to http://developer.android.com/guide/developing/device.html . This will give the instructions on how to Install the device drivers (specific to each manufacturer). Start from where it says “4. Set up your system to detect your device.”
5. Go to your internal and cd to platform-tools. (This should include both adb and fastboot.) Put your phone into fast boot. (Do this by holding the power, volume up, and volume down buttons while phone is off).
6. Once in fastboot, go back to your computer and type in “sudo fastboot oem unlock”. This will bring up the option to unlock your phone's bootloader on your device's screen. It will give you a disclaimer, and it will say that if you unlock, it will wipe all of your phone's data. Scroll to Yes using the vol up or vol down buttons, and select it with the power button.
7. If you boot straight from there, you will go through a series of boot loops (it was 2 for me) then will be prompted to go through the process of setting up your Google account again. again.
Congratulations, your phone is now unlocked. However, this doesn't mean that you have rooted your phone.
Rooting
Part 2: Putting Clockwork Mod Recovery On Your Phone
(do step one for preparation of Part 3)
1. First, we will want to push su.zip to your phone's Internal storage or “sdcard” partition. Open up Terminal and type the command “adb push 'directory_of_su.zip'/su.zip /sdcard/”. Hit enter/return and it should transfer over. (Based on the quality of usb cord, times of transfer may vary.)
To make this easier, put su.zip into the directory of adb. Then all you have to use for the command is “adb push su.zip /sdcard/”.EDIT:
After you root, you have to delete /system/recovery-from-boot.p and reflash or else every time you reboot, the recovery partition will be written over by android. This can either be done in terminal (phone or comp) or by a file manager with root access (such as Root Explorer).
Reference: http://forum.xda-developers.com/showthread.php?t=1392336
Thanks vihil
2. Put your phone in fastboot mode again (vol up + vol down + power)
3. Go back to Terminal and type in “fastboot flash recovery 'whatever the file name is'”. This will flash CWM (Clockwork Mod) onto your phone, deleting your phone's stock recovery image.
EDIT: If it doesn't work, i.e. due to permissions, run with sudo
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.
Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Special Thanks to scary alien on androidforums.com and jcarrz1 on XDA

Reserved
Reserved......

Thanks a lot I was looking for exactly this. Appreciated. Will try in a few hours when I get my phone.

Downloaded the sdk file but have no idea what to do. My windows computer died and it would be a lot easier on that to do all this but all I have is a computer with linux currently so if anyone would be kind enough to tell me how to install sdk I'd appreciate it. I seen the read me and seen it says execute "android" first but I don't know how to do that. I realize this is incredibly annoying to the xda hive mind trust me I hate needing help like this I'm nothing close to a noob as far as rooting flashing and all that good stuff I'm just unfortunately stuck with only Linux. I'd really really appreciate it.

under the tools folder there is a script called android, u can either run it in a terminal or hopefully if u were to click it, it was ask if u want to run it!

If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.

Seems like my fastboot is stuck on `waiting for device`. I have the fastboot screen on my GN.
Before rebooting into fastboot `adb devices` successfully showed a device (i.e., usb debugging is enabled, dunno whether it is needed for the unlocking):
$ fastboot oem unlock
< waiting for device >
Any idea?
EDIT: Found the solution. After doing a `fastboot devices` it told me "no permissions fastboot" so I needed to be root on my computer for it to work.

FadedLite said:
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Click to expand...
Click to collapse
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.

C-4Nati said:
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
Click to expand...
Click to collapse
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system

For simplicity, you can shorten that to: mount -o rw,remount /system
You can also delete it from a terminal on the phone or any file manager that allows root access. I think the free ES file explorer has root options.

vihil said:
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
Click to expand...
Click to collapse
for needing to type in lsusb, i found that as somewhat of a precaution. I had seen on other threads that others had their device show up as either google or samsung. So i just figured rather check first instead of installing both or something.
for the preparation, basically you do that since your phone is already on. after flashing cwm, you would have to boot back into your phone, push the file to your sdcard, then boot back into recovery. All it does is that it saves just a bit of time.
As for the sudo fastboot, I didn't actually have to do that, but i'll add it, Thanks.
As for the cwm terminal commands, i'll add that as well. Thanks again.

FadedLite said:
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Click to expand...
Click to collapse
not yet. after flashing su-bin-3.0.3.2-efghi-signed.zip (which is just the binary), the user still needs to flash Superuser-3.0.7-efghi-signed.zip, to have Superuser.apk placed in /system/app, otherwise GUI apps won't have access to su. (unless, of course, the zip you are linking here has them both)
It's preferable to have users linked to ChainsDD website, there people will find latest binaries and Superuser.apk. I also don't see any mention to him in the OP. Even if this is a tutorial, don't forget to give credit where needed.

Some help for an Ubuntu Noob/Not a Noob to Windows
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar

jmartino5920 said:
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
Click to expand...
Click to collapse
Are you getting a "waiting on device" message or something similar when you run adb or fastboot?
Forget about the udev nonsense (not important really until you start developing full time) and just drop a sudo before your commands.
You can shoot me a PM or a gtalk (same username as my xda) if you want and I'd be more than happy to help you get your system going.

Thanks, still a bit more annoying that Windows but this tutorial makes it easy.

Sorry if this is ignorant, but can I use these instructions with Unix & terminal on Mac OS X? I'm thinking yes???

I rooted mine in linux as well... No problems. For some reason I was able to do it much easier though...
I did the fastboot oem unlock step above (Part 1). Rebooted then installed superuser from the android market. Then I installed Clockworkmod from the android market.
Done.
Not sure if I'm missing out on something by doing it this way but so far I've had no issues....