[TOOL]TF201 NVFLash [Updated 21. July]
- Thread starter rayman
- Start date
-
- Tags
- apx development nvflash tf201
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.
Hi
I have a problem in flatline recovery. When i boot in recovery i found this messages
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
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 ...
I have a problem in flatline recovery. When i boot in recovery i found this messages
Code:
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_logand 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
Code:
Key driver not found ... Booting 05
[CODE]Android cardhu-user bootloader <1.00 e> by "WW_epad-10.6.1.8-20130225" A03the 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 ...
Last edited:
K
kalparker
Guest
Where are the actual tools i can download, all i find on their site is a guide that leads me in circles.
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.
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
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.
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
With a new procedure i have extracted the nvfiles directly for JB.
Inviato dal mio ZP990 utilizzando Tapatalk
You do not need to mate.
If you created NVFlash files while on ICS you do not need to do it again for Jellybean.
Last edited:
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?
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 ?
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 ?
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 ?
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 ?
in which case giv os more details.
Hi, thanks for the tut. But did you had the nvflash enabled when you used this tutorial? Because i had no luck until now
Code:
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_logI 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.
Code:
(Incorrect BLOB selected. nverror: 0x4)Can anyone give me a hint?
Code: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.
Code:(Incorrect BLOB selected. nverror: 0x4)
Can anyone give me a hint?
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.
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.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
108After much hard work and scary semi-bricks, we are proud to finally provide nvflash to the masses!
This release allows unlocked devices to create a set of device-specific files that lets you access nvflash.
Once the procedure is done, you will always be able to recover any software brick (even bootloader!) as long as you keep your files safe!
NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
More details at http://androidroot.mobi/?p=452
Important note: We kind of forgot to clarify what the license for wheelie was so here goes. Due to the nature of wheelie and the importance of people always using the latest version, Wheelie is NOT redistributable! You are allowed to download it and use it, but you are not allowed to redistribute it in any way - this means no GUI's including it, no reposting zips/tar.gz's and similar! At a later date, we will be releasing our source code and relicense it as GPL.
Update log:
- 18. July: Added windows version!
- 21. July: Clarify License
Enjoy
- AndroidRoot.Mobi Team
NOTE: If anyone wishes to donate, http://androidroot.mobi/donations/ is place to do it! DO NOT DONATE DIRECTLY TO ME.37nvflash binary package for tegra 3 ICS for win32-x86/x64
attached is a working tested nvflash binary package for tegra 3 ICS win32.
included is also fastboot and adb executables.
extract this zip and all wheelie win32 executables in the same directory and follow the directions on http://androidroot.mobi/?p=452 as rayman has stated.
a couple things to note:
MAKE BACKUPS OF YOUR BLOBS
entering apx mode was not very clear.
hold power + vol up until you feel the tablet vibrate
release power and volume up and immediately press volume up for about 3 seconds
then release volume up.
the screen will remain blank but will be in nvidia apx mode.
you will then need to install the apx driver from the universal driver package here on xda.
edit: fyi I have nothing to do with androidroot.mobi team.
I have a prime and spent the last two days trying to find the nvflash binaries on the hacked nvidia site and thought I would share.35Here's your Windows How To
Ok, took me a while to find everything I needed and make sure everything was setup just right for this to work, but finally got all my backups made. So, I figured I'd make a how to a save a few people some time.
**Note** This is for windows, windows 7 (x64) spicifically, but may also work on (x86).
1) Plug in you tablet to your PC.
2) Download the most recent version of Universal Naked Drivers here:
http://forum.xda-developers.com/showthread.php?t=1426502
3) Go to Device Manager (Control Panel -> Device Manager), select any instance of Asus or TF201, and uninstall the current driver, and also choose "delete the driver software for this device." If you were already using a older version of Naked Drivers, then you places to delete drivers are under Android Device -> Asus Transformer Prime ADB Interface, and Portable Devices -> Transformer Prime TF201.
4) Unplug your tablet, and turn off internet, just so windows doesn't go and try to download anything when you plug it back in. Plug you tablet back in and if you see it trying to install a driver, hit the X on the notification in the system tray.
5) Go back to Device Manager, select your device (should have a ? or ! by it now, since it doesn't have drivers). Right click on it & choose Update Driver Software. Browse Computer for Driver Software, Navigate to the folder where you unzipped the driver package you downloaded earlier (make sure that the include all sub-folders is checked), select Next. A Warning may come up about security, choose to install anyway.
6)Download the attached .zip, which includes blob & wheelie files provided by androidroot.mobi and the NV Flash files provided by joe ferreira. Make sure to thank both.Deleted upon developer request... Use the OP to find the proper tools.
7) Unzip the attached file, and open a command prompt in the folder (Shift+Right Click). Follow the instructions here: http://androidroot.mobi/t3_nvflash/
You do not need to issue the "$" in front of the commands.
8) After you reboot & before moving on to the "Accessing nvflash" part of the guide linked above, grab the files that were made @ /sdcard/AndroidRoot and copy them to the same folder on your PC as all the other NVFlash files... Continue with the linked guide.
9) Once you put your device in APX mode for the first time and connect it to your PC, go to Device manager and you should see a APX device with a ! symbol. Just like before, right click on it and choose update driver, navigate to your drivers folder you downloaded earlier, and update the driver. You should now be able to successfully issue the "wheelie --blob blob.bin" command and be able to move onto the next step. If your device is still showing up as Unknown device, you didn't install the drivers right, and you need to uninstall them again, and re-install them as stated.
10) I issued the NVFlash Commands in this order:
- wheelie --blob blob.bin
- nvflash --resume --rawdeviceread 0 2944 bricksafe.img
- nvflash --resume --read 14 factory-config.img
- nvflash --resume --read 7 unlock-token.img
- nvflash --resume --go <---- This reboots your device, so issue it last.
11) You should be all set to go, with all your files in one folder.... go get your brick on!!! :laugh:11fastboot/blobs after the nvflash fix
flashing a recovery like twrp:
say you get a copy of twrp from http://teamw.in/project/twrp2/93
it comes for the tf201 in a .blob format (openrecovery-twrp-2.2.0-tf201.blob)
at a commandline type
blobunpack openrecovery-twrp-2.2.0-tf201.blob
this will give you a file called openrecovery-twrp-2.2.0-tf201.blob.sos
this is the recovery.img file
in nvflash
nvflash -r --download 5 openrecovery-twrp-2.2.0-tf201.blob.sos
in fastboot
fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.2.0-tf201.blob.SOS10
No, no guide yet.
We purposedly left out the procedure for doing a full restore until it is explicitly required.
Our experience is that if we give the instructions for this, people will do it for every little brick that could easily be fixed in other ways and it's just not a good idea
For 99% of cases, you can restore by simply flashing the partitions that have been broken, e.g.
- Bootloader having issues => nvflash -r --download 4 bootloader.bin
- Broken or stock recovery => nvflash -r --download 5 recovery.img
- Broken or stock boot partition => nvflash -r --download 6 boot.img
- Broken system partition => nvflash -r --download 10 system.img
stock system.img, boot.img etc can be retrieving by using the blobunpack tool on the blob file (different blob) inside official ASUS images (downloaded from support.asus.com). When unpacked, blob.APP => system, blob.LNX => boot.img, blob.SOS => blob.LNX.
There are very few cases where you will brick further than this and when/if that happens, we'll be happy to help people through it, assuming they have ALL the backups we mention on androidroot.mobi! In everyday usage, you won't need those backups, but when/if something really bad happens, they could mean the difference between a brick and a recoverable tablet.
