Develop Bugs

[Q] How to get 2.2 with root, when I forgot what root in 2.1 I did.

Like it says, I do not remember what root I applied to my Dinc last month when I got it, I basically only rooted it for wireless tether. But once finding out all I can do with root I decided I want full root, and I think I would like 2.2 (maybe not) I really don't care which version I have, as long as I can have full root.
But I think it is only for non-rooted phones. But I guess technically mine is not a complete root, it is more of a super-user root. Basically I do not know exactly what I want, so I want to have root so I can change themes and things weekly
So in your expertish opinion what would you recommend I follow?
Edit: I just found out what method I used, well sort of, I still have the files I used. the readme file says this, and these commands I put in the prompt when I was hooked up to my phone:
1.bat
adb push payload-update.zip /sdcard/update.zip
adb shell
su
export PATH=$PATH:/system/bin
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/xbin/su
reboot
Thanks in advance for your help!!!

Cant get root! Help plz!

Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!

tranceonline said:
Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!
Click to expand...
Click to collapse
1 & 2 ...
Who can say? You could spend some time examining logcat and dmesg outputs but why? May as well just accept it went wrong and start again.
3.
You want this RUU file.
The most reliable method to flash it would be here. Make it into a pd98img.zip.
4.
After using the visionary r14 tool to temproot I then used this excellent tool to get permanent root. The tool can be used to get eng hboot s-off if you want it as well.
You should also get radio s-off using another excellent tool. Radio s-off is the single best thing you can do to protect yourself from rogue OTA updates which kill root.
5. If your phone explodes its not my fault.
I'm not sure why I'm helping a guy like you though. Fancy forking innocent children
EDIT: Just corrected my post slightly.

i'll try what u said.
I dont know why the rage command forked all the children
I am only thankfull, i did not have had to see that!!
so i am in the bootloader, first it says "no blablaimg.nbh" and so on, than it starts checking the pd98img.zip and after that, its back in the main menu of the bootloader and nothing happens

If you get stuck I'll try my best to help if I'm still around.

it doesn't ask me if i want to flash. first it loads when its says "Checking pd98img.zip" and a blue bar at the right upper corner starts loading. after that, it says "checking pd98img.zip"
when thats finished, nothing happens.
than i reboot my phone and everything is like before
it says "System UID Inconsistent" and i can press "I'm feeling lucky"
Edit: Just saw, that the browser is fully gone! no app in the list anymore!
Edit1: In the zip is an exe file? is this correckt? or is this file only for flashing through pc?
Edit3 LOL: i did a factory reset in the bootloader.
everything is back to stock and working fine now!

OMFG THATS A FU***ING JOKE!!
I did a factory reset to stock, configurated everything and what do my eyes see?
the superuser.apk! i tried SU in erminal and got SU rights! WTF???
how did THAT happen??
i dont know, but i have root now.
Tried to reboot and root stays permanent. This is ok for now i think.
Becaus i read that a Custom ROM don't gives u sooo much advantage, ill stay at stock with root for now. it runs fine and until it starts lagging to much or something else, i'll stay at stock ROM i think
Thank you very much for your help mox !

Ok, now there is another problem.
I have root, setcpu and terminal work fine. Titanium backup les too and says busybox is working too. Solo I wanted to use root explorer and delete some Stuff out of the /system/app folder. Things like amazon mp3 and so on. But I can't get read write rights in that folder. Why that? Can anyone help plz?
Sent from my Desire HD using XDA App

[Q] Problem with ClockworkMod

Hello all,
So, I recently rooted my Epic 4G using the following thread as a guide: http://forum.xda-developers.com/showthread.php?t=770388
The root worked great, but ClockwordMod isn't quite working as planned.
If I boot the phone holding Power+VolDown+Camera it boots into ClockwordMod, but if I use ROM Manager to try and reboot into ClockworkMod and backup my current ROM, it just takes me to the stock Android recovery screen.
Any ideas as to why this is happening?
Help would be greatly appreciated!
Also, when I download ClockworkMod through ROM Manager, it creates an update.zip on the root of my SD Card, but when I try flashing it, it won't go through.
Also tried manually entering Clockwork and flashing it there, and it went through, but ROM Manager still doesn't work.

You need the recovery redirector. The easiest way to get it is to run the one-click root and recovery or install a rom with the redirector in it.
The other way is to download the one-click zip and unzip it on your sdcard. Copy the files below from the one-click to the same place on your phone.
/system/bin/recovery
/system/bin/recoveryfiles/
/system/bin/recoveryres/
Then type the following commands into a terminal program.
busybox chmod -R 0755 /system/bin/recoveryfiles/*
busybox chmod -R 0755 /system/bin/recoveryres/*
chmod 0755 /system/bin/recovery
sync

DiGi760 said:
You need the recovery redirector. The easiest way to get it is to run the one-click root and recovery or install a rom with the redirector in it.
The other way is to download the one-click zip and unzip it on your sdcard. Copy the files below from the one-click to the same place on your phone.
/system/bin/recovery
/system/bin/recoveryfiles/
/system/bin/recoveryres/
Then type the following commands into a terminal program.
busybox chmod -R 0755 /system/bin/recoveryfiles/*
busybox chmod -R 0755 /system/bin/recoveryres/*
chmod 0755 /system/bin/recovery
sync
Click to expand...
Click to collapse
Followed the second part of what you suggested (manually copying the files, since the one-click script didn't work when I first rooted), and it still boots into the Android recovery.
After rebooting I verified the files were still in /system/bin and they were.
Although, looking at that script, it first checks that the OS version is Froyo.
Is the fact that I'm still on stock (rooted) Eclair the problem?

which one click root program yall talking about ... im stuck here to

Visionary r7 or visionary from android market NEEDED seriously to ROOT G2 plz help

I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...

Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
/data/local/tmp/root
Click to expand...
Click to collapse
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.

sammd301 said:
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Click to expand...
Click to collapse
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!

raitchison said:
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
Click to expand...
Click to collapse
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input

gbarayah said:
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
Click to expand...
Click to collapse
right now...neither method works not the "visionary r14 or ADB/RAGE/GFREE" I wouldn't mind using either method, the problem is that ADB/Rage/GFREE METHOD keep giving this error message "mkdir failed for /system/xbin, File exists" which I have done a ton of research and still can find a fixed,

sammd301 said:
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
Click to expand...
Click to collapse
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
ON YOUR PHONE:
1. Launch Terminal Emulator
2. Execute /data/local/tmp/rage
3. Wait for the message: "Forked #### childs."
4. Menu > Reset Term - Terminal Emulator will exit.
5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Click to expand...
Click to collapse
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)

Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.

ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Right now I going to try to use this command to fix the error and if it doesn't work, I will then try to flash a custom and see how that goes...Update will be posted as I go along....thanks for the kind help....

raitchison said:
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Click to expand...
Click to collapse
I will attempt to flash ClockWorkmod, once I try out "ianmcquinn" suggesting in trying to fix the rooting error...thanks for the help

ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Yes I used the wiki instruction to gain temporary root on the phone and proceeded to tryout the above command...I got mostly error with the command below is what I en-counted as I enter the command....
# /data/local/tmp/busybox killall rage
No error here just # prompt
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
No error again just # prompt
# rm -rf /system/xbin
Error "rm failed for -rf, Read-only file system"
# mkdir /system/xbin
Error "mkdir failed for /system/xbin, File exists"
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
Error "cp: can't stat '/system/xbin/busybox': Not a directory"
# chmod 4755 /system/xbin/busybox
Error "Unable to chmod /system/xbin/busybox: Not a directory"
# /system/xbin/busybox --install -s /system/bin
Error "/system/xbin/busybox: not found"
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
Error "cp: not found"
# cp /sdcard/su /system/bin/su
Error "cp: not found"
# chmod 4755 /system/bin/su
Error "Unable to chmod /system/bin/su: No such file or directory
I am now going to attempt the Clockwork custom rom flash..

Folks victory is mine....No, VICTORY IS OURS, I sincerely like to thank all of you all, who replied with helpful suggesting...especially the following members "raitchison" from West Hill, CA and "ianmcquinn" a true senior member of xda-developer.
This is what I did to finally get the phone rooted....
I took "Raitchison" advice by trying to use flash_image to flash ClockWorkMod recovery... but during the process I could not get pass copying file to the phone root system folder usind android terminal emulator ...so I input this command "chmod 777/system" to gain write access to the folder...after doing that I manually moved busybox file to system folder and attempted a rooting the phone using the rooting instruction from the HTC G2/DESIRE Z wiki site...at...
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
And this time around, everything went as normal after rooting the phone I open root required app and Wa La...no error message...
Guys I once again wants thank you all for the support....I also looked forward to help out others facing the same issue...so if anyone has encounter the same or similar issue please feel free to post here and I will response....

Can any one help me I am trying to close this thread...How do I go about doing it....thanks

There is no need to close the thread, if anyone has a similar problem and finds it via search they can come in here and bring the discussion back up, otherwise if there is no activity it will naturally fall to the bottom of the thread list.

It works for me I just did it yday using visionary and gfree all on my phone weird that it doesn't work for you?
Sent from my Liquid Metal using XDA Premium App

[boot script for locked and unlocked] chargemon for recovery boot

delete thread please!

Thanks! Checked the script and it seems properly coded! But where can we get the recovery? recovery.munjeni.gz? Am hoping for a new recovery with a stable build since most recoveries right now seems buggy.

Riyal said:
Thanks! Checked the script and it seems properly coded! But where can we get the recovery? recovery.munjeni.gz? Am hoping for a new recovery with a stable build since most recoveries right now seems buggy.
Click to expand...
Click to collapse
Here is, enjoy
Edit:
MIUI busybox which I have using on all roms:
adb push busybox /system/xbin/
adb shell chown root.shell /system/xbin/busybox
adb shell chmod 04755 /system/xbin/busybox
adb shell /system/xbin/busybox --install -s /system/xbin

New version is out, compatible in booth JB / KitKat, enjoy!

@munjeni
Doesn't seem to work with reboot from recovery action on android power menu

Riyal said:
@munjeni
Doesn't seem to work with reboot from recovery action on android power menu
Click to expand...
Click to collapse
Its working, but I have noticed some other bug when bootloader is locked, for example remount rw is not working since sony security is in kernel while bootloader is locked, I will try to fix in next few days! On unlocked bootloader there is no bugs!

Final version is out, for booth locked or unlocked bootloader! All RW isues solved, enjoy!

Okay, I am gonna be 'that guy'. Beyond installing BB and copying the recovery... how do I use this? There is mention of putting the script somewhere... is that a download separate from the chargemon.rar (that's been renamed)?

charlatan01 said:
Okay, I am gonna be 'that guy'. Beyond installing BB and copying the recovery... how do I use this? There is mention of putting the script somewhere... is that a download separate from the chargemon.rar (that's been renamed)?
Click to expand...
Click to collapse
Chargemon (extract file from rar) going to /system/bin , chown them root.shell , chmod them 755
recovery going to /system/bin , chmod them 644
busybox going to /system/xbin , shown them root.shell , chmod them 04755
and last step, install busybox symlinks by command "/system/xbin/busybox --install -s /system/xbin" , you are done.

Closed at OPs request