Guest inday Posted August 21, 2010 Report Share Posted August 21, 2010 (edited) Thanks for the quick response, i'll try CyanogenMod 6 then. Rodriguezstyle isn't too good for me. The link you gave is the latest CyanogenMod 6? Yes, here is the link, http://forum.xda-developers.com/showthread.php?t=749919 Setup: The recommended (easiest) method to download and install Azure is via ROM-Manager (which can be found in the Market). So please install via the rom manager, in the rom manager goto download rom and choose CyanogenMod 6 (azure-0.5.zip) and don't forget to check the options Google apps (gapps-az-20100816-0.5.zip) in the check-box. Also let the rom manager wipe you telephone and let it make a backup. For other people, only when you Legend is already rooted!!! Edited August 21, 2010 by inday Link to comment Share on other sites More sharing options...
Guest Stonejag Posted August 23, 2010 Report Share Posted August 23, 2010 (edited) Hello all - first post so be gentle! I have successfully rooted my Legend, thanks to Paul's guide/tools. I used OSX (probably worth pointing out in the first post that the tools only work on Intel Macs! Some of us are still on PPC) and turned a 64MB mini-SD that came with a Nokia many years ago into my gold card. This method was the only one that worked - for some reason when trying to use RUU to do an unrooted debrand, my (XP) PC wouldn't pick up the USB connection when the phone was in bootloader mode. All I could do was let the RUU reboot into the bootloader, then it got stuck :huh: I think it was a driver issue but not sure... My Legend came with Vodafone branding - I'd mistakenly applied the faulty OTA update (think it brings you up to 2.05.405.2?) so I had to do the hack-legend downgrading bit first. Vodafone as per usual were totally useless - when I complained their update had messed things around (Wifi went a bit picky, and the SMS thing) they suggested I do a factory reset, then call HTC! Thanks, guys *facepalm* Interestingly the man from HTC said they did have an internal 2.2 release for Legend so hopefully it won't be long now... Once I decided to use the Mac, everything went swimmingly - now I just need to put everything back as it was. Shame on Vodafone for forcing me to root it, I was quite happy with stock until they fiddled with it >_< One question: when I searched for OTA updates from the phone it said there was one available, then crashed and rebooted midway through the update. Are all the OTA updates going to be unavailable now I'm rooted? I'd like to get it back to the stock equivalent of the 2.1 ROM I was running before, if that's possible - I quite like Sense and Cyanogen doesn't really interest me. Is ROM Manager able to install stock updates? Any ideas? Cheers Stone Edited August 23, 2010 by Stonejag Link to comment Share on other sites More sharing options...
Guest gpompeus Posted August 23, 2010 Report Share Posted August 23, 2010 Thank you Paul, everything went just the way its mentioned on post# 1.... Paul, now that I have your ROM installed (1.31.405.4) am getting an OTA update that says 1.31.405.5............. Should I upgrade or not????? Link to comment Share on other sites More sharing options...
Guest borgfather Posted August 23, 2010 Report Share Posted August 23, 2010 Thank you Paul, everything went just the way its mentioned on post# 1.... Paul, now that I have your ROM installed (1.31.405.4) am getting an OTA update that says 1.31.405.5............. Should I upgrade or not????? You can but you will probably lose root and if you would like to have a more recent build you can have a look at other roms like http://forum.xda-developers.com/showthread.php?t=735299 good luck !! Link to comment Share on other sites More sharing options...
Guest vanider Posted August 26, 2010 Report Share Posted August 26, 2010 Hi everyone!! I just bought a Legend (Bell 2.02.xxxx) and downgraded to 1.31 with the help of wag3slav3 on xda-developers, as well as created my gold card, and got through step 1 with no issues.... the problem is i cannot get step2-windows.bat to work for me with varying issues, i get into recovery mode, and it seems to go downhill from there... 1. error:device offline 2. error:protocol fault and a bunch of other things... if anyone has had the same issues and has any luck with fixig anything on step 2, if you could please post or pm me, it would be great :huh: thanks in advance Link to comment Share on other sites More sharing options...
Guest autodynamix Posted August 26, 2010 Report Share Posted August 26, 2010 Does ROM version mean firmware version? My HTC Legend's firmware version is 2.1 Link to comment Share on other sites More sharing options...
Guest wyx2010 Posted August 29, 2010 Report Share Posted August 29, 2010 (edited) I've been following the instructions on the first page and on Step to i got this error. So it's not displaying me the recovery menu. Any suggestions?. Meanwhile i'm trying it again. Thanks in Advance Second Edit: I've tried to root the phone from my laptop where a 32bit version of windows 7 is running instead of the 64 on on my desktop. during this i got another error. quite the same but little different. Legend Root Step 2 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * push: files/etc/mtab -> /etc/mtab push: files/etc/fstab -> /etc/fstab push: files/sbin/wipe -> /sbin/wipe push: files/sbin/unyaffs -> /sbin/unyaffs push: files/sbin/ums_toggle -> /sbin/ums_toggle push: files/sbin/um -> /sbin/um push: files/sbin/tune2fs -> /sbin/tune2fs push: files/sbin/toolbox -> /sbin/toolbox push: files/sbin/sdparted -> /sbin/sdparted push: files/sbin/recovery -> /sbin/recovery push: files/sbin/reboot -> /sbin/reboot push: files/sbin/parted -> /sbin/parted push: files/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh push: files/sbin/mkyaffs2image -> /sbin/mkyaffs2image push: files/sbin/mke2fs -> /sbin/mke2fs push: files/sbin/log2sd -> /sbin/log2sd push: files/sbin/fs -> /sbin/fs push: files/sbin/flash_image -> /sbin/flash_image push: files/sbin/fix_permissions -> /sbin/fix_permissions push: files/sbin/e2fsck -> /sbin/e2fsck push: files/sbin/dump_image -> /sbin/dump_image push: files/sbin/busybox -> /sbin/busybox push: files/sbin/backuptool.sh -> /sbin/backuptool.sh push: files/sbin/adbd -> /sbin/adbd push: files/system/bin/sh -> /system/bin/sh push: files/system/bin/linker -> /system/bin/linker push: files/system/lib/libstdc++.so -> /system/lib/libstdc++.so push: files/system/lib/libm.so -> /system/lib/libm.so push: files/system/lib/liblog.so -> /system/lib/liblog.so push: files/system/lib/libcutils.so -> /system/lib/libcutils.so push: files/system/lib/libc.so -> /system/lib/libc.so protocol failure * daemon not running. starting it now on port 5037 * * daemon started successfully * error: device offline And thats the old log from my desktop. windows7 64 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * push: files/etc/mtab -> /etc/mtab push: files/etc/fstab -> /etc/fstab push: files/sbin/wipe -> /sbin/wipe push: files/sbin/unyaffs -> /sbin/unyaffs push: files/sbin/ums_toggle -> /sbin/ums_toggle push: files/sbin/um -> /sbin/um push: files/sbin/tune2fs -> /sbin/tune2fs push: files/sbin/toolbox -> /sbin/toolbox push: files/sbin/sdparted -> /sbin/sdparted push: files/sbin/recovery -> /sbin/recovery push: files/sbin/reboot -> /sbin/reboot push: files/sbin/parted -> /sbin/parted push: files/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh push: files/sbin/mkyaffs2image -> /sbin/mkyaffs2image push: files/sbin/mke2fs -> /sbin/mke2fs push: files/sbin/log2sd -> /sbin/log2sd push: files/sbin/fs -> /sbin/fs push: files/sbin/flash_image -> /sbin/flash_image push: files/sbin/fix_permissions -> /sbin/fix_permissions push: files/sbin/e2fsck -> /sbin/e2fsck push: files/sbin/dump_image -> /sbin/dump_image push: files/sbin/busybox -> /sbin/busybox push: files/sbin/backuptool.sh -> /sbin/backuptool.sh push: files/sbin/adbd -> /sbin/adbd push: files/system/bin/sh -> /system/bin/sh push: files/system/bin/linker -> /system/bin/linker push: files/system/lib/libstdc++.so -> /system/lib/libstdc++.so push: files/system/lib/libm.so -> /system/lib/libm.so * daemon not running. starting it now on port 5037 * * daemon started successfully * link_image[1721]: 69 could not load needed library 'libc.so' for '/system/bin /sh' (load_library[1051]: Library 'libc.so' not found)CANNOT LINK EXECUTABLE Pushing update file to device sdcard - this may take a few minutes... adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Now wipe and apply rootedupdate.zip from the recovery image menu. adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Edited August 29, 2010 by wyx2010 Link to comment Share on other sites More sharing options...
Guest weaselmode Posted August 29, 2010 Report Share Posted August 29, 2010 Hi there, I finish step1, without errors. I reboot the phone so that I can access the goldcard and wipe it. I reboot my phone and put it into recovery mode and I run step 2. This is the error I receive C:\Documents and Settings\Stephen\My Documents\r4-legend-root>adb.exe push files / push: files/etc/mtab -> /etc/mtab push: files/etc/fstab -> /etc/fstab push: files/sbin/wipe -> /sbin/wipe push: files/sbin/unyaffs -> /sbin/unyaffs push: files/sbin/ums_toggle -> /sbin/ums_toggle push: files/sbin/um -> /sbin/um push: files/sbin/tune2fs -> /sbin/tune2fs push: files/sbin/toolbox -> /sbin/toolbox push: files/sbin/sdparted -> /sbin/sdparted push: files/sbin/recovery -> /sbin/recovery push: files/sbin/reboot -> /sbin/reboot push: files/sbin/parted -> /sbin/parted push: files/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh push: files/sbin/mkyaffs2image -> /sbin/mkyaffs2image push: files/sbin/mke2fs -> /sbin/mke2fs push: files/sbin/log2sd -> /sbin/log2sd push: files/sbin/fs -> /sbin/fs push: files/sbin/flash_image -> /sbin/flash_image push: files/sbin/fix_permissions -> /sbin/fix_permissions push: files/sbin/e2fsck -> /sbin/e2fsck push: files/sbin/dump_image -> /sbin/dump_image push: files/sbin/busybox -> /sbin/busybox push: files/sbin/backuptool.sh -> /sbin/backuptool.sh push: files/sbin/adbd -> /sbin/adbd push: files/system/bin/sh -> /system/bin/sh push: files/system/bin/linker -> /system/bin/linker push: files/system/lib/libstdc++.so -> /system/lib/libstdc++.so push: files/system/lib/libm.so -> /system/lib/libm.so push: files/system/lib/liblog.so -> /system/lib/liblog.so push: files/system/lib/libcutils.so -> /system/lib/libcutils.so push: files/system/lib/libc.so -> /system/lib/libc.so 31 files pushed. 0 files skipped. 952 KB/s (0 bytes in 3734509.003s) C:\Documents and Settings\Stephen\My Documents\r4-legend-root>adb.exe shell busy box --install /sbin - exec '/system/bin/sh' failed: Permission denied (13) - C:\Documents and Settings\Stephen\My Documents\r4-legend-root>echo. C:\Documents and Settings\Stephen\My Documents\r4-legend-root>adb.exe shell nohu p /sbin/recovery - exec '/system/bin/sh' failed: Permission denied (13) - C:\Documents and Settings\Stephen\My Documents\r4-legend-root>step1-windows Legend Root Step 1 Erasing cache and rebooting in RUU mode... erasing 'cache'... OKAY ... OKAY About to start flash... sending 'zip' (121756 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] unzipping & flushing... INFO[RUU]UZ,hboot,0 INFO[RUU]UZ,hboot,100 INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping & flushing... INFO[RUU]UZ,radio,0 INFO[RUU]UZ,radio,5 INFO[RUU]UZ,radio,12 INFO[RUU]UZ,radio,17 INFO[RUU]UZ,radio,26 INFO[RUU]UZ,radio,34 INFO[RUU]UZ,radio,43 INFO[RUU]UZ,radio,51 INFO[RUU]UZ,radio,60 INFO[RUU]UZ,radio,68 INFO[RUU]UZ,radio,73 INFO[RUU]UZ,radio,81 INFO[RUU]UZ,radio,86 INFO[RUU]UZ,radio,94 INFO[RUU]UZ,radio,99 INFO[RUU]UZ,radio,100 INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,11 INFO[RUU]WP,radio,20 INFO[RUU]WP,radio,28 INFO[RUU]WP,radio,33 INFO[RUU]WP,radio,42 INFO[RUU]WP,radio,53 INFO[RUU]WP,radio,100 INFOstart image[rcdata] unzipping & flushing... INFO[RUU]UZ,rcdata,0 INFO[RUU]WP,rcdata,0 INFO[RUU]WP,rcdata,100 INFOstart image[boot] unzipping & flushing... INFO[RUU]UZ,boot,0 INFO[RUU]UZ,boot,43 INFO[RUU]UZ,boot,84 INFO[RUU]UZ,boot,100 INFO[RUU]WP,boot,0 INFO[RUU]WP,boot,44 INFO[RUU]WP,boot,89 INFO[RUU]WP,boot,100 INFOstart image[recovery] unzipping & flushing... INFO[RUU]UZ,recovery,0 INFO[RUU]UZ,recovery,20 INFO[RUU]UZ,recovery,47 INFO[RUU]UZ,recovery,99 INFO[RUU]UZ,recovery,100 INFO[RUU]WP,recovery,0 INFO[RUU]WP,recovery,22 INFO[RUU]WP,recovery,44 INFO[RUU]WP,recovery,66 INFO[RUU]WP,recovery,89 INFO[RUU]WP,recovery,100 INFOstart image[system] unzipping & flushing... INFO[RUU]UZ,system,0 INFO[RUU]UZ,system,9 INFO[RUU]UZ,system,14 INFO[RUU]UZ,system,23 INFO[RUU]UZ,system,28 INFO[RUU]UZ,system,37 INFO[RUU]UZ,system,46 INFO[RUU]UZ,system,51 INFO[RUU]UZ,system,60 INFO[RUU]UZ,system,65 INFO[RUU]UZ,system,70 INFO[RUU]UZ,system,79 INFO[RUU]UZ,system,84 INFO[RUU]UZ,system,93 INFO[RUU]UZ,system,100 INFO[RUU]WP,system,0 INFO[RUU]WP,system,100 INFOstart image[userdata] unzipping & flushing... INFO[RUU]UZ,userdata,0 INFO[RUU]UZ,userdata,100 INFO[RUU]WP,userdata,0 INFO[RUU]WP,userdata,100 INFOstart image[sp1] unzipping & flushing... INFO[RUU]UZ,sp1,0 INFO[RUU]UZ,sp1,100 INFO[RUU]WP,sp1,0 INFO[RUU]WP,sp1,100 OKAY sending 'zip' (121756 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] unzipping & flushing... INFO[RUU]UZ,hboot,0 INFO[RUU]UZ,hboot,100 INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping & flushing... INFO[RUU]UZ,radio,0 INFO[RUU]UZ,radio,5 INFO[RUU]UZ,radio,12 INFO[RUU]UZ,radio,17 INFO[RUU]UZ,radio,26 INFO[RUU]UZ,radio,34 INFO[RUU]UZ,radio,43 INFO[RUU]UZ,radio,51 INFO[RUU]UZ,radio,60 INFO[RUU]UZ,radio,68 INFO[RUU]UZ,radio,73 INFO[RUU]UZ,radio,81 INFO[RUU]UZ,radio,86 INFO[RUU]UZ,radio,94 INFO[RUU]UZ,radio,99 INFO[RUU]UZ,radio,100 INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,11 INFO[RUU]WP,radio,20 INFO[RUU]WP,radio,28 INFO[RUU]WP,radio,33 INFO[RUU]WP,radio,42 INFO[RUU]WP,radio,53 INFO[RUU]WP,radio,100 INFOstart image[rcdata] unzipping & flushing... INFO[RUU]UZ,rcdata,0 INFO[RUU]WP,rcdata,0 INFO[RUU]WP,rcdata,100 INFOstart image[boot] unzipping & flushing... INFO[RUU]UZ,boot,0 INFO[RUU]UZ,boot,43 INFO[RUU]UZ,boot,84 INFO[RUU]UZ,boot,100 INFO[RUU]WP,boot,0 INFO[RUU]WP,boot,44 INFO[RUU]WP,boot,89 INFO[RUU]WP,boot,100 INFOstart image[recovery] unzipping & flushing... INFO[RUU]UZ,recovery,0 INFO[RUU]UZ,recovery,20 INFO[RUU]UZ,recovery,47 INFO[RUU]UZ,recovery,99 INFO[RUU]UZ,recovery,100 INFO[RUU]WP,recovery,0 INFO[RUU]WP,recovery,22 INFO[RUU]WP,recovery,44 INFO[RUU]WP,recovery,66 INFO[RUU]WP,recovery,89 INFO[RUU]WP,recovery,100 INFOstart image[system] unzipping & flushing... INFO[RUU]UZ,system,0 INFO[RUU]UZ,system,9 INFO[RUU]UZ,system,14 INFO[RUU]UZ,system,23 INFO[RUU]UZ,system,28 INFO[RUU]UZ,system,37 INFO[RUU]UZ,system,46 INFO[RUU]UZ,system,51 INFO[RUU]UZ,system,60 INFO[RUU]UZ,system,65 INFO[RUU]UZ,system,70 INFO[RUU]UZ,system,79 INFO[RUU]UZ,system,84 INFO[RUU]UZ,system,93 INFO[RUU]UZ,system,100 INFO[RUU]WP,system,0 INFO[RUU]WP,system,100 INFOstart image[userdata] unzipping & flushing... INFO[RUU]UZ,userdata,0 INFO[RUU]UZ,userdata,100 INFO[RUU]WP,userdata,0 INFO[RUU]WP,userdata,100 INFOstart image[sp1] unzipping & flushing... INFO[RUU]UZ,sp1,0 INFO[RUU]UZ,sp1,100 INFO[RUU]WP,sp1,0 INFO[RUU]WP,sp1,100 OKAY Rebooting to bootloader... rebooting into bootloader... OKAY Step 1 complete - now use the bootloader menu to enter recovery mode. To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option. C:\Documents and Settings\Stephen\My Documents\r4-legend-root>step2-windows.bat Legend Root Step 2 Pushing required files to device... * daemon not running. starting it now * * daemon started successfully * push: files/etc/mtab -> /etc/mtab push: files/etc/fstab -> /etc/fstab push: files/sbin/wipe -> /sbin/wipe push: files/sbin/unyaffs -> /sbin/unyaffs push: files/sbin/ums_toggle -> /sbin/ums_toggle push: files/sbin/um -> /sbin/um push: files/sbin/tune2fs -> /sbin/tune2fs push: files/sbin/toolbox -> /sbin/toolbox push: files/sbin/sdparted -> /sbin/sdparted push: files/sbin/recovery -> /sbin/recovery push: files/sbin/reboot -> /sbin/reboot push: files/sbin/parted -> /sbin/parted push: files/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh push: files/sbin/mkyaffs2image -> /sbin/mkyaffs2image push: files/sbin/mke2fs -> /sbin/mke2fs push: files/sbin/log2sd -> /sbin/log2sd push: files/sbin/fs -> /sbin/fs push: files/sbin/flash_image -> /sbin/flash_image push: files/sbin/fix_permissions -> /sbin/fix_permissions push: files/sbin/e2fsck -> /sbin/e2fsck push: files/sbin/dump_image -> /sbin/dump_image push: files/sbin/busybox -> /sbin/busybox push: files/sbin/backuptool.sh -> /sbin/backuptool.sh push: files/sbin/adbd -> /sbin/adbd push: files/system/bin/sh -> /system/bin/sh push: files/system/bin/linker -> /system/bin/linker push: files/system/lib/libstdc++.so -> /system/lib/libstdc++.so push: files/system/lib/libm.so -> /system/lib/libm.so push: files/system/lib/liblog.so -> /system/lib/liblog.so push: files/system/lib/libcutils.so -> /system/lib/libcutils.so push: files/system/lib/libc.so -> /system/lib/libc.so 31 files pushed. 0 files skipped. 796 KB/s (0 bytes in 3734509.004s) - exec '/system/bin/sh' failed: Permission denied (13) - Pushing update file to device sdcard - this may take a few minutes... - exec '/system/bin/sh' failed: Permission denied (13) - Any ideas? My phone is now unlocked but NOT rooted! Link to comment Share on other sites More sharing options...
Guest weaselmode Posted August 29, 2010 Report Share Posted August 29, 2010 I should also mention that I don't have the custom recovery screen with options... Just the phone with red triangle and exclamation mark Link to comment Share on other sites More sharing options...
Guest Posted August 30, 2010 Report Share Posted August 30, 2010 This is what I get when performing step 1. After this, CMD crashes. Please help me! Link to comment Share on other sites More sharing options...
Guest borgfather Posted August 31, 2010 Report Share Posted August 31, 2010 This is what I get when performing step 1. After this, CMD crashes. Please help me! to me this looks like a bad goldcard i would sugest to try the goldcard procedure again Link to comment Share on other sites More sharing options...
Guest tharonald Posted September 2, 2010 Report Share Posted September 2, 2010 I should also mention that I don't have the custom recovery screen with options... Just the phone with red triangle and exclamation mark For my legend, i had to push volume up and the power button once, then it came in normal recovery mode, then run step2 and all done!! :huh: Link to comment Share on other sites More sharing options...
Guest UEGHIO Posted September 2, 2010 Report Share Posted September 2, 2010 Hi my name is marco and I'm new in this forum. First of all thank you Paul for your how to! I've got an HTC Legend too,it was a Fastweb one and I've just debranded it,downgrading to this rom RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_sig ed.exe ,but I arrived at the step 2 and now I need your help! I'm on win XP SP3 ,when I start my phone and choose "recovery",I see obviously the red triangle,but when I do the comand "step2.." no progress bar appears.Those are some info SDK installed hboot 0.43.0001 usb debug on Firmware n. 2.1 Software n. 1.31.405.4 Moreover I received an Hardware driver error ( "Android 1.0" ) when I plug in the phone in recovery mode,so I tried to fix it using this guide http://forum.xda-developers.com/showthread.php?t=737728 but without success :huh: It's my prompt message: C:\r4-legend-root>step2-windows.bat Legend Root Step 2 Pushing required files to device... adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Pushing update file to device sdcard - this may take a few minutes... adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Now wipe and apply rootedupdate.zip from the recovery image menu. adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon C:\r4-legend-root>step2-windows.bat Legend Root Step 2 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Pushing update file to device sdcard - this may take a few minutes... adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Now wipe and apply rootedupdate.zip from the recovery image menu. adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon C:\r4-legend-root> Can someone help me please? Thank you in advance,regards. Marco Link to comment Share on other sites More sharing options...
Guest inday Posted September 3, 2010 Report Share Posted September 3, 2010 Install Droid Explorer, it will also install the drivers for Windows. A tool to manage your rooted android device with the simplicity of Windows Explorer. http://de.codeplex.com/ Link to comment Share on other sites More sharing options...
Guest flopyro Posted September 4, 2010 Report Share Posted September 4, 2010 (edited) Hi my name is marco and I'm new in this forum. First of all thank you Paul for your how to! I've got an HTC Legend too,it was a Fastweb one and I've just debranded it,downgrading to this rom RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_sig ed.exe ,but I arrived at the step 2 and now I need your help! I'm on win XP SP3 ,when I start my phone and choose "recovery",I see obviously the red triangle,but when I do the comand "step2.." no progress bar appears.Those are some info SDK installed hboot 0.43.0001 usb debug on Firmware n. 2.1 Software n. 1.31.405.4 Moreover I received an Hardware driver error ( "Android 1.0" ) when I plug in the phone in recovery mode,so I tried to fix it using this guide http://forum.xda-developers.com/showthread.php?t=737728 but without success :) It's my prompt message: C:\r4-legend-root>step2-windows.bat Legend Root Step 2 Pushing required files to device... adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Pushing update file to device sdcard - this may take a few minutes... adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Now wipe and apply rootedupdate.zip from the recovery image menu. adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon C:\r4-legend-root>step2-windows.bat Legend Root Step 2 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Pushing update file to device sdcard - this may take a few minutes... adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon Now wipe and apply rootedupdate.zip from the recovery image menu. adb server is out of date. killing... * daemon started successfully * ** daemon still not runningerror: cannot connect to daemon C:\r4-legend-root> Can someone help me please? Thank you in advance,regards. Marco i had exactly the same problem, step 1 went well , and 2 "server is out of date" and after that i tryed the same thing on a diferent laptop (my gf's) installed drivers, and tryed the step 2 again (and it worked) i mention that i did not turned off the phone between the 2 PC's (i donno if this is important or not) on second toughts i donno if i succesfuly rooted my phone ! how do i check if it's rooted ? :P also please look in Task Manager-> processes -> and if you see that adb.exe is randomly starting and stopping change the PC Edited September 4, 2010 by flopyro Link to comment Share on other sites More sharing options...
Guest mnabil Posted September 9, 2010 Report Share Posted September 9, 2010 (edited) please help it didnt work for me iam under windows 7 x64 my device info r: HTC LEGEND HBOOT-0.43.0003 my software version is:1.27 kernal 2.6.29 frimware 2.1 i think my problem is i cant get goldcard to work no matter what am doing its not working when i use HxD editor always end up with unreadable card and needed to be formated again . i tried diff sd cards, king stone 2GB and a 4GB chiness card and end up the same , is there is any other way to create the goldcard? i also tried to use GoldCardTool and it always says goldcard created successful but when i start using step 1 for windows i stuck at this Legend Root Step 1 Erasing cache and rebooting in RUU m erasing 'cache'... OKAY ... OKAY About to start flash... < waiting for device > sending 'zip' (121756 KB)... OKAY writing 'zip'... any help please? Edited September 9, 2010 by mnabil Link to comment Share on other sites More sharing options...
Guest Tim80 Posted September 11, 2010 Report Share Posted September 11, 2010 please help it didnt work for me iam under windows 7 x64 my device info r: HTC LEGEND HBOOT-0.43.0003 my software version is:1.27 kernal 2.6.29 frimware 2.1 i think my problem is i cant get goldcard to work no matter what am doing its not working when i use HxD editor always end up with unreadable card and needed to be formated again . i tried diff sd cards, king stone 2GB and a 4GB chiness card and end up the same , is there is any other way to create the goldcard? i also tried to use GoldCardTool and it always says goldcard created successful but when i start using step 1 for windows i stuck at this any help please? why not try this : Fake-flash by Koush, launching recovery on your device without a PC Link to comment Share on other sites More sharing options...
Guest borgfather Posted September 11, 2010 Report Share Posted September 11, 2010 please help it didnt work for me iam under windows 7 x64 my device info r: HTC LEGEND HBOOT-0.43.0003 my software version is:1.27 kernal 2.6.29 frimware 2.1 i think my problem is i cant get goldcard to work no matter what am doing its not working when i use HxD editor always end up with unreadable card and needed to be formated again . i tried diff sd cards, king stone 2GB and a 4GB chiness card and end up the same , is there is any other way to create the goldcard? i also tried to use GoldCardTool and it always says goldcard created successful but when i start using step 1 for windows i stuck at this any help please? do you have access to a linux system ? there is a way to make a goldcard within linux by simply copying the image to your sdcard http://android.modaco.com/content/htc-lege...nd-simpler-way/ also check again your goldcard image you might have an error in the image. just make a new image. hope you manage !! good luck Link to comment Share on other sites More sharing options...
Guest mnabil Posted September 13, 2010 Report Share Posted September 13, 2010 do you have access to a linux system ? there is a way to make a goldcard within linux by simply copying the image to your sdcard http://android.modaco.com/content/htc-lege...nd-simpler-way/ also check again your goldcard image you might have an error in the image. just make a new image. hope you manage !! good luck thanks a lot that helps me i used ubuntu and now every thing works perfect :P i think the problem was windows 7 x64 Link to comment Share on other sites More sharing options...
Guest Goetzmen Posted September 23, 2010 Report Share Posted September 23, 2010 Hey guys! Actually, i'm stuck at the step when i have to remove the coldcard, format it and then replace it because i used my HTC Legend to format my sd card at the beginning. I don't get it, how can I format the goldcard now? I don't have an card reader :lol: Thanks for your help :) Link to comment Share on other sites More sharing options...
Guest Holmes108 Posted September 28, 2010 Report Share Posted September 28, 2010 (edited) Hello all. I'm actually stuck at the downgrading step... I ran the crackin.bat from the Hack4legend.zip. and the guide I used said my phone would reboot 5 times. It only reboots twice, and the message in the terminal is stuck on "adb server is out of date. killing..." I created my goldcard while the SD card was in my phone (in "Disk Drive" mode), and have never taken the card out. I used the little application that creates and patches the image to the card. I don't know if this is the problem... if I have a bad card, or if the crackin.bat isn't working... Is there any reason I need to remove my SD card and create the gold card directly on my PC? Any advice would be appreciated. Edit: Nevermind. It seems I had 2 instances of ADB.EXE running... closing one of them solved the issue. Edited September 28, 2010 by Holmes108 Link to comment Share on other sites More sharing options...
Guest randy_khoo Posted October 1, 2010 Report Share Posted October 1, 2010 Hi there, My name is Randy Khoo. I'm from the South East Asia region. Just wanna say thanks to all of you guys for your help, namely Paul and wag3slav3. Just to put down this for the other SEA boys. 1) I started off with my goldcard creation (no problems) and followed Paul's advice at unlockr.com 2) I encountered problems with step 1 -> Remote 43 main check version fail 3) I bumped into "[HOWTO] DOWNGRADE to 1.31 which you can then root for Legend 2.1" at the XDA forums. 4) I ran crackin and reached crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0 However, i kept getting permission errors while attempting this. 5) Despite the error messages, I decided at this point to just give the downgrade a try anyway... RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe 6) I succeeded and I continued Paul's instruction for Step 1 and Step 2... 7) Sweet success! Thank you... Really appreciate this community of dedicated developers making rooting possible on the legend! However i had a few speed bumps i wanted to run through with anyone else of you here that are experts in this field. 1) I had problems accessing SuperUser after the Step 2 => solved by restarting my phone. 2) ROM Manager / ClockWorkMod -> i've installed this and backed up my ROM. I wish to install Azure 6.0.0, however i am not sure if this requires a goldcard? 3) After the downgrade, i noticed there's an upgrade to 1.31.405.5 (3.89MB) when i do a system update. What will happen when I download this? Will it close up all the root vulnerabilities, letting me start all over to where i began in the first place? Will my phone brick with this update? I've read that some people had issues with their phones after they downloaded this... Link to comment Share on other sites More sharing options...
Guest alexhtclegend Posted October 1, 2010 Report Share Posted October 1, 2010 After running "step2-windows.bat", I get stuck on the red exclamation mark screen, rather than the "recovery" screen. Does anyone have a solution for this? I haven't actually bricked my phone though, if I take out and re-insert the battery I get back to my normal (unrooted) ROM. Also, I have the correct software/bootloader versions; I downgraded to 1.31 using the method over on XDA. Thanks in advance! Link to comment Share on other sites More sharing options...
Guest alexhtclegend Posted October 1, 2010 Report Share Posted October 1, 2010 After running "step2-windows.bat", I get stuck on the red exclamation mark screen, rather than the "recovery" screen. Does anyone have a solution for this? I haven't actually bricked my phone though, if I take out and re-insert the battery I get back to my normal (unrooted) ROM. Also, I have the correct software/bootloader versions; I downgraded to 1.31 using the method over on XDA. Thanks in advance! Also, I have had no luck when I keep the gold card in either (the guide tells you to replace it with a non-goldcard after stage 1) Link to comment Share on other sites More sharing options...
Guest wiggyter Posted October 14, 2010 Report Share Posted October 14, 2010 Also, I have had no luck when I keep the gold card in either (the guide tells you to replace it with a non-goldcard after stage 1) Hi alexhtclegend, On Linux he same happened to me, but running the second script with root permissions was succesful. Can you run the script on windows with 'run as administrator'? Maybe that will help. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now