Database Info

[Q] A question about my brick

I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.

jeremiah.wells said:
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
Click to expand...
Click to collapse
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.

MartyHulskemper said:
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
Click to expand...
Click to collapse
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.

Can you get into recovery at all when you hold vol down and power? I had the same problem with my infinity when the .18 update came out, i had a freeze and a crash during normal use while the update was either downloading or changing something and when it restarted I couldnt do anything but go into APX. I never unlocked it (mainly because the asus tool wouldnt work) but I had to RMA to get it fixed. If you can at least get to the recovery menu you can try reinstalling the stock rom from an mSD. Otherwise you may have to do the same as me and RMA and hope that they dont tell you tough luck since its unlocked As far as I know the only way to recover the tablet when APX is your only option is with NVFlash, which I never installed because .30 was on my infinity when i bought it.

jeremiah.wells said:
I couldn't get either recovery to boot and so I attempted a data wipe
Click to expand...
Click to collapse
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).

_that said:
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
Click to expand...
Click to collapse
Yes, with only APX available but no NvFlash backup, there's very little to no light at the end of the tunnel. I also wondered why the reports of RMA'd users mention a motherboard change, but I do remember something about unit-specific code being backed up with NvFlash. Although I'd think it strange, it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
@OP: with no fastboot available, you will not be able to follow either Scott's guide or reflash a recovery. I sincerely feel for you, especially since it was enthusiasm that got you into trouble. I know the resultant feeling, and I hate it, for it quells said enthusiasm in the future and make you overly cautious. I wish you a speedy and effective RMA!

jeremiah.wells said:
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Click to expand...
Click to collapse
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.

I feel for you too as this happened to me even without any type of modifications to my recovery or bootloader! As far as RMA and the motherboard change I am not sure whether they recovered my device without an actual change. When i got it back from RMA it was on the same firmware as before (not the most recent at the time) as well as retaining the same SN on my device. Since I got it back though I am unable to use the unlocker tool. I get that network error and a refusal from the asus unlock server that lots of people were having issues with a while back. I am in touch with Asus service now, but asus service is usually a long arduous process! I hope that they dont charge you for the replacement, but seeing as you unlocked its very possible if you have any sort of insurance from your credit card that may be a better route by trying to replace it as a lost or broken unit. My RMA was free (except shipping) but again, no unlock!
best of luck.

MartyHulskemper said:
it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
Click to expand...
Click to collapse
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.

_that said:
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
Click to expand...
Click to collapse
In cases like this, I always hope you get a motivated technician that actually hunts down your serial from that database and helps you out. Guess I'm a bit naive in that regard.
Yeah, those 16 bytes keeping the door shut are a major bummer, as is the fact that NvFlash was not pre-installed anyway...

okantomi said:
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
Click to expand...
Click to collapse
To answer your curiosity, NO... I did not install or use Rom Manager in any way to get to this state.

Got a question. Mine is rooted but locked, i attempted to install TWRP before unlocking. I can still boot it up but i cant get into recovery. Can i unlock it without a working recovery and just reinstall TWRP? what are my options? Any help would be great.
edit: nevermind, i think i found the answer...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[Q] No way back? (magic ring)

Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.

In that case I'll give ya $100 for it.
Sent from my Galaxy Nexus using Tapatalk 2

zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unfortunately, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thread that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before via HOT LINE but without any response!) This tablet is really a piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Well my friend not exactly the best words to start with if needing help from the many fine members of this forum.
The unlock tool will eventually work if that's what you want to do.
Personally your being "really ugly" to Asus thru e-mail could be why they remain unresponsive.
If you could perhaps take the calm approach those trying to help would be much more willing.

absurd paradox
Unfortunately I can understand where all these negative feelings derive from.
I am the rightful owner of a tf700 too.
To be quite frank (and I won't surprise anyone), I am not pleased.
There is no reason why I can't enjoy a smooth and flowing experience.
There is no reason why in order to make the best out of the tf700 it is recommended that I flash a custom rom.
I refuse to unlock my tf700 because there is no reason why I should void my warranty, trying to fix it - this is an absurd paradox!
It is about time someone filed a class action in order to stop this "tf700 incident",
so Asus will start to make their excuses in court or maybe solve this unfortunate condition,
once and for good.
cheers.

Nothing stopping you from filing a class action lawsuit is there?
Or you could just take control and unlock and flash a custom ROM and be done with it....
Choice is yours as Asus are not going to help you.

wish it was that simple
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
For example, I read a guide which explains how to unlock and install a custom recovery using an "adb tool",
but there is no explanation how to install the newest version of TWRP, which is required for cromi 3.4.X.
Anyone know a plain and full guide for 10.4.4.25 build?

http://forum.xda-developers.com/showthread.php?t=2088176

No very ugly
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks

zrebec said:
OK, that wasn't very ugly mail, just I wrote to ASUS that I tried contact HOTLINE two times and nobody response me I was very frustrated that I cannot unlock my tablet
Can someone explain me, why doesn't exists alternative way around unlock?
The processor is encrypted or what?
Thanks
Click to expand...
Click to collapse
A work around for the unlock isn't available.
Seems as though the key for the bootloader is encrypted very well.
Until someone leaks the key to the internet we're stuck.
My understanding is:
Asus wants the embedded serial for any tablet requesting a bootloader unlock.
The serial is registered with Asus from an outside server database.
Asus voids the warranty then shuts off OTA's because they don't want to push updates over any customisation to the tablets firmware.
This would most likely result in a bricked\non-functioning device.
Asus knows people inherently re-code devices with non-manufacturer firmware and risky applications.
The manufacturer is saying to the buyer we can't be responsible for user induced damage.

zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Another woe-is-me post! Someone please get me a hankie, quick!

zrebec said:
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
Click to expand...
Click to collapse
First of all you could use the search button
Here is a thread where I specified how I got my tablet unlocked: http://forum.xda-developers.com/showthread.php?t=2146543
Just keep in mind that the Asus Support employees are not personally responsible that the MDM-server in Taiwan does not know your tablet. Don't act like a jackass and don't act like mister-know-it-all, then they will help you, like they helped me.
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
Click to expand...
Click to collapse
These forums here provide all information one needs to unlock/ root/ install custom ROMs. I got all information from here and I did not have any problem whatsoever.
You know, people here are willing to share their experience and to help out each other, but the burden to do the work is on you. Also the risk of bricking your device is on you.
Just don't expect anybody to do your work.
As a matter of fact, installing custom ROMs on the TF700 is not trivial. You do need ADB and Fastboot to flash a recovery first. Also you have to have some basic knowledge about how computers work in general and about Android devices.
Even as complete noob, you can find all needed information here. So either you take your time and educate yourself - like I did - or you use the stock ROM or you hire somebody who does the work for you.

Root it but keep it locked! I was loosing sleep at night because I thought I was suckered into believing this was a quality machine and its got tons of glitches, no doubt. But they are mainly lack-of-RAM related. If you root, and disable most of your startups, you can get a clean 500MB after boot, and that makes all the difference in the world, trust me. I was in you boots and was actually dreaming about getting an iPad (please forgive me guys). Honestly, I was sick to my stomach then the rage set in. I decided to learn and root before throwing this POS on ebay or craigs list, and starting over with another brand, probably an Apple, I was so hurt by lack of quality and testing/debug.
Like day and night! Now I love this thing. Hasn't had a random reboot, app crash, etc. in nearly a month now. Before I was getting 5 per day. Its an amazing difference attributed to the OS and apps having room (RAM) to run in. Whoever decided that 1GB RAM for a 4-core droid tablet was enough should be tarred and feathered then shot in the head twice!!! If it had been 2GB instead of 1GB we wouldn't be having this discussion at all.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Unlocked! Yay!
Hello dears,
so I have my tablet Unlocked now... I forgot.... You must register account and then register tablet here https://vip.asus.com/login.aspx?. So maybe this can help to someone... OK, I have installed Clean Rom Inherited now and it looks and works fine Thanks to all.
So steps to reproduce:
1) Create account on https://vip.asus.com/login.aspx?.
2) Register device after that
3) Download Unlock Device App: Unlock boot loader from Android -> Utilities from http://support.asus.com/download.as...Pad Infinity TF700T&hashedid=fq2B3oq64av1O95u
4) Run the application
5) Tick the you understand that your warranty is now VOID
6) Type your google account login and password
7) After restart you should see in up-left corner message "Device is unlocked"
8) Enjoy

Update: Fixed my last known problem which was wifi streaming movies to the device from external source (wifi HDD or network connected storage). Got Dice Player, that's all I have to say. Now EVERYTHING is working perfectly. No more random reboots, app issues, conflicting apps, got plenty of RAM, got all my desired startups loaded including System Tuner with a few tweaks added, Browser2RAM, RAM booster, etc. and device runs fast, smooth, and without any "glitches". I finally have achieved rooted stability and will now take a rest and enjoy this tablet a bit before I do anything more to it because this has been a hair-puller to get to this point. Finally very happy with this device but I had to venture far from stock to get here and it was worth it.
By the way, what day of the week is it?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

NVFlash & APX Mode - What about the impatient ones?

I'm sure by the time you're reading this you have already heard how critical it is to backup the pre .30 bootloader blobs using NVflash so you have a fool-proof plan to recovery from any flashing disaster.
If not, please read about it in the relevant threads:
- [TOOL][BRICKPROOF]TF700 NVFlash release!
- Overview for the Transformer TF700 & Guide
- Technical Details on the TF secure boot key
Suffice it to say, if you upgraded to a bootloader newer than 9.4.5.30r01; you cannot use this tool to make this ultimate backup. The excuses abound and mine is simply the same of impatience. Nevertheless, I've done a good bit of reading about how nvflash and wheelie work and, provided I'm not vastly misunderstanding, wish to work on bringing the same greatness to those of us who have already upgraded past 9.4.5.30r01.
Most of the responses to a lot of these questions I've seen are basically 'sucks for you' and, while that is true, I don't know if it's the whole picture or why.
What precisely changed post .30 in the bootloader? From my understanding you need to first flash staging with a custom built blob (ebtblob.bin) and I wonder if the issue is simply (well, you know.. sorta) based around the pre-.30 bootloader that was reverse engineered? Or is it something far worse?
I would love to hear any of the technical details as I do enjoy reverse engineering Android applications, firmware and pretty much anything.
I'm also curious what is different between each user's backups making one incompatible with another, or is it just as simple as there is no vector to load the recovery images without first having access APX and a fastboot that might as well output a usage of 'reboot, devices'
I've read the great details posted above regarding the TF secure boot process but wondered if anyone would be so kind as to look at what can be done for those who have upgraded past 9.4.5.30r01 and waste sometime explaining the details to me so I might hopefully one day be able to flash new kernels with out the panic attacks I get from that delay between the bootloader and OS load..
Thoughts?

jhannah01 said:
What precisely changed post .30 in the bootloader? From my understanding you need to first flash staging with a custom built blob (ebtblob.bin) and I wonder if the issue is simply (well, you know.. sorta) based around the pre-.30 bootloader that was reverse engineered? Or is it something far worse?
I would love to hear any of the technical details as I do enjoy reverse engineering Android applications, firmware and pretty much anything.
I'm also curious what is different between each user's backups making one incompatible with another, or is it just as simple as there is no vector to load the recovery images without first having access APX and a fastboot that might as well output a usage of 'reboot, devices'
Click to expand...
Click to collapse
1. Starting with the 9.4.5.30 bootloader, Asus added a check that only correctly signed bootloaders can be flashed. That locks out the hacked bootloader (ebtblob.bin) that we need to obtain the blob for wheelie.
2. The chip ID and the related SBK are unique per device. The bootloader is encrypted with the SBK, so each user's backup is different and not exchangeable.
For more info, read the whole nvflash thread - it's all already explained there.

Why so many soft bricks and recovery problems?

I've never seen a two day span where I've seen this many near bricks and recovery problems. Its starting to look like the TF300 fiasco. Did CWM screw something up recently or are all these user problems unrelated and coincidental?

elfaure said:
I've never seen a two day span where I've seen this many near bricks and recovery problems. Its starting to look like the TF300 fiasco. Did CWM screw something up recently or are all these user problems unrelated and coincidental?
Click to expand...
Click to collapse
It is mostly user problems, but CWM can brick your device by wiping the wrong partition. TWRP has been patched and wont do this. AKA why TWRP is recommended, rather than CWM, which is a good recovery, but for our device it can cause issues. And if you read, 99% of the bricks are recovered. So the point of the bricks is nothing, it is if we can recover them or not, to which most are, which is a wonderful thing. 10 TF300s a day were bricking, this is not occurring with the TF700, so there is no fiasco happening here .
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.

_that said:
Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.
Click to expand...
Click to collapse
As a newbie, I may suggest that the Tylorw1 remarks could be announced on the http://forum.xda-developers.com/showthread.php?p=30223822#post30223822 topic (regarding that it is advised to use TWRP until CWM will be patched). Because I parsed all this topics and others before starting to flash my TF700 and never seen that recommandations and the other like "do not use software launch of recovery". Those information, you can only get them on the topic you look at once you have had an issue.
I was not totally a newbie with switching to developer mode / rooting / flashing, since I began doing this on my HTC magic, continued with an HTC desire HD, then a galaxy note. Never got those hard troubles (once I had a fear, but has been able to unlock it alone with my magic).
At last, that's very good you're here to help us after our mistakes!

The problem is that there are a lot of (stupid) people who can't bloody read.

florck said:
At last, that's very good you're here to help us after our mistakes!
Click to expand...
Click to collapse
I must be honest: I fear the day _that transitions to another device. The work he put in in your case is nothing short of amazing (to me). We all have our perks and qualities, but... pfff...
On-topic: it does seem like we are having more bricks and recovery/boot problems lately. Is that a market thing? Has the 700 gone done in price, thus reaching a greater user base? (Not to my knowledge.) Are we seeing more inexperienced users now than we did at first? (That might be a likely cause.)

_that said:
Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.
Click to expand...
Click to collapse
Well put. We have two ears and two eyes and two hands but only one mouth. Intelligent people tend to use their senses in those proportions. Only after they have mastered this can they attempt to use their brains.

MartyHulskemper said:
I must be honest: I fear the day _that transitions to another device. The work he put in in your case is nothing short of amazing (to me). We all have our perks and qualities, but... pfff...
On-topic: it does seem like we are having more bricks and recovery/boot problems lately. Is that a market thing? Has the 700 gone done in price, thus reaching a greater user base? (Not to my knowledge.) Are we seeing more inexperienced users now than we did at first? (That might be a likely cause.)
Click to expand...
Click to collapse
I'm going to be the first to second @florck 's suggestion to top-sticky a warning about CWM with a statement that it could wipe the wrong partition and leave the user SOL (maybe not in those exact words) and for XDA to point a suggestion towards using TWRP (touch) instead as a safe alternative. At least until CWM patches this bug. This would be paramount for new users to read. I found it during my rooting research but I agree that its fairly buried.
[Edit] One thing to note is he was not using an "old" CWM, in fact it was a future developer version not even released yet?? So the masses haven't even seen this version yet. Someone should inform CWM about this before they release it, it if came from them broken. I don't think I'll ever be using their recovery after seeing what can happen.
*************************************************************************
Quote @Pretoriano80 from other thread: "CWM 6.0.5.3?The latest official version is 6.0.3.0 iirc. AFAIK this kind of brick occur when using an" old" recovery (both CWM and TWRP) with the new bootloader and is triggered when the Wipe Data option it's used."
***************************************************************************
I'm also interested in learning how his cryptographic key got messed up/deleted. I've been wondering if this could be used for a bootloader exploit to enable NVflash?
Lucky for @florck to have @_that for sure as we all are, but also lucky for him he wasn't that much of an inexperienced user that he couldn't at least access a terminal and type some commands, run an adb shell, and follow instructions. He seemed to be a pretty good student but he should have read more I agree.
I find there are three types of people. Dumb people who never learn from their mistakes, smart people who do learn from their mistakes, and then there's the wise people who learn from *other peoples* mistakes.
For me as a fairly inexperienced user getting to ride the roller coaster and see the guts of a near brick was fascinating to say the least. Its good to know about these things before you need to. Its great to know @_that if you don't. His knowledge and troubleshooting prowess is phenomenal. Rare breed indeed. It wouldn't surprise me if he didn't have a mother and was beamed down.

Guys, i think you are mixing stuff here, let me explain.
1)The "wipe data/media" option in CWM
This bug can lead to a corrupted partition but it's easy to recover by installing the Stock Firmware from MicroSD with CWM recovery (yes CWM install option will still work because the staging partition is not corrupted). After the install process is complete and the tablet rebooted once you can use the Wipe Data option from the Bootloader menu, that procedure will also fix your corrupted data/media partition.
So as you can see no ADB knowledge or other skills are required in order to recover your device.
2) Using and "old" recovery version with an incompatible bootloader (both CWM and TWRP recovery)
Using the Wipe Data option from the Bootloader menu under this circumstances could lead to a bootloop to Recovery and if you don't have good ADB knowledge/skills (or if _that it's not around ) you are doomed. Anyway it seems that as long as you still have ADB you can recover from this too.
Also some users reported a hard brick under this circumstances (bootloader signature mismatch error) but there wasn't much background info from the users on the matter.
ONLY way to recover from this issue is by sending the device back to Asus and pay for repairs.
3) Regarding the missing token my understanding is that a wrong offset was used so i presume that using the correct offset you will find that the token is still there.
And even if someone could remove the token it would still be impossible to trick Asus because they already have your device's serial number on their server.
P. S: I already planned to update the AIO thread with the latest stuff /info but i've just got recovered from a knee surgery so i'm not in the mood yet.
Using
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Thanks for the very clear play-by-play problem descriptions and future resolutions of what recently happened with the one user's near brick who then witnessed the miracle of _that in action. It'll be good for CWM users if it comes up again so they can self-resolve their problem with your instructions.

Flatline: Thanks a lot to the AndroidRoot.Mobi team

I can't reply in the developers section..
i want to let you know that I successfully installed nvflash on my tf700 with 10.6.1.14.10 Bootloader and CROMi-X 5.0.4 and TWRP 2.6.1.0 using Ubuntu 13.04
Thanks a lot to @rayman and all the AndroidRoot.Mobi team and all the developers here on xda!!
Now i gonna play hard with my tf700!!

Seriously
When I got the news of this, I was overjoyed! I've had to send my tablet in to Asus for repair because they gave just enough access for you to be able to break something, but not enough access to fix it... Now that's no longer an issue! Thank you very much AndroidRoot.mobi!
There's one small thing that I object to: You've (AndroidRoot.mobi) said that "you'll let us know how to use it when we need it". There are many people who have followed your directions completely, and now have the files they need to restore their system, and a very powerful tool that can make/break their tablet.
I personally already know how to use it, and have already made a batch file for myself (on your terms, I'm not going to distribute it) to automate a complete system restore of my tablet to factory settings.
Keeping the "how-to" of this amazing and wonderful tool secret is kinda like giving a loaded weapon to a child... I think if people knew more about it, they could make better decisions on how to use it. Just a suggestion!
Besides that, I can't thank you enough for coming up with this solution! Since I've got my tablet back from the Asus repair, I've been very cautious about what I flash, but this tool allows me to not have to worry so much about it!