Still not working, but I have a logcat now.

I think these are the errors that matter:

D/DMServerUnlock( 1633): get DMServer Response retry count = 3

W/System.err( 1633): javax.net.ssl.SSLPeerUnverifiedException: No peer certificate

D/dalvikvm( 1633): GC_CONCURRENT freed 438K, 8% free 9126K/9863K, paused 38ms+9ms, total 63ms

W/System.err( 1633): at org.apache.harmony.xnet.provider.jsse.SSLSessionIm pl.getPeerCertificates(SSLSessionImpl.java:137)

W/System.err( 1633): at org.apache.http.conn.ssl.AbstractVerifier.verify(A bstractVerifier.java:93)

W/System.err( 1633): at org.apache.http.conn.ssl.SSLSocketFactory.createSo cket(SSLSocketFactory.java:381)

W/System.err( 1633): at org.apache.http.impl.conn.DefaultClientConnectionO perator.openConnection(DefaultClientConnectionOper ator.java:165)

W/System.err( 1633): at org.apache.http.impl.conn.AbstractPoolEntry.open(A bstractPoolEntry.java:164)

W/System.err( 1633): at org.apache.http.impl.conn.AbstractPooledConnAdapte r.open(AbstractPooledConnAdapter.java:119)

W/System.err( 1633): at org.apache.http.impl.client.DefaultRequestDirector .execute(DefaultRequestDirector.java:360)

W/System.err( 1633): at org.apache.http.impl.client.AbstractHttpClient.exe cute(AbstractHttpClient.java:555)

W/System.err( 1633): at org.apache.http.impl.client.AbstractHttpClient.exe cute(AbstractHttpClient.java:487)

W/System.err( 1633): at org.apache.http.impl.client.AbstractHttpClient.exe cute(AbstractHttpClient.java:465)

W/System.err( 1633): at android.net.http.AndroidHttpClient.execute(Android HttpClient.java:252)

W/System.err( 1633): at com.asus.unlock.h.b(Unknown Source)

W/System.err( 1633): at com.asus.unlock.h.a(Unknown Source)

W/System.err( 1633): at com.asus.unlock.h.c(Unknown Source)

W/System.err( 1633): at com.asus.unlock.UnLockActivity.b(Unknown Source)

W/System.err( 1633): at com.asus.unlock.UnLockActivity.d(Unknown Source)

W/System.err( 1633): at com.asus.unlock.UnLockActivity.b(Unknown Source)

W/System.err( 1633): at com.asus.unlock.t.run(Unknown Source)

W/System.err( 1633): at java.lang.Thread.run(Thread.java:856)

D/DMServerUnlock( 1633): get DMServer Response retry count = 2

D/dalvikvm( 714): GC_CONCURRENT freed 2054K, 26% free 16889K/22599K, paused 2ms+3ms, total 37ms

D/DMServerUnlock( 1633): index of line: 3

D/DMServerUnlock( 1633): DM Server Response: 104

W/InputMethodManagerService( 403): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@41ef44f0 attribute=null

I guess the most important is this one:

W/System.err( 1633): javax.net.ssl.SSLPeerUnverifiedException: No peer certificate

It seems that the tablet tries to connect to the Asus server, but the server cannot certificate itself???

I just called Asus Germany again, and I had a competent employee at the phone!

He told me that Asus currently has server problems and that the servers are probably down the whole weekend.

On Monday it should work again.

He also said that he doesn't believe that the problem is my tablet, but if it doesn't work on Monday I should call again.

So, let's wait and see...

Update: Still does not work.

Called Asus again and the hotline-guy confirmed that this is most likely a problem with the Asus server. He opened a ticket and I had to create an additional ticket via the Asus support-page.

I was promised to get an answer within 48 hours, so let's see...

good morning...

---

Originally Posted by BabelHuber

Update: Still does not work.

Called Asus again and the hotline-guy confirmed that this is most likely a problem with the Asus server. He opened a ticket and I had to create an additional ticket via the Asus support-page.

I was promised to get an answer within 48 hours, so let's see...

i never get any information or service over the ticket server... i call asus today aggain...

5 minutes ago i get a call from asus...

the mainboard of my tablet is not the original... i need to send it to asus to fix it (3weeks waiting time or more)

wtf... iam angry... new tablet ???

Originally Posted by simplytheone

5 minutes ago i get a call from asus...

the mainboard of my tablet is not the original... i need to send it to asus to fix it (3weeks waiting time or more)

wtf... iam angry... new tablet ???

Hm. I've opened a ticket via the Asus Germany page yesterday. Today I got a first answer. They needed the S/N and the MAC-address, although I gave them these informations already via phone.

According to the hotline, the problem should be the Asus server. So I assume that I don't have to send it in. But let's wait and see...

My old TF201 made no problems whatsoever when I unlocked it. So I assume that once that issue is fixed, I will be satisfied with the device.

Can't wait to try out CM10.1 and CHROMI

I have RMA'd my device twice, after getting my mainboard replaced, to get the MAC-address fixed.
Both times I got my device back without a fix and no possibility to unlock / root / downgrade or anything.

I contacted ASUS Germany again and asked for them to see if ASUS HQ in Taiwan can fix the issue as they appear to be able to as reported by a guy in this topic: http://forum.xda-developers.com/show....php?t=1795156
They replied that they would contact ASUS HQ.

I emailed Tien about this issue last night and he responded that they are aware of the problem and it's up to Asus HQ to fix the problem with the unlock tool. The issue is occuring with tablets that are brand new, bought when the unit first came out, have had RMA service, and they don't know why this is occuring. Being that the tool would void warranty it isn't exactly a high priority for them to solve. He actually apologized for the incovience and run around I got from email/phone support. There are people in Asus who care about the products and customers.

Calling in is really a chance in what end result you get. Some reps won't help because the "unlock" tool isn't supported by them and voids warranty. Same with the device tracker website. One rep I spoke with had no idea what the tracker was and kept insisiting that it wasn't an Asus product and supported by them. The real solution is finding a way to pressure\get Asus HQ to address the problem with the tool. They have already made the sale and profit from us buying the tablet and the warrning about voiding warranty is clear. It free's them of any further obligation to the device and means they can save money by not having to support hardware\software failures caused by the owners desire to modfiy things.

Till then I'll try a few times through the day and maybe get lucky with the tool working.

... next day with waiting

---

next day with waiting... asus say @ the last call i need to send the tablet back to rms...

i report the support guy from all the user who send the device back to asus and get only a update on JB and no fix of the mac/serialnumber error...

@ this point the supporter give the ticket to the next supporter... and i have to wait... i dont know why asus germany cant comunicate with asus usa and fix the problem without send the device back... i think its the cheapest way for asus...

i think i have to give my tablet back in the shop the german support dont get the problem... i wait now 1 week max...

New Day new eMail:

asus send my Ticket to the ASUS HQ (I think its a good message)