Related
What's the directory/name of the splash image (not boot animation, b4 that)? Is it possible to just use es file explorer and replace that file to change splashes?
Sent from my PG86100 using XDA App
Eat it iPhone said:
What's the directory/name of the splash image (not boot animation, b4 that)? Is it possible to just use es file explorer and replace that file to change splashes?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
it isnt in a directory. and no you cant change it with file explorer. to change it you must use fastboot
t3project said:
it isnt in a directory. and no you cant change it with file explorer. to change it you must use fastboot
Click to expand...
Click to collapse
Does that mean renaming it to PC86IMG or whatever and flashing via hboot?
Eat it iPhone said:
Does that mean renaming it to PC86IMG or whatever and flashing via hboot?
Click to expand...
Click to collapse
Yes. That is the only way to do it. And it will stay that image no matter what rom/kernel you flash until you change it thru bootloader again.
Sent from my PG86100 using XDA Premium App
jayharper08 said:
Yes. That is the only way to do it. And it will stay that image no matter what rom/kernel you flash until you change it thru bootloader again.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Cool got it thx guys
Eat it iPhone said:
What's the directory/name of the splash image (not boot animation, b4 that)? Is it possible to just use es file explorer and replace that file to change splashes?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
to more directly answer this question, the splash image is located in a special portion of internal memory. it is not directly accessible from normal android mode or from recovery mode, at least as far as anybody as found.
the only known method of access to this restricted portion of dedicated internal memory which holds the splash image is thru fastboot mode and the fastboot binary.
on other older devices, like the samsung moment, the splash image was/is stored on internal memory in a dedicated partition, but it was write accessible from android mode and recovery mode. this made it much easier to modify and change which facilitated the ability for an android app, Flash Image GUI, I created to help thru this process.
unfortunately there haven't been anyways found yet to access the splash image on the evo 3d other than thru fastboot. i do think it would be great if there was a way found one day!
hope that helps add some clarity!
is it pC86img or pG86img? Every thread i review seems to have something different.
Also, I can confirm paste new hTC_bootanimation.zip over the original doesnt work. I did a NAND and tried it when i made my boot animation (death of megatron/birth of galvatron FTW) and now it displays the HTC logo but just the initial still frame.
Why are so many things you flash or load through bootloader named PG/PC86IMG lol. I've always been hesitant on account of that. Does bootloader look inside the zip and place it in the appropriate slot based on name or something?
Thanks!
Skyphos said:
is it pC86img or pG86img?
Click to expand...
Click to collapse
PG86IMG.zip
Skyphos said:
Why are so many things you flash or load through bootloader named PG/PC86IMG lol. I've always been hesitant on account of that. Does bootloader look inside the zip and place it in the appropriate slot based on name or something?
Thanks!
Click to expand...
Click to collapse
Short answer: Yes. The bootloader looks for specific file names inside of the .zip file to know which partition to flash them too.
Longer answer: HTC designed the bootloader/fastboot/radio to have the most write access to the internal partitions. Recovery and normal android mode also have write access (unlocked bootloader, custom recovery needed, etc) but the bootloader/radio/fastboot have the most access.
Since the bootloader/radio/fastboot have the most access to the internal partitions, it is sometimes regarded as the best way to flash certain partitions of the phone and hence why there are so many different .zip files available!
Hope that helps!
@JoeyKrim:
Thanks. I was familiar with PG86IMG and its options and assumed PC was just a typo. I only seen PC on splash screen how to posts and assumed it was wrong...or i misunderstood since everything flashed through hboot seems to be named PG86IMG (i think even the 4G was that way..been a while). I'm trying to learn more with this phone so I've been reading up a lot. Many smart people on this forum so it only makes sense. I like to know as much as I can about what is really going on behind the scenes before I take any action...just seems logical. Trying to graduate from a mere flash-a-holic =-)
So the take away here is that anything flashed via fastboot/hboot is PG86IMG.zip and hboot/fastboot is smart enough to look at the folder structure within the zip and fine the appropriate partition to write to without user intervention. Good to know. I've done many things with my phone but I usually tried to leave hboot/fastboot alone due to my lack of understanding.
Sidenote: I love your projects. Thanks for all the hard work
Skyphos said:
@JoeyKrim:
Thanks. I was familiar with PG86IMG and its options and assumed PC was just a typo. I only seen PC on splash screen how to posts and assumed it was wrong...or i misunderstood since everything flashed through hboot seems to be named PG86IMG (i think even the 4G was that way..been a while).
Sidenote: I love your projects. Thanks for all the hard work
Click to expand...
Click to collapse
I think the EVO bootloader used files named PC36IMG.zip. It is up to HTC. They can program the bootloader to use files named whatever they want.
the way to determine the file name the bootloader is searching for: when first booting into the bootloader it will print out on the screen (sometimes quickly) the file names it is searching for. these names will be the correct names as they are hard coded into the bootloader and very rarely change.
appreciate the support and hope the above helps provide more detail! good luck on your progression and feel free to ask questions as they come!
@Joey: Thanks again for the insight man!
@OP: Sorry for taking the thread into a little tangent. Hopfully it helped provide more detail for some of those looking deeper into the process.
joeykrim said:
I think the EVO bootloader used files named PC36IMG.zip. It is up to HTC. They can program the bootloader to use files named whatever they want.
the way to determine the file name the bootloader is searching for: when first booting into the bootloader it will print out on the screen (sometimes quickly) the file names it is searching for. these names will be the correct names as they are hard coded into the bootloader and very rarely change.
appreciate the support and hope the above helps provide more detail! good luck on your progression and feel free to ask questions as they come!
Click to expand...
Click to collapse
will the PG86IMG.zip deal to replace Splash Image Work on an HBOOT 1.5 Evo 3D S-ON. figured better ask to avoid a brick. Thanks for your help.
grindnmosh said:
will the PG86IMG.zip deal to replace Splash Image Work on an HBOOT 1.5 Evo 3D S-ON. figured better ask to avoid a brick. Thanks for your help.
Click to expand...
Click to collapse
no, splash can't be overwritten on hboot 1.5 sadly, and you wouldn't brick if you flashed, it just wouldn't apply the image.
il Duce said:
no, splash can't be overwritten on hboot 1.5 sadly, and you wouldn't brick if you flashed, it just wouldn't apply the image.
Click to expand...
Click to collapse
Maybe soff will come soon now that GSM e3d got hboot downgrade and soff then problem solved splash for all =-)
^by the way...
all of this, one of the reasons why i am not a flashoholic when it comes to the splash screen. if something goes wrong, you get a bad download, etc., you can brick the device. i don't justify the risk for an image that simply appears for merely 3 or 4 seconds at boot up.
Please delete, obsolete
its aliveee... alive i tell u!! amaze is alive
Sent from my Sensation using xda premium
If I'm tmo then no s-off required?
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
eggydrums said:
If I'm tmo then no s-off required?
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
The OP said S-OFF required in big bold and red letters.
---------- Post added at 08:58 AM ---------- Previous post was at 08:52 AM ----------
Snargaflab said:
You need S-OFF to flash this. This zip is flashed through HBOOT. Do not flash it in recovery. I assume no responsibility for any damage done by using this file.
It will work for any HTC Amaze on any carrier as long as you have S-OFF and SuperCID (check the stickies for instructions on how to get these things). I have removed the HBOOT and Recovery from the leaked ICS Rom football posted. That is the only modification to this rom, otherwise it is completely stock and contains all other parts of the update. I think it is a better alternative for anyone with S-OFF because they don't have to reflash recovery and HBOOT after flashing.
http://www.4shared.com/zip/CP5FKMHu/PH85IMG_RUBY_ICS_TMOUS_2145311.html
You have to register for this but it's super quick and easy. It's the best site I know of. If you know of a better place to upload I'll upload it there, I can upload this file in about 3 minutes on my connection. I will not use Filefactory or Dropbox.
Click to expand...
Click to collapse
What about http://goo.im/?
Yeah I know but since this is for tmo why do I need.s-off I'm tmo
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
eggydrums said:
Yeah I know but since this is for tmo why do I need.s-off I'm tmo
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Ok I see what you're saying.
I THINK you do need S-OFF since HBOOT & Recovery have been removed, but I may be wrong about that....
S-OFF is fairly painless, it's all about timing.
I'm installing this one and got an error when it try to install the nfc it said fail "ERROR: NFC FW file! =106", did anyone else get this?
fullmetal2k said:
I'm installing this one and got an error when it try to install the nfc it said fail "ERROR: NFC FW file! =106", did anyone else get this?
Click to expand...
Click to collapse
are you SuperCID?
is a tmobile stock with s-off locked so didn't think I needed it
but I already install the other one anyways thanks for the help
S-OFF/SuperCID/ENGHBOOT on a Wind Amaze here, get a Fail-PU (106) on the NFC file mentioned also, just FYI
*See Below*
Forgot to mention that the new HBOOT is necessary to flash the nfc update, as far as I can tell the juopunutbear HBOOT and the ENG HBOOT do not understand it, which is why it reboots after installing the new bootloader and before flashing nfc. nfc seems to work fine without it. Will add to original post. Also gonna repost with it ripped out as well so it doesn't throw an error, even though it doesn't matter.
Snargaflab said:
Forgot to mention that the new HBOOT is necessary to flash the nfc update, as far as I can tell the juopunutbear HBOOT and the ENG HBOOT do not understand it, which is why it reboots after installing the new bootloader and before flashing nfc. nfc seems to work fine without it. Will add to original post.
Click to expand...
Click to collapse
Champion mate, thankyou
Can't confirm NFC as yet, but even with a 'partition error' after flashing on the ENG HBOOT, the ROM functions perfectly. You can root just by flashing the usual SU.zip.
Thanks for the good work!
Isnt SuperSID just for if you are on another carrier? IE: If I have a T-Mobile Amaze all I need is S-Off?
Since this is basically a stock ROM, I assume that everything works fine with it?
EDIT: I always get confused too; hboot is the same thing as the stock bootloader right? Hold power + volume down?
porkchopexpress said:
Isnt SuperSID just for if you are on another carrier? IE: If I have a T-Mobile Amaze all I need is S-Off?
Since this is basically a stock ROM, I assume that everything works fine with it?
EDIT: I always get confused too; hboot is the same thing as the stock bootloader right? Hold power + volume down?
Click to expand...
Click to collapse
You shouldn't need SuperCID on the T-Mobile one really, but if you run into issues it doesn't hurt to have it on there. Plus if Wind get 4.0.4 with Sense 4.0, you won't have to be jelly
HBOOT is the white screen, so yeah the stock bootloader. An ENG (Engineering) one unlocks more and allows you to send a wider variety of commands
juzz86 said:
You shouldn't need SuperCID on the T-Mobile one really, but if you run into issues it doesn't hurt to have it on there. Plus if Wind get 4.0.4 with Sense 4.0, you won't have to be jelly
HBOOT is the white screen, so yeah the stock bootloader. An ENG (Engineering) one unlocks more and allows you to send a wider variety of commands
Click to expand...
Click to collapse
Even though its not needed to do this, just to satisfy my own personal sense of curiosity, how do you get to an ENG boot screen?
Edit: I assume we are still renaming this ph85img.zip as you would with the first ROM that leaked?
You don't need SuperCID if your on T-Mobile
You don't need S-OFF to flash this
You could flash this on S-ON.
Thanks worked for me, Still have the old HBOOT and CW Recovery and ICS!
Adjust said:
You don't need SuperCID if your on T-Mobile
You don't need S-OFF to flash this
You could flash this on S-ON.
Click to expand...
Click to collapse
I'm not 100% but since I have modified the file (presumably breaking it's signature) I do not believe it will flash with S-ON. None of the files inside are modified, some are just removed, but the file itself is modified by those removals. As far as I know if even one byte of this file is changed it will not flash with S-ON. If someone would be willing to test with S-ON then I will update my post if necessary, I have no way to test personally. I do not expect it to work but it is definitely a possibility. If it does work, it will only work a T-Mobile Amaze. If it will not work, it will not damage your phone. It will fail a signature check before it installs anything. If it does not fail that signature check then the entire thing will flash as it is verified in it's entirety at the beginning of the process.
juzz86 said:
Champion mate, thankyou
Can't confirm NFC as yet, but even with a 'partition error' after flashing on the ENG HBOOT, the ROM functions perfectly. You can root just by flashing the usual SU.zip.
Thanks for the good work!
Click to expand...
Click to collapse
The reason that it says partition error is because nfc flashes to a partition and it fails. This is why it still works fine even with such a seemingly menacing error. I have ripped it out until I can figure out what I talk about in my first post. No one should receive any error now.
All right guys, I have s-on with unlocked bootloader, on tmobile, would like to test but I don't wanna risk my phone
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
Well, here's the situation, I have a rooted rezound, it works on stock rom but everytime I try to install a custom rom I end up stuck at bootscreen. I have S-On. I read something about the PH98IMG file but I've only used this file to chage radios on previous phones.
I tried these ROMs: - NeWts-OnE-XxX-S4-RC3-Signed-.zip - PKMN_VIGOR_VENASAUR_3.2.0_51412.zip
- Rezound-Pure-GMS-Sense3.6-aroma-v1.1.zip
- " " " " " -v1.0.zip
I have a backup made so if anything I can go back to stock, also a reason why I'm doing this other than having complete control over my phone is that I'm in Canada and I'm using a Canadian SIM card, I can change the network mode by going to #*#*4636*#*#, it allows me to talk and receive texts but it doesn't let me send texts. Somebody here called Joelz I think developed a GMSFix.zip file that fixes that little issue and I'm trying to find a ROM that works with it. I anybody knows about this or can point me in the right direction I would really appretiate it.
Thanks, Kevin
If you're s-on then you have to flash the boot.img seperate in the bootloader and that's the ph98img file.
Sent From My HTC Rezound
big_mike_2k6 said:
If you're s-on then you have to flash the boot.img seperate in the bootloader and that's the ph98img file.
Sent From My HTC Rezound
Click to expand...
Click to collapse
Thanks, makes sense, however, I put the PH98IMG on the root of my SD Card and when bootloader looks for it it just skips it like if it wasn't there. I'm restoring to stock now because I need my phone operational. I'll give it a try later.
Make sure its not a zip file within a zip or named ph98img.zip.zip
Sent From My HTC Rezound
big_mike_2k6 said:
Make sure its not a zip file within a zip or named ph98img.zip.zip
Sent From My HTC Rezound
Click to expand...
Click to collapse
I got it working, I got the PH98IMG file from Scott's ROM and flashed one of his ROMs for testing and it worked perfectly, and then flashed ViperRez since I wanted to get the sms fix and it's now working like a charm, now I just have to work on getting the internet working but that's really not a big deal, either way thanks for your help
Hi, what is about S-OFF for our device?
Anyone have S-OFF?, As he did? Thanks
For S-Off visit here:
http://forum.xda-developers.com/showthread.php?t=2847983
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
That's incorrect information. There is nothing about s-off in that thread and it doesn't exist yet for our phone. That thread is about system write protection, which is something entirely different.
My bad, copied the wrong post
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
I wish we had s-off, it'd make life easier.
Would have been great to s-off with sunshine but i guess our device is not supported
Someone working on s-off for our device?
Jcase and beaups are working on Sunshine S-off version 3.0, which will most likely support our device. It isn't out yet though, but should be soon. Whatever you do, DO NOT post in the sunshine thread asking anything about it.
$ 25 is a lot for a 610 Thanks for reply
Any advantages now that we can s-off with sunshine?
You can remove that ugly htc red text splash screen for starters
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Having s-off is news to me. @ClearD, did you purchase this? If so how did you implement it? I went to what I think is the thread but didn't see any notice of how to buy it...
Nevermind. Found it here. And the list confirms our phone. I don't think I'll be buying it because I'm not sure what else I can do that I'm not already doing. Good to know its there though.
http://www.androidpolice.com/2015/03/20/sunshine-3-0-released-with-ability-to-unlock-and-s-off-many-motorola-and-almost-all-htc-handsets/
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Went and removed red text and added a new splash
With it, you can also change the radio. And bootloader I think. And pretty much anything.
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
KLit75 said:
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Click to expand...
Click to collapse
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
phatmanxxl said:
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
Click to expand...
Click to collapse
And then when you get the update, you unlock again and re root. Then use titanium backup to restore your apps. It's that easy.
ClearD said:
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
***I actually misspoke there...what I meant was the current version of sunshine wasn't working on the latest firmware (not our phone I don't think) and they were going to release a new version shortly.
That fastboot command you gave me...do I need to put a specific splash img in my fast boot folder or does just typing that in fast boot get it done?
Click to expand...
Click to collapse
You have to have a specific splash screen. So, someone with a stock one can pull theirs hopefully and we can reflash that.
Red text Removed from aboot for our Sprint M9 Firmware version 1.32.651.30, 2.6.651.11 & 2.11.651.19 & 3.41.651.4
I have made a Modified Hboot(aboot) for the Sprint M9 that removes the annoying red text after Unlocking bootloader.
This is only for the Sprint M9 Firmware 1.32.651.30, 2.6.651.11 & 2.11.651.19 & 3.41.651.4Thanks to @OMJ for Firmware from which I used aboot image
YOU MUST BE S-OFF TO FLASH THIS!!!
Download
Sprint M9 Red Text Removed Firmware 1.32.651.30
Sprint M9 Red Text Removed Firmware 2.6.651.11
Sprint M9 Red Text Removed Firmware 2.11.651.19
Sprint M9 Red Text Removed Firmware 3.41.651.4
Instructions:
1. Download attached zip
2. Reboot to bootloader
3. reboot to download mode
4. type fastboot devices (Make sure your device is displayed)
5. type fastboot flash zip Sprint_M9_Red_Text_Removed.zip
6. After flash is done, you may need to reflash again(I did, said failed flush image)
7. Phone reboots, leave command prompt open type "fastboot reboot", place phone back in download mode
8. type fastboot flash zip Sprint_M9_Red_Text_Removed.zip again (should receive [email protected])
9. type fastboot reboot
10. Enjoy no more red text!
Thanks to
@herwegan for guide to edit aboot
Oh yeah, I am not responsible if you break, brick, didn't follow instructions, or can't read. Flash at your own Risk!
Reserved
Sweet, thanks bro!
Sent from my 0PJA2 using XDA Premium 4 mobile app
Thank you! Been waiting for this. I was gonna try and modify the hboot myself but I would be pissed if I bricked the phone. I hate the red text.
So I want to flash a custom splash as well from here however the android-info.txt if for the international version. File type should be the same but I didn't wanna take a chance doing it wrong for this phone. As long as the file format is correct and the android-info.txt is correct is should be fine?
Sim-X said:
Thank you! Been waiting for this. I was gonna try and modify the hboot myself but I would be pissed if I bricked the phone. I hate the red text.
So I want to flash a custom splash as well from here however the android-info.txt if for the international version. File type should be the same but I didn't wanna take a chance doing it wrong for this phone. As long as the file format is correct and the android-info.txt is correct is should be fine?
Click to expand...
Click to collapse
you can always take the android-info.txt file from the firmware zip. i used it from the red text removed zip.
Haven't really checked it out yet, so im not sure what img is the Splash on the M9.
schmeggy929 said:
you can always take the android-info.txt file from the firmware zip. i used it from the red text removed zip.
Click to expand...
Click to collapse
I should have thought of that. Awesome! Gonna flash hboot and splash as soon as my phone is done charging.
Threw you & OMJ a couple of small donations. Thanks for all you guys do.
Sim-X said:
I should have thought of that. Awesome! Gonna flash hboot and splash as soon as my phone is done charging.
Threw you & OMJ a couple of small donations. Thanks for all you guys do.
Click to expand...
Click to collapse
Thanks buddy first donation in a long time!
schmeggy929 said:
Thanks buddy first donation in a long time!
Click to expand...
Click to collapse
not a problem! Red Text is now gone and I got my breaking bad splash screen back. When I flashed it the 1st time it failed like you said, what's odd phone rebooted immediately. Just left command prompt open, did an adb reboot and flashed again once back into download mode took right away. Figure I let people know incase it does the same thing.
Sim-X said:
not a problem! Red Text is now gone and I got my breaking bad splash screen back. When I flashed it the 1st time it failed like you said, what's odd phone rebooted immediately. Just left command prompt open, did an adb reboot and flashed again once back into download mode took right away. Figure I let people know incase it does the same thing.
Click to expand...
Click to collapse
Yeah did the same thing to me, almost like flash the ADSP.img on the M8, had to flash it twice.
Glad it worked!
Sim-X said:
not a problem! Red Text is now gone and I got my breaking bad splash screen back. When I flashed it the 1st time it failed like you said, what's odd phone rebooted immediately. Just left command prompt open, did an adb reboot and flashed again once back into download mode took right away. Figure I let people know incase it does the same thing.
Click to expand...
Click to collapse
Ok what steps did you take to flash the breaking bad splash? Could you share please?
Sent from my HTCONE using Tapatalk
motoelliot said:
Ok what steps did you take to flash the breaking bad splash? Could you share please?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
@SoLdieR9312 made some custom splashes that are compatible with the M9. I'm not sure if they changed the file format from the M8 or not here. Remove the .txt file in the zip and replace it with the one schmeggy929 posted here . Make sure both the new .txt file and splash screen are in the same zip. Then just flash it per the instructions posted on soldiers splash screen thread. Worked perfect, same one I was using on my M8. His .android info file was for the international version so you just have to update that to work for the Sprint version. File format is the exact same on both variants for the splash screen so you don't have to mess with editing the splash screen file.
Thanks. Worked perfectly! Now we just need more splashes to choose from...
Sent from my 0PJA2 using Tapatalk
motoelliot said:
Thanks. Worked perfectly! Now we just need more splashes to choose from...
Sent from my 0PJA2 using Tapatalk
Click to expand...
Click to collapse
Yea I have been rocking a breaking bad one since m7. Since the screen resolution is the same I don't see why the m7 & m8 splashes that are out there wouldn't work. If htc changed the format but could be as simple as just renaming the file and updating the Android info file. Although I'm not a dev so I don't know if that would work or not.
Sim-X said:
Yea I have been rocking a breaking bad one since m7. Since the screen resolution is the same I don't see why the m7 & m8 splashes that are out there wouldn't work. If htc changed the format but could be as simple as just renaming the file and updating the Android info file. Although I'm not a dev so I don't know if that would work or not.
Click to expand...
Click to collapse
I'll look at some m8 files, but I think the m7 ones won't work without changing the resolution. Maybe it's not but how do you make a nb0 file? Or can we just
fastboot flash splash1 splash.img
Sent from my 0PJA2 using Tapatalk
motoelliot said:
I'll look at some m8 files, but I think the m7 ones won't work without changing the resolution. Maybe it's not but how do you make a nb0 file? Or can we just
fastboot flash splash1 splash.img
Sent from my 0PJA2 using Tapatalk
Click to expand...
Click to collapse
Now that I got my breaking bad splash I'm good for the time being. I have seen some stuff about making splash screens before around XDA if you poke around.
motoelliot said:
I'll look at some m8 files, but I think the m7 ones won't work without changing the resolution. Maybe it's not but how do you make a nb0 file? Or can we just
fastboot flash splash1 splash.img
Sent from my 0PJA2 using Tapatalk
Click to expand...
Click to collapse
once you convert Splash1.img to Splash1.nb0 and using M9 android-info.txt you are good to go. Sim said look around for Splash flasher 1.0.
Take your image and put it in the right folder type number for convert png, Jpg or bmp to img and rename to Splash1.nb0.
I just made this one
schmeggy929 said:
once you convert Splash1.img to Splash1.nb0 and using M9 android-info.txt you are good to go. Sim said look around for Splash flasher 1.0.
Take your image and put it in the right folder type number for convert png, Jpg or bmp to img and rename to Splash1.nb0.
Click to expand...
Click to collapse
Linky?
Sent from my HTCONE using Tapatalk
motoelliot said:
Linky?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2784348
schmeggy929 said:
http://forum.xda-developers.com/showthread.php?t=2784348
Click to expand...
Click to collapse
I'll see about updating the splash flasher so it will flash the splash also beings the OG was made for the M7