Related
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
***LINKS ARE FIXED***
Decided to make a thread for my boot animations for the Bonestock ROM by AndyBones.
Have to give thanks to @andybones (for a kickass ROM) and @gadget! (for the images). Also thanks to my friend Mike for a couple Photoshop pointers.
Below are all the boot animations I have created so far. Need some more ideas and color options!
Currently working on animating the skull.
The pulsing glow animations look better on the phone than they do on here. Apparently the pulsing preview images dont pulse if you are looking at them on tap a talk.
These are tested on both the S3 and S4 (Pre 4.3).
***S3 users are good to go flashing which ever animation you like. S4 users, if you are on a pre 4.3 BoneStock ROM you are good to go. If on the latest 4.3 BoneStock ROM these are not working. I am going to be finding a solution soon. S4 users on a pre 4.3 ROM will also need to download and flash the file in the S4boot folder in my link (if you have already flashed this just download whichever animation you want and flash it).***
***One link will now take you to all the animations.***
Install instructions:
1. Download animation of your choice
2. Move animation you downloaded to /system/media folder. It will probably ask you to replace the existing one. You can do so if you want or before moving new animation add .bak to end of original one.
3. Set permissions of new animation to rw-r--r--
4. Reboot
******DOWNLOAD ANIMATIONS HERE!******
Static Wood Grain (still wood grain)
{
"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"
}
Pulsing Pink Glow (Requested)(pink glow pulsates around image, preview gif flashes a little faster than actual boot animation)
Pulsing Orange Glow (Requested)(orange glow pulsates around image, preview gif flashes a little faster than actual boot animation)
Static Orange Glow (still image with orange glow)
Pulsing Purple Glow (purple glow pulsates around image, preview gif flashes faster than actual boot animation)
Static Purple Glow (still image with purple glow)
Pulsing Cyan Glow (Requested) (cyan glow pulsates around image)
Static Cyan Glow (still image with cyan glow)
Pulsing Blue Glow (Requested) (blue glow pulsates around image)
Static Blue Glow (still image with blue glow)
Pulsing Red Glow (Requested) (red glow pulsates around image)
Static Red Glow (still image with red glow)
Pulsing Green Glow (green glow pulsates around image)
Static Green Glow (still image with green glow)
Original Fading (Image fades in and out, fades in and out a little slower on phone)
Man it would be awesome if you could make the skulls jaw move like it was laughing
Sent from my SCH-I535 using XDA Premium 4 mobile app
texaswickedtoys said:
Man it would be awesome if you could make the skulls jaw move like it was laughing
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Something like that is in the works but is going to take a while. Keep an eye out for it in the future.
Nice work!
A firearm is like a parachute. If you need one and don't have one you'll never need one again.
Dude, these are awesome! I'm rockin' the red pulsating one right now, and I love it!
HarleyChick said:
Dude, these are awesome! I'm rockin' the red pulsating one right now, and I love it!
Click to expand...
Click to collapse
Glad you like them. If there is another color you would like to see let me know.
Wolfballz, first off, many thanks for making and offering these up. One of the few things I didn't like (and admittedly, its a small thing) about BoneStock was the Nexus boot animation ("huh? why Nexus?") so getting to replace that is awesome. I especially like the pulsating animations.
I must not be doing it correctly though, since I am not showing the newly downloaded boot animation. At first, I wasn't getting any change, but I realized I wasn't setting the permissions correctly. But even after changing permissions to RW-R-R I am still not getting the correct boot animation. Weirdly enough, instead I am getting a generic blue Android one (similar to the one from my HP TouchPad running a 10.1 ROM called OaT 10.1).
here's the steps I have been doing:
1. Downloading the Boot animation file from here. It goes to SD card/downloads.
2. Since it is downloading with a (1) after the file name, I rename it to bootanimation.zip (and it asks me if I want to write over existing one... yes)
3. I use Root Explorer to move the file to system/media, it asks if I want to replace existing one, I say yes.
4. I use Root Explorer to confirm the permissions (RW-R-R).
5. I reboot.
I've tried a few times... keep getting the generic boot animation after the Samsung name, then it goes into BoneStock. I also tried downloading a different boot animation, but same result.
I know it must be a step I am doing or not doing... can you point where I am going wrong? Especially confused since it somehow downloaded a different animation. Thanks in advance!
I think the green one should come stock in the ROM now lol. Looks good bud.
Sent from my SCH-I535 using Tapatalk 4
If I've helped, please hit the thanks button
Nomad1600 said:
Wolfballz, first off, many thanks for making and offering these up. One of the few things I didn't like (and admittedly, its a small thing) about BoneStock was the Nexus boot animation ("huh? why Nexus?") so getting to replace that is awesome. I especially like the pulsating animations.
I must not be doing it correctly though, since I am not showing the newly downloaded boot animation. At first, I wasn't getting any change, but I realized I wasn't setting the permissions correctly. But even after changing permissions to RW-R-R I am still not getting the correct boot animation. Weirdly enough, instead I am getting a generic blue Android one (similar to the one from my HP TouchPad running a 10.1 ROM called OaT 10.1).
here's the steps I have been doing:
1. Downloading the Boot animation file from here. It goes to SD card/downloads.
2. Since it is downloading with a (1) after the file name, I rename it to bootanimation.zip (and it asks me if I want to write over existing one... yes)
3. I use Root Explorer to move the file to system/media, it asks if I want to replace existing one, I say yes.
4. I use Root Explorer to confirm the permissions (RW-R-R).
5. I reboot.
I've tried a few times... keep getting the generic boot animation after the Samsung name, then it goes into BoneStock. I also tried downloading a different boot animation, but same result.
I know it must be a step I am doing or not doing... can you point where I am going wrong? Especially confused since it somehow downloaded a different animation. Thanks in advance!
Click to expand...
Click to collapse
What kernel are you using? If I remember correctly some kernels don't support custom boot animations but i may be wrong. You mentioned that when you download the animation you get a (1) after it. Usually that means you have another file named bootanimation.zip in your download folder. I would start by deleting any bootanimation.zip file in your download folder then re-download one from above. Then go into your /system/media folder and add .bak to end of the current bootanimation.zip in there then copy new one from download folder and paste into /system/media and set permissions. Then boot into recovery and wipe cache and dalvik cache and reboot. If that doesnt get it going for you then i'm not sure. You could also try fixing permissions in recovery also. Let me know how it goes and then we can look into it more.
wolfballz said:
What kernel are you using? If I remember correctly some kernels don't support custom boot animations but i may be wrong. You mentioned that when you download the animation you get a (1) after it. Usually that means you have another file named bootanimation.zip in your download folder. I would start by deleting any bootanimation.zip file in your download folder then re-download one from above. Then go into your /system/media folder and add .bak to end of the current bootanimation.zip in there then copy new one from download folder and paste into /system/media and set permissions. Then boot into recovery and wipe cache and dalvik cache and reboot. If that doesnt get it going for you then i'm not sure. You could also try fixing permissions in recovery also. Let me know how it goes and then we can look into it more.
Click to expand...
Click to collapse
Thanks Wolfballz. I am using the stock kernel that came with BoneStock, so I am guessing its one that does support custom boot animations.
The multiple zips in the download folder may be causing the mixup, so I will try the steps you describe above. Odd though that the stock android animation showed up... is it possible by removing the nexus one included stock in BoneStock it grabbed whatever boot animation it could?
I am guessing worst case I can reflash the ROM one more time, start over with the Nexus boot animation, no?
UPDATE: Success! Thanks for the patient extra instructions. Rocking with the first custom boot animation (Cyan pulsing one).
Nomad1600 said:
Thanks Wolfballz. I am using the stock kernel that came with BoneStock, so I am guessing its one that does support custom boot animations.
The multiple zips in the download folder may be causing the mixup, so I will try the steps you describe above. Odd though that the stock android animation showed up... is it possible by removing the nexus one included stock in BoneStock it grabbed whatever boot animation it could?
I am guessing worst case I can reflash the ROM one more time, start over with the Nexus boot animation, no?
Click to expand...
Click to collapse
I would ask Andy if the stock kernel supports custom boot animations. Let me know what he says cause I will update the OP regarding that. I personally have ktoonsez latest kernel for 4.1.2 touchwiz roms. I would try the steps I gave you before going through a whole new reflash.
I PMd andy about the stock kernel
wolfballz said:
I would ask Andy if the stock kernel supports custom boot animations. Let me know what he says cause I will update the OP regarding that. I personally have ktoonsez latest kernel for 4.1.2 touchwiz roms. I would try the steps I gave you before going through a whole new reflash.
I PMd andy about the stock kernel
Click to expand...
Click to collapse
Thanks again, but betting the stock kernel does support dusk boot animations since I successfully downloaded and installed yours... thanks again for all the help. Loving the new look!
Sent from my TouchPad using xda app-developers app
Nomad1600 said:
Thanks again, but betting the stock kernel does support dusk boot animations since I successfully downloaded and installed yours... thanks again for all the help. Loving the new look!
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
So you got one of my animations working on stock kernel?
wolfballz said:
So you got one of my animations working on stock kernel?
Click to expand...
Click to collapse
Yup, the first one (cyan, pulsing). I don't know if wiping cache and dalvic cache was needed but I did anyway. As much as I like the new boot animation, I also appreciate the lesson on installing custom boot animations, so thanks again!
Sent from my TouchPad using xda app-developers app
Nomad1600 said:
Yup, the first one (cyan, pulsing). I don't know if wiping cache and dalvic cache was needed but I did anyway. As much as I like the new boot animation, I also appreciate the lesson on installing custom boot animations, so thanks again!
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
No problem. Glad I could help.
These look really nice!
I was thinking about making a bone stock bootani myself but I've just been too damn busy. Let me know if you need any help making flashable .zips or anything.
Another method for installing a "bootanimation.zip " is to put it in data/local. That way you don't have to set permissions and you won't lose the animation when flashing a new ROM version (unless you wipe data)
Sent from my GS³
schu9120 said:
These look really nice!
I was thinking about making a bone stock bootani myself but I've just been too damn busy. Let me know if you need any help making flashable .zips or anything.
Another method for installing a "bootanimation.zip " is to put it in data/local. That way you don't have to set permissions and you won't lose the animation when flashing a new ROM version (unless you wipe data)
Sent from my GS³
Click to expand...
Click to collapse
Thanks. Didnt know about putting it in data/local
I think a lot of people wipe data when flashing unless they dirty flash.
dude, awesome job!!!
andybones said:
dude, awesome job!!!
Click to expand...
Click to collapse
Thanks Andy
Hi wolf... question, I dont have an exhisting bootanimation.zip in my system/media folder. Should I still place it in tgere and set perms?
Thx bud
E's S4
Blackout One Pack Edited: png-optimized for speed/loading/size and added full preview
The theme is simple enough:
1) White htc "ONE" logo on black bg at splash (splash.zip)
2) fade in white htc "ONE" logo with 8 white loading bubbles transitioning to green before looping x8 until system startup (vzw_bootup.zip)
3) quick green htc "ONE" logo fade-out for shutdown. (hTC_downanimation.zip)
I've included the zip files referenced above as well a an animated .gif preview (full now)
The entire sequence is as follows: fade up white logo, load bubbles, go green, flash three times, repeat loading animation...
For the splash be sure to place in fastboot folder. from the cmd line enter "fastboot oem rebootRUU" and then "fastboot flash zip splash.zip" once the htc logo comes up in RUU mode and then "fastboot reboot" once you're done.
>>>For animations replace the current ones (typically names as per above) in your /system/customize/resource folder and be sure the permissions are set correctly. You'll need root (for animations) and S-OFF (for splash)
Enjoy!
Working good.
do these need to be renamed bootanimation.zip and downanimation.zip to work? i my resource folder i do not have any files in there named like these files.
thanks
mikey2487 said:
do these need to be renamed bootanimation.zip and downanimation.zip to work? i my resource folder i do not have any files in there named like these files.
thanks
Click to expand...
Click to collapse
if you're running stock, these are the actual conventions. I haven't tried any, but if those are the names of the files in your directory then by all means..
mrcr0nic said:
if you're running stock, these are the actual conventions. I haven't tried any, but if those are the names of the files in your directory then by all means..
Click to expand...
Click to collapse
I'm on viper, i tried doing it that way and renaming them to what they were in the resource tab but it didn't work, viper rom thou has a setting in their tweaks to add a boot animation and i did it that way and it worked. great animation by the way really digging it!
mikey2487 said:
I'm on viper, i tried doing it that way and renaming them to what they were in the resource tab but it didn't work, viper rom thou has a setting in their tweaks to add a boot animation and i did it that way and it worked. great animation by the way really digging it!
Click to expand...
Click to collapse
Awesome. Glad you liked it! Haven't switched over to a custom ROM just yet as I've heavily modified the stock one.. I suspected it was going to require ROM-specific settings. Liking Viper?
Great!! Thanks!! Got rid of that nasty red verizon screen!
mrcr0nic said:
Awesome. Glad you liked it! Haven't switched over to a custom ROM just yet as I've heavily modified the stock one.. I suspected it was going to require ROM-specific settings. Liking Viper?
Click to expand...
Click to collapse
What have you modified about it?!
Yeah I'm really liking it. I never really liked sense or tw that much I'm more of an aosp guy but this rom is pretty bithin. Waiting for cm or slim roms to come out with a build for this phone. Other than that its petty solid. Haven't had any issues with anything and they a have few dark themes which make it really nice
mikey2487 said:
What have you modified about it?!
Yeah I'm really liking it. I never really liked sense or tw that much I'm more of an aosp guy but this rom is pretty bithin. Waiting for cm or slim roms to come out with a build for this phone. Other than that its petty solid. Haven't had any issues with anything and they a have few dark themes which make it really nice
Click to expand...
Click to collapse
This is actually the first time I've been off cm in a while.. I'm waiting for the lightweights as well.. Sense is definitely better than it was in the past, but I've shut off a lot. Hated tw.. Never ran a galaxy on anything other than aosp.. Really like the latest HTC..
Well if anyone had an animation or a mod question feel free. I swapped out the kernel, enabled all the great settings and froze everything else..
I finally made the time to put together an Aroma of a handful of my own creations along with some of my favorites! You will have the ability to enable custom Boot Animations for those running stock Roms. This mod will also install the ever so difficult to create "qmg" shutdowns! For the people running the newest Missing Link, you've seen most, but not all of what is here. Added a couple of boots and shutdowns.
New version added support to many newer Samsung devices running MM Only!
CONFIRMED SUPPORTED DEVICES
Galaxy S6
Galaxy S6 Edge
Galaxy S7
Galaxy S7 Edge
Note 4
Note 5
Note 7
AROMA BOOT/SHUTDOWN ANIMATION PICKER!! OVER 40 BOOT, 26 SHUTDOWN ANIMATIONS and 45 BOOT SPLASH IMAGES TO PICK FROM
The mod enables the use of "Custom ZIP" animations instead of the QMG animations giving you a much larger selection, even beyond this mod!! If you want to go back to QMG animations, simply just use a file manager with root access and navigate to system/media and delete the "bootanimation.zip" then reboot. Done, you will be back to the original QMG bootanimation your rom had prior to running this mod. Enjoy!!
Aroma_Bootani_1440x2560_v4_MM
Aroma_Bootani_1440x2560_v3 (Lollipop version)
Here are a couple of bootanimation i made real quick (located in post #3 of OP)
#1) Bikini Girls Bootanimation zip
PREVIEW
#2) Denfic_Skull_bootanimation_zip_enabled
PREVIEW
[/img][/url]
For the Aroma Installer hdpi version click v3 HERE
Included in the Aroma Installer below, click the show button to see
1"Blown Away"
2"Droid Scan Boot Animation"
3"Apple Smash Boot Animation"
4"DNA Boot Animation"
5"Illusions Boot Animation"
6"Supernova Boot Animation"
7"Blue Helix Boot Animation"
8"Blue Plasma Boot Animation"
9"Hulk Smash Boot Animation"
10"Motorcycles Collide Boot Animation"
11"Shattered Glass Boot Animation"
12"Not Now Boot Animation"
13"Neutron Boot Animation"
14"Warped Boot Animation"
15"Samsung Boot Animation"
16"DNA Blue Boot Animation"
17"Omega Boot Animation"
18"Zoom World Boot Animation"
19"Ice Comet Boot Animation"
20"Van Gogh Boot Animation"
21"Droid Does Boot Animation"
22"Blue Eyes Boot Animation"
23"Wave Boot Animation"
24"Washer Boot Animation"
25"Moto X Boot Animation"
26"War Boot Animation"
27"Anonymous Mask Boot Animation"
28"Cyber Globe Boot Animation"
29"Isomorphic Algorithm 2 Boot Animation"
30"Jarvis Boot Animation"
31"PAC-man Boot Animation"
THE QUICK GUIDE TO CREATING YOUR OWN BOOT ANIMATIONS"because I can feed you fish and you're good for the night or teach you to fish and you'll be good forever!!"
I have enjoyed boot animations since I started messing around with phones. I finally felt comfortable enough to start making my own and this is how i did it:
1 - First is you need an animation such as a video clip or gif whatever. I personally like them to be less than 30 seconds with the main focal part about 10 secs. By that time the phone has started up.
2 - then you need to extract the frames/convert using infanview or similar app, to image format, jpg is smaller, png is better quality and some just plain look better this way. Using Irfanview in the "options" menu click "extract all frames" then you can fine tune using "file" menu "batch conversion/rename" option
3 - download Boot Animation Factory and thank the dev for such a great tool for previewing and creating Boot Animations. From there the app will take you to creating the bootanimation.zip file needed for your phone.
4 - Then it's just a matter of getting it to where it needs to be. You can check my thread here which gives all the the different locations for various phones store the file for manual installs. There is also the "flashable zips" and "the Aroma Installer" for multiple options!
5 - last thing is to give thanks and credit where it's due and share your wonderful new creations with all of us here on XDA!!! Thank you
that is a very quick run down of how I am making Boot Animations today
*****BOOT ANIMATIONS PREVIEWS*****
This is set of boot animations I have either created or collected from all creative minds here at XDA.
The flashable zips are confirmed ONLY for Sprint's (Galaxy S2) E4GT right now!! testers welcome? Should be compatible with Samsung device's that use "bootsamsung.qmg" and "bootsamsungloop.qmg" files stored in /system/media. Just get the flashable.zip files here and flash via recovery
This link will get you to my original post with directions for installs, downloads for previews, bootanimation.zip files and flashable zips (these are made to support Samsung qmg bootanimation)
Direct downloads here for manual install of bootanimation.zip file
Previews here
Flashable zips here
These are made to support Samsung "qmg" bootanimations, specifically for the device I am on E4GT (Sprint's S2). IT'S UNTESTED ON ANY OTHER PHONES!! IF ANYONE WITH A SAMSUNG PHONE THAT HAS THE "QMG" LOCKED BOOT WOULD TEST LET ME KNOW THAT WOULD BE MUCH APPRECIATED.
I have to thank all of the XDA community for these animation and support over the years!!! Please enjoy
XDA:DevDB Information
[MOD]AROMA BOOT/SHUTDOWN ANIMATION PICKER, Theme for the T-Mobile Samsung Galaxy Note5
Contributors
stangdriver44
Version Information
Status: Stable
Created 2015-09-19
Last Updated 2017-08-31
Nice job!
good to see you again @stangdriver44, loved your work with twisted rom. But there are some boot loader that doesn't work, and some shutdown animations that causes bootloop.
eventheodds1 said:
good to see you again @stangdriver44, loved your work with twisted rom. But there are some boot loader that doesn't work, and some shutdown animations that causes bootloop.
Click to expand...
Click to collapse
Glad you like and enjoy my work. I have a fixed version below. Thanks
UPDATE: First off thank you to everyone for the support and patience. I know the v1 had some "double option choices" and a few animations didn't work. I have went through and tested further and confirm they work now. I also added a couple more choices. I still need to work on the "previews" for some of them, about half are done right now. If the previews aren't available to view during recovery they are most likely available in the OP. Again thank you for your patience!!
Aroma_Bootani_1440x2560_v2
stangdriver44 said:
Glad you like and enjoy my work. I have a fixed version below. Thanks
UPDATE: First off thank you to everyone for the support and patience. I know the v1 had some "double option choices" and a few animations didn't work. I have went through and tested further and confirm they work now. I also added a couple more choices. I still need to work on the "previews" for some of them, about half are done right now. If the previews aren't available to view during recovery they are most likely available in the OP. Again thank you for your patience!!
Aroma_Bootani_1440x2560_v2
Click to expand...
Click to collapse
Glad see you're still working on this.. Wish we could at least get your aroma if we can't get a rom outta you lol..
Sent from my SM-N920T using Tapatalk
Do we flash this in recovery?
re: recovery
rambo8987 said:
Do we flash this in recovery?
Click to expand...
Click to collapse
Yes, flash in twrp or philz recovery.
Good luck!
I have a quick question. I was hoping maybe you can get the Hunger games mockingjay logo to work on our phone like in this video https://www.youtube.com/watch?v=iZZUnZ1Hfbs&feature=youtu.be , if other people want it also? Thank you for your great work!
mushufasas said:
I have a quick question. I was hoping maybe you can get the Hunger games mockingjay logo to work on our phone like in this video https://www.youtube.com/watch?v=iZZUnZ1Hfbs&feature=youtu.be , if other people want it also? Thank you for your great work!
Click to expand...
Click to collapse
Here You go. I can work on adding sound and changing the color later if people want? Just flash the zip in recovery and enjoy!
You are the man. Thank you very much!!!
What really fun is to start adding some sound profiles to these themes pretty easy to switch out the OGG files as long as there's no correctly named
This works with the note 5 right?
The_Keeper86 said:
This works with the note 5 right?
Click to expand...
Click to collapse
Did You Really Ask That?
OP updated with MM compatible version.
Enjoy. Thank
Tried with 920p. Boot Anima didn't work but shutdown Anima did. Any suggestions. This is awesome BTW thank you
Sent from my SM-N920P using Tapatalk
Great mod! Running into a small issue. After the shutdown screen I get a snowy looking screen. Is this a Kernel issue?
How to I go back to stock note 5 splash screen. Flashed s6 one. Thanks.
Sent from my SM-N920T using Tapatalk
TeamHackura said:
How to I go back to stock note 5 splash screen. Flashed s6 one. Thanks.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
This link has the stock Note 5 version.
You will need to flash using Odin or make a flashable zip with instructions from this thread
If you are confused or not comfortable with those instructions let me know.
I have been working for over a month on my ROM update and am literally hours from being done or I would just make a zip for you.
It really is very easy to use ODIN or the zip.
Good luck
stangdriver44 said:
This link has the stock Note 5 version.
You will need to flash using Odin or make a flashable zip with instructions from this thread
If you are confused or not comfortable with those instructions let me know.
I have been working for over a month on my ROM update and am literally hours from being done or I would just make a zip for you.
It really is very easy to use ODIN or the zip.
Good luck
Click to expand...
Click to collapse
Can I just use root explorer and copy paste to the dev/block etc... ?
Sent from my SM-N920T using XDA-Developers mobile app
stangdriver44 said:
This link has the stock Note 5 version.
You will need to flash using Odin or make a flashable zip with instructions from this thread
If you are confused or not comfortable with those instructions let me know.
I have been working for over a month on my ROM update and am literally hours from being done or I would just make a zip for you.
It really is very easy to use ODIN or the zip.
Good luck
Click to expand...
Click to collapse
Will that wipe anything?
Sent from my SM-N920T using Tapatalk
BootAnimations CreatorSimplicity.
What is this?This is a simple Python script that turns an ffmpeg-supported video into a boot animation. Soon it will also pickup PNG series.
Why was this created?
Why was this created?I didn't discover any tools that would do this, so I decided to make one.
How can I use it?Go to https://github.com/MajliTech/bootanimation-creator and check on Releases to download the newest version.
Why is it still in prerelease?Since I don't have a phone to test this on. My Xiaomi Note 11 is my main phone so I don't want to brick it. However any testers are welcome!
Not a bad idea, but a more useful thing would be a desktop bootanimation previewer.
I might make one, but my boot animation is really boring anyway (and low overhead).
I also thought about this, but the boot animation format is still kinda too confusing for me. I may make a tool like this in the future, but for now this is what I got.
@MajliTech Could you post a sample of a boot animation that this generates? (Any res, any theme.)
Here's the sample.
MajliTech said:
Here's the sample.
Click to expand...
Click to collapse
Nope. It's what I thought. That is not going to work. Your zip file uses compression. It will fail.
https://android.googlesource.com/platform/frameworks/base/+/master/cmds/bootanimation/FORMAT.md
Note that the ZIP archive is not actually compressed!
Click to expand...
Click to collapse
It's a stupid gotcha. Nothing in bootanimation.zip can be compressed (beyond the original PNG compression).
MajliTech said:
BootAnimations CreatorSimplicity.
What is this?This is a simple Python script that turns an ffmpeg-supported video into a boot animation. Soon it will also pickup PNG series.
Why was this created?
Why was this created?I didn't discover any tools that would do this, so I decided to make one.
How can I use it?Go to https://github.com/MajliTech/bootanimation-creator and check on Releases to download the newest version.
Why is it still in prerelease?Since I don't have a phone to test this on. My Xiaomi Note 11 is my main phone so I don't want to brick it. However any testers are welcome!
Click to expand...
Click to collapse
@MajliTech So, did your patch from January 9 fix the compression issue?