Database Info

[Q] A question about my brick

I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.

jeremiah.wells said:
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
Click to expand...
Click to collapse
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.

MartyHulskemper said:
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
Click to expand...
Click to collapse
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.

Can you get into recovery at all when you hold vol down and power? I had the same problem with my infinity when the .18 update came out, i had a freeze and a crash during normal use while the update was either downloading or changing something and when it restarted I couldnt do anything but go into APX. I never unlocked it (mainly because the asus tool wouldnt work) but I had to RMA to get it fixed. If you can at least get to the recovery menu you can try reinstalling the stock rom from an mSD. Otherwise you may have to do the same as me and RMA and hope that they dont tell you tough luck since its unlocked As far as I know the only way to recover the tablet when APX is your only option is with NVFlash, which I never installed because .30 was on my infinity when i bought it.

jeremiah.wells said:
I couldn't get either recovery to boot and so I attempted a data wipe
Click to expand...
Click to collapse
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).

_that said:
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
Click to expand...
Click to collapse
Yes, with only APX available but no NvFlash backup, there's very little to no light at the end of the tunnel. I also wondered why the reports of RMA'd users mention a motherboard change, but I do remember something about unit-specific code being backed up with NvFlash. Although I'd think it strange, it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
@OP: with no fastboot available, you will not be able to follow either Scott's guide or reflash a recovery. I sincerely feel for you, especially since it was enthusiasm that got you into trouble. I know the resultant feeling, and I hate it, for it quells said enthusiasm in the future and make you overly cautious. I wish you a speedy and effective RMA!

jeremiah.wells said:
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Click to expand...
Click to collapse
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.

I feel for you too as this happened to me even without any type of modifications to my recovery or bootloader! As far as RMA and the motherboard change I am not sure whether they recovered my device without an actual change. When i got it back from RMA it was on the same firmware as before (not the most recent at the time) as well as retaining the same SN on my device. Since I got it back though I am unable to use the unlocker tool. I get that network error and a refusal from the asus unlock server that lots of people were having issues with a while back. I am in touch with Asus service now, but asus service is usually a long arduous process! I hope that they dont charge you for the replacement, but seeing as you unlocked its very possible if you have any sort of insurance from your credit card that may be a better route by trying to replace it as a lost or broken unit. My RMA was free (except shipping) but again, no unlock!
best of luck.

MartyHulskemper said:
it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
Click to expand...
Click to collapse
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.

_that said:
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
Click to expand...
Click to collapse
In cases like this, I always hope you get a motivated technician that actually hunts down your serial from that database and helps you out. Guess I'm a bit naive in that regard.
Yeah, those 16 bytes keeping the door shut are a major bummer, as is the fact that NvFlash was not pre-installed anyway...

okantomi said:
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
Click to expand...
Click to collapse
To answer your curiosity, NO... I did not install or use Rom Manager in any way to get to this state.

Got a question. Mine is rooted but locked, i attempted to install TWRP before unlocking. I can still boot it up but i cant get into recovery. Can i unlock it without a working recovery and just reinstall TWRP? what are my options? Any help would be great.
edit: nevermind, i think i found the answer...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Why so many soft bricks and recovery problems?

I've never seen a two day span where I've seen this many near bricks and recovery problems. Its starting to look like the TF300 fiasco. Did CWM screw something up recently or are all these user problems unrelated and coincidental?

elfaure said:
I've never seen a two day span where I've seen this many near bricks and recovery problems. Its starting to look like the TF300 fiasco. Did CWM screw something up recently or are all these user problems unrelated and coincidental?
Click to expand...
Click to collapse
It is mostly user problems, but CWM can brick your device by wiping the wrong partition. TWRP has been patched and wont do this. AKA why TWRP is recommended, rather than CWM, which is a good recovery, but for our device it can cause issues. And if you read, 99% of the bricks are recovered. So the point of the bricks is nothing, it is if we can recover them or not, to which most are, which is a wonderful thing. 10 TF300s a day were bricking, this is not occurring with the TF700, so there is no fiasco happening here .
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.

_that said:
Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.
Click to expand...
Click to collapse
As a newbie, I may suggest that the Tylorw1 remarks could be announced on the http://forum.xda-developers.com/showthread.php?p=30223822#post30223822 topic (regarding that it is advised to use TWRP until CWM will be patched). Because I parsed all this topics and others before starting to flash my TF700 and never seen that recommandations and the other like "do not use software launch of recovery". Those information, you can only get them on the topic you look at once you have had an issue.
I was not totally a newbie with switching to developer mode / rooting / flashing, since I began doing this on my HTC magic, continued with an HTC desire HD, then a galaxy note. Never got those hard troubles (once I had a fear, but has been able to unlock it alone with my magic).
At last, that's very good you're here to help us after our mistakes!

The problem is that there are a lot of (stupid) people who can't bloody read.

florck said:
At last, that's very good you're here to help us after our mistakes!
Click to expand...
Click to collapse
I must be honest: I fear the day _that transitions to another device. The work he put in in your case is nothing short of amazing (to me). We all have our perks and qualities, but... pfff...
On-topic: it does seem like we are having more bricks and recovery/boot problems lately. Is that a market thing? Has the 700 gone done in price, thus reaching a greater user base? (Not to my knowledge.) Are we seeing more inexperienced users now than we did at first? (That might be a likely cause.)

_that said:
Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.
Click to expand...
Click to collapse
Well put. We have two ears and two eyes and two hands but only one mouth. Intelligent people tend to use their senses in those proportions. Only after they have mastered this can they attempt to use their brains.

MartyHulskemper said:
I must be honest: I fear the day _that transitions to another device. The work he put in in your case is nothing short of amazing (to me). We all have our perks and qualities, but... pfff...
On-topic: it does seem like we are having more bricks and recovery/boot problems lately. Is that a market thing? Has the 700 gone done in price, thus reaching a greater user base? (Not to my knowledge.) Are we seeing more inexperienced users now than we did at first? (That might be a likely cause.)
Click to expand...
Click to collapse
I'm going to be the first to second @florck 's suggestion to top-sticky a warning about CWM with a statement that it could wipe the wrong partition and leave the user SOL (maybe not in those exact words) and for XDA to point a suggestion towards using TWRP (touch) instead as a safe alternative. At least until CWM patches this bug. This would be paramount for new users to read. I found it during my rooting research but I agree that its fairly buried.
[Edit] One thing to note is he was not using an "old" CWM, in fact it was a future developer version not even released yet?? So the masses haven't even seen this version yet. Someone should inform CWM about this before they release it, it if came from them broken. I don't think I'll ever be using their recovery after seeing what can happen.
*************************************************************************
Quote @Pretoriano80 from other thread: "CWM 6.0.5.3?The latest official version is 6.0.3.0 iirc. AFAIK this kind of brick occur when using an" old" recovery (both CWM and TWRP) with the new bootloader and is triggered when the Wipe Data option it's used."
***************************************************************************
I'm also interested in learning how his cryptographic key got messed up/deleted. I've been wondering if this could be used for a bootloader exploit to enable NVflash?
Lucky for @florck to have @_that for sure as we all are, but also lucky for him he wasn't that much of an inexperienced user that he couldn't at least access a terminal and type some commands, run an adb shell, and follow instructions. He seemed to be a pretty good student but he should have read more I agree.
I find there are three types of people. Dumb people who never learn from their mistakes, smart people who do learn from their mistakes, and then there's the wise people who learn from *other peoples* mistakes.
For me as a fairly inexperienced user getting to ride the roller coaster and see the guts of a near brick was fascinating to say the least. Its good to know about these things before you need to. Its great to know @_that if you don't. His knowledge and troubleshooting prowess is phenomenal. Rare breed indeed. It wouldn't surprise me if he didn't have a mother and was beamed down.

Guys, i think you are mixing stuff here, let me explain.
1)The "wipe data/media" option in CWM
This bug can lead to a corrupted partition but it's easy to recover by installing the Stock Firmware from MicroSD with CWM recovery (yes CWM install option will still work because the staging partition is not corrupted). After the install process is complete and the tablet rebooted once you can use the Wipe Data option from the Bootloader menu, that procedure will also fix your corrupted data/media partition.
So as you can see no ADB knowledge or other skills are required in order to recover your device.
2) Using and "old" recovery version with an incompatible bootloader (both CWM and TWRP recovery)
Using the Wipe Data option from the Bootloader menu under this circumstances could lead to a bootloop to Recovery and if you don't have good ADB knowledge/skills (or if _that it's not around ) you are doomed. Anyway it seems that as long as you still have ADB you can recover from this too.
Also some users reported a hard brick under this circumstances (bootloader signature mismatch error) but there wasn't much background info from the users on the matter.
ONLY way to recover from this issue is by sending the device back to Asus and pay for repairs.
3) Regarding the missing token my understanding is that a wrong offset was used so i presume that using the correct offset you will find that the token is still there.
And even if someone could remove the token it would still be impossible to trick Asus because they already have your device's serial number on their server.
P. S: I already planned to update the AIO thread with the latest stuff /info but i've just got recovered from a knee surgery so i'm not in the mood yet.
Using
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Thanks for the very clear play-by-play problem descriptions and future resolutions of what recently happened with the one user's near brick who then witnessed the miracle of _that in action. It'll be good for CWM users if it comes up again so they can self-resolve their problem with your instructions.

[Q] asus unlock tool error TF700

hello having issue with asus unlock tool
either by using abt tool or direct from asus , unlock tool installed on pad, when I go and run it get message that says "unknown error occurred , which may be a network error please try later"
running jelly bean 4.2.1 build 10.6.1.14.8
also noticed in my setting i have no tab for developers option I was able to activate the usb dubbing but in different way
can any one advise

b4316207 said:
hello having issue with asus unlock tool
either by using abt tool or direct from asus , unlock tool installed on pad, when I go and run it get message that says "unknown error occurred , which may be a network error please try later"
running jelly bean 4.2.1 build 10.6.1.14.8
also noticed in my setting i have no tab for developers option I was able to activate the usb dubbing but in different way
can any one advise
Click to expand...
Click to collapse
I read a few stories about this issue because somehow the devices' serials do not match the ASUS's server in order to register your device. I was lucky on the first try with the unlock tool. To answer your second question, 1. go to your setting, 2. click on the About Tablet and find the Build Number. 3. Just click on the Build Number about 7 or 8 times to enable the Developer Option. Good luck

b4316207 said:
hello having issue with asus unlock tool
either by using abt tool or direct from asus , unlock tool installed on pad, when I go and run it get message that says "unknown error occurred , which may be a network error please try later"
running jelly bean 4.2.1 build 10.6.1.14.8
also noticed in my setting i have no tab for developers option I was able to activate the usb dubbing but in different way
can any one advise
Click to expand...
Click to collapse
You cannot unlock through ADB. You have to use the Asus Unlock Tool.
Keep trying. Many users needed 5,6,7 or more attempts to get it to work. And yes, there could be a problem with your S/N not being registered in their database.
Try to sign up for Asus device tracker. That will tell you if your S/N is registered with them. If not, call Asus about a problem signing up for device Tracker, NOT about your inability to unlock!
They do not support unlocking and won't help you to do so.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Having just been through this, what berndblb said.
After several goes I managed to get the DeviceTracker to work. Some things which may or may not have helped get it to work:
Login to Asus support site and check device is registered (it was). Maybe logging in 'poked' it to update an active flag or something?
Update and go into Google Maps app on the pad, there's a new disclaimer screen that needed to be OKd
Update and go into Google+ app on the pad. Some of Google's location services (e.g. latitude) seem to have been moved to that. No idea if it's relevant for what Asus use but hey.
Logged in to the DeviceTracker using Google. My Asus account login wouldn't work.
The serial number entry just worked, and added TF201 to a dropdown at the top, then located my device.
Then Asus' unlock app on the pad (which was still open after getting the error before) worked straight off and asked for Google password.
HTH, I was about to give up and call Asus support which wasn't going to go well.

mamoulian666 said:
Having just been through this, what berndblb said.
After several goes I managed to get the DeviceTracker to work. Some things which may or may not have helped get it to work:
Login to Asus support site and check device is registered (it was). Maybe logging in 'poked' it to update an active flag or something?
Update and go into Google Maps app on the pad, there's a new disclaimer screen that needed to be OKd
Update and go into Google+ app on the pad. Some of Google's location services (e.g. latitude) seem to have been moved to that. No idea if it's relevant for what Asus use but hey.
Logged in to the DeviceTracker using Google. My Asus account login wouldn't work.
The serial number entry just worked, and added TF201 to a dropdown at the top, then located my device.
Then Asus' unlock app on the pad (which was still open after getting the error before) worked straight off and asked for Google password.
HTH, I was about to give up and call Asus support which wasn't going to go well.
Click to expand...
Click to collapse
I hate Asus support... They swear the "unlock device tool" has nothing to do with the device tracker. I have been on the phone for 1.5 hrs now with them and they say the device tracker has been having issues for a week! Asus NO SUPPORT!

What worked for me....finally
I went through a lot of posts and other forums with users having issues with the tool. I've read it relies on the Device Tracker but couldn't get that to work. After trying everything posted in this forum and doing a reset (no longer rooted) I still couldn't get v7 or v8 to work for my tf700. I contacted ASUS support via email and they replied this morning. They sent me a link to a v7 .apk and it worked with no issues. I was very happy to see them helping me do this even though it would then void the warranty. Here is what they sent me, including full text as to give all credit to them:
"Thank you for contacting ASUS Customer Service.
My name is Emma and it is my pleasure to help you with your problem.
I will do our utmost to assist you in resolving this matter, I apologize for the trouble you seem to be experiencing with the device.
Could you please check whether the unlock tool you downloaded is right first and then accomplish it through the steps I sent to you.
URL omitted due to me being new user. Search for the "Version V7" and File Size should show "613.54 (KBytes) 2012/07/25 update"
Please install this apk and follow the below steps to unlock device
1.Launch “Unlock Device” on your app menu
2.Read and check the description, Press “OK”
3.Check “agree” and press “Press to unlock your device”
If you still can not unlock it, could you please provide the wifi mac address for me?
Have a great day!
Once again, thanks for choosing ASUS products.
Welcome to refer Troubleshooting & FAQ for ASUS products in ASUS website:
If you continue to experience issues in the future, please do not hesitate to contact us.
An email survey will be sent to you within the next 5 days. Please be sure to rate the service I provided to you today.
Best Regards,
Emma
ASUS Product Support Team
888-678-3688"
I created an account here in hopes this .apk will help someone else get the tool working to allow further enjoyment on the tf700 as I plan to do.
Thanks all!

kalel28 said:
I went through a lot of posts and other forums with users having issues with the tool. I've read it relies on the Device Tracker but couldn't get that to work. After trying everything posted in this forum and doing a reset (no longer rooted) I still couldn't get v7 or v8 to work for my tf700. I contacted ASUS support via email and they replied this morning. They sent me a link to a v7 .apk and it worked with no issues. I was very happy to see them helping me do this even though it would then void the warranty. Here is what they sent me, including full text as to give all credit to them:
"Thank you for contacting ASUS Customer Service.
My name is Emma and it is my pleasure to help you with your problem.
I will do our utmost to assist you in resolving this matter, I apologize for the trouble you seem to be experiencing with the device.
Could you please check whether the unlock tool you downloaded is right first and then accomplish it through the steps I sent to you.
URL omitted due to me being new user. Search for the "Version V7" and File Size should show "613.54 (KBytes)2012/07/25 update"
Please install this apk and follow the below steps to unlock device
1.Launch “Unlock Device” on your app menu
2.Read and check the description, Press “OK”
3.Check “agree” and press “Press to unlock your device”
If you still can not unlock it, could you please provide the wifi mac address for me?
Have a great day!
Once again, thanks for choosing ASUS products.
Welcome to refer Troubleshooting & FAQ for ASUS products in ASUS website:
If you continue to experience issues in the future, please do not hesitate to contact us.
An email survey will be sent to you within the next 5 days. Please be sure to rate the service I provided to you today.
Best Regards,
Emma
ASUS Product Support Team
888-678-3688"
I created an account here in hopes this .apk will help someone else get the tool working to allow further enjoyment on the tf700 as I plan to do.
Thanks all!
Click to expand...
Click to collapse
Well! Good news! Either they changed their policy towards unlocking or you were lucky to deal wiith a very responsive rep.
I wouldn't be surprised if they leighten up on unlocking now. Lots of Tf700s are at the end of their warranty anyway - no skin off their back anymore....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Well! Good news! Either they changed their policy towards unlocking or you were lucky to deal wiith a very responsive rep.
I wouldn't be surprised if they leighten up on unlocking now. Lots of Tf700s are at the end of their warranty anyway - no skin off their back anymore....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
I am dealing with Emma now. She seems helpful. I used the Asus Device Tracker not working after an RMA tactic and then she asked for my MAC address. Im pretty happy.
This tab is nearly useless unless you ROM it.
Thanks for the post. I will report back if it works.

Emma updated their servers! Last night I was trying to unlock via the app and VOILA! FINALLY after hundreds of attempts my tablet is unlocked! Fun times ahead!

echardcore said:
Emma updated their servers! Last night I was trying to unlock via the app and VOILA! FINALLY after hundreds of attempts my tablet is unlocked! Fun times ahead!
Click to expand...
Click to collapse
Time to update your signature!

Still not working
mamoulian666 said:
Having just been through this, what berndblb said.
After several goes I managed to get the DeviceTracker to work. Some things which may or may not have helped get it to work:
Login to Asus support site and check device is registered (it was). Maybe logging in 'poked' it to update an active flag or something?
Update and go into Google Maps app on the pad, there's a new disclaimer screen that needed to be OKd
Update and go into Google+ app on the pad. Some of Google's location services (e.g. latitude) seem to have been moved to that. No idea if it's relevant for what Asus use but hey.
Logged in to the DeviceTracker using Google. My Asus account login wouldn't work.
The serial number entry just worked, and added TF201 to a dropdown at the top, then located my device.
Then Asus' unlock app on the pad (which was still open after getting the error before) worked straight off and asked for Google password.
HTH, I was about to give up and call Asus support which wasn't going to go well.
Click to expand...
Click to collapse
--------------------------------------------------
Hi! Thank you, I used the gmail account and the tracker worked !!! But, I still can't unlock my device. I can receive any updates. But the unlock tool still gives me the network erros message. What else can I do ?
Thank you!

please help!!!!!!!!!!!!
I have been reading the transformer forum and was directed here to see if there was any solution. I am having the same problem.
I call ASUS and both customer services reps. would not help me because they said my device is unlocked. My device is not unlocked. The first rep hung up on me and when I called back the second rep told me because the computer is saying my device is unlocked then they cannot help. they want me to send it back to them so that they can charge me (which by the way is alot) to fix the problem instead of changing my status in their computer and registering me with ASUS device tracker.
I tried to register with ASUS device tracker and it tells me the command failed.
Is there any way to get help now because I really want to root or is there a way to root without unlocking the tablet?:fingers-crossed:

mmgetthersjr56:
I saw this info at devicetracker.asus.com. I did the .10 update OTA and never saw anything indicating it didn't take. Later on, not because I saw this info because I hadn't yet, I downloaded .10 from Asus and flashed it from my sdcard. But the other day when I wanted to make sure the device tracker would find me I saw this when I clicked the UPDATE LIST option:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So now I wonder is this possibly what is keeping me from being able to unlock the damn thing? Would rolling back to .8 and then taking an OTA to .10 clear this data and thus allow me to unlock?
You might want to go back to the device tracker and see if your info on this page is indicating like mine is. It MIGHT be what OUR unlocking problem is but I'm not sure about that.

mmgethersjr56 said:
I have been reading the transformer forum and was directed here to see if there was any solution. I am having the same problem.
I call ASUS and both customer services reps. would not help me because they said my device is unlocked. My device is not unlocked. The first rep hung up on me and when I called back the second rep told me because the computer is saying my device is unlocked then they cannot help. they want me to send it back to them so that they can charge me (which by the way is alot) to fix the problem instead of changing my status in their computer and registering me with ASUS device tracker.
I tried to register with ASUS device tracker and it tells me the command failed.
Is there any way to get help now because I really want to root or is there a way to root without unlocking the tablet?:fingers-crossed:
Click to expand...
Click to collapse
Contact Asus support by email and send them a picture of your boot screen. If it doesn't say: "This device is unlocked" - it's not unlocked.....
You can root without unlocking by downgrading to 10.6.1.14.8 firmware and rooting it with the Motochopper tool. But you cannot run a custom rom without unlocking it.

berndblb said:
Contact Asus support by email and send them a picture of your boot screen. If it doesn't say: "This device is unlocked" - it's not unlocked.....
You can root without unlocking by downgrading to 10.6.1.14.8 firmware and rooting it with the Motochopper tool. But you cannot run a custom rom without unlocking it.
Click to expand...
Click to collapse
I went through the same run-around with Support - they said it was unlocked when it wasn't. I sent them a screenshot capturing my serial number and MAC address at their request, they still said it was unlocked, and then miraculously/luckily the next unlock I tried worked. They would not admit to changing anything on their side. The whole process and their stance on it is absurd. I love the tablet now that I have CROMi-x on it and my Nexus 7 is a great device but dealing with Asus has really soured me on them.

I got a call today from someone at asus that wanted to know about a survey I took after they sent me an RMA for the unlocking problem. They wanted to know why I gave them a bad rating. I told them they were unwilling to fix my issue which really does not need to have the tablet returned to them for repair. I told him what I was trying to do and got the same bs answer about not supporting unlocking of the device. So I said asus can kiss my posterior and will get no more of my money nor any recommendations for products to anyone I do work for or know. Told him asus was more concerned about my bad survey comments than making an impression on a customer by extending a helping hand by going the extra mile.
Since there is nothing you can do or are willing to do goodbye. I hung up the phone.
I will bad mouth Asus every chance I get everywhere I go when the topic arises. I'm not going to wear you people out about it but no one will ever hear me say anything good about Asus ever again. Sorry for whoever may find this unsavory but I really did want to unlock and run a good ROM on my tablet and I am very upset that it cant be done all because of Asus's attitude towards unlocking and bad records.
Merry Christmas to all!

trouble with unlocking ASUS TF700T
berndblb said:
Contact Asus support by email and send them a picture of your boot screen. If it doesn't say: "This device is unlocked" - it's not unlocked.....
You can root without unlocking by downgrading to 10.6.1.14.8 firmware and rooting it with the Motochopper tool. But you cannot run a custom rom without unlocking it.
Click to expand...
Click to collapse
Thank you everyone for your responses.
flhthemi - I had the very same experience and they completely ignored my concerns. I will never buy or recommend ASUS to anyone because it really is the principle of a big corporate company just selling a product and customer service does not count.
sparksd - I called and have yet to have them correct the problem because they believe that my device is unlocked and I am a liar.
berndblb - How do I downgrade and not brick my device. I have tried to do this and it never works and then my device becomes bricked. I have tried multiple ways suggest on this site and other for ASUS TF700T but have had no success. so if you could please point me to the one method that is a sure fire way to this then I would appreciate it. Also I know about the nvflash but I have yet to have it work for me.
Again thank you all for your help. It is really appreciated that there are still people that are so willing to help and give sound advice.

mmgethersjr56 said:
berndblb - How do I downgrade and not brick my device. I have tried to do this and it never works and then my device becomes bricked. I have tried multiple ways suggest on this site and other for ASUS TF700T but have had no success. so if you could please point me to the one method that is a sure fire way to this then I would appreciate it. Also I know about the nvflash but I have yet to have it work for me.
Again thank you all for your help. It is really appreciated that there are still people that are so willing to help and give sound advice.
Click to expand...
Click to collapse
Downgrading should not put you into any jeopardy of bricking! It' s all done with the stock recovery and a method build into the stock rom - what did you try?
Anyway - you download the .8 firmware for your SKU or region (US, WW, JP)
- you unzip that file once, the result being another zip
- you copy that file to the root of your internal storage
- you should get a notification that the downgrade is available. If you don't: reboot
If that does not work try method 2:
- rename the unzipped zip to EP201_768_SDUPDATE.zip (make sure your PC shows file extensions - you don't want to end up with EP201_768_SDUPDATE.zip.zip)
- load that file into the root of a fat32 formatted microSD, insert the card and boot to recovery
- the recovery should recognize the firmware file and flash it automatically
To boot to recovery you boot up holding Power and Volume Down buttons until you feel the tablet vibrate twice and see tiny script appear. You'll also see three icons: RCK, Android, Wipe Data
RCK is flashing. Push the Volume Up button to enter recovery
Once that is done you download the Motochopper tool and follow the instructions to root the tablet.
http://forum.xda-developers.com/showthread.php?t=2258633
Ignore everything but the numbered instructions in the grey box. It doesn't say so, but the tool works for the TF700 stock JB rom. Naturally you need the Asus drivers for your device - not Samsung as it says there. If you can connect to your tablet in MTP through USB you should be ok.

mmgethersjr56 said:
Thank you everyone for your responses.
....
sparksd - I called and have yet to have them correct the problem because they believe that my device is unlocked and I am a liar.
.......
Again thank you all for your help. It is really appreciated that there are still people that are so willing to help and give sound advice.
Click to expand...
Click to collapse
They didn't come out and call me a liar but they kept telling me mine was unlocked even though it clearly wasn't. Based on the date of when they said mine was supposedly unlocked, it looks like a failed unlock attempt somehow registers as an unlock to them. At any rate, I found their general tone to be the most irritating aspect of this - I felt like they were either calling me a liar or telling me I was too stupid to recognize that my device was unlocked.

I think I am rooted but still no unlock of device
berndblb said:
Downgrading should not put you into any jeopardy of bricking! It' s all done with the stock recovery and a method build into the stock rom - what did you try?
Anyway - you download the .8 firmware for your SKU or region (US, WW, JP)
- you unzip that file once, the result being another zip
- you copy that file to the root of your internal storage
- you should get a notification that the downgrade is available. If you don't: reboot
If that does not work try method 2:
- rename the unzipped zip to EP201_768_SDUPDATE.zip (make sure your PC shows file extensions - you don't want to end up with EP201_768_SDUPDATE.zip.zip)
- load that file into the root of a fat32 formatted microSD, insert the card and boot to recovery
- the recovery should recognize the firmware file and flash it automatically
To boot to recovery you boot up holding Power and Volume Down buttons until you feel the tablet vibrate twice and see tiny script appear. You'll also see three icons: RCK, Android, Wipe Data
RCK is flashing. Push the Volume Up button to enter recovery
Once that is done you download the Motochopper tool and follow the instructions to root the tablet.
http://forum.xda-developers.com/showthread.php?t=2258633
Ignore everything but the numbered instructions in the grey box. It doesn't say so, but the tool works for the TF700 stock JB rom. Naturally you need the Asus drivers for your device - not Samsung as it says there. If you can connect to your tablet in MTP through USB you should be ok.
Click to expand...
Click to collapse
Thank you for these instructions. I did everything correctly and motochopper told me I was rooted but I just need to ask this question. If I am rooted I have access to superuser correct?
Thank you for your time.

[Q] What if NVFlash got updated

Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.

I think you can only install nvflash on not-yet bricked devices!
Sent from my Transformer Pad TF300T using xda app-developers app

vahid_shirvani said:
Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.
Click to expand...
Click to collapse
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/

tobdaryl said:
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/
Click to expand...
Click to collapse
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.

graphdarnell said:
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.
Click to expand...
Click to collapse
Once nvflash is installed what you present is correct (at least that is my understanding - I have only done a simple restore for testing purposes). Look at my signature for a guide to restore with nvflash. The second method presented is what you suggest for the tf101.
The situation to install is different because Asus has locked the tablet to exclude installing nvflash.
I am in the dark as you are. I only know what I can and can't do on my tablet. Otherwise I can pass information provided by others.
My reference is the Nook Tablet. I can delete every partition and rebuild the drive from a blank state this is possible because the tablet can boot from an sdcard.
I had a pm request to provide an nvflash installation guide. I complied but did not present it on xda. The member making the request was pleased and successfully used it to install nvflash. I have since used it to install nvflash on one tablet. Honestly my guide is no better than the guide provided, just a different presentation and can be done by anyone who wishes go step by step through the guide already presented. Just copy and paste the info and do some minor rewording.
I wish I could truly help but I honestly can't. I have come to accept some related info as fact since I have not been able to prove otherwise and have grown tired while chasing dead ends. I don't have the expertise, experience, or hardware to move forward.

As nightmares go, this one is bad. [JB bootloader]

Hey guys,
I'm smack dab in the middle of a damn nightmare:
I sent in my tablet for RMA(broken digitizer). During this time i discover the sweet world of rooting and fell in love with Cyan11. I planned to unlock, flash, flash and then enjoy my tablet to the fullest because i wanted something new(and the stock ROM was getting tedius...And its a buggy and/or slow piece of S***).
Finally i got my tablet in the mail and did something stupid:I downloaded the OTA update. I then installed the tool and ran it but i got the infamous "An unknown error occurs, which may be a network connection issue. please try again later". Tried everything i could: reseting...thats about it.
I want to ask is there a possibility that the tool may work if i down grade to an earlier build of 4.2.1 or jump directly to 4.1?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Asus Tranfsformer pad tf300t
Android 4.2.1
Build: US 10.6.1.27.5-20130902

cooljoe30 said:
Hey guys,
I'm smack dab in the middle of a damn nightmare:
I sent in my tablet for RMA(broken digitizer). During this time i discover the sweet world of rooting and fell in love with Cyan11. I planned to unlock, flash, flash and then enjoy my tablet to the fullest because i wanted something new(and the stock ROM was getting tedius...And its a buggy and/or slow piece of S***).
Finally i got my tablet in the mail and did something stupid:I downloaded the OTA update. I then installed the tool and ran it but i got the infamous "An unknown error occurs, which may be a network connection issue. please try again later". Tried everything i could: reseting...thats about it.
I want to ask is there a possibility that the tool may work if i down grade to an earlier build of 4.2.1 or jump directly to 4.1?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Asus Tranfsformer pad tf300t
Android 4.2.1
Build: US 10.6.1.27.5-20130902
Click to expand...
Click to collapse
HI cooljoe30,
Can you specify the "tool" , and it seems like you're in the right position to move towards KK. I can't tell what's you problem please be clear.

b..c said:
HI cooljoe30,
Can you specify the "tool" , and it seems like you're in the right position to move towards KK. I can't tell what's you problem please be clear.
Click to expand...
Click to collapse
Sure. Asus's site is really wired but basically you go here:
service asus com/#!downloads/c1wax
and navigate to the tf300t download page.
Select android
Select utilities and its the 3rd option from there.
Thanks.

cooljoe30 said:
Sure. Asus's site is really wired but basically you go here:
service asus com/#!downloads/c1wax
and navigate to the tf300t download page.
Select android
Select utilities and its the 3rd option from there.
Thanks.
Click to expand...
Click to collapse
Ok cooljoe30, so I took and from what I see you tried to use the unlock bootloader app vr8 android 4.2? Is that correct? Also I would like to know what you meant by downloading the ota update?

cooljoe30 said:
Hey guys,
I'm smack dab in the middle of a damn nightmare:
I sent in my tablet for RMA(broken digitizer). During this time i discover the sweet world of rooting and fell in love with Cyan11. I planned to unlock, flash, flash and then enjoy my tablet to the fullest because i wanted something new(and the stock ROM was getting tedius...And its a buggy and/or slow piece of S***).
Finally i got my tablet in the mail and did something stupid:I downloaded the OTA update. I then installed the tool and ran it but i got the infamous "An unknown error occurs, which may be a network connection issue. please try again later". Tried everything i could: reseting...thats about it.
I want to ask is there a possibility that the tool may work if i down grade to an earlier build of 4.2.1 or jump directly to 4.1?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Asus Tranfsformer pad tf300t
Android 4.2.1
Build: US 10.6.1.27.5-20130902
Click to expand...
Click to collapse
The only way I've got it to work was after I register the tablet with asus. After that you have to wait more or less one day and then try again.
If that doesn't do the trick, and since you have RMA, maybe you have to contact Asus support so they can tell you what to do.
Make sure you got the right unlock tool from the Asus download page.