You sure you're not reading that serial of the sticker next to the charge port on your DOCK?
You sure you're not reading that serial of the sticker next to the charge port on your DOCK?
I can't find one thread dedicated to finding out why we can't OTA or Unlock, or both. Hopefully somebody will be able to look at this list and figure out what's going on. Once we gather a significant amount of submissions, I'll be writing to Asus with this thread as reference. Please submit the following:
1. First 6 digits of your serial
2. OTA Update: Yes or No
3. Manual update: Yes or No
4. Firmware version: .21 .22 .26 etc.
5. Were you able to unlock: Yes or No
6. Root: Yes or No
If anybody thinks something else should be added to this list please let me know.
Mine:
1. C6OKAS
2. OTA - Unconfirmed, manually updated to .26
3. Manual update - Yes
4. Firmware : .26
5. Unlock: Yes
6. Root: Yes
UPDATE: Even with the limited number of responses so far there is already a pattern forming. It seems that if you can't OTA, you cant Unlock either. Sounds like an issue with Asus not communicating with our devices properly, as a few of you have guessed already. Please keep submitting so we can build a larger data pool.
UPDATE: As of 11:00pm PST, the unlock apk just worked. Been trying since the day it came out and tonight it just randomly worked. I urge all of you to check to see if it's working for you and please update with results.
Sent from my ASUS Transformer Pad TF700T
Anyone know what the difference is between C60KAS and C70KAS? At first I thought it was the difference between 32GB and 64GB but that doesn't seem to be the case. I'm wondering if there are any improvements on build quality. Like the clicking screen over the speaker or light bleed on the right and bottom right of the screen? Mine has both of these issues, although the clicking isn't as bad on mine, and my serial number is C60KAS. Any clue?
Refers to the date the device was manufactured. C6 is June, C7 is July. Pretty soon we'll start seeing C8 August.
I got my Infinity last night . After getting it out of the box the .26 and dock updates appeared almost instantly after entering my network and Google passwords. Actually, I was really surprised how quickly they were there (my connection is not that quick!). This is probably a really dumb question but were these actual OTAs downloaded from the ASUS server or is there a chance that the updates could have been put on the sdcard and installed when the tablet was first fired up?? Did everyone receive their updates so quickly?
1. C7OKAS
2. OTA - maybe (see above)
3. Manual update - No
4. Firmware : .26
5. Unlock: Not yet - waiting to see if I have a good 'un!
6. Root: Yes
The update process actually sends only the IMEI to ASUS servers, not the S/N, so unless they do another check on their side, it is even more irrelevant in this case.
When I said sdcard I meant /sdcard, which I am sure you know is the internal memory not /Removable/MicroSD, which is the address for an external sdcard. Confusing eh?
True, that is a stupid naming probably resulting in an attempt of being compatible.
Still, it was easy to assume you though it was the other one.
This kind of attack may be possible, but asus's servers only communicate the unlock information once. You would have to capture those communications and make a modified unlocker. Whether it works depends on how the bootloader code verifies the unlock information, and how much of the unlockable tablets information can be spoofed onto the un-unlockable tablet.
Download the firmware for your tablet here:http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download1. C7OKAS
2. OTA - No
3. Manual update - Haven't tried
4. Firmware : .21 (trying to find out how to manually update.)
5. Unlock: Haven't tried. (Won't until there is something out there worth voiding the warranty.)
6. Root: Yes
Sent from my Transformer Infinity!
I was womdering if those errors had anything to do with it.
This kind of attack may be possible, but asus's servers only communicate the unlock information once. You would have to capture those communications and make a modified unlocker. Whether it works depends on how the bootloader code verifies the unlock information, and how much of the unlockable tablets information can be spoofed onto the un-unlockable tablet.Has anyone tried copying the serial from a successfully unlocked device to one that does not successfully unlock with its original serial number?