Hi Friends.
Please redownload defy_recovery.zip.sorry for my mistake.
please downloade attachment 474211
Here is the tut of how to root the defy uk 2.51 rom.
It's simple and easy way.
this will be a step by step tut.because of my poor english.i will try to explain more detial.
1、download attatch files.
defy_2.21_boot_only.sbf
View attachment 2.21boot.zip
defy_2.51_boot_only.sbf
View attachment 2.51boot.zip
defy_recovery.exe
View attachment 474211
2、flash the defy_2.21_boot_only.sbf via rsd then reboot in to system.
3、open you phone's usb debug mode(settings-application-development-usb debug mode),then double click the defy_recovery.exe you just downloaded ,it will process the root method.when it finished you phone is rooted with superuser and my clockworkmod recovery for defy.
4、the last step is flash the defy_2.51_boot_only.sbf via rsd lite.
5、and now your phone is rooted and customized recovery installed.
This method original comes from adlx @ modmymobile.com
if your like this tut.. please buy me or adlx a beer or I can buy another phone eg. Nexus S ...Thanks.
well done！
SteveChou said:
well done！
Click to expand...
Click to collapse
No way here... It doesn't fuction... There is a problem in the batch file:
Code:
@echo off
echo µÈ´ýÉ豸
adb wait-for-device
echo »ñµÃrootȨÏÞ
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell "chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin"
adb shell "./data/local/tmp/rageagainstthecage-arm5.bin & sleep 300;kill $!"
echo ÖØÐÂÁ¬½ÓÉ豸£¬¿ÉÄÜÐèÒªÒ»¶Îʱ¼ä
adb kill-server
call :sleep 10
adb start-server
call :sleep 30
echo È¡ÏûsystemÖ»¶ÁÊôÐÔ
adb shell "mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system"
echo °²×°Superuser.apk
adb push Superuser.apk /system/app/Superuser.apk
echo °²×°GoAPK MOD Recovery
adb push recovery.apk /system/app/recovery.apk
echo °²×°su
[B]adb push su /system/app/su[/B]
adb shell "chmod 4755 /system/bin/su"
echo °²×°busybox
adb push busybox /system/bin/busybox
adb shell "chmod 4755 /system/bin/busybox"
echo ÖØÉèsystemÖ»¶ÁÊôÐÔ
adb shell "mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system"
echo Íê³Éroot£¬ÇëÖØÆôÊÖ»ú
:sleep
(ping 127.0.0.1 -n 2 -w 1000 > NUL)> sleep.txt
(ping 127.0.0.1 -n %1 -w 1000 > NUL)> sleep.txt
del sleep.txt
You have to push su in bin directory non in app directory...
Code:
[B]adb push su /system/app/su[/B]
Please correct this bug.
I've also tried to upload any file thought adb (after r/w mount), but the phone doesn't recognize the apk's (Superuser and Recovery), they still invisible...
Any solution?
Well done, i did it this:
- Downloaded your 2.21boot.zip;
- Flashed thought RSD;
- Downloaded Android SDK with ADB;
- Download this Rootpack http://www.mediafire.com/?kjee8aj22j9m5zj;
- Extract this files in you /sdk/tools directory;
- Open cmd and point it in the directory with ADB;
- Run this commands:
Code:
adb devices
adb shell mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb shell mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
adb reboot
- Flash back to 2.51boot.zip
That's all!
Thank you sir!
sorry for my mistake...
bugfixed
View attachment defy_recovery.zip
its not working , root exe not found
socket84 said:
Well done, i did it this:
- Downloaded your 2.21boot.zip;
- Flashed thought RSD;
- Downloaded Android SDK with ADB;
- Download this Rootpack http://www.mediafire.com/?kjee8aj22j9m5zj;
- Extract this files in you /sdk/tools directory;
- Open cmd and point it in the directory with ADB;
- Run this commands:
Code:
adb devices
adb shell mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb shell mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
adb reboot
- Flash back to 2.51boot.zip
That's all!
Thank you sir!
Click to expand...
Click to collapse
Thank you for Your Bug Report.
Is there any way now to flash back to an older SBF?
fixed recovery.exe = its not working , root exe not found windows warning
batch reply "root.exe not found" after double click the defy_recovery.exe
also, from above reply:
"mount: Operation not permitted"
---------------------------------------------------------------------------------------------------
Hello,
I found out the way to get this rooting working.
everything stays the same until running the recovery.exe part
then please refer to the old rooting method
BUT using the rooting pack mentioned above link
then flash back to 2.51
it should work!
cheers!
cometcao said:
batch reply "root.exe not found" after double click the defy_recovery.exe
also, from above reply:
"mount: Operation not permitted"
Click to expand...
Click to collapse
Try This One
View attachment defy_recovery.zip
sorry sir,
About the root process, Why different with "http://bbs.goapk.com/forum.php?mod=viewthread&tid=48445&extra=%26page%3D1&page=1" ??
In goapk forum, the process2-> flash the original SBF? process3->Wipe data?
no need ?
Can this solution fit for Taiwan version 2.51.0?
Dear Sir:
Taiwan version could rooting by your solution!!
Thanks a lot~
you so great!!!
yeah~ it works for my Taiwanese version.
great job!
thanks~
Thank you very much for the HOW TOs.
Has anyone tried this on 2.51 HK rom?
hkipaqer said:
Thank you very much for the HOW TOs.
Has anyone tried this on 2.51 HK rom?
Click to expand...
Click to collapse
this will work on HK TW SG version 2.51
can we have any details about the rooting process ?
i want to get the Taiwan version of the Defy (Blurless)
1) is there any way to get root access, but still use the firmware that came with the phone ? (TW SG HK 2.51) i wouldn't mind doing some stuff manually...
2) As far as i know the original ROM of the Taiwan SG HK defy isn't available for download right ?
thanks for your hard work.
tenfar, thank you very much for your great work, I just rooted my HK DEFY.
Here are few steps added for those like me very new to Android and Root.
1. If you RSD Lite did not recognize your DEFY, download the USB driver here:
http://developer.motorola.com/docstools/USB_Drivers/
2. Power off DEFY. Then press 'Volume Up' and 'Power' together to boot to loader before you flash the SBF to your DEFY.
Happy rooting.
Thanks
Now I finished my HK defy rooted.
Very thanks for tenfar.
rooting wit Uk 2.51 possible..not other ROM flashable
hi Guys.....i have installed the UK JRDNEM_U3_2.51....and the root method desribed here worked too...
My question is: What happens after
- rooting the Uk U3_25.1 with our method (Sytem.boot.only 2.1 2.5 etc.)
- Restore system with SystemRecovery-App "Recovery Boot"
- i restored with a backup of t-mobile U3_2.21 (from my friend)
-worked
??
Build Number ist U3_2.21.0 now
Did I downgraded my system now?
If yes,
the Problem is then:
I cannot flash any ROM (RSD 4.9) from here http://and-developers.com/sbf:defy
except the JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB02C.0R_USAJORDANRTGB_P035_A011_HWp3_Service1FF.sbf
Therefore I dont believe i downgraded anything :-mad:
The flash-procedure with all other ROMs is the same:
RSD : finished --> Defy is not booting is hanging in the bootLoader-mode
Any Help?
Or anyone with a Vodafone 360 Original Backup that would be great
Thanks
I hope somebody can help me with this little anomaly.
Been trying to downgrade htc panache with gingerbread 2.3.3.
I was able to successfully execute the commands listed on the guide (http://forum.xda-developers.com/showthread.php?t=1178912) however, when i try to downgrade the misc_version, I get the "PERMISSION DENIED"
Here is how it goes:
> adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/*
> adb shell
> cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0: PERMISSION DENIED
According to the guide I should have seen something like this (--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...)
Please help
I've been following (or trying to) the same guide. I ran into the same error. From another member here, "aDeQ666", I found the following:
To be entered in adb
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Fixed my problem, but the next step, "./flashgc" , give the permission denied error. Still looking for answers ....
Type in
Code:
su
to gain superuser permissions before attempting those commands
They're most likely working in temp-root shell, where there is no su, and they don't need to call it explicitly.
The first case is solved, AFAIK.
The second case has some problems:
1) The first command is wrong. It should be:
cd /data/local/tmp/
2) A command is missing before running ./flashgc:
chmod 777 flashgc
3) You don't need to run ./flashgc in any case. You don't need a goldcard for downgrade, unless you have a Panache - and if you have and follow Panache guide, you'll see that a goldcard is already prepared in another form.
Nicgraner said:
Type in
Code:
su
to gain superuser permissions before attempting those commands
Click to expand...
Click to collapse
ive tried that, and it says su not found
How about actually reading the thread before posting?
Jack_R1 said:
They're most likely working in temp-root shell, where there is no su, and they don't need to call it explicitly.
Click to expand...
Click to collapse
Hi,
I'm trying to install busybox into a development board by downloading the pre-compiled binary and following the installation steps here. However, after doing so, I'm still unable to use the commands in /system/busybox. For example, when I try to run mknod, it shows me the following error:
Code:
./sh: mknod: not found
Basically, I did the following:
In Linux
Code:
adb root
adb remount
adb push busybox /system/busybox
adb shell
In device adb shell
Code:
cd /system/busybox
./busybox --install .
./sh
cd /system/bin
mv sh sh.android
ln -s /system/busybox/sh sh
It would seem like what I did to install busybox didn't work. May I know what's the correct procedure to install it?
I tried creating symlinks using the same ln command and it works, but do I have to do this manually for every single command?
Thanks!
goister said:
Hi,
I'm trying to install busybox into a development board by downloading the pre-compiled binary and following the installation steps here. However, after doing so, I'm still unable to use the commands in /system/busybox. For example, when I try to run mknod, it shows me the following error:
Code:
./sh: mknod: not found
Basically, I did the following:
In Linux
Code:
adb root
adb remount
adb push busybox /system/busybox
adb shell
In device adb shell
Code:
cd /system/busybox
./busybox --install .
./sh
cd /system/bin
mv sh sh.android
ln -s /system/busybox/sh sh
It would seem like what I did to install busybox didn't work. May I know what's the correct procedure to install it?
I tried creating symlinks using the same ln command and it works, but do I have to do this manually for every single command?
Thanks!
Click to expand...
Click to collapse
You didn't add /system/busybox to your PATH
Sent from my LT26i using XDA
Hi,
Where would I add it? init.rc or something?
Anyone?
Thanks!
I've got some questions about rooting on a locked device, which I may as well fire away.
I'm on .17 DE and has got it setup nicely, so I don't want to go to .29 just to try things out, and if something goes wrong it's better if the tablet has got a boot manager installed so rescue flash is possible. So, if someone who knows what they're doing wants to unroot and try this out (or just tell me if anything is feasible) I believe many people (primarily not rooted .WW-people, but maybe all current ICS-device owners) would be very happy.
Q1 - In the "tweaks" post seanzscreams mentions there may be a way to push build.prop to /system/ at boot.
Wouldn't it be possible to create some root stuff to push and run, like
(pushsu.bat)
Code:
adb wait-for-device
adb push su /system/
run it, reboot tablet
create a shell script file for permissions (or some other mojo) and push it aswell:
(permsu.sh)
Code:
chown 0.0 /system/su
chmod 06755 /system/su
and then run:
(pushper.bat)
Code:
adb wait-for-device
adb push permsu.sh /system/
and finally run and reboot:
(setperms.bat)
Code:
adb wait-for-device
adb shell sh /system/permsu.sh
?
Q2 - wolf849 is doing some funky stuff to downgrade firmware where he's mounting stuff at /data/local/tmp and rebooting for (I assume) permissions to write to the "stuff".
Would it be possible to test these commands (modified to possibly work or break something) (mmcblk0p1 = /system on my device):
(in adb shell or something)
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p1 /data/local/tmp
exit
Then reboot and see if /data/local/tmp is in fact /system mounted rw (ie "copy or push su"-able).
If the former wouldn't work because of symlinking rights maybe another approach would be a bat file, like
Code:
adb mv /data/local/tmp /data/local/tmp.bak
adb reboot
adb wait-for-device
adb ln -s /dev/block/mmcblk0p1 /data/local/tmp
adb reboot
Please don't try these suggestions if you don't know how to recover from possible bootloops or semibricks.
I would try them if I'd been unlocked and boot managered, but I'm out of luck if something goes wrong.
So I am trying to make a batch file that automatically flashes a custom bootanimation from my computer and I am having trouble with these commands.
adb wait-for-device shell "su -c 'ls /system/media'"
adb wait-for-device shell "su -c 'mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system'"
adb wait-for-device shell "su -c 'rm /data/media/bootanimation.zip1'"
Bascially I want to have the adb shell enter superuser mode, remount system in read write mode and delete the existing bootanimation.zip
Whenever I try and run this it says permission denied.
Please post your question in Android General so that the right experts may be of help.
Thread Closed. Thank you.