Develop Bugs

[GUIDE] Using ADB & FASTBOOT in OSX / Mac

Hi,
I thought I'd add this here because I've recently starting using OSX after building my own hackintosh out of PC parts. I got very fed up with Windows and the need for drivers all over the shop so I'm moved over now.
I've also just got into flashing my HTC Desire and it was made very easy by lots of the guys here. One thing that will always be useful when rooting and flashing your phone is ADB. There are lots of guides out there for ADB on Windows but I wanted to run in natively in OSX.
After a lot of research and a few failed attempts .... I've now worked out how to run ADB in OSX.
What you will need:
A Mac
USB cable
Android SDK for OSX- http://developer.android.com/sdk/index.html
At the time of writing this the version was "android-sdk_r08-mac_86" so please have a look at the above link and let me know if you can't find that same version.
So download the zip file and I would extract it to a folder where you are happy to keep it such as within your user home folder i.e. Macintosh HD/Users/{Your User Name} and for my mac it is Users/siedkins which is how I have my OSX set up.
Then open then still in Finder, open "android-sdk-mac_86" then "tools".
Now launch Terminal - ⌘ + space then type Terminal or Applications>Utilities>Terminal
Now drag and drop the file called "android" in the "tools" folder into your terminal window and you should see something like:
/Users/siedkins/android-sdk-mac_86/tools/android
Then hit enter - this should load Android SDK
Next go to Available Packages on the left and Android Repository > Android SDK Platform-tools, revision 1 -tick the box and hit "Install Selected"
It should download and install the Platform Tools which includes ADB !!!!
Now quit Android SDK after it has downloaded and go back into Finder. Now you should see a new folder "platform-tools" in the "android-sdk-mac_86" folder. Open that and you can now see a file called adb.
Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it.
Go back to your Terminal window and type (or copy & paste):
Code:
cd ~
The screen should then look like
NAME_OF_YOUR_MACHINE:~ USERNAME$
For me I have:
Mac-Pro:~ siedkins$
Next, type
Code:
touch .bash_profile
to create your new bash / path file
Next, type
Code:
open -e .bash_profile
to open it in TextEdit.
Now into Text Edit please copy:
Code:
export PATH=${PATH}:
Then go into Finder and navigate your your "android-sdk-mac_86" folder. Then click on the "platform-tools" folder and drag and drop this into TextEdit at the end of the code above that you copied. Mine looks like:
export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools/
Yours should look like:
export PATH=${PATH}:insert your path to the "platform-tools" folder in your Android SDK here
All you need is that one line. Then Save and exit TextEdit and then very importantly QUIT TERMINAL.
***** If you have issues being able to save the file at all then please jump to the bottom of the post*****
Now ........ to turn on USB Debugging in your handset Settings > Applications > Development > USB Debugging - ticked and also go to Settings > Connect to PC > Default connection type > Charge Only and also UNTICK "Ask me ..." there also. You can always go back here and change these settings back.
Now plug in your phone to a USB port. I noticed that if I plugged my phone into one of the standard USB ports on the front of my machine I couldn't see the phone further down the line and if I plugged it into a powered USB port on the front (I have an "akasa AK-ICR-08" which has a powered connector behind the 5 USB ports. But you guys will probably be using a MacBook or MacPro and there shouldn't be any issues with the power to your USB ports.
Now to launch ADB - re-open terminal (remember that you had quit it - very important!) then type in:
Code:
adb devices
And you should see:
List of devices attached
HXXXXXXXXXX device
where XXXXXXXX is your unique phone ID.
Now you can run all of your favourite ADB commands straight by typing:
adb shell
etc straight into Terminal. I won't go into that here as there are plenty of guides about what to do with ADB once it's installed!
Now you have ADB setup on your Mac and can run it without the need for installing HTC Sync - un-installing it - loading some modified drivers over the top !!!!
It all just works !!!!!!
Please drop me a line if you have any queries about this !
******************
If you are have user account issues such as Terminal or TextEdit says that you can't do anything then try adding "sudo" to the front of your terminal command as this will allow you to execute the account as a superuser or root user for OSX! ROOT!!! Note that you will have to enter your password to enable the superuser access rights and you won't see anything as you type in your password.
i.e. try:
Code:
sudo touch .bash_profile
then
Code:
sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit .bash_profile
(slight change in the coding here to ensure that TextEdit opens
Or you could do:
Code:
sudo pico .bash_profile
This will open up the Pico text editor instead of TextEdit. Here you will have to type out all of the text then you press "ctrl+x" to exit and then you can save on the next screen. To check that has worked you can then open the file in terminal again and check it with the normal command:
Code:
open -e .bash_profile
******************
Please see post #37 for How To Use ADB Over WIRELESS !!!!
************************************************************************
EDIT - 27th JAN 2010
FastBoot
I've now found you all a precompiled version of Fast Boot:
http://developer.htc.com/adp.html
Please download and unzip the precompiled version for OSX to your "SDK/platform-tools" folder.
Rename the unzipped file from "fastboot-mac" just to "fastboot". You need to fix the permissions of the fastboot file using CHMOD in Terminal.
In Terminal navigate to your "SDK/platform-tools" folder and then type:
Code:
ls
You should see all of the files in your "platform-tools" folder such as adb, aapt, fastboot, etc.
Then type:
Code:
chmod 777 fastboot
PLEASE NOTE THAT I AM ASSUMING THAT YOU HAVE CHANGED THE FILE NAME ABOVE !
Now with the permissions fixed you should be able to run fastboot.
Connect your phone via USB and set to "charging only". Then turn off your phone and leave the USB in. Then hold the back key and then turn your phone on again. You will have a white screen with 3 skateboarding androids on.
Now in Terminal type:
Code:
fastboot devices
And you should see your unqiue phone ID! (Note that you have to be at that white screen with the skateboarders for the "fastboot devices" code to run!
Now you have a fully working fastboot !!!
Sorry this explanation is a bit short - I did write out a longer one but my browser crashed and I lost it all. However if you cannot follow the above then I think it's maybe best that you don't use fastboot as you could seriously brick your phone.
NOTE - I HAVE NEVER USED FASTBOOT TO FLASH A RADIO OR PHONE SO I PROBABLY WON'T BE ABLE TO HELP IF YOU GET ERRORS IN USING FASTBOOT OR FLASHING YOUR DEVICE ! The above information is how to shortcut the navigation to the folder. Please don't blame me if you break the recovery image of your phone!

Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
which last step ?

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
What version of MacOS? Also are you sure your device is properly rooted? I'm assuming you are getting the error when typing "adb devices"?
EDIT: That's what I get for being distracted while typing this.. ;-)

The easiest way to get the sdk is by using homebrew, which is an amazingly useful tool. https://github.com/mxcl/homebrew
Code:
brew install android-sdk
It doesn't add adb to your path however, you have to do that manually by adding /usr/local/Cellar/android-sdk/r8/platform-tools to your path.
Hope that makes it a little bit easier.

I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices

Thanks for the walk through
This work great. I put the the SDK folder on the root of Macintosh HD and renamed it to AndroidSDK. Then in the .bash_profile my path was /AndroidSDK/platform-tools/ . I then made a backup of my SD card with adb pull from /mnt/sdcard to my local machine.

mun-key said:
I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices
Click to expand...
Click to collapse
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.

It doesn't even have to be this complicated. Download the sdk, whatever files you want to push to your phone put it in the same folder. Then do the commands (./adb push). Simple.

Great and easy tutorial! Got it working in 5min ^_^

madj42 said:
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.
Click to expand...
Click to collapse
Ok - that makes sense now. And reading Krisrk's reply, that's exactly how I did it.
On my device I only needed to push a single file. Don't really need adb anymore. Your post was like 12-hours too late for me though. I spent 3 hours trying to figure out why it wouldn't work, then saw the ./ in a youtube video. After that I was rooted with a new rom in minutes
thanks for all the great info guys

Just wanted to thank you! I already had ADB working on my Mac OSX but didn't have the "environment variables" in the .bash_profile. So now I can just use adb commands directly without going into the finder and find the adb!
Also, kudos for the very detailed guide with your own examples, that reads very well!

Thanks for the comments guys.
I know that you can navigate to the SDK folder and just run it from there but I thought that people might like the above guide to do the shortcut once and then never have to jump around folders again in terminal which is a bit of a pain. Plus my method removes the need for the "./" prefix.
anyways I'm easy I'm sure that everyone will have their own preferred method if you already use adb on OSX

i cannot get beyond the command:
touch .bash_profile
the terminal returns permission denied. what do i need to add or what am i doing wrong?

What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?

Thanks for this!!!!!
Nobody ever shows macs love.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

siedkins said:
What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?
Click to expand...
Click to collapse
it popped up and asked my password, then it said i entered the wrong one and i never was asked this again. this is incredibly frustrating as i cannot even get it to work in windows
edit: ok got to the part where i bring up text edit, but it will not let me save. states i do not have permission to save. is there a way i can turn off this password crap for the time being? all i want to do is push files to my phone, i can't even get this far

Ok...
I'm trying not to look stupid, but for gods sake, im stuck at the first command. I copy paste cd~ and nothing happens. press enter nothing. I've been reading up on terminal and i still feel quite stupid considering how im stuck on step one
edit: got it! I got lost going back into the same terminal and not closing the android sdk window. there fore I was still in the sdk and not telling the computer anything. a dur. Opening a new terminal and doing all of the steps did the trick. Thanks for this btw!

thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!

monstereo said:
thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!
Click to expand...
Click to collapse
Hey just a random note, nice prof pic stig ftw

[Mod Edit: Incomplete] How easily root mytouch 4g for noobs! (look)

Mod Edit: Incomplete instructions. Follow at own risk.
Hello all! I am making this thread, and i know there are plenty out there, because there are still people who cant seem to root their phone no matter what they try. I was one of these people, I couldn't root my phone for the life of me until i tried the method im about to explain to you. Im going to try to make it as easy as possible. Here we go.....
Before we get started:
I am not responsible for what happens to your phone. It will void your warranty and if not followed correctly, can brick your device. So read the directions and follow it to a "T" if you wish to root your phone.
FIRST
Set up ADB/USB Drivers
1. Download the Android SDK from Google.
http://developer.android.com/sdk/index.html
2. Extract the Android SDK .Zip file to C:\AndroidSDK
3. From your phone click SETTINGS, APPLICATIONS, and make sure USB DEBUGGING is on.
4. Plug your phone in via USB to your computer. If you are using windows, it should say installing drivers.
5. After the drivers finish installing, go to the Start menu on your computer and type in CMD in the search bar. You can also click run and type in CMD and it will open the command prompt.
6. Type as follows (hit enter after every line)
cd\
cd AndroidSDK\tools\
adb devices
7. After you have typed all of that, You should see a serial number and the word "device" to the right of it. If you see that, then you are set and can continue reading.
(If it says adb not found or something along those lines, then you need to download these files and extract them into the Tools folder of the SDK)
(If that still doesnt work, then try re-installing the drivers)
SECONDLY
1. Make sure you have visionary installed. (It can be the new r14 version)
2. Download this file [URL="http://www.mediafire.com/?gzaozcurazidh98"]http://www.mediafire.com/?gzaozcurazidh98
3. Unzip the file you just downloaded into the Tools folder in the SDK
4. Plug your phone into the computer.
5. Head over to the Tools folder thats located in the SDK and hold down shift and right click on your mouse over that folder. Select open command window here.
6. Type "adb push gfree /data/local" and press enter. (exclude the quotations)
7. Unplug the device from your computer.
8. Run Visionary to gain temporary root (temp root)
9. Open terminal emulator on your phone (if you dont have it, its a free app in the market) and type "su" (exclude parenthesis) to get root permissions.
10. Type in "cd /data/local" (exclude parenthesis) and press enter.
11. Then type "chmod 777 gfree" (exclude parenthesis) and press enter to make the program executable.
12. Then type in "./gfree" (exclude parenthesis) and press enter.
13. Wait for it to finish then reboot into HBoot by powering down and then powering your device back up by holding volume down and power to see if you have S=OFF. If you have S=OFF with the 0.86.0000 bootloader version, it worked!!

Not to be an ass.... but how is this different from the other threads we have on this?
If people can't figure it out using the guides.... they probably have absolutely no business rooting and should be using a moto razor.
Sent from my HTC Glacier using XDA App

Yeah, this is getting ridiculous...
And by the way, your method there will leave you with a half-rooted device. What I mean is, yes, it is S=OFF, however, you still don't have the su binary and Superuser.apk in the proper places until you "permaroot" with Visionary or another tool by setting the system R/W and putting those binaries in place. That is unless you are already half-assed-rooted with the binaries in place but still S=ON before you even do this. This guide is incomplete, and why so many are having trouble rooting completely.
There are three distinct things that must be done to completely root the MT4G.
1. Temp-root - so you can do the next step.
2. Turn S=OFF - so you can do the next step.
3. Permanently root - to copy the proper binaries and complete the process.
If you can't follow the instructions here: http://forum.xda-developers.com/showthread.php?t=858996 then you shouldn't root your device. No, seriously, we mean it.

Should just delete this thread... incomplete guide with incomplete instructions..... just going to lead to people having problems.
Sent from my HTC Glacier using XDA App

You mean .85.2007?
Sent from my HTC Glacier using XDA App

.........(blank stare)

Made a small change to the OP for the safety of readers.

For the safety of the readers . Lol that sounds so professional
option94 said:
Made a small change to the OP for the safety of readers.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

[HOW TO] Root a bootloader-unlocked Xperia Pro MK16a

There is now a MUCH easier way to root ALL Sony Ericsson 2011 phones including the Xperia Pro, making these instructions obsolete. Please see DooMLorD's thread here: http://forum.xda-developers.com/showthread.php?t=1319653
Remember to say thanks to DooMLorD for his awesome work!
However, I'll sill keep the 2 sets of instructions here in case anyone needs them or wants to refer back to them. My ZIPs do have all the drivers needed with good instructions on how to install them after all
My original instructions based on alvaroag's work can be found below, and the instructions via my instructions the Xperia Pro CWM Recovery method can be found on post 50 of this thread.
It's important to note that DooMLorD's tool only works for Windows. You can still use our original method in this post if you're running Linux.
We finally have a method to root the Xperia Pro MK16a (and PROBABLY MK16i) thanks to XDA Member alvaroag!!
This is his method, with the instructions modified by myself for ease of use.
What you need before you begin:
1. A rock hard stomach, because should the very unlikely happen and this brick/damage your phone in some way, I’m not responsible
2. An Unlocked Bootloader
NOTE: Sony offers a totally free, official, and simple method to unlock your bootloader here: http://unlockbootloader.sonyericsson.com/
Should that not work for you, your phone is probably SIM locked from your carrier (FIDO for example does that). You'll need to get the bootloader unlocked remotely from someone who has SETool and the appropriate security USB dongle. THIS COSTS MONEY, as SETool requires that user to pay per use.
Please see this thread for further instructions as it's the method I used personally: http://forum.xda-developers.com/showthread.php?t=1232050
Alejandrissimo was awesome at helping me through it.
3. On the phone itself navigate to the following locations:
a. Settings - applications – Make sure Unknown Sources (first option) is checked
b. Settings – applications – development – Make sure USB Debugging is checked
4. Download this archive. It contains all the files and drivers you will need:
http://www.mediafire.com/?7cz7672da9cxkrd​
Instructions:
1. Extract the archive you downloaded to a folder on your computer. Where doesn’t matter as long as you remember where it is.
2. Navigate to the folder ADB For Dummies (thanks to VanillaTbone for his guide) and install ADB for Dummies.exe
a. This will create a new folder on your C: drive called “android-sdk-windows”
3. Take the file “xperia_pro_root.zip” from the archive you downloaded and extract the contents to C:\android-sdk-windows\platform-tools\
4. Power off the phone and make sure it’s not plugged into anything.
5. Hold down the MENU button and connect the USB cable. A blue light will appear. If a blue light does NOT appear, then your phone can't get into FastBoot, and probably still has the bootloader locked.
a. If Windows asks you to install the drivers, install the driver from the folder “Fastboot Driver” in the archive you downloaded. Should those drivers not work, try the drivers found in "C:\android-sdk-windows\google-usb_driver"
6. Open the “Fastboot” folder in windows explorer (its part of the archive you extracted in step 1. Hold down the shift key and right click on an empty space in the folder window, select Open Command Prompt Here.
7. Type:
fastboot boot recoveryNEO.img​
8. The blue light on the phone will turn off, the screen on the phone will be blank, and the phone will be disconnected from windows, but after a few seconds you will get a Mass Storage & ADB Interface Detected. Note that the phone’s screen will continue to be black for the rest of this process. THIS IS NORMAL, your phone has not been bricked. If you need to stop anywhere along the way, simply unplug the phone from the computer and take your battery out. The phone will return to normal operations, though UNROOTED.
a. Windows will PROBABLY say hardware failed to install. This is fine.
i. Open the start menu, right click on “Computer” and select “Manage”
ii. Select Device Manager on the left side of the Computer Management window that opens.
iii. Look for the unknown piece of hardware. Right click on it and select update/install driver.
iv. Browse your computer, and select the main folder you extracted the archive to way back in step 1 – the drivers are somewhere in there, don’t worry about where, as windows will find them just fine.
9. On your computer navigate to “C:\android-sdk-windows\platform-tools”. Hold down the shift button on your keyboard and Right click on an empty part of the windows, and select “Open Command Window Here”
10. Type "adb shell". If it says "device not found", disconnect the USB cable, remove the battery, and try again from step 6. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
Now you’ll have to run a bunch of commands inside the ADB Shell window (the one with the black background and looks like a DOS window). You can just copy and paste each one from here. Be sure that once you start this step, you continue until the end of these instructions.
mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system​
If it says “/system is not empty” then type:
"rmdir /system/bin" and then run the first mount command again
type "exit"
11. From the DOS window, Run these commands (again copy and paste each one is fine)
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell​
12. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot​
13. The adb shell will terminate. Disconnect the phone from the USB cable, wait for about 15 sec, remove the battery, and then turn it on.
14. From the phone, Open the Market, search for "Busybox" by "Stephen (Stericson)". Install that
15. From the Market, go to My Apps, search for "Superuser" by "ChainsDD" and make sure you're running the latest edition
16. Run the App "Superuser" from your app tray.
- under the settings tab, scroll to the bottom and click SU Binary "tap to check for updates"
17. Run the "Busybox Installer" app. Follow the onscreen instructions - just leave everything at default.
Congratulations! Your device should now be rooted! I personally suggest downloading and installing Titanium Backup to make sure - it will run a root check on startup and notify you if anything is wrong.
Notes:
This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution. - alvaroag​Thanks to VanillaTbone of XDA Developers for his awesome ADB For Dummies guide and app.
http://forum.xda-developers.com/showthread.php?t=502010
And of course thanks to Bin4ry for his NEO recovery image.
And thanks to all the other contributors to this thread for their help, advice, and overall contribution.
And if this thread helped you in some way, Please click THANK YOU to show your appreciation
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse

rcummings100 said:
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk

Edit; ............
Sent from my LT15i using XDA App

taaviu said:
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess

XperienceD said:
There is a Mini Pro forum. ;-)
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Totally different phone
This is just the "Xperia Pro" - it was released in August. It's the same phone as the Neo, but with a slide out QWERTY keyboard. Model is MK16a (or MK16i for the international one)

Gingerbreak??
Sent from my MT15i using Tapatalk

Alejandrissimo said:
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess
Click to expand...
Click to collapse
How to do it? Generate prerooted system.img
Thanks!
Sent from my MT15i using Tapatalk

I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards

Bin4ry said:
I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards
Click to expand...
Click to collapse
That was the first thing I tried, since the Pro should just be a Neo with a keyboard. Unfortunately it doesn't work.
Here's the output:
C:\root-play>fastboot boot recoveryNEO.img
downloading 'boot.img'...
(bootloader) USB download speed was 9336kB/s
OKAY [ 0.517s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.002s]
finished. total time: 0.519s​
The phone is clearly still turned on, but no longer in fastboot mode, and the screen is totally blank, though the backlight is active.
I've tried the same thing with the Arc and Play recovery images and had the same results.
What do you mean by the keys are mapped wrong?
Is this what you're talking about?
http://www.knowyourcell.com/sony-er..._hard_reset_the_sony_ericsson_xperia_pro.html
The instructions on how to get into Recovery on that site are very similar to how to do it on the stock build of my previous phone, the Motorola Milestone. Unfortunately THEY DON'T WORK
I've tried substituting the volume down button with other keys, but with no success. Pretty difficult to guess the right key combination when there's a full qwerty keyboard on here
Is there a way to boot into the standard recovery from ADB or fastboot or something? Possibly from an on-board terminal emulator? A command like "Reboot Recovery" perhaps? Or is that too easy to be possible...
It's ironic that my old Motorola milestone with a totally locked down bootloader proved easier to hack than this phone with it's wide open bootloader

Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards

Bin4ry said:
Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards
Click to expand...
Click to collapse
Nope, adb shell doesn't work. Shows "error: device not found"
But because I'm new to this (I came from a motorola milestone), I want to make sure I did what you actually asked of me:
- I turned on the phone into fastboot mode (hold down menu, plug in usb cable, get blue light)
- from a command prompt window: fastboot boot recoveryARC.img
(replacing ARC with NEO and PLAY depending on the image I'm trying)
- phone now boots into black screen, no blue light, screen backlight is on
- unplug from computer, plug back in
- from command prompt: adb shell
Are those the instructions you wanted me to follow?
Fastboot works fine. Can I do anything from there? Getvar for example, or something? can I run the command Update and flash the RootXperia.zip file? Or will that not work because it's not signed properly or something similar?

Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards

Bin4ry said:
Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
Click to expand...
Click to collapse
I figured as much. Just hoped I might be wrong.
Bin4ry said:
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards
Click to expand...
Click to collapse
Can anyone give me instructions or pointers on how I extract the kernel.sin from my firmware?
Thanks for your continued patience with me. I really do appreciate it.

Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium

datagubben said:
Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
It's because they're all so similar, and are based on the same hardware as the Arc.

Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards

Bin4ry said:
Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards
Click to expand...
Click to collapse
Unfortunately the very first thing I did with the phone was unlock the bootloader. 'Fido' is the only phone company selling the phone, but I'm with 'Rogers'...so I needed to unlock the bootloader in order to actually use the phone as a phone, which was and remains the most important thing to me.
That being said, I'll see if Alejandrissimo can give me a hand with re-locking the bootloader, then I can get the firmware as you instructed, then have him re-unlock the bootloader. I'll just stick my SIM Card back in my old motorola milestone while we work on this so I can still have a working phone.
You're awesome Bin4ry for helping like this

Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.

ratius said:
Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.
Click to expand...
Click to collapse
If you could, that'd be great. I don't especially want to lock my bootloader over again since you have to use SETool to unlock it, which costs money each time you use it (essentially). Not to mention it involves some acrobatics with a paperclip to connect a testpoint inside the phone to a ground!
Unless there's an easier way to lock/unlock now that I've done it once that is...if so, I'm happy to do it.
As for accessing the files Bin4ry is talking about, boot to windows if you can and do it that way. Just follow his instructions to repair your firmware, then go to that folder in windows (it's located in C:\Program Files (x86)\Sony Ericsson\Sony Ericsson PC Companion). At least, that's my understanding.

Hi. Yesterday, I bought a Xperia Pro. Ive spent most of the afternoon and the nigh trying to root it, and I've finally got how to do it. It's a manual method, as there is not an automated one.
There's no need to say I'm not responsible for any damaged or bricked devices(but mine is working ok )
What you need:
1. The Xperia Neo Recovery, by Bin4ry, get it here
2. xperia_pro_root.zip I'm attaching. It contains the files from RootXperia.zip, but without the update.zip-related files, as they are not needed.
3. The Android SDK, with the Google USB Drivers Package.
4. If you've never used your device in fastboot mode, you may also need to follow steps 7 & 8 from SE bootloader unlocking tutorial.
5. [NOT REALLY SURE] Application Debugging & Unknown Sources enabled.
6. [NOT REALLY SURE] Unlocked Bootloader. This is because mine is unlocked, but I don't really know if that is required to boot the recovery image via fastboot.
I'm assuming that you are working on a Windows/Unix terminal, with a working directory where you have recoveryNeo.img, Superuser.apk and su /these two from the zip file I attach), and that fastboot & adb are on the PATH. If some file is not on the working directory, or fastboot/adb are not on the path, use full paths.
Instructions:
1. Disconnect & Power off the phone.
2. Hold down the menu button and connect the USB cable.
(If Windows asks you to install the drivers, install the driver from ANDROIDSDK\extras\google\usb_driver folder).
3. Run "fastboot boot recoveryNeo.img". The fastboot device will be disconnected, but after a few seconds you will get a Mass Storage & ADB Interface Detected.
4. Run "adb shell". If it says "device not found", disconnect, remove the battery, and try again from step 1. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
5. Run "mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system" from the adb terminal. If it says /system is not empty. run "rmdir /system/bin" and then run mount again.
6. type "exit"
7. Run :
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell
8. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot
9. The adb shell will terminate. Disconnect the phone, wait for ~15 sec, remove the battery, and then turn it on.
10. Your device should now be rooted.
Notes:
1. When booting with recoveryNeo.img, the screen will keep blank. That's normal(I think).
2. This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution.
Hope this is usefull for you.

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

[Guide] [Z1s] for Root For Sony Xperia Z1s T-mobile (C6916)

Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.

I tried this but nothing happens I attached what happens in cmd
Sent from my C6916 using XDA Free mobile app
---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------
not working for me this is what I get in CMD
C:\Root Tool>adb push pwn /data/local/tmp/pwn
2792 KB/s (574722 bytes in 0.201s)
C:\Root Tool>
C:\Root Tool>adb shell chmod 755 /data/local/tmp/pwn
C:\Root Tool>
C:\Root Tool>adb shell /data/local/tmp/pwn
superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse

Just use z2 exploit 11 run it twice.
Sent from my C6916 using xda premium

Im getting this error whenever I try open SuperSU.. Tried your method about 6 or 7 times, same error everytime.. any advice?

48bloo said:
Im getting this error whenever I try open SuperSU.. Tried your method about 6 or 7 times, same error everytime.. any advice?
Click to expand...
Click to collapse
Sorry about that, SuperSu its giving to you this error because the rooting it's not done, please check that your phone its adb recognizable with "adb devices" in CMD, Remember to Unistall Super Su if you get the error and Reboot in order to try again.

Damented said:
I tried this but nothing happens I attached what happens in cmd
Sent from my C6916 using XDA Free mobile app
---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------
not working for me this is what I get in CMD
C:\Root Tool>adb push pwn /data/local/tmp/pwn
2792 KB/s (574722 bytes in 0.201s)
C:\Root Tool>
C:\Root Tool>adb shell chmod 755 /data/local/tmp/pwn
C:\Root Tool>
C:\Root Tool>adb shell /data/local/tmp/pwn
Click to expand...
Click to collapse
Please try again pressing enter just once at each code.

superangel16 said:
Sorry about that, SuperSu its giving to you this error because the rooting it's not done, please check that your phone its adb recognizable with "adb devices" in CMD, Remember to Unistall Super Su if you get the error and Reboot in order to try again.
Click to expand...
Click to collapse
Okay so after working at this for a couple of hours I finally got it to work. For some reason, I wasn't able to uninstall SuperSu because it had been installed as a system app and I could only disable it, or uninstall updates from it. After trying over and over, I found this link.
http://forum.xda-developers.com/showpost.php?p=53442704&postcount=1075&nocache=1&z=9157358331140130
Here, they include the exact same method in this thread, with one extra step; creating a boot script to maintain root/system permissions. Im not exactly sure how it works, but i followed the instructions provided by the links and then, after rebooting, was able to install binaries, and achieve full root (FINALLY!!) So if anybody has the same problem I did, try this out

48bloo said:
Okay so after working at this for a couple of hours I finally got it to work. For some reason, I wasn't able to uninstall SuperSu because it had been installed as a system app and I could only disable it, or uninstall updates from it. After trying over and over, I found this link.
http://forum.xda-developers.com/showpost.php?p=53442704&postcount=1075&nocache=1&z=9157358331140130
Here, they include the exact same method in this thread, with one extra step; creating a boot script to maintain root/system permissions. Im not exactly sure how it works, but i followed the instructions provided by the links and then, after rebooting, was able to install binaries, and achieve full root (FINALLY!!) So if anybody has the same problem I did, try this out
Click to expand...
Click to collapse
Nice! I'm happy To heard that! JCase said in his post that some people will have this problem to write to system, but in my case i was able to, now we have to find a working recovery in order to have a custom rom or something like that, Some people say that xzdualrecovery works for z1s, but it is in beta version, if you find something please let us know.

Guys not to be mean but we posted this a while back shows you how to root what to install for recovery as well as a deodex and perm root http://forum.xda-developers.com/showthread.php?t=2783626

Tactic13 said:
Guys not to be mean but we posted this a while back shows you how to root what to install for recovery as well as a deodex and perm root http://forum.xda-developers.com/showthread.php?t=2783626
Click to expand...
Click to collapse
Oh! Excellent! thank you so much now we can all get the final access, i searched before but no luck, thank you. Now just have to buy a new phone, mine was robbed on friday , just 3 days of use .......

superangel16 said:
Oh! Excellent! thank you so much now we can all get the final access, i searched before but no luck, thank you. Now just have to buy a new phone, mine was robbed on friday , just 3 days of use .......
Click to expand...
Click to collapse
Not full access bootloader is still locked but you can flash things onto your phone and as well as backups. Also sorry on the phone thing.

Tactic13 said:
Not full access bootloader is still locked but you can flash things onto your phone and as well as backups. Also sorry on the phone thing.
Click to expand...
Click to collapse
Hey Thanks for Reply, that's the reason because i said de Final Acces, because we can acces to bootloader because branded phones can't have bootloader unlocked.:fingers-crossed:

Has anyone taken the update? Will we lose root?

POMF2K said:
Has anyone taken the update? Will we lose root?
Click to expand...
Click to collapse
I can't be sure of that because is a said I lose my phone, but ever when you do a official update you lose root.
Sent from my C6603 using XDA Free mobile app

superangel16 said:
I can't be sure of that because is a said I lose my phone, but ever when you do a official update you lose root.
Sent from my C6603 using XDA Free mobile app
Click to expand...
Click to collapse
I did not lose root. I check the box in SuperSU to try to retain root.
Kept root, now I just have to fix all the issues 4.4 has created.

POMF2K said:
I did not lose root. I check the box in SuperSU to try to retain root.
Kept root, now I just have to fix all the issues 4.4 has created.
Click to expand...
Click to collapse
Which box in SuperSU was it?
Doc

superangel16 said:
Please try again pressing enter just once at each code.
Click to expand...
Click to collapse
So you have to enter each line and then enter and then the next line and enter. Correct?
Sent from my C6916 using Xparent Cyan Tapatalk 2

superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Hello, three commands you wrote down. Do I need to write them exactly like that with a space in between each line and then enter? Or do I need to type one command and then ENTER after each command?
Thanks in advance
Sent from my C6916 using Xparent Cyan Tapatalk 2

superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Hey boss, I did everything exactly as instructed and my phone has no problem being identified in adb devices but every time I run the commands I get the first 2 commands looking like it went OK but the last command just can't execute.
C:\Users\TEMP\Downloads\xperia root>adb devices
List of devices attached
CB5A1Z18JC device
C:\Users\TEMP\Downloads\xperia root>adb push pwn /data/local/tmp/pwn
2806 KB/s (574722 bytes in 0.200s)
C:\Users\TEMP\Downloads\xperia root>adb shell chmod 755 /data/local/tmp/pwn
C:\Users\TEMP\Downloads\xperia root>adb shell /data/local/tmp/pwn
/system/bin/sh: /data/local/tmp/pwn: can't execute: Is a directory
C:\Users\TEMP\Downloads\xperia root>
Please help.

Bill Idol said:
Hey boss, I did everything exactly as instructed and my phone has no problem being identified in adb devices but every time I run the commands I get the first 2 commands looking like it went OK but the last command just can't execute.
C:\Users\TEMP\Downloads\xperia root>adb devices
List of devices attached
CB5A1Z18JC device
C:\Users\TEMP\Downloads\xperia root>adb push pwn /data/local/tmp/pwn
2806 KB/s (574722 bytes in 0.200s)
C:\Users\TEMP\Downloads\xperia root>adb shell chmod 755 /data/local/tmp/pwn
C:\Users\TEMP\Downloads\xperia root>adb shell /data/local/tmp/pwn
/system/bin/sh: /data/local/tmp/pwn: can't execute: Is a directory
C:\Users\TEMP\Downloads\xperia root>
Please help.
Click to expand...
Click to collapse
Thank yoy sir for follow my instructions, i am sorry for the delay to answer, i lost my phone. Well i see you are getting a problem to get into the last step in this guide, please check the Jcase post to get you're problem solved; http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004.
Hope you can solve it!