Database Users

Editing "software can't be checked for corruption" message from unlocking bootloader?

Editing "software can't be checked for corruption" message from unlocking bootloader?
I have rooted, modded, etc. my OnePlus 5 but that required me to unlock my bootloader. When you do that, it causes an ugly message to appear for 5 seconds at boot. I want to keep this message so I have 5 seconds to go into Recovery, Fastboot, etc and so myself and others will be aware that the bootloader is unlocked. However, I could make a much better design, maybe even add a changing countdown number until boot.
However, I don't know how to change it.
Does anyone know how to edit the "software can't be checked for corruption" message?
{
"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"
}

I'm surprised this hasn't been changed as a couple of other phones have had this removed months ago...
I have an Axon 7 and that was solved a few weeks after it came about. There are fewer devs there than working on the One+ phones and we still have this undesirable boot screen every time we boot up...

keeganjk said:
I have rooted, modded, etc. my OnePlus 5 but that required me to unlock my bootloader. When you do that, it causes an ugly message to appear for 5 seconds at boot. I want to keep this message so I have 5 seconds to go into Recovery, Fastboot, etc and so myself and others will be aware that the bootloader is unlocked. However, I could make a much better design, maybe even add a changing countdown number until boot.
However, I don't know how to change it.
Does anyone know how to edit the "software can't be checked for corruption" message?
Click to expand...
Click to collapse
I don't think u can change it. It's becoming more and more common on phones now. There are some able to change on phones but with OnePlus I don't think so.

the_rooter said:
I don't think u can change it. It's becoming more and more common on phones now. There are some able to change on phones but with OnePlus I don't think so.
Click to expand...
Click to collapse
Can't flash with fastboot out something?

keeganjk said:
Can't flash with fastboot out something?
Click to expand...
Click to collapse
Explain? Alittle

the_rooter said:
Explain? Alittle
Click to expand...
Click to collapse
IDK, that's why I'm asking.

keeganjk said:
IDK, that's why I'm asking.
Click to expand...
Click to collapse
The screen u see is telling u that the bootloader is unlocked and that with that showing u can flash twrp, roms and root the phone. U can't flash factory imsges unless the bootloader screen that u see is showing .

ultramag69 said:
I'm surprised this hasn't been changed as a couple of other phones have had this removed months ago...
I have an Axon 7 and that was solved a few weeks after it came about. There are fewer devs there than working on the One+ phones and we still have this undesirable boot screen every time we boot up...
Click to expand...
Click to collapse
I don't want to GET RID of it, I just want to EDIT the image.

keeganjk said:
I don't want to GET RID of it, I just want to EDIT the image.
Click to expand...
Click to collapse
I really don't think u can. It's built I believe right in the bootloader or aboot . Maybe someone with more knowledge can confirm. But I believe it's there the way it is.

the_rooter said:
I really don't think u can. It's built I believe right in the bootloader or aboot . Maybe someone with more knowledge can confirm. But I believe it's there the way it is.
Click to expand...
Click to collapse
Again, this HAS been removed from the Axon 7... It doesn't sit there for 5 minutes with a blank screen then boot, it boots up as per normal without displaying the Bootloader unlocked" screen...

ultramag69 said:
Again, this HAS been removed from the Axon 7... It doesn't sit there for 5 minutes with a blank screen then boot, it boots up as per normal without displaying the Bootloader unlocked" screen...
Click to expand...
Click to collapse
Completely different phone. Not possible with OnePlus.

Some phones have the image in a separate partition on the flash memory.
These are easy to hack (although Google has made it harder to do that recently, with checksums).
For others, the image is embedded in the bootloader. Hacking the bootloader is very risky as any mistake will end up with a brick.
OP5 is the latter.
You can change the OS boot picture. You can change the OnePlus logo that's displayed first. But not that warning. I even think the warning is mandated by the Android certification process.

Little Help needed to get my 6p alive again

please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.

smartpreet said:
please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.
Click to expand...
Click to collapse
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .

Exodusche said:
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .
Click to expand...
Click to collapse
i have tried that earlier, but still i got the red triangle.
since i failed to go to stock today i installed latest twrp-3.2.2-0-angler using latest SDK tool.
then i flashed Magisk-v16.0 and then ResurrectionRemix-M-v5.7.4-20161008-angler and it immediately went to google logo and stuck there.

just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers

billycar11 said:
just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers
Click to expand...
Click to collapse
{
"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"
}
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening

smartpreet said:
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening
Click to expand...
Click to collapse
What did the command line windows say when it was flashing

billycar11 said:
What did the command line windows say when it was flashing
Click to expand...
Click to collapse

smartpreet said:
Click to expand...
Click to collapse
It looks good but didn't seem to flash radio and bootloader maybe just not in screen shot should boot but if it still won't boot in to the stock recovery and factory reset might help

You could have the bad big cores try flashing one of the 4 core fixes. Also I wait to flash magisk until after first boot. It can hang you on the Google screen .

Lg g6 thinQ splash screen removal?

Is there any way to remove the lg g6 thinQ logo before the boot animation? My phone is rooted and is on ressurection remix. It's annoying to the see that picture splash screen before the boot animation.

Ghoster626 said:
Is there any way to remove the lg g6 thinQ logo before the boot animation? My phone is rooted and is on ressurection remix. It's annoying to the see that picture splash screen before the boot animation.
Click to expand...
Click to collapse
If be fine with that one of I could get the t mobile screen to go away. Freaking pink (magenta, whatever)
Sent from my LG-H872 using Tapatalk

Ken C said:
If be fine with that one of I could get the t mobile screen to go away. Freaking pink (magenta, whatever)
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Do you have root? If you do it's quite easy to remove the T-Mobile splash screen
(I believe you can unlock the bootloader and root Tmo varient...)

Mnky313 said:
Do you have root? If you do it's quite easy to remove the T-Mobile splash screen
(I believe you can unlock the bootloader and root Tmo varient...)
Click to expand...
Click to collapse
Already rooted and answered my own question last night [emoji23]
Sent from my LG-H872 using Tapatalk

Mnky313 said:
Do you have root? If you do it's quite easy to remove the T-Mobile splash screen
(I believe you can unlock the bootloader and root Tmo varient...)
Click to expand...
Click to collapse
Hey i have rooted g6 with twrp it has TIM mobile logo after g6 splash screen i tried to change boot animation zip but they seems to do nothing can you please tell me how to remove that TIM logo.

kurogami555 said:
Hey i have rooted g6 with twrp it has TIM mobile logo after g6 splash screen i tried to change boot animation zip but they seems to do nothing can you please tell me how to remove that TIM logo.
Click to expand...
Click to collapse
Hmm... Try using bootanimations for superuser from the play store, (https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations), there is a plus in bottom corner to import your own zips, alternatively you can copy the boot animation.zip to /system/media with chmod 644 I believe.

Mnky313 said:
Hmm... Try using bootanimations for superuser from the play store, (https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations), there is a plus in bottom corner to import your own zips, alternatively you can copy the boot animation.zip to /system/media with chmod 644 I believe.
Click to expand...
Click to collapse
i tried that i even deleted the bootanimation.zip and booted the phone but that logo is till showing

kurogami555 said:
i tried that i even deleted the bootanimation.zip and booted the phone but that logo is till showing
Click to expand...
Click to collapse
Interesting, its probably a secondary animation stored somewhere else, lemme check with my friend's VZW g6, try looking around in /system/media for other bootanimation zip files.

Mnky313 said:
Interesting, its probably a secondary animation stored somewhere else, lemme check with my friend's VZW g6, try looking around in /system/media for other bootanimation zip files.
Click to expand...
Click to collapse
There are these files, don't know what they do i never have seen them on previous phones.

kurogami555 said:
There are these files, don't know what they do i never have seen them on previous phones.
Click to expand...
Click to collapse
Bootanimation_plus.zip is the boot animation for the G6+, it should match the stock one just with a + on the splash screen, and bootanimation_decrypting.zip is the animation it plays when you decrypt your phone (if you encrypted it, if you didn't it is unused) I'm extracting a tmo ROM RN, try replacing all 3 animation zips with the one you want

I used this out of magisk (midnightcore) and it works. There are 2 files now in system /media didn't look before but theoretically it should allow for changing the animation regardless of the module I would think. Just permissions and size etc that could get in the way. But that stuff isn't stuff I've dove into. But, if you're the type to build them I think it's doable. Flash that module, run it, and see what it puts in there. I believe it backs up the stock like you would if done manually. Can't see it being so much more than changing the picture size (the ones I've used aren't optimized for or screens that I've noticed) or replacing the pictures all together.
{
"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"
}
If nothing else it got rid of that God awful pink tmo screen
Sent from my LG-H872 using Tapatalk

Mnky313 said:
Bootanimation_plus.zip is the boot animation for the G6+, it should match the stock one just with a + on the splash screen, and bootanimation_decrypting.zip is the animation it plays when you decrypt your phone (if you encrypted it, if you didn't it is unused) I'm extracting a tmo ROM RN, try replacing all 3 animation zips with the one you want
Click to expand...
Click to collapse
ok hopes that works.

Ken C said:
I used this out of magisk (midnightcore) and it works. There are 2 files now in system /media didn't look before but theoretically it should allow for changing the animation regardless of the module I would think. Just permissions and size etc that could get in the way. But that stuff isn't stuff I've dove into. But, if you're the type to build them I think it's doable. Flash that module, run it, and see what it puts in there. I believe it backs up the stock like you would if done manually. Can't see it being so much more than changing the picture size (the ones I've used aren't optimized for or screens that I've noticed) or replacing the pictures all together. View attachment 4632765
If nothing else it got rid of that God awful pink tmo screen
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
nope not working mid night shows that it successfully applied a new boot animation but after i restart the device it's still TIM logo animation ?

kurogami555 said:
nope not working mid night shows that it successfully applied a new boot animation but after i restart the device it's still TIM logo animation [emoji22]
Click to expand...
Click to collapse
That midnight deal starting acting weird for me too after it was updated this morning. I tried changing to the superhero deal and it gave me issues also.
Edit: give it another try, I just did after making the above comment and it worked.
Something to think about. While I was looking around my files in the phone I noticed that if I had saved the animation zip when asked that it did. Because I'm thinking if the script will download but seems to have an issue applying the animation if we couldn't just take the zip from where midnight downloads it to and manually place it. Don't see why not. Script is only automating the process
Sent from my LG-H872 using Tapatalk

Ken C said:
That midnight deal starting acting weird for me too after it was updated this morning. I tried changing to the superhero deal and it gave me issues also.
Edit: give it another try, I just did after making the above comment and it worked.
Something to think about. While I was looking around my files in the phone I noticed that if I had saved the animation zip when asked that it did. Because I'm thinking if the script will download but seems to have an issue applying the animation if we couldn't just take the zip from where midnight downloads it to and manually place it. Don't see why not. Script is only automating the process
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
ok, so o just tried the midnight after update with clean install but no luck even if i manaully replace it it won't show the animation. I think it's built in boot image because even if i delete all the bootanimation zips from /system/media folder the TIM logo still F##king shows. ?

Galaxy J5 SM-J500FN stuck on boot screen after flashing custom ROMs

Hello to everyone,
I hope that someone can help me at this point where i'm stuck on bootscreen after i flashed an custom ROM.
So, let me tell you my story.
I have a little of experience with flashing custom ROMs. And on my personal phone (Galasy S5) i succesfully installed over and over again custom ROMs. I really like the ROMs from AOSP Extended. They are covering all of my needs. So today i have an Samsung Galaxy J5 SM-J500FN. It is having some problems with the capacitive buttons(Back and multitasking buttons); those are playing however they want, so you can realise that entering in some app and your phone exiting fro it by itself is very annoyng. So on my S5 i have an option that can disable those buttons for good. And i wanted to install the Android &.1 Nougat offered by AOSP Extended today. So i ve got the TWRP from the official website for the right model of the phone (J500FN) and put it succesfully on it. I downloaded the ROM from official AOSP website, and succesfully installed it on the phone whithout any error. Then i installed the GApps nano, again with 0 errors. And when i was relaxing a little bit hoping that everything it s allright, when i wanted to boot up the phone, it froze up at boot screen (At the moment with that logo with Samsung ... powerd by Android). Then in a couple of seconds it started to turn to an green screen and then to an white screen. At this point, everything is frozen. So i removed the battery and entered in recovery mode(TWRP). There was no problem (only with those capactive buttons that i want to block).. But anyway, i donloaded several ROMs and nothing so far. I tried with anoter TWRP version, samething, stuck on boot screen.
Until my first atempt to flash the custom ROM, the phone worked just fine, only that those buttons ware going crazy. But now, i can't start it up in every mode i can think of.
Can anyone help me with this, please?! Any ideea of how to slve it?
TWRP version 3.1.1-1 j5 nlte
Firmware version: AospExtended-v4.5-j5ltexx-20170816-2007-OFFICIAL
Phone version: SM-J500FN
Tried with various TWRP versions and ROMs. Installing with and without GApps. All the results were the same like in the pictures below:
1) Start up like a normal Android phone
{
"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"
}
2) The the big surprise
3) Getting colorfull
4) Advancing...
For now, i can flash with Odin any version of TWRP, i can flash from TWRP any firmware, but i cannot get it boot up normally.
I don't have any backups from stock firmware so, please don t ask me about that.
Thanks in advance...

Look at the aosp file you downloaded. It says j5LTE.
Your device is j5nlte not j5lte you tried to install the wrong file.
Simple as that.
And if that isnt your problem you may have the wrong bootloader and modem but changing that is easy just follow the guide here https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page15

garylawwd said:
Look at the aosp file you downloaded. It says j5LTE.
Your device is j5nlte not j5lte you tried to install the wrong file.
Simple as that.
And if that isnt your problem you may have the wrong bootloader and modem but changing that is easy just follow the guide here https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page15
Click to expand...
Click to collapse
I downloaded all the files i found out there to try see if anything is changing ))
I will try your solution later. Thank you for your reply

All done!
So, guys, my problem wasn-t from the firmware model, because i tryed many.
Thanks to
garylawwd
Click to expand...
Click to collapse
i flashed with Odin ''BootLoader version 5.1.1'' and everything after that was pretty simple.

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"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"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.