Database Info

Boot animation preview [7/7/10] - Lucky Day

This is a tool for windows that will allow you to preview a boot animation (bootanimation.zip) file before applying it to your device. If you have the SDK in your environment path, it will also allow you to apply the boot animation to the device. I have tested about 50 boot animations and only had 2 that wouldn't load, and they didn't load because there was an invalid line in the desc.txt file.
Requirements
.NET Framework 4.0
Windows XP or later
Android SDK added to Environment path (to set the boot animation on the device, if you don't have it in the path, you just cant set it from the app)
Boot Animation files to open (you can pull one off your device @ /system/media/bootanimation.zip)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the dialog to create an animation, it takes a directory, analyzes the "parts" and creates the desc.txt from the values entered in the property grid. Then asks where to save the animation and names it based off the name of the folder.
The other feature that BAP offers, is the ability to export a boot animation as an animated GIF. It will try the best it can to create a gif that will do the animation justice. The export can take some time, and can be somewhat large, depending on the number of images, parts, and "loops" of the boot animation.
Below is an export of the CyanogenMOD 5.07-test2 boot animation
Here is the download for this boot animation, I do not remember where I found to, so if you created it please let me know and I link to your thread instead.
if your interested in more boot animations, here is my skydrive with all the boot animations I have. there may be some dupes in there.

Thanks very much for this. It will come in very handy.

I've made some updates to the application. It now gives you more control when exporting to a gif, you can set the quality and set how many times the "infinite loop" section should loop (if there is one that loops forever). These settings can decrease the size of the file, plus the amount of time it takes to create the animated gif. The better the quality, the longer it will take to process, also the more loops, the longer it will take and the gif will be larger.
See OP for new download.

Is it possible for you to upload the boot animation of the green android on the second GIF? I loved it and i would like to put it on my phone without flashing CM 5.0.7 (i have 5.0.6 already)
thank you.

I may just be misunderstanding how to operate this, but I unzipped the .exe to my sdk tools folder (where adb is located) and ran it from there, opened a random bootanimation, and then hit the phone icon. windows requested permission to run adb, so it appears to have found it, but when I rebooted the phone, my animation was unchanged.
Do I need to have the phone booted into recovery for this to work or have the .exe extracted elsewhere?

AWESOME! It's been an eternity of searching until I finally found this tool allowing me to export zip contents to gif! Thank you!!!

Is this for android 2 and newer versions, or it works and for 1.5, 1,6?

PeRRiiN said:
Is it possible for you to upload the boot animation of the green android on the second GIF? I loved it and i would like to put it on my phone without flashing CM 5.0.7 (i have 5.0.6 already)
thank you.
Click to expand...
Click to collapse
Bump,
Did the OP left this project or something?

sorry, im gon bump this also, but i sent an animation to my phone and it works. but when i flash new roms with diff animations... the animation doesnt change.
i want to know where it gets stored when its sent via the program. i searched in /system/media but the animation in there is the one from the recently flashed rom, and not the one i sent using the program.
so im kinda stuck and wondering now...

jakijal said:
sorry, im gon bump this also, but i sent an animation to my phone and it works. but when i flash new roms with diff animations... the animation doesnt change.
i want to know where it gets stored when its sent via the program. i searched in /system/media but the animation in there is the one from the recently flashed rom, and not the one i sent using the program.
so im kinda stuck and wondering now...
Click to expand...
Click to collapse
I would try checking /data/local/, as far as I am aware that is the only other place it can go.

JAguirre1231 said:
I would try checking /data/local/, as far as I am aware that is the only other place it can go.
Click to expand...
Click to collapse
well, i forgot to mention that... but i used 'astro' and 'andexplorer' but nothing was inside /data folder. so dunno whats up with that. dunno if its the app that doesnt actually show the files or what.
i havent really used adb to check it tho, cuz im not 2 sure how to do it either but... i dunno...

jakijal said:
well, i forgot to mention that... but i used 'astro' and 'andexplorer' but nothing was inside /data folder. so dunno whats up with that. dunno if its the app that doesnt actually show the files or what.
i havent really used adb to check it tho, cuz im not 2 sure how to do it either but... i dunno...
Click to expand...
Click to collapse
Those aren't very goof apps to be using as that is the problem. I suggest using something like Root Explorer or SUFBS instead, they are root file explorers.

jakijal said:
well, i forgot to mention that... but i used 'astro' and 'andexplorer' but nothing was inside /data folder. so dunno whats up with that. dunno if its the app that doesnt actually show the files or what.
i havent really used adb to check it tho, cuz im not 2 sure how to do it either but... i dunno...
Click to expand...
Click to collapse
sorry, i dont check this thread that often. Yes, it puts it creates /data/local/bootanimation.zip
If you cant find it using any file explorers for your phone, from a command line you can do
adb shell rm /data/local/bootanimation.zip

Thanks very much!
Now I can prview it in full quality and see if it's working!

thank you. i did get root explorer and was able to remove it through that.

Boot Animation Preview 1.5 uploaded and added to OP. This has some minor fixes in the animation algorithm and other little tweaks.
The main feature added is the ability to take a directory and turn it in to an animation. It will read the directory, and the "parts" in there. Then it generates the desc.txt from the values entered in the dialog, like FPS, size etc. Then it zips up the directory to a file named after the base directory.

PeRRiiN said:
Is it possible for you to upload the boot animation of the green android on the second GIF?
Click to expand...
Click to collapse
I would love this boot animation as well ... could you upload it please?
EDIT: couldn't find the exact one but found some like it here
would still like the one you posted

Any chance of a Linux version of this program (Or at least one that runs in Mono)?
Ok, so it seems that since the application is targeted towards .net 4.0 which so far only SVN Mono supports. Is there something specific in .net 4.0 you are using in your app, or could it be compiled for .net 3.5 so it would (potentially) work in Mono as well?

Thx a lot - great Programm!
Opening the same animation which is already loaded will cause the program to crash
I need this BootAnimation you created a gif from - the one with the big android in the middle and the lightshow in the background =) where can i find it ?
Nik

He dose it again.
Amazing preview app, Fair play!!

[MOD] White On Black Evo Splash Screen

Here is a Splash Screen i wanted to share with the community, It's simple just the original with inverted colors
Please enjoy.
As always please backup before trying, I won't be responsible for anything that may go wrong if this fails
and mods if this is posted in the wrong place please move thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To apply just unzip the contents of the package below into the tools folder of the android sdk
How-to Enter fastboot mode .... While the phone is off hold down "Volume down key" and then "power button" hold both till you get a white screen with the androids and skateboards
to confirm your device is seen by adb use this command
Code:
fastboot devices
you should see your phone listed under the command you just typed. After that type the next command to flash the splash image
Code:
fastboot flash splash1 splash1.nb
Then you should see that it was successful and rebbot the phone and preview your new image by typing
Code:
fastboot reboot
Please Thank and post comments as needed, if there is any trouble i'll try to help if i can i'm rather busy lately...lol

There was a huge thread on how to change splash with win 7 and I am stuck in osx thanks for a tut on how to to it in fastboot

Thanks! I followed the instructions and applied it no problem. Makes booting up look seamless with Fresh's bootscreen

So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim

Criimson said:
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Click to expand...
Click to collapse
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition

Am I missing something? I do everything step by step and it won't find fastboot command in the terminal (using OS X). I can't do anything.

JSZESZE said:
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Click to expand...
Click to collapse
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Is there a way to flash from the EVO itself? I can copy files with no problem if I connect as a HDD.

add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it

Criimson said:
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Click to expand...
Click to collapse
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone

I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?

JSZESZE said:
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Click to expand...
Click to collapse
Awesome! Thanks man, I appreciate it. Looks great.

beautiful! thank you VERY much for this

JSZESZE said:
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
Click to expand...
Click to collapse
No it is in fastboot
From what I gather a lot of people have this issue with Vista 32bit and HTC Sync. I haven't been able to track down a solution. Even when trying to use Sync..it always just errors and says:
Unable to find HTC Sync on your PC. Please make sure.....
Kind of a pain, but so far I have been able to do everyting I want just doing it from the phone with files copied over. Using the terminal emu or file manager
Criim

imaxreed said:
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
Click to expand...
Click to collapse
sounds like a permission issue... are you rooted and nand unlocked?

JSZESZE said:
sounds like a permission issue... are you rooted and nand unlocked?
Click to expand...
Click to collapse
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?

imaxreed said:
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
Click to expand...
Click to collapse
in adb type
Code:
adb shell
then you should see
Code:
#
A $ prompt is the prompt for normal terminal ...
whereas:
a # prompt is the prompt for root (super user)

i am running osx and can access adb shell
http://imgur.com/t8MKg.jpg

does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues

JSZESZE said:
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
Click to expand...
Click to collapse
yes exactly. I haven't had a problem before this is strange.

Works great for me, no problems. This is a great way to save battery!
haha.

[Win32 Tool]GUI Root with Check and Recovery!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ShiftRRv1.0
Shift Root and Recovery will be able to root you're phone in a pretty safe manner. The program is designed to only flash the eng boot if the MD5 checksums are correct.
This does it by simply pushing / pulling the hboot from the phone and checking the MD5 as if you were to manually do it. Only this just does it automatically.
Check Root:
This will just run a quick and simple SU test to make sure you are or are not rooted.
Root:
You will click on this to install the ENG Hboot and load the correct files after the Hboot has been flashed.
Install Recovery:
You simply select the recovery image you want to use with your HTC Evo Shift. Leave the phone at the home screen and click install. It will auto reboot you to bootloader, flash the zip then auto reboot you to recovery to make sure it flashed successfully.
Backup / Restore WIMAX:
This option lets you quickly and easily backup your wimax keys to your home pc. It will also let you restore your wimax keys to your phones partitions.
[WHAT THIS PROGRAM DOES]
When you click on root, and click "NO" for this phone does not have a ENG Hboot. The program push's the ENGHboot from the Hboot folder to the phone and push's busybox. From there it gets a temp root shell. It then cross checks the MD5sum on the phone itself using busybox md5sum /data/local/eng_hboot if the MD5Sum math's it then proceed's with the dd if cmd. Once the dd if cmd is done. The program then sends the dd if cmd to /data/local/eng_hboot_check, it runs the cmd busybox md5sum again and verifies that the MD5Sum matches if so everything went well, the program cleans up its mess off the phone and alerts you its safe to reboot. IF IT FAIILS it will try 1 more time. The program is designed to check the HBOOT md5sum and verify if its the ORIG hboot if it is not and the MD5Sum doesn't check between the ENG and ORIGINAl it will attempt to flash the original and notify you if it succeeds. IF IT FAILS AGAIN. IT WILL NOTIFY YOU NOT TO TURN OFF YOUR PHONE AND COME HERE FOR FURTHER INSTRUCTIONS. I ADVISE YOU TO LISTEN.
After this YOU MUST REBOOT THE PHONE.
When phone is powered up again Click Root again this time select "YES" that the phone has a ENGHboot, this will get temp root again and push all the needed files, "SQLITE3", "BusyBOX", "SU", "Superuser.apk" to there proper location.
If YOU CLICK "YES" and didnt have the ENG Hboot thats fine it simply will temp root you and push files to your phone, but when you reboot they will be gone. Just start from the begining again and do it again.
Download V1 Here
DOWNLOAD NOW HERE
User's having trouble opening the application please download the latest dotNET framework from:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7
THIS IS FOR XDA MEMBERS ONLY. PLEASE DO NOT POST IN OTHER FORUMS AND PLEASE DO NOT MIRROR THE PROGRAM.

download link added
Image of program added.
Reserved...

Thanks for sharing. No need for me to try it now but if I ever replace or need to re-root. Really like the option to backup wimax keys too.

Looks great but too bad I don't need it! Like the option to back up wimax, but what about restoring them!?

Im giving this a try now

It "did its thing" after rebooting the program is still "waiting" and the phone is booted. Hmmm help?

xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?

ahhhh!! I'm back 2 download it and.. well I'll wait again lol Thanks a lot for this..
I RUUed my phone and Wanted an easy way to re-root..

working?
other than the OP has anybody got this to work properly?

amoamare said:
xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?
Click to expand...
Click to collapse
I was trying to root, and I have windows 7 64 bit

Where is the link ! someone please give me the file , pretty please please please been waiting for this !!!

I don't know if this is what it's trying to achieve or not. I don't know how to do it either. Judging by all my previous phones, an all in one script could be written to do everything the s-off, root, and recovery post is telling how to do. Just a "simple" batch file and some support files and presto, it's all done!
Zip everything needed together and just unzip and run. I could probably teach myself by ripping apart other all in one packages and adjusting my port to follow loosely what they are doing but I just don't have the free time to spend on that project. By the time I would get around to doing it, someone else would have finished it. I just don't know things like telling the phone to reboot into different modes so it could continue it's job. I can visualize it in my head but making it a reality is completely different. Doh!

Anyone know where the download link went? I've been having trouble with rooting my phone and wanted to try this, but theres no download link in the first post (unless my computer decided to stop showing links).

Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?

Oops, saw everything except "removed temp..." in the first post.
It looks like there isn't anything extra that needs to be downloaded. Looks like the OP figured out a way around it.

SirRipo said:
Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?
Click to expand...
Click to collapse
Possibly the recovery files ( clockworkmod 2.x or 3.x ) and have HTC sync set up to even connect the phone I would guess.
Sent from my PG06100 using XDA App

Sorry guys will work on this again in a few days girl is supposed to be going in to labor today...
On the side note the issue that I ran into is that running rageagainstthecage from the windows side does not give you root. It actually disables usb connection between the phone and the computer. I was trying to make this so you didnt need anything other then the program. But now with that being a problem z4root would be needed to obtain at least temp root but if i doesnt drop you to # then it still will not work from doing it automatically using arguments. That is what i'm trying to resolve first..
Ill get back to you guys on it, and ill even add the option to restore wimax keys.

That's what I was thinking You have to Temp root with Z4root first.
Since The manual root requires super user to work.

Dude!!!! thank you so much for this. Been wanting t root badly but was afraid to try the other method. Good luck with baby!!

Perhaps someone brave could test it out by temp rooting with visionary/z4root and then running the program? If you posted the download link back up.

[Q] New Boot Logo/Splash Screen Without NvFlash?

Is there a way to change that ugly ASUS boot splash logo screen whatever you wanna call it thingy? I'm sbkv2 so no nvflash.. but I'm rooted. Is there a file somewhere in /system/ that I can replace? Or?
Thanks for any help/guidance.

Not possible then?

To the best of my knowledge, you don't need nvflash to change the boot animation. Just get a new one, rename it to bootanimation.zip and place it in /data/local. Someone correct me if i'm wrong.

Saav said:
To the best of my knowledge, you don't need nvflash to change the boot animation. Just get a new one, rename it to bootanimation.zip and place it in /data/local. Someone correct me if i'm wrong.
Click to expand...
Click to collapse
I think he's talking about the splash screen, the one that appear before the bootanimation.

baseballfanz said:
I think he's talking about the splash screen, the one that appear before the bootanimation.
Click to expand...
Click to collapse
He is correct, I mean the splash screen,

I know it's gotta be possible! I just can't find an image in /system anywhere

The splash screen is in the bootloader/EBT. You can mod it and flash it through the staging partition. Whirly eyes has a thread in the dev section. I think it's much easier with nvflash since you can test it before writing it.
sent from my transformer

Thanks, I'll look for the thread, so I can do this with Sbkv2?

It should be possible, but I've never done it.
sent from my transformer

How would I go about flashing the new blob with the boot screen without NvFlash though, I have cwm I'm just a tad unsure and don't want to be accidentally flashing over something important... Thanks for the help

You can pack up just the EBT partition as a blob and flash it through the staging partition. It will only overwrite your recovery if you include an SOS partition in the blob. The relevant threads are in the dev section.
sent from my transformer

Awesome, so I can just flash certain sections, doesn't have to be all. Thanks for the help!

Okay, as far as which source to download, does it matter? Since I can't use NvFlash to extract mine I want to be extra careful.
I'm running AOKP Build 35 with Guevor v20 kernel or TestyMehIcs kernel.

I have a blob with just the EBT and the new screen made. It just says blob (not .EBT)
If I make this into a .zip and flash it, will it overwrite EVERYTHING or just .ebt? This is very important :/ I can't nvflash a brick and really want this to be clear. Should I rename it?

First off, there are no guarantees! As you said, without nvflash, you're screwed if you make a mistake, and it will be a real brick, not one of those, "help I turned off my tablet and I think it's bricked!"-type threads.
How did you pack the blob?
blobpack your_blob EBT blob_mod.EBT
You don't need to pack it up as a zip, you can just flash it through the staging partition. Not to sound condescending, but be sure you know what you are doing because the consequences are real. I truly think that it's great that you are heading down the Android! journey.
EDIT: I think I see where the confusion is coming from- most people think of the splash screen as the bootanimation. In this case, the splash screen is the Asus/nvidia logos without the spinning balls. If you change the bootanimation.zip, you will still see the splash screen.

Gah this is incredibly scary, damn Asus making Sbkv2 -_-!!
Sofar I havn't packed with blobpack, I've just used that spash image creator gui pointed to EBT then save as blob.
What I've done to this point:
Downloaded BlobTools.
Downloaded Latest .24 US
Unzip, Unzip, Copy blob
Use Blob unpack on blob
I did NOT get a blob.header for whatever reason? Or am I misreading something?
Found blob.ebt
Used This: http://forum.xda-developers.com/showthread.php?t=1232410&highlight=splash Splash screen patcher to open it.
Patched
Save as blob
I have a blob with no extention.
Did I do anything wrong? Now what?
Thanks!
Edit: Also the filesize of the blob before the patch and after is exactly the same. 1421KB

file extensions are a false indicator- what matters is the data format inside. A properly packed blob will start with msm-radio update, some blank space, and then some hex and text that indicates partitions and their size that are included in the blob. Take some blobs apart and see what's inside of them. Get a calculator and check the file sizes of the blobs inside. Then repack them to see if you get the same thing/order.

This is a screen of the EBT blob that was saved by the app, MSM-Radio-Update, some 0s, then a whole lot of gibberish.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

That looks like a packed blob. I guess whirly eye's program packs it up for flashing. Notice the EBT part in the second line, and the fact that there aren't any other partitions like SOS, LNX, or APP.
sent while running with scissors

I unpacked just the EBT blob that I unpacked with blobunpack and opened it with his patcher then edited. Should be fine then I hope, if nothing messed up.
Scrolling through the rest, it just looks like EBT, I saw whirleyes left a watermark in quotes about the patcher before the image, and a section with the display text "cold-booting linux, unsupported bootloader, error, wipe data" (The options stuff) rest was blank or gibberish.
Is this primed to flash then? You said to flash through the staging partition, how would I go about this in Cmw Rouge xm recovery, do I need to pack a .zip, or what is the command to run?
Thanks majorly for all the help!

Do I have the "correct" nvflash blob files?

I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, it doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and if I find I have a bad nvflash blob file).
For other's info, I'd originally asked about re-running the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set. In preparation for recreating one, I moved the /sdcard/AndroidRoot folder to another location. I happened to reboot and noticed the AndroidRoot folder and its contents are automatically recreated upon rebooting. So for these files, there's no need to re-run the fastboot command for another set.
I did notice one "issue" viewing the /sdcard/AndroidRoot folder in Windows 7 after the initial reboot. While they display fine via my TF300T's File Manager, it took either disconnecting/reconnecting my usb cable or rebooting one more time for them to display correctly in Windows 7.
I still plan on re-running nvflash to create a new bricksafe.img, factory-config.img, and unlock-token.img set just to be extra safe.

wha2do said:
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and I find I have a bad nvflash blob file).
Can I rerun the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set? While I'm at it, I figure I should be able to rerun nvflash and create a new bricksafe.img, factory-config.img, and unlock-token.img... Is that possible and does it make sense?
Thanks!
Click to expand...
Click to collapse
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.

totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
Thanks for the confirmation. I dislike relying on an unverified backup only to find out too late that it's not valid or usable! And out of curiosity, you went through a recovery successfully? It'd be great if you had a link to the thread/post you followed.

I had missed one step after upgrading the jb bootloader (didnt force shutdown after upgrade, just let it load) and were stuck with official jb with no root or recovery, so i tried to use nv flash and messed up even more , post 3 in this thread helped me get the bootloader to work so I cound install TWRP again using fastboot.
I do not recommend testing it "just for fun" but it worked for me. Search for "nvflash restore" if you have any problems.

totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
I'm curious about your sizes matching mine; more specifically my unlock-token.img file size matching yours. Maybe fine if you used your unlock-token.img file when you did your recovery. If didn't use, might want to (if you still can) go back and recreate it and compare with your original...see below why.
Being OCD on backups, I created a new bricksafe.img, factory-config.img, and unlock-token.img and compared the files. I was a bit surprised to see factory-config.img and unlock-token.img were not exact copies of the original set created. Factory-config.img had some bits that varied, but was mostly the same. I'm figuring it's something "internal" as I haven't changed anything on my table between runs and is fine...
But seeing a large size change between the two unlock-token.img files, I went back through my logs, etc. Lo and behold, I had a typo and hadn't changed the partition from 14 to 7! So I had made duplicate backups of the factory-config partition by accident. The actual file size is 8,192 KB and not 5,120 KB.
That could have been a real problem down the road if ever I need to recover (assuming this file is vital to the particular recovery procedure). So if nothing else...the lesson to learn is always double check what you've done to make sure!