EDIT :Successfully rooted my phone via changing the microSD card, did the downgrading process, Goldcarding and rooting process from scratch and it worked!
Hi , i have just created an account after failed rooting on countless tries , i tried all the methods the forum gave me ... so i just opted to create an account to post about this problem im having ...
ok , i downgraded successfully , running ROM ver 1.31.405.5 , my HBOOT is 0.43.00001 , MICROP-0816 ,RADIO-7.05.35.26L, LEGEND UNKNOWN SHIP S-ON so i should be fine to start rooting right?
i followed MaDaCo's Steps and failed numerous times at step 2 , the green recovery window wont show itself! then i found other guides where it says do not remove the goldcard after step 1 as shown here
youtube.com/watch?v=SQzo6qahctk
this is my step 1 proceedure in the CMD :
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
sending 'zip' (121756 KB)... FAILED (command write failed (Too many links))
< waiting for device >
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
....
then it continues to all the way ...
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.
so i followed the Unlockers way now ... not removing the goldcard and going straight into Recovery mode ( the triangle with the ! sign ) and started Step 2 in CMD :
C:\r4-legend-root>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 *
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.
1577 KB/s (3734509 bytes in 2.312s)
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
and then im STILL at the bloody triangle box with no green recovery window anywhere in sight.
EDIT: about the ADB Server didn't ACK , i tried numerous times after rebooting and spammed step 2 bat file , i would get this :
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.
1577 KB/s (3734509 bytes in 2.286s)
adb server is out of date. killing...
*daemon started successfully*
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
Everything else is the same , whether ADB Server didn't ACK or not
While in Recovery Mode , i pressed volume up + power i would get a small blue recovery window , at the bottom it says "E:Can't open/cache/recovery/command"
it will be there no matter what, even before doing step 1 or 2 , i went to recovery mode afew times to check what is wrong and would always see THAT message ...
so can anyone point out what is wrong ? Q.Q
THANK YOU SO MUCH IF YOU HELPED ME !!
, im currently stuck on ROM 1.31 , i cant upgrade to later versions of rom for some reason. so its me rooting this legend or nothing 
Edit again : about this error :
sending 'zip' (121756 KB)... FAILED (command write failed (Too many links))
i re-downgraded , tried the rooting process again , and this error did not show up, the process itself was identical to what i posted above. Main problem lies in step 2 where the green recovery windows dont pop up ... i suspect that after "pushing" the 31 files , there needs to be more "pushing" of files to SD card but failed to do so? :/
Hi , i have just created an account after failed rooting on countless tries , i tried all the methods the forum gave me ... so i just opted to create an account to post about this problem im having ...
ok , i downgraded successfully , running ROM ver 1.31.405.5 , my HBOOT is 0.43.00001 , MICROP-0816 ,RADIO-7.05.35.26L, LEGEND UNKNOWN SHIP S-ON so i should be fine to start rooting right?
i followed MaDaCo's Steps and failed numerous times at step 2 , the green recovery window wont show itself! then i found other guides where it says do not remove the goldcard after step 1 as shown here
youtube.com/watch?v=SQzo6qahctk
this is my step 1 proceedure in the CMD :
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
sending 'zip' (121756 KB)... FAILED (command write failed (Too many links))
< waiting for device >
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
....
then it continues to all the way ...
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.
so i followed the Unlockers way now ... not removing the goldcard and going straight into Recovery mode ( the triangle with the ! sign ) and started Step 2 in CMD :
C:\r4-legend-root>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 *
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.
1577 KB/s (3734509 bytes in 2.312s)
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
and then im STILL at the bloody triangle box with no green recovery window anywhere in sight.
EDIT: about the ADB Server didn't ACK , i tried numerous times after rebooting and spammed step 2 bat file , i would get this :
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.
1577 KB/s (3734509 bytes in 2.286s)
adb server is out of date. killing...
*daemon started successfully*
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
Everything else is the same , whether ADB Server didn't ACK or not
While in Recovery Mode , i pressed volume up + power i would get a small blue recovery window , at the bottom it says "E:Can't open/cache/recovery/command"
it will be there no matter what, even before doing step 1 or 2 , i went to recovery mode afew times to check what is wrong and would always see THAT message ...
so can anyone point out what is wrong ? Q.Q
THANK YOU SO MUCH IF YOU HELPED ME !!
Edit again : about this error :
sending 'zip' (121756 KB)... FAILED (command write failed (Too many links))
i re-downgraded , tried the rooting process again , and this error did not show up, the process itself was identical to what i posted above. Main problem lies in step 2 where the green recovery windows dont pop up ... i suspect that after "pushing" the 31 files , there needs to be more "pushing" of files to SD card but failed to do so? :/
Last edited: