Database Info

Is the boatloader's unlockability covered under warranty?

Unfortunately I got one of those tabs that won't OTA or unlock. I've contacted asus and told them that I can't receive OTAs, and I got the canned "flash the updates manually".:silly: This is an unacceptable solution because for one it's a PITA to update it that way, and I still won't be able to unlock the bootloader.
I have avoided mentioning the un-unlockable boatloader problem to the asus rep because I'm not sure it is covered under warranty. But the has me thinking: Could I argue that the device is being sold as unlockable and my device does not meet that spec and is therefore defective? If not, could I argue the same for the fact that it won't receive OTAs?
I am also wondering if the reason it won't function properly is because I got it as an exchange from Best Buy instead of buying it fresh. Has anyone gotten it the same way and not had the same issue?
I'm still within my 30 days, but I'm afraid if I exchange it I'll get another un-unlockable tablet.

I'd advise you to:
1) not argue that unlockability is a device 'feature', since pretty much all Android devices are sold locked, and since you purchased it in that state -- not even knowing if the unlocker will become become available or not -- signifies your accepance of the device even in a locked state;
2) press the fact that you canot receive OTAs and that workability suffers as a result. At least under European consumer law, ASUS would be responsible for selling a finished and workable product. The state in which the TF700 has shipped so far is suboptimal to say the least, and the fixes since have brought tangible improvements. Saying "oh, flash the updates manually yourself" in my mind is the same as a automobile manufacturer opting to NOT do a calllback of sold vehicles due to some ailment (faulty brake discs, or safety belts or something) but instead shipping the parts to their customers and saying "well, you can handle a pair of scissors and a screwdriver, right? Do it yourself then." -- I say, screw them. If this argument fails as wel, you have a support rep with only a few glands where the brain should be located (probably only a visual cortex to be able to type on a keyboard and find it way to the toilet). If that is the case, first drop Gary Key a line, since he has offered to intervene on a customer's behalf before. That might be a second line of rescue.
3) If all else fails, exchange nonetheless, the risk of receiving another essentially-faulty unit notwithstanding. If OTAs and the bootloader issue are a sign of ASUS not having your serial number in their database, you might get into trouble if in need of warranty later on. I'd prefer a few returns to issues down the way (even though I know the feeling of having to wait yet again, and having to run the setup again and so on, and so on), but hey, that's just me.
Sent from my ASUS Transformer Pad TF700T

1. I guess I could say that because asus released the bootloader unlock, and it works on most of the tablets except for mine, that my tablet is not receiving the same services due to a technical glitch. Heck I could even say the same for the OTA updates.
Fear Not, I am avoiding this argument religiously. I don't even want to mention the "b word" to asus, it would complicate the issue more than it needs to be.
2. I am leaning hard on getting the OTA updater fixed. At the moment it's what I am most concerned about. ASUS telling me to flash the updates manually is less than acceptable. It's simply not convenient or practical for me to continue to flash them manually. The problem is that the problem is beyond the tech support people. Which is not surprising. The engineers are the only ones with the actual knowledge and they don't deal with customers. The tech support are merely handed a card with questions and responses. My only hope is to press the rep until they hand the matter off to someone more knowledgeable. The bootloader I guess is what is driving me to get the problem fixed.
My problem at the moment is trying to prove that the ota's are broken. The rep told me that the .26 update probably hasn't been released to my district yet and I should wait. I say BS, the .26 update has been out for long enough I should have gotten it. I even gave the bootloader unlocker a shot: network error. Yup, I would be gray long before the update to hit my device. Problem is I can't say that to the rep without mentioning the aforementioned "b word".
Fortunately, I read a thread here (I'm too lazy to look it up now) about a prime user who successfully RMAd for the same issue, and got it fixed.

rightonred said:
1. I guess I could say that because asus released the bootloader unlock, and it works on most of the tablets except for mine, that my tablet is not receiving the same services due to a technical glitch. Heck I could even say the same for the OTA updates.
Fear Not, I am avoiding this argument religiously. I don't even want to mention the "b word" to asus, it would complicate the issue more than it needs to be.
Click to expand...
Click to collapse
Sounds like a plan to me.
2. I am leaning hard on getting the OTA updater fixed. At the moment it's what I am most concerned about. ASUS telling me to flash the updates manually is less than acceptable. It's simply not convenient or practical for me to continue to flash them manually. The problem is that the problem is beyond the tech support people. Which is not surprising. The engineers are the only ones with the actual knowledge and they don't deal with customers. The tech support are merely handed a card with questions and responses. My only hope is to press the rep until they hand the matter off to someone more knowledgeable. The bootloader I guess is what is driving me to get the problem fixed.
Click to expand...
Click to collapse
Yup, you're caught in a protocol. Not bad in itself, but when you;re experiencing soething that isn't covered by the protocol, you're pretty much screwed unless you can get through to their second line of defense.
My problem at the moment is trying to prove that the ota's are broken. The rep told me that the .26 update probably hasn't been released to my district yet and I should wait. I say BS, the .26 update has been out for long enough I should have gotten it. I even gave the bootloader unlocker a shot: network error. Yup, I would be gray long before the update to hit my device. Problem is I can't say that to the rep without mentioning the aforementioned "b word".
Fortunately, I read a thread here (I'm too lazy to look it up now) about a prime user who successfully RMAd for the same issue, and got it fixed.
Click to expand...
Click to collapse
I think that you should have gotten the update by now as well. It seems to have been delivered worldwide, so there's no reason for you to be exempt from the bliss the rest of the owners are already experiencing. The bootloader not unlocking due to a network error is an argument believable for two or maybe three tries, but when it stubbornly keeps refusing to be unlocked, well, that is symptomatic of something else.
I did hear several reports of Prime users getting their units succesfully RMA'd, but also at least one user reporting that he received his unit in an locked state, from which he was no longer able to unlock. That might be a problem in your case...
Sent from my ASUS Transformer Pad TF700T

Its a shame though, the tablet works perfectly other wise. The wifi and gps reception is excellent. no dead pixels, hot pixels, dark or light spots, dust under display, scratches, etc. The screen is bonded frimly to the back and is not loose. In fact I think it's one of the nicer tabs out there. It's just that the thing won't update (or unlock).

rightonred said:
Unfortunately I got one of those tabs that won't OTA or unlock.
Click to expand...
Click to collapse
There must be a problem with some of these tablets and OTA updates. I received my Infinity a week ago with the. 21 firmware. No matter what I did it would not update OTA to 22. I did a manual update to. 22 which was very easy. A couple days later. 26 was available on their website. Again no OTA update and again I did it manually with no problem. My Infinity was neither rooted or unlocked at the time though I rooted after the. 26 update. I have read post on various forums with other owners with the same exact update issue while others did receive their updates OTA. I guess that shows that there are differences between this same model being it a software or hardware problem. Other than the OTA update issue my Infinity is working great. Much better than the 3 Primes that I owned.
Sent from my ASUS Transformer Pad TF700T using xda premium

Eddie Hicks said:
There must be a problem with some of these tablets and OTA updates. I received my Infinity a week ago with the. 21 firmware. No matter what I did it would not update OTA to 22. I did a manual update to. 22 which was very easy. A couple days later. 26 was available on their website. Again no OTA update and again I did it manually with no problem. My Infinity was neither rooted or unlocked at the time though I rooted after the. 26 update. I have read post on various forums with other owners with the same exact update issue while others did receive their updates OTA. I guess that shows that there are differences between this same model being it a software or hardware problem. Other than the OTA update issue my Infinity is working great. Much better than the 3 Primes that I owned.
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
We have a strong hunch that the issue is on ASUS' end, probably the serial numbers not being available in their database of shipped units, and therefore a) preventing OTA and b) preventing bootloader unlocking (since that's another instance of serial number checks against said database). Has any one of you run the unlock app already? I'd bet a beer on it it fails as well.

MartyHulskemper said:
We have a strong hunch that the issue is on ASUS' end, probably the serial numbers not being available in their database of shipped units, and therefore a) preventing OTA and b) preventing bootloader unlocking (since that's another instance of serial number checks against said database). Has any one of you run the unlock app already? I'd bet a beer on it it fails as well.
Click to expand...
Click to collapse
You didn't loose that beer.
The I-can't-unlock-or-update club is picking up quite a few members. I'll have to remember to bring donuts and coffee to the next meeting.
Anyway, I've given up on tech support. If it's affecting a significant number of people, asus will find out about it and fix it. At the moment it's a pain, but I'm not too worried.

Difference between firmwares

Hi,
I am currently in China and bought a TF300T, but although I did foresee it might not have the google apps included, I foolishly thought it might be simpler to install them. I read a bunch of threads, it seems that it is possible to change the firmware, but I have a question, what is the difference between a WW (I assume world wide?) and US file?
Also...
Is there a simpler way to install them?
Finally, the thread I read mentioned this doesn't void the warranty, is it true? I don't have a lot of hope for the warranty anyhow because in a few weeks/months I will go back to my country (Mexico) and I don't think they will honor it there... I bought the tablet here because right now in Mexico the TF101 is going for more than 500 USD, they are not even selling the TF300. We get robbed badly with electronics.
Thanks in advance

Firmwares updates come from Asus so there is nothing wrong with updating. You will have warranty in México as long as you keep your receipt and warranty card you can take it to an Asus service center for warranty repair for 1year. I'm not quite sure if there are any real differences between WW and US firmwares, living in Mexico you will probably have the WW firmware, so I suggest you just stay on that one. I don't understand why you say it didn't come with gapps it does come with gmaps, Gmail, gtalk, Google plus etc.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

jgaf said:
Firmwares updates come from Asus so there is nothing wrong with updating. You will have warranty in México as long as you keep your receipt and warranty card you can take it to an Asus service center for warranty repair for 1year. I'm not quite sure if there are any real differences between WW and US firmwares, living in Mexico you will probably have the WW firmware, so I suggest you just stay on that one. I don't understand why you say it didn't come with gapps it does come with gmaps, Gmail, gtalk, Google plus etc.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
no, right now I have the CN firmware, which has baidu and some other chinese apps...

Ah I see, then you should flash the latest WW firmware.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Am I still about to change to different region? I already upgraded it to JB OTA recently. Thanks.

uc4n7cm3 said:
Am I still about to change to different region? I already upgraded it to JB OTA recently. Thanks.
Click to expand...
Click to collapse
if it was the tg version or a phone using the "wrong" region firmware could mean having the wrong 3g baseband and thus losing connection but as your tablet has no 3g this shouldnt be a problem.
probably you'll need to download the extended languages file from play store for getting chinese characters and keyboard.

No Jellybean update in Japan...yet.

Just thought I'd let you know of a little issue. I bought my TF300T in Japan (love this tablet) and I'm still awaiting an OTA for JB. I emailed Asus 'customer service' to ask them for a rough schedule, they fobbed me off stating that I was to phone the local Asus office, I tried the number they gave me and lo-and-behold, it's dead. So I emailed back a rather testy email (I'm rather sick of them pushing paying customers to the back-burner, I had issues with my TF101 too)
and was yet again fobbed off with a generic 'we'll sort it' response.
The long and short of this moan is to find out if anybody can find out the release date for JB OTA in Japan, I'll check the Asus website again soon and I've looked on Google, so my skills may be lacking. I'm reticent to unlock, because of the issues I had with my TF101.
Many thanks.
Sent from my ASUS Pad TF300T

unless you need japanese software, you could try the method to switch your firmware to US or WW, then apply the update for those (no unlocking needed)... I did that with the chinese firmware, specially because I wanted to get rid of the chinese apps and have google's. Lots of people are not happy with JB, so give that some thought too... personally I have had no issue other than a little less battery life. No big deal because I don't use the tablet heavily, maybe if I did I would have a different opinion :S

It is worth consideration, thanks for your reply. I'll look into changing my software to WW, I don't really need the JP version. I was actually unaware that you can change without unlocking, so thank you for that nugget of information.
Sent from my ASUS Pad TF300T

NVFlash does not work with the 9.4.5.30 and JB bootloaders

Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this

Completely agree. NVFlash for all.
paddycr said:
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Click to expand...
Click to collapse

+1

+1
There should be no lockdown code in the bootloader for "unlocked" devices.

I agree, they're surprisingly draconian about what "unlocked" means. We're not even covered under their warranty, might as well give us full access to our devices smh

Not to be the devil's advocate, but judging by some of what I read here, like folks asking some questions that make one wonder, "Is this guy really gonna try to flash his brand new $500 tab like that?"
I mean, and said person then does an RMA after he bricks it. That type of warrantee churn was probably something Asus did not anticipate. I can see how they'd want to slow that trainwreck down for awhile.
Sure, we were all n00bs at some point, but the frenzy of folks to get to JB and the way they go about it is probably getting a lot of folks in Asus support working overtime, lol!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

i
urrlyx said:
+1
get
There should be no lockdown code in the bootloader for "unlocked" devices.
Click to expand...
Click to collapse
:good: Yep. All or nothing. Don't void my warranty then partially cripple my ability to get my money's worth

Slammin said:
Not to be the devil's advocate, but judging by some of what I read here, like folks asking some questions that make one wonder, "Is this guy really gonna try to flash his brand new $500 tab like that?"
I mean, and said person then does an RMA after he bricks it. That type of warrantee churn was probably something Asus did not anticipate. I can see how they'd want to slow that trainwreck down for awhile.
Sure, we were all n00bs at some point, but the frenzy of folks to get to JB and the way they go about it is probably getting a lot of folks in Asus support working overtime, lol!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
of course nv flash would have saved all of those bricks from going back to asus.
they should be providing this tool rather then locking it down.

Hearing that the .30 bootloader is signed and won't allow flashing of unsigned bootloaders (downgrades included, since they are not signed) made me incredibly angry with ASUS. It's the wrong way to attack the problem. Even then, it's still possible to flash Jelly Bean to a TF700 in (IMHO) the most crazy of ways, by flashing the TF300 JB ROM. Even on locked devices!
There is this nvflash tool that makes it possible to recover from any brick known to man, and they just don't seem to want us to have access to it. I have unlocked my tablet to do exactly what I want with it, but even after I've voided my warranty, ASUS won't let me do it. Custom ROMs have a higher tendency to brick a device than a stock ROM, and people who've unlocked their devices should be tech-savvy enough to follow a tutorial to nvflash it back from the dead. Instead, ASUS wants them to enjoy their new shiny $500 paper weight/door stop.
ASUS, this was a **** move. The least you could do would be to provide a possibility to downgrade the bootloader (ie. a signed blob of an unsigned bootloader, for example the 9.4.5.26 one). Even better, you could actually unlock unlocked devices, or just give us nvflash for real.

The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
+1 on this, i also think that Asus will never provide a NvFlash tool for the tf700t,they have no interest to do it because they will loose repairs money. The previous Transformer devices got the same treatment so i don't see Asus acting different with the Infinity.

That's one of the great things about my old TF101 - it's NVFlash capable, so I can *always* recover from a bad flash or whatever. It's also a *very* "clean" way of installing a ROM - this way you absolutely know for a fact that you have a complete overwrite - no chance of something from a previous flash being "left over".
It's such a nice tool (NVFlash) - I *really* wish that it was available natively for the TF700... Lucky for me, I never updated to .30, so I can use NVFlash tool for the TF700 as well, but there are so many others that did update to .30 and they are now stuck. Very unfortunate...
By the way, what is the difference between native NVFlash and the "wheelie" version? I don't have any experience with the "non-native" (if that's a correct way of saying it) version of NvFlash/wheelie? If I recall correctly, it uses some "trickery" in order to use NVFlash - is that correct?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
That's one of the great things about my old TF101 - it's NVFlash capable, so I can *always* recover from a bad flash or whatever. It's also a *very* "clean" way of installing a ROM - this way you absolutely know for a fact that you have a complete overwrite - no chance of something from a previous flash being "left over".
It's such a nice tool (NVFlash) - I *really* wish that it was available natively for the TF700... Lucky for me, I never updated to .30, so I can use NVFlash tool for the TF700 as well, but there are so many others that did update to .30 and they are now stuck. Very unfortunate...
By the way, what is the difference between native NVFlash and the "wheelie" version? I don't have any experience with the "non-native" (if that's a correct way of saying it) version of NvFlash/wheelie? If I recall correctly, it uses some "trickery" in order to use NVFlash - is that correct?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Not sure if i understood what you meant with the "wheelie" version but afaik wheelie is used just for "bootstrap" (basically is used to bypass the lock that Asus used in order to prevent us from using NvFlash) in NvFlash mode, after that you will use "native" nvflash commands (wich are different based on the device u are using) , basically what Asus should provide to us from the start.

I'm probably not using the right terms... Using the TF101 as an example, the early TF101s (SBK V1) were able to use NVFlash directly, with no restrictions. Then, Asus being Asus, they modified the SBK (Secure Boot Key?) in the newer TF101's and NVFlash would no longer work on these SBK V2 devices. That's when one of the awesome developers released Wheelie - it allowed NVFlash to be used on the newer SKB V2 TF101's.
So, I think you already answered my question!
If I understand you correctly, Wheelie is just used to get around the SBK at which point NVFlash can be used normally?
Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

I could be wrong but i think that on the first tf101 batch nvflash was not ready "out of the box" but was possible only after the SBK leak. And that explain why Asus used SBK v2 on the next tf101 batch... Basically they never provided full APX/NvFlash access and i guess they never will.

jtrosky said:
The only reason that I can come up with is that Asus would want us send them the brick and charge us to un-brick it, which as has been stated is really not a good way to treat customers...
So let's see, give us a tool to unlock, which voids the warranty, and then make it impossible for us to recover from said brick... Hmm, sure sounds like a sure-fire way to make extra money!
Click to expand...
Click to collapse
Pretoriano80 said:
+1 on this, i also think that Asus will never provide a NvFlash tool for the tf700t,they have no interest to do it because they will loose repairs money. The previous Transformer devices got the same treatment so i don't see Asus acting different with the Infinity.
Click to expand...
Click to collapse
Lets face it, I think everyone was blindsided when .30 was released. Wasn't JB meant to be released next?? I am wondering whether the reason they have actually done this is to prevent flashing TF300 JB on the TF700. Has anyone on .30 actually been able to flash the TF300 firmware? I suspect that there were a few red faces when ASUS saw that the TF300 firmware could be flashed on locked TF700s. Also, that flashing this firmware caused TF700s to be stuck with the TF300 JB bootloader. .30 did repair the damaged TF700 bootloaders but has had the knock-on effect of not allowing us to not use NVFlash. This is not cool...
Hit the "Newsworthy Thread" thing at the top! Lets see if we can get the XDA news people to take a bit of interest in this and cause ASUS a little bit of shame This thread from the Prime forum seemed to get some attention from Tien once XDA made it public (see post 200): http://forum.xda-developers.com/showthread.php?t=1764917&page=20

paddycr said:
Like many of you who have updated to the 9.4.5.30 firmware, I was extremely disappointed to learn that we will not be able to use NVFlash. It appears that for whatever reason ASUS has decided to add some type of 'prevention code' to the 9.4.5.30 bootloader to prevent users from flashing the modified AndroidRoot.Mobi bootloader.
This is very unfortunate since as we all know, NVFlash is a powerful tool that allows all of those users with unlocked bootloaders to flash ROMs and not have to worry about the potential for bricking our devices. Thus, as things currently stand a large pool of current users as well as most future users will be excluded from using NVFlash. I would argue that it is probably in the interest of ASUS to undo whatever changes were made to the 9.4.5.30 bootloader, which would make it possible for us to once again flash the AndroidRoot.Mobi bootloader. The changes incorporated in 9.4.5.30 increase the likelihood that their customer service will have to deal with bricked units. Those of us who have owned the TF201 for example know of instances where bricked units get serviced under the warranty. This eats into their profits…
The purpose of this thread is to try and get ASUS's attention and alert them to the fact that there is a desire among the XDA TF700 community to use NVFlash and that the changes in 9.4.5.30 prevent this. However, the purpose of this thread is not to receive condescending lectures about the risks of unlocking - we are all aware . I would urge anyone who is also concerned about this to post in this thread. ASUS certainly seems to pay some sort of attention to XDA. Also, for those of us in the US we should also e-mail Tien about this issue. His user name is Asus_USA and his e-mail address is [email protected].
Thanks for taking the time to read this
Click to expand...
Click to collapse
+1

one more here.

Another here I was Awesomely Pleased when i have to Unbrick my Prime, but now that NVFlash is out on the Infinity I can't use it? Aww ASUS you Disappoint me..

This is a lost cause as they promised to be looking in to an official nvflash release for the transformer prime but as you can see it never came. The only access we had is when wheelie was released. This is why I cant support them with the way they are treating customers that are buying their tablets. At least with samsung products I have odin. You are just SOL with the asus now. As someone stated above, its like all they want to do is line their pockets. All they are doing is driving the customers away.
Also when yiu unlock your transformer tablet they delete the DRM Keys. Meaning any program relying on it like hulu or play movies will not work (netflix works I think).
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Understanding OTA functionality

Hi all!
Before I phrase my question I should inform that I have an ongoing issue with Asus regarding FOTA not working after Asus replaced my MB, and rear camera functionality. I'm on the TF300T, bought july 2012, completely stock, no root, no unlocked bootloader. I'm pretty much a newbie and do not wan't to lose warranty by doing things I don't understand .
As stated above, I have an ongoing issue with Asus; my MB and rear camera were replaced in connection with the third RMA (rear camera issue). The tablet I handed in had the ww 10.4.2.13 version. All updates from ICS have been performed via OTA and have worked flawlessly. When I got the tablet back, I discovered that it had the ww 10.4.2.9, which I experience as buggy and not very satisfying (in addition - the camera issue had not neen resolved). Fine, I'll just update OTA, I thought, but my tablet states that no update is available. I have tried this over a period of weeks now - no update is available. Actually, the tablet has been handed in to Asus Holland for a fourth RMA and they now claim that no errors exist.
So, what could be the explanation to the fact that I don't see any updates? My internet connection is working, all default settings after numerous factory resets and cold boots, no google account issues, other brand equipment in the household works fine. I know that replacing MB also means different MAC address. Unfortunately, I didn't write down the old MAC address so I can't really compare. Could MAC be the issue; meaning that maybe Asus failed to sync/pair the new MAC with serial# or other certain HW ids, and that there somehow needs to be a match between these?
I'd appreciate any input on the issue as I need to understand certain things before having further discussions with Asus.
Rgds,
sten_amund

It probably not your device since my 3 day old tf can't get ota update either. I am on the same kernel version and getting the same error message as you that no update exist. Which is false. So I went to Asus site and download the latest and manually installed it. Big difference in performance.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app