THis is a very simple batch file to assist you in flashing a boot screen
it still uses the same files as before its just put together in one section for ease of use as you can see
thanks to xMemphisx for supplying the required files for this to work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.Extract BSF3000 and open the BSF300 Folder
2. Run CreateG1Splash.exe and choose your boot image (320 x 480 PNG for best results)
3. run the bootflash.bat and follow the on screen steps
* Reboot into fastboot
* IF you're on the older spl then u have 2 screens to flash so you're gonna follow step 3 and 4. and reboot
*If you're on the newest spl the you're just going to flash 1 screen by following step 2 and reboot
4. VIOLA!!! u have a new bootscreen with no copying and pasting
Original Boot Screen
http://www.mediafire.com/?wdmuuzhmmnw
BSF3000.zip
I don't get it. What is classified as the "special" SPL, and what is the "other" spl's? Create a list please .
I'm using Haykuro's Danger SPL...I assume that's "special"?
im assuming special is haykuros and other is any other spl
grr...I hate having a Mac! lol
Anyway someone could setup something like this for linux or Mac users. Pretty please.
Yes sorry for any confusion ....haykuros spl is the special spl
Where is it pulling mysplash.rgb565 from? Says mine cannot load it.
Edit: Fixed the problem. I placed the .bat file in my Android SDK Tools folder, intended to work next to ADB. Didn't know you could run the .bat from the extracted zip folder itself.
Problem: Haykuro's SPL only flashes the first screen, the T-Mobile G1 screen, correct?
lukekirstein said:
Where is it pulling mysplash.rgb565 from? Says mine cannot load it.
Click to expand...
Click to collapse
if u created ur own bootscreen it should be pulling it from the folder
Alright. Got everything to work. Might want to flash back to the original G1 screen, because having that first T-Mobile screen is crucial to me.
On a side note, a couple of apps and widgets broke upon rebooting. Some widgets wouldn't load, other apps lost data connections. Ran a fix_permissions, everything works fine now
Curious question, does anyone have the original "T-Mobile G1" boot screen?
lukekirstein said:
Alright. Got everything to work. Might want to flash back to the original G1 screen, because having that first T-Mobile screen is crucial to me.
On a side note, a couple of apps and widgets broke upon rebooting. Some widgets wouldn't load, other apps lost data connections. Ran a fix_permissions, everything works fine now
Curious question, does anyone have the original "T-Mobile G1" boot screen?
Click to expand...
Click to collapse
Theres a thread with them. You can check the bootscreen tutorial thread, its in there as well
lukekirstein said:
Alright. Got everything to work. Might want to flash back to the original G1 screen, because having that first T-Mobile screen is crucial to me.
On a side note, a couple of apps and widgets broke upon rebooting. Some widgets wouldn't load, other apps lost data connections. Ran a fix_permissions, everything works fine now
Curious question, does anyone have the original "T-Mobile G1" boot screen?
Click to expand...
Click to collapse
what build are u on?
original boot screen >>> http://www.mediafire.com/?wdmuuzhmmnw
dom2684 said:
what build are u on?
original boot screen >>> http://www.mediafire.com/?wdmuuzhmmnw
Click to expand...
Click to collapse
In my siggy
i love this its alot easier than b4 IMO
nice work dom. It was quite a bit easier this way. I noticed after flashing the danger spl that i could only change one boot screen. Anyone know why that is? Not super important since the first one only last a couple seconds anyways.
*BUMP YO need some feed back on this
Can this batch file also install a .gif splash screen? I'm wanting the HTC splash with the little android that peeks out.
uansari1 said:
Can this batch file also install a .gif splash screen? I'm wanting the HTC splash with the little android that peeks out.
Click to expand...
Click to collapse
no its only for the primary boot screen
added original boot screen to 1st post
I noticed after flashing the danger spl that i could only change one boot screen. Anyone know why that is?
Click to expand...
Click to collapse
"danger" SPL only has 1 boot screen to flash, there's a thread about it somewhere, think i read it in the old thread somewhere
note about the tool, VERY fast, VERY easy, even a n00b like me could do it. If you have "danger" SPL you will need updated USB drivers, but i'm sure you know that already
The script litterally is, put your image into the folder, run the bat, press 2 <enter> (for special SPL that is)and you're done, really couldn't be simpler if you tried
I'm glad everyone likes it
my adb work find, but for some reason this script stay at wating for device, any input?
Related
I have just got my "mytouch3g" and was wondering if there is a way to change the boot screen??? Step by step instructions would be nice...
theflash1011 said:
I have just got my "mytouch3g" and was wondering if there is a way to change the boot screen??? Step by step instructions would be nice...
Click to expand...
Click to collapse
1st step.... SEARCH
2nd step....READ
3rd step....READ
I assume you mean the initial splash screen that pops up when you startup the phone. I did this on my G1, which was used on AT&T until I just got a Rogers Magic yesterday.
w00t.
Information can be found here: (Dream forum)
http://forum.xda-developers.com/showpost.php?p=3010171&postcount=1
I've verified that it works, I now have a pretty bootsplash on my new Magic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
korndub said:
1st step.... SEARCH
2nd step....READ
3rd step....READ
Click to expand...
Click to collapse
These replies don't help anyone
MikLSP said:
These replies don't help anyone
Click to expand...
Click to collapse
It should. Tough luck if you can't figure it out from there.
I've been struggling with this for a few days and may give up due to the risk involved.
Basically, it all depends on what version of the device you have.
1. You need to root your phone.
2. Check this website: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking
It has detailed information on how to edit your boot screen.
Issues arise if you have a perfect SPL, like I do. (which is most likely what you bought) With a perfect SPL you will need to follow Ra's 30 - 40 steps to creating a Gold card (which might brick your phone and super complex) and then install an engineering SPL. After you've installed the busted SPL you can then use fastboot to push a new boot screen you've created using tools found is several other threads in this forum.
To do just about anything with the boot screen you'll need an extra non-scan disk SD card, RA's engineers SPL, the boot screen image converter created by JesusFreak (http://forum.xda-developers.com/showthread.php?t=467064) and some other stuff. I'd recommend doing some homework. MT3G is a super pain in the ass in comparison to the G1.
You might want to keep an eye on the thread I started yesterday... which is basically what you are asking... except I've done a lot of reading. (http://forum.xda-developers.com/showthread.php?t=568434)
http://ostebaronen.dk/?p=124 gives a great detailed instruction PLUS a load of splash screens!you dont have to make them just use his tut
i have made a couple of orange ones myself!
bonesy said:
http://ostebaronen.dk/?p=124 gives a great detailed instruction PLUS a load of splash screens!you dont have to make them just use his tut
i have made a couple of orange ones myself!
Click to expand...
Click to collapse
Yeah, that wont work for his American MT3G.
it should do its only flashing the splash screen, not the android screen
"fastboot flash splash1 mysplash.xxx"
its very simple, u can change the bootsplash on the mt3g, but first you have to change the spl, the one that comes on it already ends in 0006, you have to change it to 2005 the same one from the g1, after that u can change it the same way with the g1 thru fastboot flashing....thats how i did mine and a few of my frineds mt3g...good luck
Follow my walkthrough here to get root access and the correct SPL on a bone stock MyTouch 3G from t-mobile so you can fastboot: http://alldroid.org/viewtopic.php?f=96&t=76
Then follow this thread on how to create and flash your new boot screen through fastboot: http://forum.xda-developers.com/showthread.php?t=555114
If you only just got 5 posts I really recommend you to help other people first and search this forum.
brandenk said:
Follow my walkthrough here to get root access and the correct SPL on a bone stock MyTouch 3G from t-mobile so you can fastboot: http://alldroid.org/viewtopic.php?f=96&t=76
Click to expand...
Click to collapse
I was reading through and my question that I have is if I am already loaded with cyans lates 4.2.5 and all But I do not have the engineering SPL could I load it like it stated in your posted link from alldroid just like a basic update.zip and still be ok.
I didn't make the original work. I just modified the information so that it tailored the specs of the G2.
Code:
adb devices (optional, only to see if adb sees your phone)
adb remount
adb push bootanimation.zip /data/local
(if this doesn't work, try pushing to /system/media also)
Now to test if it worked type:
Code:
adb shell bootanimation
<press ctrl+c to quit>
Info on BIOS is for G2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Update* 01/03/11
All the updates are in! 800 MHz is made per request.
Added Gingerbread versions for those running 2.3!
Rename file to "bootanimation.zip", then follow instructions above.
Enjoy!
*Update* 02/28/11
Added CM6 and CM7 version for those using Flippy125's Kernel.
Okay...WE NOW HAVE SOUND!!
First off, thanks to mrdaviso for script and instructions from spiicytuna.
My apologies to amazinglarry311, credit goes to him/her for the enablesound script.
enablebootsound scripts can be found here:
Enable Sound Boot
Here's how I did it:
Flash zip file from recovery.
reboot
Place android_audio.mp3 on sdcard root (change name of android_audio.zip to android_audio.mp3)
adb shell(I am assuming you are root)
enablebootsound(mine wasn't already enabled)
newbootsound
You can also use this script to install bootanimation now. ( I still prefer the old way)
place bootanimation.zip on sdcard root
newbootanim
A "Thanks" will do.
Nice! I'll def. give this boot animation a shot! Thanks for sharing.
I like it but... on part1, youre missing several images causing a blank bootup at the end of the bios animation. you might wanna add some more in part1 to remedy that.
sino8r said:
I like it but... on part1, youre missing several images causing a blank bootup at the end of the bios animation. you might wanna add some more in part1 to remedy that.
Click to expand...
Click to collapse
I wasn't sure if it's part0 or part 1.
Do I have to divide the number of images in each folder evenly?
sino8r said:
I like it but... on part1, youre missing several images causing a blank bootup at the end of the bios animation. you might wanna add some more in part1 to remedy that.
Click to expand...
Click to collapse
I fixed it. I've replaced the attachment.
booting up my desire z takes roughly 3 seconds.
why wasting time with a 30 seconds boot image?
snudel said:
booting up my desire z takes roughly 3 seconds.
why wasting time with a 30 seconds boot image?
Click to expand...
Click to collapse
well if u want it take if not don't use i know i will try it
Could you change/make another version showing pershoot kernel speeds?
1.51Ghz?
Just wondering...
should it go to /data/local or /system/media?
does it matter?
Thanks it works!!!!!!!
Sent from my T-Mobile G2 using XDA App
looks great! I've been looking for something to snazzy to replace the generic g2 logo and have been too lazy to look into how to make my own
very nice
I installed it and the first bootup it froze on me at the android logo screen part. Second time it started hanging a little bit after where it froze before... then it went black screened and eventually showed my home screen. Weird...
Edit: tried it once more and it's frozen :/
I am such a nerd this totally made my day! Freaking sweet boot animation. I don't think I will ever change it. My G2 is running so fresh now. Good work yo
works great, and I like it! so nerdy! hahaha
snudel said:
booting up my desire z takes roughly 3 seconds.
why wasting time with a 30 seconds boot image?
Click to expand...
Click to collapse
That's not really booting though, that's a trick where it doesn't shut down, it just suspends and switches off. A proper boot takes a lot longer.
Can someone post screenshots of this?
Sent from my HTC Vision using XDA App
*Nevermind went to orig. Forum post and saw screenshots. Thank you!
snudel said:
booting up my desire z takes roughly 3 seconds.
why wasting time with a 30 seconds boot image?
Click to expand...
Click to collapse
The boot logo at the end only stays til booting is done.
dietotherhythm said:
I installed it and the first bootup it froze on me at the android logo screen part. Second time it started hanging a little bit after where it froze before... then it went black screened and eventually showed my home screen. Weird...
Edit: tried it once more and it's frozen :/
Click to expand...
Click to collapse
Trys pushing file to /system/media/
Busy at the moment. Will make one with pershoot's speed later...
xomikronx said:
Sent from my HTC Vision using XDA App
The boot logo at the end only stays til booting is done.
Click to expand...
Click to collapse
I think he was refering to hot reboot that the desire z does standard which isnt true rebooting. Its possible to perform one on the G2 via script or an app called Hot Reboot. While the phone is hot rebooting... it will skip parts when booting. So there is no real concern when adding a custom boot animation.
can anyone tell me why my htc desire is stuck at this screen when i put in the battery?
-- 1 minute later --
well, i can't post a pic since not allowed to link until after 8 posts
it looks like a boot screen with 3 android dudes on the bottom.
any ideas?
Your stuck at the bootloader. Means that there is no boot.img. You've done something to it. Just flash a rom and it'll be fine. Don't forget to wipe data.
ok, thats positive news so far
the things is, i think its water damage but not much water at all really. just a bit from snowing while skiing.
the power and volume buttons do not seem to respond AND the ohone turns on by itself when i insert the battery.
is it still just a case of 'flash a ROM'? or is there more?
oh, and here is the image..... finally,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You don't have root or a custom recovery, correct? You just want to go back to the stock Froyo?
I think if the power buttons don't work it may be a bit of a problem selecting options in that menu, since the power button works as "select" in that menu.
I think you could boot to recovery using command prompt, but I am not 100% sure about that.
Also, are you rooted? Do you have a custom recovery installed?
What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?
sonoftobit said:
What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?
Click to expand...
Click to collapse
--- confusion ensues ---
my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help
liquidmonkey said:
my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help
Click to expand...
Click to collapse
Do you have a note of which rom was installed in your device? Is it carrier locked? Branded?
Select the newest RUU that fits your phone & carrier from http://shipped-roms.com/shipped/Bravo/. Extract the ROM, rename to PB99IMG.zip, place in root dir of sd-card and reboot. Should do everything else automatically.
don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.
and i should add that i am sweden if that matters.
The file you download from shipped roms is an exe file. When you execute the file it will extract a couple of files to your harddrive. Among those is a file named ROM.zip. That's the one you're looking for.
When I extracted it the file was here C:\Users\*User Name*\AppData\Local\Temp\{722DC7D5-7B69-4EBC-B6FB-B63AE38C01DE}\{50F2F878-636A-496F-A7CB-544C067E0C4B}
The ROM on shipped ROMs are all the standard carriers version that are unmodified.
liquidmonkey said:
don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.
Click to expand...
Click to collapse
Yeah but there are different versions of 2.2 depending on carriers etc, thats why I was asking!
I *think* any of the ROMS here with RUU at the beginning & WWE in the filename should work. (I am not 100% sure about this, as I have not had an official rom installed for AGES).
You will then have to follow sonoftobit's instructions I think, don't ask me how to extract the ROM though, as I don't know how to do it!
PS sonoftobit - Ignore this liquidmonkey!
If you go to the CM7 nightly thread and go to the 2nd post, Kali has a script for enabling Apps2SD. That is what I am running, tried to use S2E but it screwed things up royally and I had to restore a Nandroid!
Yeah, I had the same problems with S2E. I'm using DarkTremor App2SD now which has worked flawlessly ever since (both Sense Froyo and CM7). Also there's A2SDGUI for DarkTremor now which makes it even better.
StuMcBill said:
PS sonoftobit - Ignore this liquidmonkey!
Click to expand...
Click to collapse
why on earth would you write that?
so check it out!!!
i have had the phone off for a few more days and then put in the battery and BANG, it started up after a little while.
problem was that my battery only lasted 10 seconds so i was not able to fully test things.
then i put the battery in again and i was back where i started, crappy boot screen.
is there something in the phone that keeps memory of the boot screen and then disapates after a day which would explain why it started today.... or?
Hey guys can someone help me with it?
http://pastebin.com/7q69qymd
just tried to port from explorer Aisa India ruu to wildfire s from dsixda's kitchen..
the splashscreen comes vibrates once and then againn it goes .. it comes vibrates and goes.. and so on. sort of a bootloop..
mhrsolanki2020 said:
Hey guys can someone help me with it?
http://pastebin.com/7q69qymd
just tried to port from explorer Aisa India ruu to wildfire s from dsixda's kitchen..
the splashscreen comes vibrates once and then againn it goes .. it comes vibrates and goes.. and so on. sort of a bootloop..
Click to expand...
Click to collapse
You sure its a bootloop?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MrTaco505 said:
You sure its a bootloop?
Click to expand...
Click to collapse
the ans might be a no cuz i can use the logcat as it only says -waiting for device-
when i connect my device and still that splash screen goes on rebooting
I don't know why you pasted over a thousand lines for this (ya, i browsed through all of it). I'm pretty sure you can't just throw any old ROM in the kitchen and get a bootable port.
But to be clear, that IS a bootloop (not sure how you got confused about that). And i believe (don't know) that the problem is your boot img. Did you happen to at least switch those out when you cooked?
Sent from my HTC_A510c
BigChillin said:
I don't know why you pasted over a thousand lines for this (ya, i browsed through all of it). I'm pretty sure you can't just throw any old ROM in the kitchen and get a bootable port.
But to be clear, that IS a bootloop (not sure how you got confused about that). And i believe (don't know) that the problem is your boot img. Did you happen to at least switch those out when you cooked?
Sent from my HTC_A510c
Click to expand...
Click to collapse
when i created the rom (the ported one of which recovery.log you read) it had said something to me like
Code:
the kitchen creates a flase boot.img sometimes for porting
Creating boot.img
and something like that i then thought of pasting the recovery log ..
then i tried again.. this time i extracted the rom.zip from htc explorer and extrcted into the folder n kept it in the place where i keep the boot.img and system.img (original_update folder) and when in kitchen i selected the whole folder while porting the second time.. then flashed the rom.. it again got the same splash screen and rebooted (i thought when you get a bootanimation and reboot then it is called boot loop and in my case its splash screen and boot loop so got a lil confused)
i updated the working folder of the second rom i made... i removed all system apps and pasted all system apps from the m1ndh4x8r's sense 3.5 rom.. (i am not using his rom as it is ported from chinese ruu and it has many FRIED RICE AND CHINEESE noodles in it (i mean chinese things like browser , contacts and all) ) and i have never ported a rom before and i dont know how to detect errors in recovery log.. even i read the whole thing but didnt understood it.. so posted.. thanks for reading it.. can you help me further in this?
BigChillin said:
I don't know why you pasted over a thousand lines for this (ya, i browsed through all of it). I'm pretty sure you can't just throw any old ROM in the kitchen and get a bootable port.
But to be clear, that IS a bootloop (not sure how you got confused about that). And i believe (don't know) that the problem is your boot img. Did you happen to at least switch those out when you cooked?
Sent from my HTC_A510c
Click to expand...
Click to collapse
changing the build.prop (copying a build.prop from a working rom of wildfire s and pasting in this working folder of sense3.5 rom overwriting the exiting one ) will be of ny help?
It sure couldn't hurt too much. And you could be right, i hadn't heard of just the HTC screen being called something else so I've just assumed it was all a bootloop. (my n00bness)
In general somewhere, a guy replaced just the boot.img and one other file (possibly the build.prop, I'd have to check) and got cm9 to boot for the marvelc. It had a bunch of other problems, but the point it's that in practice, it should work.
Sent from my HTC_A510c
BigChillin said:
It sure couldn't hurt too much. And you could be right, i hadn't heard of just the HTC screen being called something else so I've just assumed it was all a bootloop. (my n00bness)
In general somewhere, a guy replaced just the boot.img and one other file (possibly the build.prop, I'd have to check) and got cm9 to boot for the marvelc. It had a bunch of other problems, but the point it's that in practice, it should work.
Sent from my HTC_A510c
Click to expand...
Click to collapse
replaced the boot.IMG ??:O do we have to use boot image of the ROM which we wanna port or we have to use our boot.IMG ??
hey i tried using the boot.img of htc wildfire s for both the time (one when it asked to select a working rom for my device and second when it asked me to select a rom i wanna port {had replaced the boot.img with the one in one of my back up of rom}) and also pasted the build.prop
had no luck ..
now i pulled the recovery log for the ported rom.. and then i flashed a previously working rom and took its recovery log too .. now gonna examine both and see where is the fault and i guess i will gradually learn to read recovery log.. no other way to do rather than trail and error
BigChillin said:
It sure couldn't hurt too much. And you could be right, i hadn't heard of just the HTC screen being called something else so I've just assumed it was all a bootloop. (my n00bness)
In general somewhere, a guy replaced just the boot.img and one other file (possibly the build.prop, I'd have to check) and got cm9 to boot for the marvelc. It had a bunch of other problems, but the point it's that in practice, it should work.
Sent from my HTC_A510c
Click to expand...
Click to collapse
hey man can you do me a last favour? just read these both again.. (not the whole 1000 lines.. i have read it all so you dont have to need to do that again )
just see starting part untill the minzip starts and the line number 977 and 978 in The ported roms log
and line number 973 and 974 in recovery log of Stock rom
Hey guys, I've created 2 new bootanimations for the Google Pixel. One is dark and kind of blueish. The other is completely black. Your choice! Enjoy!
I also included the stock bootanimation for anyone that wants to revert or use on another device.
Instructions: (same as forever)
1. Download bootanimation.zip of your choice, into SD Card.
2. Move zip to /system/media/ and overwrite existing bootanimation.zip
3. Change permissions for the .zip file to 0644 (rw- r-- r--)
Optional 4. Reboot
Enjoy on your next reboot.
Download Black
Download Darkish
Download Pixel STOCK
Download Pixel XL STOCK
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did you make this when this exists?
First, I was bored. Second, this actually applies the original/stock Google format of the images. Third, smaller filesize . Fourth, because I can.
P.S No I cannot change the unlocked screen because it's buried somewhere in the bootloader which first needs extracting then repacking, and it's certainly not worth the risk for me to try and get that. If you know then that's great!
P.P.S If you want to make this for Pixel XL (I don't have this phone so I didn't bother), replace the images in XL zip with the ones in the Dark/Black zip I provided (the pictures might come out weird/smaller or just blurry). They are different resolution, that's why I didn't bother to do it... Photoshop Action script didn't work as planned on XL because the image actually touches the edge, so it'd be manually going through ~300 images to touch up missed fills, lol nothx.
I have just installed the black version: very nice, thank you.
F.
i also just installed the darkish one with substratum dark theme
If we can only get rid of that boot image!
Should the Google screen be black as well or just the 4 dots screen? The Google screen is still white for me.
airmaxx23 said:
Should the Google screen be black as well or just the 4 dots screen? The Google screen is still white for me.
Click to expand...
Click to collapse
"P.S No I cannot change the unlocked screen because it's buried somewhere in the bootloader which first needs extracting then repacking, and it's certainly not worth the risk for me to try and get that. If you know then that's great!"
In the OP....
JAYNO20 said:
"P.S No I cannot change the unlocked screen because it's buried somewhere in the bootloader which first needs extracting then repacking, and it's certainly not worth the risk for me to try and get that. If you know then that's great!"
In the OP....
Click to expand...
Click to collapse
The unlocked screen he's referring is the one when you first boot up and it says "your device software can't be checked for corruption, please lock your bootloader". The pics in the OP show the Google screen as black and mine is still white.
airmaxx23 said:
The unlocked screen he's referring is the one when you first boot up and it says "your device software can't be checked for corruption, please lock your bootloader". The pics in the OP show the Google screen as black and mine is still white.
Click to expand...
Click to collapse
Touché.
Now I am curious because mine is still white, too. Thought that's what he was referring to...
I can't get the new boot animation to work. I named it the same as the original and left the original in the directory but added "stock" to the name. What am I doing wrong? I keep getting the default boot logo. Permissions appear to be correct as well.
Thanks!
airmaxx23 said:
The unlocked screen he's referring is the one when you first boot up and it says "your device software can't be checked for corruption, please lock your bootloader". The pics in the OP show the Google screen as black and mine is still white.
Click to expand...
Click to collapse
Sorry for the confusion, I should've been more specific. It's the both the screen you are talking about AND the Google screen with the unlocked icon on the bottom. Both are separate from the actual boot animation.
ej_424 said:
I can't get the new boot animation to work. I named it the same as the original and left the original in the directory but added "stock" to the name. What am I doing wrong? I keep getting the default boot logo. Permissions appear to be correct as well.
Thanks!
Click to expand...
Click to collapse
That's strange, what program did you use to change the permissions? I used ES File Explorer. You should move your stock .zip into another folder too, maybe /sdcard/Downloads ?
OK it's working. Is there anyway to change the initial white screen with the G logo showing your phone is unlocked prior to the boot animation.
グリッチ said:
Sorry for the confusion, I should've been more specific. It's the both the screen you are talking about AND the Google screen with the unlocked icon on the bottom. Both are separate from the actual boot animation.
Click to expand...
Click to collapse
Thank you for the clarification.
Looks great but small on xl
Great job グリッチ !
Since we can't change the white 'Google' lock screen, yet, how about making it fade from white to black/darkish in part0?
It might make the white to black/darkish change a little less dramatic.
Just a thought
Awesome this is exactly what I was looking for. Too bad we're stuck with the white Google unlock screen
This is fantastic! Thank you.
Sent from my Pixel using XDA-Developers mobile app
I can't download the zips. They show up in some weird GDrive format and I can't save it. Anyone else seeing this?
Thanks!
Sent from my Pixel using Tapatalk
pilotgav said:
I can't download the zips. They show up in some weird GDrive format and I can't save it. Anyone else seeing this?
Thanks!
Click to expand...
Click to collapse
I've dealt with that when trying to download from gdrive via mobile. Have you tried downloading on a pc?
For whatever reason I am unable to set permissions for the zip once I've moved it to /system/media. Help?
crossen0 said:
For whatever reason I am unable to set permissions for the zip once I've moved it to /system/media. Help?
Click to expand...
Click to collapse
U rename it to just bootanimation?