Related
Is it possible to change it on our device? I can't find anything about it and I've looked all around.
If anyone knows how or can point me to a thread, that would be great.
waffleman911 said:
Is it possible to change it on our device? I can't find anything about it and I've looked all around.
If anyone knows how or can point me to a thread, that would be great.
Click to expand...
Click to collapse
If you are talking about boot animations:
Here
Here
Here
grubbster said:
If you are talking about boot animations:
Here
Here
Here
Click to expand...
Click to collapse
No. I am talking about the splash screen... Completely different from a boot animation.
A splash screen is the first still image right before the boot animation when the phone starts up. The Nexus 4 has just a black background that says "Google".
That is what I want to change.
From the discussions I have seen no one has a solution for that yet. Sorry.
........Epic WHOMP!!
RMA, and request a new splash screen, with a fruit on it.....
I also want to change the splash screen and use my own. If there is a way , please tell us or post a link if you find any. Thankx
Same here. I want to add my contact-info to the splash-screen. I have done that before with my HTC Desire and Galaxy S2. It's really useful when you lose your phone and someone just turns it on.
waffleman911 said:
Is it possible to change it on our device? I can't find anything about it and I've looked all around.
If anyone knows how or can point me to a thread, that would be great.
Click to expand...
Click to collapse
I think its part of the boot loader, as it shows the locked and unlocked symbols, so maybe if you downloaded the image from https://developers.google.com/android/nexus/images and extracted the bootloader image you could modify that and flash it through fastboot?
Sent from my Nexus 4
You can on other nexus devices with this app https://play.google.com/store/apps/details?id=aperture.ezekeel.logome not the n4 though
Sent from my Nexus 4
Tom540 said:
I think its part of the boot loader, as it shows the locked and unlocked symbols, so maybe if you downloaded the image from https://developers.google.com/android/nexus/images and extracted the bootloader image you could modify that and flash it through fastboot?
Sent from my Nexus 4
Click to expand...
Click to collapse
You can't simply extract the Bootloader and edit it's files. You would have to open it up in a hex editor and find the offsets for the image. Then inject your own into that offset and pray that you got all the dimensions and formatting 100% correct or else when you flash it you will have a nice hard brick
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
You can't simply extract the Bootloader and edit it's files. You would have to open it up in a hex editor and find the offsets for the image. Then replace it with your own in hex and pray that you got it 100% correct or else when you flash it you will have a nice hard brick
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Fair enough, its just that's the only way I could think to modify the splash screen
Sent from my Nexus 4
Did anyone figure out the way to do this?
t'was so easy on all my other devices.
Maine_Coon said:
Did anyone figure out the way to do this?
t'was so easy on all my other devices.
Click to expand...
Click to collapse
The splash screen depends on the bootloader. It might be easier on another device, but the Nexus's bootloader was not designed in such a way that makes this easy. You would have to modify the bootloader, but it really isn't worth it because there is no room for error. One wrong character in the bootloader and you have a nice shiny brick.
lopezk38 said:
The splash screen depends on the bootloader. It might be easier on another device, but the Nexus's bootloader was not designed in such a way that makes this easy. You would have to modify the bootloader, but it really isn't worth it because there is no room for error. One wrong character in the bootloader and you have a nice shiny brick.
Click to expand...
Click to collapse
Got it.
Indeed, not worth it.
Have to live w/Google splash, alas.
Dang! I did SO want to change it to "Goobers" or "Goofball" or somesuch.
That "Google" shown on when starting up the phone in my knowledge the bootloader.
There might way to change the image , but you would have to mess with the bootloader.
Messing with the bootloader is dangerous, and a corrupted bootloader most of the time leads to bricked phone( there are ways to recover but its best not let it come to this)
So its best to leave the "Google" thing alone; It's not that intrusive and quickly disappears.
Actually, all of you are wrong in two ways:
1) You can't flash a custom bootloader on Nexus 4, because due to its qfuse configuration (in bootloader it appears as "Secure Boot: Enabled") it would compromise the trusted bootchain and therefore lead to a bricked device.
2) The splash image is not STORED in the bootloader itself, i'm currently working to find out where it is stored, but unless google pushes out an update with an updated splash screen it is going to be difficult.
I found out that a copy of the charging animation(when the phone is turned off), which is displayed by the bootloader is stored in "/res/images/charger"
My current idea is to find the function that puts the animation there and see where it comes from.
On other devices like HTC and Motorola it is more easy as the splash screen is stored in a seperate partition.
(Oh, and the bootloader isn't just what you see when you boot into fastboot mode, it consists out of tz, sbl1, sbl2, sbl3, rpm and aboot.)
So anyone figured out or we cant change the splash screen?
I wanted to go ahead and make an open thread for N6 AT&T folks so that we can talk about removing all AT&T customization from the phone. Here's what we know so far:
1. Phone is SIM locked to AT&T.
FIX: user @jamezr used http://www.cellunlocker.net/ for $25 and was able to obtain a working unlock code.
Also I requested an unlock code from http://www.swiftunlocks.com. They only charge $9.99. Code was delivered in 2 days (no weekends) and worked without issue.
2. Carrier branding on back of device-
FIX: from user @Affliction716 "On another note the AT&T Deathstar on the back scrapes off without leaving a mark at all!!! Just take a knife or the edge of a credit card and lightly scrape over it. Disappears like it was never there"
3. Bloatware is installed when device is activated with AT&T sim. Can be easily removed.
FIX: Setup the phone without AT&T Sim and it will not show up.
4. On bootup there is an annoying AT&T splash screen. This cannot be removed by simply flashing the factory image.
FIX: From @bodosom Using your favorite File Manager with root permissions:
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
5. Annoying AT&T default ringtones by default
FIX: Courtesy of @Plexicle (takes care of boot splash as well)
Contents of OEM:
/oem/lost+found/
(empty)
/oem/media/
/oem/media/ringtones/
/oem/media/ringtones/ATT_Catch_Me.mp3
/oem/media/ringtones/ATT_Firefly.mp3
/oem/media/ringtones/ATT_Play_On.mp3
/oem/media/ringtones/ATT_Stargazer.mp3
/oem/media/bootanimation.zip
/oem/oem.prop
oem.prop contains one line:
"ro.config.ringtone=ATT_Firefly.mp3"
The entire oem partition looks completely useless and should be safe to nuke.
Edit:
I emptied the oem partition entirely. Going to do a quick round of testing and make sure nothing is messed up and report back.
Editx2: back!
Everything is working great. The only thing I noticed is that the call ringtone was initially set to "Unknown ringtone" after first boot. It was probably set by oem.prop and then couldn't find it after that. Just changed it to a different tone, works great.
From @DA6030: So, it sounds like the single command "fastboot erase oem" should take care of most people, and can replace directions #4 and #5 in the OP. This avoids root or messing with ROMs, for the many users who don't need root, and preserves OTA compatibility from Google. One could even re-lock (fastboot oem lock) immediately afterwards, if one doesn't need the tethering fix.
6. Tethering is disabled unless you have a tethering plan.
FIX: http://forum.xda-developers.com/showpost.php?p=56915621&postcount=48
Discuss!
iboj007 said:
I wanted to go ahead and make an open thread for N6 AT&T folks so that we can talk about removing all AT&T customization from the phone. Here's what we know so far:
1. Carrier branding on back of device
2. Bloatware is installed when device is activated with AT&T sim. Can be easily removed.
3. On bootup there is an annoying AT&T splash screen. This cannot be removed by simply flashing the factory image.
Discuss!
Click to expand...
Click to collapse
I also would like to know how to change the boot animation. It's driving me crazy, both from a Nexus standpoint and just because it's loud as hell. The first strike against the N6 in general is the Motorola M on the back. I would have rather seen the Nexus X logo there.
In my eyes, the ATT version is not a Nexus. Same thing happened with the Galaxy Nexus.
jcarlm said:
In my eyes, the ATT version is not a Nexus. Same thing happened with the Galaxy Nexus.
Click to expand...
Click to collapse
It has a couple neg points, but it is still a nexus. I would agree with you if it had a different build number and didn't receive the updates directly from Google. In all the ways that really matter it's a Nexus. Just pisses purists off, myself included.
jcarlm said:
In my eyes, the ATT version is not a Nexus. Same thing happened with the Galaxy Nexus.
Click to expand...
Click to collapse
I would almost agree with you, but not quite.
Bootloader is still unlockable. Factory image still comes from Google. Carrier didn't touch the system partition. It's Nexus.
We can fix the animation issue.
iboj007 said:
.........4. Tethering is disabled unless you have a tethering plan.
FIX: http://forum.xda-developers.com/show...1&postcount=48 Discuss!
Click to expand...
Click to collapse
Here is the complete link (possible fix for tethering). http://forum.xda-developers.com/showpost.php?p=56915621&postcount=48
Some guy in another thread here had success scraping off the AT&T logo with the edge of a credit card. Said it left no mark.
Don't blame me if you muck up your device. Lol.
SilkyJohnson said:
Some guy in another thread here had success scraping off the AT&T logo with the edge of a credit card. Said it left no mark.
Don't blame me if you muck up your device. Lol.
Click to expand...
Click to collapse
I just did it, but couldn't get it done with a credit card. Used a scissors and lightly took it off. There's still a very faint imprint of the logo, but you need to be in the right light. I'll upload pics in a bit.
ald9351 said:
It has a couple neg points, but it is still a nexus. I would agree with you if it had a different build number and didn't receive the updates directly from Google. In all the ways that really matter it's a Nexus. Just pisses purists off, myself included.
Click to expand...
Click to collapse
Plexicle said:
I would almost agree with you, but not quite.
Bootloader is still unlockable. Factory image still comes from Google. Carrier didn't touch the system partition. It's Nexus.
We can fix the animation issue.
Click to expand...
Click to collapse
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
T
So Google will update this phone with the AT&T boot up on it or will AT&T update the phone adding the AT&T boot
This is why I don't believe it is a true pure Nexus
jcarlm said:
So Google will update this phone with the AT&T boot up on it or will AT&T update the phone adding the AT&T boot
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
This is why I don't believe it is a true pure Nexus
Click to expand...
Click to collapse
Google still updates it. the AT&T boot animation is in a separate partition from the system.
iboj007 said:
3. On bootup there is an annoying AT&T splash screen.
Discuss!
Click to expand...
Click to collapse
Open /oem/media with your favorite tool.
Mount r/w.
Remove or rename the file bootanimation.zip and the directory ringtones.
Mount r/o or just reboot since you know you want to.
bodosom said:
Open /oem/media with your favorite tool.
Mount r/w.
Remove or rename the file bootanimation.zip and the directory ringtones.
Mount r/o or just reboot since you know you want to.
Click to expand...
Click to collapse
Holy nexus, that worked!! Now to scrape off that logo..
bodosom said:
Open /oem/media with your favorite tool.
Mount r/w.
Remove or rename the file bootanimation.zip and the ringtones.
Mount r/o or just reboot since you know you want to.
Click to expand...
Click to collapse
I read that the ATT boot animation was in a partition named logo. You should be able to clear it out.
http://www.androidpolice.com/2014/1...be-and-jingle-on-the-boot-screen-because-att/
This is awesome. I just updated the first post.
Anything else?
iboj007 said:
This is awesome. I just updated the first post.
Anything else?
Click to expand...
Click to collapse
Yeah,...go back and edit the tethering link...it's not correct.
soulctcher said:
Yeah,...go back and edit the tethering link...it's not correct.
Click to expand...
Click to collapse
Fixed and added the fact that it's SIM locked.
iboj007 said:
4. On bootup there is an annoying AT&T splash screen. This cannot be removed by simply flashing the factory image.
FIX: From @bodosom Using your favorite File Manager with root permissions:
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
Click to expand...
Click to collapse
Thank you so much! I don't mind the AT&T logo on the back, but damn that boot animation was annoyingly loud! I just disabled it and I no longer dread restarting my phone for fear of destroying my ear drums.
Wait, what?!? The AT&T-bought N6's are SIM-locked to AT&T only? Thank God for T-Mobile and keeping the Nexus devices pure!
Question- will i have this issue if i purchased the phone from the GPS and then activate it with an att sim? Or is it only phones purchased from att?
sfidelisrp said:
I just did it, but couldn't get it done with a credit card. Used a scissors and lightly took it off. There's still a very faint imprint of the logo, but you need to be in the right light. I'll upload pics in a bit.
Click to expand...
Click to collapse
I would love to see photos of what it looks like scraped off. I get mine Monday, and would be so happy if I could remove that logo on the back without scratching the heck out of it. I always knew the bootup could be removed or changed....I've been rooting and flashing for years now. So if you get a chance to upload some photos...or if anyone can, that would be greatly appreciated.
For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.
So the difference in between whats out there and this is? I'm curious as the build is different.
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.
Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app
Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.
Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.
Well no worries this all but confirms vzw is rootable and unlockable
Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx
Is there a rooted version??
Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition
Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.
Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?
How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat
mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA
Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone
Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?
Hi everyone, new poster here but long time user!
I have recently rooted and installed twrp on my sprint lgv20. I also installed the stock international ROM to sim unlock for various uses. My only annoyance with the root is the red warning corruption screen, i was wondering if anyone had a work around or image to flash to get rid or hide the screen somehow with maybe an lg screen or anything.
Thank you for any suggestions,
Zach
juicemane141997 said:
Hi everyone, new poster here but long time user!
I have recently rooted and installed twrp on my sprint lgv20. I also installed the stock international ROM to sim unlock for various uses. My only annoyance with the root is the red warning corruption screen, i was wondering if anyone had a work around or image to flash to get rid or hide the screen somehow with maybe an lg screen or anything.
Thank you for any suggestions,
Zach
Click to expand...
Click to collapse
Unfortunately there is no current fix for this. I am not sure what exactly is needed for this to be fixed, but I would assume that those people who are developing roms for the V20 have already exhausted what ever options there are.
Would be nice to have fixed, but since that screen is only during initial boot up I don't think anyone is terribly concerned with getting this corrected.
Hope this helps.
No fix
It is related to google
Not lg
I would imagine the reason for this is both for security and to let manufacturers know when a phone has been modified.
I don't believe there is a workaround for it either because it can't be done (doubtful as I am sure its software based) or people just don't care (honestly I am sure some developers were annoyed enough to look into it). I just don't think anyone has found a way around it.
This "feature" was introduced in marshmallow.
Edit: further research shows the Nexus 5x developers were able to work around it by replacing the image. So while it doesn't remove the function it hides it.
https://forum.xda-developers.com/nexus-5x/help/to-remove-corruption-warning-message-t3248441
Please note this is a marshmallow phone not nougat so I am not sure the same concept would work on our phone.
Sent from my LG-H918 using XDA-Developers Legacy app
That's what they did with the HTC one m7. Was to replace the image. It's just finding the way to do it. As Everytime the devs find a way around something. Then Google, the phone makers,or carriers patches it to make it harder next time. I understand why they make that tamper screen because to many people trying to root and bricks their phones lies about not tampering with their phones OS. They say don't know what happened I just turned it on and nothing. I am sure they will find a way to replace the image. It just takes time and it's low priority on the devs list of things to do.
Sent from my LG-H910 using Tapatalk
Dark Jedi said:
That's what they did with the HTC one m7. Was to replace the image. It's just finding the way to do it. As Everytime the devs find a way around something. Then Google, the phone makers,or carriers patches it to make it harder next time. I understand why they make that tamper screen because to many people trying to root and bricks their phones lies about not tampering with their phones OS. They say don't know what happened I just turned it on and nothing. I am sure they will find a way to replace the image. It just takes time and it's low priority on the devs list of things to do.
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
It appears that the image is located within the bootloader. It would have to be extracted, changed, and put back in assuming there is not a signature check with it on boot up. From what I was reading it depends on which partition it is located in whether it can be done or not. If it is in aboot, Tilde has mentioned that we can't edit this partition. Unfortunately it doesn't sound like it's a simple case of replacing an image.
androiddiego said:
It appears that the image is located within the bootloader. It would have to be extracted, changed, and put back in assuming there is not a signature check with it on boot up. From what I was reading it depends on which partition it is located in whether it can be done or not. If it is in aboot, Tilde has mentioned that we can't edit this partition. Unfortunately it doesn't sound like it's a simple case of replacing an image.
Click to expand...
Click to collapse
I can confirm it is located in aboot itself.
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
Its not random, and if you look closer its a bootmenu. you can get past it marginally quicker by just tapping power button or use it to boot to recovery, fastboot/bootloader, etc.
And you cannot remove it.
You can go back to b20...
@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.
metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
The screen is part of the bootloader image. I strongly advise you to just live with it since if you screw up the bootloader you're bricked.
Might I suggest you start by looking around in the bootloader unlock zip. Might give you some idea where it is or if it can be removed.
Also look at older list mentioning it, I remember seeing mention of other phones it's been used on, maybe someone has more info in one of those forums.
And I will look for those boot animations. If I can suggest a superman or superAndy would be nice
Good Hunting
metpolds said:
@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.
Click to expand...
Click to collapse
I know what you are talking about - on older motorola phones we did away with it - it was just a stored image in those phones. Seeing as how here it is a fully functional menu I would bet any attempt to remove or replace it would most definitely brick the phone. I gave up on it a long time ago.
@lafester .. @nujackk .. @bkores .. @tabletalker7 .. Thanks guys for all your comments - I guess my next step eventually, there is no great hurry for this, is to make certain I have a couple of good backups before messing around with disassembling the bootloader and boot image. If I ever get anywhere with this I will let you guys know.
@nujackk I note your comments re the animations. I'm about to add another Andy animation to the thread but have searched in the past for usable Superman material without much success, however I will see what I can find.
Yeah I haven't seen many that were very good either, but keeping hope alive :fingers-crossed: