yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] hoya68:
Sorry I Offended You

Flumster, believe me I did read the instructions. Everything was fine until instruction 6. I have received the message that my device is ready in nvFlash mode. I then type "nvflash.exe -r --download 4 blob.EBT" (without quotes) and receive message "Nvflash version 13. 87295 started

[resume mode] file open failed NvError 0x30013 command failure : failed to pad bootloader" I saw nothing in the instructions or the thread that would get me beyond this.

---------- Post added at 08:50 PM ---------- Previous post was at 08:47 PM ----------

I did google "failed to pad bootloader" and only discussion was a thread that was (literally Greek or maybe Russian to me) http://4pda.ru/forum/index.php?showtopic=426283&st=540
[Asus  Eee Pad Transformer Prime] flumpster:
Have you downloaded the "UN-BLOB'D STOCK" rom that you want from the bottom of the post and extracted it into your nvflash folder first?

From what I can make out on that russian link the guy eventually gets around his problem by using a different machine ( he used xp ).
[Asus  Eee Pad Transformer Prime] hoya68:
Thank You

Unfortunately, I am receiving the message "We are currently syncing all old data to our new system so please hang tight if things are not working properly!" and then a server error 500. I assume this is a temporary glitch and will try again later, unless you know another link for the download. I really do appreciate your willingness to share your expertise. I did my best to fix the issue on my own by searching and reading everything I could find.
[Asus  Eee Pad Transformer Prime] flumpster:
What files are you missing? Just the UnBlob'd rom ?
[Asus  Eee Pad Transformer Prime] hoya68:
The files I have in the nvflash directory are: blob.bin, blob.log, bootloader.ebt, bricksafe.img, create.bct, factory-config.img, libnv3p.dll, libnvaes_ref.dll, libnvapputil.dll, libnvboothost.dll, libnvdioconverter.dll, libnvflash.dll, libnvos.dll, libnvtesttio.dll and libnvtestresults.dll.
[Asus  Eee Pad Transformer Prime] flumpster:
You must have the nvflash and wheelie files in there as well or you wouldn't have got as far as you did.

You also need an unblobed rom to go in that folder and as you said the download links are down at the moment.

I do have tools here that I use to unblob the main stock rom but they either require linux or knowing how to use cygwin in windows.

If the download links don't come back in the next few days let me know and I will unblob it for you and upload it. This does take me ages to upload tho so it's a last resort.

---------- Post added at 12:25 PM ---------- Previous post was at 12:12 PM ----------

EDIT

I'm not really doing anything for the next hour and I know you need these files so I am uploading an Unblob'd version of stock Jellybean for you at the moment.

Other people are going to need them at some point if the other links don't come back online.

I will post a link when it is done and I will upload an Unblob'd version of ICS also in the next day or two.
[Asus  Eee Pad Transformer Prime] hoya68:
I apologize, when I split the screen to type the directory I left out the bottom part of the directory which contained nvflash.exe, pt_patch.log, pt_restore.log, rec_bootloader.bin, recovery.bct, unlock-token,img, unlock_token.img and wheelie.exe.

The download site was still down a couple of minutes ago.

If we get this fixed, I definitely will make a donation. I know you are really trying to help.

Thanks for offering to post a link to the files.
[Asus  Eee Pad Transformer Prime] flumpster:
Sorry mate. I was half way thru uploading it earlier and my Internet died until now. Lucky really as they told me I would have to wait on an engineer on Monday but it seems to have been fixed at the exchange.

I will start the upload again now.
[Asus  Eee Pad Transformer Prime] hoya68:
You don't need to apologize. You are doing me a favor.
[Asus  Eee Pad Transformer Prime] flumpster:
Here you go.

DOWNLOADS:

UN-BLOB'D STOCK ICS 4.0.3 (9.4.2.28) ROM

- MD5 - a74e05be2d3aba2af5c970e30d3a3720

- Un-blob'd stock ICS 4.0.3 (9.4.2.28) ROM

- Completely unmodified

UN-BLOB'D STOCK JB 4.1 (10.4.2.18) ROM

- MD5 - 47603552984c10b7e7180fb6cb23901e

- Un-blob'd stock JB 4.1 (10.4.2.18) ROM

- Completely unmodified
[Asus  Eee Pad Transformer Prime] hoya68:
OK I made some progress and then got stuck. I unzipped the file into the nvflash folder. I got through step 6 successfully and tablet booted into cyronogen screen which stuck on the spinning image. If I tries to do step 7 I receive connection failed message. If I went back to APX mode and tried to flash blob.SOS nvflash starts and then gets stuck (five minutes and counting) on resume mode. Should I do a wipe and start over, or do you have a better recommendation? Thank you, my friend.
[Asus  Eee Pad Transformer Prime] flumpster:
I don't ever remember it restarting after step 6 when I have done this before. I normally have just gone thru them all and then restarted.

ICS will be up in a few minutes so you can try that instead first if you like. I will update previous post link in a few.

Edit.. Also make sure that the md5 matches the zip that you download.
[Asus  Eee Pad Transformer Prime] hoya68:
Edit.. Also make sure that the md5 matches the zip that you download.[/QUOTE]

You got me with this comment. How do I check?
[Asus  Eee Pad Transformer Prime] flumpster:
Download this http://getmd5checker.com/download

and load the zip file you downloaded into it. It will show you a long number which should match the md5 I put under the download links.

If they don't match the file is corrupted on download.
[Asus  Eee Pad Transformer Prime] hoya68:
The md5's match
[Asus  Eee Pad Transformer Prime] flumpster:
Then try both roms but remember that the recovery is not going to work when you restore from them files as it is the stock recovery, so just try to get the rom working.

If you are still not getting it working then take a look at this.

http://xdaforums.com/showthread.php?t=2409602
[Asus  Eee Pad Transformer Prime] hoya68:
It worker. Every time I ran a command it would go out of nvflash mode. I would then go back to APX and run wheelie.exe and then run the next command. After I loaded the system image it rebooted properly. I did this with the 4.01 rom. Can I repeat the process using 4.1?

PS I am making a donation as thanks for your help.
[Asus  Eee Pad Transformer Prime] flumpster:
Don't worry about a donation mate.

If I was you now I would try and flash a version of TWRP on there for ICS.

After that you will be able to either run the downgrade zip in the second post of the hairybean thread to take you to 4.1 bootloader and a compatible twrp or you could flash the upgrade.zip to take you to the 4.2.1 bootloader and compatible twrp if flashing hairybean.

If you are just trying to get CM working you will want the downgrade.zip.

Try and get TWRP working on there first by flashing it in fastboot and make sure you get the ICS version.

Edit...

Here is the TWRP you want for ICS. http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.6.3.0-tf201-ICS.blob

Here are the instructions.
[Asus  Eee Pad Transformer Prime] flumpster:
First up, on jellybean there is no fastboot icon. You are instantly in fastboot mode as soon as you enter the bootloader.

I don't know what you mean when you say you are trying to flash the bootloader thru fastboot. What files are you using and where did you get them etc?

Did you manage to get twrp installed for ics?
[Asus  Eee Pad Transformer Prime] hoya68:
I didn't try ics first. I will do that and then go to jb

This is what I installed correctlt

UN-BLOB'D STOCK ICS 4.0.3 (9.4.2.28) ROM

- MD5 - a74e05be2d3aba2af5c970e30d3a3720

- Un-blob'd stock ICS 4.0.3 (9.4.2.28) ROM

- Completely unmodified
[Asus  Eee Pad Transformer Prime] flumpster:
You said you have Ics installed already. That's all I need you to do is to install the TWRP I linked you too earlier for ICS and then I will give you more instructions.
[Asus  Eee Pad Transformer Prime] hoya68:
twrp is now installed
[Asus  Eee Pad Transformer Prime] flumpster:
Ok mate.. One last thing. What rom do you want to end up with at the end?
[Asus  Eee Pad Transformer Prime] hoya68:
the latest stable jelly bean
[Asus  Eee Pad Transformer Prime] flumpster:
I have just sent you a PM with my google talk address in it. It will probably be easier to continue this there and not clog up all this thread.
[Asus  Eee Pad Transformer Prime] Cusciolino:
is it possible to create a guide for nexus 7 3g (2012)?

hosting a backups of system to recover hardbriked tablets

thank you so much
[Asus  Eee Pad Transformer Prime] RickoT:
I just wanted to thank you for this guide, it totally saved my ass! I had sold it on ebay, and when I went to update it it bricked the whole thing. This guide + flatline_tf201 completely saved me!

Thanks again!
[Asus  Eee Pad Transformer Prime] polymath257:
I want to make sure I understand a few details in this. I am on JB bootloader. When I made the blob files, I got

bootloader.ebt, recovery.bct, bricksafe.img, factory-image.img, and unlock-token.img.

I am assuming that bootloader.ebt takes the place of blob.EBT in the OP. Similarly for recovery.bct for blob.SOS.

If I get into trouble, should I also flash factory-image.img and unlock-token.img back to paritions 14 and 7?

If I want to preserve my current set-up, can I read the current partiton 6 and 8 and use them instead of the

stock LNX and APP blobs?

When does bricksafe.img come into play? Do I simply rawdevicewrite back to 0 2944 if required?

There are a number of other partitions listed in the partition table. Are these simply regenerated when required

or can they be flashed also? What are the advantages/disadvantages of doing so?
[Asus  Eee Pad Transformer Prime] dj_chapz:
Same here. Fully unable to come to the part to even try to restore although i have all the restore files....
[Asus  Eee Pad Transformer Prime] Frazazza:
Almost Bricked - Asus Transformer Prime TF201

Decided to root my TF201 and load the newest ROM.

Followed directions to get root, used flatline_tf201.img for recovery, and saved nvflash files to be 'brick-proof'.

Downloaded KitKat 4.4.1 and it didn't take .. after I had wiped my system.

Eventually only APX mode would connect to the pc.

The nvflash directions as detailed I had to modify to get my system back.

Comments:

My TF201 would reboot after each successful nvflash, and I would have to force reboot to APX mode and run wheelie to attempt the next one. Nvflashing blob.SOS failed every time in the order shown, and I tried someone's suggestion to download the latest twrp recovery and use that instead of blob.SOS, but it didn't work. Wild thought of trying the other nvflash commands AFTER blob.SOS to see if they would take. They did! So I proceeded to nvflash, reboot to APX, run wheelie, again and again until I had performed all of the nvflash commands, and lastly tried the blob.SOS (twrp recovery) and it rebooted to the TEAM recovery and I was back to Android 4.1.1 with 10.4.2.15. I didn't give up on rooting though!

Decided to try 4.3.1 instead of 4.4.1 and everything went smoothly. Performance greatly improved and I appreciate everyone's helpful comments and guides. Hope this helps someone else stuck on APX mode only!
[Asus  Eee Pad Transformer Prime] nikoltu:
Thank you so much for command list, saved my Prime from being just another brick in the wall :) Also if someone fails to bring it back to life and have factory-config.img (14) and unlock-token.img (7) for JBs just flash as the last two steps and Prime will reboot to android in a few. I figuered that some unloced primes need that token to vertify ROM cuz I flashed like 6 times before giving a try for my own generated images. After seeing unloced text in the up corner it booted to android. Though havent figuered out yet what for is bricksafe.img needed.
[Asus  Eee Pad Transformer Prime] njdvils99:
I was wondering if I could get a little help from the anyone on this. I am trying to follow the instructions on this page:

http://xdaforums.com/showthread.php?t=1927818

I bricked it. Stupid move I know. My question is this. While using the method described on the above page I am having trouble. The first step works just fine. I run the wheelie and it tells me I am 100% and ready to go. But after that, none of the following commands work. I extracted all the files called for, put them all in the same directory, but when I enter ANY of the commands, I get a separate command prompt window that opens with an instruction manual. It does nothing to the tablet. And when you press enter all the way thought the end, the command box closes and then I am back to where I started in the original command box with the next prompt line ready for input. What the hell am I doing wrong? I apologize if this seems ridiculously easy, I am a noob and am just trying to unbrick and get back to stock. Any help would be appreciated.
[Asus  Eee Pad Transformer Prime] KlipperKyle:
Darn! Sounds like a Windows thing (and I'm a Linux user). It's also been a while since I played with wheelie and nvflash (I still have to update my old TF201's bootloader; I just never got around to it).

Anyway, quick sanity check:

If I remember correctly, either wheelie, nvflash, or both have to run as an administrator on Windows. (In Vista/7/8, this means right-clicking on "Command Prompt" in the Start Menu and selecting "Run as Administrator.")

You should plug in your TF201 directly to a usb port. You should not be plugged into the keyboard dock when running these commands.

To enter the special APX mode, power the TF201 off. Then, hold the volume up button, and press/hold power while continuing to hold the volume up button. You should feel a vibration, but the screen should remain blank. After that, you can run the wheelie command.

Check which directory you are in with cd and dir.
[Asus  Eee Pad Transformer Prime] njdvils99:
Thanks for the reply. I am running windows 7 and I am the only user on the computer so there is no option for run as administrator. It lets me open the command box and it fully runs the wheelie and the last line says:

[!] Done your device should now be ready for nvflash.

The tablet then reboots out of APX mode and the boot screen comes up with the asus logo. In the top left hand corner it says:

"Entering Nvflash recovery mode / Nv3p server" and under that it has the Chip Uid.

So do I continue working from this state or do I need to reboot into APX mode again?

The tablet is connected directly to the computer with no docks of any kind just the usb cable.

I have searched the directory to make sure it is correct and the right files are there.

I hope this info helps. Thanks for your time.
[Asus  Eee Pad Transformer Prime] KlipperKyle:
That sounds normal. You should be able to run nvflash commands from this state.

Make sure that Windows can see the TF201 in nvflash mode. (Control Panel -> Administrative Tools -> Computer Management -> Device Manager; look for your TF201)

Also, make sure that nvflash can see the TF201. (I can't remember the command offhand, but I'm sure it's listed in "nvflash.exe --help")

I still have no idea why nvflash is opening its own command prompt window. This is not normal. (And based on your description, it sounds like output is being piped through "more")

When I was talking about launching a command prompt window as administrator, right-clicking on the shortcut in the Start Menu is necessary because of UAC (Vista and later). UAC prevents normal programs from running with unfettered permissions (even when you are logged on as an administrator). It's kinda confusing, but that's the way Microsoft built it.

(I consider myself a Linux user, but I still have to deal with Windows quite a bit. That's how I know some of these things.)
[Asus  Eee Pad Transformer Prime] KlipperKyle:
I'm not quite sure what nvflash you have, but it's not the nvflash you are supposed to be using for the TF201. (I think you have this nvflash, which appears to be for flashing a BIOS on certain NVIDIA graphics cards.)

After investigating, I found that the nvflash and wheelie links in the OP are dead. So, I have attached the copies I have somehow retained from androidroot.mobi in September 2012.

You can read their guide about nvflash and wheelie on archive.org (as the original blog post was deleted):

<http://web.archive.org/web/20120820182123/http://androidroot.mobi/t3_nvflash>

Hopefully that will help. Good luck!

(Ironically, I posted here last November about dead links in the OP.)
[Asus  Eee Pad Transformer Prime] njdvils99:
Thanks so much for the info. I downloaded the new files you provided, extracted everything, moved the blobs I needed and started over.

Now when I try to start the wheelie, I get this:

[-] Error 3 receiving response from command

So how did wheelie work before, and now this? This is beyond frustrating. Thanks so much for your time.

---------- Post added at 02:39 PM ---------- Previous post was at 02:20 PM ----------

So it turns out that the new wheelie I downloaded wasn't the newest version. So I swapped it with the one that I had been using and it worked. SO now when I enter the commands, it will send xxxxxxx bytes and then say BLOB.xxx sent successfully. But, after EACH blob, the device reboots to the recovery screen. So I followed the steps to get each file downloaded and now we are getting a lot farther than I was.

Unfortunately I have hit another snag. Now instead of booting twice and then bringing me to the recovery screen, it boots the asus screen, then shows the droid with the blue status bar for a split second, then shows the droid on its back with the red exclamation point sign for approx 2-3 minutes.

The problem is it does the above, then reboots, then does it all over again. So I have made progress, but am now here. Any suggestions? Is this newest issue something I may be able to tweak using the recovery?
[Asus  Eee Pad Transformer Prime] KlipperKyle:
Will you please attach the version of wheelie that worked for you? I may need the newer version when I finally get around to messing with my TF201's bootloader.

That sounds like you are flashing a bad image somewhere along the line. I know for a fact that the links to the unblobbed images in the OP are dead. Where did you find the unblobbed images?

What I ended up doing was downloading the BlobTools and the Asus firmware package. Then I used the BlobTools to unblob the Asus firmware package. Unfortunately, it's rather complicated because you have to compile BlobTools. (See my earlier post from last November.)

Edit:

I don't know how I missed this. I happened to visit the home page of androidroot.mobi, and guess what I see: Introducing Flatline ! (Nvflash for Jellybean N7v1, T201, TF300T, TF700T)
[Asus  Eee Pad Transformer Prime] njdvils99:
I got the blobs when I was originally trying to back everything up. I used motochopper and extracted them from my tablet before the brick.

Here is a copy of the wheelie I used.

At this point, since it is actually trying to boot and not bringing me to the recovery screen is there any way I can either use the sideloader of a micro sd and just install a rom that way? I'm just trying to keep it as simple as possible as many of these have been over my head. Thanks again.
[Asus  Eee Pad Transformer Prime] njdvils99:
Update: I redid all the steps from page 1, used the wheelie I attached and the flash you provided. Did it step by step, and KABLAMO! I have 4.1.1 back on my TF201!! I can't thank you and this forum enough for your help. I made a donation because I feel your and this sites help is worth every penny. Its not much as I haven't worked in awhile, but its something and I hope it helps. Thank you again for all your help, it is appreciated more than you know.
[Asus  Eee Pad Transformer Prime] KlipperKyle:
I'm glad I can help. Have fun!
[Asus  Eee Pad Transformer Prime] easylistener:
Does anyone have the windows nvFlash binary/executable files? I use the links and they are not longer there...I bought a tablet with the .28 bootloader unlocked running 4.0.3 and want to install nvflash and root with custom roms......after some reading it sure seems like if you have the option to use this method you would be foolish not too.....Or should I update and use this guide?
[Asus  Eee Pad Transformer Prime] KlipperKyle:
The website did a little reorganizing.

NvFlash Guide: <https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/>

It looks like a fair amount has changed since I originally backed up my bootloader. Be sure to read through the guide thoroughly. Good luck!
[Asus  Eee Pad Transformer Prime] easylistener:
Thanks for helping me out but that is for jellybean and I have ice cream sandwich... I didn't think I could use it.... Can I use jellybean stuff for ics? I am really stuck now.... I bought this tablet used and it has trwp 2.2.2.0 on it already.... It's asking for a password so now I am lost on where to start in the whole process.... I don't know if I can just ignore it and install nvflash and keep going thru the instructions or if I have to start some where else.... It is asking for a password so I don't think I can do anything with it.... I also don't know if it is rooted and just missing superu.... This stinks....
[Asus  Eee Pad Transformer Prime] kokopuphz:
Try this post. Seems similar to issue that you are having.

http://xdaforums.com/showthread.php?p=30789225

Post 399
[Asus  Eee Pad Transformer Prime] B3rt:
Stuck on updating...

Hi, i bricked my tf 201.

I formatted the internal SD, no partitions are present anynore :(

I can access fastboot but cannot install any mod because i cannot see the external SD card, the internal SD is blank....

I used this topic manual to restore but i am stuck...

I entered APX mode and used wheelie, this is what happens:

c:\asus>wheelie.exe --blob blob.bin

Wheelie 0.1 - Preflight for nvflash.

Copyright (c) 2011-2012 androidroot.mobi

========================================

Waiting for device in APX mode...

[=] Chip UID: 0x15c7d7a47580e1b

[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3

[+] Sending bootloader...

Sending file: 100 %

[!] Done - your device should now be ready for nvflash

--- TF201 reboots in nvflash mode and i continue:

c:\asus>nvflash.exe -r --download 4 blob.EBT

Nvflash v1.13.87205 started

[resume mode]

padded 3 bytes to bootloader

sending file: blob.EBT

/ 1558592/1558592 bytes sent

blob.EBT sent successfully

-- TF 201 reboots again but now only says 'this device is unlocked', nothing happens anymore... (waited 1 hour)

When i continue on the command prompt i get:

c:\asus>nvflash.exe -r --download 5 blob.SOS

Nvflash v1.13.87205 started

[resume mode]

connection failed NvError 0x30011

c:\asus>

I tried several times and eachtime same result...

I do have (and used) the original blob files etc

What do I wrong here, can someone please advise how to fix this?
[Asus  Eee Pad Transformer Prime] flumpster:
After it reboots you are going to have to go into apx mode again and enter wheelie again before continuing with the next command.
[Asus  Eee Pad Transformer Prime] B3rt:
If i understand correctly:

1 - go in apx mode --> wheelie -> nvflash blob part 1

- manual pad reboot, because nothing happend

2 - go in apx mode --> wheelie ->nvflash blob part 2

- manual pad reboot, because nothing happend

3 - go in apx mode --> wheelie ->nvflash blob part 3

- manual pad reboot, because nothing happend

repeat step 2, 3 until all steps are done, correct?

I find this strange, the manual does not suggest thuis in any way, if i understand it correctly it should be done in 1 APX/nvflash session...

Also i tried this already but the rebrick does not work, when done it boots up and stops in 'this device is unlocked', when i go into USB mode there are no files/partitions present. My pc (usb mode) only detects 1 drive which is completely empty, i can upload files onto it.

Who can help/advise?

i tried it again and now i even cannot get in the recovery section anymore..

When i start power+vol down it bootup and the 4 icons are shown, when i choose 'rck' it shows a 'dead droid' and stops.

This happend after i tried flashing the steps i descriped.

I still can get into APX mode.

Please can someone help, have no idea how to fix this....