Hi, I recently unlocked my Qualcomm Moto E4's bootloader and flashed a custom ROM, and now I'm getting the familiar black screen with "N/A" in the top right corner on boot. I wanted to change it to something a bit nicer; however, flashing a new logo.bin does not seem to change anything, and the logo is not seen at boot. From my research, this issue doesn't seem to affect similar Moto phones, and the one thread I found concerning the E4 only had a supposed solution for the Mediatek variant. Does anyone have any ideas? Thanks.
It's a mystery that no one seems to be able to crack. Discussed it here already.
You have to change boot animation in /system/media as well as /OEM/media but you have to do that in TWRP for OEM side you have to mount the OEM partition and replace the file in file manager in twrp
He's talking about the boot logo, as in logo.bin. Not the boot animation.
mn1968 said:
He's talking about the boot logo, as in logo.bin. Not the boot animation.
Click to expand...
Click to collapse
Well either way now he knows how to change his boot animation also
mn1968 said:
It's a mystery that no one seems to be able to crack. Discussed it here already.
Click to expand...
Click to collapse
Yes, this was the thread I was referring to in my original post. I haven't found another regarding the topic, so I suppose it really hasn't been looked at that much. I figure any developers working on the device may have an idea.
mattvail692 said:
Well either way now he knows how to change his boot animation also
Click to expand...
Click to collapse
Sorry for the misunderstanding, I hoped that explicitly mentioning logo.bin would clear up possible confusion. In any case, thanks for the information.
fleinheus said:
Yes, this was the thread I was referring to in my original post. I haven't found another regarding the topic, so I suppose it really hasn't been looked at that much. I figure any developers working on the device may have an idea.
Sorry for the misunderstanding, I hoped that explicitly mentioning logo.bin would clear up possible confusion. In any case, thanks for the information.
Click to expand...
Click to collapse
Hey it was my misunderstanding also didn't read clearly enough though IDK why Motorola aka Lenovo has to add the stuff but we just have to work around it
fleinheus said:
Hi, I recently unlocked my Qualcomm Moto E4's bootloader and flashed a custom ROM, and now I'm getting the familiar black screen with "N/A" in the top right corner on boot. I wanted to change it to something a bit nicer; however, flashing a new logo.bin does not seem to change anything, and the logo is not seen at boot. From my research, this issue doesn't seem to affect similar Moto phones, and the one thread I found concerning the E4 only had a supposed solution for the Mediatek variant. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
Hi, sorry for this question, but I what to know what rom uses actually, because I try install one rom but not working, specific Resurrection remix but not working, I have the same smartphone, what roms do you recommend, thanks
jspguerrero said:
Hi, sorry for this question, but I what to know what rom uses actually, because I try install one rom but not working, specific Resurrection remix but not working, I have the same smartphone, what roms do you recommend, thanks
Click to expand...
Click to collapse
Why comment here instead of an off topic thread? This isn't where to post that.
fleinheus said:
Hi, I recently unlocked my Qualcomm Moto E4's bootloader and flashed a custom ROM, and now I'm getting the familiar black screen with "N/A" in the top right corner on boot. I wanted to change it to something a bit nicer; however, flashing a new logo.bin does not seem to change anything, and the logo is not seen at boot. From my research, this issue doesn't seem to affect similar Moto phones, and the one thread I found concerning the E4 only had a supposed solution for the Mediatek variant. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212
(Finally Answered)
Related
Hey guys, so I own a Nexus 6 (shamu) not a 6p, but just a curiosity question. I was told that the dm verity for the 6p was in the bootloader and not the kernel, it's built into the kernel on the shamu and the solution is just a custom kernel to remove the message, as for the 6p, is there a known way to remove those messages seeing as it is in the bootloader this time around? Nobody want's to corrupt a bootloader, or you're screwed! Lol
No.
Gytole said:
No.
Click to expand...
Click to collapse
Not at all possible yet?
H4X0R46 said:
Not at all possible yet?
Click to expand...
Click to collapse
Still no.
Thanks guys for your responses! Appreciate it! It was a super noob question, but like I said, I own a shamu and it's different. Thanks!
H4X0R46 said:
Hey guys, so I own a Nexus 6 (shamu) not a 6p, but just a curiosity question. I was told that the dm verity for the 6p was in the bootloader and not the kernel, it's built into the kernel on the shamu and the solution is just a custom kernel to remove the message, as for the 6p, is there a known way to remove those messages seeing as it is in the bootloader this time around? Nobody want's to corrupt a bootloader, or you're screwed! Lol
Click to expand...
Click to collapse
dm verity is part of the kernel. it can be seen in the linux tree. the bootloader just has a message about being unlocked. i was able to disable dm verity in AOSP when compiling android, without modifying the kernel. just a command in the fstab tells it to verify. the message in the boot loader is just to make sure you know it is unlocked.
dl200010 said:
dm verity is part of the kernel. it can be seen in the linux tree. the bootloader just has a message about being unlocked. i was able to disable dm verity in AOSP when compiling android, without modifying the kernel. just a command in the fstab tells it to verify. the message in the boot loader is just to make sure you know it is unlocked.
Click to expand...
Click to collapse
So a simple command can disable verity messages in this case? The others in the thread here were saying it's pretty much impossible.
H4X0R46 said:
So a simple command can disable verity messages in this case? The others in the thread here were saying it's pretty much impossible.
Click to expand...
Click to collapse
No. A simple command does not disable verity, but modifying boot does. The messages that you get about "possibly corrupt" are from the boot loader. If relocked, then it would go away.
It lamens terms it is saying "Hey i'm vulnerable! Read what you do before you flash that Galaxy S9 Rom on me!"
I honestly don't mind the message, and its only on screen for 3 seconds...I don't get the big deal.
And you can't compare phones....the Nexus 6 and Nexus 6P....are different phones....they use different everything and google is movong towards a more secure android experience so expect a plethora of corrupt this and broken that messages. Haha
I actually borked my friends Nexus 6 for a good 5 minutes a few months back because I didnt know you had to flash a modified boot and all we did was root it! But lesson learned and not one problem since!
But the message won't go away, it's to tell the next person you sell it to you did stuff to it. That's what she said.
Gytole said:
It lamens terms it is saying "Hey i'm vulnerable! Read what you do before you flash that Galaxy S9 Rom on me!"
I honestly don't mind the message, and its only on screen for 3 seconds...I don't get the big deal.
And you can't compare phones....the Nexus 6 and Nexus 6P....are different phones....they use different everything and google is movong towards a more secure android experience so expect a plethora of corrupt this and broken that messages. Haha
I actually borked my friends Nexus 6 for a good 5 minutes a few months back because I didnt know you had to flash a modified boot and all we did was root it! But lesson learned and not one problem since!
But the message won't go away, it's to tell the next person you sell it to you did stuff to it. That's what she said.
Click to expand...
Click to collapse
Yea, not so much comparing the phones, just using the Nexus 6 as an example. Yea the 6p is definitely different from the older Nexus models, and I remember someone saying something about an efuse thing you can trip and can't reverse, much like Samsung phones. How does this work? Is it like Samsung where it will always say it's been tampered with forever?
H4X0R46 said:
Yea, not so much comparing the phones, just using the Nexus 6 as an example. Yea the 6p is definitely different from the older Nexus models, and I remember someone saying something about an efuse thing you can trip and can't reverse, much like Samsung phones. How does this work? Is it like Samsung where it will always say it's been tampered with forever?
Click to expand...
Click to collapse
I guess I am very confused at why you're asking this...are you truing to figure out if the message means its corrupt? Because it more than likely isn't...it is just warning of possoble corruption you can has.
And you do lnow fuses can't be fixed once they're blown...you should have answered your own question haha
Gytole said:
I guess I am very confused at why you're asking this...are you truing to figure out if the message means its corrupt? Because it more than likely isn't...it is just warning of possoble corruption you can has.
And you do lnow fuses can't be fixed once they're blown...you should have answered your own question haha
Click to expand...
Click to collapse
Yea, the messages i know are just to let you know, the fuse is what i was wondering about. Kind of how the older Galaxy phones, the flash counter was able to be reset with the triangle away app and root, the nexus 6p is permanent? Yea, some noob questions, but it's because I own a shamu and never had to worry about any of this new stuff lol
H4X0R46 said:
Yea, the messages i know are just to let you know, the fuse is what i was wondering about. Kind of how the older Galaxy phones, the flash counter was able to be reset with the triangle away app and root, the nexus 6p is permanent? Yea, some noob questions, but it's because I own a shamu and never had to worry about any of this new stuff lol
Click to expand...
Click to collapse
No, the Nexus 6P is not permanent unlock. You can easily relock. There is no "unlock counter" or a "flash counter". I have mine unlocked the fuse I have read about elsewhere is still NOT blown. If you do call up google for support and you are unlocked, rooted, and/or custom ROM, then their first trouble shooting will be to download and flash the factory images. If the flashing of factory images does not fix your problem, then they will step up from there. Like replacing the phone. Unlike Samsung.
dl200010 said:
No, the Nexus 6P is not permanent unlock. You can easily relock. There is no "unlock counter" or a "flash counter". I have mine unlocked the fuse I have read about elsewhere is still NOT blown. If you do call up google for support and you are unlocked, rooted, and/or custom ROM, then their first trouble shooting will be to download and flash the factory images. If the flashing of factory images does not fix your problem, then they will step up from there. Like replacing the phone. Unlike Samsung.
Click to expand...
Click to collapse
Cool! So the Qfuse isn't even blown by installing custom files and unlocking the bootloader? I've read other places that people said you can never relock your bootloader, glad that's not true!
H4X0R46 said:
Cool! So the Qfuse isn't even blown by installing custom files and unlocking the bootloader? I've read other places that people said you can never relock your bootloader, glad that's not true!
Click to expand...
Click to collapse
I just used "fastboot flashing unlock", but I think if you use "unlock_critical" it might blow. I am not going to do this.
The "unlock_critical" allows you to flash a custom bootloader and radio. This may help if you want to flash a bootloader without the corrupt message, but it is only visible for a few seconds in booting. Flashing a custom bootloader is very risky. Not worth it for me. Bad bootloader flash or bad bootloader code and no fastboot after, thus no flashing stock bootloader.
Most will only need "unlock" to flash vendor, system, boot, and recovery.
dl200010 said:
I just used "fastboot flashing unlock", but I think if you use "unlock_critical" it might blow. I am not going to do this.
The "unlock_critical" allows you to flash a custom bootloader and radio. This may help if you want to flash a bootloader without the corrupt message, but it is only visible for a few seconds in booting. Flashing a custom bootloader is very risky. Not worth it for me. Bad bootloader flash or bad bootloader code and no fastboot after, thus no flashing stock bootloader.
Most will only need "unlock" to flash vendor, system, boot, and recovery.
Click to expand...
Click to collapse
So on the 6p, you need unlock_critical to flash the radio? Doesn't every factory image come with a new radio file? So you may have to blow the qfuse if you want the newest bootloader and radio file?
H4X0R46 said:
So on the 6p, you need unlock_critical to flash the radio? Doesn't every factory image come with a new radio file? So you may have to blow the qfuse if you want the newest bootloader and radio file?
Click to expand...
Click to collapse
He means "custom" (third-party/unsigned) ones. Official ones are okay.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
He means "custom" (third-party/unsigned) ones. Official ones are okay.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Click to expand...
Click to collapse
Same for stock radio? Yea, I wouldn't even risk flashing a custom Bootloader to anything! Not worth the consequences lol
H4X0R46 said:
Same for stock radio? Yea, I wouldn't even risk flashing a custom Bootloader to anything! Not worth the consequences lol
Click to expand...
Click to collapse
Same goes for the radio. I forgot to say that you can flash the factory ones no problem. They are signed.
dl200010 said:
Same goes for the radio. I forgot to say that you can flash the factory ones no problem. They are signed.
Click to expand...
Click to collapse
Thanks guys!
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Unless you are on the totally stock system then I wouldn't lock your bootloader.
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
mrcooter said:
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
Click to expand...
Click to collapse
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
If you relock your bootloader with anything other than a factory image you will brick your device.
vjyrdy said:
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
Click to expand...
Click to collapse
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
mrcooter said:
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
Click to expand...
Click to collapse
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
zlost1 said:
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
Click to expand...
Click to collapse
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Sent from my PH-1 using XDA Labs
swiftbones74 said:
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Click to expand...
Click to collapse
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
zlost1 said:
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
Click to expand...
Click to collapse
This ain't the rocket and thread forum or the whatever dumb other thing forum so it really doesn't matter what the answer is.
Sent from my PH-1 using XDA Labs
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
zlost1 said:
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
Click to expand...
Click to collapse
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
MOD EDIT
You are one trippy person ? if you really feel the need to post about your LG phone in the mata thread go right ahead buddy.
Sent from my PH-1 using XDA Labs
MOD EDIT
It's worth noting that the Essential PH-1 uses an A/B partition system so any advice given here would not be helpful in the slightest for devices that don't have the same file system. Quickly doing a search of your phone reveals it's not an A/B partitioned system so following advice here could potentially lead to you actually destroying your phone.
could you lock the BL once rooted if in fastboot mode it lists device tampering = false?
Wonderful reply
tech_head said:
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
Click to expand...
Click to collapse
Thanks, this reply should be pinned to the top of the thread. It is crucial information for our dear noobies
swiftbones74 said:
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
Click to expand...
Click to collapse
Just an opinion, but...there are rules for posting in forums that Dev's, no matter how over worked and underpaid/appreciated should follow as well. Teach by example not proxy. Applaud the calm gentleman who responded with eloquent grammar and poise.
NaterTots said:
Unless you are on the totally stock system then I wouldn't lock your bootloader.
Click to expand...
Click to collapse
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
rossrosh007 said:
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
Click to expand...
Click to collapse
I don't know.
Well hello good sir or mam!
I seem to be in quite the pickle, but i hope you can help
You see, i just bought this phone on amazon and will be arriving in two days. I read the review and the hardware is amazing but the software makes you want to question why haven't murdered a tub of puppies.
The cute kind. :angel:
Well I want to put Lineage OS 15.1 on there. But i haven't the faintest idea how...
WAIT! Hold that mouse! I know what your about to do.
I have searched the forums and watched tons of you-tube videos but none say how to do it properly or the guy talks with such a accent i cant understand him.
So can someone post like a super noob guide for me.
All i know is that i want a new OS but no idea on how to get it.
:highfive:I look forward to your assistance. :highfive:
Please and thank you!
If you have no clue about ROM management, better read instructions on our forum 2-3 times! You can soft brick it really easy, if you dont know what to do..
For LOS you need:
Custom Recovery (TWRP)
Unlocked bootloader
LOS ROM
Their are forms on this already.
What pro3 are you getting?
Sent from my LEX720 using xda premium
mchlbenner said:
Their are forms on this already.
What pro3 are you getting?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
LeEco | Le Pro3 Unlocked Smartphone, 5.5" Display, 64GB Storage, 4GB RAM, 16MP Main Camera, 4K Video, Dolby Audio, U.S. Warranty (Gold)
Sony make.belive said:
If you have no clue about ROM management, better read instructions on our forum 2-3 times! You can soft brick it really easy, if you dont know what to do..
For LOS you need:
Custom Recovery (TWRP)
Unlocked bootloader
LOS ROM
Click to expand...
Click to collapse
Ok, but I saw that twrp can brick a phone, it’s in the top sticky thread
Kingofsquirrelz said:
Ok, but I saw that twrp can brick a phone, it’s in the top sticky thread
Click to expand...
Click to collapse
That's for the x722. Just don't flash stock 26s through TWRP. Not difficult to understand. Doesn't apply to other versions of the Pro3 like the x720 or x727.
https://forum.xda-developers.com/showpost.php?p=71566961&postcount=203
marcukial said:
https://forum.xda-developers.com/showpost.php?p=71566961&postcount=203
Click to expand...
Click to collapse
OK, nice, im starting to wrap my head around this, i downloaded twrp and the bootloader but both say to "put into adb directory on your PC"
how do i do that?
sk8223 said:
That's for the x722. Just don't flash stock 26s through TWRP. Not difficult to understand. Doesn't apply to other versions of the Pro3 like the x720 or x727.
Click to expand...
Click to collapse
OK, so, how do i tell if mine is a x722 or not. i looked on the amazon page and it didnt give the info.
Also what is "Stock 26" and how do i avoid it?
Kingofsquirrelz said:
OK, nice, im starting to wrap my head around this, i downloaded twrp and the bootloader but both say to "put into adb directory on your PC"
how do i do that?
Click to expand...
Click to collapse
Just in case you haven't yet you need to install adb and fastboot first.https://forum.xda-developers.com/showpost.php?p=48915118&postcount=1
marcukial said:
Just in case you haven't yet you need to install adb and fastboot first.https://forum.xda-developers.com/showpost.php?p=48915118&postcount=1
Click to expand...
Click to collapse
I do, i got the abd and fastboot files needed, and i also changed the address on the advanced setting option on my computer
I always put the files like twrp on my desktop.then before I flash the file I will change directory to Desktop then flash it.
Kingofsquirrelz said:
OK, so, how do i tell if mine is a x722 or not. i looked on the amazon page and it didnt give the info.
Also what is "Stock 26" and how do i avoid it?
Click to expand...
Click to collapse
Look on the box, in the manual, at the back of the phone. The easiest way to tell is if you've got a Snapdragon 821 or not. If you do, you have an x720 (or x727, which is the U.S. version).
i did rooted the oneplus 6t to get the oneplus McLaren logo on startup by a normal 6t.
with the twrp flash.
i did install the McLaren module by magisk and works for so far.
phone boots up with no probs at all except one thing i am trying to figure out.
when the phone boots up there is a for a few seconds the message bootloader unlocked with a Orange triangle and goes then into the McLaren logo and starts up further as a normal unrooted 6t.
anyways no i am trying to figure out how i can get rid off/bypass that google bootloader unlock message in the first few seconds at startup.
found out that it is possible to get rid of the message by other brands/types of phones.
but i cant put the things together howto do this on a 6t nor find any related information on the web.
it is not a really big issue/problem for me.
but i want to write a howto get the complete McLaren experience on a normal 6t included fingerprint animation themes and the ar thing (for the booklet) so far i have everything complete except that message.
and to make a complete howto i also want to include how to get rid of that message.
also i found out that there is a way to buy the McLaren back cover so it Will look and handle as a McLaren edition and then the only difference Will be the extra ram what is missing and the warp charge (hardware related stuff which cant be changed).
any help on this one is appreciated.
PS i know i can get rid of the message by unrooting it and locking the bootloader again but that's not what i am looking for.
trying to keep the McLaren things altogether without going back to full stock (and without bricking the phone off course).
best regards.
Short answer is you can't.
bladestonez said:
Short answer is you can't.
Click to expand...
Click to collapse
I doubt that but lets wait what others have to say about it
Michel oneplus said:
I doubt that but lets wait what others have to say about it
Click to expand...
Click to collapse
It's been possible before with certain older devices, it's more complicated than you think. Chances are very slim.. closer to a not possible, if ever.
Addiso said:
It's been possible before with certain older devices, it's more complicated than you think. Chances are very slim.. closer to a not possible, if ever.
Click to expand...
Click to collapse
I indeed found out that it is very complicated on other phones but it could be done on older phones i Will wait the reactions on this xda thread thanks in advance for replying.
No need for this thread when there's already a WIP thread: https://forum.xda-developers.com/oneplus-6t/development/wip-dissecting-bootloader-aka-rid-t3878470
Thread in the wrong section (I don't even know in which section it should go, let's say Q&A), and subject is as mentioned above been discussed since years for OnePlus phones and the short answer will always be the same
YOU CAN'T GET RID OF THAT SCREEN WHILE UNLOCKED
Read the thread linked above should have been the first thing done
SpasilliumNexus said:
No need for this thread when there's already a WIP thread: https://forum.xda-developers.com/oneplus-6t/development/wip-dissecting-bootloader-aka-rid-t3878470
Click to expand...
Click to collapse
Go to that thread and you will find that it isn't possible.
You will need a signed boot loader from OnePlus that does not have the splash screen. Good luck with that.
It has to be there for Android trusted boot. Google requires it.
Thanks for pointing out the right topic didn't find it sorry forum posting it in the wrong section made a thread over here because xda said when i made a account i couldnt posted it in the developer section because i am a junior member (found that a bit funny,i am familiar with Linux backtrack, android rooting and all the stuff what Comes with it and also a bit programming with Windows) but thanks anyways topic can be closed i Will continue on the wip thread as a junior ? my wife got her degree in Windows networking programming but she has to ask me always hunny can You help me with something i cant solve (and i haven't got any degrees at school Just plain old hobby playing with software and stuff)
Some devices have fixed for that like https://forum.xda-developers.com/t/guide-remove-unlocked-bootloader-warning.4069207/
So stop say that "YOU CAN'T DO THAT"
Any news on this matter for OP?
Michel oneplus said:
i did rooted the oneplus 6t to get the oneplus McLaren logo on startup by a normal 6t.
with the twrp flash.
i did install the McLaren module by magisk and works for so far.
phone boots up with no probs at all except one thing i am trying to figure out.
when the phone boots up there is a for a few seconds the message bootloader unlocked with a Orange triangle and goes then into the McLaren logo and starts up further as a normal unrooted 6t.
anyways no i am trying to figure out how i can get rid off/bypass that google bootloader unlock message in the first few seconds at startup.
found out that it is possible to get rid of the message by other brands/types of phones.
but i cant put the things together howto do this on a 6t nor find any related information on the web.
it is not a really big issue/problem for me.
but i want to write a howto get the complete McLaren experience on a normal 6t included fingerprint animation themes and the ar thing (for the booklet) so far i have everything complete except that message.
and to make a complete howto i also want to include how to get rid of that message.
also i found out that there is a way to buy the McLaren back cover so it Will look and handle as a McLaren edition and then the only difference Will be the extra ram what is missing and the warp charge (hardware related stuff which cant be changed).
any help on this one is appreciated.
PS i know i can get rid of the message by unrooting it and locking the bootloader again but that's not what i am looking for.
trying to keep the McLaren things altogether without going back to full stock (and without bricking the phone off course).
best regards.
Click to expand...
Click to collapse
Try using Universal SafetyNet Fix module. It hides the unlocked bootloader from system too
0purple said:
Try using Universal SafetyNet Fix module. It hides the unlocked bootloader from system too
Click to expand...
Click to collapse
That module does nothing for the message that appears during boot.
Huskied said:
That module does nothing for the message that appears during boot.
Click to expand...
Click to collapse
My xiaomi device doesn't know that the bootloader is unlocked anymore, idk
0purple said:
My xiaomi device doesn't know that the bootloader is unlocked anymore, idk
Click to expand...
Click to collapse
That's the difference. You talking about Xiaomi in a OnePlus thread, very different breed. Many apologies fam.
On my other phones there's been a method to cover it up. For Motorola devices, there are many custom splash screens that are an overlay, covering the words with an image
Yeedatoy said:
On my other phones there's been a method to cover it up. For Motorola devices, there are many custom splash screens that are an overlay, covering the words with an image
Click to expand...
Click to collapse
It's impossible on this device because the OnePlus 6/6T is made different from other devices and that warning cannot be modified due to how it is made. This was the very first thing I set out to do and from searching on our forums I learned this to be true. It's impossible on 6/6t.
flash713 said:
It's impossible on this device because the OnePlus 6/6T is made different from other devices and that warning cannot be modified due to how it is made. This was the very first thing I set out to do and from searching on our forums I learned this to be true. It's impossible on 6/6t.
Click to expand...
Click to collapse
This is something a lot of people need to understand.
All androids devices are not equal. Depending on the device even the bootloader is different so the same tricks don't work on all devices.
Has their been ways for other devices? Yes by exploiting a hole in the system. This is still an actively updated device. You will have to wait a few before a hole like that can be found and more importantly not patched.
Now on the other hand. This is Xda. Nothing is impossible. So by all means dig in and find the hole and come back and share it. I'm sure there are those here willing o help.
Does anyone have the stock fastboot ROM for the McLaren 5G?
I might have one
DanDroidOS said:
Does anyone have the stock fastboot ROM for the McLaren 5G?
Click to expand...
Click to collapse
I am trying one now but its stuck on the mclaren start screen...If it works ill let you know about it otherwise please let me know if you find one.
@Lui914 You can't just say that without providing basic info like a filename and how you obtained it. I'd like to be wrong and swiftly apologize, but you probably just flashed the wrong file somehow and bricked your phone without the expected checksums or incompatibilities stopping you. I don't know why there'd be a McLaren start screen when we're looking for the T-Mobile variant, which is quite pink for every boot.
The only potential filename that's ever popped up for this phone is an OTA: oneplus7tpronroxygen_13.o.17_glo_017_1912042023.
Lui914 said:
I am trying one now but its stuck on the mclaren start screen...If it works ill let you know about it otherwise please let me know if you find one.
Click to expand...
Click to collapse
I think @LLStarks is right, I think you flashed the wrong file! The McLaren 5G ROM has the stupid T-Mobile bootanimation! If I find one I will definitely share it here!
Correct
DanDroidOS said:
I think @LLStarks is right, I think you flashed the wrong file! The McLaren 5G ROM has the stupid T-Mobile bootanimation! If I find one I will definitely share it here!
Click to expand...
Click to collapse
Yea sorry I didn't want to post anything that would mess your phone up as well. I was hoping you could just switch on over so I did flash the international rom and am now stuck on the screen becasue of it and not sure how to get back. All i wanted was my dang bluetooth to work in my car! Please le tme know if ya'll find out how to get back to stock. I can't find the rom anywhere.
Lui914 said:
Yea sorry I didn't want to post anything that would mess your phone up as well. I was hoping you could just switch on over so I did flash the international rom and am now stuck on the screen becasue of it and not sure how to get back. All i wanted was my dang bluetooth to work in my car! Please le tme know if ya'll find out how to get back to stock. I can't find the rom anywhere.
Click to expand...
Click to collapse
What I did was change my active. I flashed Omni and it boots but doesn't have data only wifi so I switched my active from 'b' to 'a' with "fastboot --set-active=a". It got me back to my McLaren rom, after you switch active I had to do "fastboot -w" to get it to boot. It will no longer update because I messed up slot 'b' which is why I'm looking for a fastboot ROM to fix it. Good luck!