Develop Bugs

Custom HTC/Nexus One Boot Animation

TESTED ONLY ON AN ROGERS HTC MAGIC (32A) RUNNING CURSORDROID'S LATEST SENSE UI ROM.
NOT TESTED ON ANY OTHER ROM OR PHONE.
I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU CAUSE TO YOUR PHONE.
ALWAYS MAKE A NANDROID BACKUP IN CASE ANYTHING GOES WRONG
Preview:
{
"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"
}
Downloads:
Custom HTC/Nexus One Boot Animation with sound
bootloop_w_sound.zip
Custom HTC/Nexus One Boot Animation without sound
bootloop_wo_sound.zip
To backup:
Code:
Go to command prompt type:
adb pull /data/media/bootscreen/ C:
Instead of C: you can put any directory you want.
To install:
Code:
1. Unpack the ZIP of your choice (I recommend to C:/Boot/)
2. Assuming you unzipped it in C:/Boot Go in command and type:
adb push C:/Boot/boot.gif /data/media/bootscreen/
adb push C:/Boot/bootloop.gif /data/media/bootscreen/
adb push C:/Boot/boot_animation.xml /data/media/bootscreen/
adb push C:/Boot/boot.mp3 /data/media/bootscreen/
Note: Anyone interested in taking the HTC Quietly Brilliant section of the boot animation for your own boot animation you're free to extract it. Just mention me in the credits please. It took me a retarded amount of time to merge 2 gifs together.

Nice!
This will definitaly be my new bootscreen
Thank you for sharing!

Thanks for this, installed as my new boot.

Testet on Cyanogen 4.2.15.1: no function

It's nice, but the nexus animation stutters, unlike on actual eclair roms (where it's implemented in a different way). Probably nothing to be done about that.

drbobb said:
It's nice, but the nexus animation stutters, unlike on actual eclair roms (where it's implemented in a different way). Probably nothing to be done about that.
Click to expand...
Click to collapse
I could try adjusting the delay time per frame, but that would just artificially make it seem like it's going smoother.
Also, I think it might have to do with the fact I made the animations a full 320x480. I'll try to reduce the sizes.
I'll try some modifications out and re-post an update if they works well.
westgds said:
Testet on Cyanogen 4.2.15.1: no function
Click to expand...
Click to collapse
I'll check the implementations on 1.6 ROMs and higher and see if I can come up with something.
I'd need someone to test it though.

Could you please confirm how to instal on the Stock rom wich is rooted from europe with edition : 3.05.401.3 because i cannot detect with adb. Do you know what might be the issue? Thank you

Taknarosh said:
I'll check the implementations on 1.6 ROMs and higher and see if I can come up with something.
I'd need someone to test it though.
Click to expand...
Click to collapse
I think eclair roms would work, but Incase you didn't know.. (I think you know but I guess ill try and explain anyway. I don't even know why the other member tried this because the files don't even go in the same folders as the bootscreen files do for 1.6 lol. The folder doesn't even exist and they use completely different image files. Some people, good lord. I bet if you put FLASH THIS UNKNOWN RADIO, someone would do it. Test it one day! haha)
1.6 uses two images, i think it's a png image. One sits there, and the other scrolls through. You could definitely make the HTC shine (pretty easy if you do it one way, but probably relaly difficult or almost impossible to have it shine as nicely. It'd be a pain in the butt to work with transparency). And the quietly brilliant, well it's basically nearly impossible to make it move as nicely. You could definitely have it do the quietly brilliant like that but having it synchronizing and **** would be a pain in the butt and perhaps not even possible. Just don't do it, it's not easy for 1.6 and you dont have much control over the bootscreen scrolling. I don't know if I'm clear but you should understand where I'm heading with this lol. Unless you wanna recode etc etc all that for a bootscreen, then perhaps it will become more possible!

KAwAtA said:
I think eclair roms would work, but Incase you didn't know.. (I think you know but I guess ill try and explain anyway. I don't even know why the other member tried this because the files don't even go in the same folders as the bootscreen files do for 1.6 lol. The folder doesn't even exist and they use completely different image files. Some people, good lord. I bet if you put FLASH THIS UNKNOWN RADIO, someone would do it. Test it one day! haha)
1.6 uses two images, i think it's a png image. One sits there, and the other scrolls through. You could definitely make the HTC shine (pretty easy if you do it one way, but probably relaly difficult or almost impossible to have it shine as nicely. It'd be a pain in the butt to work with transparency). And the quietly brilliant, well it's basically nearly impossible to make it move as nicely. You could definitely have it do the quietly brilliant like that but having it synchronizing and **** would be a pain in the butt and perhaps not even possible. Just don't do it, it's not easy for 1.6 and you dont have much control over the bootscreen scrolling. I don't know if I'm clear but you should understand where I'm heading with this lol. Unless you wanna recode etc etc all that for a bootscreen, then perhaps it will become more possible!
Click to expand...
Click to collapse
I extracted the quietly brilliant section from an Eclair ROM. So I don't think it would be a stretch to get it to work on them.

Can you make the Nexus boot animation only- without Android logo

shokuhawan said:
Can you make the Nexus boot animation only- without Android logo
Click to expand...
Click to collapse
That's available somewhere else on these forums.

Incase it was not noticed in the cursorsense thread, will this remove the rogers logo on the first boot screen that comes up on my Magic? Thanks.

i passed the boot image according to those instructions but it didnt work still has the other iages. Do you know what might have happened?

gomo187 said:
Incase it was not noticed in the cursorsense thread, will this remove the rogers logo on the first boot screen that comes up on my Magic? Thanks.
Click to expand...
Click to collapse
No it doesn't. That's an RBG bootscreen replacement. There are a few threads on how to do that.
jgcaap said:
i passed the boot image according to those instructions but it didnt work still has the other iages. Do you know what might have happened?
Click to expand...
Click to collapse
What ROM and Android firmware are you running?

I realy like this. Would like to put it on my mytouch 32b

that is amazing
i would love to do this on my phone

Flashing the boot screen
I think this is a brilliant screen and thank you for making it, but, before my phone potentially becomes a brick, is there an easier way to flash a new boot screen other than going through adb, such as maybe flashing the zip through a recovery?
Thanks for your support!

[CLOSED] Goto G3 Android Development

GOTO: NebulaKernel On G3 Android Development
XDA:DevDB Information
NebulaKernel, Kernel for the T-Mobile LG G3
Contributors
Eliminater74, thewalkingdude
Source Code: https://github.com/Eliminater74/NebulaKernel/tree/nebula-mod
Kernel Special Features: Tons of Mods
Version Information
Status: Testing
Created 2015-06-26
Last Updated 2015-10-01

( Downloadz )
CLOSED

NFO:
Closed

{
"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"
}

Hi thanks for your work is appreciated , I have problem installing the file using TWRP it said Error executing updater binary in zip Failed any help will be appreciated.

Nice! Thanks for this!
Sent from my LG-D851 using Tapatalk

egalpr said:
Hi thanks for your work is appreciated , I have problem installing the file using TWRP it said Error executing updater binary in zip Failed any help will be appreciated.
Click to expand...
Click to collapse
Must be an error in zip, Ill fix that and Re-Upload it..

Update: Do to a problem with the Zip file, I had to Redo Zip. New one has been tested by me, And works.
Sorry for the inconvenience..
BTW: This kernel is worked on all the time, So new updates will be released alot. I already know of a few more things that I want to add.
My Goal is to make this Operate at low temps while keeping its performance as well at Longer Battery Life.
One of my test builds, The battery lasted me 3 days on a single charge. Without heavy usage.
My temps range betwen 87f /30c - and - 100f/37c (Stabilize around 97f/ 36c).

Eliminater74 said:
Reerved
Click to expand...
Click to collapse
Updater Binary failed at install... Downloaded from both links, same deal. Swapped out boot img into zip from 06/25 and it installed fine. Just a heads up. Thanks, good work. Todays update even more fun stuff!!!
Edit: I'm too slow, you already know.

zoman7663 said:
Updater Binary failed at install... Downloaded from both links, same deal. Swapped out boot img into zip from 06/25 and it installed fine. Just a heads up. Thanks, good work. Todays update even more fun stuff!!!
Edit: I'm too slow, you already know.
Click to expand...
Click to collapse
You must have gotten the zip that was bad before I replaced it with new one...........
Cause I tested the new one my self. and it worked......

@Eliminater74
Keep it up! It will get easier over time and its nice to look back and see how you have become more adept at what you are doing.
Just some friendly advice:
1. Always give proper credit
2. Always make clean commits.
1. is just because we do this for fun and for some sort of recognition (Even if some Devs won't admit it) and 2. because it makes troubleshooting, and reverting WAYYYY easier. When I started, I learned this the hard way. This way if you get into a situation where you have to make reverts or reset the branch, you are able to be more surgical about what you remove. If you have a commit that has alot going on in it then sometimes you cannot revert cleanly and it will have to be done manually. This can sometimes leave you more prone to make simple mistakes. Ones that we ALL make when Dev'ing late at night after a day of hard work and should really be getting more sleep. lol
Oh and 3. Learn to use Meld properly. This will make merging so easy, and will save you a metric crap ton of time.
If you need anything, feel free to PM me.
Regards,
Render

Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
Sent from my LG-D851 using Tapatalk

bofiana said:
Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
This Kernel is for Aosp only that is why your rom is not booting past the splash screen.
Click to expand...
Click to collapse

TheBlackMaou said:
bofiana said:
Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
This Kernel is for Aosp only that is why your rom is not booting past the splash screen.
Click to expand...
Click to collapse
Well sh!t. Guess i missed that in the op
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse

bofiana said:
Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Yes, you you cant install over a stock rom.. its only for Custom Roms AOSP example: CM,PAC-Rom,Bliss,Resurrection Remix, Ext...

RenderBroken said:
@Eliminater74
Keep it up! It will get easier over time and its nice to look back and see how you have become more adept at what you are doing.
Just some friendly advice:
1. Always give proper credit
2. Always make clean commits.
1. is just because we do this for fun and for some sort of recognition (Even if some Devs won't admit it) and 2. because it makes troubleshooting, and reverting WAYYYY easier. When I started, I learned this the hard way. This way if you get into a situation where you have to make reverts or reset the branch, you are able to be more surgical about what you remove. If you have a commit that has alot going on in it then sometimes you cannot revert cleanly and it will have to be done manually. This can sometimes leave you more prone to make simple mistakes. Ones that we ALL make when Dev'ing late at night after a day of hard work and should really be getting more sleep. lol
Oh and 3. Learn to use Meld properly. This will make merging so easy, and will save you a metric crap ton of time.
If you need anything, feel free to PM me.
Regards,
Render
Click to expand...
Click to collapse
Wow, I would of never thought that someone like you would stop in to say anything. And very positive feedback indeed..
When I saw your name, I thought I was seeing things. I had to look twice.
But thanks man... I appreciate everything you said.. It all makes perfect sense..

It's a pity this kernel won't work with slim based roms. I really wanted to try it. Running Tesla ROM and it gets stuck on boot-up screen.

EVR_PR said:
It's a pity this kernel won't work with slim based roms. I really wanted to try it. Running Tesla ROM and it gets stuck on boot-up screen.
Click to expand...
Click to collapse
It boots on my friends Slim Rom.. This kernel is for 5.1.1.

Eliminater74 said:
It boots on my friends Slim Rom.. This kernel is for 5.1.1.
Click to expand...
Click to collapse
Apparently only the original 777kernel works with Tesla. Tesla is lollipop 5.1.1_r4. Thanks anyway.

Proof that it works with Slim based Roms.....
PS: Thats not a screen shot of my phone.. its a friends..

Pixel XL - System UI Has Stopped Working

Hello all,
I usually don't join forums and jump in to make one post pertaining to my issue but rather conduct extensive research to figure out my problem, so many apologies beforehand. However, this issue seems to be unique to me and I would to know if anyone can help me out!
After unlocking the bootloader yesterday, I rooted my Pixel XL using chainfire's systemless root method and I was ecstatic as ever! I followed the directions to the T to make sure I didn't make any mistakes, but using ADB program is familiar territory to me - everything went as expected and I successfully rooted my phone. However, I made the mistake of downloading apps that were not compatible with the systemless root, which I read could have some complications. This is where I was stumbling upon new ground, because I am not entirely familiar with "systemless root" and what the key differences are, nor what the repercussions would be for downloading apps that would look for root access in the /system partition. The two apps that I downloaded were "Magisk Manager" and "Game Guardian." On the Magisk Manager, the install data was downloaded to my phone, nothing was actually installed to the phone. As for Game Guardian, I don't think that app had compatibility with systemless root yet.
This issue where my UI would crash would persist, even after restarting my phone. I would boot the phone up to bootloader and recovery mode - just to cycle through and restart the phone regularly (since you can't wipe the cache partition), that didn't work. I tried deleting those apps and clearing their data from my phone, and that didn't work.
I made a revelation when I plugged the phone in and the persistent UI crashing stopped. I had thought that I fixed the issue, but then it continued throughout the day - up until before I posted this post. That was when I noticed that the crashing is tied with the battery status;
When I had low battery and my phone wasn't charging, my System UI would immediately crash.
When I had low battery and my phone was charging, my System UI would not crash.
When I have a decent charge (anything above what is "low battery" - 15%?), my System UI would not crash.
I did a little experiment when I was at low battery and I noticed that RIGHT BEFORE the System UI would crash, the battery icon would stay with the lightning bolt, instead of switching over to a red battery with low charge. I was unable to get a screenshot before it crashed, though. Provided, are screenshots of what my screen looked when the System UI would crash (minus the consistent pop-up) and when it was charging:
{
"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"
}
My concern right now, with my ignorance on systemless rooting and how incompatible apps could affect the phone, is that maybe the stock battery icon for when the phone is at a low charge is missing from the system file images and that is what might be causing the crashing.
Can anyone give any insight on the matter? I'll provide any information required, if need be!
Thank you in advance.
EDIT 1:
This issue is being tracked; http://forum.xda-developers.com/pixe...3490156/page11

this has been well documented in other threads. read around...

nbhadusia said:
this has been well documented in other threads. read around...
Click to expand...
Click to collapse
I understand that this a well-documented issue on other threads. However, those particular issues on those particular devices offered no remedy to the issue on my phone.

Callyvan said:
I understand that this a well-documented issue on other threads. However, those particular issues on those particular devices offered no remedy to the issue on my phone.
Click to expand...
Click to collapse
....thats because 'those' devices are the same devices as yours and theres currently no 'remedy' though CF is workin on one.... read around... its well documented for the device youre using....
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156/page11

Change your battery saver to 15%.
See pic below.

nbhadusia said:
....thats because 'those' devices are the same devices as yours and theres currently no 'remedy' though CF is workin on one.... read around... its well documented for the device youre using....
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156/page11
Click to expand...
Click to collapse
My apologies, I had thought that "read around" meant that other threads were posted, not that it was discussed in a previous thread.
Thank you for a point in the right direction.

Callyvan said:
My apologies, I had thought that "read around" meant that other threads were posted, not that it was discussed in a previous thread.
Thank you for a point in the right direction.
Click to expand...
Click to collapse
I have not experienced this problem. And some that have were using outdated ADB / SDK drivers.
One person fixed it by simply updating ADB and drivers then re-rooted and he was all set. I will try to find the link...
Correction: Chainfire did identify the issue: http://forum.xda-developers.com/showpost.php?p=69405488&postcount=143

Scott said:
I have not experienced this problem. And some that have were using outdated ADB / SDK drivers.
One person fixed it by simply updating ADB and drivers then re-rooted and he was all set. I will try to find the link...
Correction: Chainfire did identify the issue: http://forum.xda-developers.com/showpost.php?p=69405488&postcount=143
Click to expand...
Click to collapse
Thank you for that, Scott. I'll be following that main thread now.
At least it is indeed that it only happens when the battery level is low.

Callyvan said:
I understand that this a well-documented issue on other threads. However, those particular issues on those particular devices offered no remedy to the issue on my phone.
Click to expand...
Click to collapse
The current fix is to flash the stock boot.img or custom kernel and don't flash root. Im hopeful it will be fixed in next Supersu update.

Wtf
nbhadusia said:
this has been well documented in other threads. read around...
Click to expand...
Click to collapse
Who the heck are you helping even posting this stupid sentence? Not everyone is sitting at a desktop. Your post is just a big waste of time for you and everyone who reads it. Why not try to be helpful for once. I see over 200 people have viewed this post but all you can do is post how it's documented . Thanks a whole lot buddy..

ko0ky said:
Who the heck are you helping even posting this stupid sentence? Not everyone is sitting at a desktop. Your post is just a big waste of time for you and everyone who reads it. Why not try to be helpful for once. I see over 200 people have viewed this post but all you can do is post how it's documented . Thanks a whole lot buddy..
Click to expand...
Click to collapse
You're welcome. So hows that anger management course coming along 'buddy'?

nbhadusia said:
You're welcome. So hows that anger management course coming along 'buddy'?
Click to expand...
Click to collapse
Useless reply.

[TOOL][PIXEL 2 XL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Cant wait to try it

Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you

I'll wait for a few others as well

Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly

does this do the critical unlock as well?

razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work

mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply

razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works

This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:

jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?

mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate

jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first

Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?

almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol

almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key

mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.

Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.

dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.

dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??

Lineage OS Splash Screen/Remove bootloader unlock warning on Mi A1 (tissot)

Lineage OS Splash screen for Mi A1 a.k.a. tissot
Unlocked bootloader required for installation!
Not tried on other phone models, neither I suggest you to...
Splash screen is the content (images) on the screen that appears before bootanimation (the phone start-up animation).
As you know, once we unlock our phone's bootloader, we get an ugly message reading 'Bootloader has been unlocked, device could not be verified...' every time the phone starts/restarts:
{
"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"
}
So, I created this splash screen replacement to hide that annoying warning. Also, I do most of the tinkering with custom ROMs on my Mi A1 at night, and restarting with a white screen on full brightness kind of makes my eyes bleed, so every possible screen is now with black background. Refer images:
The critical error screen, and fastboot screen are kept stock, as those were black already:
Pre-requisites:
Unlocked bootloader
A PC with adb drivers
A backup of stock Splash-screen (Refer Below)
New splash file to flash (Refer below)
Installation steps:
Reboot to fastboot/bootloader mode or start the phone by pressing [Vol down] + [Power].
Connect the phone to PC and paste the splash file to folder containing the adb files.
While in the adb folder, press [Shift]+[Right Click] and select 'Open Powershell Window Here'/'Open Command Prompt Window Here'
Enter command 'fastboot devices'. This will return the list of devices connected. This is to ensure that your device has been connected properly.
Enter command 'fastboot flash splash <spash image name>.img', where <spash image name> is to be replaced with the name of image you are flashing. Once the command finishes executing, power on the phone, and Voila!
Confirmed to be working on Pie based Roms(Personally Tested)
Credits:
Made using guide by GokulNC. Thread:https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-change-boot-logo-splash-t3681033
All the logos used here are the properties of their respective owners, and no copyright infringement is intended.
Buy me coffee: https://www.paypal.me/devashishgulati
Splash Screen Flash Files (More to be added later):
Stock Splash: https://forum.xda-developers.com/attachment.php?attachmentid=4286848&d=1506686803
Lineage OS: https://drive.google.com/open?id=18l2F-pEEonARIwRteWmJ-KMEmJhioqUH
Stock black with warning removed: https://drive.google.com/open?id=1OG7WSmnJau9NsA4PYubUkhaCjkDa7mjP

What if we want to go back to stock one?

WhatzIt2Ya said:
What if we want to go back there stock one?
Click to expand...
Click to collapse
I have attached the stock splash file in pre-requisite steps, in case you run into an error or don't like the new splash or want to visit service center, and want to revert.

indtiger93 said:
I have attached the stock splash file in pre-requisite steps, in case you run into an error or don't like the new splash or want to visit service center, and want to revert.
Click to expand...
Click to collapse
Just a suggestion, can you add screen shot to op..

adnbwta said:
Just a suggestion, can you add screen shot to op..
Click to expand...
Click to collapse
Wasn't clear with what screenshot was required. Instead Moved stock splash to the same place in the page.

indtiger93 said:
Wasn't clear with what screenshot was required. Instead Moved stock splash to the same place in the page.
Click to expand...
Click to collapse
No, I mean screenshot for the "lineage splashscreen"

Has anyone else tested this splash image?

This is it as a flashable zip. Thank me later.

Is it possible to make a black version of the stock Xiaomi splash animation like in the OP? Tired of seeing the warning screen as well but I'm currently on PE so the LOS one doesn't really fit.

cheffy11 said:
This is it as a flashable zip. Thank me later.
Click to expand...
Click to collapse
then how can I go back to the stock bootanimation?

Thanks man.

Sorry guys for being AFK for so long

RohinZaraki said:
Is it possible to make a black version of the stock Xiaomi splash animation like in the OP? Tired of seeing the warning screen as well but I'm currently on PE so the LOS one doesn't really fit.
Click to expand...
Click to collapse
Added stock splash dark version with warning removed https://drive.google.com/open?id=1ory7EvHkzq_UiWjGXeJmxRxumx6aDaGj
Sorry for the late reply. Moved to a different country

I installed the StockDark splash screen and when i rebooted the phone the image apeared laggy (like a TV without signal, with green lines all over the screen), tried it again and it happened aswell, so I installed the LineageDark one and works great.
Thank you, hope you can fix it

Can someone please provide a flashable zip file for Stock Black ?
---------- Post added at 05:12 AM ---------- Previous post was at 05:11 AM ----------
oliese said:
I installed the StockDark splash screen and when i rebooted the phone the image apeared laggy (like a TV without signal, with green lines all over the screen), tried it again and it happened aswell, so I installed the LineageDark one and works great.
Thank you, hope you can fix it
Click to expand...
Click to collapse
Agreed... Same happing with me.

indtiger93 said:
Added stock splach dark version with warning removed https://drive.google.com/open?id=1ory7EvHkzq_UiWjGXeJmxRxumx6aDaGj
Sorry for the late reply. Moved to a different country
Click to expand...
Click to collapse
In this one both the fastboot screen and splash screen are just noisy image with lines over and over (as explained by posts above). Used the lineage black one for now. That one works with no problem.

Eleo said:
In this one both the fastboot screen and splash screen are just noisy image with lines over and over (as explained by posts above). Used the lineage black one for now. That one works with no problem.
Click to expand...
Click to collapse
Really sorry man, to you and to all others who flashed the buggy image. The thing is I have reverted my Mi A1 to fully stock, and have bought OnePlus 7 as my primary device.
Nevertheless, I will be posting an updated and fixed dark stock image tonight or tomorrow night. Please check if it solves the problem.

indtiger93 said:
Really sorry man, to you and to all others who flashed the buggy image. The thing is I have reverted my Mi A1 to fully stock, and have bought OnePlus 7 as my primary device.
Nevertheless, I will be posting an updated and fixed dark stock image tonight or tomorrow night. Please check if it solves the problem.
Click to expand...
Click to collapse
No problem. I was just reporting. You have no obligation or hurry.
Good luck:good:
P.S. Congrats on new device

Eleo said:
No problem. I was just reporting. You have no obligation or hurry.
Good luck:good:
P.S. Congrats on new device
Click to expand...
Click to collapse
Thanks, Man
Here is your image for stock dark mode (new android one logo instead of bootloader warning )
https://drive.google.com/open?id=1OG7WSmnJau9NsA4PYubUkhaCjkDa7mjP

mrhimanshu said:
Can someone please provide a flashable zip file for Stock Black ?
---------- Post added at 05:12 AM ---------- Previous post was at 05:11 AM ----------
Agreed... Same happing with me.
Click to expand...
Click to collapse
Check now with link posted above :good: