Related
Hi,
I recently received my transformer back from service (had Wi-Fi problem). Before warranty repair I had a B70 model. I was told I had a mainboard problem and it was replaced. It came with 8.6.5.21 and unfortunately, I can't root it with any available tool (nachoroot/nvflash/tried all kinds of combinations of ROM downgrading trick).
I tried nachoroot but I get this error on stage2:
"cannot create /data/local.prop: permission denied" and rooting never happens.
I was told this may mean I got a b40-b50 device. But nvflash fails with usb writting which means (afaik) I have a locked boodloader. I've done sbkCheck and it says I got SBK v2:
Chip UID: 0x37c708942bfe197
Detected SBKv2
As bottom line, is this rootable? Any advise on this? Thanks.
try this method and use RazorClaw
http://forum.xda-developers.com/showthread.php?p=20799328
baseballfanz said:
try this method and use RazorClaw
http://forum.xda-developers.com/showthread.php?p=20799328
Click to expand...
Click to collapse
On my previous android I was able to root with this trick. But on this one it's not working to me. I tried all sort of combination with files on internal/sd, had formatted SD card to FAT32 several times with different settings etc. Well, it always find an update but also it always fails to install it - android with yellow exclamation in recovery and unknown error -2 reported when android boots back.
Hey All,
Ill keep this short since it's late and I have been fussing with my tab all day to no avail. I posted on here last month that I got stuck in a bootloop and then was unable to access the recovery menu leading to a full on brick (no nvflash). This happened when my infinity froze in the middle of regular use (day of .18 update). I sent the unit in RMA and just got it back with a replaced system board. I am not too thrilled with the performance + dock issues i seem to have with every JB build so I decided I would unlock and run a custom build. I have done this on my 2 primes so I have some experience.
I got the "unknown error" message about a thousand times while trying to run the unlocker tool (device came back with .16 on it). I decided to downgrade to .30 and try it, but I kept getting the network connection issue. I figured since i was on .30 I would root the device and try and backup the root when I went back to JB. I went up to .18 trying to maintain the root using rootkeeper, wasn't able to keep it. Tried running the unlock tool again and got the same error, but noticed that in my logcat logs (was checking to see if i kept getting the asus server refusal) it wasnt even pinging the server, which led me to thinking maybe the unlock went through after one of those attempts and i just wasnt paying attention (unlikely!)
Now things get a little strange. When I boot my device I see "No certificate to inject" in white text where it would normally say the device is unlocked... I have never seen that before and couldnt find anything through searching. I'm not sure which certificate its talking about and how it disappeared. I am able to access fastboot, and I am able to flash recovery blobs or images for TWRP or CWM. The fastboot prompt shows that the file is sending, and then writing, both successful. When I reboot the device and try and enter recovery I get the stock JB recovery, RCK gives me a sad dead android (assuming i dont have a stock zip on my mSD card).
I would really like to get this functioning with a custom rom. The device still functions normally though, and has no problems going between firmwares and was able to root properly in .30 but now i have a missing certificate which I am guessing is pretty important to all of this (again I have never seen this issue).
I spent about 6 hours on this today, I have done lots of things, wiping data, factory resets, etc... not sure where things are going wrong. I assume the device is in an unlocked state because I am able to use fastboot and successfully write while using the flash command, but I could be wrong.
I appreciate any suggestions or help you guys might have!
Not sure about this you may have to do a little more digging.
Thought I had read about RMA'd tablets being permanently locked for some reason.
I'm not sure if Asus re-serializes the tablet if it had a board replaced.
Does the system serial number match the sticker on the bottom?
If not I'd try registering the tablet with the boards s\n.
Hope you can figure this out.
jallweiss said:
Hey All,
Ill keep this short since it's late and I have been fussing with my tab all day to no avail. I posted on here last month that I got stuck in a bootloop and then was unable to access the recovery menu leading to a full on brick (no nvflash). This happened when my infinity froze in the middle of regular use (day of .18 update). I sent the unit in RMA and just got it back with a replaced system board. I am not too thrilled with the performance + dock issues i seem to have with every JB build so I decided I would unlock and run a custom build. I have done this on my 2 primes so I have some experience.
I got the "unknown error" message about a thousand times while trying to run the unlocker tool (device came back with .16 on it). I decided to downgrade to .30 and try it, but I kept getting the network connection issue. I figured since i was on .30 I would root the device and try and backup the root when I went back to JB. I went up to .18 trying to maintain the root using rootkeeper, wasn't able to keep it. Tried running the unlock tool again and got the same error, but noticed that in my logcat logs (was checking to see if i kept getting the asus server refusal) it wasnt even pinging the server, which led me to thinking maybe the unlock went through after one of those attempts and i just wasnt paying attention (unlikely!)
Now things get a little strange. When I boot my device I see "No certificate to inject" in white text where it would normally say the device is unlocked... I have never seen that before and couldnt find anything through searching. I'm not sure which certificate its talking about and how it disappeared. I am able to access fastboot, and I am able to flash recovery blobs or images for TWRP or CWM. The fastboot prompt shows that the file is sending, and then writing, both successful. When I reboot the device and try and enter recovery I get the stock JB recovery, RCK gives me a sad dead android (assuming i dont have a stock zip on my mSD card).
I would really like to get this functioning with a custom rom. The device still functions normally though, and has no problems going between firmwares and was able to root properly in .30 but now i have a missing certificate which I am guessing is pretty important to all of this (again I have never seen this issue).
I spent about 6 hours on this today, I have done lots of things, wiping data, factory resets, etc... not sure where things are going wrong. I assume the device is in an unlocked state because I am able to use fastboot and successfully write while using the flash command, but I could be wrong.
I appreciate any suggestions or help you guys might have!
Click to expand...
Click to collapse
If you rooted, try to install custom twrp recovery using goomanager from the market, see if it installed.
Just guessing here: I think "no certificate to inject" might be pointing to a root certificate that isn't there.
My guess is that the "certificate to inject" is related to the CER partition that contains the bootloader unlock token, and the device is "half unlocked".
Thanks for the responses.
I've been really busy with work and I also just got a brand new Galaxy S3 that I have been tinkering with. Ill try some of your suggestions in a little bit and let you know whats up. Also the serial number in the OS is the same as my original SN on the box/sticker.
Cheers!
Quick update...
1)Went from .18 back down to .30 no problems. Wiped data/factory reset before downgrade.
2)Rooted in .30 using debugfs method, no problems
3)Verified superuser was working, downloaded goomanager
4)Installed openrecovery twrp blob through goomanager.
5)On restart and trying to access recovery menu recieved "Blob Signature failed" message
6)Device rebooted itself, attempted recovery again. Got Default android recovery with dead droid (removed mSD card so it wouldnt try to re-install firmware) hit power and confirmed its default android system recovery.
7)Flashed twrp.blob from twrp site using adb, which was successful. Restarted and got same result as #5 and #6
8)Flashed newest version of cwm non-touch using adb, which was successful. Restarted and got same result as #5 and #6
Unlock tool still gives the unknown error, and im registering my device on vip.asus.com right now.
Any thoughts? I really appreciate everyone's knowledge on this.
Thanks!
EDIT: Registered with vip.asus.com unlock tool still returns unknown error. The idea of the device being semi-unlocked seems probable at this time... hope i can fix it.
jallweiss said:
4)Installed openrecovery twrp blob through goomanager.
5)On restart and trying to access recovery menu recieved "Blob Signature failed" message
Click to expand...
Click to collapse
Just to explain what you see:
Step 4 copies the blob to the update staging partition.
Step 5 is the bootloader which sees the blob in the update staging partition, checks the signature of the blob (because the device is not unlocked), and refuses to flash the blob to the recovery partition because the signature is not from Asus.
Step 6 therefore boots the stock recovery, because it has not been overwritten by step 5.
Steps 7 and 8 are just variants of step 4. (assuming you were using dd to mmcblk0p4, which is the update staging partition), so they have the same effect. All methods for flashing recovery or kernel require cooperation of the bootloader.
I think you can only continue running the Asus unlock tool from time to time, maybe they fix their server issues.
_that said:
Just to explain what you see:
Step 4 copies the blob to the update staging partition.
Step 5 is the bootloader which sees the blob in the update staging partition, checks the signature of the blob (because the device is not unlocked), and refuses to flash the blob to the recovery partition because the signature is not from Asus.
Step 6 therefore boots the stock recovery, because it has not been overwritten by step 5.
Steps 7 and 8 are just variants of step 4. (assuming you were using dd to mmcblk0p4, which is the update staging partition), so they have the same effect. All methods for flashing recovery or kernel require cooperation of the bootloader.
I think you can only continue running the Asus unlock tool from time to time, maybe they fix their server issues.
Click to expand...
Click to collapse
Thats what I was thinking when I saw what was going on. I guess that flashing using adb, goomanager, or fastboot was successful on all the attempts because of rooting and not unlocking? I figured if the device was fully locked that any type of flash to any partition would return an error saying that it was unable to write. Is there a way that I can flash over the bootloader so that it doesnt restore the stock recovery every time (assuming its able to write on that partition)?
I've been in touch with Asus support with the guy who handled my RMA. He told me to register the device which I did yesterday, but the unlock tool still isnt working, and the log still shows that my asus connection is refused. At the same time when I run the unlock tool it did generate a text file saying "Device unlocked at such and such date and time" will that file generate even on an unsuccessful unlock?
Thanks again for your response.
I doubt it will help solve my unlocking problem, but here are my logs (filtering to see the keyboxservice while running unlock tool)
Code:
W/ActivityManager( 224): Scheduling restart of crashed service com.asus.wvdrm/.KeyBoxService in 5000ms
I/ActivityManager( 224): Start proc com.asus.wvdrm for service com.asus.wvdrm/.KeyBoxService: pid=8937 uid=1000 gids={3003, 1015, 3002, 3001, 3007}
D/KeyBoxService( 8937): === onCreate()
D/KeyBoxService( 8937): === onStartCommand(), intent=null, flags=2, startId=35
D/KeyBoxService( 8937): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 8937): === OTA BEGIN
E/KeyBoxService( 8937): === Connection to http://wvdrm.asus.com refused
D/KeyBoxService( 8937): === Retry after 60 seconds.
D/KeyBoxService( 8937): === OTA END
D/KeyBoxService( 8937): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 8937): === OTA BEGIN
E/KeyBoxService( 8937): === Connection to http://wvdrm.asus.com refused
D/KeyBoxService( 8937): === Retry after 300 seconds.
D/KeyBoxService( 8937): === OTA END
D/KeyBoxService( 8937): === onStartCommand(), intent=Intent { cmp=com.asus.wvdrm/.KeyBoxService }, flags=2, startId=36
D/KeyBoxService( 8937): === StatusCode: SC_UNAUTHORIZED!
D/KeyBoxService( 8937): === OTA BEGIN
D/KeyBoxService( 8937): === onStartCommand(), intent=Intent { cmp=com.asus.wvdrm/.KeyBoxService }, flags=2, startId=37
D/KeyBoxService( 8937): === OTA END
D/KeyBoxService( 8937): === StatusCode: SC_UNKNOWN!
D/KeyBoxService( 8937): === Nothing To Do!
D/KeyBoxService( 8937): === onDestroy()
EDIT: Just thought I would check to see if it was related. Im running .30 and I went into system information and hit the button to check for an update for the firmware which ended up saying there is no new firmware updates for my system. Im guessing this means that OTA is not functioning which I had heard was an issue with units returning from RMA (happened on my prime after an RMA but I could still unlock it). Hopefully Asus service may have a solution because at this point I don't think there is much I can do. Unless there was a solution that I missed while searching those old threads
jallweiss said:
Thats what I was thinking when I saw what was going on. I guess that flashing using adb, goomanager, or fastboot was successful on all the attempts because of rooting and not unlocking? I figured if the device was fully locked that any type of flash to any partition would return an error saying that it was unable to write. Is there a way that I can flash over the bootloader so that it doesnt restore the stock recovery every time (assuming its able to write on that partition)?
Click to expand...
Click to collapse
The bootloader does not restore the stock recovery. You cannot flash the bootloader, kernel or recovery directly (they don't even have corresponding entries in /dev/block) - you can only write a signed blob to the staging partition (mmcblk0p4). The blob contains one or more partition images and a digital signature. The bootloader checks the signature, and only if it is correct it copies the image to the correct partition(s).
So anyone with root access can write anything to the staging partition, but only the bootloader decides if and what will be flashed to the system-critical locations. And without unlocking, it accepts only blobs signed by Asus.
btw, I am not sure if wvdrm has anything to do with unlocking or OTA updates - I remember I also got lots of these "connection refused" messages, but I still was able to unlock.
_that said:
The bootloader does not restore the stock recovery. You cannot flash the bootloader, kernel or recovery directly (they don't even have corresponding entries in /dev/block) - you can only write a signed blob to the staging partition (mmcblk0p4). The blob contains one or more partition images and a digital signature. The bootloader checks the signature, and only if it is correct it copies the image to the correct partition(s).
So anyone with root access can write anything to the staging partition, but only the bootloader decides if and what will be flashed to the system-critical locations. And without unlocking, it accepts only blobs signed by Asus.
btw, I am not sure if wvdrm has anything to do with unlocking or OTA updates - I remember I also got lots of these "connection refused" messages, but I still was able to unlock.
Click to expand...
Click to collapse
very interesting, I have a lot of experience with PCs and some specialty computers but I did not know exactly how the staging partition was handled by the bootloader, thanks for that info. As far as those wvdrm related instances in the logs, I see them with some other tasks associated, but the key handler is what i see consistently return an error when using the unlock tool.
Also I just heard back from the Asus rep Carl who had worked with me on 2 previous RMA cases (Prime and Infinity), I went from being called by name to "Dear Valued Customer," and he told me I should RMA the unit again. Based on what I have read on the forums about people RMAing for unlock issues and knowing they wont unlock it in the service center, I really doubting this is any sort of solution. I replied asking to get into contact with either a service manager or being put in touch with a technician or engineer who actually has some sort of access to the servers responsible for tracking SNs or the unlock manager. I doubt I will get anywhere with it but its worth a shot right?
Until then I think im just going to stick to ICS, .20 was just as unstable as .16 and .18 for me, constant crashes and horrible performance. I still love my infinity, but I just feel very constrained and unsatisfied now
If anyone has any contacts within the depths of Asus I would love to talk to them though so that my serial number isnt on the unlocker S#!tList anymore
cheers
asus?!?
jallweiss said:
very interesting, I have a lot of experience with PCs and some specialty computers but I did not know exactly how the staging partition was handled by the bootloader, thanks for that info. As far as those wvdrm related instances in the logs, I see them with some other tasks associated, but the key handler is what i see consistently return an error when using the unlock tool.
Also I just heard back from the Asus rep Carl who had worked with me on 2 previous RMA cases (Prime and Infinity), I went from being called by name to "Dear Valued Customer," and he told me I should RMA the unit again. Based on what I have read on the forums about people RMAing for unlock issues and knowing they wont unlock it in the service center, I really doubting this is any sort of solution. I replied asking to get into contact with either a service manager or being put in touch with a technician or engineer who actually has some sort of access to the servers responsible for tracking SNs or the unlock manager. I doubt I will get anywhere with it but its worth a shot right?
Until then I think im just going to stick to ICS, .20 was just as unstable as .16 and .18 for me, constant crashes and horrible performance. I still love my infinity, but I just feel very constrained and unsatisfied now
If anyone has any contacts within the depths of Asus I would love to talk to them though so that my serial number isnt on the unlocker S#!tList anymore
cheers
Click to expand...
Click to collapse
i am dealing with a very similar situation here! i paid $600 on the tablet, then RMA it for another $200 and got a tablet which cannot be unlocked anymore. my fault! should have never gone with asus (their technical stuff looked good on paper but i disregarded other "details"...)
got two new samsung tablets and they're working great. will never EVER buy an asus device in my life!
PS
I also think that google is smoking to use asus for their new tablet... all the people i know avoid asus at ALL COST
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
In that case I'll give ya $100 for it.
Sent from my Galaxy Nexus using Tapatalk 2
zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unfortunately, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thread that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before via HOT LINE but without any response!) This tablet is really a piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Well my friend not exactly the best words to start with if needing help from the many fine members of this forum.
The unlock tool will eventually work if that's what you want to do.
Personally your being "really ugly" to Asus thru e-mail could be why they remain unresponsive.
If you could perhaps take the calm approach those trying to help would be much more willing.
absurd paradox
Unfortunately I can understand where all these negative feelings derive from.
I am the rightful owner of a tf700 too.
To be quite frank (and I won't surprise anyone), I am not pleased.
There is no reason why I can't enjoy a smooth and flowing experience.
There is no reason why in order to make the best out of the tf700 it is recommended that I flash a custom rom.
I refuse to unlock my tf700 because there is no reason why I should void my warranty, trying to fix it - this is an absurd paradox!
It is about time someone filed a class action in order to stop this "tf700 incident",
so Asus will start to make their excuses in court or maybe solve this unfortunate condition,
once and for good.
cheers.
Nothing stopping you from filing a class action lawsuit is there?
Or you could just take control and unlock and flash a custom ROM and be done with it....
Choice is yours as Asus are not going to help you.
wish it was that simple
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
For example, I read a guide which explains how to unlock and install a custom recovery using an "adb tool",
but there is no explanation how to install the newest version of TWRP, which is required for cromi 3.4.X.
Anyone know a plain and full guide for 10.4.4.25 build?
http://forum.xda-developers.com/showthread.php?t=2088176
No very ugly
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
zrebec said:
OK, that wasn't very ugly mail, just I wrote to ASUS that I tried contact HOTLINE two times and nobody response me I was very frustrated that I cannot unlock my tablet
Can someone explain me, why doesn't exists alternative way around unlock?
The processor is encrypted or what?
Thanks
Click to expand...
Click to collapse
A work around for the unlock isn't available.
Seems as though the key for the bootloader is encrypted very well.
Until someone leaks the key to the internet we're stuck.
My understanding is:
Asus wants the embedded serial for any tablet requesting a bootloader unlock.
The serial is registered with Asus from an outside server database.
Asus voids the warranty then shuts off OTA's because they don't want to push updates over any customisation to the tablets firmware.
This would most likely result in a bricked\non-functioning device.
Asus knows people inherently re-code devices with non-manufacturer firmware and risky applications.
The manufacturer is saying to the buyer we can't be responsible for user induced damage.
zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Another woe-is-me post! Someone please get me a hankie, quick!
zrebec said:
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
Click to expand...
Click to collapse
First of all you could use the search button
Here is a thread where I specified how I got my tablet unlocked: http://forum.xda-developers.com/showthread.php?t=2146543
Just keep in mind that the Asus Support employees are not personally responsible that the MDM-server in Taiwan does not know your tablet. Don't act like a jackass and don't act like mister-know-it-all, then they will help you, like they helped me.
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
Click to expand...
Click to collapse
These forums here provide all information one needs to unlock/ root/ install custom ROMs. I got all information from here and I did not have any problem whatsoever.
You know, people here are willing to share their experience and to help out each other, but the burden to do the work is on you. Also the risk of bricking your device is on you.
Just don't expect anybody to do your work.
As a matter of fact, installing custom ROMs on the TF700 is not trivial. You do need ADB and Fastboot to flash a recovery first. Also you have to have some basic knowledge about how computers work in general and about Android devices.
Even as complete noob, you can find all needed information here. So either you take your time and educate yourself - like I did - or you use the stock ROM or you hire somebody who does the work for you.
Root it but keep it locked! I was loosing sleep at night because I thought I was suckered into believing this was a quality machine and its got tons of glitches, no doubt. But they are mainly lack-of-RAM related. If you root, and disable most of your startups, you can get a clean 500MB after boot, and that makes all the difference in the world, trust me. I was in you boots and was actually dreaming about getting an iPad (please forgive me guys). Honestly, I was sick to my stomach then the rage set in. I decided to learn and root before throwing this POS on ebay or craigs list, and starting over with another brand, probably an Apple, I was so hurt by lack of quality and testing/debug.
Like day and night! Now I love this thing. Hasn't had a random reboot, app crash, etc. in nearly a month now. Before I was getting 5 per day. Its an amazing difference attributed to the OS and apps having room (RAM) to run in. Whoever decided that 1GB RAM for a 4-core droid tablet was enough should be tarred and feathered then shot in the head twice!!! If it had been 2GB instead of 1GB we wouldn't be having this discussion at all.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unlocked! Yay!
Hello dears,
so I have my tablet Unlocked now... I forgot.... You must register account and then register tablet here https://vip.asus.com/login.aspx?. So maybe this can help to someone... OK, I have installed Clean Rom Inherited now and it looks and works fine Thanks to all.
So steps to reproduce:
1) Create account on https://vip.asus.com/login.aspx?.
2) Register device after that
3) Download Unlock Device App: Unlock boot loader from Android -> Utilities from http://support.asus.com/download.as...Pad Infinity TF700T&hashedid=fq2B3oq64av1O95u
4) Run the application
5) Tick the you understand that your warranty is now VOID
6) Type your google account login and password
7) After restart you should see in up-left corner message "Device is unlocked"
8) Enjoy
Update: Fixed my last known problem which was wifi streaming movies to the device from external source (wifi HDD or network connected storage). Got Dice Player, that's all I have to say. Now EVERYTHING is working perfectly. No more random reboots, app issues, conflicting apps, got plenty of RAM, got all my desired startups loaded including System Tuner with a few tweaks added, Browser2RAM, RAM booster, etc. and device runs fast, smooth, and without any "glitches". I finally have achieved rooted stability and will now take a rest and enjoy this tablet a bit before I do anything more to it because this has been a hair-puller to get to this point. Finally very happy with this device but I had to venture far from stock to get here and it was worth it.
By the way, what day of the week is it?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Hi, I have a bricked Tf300t saying Unrecoverable bootloader error (0x000000000) whenever i try to access recovery, cold-boot or wipe.
If i don't go into fastboot, the loading screen will get stuck .. says - Your Device is UnLocked.
It had WW_epad-10.6.1.8-20130225 A03 , when it was working.
Whenever i try to flash recovery using Fastboot:
sending 'recovery' (7500 KB).
OKAY [ 2.762s]
writing 'recovery'...
OKAY [ 2.465s]
finished. total time: 5.227s
Fastboot on tablet freezes, nothing happens.
Any help would be appreciated. Thanks.
I have the exact same problem.
http://forum.xda-developers.com/showthread.php?t=2205158
Let me know if you figure it out
At least im not the only person on this ship hehe.
I tried most of the solutions with no success also, i think next step is to create a bootable sdcard and maybe bootloader works, then repartition the internal directories.
Anyone can confirm if this works before i waste more time trying to boot an sdcard please?
Edit:I updated to JB 4.2.2 before i managed to brick it... also i could't find any bootable android images for external Sd's
Since the latest update, NVFlash is not functional? Please somebody enlighten me with a solution as i use this tablet for work.
Any good news ?
mohlam12 said:
Any good news ?
Click to expand...
Click to collapse
nope we all have the same trouble! holding for a solution
First of all try to reflash the bootloader in fastboot, better yet, flash asus stock rom with fastboot....
It takes a long time and sometimes it looks like the computer freezes but it will work......after that flash the patched trwp recovery for 4.2.1.
If this all works you need to do a "wipe" in the fastboot screen (not recovery)
I have already tried reflashing stock rom with fastboot, and when it's ready fastboot freezes. After that i restart by power button and still same error.
Tomorrow i will try again and leave you some feedback, maybe this time i will be lucky...
Hi again, i just ordered a new mainboard for my tab. Hopefully i will get it running after i replace my board. When the mainboard arrives I will keep you updated with the results
alvinm91 said:
Hi again, i just ordered a new mainboard for my tab. Hopefully i will get it running after i replace my board. When the mainboard arrives I will keep you updated with the results
Click to expand...
Click to collapse
Hi,I have the same situation.Where did you buy the mainboard?And how much you paid?
I'm in the same ship. Any solution??
Unfortunately i had problems with shipping for the motherboard but i managed to order another one yesterday.
I found tf300t 32gb motherboards on ebay for $120 shipped. That is the only known solution at the moment.
Even the local store from where i bought it didn't have a clue how to fix it, so they wanted to ship it to Asus but i declined since software issues are not covered by warranty. Will keep you updated with installation photos when the motherboard arrives. Goodluck guys!
g-member said:
First of all try to reflash the bootloader in fastboot, better yet, flash asus stock rom with fastboot....
It takes a long time and sometimes it looks like the computer freezes but it will work......after that flash the patched trwp recovery for 4.2.1.
If this all works you need to do a "wipe" in the fastboot screen (not recovery)
Click to expand...
Click to collapse
I'd try following this if you haven't already.
Are you flashing the correct blob and whatnot? I'm also assuming you're using the right fastboot commands (fastboot -i 0x0b05 blah blah). Not trying to offend, just seeing exactly what steps you took.
Or perhaps you can flash to an earlier version of the official Asus ROMs.
Yep, i already tried flashing the correct blob, cmd prompt says succeeded but the tab freezes completely.
Earlier version don't work also. The problem is that after wiping the data, bootloader locked itself again. Bug from Asus? dunno but after wiping the data on my tf300 i couldn't flash anything.
Same problem
I have the same problem and after two days of fighting, suppose there are only two solutions: change the motherboard or wait for the NVFLASH to run in APX mode commands like: wheelie / nvflash. I signed the petition to ASUS and we await news. Good Luck.
Hi expertmicro , alvinm91 and all.
I have the same error on my device which is instead an Asus ME301T (the memo smart pad); sorry for jumping in with a post about another device but I tried quite few things to fix it and no luck. The TF300T and the ME301T have anyway similarities as to root it I used a method made for the TF300T and worked fine.
While I'm still searching for a solution, here you can find the ME301T thread, in case you would like to see what I tried.
Even if I don't know what NVFLASH is, if I can help by signing the petion please share the URL where I can do so.
FYI, I found this thread where is shown another method to fix the TF300T: http://forum.xda-developers.com/showthread.php?t=1622628 - don't know if it is applicable you tried it already?
Hi guys,
I solved the problem with the bootloader error (0x0000000) assistance in sending the TF300T. I told him that during the upgrade something must have gone wrong and the OS did not boot anymore. They repaired free of charge. My dealer to whom I entrusted the tablet is Mediaworld (a chain of electronic products Italian). I hope you can serve
I managed to fix mine after beig heavily bricked, hope it works for you
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Good Luck!
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.