[Asus Transformer TF700] MartyHulskemper:
EDIT: before even reading this incredibly long P.O.S. -- does the flashing procedure work on 64-bit Linux only? That's what some online sources say. I'm doing this on Windows 7 x64. If that's very stupid, just laugh openly at me, tell me, and I will get that dualboot Ubuntu 64 up and running ASAP (and probably run into a thousand other problems, but I'll get by eventually then).

Hi guys and girls, I need more brain capacity than my peanut-size one has been able to provide for the past four hours. Web searches led to nothing, so apart from banging my head on my desk (which I've done several times now), you are my only hope of getting this to work (and preventing a worse headache than I've already got :) ).

I have installed the Universal Naked Driver, and have all files in their respective directories (I've even gone so far as to put them all in the same directory (C:\android-sdk\platform-tools)... nvflash, wheelie, the blob bin file, fastboot's there, adb's there -- it's one big, happy but slightly dysfunctional family. :cowboy:

While in CM10u, ADB connects properly (if only after killing and restarting the adb server, but I can live with that ;) ) and reports with a device ID (015d262e9917ec07 device), so I guess there's nothing wrong with either my USB port, the cable or the device in the proper sense. Windows 7 x64 detects the 700 in ''normal'' mode (i.e., in ADB, CM10 Unofficial running) under "Asus Transformer Prime ADB Interface".

While Windows reports "Asus Fastboot Interface" when trying to connect to fastboot, and while I can get fastboot to reboot my 700 with "fastboot -i 0x0b05 reboot", I cannot get it to flash anything, and I've tried using it with and without "-i 0x0b05" flag --- "fastboot -i 0x0b05 devices" just give me a nice set of DOS help crap (list of usable flags and parameters) -- no device being detected at all), while "fastboot devices" just gives me "? fastboot".

If I try to flash the AndroidRoot bootloader with "$ fastboot -i 0x0b05 flash staging ebtblob.bin" I get a report that "$ is not a recognized command.... blablabla". Realizing this is Windows ;) I do "fastboot -i 0x0b05 flash staging ebtblob.bin".... and that's where the fun starts. It borks out with "Failed to process command download: 001ccf48 error(0x120003)", with fastboot borking terminally while uttering "sending staging (1843 KB)... FAILED (data transfer failure (Too many links)) finished. total time: 0.010s"...

This "too many links" thingy hasn't been solved consistently before, based on some web searching, so I hope you clever people have something clever to say (I've learned so much in here over the years, I wouldn't even be surprised, to be honest ;) ). The only upside is that the process fails faster than I can blink my eyes -- that keeps things rolling, at least. :o Is this an error I can do something about? Should I reflash the ROM I'm currently on? Should I revert to stock? On a PC, this would mean something got corrupted -- could it be the storage itself (RAM or otherwise)?

Ugh... I'm getting so tired and frustrated, and feel miserable. I'll just go to bed now and get back in here tomorrow. (I wish I could say that'd be tomorrow afternoon or in the evening, but knowing me, checking out here will probably be the first thing I do when I wake up. ;) )

Thanks for even reading this long crappy post, and I'm glad with any ray of light in this darkness, and any shred of advice on how to proceed to get this working. I've been OCD-flashing a lot the past year on several devices (5, without the security of Nvflash </stupid>), but I cannot think of any solution here...