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
Related
Well i used the OTA Simple Root and it worked, but now everytime i try to go into recovery (power plus volume down) it searches the files again and tries to run all the updates and reboot the system. Then when i skip that and try to go to recovery to update a rom i get a black screen with a red triangle and cant get to the recovery menu even. I did one time and i was in boot loop.
My questions are these, how can i set my phone back to completely stock with nothing on the sd card but what i need.
Is there anyway to fix this with out having to start all over again?
Easier fix is to install Rom manager. Once inside tell it to flash clockwork recovery. Boom. Have recovery again.
Sent from my EVO
Delete any files named PC36IMG.zip from the root of your SD card. Then either flash Amon_RA's or Koush's Clockwork recovery.
===============================================================
===============================================================
Simple Root 1.47.651.1 OTA Edition
===============================================================
===============================================================
* server not running *
===============================================================
Pushing files, PLEASE WAIT!.....
===============================================================
* daemon not running. starting it now *
* daemon started successfully *
912 KB/s (26172 bytes in 0.028s)
1209 KB/s (655360 bytes in 0.529s)
160 KB/s (1813 bytes in 0.011s)
17 KB/s (424 bytes in 0.024s)
107 KB/s (1754 bytes in 0.016s)
cannot stat 'PC36IMG.zip': No such file or directory
Pushing complete!
Press any key to continue . . .
I formated my sd card and tried to start simple root over again and after step one i get this message, what does it mean and how can i fix it? thanks for the fast replies.
twigums said:
===============================================================
===============================================================
Simple Root 1.47.651.1 OTA Edition
===============================================================
===============================================================
* server not running *
===============================================================
Pushing files, PLEASE WAIT!.....
===============================================================
* daemon not running. starting it now *
* daemon started successfully *
912 KB/s (26172 bytes in 0.028s)
1209 KB/s (655360 bytes in 0.529s)
160 KB/s (1813 bytes in 0.011s)
17 KB/s (424 bytes in 0.024s)
107 KB/s (1754 bytes in 0.016s)
cannot stat 'PC36IMG.zip': No such file or directory
Pushing complete!
Press any key to continue . . .
I formated my sd card and tried to start simple root over again and after step one i get this message, what does it mean and how can i fix it? thanks for the fast replies.
Click to expand...
Click to collapse
Download whichever PC36IMG.zip file is relevant to that method and place it on the root of your SD card.
me thinks the PC36IMG.zip is in included in the OTA simple root zip file, just copy it to the root of your SDCARD using the phone as a USB drive
whit's "Start over" method will work since he has partial root. and it'll update radios appropriately.
Try use toast method 2 nand unlocking and flash the recovery image. Should work just fine.
Sent from my PC36100 using XDA App
i think i found the problem, down load was messed up for simple root, redld it and having no problems so far (crosses fingers)
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
hello
im trying to unlock a x10mini. almost all tools are windows tools. everything ok, except that im running osx86. so i have to investigate with linux unlocking methods.
thanks to this thread http://forum.xda-developers.com/showthread.php?t=1261898 (credits to the_laser and ff0000) i managed to run msm7227 script, this is the output:
Code:
sh-3.2# sh msm7227_semc.sh
******************************************************
*** Process requires standard Android 2.x firmware ***
*** -= now it's up to you! ;) =- ***
******************************************************
1. searching for 'adb' executable
2. getting root priviledges
waiting for device...
pushing exploit...
1255 KB/s (585731 bytes in 0.455s)
executing exploit...
mmap() failed. Operation not permitted
waiting for device...
3. removing NAND MPU restrictions via SEMC backdoor (this is permanent)
165 KB/s (3087 bytes in 0.018s)
success
Rebooting...
Waiting for device...
4. re-getting root priviledges (wait for complete boot process)
property service neutered.
killing adbd. (should restart in a second or two)
Waiting...
5. getting access to semcboot area
180 KB/s (8064 bytes in 0.043s)
6. writing semcboot
694 KB/s (596916 bytes in 0.838s)
successfully wrote 0003ff00
7. All done.
but there is one suspicious line (the one with the mmap error)
i dont want to continue installing a custom kerner until im sure that bootloader is unlocked, but s1tool is not avaliable for nonwindows platforms.,,, i just want to check ib bootloader is unlocked now.
i have read in other threads about power on with the volume button pressed, but nothings happens.
ps: this thread maybe should go in the one i told but i cannot post on it.
peace
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!
=============================================
alohaa guys,first post and thread
sinds i cant post in the developers thread
ill post here
as the title says im stuck on the sony logo,after trying to root my z1c
flashtool still see my phone,but it says :device connected with USB debugging off
i tried a couple of times to get in the recovery menu,boot phone,and press either volume up or down S:
nothing ever happens it just shows the sony logo and dissapears,then it comes back again :S
i got the proper files on the mirco sd card,as written in the tutorial
http://forum.xda-developers.com/showthread.php?t=2642081
any help is appriciated,and i will look further also in the trheads if i can find a solution for this,but havent found anything yet,if there is any
I made the mistake to first connect the phone to the PC and then running flash tool. Try to start the flashtool first. When it asks You to connect the phone do so ( I think in fastboot mode).
Then the ftf files should be flashed properly and the phone boot up normally
Gesendet von meinem D5503 mit Tapatalk
konsi said:
I made the mistake to first connect the phone to the PC and then running flash tool. Try to start the flashtool first. When it asks You to connect the phone do so ( I think in fastboot mode).
Then the ftf files should be flashed properly and the phone boot up normally
Gesendet von meinem D5503 mit Tapatalk
Click to expand...
Click to collapse
yes flash tool was already running before,so it detects the phone,i tried flashing again and this time it worked,eg just the flashing
at .16 of the tutorial i posted a link of i flashed D5503_14.3.A.0.681_Generic_UK-nosystem.ftf ,but then afterward,still same logo from sony comes and goes,but it doesnt get in recovery mode S:
before i flash anything more,ill wait for anwers,i geuss overflashing doesnt exist but i very uncertian of what im doing now
btw thanks for the quick reply
edit this is what unroot gave me http ://i61.tinypic.com/jhufyg.png
Well, I'm a noob as well
I did the root process with instructions from another thread which was called noob proof it doesn't unlock the bootloader though. I don't have the link right now. But it is one on the top of the forum.
Btw the rooting process of this phone is IMHO very complicated.
Edit: sorry, I didn't see it was this thread you are talking about. I used the same ?
Gesendet von meinem D5503 mit Tapatalk
Please start again from step 1 of the guide. Post the output of dualrecovery installer once you run it.
Bootloop can be caused by multiple mistakes the user did.
konsi said:
Well, I'm a noob as well
I did the root process with instructions from another thread which was called noob proof it doesn't unlock the bootloader though. I don't have the link right now. But it is one on the top of the forum.
Btw the rooting process of this phone is IMHO very complicated.
Edit: sorry, I didn't see it was this thread you are talking about. I used the same ?
Gesendet von meinem D5503 mit Tapatalk
Click to expand...
Click to collapse
lol,i read a few pages further, this post it says start over again from step 1,if sony logo keeps coming up,and no green light flashes
http://forum.xda-developers.com/showpost.php?p=50227041&postcount=19
i will try again S:
edit: thanks @ zxz0O0 ill try D:
I would've done the same. Report if you succeed
Gesendet von meinem D5503 mit Tapatalk
guys thanks for the help,i managed to root my xperia z1c
and i think i know what went wrong,the first time i used Z1C-lockeddualrecovery2.7.123-BETA.installer
with option 3 [Installation on unrooted ROM]
at exact same time windows explorer crashed dont know why,but that resulted in a protocol failure??,and afterwards could not connect to device
error :device not found , it said a few times
this is why i could not get in the recoverymode
after starting at step 1 again
and i could start/boot with the flashed docomo firmware,i was very reliefed (btw whats up with that docomo sheep walking on the screen lol)
and useing Z1C-lockeddualrecovery2.7.123-BETA.installer, install.bat for the 2nd time i saw the difference
this time it gave me this
Code:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices =
= =
==============================================
[ 1. Installation on ROM rooted with SuperSU ]
[ 2. Installation on ROM rooted with SuperUser ]
[ 3. Installation on unrooted ROM ]
[ 4. Exit ]
Please choose install action. [1,2,3,4]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found
=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (29 bytes in 0.457s)
19 KB/s (17768 bytes in 0.907s)
415 KB/s (15759 bytes in 0.037s)
163 KB/s (501 bytes in 0.003s)
720 KB/s (11798 bytes in 0.016s)
2405 KB/s (56662 bytes in 0.023s)
1003 KB/s (3082 bytes in 0.003s)
6 KB/s (385 bytes in 0.056s)
1316 KB/s (657704 bytes in 0.488s)
3564 KB/s (2602457 bytes in 0.713s)
3150 KB/s (2464762 bytes in 0.764s)
2776 KB/s (1845018 bytes in 0.649s)
234 KB/s (8658 bytes in 0.036s)
=============================================
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 (Post #2) on XDA for more deta
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app
You can use one of the recoveries to root your device.
=============================================
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!
/data/local/tmp/recovery/install.sh: line 23: /system/xbin/busybox: not found
/data/local/tmp/recovery/install.sh: line 23: /system/bin/busybox: not found
##########################################################
#
# Installing XZDR version 2.7.123 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to a
low installation.
Copy recovery files to system.
Rename stock mr
Copy mr wrapper script to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
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 TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after itself if you see the install.ba
/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries
=============================================
the rest was a piece of cake
thanks for all the very quick responses
this thread can be deleted by the mods if they wish to
or leave it for people with the same bad luck as me