I have a Desire with OS 2.2 last update , it's Arabic android with the following software information :
Android version : 2.2
Baseband version : 32.49.00.32U_5.11.05.27
Kernel version : 2.6.32.15-gd96f2c0 htc-kernel and18-2 #1
Build number : 2.32.415.3 CL283905 release-keys
Software number 2.32.415.3
Browser version : Webkit 3.1
now my story is I paid lots of money to install the Middle East ROM that come with HTC Desire to Middle East since I bought my mobile from Poland Unlocked , with the last update we received in Middle East about 10 days a go I accepted the new update from 2.1 to 2.2 but some thing wrong happened and my mobile keep restarting so I paid lots of money again to get it back to work , now I decided to root it and learn how to install ROM by my self so i can save money , specially that I am Linux Geek and this things should be easy for me but because it's my only cell phone I have so I can not turn of my phone for long time , that's why I had to pay to fix it fast .
now I tried Unrevoked 3 but it's stuck where " Waiting for root.....( safe to restart if this doesn't work ) i repeat this many many times with Unrevoked 3.21 then Unrevoked 3.22
then I tried to downgrade the phone with this steps :
Linux/Mac Installation
1. Download and extract the utility in a terminal:
$ unzip downgrade23.zip
$ cd desire_downgrade
2. Enable USB debugging on your phone. Ensure 'ask me' is set under 'Connect to PC' setting, and 'charge only'. Plug in your phone.
3. Run the utility.
$ sudo ./downgrade.sh
4. Wait for the process to complete.
If you chose not to downgrade, you can now flash any RUU.
Windows Installation
0. Install HTC Sync (driver required).
1. Extract the downloaded zip file fully (do not just click on the zip file).
2. Enable USB debugging on your phone. Ensure 'ask me' is set under 'Connect to PC' setting with 'charge only'. Plug in your phone.
3. Double-click on the win-down file.
4. Follow instructions and wait.
in both cases I got this error :
error: device not found
although I tried windows " as administrator " and installed the driver many times , and tried Linux " as root " as well and I got the same error , change the USB port many times
i copied the PB99IMG.zip to my SD card and made the goldcard and boot by pushing the power button and Vol down it keep loading and in the end fail .
ANY HELP
copy from ./downgrade.sh output
Android 2.2 (froyo) to 2.1 downgrade utility.
=============================================
v2.2
For information, see this thread:
http://forum.xda-developers.com/showthread.php?t=768256
Press ctrl-c to exit this utility.
Checking for device... Waiting for device. Ensure USB debugging is enabled.
* daemon not running. starting it now *
* daemon started successfully *
Pushing essential files.
621 KB/s (26172 bytes in 0.041s)
112 KB/s (5392 bytes in 0.046s)
1005 KB/s (655360 bytes in 0.636s)
6 KB/s (315 bytes in 0.044s)
5 KB/s (264 bytes in 0.045s)
6 KB/s (334 bytes in 0.051s)
17 KB/s (819 bytes in 0.044s)
1267 KB/s (1120536 bytes in 0.863s)
0 KB/s (55 bytes in 0.055s)
6 KB/s (304 bytes in 0.047s)
7 KB/s (364 bytes in 0.048s)
14 KB/s (625 bytes in 0.043s)
Done.
Pushing recovery image to the sdcard.
Press n and enter to skip this stage, or just press enter to continue:
Beginning transfer. This may take a minute or two...
1738 KB/s (144182346 bytes in 80.973s)
1 KB/s (54 bytes in 0.046s)
Now verifying the downgrade file.
Downgrade file passed verification.
Obtaining root access.
Please wait a moment.
Done.
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
===================================================================
Your phone is now ready to be downgraded - rebooting to bootloader.
Starting in 10 seconds (ctrl-c to quit)
error: device not found
error: device not found
error: device not found
error: device not found
Complete.
* Now wait for the boot screen to appear.
* Press power to select the bootloader option.
* Wait for the recovery image to be located and checked.
* Press vol-up to start the update.
If you want to cancel the downgrade press vol-down.
Once flashed you can root your phone with unrevoked3.
Exiting.
Have the same issue. I have a Desire that has the same software. I've only had it a couple days, but haven't found a way to root it yet.
stealth658 said:
Have the same issue. I have a Desire that has the same software. I've only had it a couple days, but haven't found a way to root it yet.
Click to expand...
Click to collapse
i am searching now for more than 10 days , review most of youtube vedios most of forums , can't break this ROM and root it till now .
olvatito said:
Android 2.2 (froyo) to 2.1 downgrade utility.
=============================================
v2.2
For information, see this thread:
http://forum.xda-developers.com/showthread.php?t=768256
Press ctrl-c to exit this utility.
Checking for device... Waiting for device. Ensure USB debugging is enabled.
* daemon not running. starting it now *
* daemon started successfully *
Pushing essential files.
621 KB/s (26172 bytes in 0.041s)
112 KB/s (5392 bytes in 0.046s)
1005 KB/s (655360 bytes in 0.636s)
6 KB/s (315 bytes in 0.044s)
5 KB/s (264 bytes in 0.045s)
6 KB/s (334 bytes in 0.051s)
17 KB/s (819 bytes in 0.044s)
1267 KB/s (1120536 bytes in 0.863s)
0 KB/s (55 bytes in 0.055s)
6 KB/s (304 bytes in 0.047s)
7 KB/s (364 bytes in 0.048s)
14 KB/s (625 bytes in 0.043s)
Done.
Pushing recovery image to the sdcard.
Press n and enter to skip this stage, or just press enter to continue:
Beginning transfer. This may take a minute or two...
1738 KB/s (144182346 bytes in 80.973s)
1 KB/s (54 bytes in 0.046s)
Now verifying the downgrade file.
Downgrade file passed verification.
Obtaining root access.
Please wait a moment.
Done.
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
===================================================================
Your phone is now ready to be downgraded - rebooting to bootloader.
Starting in 10 seconds (ctrl-c to quit)
error: device not found
error: device not found
error: device not found
error: device not found
Complete.
* Now wait for the boot screen to appear.
* Press power to select the bootloader option.
* Wait for the recovery image to be located and checked.
* Press vol-up to start the update.
If you want to cancel the downgrade press vol-down.
Once flashed you can root your phone with unrevoked3.
Exiting.
Click to expand...
Click to collapse
adb/fastboot/bootloader drivers are not installed properly
its saying device not found which its an adb/fastboot command. even if it was preventing it you should find the device
EDIT:
am i reading this wrong? or did it downgrade successfully as now im reading it again it looks as if its waiting for the device then actually finding it after 4 attempts
Rastaman-FB said:
adb/fastboot/bootloader drivers are not installed properly
its saying device not found which its an adb/fastboot command. even if it was preventing it you should find the device
EDIT:
am i reading this wrong? or did it downgrade successfully as now im reading it again it looks as if its waiting for the device then actually finding it after 4 attempts
Click to expand...
Click to collapse
Actually after 4 attempts i think the script go to the next step , i even tried it without connecting my Desire and script keep taking step after another and keep giving errors till the script finish .
to be sure it's not Driver problem i used Linux to be sure the script will use adb command to find my device and root it , but it did not work , anyway , i will try again with this adb/fastboot and tell you the results
Thank you
I think, in Windows method, you should have uninstall HTC Sycn, after you installed it once for drivers. So, before starting this script, make sure htc sync isn't installed. But idk, just my guesses.
Reported it so that the mods can move it to the right section, you will get more hits there
Thread moved to Desire Q&A.
fixerDESIRE said:
I think, in Windows method, you should have uninstall HTC Sycn, after you installed it once for drivers. So, before starting this script, make sure htc sync isn't installed. But idk, just my guesses.
Click to expand...
Click to collapse
I did remove HTC sync and to be sure i tried Linux as well to be sure HTC sync will not effect , but still , it Push the PB99IMG.zip and restart for one time then waiting waiting for very long time with no action .
i think this HBOOT 0.93 is very hard to break , or nothing can break it till now , maybe soon some one will find some thing for it .
I had HBOOT 0.93 and rooted with Unrevoked 3.2 (the pulled version) but this also BRICKS your USB with the rest of the stuff, but you get the recovery flashed.
I cried for a few days that i didnt find a solution to unbrick my phone but i got help on irc #rootmydroid
There as a downgrade to 2.1.zip with the stuff as the teppic downgrade does it but its in the flashable zip, and as i had recovery in i used a cardreader to get the files over, rebooted to recovery, flashed the 2.1 downgrade.
Phone booted up as stock 2.1 without any recovery or root, but everything worked! HBOOT was 0.83 after this then i rooted again with an older version of unrevoked, i think it weas 3.14 and rebooted, had root and everything worked, nothing bricked.
I dont want to recommend this procedure but it is a way to do it.
Brick the phone to get recovery to be able to flash the downgrade 2.1 zip to be able to root with an older version of unrevoked.
All this was on a unbranded retail amoled desire with 2.2 OTA update, HBOOT 0.93.
But i had to do this cause my misc was broken, complained about bad blocks and stuff so i couldnt unbrick USB with traditional flash_image misc mtd0.img procedure.
kimozabe said:
I had HBOOT 0.93 and rooted with Unrevoked 3.2 (the pulled version) but this also BRICKS your USB with the rest of the stuff, but you get the recovery flashed.
I cried for a few days that i didnt find a solution to unbrick my phone but i got help on irc #rootmydroid
There as a downgrade to 2.1.zip with the stuff as the teppic downgrade does it but its in the flashable zip, and as i had recovery in i used a cardreader to get the files over, rebooted to recovery, flashed the 2.1 downgrade.
Phone booted up as stock 2.1 without any recovery or root, but everything worked! HBOOT was 0.83 after this then i rooted again with an older version of unrevoked, i think it weas 3.14 and rebooted, had root and everything worked, nothing bricked.
I dont want to recommend this procedure but it is a way to do it.
Brick the phone to get recovery to be able to flash the downgrade 2.1 zip to be able to root with an older version of unrevoked.
All this was on a unbranded retail amoled desire with 2.2 OTA update, HBOOT 0.93.
But i had to do this cause my misc was broken, complained about bad blocks and stuff so i couldnt unbrick USB with traditional flash_image misc mtd0.img procedure.
Click to expand...
Click to collapse
i do not know what you mean by BRICKS , and i tried to downgrade but it did not work too , i do not know why .
so can you please tell me step by step how to downgrade HBOOT 0.93 ?? note that i did try most of solutions i find online but it did not work , because after loading PM99IMG.zip , i got message faild
Same here,..
Hello guyz
Same problem here seems this OTA 2.2 Arabic Version is really hard to root...
http://forum.xda-developers.com/showthread.php?p=10083685#post10083685
ANY IDEAS ANYONE?!
Thanks all!
Finally
Finally , download Unrevoked3 version 3.32 and you will get your phone rooted in 10 minutes ,
HBOOT 0.93
Android 2.2
http://unrevoked.com
Enjoy
now i know this is pretty basic i couldnt find anywhere that tells you how to root on linux or any other unix os but here it is. Thanks goes to bubby!!! PLEASE check out his original post and HELP HIS EFFORTS
FOR bubbys ONE CLICK ROOT BUSYBOX INSTALLER SAMSUNG CONTINUUM V0.1!!
Finally, i after days of searching and trying to execute the commands for this root Manually i pulled my sd, and Formatted my phone and then Found the command to run the one click root on my continuum.
MAKE SURE YOU BACK UP YOUR FILES!! ITS A MUST,, ALSO DEFINATELY ODIN BEFORE THE ROOT.
Next, Open terminal Locate your Unzip folder i recommend you place the folder near your sdk folder Ex. CD ~/android-sdk-linux_x86/oneclickroot
since we've located the destination Check to make sure your in the right place ls. Look at the list make sure you see the run.sh Ok Now Type in the terminal
sh run.sh you should then see
One Click Root v 0.1 for the Samsung Continuum
Scripted by bubby323
read: 11: Illegal option -n
[: 18: Linux: unexpected operator
-e
Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-e
Copy and run the exploit (may take up to two minutes)
74 KB/s (5392 bytes in 0.070s)
0 KB/s (43 bytes in 0.075s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2961
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
it comes to adb connection will reset, restart adb server on desktop and re-login.
unplug your phone and wait 10sec and plug it back in
then you should see
Wait for phone to reconnect...
run.sh: 77: [[: not found
Mount system as r/w, cleanup old files, do some basic configuration
rm failed for /system/bin/playlogo, No such file or directory
failed on '/system/bin/playlogo-orig' - No such file or directory
Unable to chmod /system/bin/playlogo: No such file or directory
63 KB/s (4793 bytes in 0.073s)
Copying files onto phone...
361 KB/s (26264 bytes in 0.070s)
1120 KB/s (196521 bytes in 0.171s)
1219 KB/s (978414 bytes in 0.783s)
1207 KB/s (486948 bytes in 0.393s)
9 KB/s (483 bytes in 0.051s)
Setting permissions...
Installing busybox...
Waiting for phone to reboot...
run.sh: 117: [[: not found
Cleaning up files...
read: 129: Illegal option -n
now your rooted to check go to the market and try installing Titanium back-up
if all goes well you have root access
Just recently I have got my new HTC One X. I would like to have a root though, from what I have read here around the OneClick method do not work with 1.29.401.11 software version. I have tried it myself and this is what I got:
Code:
---------------------------------------------------------------
One-Click Root ToolKit For HTC One X!
Script by Max Lee from OneXRoot.com
Credits go to XDA users sparkym3 and Dan Rosenburg for exploit.
---------------------------------------------------------------
[*] This script will:
(1) root your HTC One X on ICS
(2) install Busybox
(3) install SU files
[*] Before u begin:
(4) Make sure to read full instructions at OneXRoot.com!
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
Start Rooting...
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount succeeded
1251 KB/s (91980 bytes in 0.071s)
rm failed for /system/xbin/su, No such file or directory
1255 KB/s (568647 bytes in 0.442s)
1254 KB/s (1075144 bytes in 0.836s)
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.340 secs (3162188 bytes/sec)
rebooting
All Done rooting HTC One X, check out OneXRoot.com for more cool stuff like ROMs, hacks, tips, and more!
runmelinux.sh: 49: runmelinux.sh: @pause: not found
It did not install superuser or busybox. I guess it all fails at creating/getting access to /system/xbin/su ?
I have read about some other methods to unlock the bootloader but as it states on the htcdev.com website if it will be executeted there is no way back to re-lock the bootloader. I guess there is no option to get the S-OFF without unlocking the bootloader at the moment for 1.29.401.11 software version? Seems like it worked for the previous version of the software, I wished I have ordered my phone few months ealier
withhope said:
Just recently I have got my new HTC One X. I would like to have a root though, from what I have read here around the OneClick method do not work with 1.29.401.11 software version. I have tried it myself and this is what I got:
Code:
---------------------------------------------------------------
One-Click Root ToolKit For HTC One X!
Script by Max Lee from OneXRoot.com
Credits go to XDA users sparkym3 and Dan Rosenburg for exploit.
---------------------------------------------------------------
[*] This script will:
(1) root your HTC One X on ICS
(2) install Busybox
(3) install SU files
[*] Before u begin:
(4) Make sure to read full instructions at OneXRoot.com!
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
Start Rooting...
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount succeeded
1251 KB/s (91980 bytes in 0.071s)
rm failed for /system/xbin/su, No such file or directory
1255 KB/s (568647 bytes in 0.442s)
1254 KB/s (1075144 bytes in 0.836s)
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.340 secs (3162188 bytes/sec)
rebooting
All Done rooting HTC One X, check out OneXRoot.com for more cool stuff like ROMs, hacks, tips, and more!
runmelinux.sh: 49: runmelinux.sh: @pause: not found
It did not install superuser or busybox. I guess it all fails at creating/getting access to /system/xbin/su ?
I have read about some other methods to unlock the bootloader but as it states on the htcdev.com website if it will be executeted there is no way back to re-lock the bootloader. I guess there is no option to get the S-OFF without unlocking the bootloader at the moment for 1.29.401.11 software version? Seems like it worked for the previous version of the software, I wished I have ordered my phone few months ealier
Click to expand...
Click to collapse
the only way you can root it, is by unlocking it from htcdev
just follow simple steps mentioned there...
then flash clockworkmod through fastboot
boot into recovry flash super su
Enjoy
Too bad you can't re-lock it after you do it (htcdev.com method).
Is there any chance it will be possible though, to root the 1.29.401.11 version in a way that you can get back to the stock whenever you want so it would be in the same state as you bought it?
There isn't anyway at the moment. Devs are working on s-off.
Sent from my GT-I9300 using xda app-developers app
Hey guys,
Just get the phone, so nothing is changed except turning on "debugging mode"
It's a HUAWEI Y201 PRO running Android 4.0.3
I like to use some apps as root and therefore I tried Root_with_Restore_by_Bin4ry_v18
Cause I'm running Ubuntu I configured /etc/udev/rules.d/99-android.rules and added the phone there.
adb is installed and seems to work well
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
78F5FD159EAB device
and running the script:
Code:
[email protected]:~/Downloads/Root_with_Restore_by_Bin4ry_v18$ sudo ./RunMe.sh
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
= ported to Linux by Kamistral (15.09.2012), =
= updated by codeworkx (01.10.2012) =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice:
1
Normal mode enabled!
Checking if i should run in Normal Mode or special Sony Mode
Please connect device with ADB-Debugging enabled now ...
remote object '/system/bin/ric' does not exist
remote object '/system/app/Backup-Restore.apk' does not exist
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now ...
Pushing busybox ...
4697 KB/s (1085140 bytes in 0.225s)
Pushing su binary ...
3789 KB/s (91980 bytes in 0.023s)
Pushing Superuser app
4021 KB/s (996704 bytes in 0.242s)
Pushing ric
1 KB/s (57 bytes in 0.040s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again ...
Copying files to it's place ...
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press key to exit ...
So there is trouble with mounting it. If I did everything in the right way the script seems not working for HUAWEI Y201 PRO
Maybe someone of you could add the phone.
BTW in the head is still v17 instead of v18
Have fun
Hi evreyone !
I spent hours trying and reading posts everywhere I could without any success.
I'm trying to follow this rooting guide: http://forum.xda-developers.com/showthread.php?t=2634196 (Root and Dual Recovery for Locked Bootloader) and I'm stuck in a bootloop at step 10.
I'm using the last Z1C-lockeddualrecovery2.7.117-BETA.installer.zip and I noticed an error during recovery installation (after DEVICE WILL NOW REBOOT!):
Code:
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
(Note that I'm using Linux... I tried to run the bash script both as a user or as root)
If I continue the rooting process by flashing D5503_14.2.A.1.114_Generic UK.ftf (step 9), I'm stuck at step 10 as I can't boot any recovery. The phone is stuck in a bootloop, and after the green light pressing vol up (ou down) won't do anything...
I tried the whole process (from the begining: docomo) several time and end up everytime with the same result: an error at the end of the recovery installation and a bootloop at step 10 that prevent me from entering any recovery...
I'm out of ideas ! What can I do to manage the installation of the recovery ?
OldBeurt said:
What can I do to manage the installation of the recovery ?
Click to expand...
Click to collapse
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Thanks for your answer !
XperienceD said:
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Click to expand...
Click to collapse
Since I don't have access to any recovery, I don't understand how I can follow this guide (step 5: Go to recovery menu[...]).
What did you meant ?
OldBeurt said:
I don't understand how I can follow this guide (step 5: Go to recovery menu[...])
Click to expand...
Click to collapse
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
XperienceD said:
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
Click to expand...
Click to collapse
Of course I red the requirements. The root method described is the same (http://forum.xda-developers.com/showthread.php?t=2642081) than the one I followed (http://forum.xda-developers.com/showthread.php?t=2634196). And so the result is going to be the same: being stuck in a bootloop after flashing the recovery form the computer (flashing witch returns an error that I quoted above).
I need help to "recover" the recovery, I mean to be able to properly flash the dual recovery on my phone (whether I wish to unlock the bootloader or not is not the point for now, since I need to root with the locked bootloader in the first place).
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Thanks for your input !
zxz0O0 said:
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Click to expand...
Click to collapse
I don't know where the error came from, but I tried several times (about 10) and it end up the same way ! I will try on another machine (Linux too).
zxz0O0 said:
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Click to expand...
Click to collapse
Yes I'm using install.sh, I just pasted the relevat part of the output, but here I paste all of it:
Code:
Will attempt to get root to install!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
Succes
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
0 KB/s (29 bytes in 0.056s)
362 KB/s (17768 bytes in 0.047s)
325 KB/s (15578 bytes in 0.046s)
11 KB/s (501 bytes in 0.043s)
272 KB/s (11791 bytes in 0.042s)
3186 KB/s (44383 bytes in 0.013s)
70 KB/s (3082 bytes in 0.042s)
9 KB/s (385 bytes in 0.041s)
3645 KB/s (657704 bytes in 0.176s)
3521 KB/s (2597754 bytes in 0.720s)
3936 KB/s (1842873 bytes in 0.457s)
5217 KB/s (2447499 bytes in 0.458s)
193 KB/s (8124 bytes in 0.041s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread on XDA for more details.
=============================================
ro.build.product=C6903
ro.build.id=14.1.G.1.534
search kallsyms...
1 2 3 4
(kallsyms_addresses=c0899410)
(kallsyms_num_syms=00014df1)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00b89f4
commit_creds=c00b8518
ptmx_fops=c0ea365c
Succeeded in getroot!
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================