FORUMS
Remove All Ads from XDA

Fastboot flash failed: error too many links

20 posts
Thanks Meter: 0
 
By Xeroproject, Junior Member on 3rd February 2009, 03:49 AM
Post Reply Email Thread
Quote:
Originally Posted by trmacdonal

How to Restore your phone on a Windows PC using a Nandroid backup

I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.

What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/show...53&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img

Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:

fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot

Your phone should now be restored exactly as you had it when it was backed up.

I'm young yet in my android/linux learnings and this guide here is great. I've been soaking in information for weeks now on the boards but still, my kungfu is weak.

Hence I'm having an issue today and I've been working on it almost all day so far. Something happened and I ended up having to factory restore my phone and I'm attempting to recover from my nandroid backup files.

I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.

My HTC is correctly running in Fastboot as an ADB Interface in WinXP Pro SP3, I've got my nandroid backup files placed in the C:\Android folder on my pc as directed. Fastboot is in the /system32 folder (and in cmd Fastboot devices lists my phone), but I keep banging my head into this error over & over. Its driving me pretty insane and any help would be appreciated. I know you guys aren't a support desk and I'm probably screwing up something elementary, but I just wanted to say that I'm finally asking as a last resort. I've been trying to figure this out myself for about 9 hours now. My thanks in advance.
 
 
3rd February 2009, 04:10 AM |#2  
Member
Thanks Meter: 59
 
More
Quote:
Originally Posted by Xeroproject

I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.

If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.

Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.
3rd February 2009, 04:21 AM |#3  
Xeroproject's Avatar
OP Junior Member
Flag Seattle, WA
Thanks Meter: 0
 
More
Quote:
Originally Posted by infernix

If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.

Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.

Thanks for the suggestion, I'll have to see if I can find a suitable USB cable, although from some inquires to linux buddies more in the know, I was told it was indicating a "a circular reference symlink" either in fastboot or in the command I used.

Considering I used exactly the commands in the guide, I'm puzzled. Also, I pulled the fastboot.exe for win32 from JF's own attachment.

Regarding another PC, yes, that would be ideal for troubleshooting this, however the pc I have at home is Vista 64bit (unfortunately), so shouldn't I run into issues there?
3rd February 2009, 05:31 AM |#4  
Retired Moderator
Thanks Meter: 11
 
More
Quote:
Originally Posted by Xeroproject

Hrm, sorry about the few posts in here mods, it seems my issue isn't related to a mistype in the command line of trmacdonal's guide like I thought it was, so its most likely not related to this thread & needs to be split into a separate thread to prevent clutter.

I have noticed something regarding my situation: in command line when I type "fastboot devices" it recognizes & lists my phone. However when I type "adb devices" it does not list my phone. Might this be related?

ADB won't see your device till it has booted into android.

And send me a PM with the post numbers and a new thread title and I will move your posts and any posts related to them.
4th February 2009, 03:05 AM |#5  
Xeroproject's Avatar
OP Junior Member
Flag Seattle, WA
Thanks Meter: 0
 
More
So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.

So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.

Is there any information I can include that would help pinpoint whats causing this issue?
4th February 2009, 03:10 AM |#6  
JesusFreke's Avatar
Recognized Developer
Flag Dallas
Thanks Meter: 52
 
More
Quote:
Originally Posted by Xeroproject

So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.

So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.

Is there any information I can include that would help pinpoint whats causing this issue?

Have you tried booting normally at least once?

Maybe try "fastboot erase cache", then try again?
5th February 2009, 01:53 AM |#7  
Xeroproject's Avatar
OP Junior Member
Flag Seattle, WA
Thanks Meter: 0
 
More
Quote:
Originally Posted by JesusFreke

Have you tried booting normally at least once?

Maybe try "fastboot erase cache", then try again?

If you mean booting normally into Vista 64, yes, it sees the G1 as an "unknown device" in Device Manager and when I point it to the 64-bit driver, it won't take it. Same for when driver auth is disabled. (although the message changes from "no device drivers found" to "this driver is not compatible with your device)

If you mean the phone, yes, the phone works, its not bricked, but there's a lot of data I'm losing if I can't solve this issue & backup from my nandroid backups.

I'll give the erase cache thing a shot now and post results, thanks for the suggestion.
5th February 2009, 01:56 AM |#8  
Xeroproject's Avatar
OP Junior Member
Flag Seattle, WA
Thanks Meter: 0
 
More
interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error

Perhaps the problem is with the fastboot.exe file?
5th February 2009, 02:10 AM |#9  
JesusFreke's Avatar
Recognized Developer
Flag Dallas
Thanks Meter: 52
 
More
Quote:
Originally Posted by Xeroproject

interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error

Perhaps the problem is with the fastboot.exe file?

I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.

It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?

I would also try any and all of the fastboot commands

If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.
5th February 2009, 02:20 AM |#10  
Xeroproject's Avatar
OP Junior Member
Flag Seattle, WA
Thanks Meter: 0
 
More
Quote:
Originally Posted by JesusFreke

I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.

It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?

I would also try any and all of the fastboot commands

If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.

Yeah, I wish I knew the cause of it, but the initial use was uninterrupted (and everytime I reboot, I will get 5-10sec lag before getting the error, while after that the error will popup immediately)

I'm happy to try any of the fastboot commands, but being a little nubbin, I'm a little afraid of doing any damage. I did try fastboot reboot and fastboot reboot-bootloader and got no response from the phone. "fastboot devices" immediately sees my phone. "fastboot flashall" returns: "error: neither -p product specified nor ANDROID_PRODUCT_OUT set".

Removing the battery is something I've done a couple times the other day, just gave it another shot now, same result. I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write".

Concerning reloading the phone back to RC29....you mean taking it back to RC29, then reflashing the Engineering SPL, then immediately trying to backup from my nandroid backups? (prior to installing any of the JF OS versions?)
5th February 2009, 02:21 AM |#11  
Member
Thanks Meter: 9
 
More
I have also faced this error few time, what I do is disconnect the USB, restart both PC and G1, next time I get proper connection, once time I was able to resolve just by moving the ramdisk.img and kernel file from the directory, this was when I was using the fastboot -w flashall command!!

-Pramod
Post Reply Subscribe to Thread

Tags
backup, fastboot, nandroid, too many links

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes