Hello all.
I have an Asus TF201 bricked.
I readed a lot of forums, and nothing to do for now.
My Asus was fall in brick after install cwm, and now, only can reboot in APX.
When I reboot normal or fastboot, it only show logo and stop.
I can't enter in fastboot, adb dont detect my device.
Wheelie detect but I havn't got blob.bin, so I can´t use nvflash.
Arggg!
Is there any solutions?
arjona00 said:
Hello all.
I have an Asus TF201 bricked.
I readed a lot of forums, and nothing to do for now.
My Asus was fall in brick after install cwm, and now, only can reboot in APX.
When I reboot normal or fastboot, it only show logo and stop.
I can't enter in fastboot, adb dont detect my device.
Wheelie detect but I havn't got blob.bin, so I can´t use nvflash.
Arggg!
Is there any solutions?
Click to expand...
Click to collapse
I seem to have the same problem
Hi!
I have the same problem.
Somebody can hepl us please!! Thank you
I downloaded Tegra Android Developer Pack and image "dalmore" where are some utilities to generate encrypted necessary to enable executing commands in the boot. These are: nvsecuretool.exe or nvsbktool.exe.
but anyway the correct key is needed.
I used the calculator sbk but do not know if this works only for Acer tablet with tegra2.
A desperate chance. would take the sbkcalculator, and the apk asus application to unlock the boot, and test if there is any clue as to how you can make the sbk from cpuid on this model.
but I have no hopes for it.
I hope someone knows how to get the sbk from the cpuid for asus tf201.
why? why is so hard to find files to unbrick tf201?, ****ing secure boot, links deads
sometimes what is legal is not fair,
sorry but my skills are a dried **** as my translator
i try to find a .bct no encripted to build the blob.bin with my doubtful sbk from sbkCalc, but nothing,
I know it's possible, but I also realize that I will not be able to do.
alemap said:
why? why is so hard to find files to unbrick tf201?, ****ing secure boot, links deads
sometimes what is legal is not fair,
sorry but my skills are a dried **** as my translator
i try to find a .bct no encripted to build the blob.bin with my doubtful sbk from sbkCalc, but nothing,
I know it's possible, but I also realize that I will not be able to do.
Click to expand...
Click to collapse
I'm sorry, but it is only possible to un-brick a hard-bricked TF201 by using files that have been created on your own device with NVFlash.
Did you have nvflash enabled before you bricked? If not then you have a paper weight.
Check out my website for encouragement....
www.projectintercession.blogspot.com
Yes i enabled nvflash before brick, but i dont copied the blob.bin o any other file from the root backup folder to my pc.
i dont find it, maybe i delete carelessly when try install kitkat in the tablet.
tremendous fail !!.
If you bricked without having your NVflash blob files backed up, you're out of luck at the time of this writing. For a HARD BRICK, which you are experiencing, the ONLY way to recover if with those blob files. I have mine on google drive, dropbox, and on my PC for safekeeping.
I sold the prime I managed to brick for parts on ebay. I got $100 for it, but that was well over a year ago. There are better tablets out there, and most of them definitely put this old guy to shame. I would suggest upgrading your hardware, as the device you have is no longer usable.
I hate to be the bearer of bad news, but this is the chance you take when you unlock bootloaders, hack and flash ROMS, root, etc. Sometimes $h!7 happens. That's life.
Hello,
I have the same problem.
TF201 bricked !
Unable to go into the bootloader, so unable to go on fastboot !
I never activate nvflash so i dont have my blob file.
I'm sofwtare programmer, i think we could fin any way to hack nvflash or a wayt patch any blob file in order to be compatible for our device....
Please, union made strong ! We need to create or get a hack in order to use correctly APX!
---------- Post added at 08:35 PM ---------- Previous post was at 08:07 PM ----------
alemap said:
I downloaded Tegra Android Developer Pack and image "dalmore" where are some utilities to generate encrypted necessary to enable executing commands in the boot. These are: nvsecuretool.exe or nvsbktool.exe.
but anyway the correct key is needed.
I used the calculator sbk but do not know if this works only for Acer tablet with tegra2.
A desperate chance. would take the sbkcalculator, and the apk asus application to unlock the boot, and test if there is any clue as to how you can make the sbk from cpuid on this model.
but I have no hopes for it.
I hope someone knows how to get the sbk from the cpuid for asus tf201.
Click to expand...
Click to collapse
Interresting post...you could have the sbk on the tabs sticker...
But the question is...how patch a blob file in order to use the NVFlash....
I'm software programmer, maybe i can help you dude !!
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Restorer said:
I'm sorry, but it is only possible to un-brick a hard-bricked TF201 by using files that have been created on your own device with NVFlash.
Click to expand...
Click to collapse
There is probably a way to hack this file....to patch this....
I would like to compare two file in order to see differences....maybe it's simple to merge and patch.....
Wellcome to the Wall.
Related
Hello and thanks to take care about this thread,
When I tryed to install CyanogenMod, the internal storage was moved from /dev/block/mmcblk0 to /dev/block/mmcblk1.
Fortunaly I could access to the adb and fastboot interface.
So I used './adb shell' then 'dd if=/dev/block/mmcblk1 of=/dev/block/mmcblk0 bs=4096 conv=notrunc,noerror' to restore the first partition, but during the process, the asus transformer prime shuting down (no more baterry ?) and now i can't access clockworkmod, i can't see the splach screen, i think the mmcblk0 is corrupt but no empty, and i can't acess fastboot or adb.
The last interface avaible is the apx nvidia device who is recognise when i log the tablet on the computer, it's possible to do anythink with that ?
With hope
Scarilan
The dd command that you have in your post will overwrite everything in mmcblk0, not just the first partition. The internal storage that is used by android as the data partition is mmcblk0p8, a partition on the block.
That being said, the first few partitions are extremely important in order for tfp to work, which include the bootloader and boot configuration table. Corrupt these and you will have a brick.
Nvflash would be the only way to recover, however the only available way to use this is to create device specific files PRIOR to bricking.
Unfortunately in your situation, it would appear from what you have posted that you have corrupted your bootloader, and will not be recoverable, only unless you have done the wheelie/nvflash procedure prior to your current state.
Sent from my SO-01C using xda app-developers app
I didn't execute this procedure before my state, should i return the device to asus or it's existing a procedure with the sdcard or an other with the use of nvidia who can help me ? I never learned much about android before this story, but it was a costly took had a lack of knowledge apparently.
There are any escape ?
-> Edit :
I have an idea, Can i access to the storage with ubuntu ? If i can mount the HDD on ubuntu, i could regenerate the partition and solve my problem.
If it's possible, can i mount the hdd with the nvidia apx on my computer or is it required to open the tablet ?
Scarilan said:
I didn't execute this procedure before my state, should i return the device to asus or it's existing a procedure with the sdcard or an other with the use of nvidia who can help me ? I never learned much about android before this story, but it was a costly took had a lack of knowledge apparently.
There are any escape ?
-> Edit :
I have an idea, Can i access to the storage with ubuntu ? If i can mount the HDD on ubuntu, i could regenerate the partition and solve my problem.
If it's possible, can i mount the hdd with the nvidia apx on my computer or is it required to open the tablet ?
Click to expand...
Click to collapse
hey mate..can you tell me what happened with your tablet? because i've exactly the same problem. Moe
0din said:
hey mate..can you tell me what happened with your tablet? because i've exactly the same problem. Moe
Click to expand...
Click to collapse
If you have done the same as the op, there is no way unfortunately that you will be able to restore this device yourself, unless you took the NVFlash backup prior to it breaking, (and backed this up somewhere other than your tablet).
effectively, you will have wiped every partition off the MMC including the bootloader. this would leave Nvidia APX mode as your only route to restore, Asus have locked out this functionality, however if you were prepared and did the nvflash backup, this works around the lock that asus put in place.
If you didnt do the NVFlash backup, ASUS are your only hope (and they will likely charge for the privelage)
Steve
rosebud said:
If you didnt do the NVFlash backup, ASUS are your only hope (and they will likely charge for the privelage)
Steve
Click to expand...
Click to collapse
I sent the tablet to Asus. It was restored and I didn't have to pay the cost of repair. It's the luck or Asus is a very good company. I hope you'll solve your problem.
Thanks to Asus and to all the member of XDA
Scarilan said:
I sent the tablet to Asus. It was restored and I didn't have to pay the cost of repair. It's the luck or Asus is a very good company. I hope you'll solve your problem.
Thanks to Asus and to all the member of XDA
Click to expand...
Click to collapse
Repaired or changed the motherboard from ASUS ?
Asus repair the device. I have sent only the tablet (no the dock) and I have received it after one week. I don't know why but Asus joined with the device a micro-usb card of 16go (that was not my card of 32go, removed before sent my tablet). I won 16go with this story (i take care about virus, don't worry for that )
rosebud said:
If you have done the same as the op, there is no way unfortunately that you will be able to restore this device yourself, unless you took the NVFlash backup prior to it breaking, (and backed this up somewhere other than your tablet).
effectively, you will have wiped every partition off the MMC including the bootloader. this would leave Nvidia APX mode as your only route to restore, Asus have locked out this functionality, however if you were prepared and did the nvflash backup, this works around the lock that asus put in place.
If you didnt do the NVFlash backup, ASUS are your only hope (and they will likely charge for the privelage)
Steve
Click to expand...
Click to collapse
I have similar symptoms as the OP, although I didn't really do the same things as him.
Here's what happened to the best of my memory. I had my tablet running the official jellybean OTA with no problems. I unlocked the bootloader using ASUS' tool. I then rooted using the modified debugfs method (http://forum.xda-developers.com/show....php?t=1706588). At this point, the tablet seemed stable and I confirmed it was rooted.
I already had CWM downloaded on the tablet (I've used it for a year or two successfully with my phones) and decided to make a nandroid backup. However, when I attempted to boot into CWM recovery, the tablet booted instead into TWRP's screen (w/ RCK, restart, and ADB options). I assume that the root method I used automatically installed TWRP onto the tablet it was somehow "overriding" CWM. When I researched a bit, it appeared as if most people recommend TWRP anyway, and so I decided to uninstall CWM.
After deciding to get rid of CWM, I did it as one uninstalls normal apps. By simply going to the app in my app drawer and dragging it to the uninstall icon. From this point on, I can no longer get past the ASUS splash screen. Power and power+volume down reboots device and gets stuck at ASUS splash screen. Power+volume up does bring me to APX mode, but I never created a NVFlash backup (I had never even heard of it since it appears to be a way to potentially unbrick a device that was bricked by the JB update...but my update went fine).
This sure seems like a brick 2 as per diamondback's thread (http://forum.xda-developers.com/showthread.php?t=1514088), although it is a bit different. I'm stuck at an ASUS splash screen, not an EeePad splash screen. Also, I do not get an "unrecoverable bootloader error" (or any errors, for that matter).
I'm assuming that I'm hosed and will need to pay ASUS to replace the board, but figured I'd at least ask. Any ideas? Thanks!
Any suggestions? Thanks again!
It is no use as ASUS will not do any repairs. I just hate the products sold by this company. Wow what a way to make money thereby troubling its customers. I would rather say dump this company and buy either Samsung or Apple product you will have a company backing you up in case their devices have flaw and will take care of their customers. I am in the same boat and Asus refuses to repair since the bootloader is unlock, and will only repair if Paid $300 and above to replace the motherboard.
Scarilan said:
Asus repair the device. I have sent only the tablet (no the dock) and I have received it after one week. I don't know why but Asus joined with the device a micro-usb card of 16go (that was not my card of 32go, removed before sent my tablet). I won 16go with this story (i take care about virus, don't worry for that )
Click to expand...
Click to collapse
What was on the sd card that ASUS left in your tablet ????
Please forgive me that im witing this in the DEVS section,
however please don't critic/blaming me or telling that it is impossible to be done.
I know that programming and/or pushing file via APX mode it's POSSIBLE! if NVFLASH can do this so there a way to get it done manualy.
and about the .blob files that NVFLASH[wheelie] needs is truley possible to get it by your self even in hardbrick.
all i want to know it's how?!
what exactly the goal/mean of wheelie? how can i unbrick my tf201 whithout NVFLASH? and if with NVFLASH how can i do it without wheelie?
and please don't tellme that it's impossible.please.
---
furthermore, in the samsung I9000 thereno way to hear something like "sorry you are unlucky, get a RMA num'" the devs of i9000 trying to help andmake new things and ways. why TF201 don't have something like a JIG[301K RES]? why don't we have TJAG or something?!?!?!?! i think we have to learn from them.
ApresVu said:
Please forgive me that im witing this in the DEVS section,
however please don't critic/blaming me or telling that it is impossible to be done.
I know that programming and/or pushing file via APX mode it's POSSIBLE! if NVFLASH can do this so there a way to get it done manualy.
and about the .blob files that NVFLASH[wheelie] needs is truley possible to get it by your self even in hardbrick.
all i want to know it's how?!
what exactly the goal/mean of wheelie? how can i unbrick my tf201 whithout NVFLASH? and if with NVFLASH how can i do it without wheelie?
and please don't tellme that it's impossible.please.
---
furthermore, in the samsung I9000 thereno way to hear something like "sorry you are unlucky, get a RMA num'" the devs of i9000 trying to help andmake new things and ways. why TF201 don't have something like a JIG[301K RES]? why don't we have TJAG or something?!?!?!?! i think we have to learn from them.
Click to expand...
Click to collapse
It doesn't belong in dev section. Telling people to not critique you for posting it in the wrong place does not make it any more dev related.
IF there is a way to do these things, I assure you, they would be out there. Wheelie obviously does some magic stuff to even be allowed to use nvflash, and I wouldn't expect anyone to ever find a way no involving generating device specific blobs as we do.
JIG is device-specific. Samsung explicitly created it for recovery purposes - there's no reason to think asus would include something similar.
JTAG is disabled on all production fuses Tegra devices, so there's really no way to get access to that (Even if you get access to the pins, it would just refuse access.)
all i want to know it's how?!
Click to expand...
Click to collapse
Seriously? You just want the holy grail handed to you and then you'd magically dev it?
I agree with what rayman says... rayman & the other folks at AndroidRoot have done us wonders with wheelie to enable nvFlash for our devices...
The truth of the matter is... you need to start by getting you basics right...nvFlash is the low-level utility for nVidia based devices & chipsets... I've used a Tegra 2 device before (GTablet) which was pretty much open and nvFlash worked out of the box... Here, however, Asus locked down things with very few ways to circumvent things...
With the information & knowledge available, wheelie is the only way to get nvFlash working.... why don't you read this amazing article written by the AndroidRoot team and understand the technicals of the situation.... http://androidroot.mobi/technical/tf-secure-boot-key/
craigacgomez said:
I agree with what rayman says... rayman & the other folks at AndroidRoot have done us wonders with wheelie to enable nvFlash for our devices...
The truth of the matter is... you need to start by getting you basics right...nvFlash is the low-level utility for nVidia based devices & chipsets... I've used a Tegra 2 device before (GTablet) which was pretty much open and nvFlash worked out of the box... Here, however, Asus locked down things with very few ways to circumvent things...
With the information & knowledge available, wheelie is the only way to get nvFlash working.... why don't you read this amazing article written by the AndroidRoot team and understand the technicals of the situation....
Click to expand...
Click to collapse
So it is impossible to unbrick Primes? Or anyone is working on it? Do You know?=)
I have searched around regarding this.
It seems that there is a SBK calculator made for the Acer A500 device.
This was made to generate blobs that match your device's CPUID.
If we could get this working on the Prime, it might perhaps unbrick it. (?)
DarkWader said:
I have searched around regarding this.
It seems that there is a SBK calculator made for the Acer A500 device.
This was made to generate blobs that match your device's CPUID.
If we could get this working on the Prime, it might perhaps unbrick it. (?)
Click to expand...
Click to collapse
Sadly, that won't work.
SBK generation is vendor-specific - there's no standard.
The SBK calculator for Acer A500 is extremely specific to A500 and won't work on other devices. (Acer ****ed up and the algorithm they used essentially got leaked).
It's possible something similar exists for ASUS devices, but it's pretty unlikely we'll get our hands on such a thing.
@ndrey said:
So it is impossible to unbrick Primes? Or anyone is working on it? Do You know?=)
Click to expand...
Click to collapse
Not if you have nvFlash enabled before you brick your device or upgrade to JB... if you have done [http://androidroot.mobi/t3_nvflash/], you should be able to recover from almost any brick...
craigacgomez said:
Not if you have nvFlash enabled before you brick your device or upgrade to JB... if you have done , you should be able to recover from almost any brick...
Click to expand...
Click to collapse
But if I dont? Bricked forever? :crying:
@ndrey said:
But if I dont? Bricked forever? :crying:
Click to expand...
Click to collapse
Quite possibly!!
I've gotten pretty far in the tutorial for using nvflash until I get to the wheelie --blob blob.bin command.
I've reinstalled the naked drivers after first entering APX mode, but now I'm getting a different error that reads:
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4b20060c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
I feel like this is the last big step for me to get to Androwook, but I'm too scared of flashing until I've done the necessary procedures for NVFlash. Anyone have more info on this particular error and how to fix?
jynlude said:
I've gotten pretty far in the tutorial for using nvflash until I get to the wheelie --blob blob.bin command.
I've reinstalled the naked drivers after first entering APX mode, but now I'm getting a different error that reads:
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4b20060c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
I feel like this is the last big step for me to get to Androwook, but I'm too scared of flashing until I've done the necessary procedures for NVFlash. Anyone have more info on this particular error and how to fix?
Click to expand...
Click to collapse
just checking 1 more time if anyone can help out or has any insight/thoughts as to what to do?
jynlude said:
just checking 1 more time if anyone can help out or has any insight/thoughts as to what to do?
Click to expand...
Click to collapse
I have exactly the same error and cannot find any answer.
Can someone please help ?
yankeefr78 said:
I have exactly the same error and cannot find any answer.
Can someone please help ?
Click to expand...
Click to collapse
happen to have found a solution? i might just restart and try again from scratch
Same issue here. Recreated blobs, uninstalled and reinstalled drivers, rebooted everything, tried a different computer, no change.
Making an addition to this thread. Also having ongoing "Error 3 receiving response from command" when entering "./wheelie --blob blob.bin"
When run as root, I get:
"RCM_Receive communication failure"
The device is showing up when I run lsusb
Anyone been able to find a work around?
wanted to see if anyone can help with an update to see if anyone was successful with this yet? still scared to flash to hairybean without successfully going through this process
This worked for me
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
Totally worked! Thanks so much...was able to get my recovery files...next step is hairybean!
I'm glad this worked for you too! Gives promise that it will help others.
After bricking my TF201 once, I learnt my lesson and was not going to proceed without taking all the right precautions.
jynlude said:
Totally worked! Thanks so much...was able to get my recovery files...next step is hairybean!
Click to expand...
Click to collapse
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
unfortunately I dont have luck whit that, i can run 2 times wheelie.
1. time it says error 3
2. time it says nverror 0x2
and then device disconnects, i press and hold power and it boots directly into APX and i can start over with the same result
any solutions? :crying:
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
Is it even possible to brick APX mode?
dj_chapz said:
Is it even possible to brick APX mode?
Click to expand...
Click to collapse
Hi mate,
The steps I listed are for creating the backup blobs. Are you trying to create them or have you bricked your device and are trying to recover?
jim.g87 said:
Hi mate,
The steps I listed are for creating the backup blobs. Are you trying to create them or have you bricked your device and are trying to recover?
Click to expand...
Click to collapse
Im trying to recover. I got the backup files. Long story short, flashed wrong recovery, wiped eMMC (all partitions gone i think) so i need to repartition. I am in constant APX mode, cant get out, if i hold power it reboots directly into APX...
I had the same problem, try use this version.
redvirus said:
I had the same problem, try use this version.
Click to expand...
Click to collapse
It's a long time ago but thanks, this version helped me overcome error 3.
:good:
I'm resorting to xda developers because no longer know what to do and the more I read less i know!
I have a Asus Tf201 JB. Sometimes ago the screen broke, i buy one on ebay but when i assembly the new screen i got the x-axis reversed, so i google and found the fix to x axis reversed here on forum.
First i unlock the device with asus tool, after i root and use some android software (i cant remmember the name) to flash the x axis reversed fix patch.
My bad, i do something wrong, now it stuck on asus/nvidia logo screen.
My pc only recognize APX mode if power+upvolume nothing more.
Please help me and tell me:
Are permanently dead, can i fix or its garbage?Can here any expert solve me this problem!?I pay if necessary.
If it dead can i swap the motherboard and get the problem solved!?
Sorry about my English
Thanks in advance
Best Regards
im sorry to ask this while I can't help you, but im trying to root my Tf201 and I can't seem to figure out how. How did you? I've got it unlocked using the Asus tool, like you, but every way I've found to root has not worked for me.
Thanks, and sorry I couldn't help your issue.
Claymorb said:
im sorry to ask this while I can't help you, but im trying to root my Tf201 and I can't seem to figure out how. How did you? I've got it unlocked using the Asus tool, like you, but every way I've found to root has not worked for me.
Thanks, and sorry I couldn't help your issue.
Click to expand...
Click to collapse
Hi, i use Motochop it works fine for me, dont forget run app as admin!
Regards
The information is out there, but not always easy to find. I haven't had to recover my Prime yet, but I've done the backups before flashing to Androwook, and have read up on how to recover should anything go wrong. here is what I've found as a good resource:
*Note: Being able to get into APX mode is a good start*
Go to this thread, "[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201"
The step-by-step guide is self explanatory. It goes over getting the NVIDIA Naked Drivers, NVFLASH and Wheelie. And the best part, there are links to the stock "un BLOB'D" files, which you will need for a recovery. This is basically the stock rom you can download from the ASUS site, and broke out into the separate recoveries for all the partitions.
and to answer your last question about what to do if you cannot unbrick... yes, you would need to replace the motherboard as the last resort.
Good luck!
edit: Found a really good thread (saved to my favorites) showing step-by-step process to unbrick:
Post 16 from "Need help with APX mode" thread
Hello,
I download from the ASUS website the firmware with version "V10.4.2.18 Only for WW SKU (Android 4.1)" and the pop-up for update de firmware appear normally to me.
Then, the TF201 restarted and since then does not passes through the ASUS Logo.
I Was on 4.0.0.3, firmware 9.4.2.28 and tried to upgrade to a superior version (my mistake as I can see now).
Even when restarting with Power + VOL DOWN the only thing that appears is :
----......................
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.2.28-20120525" A03
Checking for android ota recovery
Booting recovery kernel image
-----------
And stays here forever... No option with the 3 icons, so I can choose USB... And neither the VOL UP during this process does nothing...
Anyone can help?
Thanks in advance
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
sl0mar said:
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
Click to expand...
Click to collapse
I installed the drives and the PC recognizes the TF-201.
But it seems that fastboot can't recognize the tablet.
Well, I didn't get so far...
But I still want to try, but I'm a little lost...
Any help?
what you see when u run fastboot devices ?
inbg said:
what you see when u run fastboot devices ?
Click to expand...
Click to collapse
From my PC device manager I can see the asus transformer Prime APX Interface and is saying that "This device is working properly.".
However, every command that I sent from fastboot the result is always the same:
< waiting for device >
I'm completely out of ideas to get this back to work...
THATS BAD do u have working adb ?
No i don't...
HOW to Reserruct from APX mode^
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
logicmate said:
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
Click to expand...
Click to collapse
Logicmate, seems there is no help how to unbrick the tf201 in APX mode...
Did you get lucky meanwhile?