Related
I'm currently trying to unlock my bootloader, but encountering problems. It's a JP TF300T and I'm sick of never getting OTA from ASUS (or getting it four months down the line). I finally decided to unlock the bootloader and try a custom ROM. The issue is, it's coming up with the message 'An unknown error occurs, which may be a network connection issue, please wait and try again later', when I try to unlock the device. I have been trying again and again and again...to no avail. Can anyone tell me an easy way to change my region from JP to WW or US, without unlocking please? If not, is there any way to resolve the issue with the unlocking tool?
Kernel: [email protected]#1
Build Number: IML74K.JP_epad-9.4.3.30-20120604
I understand there may be an issue with the .30 build, but don't know how to sort it, any help would be appreciated.
Disclaimer: I have searched to forums and found an issue with the bootloader, but it doesn't entail the changing of region builds.
It would appear that the error was server-side, I am now rooted, unlocked, and on running US Jellybean.
I've just bought a second hand tf300 of Amazon and saw it still had ICS on it. When I tried to OTA update to JB it wouldn't. Closer inspection showed that in settings status the serial number is listed as unknown. I've now updated manually to JB and CWM was not installed so I dont think its unlocked and rooted. However I just want to run it with stock receiving OTA updates. Any ideas how I can fix the serial number issue or bypass to get OTA?
jimbo34 said:
I've just bought a second hand tf300 of Amazon and saw it still had ICS on it. When I tried to OTA update to JB it wouldn't. Closer inspection showed that in settings status the serial number is listed as unknown. I've now updated manually to JB and CWM was not installed so I dont think its unlocked and rooted. However I just want to run it with stock receiving OTA updates. Any ideas how I can fix the serial number issue or bypass to get OTA?
Click to expand...
Click to collapse
Here is my guess. You are unlocked. You can't load something like cwm if you're not.
I'm guessing before you got the tablet, the previous owner unlocked it, screwed it up, sent it to Asus for repair, and Asus returned it working, but loaded code somehow to eliminate the serial. This has happened to others, or so I've read. Feel lucky if you're unlocked. Users who have been reporting this problem have said their tablets are locked, and since there's no serial, they can't use the tool to unlock it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Here is my guess. You are unlocked. You can't load something like cwm if you're not.
I'm guessing before you got the tablet, the previous owner unlocked it, screwed it up, sent it to Asus for repair, and Asus returned it working, but loaded code somehow to eliminate the serial. This has happened to others, or so I've read. Feel lucky if you're unlocked. Users who have been reporting this problem have said their tablets are locked, and since there's no serial, they can't use the tool to unlock it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
CWM was not installed when I received it but is there any way of knowing if the unlock tool has been run previously? If I'm stuck doing manual updates how long does it take the ota updates to appear for download on the Asus site?
jimbo34 said:
CWM was not installed when I received it but is there any way of knowing if the unlock tool has been run previously? If I'm stuck doing manual updates how long does it take the ota updates to appear for download on the Asus site?
Click to expand...
Click to collapse
Usually a week give or take.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
jimbo34 said:
CWM was not installed when I received it but is there any way of knowing if the unlock tool has been run previously? If I'm stuck doing manual updates how long does it take the ota updates to appear for download on the Asus site?
Click to expand...
Click to collapse
When you boot, do you see "this device is unlocked" in small white text on the upper left corner? that's how you tell.
Btw, unlock doesn't mess with the serial number.
Sent from my ASUS Transformer Pad TF300T using Tapatalk
The guy you bought it from bricked the unlocked tablet and send it to Asus for repair. They then performed a full reflash but forgot or didn't repair the partition that holds the device ids. You can send it back to Asus for repair and they will fix the serial number issue but even after that you won't be able to receive OTA updates and you won't be able to unlock the device again.
p0k3y said:
When you boot, do you see "this device is unlocked" in small white text on the upper left corner? that's how you tell.
Btw, unlock doesn't mess with the serial number.
Sent from my ASUS Transformer Pad TF300T using Tapatalk
Click to expand...
Click to collapse
I don't see the "this device is unlocked" message on booting. I tried to run the unlock tool but get an error message. Guess I'm screwed for OTA or unlocking then. A newby question though, if I just want to root (mainly to install adblock and titanium backup, 6 axis etc), do I still need to unlock? If so, will there ever be a root without unlocking ie Debugfs?
jimbo34 said:
I don't see the "this device is unlocked" message on booting. I tried to run the unlock tool but get an error message. Guess I'm screwed for OTA or unlocking then. A newby question though, if I just want to root (mainly to install adblock and titanium backup, 6 axis etc), do I still need to unlock? If so, will there ever be a root without unlocking ie Debugfs?
Click to expand...
Click to collapse
You don't need to unlock for root access.
bazzio said:
You don't need to unlock for root access.
Click to expand...
Click to collapse
You do if you're running jb. If you found a means to do it without unlocking and on jb, please post it, and I don't mean carrying over root from ICS. Some don't have that option.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
jimbo34 said:
I've just bought a second hand tf300 of Amazon and saw it still had ICS on it. When I tried to OTA update to JB it wouldn't. Closer inspection showed that in settings status the serial number is listed as unknown. I've now updated manually to JB and CWM was not installed so I dont think its unlocked and rooted. However I just want to run it with stock receiving OTA updates. Any ideas how I can fix the serial number issue or bypass to get OTA?
Click to expand...
Click to collapse
I think that the best solution for you is to return to Asus your TF300 with the invoice, cause you bought this second hand on Amazon, and normally they should repair it to you without problem.
bazzio said:
You don't need to unlock for root access.
Click to expand...
Click to collapse
At the moment, you cannot root only your tablet if it's on JB bootloader.
If you want a root on JB bootloader, you need to unlock before
i have a TF300 that is having the same problem, i can not unlock the bootloader with the asus app... now is there another method to unlock the bootloader?
unfortunately not. You are stuck with Stock.
I know there have been reports of network error when trying to use the unlock tool. So I'm wondering if the problems happens intermittently or the unlock server has been down for everyone.
thanks!
Down for me, unknown error since i got this tablet,impossible to unlock
neeeko! said:
Down for me, unknown error since i got this tablet,impossible to unlock
Click to expand...
Click to collapse
I have a TF300T on latest JB stock, Unlock tool gives me the "unknown error" as well. Hoping it's everyone and they figure it out soon, not looking forward to a possible RMA journey...
giant25 said:
I have a TF300T on latest JB stock, Unlock tool gives me the "unknown error" as well. Hoping it's everyone and they figure it out soon, not looking forward to a possible RMA journey...
Click to expand...
Click to collapse
damn! already experiencing browser issues (i.e. IO) :/
Hi, I`m italian and excuse me for my simple english. I am the owner of an Asus TF700T with Android 4.1.1.
I wanted to install a custom rom, I read in the forum that it was necessary to first unlock the bootloader with the original asus `app.
I tried to run the Unlock Device Tool v.7 with Android 4.1.1 JB., But I am always returned the message "An error occours unkwon, Which may be a network connection issue, please wait and try again later." I tried, and tried, and tried, but nothing.
Then I read on the website of Asus that the `app worked with ICS, so I downgraded to build 9.4.5.30, I re-installed the` app I tried again and again.
But the `app continues to give me the same error message. Obviously the wireless network and the wifi work and I also tried with different networks but nothing.
Possible that there is no other way to unlock the bootloader?
Thanks in advance for the help that you can give me. Greetings to all.
juttere said:
Hi, I`m italian and excuse me for my simple english. I am the owner of an Asus TF700T with Android 4.1.1.
I wanted to install a custom rom, I read in the forum that it was necessary to first unlock the bootloader with the original asus `app.
I tried to run the Unlock Device Tool v.7 with Android 4.1.1 JB., But I am always returned the message "An error occours unkwon, Which may be a network connection issue, please wait and try again later." I tried, and tried, and tried, but nothing.
Then I read on the website of Asus that the `app worked with ICS, so I downgraded to build 9.4.5.30, I re-installed the` app I tried again and again.
But the `app continues to give me the same error message. Obviously the wireless network and the wifi work and I also tried with different networks but nothing.
Possible that there is no other way to unlock the bootloader?
Thanks in advance for the help that you can give me. Greetings to all.
Click to expand...
Click to collapse
See this thread: http://forum.xda-developers.com/showthread.php?t=1764917
Cheers :good:
juttere said:
Hi, I`m italian and excuse me for my simple english. I am the owner of an Asus TF700T with Android 4.1.1.
I wanted to install a custom rom, I read in the forum that it was necessary to first unlock the bootloader with the original asus `app.
I tried to run the Unlock Device Tool v.7 with Android 4.1.1 JB., But I am always returned the message "An error occours unkwon, Which may be a network connection issue, please wait and try again later." I tried, and tried, and tried, but nothing.
Then I read on the website of Asus that the `app worked with ICS, so I downgraded to build 9.4.5.30, I re-installed the` app I tried again and again.
But the `app continues to give me the same error message. Obviously the wireless network and the wifi work and I also tried with different networks but nothing.
Possible that there is no other way to unlock the bootloader?
Thanks in advance for the help that you can give me. Greetings to all.
Click to expand...
Click to collapse
You probably would get more responses if you made your thread title a little more descriptive
The Unlock tool works fine on all JB roms (4.1 and 4.2) - if it works at all.....
Unfortunately you are not the only one who has problems unlocking and it seems to be related to missing or incorrect databases on Asus' servers.
Don't give up, try again a day or two later.
In the meantime you could try to sign up for Asus Device Tracker service. It's free and gives you an idea if your S/N is registered on Asus servers. If you also get an error message call Asus customer service and ask them to correct the database because you want to sign up for Device Tracker.
Do not tell them you want to unlock! Asus does not support unlocking and their reps will not help you to do it.
There is no alternative method. It's either the Unlock Tool or nothing... :crying:
Sneaky bastards.
MartyHulskemper said:
Sneaky bastards.
Click to expand...
Click to collapse
+1
If they at least were consistent sneaky bastards! But if you look into who could not unlock and why and who finally managed to and how - you'll loose the rest of your hair!
Just read about a guy with a Prime who started his ordeal July 2012 and was able to unlock April 2013!!
Sent from my DROID4 using Tapatalk 2
Thank you all for the quick responses, the effects reported by chew1992 thread describes my problem very well, although it is not very comforting, that was a possible solution.
Having registered on the Asus site also try to download the app after you have logged-in.
And as indicatomi from berndblb, I'll try to contact Asus to ask what is the correct database.
I will keep you informed.
Greetings to all.
Hi, I hard bricked my ASUS Transformer TF300T (my fault) and sent it to ASUS to repair it. They replaced motherboard. So now I have it back with fresh Android 4.1.1. I tried to use ASUS' app to unlock bootloader (stock ROM without root is not usable for me), but when I agree and tap to "unlock", it only says "unknown error" and it doesn't work. It also says it might be problem with network, but network is working correctly. I think the problem is related to replacement of motherboard, but I don't know how. Does anyone have same problem? Some advice? Thanks in advance...
vjtz said:
Hi, I hard bricked my ASUS Transformer TF300T (my fault) and sent it to ASUS to repair it. They replaced motherboard. So now I have it back with fresh Android 4.1.1. I tried to use ASUS' app to unlock bootloader (stock ROM without root is not usable for me), but when I agree and tap to "unlock", it only says "unknown error" and it doesn't work. It also says it might be problem with network, but network is working correctly. I think the problem is related to replacement of motherboard, but I don't know how. Does anyone have same problem? Some advice? Thanks in advance...
Click to expand...
Click to collapse
You want to use v7 APK. If the device is busy doing something else, it'll return with unknown error. That being the case, you need to wait until after the tab has completed updating all the apps.
graphdarnell said:
You want to use v7 APK. If the device is busy doing something else, it'll return with unknown error. That being the case, you need to wait until after the tab has completed updating all the apps.
Click to expand...
Click to collapse
When I try it, tablet is doing nothing else. I'm sure I use correct version of unlock app. All apps are updated using Play. It doesn't show updates of Android (it has 4.1, id doesn't see OTA to 4.2). Anyway, thanks for advice...
It was solved by ASUS - I had to write to their customer center and wait little bit. But it works fine now.
vjtz said:
Hi, I hard bricked my ASUS Transformer TF300T (my fault) and sent it to ASUS to repair it. They replaced motherboard. So now I have it back with fresh Android 4.1.1. I tried to use ASUS' app to unlock bootloader (stock ROM without root is not usable for me), but when I agree and tap to "unlock", it only says "unknown error" and it doesn't work. It also says it might be problem with network, but network is working correctly. I think the problem is related to replacement of motherboard, but I don't know how. Does anyone have same problem? Some advice? Thanks in advance...
Click to expand...
Click to collapse
Yuuuuup,my TF300t had a broken dock/tablet connector.Got it back with a new mobo and 4.2.1 and the previous bootloader version V10.6.1.15.3, i tried every unlock theory around....nothing happened,but rooted it with motochopper.Its one big fustrating sheit....!!!!
vjtz said:
It was solved by ASUS - I had to write to their customer center and wait little bit. But it works fine now.
Click to expand...
Click to collapse
What was the procedure,can you explain what the fix was...?
Sincerely,LLCOOLVEER
llcoolveer said:
What was the procedure,can you explain what the fix was...?
Sincerely,LLCOOLVEER
Click to expand...
Click to collapse
The problem was, that after replacement of the motherboard, the tablet was locked. When you use the ASUS unlock utility, it connects to ASUS server and makes there entry, that your tablet with respective SN is unlocked now. It is not possible to relock tablet or unlock one tablet twice. Obviously. But when I've got it back, it was locked, but in their DB they still had entry, that it is unlocked, but in fact I couldn't unlock it. So I wrote to ASUS service and after exchange of several e-mails we found where problem lies and they enabled me to unlock it again.
vjtz said:
The problem was, that after replacement of the motherboard, the tablet was locked. When you use the ASUS unlock utility, it connects to ASUS server and makes there entry, that your tablet with respective SN is unlocked now. It is not possible to relock tablet or unlock one tablet twice. Obviously. But when I've got it back, it was locked, but in their DB they still had entry, that it is unlocked, but in fact I couldn't unlock it. So I wrote to ASUS service and after exchange of several e-mails we found where problem lies and they enabled me to unlock it again.
Click to expand...
Click to collapse
You mean the Akamai netsession interface Asus uses...?! I read an article wat described this feature...you also can do it yourself btw. Did you have to put the TF in download mode..? Or was it done fully operational...? And did you have to log in to your Asus account and register it first...? I tried it this way...but maybe i made a tiny mistake....Can you confirm this please, it would make me a very happy person...:good:
Have a Good Weekend.....
llcoolveer said:
You mean the Akamai netsession interface Asus uses...?! I read an article wat described this feature...you also can do it yourself btw. Did you have to put the TF in download mode..? Or was it done fully operational...? And did you have to log in to your Asus account and register it first...? I tried it this way...but maybe i made a tiny mistake....Can you confirm this please, it would make me a very happy person...:good:
Have a Good Weekend.....
Click to expand...
Click to collapse
Hi, I didn't find way how to do it myself. At leas not with 4.2 bootloader. It was done fully on their server side. They confirmed me they correct respective entry in their DB, so I could use the unlock app to unlock it again. I don't have any ASUS account and I don't want any.
On the beginning I wrote them I'm not able to unlock it again after exchange of motherboard. They told me, that in their DB it shows as unlocked - so that I can't unlock it again. After exchange of few mails Czech ASUS support contacted Taiwan HQ and it was done.
Now I'm happy with Baked ROM.
vjtz said:
Hi, I didn't find way how to do it myself. At leas not with 4.2 bootloader. It was done fully on their server side. They confirmed me they correct respective entry in their DB, so I could use the unlock app to unlock it again. I don't have any ASUS account and I don't want any.
On the beginning I wrote them I'm not able to unlock it again after exchange of motherboard. They told me, that in their DB it shows as unlocked - so that I can't unlock it again. After exchange of few mails Czech ASUS support contacted Taiwan HQ and it was done.
Now I'm happy with Baked ROM.
Click to expand...
Click to collapse
Now i understand...the old serialnr.is still in the DB at Asus,but the nem mobo has off course no relation to the old one...i will check my RMA bill to see if i can find something about it,and if i do i register this one too....see how that works out...:good:
Thanx for the info,it was very usefull..
yah im having the same issue, so who do I have to contact to fix this issue?
rileylarche said:
yah im having the same issue, so who do I have to contact to fix this issue?
Click to expand...
Click to collapse
Official ASUS service in your country.
yah i did that the live chat people were no help now i have to resort to email.......
Check your about tablet screen for a serial. I've heard when some get tablets back from Asus, the serial is all zeros or nonexistent which is required to unlock. No fix is known for this to my knowledge.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Same issue, rma'd for upgrade issue then second rma because I couldn't unlock. Supposedly Mac addresses and serials were not keyed in correctly during this process for others. I still can't unlock, network error like before