No OTA or Unlock list. Please submit.

Search This thread
By:
Advanced…
megadirk

megadirk

Member
Jul 21, 2012
38
3
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.

Last Update 8/8/12: It seems that a good amount of us are now able to OTA and Unlock. Whatever the issue was it looks like ASUS fixed it.
Sent from my ASUS Transformer Pad TF700T
 
Last edited:
F

flyingreasemonkey

Member
Jul 9, 2011
15
2
From what I have found it is a problem with the asus database.

Sn C6OKAS
OTA no
Manual yes .26
Unlock no
Root yes

Sent from my ASUS Transformer Pad TF700T using xda app-developers app
 
Last edited:
  • Like
Reactions: megadirk
ftmaniac948

ftmaniac948

Senior Member
Aug 28, 2011
368
114
Have you guys tried manually pushing the firmware to your tablet and updating it that way?

Sent from my Galaxy Nexus using xda premium
 
G

gienod

Member
Mar 26, 2012
10
2
I also cant unlock the bootloader :( . Needed to manually update my tablet from .21 to .26
Rooting was no problem.

Will this ever get fixed or should I RMA my tablet??
 
jaxboater

jaxboater

Senior Member
Dec 15, 2007
265
22
Fl.
1. C7OKAS
2. OTA Update: No
3. Manual update: Yes
4. Firmware version: .26
5. Were you able to unlock: No
6. Root: Yes

---------- Post added at 03:33 AM ---------- Previous post was at 03:31 AM ----------
flyingreasemonkey said:
Rumor is that it may be fixed. But that all rests on how asus is going to handle the problem.

Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse

I've done a quick search of the other sites and a Google search & haven't found anything new or useful.

Where'd you get this rumor?
 
  • Like
Reactions: megadirk
N

neo1738

Senior Member
Nov 24, 2010
369
50
1. C7OKAS
2. OTA Update: No
3. Manual update: Yes
4. Firmware version: .26
5. Were you able to unlock: No
6. Root: Haven't tried do it later
EDIT: Rooted just on first attempt using debug method.
 
Last edited:
  • Like
Reactions: megadirk
B

bubbadk

Member
Jun 30, 2008
18
2
1. C6OKAS
2. OTA Update: No
3. Manual update: Yes
4. Firmware version: .26
5. Were you able to unlock: No
6. Root: Yes

And its annoyingly slow at times :(
 
  • Like
Reactions: megadirk
J

Jotokun

Senior Member
Apr 23, 2011
785
228
I've since returned this infinity due to the wifi dying, but it was unable to unlock so might as well post it.

1. C6OKAS
2. OTA - No
3. Manual update - Yes
4. Firmware : .26 (shipped with .21)
5. Unlock: No
6. Root: Yes
 
  • Like
Reactions: megadirk
T

tha_kreature

Senior Member
Jul 5, 2012
168
51
1. C6OKAS
2. OTA Update: Yes
3. Manual update: no need
4. Firmware version: .26
5. Were you able to unlock: not wanted to yet
6. Root: not bothered yet

I did do a little sniffing on the network though.
When I ask it to check for updates it does a SSL connection to mdm.asus.com (even multiple ones it seems) and the site uses a certificate that appears to be validated by something stored on the devices. If you go to https://mdm.asus.com it will say there is a problem with the certificate, but if you continue anyway you get a testsite and it sais "It works !". If not, you won't be able to OTA either as the tablet can't phone home...

So, to you that can't access any OTA or unlock, try opening the url and see.
 
  • Like
Reactions: Jotokun
T

tateg

Senior Member
Mar 4, 2011
78
5
It works for me but I can't unlock or ota

Sent from my ADR6425LVW using xda premium
 
You must log in or register to reply here.

Similar threads

rickymh19
ASUS TF700T unlock and root JB 4.2.1 stock
Replies
599
Views
325K
yongyek
yongyek
d14b0ll0s
[LIST] Best (and worst) apps for the TF700
Replies
355
Views
189K
Y
yozotheboss
sbdags
  • Locked
[ROM]★★[TF700 KitKat 4.4.4r2][CROMBi-kk R1][Sep 21]★★
Replies
2K
Views
556K
sbdags
sbdags
zeus34
[Device is unlocked][Video Added] Bootloader Unlock Tool Released [25.7.2012]
Replies
484
Views
197K
G
Gopar2292
KilerG
[LIST] Best Games for the TF700
Replies
300
Views
102K
greydelta38
greydelta38

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 5
    kokopuphz
    kokopuphz
    rightonred said:
    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.
    Click to expand...
    Click to collapse

    Here are my findings in regards to the unlock tool, for TF201 however probably applies to TF700 as well.

    The Unlock tool app itself has these basic functions.
    1. Install certificate that is included in the BKS keystore file.
    2. DMServerUnlock. Connect to https://mdm.asus.com/DmServer/DeviceState using SSL connection, using the following parameters:
    --a. id=Wifi MAC address with columns removed
    --b. AUTH=an MD5 hashed string with some modification. The string itself consists of Wifi MAC + SerialNo + WVDrmUtils.getKeyBoxSha1(0) + the string "dm_server" + the string "nEEd_query_STATe"
    ----i. the getKeyBoxSha1 is probably DRM related information specific to the device. ---not confirmed as this seems to be native commands.
    --c. action=get
    3. The above connection will return whether your device is already unlocked or not from ASUS servers.
    4. If your device is still shown as locked, then it will proceed with determining whether a pin code verification or google account verification is necessary.
    5. Upon above verification, then the actual unlock process starts.
    6. NotifyDMServer - throws an android intent to the DMClient.apk program using the following: Action=com.asus.unlock.intent.REGISTRATION, Extra:registration_cpu_id = YourCpuId
    --a. YourCpuId is parsed from /sys/devices/platform/cardhu_misc/cardhu_chipid
    7. ---DMClient logic yet to be analyzed---
    8. The DMClient will return a two part string separated by ";;".
    --a. The first part is the unlock status. On success, this will be "unlock success"
    --b. The second part is the "SecretCpuId" which according to Rayman is simply your cpuid + 256byte length ASUS RSA 2048 signature as a hex string. The total byte length of the unhexed string needs to be 292.
    9. If unlock success and length is 292, then:
    --a. "boot-unlock recovery" is written to mmcblk0p3 (misc partition)
    --b. the "SecretCpuId" is written to mmcblk0p4 (staging partition)
    10. A reboot is issued.
    11. upon reboot, the bootloader checks the MISC partition for any commands, finds the "boot-unlock" command.
    --a. writes the contents ofmmcblk0p4 into mmcblk0p7 (CER partition)
    --b. bootloader will check the mmcblk0p7 contents, see if it is properly signed by ASUS, and if the cpuid matches, then:
    ----i. allow fastboot access
    ----ii. stop checking signature of blobs (not the header part, but the ASUS RSA signature at the end of BLOB files)
    ----iii. stop checking for signatures of boot images in SOS (recovery) and LNX(boot) partitions.

    So basically, most of the logic within the unlock tool can be skipped. Acquiring the actual signed cpuid takes place within DMClient, I believe we need to analyze DMClient to see what parameters are being passed to the ASUS servers. Once this is done, we can do the following:
    - figure out if any of the parameters are incorrect or not being parsed successfully.
    - figure whether it is an issue with the proper SSL certificate being installed within the tablet itself.
    - if above two are not the issue, then its most likely the ASUS server does not have the correct combination of parameters for our devices defined within their databases...
    View
    2
    megadirk
    megadirk
    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 its working for you and please update with results.

    Sent from my ASUS Transformer Pad TF700T
    View
    2
    R
    rightonred
    Skullmonkey said:
    1. 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!
    Click to expand...
    Click to collapse
    Download the firmware for your tablet here:http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
    extract it (it should be another zipfile) to the root of your internal momory.
    Reboot the tablet. The next time it boots, you'll get a firmware update notification, tap on it.
    armanisafarai said:
    @rightonred getting exactly same log as you, (Not unlocked)
    Click to expand...
    Click to collapse
    I was womdering if those errors had anything to do with it.
    We need the logcat of someone who hasn't unlocked and can OTA to see if there are any differences.
    So far what I gather is wvdrm.asus.com is an ssl (https) secured site that refuses unsecured (http) connections, and the tablet is trying to make an unsecured connection to that site. I tried connecting using sslstrip and that error message went away, but I got a network error when trying to update. I have yet to try using sslstrip and bypassing it for mdm.asus.com.
    eousphoros said:
    Has anyone tried copying the serial from a successfully unlocked device to one that does not successfully unlock with its original serial number?
    Click to expand...
    Click to collapse
    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.

    EDIT: I really wish these tablets would unlock like the nexuses, this would have been avoided. ASUS is being overly cautious, verifying the tablets before they update, registering the unlocks and making them permanent, and it has backfired.
    View
    1
    F
    flyingreasemonkey
    Rumor is that it may be fixed. But that all rests on how asus is going to handle the problem.

    Sent from my ASUS Transformer Pad TF700T using xda app-developers app
    View
    1
    RubyRhod62
    RubyRhod62
    1. C7OKAS
    2. OTA Update: No
    3. Manual update: Yes
    4. Firmware version: .26
    5. Were you able to unlock: No
    6. Root: Yes
    View

New posts