[Asus  Eee Pad Transformer Prime] wickid_d:
Did you run through the nvflash process and get your blob files and all that, before you started this? Or can you at least get to fastboot via key combo?

THAT post, sir, made my morning, lmao! Thank you! It's great when you can wake up and laugh! :D

I know EXACTLY how you feel.. mine is way up there too, and I'm quite a logical thinker.. And I'm pretty sure I've been through about every type of brick you can get in with this tablet, so I also know how to pull out of every type. The problem is trying to establish the current type of brick a person is in, in order to help them, because you rarely get enough information to establish this. Also, you're absolutely right, you're not going to find a detailed thread or manual on the inner workings of nvflash anywhere on the forums or on androidroot.mobi, the AndroidRoot Team's site (or at least, to the best of my knowledge, it doesn't exist in these places), and the creators of the nvflash tool that we use. The ONLY place you're going to find this (once again, to the best of my knowledge.. I could be wrong) is by looking through the header files that go into compiling nvflash, on their github. The best their site can offer is telling what nvflash does and how to use it for various situations, but as for built-in options, yeah, that's the best advice I can offer. I honestly looked for something similar when I got started with using nvflash myself, as I'm sure a lot of us out here in xda tf201 land have, and this was after I hard-bricked my first board for this tablet because, at first at least, I refused to believe you could hard-brick something that works exactly like a pc (when you really sit and think about it), without it being a hardware malfunction. Alas.. the embedded world is a little bit of a different ballgame. I even went so far as to contact one of the nvidia engineers that contributed to a github branch to see if there was any way out of that type of brick, and the answer I got back wasn't much of a help because he explained that there's actually a hardware tick that gets set when you tell the board to boot the recovery image, and if you have it in a position to where it sees that hardware tick before booting, and the recovery is screwed, then the entire board is screwed because of that (because it keeps trying to boot the screwed recovery), and your only options are the uart interface or apx mode, which (as he went on to explain) is a mode that interacts with the uart interface, internally. I also asked him about the uart interface that is on the boards (there is one, I forget where exactly, but it's 4 gold landing pads for soldering to, and they're small), and he said that even in the low-level state, you still need the 128bit security key to unlock that interface, which is what nvflash embeds into blob.bin, and why running through the nvflash process is, basically, an essential part of doing anything advanced on these as a preventative measure.

I apologize to anyone that reads this (also for the thread jack and getting off topic again), including you lewmur, for the long read, but I figured some clarification was in order for any of us logical thinkers (which it sounds like you are), as to why it's easier just to say f*** it and get it done than to keep searching for something that you may never utilize fully. I just hope I haven't upset you more lewmur. That definitely was not my intent if I did.