First off, thanks to everyone for helping make the Nook Color such a vibrant community. There's a wealth of information here and I'm really grateful for it. I love the NC and it's great that we can unlock its full Android potential thanks to the hard work of the folks here... both the people that make the tools, and the people that help support it.
I am curious to know if anyone out there has some custom boot animations that aren't so flashy. Both the wife (who also rooted her NC) and I suffer from migraines, and the bootup sequence can be really painful with the bright flashing colors. Something a little more subdued would be preferable.
I'm also not sure if I can run a custom boot animation on the NC without using Cyanogen? I've upgraded to 1.4.1 today (which promptly went into a boot loop which MN 4.6.16 didn't solve, so I reverted to 1.2 and then went back to 1.4.1 and got it re-rooted with MN 5.12.20 properly... thanks again for all the info here!), so I'm just using a rooted stock system. I searched for boot animations on the forum but most of the results were pages of people mentioning which animation they got stuck on while trying to root
Also, does anyone know anything about NookDevs.com going dark? Their site just shows a blank HTML page and any old links give a 404. It's a pity, because their wiki was a bit more in-depth than the NC wiki here.
stormerider said:
[...] I am curious to know if anyone out there has some custom boot animations that aren't so flashy. Both the wife (who also rooted her NC) and I suffer from migraines, and the bootup sequence can be really painful with the bright flashing colors. Something a little more subdued would be preferable.
Click to expand...
Click to collapse
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).
I'm also not sure if I can run a custom boot animation on the NC without using Cyanogen?
Click to expand...
Click to collapse
Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
bobstro said:
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Click to expand...
Click to collapse
I just finished getting everything set back up (I hit a setting page that did a reset on my unit... not so happy. Running Titanium Backup now...), so I'm not really keen on re-running MN. I'd rather just tweak what needs to be done, as things seem to be a little bit fragile and breaking things requires a lot of time to get back up and running.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
Click to expand...
Click to collapse
Does MN override the bootanimation binary to support /data/local, or does bootanimation support that location directly? I did some searching and it looks like some people are patching the binary so it works with more standard Android boot animations and it was unclear to me if the /data/local path was part of that customization as well or not.
Also, I was in part posting to see if anyone had any recommendations for the animations themselves. Graphics work is definitely not my forte, I'm more of a server guy
bobstro said:
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
Click to expand...
Click to collapse
No need to go through all of that trouble. If you don’t like the boot animation in MN, simply go to /data/local, and delete or rename bootanimation.zip to bootanimation.zip.old, this will take you back to the factory boot animation.
The NC will work with any boot animation you can think of, you just need to follow a few basic rules. The rules are outline at nookdevs.com, Link, the site is down at this time, so here is a link for the cached site, Link.
If you are going to take a boot animation from another device, or from online, and edit it for the NC, the most important step is to NOT use any compression when you zip it back up. You can screw-up almost every other step, and still have a working boot animation, but if you compress the zip, it will not work at all.
CM 7.1.0-encore note
FYI: After putting CM 7.1.0-encore on my NC (and then wanting to change the boot animation), I discovered that the path is: /system/media/bootanimation.zip
Awesome. thanks for the info. Starting to build my own intro...
Related
Title pretty much sums it up. I extracted and went through the dd images and the bootanimation is not in /system/media like it should be.
Does anyone have it. I'm running CM7 and would like to have the original bootanimation instead of the CM7 one.
if you want the one that just flashes the word android delete the boot anim in /system/media and any in /data/local it should come on automatically
Sent via Cyanogenmod7 Encore/Tapatalk Pro
thanks for the fast reply but no, I'm looking for the original B&N stock one that has the white background with the NOOKcolor logo pulsing.
http://www.youtube.com/watch?v=PbvpVvGAlBc
go to timestamp 3:44 and that's what I'm looking for.
I am willing to dig for this myself if folks know how to extract the files in the full system restore archives. I am thinking that it might be in one of the ramdisk images.
I just about tore my hair out looking for this the other day. It's actually a super-simple, but not so obvious fix.
You'll need the /system/bin/bootanim from a stock B&N device. Just place that in /system/bin, and delete the bootanimation.zip from /data/local or wherever it is on a B&N install, and when you reboot you'll have the stock animation. Magical.
Geniusdog254 said:
I just about tore my hair out looking for this the other day. It's actually a super-simple, but not so obvious fix.
You'll need the /system/bin/bootanim from a stock B&N device. Just place that in /system/bin, and delete the bootanimation.zip from /data/local or wherever it is on a B&N install, and when you reboot you'll have the stock animation. Magical.
Click to expand...
Click to collapse
it's pretty funny that you post that because I discovered this on my own today (in a backhanded kind of way). My question now is how to get it off of the stock device. Doesn't nooter automatically overwrite it?
svet-am said:
it's pretty funny that you post that because I discovered this on my own today (in a backhanded kind of way). My question now is how to get it off of the stock device. Doesn't nooter automatically overwrite it?
Click to expand...
Click to collapse
you can "adb pull /where/the/file/is" from your computer right?
svet-am said:
it's pretty funny that you post that because I discovered this on my own today (in a backhanded kind of way). My question now is how to get it off of the stock device. Doesn't nooter automatically overwrite it?
Click to expand...
Click to collapse
Nooter adds a zip animation, but leaves the binary the same. At least it did on the Nook I rooted just the other day. If its not working for you, I can send the file. Email me if you need it. Email is in sig
Introduction
Okay, so there are lots of good boot animations out there but you can only choose one? Not good enough I say!
So, here I provide a script that will allow you to have multiple boot animations that are randomly selected each time you boot you phone!
This script was originally provided by Nighthound here many moons ago but I've since adapted it to my Nexus One ROM (Kang-o-rama) and now for the LG Star.
This version should be compatible with *all* custom ROM's LG P990, P999 as well as other manufactures and ROM's with init.d support.Installation
It's pretty simple to install and very little configuration is required. Simply download the attached .zip file, install it from recovery and you're all set!
Download zip file below
Install zip from SD Card in recovery
Copy any boot animation .zip you want to use to /data/local/bootanimations/
Give each boot animation .zip file a unique name!
Reboot and enjoy
Hit 'Thanks' below
The 'bootanimations' directory will be created for you the first time you boot after applying this update zip and then you can download any suitable boot animation you want at any time and just place it in /data/local/bootanimations/ (make sure it is not called 'bootanimation.zip' to avoid conflicts). Easy as pie.Animation Authors
To help our user community I have two suggestions:
Please let users know in your thread of this script; and,
Put a note in about unique file names so users don't get confused
Have fun kids and don't run with scissors, be safe...
haha nice! I'll check it out in a few! Thanks for the effort tho!
edit:
Ok installed it and installed some boot animations i like and it works like a charm thanks!
Thank you! Like custom bootanimations, so this is something I can use!
ARGHHHH, what files does this replace as after installing this my phone just reboots just after the lock screen shows.
Although it does show me MANY random bootscreen now.
i've placed over 10 bootanims, everything is working as is should be
thnx m8
stevvie said:
ARGHHHH, what files does this replace as after installing this my phone just reboots just after the lock screen shows.
Although it does show me MANY random bootscreen now.
Click to expand...
Click to collapse
It just adds one file called 10bootanimations to /system/etc/init.d/ - you can of course remove this if you like.
It won't actually show *any* random boot animations until you add them so I'm not sure I've understood your problem correctly.
I'm trying to using this on my LG G2x running CM7 and nothing happens ... I've copied a few bootanimations to data/local/bootanimations ... and nothing at all
I've confirmed that the file got flashed to system/etc/init.d ... is there a way i can confirm if it is actually running etc?
Another thing of importance perhaps, the first time i rebooted after flashing the attached zip through recovery, it didn't create the folder at data/local/bootanimations like the script says it should ...
any thoughts?
Nice little tool, thx.
ridicool said:
I'm trying to using this on my LG G2x running CM7 and nothing happens ... I've copied a few bootanimations to data/local/bootanimations ... and nothing at all
I've confirmed that the file got flashed to system/etc/init.d ... is there a way i can confirm if it is actually running etc?
Another thing of importance perhaps, the first time i rebooted after flashing the attached zip through recovery, it didn't create the folder at data/local/bootanimations like the script says it should ...
any thoughts?
Click to expand...
Click to collapse
I'm not sure, is the CM7 processing init.d? Logcat at boot will tell you, the script should launch very early in the boot process and will write to the main log.
djmcnz said:
I'm not sure, is the CM7 processing init.d? Logcat at boot will tell you, the script should launch very early in the boot process and will write to the main log.
Click to expand...
Click to collapse
I think you're right because on the logcat, there is no mention of randombootanimations ... no one over at cyanogenmod answered when i asked if it was a bug that init.d wasn't being processed ...
anywyas, i'll keep this and keep giving it a shot and eventually it will work
Hey XDA, been away for a while and just finished my first semester of college. Checked up on my old thread to find alot of positive things. A while back I wanted to do more with this and never got around to it, but figured it was about time I did...
The new animation starts somewhat similarly to the old one with added transition between the HTC logo and the vortex. Also after the vortex, instead of a static image at the end I've thrown together a completely new piece that will loop until the phone finally decides to start.
This version also uses JPGs rather than PNGs. I just found out JPGs could be used the other day... After optimizing the PNGs, (something that wasn't considered for the old one) this new one comes out to a total of 234MB... (one of those things that happen when you only use AfterFX for the project...) If anyone would like this anyway... Let me know and I'll put it up somewhere.
I also made a basic splash screen, something that was misadvertised with the old version. It is the first image in the attachments and can be installed thru bootloader. (http://www.mediafire.com/download.php?37e8as4f4m68cwu)
Download: http://www.mediafire.com/download.php?w1ci9p2ugk7271d
If you would like the stock sound to use with this download it from the attachments below, extract the mp3 and add it to /system/media.
GIFs were 4-5MB each so heres a video instead...
Old version has been moved to http://forum.xda-developers.com/showpost.php?p=20568970 if anyone wants to check it out.
Thanks for the link, and if you get a chance to try it out let me know how you like it
This is [email protected]$$! Way better then the stock bootanimation
Great work!
>--The Game--<
How to I install this? HBoot or Recovery? I know sometimes you need to rename it to the PG0059 thing (I know it's not right) and I'm just curious before I go screwing anything up
Bigwidge said:
How to I install this? HBoot or Recovery? I know sometimes you need to rename it to the PG0059 thing (I know it's not right) and I'm just curious before I go screwing anything up
Click to expand...
Click to collapse
I personally used clockwork recovery and did install sdcard/update.zip
Place the update.zip from the download onto the root of the sd card, then in ROM manager, reboot into recovery and install the update.
There are alternatives to this such as just putting the bootanimation.zip into the right folder using root explorer, but I ran into permission problems so I did it this way.
If you have any other questions feel free to ask.
bobz1993 said:
I personally used clockwork recovery and did install sdcard/update.zip
Place the update.zip from the download onto the root of the sd card, then in ROM manager, reboot into recovery and install the update.
There are alternatives to this such as just putting the bootanimation.zip into the right folder using root explorer, but I ran into permission problems so I did it this way.
If you have any other questions feel free to ask.
Click to expand...
Click to collapse
Thanks alot bud! Thats what I thaught but I figured I would ask before doing anything. Looks sick- thanks for posting!
EDIT: Just flashed it and it looks amazing! Definitley a keeper! I like how fast it spells "quietly brilliant" (I hate slow screens) and the animations on the boot animation is just plain awesome. ++++1
DUDE this is sweeet! Thanks!
Glad you guys like it. Are you using the stock sound with it. Seems like it would work good with this, but I lost it when I flashed to the ROM I'm on >.>
yes stock sound and it is perfect!
bobz1993 said:
Glad you guys like it. Are you using the stock sound with it. Seems like it would work good with this, but I lost it when I flashed to the ROM I'm on >.>
Click to expand...
Click to collapse
bobz1993 said:
Glad you guys like it. Are you using the stock sound with it. Seems like it would work good with this, but I lost it when I flashed to the ROM I'm on >.>
Click to expand...
Click to collapse
Yeah same here, the stock sound works great with it
Is this new boot animation really 24MB? Like, I yanked it out of the update .zip because I normally move them with Root Explorer. I find easier, and I have a system to doing this where I save the old ones in the folder and just rename them. Allowing me to swap them out at will by simply altering the name of the bootanimation . zip back to that.
-Edit- NVM. I see why it's 24MB now.
Holy effing sh!t cakes! That's a lot of graphical content to run through there in the beginning. Looks awesome though!
Again, just to anyone reading this that hasn't tried this boot animation yet.
THIS BOOT ANIMATION IS AWESOME!
Asmodeus6 said:
Is this new boot animation really 24MB? Like, I yanked it out of the update .zip because I normally move them with Root Explorer. I find easier, and I have a system to doing this where I save the old ones in the folder and just rename them. Allowing me to swap them out at will by simply altering the name of the bootanimation . zip back to that.
Click to expand...
Click to collapse
Glad you like it. I would have done the same using root explorer, but I ran into read only and permission problems for anything i tried to use it with. And I really tryed to lower the size the best I could... It was originally 165mb, then found out it was rendering w/o compression (lossless), changed render settings managed to get to 95mb... to get it to 24mb I lowered the quality a little more and it skips every other frame. After uploading it I attempted to make it smaller but all i can do is lower the quality even more, and at 17mb it looked pretty bad.
PS- could someone link me to the stock FinalThunder.mp3 I haven't had it since I flashed my ROM
bobz1993 said:
Glad you like it. I would have done the same using root explorer, but I ran into read only and permission problems for anything i tried to use it with. And I really tryed to lower the size the best I could... It was originally 165mb, then found out it was rendering w/o compression (lossless), changed render settings managed to get to 95mb... to get it to 24mb I lowered the quality a little more and it skips every other frame. After uploading it I attempted to make it smaller but all i can do is lower the quality even more, and at 17mb it looked pretty bad.
PS- could someone link me to the stock FinalThunder.mp3 I haven't had it since I flashed my ROM
Click to expand...
Click to collapse
No I wasn't *****ing about the size. I was checking to make sure I didn't bork something up extracting it. I was just verifying as most of them are 2-6MB.
Here's the Final Thunder .mp3
I ripped it right from the system folder with RE so it should be good. Make sure you check the permissions though. As they may need to be altered to get it to jive with the way it gets read. It should be;
X-X-[0]
X-[0]-[0]
X-[0]-[0]
I think.
X meaning checked.
I had to rar it to post it.
Edit: Yes, that's the way the permissions need to be above, but when it gets extracted it changes them to;
[0]-[0]-[0]
X-X-X
X-[0]-X
So if you just drop it in there it probably WON'T WORK. Make sure you change the permissions!
Again, thanks for the awesome boot animation!
Thanks, I just now noticed the mount r/w button at the top of root explorer >.>
I also did all of this before I saw the post edit, so I did just throw it in there, but it still worked =o
Now I can see the bootscreen everyones been thanking me for lol... Thanks again for the sound clip =)
bobz1993 said:
Thanks, I just now noticed the mount r/w button at the top of root explorer >.>
I also did all of this before I saw the post edit, so I did just throw it in there, but it still worked =o
Now I can see the bootscreen everyones been thanking me for lol... Thanks again for the sound clip =)
Click to expand...
Click to collapse
Hardly a fair trade for the kick ass boot animation. But no problem.
Yeah, many moons ago RE owned me until I found that little mount r/w button. After finding it however it's been an extremely useful tool.
I'm surprised the MP3 worked for you actually w/o changing permissions. :shrugs: I'm leaving the warning there in case someone else downloads it for the same purpose and it doesn't.
Which file or folder do i drop this into to make sound work. I am on gingeritis and had to delete the VZW_bootanimation and there is no sound once i swapped that boot animation out with this one?
Asmodeus6 said:
No I wasn't *****ing about the size. I was checking to make sure I didn't bork something up extracting it. I was just verifying as most of them are 2-6MB.
Here's the Final Thunder .mp3
I ripped it right from the system folder with RE so it should be good. Make sure you check the permissions though. As they may need to be altered to get it to jive with the way it gets read. It should be;
X-X-[0]
X-[0]-[0]
X-[0]-[0]
I think.
X meaning checked.
I had to rar it to post it.
Edit: Yes, that's the way the permissions need to be above, but when it gets extracted it changes them to;
[0]-[0]-[0]
X-X-X
X-[0]-X
So if you just drop it in there it probably WON'T WORK. Make sure you change the permissions!
Again, thanks for the awesome boot animation!
Click to expand...
Click to collapse
It's either system/media
or
system/customize/resource
But I think it's system/media
Find the bootanimation .zip and that's where the sound file should go.
I tried putting it system/customize/resource and that didnt do anything so i will try system media I guess just put in the main file or any one of the sbu files I have
audio
GPU
weather
folders in there will try a few i guess?
Asmodeus6 said:
It's either system/media
or
system/customize/resource
But I think it's system/media
Find the bootanimation .zip and that's where the sound file should go.
Click to expand...
Click to collapse
If anyone wants to try this, it is a zip of the vortex boot animation hopefully with the sound. It is for anyone running a rom that has a boot animation in the system/customize/resource folder and the boot animation is labeled VZW_bootanimation.
Let me know how it goes please
My apologies if the OP does not want this and will take down if asked
http://dl.dropbox.com/u/9663029/VortexBootAnimation.zip
I got the animation to work, but no thunder. Tried everything! I think it may be my current set up (gingeritits and imosyons 2.5.4.test.4 kernel) since day one, there's been no sound. It came with the old school PC looking bootanimation and I read somewhere that, that boot ani is supposed to sound like a disc drive spooling up with clicks n what not, but it never did. I remember on the virus Rom I had, it DID have sound and the .mp3 was called VRsound.mp3. I made my own, fixed permissions, renamed it to VRsound.mp3 and replaced it. That worked. I could be wrong, but because this ROM didn't come with sound in the first place, I just can't get it.... Oh well. Still a tight boot! sound or not!
4Geezy ON DopeDiculous's ROOTED TBeezy!
Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u
i need this about 6 hrs ago lol.
Quite useful mate cheers.
=smc
Thank you so much for sharing this file. Your work is greatly appreciated.
This is a nice little(big)addition to safestrap! Thanks for adding it in!
I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!
Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.
TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.
I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium
Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.
I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.
This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!
I think I'm pretty versed in this stuff and I have a clue - but all the info I find on the subject says I should find the boot_logo.bin file in /system/media/images
Trouble is, that folder don't exist and I am unable to find the file that shows me the bootlogo image.
I am currently using the LiquidSmooth latest L ROM but suspect any of the others I test, would have the same folder/file structure. Anyway, I can obviously change the logo image by fastbooting pre-made ones but I want to make my own. Problem is, Logo Builder does not work like all the info I have seen on it. The Make button never lights up. Program seems to load the logo.bin file I initially feed it but that's it. I don't get it.
Anyone ever dabble with changing their boot logo image successfully? Appreciate the help, must be something simple I am over looking.
I did manage a cool bootanimation.zip that turned out nice, especially if you're a
US Marine - or used to be...
Check it out-> http://boopt.com/2/bootanimation.zip
Thanks for the help, XDA...