Related
Hi to all,
I don't know if thisever been post it or not! but I want to start a new post that veiw all the nice image of boot splash (not the welcome screen, but the first 2 images when you boot your phone in RUU_signed.nbh format)
I have custom ROM and I love it but I don't like the images (phone carrier) when I boot my phone and I want to change it if I can
I can't help myself
Obviously I have to post my own work first!!!
Cheers
andrew-in-woking
p.s. Use the initial boot splash screen (the one you have to flash to the phone) on Kaiser (Tytn II) only!
nice work. keep up the good work
From a ROM I made a while back, still use it!
can you share your boot splash with us please!
its for touch?
ka911 said:
can you share your boot splash with us please!
its for touch?
Click to expand...
Click to collapse
Should work on anything, it's 320x320 so it will load in landscape.
Jusr right-click and save !
These are mine that I use for my sprint touch:
how do you make one of these?
is it just an image and you put it into windows?
compiled from others, Can not remember who
How do I do to get costume splash screen? Save the picture and then were I put it and what should it be named?
brol1k said:
These are mine that I use for my sprint touch:
Click to expand...
Click to collapse
a HIM fan!
nice!
heres mine
The one thats from my iPhloam theme
all this image nice but I was looking for specific images format (RUU_signed.nbh) file
bedaweed said:
how do you make one of these?
is it just an image and you put it into windows?
Click to expand...
Click to collapse
You have to name it welcomehead.96.jpg and it must have the size of your screen to fill it. And yes it goes in windows. There is also a small mort script named random splash screen which launches splashscreens from a defined folder randomly on every start up... very nice
ka911 said:
all this image nice but I was looking for specific images format (RUU_signed.nbh) file
Click to expand...
Click to collapse
That's the actual ROM file, not the splash image.
claus1953 said:
You have to name it welcomehead.96.jpg and it must have the size of your screen to fill it. And yes it goes in windows. There is also a small mort script named random splash screen which launches splashscreens from a defined folder randomly on every start up... very nice
Click to expand...
Click to collapse
Should be a .png file.
TheChampJT said:
That's the actual ROM file, not the splash image.
I understand that! I have Bell Rom and I want to chnage the Bell boot iames. I can't do it by chnaging the png image file...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TheChampJT said:
That's the actual ROM file, not the splash image.
Should be a .png file.
Click to expand...
Click to collapse
I think he is looking for the first two splash screens like Badbert used to make
sort of like these:
http://forum.xda-developers.com/showthread.php?t=308504
DON"T USE THEM IF NOT AN HTC WIZARD
( sorry I could not be of more help... but if it exists for wizards, it should exist for other devices as well)
Ages ago when JASJAM put a call out for one of his Black Hermes roms ...
There was this awesome Cylon one i never got down ..
S.V.I said:
I think he is looking for the first two splash screens like Badbert used to make
sort of like these:
http://forum.xda-developers.com/showthread.php?t=308504
DON"T USE THEM IF NOT AN HTC WIZARD
( sorry I could not be of more help... but if it exists for wizards, it should exist for other devices as well)
Click to expand...
Click to collapse
right this is what I'm looking for! but for HTC Touch
Here's mine
Hey guys,
I'm looking for the proper directory to push wallpapers into my device, so I won't have to load it off the SD Card. Especially interested to inject the default Desire wallpapers.
Thanks,
Evan
The wallpapers are usually part of an apk. Usually it is Launcher.apk
If you know how to edit the files within an apk, that is one way, if not, its pretty simple, just find the wallpaper you want. Find the one you want to replace. Rename the wanted wallpaper to the same as the wallpaper you will be replacing. Copy it over and do the same for the wallpaper_small.png file that corresponds. Then either adb push or use an adb GUI to get the launcher.apk back over to the phone.
This is in no way, a detailed description, just the jist of how to do things.
launcher2.apk if you're running Android 2.0 or higher.
But otherwise, above is correct.
Cheers guys,
Can I just keep adding files? Or do I have to rename files?
hidea said:
Cheers guys,
Can I just keep adding files? Or do I have to rename files?
Click to expand...
Click to collapse
No, you can't just add... there are a pre-defined and finite number of "slots" - you can't include more than the application currently supports. Files need to be exactly the correct names.
Also, if the files are different sizes, or you change too many, you'll upset the digital signature on the launcher2.apk you'll need to resign the launcher2.apk file before pushing it back.
If that all sound too hard let me know...
djmcnz said:
No, you can't just add... there are a pre-defined and finite number of "slots" - you can't include more than the application currently supports. Files need to be exactly the correct names.
Also, if the files are different sizes, or you change too many, you'll upset the digital signature on the launcher2.apk you'll need to resign the launcher2.apk file before pushing it back.
If that all sound too hard let me know...
Click to expand...
Click to collapse
That does sound a bit 'hard'. But nothing I can't tackle with a bit of reading.
So, how do re-sign the launcher2.apk file?
hidea said:
That does sound a bit 'hard'. But nothing I can't tackle with a bit of reading.
So, how do re-sign the launcher2.apk file?
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?p=5856509&#post5856509
Let me know how you get on.
That doesn't sound overly complicated, but it's too much work for a single wallpaper from the HTC Desire. As of right now, it resides in the SDCard. And I do use HelixLauncher2. I wish there's a simpler way… let's say, like an app that can inject files directly into HelixLauncher2.
Thanks for your help, though!
Fair enough.
You may be interested in keeping an eye on Kang-o-rama, that uses HelixLauncher2 and I'll be adding some static wallpapers back in in version 0.6.
If you are interested, let me know which wallpaper you want and I'll put it in there for you...
i was wondering if there was a way to change the size of the soft buttons for home, back, ect. I was hoping to make them smaller as to not interfere with games and other apps. as well as making the home screen larger and better looking. please if any one has any info on this i would appreciate it. i am not a developer but do have lots of android experience so any info may be useful. Thanks
EDIT: with new firmware out if you have updated the frameworks posted here so far wont work. i am trying to get someone to post a new framework from the new firmware. Hopefully someone will. Thanks
The icons you're interested in are located in the drawable folder of the framework-res.apk (buttonbar_sys_*), along with the relevant xml files. I tried resizing the existing icons, but all you get is smaller icons! The buttonbar remains the same size. I'm currently looking at which xml file to edit to resize the bar itself.
cool looks like a start at least. keep me updated. thanks
You can remove side panel alltogether. Buttons will then placed in the top status panel. Root is needed.
From Archos Gen8 FAQ on 4pda.ru (can't posting outside links, sorry):
In the /data/local.prop file add string
Code:
ro.board.has_buttonbar=no
reboot
to change buttons size, install app LCD Density
add to local.prop sting
Code:
ro.sf.lcd_density=120
reboot
PS. Perhaps with modified buttons from reply #2 we don't need the last step, as it change font size too.
you can also use the app 'lcd density' to change the resolution of the screen, which makes the buttons smaller.
tashtego said:
You can remove side panel alltogether. Buttons will then placed in the top status panel. Root is needed.
From Archos Gen8 FAQ on 4pda.ru (can't posting outside links, sorry):
In the /data/local.prop file add string
Code:
ro.board.has_buttonbar=no
reboot
Click to expand...
Click to collapse
This (and other system settings) can also be found here at XDA
to change buttons size, install app LCD Density
add to local.prop sting
Code:
ro.sf.lcd_density=120
reboot
Click to expand...
Click to collapse
Just to clarify, you either need to add that string to local.prop or install LCD Density, no need for both. The only problem with this is that it changes the size of the entire UI, and makes the icons in the status bar really tiny. That really bugs me!
PS. Perhaps with modified buttons from reply #2 we don't need the last step, as it change font size too.
Click to expand...
Click to collapse
There are different images for the icons in the notification bar. They are also in the drawable folder, but are called stat_sys_*. Also, simply resizing those doesn't work either. Tried it, but the icon area stays the same, so the smaller icons are just stretched out to fill the space - doesn't look good!
Why all the guys want to kill the softbuttons?
Without them, it don´t work
The only thing is bad on the buttons is the fact that they still there by playing games
But on my Archos 5 IT , theres an fullscreen mode with that you can disable the bar/buttons by playing games.. maybe a dev can look at it
Lennb said:
Why all the guys want to kill the softbuttons?
Without them, it don´t work
The only thing is bad on the buttons is the fact that they still there by playing games
But on my Archos 5 IT , theres an fullscreen mode with that you can disable the bar/buttons by playing games.. maybe a dev can look at it
Click to expand...
Click to collapse
no, kill them than install softkeys, it works for me, no any problem^^
Reading through gen8 thread on 4pda.ru i have found another method:
For example, for 32px notification bar height, unpack framework_res.apk and change file \res\values-long-mdpi\dimens.xml as follows:
Code:
<dimen name="full_statusbar_height">32.0px</dimen>
<dimen name="compact_statusbar_height">32.0px</dimen>
<dimen name="statusbar_button_width">40.0px</dimen>
<dimen name="statusbar_button_height">32.0px</dimen>
And don't forget string "ro.board.has_buttonbar=no" in the \data\local.prop
No need to resize images. They will be scaled down automatically.
See attached screens.
ahh looks like progress , im guessing im going to need root if i want to change the framework_res.apk? which one is best for this archangle, uruk or churlis method?
tashtego said:
Reading through gen8 thread on 4pda.ru i have found another method:
For example, for 32px notification bar height, unpack framework_res.apk and change file \res\values-long-mdpi\dimens.xml as follows:
Code:
<dimen name="full_statusbar_height">32.0px</dimen>
<dimen name="compact_statusbar_height">32.0px</dimen>
<dimen name="statusbar_button_width">40.0px</dimen>
<dimen name="statusbar_button_height">32.0px</dimen>
And don't forget string "ro.board.has_buttonbar=no" in the \data\local.prop
No need to resize images. They will be scaled down automatically.
See attached screens.
Click to expand...
Click to collapse
Can you attach your moded framework-res.apk? I have an A70S if that matters. I don't knw how to mod the xml myself so please help out
tashtego said:
Reading through gen8 thread on 4pda.ru i have found another method:
For example, for 32px notification bar height, unpack framework_res.apk and change file \res\values-long-mdpi\dimens.xml as follows:
Click to expand...
Click to collapse
Nice find, thank you so much for sharing. Was still looking at xml files in the drawable folder.
Bickmista said:
ahh looks like progress , im guessing im going to need root if i want to change the framework_res.apk? which one is best for this archangle, uruk or churlis method?
Click to expand...
Click to collapse
Won't work with Archangel root, as that doesn't allow you to make changes to system files.
saprano614 said:
Can you attach your moded framework-res.apk?
Click to expand...
Click to collapse
Will be making some changes to my custom framework, so check out my thread over the next few days.
i need A framework for an 70it. I don't think that the one for a 101 will work on mine. But I don't know.
fisha21 said:
Won't work with Archangel root, as that doesn't allow you to make changes to system files.
Click to expand...
Click to collapse
cheers just one more question, would this work on the A43?
Attaching zipped framework apks, 32px and 24px versions fo 70IT, courtesy by bokorez from 4pda.ru. He used rooting method from here: http://forum.xda-developers.com/showthread.php?t=930197 (permanent r/w). I myself now only waiting for tablet, so i can't check files yet. Use it for your own risk please
It would be fine if somebody much knowledgeable than me would explain here, how to upload these files on the device.
Thanks alot. that helped out a great deal.
EDIT: I think that both are the same. i used them both and they worked but both changed the size to the same. i think that they are both 32px.
tashtego said:
Reading through gen8 thread on 4pda.ru i have found another method:
For example, for 32px notification bar height, unpack framework_res.apk and change file \res\values-long-mdpi\dimens.xml as follows:
Code:
<dimen name="full_statusbar_height">32.0px</dimen>
<dimen name="compact_statusbar_height">32.0px</dimen>
<dimen name="statusbar_button_width">40.0px</dimen>
<dimen name="statusbar_button_height">32.0px</dimen>
And don't forget string "ro.board.has_buttonbar=no" in the \data\local.prop
No need to resize images. They will be scaled down automatically.
See attached screens.
Click to expand...
Click to collapse
Ok I can't find that file in the framework-res.apk. there is no values-long-mdpi folder. A little help
saprano614 said:
Ok I can't find that file in the framework-res.apk. there is no values-long-mdpi folder. A little help
Click to expand...
Click to collapse
I don't know why, but if you open apk with archiver program, there is really no such folder, but if use
Code:
apktool -v d -s framework-res.apk
you get:
Code:
$ ls framework-res/res/values-long-ldpi/
dimens.xml
I think that both are the same. i used them both and they worked but both changed the size to the same. i think that they are both 32px.
Click to expand...
Click to collapse
No, they are different. File framework-res/res/values-long-ldpi/dimens.xml are the same in both versions and contain "24.0px" value (this is error, i suppose). Files framework-res/res/values-long-mdpi/dimens.xml are different and contain "24.0px" and "32.0px" values in 24- and 32-version respectively.
It seems i need to sort it out with the author on 4pda.ru, as i don't have device yet. Or you can try to change file dimens.xml in the folders values-long-* by yourself.
tashtego said:
Attaching zipped framework apks, 32px and 24px versions fo 70IT, courtesy by bokorez from 4pda.ru. He used rooting method from here: http://forum.xda-developers.com/showthread.php?t=930197 (permanent r/w). I myself now only waiting for tablet, so i can't check files yet. Use it for your own risk please
It would be fine if somebody much knowledgeable than me would explain here, how to upload these files on the device.
Click to expand...
Click to collapse
Very happy with the 32px framework!
Next step is to get button savior working properly (return and menu and search get disable themselves after a while , only home keeps working... ) and get completely rid of those buttons on the side AND in the bar
sibere said:
Next step is to get button savior working properly
Click to expand...
Click to collapse
Not sure if you saw the following posts on the enable system settings thread?
yepayepa said:
Mates,
I've investigated why Button Savior won't work, and I've found the solution.
In Uruk (since I'm using it), /system/bin/input shell script miss execute attributes.
So, as root just do this:
chmod +x /system/bin/input
That's all.
Cheers.
Click to expand...
Click to collapse
aznmode said:
Ok so here's exactly what I have to do to get all button on Button Savior to work.
Again I'm rooted via SDE so I'm not sure if this works for Archangel root.
1. With Root explorer, go to System> Bin and look for "input" file.
2. Press and hold for option to pop up and select "Permissions" and check all read, write, etc.
3. Reboot the device
4. Then press the regular Menu button (NOT on Button Savior yet) and go to Settings> Applications> Development then uncheck and recheck USB Debugging and hit OK.
5. Now on Button Savior press the either back or menu button.
6. The Superuser permission will pop up and select yes. If superuser is already set previously then a dialog box will shortly appear stating superuser permission applied.
7. Wait till the dialog box goes away, then press the back button. It should now back up one screen. If you press menu nothing will happen since you are in the Development screen which doesn't have a menu option so don't panic if that happens.
From here you can go back to home and test each button and they should all work now.
Each time you reset the buttons might not work again so what you need to do is go back and uncheck/recheck debugging first before pressing any of the Button Savior buttons. If you press any of Button Savior before recheck/unchecking debugging then it wont work. You'll need to reboot. To be safe uncheck/recheck it every reboot prior to using Button Savior.
The permissions should not be affected on reboot. The only time the permission gets unchecked is if you do the 10 second reset (holding power button for 10 seconds). In this case you have go back to step 1.
Click to expand...
Click to collapse
Alright, last week or so, I said I was going to try working on themes and after a few days finally got the whole 9 patch PNG jargon figured out!!! It was a pain in the ass figuring out how it all worked and even after searching i was still unclear.
Software you will need:
Adobe Photoshop or equivalent to edit your PNGs, adjust transparency, add effects)
Android SDK Tools and SDK starter package
Xultimate-d9pc.exe and repsective .zip file (this converts the raw .9.png into a working .9.png)
draw9patch (included in the SDK Tools) *I am working on another way to cut this step out since it is what takes the majority of time*
Java JDK (For Android SDK Tools to work)
Android SDK: Click Me! Android SDK r12 Do all the updates for the tool packages.
Xultimate-d9pc: Click Me!! Extract this into the Android SDK Tools Folder!! VERY IMPORTANT!!!
Java JDK: Click.. for 64 bit Windows Click.. for 32 bit Windows
I have uploaded all of these to my website for your convenience. I don't have the quickest server, so be patient with the downloads!!
Sorry for no audio in the video either. I didn't have a Mic hooked up and figured a video tutorial would be enough. Below is a youtube link and the pasted instructions from the youtube video.
WARNING: the steps below look intimidating, but really are quite easy after you grasp the idea.. I created so many steps to keep the total n00b in mind.
Step 1: Send the .apk that you want to modify from your phone to your email (or transfer your way of choice)
Step 2: copy the .apk somewhere on your harddrive (I put all my android stuff including tools and SDK in an 'android' folder as you will see in the video)
Step 3: open up the .apk in 7zip and navigate to the drawable folder (in this case; res >> drawable-hdpi)
Step 4: highlight all the pngs and .9.png's you would like to modify and copy them to a folder (this is where you will make your edits outside the .apk and compile them at a later time)
Step 5: Open the .9.pngs in photoshop and have some fun! (use your creativity to add overlays, borders, glows, etc.) tip: don't get to complicated, because you will need to pick split/stretch points later for the 9 patch conversion.
Step 6: When done modifying the .9.pngs, just save and overwrite the files you would like (in the case of the MMS app, the same image is used for multiple bubble files)
Step 7: Open up ONLY the .9.png's in the draw9patch tool located in your android SDK tools folder. Add the 9 patch data as shown in the video. Tip: some people only add one middle top and middle left split point/pixel, but i find its usually easier to add TWO points for the top and left quadrant as you will be picking your EXTENTS of where you want the content to be.
Step 8: On the right and bottom quadrant, create a solid line connecting the respective pixels together. These two steps will add the information to the PNG of where to split and stretch from, while also giving constraints of where the content can go.
Step 9: After all the 9 patch images are saved in draw9patch, if you open them you will notice the black pixels you just created. Do NOT, DO NOT try and recompile the .apk at this point, thinking you are done.. the bubbles (in this case) will look like crap, because you are not finished yet.
Step 10: Copy (or move) the newly created .9.png's into the ORIGINALS folder for the xultimate.exe software.
Step 11: Run the xultimate.exe. This will take about 2 seconds or less.
Step 12: naviigate through the 'done' folder and you will notice the .9.PNGs no longer contain the black border pixels!!! CONGRATS!!!
Step 13: Copy all modified images back into the open 7zip .apk archive and overwrite all the existing.
Step 14: replace your current .apk on your phone with this 'new' .apk and enjoy!!
and finally...
Tutorial -couldn't get youtube tags to work.
*If anyone is wondering why I Copied to the REV 2 folder but did the tutorial on the REV 1 folder, I was just demonstrating how to copy the files, but was working on my theme in the Rev 1 folder. DONT BE CONFUSED!!*
Thank you kind sir!
-Sent from my Random Epic.
This could be useful enough to move to Themes and be stickied with dreams tutorial.
Only reason I didn't throw it in those forums yet was that I figured a few people could try it and review the process before it became a 'good' tutorial. I know sometimes a tutorial is easy to understand or works for some people, but others have issues or don't understand the directions as well.
I hope this works for everyone and people are less intimidated to mess with this type of stuff!!
Relating to my other thread, I will continue to work on the MMS and Swype theming, I just wanted to get this together so everyone can start theming!
Wow, this looks very "easy"
Maybe I'll finally be able to edit .9.pngs without help
/sig
Avelnan said:
Phones are going to come to life someday. Take note: LG Optimus line. ASUS Transformer. And now the Nexus Prime.
Click to expand...
Click to collapse
Why not just use apk manager to decompile, edit the .9.png's leaving the black outer border pixels alone, then recompile the apk, extract the modded png's, then copy them into the source apk?
shane6374 said:
Why not just use apk manager to decompile, edit the .9.png's leaving the black outer border pixels alone, then recompile the apk, extract the modded png's, then copy them into the source apk?
Click to expand...
Click to collapse
That's fine in some instances, but it wouldn't really allow you to create .9pngs that are of a different size....
Also...I would think editing them in say GIMP only would "corrupt" the draw9patch data? It seems to me that it's more than just having a few pixels as borders and guidlines, it's also the files data in relation to those pixels
Sent from my SPH-D700 using xda premium
squshy 7 said:
That's fine in some instances, but it wouldn't really allow you to create .9pngs that are of a different size....
Also...I would think editing them in say GIMP only would "corrupt" the draw9patch data? It seems to me that it's more than just having a few pixels as borders and guidlines, it's also the files data in relation to those pixels
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Editing with gimp wouldn't and doesn't corrupt the image from what I know. That's why your able to compile the image after editing it with gimp without error.
Sent from my SPH-D700
ac16313 said:
Editing with gimp wouldn't and doesn't corrupt the image from what I know. That's why your able to compile the image after editing it with gimp without error.
Sent from my SPH-D700
Click to expand...
Click to collapse
Exactly. What I do is cut all but the 1 pixel border into a new layer, edit that layer, merge the layers and save. I understand the concept the op is stating, but all of this can be done with the method I said as well. If you want to completely change, or add png's you will need to also make xml edits to add the image there or change container sizes, which is done by decompiling with apk manager. The only thing you might have to do is run the images throught the draw9 tool, but in most cases you wouldn't even need to do that.
Sent from shane6374's Epic via Tapatalk
also, if you see the black bars, you are dealing with a previously edited rom/apk. when you build from leaks or official google aosp releases you dont have that. very nice work mr. socks
I have a question. How do you create a new 9.png to use, for example with miui lockscreen. I dont really get that. Do I have to create the 9.png as the same as the original 9.png on the lockscreen. just wondering. Any help would be appreciated
thank you
cowsquad said:
I have a question. How do you create a new 9.png to use, for example with miui lockscreen. I dont really get that. Do I have to create the 9.png as the same as the original 9.png on the lockscreen. just wondering. Any help would be appreciated
thank you
Click to expand...
Click to collapse
It really depends on what image it is and what you want it to do. Some aspects that you might think are controlled by an image might actually be controlled by a xml file.
shane6374 said:
It really depends on what image it is and what you want it to do. Some aspects that you might think are controlled by an image might actually be controlled by a xml file.
Click to expand...
Click to collapse
Is there a way to find what aspects are controlled by a xml file.
Sent from my Droid using Tapatalk
cowsquad said:
Is there a way to find what aspects are controlled by a xml file.
Sent from my Droid using Tapatalk
Click to expand...
Click to collapse
Sure, you can take the name of the image and search for it in the xml files. Very easy to do with windows explorer. I use it to fine images and color codes all the time. If you know how to read the xml file you can see how it all works.
I don't know what file you're wanting to edit, but that might help. I'd throw up some resources I've used for you but I'm at work right now.
shane6374 said:
Sure, you can take the name of the image and search for it in the xml files. Very easy to do with windows explorer. I use it to fine images and color codes all the time. If you know how to read the xml file you can see how it all works.
I don't know what file you're wanting to edit, but that might help. I'd throw up some resources I've used for you but I'm at work right now.
Click to expand...
Click to collapse
Whenever you have time, could you email me those resources. That will be appreciated. Pm and I send you my email
Sent from my Droid using Tapatalk
cowsquad said:
Whenever you have time, could you email me those resources. That will be appreciated. Pm and I send you my email
Sent from my Droid using Tapatalk
Click to expand...
Click to collapse
Start with this one here. If you have sdk and draw9patch in the tools folder, you can use this to help guide you. There was one other site I found when I was starting out themeing, but I'm not finding it right now.
http://developer.android.com/guide/developing/tools/draw9patch.html
i tried to run the ultimate.exe but i get an error, my ant/res doesnt exit. how do i fix that
cowsquad said:
i tried to run the ultimate.exe but i get an error, my ant/res doesnt exit. how do i fix that
Click to expand...
Click to collapse
I don't even know what that is. Do you have sdk installed?
Sent from shane6374's Epic via Tapatalk
shane6374 said:
I don't even know what that is. Do you have sdk installed?
Sent from shane6374's Epic via Tapatalk
Click to expand...
Click to collapse
Yes, I do. I have sdk, eclipse and java set up already. I'm gonna reinstall everything now and see the results.
hi there
is there a way to change the boot logos ?
Michael
megasounds said:
hi there
is there a way to change the boot logos ?
Michael
Click to expand...
Click to collapse
Yes, but I didn't tested this yet
-W_O_L_F- said:
Yes, but I didn't tested this yet
Click to expand...
Click to collapse
just give it a try !
how ?
thx m
Registry edit to change logo to "Samsung"
Code:
[HKEY_LOCAL_MACHINE\SYSTEM\Shell\BootScreens]
"WPBootScreenOverride"= "\Windows\System32\mologo_OPEN_Common.bmp" (String)
I did change path and now got both of them, Samsung one and custom because file : mologPEN_Common.bmp is not even displayed. Must be in other location.
Code:
C:\Data\Users\Public\Bootlogo\logo.bmp
Yeah, it'll be different depending on where the phone comes from. Just check your System32 directory first for logo images, then set the one you want. Or upload your own to the phone and use that path...
I looked on all mologo bmp files and none of them looks like the one while booting. So now I got WP, Samsung and the custom one on the end. Is wasting time I believe
true
djtonka said:
I looked on all mologo bmp files and none of them looks like the one while booting. So now I got WP, Samsung and the custom one on the end. Is wasting time I believe
Click to expand...
Click to collapse
TRUE
in my case i do not want to see any boot logo ...i do not know if you can switch it completely off ...:fingers-crossed:
so first we want to know : WERE are the default logo's stored in the filesystem ???
what is the location of the default logos ?
M
megasounds said:
TRUE
in my case i do not want to see any boot logo ...i do not know if you can switch it completely off ...:fingers-crossed:
so first we want to know : WERE are the default logo's stored in the filesystem ???
what is the location of the default logos ?
M
Click to expand...
Click to collapse
the first boot logo is Most likely stored in the bootloader it self ( so no way too Change that one)
Once you have complete file system access, just place one in Windows\System32 and name it "mologo_custom.bmp" for easier reference and save it as a 24bit BMP file. I have the original bootscreen and 2 custom ones for you to choose from, attached below: