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
By:
Advanced…
Hawkysoft

Hawkysoft

Senior Member
Jul 21, 2010
762
182
40
Rotterdam
Ok here my 2cents...

Tried unlocking trough my phones WiFi... Same error as you guys.. next day i tried it at home on my normal wifi...

Profit. Unlocked.

Hope it works for you guys as well.

I dont know why it didnt work but tried it like a ten times...
Maybe stability issue of the phones WiFi or smthn...

Sent from my HTC Incredible S using xda premium
 
Last edited:
  • Like
Reactions: xboxorcist
G

grilko

Member
Feb 26, 2012
32
2
Bratislava
After some emails with asus online servise they told me i have to send my device to servise. I dont wont to send it AGAIN to servise but when i want to unlock my device i have no choise.
 
bASKOU

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
Hawkysoft said:
Ok here my 2cents...

Tried unlocking trough my phones WiFi... Same error as you guys.. next day i tried it at home on my normal wifi...

Profit. Unlocked.

Hope it works for you guys as well.

I dont know why it didnt work but tried it like a ten times...
Maybe stability issue of the phones WiFi or smthn...

Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse

I always use my wifi router and never the one of my phone. Did your tab went on RMA?

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

bASKOU

Senior Member
Mar 4, 2012
818
292
Nîmes
paddycr said:
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 :(
Click to expand...
Click to collapse

Same for me, unfortunately for Asus I wanted to buy the tf700 and let the prime for my wife. But now I'll wait that another manufacturer make a quad-core tab for change my prime. By doing this Asus is going to loose a lot of customers who like us want to install custom ROMs, kernels, etc... As no manufacturer release an Android devise working at 100% of its capacities so we are forced to flash custom ROMs for that.

It's a shame to see that my HTC Sensation XE dual core with Sense 4 is faster and smoother than the prime. I never had an ANR on my phone and learned what it is on prime forum.

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

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
ekalb10 said:
If you send it in let us know how it went' and if you were able to unlock afterwards.

Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse

I have been chatting with Tien, our ASUS rep on this forum. He stated that you cannot RMA to fix the unlockable bootloader since the unlock tool is not supported. He was very helpful but that sucks :mad:

Sent from my Nexus 7 using xda premium
 
nhshah7

nhshah7

Senior Member
Feb 14, 2009
2,068
568
Boston
paddycr said:
I have been chatting with Tien, our ASUS rep on this forum. He stated that you cannot RMA to fix the unlockable bootloader since the unlock tool is not supported. He was very helpful but that sucks :mad:

Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse

I also emailed back and forth with Tien. He informed me that Asus is aware of the issue and might be working on a fix...but he didn't say if he knew for sure or anything else about it...

Sent from my Inspire 4G using xda premium
 
  • Like
Reactions: bASKOU and ekalb10
gunzy83

gunzy83

Senior Member
Nov 23, 2010
88
18
Brisbane, AU
Well this is frustrating. Finally got up the courage to unlock and I have this exact problem. I have tried cold boot, factory reset, downgrading to .15 firmware and back to .28 firmware now and still no dice. I was rooted originally, now I am not. I have never RMA'd and I have always had a Serial Number.

I found this in my logcat:
Code: 
D/DMServerUnlock( 1905): index of line: 3
D/DMServerUnlock( 1905): DM Server Response: 104

No mention of http://wvdrm.asus.com/ so it is not even getting that far.

Don't know if that helps....
 
P

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
dude2k5 said:
Please Tien, you're our only hope.
Click to expand...
Click to collapse

This is a quote from a message that Tien sent me: "The issue seems to have something to do with the website. I have had users experiencing this issue who have done an RMA and who have never even sent in their tablet. It's a little tricky to track it down. However, we are unable to support the unlocking tool here - I'm sorry. They are aware of it over at HQ, but I cannot give you assurances that it will be resolved soon."

I have my Prime listed on CL. I really hate selling it because unlike a lot of people I think it is a really nice piece of hardware but I think the stock ROM sucks. I don't think this issue is going to be resolved anytime soon and I don't want to keep it if I have no choice but running stock.
 
gunzy83

gunzy83

Senior Member
Nov 23, 2010
88
18
Brisbane, AU
paddycr said:
This is a quote from a message that Tien sent me: "The issue seems to have something to do with the website. I have had users experiencing this issue who have done an RMA and who have never even sent in their tablet. It's a little tricky to track it down. However, we are unable to support the unlocking tool here - I'm sorry. They are aware of it over at HQ, but I cannot give you assurances that it will be resolved soon."
Click to expand...
Click to collapse

Well that's just bloody fantastic. Thanks for the heads up. I have reported the issue to their support if only to annoy them into some action. I hope that is just the usual "no expectations" speak to keep away the bad press...

---------- Post added at 09:12 AM ---------- Previous post was at 08:23 AM ----------

Wow. I just found something very very weird. I have always quoted my serial number from inside the OS but I just compared it to the sticker on the chassis. There are a two numbers (2 5s that should be a 6s) that are wrong on the device compared with the sticker on the bottom. I can't believe I missed it...

---------- Post added at 10:04 AM ---------- Previous post was at 09:12 AM ----------

A further update:

I am now unlocked. Serial number typo between the sticker and the software was the problem. This is how I did it:

1. Am at work so had to install the Asus USB driver and Android SDK (thanks administrator account :))
2. Rooted with this: http://xdaforums.com/showthread.php?t=1706588 because the mempodroid exploit in the next step does not work with the .28 firmware I am currently on.
3. Updated my S/N with this: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/ to the number on the sticker on my device.
4. Run unlock tool.
5. Profit.

I would suggest anyone having this problem check their serial numbers against the sticker. Seems root is not an issue, unlocked while rooted and using my HTC One XL as internet access.

Good luck guys :good:
 
Last edited:
  • Like
Reactions: paddycr, nhshah7, Bait-Fish and 1 other person
epeereboom

epeereboom

Senior Member
Jan 9, 2011
61
22
Plano
That is a good find. I wonder how many people this will help.



Sent from my Transformer Prime TF201 using XDA Premium HD app
 
Last edited:
dude2k5

dude2k5

Senior Member
Jul 9, 2010
761
284
www.futurenology.com
gunzy83 said:
Well that's just bloody fantastic. Thanks for the heads up. I have reported the issue to their support if only to annoy them into some action. I hope that is just the usual "no expectations" speak to keep away the bad press...

---------- Post added at 09:12 AM ---------- Previous post was at 08:23 AM ----------

Wow. I just found something very very weird. I have always quoted my serial number from inside the OS but I just compared it to the sticker on the chassis. There are a two numbers (2 5s that should be a 6s) that are wrong on the device compared with the sticker on the bottom. I can't believe I missed it...

---------- Post added at 10:04 AM ---------- Previous post was at 09:12 AM ----------

A further update:

I am now unlocked. Serial number typo between the sticker and the software was the problem. This is how I did it:

1. Am at work so had to install the Asus USB driver and Android SDK (thanks administrator account :))
2. Rooted with this: http://xdaforums.com/showthread.php?t=1706588 because the mempodroid exploit in the next step does not work with the .28 firmware I am currently on.
3. Updated my S/N with this: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/ to the number on the sticker on my device.
4. Run unlock tool.
5. Profit.

I would suggest anyone having this problem check their serial numbers against the sticker. Seems root is not an issue, unlocked while rooted and using my HTC One XL as internet access.

Good luck guys :good:
Click to expand...
Click to collapse

im sure this will help those who have the same thing. tried to re-enter mine, hoping, but sadly it still gets the error. but good find. :good:
 
nhshah7

nhshah7

Senior Member
Feb 14, 2009
2,068
568
Boston
DAMN! My serial no is correct on the system. That's a great find though. Thanks for sharing!!!

Sent from my Transformer Prime TF201 using XDA Premium HD app
 
MartiniMoe

MartiniMoe

Senior Member
Nov 8, 2010
66
6
gunzy83 said:
Well that's just bloody fantastic. Thanks for the heads up. I have reported the issue to their support if only to annoy them into some action. I hope that is just the usual "no expectations" speak to keep away the bad press...

---------- Post added at 09:12 AM ---------- Previous post was at 08:23 AM ----------

Wow. I just found something very very weird. I have always quoted my serial number from inside the OS but I just compared it to the sticker on the chassis. There are a two numbers (2 5s that should be a 6s) that are wrong on the device compared with the sticker on the bottom. I can't believe I missed it...

---------- Post added at 10:04 AM ---------- Previous post was at 09:12 AM ----------

A further update:

I am now unlocked. Serial number typo between the sticker and the software was the problem. This is how I did it:

1. Am at work so had to install the Asus USB driver and Android SDK (thanks administrator account :))
2. Rooted with this: http://xdaforums.com/showthread.php?t=1706588 because the mempodroid exploit in the next step does not work with the .28 firmware I am currently on.
3. Updated my S/N with this: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/ to the number on the sticker on my device.
4. Run unlock tool.
5. Profit.

I would suggest anyone having this problem check their serial numbers against the sticker. Seems root is not an issue, unlocked while rooted and using my HTC One XL as internet access.

Good luck guys :good:
Click to expand...
Click to collapse

Nice :D
But my serial number is correct :(
Im thinking of selling my TFP and getting the N7. I do want custom ROMs!
 
gunzy83

gunzy83

Senior Member
Nov 23, 2010
88
18
Brisbane, AU
I just hope what I found helps someone and isn't entirely isolated to me lol. Hope you guys get this sorted! :fingers-crossed:
 
P

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
gunzy83 said:
I just hope what I found helps someone and isn't entirely isolated to me lol. Hope you guys get this sorted! :fingers-crossed:
Click to expand...
Click to collapse

That's a really nice find. This is complete speculation on my part but I think the the unlock tool requires the Prime's CPUID and serial number. Since my mainboard was changed during RMA the CUPID will have changed. I wonder if the unlock tool requires a match between CPUID and serial number to successfully unlock?? I dunno...this is really frustrating.
 
Last edited:
dude2k5

dude2k5

Senior Member
Jul 9, 2010
761
284
www.futurenology.com
paddycr said:
That's a really nice find. Did you RMA? This is complete speculation on my part but I think the the unlock tool requires the Prime's CPUID and serial number. Since my mainboard was changed during RMA the CUPID will have changed. I wonder if the unlock tool requires a match between CPUID and serial number to successfully unlock?? I dunno...this is really frustrating.
Click to expand...
Click to collapse

I think you're on to something with the CPUID and Serial, on their servers they probably have the 2 matching, but when we RMA, they change parts, but don't update on their servers to the new CPUID or something. Not even sure how to find/get our CPUID in ICS...but I imagine if we get it and send it to them, I wonder if they could fix it on their side...


edit: Checked some logs
Wonder if androidboot.serialno has something to do with it. Wonder if it needs to be the real serial or the new serial we need to send asus so they can match it with our "real" serial to unlock us

Kernel command line: tegraid=30.1.3.0.0 mem=1024M@2048M vmalloc=256M androidboot.serialno=015d0787xxxxxxxx video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=8192@0xbcbed000 tegra_fbmem=4098560@0xbdc15000 core_edp_mv=1300 audio_codec=wm8903 tegraboot=sdmmc gpt gpt_sector=62078975 androidboot.product=TF201 androidboot.carrier=wifi-only


found this warning too, not sure what it means:
WARNING: at /home/android/Project/AutoSync/ICS-mr1-t30-r2/kernel/drivers/i2c/busses/i2c-tegra.c:640 tegra_i2c_xfer+0x2d4/0x3bc()


edit3: Lastly, in /sys/firmware/fuse/ what do you have in there? All mine seem blank, do they need something? I have no idea. Sigh. I attached mine, see if it matches with yours (unlocked or locked)
 

Attachments

  • fuse.zip
    1.2 KB · Views: 34
Last edited:
You must log in or register to reply here.

Similar threads

flumpster
[ROM][May 13][JB 4.2.1] AndroWook Prime Hairy Bean v2.2 **Unleash The Beast!**
Replies
10K
Views
1M
S
sachinkumar1312
-viperboy-
[TOOL][Updated 5.9.12]viperMOD PrimeTime v4.6 | Auto Root/Unroot/Busybox/CMW Flash!
Replies
2K
Views
658K
E
evan661212000101
Gary Key
  • Locked
Unofficial by Official ASUS Thread - Product Updates
Replies
2K
Views
522K
Diamondback
Diamondback
Diamondback
[HOW-TO] Unbrick your Transformer Prime (or not)
Replies
623
Views
260K
J
jonafun
Wordlywisewiz
Not So Persistent Perfection Asus Transformer Prime Bootloader Unlock!
Replies
742
Views
160K
jotha
jotha

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 12
    nhshah7
    nhshah7
    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:
    AlphaDog_NL said:
    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!
    Click to expand...
    Click to collapse


    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...
    View
    9
    A
    Asus_USA
    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.
    View
    7
    A
    Asus_USA
    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
    View
    7
    kokopuphz
    kokopuphz
    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.
    View
    5
    dude2k5
    dude2k5
    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.
    Click to expand...
    Click to collapse

    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
    View

New posts