Ever since I got S-OFF on my G1, I set up a custom splash image. Here's how to do this on the Doubleshot (MyTouch 4G Slide).
Info:
The Doubleshot stores the splash image on the /dev/block/mmcblk0p14 partition, even though it only uses the first 768k of the 6MB partition. By default, this is a white image with green letters spelling the 'myTouch 4G slide' logo in the center of the screen and the '-T---Mobile-' gray and magenta logo above it.
Prerequisite:
Install and get familiar with the Android SDK see Android SDK | Android Developers also [HOW-TO] ADB for Dummies(How-To Learner's Guide) G1 Android Development
Unlock your T-Mobile MyTouch 4G Slide / HTC Doubleshot see How To Turn S-Off, Install MoDaCo Clockworkmod Recovery, and Install a Rom For Dummie
Install FFmpeg
Windows:
Extract the ffmpeg.exe file from the bin folder in ffmpeg-r25512.7z
- or Shortcut - get the getsplash.zip from gariak
Install the adb (Android Composite ADB Interface) and fastboot (Android Bootloader Interface) drivers from the android-sdk-windows\extras\google\usb_driver folder
Mac:
Might find this ffmpeg guide helpful - An easy install of the ffmpeg command line tool - Mac OS X Hints
Backup: (Optional)
To get the current image from the phone, execute this from a root shell:
Code:
dd if=/dev/block/mmcblk0p14 of=/sdcard/splash.img
On your computer, you can turn this into a PNG using ffmpeg from the command line:
Code:
ffmpeg -f rawvideo -pix_fmt rgb565 -s 480x800 -i splash.img -f image2 splash.png
Flash:
You can set the splash by converting an image you want to a 480x800 resolution PNG file, then use ffmpeg to convert it to raw565 format using the command line:
Code:
ffmpeg -i new_splash.png -f rawvideo -pix_fmt rgb565 new_splash.img
Then with an unlocked (S-OFF) bootloader, flash the new_splash.img file to your phone:
Code:
adb reboot bootloader
fastboot flash splash1 new_splash.img
fastboot reboot
OR you can flash from a terminal window on your phone. Be very careful with this method and triple check that you typed everything correctly so you do not accidentally brick your phone:
Code:
dd if=/sdcard/splash.img of=/dev/block/mmcblk0p14
References:
[GUIDE][MOD] Splash Image
[Request] MyTouch splash screen?
[TOOL] [Linux / OSX] Splash Screen creator / flasher
gravis86
gariak
An easy install of the ffmpeg command line tool - Mac OS X Hints
wilnotdie
Absolutely fantastic write up!
This is just the kind of information that belongs here in the dev section.
I like how you explained a lot of information that wasn't exactly necessary, but is very helpful to continue developing this topic in new directions.
Before anyone comes in and says there are threads on how to do this in the "themes and apps" section of the MT4GS forums, let me point out that they do not go into the detail and depth that this guide has done, and this write-up shows how to do it all manually.
Thank you for taking the time to lay this all out so people can see the process, and do it on their own.
MT4GS "themes and apps" links:
Replace your splash screen
Charlieb's gallery of pre-made boot splash images that you can flash with the new method listed here in dev:
Gallery Of Custom BootSplash Screens To Choose From
Great write up, much appreciated.
This was already posted back in September...
Already posted. Also wrong section.
Sent from my mt4gs
Madblaster6 said:
Already posted. Also wrong section.
Sent from my mt4gs
Click to expand...
Click to collapse
No, it hasn't, and no, it's not.
This is very helpful Dev material, which I have already been referencing to try to solve a splash flashing issue.
Please post a link to where it was already posted if you think that was the case, but there are no other dev postings to my knowledge that contain this very useful information.
Blue6IX said:
No, it hasn't, and no, it's not.
This is very helpful Dev material, which I have already been referencing to try to solve a splash flashing issue.
Please post a link to where it was already posted if you think that was the case, but there are no other dev postings to my knowledge that contain this very useful information.
Click to expand...
Click to collapse
Androidautobot referenced this writeup back in September on the MT4GS part of the site....
http://forum.xda-developers.com/showthread.php?t=1258873
@reukiodo - I used your method back in my G2 days so I thank you for that.
Not meaning to steal some else's spotlight but in case anyone seriously needs a noob proof method as posted by others as well and the way I did it back when I still had a MT4G is to go with TrueBlue_Drew's method....You'd have to be a true square headed moron to screw up...
http://forum.xda-developers.com/showthread.php?t=956434
Thanks, jsyi84.
I know about those links in the themes & apps section - and for users that's great.
Neither of the two threads in themes & apps contain the developers info that is included in the OP of this thread.
That's okay, it's not their purpose, which is why they are over in themes & apps.
This thread is a reference for people working on creating things like the utilities linked to in the other threads, and not really targeted at end users.
jsyi84 said:
This was already posted back in September...
Click to expand...
Click to collapse
Madblaster6 said:
Already posted. Also wrong section.
Click to expand...
Click to collapse
I apologize if you think this is a duplicate post or in the wrong section. In my search I was looking for which partition the splash image was stored on, and was unable to find that information.
Now with the reference provided, I see that information was already available, however difficult to find.
In response, I hope you agree that this post has all the information related to the splash image in one location, including a copy of the original splash image.
reukiodo said:
I apologize if you think this is a duplicate post or in the wrong section. In my search I was looking for which partition the splash image was stored on, and was unable to find that information.
Now with the reference provided, I see that information was already available, however difficult to find.
In response, I hope you agree that this post has all the information related to the splash image in one location, including a copy of the original splash image.
Click to expand...
Click to collapse
It's a very valuable piece of information I figured you'd be happy to know someone else already posted a topic referencing your topic lol. I agree it's easier for others to find posted here than having to hunt around in another phones forum lol.....sort of like how some people had to go in the g2 forums to downgrade to 2.2 in order to root their phones in the mt4g forums which only adds to confusion to some as for most people it's a red flag having to do stuff to their $400+ device from information posted for an entirely different phone lol.
+1
10char
I used this tool ages ago when I first got my Doubleshot. It is by far the easiest way to change the splash screen, and is great for noobs. Just follow the prompts, and presto change-o you have a new splash screen!
http://forum.xda-developers.com/showthread.php?t=956434
Here is my splash screen, I love it, but I have had it for so long I may change it to something else now.
Related
hello xda!!! been doing alot of reading here and desided that i wanted to be part of the action...with that said...
did some reading on how to get clockworkmod on the mesmerize and have no clue how in gods name to use adb...is there a how to that could help me better understand how to use it and get this on my phone after i have it rooted...soory for the noob question but as you can see. im a noob at this. only phone i have really modded is the samsung acclaim (which btw is a weak phone but good for the noobie droid user) so any help is greatly appreciated. thanks in advance guys and i look forword to helping devs by testing and such
adb, or android debug bridge, is a tool distributed with the android sdk. In current versions of the sdk, it is located in the platform-tools folder, which only appears after you download the sdk tools after downloading the sdk zip itself.
It should be noted that usb debugging needs to be enabled on your device in order for adb to work properly. This can be turned on under: Applications > Development
To use adb, you open up a command window if on windows or a terminal emulator if on linux or mac. Type:
adb <command> [options]
Where command is any one of the commands listed when typing "adb help" and options are things like file names, paths, or other flags.
Common commands include:
pull
push
shell
pull copies a file on your device to your current working directory (or the optional specified location)
push copies a file from your computer onto the device
shell invokes a simple shell on your device allowing you work in a linux like environment on your device
There is a reboot command that is sometimes helpful but that can always be done using the power button on the device.
You will probably only use push and shell.
Examples:
adb shell
adb push update.zip /sdcard/update.zip
Hope that clairifies things a bit.
yes it does sir...so with those commands i can "push" the clockworkmod onto my mesmerize and have that beautiful recovery? the only directions i found where using the adb. if there any way i can screw this up ei: mistyping or will it just say invalid command or something? and again ty for the fast response!!!
you got the thanks for that...lol...im grateful for any and all help
Typos shouldn't hurt. If it's a bad command it just won't execute. If it's a bad filename you may have to clean up a bit (like remove the file that is improperly named or in the wrong directory) but nothing fatal should happen.
alright...i feel a bit more confident that i can make clockworkmod happen when i get my mesmerize and get it rooted...any other suggested mods for spped?
You should install a custom ROM, (I use Super Clean, some people prefer the pick n pack) then a theme you like from the themes and apps section, then install the voodoo lagfix kernel. Everything mentioned can be found in the Mesmerize forum.
yea i seen voodoo but wasnt quite sure what exactly it does. as far as the pick n pack or super clean...could you tell me the difference or does it say it on the page where it was posted and im just blind and didnt see it?
BakedTator said:
yea i seen voodoo but wasnt quite sure what exactly it does. as far as the pick n pack or super clean...could you tell me the difference or does it say it on the page where it was posted and im just blind and didnt see it?
Click to expand...
Click to collapse
Its obvious you didn't read the threads.
Sent from my SCH-I500 using XDA App
ADB is nice and all ..
But there other ways to install and do everything needed to Flash a ROM or Kernel.
How to get ADB up and running.
And a couple other great links for learning more.
http://forum.xda-developers.com/showthread.php?t=502010
http://forum.xda-developers.com/showthread.php?t=872128
If you look in the Clockwork Mod thread here in the Mez forums there are walkthroughs on BOTH ADB method to get CWM working and sans ADB methods.
And again. Always Read.. Read again.. if all else fails.. Read once more.. And ask.. Everyone here is very informative and glad to help when we can.
I knew nothing of Android before I came here and a month later I know enough now to be dangerous.. LOL
skitzo_inc said:
Its obvious you didn't read the threads.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
i did read just havnt read over it several times to see if i have missed anything...just a lil scared of adb because i have never used it before..i have an acclaim and could do everything from the swupgrade flasher for the moment and that made life easy(aint tryin to brick a 600$ phone)
to Sighcosis
thanks for the link...will read over them tonight seeing as my phone will be here no later than Wednesday and i wanna have everything downloaded and ready to roll cause the second i get this phone imma start fashing it and getting everything i want on it...again thanks for all the help guys...now more reading
Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S
Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS
another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).
albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS
You can get it from here:
Fastboot + Recoveries.7z
I decided because it get's a little tad difficult to find what you might want or need for Recoveries and Fastboot, (I had a B**** of a time myself )
I'd thought it would be nice to offer my assitance, (because I haven't done a d**n thing to contribute since I bought the Q )
So here's a list of nice things I elegantly made for you (Don't ban me mods :angel: :fingers-crossed: )
*What To Do*
For A Little Assistance:
Linux: go to folder and "Right Click" Click on "Terminal/Konsole"
Type "su" (without quotes)
Then copy/paste any of the following (not anything in parentheses)
fastboot flash recovery open_recovery.img (Open Recovery's Mod) (Skrilax_CZ)
or
fastboot flash recovery cwm.img (Clockwork's Mod) (Shabby Penguin)
or
fastboot flash recovery twrp.img (Team Win Recovery Pro) (arrrghhh)
or
fastboot flash recovery recovery.img (Stock Recovery Image) (dunno)
Windows: Go to folder and press "SHIFT and Right Click" run command window (or something close to it)
Then any of the upper ones
Mac: I don't know how to use it, but hey it's here.
Oh yeah thanks to falln Saint, I have my favorite boot logo
It's an android popping it's head out on the Moto with the phone name underneath
fastboot flash logo moto.img
Hope I helped, Have fun :good:
SYKKNYZZ
P.S. I only made it easier to find the files, I didn't create them.
Real credit goes to the members on XDA who work their a** off to help us out. :highfive:
P.P.S. I don't come here often, but if there is any problems, I will answer them as fast as i can.
Why not just link to the thread, where you got the recovery? Including them all in one big .7z file doesn't make a lot of sense - if TWRP or OpenRecovery are updated, that .7z file you have is now outdated...
Just a thought - interesting to see the stock recovery tho!
True
arrrghhh said:
Why not just link to the thread, where you got the recovery? Including them all in one big .7z file doesn't make a lot of sense - if TWRP or OpenRecovery are updated, that .7z file you have is now outdated...
Just a thought - interesting to see the stock recovery tho!
Click to expand...
Click to collapse
Thanks arrrghhh, I just thought to make this simple as possible.
But I do like what is going on with the new roms, I have AOKP because Carbon kept glitching on me and deleting my savedata and setting it under a folder called 0
SykkNyzz said:
Thanks arrrghhh, I just thought to make this simple as possible.
But I do like what is going on with the new roms, I have AOKP because Carbon kept glitching on me and deleting my savedata and setting it under a folder called 0
Click to expand...
Click to collapse
This isn't a glitch, it's a "feature" with 4.2.2.... Unfortunately the more 4.2.2 ROM's you flash, the more this feature will become apparent.
arrrghhh said:
This isn't a glitch, it's a "feature" with 4.2.2.... Unfortunately the more 4.2.2 ROM's you flash, the more this feature will become apparent.
Click to expand...
Click to collapse
Yeah I realized that, but Unicorns are for Gangsters.
And I might go back to carbon, if it didn't delete my info even when I reboot normally after flashing. But thanks for your hard work.
Any way I can be a beta tester for any upcoming products?
I am staying a Q Fan until next upgrade on my contract thru sprint
Sent from my Asanti C using xda app-developers app
I had about 7 "0" folders when I browsing my phone's files looking for a cache'd boot logo...it was like one of those russian dolls with a smaller and smaller doll inside and could not figure out what the heck was going on, lol. Ended up deleting all but the first parent and didn't seem to cause any issues....free'd up a good gig or two of internal storage space! Good to know now what the cause of this was as I was experimenting with a lot of different recoveries around the time this happened. Thanks^^
Argh! I came to this thread hoping for a nice, organized place to find all the links/downloads I needed to fix my girlfriends phone.
Now I have to read, AND continue my search for the files. (mild sarcasm)
Okay.... I know its late but still here are some boot logos for the moto x .
NOTE: This is not a flashable zip... u have to extract the desired logo.bin to the folder in which fastboot and adb are present...
Currently There are 2 logos....
NOTE: Your device must have a unlocked bootloader for this to work.
1. Connect Your Device To Your PC
2. Make sure you have android sdk or the minisdk installed
3. Extract the desired logo.bin to the platform-tools folder
4.(a) Hold shift and right click anywhere in the platform tools folder and select open command window here
OR
(b) Open command prompt and navigate to the platform-tools folder
5. Reboot to bootloader using this command:
Code:
adb reboot bootloader
6. After the device boots into the bootloader execute this command to flash the bootlogo
Code:
fastboot flash logo logo.bin
Done..... Any problems Ask Below..
They look good. Gonna install the joker when I get a chance tonight.
Sent from my XT1053 using XDA Premium 4 mobile app
Thanks
UPDATE 1
Okay... i will be making more logos and also im taking requests... Here is Mortal Combat.....
The instructions to install are the same
Enjoy...:good::good:
UPDATE 2
Update 2
Abstract moto x bootlogo
Note: All the updates will be included in the bootlogo.zip
How bout the joker face from dark knight, plain and simple similar to this possibly with the "why so serious" text
Sent from my XT1060 using XDA Free mobile app
Sure I'll upload it soon
Sent from my XT1052 using XDA Free mobile app
Not to burst your bubble... but there were already a few threads about changing your bootlogo... including instructions on how to make your own.
For LOCKED bootloader there is -> http://forum.xda-developers.com/moto-x/general/changing-moto-x-bootlogo-root-t2445150
For UNLOCKED bootloader there are...
http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
KidJoe said:
Not to burst your bubble... but there were already a few threads about changing your bootlogo...
Click to expand...
Click to collapse
But... How do you know he doesn't already know and just posting the info with his in case someone else doesn't know? Lol
Sent from my XT1053 using XDA Premium 4 mobile app
Nemosfate said:
But... How do you know he doesn't already know and just posting the info with his in case someone else doesn't know? Lol
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly. Im just making and posting bootlogos... If i wouldnt include instructions people wuld have to findd another guide which frm my experience is a pain in the ass ...
Done.
Jexx11 said:
How bout the joker face from dark knight, plain and simple similar to this possibly with the "why so serious" text
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry it took this much time but i had some problems... Here it is... Joker Bootlogo... The classic joker Enjoy!:laugh:
Here is a little demo I stumbled upon in the X
Also found these folx in the same directory.......
nipunx1999 said:
Exactly. Im just making and posting bootlogos... If i wouldnt include instructions people wuld have to findd another guide which frm my experience is a pain in the ass ...
Click to expand...
Click to collapse
This thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 , started a long time ago, was a repository of replacement LOGO.BIN files, and has instructions to make your own logo.bin and flash...
But either way is fine.
KidJoe said:
This thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 , started a long time ago, was a repository of replacement LOGO.BIN files, and has instructions to make your own logo.bin and flash...
But either way is fine.
Click to expand...
Click to collapse
Ur telling me that there r other forums n u make a new one today. Just WOW. *applauds*
http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
nipunx1999 said:
Ur telling me that there r other forums n u make a new one today. Just WOW. *applauds*
Click to expand...
Click to collapse
No, actually, I'm telling you there was already another thread with replacement LOGO.BIN files, with instructions on how to make. And if you used the link I posted to view that thread, you would have seen it was started originally In Aug 2013, and we added new info in June 2014 for the 4.4.x updates.
nipunx1999 said:
http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Click to expand...
Click to collapse
I think you need to look more closely at what thread your are quoting. ^^^ This thread of mine that I just made today, is repository of all the Boot Animations from the Moto Boot Services App (in flashable format), and since it may also be asked for, the LOGO.BIN's too (since moto boot services doesn't change the LOGO.BIN on unlocked bootloaders)
Its not the same any any other threads to date. It is not a repeat.
While yes, I've created LOGO.BIN's from the CLOGOs that Moto Boot Services pushed down, and included them in a ZIP a while ago. As noted in the thread, when I get time, I will change it and put just those from Moto Boot Services there.
HOWEVER, not all of the Boot Animations from the Moto Boot Service app have been posted before, even when you look at the separate threads that had been created when the boot animations had changed. And that is the point of that thread. The Boot Animations from Moto Boot Services.
In contrast this thread is a duplicate of at least two other threads (which I've provided links to) instructing users how to flash a custom logo.bin, containing ready made logo.bin's, but unlike the other two, this thread doesn't say how to make them.
Either way.,... carry on.. and have fun. C'ya
Sorry, this is going to come off bad after what I've already posted but after downloading the sample logo.bin's you've posted I have some questions about them.
1. How were they made?
2. Do they contain just the single graphic? Or do they contain the "M" graphic, 0-3% battery graphic, and this new graphic?
I ask because the MLOGO tool (See -> http://forum.xda-developers.com/moto-x/themes-apps/app-moto-x-g-boot-logo-command-line-tool-t2819494 which is another thread about creating and flashing custom LOGO.BIN files), errors on each of these when trying to list the included elements. And opening with a hex editor they don't have the normal header which would mean they are a single image graphic.
While not a big problem, having just a single image means that if the battery level is below 3%, and the phone is off and charging, the user will not see anything on the screen, making it seem like the phone is dead, until the battery reaches 4% or above.
I made them using the original logo.bin file and edited it using Photoshop and gimp....
Sent from my unknown using XDA Premium 4 mobile app
Is there currently a working solution to change boot logo/splash on the OnePlus 7 pro???
I have scoured the internet & XDA and haven't found anything on the subject besides a general guide for Snapdragon devices and SplashInjector. I used the directions on the general guide to extract (for op7pro we have all these) Splash, LOGO_a & LOGO_b and will attach files. However the OP of said thread hasn't been responding or continuing to make/find solutions. Thread can be found here https://forum.xda-developers.com/t/...en-for-snapdragon-devices-splash-img.3470473/. SplashInjector is a git bash program that runs on Linux and to a good extent Windows, created by EthanBanker2042, @makers_mark, boblagus but it only works for OnePlus devices up to the 5. I used it to mod the splash of my OnePlus 5 on Windows and it worked great. Find it here https://forum.xda-developers.com/t/tool-splashinjector-op5.3650374/post-73282055.
I was hoping to find a dev or someone with more knowledge/skills than myself who has or is willing to create a solution for modding the splash/boot logo on our OnePlus 7 Pro devices. I imagine it would be somewhat more complicated than on previous devices due to treble A/B structure. I found in /dev/block/bootdevice/by-name/ 3 related files: 'Splash', 'LOGO_a' & 'LOGO_b'. My guess is that LOGO_a & LOGO_b are the same, and are the actual splash image of the OnePlus logo in the center with "powered by Android" at the bottom and 'Splash' might be the bootloader unlocked screen, however I'm not totally sure. I used FX file explorer to view binary of the files and the 'Splash' was, as far as it would show (file too large to completely display), nothing. However, the LOGO_a/b files state "Splash" at the beginning and contain actual data beyond 0's.
If anyone has any relevant information I would be very grateful. I am ready and willing to set time aside to help/work on this as much as needed.
Thanks in advance
*My device that files were extracted from is a GM-1910
Attached is the 'Splash.img' extracted from /dev/block/bootdevice/by-name/Splash.
Aballamis said:
Is there currently a working solution to change boot logo/splash on the OnePlus 7 pro???
I have scoured the internet & XDA and haven't found anything on the subject besides a general guide for Snapdragon devices and SplashInjector. I used the directions on the general guide to extract (for op7pro we have all these) Splash, LOGO_a & LOGO_b and will attach files. However the OP of said thread hasn't been responding or continuing to make/find solutions. Thread can be found here https://forum.xda-developers.com/t/...en-for-snapdragon-devices-splash-img.3470473/. SplashInjector is a git bash program that runs on Linux and to a good extent Windows, created by EthanBanker2042, @makers_mark, boblagus but it only works for OnePlus devices up to the 5. I used it to mod the splash of my OnePlus 5 on Windows and it worked great. Find it here https://forum.xda-developers.com/t/tool-splashinjector-op5.3650374/post-73282055.
I was hoping to find a dev or someone with more knowledge/skills than myself who has or is willing to create a solution for modding the splash/boot logo on our OnePlus 7 Pro devices. I imagine it would be somewhat more complicated than on previous devices due to treble A/B structure. I found in /dev/block/bootdevice/by-name/ 3 related files: 'Splash', 'LOGO_a' & 'LOGO_b'. My guess is that LOGO_a & LOGO_b are the same, and are the actual splash image of the OnePlus logo in the center with "powered by Android" at the bottom and 'Splash' might be the bootloader unlocked screen, however I'm not totally sure. I used FX file explorer to view binary of the files and the 'Splash' was, as far as it would show (file too large to completely display), nothing. However, the LOGO_a/b files state "Splash" at the beginning and contain actual data beyond 0's.
If anyone has any relevant information I would be very grateful. I am ready and willing to set time aside to help/work on this as much as needed.
Thanks in advance
*My device that files were extracted from is a GM-1910
Click to expand...
Click to collapse
Try Boot Animation for Superuser from PlayStore, for me work.
VampireHeart said:
Try Boot Animation for Superuser from PlayStore, for me work.
Click to expand...
Click to collapse
Boot animation and Boot logo is different, you should ve read twice before suggesting this thing
thedeadfish59 said:
Boot animation and Boot logo is different, you should ve read twice before suggesting this thing
Click to expand...
Click to collapse
I misunderstood but you don't need to be so irritating.
VampireHeart said:
I misunderstood but you don't need to be so irritating.
Click to expand...
Click to collapse
Didn't meant to be irritating, my bad sorry. But its generally wise to get what's written right mate? No offense buddy
thedeadfish59 said:
Didn't meant to be irritating, my bad sorry. But its generally wise to get what's written right mate? No offense buddy
Click to expand...
Click to collapse
Thanks, no problem, have a nice day.
you need to extract the .img and put it through the explorer to the root of the system
did you found a solution,i have op6 trying to change my boot logo
bishoy ashraf said:
did you found a solution,i have op6 trying to change my boot logo
Click to expand...
Click to collapse
No, currently there is no known working method to decompile the "LOGO_a" & "LOGO_b" omg files. Sorry, hopefully someone will come along and add support to the aforementioned "SplashInjector" got bash utility, as I believe this would be the easiest method. Good luck!