POLL: Unable to unlock your prime? POTENTIAL FIX! Mine is unlocked!

How was your unlocking experience using Asus' unlock tool?

  • Unlocked with no issues whatsoever.

    Votes: 151 29.0%
  • Unlocked after factory reset.

    Votes: 12 2.3%
  • Unlocked after downgrading to older version.

    Votes: 3 0.6%
  • Unlocked EVEN after an RMA.

    Votes: 7 1.3%
  • Unable to unlock due to "unknown error".

    Votes: 347 66.7%

  • Total voters
    520
Search This thread

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
I had .28 rooted and was able to do the unlock no problem. I had to download the app from a dropbox account as I was unable to download from ASUS's website.

I would like to have the same luck than you. I downloaded it direct from eAsus. I bought this tab knowing in can unlock it. But seems impossible for me right now. As Asus don't show any concern about it... Maybe I'll try one day to downgrade for see if reverting to .21 or .15 change it. But I just factory reset and re-flash manually my tab and put everything back on the infernal memory. 4 hours for 6 gb, don't want to do it again soon ^^

My first and last Asus product for sure.

Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
 

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
The issue seems to be related to RMAs. I bought mine 2nd hand from a guy who got it from his boss, so theres no way of knowing if it was ever returned. It doesnt seem to matter on which firmware you are or if you are rooted or not.... All we (probably) have in common is the RMA factor. At least thats progress! :D

My tab never went in RMA, so it have nothing to do with it.

Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
 

nhshah7

Senior Member
Feb 14, 2009
2,068
568
Boston
My tab never went in RMA, so it have nothing to do with it.

Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

Do you have the unknown serial issue? I'm almost 100% sure that errors unlocking stem from unknown serial errors or a past RMA.

Also have either of you run a logcat while trying the tool?

Sent from my Inspire 4G using xda premium
 

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
Do you have the unknown serial issue? I'm almost 100% sure that errors unlocking stem from unknown serial errors or a past RMA.

Also have either of you run a logcat while trying the tool?

Sent from my Inspire 4G using xda premium

I don't know about this serial issue, I should try to run a logcat for more info as I don't have the same error than you all. I'll try to give a look if I can this weekend.
 

nhshah7

Senior Member
Feb 14, 2009
2,068
568
Boston
July 13th Update:

I have contacted Asus with this information. I learned something interesting. Asus has my tablet (s/n) listed as LOCKED. They also did not replace my mainboard when I RMA'ed the tablet. I also have not had the unknown serial number issue. Considering those were the 3 criteria a few of us had considered to be the reasons for not being able to unlock, I am now baffled.

I am going to continue communicating with Asus and hopefully push the matter a little bit more so that something happens. As I was told, "HQ is probably aware and working towards a fix". Let's hope that happens sooner rather than later.
 

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
This is the first time I make a log, have a lot of info and I think I found the good lines (really not sure about it)

Code:
I/ActivityManager(  192): Start proc com.asus.cm for service com.asus.cm/.push.PushService: pid=11731 uid=1000 gids={3003, 1015, 3002, 3001, 3007}

D/CMC->CMConfig(11731): DMConfig.init()

D/CMC->CMConfig(11731): mFumoHandlerName=DefaultFumoHandler

D/CMC->CMConfig(11731): allowShowMoreInfoOnError=false

D/CMC->CMConfig(11731): allowFotaPolling=true

D/CMC->PushService(11731): ============== PushService.onStartCommand() ==============

D/CMC->UniqueId(11731): get cached uniqueID

W/ActivityThread(11731): ClassLoader.getResources: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());

D/CMC->NioClient3(11731): addClient: XXXXXXXXXXX
I/ActivityManager(  192): Start proc com.asus.dm for broadcast com.asus.dm/.c2dm.C2DMReceiver: pid=19858 uid=1000 gids={3003, 1015, 3002, 3001, 3007}

D/DMC->DMConfig(19858): DMConfig.init()

D/DMC->DMConfig(19858): mFumoHandlerName=DefaultFumoHandler

D/DMC->DMConfig(19858): allowShowMoreInfoOnError=false

D/DMC->DMConfig(19858): allowFotaPolling=true

D/DMC->C2DMReceiver(19858): context: android.app.ReceiverRestrictedContext@410ae150, intent: Intent { act=com.asus.unlock.intent.REGISTRATION flg=0x10 cmp=com.asus.dm/.c2dm.C2DMReceiver (has extras) }

D/DMC->C2DMReceiver(19858): dmControl: registrationId = null, error = null, removed = null

D/DMC->C2DMReceiver(19858): unlock session ready to start

D/DMC->DMService(19858): =================== DMService onCreate() ===================

D/DMC->DMService(19858): check current tree

D/DMC->DMService(19858): mBatteryState = 75

D/DMC->DMDownloadProgress(19858): new Class: com.asus.dm.DefaultNotify

D/DMC->SessionStateNotifier(19858): SSC: registerObserver: com.asus.dm.DMService@410b0d28

D/DMC->DMRegistry(19858): getStringValue(pref_key_tree_file) = DMTREE

D/DMC->DMStorage(19858): invoke openInputStraem() of DMStorage.....

I/DMTreeParser(19858): Start document

I/DMTreeParser(19858): Start tag rdmtree

I/DMTreeParser(19858): Start tag version

I/DMTreeParser(19858): Text@0 "1.02"

I/DMTreeParser(19858): End tag version

I/DMTreeParser(19858): Start tag node

D/dalvikvm(19858): GC_CONCURRENT freed 320K, 6% free 6631K/7047K, paused 2ms+2ms

I/DMTreeParser(19858): End tag rdmtree

D/DMC->DMService(19858): DMConfig.getFumoHandlerName()= DefaultFumoHandler

D/DMC->DMService(19858): DMConfig.getFumoRootUri()= ./FwUpdate/Flash

D/DMC->DMService(19858): ============== finish onCreate =============

D/DMC->DMService(19858): =================== DMService onStartCommand() ===================

D/DMC->DMService(19858): ===== acquire wake_lock

D/DMC->DMService(19858): ===== doC2dmIDSession =====

D/DMC->DMService(19858): use Asus register

D/DMC->DMHandlerHelper(19858): register IO on:./DevInfo/DmV

D/DMC->DMHandlerHelper(19858): register IO on:./DevInfo/FwV

D/DMC->DMHandlerHelper(19858): register IO on:./DevInfo/SwV

D/DMC->DMHandlerHelper(19858): register IO on:./DevInfo/HwV

D/DMC->DMHandlerHelper(19858): register IO on:./DevInfo/Mod

D/DMC->DMHandlerHelper(19858): register IO on:./DevInfo/Man

D/DMC->DMHandlerHelper(19858): register IO on:./DevInfo/Lang

D/DMC->ConnectivityStateReceiver(19858): ConnectivityStateReceiver:onReceive

D/DMC->ConnectivityStateReceiver(19858): ===== Network type: 1, state=CONNECTED,  LastFotaPollingSuccess: true =====

D/DMC->VersionHandler(19858): ***** bytes is Transformer Prime TF201 *****

D/DMC->VersionHandler(19858): ***** bytes is Transformer Prime TF201 *****

D/DMC->VersionHandler(19858): ***** bytes is asus *****

D/DMC->VersionHandler(19858): ***** bytes is asus *****

D/DMC->VersionHandler(19858): ***** bytes is en *****

D/DMC->VersionHandler(19858): ***** bytes is en *****

D/DMC->VersionHandler(19858): ***** bytes is 1.3 *****

D/DMC->VersionHandler(19858): ***** bytes is 1.3 *****

W/DMC->DMService(19858): ********** notify_start **********

W/DMC->DMService(19858): mCurrentSessionType=DM, mCurrentSessionState=STARTED, lastError=ERROR_CODE_OK, SessionInitiator=com.asus.dm.c2dm.RegC2dmIdInitiator

W/DMC->DMService(19858): ********** notify_end **********

D/DMC->DMService(19858): state=C2DMRegSession: STARTED, lastError=ERROR_CODE_OK

D/dalvikvm(19858): GC_CONCURRENT freed 363K, 7% free 6725K/7175K, paused 3ms+2ms

I/ClientSessionHandler(19858): Checking credentials using auth-md5.

I/DMCommunicator(19858): Sending package from IMEI:XXXXXXXXXXXX to https://mdm.asus.com/DMServer/AsusDMServlet

D/dalvikvm(19858): GC_CONCURRENT freed 324K, 6% free 6823K/7239K, paused 4ms+2ms

E/HttpLinkChannel(19858): response status code: 500

I/HttpLinkChannel(19858): Send dm message failed, retry after 300ms

E/HttpLinkChannel(19858): response status code: 500

I/HttpLinkChannel(19858): Send dm message failed, retry after 450ms

D/dalvikvm(19858): GC_CONCURRENT freed 425K, 8% free 6841K/7367K, paused 4ms+3ms

E/HttpLinkChannel(19858): response status code: 500

I/HttpLinkChannel(19858): Send dm message failed, retry after 675ms

I/HttpLinkChannel(19858): send dm message failed!!!!!

W/DMC->DMService(19858): ********** notify_start **********

W/DMC->DMService(19858): mCurrentSessionType=DM, mCurrentSessionState=ABORTED, lastError=ERROR_COMMS_NON_FATAL, SessionInitiator=com.asus.dm.c2dm.RegC2dmIdInitiator

W/DMC->DMService(19858): ********** notify_end **********

D/DMC->DMService(19858): state=C2DMRegSession: ABORTED, lastError=ERROR_COMMS_NON_FATAL

D/DMC->DMService(19858): stop me

D/DMC->DMService(19858): clear Asus register

D/DMC->DMService(19858): ===== release wake_lock

D/DMC->DMService(19858): DM process finish

If I did wrong can someone tell me what I should look after ? And if it's the good lines hope it can help.
 
Last edited:

nhshah7

Senior Member
Feb 14, 2009
2,068
568
Boston
This is the first time I make a log, have a lot of info and I think I found the good lines (really not sure about it)

If I did wrong can someone tell me what I should look after ? And if it's the good lines hope it can help.

interesting. try to search for wvdrm.asus.com in your logcat and post the code around there. also, you may want to x out your imei number from the code. you don't want that out in the open!
 
  • Like
Reactions: bASKOU

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
interesting. try to search for wvdrm.asus.com in your logcat and post the code around there. also, you may want to x out your imei number from the code. you don't want that out in the open!

Thanks for your advice about the IMEI, I never think about hide some infos ^^

Code:
I/ActivityManager(  192): Start proc com.asus.wvdrm for service com.asus.wvdrm/.KeyBoxService: pid=15107 uid=1000 gids={3003, 1015, 3002, 3001, 3007}

D/KeyBoxService(15107): === onCreate()

D/KeyBoxService(15107): === onStartCommand(), intent=null, flags=2, startId=20

D/KeyBoxService(15107): === StatusCode: SC_UNAUTHORIZED!

D/KeyBoxService(15107): === OTA BEGIN

E/KeyBoxService(15107): === Connection to http://wvdrm.asus.com refused

D/KeyBoxService(15107): === Retry after 60 seconds.

D/KeyBoxService(15107): === OTA END

It basically repeat this severals time until get:

Code:
D/KeyBoxService(15107): === Retry after 2400 seconds.


D/KeyBoxService(15107): === OTA END

If you want my full log just PM me and I'll send you.

EDIT: I just checked on internet, and seems that this problem come with tab that went in RMA, so I wonder if the tab I bought in a new package had been return due to a problem and customer asked for a refund. Asus repaired it then package it back ready to be sale again...
 
Last edited:

AlphaDog_NL

Member
Feb 17, 2010
23
3
Delft
I just found a repair sticker on my box, so you can definitely add my case to the "After RMA" pile. At least we know the "cause" of 90% of the failures. Perhaps we could ask some more specific questions now...
 

CharliesTheMan

Senior Member
Have any of you that have had trouble unlocking not ever rooted your tfp?

I've been studying some data and I'm wondering if some of you who are having trouble unlocking, have remained bone stock and never rooted or if most all of you rooted your Prime sometime during your ownership and before you unlocked it.

Sent from my ADR6425LVW using xda premium
 

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
Have any of you that have had trouble unlocking not ever rooted your tfp?

I've been studying some data and I'm wondering if some of you who are having trouble unlocking, have remained bone stock and never rooted or if most all of you rooted your Prime sometime during your ownership and before you unlocked it.

Sent from my ADR6425LVW using xda premium

I have wondered this too. I get my Prime back from RMA on Wednesday after having the mainboard replaced. The first thing I am going to do is run the unlock tool. If that doesn't work, the next thing I will do is list the POS on Craig's List :p

Sent from my Amazon Kindle Fire using xda premium
 

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
I have wondered this too. I get my Prime back from RMA on Wednesday after having the mainboard replaced. The first thing I am going to do is run the unlock tool. If that doesn't work, the next thing I will do is list the POS on Craig's List :p

Sent from my Amazon Kindle Fire using xda premium

Some people rooted they tab then could unlock, some other didn't root and couldn't unlock bootloader. So the root seems to have no effect from what I read on this forum and on others.

Sent from my Transformer Prime TF201 using Tapatalk 2
 

nhshah7

Senior Member
Feb 14, 2009
2,068
568
Boston
Some people rooted they tab then could unlock, some other didn't root and couldn't unlock bootloader. So the root seems to have no effect from what I read on this forum and on others.

Sent from my Transformer Prime TF201 using Tapatalk 2

Agreed. The common thread seems not to be rooting but RMA or unknown serial.

Sent from my Inspire 4G using xda premium
 

ekalb10

Senior Member
Feb 11, 2012
80
14
College Station. Texas
I RMAd my Prime back in June and saw cm 10 in the developer forum today, and I was going to take the leap and unlock. But to no avail and happened onto the same error yall came upon.

Sent from my Transformer Prime TF201 using XDA Premium HD app
 

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
Yep, got my RMA back today and I get the unknown error. Even tried downgrading to .14 but no dice :(

Sent from my HTC Sensation using xda premium

With all I read it simply that Asus block all tabs that went on RMA to be unlocked and this certainly by something hardware. This is dirty, then they come to say that the unlocker apk doesn't have support.

Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
 

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
With all I read it simply that Asus block all tabs that went on RMA to be unlocked and this certainly by something hardware. This is dirty, then they come to say that the unlocker apk doesn't have support.

Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

Its a real shame. My Prime was for fun, not work fortunately and a great deal of my time was spent flashing different ROMs and trying them out. I am certainly not saying that ASUS owes me anything and unfortunately I guess it is their prerogative to say they don't support the unlock tool. Unlike a lot of people on this forum I have really enjoyed owning my Prime and I think it is a great piece of hardware, but this leaves me no choice but to sell it. I will be listing it on Craig's List today :(
 

Tempie007

Senior Member
Dec 15, 2010
499
72
RMA'd mine today and i hope it will be unlockable on return ..... if not im RMAing it again because the device is not in its original state ....

if that does not work its for my GF or ebay and i get a samsung tablet and i will never buy asus again.. simple :thumbup:
 

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
RMA'd mine today and i hope it will be unlockable on return ..... if not im RMAing it again because the device is not in its original state ....

if that does not work its for my GF or ebay and i get a samsung tablet and i will never buy asus again.. simple :thumbup:

Has anyone been able to re-RMA'd for this unlockable bootloader issue? I would be *really* interested to know if anyone has done this successfully. I would be happy to pay to send it back and have it fixed but I suspect that they won't touch it again...
 

Tempie007

Senior Member
Dec 15, 2010
499
72
im wondering:

- are there people that RMA'd and got the device in original state -software wise?
- or if wiped, are there people that were able to unlock ( again ) ?

or am i simply screwed now i rma'd it??
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    4/18/2013
    After months of waiting, my tablet is FINALLY UNLOCKED! If you are in the US, see this post. Thanks you Tien (Asus_USA)!


    Update 9/2013:
    It's back.

    It works

    Sooooooo people, contact ASUS Support about your device tracker not working! They will give you support on that, and because it has the same problem causing it, it will fix the unlock issue!


    Hi all, I decided to finally take the dive a couple days ago to unlock my beloved prime and try out androwook and other custom roms that supposedly put stock to shame. However, I was unfortunately confronted by a crude and nasty message along the lines of:

    Code:
    An unknown error occurs, which may be a network connection issue. 
    Please wait and try again later

    As usual, I unrooted, rebooted, and tried again. No luck.
    I disabled and uninstalled ATP Tweak (sio scheduler/systune), replaced my modified dock keyboard files (browser mod, switched alt/search buttons), and tried again. No luck.
    Factory reset from the settings menu. No luck.
    Placed the .28 US update on my SD card, rebooted, and re-flashed the update. No luck.

    Where does that leave me now? Locked and feeling imprisoned. I'm wondering if it is worth it to downgrade and try unlocking. So far, I have only seen one person have any success with this. Due to the potential brick risk, I want to stay away from this unless I know it will work. I also know that Asus asked for the MAC address of a prime owner with this issue, but that didn't go anywhere.

    This seems like it may be an issue that is experienced by anyone that RMA'ed their tablet for whatever reason. I, personally, sent mine in for a green camera issue and mura, but do not think that they changed my motherboard.

    I am also curious to see how many other people are having this issue. If it is sizable, I am willing to start a petition to Asus for them to support their unlock tool and fix this stupid error without an RMA. To that effect, please answer the poll above to let me gather some data on the unlock tool.

    Thanks to everyone for your help and support that makes xda such an amazing community!

    PS I don't want to see any "Asus sucks" posts. There are tons of other threads for that so please spare us :)



    Additional info:
    Have tried this on several different network connections.
    Have not yet contacted Asus to see if they have my prime listed as "unlocked" already, but will do so sometime this week.
    Logcat of running unlock tool results in this:
    Code:
    D/KeyBoxService(10158): === StatusCode: SC_UNAUTHORIZED!
    
    D/KeyBoxService(10158): === OTA BEGIN
    
    E/KeyBoxService(10158): === Connection to http://wvdrm.asus.com refused
    
    D/KeyBoxService(10158): === Retry after 600 seconds.
    
    D/KeyBoxService(10158): === OTA END





    July 13th Update:

    I have contacted Asus with this information. I learned something interesting. Asus has my tablet (s/n) listed as LOCKED. They also did not replace my mainboard when I RMA'ed the tablet. I also have not had the unknown serial number issue. Considering those were the 3 criteria a few of us had considered to be the reasons for not being able to unlock, I am now baffled.

    I am going to continue communicating with Asus and hopefully push the matter a little bit more so that something happens. As I was told, "HQ is probably aware and working towards a fix". Let's hope that happens sooner rather than later.

    September 5th update:
    Seems that Asus HQ figured out a fix, but it requires an RMA. We'll find out soon if it actually works...

    September 29th update:
    Some of the members in this thread have sent their primes in for an RMA to fix the issue. The first prime back STILL has the problem. Asus HQ is looking into the matter...again...
    9
    Hey Everyone!

    I haven't been on here in a while, but I'm back!

    For those who are in the US, have had their Primes RMAed, and can still not get the device to unlock, I am going to see if I can help. Please shoot me an e-mail at cl-tien@asus.com. Use the e-mail address as I rarely check the PMs here. In the e-mail, please include:

    Name:
    Previous RMA #s:
    Device Serial Number:
    MAC Address from the "about tablet" screen in the Settings:

    A screen shot of the About Tablet screen would be OK too; just make sure to send as an attachment.

    I am going to gather up some affected users and submit them to HQ. Hopefully, we can get some answers and some solutions soon. No promises as of right now, but we at the US office would like to get this resolved.

    Many thanks to nhshah7 for keeping me informed regarding this possible solution from HQ.
    7
    I cannot speak for other countries or regions, but if you are located in the US or Canada, our facilities do have a fix for the unlock error. However, as Mason said, it does require that you send it in for RMA.

    The call center and technical support might not be aware, but our technicians already know the procedure on how to fix it. I apologize to all of those who have tried to get an RMA for this through the call center. They are instructed not to assist with issues regarding unlocking device - as we all are. However, we understand that this is a special issue, and have set-up a repair process for the affected tablets.

    I apologize for the wait and would like to thank those who were patient while we got to the bottom of the issue, and devised a fix for it. If you are having a hard time with getting an RMA from the call center, please shoot me an e-mail to this inbox: cl-tien@asus.com and I will be happy to help arrange the RMA for you. Again, I can only assist those located in the US and Canada.

    Tien
    7
    Just an update to dev/analysis that I'm currently working on.

    A simple check of all the various releases that ASUS have done shows that the EBT partition (bootloader) have had various changes made to them in the past. For example, .17 and below will not show the "bootloader is unlocked" message whilst on boot, versions prior to the ICS release does not have the unlock alogrithm, etc.

    Rumor has it that the JB version of the TF300 have fastboot enabled, thus this might be of some help for us in the future, yet at the current moment, it helps us none.

    Anyhow, back to topic. Since there's been various changes in the bootloader itself, there may be a slight chance that ASUS left out one of the signature checks in one of the bootloader versions. Thus one angle that we could go is to keep trying different bootloaders and checking to see either if the blob signature check is in effect or if the AES engine has been disabled properly in the bootloader. If the blob signature check has been let out, then we would theoretically be able to flash a modified bootloader to bypass the various checks that happen in the bootloader. The AES engine part, if we can verify if it has forgotten to be disabled, we would be able to generate the NVflash files needed for wheelie, and we'd have more avenues to try.

    The other angle that I'm currently looking at is somehow figuring out the private key for RSA signature. I've looked into RSA signatures, and theoretically it is pretty much impossible to crack, specially in the case of RSA encryption. In RSA, the public key is used to encrypt, the private key is used to decrypt. In the case of RSA signatures, the private key is used to "decrypt" a string, usually the sha1 hash of the file needed to be signed. Then the public key is used to "encrypt" this signature, and compare the result with the hash of the file we want to check.

    Since we have various files from ASUS that have signatures, we have the "decrypted" strings which are the signatures, and the "encrypted" strings which would probably be the hash file checksums of the various blobs.

    In order to determine this logic, we need a few things. 1. we need to disassemble the bootloader binary file to determine whether it is in fact the sha file checksum that is being used as the string. 2. we need to disassemble the bootloader to get hold of the public key that is being used. I've tried the certificate in the zip files, however these appear to be a different certificate than the one that is being used for blob checking.

    I'm currently working mostly on a way to figure out the private key exponent that is being used to decrypt the strings. This is a very complex task, and possibly impossible, however having various combinations of signatures and strings should help. Once the signature can be figured out, we'd be able to sign the modified bootloader and load that into the system, effectively giving us an unlocked bootloader.

    The only problem is, I have not experience with disassembly of the bootloader binary. I believe I need a linux box with the arm toolchain installed at the least. On the other hand if any devs here already have disassembled the bootloader binary (for example android.root mobi team), then it would help in speeding things up.
    5
    News!

    If you can get me the serial number of your tablet along with the WiFi’s MAC address then HQ can use that to check the server conditions. You might want to collect the S/N and WiFi MAC of several people from the forum but at least if we have your S/N and WiFi MAC, I can have HQ check to see why you aren’t able to unlock the unit.

    Ok, so I might create a google doc and have you guys put the information so I can send it to them. Would you be ok with this? Or do you want to PM me instead?

    edit: here it is

    https://docs.google.com/spreadsheet/ccc?key=0AnAJoa0-ynONdEYxU1lhRVk3eGN2UWxOMU1aSG1hc3c