Is there any way to change the white vibrant bootup logo? Where is this file located and would it be better to use a deodex rom to change this?
Thanks in advance
There's a lot of info on this. Try boot animation from the market. You need to be rooted BTW
is there a way to make my own bootanimation if I have a video file? or a pic?
Check tonicacids threads theres a tutorial on how to make them on his boot animation thread
This is not part of bootanimation.zip.
Its called a splash screen, and no I dont think u can change this yet, I think its hard coded into the kernel, but im no dev so not sure, I know u could on the g1 though
Sent from my SGH-T959 using XDA App
Check develop section. There was one thread about it I think
Sent from my SGH-T959 using XDA App
General FYI,
The Vibrant uses a 2-stage static splash screen, totally different from the traditional splash.img used on other android phones.
The first is called by the bootloader from the lfs partition, there's a thread in the development section on how to change this logo here: http://forum.xda-developers.com/showthread.php?t=947331
The second screen (in the case of the vibrant, this is identical to the lfs splash, so it seems like we only have one screen, but we don't, we still have two) is built into the kernel during compile.
There's a thread about this in the captivate section, with a specific post about the second splash here: http://forum.xda-developers.com/showpost.php?p=10851192&postcount=118
I tried playing with kernel dev today a little bit, but am having an awful time getting everything setup, even using existing, good kernel source like ttabbal's dragon kernel.
Anyway, hope this helps, cheers, =)
Its here...
http://forum.xda-developers.com/showthread.php?t=947331
Edit: Oops awesome Jocelyn explained it already.
Thanks everyone for pointing in the right direction! I'm prolly gonna want to change both anyways but may not be able to change the splash cuz of my limited knowledge. Also where is the splash img located? Is there asn apk I have to decompile?
ps.- jocelyn I have seen you help so many people why is you thank meter stuck at 7?
aamir123 said:
Thanks everyone for pointing in the right direction! I'm prolly gonna want to change both anyways but may not be able to change the splash cuz of my limited knowledge. Also where is the splash img located? Is there asn apk I have to decompile?
ps.- jocelyn I have seen you help so many people why is you thank meter stuck at 7?
Click to expand...
Click to collapse
Hey again,
The first splash (the one called by the bootloader) is stored in the lfs partition, the first link I provided has a great video walkthrough on how to change it. Basically, you have to flash a new param.lfs to your phone that by default doesn't contain a logo_T959.jpg image.
Then you create your new logo, 480x800, and save as logo_T959.jpg, keep filesize small (the video mentions ~20k being the optimal size.) Then use his provided batch script to remount the lfs partition read/write, and push the new logo to the phone.
The second image is vastly harder to change, since it has to be compiled into a kernel. The second post I linked to contains a walkthrough to make the image, but you then still need kernel source, and a build environment setup to compile your custom kernel with your splash screen.
Basically, you have to use GIMP to save your logo as "C Source Header" and then run a shell script to convert it into the proper samsung logo format, drop it in your /kernel/drivers/video/samsung directory, and compile the kernel.
Sorry, I've not been able to configure a build environment yet to successfully build a kernel (even from known good source, like ttabbal's dragon kernel) on my OSX partition, and I'm too stubborn to triple-boot mac/win7/ubuntu again.
Oh, and my thanks meter is low because I haven't posted much here since it was implemented, the lack of credit/thanks burned me out on android and xda-dev for a couple months.
Hope this helps, cheers, =)
s0niqu3 said:
Hey again,
The first splash (the one called by the bootloader) is stored in the lfs partition, the first link I provided has a great video walkthrough on how to change it. Basically, you have to flash a new param.lfs to your phone that by default doesn't contain a logo_T959.jpg image.
Then you create your new logo, 480x800, and save as logo_T959.jpg, keep filesize small (the video mentions ~20k being the optimal size.) Then use his provided batch script to remount the lfs partition read/write, and push the new logo to the phone.
The second image is vastly harder to change, since it has to be compiled into a kernel. The second post I linked to contains a walkthrough to make the image, but you then still need kernel source, and a build environment setup to compile your custom kernel with your splash screen.
Basically, you have to use GIMP to save your logo as "C Source Header" and then run a shell script to convert it into the proper samsung logo format, drop it in your /kernel/drivers/video/samsung directory, and compile the kernel.
Sorry, I've not been able to configure a build environment yet to successfully build a kernel (even from known good source, like ttabbal's dragon kernel) on my OSX partition, and I'm too stubborn to triple-boot mac/win7/ubuntu again.
Oh, and my thanks meter is low because I haven't posted much here since it was implemented, the lack of credit/thanks burned me out on android and xda-dev for a couple months.
Hope this helps, cheers, =)
Click to expand...
Click to collapse
Yea but alot of what you said sounds like chinese. Ill give it a try and it seems too hard its best left alone I guess. And your one of the best on these forums thanks for everything.
Related
Why oh why can I not get anything to boot on my gosh darn incredible? I've tried everything except making it all work.
I want so badly to get something to boot, but alas it never happens. Stuck at the white screen is as far as I ever get. I don't even get the satisfaction of seeing a bootloop, at least then I'd be seeing some sort of progress. Its disheartening. I've tried all kinds of roms and system dumps to no avail.
There must be something I'm doing wrong, what?
Sent from my ADR6300 using XDA Premium App
Do wipe data and cache before flashing?
Yeah. I did manage to get a boot loop with the huashan gingersense leak. So some progress.
Sent from my ADR6300 using XDA Premium App
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
gnarlyc said:
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
Click to expand...
Click to collapse
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Mr. Rager said:
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Personally, I wouldn't copy entire folders over. I also wouldn't copy the boot.img over. I'm not saying that it won't work in some cases. It might. I've always swapped the kernels inside the boot.img, and renamed the device specific init file. Then, I would compare the init files from an existing ROM for my device with the init files from the ROM that I'm trying to port and see if there are any lines that are device-specific. If the init file is trying to start up something that doesn't exist on my device, then it doesn't make sense to keep that line. On the other hand, there might be a line that changes something for that ROM that IS needed.
This same thing kind of goes with the libs and other files too. You might have one lib that relies on another lib being there. And it might need a particular build of that lib. And other files might call certain libs. This is one reason that building from source generally works better over the long run than trying to get one device's ROM to work on another.
You have device specific and ROM specific things going on at the same time, so wholesale copies tend to miss one or the other. Plus it's nice to dig in and get an idea about what's going on.
Also, if you can get adb access while it's booting, grab a logcat. It might give you an idea about what is failing.
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Mr. Rager said:
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Click to expand...
Click to collapse
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
dsixda said:
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
Click to expand...
Click to collapse
I've had a busy past couple of days, but I'll check into the recovery dump and see what's up. I did change the ro.board.
I was trying to abstain from your porting tools, no offense, only so I could do it manually. Just trying to gain more experience, I guess, and learn. Your kitchen is excellent. I use to set up my environment and deodex among other things. The porting tool, though greatly eases the pain and shorten the manual labor ( yes lazy America) , take the learning curve out, a bit. But I guess I could take a look at the script to see what's going on too. Lol.
EDIT#1 - So I just tried to flash my rom. However, it wouldn't, because for some reason my phone is very particular about how one copies files over to the sd card. For one, you have to have the phone booted up, MIUI GB latest in my case, and mount usb storage. If I mount it through recovery, it corrupts my sd card, too bad I wish I knew that earlier. It's a PITA really...Ubuntu...
But, as phone WAS:
Hboot - 0.92
Radio - 11.19
Ship S - OFF
I tried copying and flashing through recovery. Fail as usual. So, I was gonna boot up into MIUI and try to copy from there, and got the infamous 5-vibe and twinkle.
I tried several times to boot into MIUI, but after many battery pulls, I figured out something ODD. In the bootloader the first couple of times it skipped the scanning process, then it started scanning again. Upon further inspection:
Hboot - still 0.92
Radio - still 11.19
Ship S - ON <---NOT A TYPO
Why? I haven't a clue. I tether my phone, so I got it booted, yay, but to do it, my sd card has to be removed and my usb plugged in, then turn on. So, my next edit will be a progress update. AFTER I s-off again ( that sounds kinda dirty, lol ), and re-format my sd. Also, my phone thinks it's charging...ITS UNPLUGGED. Lol, infinite-charging batteries, it's the future...
Sent from my ADR6300 using XDA Premium App
So...Good news is I got another incredible with amoled screen
Bad news I got another incredible with nothing on it, or rooted :-( But I rooted it before I even activated it with *228
But, alas, I still have all of my work on my computer. I managed to back it up before my phone crapped out. Plus I kinda get to start from the beginning so I can be more observant, and particular.
So, back to work...will update tonight.
Edit 1 - So after some more tinkering I've managed to fix some issues, but others have popped up namely the HTC Sim card authentication, which I have no idea about, yet, bouncycastle.jar is being stubborn by not fiding its classes, and libaudioflinger.so is failing to link to libsystem_server.so which in turn fails the link to libandroid_servers.so. Same three problems as before it seems.
Here's a pastebin of the logcat.
http://pastebin.com/QYde7fuQ
I'll keep tinkering about and see what I can come up with. Hopefully I'm closer to getting this thing booted up than I think.
We have been discussing in another thread the possibility of getting a CM7 rom available for the NT.
Now that we have a functional recovery this should seriously help out with testing, if it goes wrong we can just restore to a working rom and start again debuging as we go.
***UPDATED 5TH Feb 2012***
I thought it was about time I updated this post with some up to date info on current state of development.
As many of you will know we got together last week and decided that we would like to build a CM7 rom for the Nook Tablet.
Goncezilla had already been making progress building firmware and a boot.img to get the thing booting up. Initially the system booted and you couldn't do a lot with it, but it prooved it could be done. Here's the vid showing the first boot:
After that it was down to work to make it useable. After a bit of investigation and a lot of man hours this is where we are at now
HARDWARE FUNCTIONS
Touchscreen FULLY WORKING
Orientation sensors FUNCTIONAL
Sound WORKING
SDCard WORKNING
WIFI Fully WORKING
Hardware video acceleration WORKING
SOFTWARE
Custom Kernel BUILT AND FUNCTIONING
Full tablet version on Cyanogen Mod WORKING
Root Access WORKING
Gapps WORKING
Sleep mode WORKING
Brightness control WORKING
BOOT FROM SD CARD SOLUTION AVAILABLE
and the one everyone seems to think is important
Angry Birds YES IT WORKS PERFECTLY lol
Another little video of current progress
Finally we have wifi working!
Sorry it's sideways, it's changing it now but it seems Google have slow computers!
So the main things we have left to fix are
1. Ermm... hmm... I'm sure we'll think of something
Thanks to Celtic for taking on the OP of this forum!
EDIT 2/5/2012Here are the source files used to create the first CM7 beta:
Internal
1. Kernel built from source - http://www.mediafire.com/?tu5lm7q8t5pbqpf
2. Nook Color CM7 Ramdisk (the one we want to modify) - http://www.mediafire.com/download.php?epv9n97evhnuaoi
3. Stock Nook Tablet Ramdisk (the one we need to borrow from) - http://www.mediafire.com/download.php?xms3aeztgupkjco
4. Buawk's Internal Boot.img 2ndboot (this gets appended to the front of a boot.img to get around the locked bootloader) - http://www.mediafire.com/download.php?9l8uxx7rhbqzund
5. Modified CM7 /system partition files (should be good to go for NT) - http://www.mediafire.com/download.php?il5ky2l51q48e8h
6. Modified Ramdisk - http://www.mediafire.com/download.php?9l8uxx7rhbqzund
7. Wifi Driver files (built from Kindle Fire source) - http://www.mediafire.com/?vogxuygrf84xsoe
8. Kernel Config File (settings used to build kernel above) - http://www.mediafire.com/?7vjvqctmlnd4enw
9. GFX Drivers (put in /system/lib/modules and insmod) - http://www.mediafire.com/?5uw4wgytb60n485
SDCard
1. SDRamdisk - http://www.mediafire.com/?4p3wq0u4p9j9mtd
All other files are same as internal.
EDIT 2/4/2012
My Plan for success:
1. Build a boot.img from CM7 NookColor Rom - Done!
3. Get a booting rom working from SDcard to verify steps 1 and 2 - Done! SDcard working great!
4. Port to internal boot partition (CWM) -Done!
5. Tweak to get everything working - Ongoing....
All other ideas welcome here!
I'll flash and test things for you all.
Sent from my Nexus S 4G using Tapatalk
LiuAnshan said:
I'll flash and test things for you all.
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Thanks
Just to let anybody interested know in advance, this may or may not turn into a working rom, even if it does become a fully functional rom please remember that during testing if your tablet does a nose dive and you can't recover for some obscure reason, we take no responsibility for any damage caused.
Other than that, as and when we have something testers will efinately be needed
Goncezilla said:
Reserved.
Ill post my current working files here soon. Thanks to Celtic!
My Plan for success:
1. Build a boot.img from CM7 NookColor Rom - Kernel built, working on ramdisk
2. Port /system partition -Mostly done but untested
3. Get a booting rom working from SDcard to verify steps 1 and 2
4. Port to internal boot partition (CWM) -2ndboot.img built and waiting
5. Tweak to get everything working
All other ideas welcome here!
Click to expand...
Click to collapse
So i'd thought id put in my two cents here...
First off, whom ever is testing this will want to have 2 sd cards, one of which is the update_acclaim boot disk, so they can "unbrick" their device. This device is nearly unbrickable, and whom ever ends up testing it, can make sure that they can always return it to stock.
Second off, I would HIGHLY recommend using the stock kernel, with the security keys stripped off. This would eliminate any problems that you would encounter with the kernel not causing a boot. I can get you guys a copy of the stock if you want, as it is easiest to just take the first 288 bytes off of the existing kernel, and ramdisk. I don't have an NC, but i'm not sure that the partitions are the same, I would think about building the ramdisk by combining the two ramdisks.
Lastly if someone has the inclination, they COULD eliminate the useless partitions, DO NOT TOUCH THE X-LOADER OR UBOOT PARTITIONS, MODIFYING THEM WILL BRICK YOUR DEVICE. However there is the useless BN and rom partitions that could be consolidated.
Ill be checking in from time to time, I would recommend that you join the CM7 IRC channel and make a new one so that you will not be bothered.
I've done little more than keep the port of miui updated for the Samsung infuse, but I'd be willing to help where I can. I'll probably only be useful for testing, but I'm more than willing to soft brick several times (or risk a hard brick )
Don't modify the rom partition, it forces a wipe of the device and without a proper recovery for that (stock) you're **** out of luck.
Sent from my Nexus S 4G using xda premium
Loglud said:
Second off, I would HIGHLY recommend using the stock kernel, with the security keys stripped off. This would eliminate any problems that you would encounter with the kernel not causing a boot. I can get you guys a copy of the stock if you want, as it is easiest to just take the first 288 bytes off of the existing kernel, and ramdisk. I don't have an NC, but i'm not sure that the partitions are the same, I would think about building the ramdisk by combining the two ramdisks.
Click to expand...
Click to collapse
Interesting about the first 288 bytes. Any specific reason for stripping them? Is this the kernel header or is it for the ramdisk too? The kernel Im using was built from the BN source.
The ramdisk Im putting together is a combo of the NC and NT. Im working on porting the .rc files and build.prop. There is a lot to look at and any help is appriciated. Ill post the files when I get home this weekend.
Lastly if someone has the inclination, they COULD eliminate the useless partitions, DO NOT TOUCH THE X-LOADER OR UBOOT PARTITIONS, MODIFYING THEM WILL BRICK YOUR DEVICE. However there is the useless BN and rom partitions that could be consolidated.
Click to expand...
Click to collapse
Good call here. I was thinking about mounting the 15GB B&N partition as rw and leaving it at that. If we get brave we can try and merge the partitions.
Thanks for the input.
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Indirect said:
Don't modify the rom partition, it forces a wipe of the device and without a proper recovery for that (stock) you're **** out of luck.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Maybe this is the issue Im seeing. Does this mean we have to use 2ndboot to point to another partition? Is there a mdsum check being done at boot that triggers this?
EDIT: Nevermind was thinking boot partition instead of rom. Rookie mistake No plans to touch rom partition.
Guys, we won't need testers. We all have NT's. You all will get a build once it's in alpha.
Like Indirect said, as far as startup is concerned we'll be able to do the testing, we won't really need external testing until we have something semi stable.
Thanks for all your offers though. I'm sure when we get to alpha/beta stage you'll all get a shot at it
As agreed with OP i am going to move this to general. As soon as development is posted, it will be moved back to Development.
Thanks to the OP for his co-operation, He is a gentleman and exactly the type of member we want at XDA Developers!
Peace!
clock work mod
thanks to Albert I am beginning to understand the early stages of getting things like CM7 or 9 functional for the NT and his his recent video on youtube gives a good idea on the developments going on for the NT. I am trying to understand the possible uses of CWM for the nook other than it being a framework for installing custom roms. .. Thanks
Rafael863 said:
thanks to Albert I am beginning to understand the early stages of getting things like CM7 or 9 functional for the NT and his his recent video on youtube gives a good idea on the developments going on for the NT. I am trying to understand the possible uses of CWM for the nook other than it being a framework for installing custom roms. .. Thanks
Click to expand...
Click to collapse
Link to the video, per chance? Thanks in advance!
Just a quick update before I call it a night.
I've been having a lot of trouble getting a working boot.img built. When I cat the 2ndboot to my boot.img I see the flash screen on bootup but quickly get a black screen followed by a reboot of the system.
I can't even get the stock boot.img to boot after appending the 2ndboot.img file. I was, however, able to boot into CWM from the boot partition by attaching the 2ndboot.img. This tells me that the 2ndboot is working properly.
I'm continuing to deep dive on the boot.img files, but if any other devs want to play around with cat 2ndboot to a boot.img it might help.
All I've been doing to this point is taking the boot.img from a CWM recovery, adding the 2ndboot.img to the front of it, placing the modified boot.img back into a new CWM recovery folder (and rebuilding nandroid.md5), then flashing the boot back on using CWM Advance Recovery.
Well, I can report some partial success!
I was finally able to unpack a stock boot.img, modify the ramdisk (nothing major just a small tweak to test results), repack with another unsigned kernel, flash the new boot.img and get a good boot. I did this by using the kernel extracted from nemith's CWM image and not the custom kernel I've posted, so it seems like there is an issue with that kernel for now.
Anyway, I'll try and post some more files later but in the mean time I'm moving on with trying to get a CM7 ramdisk to boot.
I think this is now at a stage that it can be moved back to development.
Good work Guys!
Goncezilla said:
Well, I can report some partial success!
I was finally able to unpack a stock boot.img, modify the ramdisk (nothing major just a small tweak to test results), repack with another unsigned kernel, flash the new boot.img and get a good boot. I did this by using the kernel extracted from nemith's CWM image and not the custom kernel I've posted, so it seems like there is an issue with that kernel for now.
Anyway, I'll try and post some more files later but in the mean time I'm moving on with trying to get a CM7 ramdisk to boot.
Click to expand...
Click to collapse
Great to see you've made some decent progress. Sorry for my total lack of input, you're a good few steps ahead of me in developing. I'm still on a serious learning curve!
I'm getting there hopefully in time I catch up with you and give some decent worthwhile input!
CelticWebSolutions said:
Great to see you've made some decent progress. Sorry for my total lack of input, you're a good few steps ahead of me in developing. I'm still on a serious learning curve!
I'm getting there hopefully in time I catch up with you and give some decent worthwhile input!
Click to expand...
Click to collapse
Hey if you have any questions throw them out there. I'm learning some things as I go along but don't have all the answers either. Hoping we can start combining efforts to move forward.
---------- Post added at 10:31 PM ---------- Previous post was at 09:31 PM ----------
EDIT:More progress!
Was able to get the stock ramdisk to boot using the compiled kernel I posted. I think the issues were with my compilers. No guarantees they are fixed but we are getting close I can feel it!
I'm not sure but I think this kernel can be overclocked, so if nothing else this should allow you to overclock a rooted stock device for now. I'll do some testing and get back....
EDIT 2:
Well it looks like this kernel should be capable of overclocking, but there are a few other bugs with it (could not turn on wifi) that still need to be worked out so I am moving on for now. I will post the boot.img if anyone else wants to play around with the custom kernel on stock firmware in the meantime.
They had issue with wifi in the cm9 thread which they've now fixed. Perhaps some help from there thread will be available?[/QUOTE]
Good call, maybe we can leverage from them. I think I'm just missing a configuation setting in my kernel build but everything else seemed to be working so I'm not too worried about fixing it right away. Would rather get CM7 to boot
EDIT:
Well more progress to report this morning! I've finally got a CM7 boot screen! I'm stuck in a bootloop but we are really close now!
Turns out my permissions were all jacked up on my system partition and it was refusing to allow the kernel to load divers. I've jacked with files so trying to get a good boot that I'm not even sure what I have right now, so I'll go back to square one and hopefully see a full boot
Whenever you get a boot loop, I suggest that you get a logcat so you know what to look at.
Sent from my Nexus S 4G using xda premium
Hey guys.
So in the last couple months I ported the encore u-boot menu/console/configuration stuff over to acclaim (Nook Tablet). The acclaim really needed the menu plus had a ton of "2nd bootloader" issues that needed to be addressed to fix the locked bootloader bug. On nemith's suggestion, the u-boot really isn't just for cm7/9 (it can be used with any OS), so I called the newer bootloader, "CyanoBoot". Kind of a working title until I think of something better.
In the process of the acclaim port, the UI menuing interface was rewritten and some small features were added.
Anyhoo... Last night on a whim I decided to port the improvements back to encore's u-boot. So there's a version now for encore as well so that NC can enjoy the UI benefits.
It's similar to the acclaim version, minus fastboot (which we don't need, since encore doesn't use dedicated boot and recovery partitions) and minus a 'clear bootcount' setting since, well, development is up to speed w/NC that such a feature seems not necessary.
That said, here's the new stuff:
new exciting splash
Indicator in top left. "E" means u-boot is loading from emmc. "S" means it's loading from Sdcard.
Additionally you can now see the system's "boot count" - the number after the indicator described above. If this count goes up, your boot count is not being cleared as it should be.
Instruction to "hold down "n" for menu"
boot menu is way easier to use, clearer, and uncluttered.
all the old stuff is there (Nook Color Tweaks' boot settings), combo keys, etc.
If you feel bold and are willing to risk everything, give it a try and let me know if you run into issues. Think of this as an alpha. If people like it, I'll push it to the repo as the default.
To install: It's just "u-boot.bin", and it goes in the first partition of your SD or EMMC. Make sure you have a good backup in case things screw up.
NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.
Aside from thanks mentioned in the acclaim thread, I want to add thanks to hacdan and racks for testing for me on emmc and sd.
Seriously though, as opposed to the acclaim version that was in development for weeks, this has been tested for like an hour. On the other hand I actually have a device to try it.
Update March 28, 2012
So thanks to some hard work from tonsofquestions, we've got a new version with some very cool improvements!!!
New Stuff
* The UI now dims out any option in the menu that isn't available
* some nice code refactoring that I was too lazy to do
* the "altboot" button combo (up and down volume keys) will now choose regular boot if altboot is set as default (and vice versa)
* You can now enable a previously "hidden" menu option (plus a second configuration menu) by doing the following commands:
adb shell echo "0" > /rom/u-boot.altboot
adb shell echo "0" > /rom/u-boot.device
This unlocks a "built-in" default menu, effectively doing the same thing as the Tablet Tweaks build options, only right from u-boot itself!
Please test from various configurations (emmc/sdcard/normalboot/altboot/etc/etc)... I haven't tested this one as thoroughly.. or really thoroughly at all. And thanks to tonsofquestions for the contribution!
updates:
9/20/12: Two minor fixes...
9/19/12: Moved to a new repository at nookiedevs.
3/28/12: New features from tonsofquestions. See update notice above.
3/16/12: Clear the "Push n for menu" message on screen once boot has been determined.
cyanoboot-12-9-20.tar.gz
(source)
Another post.
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
911jason said:
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
Click to expand...
Click to collapse
It would go in /boot-- or partition 1. On emmc it looks like: /dev/block/mmcblk0p1 on SD it's /dev/block/mmcblk1p1.
There should indeed be one there already. Along with uImage, uRamdisk, etc...
it's not usually mounted by default. One way to access it is to use these commands from your computer:
$ adb shell mkdir /data/mnt
$ adb shell mount -t vfat /dev/block/mmcblk0p1 /data/mnt
$ adb shell cp /data/mnt/u-boot.bin /data/mnt/u-boot.bin.old
$ adb push u-boot.bin /data/mnt/
$ adb reboot
$ is the prompt, of course. Here's what they do:
1. make a "mount point" (a directory) at /data/mnt so that you can
2. mount the vfat boot partition (p1) at that mount point. Then,
3. backup your old u-boot.bin in case this one is deeply flawed
3. push your local copy of u-boot.bin (CyanoBoot) on top of the old one, and
4. reboot and hope it doesn't crash.
Good luck, and my apologies in advance if/when this screws up. Remember, you are assuming all risk here
(you can also do it by loading clockworkmod, mounting boot to /boot and then backing up and/or pushing u-boot.bin to /boot)
911jason said:
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
Click to expand...
Click to collapse
its in the boot partition
Works like a charm! Very nice!
thanks fattire, this in my opinion is much nicer then the other menu we have available to us. hope to see you polish this off
ehh, the possibilities of running 4 OS's with this makes me smile
Dropped it into one of Eyeballer's nightly opengl zips (http://forum.xda-developers.com/showthread.php?t=1526115) and it works great! Thanks fattire!
Excellent work, Thanks
Been following your development on the NT even though I don't have one. I was hoping this would be ported sooner or later.
Can someone please drop this into a normal ZIP file and put it somewhere where it can be downloaded?
Thanks....
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Additionally:
@ fattire... is it ok if I include this in my file for customizing ROM's in this post instead of the cyanogen u-boot.bin?
DizzyDen said:
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Additionally:
@ fattire... is it ok if I include this in my file for customizing ROM's in this post instead of the cyanogen u-boot.bin?
Click to expand...
Click to collapse
Sure and sure. Be sure to include the GPL notice.
CyanoBoot in RAR
Thanks to fattire for all the hard work put in for our devices... and with his ok... here is the CyanoBoot in RAR format for those that have difficulties with gz files.
I will keep this updated and named to coincide with development.
DizzyDen said:
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Click to expand...
Click to collapse
Thx Dizzy....I'll find the win-gz and use that.
---------- Post added at 02:21 PM ---------- Previous post was at 02:09 PM ----------
Works great on an SD card using CM7
Thanks Fattire!
Good to go in my opinion, great work as always fattire.. my nook and tp would be collecting dust if it wasn't for your hard work
Just since we're chiming in here, yeah looks ready to me too. I've been testing several types of software this last week, some of which require flashing and rebooting for what seems to be all day. No joke, I have probably rebooted 60+ times since I downloaded this yesterday. Multiple installations, multiple configurations. No dual-emmc, but everything else has worked great.
It has been kind of bittersweet to lose the little green box though, even to such an obvious upgrade. Despite all the crap I've tried on this thing, once that logo showed up, I knew it was gonna be okay, ya know?
I have had a totally different relationship with technology since the very first time I laid eyes on it.
Good of time as any to thank the commenters on this thread in particular.
Heh. I know what you mean re that green logo (from drakknar, btw). For me it was a HUGE battle to get a multi-colored logo to appear in the first place ...This commit and this one took many, many cycles of booting and rebooting... and trying to figure out how to get the pallette to work, etc. Before it, the u-boot could only do black and white logos (does anyone remember the "Loading..." text?) and it looked pretty awful. But nemith made a good case that for the next revision, the newer u-boot might be rebranded since it's not the start up for only CM... Still, I kept the "cyano" part in the name as a tribute...
Thanks for testing, and I'm glad y'all are having success. Maybe tomorrow I'll push to the repo.
mateorod said:
It has been kind of bittersweet to lose the little green box though, even to such an obvious upgrade. Despite all the crap I've tried on this thing, once that logo showed up, I knew it was gonna be okay, ya know?
I have had a totally different relationship with technology since the very first time I laid eyes on it.
Click to expand...
Click to collapse
Just curious: Tell me about your relationship with technology and how it's changed? I feel like the NC in the last year has really helped me to learn a LOT.
OFF-TOPIC (spoiler alert).
I got a replacement nook for the one my wife got me at Christmas last October. I was absolutely flabbergasted that they has changed the storage so that it couldn't hold the books and music I had sideloaded on the original. I looked to see what I could do, and followed directions to repartition the emmc.Flashing the ROM was an afterthought.
I didn't know before finding the info that the reader had external storage. I didn't know what an sdcard was. I had to sign up for Gmail. My last computer died because of the Love Bug.
Yes.
The only reason I registered here was because I couldn't understand why every time I tried to install the Google Music Manager .exe, it wouldn't work.
Today I decompiled a services file and edited it, so I could share it with others. I spent this evening testing a package distro system. I posted in the forum and some of the words are in color!
My wife bought me an e-reader, you know? These things you've made have had a big impact and it can't only happening to me.
Thanks fattire! Have it on my SD and it works great!
I'm not sure if this is a bug or just a user common sense issue, but if you select an Alternate boot from the menu without actually having an alternate image, the Nook freezes on "Loading AltBoot from"... requiring a hard reset.
Obviously, if you don't have an Alternate boot, you wouldn't be selecting it. But I wasn't sure if there could be a potential improvement, like if Cyanoboot doesn't detect an uAltImg, it wouldn't give it as an option?
I never tried S8500 Android, nor I have experience with Android handsets...
But I have stupid Questions.
Feel free to correct me, if I'm too stupid.
1.
I have never seen "optimized" aka custom ROMs...
Why?
Is it not possible to remove few Sounds, Pics... config files?
Maybe edit few settings...
2.
What is with such funny and normally easy tasks like this...
Some Logo or maybe start Animation or something like this:
http://forum.xda-developers.com/showthread.php?t=1396818
3.
Please read now carefully or ignore it.
Your choice.
Everyone is welcome to post something usefull...
if not usefull... who cares...
Free speech for everyone.
Best Regards
P.S.:
I'll start soon with Download files... and check few things...
As I am Android MEGANOOB.
1. Kernel is not ready so it is harder to make a ROM
2. The boot animation is a minor thing. The most important is to make android working on Wave I and II. Maybe after the devs would choose a boot animation.
1. Kernel is not ready so it is harder to make a ROM
2. The boot animation is a minor thing. The most important is to make android working on Wave I and II. Maybe after the devs would choose a boot animation.
Click to expand...
Click to collapse
At the moment our Porting "Gods" not talk anymore with as stupid groupies...
I am not dumb enough to wait ... wait...
Why not use time to learn something.
I will starting now with lesson 1.
I will teach myself.
Attention. Lesson 1.
Downloading file from Internet... You need any space on HD and Browser...
Lesson 2.
After 10000 seconds I found this file:
ext2system.zip
Impossible task.
Zippo I know, but what is ZIP...
Sounds like .trip...
Oh, found something to decompress...
ZIP
WinRAR
Lesson 3.
New file ext2system.img
What I need to open this file...
Thanx in advance...
Best Regards
Okay, this time no joke...
How to extract *.img
Maybe this?
http://forum.xda-developers.com/showthread.php?t=1132724
Need some time for learning...
Best Regards
There is very useful page where You can check file formats and how to open it :
fileinfo . com/extension/img
Maybe you dont have to open img files.
http://forum.xda-developers.com/showthread.php?t=1212616
you can find all the files inside the img files in this thread hopefully. If the links still works.
adfree said:
Okay, this time no joke...
How to extract *.img
Maybe this?
http://forum.xda-developers.com/showthread.php?t=1132724
Need some time for learning...
Best Regards
Click to expand...
Click to collapse
You just have to mount it under linux (something like mount -t ext2 -o loop whatever.img /some_folder). It's an ext2 filesystem image.
But without the working kernel you can't do much... You can change the boot animation (it's stored in the system.img), or the boot logo with some tricks (you have to trick here as the bootlogo comes from the kernel, but it's pretty easy to change).
What do you want to acheive?
What do you want to acheive?
Click to expand...
Click to collapse
Good question...
I want to see files inside to analyze... learning.
This is what I do since 2006...
Playing with Firmware...
Maybe Android is cool...
NO idea yet. As no Android handset in use nor Linux on my PC...
But why not use time...
I am not smart enough to have enough Coding skills...
But my butt is fat enough... waiting for something is not really an option.
Best Regards
As Windows Fanboy maybe I'll try this...
http://www.howtoforge.com/access-linux-partitions-from-windows
Best Regards
My fault...
WinHex can extract files from ext2system.img
Later more...
Best Regards
as I've said many times, you can MOUNT the ext2system.img file from a Linux system using the following:
mount -o loop ext2system.img /some_dir
kind of same principle as here, except it's ext2 filesystem and not samsungs moronic rfs:
http://forum.xda-developers.com/showthread.php?t=751827
when working with android it's definitely preferable to do so on a Linux system, suggest you try installing Ubuntu on a Virtual machine.
I guess the reason a bunch of custom roms haven't popped up is because the lack of modem drive means they don't make it more useful, and we still have no idea how to solve problems like the sleep-power off or microphone crash.
If you want to have a go at modifying it however, the contents of the ext2system.img file are mostly from the I9000XXJPX firmware's "factory.rfs" file image, and many modifications that can be done to that (which is froyo 2.2 based) can possibly be made to work with this one.
note: do not attempt to use the recovery system for any of the "update.zip" packages available
I can see *.qmg Pics...
Are there any Viewer for Android?
I mean any Tool to see *.qmg on PC?
Interesting...
Around 1000 files in 50 folder...
biggest file is Swype.apk with 10 MB...
libicudata.so is with 6 MB biggest .so file in lib folder...
.so are ELFs...
Hmmm...
First I would remove Sounds...
Btw... few Fonts... in ttf...
Hmmmmm.... maybe first would be around 50 MB reduce...
Best Regards
adfree said:
Hmmmmm.... maybe first would be around 50 MB reduce...
Best Regards
Click to expand...
Click to collapse
But why do you want to remove stuffs from it? It's just storage space... I think you'd better install the SD based "release" on your Wave, it's easier to experiment with it. But I totally agree with nbates66: you will need Linux at some point to progress. I have Ubuntu in VirtualBox to tinker with Android.
the ".so" files are kernel module drivers(I am incorrect here, ".ko" files are kernel modules, ".so" files are some form of library), ".apk" files are android applications. The contents of .apk's can be extracted by using an archiver, I just checked using 7-zip.
".qmg" files are basically some sort of animation graphic, you can see them in /system/media/ for battery animation, and boot animation, there is nothing new here it has all previously been modified to death on the 100's of other android devices and most mods done for a Galaxy i9000 Froyo 2.2 firmware should be workable for this one.
you can also clearly see the shutdown animation stored as a set of .png files at /system/media/video/shutdown
the various audio files are all in the .ogg format in audio.
the 4 files inside "/system/firmware" are firmware files for a Galaxy i9000 camera NOT FOR A WAVE S8500 camera!!!
the bootsound and various settings are stored in "/system/etc"
"/system/bin" has various executable files used by the system, though they all are symlinked from "toolbox", this includes things like mv (move file), rm (remove file), and also executables for tasks during boot and handling wifi like "bootanimation" or "playlogo" and "dhcpcd"
if you really have to look at it from within windows, I believe Winimage can extract the contents of ext2system.img.
EDIT: wrong on ".so" files
".qmg" files are basically some sort of animation graphic, you can see them in /system/media/ for battery animation, and boot animation, there is nothing new here it has all previously been modified to death on the 100's of other android devices and most mods done for a Galaxy i9000 Froyo 2.2 firmware should be workable for this one.
Click to expand...
Click to collapse
I need only way convert from qmg into JPG or PNG...
QMG-->JPG
Reason is very simple in my eyes.
the ".so" files are kernel module drivers,
Click to expand...
Click to collapse
Hmm. Maybe now more clear... if folder is named lib like library.
Then these are only parts... like DLL in Windows world...
Btw...
"Surprise". QMG and *.so also exists in bada world...
About *.so...
Are these proprietary Samsung stuff?
Or open source...
Maybe then we could more understand, what is for what...
But why do you want to remove stuffs from it? It's just storage space...
Click to expand...
Click to collapse
Why not... nobody will die or explode.
1.
Train my little brain
2.
Removing unnessary crap can help to free more RAM or other memory...
This is no secret.
3.
XDA is for sharing knowledge and to learn something usefull.
Not only download, without asking why...
Best Regards
adfree said:
I need only way convert from qmg into JPG or PNG...
QMG-->JPG
Reason is very simple in my eyes.
Click to expand...
Click to collapse
well i'm afraid I don't know how to open the QMG's themselves, but all they contain are some sort of animation, the "playlogo" and "playlogos1" executables appear to be something non-standard Samsung created for their boot animations, to use custom animations I believe the workaround used is to rename the playlogos file to something else, and in it's place put a file that points to the android standard "bootanimation" executable, the bootanimation executable plays a boot animation from the "bootanimation.zip" file which is just a zip file with a set of images and a txt file that describes how it should play
here is some info regarding the bootanimation.zip: http://android.modaco.com/topic/338...nimationzip-futurama-bender-bootanimationzip/
adfree said:
Btw...
"Surprise". QMG and *.so also exists in bada world...
About *.so...
Are these proprietary Samsung stuff?
Or open source...
Maybe then we could more understand, what is for what...
Click to expand...
Click to collapse
well the QMG format I believe is some proprietary Qualcomm format (the modem in Wave phones which happens to be Qualcomm can be used for processing of various formats) but the (INCORRECT INFO).so file extension is used across a variety of systems for kernel driver extensions, and .so's are used in this case and for many android devices to allow manufacturers to install drivers without putting them into the Android kernel source (which apparently voids them the responsibility of publishing source codes) however .so's are NOT inter-compatible with different systems, IE bada .so files will likely fail if you attempt to use them on Linux kernel and vice versa, even Linux .so's for a slightly different Linux kernel version fail to load.(".ko" files are Linux kernel modules, ".so" files have been described as some form of software/native code libraries)
as for storage space on the "ext2system.img" file, it is generally mounted as read-only by the system and not modified unless your modding, the space in ext2system.img is normally not used for install of applications or for file/document/save storage of any kind.
sorry if this post doesn't make much sense, I in fact know very little about the inner workings of android, I mainly contributed slightly to modifications on init.rc:
http://code.google.com/p/badadroid/source/browse/trunk/nbates_files/xxjpxinitramloop030711/init.rc
EDIT: regarding the QMG format I just had a rethink and remembered that the Galaxy i9000 (from which this firmware came from) has a completely different modem configuration other than manufacturer (Qualcomm) yet the animation plays fine on Wave S8500, so possibly not the modem that is processing it in this case.
EDIT2: wrong about ".so" files
Hello guys, please make me clear this. I own a samsung wave y s5380 with bada 2,0 os the phone has a 832 mhz cpu, can this phone support Android?Can I upgrade os to android instead of bada?Please answer me I searched whole internet and didn't find any tread or post to say something about if this can be done or not.Thank you and have a good day.
Hello guys, please make me clear this. I own a samsung wave y s5380 with bada 2,0 os the phone has a 832 mhz cpu, can this phone support Android?
Click to expand...
Click to collapse
S5620...
http://darkforestgroup.com/forum/index.php/topic,9231.0.html
This is Broadcom based...
...I searched whole internet...
Click to expand...
Click to collapse
Sure...
This is the reason why you think its easy to port to every device...
Your handset S5380 is also Broadcom based...
BUT this all on similarity with S5620 Monte....
S5380 NO known or confirmed Android solution yet...
Sorry.
If wrong answer.
Sorry.
Best Regards
I still hope that will appear something that can I upgrade from bada to android (
I still hope that will appear something that can I upgrade from bada to android...
Click to expand...
Click to collapse
Hope ever dies at last...
BUT why the hell you buy an bada handset, if you love Android?
Fastest working solution for your problem is.
Buy Android handset.
If you have time... much time.
Range between 0 and open end... (in years)
Then wait or maybe port self Android to your handset.
No joke...
There are several projects to port Android to unsupported handsets...
Why not start new project for S5380...
You need only NEW Devs... so you can recruit NEW Team members.
It makes sense ... user with S5380 or Broadcom knowledge like Monte team...
Again. For Broadcom I know only this:
http://darkforestgroup.com/forum/index.php/topic,9231.0.html
Good luck.
Best Regards
This is a simple tool/script used to:
1. convert .jpg .png and .bmp files into the format used for the splash screen on your device.
2. Make a full backup/restore of your device.
3. Flash the new image to your device.
I have only tested this on the HTC Droid DNA, if anyone wants to test it for another device and post results that would be great.
This script is based on the work done by TrueBlue_Drew, but since I am on a Mac, I got tired of booting a virtual machine every time that I wanted to make a new splash screen. So I decided to "convert" his script to a bash script to make my life easier. After testing several boot screens and all of the functions myself to make sure they all work, I decided to share the script with everyone here on XDA. I have been using this site since I got my first Android phone just a few years ago (and it was a Motorola Citrus...one of the worst "smart" phones ever created!), and have learned a ton - I figured it is time that I start giving back to the community.
If you like my work, don't be afraid to click the "Thanks" button. If you see any way to improve the script or have suggestions for other functions, leave a comment. If you have a question about bash scripting or using adb, leave a comment (I may or may not be able to help, but I will try...and there are many others here that can help).
Thanks again to TrueBlue_Drew for writing a nice little batch file that got me started on the path to creating this tool for myself.
The flash/backup splash option should work for any HTC devices that use a 1080x1920 splash screen but has ONLY been confirmed working with the HTC Droid DNA (I will add others to the list if anyone else confirms they work. I am already thinking about a way to select an option for the boot screen size you want to convert in order for this to work on more devices. :fingers-crossed:
REQUIREMENTS
1. Written on Mac running OSX 10.9.1 (Mavericks), but should work on any OSX Mac
2. Rooted HTC device with S=OFF and Eng Hboot
3. 1080x1920 png, jpg or bmp image
INSTRUCTIONS
1. Download the attached zip and unzip it somewhere on your Mac.
2. Create or find the 1080x1920 image you want for your splash screen.
3. Go into the "Splash Flasher Mac" folder you unzipped and place your image
in the "place-image-here" folder.
4. Run the file "splash_flasher.sh" file in the terminal and follow the on screen instructions.
NOTE: At this time this does not support having more than one of the same image type in the "place-image-here" folder when converting and flashing. A fix for that is already being worked on, but didn't see it as a major issue right now since you can only flash one splash screen anyway.
NEW NOTE: I was finally able to get the multiple images in one folder working and have implemented it only for .png images (other file types coming with next version). So now you can dump multiple .png files in the folder and the program will create the boot images, name them using the original filename and move them to the "images" folder. The next part of this to figure out is how to select your screen size and create a boot image of that size. Stay tuned...not that it seems many people are tuned, but that's OK.
NOTE: VERSION 1.2 - Removed support for .jpg and .bmp files. Didn't see the need to support multiple file types. There is now a Photoshop template file included with the script. Just open in photoshop and add your image to the top layer (labeled as "Team Logo" because I am using that as my template for my sports teams splash screens). If your image is large and covers the HTC and Beats logos (and you want them in your splash screen), just move the layers around how you want them. The colors of the HTC letters can also be changed however you want.
RESERVED
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
drakemata said:
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
Click to expand...
Click to collapse
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
I don't typically work with Windows, either...but I know there us still a large demand for making things easier for Windows users since a great majority of them are not as inclined to do stuff at the command line.
As long as there is one person interested, I will continue to work on this. Thanks for your reply.
Mav3rick40 said:
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
drakemata said:
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
Click to expand...
Click to collapse
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Mav3rick40 said:
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
Ok cool. Yeah I'm going to school for programming.
Sent from my HTC6435LVW using Tapatalk
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Mav3rick40 said:
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Click to expand...
Click to collapse
You need to navigate to it from the terminal and do ./splash_flasher.sh
Sent from my Droid DNA using Tapatalk
I figured it out after playing around with it for a couple of hours.
Sent from my HTC6435LVW using Tapatalk
Glad to see you figured it out. I am trying to convert this over to an Applescript app as well as working on my Linux version and making new splash screens for all sports teams (which was a much bigger undertaking than I thought it would be).
If you have any suggestions for improving the script or for additional tools that should be added, I would appreciate the feedback.