yashsingh1/xdaforums huggingface dataset:
[Asus Transformer TF700] kokopuphz:
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...
[Asus Transformer TF700] armanisafarai:
stupid idea, but can't we all go to their facebook page and spam them like hell? I mean HTC gave in with their unlock tool because of so many people raging in facebook. Worth a shot?
[Asus Transformer TF700] Schrotty35:
1. C6OKAS

2. OTA - No

3. Manual update - Yes from .21 to .26

4. Firmware : .26 (shipped with .21)

5. Unlock: No

6. Root: Yes

7: Size: 64GB
[Asus Transformer TF700] 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
[Asus Transformer TF700] rightonred:
Just force downgraded to .22 and checked for update.

Confirm OTA is working.:victory:

*gets up and starts dancing (badly)*
[Asus Transformer TF700] californiarailroader:
1.C7OKAS

2.No

3.Yes

4. .26

5.No

6.Yes

Edit-I just tried the Unlock a few minutes ago (11:30 PDT), and it finally WORKED, yay!!! I have been trying for days to get it to work, Asus must have fixed something.
[Asus Transformer TF700] tha_kreature:
You're welcome :)

If I'd had root I'd do it myself though.

Looks like we have multiple addresses:

wvdrm.asus.com

drm.asus.com

We should have following regions: WW, TW, CN and JP.

So why wv infront of drm ?

Try going to https://wvdrm.asus.com and you will see it behaves differently.

In fact, I get a "OK" in the browser and no cert warning as it uses a cert issued to *.asus.com by verisign.

I think we are on the right track as to why OTA and such doesn't work, there has definately been server/certificate issues.

Maby now Asus will fix it ?
[Asus Transformer TF700] guthrien:
So it's working for others that were locked out before? Well hell yea.
[Asus Transformer TF700] Schrotty35:
Unlock working now, yeahhhh.
[Asus Transformer TF700] californiarailroader:
On a similar note, I finally got Asus Device Tracker to work tonight too, though I had to log in with my Google Info, using my Asus Account still fails.
[Asus Transformer TF700] gmfeny:
OTA now working!!!
[Asus Transformer TF700] Abalos65:
It seems that Asus fixed the problem :D
[Asus Transformer TF700] okantomi:
1. C7OKAS

2. OTA--yes

3. manual update--n/a

4. firmware version--26

5. unlock--not yet

6. root--not yet

7. 32GB (amethyst)
[Asus Transformer TF700] Skullmonkey:
Woke up to an update notification. Finally.
[Asus Transformer TF700] Bee's Buzz:
Same for me: finally updated today!

1. C6OKAS

2. OTA: Yes

3. Manual update: no need

4. Firmware: .26 (shipped with .22)

5. Unlock: Haven't tried.

6. Root: Yes

7. 32GB

Depending of your device, you have to wait up to 3 weeks after the FOTA has been released to "see" it (info from ASUS)!
[Asus Transformer TF700] armanisafarai:
HELL YES! C70KAS now working. Thanks Asus!
[Asus Transformer TF700] RubyRhod62:
OTA and unlocking bootloader is finally running fine :)
[Asus Transformer TF700] tha_kreature:
You sure you're not reading that serial of the sticker next to the charge port on your DOCK?
[Asus Transformer TF700] rbrmfld:
Mine still remains unable to receive the updates.

It said there was an update, and it failed. When I try to see if there are anymore updates, it says that there aren't any. I'm still stuck on .21 also.
[Asus Transformer TF700] polish_pat:
1. C7OKAS

2. OTA - No

3. Manual update - Yes

4. Firmware : .26

5. Unlock: No

6. Root: Yes
[Asus Transformer TF700] armanisafarai:
Yeah i'm sure. The sticker is right next to the 40 pin charger.
[Asus Transformer TF700] Blueback22:
1. C6OKAS

2. OTA - no, manually updated to .26

3. Manual update - Yes

4. Firmware : .26

5. Unlock: unknown

6. Root: Yes
[Asus Transformer TF700] alienedd:
1. C6OKAS

2. OTA--no

3. manual update--n/a

4. firmware version--21

5. unlock--finally, Aug 7 12

6. root--yes

7. 32GB (GR)

Couldn't OTA but finally got unlock. Strange, but I'm glad it was an "ASUS-side" issue and I was able to sever that umbilical on the quick fast!
[Asus Transformer TF700] BeverageNinja:
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?
[Asus Transformer TF700] Jotokun:
Refers to the date the device was manufactured. C6 is June, C7 is July. Pretty soon we'll start seeing C8 August.
[Asus Transformer TF700] bckldwn:
1. C7OKAS

2. OTA - No

3. Manual update - Yes

4. Firmware : .26

5. Unlock: No

6. Root: Yes
[Asus Transformer TF700] tha_kreature:
My Tablet was C6 and my dock is C7. They both arrived from import and was delivered to me within days of availability.

I guess it appears month-based yes.
[Asus Transformer TF700] Thats OK:
I see nothing from ASUS

1. C7OKAS

2. OTA - manually updated to .26 within hours of receiving the tab.

3. Manual update - Yes

4. Firmware : .26

5. Unlock: No (scared to do it)

6. Root: No (afraid to do it)
[Asus Transformer TF700] paddycr:
I got my Infinity last night :D. 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
[Asus Transformer TF700] d14b0ll0s:
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.
[Asus Transformer TF700] tha_kreature:
There is no sdcard with the tablet. You have to buy one.

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

The non 3G/LTE tablets do not have an IMEI.
[Asus Transformer TF700] paddycr:
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?
[Asus Transformer TF700] tha_kreature:
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.
[Asus Transformer TF700] paddycr:
Thank you very much for taking the time to address my question. My sincere apologies for any ambiguity in my earlier post :rolleyes:
[Asus Transformer TF700] bckldwn:
anyone else have C7OKAS (.26) and still can't unlock? I'm getting "an unknown error has occured, might be network connection issue, please try again later.".. something along those lines.

any ideas?
[Asus Transformer TF700] simplytheone:
1. C7OKAS

2. OTA Update: No

3. Manual update: Yes

4. Firmware version: .26

5. Were you able to unlock: No

6. Root: Yes
[Asus Transformer TF700] Jokun:
1. D1OKAS

2. OTA Update: No

3. Manual update: Yes

4. Firmware version: .25

5. Were you able to unlock: No

6. Root: Yes
[Asus Transformer TF700] DarkFire1985:
1. C60KAS

2. OTA Update: Yes

3. Manual update: Yes

4. Firmware version: .25

5. Are you able to unlock: No, wrong MAC-address

6. Root: No, can't downgrade from .25

Typo: must be .25 of course instead of the .30
[Asus Transformer TF700] MartyHulskemper:
^^ This is interesting...
[Asus Transformer TF700] DarkFire1985:
Well I presume the OTA is working, haven't received one yet after my last RMA but it worked in the past even though the unlocking wasn't working.

I also presume my unlock isn't working because of the wrong MAC-address in comparison with the ASUS Backend servers. ASUS Germany is trying to get Taiwan to fix my MAC-address, 2 RMA actions didn't help.

Anyway more frustrating than interesting if you ask me :)
[Asus Transformer TF700] MartyHulskemper:
I am sorry if I offended you with my first reply -- that was surely, certainly and absolutely positively not my intention. It's just very strange that unlocking *doesn't work* while receving an OTA update (which ALSO requires a device-specific number to be present in ASUS' databases) *does*. Ugh multi-factorial, multilevel screwup, LOL. This does reaffirm that -- with ASUS as with pretty much every other large, 'optimized' (and global) company -- you just need to be lucky to avoid the imcompetent "customer care" department in order to have a good user experience. Once you devce fails, you run a large chance to be screwed over. ;)
[Asus Transformer TF700] DarkFire1985:
Don't worry, I wasn't offended ;)

There are success reports of Taiwan getting the MAC-address changed, I'm crossing my fingers that the German boys succeed in communicating with them.
[Asus Transformer TF700] Jokun:
Hi there.

I´m right in the middle of that process as well - German support trying to get Taiwan HQ to fix the problem. Haven´t heard from them in over a week now. So they did indeed fix the issue for some users? That´s a glimmer of hope, then. Could you kindly point me to some of the success reports you´ve been mentioning?
[Asus Transformer TF700] DarkFire1985:
I haven't heard anything yet either and I will ask for an update after a few more days.

I think that's what you should do as well, ask for an update.

For the succes reports check the following 2 topics:

http://xdaforums.com/showthread.php?t=2146543

http://xdaforums.com/showthread.php?t=1795156
[Asus Transformer TF700] jcmarcanot:
studying the unlock_v8.apk code

I have being studing the code of this apk, and everything what you explain is true, also I try to study the DMClient.apk, but I don't fine any code inside. The unlock_v8.apk send a Context.sendBroadCast to DMClient with this information:

d="0";
Intent intent = new Intent();
intent.setClassName("com.asus.dm", "com.asus.dm.c2dm.C2DMReceiver");
intent.setAction("com.asus.unlock.intent.REGISTRATION");
intent.putExtra("registration_cpu_id", getID());
mContext.sendBroadcast(intent);
Log.d("NotifyDMServer", "Notify DM Client Successfully");

but I opened the DMClient.apk and in the manifest file there isn't a "com.asus.unlock.intent.REGISTRATION".

I hope this information help.
[Verizon Droid Incredible 2] geekcentercreations:
I pulled my phone out of my pocket it and saw that it was on the HTC boot screen. It stayed like the for a while so i shut it down using Power, Volume UP&Down.

I tried to boot again but was freezing at the HTC boot screen.

I booted into recovery and it said it couldnt load /cach/x (command and log and last_log)

Ive tried everything from flashing RUU to new HBOOTS, nothing is working.

Now my laptop keeps saying a USB port is malfunctioning everytime i plug the phone in.

Im two seconds away from smashing this with a sledgehammer.

I was running Aeroevan's Unofficial CM10 Jelly Bean With the v12 Kernel w/ Video Drivers.
[Verizon Droid Incredible 2] jamminjon82:
Have you tried the pg32img in bootloader?
[Verizon Droid Incredible 2] geekcentercreations:
Yes, when i go to install it, it does a few things.

It p****s the zip

bypasses the bootload

and freezes at boot saying updating and at the bottom is says can not roll back hboot version.

Its been at this screen for about 45 minutes THIS TIME
[Verizon Droid Incredible 2] dirtsky:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..

EDIT: Here you go. Follow everything to the T.

http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
[Verizon Droid Incredible 2] geekcentercreations:
The only issue now is I only have FastBoot Support but no ADB support. I have no idea why but my phone only shows up under fastboot devices and not adb devices. so i have no idea how to use that guide
[Verizon Droid Incredible 2] hkleiner:
The Inc 2 ports often go bad. Try wiggling and plugging it in not all the way. Also sometimes had to push on the cable and hold for it to recognize the USB.

________________________________

Easy as 3.1415926536
[Verizon Droid Incredible 2] sjpritch25:
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
[Verizon Droid Incredible 2] CondemnedSoul:
I did?? :eek:

Sent from Kangdemnation
[Verizon Droid Incredible 2] sjpritch25:
What happens when you type

adb devices?

what about fastboot devices.

If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
[Verizon Droid Incredible 2] geekcentercreations:
When i type in Fastboot device my phone shows up, but when i type in adb devices it doesnt. i set up the android sdk and assorted tools the way i always have because i use them for development in eclipse, but ive never had a problem with adb before.
[Verizon Droid Incredible 2] sjpritch25:
this is what it should look like.
[Verizon Droid Incredible 2] Triscuit:
Lol I think he had just looked at your contact picture. They look very similar at a glance
[Verizon Droid Incredible 2] CondemnedSoul:
If your phone isn't booting past HTC screen it won't usually show up as an adb device.

Are you s-off?

Have you tried the return to stock that I posted?

http://xdaforums.com/showthread.php?t=1599767

This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully :o
[Verizon Droid Incredible 2] geekcentercreations:
Everything i try keeps freezing in the bootloader screen when i go to install any RUU or image file or zip including that PG32IMG thing or whatever.

My phone recognizes it in fastboot but not adb.

I am S-Off. I rooted the phone the day i got it 6 months ago and have flashed a new rom weekly. never had a problem like this before.
[Verizon Droid Incredible 2] geekcentercreations:
The download links in this do not work or else id try that too.
[Verizon Droid Incredible 2] flydoug9:
Try it

Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
[Verizon Droid Incredible 2] geekcentercreations:
Yes i would try this except ClockWorkMod isnt working when i attempt to boot into it. It starts to load then freezes.
[Verizon Droid Incredible 2] TheValk:
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
[Verizon Droid Incredible 2] geekcentercreations:
Yeah i've been trying everything. When i install any RUU or anything it keeps getting hung up at recovery and i tried flashing that seperately and that isnt doing anything.
[Verizon Droid Incredible 2] ninjasailas:
Have you tried doing anything in fast boot like wiping data and cache?
[Verizon Droid Incredible 2] andybones:
if your phone still turns on, it isn't bricked..
[Verizon Droid Incredible 2] hudsong:
Are both people with this problem running Aeroevan's CM10 w/ v12 kernel? If so, a big warning for that ROM is in order...
[Verizon Droid Incredible 2] Tortuga:
It sounds to me like a hardware issue. I'd be curious to know specifics on exactly what roms and mods were installed on each phone experiencing the issue. I highly doubt it's related to the unofficial CM10 rom or the v12 kernel, based on the large numbers of folks using them currently. But without knowing the circumstances all we can do is guess.
[Verizon Droid Incredible 2] Nephilim:
Highly doubtful it's related to aero's CM10 or v12, aero is among the top developers for this phone and I've been using his roms and kernels since he's been posting here on the Inc2 section of XDA, More recently I've used every one of his CM10 builds with no issue, this goes the same for his kernels, the only kernel I did not use was the v11 because it did not support undervolting. Now if this issue were persistant among the majority I would think it's worth considering but 2 out of the probably hundereds of people using this rom is really not something for anyone to become concerned about.
[Verizon Droid Incredible 2] fenduru:
When you say you have it set up the way you always have, does that mean that you have previously used ADB on this specific setup (read: not the "same" setup on a different machine)?

What OS are you using, and is your ~/.android/adb_usb.ini setup appropriately for the device. I always forget to do this when I (rather often) try to use adb on a different machine or different Linux install.
[Verizon Droid Incredible 2] The Archangel:
An welcome to the Q&A section. This is where the post should of been posted
[Verizon Droid Incredible 2] AJGO23:
I wondered why it took so long. ;):D
[Verizon Droid Incredible 2] geekcentercreations:
Whenever I try and install anything via FastBoot such as a RUU or some method to return to stock it freezes when trying to update recovery. I tried taking the recovery file out of one RUU i attempted to flash but it still froze trying to update recovery. I can no longer boot into clockwork recovery via the bootloader and this is my only phone. Like i stated in the OP, i pulled my phone out of my pocket and it was on the HTC white boot screen. Ive flashed about 20 different ROMs and builds on this device never without a problem BUT i have never had to use adb or fastboot before this incident. I do however know how to use them and they are set up correctly.

I just need my phone working again.
[Verizon Droid Incredible 2] woohhaa:
This is so bizzare because I'm also having a similar problem. Started Friday night. I've been searching for answers ever since. I posted this on phandroid's forum.

Last week my rooted incedible 2 running the below ROM started giving me problems when installing google+. I pulled the battery, as it became unresponsive, and once it booted back up it would quickly become unresponsive again. I finally booted into clockworkmodrecovery v5.0.2.0 and tried installing various new ROMs with no success. Every time I get a errors similar to below. It happens with every ROM I try.

I'm not really sure what's going on here but I suspect I have have some corrupt memory. Any advise would be much appreciated.

ROM Prior to issues:

RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_signed. zip

Messages during install of ROMs:

Installing: /sdcard/com-7.2.0-vivow.zip

Finding update package...

Opening update package...

Installing update...

E:Error in /sdcard/rcm-7.2.0-vivow.zip

(Status 1)

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log
[Verizon Droid Incredible 2] The Archangel:
Sounds like a emmc failure
[Verizon Droid Incredible 2] jellybellys:
Just for future reference, adb cannot be used in the bootloader.

And if you are having trouble finding an RUU, I have all the signed RUUs right here. >> http://rootzwiki.com/topic/18873-ruu-htc-incredible-2-signed-ruus-pg32imgzip/

---------- Post added at 10:47 PM ---------- Previous post was at 10:44 PM ----------

That does sound like emmc failure. You should take a look at this thread before giving up.

http://xdaforums.com/showthread.php?t=1284196