Develop Bugs

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

Different Firmware- can I still root?

I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.

timswait said:
I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.
Click to expand...
Click to collapse
Have you run SEUS or PC Companion at all? There's been 5 FW releases since then according to Wotan Server.

From what I have heard, the regular root method for GB, 4.0.2.A.0.58 and lower, should work also on 4.0.2.C.0.5 firmware. Give it a try, you got nothing to lose there.

OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!

timswait said:
OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!
Click to expand...
Click to collapse
If it doesnt work, your phone should be fine. But that also means that you've been doing something wrong. Give it a go
Sent from Xperia Arc S

I followed the instructions here for rooting:
http://forum.xda-developers.com/showthread.php?t=1601038&nocache=1
It seemed to go through all the stages, the phone rebooted several times and it came up "All done" at the end. The good news is that the phone still works fine, the bad news is that it doesn't seem to be rooted. I've installed Titanium Backup and it comes up with "could not acquire root privileges, please check that your phone is rooted", so I assume this means it hasn't worked? Is there any other way to see if it's rooted? This is the output from running the rooting batch script:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3059 KB/s (1075144 bytes in 0.343s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 56068 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .

There's four links to root threads now in my guide, give them a read.

Thanks, that guide was very useful. I've actually used a combination of the techniques, and it seems to have worked Here's what I did, might be useful to someone, also please if anyone who knows better than me can see any problems then please let me know if I'm going to have problems in the future
1. Backed up my firmware using the instructions from 100rabh791 here:
http://talk.sonymobile.com/message/178992
2. Flashed back to 4.1.A.0.562 Kernel using Nabeel's instructions here:
http://talk.sonymobile.com/thread/41119?start=0&tstart=0
3. Rooted using DooMLoRD's root kit here:
http://forum.xda-developers.com/showthread.php?t=1601038
At this point I seemed to have a fully working and rooted phone, however I thought it was best to go back to my original build version (4.1.L.0.8), so I re-flashed my backed up firmware, However this lost my root privileges, so I was back to the start. So I re-did steps 1-3 and then:
4. Re-flashed back to my original firmware, but checked the options "Exclude system", "Exclude baseband", "Exclude Fota" and "Exclude TA" (in other words just left Kernel unchecked).
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.

timswait said:
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.
Click to expand...
Click to collapse
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?

XperienceD said:
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?
Click to expand...
Click to collapse
4.1.L.0.8 which is what it was on after the official upgrades before I started the rooting process.

Weird error-normal-error-normal sequence on rooting using doomlord easyroot.

Hello, I'm new here, bought my Xperia Arc S rooted with 4.0.4 and .587 kernel, xda has helped me a lot but unfortunately I haven't been able to install Jelly Bean, no matter how hard I try... so, basically my problem is
After lots of failed tries to install JB, I ended up with a bricked phone, so I had to flash an official .ftf with its kernel, all okay. Now the bad thins is, I lost my root, and the phone came rooted so I have no idea how to do this, I've followed these steps:
-Install ADB drivers
-Flash/Downgrade kernel
-Debug mode checked
-Unknown sources checked.
then, when I try to do the root, this is what happens (this is the log of cmd).
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
error: more than one device and emulator
--- creating temporary directory
error: more than one device and emulator
--- cleaning
error: more than one device and emulator
--- pushing zergRush
error: more than one device and emulator
--- correcting permissions
error: more than one device and emulator
--- executing zergRush
error: device offline
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
error: more than one device and emulator
--- DEVICE FOUND
--- pushing busybox
error: device not found
--- correcting permissions
error: device not found
--- remounting /system
error: device not found
--- checking free space on /system
error: device offline
error: device not found
error: device not found
--- copying busybox to /system/xbin/
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- installing busybox
error: device not found
error: device not found
--- pushing SU binary
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- correcting symlinks
error: device not found
error: device not found
--- pushing Superuser app
error: device not found
--- cleaning
error: device not found
--- rebooting
error: device not found
ALL DONE!!!
Press any key to continue . . .
of course, that "ALL DONE!" is a lie and useless, and I'm still unrooted, no reboots, anything. I hope you guys can help!
My phone has unlocked bootloader, it's a SonyEricsson Xperia Arc S Lt18i with ICS 4.0.4 and kernel 4.1.B.0.587
Thanks in advance ^w^

Keep trying - root arc s 587

As i can see of your log, it dont detect phone. Probably driver issue
Try this
Download thr superuser.zip from their site. Put it on sd card.
Now find a stockbased kernel with cwm.
Hotboot it
Fastbootcode
Fastboot boot yourkernelnamehere.img
Phone will boot itself
Repeatly press volume down on blue led
In cwm install the superuser.zip
Reboot
Sent from my LT15i using xda premium

TheHaso said:
As i can see of your log, it dont detect phone. Probably driver issue
Try this
Download thr superuser.zip from their site. Put it on sd card.
Now find a stockbased kernel with cwm.
Hotboot it
Fastbootcode
Fastboot boot yourkernelnamehere.img
Phone will boot itself
Repeatly press volume down on blue led
In cwm install the superuser.zip
Reboot
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
I couldn't find a superuser.zip anywhere.. and, how am I supposted to hotboot? o3o, thanks in advance D:

AW: Weird error-normal-error-normal sequence on rooting using doomlord easyroot.
To avoid the driver problem, deinstall pc companion, get the latest Version of flashtool and install the drivers that comes with it. Then try again.
Sent from my LT15i using xda app-developers app

Code:
error: more than one device and emulator
Maybe you should concentrate on one device connected at a time... or disable your emulator!
Follow the other hints and use the search function...
There are some bullet proof how-to's already which will guide you to root, if you read them :angel:
Regards,
scholbert

scholbert said:
Code:
error: more than one device and emulator
Maybe you should concentrate on one device connected at a time... or disable your emulator!
Follow the other hints and use the search function...
There are some bullet proof how-to's already which will guide you to root, if you read them :angel:
Regards,
scholbert
Click to expand...
Click to collapse
Actually the problem is somewhere on my PC, I was able to flash custom ROM and root using my grandpa's laptop.. :l I've already tried having ONLY my phone connected to my pc, still no result or anything.

Did you closed flashtool before starting the rootkit?

HUGE BUMP, but someone may be facing this problem too so.. I want to report my solution
I was using a 3.0 USB port all the time, all I had to do is use a normal USB port and it worked.

cwm installation problem xperia s

hi, am i the only one who gets the message"system cannot file the file specified" in cwm installation method ?
i have root and i have install drivers correctly so what it could be wrong?

Did you follow instructions correctly???

Make sure you have enabled USB debugging.

i have usb debbuging enabled and i follow instructions correctly but every time i run install as administrator i get the message

akattack said:
i have usb debbuging enabled and i follow instructions correctly but every time i run install as administrator i get the message
Click to expand...
Click to collapse
it happened to me
u just have to look at ur screen and wait till the superuser asks u the permissions press allow and the process will be completed after that u ll have a reboot and a working cwm
hit thanks if i helped :good:

CWM Recovery for 2012 Xperia Installer
script created by kenjidct
The system cannot find the path specified.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
OK
=============================================
Step2 : Sending some files.
=============================================
cannot stat 'chargemon': No such file or directory
cannot stat 'charger': No such file or directory
cannot stat 'recovery.tar': No such file or directory
cannot stat 'sh': No such file or directory
cannot stat 'step3.sh': No such file or directory
=============================================
Step3 : Setting up files system partition.
=============================================
Unable to chmod /data/local/tmp/cwm/sh: No such file or directory
Unable to chmod /data/local/tmp/cwm/step3.sh: No such file or directory
sh: /data/local/tmp/cwm/step3.sh: not found
Finished!
Press any key to continue . . .
this is what i get in cmd .no superuser answer in my phonescreen.i checked root with root checker ,everything is ok, usb debugging enabled ,unknown sources on, device recognised firmware .55

Ohh looks like there is a problem with ur files just redownload it again and right click on the zip then click extract here bcz there is something wrong with the directories on ur computer
Just try it and tell me
Sent from my LT26i using xda premium

SAMURAI6969 said:
Ohh looks like there is a problem with ur files just redownload it again and right click on the zip then click extract here bcz there is something wrong with the directories on ur computer
Just try it and tell me
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
same thing again ,redownloaded,put it in different directories even in hard drive,run it in cmd,no use.i found an app called recoverx not woking too.thanx for ur help

Make sure you have necessary drivers installed? Can to connect successfully via adb? Also once you click bat file look @ your screen and allow the root permissions. Also try running without admin previledges

s-X-s said:
Make sure you have necessary drivers installed? Can to connect successfully via adb? Also once you click bat file look @ your screen and allow the root permissions. Also try running without admin previledges
Click to expand...
Click to collapse
Im not shure does it matters but if you rooted phone by eroot did you installed busybox from the googleplay? Cause you have to install it manually..not shure will it help but cost you nothing to try.
Sent from my LT26i using xda app-developers app

[Q] Why second adb.exe starts when i begin rooting process

Hello guys,
I am new here not too familiar with all this stuff but i can handle them, the last two days i am trying to root my phone with doomlord's tool kit but no luck, i have tried everything but in the command window it stuck in the first commands
"--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *"
Then in i go and see my running programms i see 2 adb.exe if i delete the one who "works" the most i get the error, "error: More than one device or emulator" and if i delete the other .exe(A little observation: i think that 2nd adb.exe it's not stable it stops and it beggins again and again) i get the error "error: Device offiline" Despite my phone's build number says .587 it's .562
Do you have any idea what is wrong?
Thanks in advance.

your phone is connected and with usb debugging on? use the tool and wait a bit..it should reboot itself and then its rooted....but at this time why you dont unlock your bootloader?
that way you can flash custom kernel and custom roms easier..

Do you have Flashtool or any other Android-related app running in the background? If yes, close it.
Also, questions must be posted in Q&A.

No nothing is running in the back. Is it normal that a 2nd adb.exe runs too?

What if you try to close both of them and then run the app?
This issue happens when one instance of adb.exe is already running.

Someguyfromhell said:
What if you try to close both of them and then run the app?
This issue happens when one instance of adb.exe is already running.
Click to expand...
Click to collapse
One question, is there any problem if i am connecting my usb cable into USB3 port?
edit: the thing is that if i connect in in a normal usb the proccess goes on but in the end fails
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
instead of USB3 port which stops in the begining

Finally i got it root with e-root, before that eroot always was stucking in the last step before rooting hopefully i am rooted again