Database Develop

Require some guidence Samsung Captivate

I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.

Did you download busy box app from market?
Busy box is a set of commands that many root programs utilize

groovydude1981 said:
I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Click to expand...
Click to collapse
After u root:
1. Go to market and search for busybox and install it.
2. Open busy box, and follow the steps in it install the required commands.
You should be good now.

mcord11758 said:
Did you download busy box app from market?
Busy box is a set of commands that many root programs utilize
Click to expand...
Click to collapse
@mcord11758: * one more collision *

diablo009 said:
@mcord11758: * one more collision *
Click to expand...
Click to collapse
We are in sync

mcord11758 said:
We are in sync
Click to expand...
Click to collapse
oops. wrong word. u sure know how to phrase ur sentences. r u in any business/management role?

diablo009 said:
oops. wrong word. u sure know how to phrase ur sentences. r u in any business/management role?
Click to expand...
Click to collapse
I am in sales, but my educational background Is business

groovydude1981 said:
I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Click to expand...
Click to collapse
Wow, I had my phone rooted and flashed within an hour of even learning what it all was.
Video tutorials are the best way to learn the basics, and once you have a grasp of what youre doing written instructions become easier to understand.
I recommend watching as many ROM review and install videos as possible, make sure to watch them more than once and while youre actually doing the steps.

thanks for the quick responce
I did download busybox from the market, but it tells me that everything is unavailable, and that my phone is rooted but my nand protection is still on. Plus busybox tells me that it can't find itself, whatever that means. lol
Pls let me know how to correct this.
By the way I used super 1 click 1.6.3 to root my device.
Thanks ppl your all awsome.

I also watched lots of videos, but could not find anything specific to my device. What other device videos are compatible in content with my samsung captivate?
thanks again.

Did you click install in busy box?

I dont know why but Itried busy box again and it installed. Now i think I just need nand protection removed andthe on click lag fix installed. it still wont install

groovydude1981 said:
I dont know why but Itried busy box again and it installed. Now i think I just need nand protection removed andthe on click lag fix installed. it still wont install
Click to expand...
Click to collapse
I would not use one click lash fix, but that is just me. If you want a lag fix consider a custom rom. One click lag fix is obsolete

thanks for the heads up. I installed the one click lag fix for now. When i learn how to use custom roms, ill uninstall it and use an up to date rom.

some help
groovydude1981 said:
thanks for the heads up. I installed the one click lag fix for now. When i learn how to use custom roms, ill uninstall it and use an up to date rom.
Click to expand...
Click to collapse
This is probably a great place for you to start.
http://forum.xda-developers.com/showthread.php?t=887525
there is a one click out there with root, unroot, and non market apps. i'm looking for it for you
EDIT
Here it is
http://forum.xda-developers.com/showthread.php?t=803682
Also before doing too much i'd familiarize yourself with the ODIN one click and learn about it as well as download mode so you know how to fix a bricked phone, well a soft bricked one.

I used super 1 click to root my phone, but anything you can send me is most appreciated. I will not be able to thank you enough.

Try rooting again with Galaxy one click root.

What will galaxy one click do for me that super one click wont?

They both essentially do the same thing. After your phone has been rooted you need to see if you can find the Super User app. It should be installed on your phone.
I've meant to update the Q&A sticky with what versions are easy to root.. so I apologize for not having it there.
When you install anything that requires root access (hence why your phone is rooted to begin with ) you would get a pop up requesting to have that application gain root access.
But.. there are only a few 3rd party apps that require root access if your not going to flash a custom ROM.
Titanium Backup btw will install the latest version of BusyBox for you - it is a highly used application to backup your system and applications for your phone.
Another highly used application is ROM Manager (used for flashing ROMs)
I would highly suggest you get familiar with how you restore your phone back to stock - then check out teh sticky under the dev forum on how to flash a custom ROM.
Then your on your way to becoming a fellow flash junky

I'm in the same boat as groovydude.
I have a 2 month old Samsung Captivate (first smart phone). I'm trying to root it. I have run SuperOneClick at least 6 times trying everything that I can find in the forums. I have drivers installed. Does anyone know if this tool will work on this phone, or if there is a tool that does. The output from SuperOneClick-ShortFuse is below. Every time it runs it tells me it is rooted, and every app that I open requiring root tells me it is not.
I have tried instructions to root via Update.zip. The instructions were to drop the file on the internal sd. When I plug the phone into the usb port, two drives show up. Nothing can be dropped on either. They both say to insert a disk. I have no external sd card. Does anyone know what might be the holdback?
Also, SuperOneClick said that BusyBox was installed, but I could not find it, so I downloaded Stericson's BusyBox installer. It failed to install with a message that the phone was now rooted but BusyBox was not found. It said the application failed because the phone is not "nand unlocked." What is nand unlocked? The only unlocking procedures that I can find instructions for are to unlock a phone from a carrier. Is this what "nand means"?
I tried Titanium Backup to install BusyBox, and it complains that the rom is not rooted after both other processes said it was. TI offered to download and install BusyBox and it failed too.
Does anyone know why all these procedures say that they have rooted the phone but nothing still works? Or what is nand unlock? and how is it done?
SUPERONECLICK OUTPUT:
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
558 KB/s (585731 bytes in 1.024s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
974 KB/s (1062992 bytes in 1.065s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/stl9
OK
Reading OS Version properties...
Version: 1.5
OK
Remounting system with read-write access...
OK
Pushing su-v1...
640 KB/s (26256 bytes in 0.040s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1626 KB/s (196521 bytes in 0.118s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
ro.wifi.channels=
ro.product.cpu.abi=armeabi-v7a
ro.product.model=SAMSUNG-SGH-I897
ro.build.tags=test-keys
ro.build.version.release=2.1-update1
ro.build.description=SGH-I897-user 2.1-update1 ECLAIR UCJH7 release-keys
ro.product.brand=Samsung
ro.product.device=SGH-I897
ro.build.version.incremental=UCJH7
ro.build.type=user
ro.build.date.utc=1282903617
ro.board.platform=s5pc110
ro.product.name=SGH-I897
ro.product.board=SGH-I897
ro.build.user=jetaek.lee
ro.build.display.id=ECLAIR
ro.build.version.codename=REL
ro.build.product=SGH-I897
ro.build.id=ECLAIR
ro.build.version.sdk=7
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.region=GB
ro.build.date=2010. 08. 27. (???) 19:06:57 KST
ro.product.locale.language=en
ro.build.host=sep-11
ro.build.fingerprint=Samsung/

[TOOL] Perma-Temp-Root Solution [Mac/Linux/Windows]

Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
Its stable & works 100%
I personally have not lost root with this method in over 48 hours.
Zero com.noshufou.android.su crashes.
Before Using!!
HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
Restart your phone!
Lastly, if you're getting com.noshufou.android.su force close errors
Uninstall superuser prior to running scripts.​
If you Lose Root, all you have to do is open Terminal Emulator & type fixsu
No More Rebooting & running the exploit again for R/W on system to get Root back in place!​
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal and type fixsu to get root back.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot.
Q. Can I push & remove items to system and will it work?
A. Yes, but all changes are reset on a reboot.
~~~~~~~~~
For Mac/Linux users
Once downloaded, extract vividtemproot.zip to your home/root folder.
(Typically named after your login, has a house icon in Finder's sidebar of places)
Open folder vividtemproot, double-click run_me_mac (or run_me_linux)
and thats is all!
Click here to download for Mac/Linux
(Updated 11/14 - 23:50)
~~~~~~~~~
For Windows Users
Once downloaded, extract where ever you please.
Double click _RUN_ME
and enjoy!
Click here to download for Windows
(Updated 11/14 - 23:50)​

Link for Windows is the Mac file...

CharlieMurphyIVXX said:
Link for Windows is the Mac file...
Click to expand...
Click to collapse
Thank you :]
Fixed

Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!

thecubed said:
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
Click to expand...
Click to collapse
I haven't lost root in going on ~60 hours, as as a newbie here, you definitely know far more than I do!
As you'll see in the fixsu, I redundantly copy su from /vendor/bin
to /system/xbin/ from which I hardlink (as you'd know is virtually the same as bind mounting in this case) to /system/bin
I added the fixsu, as a last resort, in case the something would dissolve, but unless someone really fudges something up, the fixsu shouldn't be needed
As my programming teacher once told me: the code doesn't need to be pretty as long as it works.
And through that philosophy I've used a lot of redundancies, that may or may not need to be there,
but they'll definitely keep anyone from having any sort of issues using the scripts!
P.S. Thank you :]

Thanks, I'll try this out and report back.
Sent from my HTC PH39100 using xda premium

It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!

http://pastebin.com/MkGHWadW
appears to have failed for me
Drew

The device rebooted itself -- the "root" is lost

guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .

rinnycoop121 said:
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
Click to expand...
Click to collapse
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!

drewdatrip said:
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
Click to expand...
Click to collapse
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.

3f62011 said:
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
Click to expand...
Click to collapse
I don't own a Windows box, an had to write the Windows bat file
without giving it a test run for errors.
I'm sure I did mess up the syntax, an probably left some command that isn't windows relavent at the end of the script.
No worries, you've got root, and shouldn't loose it.

bjg222 said:
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
Click to expand...
Click to collapse
I tried to pipe all errors out to null, as I took a mash up of your code, my code, and and another guys code, and left a lot of "in case it exists" type of lines in the code, to make sure no one would have any issues.
Apparently I didn't pipe it all to null well enough
The mac/linux version you only see 'starting' and 'finished' haha

rpendrick said:
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
Click to expand...
Click to collapse
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium

drewdatrip said:
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.

rpendrick said:
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
Click to expand...
Click to collapse
Yes, works much better with something in the folder.

Scrog said:
Yes, works much better with something in the folder.
Click to expand...
Click to collapse
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium

drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I was able to update superuser, but titanium back up doesn't see either SD card.

drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Superuser crashes when it is the lastest versions.
Do a google search for superuser.apk 3.0
I thought I included it in the package, but perhaps, once again in a rush
fudged that up too...

Droid 4 Utility ICS Only

This tool is based on the original D4 Utility with additions and rewrites by me. Doing any of this is at your own risk.
08/14 Tool Version now 2.0 !!! THE JUMP TOOL IS DEAD!!! No reason for this now that we have ICS Fastboot files.
08/31 Tool Version now 2.1 Here's what's new
10/25 Tool Version 2.2 corrected minor script error and updated to safestrap 3.05
1. Set of instruction included within the tool. Once you open the tool select menu 1 to display them. This is a .txt file so you must have some reader (I use notepad++).
2. Safestrap 3.05 (Thanks Hashcode)
3. Latest Superuser (3.1.3) and binary (3.1.1)
4. Restore to 6.16.217 ICS or upgrade a GB phone to 6.16.217 ICS with option to save or erase data
5. Unroot script - This will remove superuser, the su binary and busybox. However if you boot into recovery it will still indicate root or at least past root (qe display in recovery). Even a fastboot with data wipe will not reset this.
Where to download: http://d-h.st/users/jsnweitzel
Add the ICS fastboot file to the lite tool to run menu 11 or 12. Get it here: http://sbf.droid-developers.org/cdma_maserati/list.php Then unzip it and add the files to the "files" folder of the tool.
If you have trouble connecting your phone be sure you have the latest drivers installed from moto:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/78460/p/30,6720,8302
Use this tool at your own risk.

Can't wait to try this to go from .213 to .215! Will let you know my results. Right now, there are too many bugs in .213 for me to use it on a daily basis, hope .215 is better!
Edit: nevermind, d-h.st is back up again!
Edit 2: update went very smoothly, thanks!
Edit 3: fixed my issues with a data wipe - almost got bricked, but your tool saved me again! Now I'm back in action with .215 and having the best phone experience ever. If I could hit 'thanks' multiple times, I would!

Works just fine! Thank you very much!

..

Works great!!! Thanks

I just pushed this to my phone and now it is running soo much better (mostly due to the new build of the ICS leak) I was missing a home button and the lock screen, but so far not seeing too many bugs and I have root again. Brilliant! Cheers!

Just giving post a bump, updated tool.

FYI, there is no link to the .217 OTA zip in the OP.

Dave Lister said:
FYI, there is no link to the .217 OTA zip in the OP.
Click to expand...
Click to collapse
Thanks for the heads up. Fixed the link.

So let's see I'm reading this correctly.
I installed the 217 leak file today (got tired of waiting for the ota soak test) and lost root.
To get it back I just need the lite version linked above, is that correct?

bdbraaten said:
So let's see I'm reading this correctly.
I installed the 217 leak file today (got tired of waiting for the ota soak test) and lost root.
To get it back I just need the lite version linked above, is that correct?
Click to expand...
Click to collapse
Yes only menu 9 will not work, everything else should be good.

jsnweitzel said:
Yes only menu 9 will not work, everything else should be good.
Click to expand...
Click to collapse
Any thoughts on what's going on, I tried it and ran option 8 to root but my root apps aren't working. Here's what the screen says:
---------------------------------------------------
[*]
[*] Motorola ICS Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Rebooting device...
[*] Waiting for device to reboot...
[*] Rebooting device again...
[*] Waiting for device to reboot...
[*] Attemping persistence...
remount succeeded
1397 KB/s (0 bytes in 22364.000s)
2321 KB/s (0 bytes in 2005736.000s)
2196 KB/s (0 bytes in 843503.000s)
[*] Cleaning up...
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
---------------------------------------------------
So it looks like it worked I don't see superuser in my app drawer and when I try an app that can use root like estrongs file explorer it says "feature not available"
Any ideas? I've tried it multiple times and with two different computers (one on vista the other xp pro) and same result.
Thanks.

It look like the install of busybox and superuser were skipped (failed is probably more accurate) for some reason. Did you have the phone set to "MTP" or "PTP" mode. You don't want to run it in mass storage.

jsnweitzel said:
It look like the install of busybox and superuser were skipped (failed is probably more accurate) for some reason. Did you have the phone set to "MTP" or "PTP" mode. You don't want to run it in mass storage.
Click to expand...
Click to collapse
I don't remember which one it was set as. Does it make a difference on mtp or ptp mode for which one works better?

I have only seen an issue with the mass storage mode. Check in the tool files folder and be sure that a copy of Superuser.apk is there. If it still doesn't work I can't see why. As a last resort you could try installing it from the market.

jsnweitzel said:
I have only seen an issue with the mass storage mode. Check in the tool files folder and be sure that a copy of Superuser.apk is there. If it still doesn't work I can't see why. As a last resort you could try installing it from the market.
Click to expand...
Click to collapse
Thanks for the help, the superuser is there in the files folder.
I'm debating if I should try it from the market or just try fastbooting the phone and see what happens.
I only want to root to get rid of the bloat, not sure if I'll install custom roms or not yet on this one.

You can "disable" some apps without root. Looking under settings and apps. Select one and hit disable. For some you will have to uninstall updates first.

jsnweitzel said:
You can "disable" some apps without root. Looking under settings and apps. Select one and hit disable. For some you will have to uninstall updates first.
Click to expand...
Click to collapse
I'll look into that.
I'm going to try downloading the full tool and try that, I was just using the lite version. It shouldn't make a difference but I figure it doesn't hurt to try it. If that fails I'll try to decide what my next step will be.
I tried to install superuser from the market but it wouldn't let me.

just get the one on the market and update the binary and it should work fine.. tib wiil fix the perms when you run it the first time. tried it b4 and it works fine

myfishbear said:
just get the one on the market and update the binary and it should work fine.. tib wiil fix the perms when you run it the first time. tried it b4 and it works fine
Click to expand...
Click to collapse
Are you talking about the superuser app from the market? I tried to get it and it wouldn't let me install it, claims it's already installed but it doesn't show up in my app drawer.
---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------
I GOT IT!!!!!!!!
I had an idea based on the comment about getting from the market so I tried the idea and it worked.
I copied the superuser apk file over to my sd card, I installed it from there and said to go ahead and replace the file that was there. I opened it directly after the install and updated the binarys (said it was current but did it anyway) now my root apps ask for and get super user permission.
So it looks like I'm up and running.
Thanks,
Brent.

[HOW TO] Rooting the LT25i without unlocking the bootloader (4.0.4)

Rooting the Xperia V: How-To.
(XDA member datagubben requested that I post this here, as per http://forum.xda-developers.com/showpost.php?p=36753824&postcount=19)
Mirrors for the files provided are welcome.
This root method is courtesy of Xperia-Freaks.org, originally developed for the Xperia AX, translated and adapted by me for the LT25i.
Supported firmware: 9.0.1.D.0.10, probably also 9.0.D.0.484.
Reportedly does not work with 9.1.A.0.489.
You will need: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (direct link: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf) or the original LT25i-SOL21_9.0.F.0.195.ftf (this FTF has its loader.sin replaced with LT25i's loader.sin; the trimmed version lacks unneeded files like baseband etc. and as such removes unneeded wipe/exclude options, leaving only the three files we actually need) and an LT25i FTF of your choice; the rootkit (this one is "translated" and edited for convenience; do NOT use regular GX/SX rootkits blindly as they require modification).
Make a backup using the stock Backup and Restore app in case something goes wrong so you can perform a factory reset.
Once rooted, you can safely restore from that backup.
1. Power the phone up in Flashmode (hold Volume down; connect USB). Using Flashtool, flash TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (or the untrimmed version if you like fiddling with excess checkboxes) using:
kernel.sin
loader.sin
system.sin
(Remember to uncheck the wipe options!)
2. Unplug USB. Turn the phone on. Enable USB debugging if it wasn't enabled previously. Connect the phone via USB again.
3. Unpack the Rootkit and start it (run install.bat). Confirm restore of the backup as requested, and press any key in the cmd window. Press any key again; the device will reboot (twice).
4. Run adb shell. To do it, you can open the rootkit folder in Windows Explorer, and shift-Right Click the "files" folder inside it. Choose "Open command window here". Type "adb shell" in that window.
If you're presented with a prompt that ends with "$", type "su".
The prompt should end with "#" now.
Type "echo ro.kernel.qemu=1 > /data/local.prop" and check if the file was created successfully by typing "ls -l /data/local.prop": below you will find an example of what the output looks like.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo ro.kernel.qemu=1 > /data/local.prop
echo ro.kernel.qemu=1 > /data/local.prop
[email protected]:/ # ls -l /data/local.prop
ls -l /data/local.prop
-rw-r--r-- system system 17 2013-01-15 17:29 local.prop
[email protected]:/ #
5. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
loader.sin
system.sin
(Remember to uncheck the wipe options!)
6. Turn the phone on. Open a command prompt into the files subfolder of the rootkit folder, like in step 4, or return to that window if you haven't closed it.
Type "adb shell". If you get a $ prompt, try "su" to get to "#". Once in adb, type "/data/local/tmp/step2.sh", then "reboot". The phone will reboot.
When it boots back, run adb shell again, and type "/data/local/tmp/step3.sh". You'll witness another reboot or maybe two. You should be rooted now.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # /data/local/tmp/step2.sh
/data/local/tmp/step2.sh
0+1 records in
0+1 records out
57 bytes transferred in 0.001 secs (57000 bytes/sec)
[email protected]:/ # reboot
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # data/local/tmp/step3.sh
data/local/tmp/step3.sh
43+1 records in
43+1 records out
22364 bytes transferred in 0.002 secs (11182000 bytes/sec)
1647+1 records in
1647+1 records out
843503 bytes transferred in 0.123 secs (6857747 bytes/sec)
2119+1 records in
2119+1 records out
1085140 bytes transferred in 0.089 secs (12192584 bytes/sec)
7. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
kernel.sin
loader.sin
(Remember to uncheck the wipe options!)
Do NOT skip this step: you need the LT25i kernel on your LT25i system!
8. Let's finish.
We will need adb shell once again. This time, you will need to type a few lines as follows:
Obtain root:
su
Remount /system:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
Remove /data/local.prop since it's a security hole; this is important and is normally done by the rootkit's step 3, but we needed to save the file to get to keep root access on our LT25i firmware:
rm /data/local.prop
And finally reboot:
reboot
Code:
G:\Android\LT25i\rootkitGXSX_v3\files>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
[email protected]:/ # rm /data/local.prop
rm /data/local.prop
[email protected]:/ # reboot
reboot
Done. You now have busybox, Superuser and su on your stock LT25i firmware.
Remember to clean up those pesky au apps.

Will link to the all in one. Many thanks

Good job translating!
Sent from your backyard...
Slender watches what you do...

I did some n00b experiments:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse :crying:
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?

datagubben said:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?
Click to expand...
Click to collapse
Using the Bin4ry approach should be possible since as far as I know it's the exact same backup/restore timing exploit, you probably need to recreate /data/local.prop though before flashing the V's system.sin. Or do you mean reducing the number of flashing operations to 2? That won't work, we need to regain root on V's system to get it to enable adb root shell with the V's kernel.
If you delete something from /system/app and the phone starts rebooting, it means you just deleted a part of the Timescape framework, I'd presume?

This method will clean up my installed app?

Dude i'm step 6 but I keep getting this prompt.
C:\Users\user\Documents\Development\Xperia\Xperia V\rootkit-sony\files>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
edit: now do i panic?

Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?

Gasai Yuno said:
Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?
Click to expand...
Click to collapse
Found my mistake, I'm going to try again Fifth time!
Edit: Done! Love you dude.

All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.

sunny7day said:
All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.
Click to expand...
Click to collapse
Because "some japanese" firmware is with exploit before it was fixed by Sony

where can I download official hong kong firmware? I am stuck on step 5.

sunny7day said:
where can I download official hong kong firmware? I am stuck on step 5.
Click to expand...
Click to collapse
I haven't seen HK firmware beeing uploaded here on XDA yet, but you can make yourself with PPC + flashtool (its not difficult, look in the forum how to do).

I just got the hk firmware and finished all the steps in the first post, now i am rooted.
Yes it is rooted but it left alot of unwanted au japanese sofware in my phone.
It should be noted in the first line in the first post of this thread.
But thank you anyways.
So, I have to wipe and re-flash my stock HK firmware.
Are there any other way to root my Xperia V without flashing other firmware?

If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
Remember to clean up those pesky au apps.
Click to expand...
Click to collapse
sunny7day said:
Are there any other way to root my Xperia V without flashing other firmware?
Click to expand...
Click to collapse
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.

Gasai Yuno said:
If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.
Click to expand...
Click to collapse
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!

datagubben said:
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
Click to expand...
Click to collapse
And if you do please PLEASE share it as we could do with it here
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
Click to expand...
Click to collapse
not a scooby doo fan then?
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
There is no way to know untill it lands on our devices, Sony can(and do) monitor what we do on this forum and, allthough they are quite dev friendly, do find way to fix the loopholes we exploit to get root access. They want us only to get that via an official unlocking from their site. You cant blame them for that, they are a big company and have lots of ways of losing contracts if they cant secure their system.
But you can be your bottom dollar tha if they close that exploit, we will find another way
[/quote]
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Click to expand...
Click to collapse
I know this is a personal message but the rules state this is an english speaking forum. You can post in other languages but an english translation is always required. (I know you dont need this next bit but..) Please use google translate if you have trouble with getting an english translation
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!
Click to expand...
Click to collapse
lol!

I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
I don't watch Scooby Doo.
I speak japanese and I said "I lived in Tokyo but not now".
S,h,i,t

datagubben said:
I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
Click to expand...
Click to collapse
I meant the other guy, in response to your post about making his own ftf, if he does, he should post it and share
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
Click to expand...
Click to collapse
not sure
I don't watch Scooby Doo.
Click to expand...
Click to collapse
google it and watch, a clasic kids cartoon with a classic catchphrase of "I would have got clean away with it, if it wasnt for you PESKY kids!
I speak japanese and I said "I lived in Tokyo but not now".
Click to expand...
Click to collapse
thanks
S,h,i,t
Click to expand...
Click to collapse
I gathered that

datagubben said:
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
c) Make a copy of your stock FTF file. Open the copy in Total Commander or 7-Zip. Delete everything except the manifest, loader.sin, kernel.sin and system.sin. No more app_log.sin appearing in Flashtool, yay!
d) Depends on two factors.
First, if the 4.1 update will replace the keys used to sign .sin files, removing compatibility with older firmware, this approach will be unavailable. This is what Motorola did with the DROID 2/X/2 GLOBAL.
Second, provided they don't replace the bootloader, and we can still flash back to 4.0: whether we will be able to retain root during firmware update (via OTA RootKeeper or whatever else exists).
As for the language filter, use Kunrei romaji (you know, the system where you use “si” instead of “shi” for し and “ti” instead of “chi” for ち) to work around it.

[Q] Too many symbolic links generated - rooting

Hi
So i have the Xperia Z and went about rooting it as i've always done with all my devices.
http://forum.xda-developers.com/showthread.php?t=2186368
Followed the usual as always kindly provided by DoomLord.
It "kinda" worked, it never asked for permissions for SuperUser so anything requiring root access took a while then timed out and failed. So, i installed SuperUser from the android market and it worked well, for a few installs like themes etc. Root Checker was happy it had root access, ES Explorer happily let me overwrite default themes with root access. Then ES Explorer crashed, the root checker said i no longer had root access and problems arose.
Im no longer rooted for some reason but i can no longer re-root.
I get the error "Too many symbolic links encountered" when trying to write the system/bin SU file. I can't do it manually and i cant do it with the flash tools.
Here is the rooting tool log:
Main point
"/system/bin/su: cannot open for write: Too many symbolic links encountered
Unable to chown /system/bin/su: Too many symbolic links encountered
Unable to chmod /system/bin/su: Too many symbolic links encountered"
Anyone able to help ?
Thanks
Adam
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\marshala>cd\
C:\>cd root
C:\root>runme
----------------------------------------------------------------------
Easy rooting Toolkit for XPEIRA Z SO-02E (ver 1.0.1)
from [user=2526007]@goroh_kun[/user] idea
by HUHKA (@huhka_com)
ENGLISH Translation thanks to [email protected]
----------------------------------------------------------------------
[*] To do:
(1) get root access
(2) intall busybox
(3) install su
(4) disable /sbin/ric
[*] Tested version:
üE10.1.D.0.317
üE10.1.D.0.322
[*] To be prepared in advance:
(1) install USB driver in your PC
(4) connect your phone to PC
----------------------------------------------------------------------
Press any key to continue . . .
### beginüI ###
waiting for device
adb server is out of date. killing...
* daemon started successfully *
transfer files to your phone part1
13 KB/s (442 bytes in 0.031s)
0 KB/s (170 bytes in 1.000s)
----------------------------------------------------------------------
[*] description:
1. press the button to restore the data in your phone operation.
Now unlock your device and confirm the restore operation.
if Restoring data is complete,
Press any key to continue . . .
----------------------------------------------------------------------
[*] description:
1. Dial *#*#7378423#*#* and select "Service tests" in your phone operation.
2. select "Display" in your phone operation.
* Screen is white until completion of restart
Starting: Intent { act=android.intent.action.MAIN cmp=com.sonyericsson.android.s
ervicemenu/.ServiceMainMenu }
executing /data/local/tmp/onload.sh ...
----------------------------------------------------------------------
[*] description:
1. push power button, so turn off the screen
2. push power button, so turn on the screen
* Repeat steps 1 and 2
----------------------------------------------------------------------
transfer files to your phone part2
4526 KB/s (1096224 bytes in 0.236s)
0 KB/s (38 bytes in 1.000s)
0 KB/s (1022 bytes in 1.000s)
0 KB/s (96 bytes in 1.000s)
3970 KB/s (380532 bytes in 0.093s)
installing busybox,su,Superuser,etc...
intall /system/xbin/busybox ...
2141+1 records in
2141+1 records out
1096224 bytes transferred in 0.061 secs (17970885 bytes/sec)
intall /system/bin/su ...
/system/bin/su: cannot open for write: Too many symbolic links encountered
Unable to chown /system/bin/su: Too many symbolic links encountered
Unable to chmod /system/bin/su: Too many symbolic links encountered
intall /system/etc/install-recovery.sh ...
0+1 records in
0+1 records out
38 bytes transferred in 0.001 secs (38000 bytes/sec)
4597 KB/s (1468798 bytes in 0.312s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Cleaning up
now reboot!
wait for device...
### finishüI ###
Press any key to continue . . .

Noone ?

Try repairing with pc companion, and start over.

^ yup what he said, or better yet use Sony Update Service.
Make sure you understand doomlord's procedure before proceeding, missing one step may be the cause of it.

LitoNi said:
^ yup what he said, or better yet use Sony Update Service.
Make sure you understand doomlord's procedure before proceeding, missing one step may be the cause of it.
Click to expand...
Click to collapse
Damn, the thought of having to redo all my apps and stuff is daunting. I dont trust the standard backup software (non-root) to be able to set my phone up back how it was, well i know it wont
I do understand the steps, i had root access for a while, but like others on the rooting thread, i didn't get superuser asking to set any permissions and it never would, until i uninstalled it from Apps, redownloaded it from the market and updated the binaries. Then i had root access for a few installs using CWM. I'm not sure how it lost it to be honest.
I'll do the restore and see how it goes the second time.

adamkm said:
Damn, the thought of having to redo all my apps and stuff is daunting. I dont trust the standard backup software (non-root) to be able to set my phone up back how it was, well i know it wont
I do understand the steps, i had root access for a while, but like others on the rooting thread, i didn't get superuser asking to set any permissions and it never would, until i uninstalled it from Apps, redownloaded it from the market and updated the binaries. Then i had root access for a few installs using CWM. I'm not sure how it lost it to be honest.
I'll do the restore and see how it goes the second time.
Click to expand...
Click to collapse
Follow this (thats what i did and i never had problems)
1) back up your files (like app backups ex. 3g watch dog, sms backup, whatsapp etc..., not full backups with CWM or the original sony back up, start fresh.
2) repair it with Sony update service
3) after repairing and logging into phone, wipe user data under settings > backups and restore (this procedure will remove all your internal files)
4) after doing all that, head to settings > developer tools and check the USB plug thingy, then head over to security and check the allow other apps to install thingy, then root it with doomlord thread's root
5) after rooting is done, you should now have superuser (SU1). go to play store and download superSU (SU2) <----(the chainfire one)
6) launch the superuser (SU1) (that it came with, the first one) and set up the app, then exit and head over to the (SU2) chainfire, SU(1) will ask you do you want to let SU(2) grant access to your files, click yes or grant.
7) go to settings > apps > and remove the superuser (SU1).
8) install CWM if you need.
stick with the chainfire (SU2) and it should be okay. Dont uninstall it.
for me i havent had any problems with this, so hopefully it will work for you as well.

LitoNi said:
Follow this (thats what i did and i never had problems)
1) back up your files (like app backups ex. 3g watch dog, sms backup, whatsapp etc..., not full backups with CWM or the original sony back up, start fresh.
2) repair it with Sony update service
3) after repairing and logging into phone, wipe user data under settings > backups and restore (this procedure will remove all your internal files)
4) after doing all that, head to settings > developer tools and check the USB plug thingy, then head over to security and check the allow other apps to install thingy, then root it with doomlord thread's root
5) after rooting is done, you should now have superuser (SU1). go to play store and download superSU (SU2) <----(the chainfire one)
6) launch the superuser (SU1) (that it came with, the first one) and set up the app, then exit and head over to the (SU2) chainfire, SU(1) will ask you do you want to let SU(2) grant access to your files, click yes or grant.
7) go to settings > apps > and remove the superuser (SU1).
8) install CWM if you need.
stick with the chainfire (SU2) and it should be okay. Dont uninstall it.
for me i havent had any problems with this, so hopefully it will work for you as well.
Click to expand...
Click to collapse
Thank you very much LitoNi !
Ah ok i was in the middle of doing the Sony Backup, i guess i'll just do app backups and images/video's i'll extract off myself and re-import manually.
Thanks alot, i'll update this thread when im done

LitoNi said:
Follow this (thats what i did and i never had problems)
1) back up your files (like app backups ex. 3g watch dog, sms backup, whatsapp etc..., not full backups with CWM or the original sony back up, start fresh.
2) repair it with Sony update service
for me i havent had any problems with this, so hopefully it will work for you as well.
Click to expand...
Click to collapse
Uh oh i have a huge problem now. I did the Sony Update Service, I got "The Update was Unsuccessful " ... try again blah blah but my phone now wont boot. Grrrr... When turning on it vibrates, comes up with "Sony" and then goes off again.
I'm trying the SUS again but im not hopeful. Argh. Looks like i'll be taking a trip to a Sony shop. I hope they can't tell i messed around with the software and refuse to honour the warranty

Oh phew, the 4th time i did the SUS it managed to complete. Scary

OK root seems to have stuck well this time.
Thanks for your help

LitoNi said:
Follow this (thats what i did and i never had problems)
Click to expand...
Click to collapse
I did pretty much the same, but didn't use SuperSU, but Koush's Superuser.

"/system/bin/su: cannot open for write: Too many symbolic links encountered
Unable to chown /system/bin/su: Too many symbolic links encountered
Unable to chmod /system/bin/su: Too many symbolic links encountered"
I think you already have the symbolic link on /system/xbin/su
For me the su root file is in xbin folder!
check if you have a su file in the xbin folder.