[Legend General] tssf:
Hi there,

So I'm trying to re-root my HTC Legend from Virgin Mobile. I had success with rooting it the first time using a guide from techenclave (it seemed to be the most complete, most robust, and most user-friendly guide out there..). This guide also merged a lot of the accumulated information on the internet and was the only one (that I could find) that mentioned to use MMC0 if MMC1 didn't work whilst making a goldcard.

I did this on January 9th.

However, January 22nd, the mod I was using (cyanogen 6.2.1) started to have problems, widgets were getting corrupted and certain links stopped working properly..so I decided to start it over from scratch by re-flashing with RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_signed.exe

It worked, so I'm back. I tried following all the instructions again, which brings me to now.

I make it past step1, then the phone reboots back to the bootloader. I load to Recovery mode (the phone has a little

/!\

in the corner), when I type "step2-windows.bat", random results seem to pop up.

C:\froyoinstall\r4-legend-root>step2-windows
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
31 files pushed. 0 files skipped.
1417 KB/s (3734509 bytes in 2.573s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:

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:\froyoinstall\r4-legend-root>

this is what happened the second time I did it:

C:\froyoinstall\r4-legend-root>step2-windows
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:\froyoinstall\r4-legend-root>

When I did it a third time, the first results happened again (but keep in mind it's totally random, it could go to the first one or the second one)

So, I searched up and noticed my adb.exe was certainly out of date, so I loaded Android's SDK Manager and it downloaded "revision 2" of the "platform-tools" kit, which did not help at all.

Booting the phone loads the stock ROM that HAS root access, but ROM Manager will not reboot to ClockworkMod's Recovery (despite successfully flashing).

Any advice or help would be totally appreciated, I've been scratching my head on this for the past little while.

UPDATE:

I noticed when rebooting the phone to the bootloader, it states "S-ON" .. do I need to shut that off? I'll try AlphaRev to see if that fixes things.

UPDATE 2:

I don't know..through sheer persistence and luck.. (I think mostly just luck) I swapped out SD Cards, and now Step 2 worked. I did this step before and it didn't..but now I am all good.

You can lock this topic, now. Thank you.