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:
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:
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:
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...
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...
Last edited: