No OTA or Unlock list. Please submit.
- Thread starter megadirk
- Start date
Great! That narrows it down!
Someone with a rooted tabled could possibly find the certificate that is being used.
CACert is an app that requires a rooted tablet and should do it I think?
Need both someone with OTA working and someone without to compare their certs I guess.
Can anybody confirm this being a possible avenue to head down? I'm at work now so I can't contribute till later.
Sent from my ASUS Transformer Pad TF700T
1. C60KAS
2. OTA Update: No
3. Manual update: Yes
4. Firmware version: .26
5. Were you able to unlock: No
6. Root: Yes
Here's an extra one:
7. 16gb or 64gb: 16gb
This is just speculation on my part but when I had the TF300, I initially bought the 16gb and was not able to unlock or get OTA, I then exchanged it the next day for the 32gb and was able to do both OTA and unlock.
There is another forum member who purchased the TF700 32gb and was not able to do the OTA or unlock but exchanged for the 64gb and was able to do both. I'm just adding more fuel to the fire I guess...
2. OTA Update: No
3. Manual update: Yes
4. Firmware version: .26
5. Were you able to unlock: No
6. Root: Yes
Here's an extra one:
7. 16gb or 64gb: 16gb
This is just speculation on my part but when I had the TF300, I initially bought the 16gb and was not able to unlock or get OTA, I then exchanged it the next day for the 32gb and was able to do both OTA and unlock.
There is another forum member who purchased the TF700 32gb and was not able to do the OTA or unlock but exchanged for the 64gb and was able to do both. I'm just adding more fuel to the fire I guess...
1. C6OKAS
2. OTA - No
3. Manual update - Yes
4. Firmware : .26
5. Unlock: No
6. Root: Yes
7. 64GB
****ing pissed. I have had it for a week and i didn't unlock until everythig was working properly. Now that everything works i tried to unlock, and boom not working. Getting network error message in unlock app. the worst thing is the store i bought it from has nothing in stock atm. Should i return or wait and see if asus will update unlock app? I got 7 more days to return.
2. OTA - No
3. Manual update - Yes
4. Firmware : .26
5. Unlock: No
6. Root: Yes
7. 64GB
****ing pissed. I have had it for a week and i didn't unlock until everythig was working properly. Now that everything works i tried to unlock, and boom not working. Getting network error message in unlock app. the worst thing is the store i bought it from has nothing in stock atm. Should i return or wait and see if asus will update unlock app? I got 7 more days to return.
Last edited:
1. C6OKAS
2. OTA - No
3. Manual update - Yes
4. Firmware : .26
5. Unlock: No
6. Root: Yes
7. 32GB (amethyst)
(literally copied it from your first post, It all still applies to mine)
I doubt the sn means anything, although I don't think anyone with a c7 sn can ota or unlock. (feel free to prove me wrong). I also doubt root makes a difference. I tried updating mine without root, and still no luck. Considering this is XDA and most people who are posting here have tried using the unlock tool with the intent of hacking their device, would explain why almost everyone here is rooted. I dont think there's a coherent pattern other than otas and unlocks do not work at the same time.
I highly believe this is a database error on asus's end, and there's nothing we can do but wait for asus to fix it.
2. OTA - No
3. Manual update - Yes
4. Firmware : .26
5. Unlock: No
6. Root: Yes
7. 32GB (amethyst)
(literally copied it from your first post, It all still applies to mine)
I doubt the sn means anything, although I don't think anyone with a c7 sn can ota or unlock. (feel free to prove me wrong). I also doubt root makes a difference. I tried updating mine without root, and still no luck. Considering this is XDA and most people who are posting here have tried using the unlock tool with the intent of hacking their device, would explain why almost everyone here is rooted. I dont think there's a coherent pattern other than otas and unlocks do not work at the same time.
I highly believe this is a database error on asus's end, and there's nothing we can do but wait for asus to fix it.
I'm guessing you meant 32gb and not 16gb for option 7? If not, then you have the worst factory defect of us all
Lol oops...yes I have 32gb.
I can't get OTA and likely not unlock. I at least partially know why now, I pulled my logcat and there are multiple rejections from wdrm. Asus. Com and checks which say unauthorized user. So my brand new tablet basically is not going to updat/unlock because their brilliant drm is broken. Awesome engineering.
Sent from my Nexus 7
Sent from my Nexus 7
Can someone who can unlock or OTA take a logcat, apply the filter: "keybox", and post it. You can do this using the aLogcat app. (no root needed)
Here's mine.
Here's mine.
Code:
I/ActivityManager( 219): Start proc com.asus.wvdrm for broadcast com.asus.wvdrm/.KeyBoxReceiver: pid=1595 uid=1000 gids={3003, 1015, 3002, 3001, 3007}
D/KeyBoxReceiver( 1595): === Connectivity.CONNECTED ===
D/KeyBoxService( 1595): === onCreate()
D/KeyBoxService( 1595): === onStartCommand(), intent=Intent { cmp=com.asus.wvdrm/.KeyBoxService }, flags=2, startId=1
D/KeyBoxService( 1595): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 1595): === OTA BEGIN
E/KeyBoxService( 1595): === Connection to [url]http://wvdrm.asus.com[/url] refused
D/KeyBoxService( 1595): === Retry after 60 seconds.
D/KeyBoxService( 1595): === OTA END
D/KeyBoxReceiver( 1595): === Connectivity.CONNECTED ===
D/KeyBoxService( 1595): === onStartCommand(), intent=Intent { cmp=com.asus.wvdrm/.KeyBoxService }, flags=2, startId=2
D/KeyBoxService( 1595): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 1595): === OTA BEGIN
E/KeyBoxService( 1595): === Connection to [url]http://wvdrm.asus.com[/url] refused
D/KeyBoxService( 1595): === Retry after 300 seconds.
D/KeyBoxService( 1595): === OTA END
D/KeyBoxService( 1595): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 1595): === OTA BEGIN
E/KeyBoxService( 1595): === Connection to [url]http://wvdrm.asus.com[/url] refused
D/KeyBoxService( 1595): === Retry after 600 seconds.
D/KeyBoxService( 1595): === OTA END
D/KeyBoxService( 1595): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 1595): === OTA BEGIN
E/KeyBoxService( 1595): === Connection to [url]http://wvdrm.asus.com[/url] refused
D/KeyBoxService( 1595): === Retry after 1200 seconds.
D/KeyBoxService( 1595): === OTA ENDThis is the first bit of headway I've seen anybody make on this. Please somebody with an OTA or Unlock do this so we can compare.
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!
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!
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
5
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...2
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.
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.
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.1Rumor 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 app11. C7OKAS
2. OTA Update: No
3. Manual update: Yes
4. Firmware version: .26
5. Were you able to unlock: No
6. Root: Yes
