yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] craigacgomez:
I've added the semi-automated complete recovery zip and information. Download and info in the OP.

This process completely wipes all partitions (except external SD/mSD cards) and reflashes everything, essentially returning your device to a near factory state. You will not lose you unlock status or nvFlash access. You will lose all data from your internal storage (/storage/sdcard0 or /data/media).

Unfortunately, due to technical reason, this process is possible only using Linux, since the nvflash executable for Windows is very old and cannot handle this process. I will be creating a detailed step-by-step guide for those not comfortable with Linux. But for now, this is available for all those who know how to use Linux.

To use this, you need to download one of the unblob'd stock ROMs (or create your own) along with the semi-automated complete recovery zip.

You will also need the device specific nvFlash backup generated when you enabled nvFlash.

Complete instruction are in the "README" file in the semi-automated complete recovery zip.
[Asus  Eee Pad Transformer Prime] andrewjt19:
UNBRICKED TF201 PRIME is back

Thanks man so much for your time... this was an absolute miracle.
[Asus  Eee Pad Transformer Prime] d1ez3:
Thank you so much, I thought I was completely bricked but you saved my tablet.

Now that I am on the stock JB rom that you posted but am unlocked, how can I install TWRP without root access? Can I still boot into fastboot to install a custom recovery?
[Asus  Eee Pad Transformer Prime] wejgomi:
Wish you ported it to windows. We already had that. Thanks anyway.
[Asus  Eee Pad Transformer Prime] nicnec:
Hello! TF201 hold a brick(after a reset has not started, nor enter the bootloader menu lock ASUS remini) and I want to bring back to life after this method Dr. not know where to get these files:

-factori-config.img

-unlock-token.img

-create.bct

-blob.bin

thanks!
[Asus  Eee Pad Transformer Prime] wickid_d:
What, EXACTLY, do you mean by, 'does not start up'? Do you get an error code? does it not run at all? Please, ellaborate, and maybe we can help you.. that is far too general for us to make any determination as to why it's not working for you..

---------- Post added at 12:54 AM ---------- Previous post was at 12:23 AM ----------

It's possible.. I don't know if nvflash or apx limits the file size per partition, but boot.img (or the blob file of it), is what sets up the partitions.. Peep my sig.. Only thing that doesn't work in this configuration is bluetooth, but I rarely use that anyway on this..

/system is currently:

[IMG="blah"]http://wickidtech.com/images/xda_pic_1.jpg[/IMG]
[Asus  Eee Pad Transformer Prime] Namidairo:
The boot.img is the kernel image. What you are thinking of is the partition table.
[Asus  Eee Pad Transformer Prime] tux-friend:
Hard brick despite of having a working blob.bin file

At first I would like to express my thanks to craigacgomez for starting this great thread! I could learn a lot! :victory:

Although, I thought that I made everything right to prevent a hard brick regarding my TF201 device, it has finally happened: A hard brick, although I created a working blob.bin file by flatline recovery :crying:. Maybe, I made some stupid mistakes, I don't exactly know. I tried to flash multirom on my TF201 by using an unofficial version for the Asus TF300t tablet. At first it was working, but I noticed that the device recognition got mixed (the TF201 turned into an TF300t) and I experienced some problems during installing some custom roms for the TF201. I tried to undo the changes to get cm11 working again. However, the flashing process was not sucessful. Then I lost control over my tablet. I couldn't enter bootloader anymore including fastboot or recovery mode. However, while trying to press the hardware keys to enter apx mode, I recognized that the display of my TF201 remained black (which is actually a good sign because it should be like that during first stage of this mode).

However, on my PC the tablet is not recognized as apx device anymore after connecting it via USB cable. I was not successful, neither under Linux nor under Windows. Under linux I could not find the device by typing:

lsusb

Normally there should be a new entry after connection.

Is there any suggestion, what I still could do? And yes, I can confirm that I have a working blob.bin file created before this error has happened.
[Asus  Eee Pad Transformer Prime] KlipperKyle:
Just as a sanity check, the TF201 should be plugged into the computer directly (not via the dock).

You could try dmesg -w while plugging in the TF201. dmesg -w displays the kernel ring buffer and automatically updates it (in a tail -f manner). This will show any and every piece of hardware as it is attached and detached.

If you still don't see anything, there is the slight chance the problem could be dirt/grime in the dock connector of the TF201. You could try cleaning it out.

Let us know what dmesg -w tells you.
[Asus  Eee Pad Transformer Prime] tux-friend:
Thanks KlipperKyle for your suggestion! Unfortunately dmesg -w does not work on my system (bodhi linux based on ubuntu 12.02). But I think it's no problem. Alternatively, I just typed

dmesg | tail -f

after plugging in the TF201 (I have repeated this procedure one more time). Here is the output:

user@GreenPlanet:~$ dmesg | tail -f

[ 1187.804067] usb 6-1: new full-speed USB device number 15 using uhci_hcd

[ 1187.928072] usb 6-1: device descriptor read/64, error -71

[ 1188.156072] usb 6-1: device descriptor read/64, error -71

[ 1188.372063] usb 6-1: new full-speed USB device number 16 using uhci_hcd

[ 1188.784063] usb 6-1: device not accepting address 16, error -71

[ 1188.896073] usb 6-1: new full-speed USB device number 17 using uhci_hcd

[ 1189.308070] usb 6-1: device not accepting address 17, error -71

[ 1189.308101] hub 6-0:1.0: unable to enumerate USB device on port 1

So it seems that there is a communication problem. Just to clarify, I want to add that my usb cable is not broken (I have a second TF201 and I could verify this) . Furthermore, I have used another usb cable as well and the same error appeared. Last but not least, I wanted to make sure that the ribbon cable for the power connector was faulty. Therefore, I have replaced it with a working cable. But again, the same problem occured.

Somehow, I get the feeling that the partition table or bootloader is corrupted on my system :crying:. Probably, there is only a chance if I force my linux system on the PC to accept the plugged in TF201 as apx device. But I really don't know how to apply this hack :confused:.

And maybe a last important hint about the current situation with my Prime:

1. If I turn it on in the normal way, the Asus logo just appears and the information is displayed that my "device is UnLocked". Nothing happens afterwards.

2. If I press power button and volume down simultaneously to enter the bootloader, the same informations is shown like under 1 and nothing happens again. Furthermore, there is no possibility to enter recovery or fastboot mode.

3. If I press power button and volume up simultaneously, the touch screen remains black which is actually a hint that apx mode is probably working.
[Asus  Eee Pad Transformer Prime] KlipperKyle:
My optimistic guess is that APX mode is working, but the dock connector is too dirty for the PC to see anything.

The "device descriptor read" and "device not accepting address" errors generally mean a faulty connection. It sounds like you checked the cable and USB port on your machine, so I suspect the dock connector on the TF201 is dirty.

It looks like there are two sides of pins on the dock connector. Reaching the side facing the screen might be difficult. I would recommend scraping the connector with a toothbrush.

You mentioned a power ribbon. Is that on the inside? If you do have access to the insides, you might be able to take the dock connector out, clean it with flux cleaner, and reinstall it. (I recently did this with my Nexus 4's microUSB port.)
[Asus  Eee Pad Transformer Prime] tux-friend:
Thanks KlipperKyle again! I tried to follow your suggestion to use a toothbrush for cleaning. But unfortunately this couldn't solve the problem for my TF201. I am sure now that the connector is not the problem. Furthermore, I have already tried to replace the ribbon cable from the interior of my prime which is directly connected with the dock connector for plugging in power or just usb (actually the connector and the ribbon cable is one fixed unit and it was working in another TF201 device).

For this reason, I suppose that either the partition table or even nvflash is somehow corrupted on my eMMC so that communication fails.

By the way, I checked the communication between my prime and the PC under windows as well. In fact, Windows recognizes that a new usb device was plugged in but again the device could be not detected in the right way and a yellow triangle with the exclamation mark appears in the device manager. And to clearify: I have already installed the correct driver for the TF201 under Windows. Thus, the driver shouldn't be the problem.

More and more, I have the impression that I experience a new kind of hard brick despite the fact that I have a working blob.bin. I guess that only a low level hack could save my prime. Any idea?
[Asus  Eee Pad Transformer Prime] Stargazer Optimus:
With the very recent release of the 4.0 version of the grimlock kernel, we may not need to be bothered with altering the partition table of internal storage as you can have rom2sd on a microsd card. The system partition becomes the third partition on the card so can be set up to whatever size you desire. You just lose the microsd slot for other purposes this way.
[Asus  Eee Pad Transformer Prime] Gibby1310:
I had followed a guide a while back to flash my TF201 to KK with a TF300 build, when I went to go to a normal KK TF201 build I lost access to the bootloader and recovery. Follow this and worked great to get back. Thanks!

Note: I had to use the ICS un-blob'd zip in the first post, the JB one did not work for me.
[Asus  Eee Pad Transformer Prime] trueagle:
I need help with my TF201. I received a bootloader error and device went black. The only thing I can do is boot to apx mode and when I start wheelie it goes through the start up process then recognizes my tablet by unique curd says sending bootloader, sending files 100% and just hangs there any help would be appreciated
[Asus  Eee Pad Transformer Prime] zgpirate:
Great tutorial Craig. I understand most of it now. Thanks!
[Asus  Eee Pad Transformer Prime] k33pys:
Thanks for this tut hope I can unbrick with this knowledge.
[Asus  Eee Pad Transformer Prime] wickid_d:
Even if you can't unbrick, there's 2 listings on eBay right now for main boards @ $63 USD, and you can use this after install to prevent future bricking.

Cheers,

~Wickid~
[Asus  Eee Pad Transformer Prime] k33pys:
Hi guys I used this method on widows to unbrick my twrp password bootloop. Each time i run a nvflash command I have to reboot my device into apx mode then wheelie back into nvflash before being able to go to the next step. I cannot flash twrp or cwm back to my device now though ?

I was trying to flash twrp to jb and it didn't work I renvflashed is and I'm back and fulled loaded to lollipop.
[Asus  Eee Pad Transformer Prime] la2015:
Nvflash Fails after step 2 loading the EBT blob??

Hi All,

I have backed up my original blob files per the guides. Now the issue ;)

Due to some file system errors i decided to restore my device using the nvflash to bring it back to a clean state. i performed this a couple of times while playing around with different CM and Katkiss rom's. Now what happens I go into APX mode following the instructions here, I am able to Wheelie in and I get the nvflash mode, When i perform the next step "sudo ./nvflash -r --download 4 blob.EBT" it loads, then in my terminal It waits a few seconds before returning to the prompt, I also notice very quickly a short message on the tf201 and i think it says something about failed and the screen goes black. I am no longer able to load anything, and i can only wheelie back.

Any got an ideas or am i up a creek without a paddle??
[Asus  Eee Pad Transformer Prime] wickid_d:
Did you use the '-i 0x0b05' option when trying to flash twrp or cwm from fastboot? If you left that out, that maybe your problem. And yes, you can flash twrp.blob during the apx process - just make sure you're on the right step where it says 'to flash the stock recovery, use...', and use the twrp.blob instead. It doesn't always work this way, but most of the time, as long as everything's in order, it will.

Cheers,

~Wickid~

---------- Post added at 08:24 AM ---------- Previous post was at 07:34 AM ----------

I started searching all over the bloody forum for an option with wheelie or nvflash (I don't remember which one it is) that fixes a corrupt bootloader, then came back and reread your post, and saw the red flag in your post.. So, let me stop you right there - file system errors, where? On the tablet, or your computer?

If it was your computer, possibly corrupt blob.EBT - I'd do an md5 sum and check it that way.. Then all you have to do is re-expand the rom files (I'd completely get rid of the corrupt one so it doesn't overwrite it, and you end up with good and bad bits in the file) and try again..

If not, then it maybe what I just previously mentioned, (the corrupt bootloader) and if that's the case, then I'll keep looking.. It may even be earlier in this thread where that appeared..

Cheers,

~Wickid~
[Asus  Eee Pad Transformer Prime] la2015:
Hi Thanks for taking a look, The File system error were on the tablet, while in twrp.. What was happening in twrp when I performed a wipe cache/dalvik I was getting a funny "E: cannot determine correct filesystem blah blah.. " So I thought let's bring it back top a clean slate and play somemore..
[Asus  Eee Pad Transformer Prime] wickid_d:
If it was twrp 2.8.3.0, yeah, I got something similar while getting into recovery.. I think that one's a little on the buggy side still.. I stepped back to 2.8.1.0 and all is well again.. That's for that, but not being able to flash blob.EBT still sounds like a corrupt file to me. If it was a corrupt bootloader, you wouldn't get that far - it would cut out on 'wheelie-ing'. And as for your linux box, you can have a perfectly running system and get file corruption errors.. it happens *shrug* lol Question, what kind of file system are you running for the linux partition where your rom files sit? if it's xfs or jfs, I've run into issues with both of those (different issues, but yeah). ReiserFS ver 4 (or later) and EXT 4, I've always found to be the best and safest from file corruption, due to journaling (even though that's what jfs is), and just simply, better code..

Cheers,

~Wickid~
[Asus  Eee Pad Transformer Prime] la2015:
Hi, So my fix seems to be recovering using my blobs that I saved. I used lj50036's instructions here [NvFlash] [Recovery] With [Generated Blobs][TF-700-T], But used the TF201 factory stuff.. Now it looks like I am back in business.. Whewwwwwww That was a hair pulling couple of days.. With lots of reading.. No to Update it again to katliss 5 using lj50036's instructions.. :) i feel much better now knowing I can recover this old gal.... Thanks wickid
[Asus  Eee Pad Transformer Prime] k33pys:
My problem was a little different because I had installed the dual boot grub menu and was running Linux off a usb and android off the tablet. I backed up using nvflash before this and my problem occurred when trying to reinstall the original bootloader over grub. I tried both the jb and ics bootloader's this is where I got stuck in a twrp password bootloop. I had to use a combination of apx and fastboot to be able to get it back up and running.
[Asus  Eee Pad Transformer Prime] wickid_d:
Well, I'm glad yall got your problems fixed and up and running again, even if I wasn't much help, lol sorry :(

~Wickid~
[Asus  Eee Pad Transformer Prime] k33pys:
Sending bct

Hi guys my tf201 is frozen on sending bct after starting wheelie command. I got it all working but then ran into a few problem with the lollipop rom so tried to flash it again and now I'm back to square 1 . I knew something was wrong but having trouble mounting in twrp
[Asus  Eee Pad Transformer Prime] Rapax:
No downloads on androidroot.mobi?

Seems the download page on androidroot.mobi has gone AWOL. None of the links work (get the 'outdated download' page) and going directly to /download gives me a 404.

Any idea where to grab the required files for a TF201 and Linux?
[Asus  Eee Pad Transformer Prime] :
The link for the wheelie binary/executable is dead.. can you please tell me where I can find it?

thanks.
[Asus  Eee Pad Transformer Prime] das chaos:
Not true, link is working:

https://download.androidroot.mobi/nvflash-tools-linux.tar.bz2
[Asus  Eee Pad Transformer Prime] DJ_MiX:
Need help I Have a ASUS MEMO Pad smart 10

Where can I get a blob.bin from?

I can only go into APX mode, Have no ADB
[Asus  Eee Pad Transformer Prime] flumpster:
Unless you created your own then someone elses is not going to help you. It is linked to your motherboard.
[Asus  Eee Pad Transformer Prime] wickid_d:
what [MENTION=3909556]flumpster[/MENTION] said..
[Asus  Eee Pad Transformer Prime] awarannepal:
Link Please.

Hey can you please give me the link to wheelie.exe. the link you provided doesn't work.

Thank You.
[Asus  Eee Pad Transformer Prime] jinseiichido:
The nvflash & wheelie download links in the guide seem broken and the files are no there any longer.. could someone provide us these files???
[Asus  Eee Pad Transformer Prime] jinseiichido:
Hello everyone.. I have been trying to follow the guide to get my tablet working but I'm having some problems following the steps.

I can get my TF201 into APX mode so I can use nvflash.. but my tf201 keeps rebooting itself to ASUS logo screen after each time I run a nvflash command in the steps. Please look at the screenshot images I attached to this thread.

So basically I have done the following..

If anyone is interested I have a thread going here - http://xdaforums.com/transformer-prime/help/tf201-stuck-asus-splash-screen-t3091490/

Any help is appreciated. Thank you so much in advance. I really want this tablet working again so I can give it to someone.
[Asus  Eee Pad Transformer Prime] dsouzama@gmail.com:
Stuck on ASUS Splash Logo, shows as APX in Device Mgr

Please Help me.

I rooted my device recently but it was already unlocked few months back and no issues. I had stock rom JB 10.4.2.18, and since the performance on the device was slow. I decided to root it and update to CM Kit Kat, the only thing i did was to get into recovery and did wipe data to get into Factory mode, and ultimately after that it is stuck on Splash Screen with Asus Logo and the normal message at the top left Device is unloced and the NVidia Tegra logo on the bottom right.

I can see the device in device manager as "Asus Transformer Prime APX interface" but when i execute ADB reboot bootloader or with Fast boot, it says Error no device found.

I dont have any backup or any device specific blob file other than whatever i downloaded from ASUS web site. I sent it to ASUS and they gave me a quote for $300 to replace Mother Board . Do i have any chance for recovery ?
[Asus  Eee Pad Transformer Prime] dsouzama@gmail.com:
The only thing i see in Device Manager is :-

Android Phone -

Asus Transformer Prime APX Interface

Any help to get this fixed will be highly appreciated.
[Asus  Eee Pad Transformer Prime] bb100dulski:
I have the sbk for my tf201.Can I somehow recover?
[Asus  Eee Pad Transformer Prime] Dnkl96:
will this work on tf201?

will this work on tf201? i just go into fastboot mode and accidentally data wiped it. i already unlock my tf201 but i can't instal recovery. can this work on tf201? or is there other way to unbrick it?
[Asus  Eee Pad Transformer Prime] thebig24fan:
Would this fixed my problem getting in recovery mode as it fails everytime i try ?
[Asus  Eee Pad Transformer Prime] tania9423:
HI ALL

this DOWNLOADS it fail...

I need DL STOCK nvflash ROM

PLZ:)

TK"S

UN-BLOB'D STOCK ICS 9.4.2.28 ROM

- Un-blob'd stock ICS 9.4.2.28 ROM

- Completely unmodified

UN-BLOB'D STOCK JB 10.4.2.15 ROM

- Un-blob'd stock JB 10.4.2.15 ROM
[Asus  Eee Pad Transformer Prime] albertao83:
Transformer Prime Bricked

Sorry guys, but I'm become crazy with this device.

Two years ago I bricked my tf201 and I doesn't found a solution.

Now I want fix it.

When I power the device it appear a screen with "Asus - inspiring innovation - persistent perfection" writed in the middle.

In the corner top left is written " the device is unlocked".

If I push power+volume down doesn't happen anything. Simply remain in the black screen with the logo in the middle.

I Have windows 10 and the laptop doesn't recognize it. When I plug the usb when the tablet is in power off windows says this "ID dispositivo corrispondente: USB\DEVICE_DESCRIPTOR_FAILURE

Driver prioritari: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000"

What do I do? :mad::mad::mad::mad:
[Asus  Eee Pad Transformer Prime] negRomino:
Links for unblobd ROMs and Semi-automated complete Recovery are offline.

Anyone who can help out?:confused:
[Asus  Eee Pad Transformer Prime] ozgurkinaci:
Unblob'd stock files

Hi everyone,

I have found the unblob'd stock files and wanted to share with everyone.

https://www.androidfilehost.com/?fid=23212708291677381

I have unbricked my TF201 with this guide, thanks to [MENTION=2322613]craigacgomez[/MENTION]

Now I need to update to Nougat. :)
[Asus  Eee Pad Transformer Prime] jo_r:
Hi guys,

Sorry, I can't help as I'm a newbie and I followed this guide and my tablet is now bricked.

Maybe someone could help me as I'm facing the same issue some of you had but I've been unable to resolve the way you did.

The problem came when I made this :

adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard

I confirmed flashing.

The tablet restarted, the blue bar appeared but only a few seconds and then rebooted.

Since, I've got the nvidia logo (on top left is written it is unlocked) and that's it.

I downloaded file "WW_epaduser_10_4_2_18UpdateLauncher.zip" from Asus website (it is the correct one as it's written at boot "ww_epad-10.4.2.15-20120917 A03"). I've TWRP v2.6.3.0 installed.

I tried to flash this rom but I got immediately "Failed" message.

When trying to flash "KatKiss-7.1_TF201_026.zip" from my external sd card, the progress bar showed during a few minutes until it displayed "Failed".

For information, APX works and I can enter TWRP.

Thanks a lot.

Jo
[Asus  Eee Pad Transformer Prime] Nektopoli:
You need to update your TWRP to the latest version. What bootloader are you on, it should show the version in the upper left when you boot into the bootloader.

NP
[Asus  Eee Pad Transformer Prime] M!W:
Does anyone have the latest Linux binaries? The download links for Linux are broken.
[Asus  Eee Pad Transformer Prime] nguberinic:
Cant really understand

Please can someone clarify the procedure !

I can get to APX mode with my asus tf 201 transformer..

I have backup of files:

recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log, bricksafe.img, factory-config.img and unlock-token.img.

But I have no idea why in the hole process of restoring tablet I use none of the files.

My Asus is stucked in bootloop, and it boots back after roughly 10 sec beaing stuck in teamwin recovery window and then bootloops again and so on.

When I press power and volume up button and I

call wheelie in help it uploads 'wheelie.exe --blob blob.bin',

as soon as I enter next command 'nvflash.exe -r --download 4 blob.EBT' it uploads the file and it goes to loop again.

I have followed guide for installing Android 7.1 Nougat 'https://xdaforums.com/transformer-prime/help/guide-tutorial-asus-transformer-prime-t3486237'

and there it says •Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot) bootloader V 10.4.2.18.

Here am reading that it's not good if it's v10.4.2.18... Am getting really confused.

Once again, if someone could clarify in simple English, what am I doing wrong, or what should I do to do it the right way...

Thank you all for patience !