Hi, I want to remove the warning screen after unlocking the bootloader. I have tried to replace images in logo.bin using MotoBootLogoMaker and python script but after flashing logo.bin orange1 image that is unlocked Warning screen was replaced by some text screen. I want to either remove that screen or replace some of my images or replace the text. I am attaching the image of the screen/ text I want to remove. This screen/text starts showing when I try flash logo.bin with any change. My goal is to remove this screen by keeping my custom OS installed.
Note: I have a custom os installed so I can not relock the bootloader if it is possible please let me know that.
{
"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 have the same problem, documented here:
How to remove Unlocked Bootloader warning on Moto G Play?
After unlocking the bootloader on the Moto G Play (2021), the unlocked bootloader warning appears graphically. After flashing an alternate logo.bin, the graphical message goes away, only to be subsequently replaced by a textual message saying...
forum.xda-developers.com
Is your phone android version 11?
nix_uid0 said:
I have the same problem, documented here:
How to remove Unlocked Bootloader warning on Moto G Play?
After unlocking the bootloader on the Moto G Play (2021), the unlocked bootloader warning appears graphically. After flashing an alternate logo.bin, the graphical message goes away, only to be subsequently replaced by a textual message saying...
forum.xda-developers.com
Is your phone android version 11?
Click to expand...
Click to collapse
My phone is on Android 10 and does this too.
So, after years, this TEXT message can not be removed ?
Mitezuss said:
So, after years, this TEXT message can not be removed ?
Click to expand...
Click to collapse
Afaik it lives in the abl partition which is signed by moto and verified by the SoC's bootrom. The bootrom will send you straight to EDL if the signature check fails. This is the very beginning of Android's chain of trust, where the bootloader lock is actually implemented, the chain is broken only after aboot is already loaded and has prompted you with the warning.
Related
Successfully Done
✓ bootloader unlock
✓ TWRP Recovery twrp-merlin-2.8.7-r7.img
All most try all super user
{
"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"
}
but after flash super user zip phone stop work at bootloader warning
same thing happen to me too..plz someone answer.
Prior to flashing supersu.zip, open twrp>advanced>terminal and enter (without quotes) enter the command
Code:
"echo SYSTEMLESS=true>>/data/.supersu"
Now SuperSU would install in systemless mode. The latest betas automatically install in systemless mode (I am using 2.74). Check if now it works.
Broadcasted from Zeta Reticuli
@Gravemind2015 is correct, that is the command needed to make it work... note that since you already tried flashing several SuperSU versions the old way, if it continues to be a problem you may need to reflash the factory images and verify booting prior to trying the mentioned systemless method.
mindjek07 said:
...after flash super user zip phone stop work at bootloader warning
Click to expand...
Click to collapse
I had the exact same issue on my 16 GB xt1540, running stock, fresh 6.0. Trying to root with SuperSU's (over TWRP), several versions up to 2.74, earlier versions down to 2.4 ish... I'd freeze at boot logo every time, after what appeared to successful installs.
After reading somewhere about someone else's luck, I gave 2.65 a go, a version I must not have tried (and one I notice is not on your screen shot), and it worked. I certainly didn't expect it to, and obviously it could be completely coincidental. I'm pretty sure, however, that I did nothing differently on that install to what I had done other times.
HTH
Buena suerte
Love you!!!
You pacified my pain.
Hello!
I was disappointed about some missing features in MIUI ( unable to unlock by bluetooth by not Xiaomi devices, no reliable notification LED,.. ) so I decided to flash Android P ( I know, it´s beta, but it´s AOSP ) by using the Xiaomi Flash Tool. I left the button at 'clean and lock', because I don´t wanted to go back in the near future - and this was a big mistake! The tool shown after flashing 'successful', but since then the Mix2s shows 'system destroyed - push power button to switch off' on booting. I get access by fastboot, but the bootloader is now locked....
I´ve tried to get access by deepflash, but the problem is, that if I connect it to USB the phone switches on and shows the mentined message - again and again. I´m not able to switch it off, to get the connection by qualcomm drivers to USB. I tried to push and hold the power button very long, push all buttons together and so on...
Has anyone an advice or can tell me about testpoints of the Mix2s ( if it has? )
{
"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"
}
When in edl mode, only nop and sig tags can be recevied before authentication.
Thanks!
In this thread, some users speak about test points. There is a photo of it
http://en.miui.com/thread-3123002-1-1.html
Edit: Method for Mi Mix 2, maybe this can help you...
http://en.miui.com/thread-1351514-1-1.html
You should send it to customer servt
You can try to contact xiaomi support, they can grant you access to unlock the bootloader without adding an account... However, there were only one or two guys in miui forum who were successful with that, for all the others xiaomi said they can't allow it
What happens when you try to unlock your bootloader? And why cant you unlock it again?
Enter Fastboot and unlock your bootloader again by using xiaomi mi bootloader unlocking tool.
same problem when i've flashed the beta, i had to unlock the bootloader again and the phone boots
A relative brought me his Moto G3 (XT1542) because it did not turn him on, he told me that the device was being updated and turned it off without knowing that something bad could happen, then he wanted to turn it on and send it to the following screen:
{
"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"
}
When "Start" was selected using the power button, the Motorola logo was displayed for a fraction of a second and the following screen appeared:
No matter which option is selected, "Bootloader Log" appears in all.
I have already tried to load the stock firmware but it does not take it, the same error continues.
I already thank you if you can help me solve this, it is already giving me headaches
Sorry for my bad English, I had to translate it because I don't speak that language.
As our phones are old this software may or may not work but give it a try,
https://support.lenovo.com/gb/en/downloads/ds101291
HTH
R1ffR4ff said:
As our phones are old this software may or may not work but give it a try,
hXXps://support.lenovo.com/gb/en/downloads/ds101291
HTH
Click to expand...
Click to collapse
did this work? I am stuck at the same problem
This error is indicative that either the ramdisk or kernel is corrupted. However, this is a soft brick and can be restored by using fastboot mode or RSD-Lite to flash an official firmware package to your device. Doing so will restore the device back to a factory stock state (but will not relock the bootloader if it has been unlocked. But, since relocking the bootloader carries no advantage except warranty related advantages, this is of little consequence). Official firmware packages for the Moto G 2015 can be found here https://mirrors.lolinet.com/firmware/moto/osprey/official/
Select the most current package for your variant. There are numerous guides here on XDA for restoring Moto devices using fastboot or RSD-Lite. The best fastboot guide I have seen is @lost101's tutorial & firmware repo here https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
(Official firmware is available at either of the above links. Just choose a link and find the most current build for your device.) @R1ffR4ff's earlier post linking the Lenovo Motorola Smart Assistant should also fully restore your device, and is less complicated than manually flashing an official firmware package. As such, the methods outlined in my post should only be used if the Smart Assistant did not do the trick.
I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
{
"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 can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
hpernaf said:
I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
I can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
Click to expand...
Click to collapse
Unlock the boot loader with fast boot if possible with Samsung phones. If you can flash twrp which I presume you can't, flash RMM bypass zip and hope for the best. Good luck.
So I got the first step, flashing TWRP. But, there's only a version of TWRP for the a10, would this work?
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
imalreadycrying said:
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
my phone doesn't show an oem bootloader unlock option
is it grayed out or do you just not see it
imalreadycrying said:
is it grayed out or do you just not see it
Click to expand...
Click to collapse
doesn't exist.
do you have dev options?
imalreadycrying said:
do you have dev options?
Click to expand...
Click to collapse
yes
send me a screen recording if you can, dev options should look like this
{
"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 have previously tried Kingo/King Root which worked on my KitKat Nabi tablet, I tried that on my a10e it failed. Root checker says there is no root for andr 11 on the a10e
whatever you do, do NOT use kingoroot, it basically installs a outdated version of SuperSU (which isn't liked by the community anymore because the original developer sold it to some random company) and bloats ur system up.
Yep, no OEM bootloader unlock option in dev settings
it may be possibly locked to your carrier. again, you can send me a screen recording or get an unlocked phone
My phone appears to be unlocked already, there is no sign of Verizon still being on here. I have since upgraded phones and the SIM card isn't in anymore.
Do I have to factory reset to fully get rid of the OEM?
i found this youtube video with some quick searching. it's in hindi but you can get the gist of it.
I most certainly dont have to disable automatic time right?
i don't know, after you get the option maybe you can set it back
i followed and nothing happened
did you reboot your phone after the fact?
yep, nothing works