yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] Restorer:
Full instructions: http://xdaforums.com/showthread.php?t=1426502

It's the thread below this one - so you didn't have to look too far ;)

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

You don't say what ROM you are on. The instructions for NVFlash in this thread are only for ICS. If you have a JellyBean bootloader you need to use the link provided by joshkun in the post above yours:
[Asus  Eee Pad Transformer Prime] CrazyKoala:
Hey.

I am running ICS.

Bu right now I am facing another issue. My prime is no more detected over USB. No idea why :(
[Asus  Eee Pad Transformer Prime] joshkun:
in which case giv os more details. :confused:
[Asus  Eee Pad Transformer Prime] CrazyKoala:
I am running android 4.0.3
[Asus  Eee Pad Transformer Prime] joshkun:
Dear friend try a fresh clean install after a full wipe and then use ICS guide step by step you can not mix the bootloaders it must be the same bootloader. Use this guide step by step you can finde some guide on the youtube too. :D
[Asus  Eee Pad Transformer Prime] jg10571:
This worked like a charm. Have all my backups now...let the flashing begin..
[Asus  Eee Pad Transformer Prime] frusso:
Hi

I have a problem in flatline recovery. When i boot in recovery i found this messages

FlatLine CWM Recovery v1.0RC1
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

and of course i unable to run the step1 inside a advanced --> wheelie menu.

I have installed the ROM 4.1.1 (stock-v411-Build-10.4.2.18) caming back from Hairy bean

I note now that when i boot the device i read this

Key driver not found ... Booting 05
[CODE]Android cardhu-user bootloader <1.00 e> by "WW_epad-10.6.1.8-20130225" A03

the device boots normally in android but i am unamble to create the nvfiles

any suggestion ?

EDIT : I have found the now i am unable to do a backup with TWRP because the file sytems are not mounted correctly (/cache and /external_sdcard). Most probably this happen because the hairy rom have changed something. I need to investigated ...
[Asus  Eee Pad Transformer Prime] :
Where are the actual tools i can download, all i find on their site is a guide that leads me in circles.
[Asus  Eee Pad Transformer Prime] flumpster:
It sounds to me like you were still on the tf300 bootloader and when you downgraded back to 4.1.1 rom you never downgraded the bootloader.

If this is what you have done then try using the files for the TF300 instead.
[Asus  Eee Pad Transformer Prime] frusso:
Yes, you have right.

As i know the hair roms are based on tf300 and if this is the case you have right

but i have solved

First i have restore my ICS 4.0.3 through my nvfiles

after installaed an ics recoevery and then installed an old version of cm10 with jb bootloader

now i have reinstalled latest twrp and the craigomez rom

now i hope to create the new nvfiles to restart, in case of necessity, form JB instead of ICS
[Asus  Eee Pad Transformer Prime] flumpster:
Wait a sec mate.. If you have nvflash files already you do not need to do it again.

The ones you have from the ICS nvflash will always work.
[Asus  Eee Pad Transformer Prime] frusso:
Yes i need because my nvfiles restore the ICS version after i need the upgrade rom and bootloader.

With a new procedure i have extracted the nvfiles directly for JB.

Inviato dal mio ZP990 utilizzando Tapatalk
[Asus  Eee Pad Transformer Prime] flumpster:
You do not need to mate.

If you created NVFlash files while on ICS you do not need to do it again for Jellybean.
[Asus  Eee Pad Transformer Prime] polymath257:
What is the status of nvflash starting from the 10.4.2.18 bootloader? I saw some people having problems with an 'error 3'. has that been resolved? I am using a linux Mint system, currently have twrp 2.3.0.1 and CM 10.2. If I do this procedure, can I reflash twrp?
[Asus  Eee Pad Transformer Prime] CrazyKoala:
Hi. I am using ICS still (4.0.3), the official update.

I'm not too sure which version of the guide to apply between those 2 :

https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash/

https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/

Any help ?
[Asus  Eee Pad Transformer Prime] CrazyKoala:
OK I tried the recovery flash from there : https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/

but recovery doesn't seem to work.

It remain on "Booting recovery kernel image"

It says above "TW_epad-9.4.2.21-20120323"

Could it be that I have a ICS bootlader, and so this flatline thingie cannot work with it ?
[Asus  Eee Pad Transformer Prime] marmelo:
Hi, thanks for the tut. But did you had the nvflash enabled when you used this tutorial? Because i had no luck until now
[Asus  Eee Pad Transformer Prime] brantje:
-nvm-
[Asus  Eee Pad Transformer Prime] wolwe:
FlatLine CWM Recovery v1.0RC1
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

I tried to went on from HairyBean (TWRP / JB Bootloader) to a new KitKat ROM, but failed while preparing my NVFlash Blob Files via FlatLine (Tutorial https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/) with the same error.

I managed to create some blob files, but they don't work.

(Incorrect BLOB selected. nverror: 0x4)

Can anyone give me a hint? ;)
[Asus  Eee Pad Transformer Prime] flumpster:
I can give you one big hint. You flashed a different recovery onto the hairybean bootloader which it specifically says not to do in the hairybean thread.
[Asus  Eee Pad Transformer Prime] wolwe:
You're right, that is a big hint. ^^

Stupid me.

So im screwed at this very moment, or is there any way out, getting KitKat on my TF201?

My OS is still booting though.

Thanks anyway.
[Asus  Eee Pad Transformer Prime] flumpster:
http://xdaforums.com/showthread.php?t=2654694
[Asus  Eee Pad Transformer Prime] wolwe:
Yay, looks like fun. ;)

Allright, thanks a lot for your patience flumpster!
[Asus  Eee Pad Transformer Prime] fatdoggie:
Somehow, I messed up while attempting to flash CM11 and have gotten stuck on the Asus logo screen and cannot re-enter recovery. It doesn't show the "Device is UnLocked" as it normally did- it just hangs forever.

I can get into the APX mode, have the latest Naked Drivers loaded (tried on x64 and x32 Windows) and the device shows up in device manager. I have also tried using Linux and the device in AXP mode is shown in the lsusb output. I've tried this with multiple USB dock cables.

No matter what configuration I try, I have been unable to get wheelie to communicate - it always dumps out with an "Error 3" as below:

C:\nvflash>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15d0787bc641408
[=] RCM Version: 0x30001

[-] Error 3 receiving response from command

I found several mention of a Linux version of wheelie 0.2 that is supposed to solve this for some, but the androidroot.mobi site is a bit of a mess and all the older links are broken.

OK, got it working again. I left the tablet on the Asus logo screen until the battery died, then plugged it in and charged it for a couple hours.

Attached it to a linux machine and followed this guide: http://rootzwiki.com/topic/35086-guide-nvflash-general-users-guide-unbrickrecoverdowngradeupgrade-tf201/

Just using wheelie and flashing the images wasn't enough - I had to use the "semi-automated recovery" script, which also rebuilds the partitons and sends over additional configuration.

On the linux side, the NVFlash is 32 bit, so I had to install the i686 version of libstdc++, YMMV.
[Asus  Eee Pad Transformer Prime] ojessie:
Hi,

I'm having exactly the same problem. Coming from HairyBean tried to install CM11 and the same as above.

Does anyone know how to fix it with a Windows PC. ... By the way I'm not having the Error 3 with my "old" wheelie ... just getting it when installing a newer wheelie. But at the end it doesn't matter the result is the same. Prime freezes at the Logo cannot access recovery or fastboot just wheelie "old" is working installing all the blobs doesn't fix.

Help would be highly appreciated.

Thanks
[Asus  Eee Pad Transformer Prime] outbackpaul:
I get all the way to nvflash --resume --read 14 factory-config.img and then I get an error "file create failed NvError 0x30010".

I've rebooted and still get the same error. If I close out the command prompt and try again it just hangs.

Any help appreciated.
[Asus  Eee Pad Transformer Prime] outbackpaul:
Ok, I figured it out. I had to open my command prompt as administrator.
[Asus  Eee Pad Transformer Prime] stuartb88:
So great community developers like wugresh, chainfire cfrooter, unified android tool developer etc that creates adb GUI devices to semi automate processors are doing the android Dev community a disservice? These are the best devs in the community and they develop programs and apps to help others for free, and are usually very happy to offer help and clear concise how to's to newer people in this community. Its called progress, that's what developers do, write computer programs to simplify tasks ( jobs) for the wider community, you wouldn't have a PC or even a mobile phone if nobody helped anybody by not developing software tools... I agree the tf 201 is a *****, I had one for years, it unlocked via Asus method, rooted for all intensive purposes, su and busybox ran, all rooted apps ran, but it could not install Roms from twrp or cwm, it would stall halfway through, I had to reboot to recovery then reboot.? This went on for months on end, I'd leave it a box somewhere and pull it out again months later when I was ready for the challenge, or bored!. Untill eventually in frustration I totally bricked it, by that time I already had a nexus 10 & 7 so it was outdated and retired anyway. It was also the ist android I learnt these methods on.

Point is if some good talented Dev who can actually write programs ( as against those knowing how to enter a bit of code in adb, and think they are the ducks nuts because of it and anyone who hasn't grasped it yet are morons ) then maybe I wouldn't have gone through all that frustration and could have had an updated tf201, as Asus only did one update in the three years I had it., it was a great concept android device and I believe the first detachable, great build quality but the 1gb ram basically outdated itself too soon.

Anyway I get sick of reading these replies like just google it,or if you can't use code in adb shell then you shouldn't be custom romming your phone.

Everyone starts somewhere and usually asks for a bit of guidance when they do, even you criticalis I bet, so I would say if you can't add something constructive or positive to the conversation then why bother answering at all? Forums are communities, which mean all members are part of that community, so show some respect and try and help people and if you can't, or just an angry young dude on a negativity troll trip, try and curtail your incessant need to put down others, when your feeling that way just walk away from your computer and go breathe some fresh air, take a walk, have a break, you will feel so much better asfterwards
[Asus  Eee Pad Transformer Prime] tux-friend:
Hard brick although a working blob.bin file has been created?

First of all, I would like to express my thanks to all developers who made nvflash working on the TF201! Your support is really appreciated and I can confirm that it already saved me from hard bricking my Prime in at least two cases. :fingers-crossed:

However, the best preparation is not always a absolute guaranty to avoid hard bricking as I have faced now: Although, I created a working blob.bin file by flatline recovery, I can't get into apx mode anymore. Maybe, I made some stupid mistakes, I don't exactly know :crying:. I tried to flash multirom on my TF201 device 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, as mentioned above my tablet is not recognized as apx device on my PC anymore after connecting it via USB cable. I was not successful, neither under Linux nor under Windows. Under linux I could not find any entry for the device by checking the lsusb output.

Is there any idea, what I still can do? Any constructive advices are very appreciated!

--

Many thanks
[Asus  Eee Pad Transformer Prime] AndyMclamb:
Hi Guys My Prime is with unlockedBootloader In the Stock room , i have To Root to be able to Usa NVFlash and Save the Blobs files ,someone can provide me the link how to save my blobs step by steps ? Pls and Thank you all
[Asus  Eee Pad Transformer Prime] rayman:
To preempt any silly questions:

It's still linux. Just 32-bit and statically compiled. It should be more compatible across different linux distributions (both 32-bit and 64-bit).
[Asus  Eee Pad Transformer Prime] beekay201:
i'll take no awnser as a "yes".

Another question, can I use fastboot binary built from aosp tree?
[Asus  Eee Pad Transformer Prime] lilstevie:
I personally feel there isn't much difference in doing it once, or many times, if it makes you feel better, go for it, but backing up your per-device data with nvflash is proof that it works before you even put yourself in a position where bricking is a risk, the biggest part of the risk is the first step
[Asus  Eee Pad Transformer Prime] beekay201:
Sure, I get what you're saying. The biggest part of the risk? I'm ready to take it.

Just need to know if I can use fastboot binary built from aosp tree (i use fastboot with my nexus, don't even have to use sudo - my user has been added to adbusers group and is the owner for the udev rule).

I had wondered if the Prime doesn't need a second rule for fastboot? I've seen the post earlier about it, and it's like I have now, only one rule for adb.

edit: nvm, I'll use fastboot binary found on sdk, works.

edit: posting as I go, it seems.

I had already copied my blob.bin there, but I wasn't sure; Well, no biggie, fastboot would probably have complained if file was missing :D

edit:
[Asus  Eee Pad Transformer Prime] Subsonic44:
I'm sooooo close! I enter ./wheelie --blob blob.bin from an elevated terminal and it just sits at "Waiting for device in APX mode...
[Asus  Eee Pad Transformer Prime] beekay201:
Try powering down the prime (with it already connected to usb), then Power+VOL UP for 5 seconds, let go, the screen will stay blank, but if you 'lsusb' you shall see

when device is in fastboot:

when device is connected to adbd:
[Asus  Eee Pad Transformer Prime] otto888:
Someone working at ASUS is thinking this right now. Has anyone figured out where the splash screen(s) is stored in the bootloader? I know that the TF101 guide will be little to no help...
[Asus  Eee Pad Transformer Prime] Subsonic44:
OK, it must be because I'm attempting it from a VM. When I type lsusb I get "Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet

Guess I will get to installing Mint on my old laptop! Will I need to install ADB drivers in linux?
[Asus  Eee Pad Transformer Prime] beekay201:
Great. Just great. :D

1- unlock/download the tf201_nvflash.tar.bz

2- fastboot -i 0x0b05 flash bootloader ebtblob.bin

3- fastboot -i 0x0b05 boot nvfblobgen.img ('fastboot reboot' when you're done)/grab the files from /sdcard/AndroidRoot/

4- sudo ./wheelie --blob blob.bin <------------ don't reboot here <--------------------- *

5- sudo ./nvflash --resume --rawdeviceread 0 2944 bricksafe.img

6- sudo ./nvflash --resume --read 14 factory-config.img

7- sudo ./nvflash --resume --read 7 unlock-token.img

done. now:

8- sudo ./nvflash --resume --go

9- backup all those files, along with those that we got from /sdcard/AndroidRoot/ earlier in the process.

* blob.bin is one of the files we got from step 3; copy it into wheelie's folder.

THANKS GUYS!!! :D

suggestion: move that

to after getting the backups (factory-config.img, unlock-token.img and bricksafe.img). It's misleading, IMO.

edit: Not sure why I managed to run wheelie on the first time, without root permissions. Oh well.
[Asus  Eee Pad Transformer Prime] brantje:
Maybe a dumb question, but for what is nvFlash?

Will a normal user from a custom rom ever need it?
[Asus  Eee Pad Transformer Prime] rayman:
Surely they must be thinking - yay, I don't have to find out what nvflash is now! ;)

Seriously though, they claim to have been working on providing nvflash for unlocked users. We did just that. Since it only works on unlocked devices, it preserves the sanctity of DRM keys as well.

http://xdaforums.com/showpost.php?p=27633137&postcount=4
[Asus  Eee Pad Transformer Prime] Subsonic44:
I'm getting closer... I installed VM Ware 8 since it looked like you had success with it. I can attach my to the VM under removable devices - NVidia USB Device. When I use lsusb, I get Bus 001 Device 002: ID 0955:7330 NVidia Corp.

But when I send it ./wheelie --blob blob.img

I get:

libusb:error (op_open) libusb requires write access to USB device nodes.

libusb:error (op_open) libusb couldn't open USB device /dev/bus/usb/001/002: Permission denied.

How do I give it write permission?
[Asus  Eee Pad Transformer Prime] rayman:
Both yes and no.

Running our bootloader + booting the image, provides a set of blobs that allows you to recovery from any brick. Combined with doing the backups we recommend, you are 100% unbrickable.

This means, that if your tablet fails while e.g. flashing a custom rom or even flashing a stock rom (more likely ;)), it will be possible to recover your tablet. But only if you have those files stored somewhere safely. The files are unique per-device, so you can't use someone elses.

As previously mentioned, there *is* a slight risk in doing this procedure. In practice, it's about the same risk as flashing an ASUS OTA update on a locked device.
[Asus  Eee Pad Transformer Prime] beekay201:
Use sudo to escalate permissions. I refered it in my post, a couple of posts back.

@rayman, can we still flash blobs over with fastboot? Example: a custom recovery.

sent from my tf201
[Asus  Eee Pad Transformer Prime] Subsonic44:
OK... I can now successfully use the wheelie command. I typed ./wheelie --blob blob.bin and it sent the file and my prime booted into bootloader. However, when I type ./nvflash --resume --go I get ./nvflash: No such file or directory. I have the files in a folder I named asus and it contains wheelie, nvflash and blob.bin. I did a chmod +x on both wheelie and nvflash. Something tells me I need to install some package...
[Asus  Eee Pad Transformer Prime] stinebd:
I believe I demonstrated quite well that the human/moron element adds a bit of zest to the process also. ;)

In other words, the risk isn't too bad as long as you actually follow the instructions.
[Asus  Eee Pad Transformer Prime] UPEngineer:
I had the same thing happen to me. You need to add the usb device configurations to /etc/udev/rules.d/99-android.rules

Make sure at least the following two lines are in there.

#Asus

SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"

#NVidia

SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"

sudo service udev restart

Unattach and then reattach the Nvida Device. It should work then when you boot into the ATX Mode. Worse case, reboot the VM linux and retry it.

Works like a champ after that.

Hope this helps.

Scott
[Asus  Eee Pad Transformer Prime] Subsonic44:
THANKS ALL! I remembered reading this a while back: ok so anyone running 64bit ubuntu and not able to execute nvflash ... run this first

sudo apt-get install lib32stdc++6

After doing that, I now have all my back up files! Feels great to be "brick proof"!

Thanks again for all the pointer to a linux novice.
[Asus  Eee Pad Transformer Prime] JaceAlvejetti:
Everything done and done once i relized you have to run wheelie to get into nvflash, other then that flawless!
[Asus  Eee Pad Transformer Prime] rayman:
No. You need a "raw" android boot.img in the new bootloader.

You can use our blobtools available at github.com/androidroot/blobtools to unpack blobs so you can flash directly.

Blob flashing still works if you flash through update.zips/staging partition.
[Asus  Eee Pad Transformer Prime] djkinetic:
Question, would wheelie work on an already semi bricked/bricked device, asking this before I send off my prime to asus in hopes they can reflash the device.
[Asus  Eee Pad Transformer Prime] brakeb:
SON OF A... I just gave up three days ago of ever having a fully rooted TF201, and had a Samsung Galaxy 2 10.1 sent to me... NOW THIS!?

Well done everyone!!! Guess I'll be figuring out how to setup adb on a linux machine... looks like 64-bit Mint is the way to go...
[Asus  Eee Pad Transformer Prime] lilstevie:
depends, if you have fastboot access there would be no point in sending it off because you could unbrick it normally. But as long as you have access to fastboot you can apply this
[Asus  Eee Pad Transformer Prime] djkinetic:
Well here in lies my problem, if I do power+volume down it boots straight to CWM Recovery, i don't get a choice to press volume up to boot into recovery like normal or not press volume up so that i get the choice for fastboot/cold boot linux, all it does is boot straight to CWM...now if i do volume up+ power it boots to APX mode, either way when I connected it to the PC it gives me an unknown device error, and i've tried uninstalling the drivers from my gnex atrix and gs3, tried resetting up my adb, still can't get any drivers for the Prime to install...this is on windows...so i figured ok mayb my Mac will read it since its unix still no luck there...so basically i'm hoping that i can get nvflash to recognize the device in Linux and mayb go from there..now if ADB reads in linux i could just issue the ADB command to fix my brick as outlined in the 1a section of the unbricking section...but in case that doesnt work trying to see if nvflash/wheelie can be of any use.
[Asus  Eee Pad Transformer Prime] lilstevie:
unless you can get adb access from CWM there is no chance of it helping you out, the steps at the start are required for wheelie to work
[Asus  Eee Pad Transformer Prime] djkinetic:
ugh doesnt look good then...i cant figure out what was so different that my fast boot option basically got wiped...all i did was hit reboot to recovery when i shouldnt have in AOKP which is how I got the brick..note to self read up on updates in the future lol.
[Asus  Eee Pad Transformer Prime] lilstevie:
try getting it on linux, and without the dock connected
[Asus  Eee Pad Transformer Prime] djkinetic:
just tried in linux and no go, lsusb doesnt even list it connected to the pc, if i plug in my gnex or gs3 lsusb will show them plugged in, the prime in recovery or apx mode doesnt show up at all in ubuntu...so pretty much i think the only option is to phone up Asus and maybe get lucky unless you can think of any other way to get it to at least show up in linux...if they charge to much to recover it then its off to craigslist/ebay heh.
[Asus  Eee Pad Transformer Prime] lilstevie:
it could be your cable, you really need to try and eliminate that being the issue, the easiest way is if you have another eeepad transformer range device, or know someone who does, and try your cable on their unit or their cable on yours.