Related
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.
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.
As of you guys have found out there has been a few threads that have been started that throw around theories about getting CWMR to work and such and I'm here to finally give you guys the progress from the dev that's working on it.
I have been working on getting CWMR working off and on for a few months now to some avail. I have been slowly testing it and sending out alphas to people on the IRC and now I'm here to tell you where I'm at and what has been accomplished.
Part 1: Getting into CWMR
I started working with our current bootstrap recovery as a base for CWMR. It was of course in charge mode, but it was a step that had to be done first. I got a hold on a CWMR binary and after a bunch of shell commands managed to get the mangled version of CWMR that we've seen before. From there I had the idea to inject the ATRIX binary into the recovery and try it from there. It was a big success and I could use some (very few) of the functions that if offered. But I was finally in CWMR on the X2. (I posted the picture on my twitter).
Part 2: Making the Functions Work
From here the first thing I decided to do was to get the "Fix Permissions" script working. By getting this to work I know I could place my own code in there that will log to the file that I could open up and see whatever I wanted as ADB didn't work YET (more on that later). I fiddled with it a bit and got it working.
This also allowed me to access the log and find out why the unmounting and formatting wasn't working either. This was due to an issue with the mke2fs and other complementary binaries not being appropriately compiled for our phone. As I was working on CM7 at the time, i had access to the sources of these and to the recovery binary as well. I decided to build a recovery binary that was tailored to our phone and not the ATRIX and the binaries that handle formatting partitions, etc. These worked on some partitions I could wipe data and cache properly by reformatting, I could easily erase a partition at will except for one: /system.
Part 3: Getting /system Formatted (WIP)
At this point I decided to find out why /system could never be formatted. When a partition needs formatting it must be unmounted first. But I could never unmount /system. By using the logs I found out that the partition was still in use. By using the "Fix Permissions" script, I managed to find that a lot of daemons (aka services) were being ran from the /system sub directories. This meant that in order to format, I had to have them not running. Easy enough as there's a script in CWMR that allows us to kill certain processes before the new recovery starts. I decided to kill all of the services with this script but found that the display would go blank. From there I found that two services are REQUIRED to be running on the phone for drawing (making things show on the screen) to take place: servicemanager and nvrm_daemon.
The servicemanager does exactly what it's title says: it manages the currently running services. This has to be running to keep nvrm_daemon running or else things get kinda freaky.
nvrm_daemon is what is used to manage drawing commands to the screen (the nv stands for nVidia which is who made the Tegra 2). With this service running I was able to (while in charge mode still) draw to the screen and show all of the menus for CWMR.
This created a problem. As these HAD to be running /system could never unmount because they were in there. Unless we used 2nd-init. From here I created my own hijack script that allowed me to copy over the necessary daemons into /sbin (which is just a sub directory of the rootfs). Then by using a new init.rc I could start these daemons from /sbin and see if they worked for CWMR.
After a lot of coding I managed to get the daemons running from /sbin and I thought I was free from there. And while I was at it, I might as well tried to get it out of charge mode.
Part 4: Untethering the Recovery (WIP)
I figured that since I was using 2nd-init anyway that I might as well have been working on trying to get it untethered also. After a bunch of looking into why charge mode was the only way to get it working, I found that before charge mode was started the init.rc started the "pre-zygote" services. These include usbd (the usb daemon), battd (the battery daemon), etc. What was also started was nvrm_daemon (another proof that we needed this running) to draw on the screen (charge mode draws the battery indicator to show charging progress).
I decided to move to mot_boot_mode to do the hijacking. I eventually managed to get things running but it still wouldn't draw to the screen. A look at the logs showed that for whatever reason we still didn't have access to the framebuffer (the memory space aka buffer that is drawn to the screen). I was tired of rebooting over and over again to get results and by now I had SBF'd I don't know how many times, only to not be able to access the logs due to a wipe. So next thing I decided was to get ADB working at boot.
Part 5: Starting ADB at Boot (The Short Version)
I took a look through the init.rc and found that Motorola had disabled the default way to get ADB working at boot. Through a bunch of digging I found that I could re-enable the method but it started usbd also (yet another daemon I'd have to move and thus more time, etc.). But eventually I found another property (aka system variable) that i could set that would start ADB without having usbd started: persist.adb.enable_NV_DISABLED. Setting that to 1 started ADB whenever I wanted it to. This allowed me access to the system (as root actually) without having to reboot and try to get into logs and whatnot. I could see everything that was running, mount/unmount and do everything I normally could and see better why they were failing.
Part 6: Recent Discoveries (as of 1/3/12) On the /system Unmount
I decided that I was going to go back to charge mode for now. After causing too much pain with framebuffer access I decided to look into why /system STILL wouldn't unmount after moving everything out of there. With the help of mastafunk and DrPenguin I was able to get a hold of a program named strace. This allows you to debug what binaries are doing down to pretty much every comparison, file opening, memory mapping, etc. I had found that nvrm_daemon (although started from /sbin) was looking for and loading drivers found in /system/lib. This was a problem and I thought that we may never get /system unmounted. Until I found out one other thing.
The nvrm_daemon doesn't look for the drivers inside of /system/lib first. It looks for them in /vendor/lib first and then if it can't find them, goes to /system/lib. So simple enough. I thought I could just make a /vendor/lib directory, copy the libs over and have them load from there. Well it's not that simple as there is already a file in the rootfs named vendor. But the file is a symlink to /system/vendor so if it looks at /vendor/lib it really looks at /system/vendor/lib. I thought I was stuck again until I took a closer look at the /system directory. There is no ./vendor sub directory in /system. That being said, I was able to delete the symlink in the rootfs and then create a /vendor/lib directory copy over the libs to it and nvrm_daemon successfully loaded the libs from there and not from system.
Conclusion
You are now caught up on when we've basically done to try to get CWMR working on the X2. Being that we're the only Tegra 2 phone from Motorola that is locked, we're kinda stuck trying to get things working. For now I consider this progress. Albeit slow progress, but progress none the less. If you took the time to read this, I hope you now understand the frustrations I've had to deal with this. All the while trying to help masta get 2nd-init fully working for our phones.
Thank you.
Thank you very much for the detailed explanation - well written so that even a novice like myself could understand your progress and frustrations. Thank you to you and your peers also for your hard work and determination to see this through. I think I can speak for all X2 users and say this is most appreciated!
Great writeup. Very informative. Thank you for your dedication.
I thought 2nd init was done and masta was working on aosp? I mean we can log from our new init.rc so it is using it. In the meantime i've been working on my barebones so we can get new blood using 2nd init and because I want a decent daily driver in the event we cant get stuff going.
To echo what others have said, thank you very much for the information. This kind of transparency is always very much appreciated when there's some spare time to put that out there. It not only is really helpful to make it understandable, but it's nice to know that these projects are still active.
Perhaps most importantly though in the context of potential progress: having specific information is a great way for knowledgeable people reading to recognize if they might be able to help out in certain areas. You might get some fresh ideas from people who hadn't considered themselves familiar enough with the situation to be useful. Who knows.
Anyways, thank you very much again. It's very encouraging to hear progress reports in general, not to mention ones like this that involve so many successes.
Wow thanks so much for your hard work and dedication can't wait until you conquer this sounds like you are closer then ever
Sent from my DROID X2 using XDA App
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
skwoodwiva said:
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
Click to expand...
Click to collapse
No need to appologize man... Stuff like this should have been posted or known. To be honest, I thought Masta was finishing 2nd INIT and starting to work on getting AOSP running and CWM was out the window, thats why I jumped in to try and get progress on CWM. Thanks DK and now I know the IRC is more active, I will be on there more to try and help out.
Thank you!
Thanks a ton for all the effort you're putting in. When I got my DX2 I thought that despite the crazily over-bloated Motoblur, I would be OK due to the Tegra 2 power and wonderfully innovative developer community. I didn't count on their being such a small number of us out there for this device or the complexity that Moto would unnecessarily bake in. So, after many months of gut wrenching disappointment, I finally have hope again.
You are a true nerd hero, sir!
Its nice to have an explanation of things and why they work or dont work. A lot of us are just trying to learn so we can be useful.
Sent from my Eclipsed and ICS themed X2.
Dragonz...after reading the info about 1/3/12 I am curious...
Does this mean that you might be able to get it working and unmount system as u need it to?
Or were there still other processes using system that you will need to mess with and change around as you did with the vendor ?
Do you still need to move the servicemanager also?
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
PM me with a copy of your nightly so I can help as well please
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
drapp said:
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
dragonzkiller said:
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
Click to expand...
Click to collapse
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
aceoyame said:
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
Click to expand...
Click to collapse
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
dragonzkiller said:
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
Click to expand...
Click to collapse
Let me rephrase that, add CM stuff and then remove Moto stuff. So get back to that, delete moto apk's and then edit init.rc for the framework. All those FC's we are getting if when were in that state are vital clues as to whats isn't playing nice with CM's apk's and framework. The fact it can even somewhat boot in a state like that means it's fairly close to how it wants. If it didn't wipe /system/ then it sounds like you just need to properly 2nd init that ***** and then in moto's init.rc remove moto jar's and apks's. Remember if it didn't wipe then you replaced the framework with CM and it's blur running ontop of it.
ashclepdia said:
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
Click to expand...
Click to collapse
Thanks ashclepdia.... helpful as always...
Sent from my DROID X2 using xda premium
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.
Hey guys, i figure this might be a longshot but if anyone has or know someone who has an android rearview mirror ie: http://www.ebay.ca/itm/201130187577?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
If you could take 5 minutes and copy some of your files using adb, you might save me from having turned my android mirror into a paperweight.
adb pull system/framework d:\files\framework
I ran some scripts and i accidentally nuked some files without having made a backup (smart i know..) i'm pretty sure the culprit is framework-res.apk but just in case the command pulls the whole framework folder.
Thanks!
---
It has a weird launcher forced into it, that cannot be replaced as far as i can tell and has an app fireeye.apk that also boots and is forced into memory. I tried to get a different launcher to work, but their interface is modified and the home button is not really a homebutton, but is hardlinked to their launcher. Trying to bypass that i managed to screw it up, also no fastboot, it uses livesuit for restore and as far as i can tell no chance of flashing the cm for allwinner as it has a really weird partition set. I'm kinda stuck.
I have one
I have 2 of these and I am interested in helping you. what do I need to do to get you a copy of the files on it?
Recovery???
How did you get it into recovery mode??? i messed something up and it wont go pass the Android logo!
Sorry to dig up an old thread.
I have one of these dashcams and the fireeye app keeps freezing on me. its really annoying. Until yesterday i have put up with it by resetting the device. Yesterday i was invloved in a minor car accident only to realise that the fireeye app had frozen again and did not get a recording of the accident. would have come in usefull.
Has anyone had problems with the fire eye app freezing and have you figured out a a way around this?
Hoping someone can help
OlvrCA said:
How did you get it into recovery mode??? i messed something up and it wont go pass the Android logo!
Click to expand...
Click to collapse
There is another thread about this
http://forum.xda-developers.com/general/connected-car/android-reversing-mirror-model-rt01-t3097492
This is the download link, and there are instruction which will tell you how to upgrade it.
http://yunpan.cn/cKzgb95TaCEJk
Password: 8880
These were the instructions I got from a seller on aliexpress.
It's a little different but maybe someone could extract from here and make yours work