I have still not heard back from anybody and I've, of course, followed the directions. Quick posting of the updates online has really made this a much more minor problem than originally, but still . . .
Thank god I chose to RMA about a month and a half ago.
Still no fix? Why so stubborn, guys? Just RMA...they did overnight for me. If you moan and complain enough, they will cover shipping both ways. I had a replacement within 3 days with a S/N.
I doubt ASUS will ever release a fix for this. They will likely just sweep it under the carpet. After all, they have like 4 new models of TF coming through the pipeline very soon.
i was registering my device yesterday and it wouldnt recognize my serial number. i also noticed the serial number on my device and on the system settings didnt match with the one on the box. so when i tried to register it to get the gps dongle it wouldnt recognize my serial so i tried to contact asus thru the live chat option bt no one would connect to me. so i just left it there and when i tried to register it today it was already registered. asus must have done it automatically. anyone else have the issue with the serial numbers not matching up?
This is the first I heard of this!
Sorry ,i have this problem ,too
1.root
2.ratchet fix
3.unlook tool
4. Does Not function
Well it's been quite a voyage..
Got my TF201 returned from RMA yesterday, it works fabulous - let's work it with Unlock Tool.
Gives me unknown error. What could that mean? After some lurking I find my s/n is "unknown". What's that? Maybe it can't authenticate with the Asus servers? After more investigation I find various s/n unknown threads and stumble upon the Ratchet fix for this. Sure I thought.
But Ratchet required root, so first a downgrade (I used 9.4.2.15). Then hard wipe to clean the new firmware from previous garbage data.
Next use mempodroid to gain temporary root access and apply the s/n fix according to the guide.
Allright, serial number pops up in settings.
Let's try OTA and Unlock Tool to confirm success - none work.
Unlock Tool still displays "Unknown error. This may be a network connection issue. please wait and try again later.".
That seems like a short story. Well for documentation here's the howto to what was done:
- Settings - Applications - Manage - All - DMClient - Force Close/Clear Data/Clear Cache and then reboot. Next, go to Settings - About - Check for update.
- Soft factory reset - factory reset from within android settings.
- Hard reset - When device is off perform the following: "vol down+power button" -> "vol down button" -> "choose wipe by toggling with vol down button" -> "confirm by pressing vol up button twice"
- Manual downgrade - Use Method 2. Downgrades regardless of previous SKU (WW/US/TB etc.) and previous firmware version. Perform a hard reset to cleanup after flash. Enable "USB debugging" under "Developer options" in settings and get familiar with ADB to do this.
- Fix serial number with Ratchet - Chronologically I used the s/n restore guide here. Since the the TF201 is downgraded, the temporary root exploit described in the guide will work.
- root - (Optional) - It was attempted simply because it was possible at this stage, although futile if the next step is performed, even with OTA Rootkeeper.
(Choose (1) or (2))- (1)Manual update - make sure SKU of new firmware matches currently possessed SKU. Any root access after performing this step is gone.
- (2)Manual update and keep root without s/n - (Experimental) - Apparently some people have attempted to manually write the incremental OTA Updates to /cache/ partition and force update - thereby keeping root. However, even by reading the posts I cannot grasp how, and it was a heart-attack inducing experience. Not recommended.
I have tried the above with "US_epad-user-9.4.2.15" and "WW_epad-user-9.4.2.11" downgrades, upon which I upgraded them to their corresponding SKU (important).
Beginning the attempts with "WW_epad-user-9.4.2.21" I now rest on "US_epad-user-9.4.2.15".
Maybe this will work for somebody, it did not for me, but I am far from being bricked and await another RMA to resolve the issue. I am incredibly happy with Asus' support and what they do for the community. A sincere thank you to Gary Key who kindly forwarded me to some very knowledgeable people.
Hope this is of use to somebody!
That's not for an uber-newb as there seems to be a lot of pre-steps and things to download, e.g., and which appear to need other things loaded first.
I'm asking for a walk through for a literal no nothing whose first experience of android is the ATP--there's a lot of us on this site.
But if this kind of thing is beyond us--well, thanks for your efforts, but we'll have to wait.