Unlocked bootloader warning - Nexus 5X Q&A, Help & Troubleshooting

Hi, yesterday I rooted my N5X and I want to ask if is possible to block, hide that ugly warning when device starts
{
"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"
}
Please no custom ROM suggestions.
Thanks

I think there are a couple of threads on that in the themes and apps section. Give it a quick browse.

Thanks, found it here
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7

i see you already found a solution that works for you, nonetheless i wanted to give an answer for clarification based on what i understand on this matter:
there currently is no way of bypassing this message. it is possible to hide it by replacing the actual image this message consists of (e.g. complete black) though.
this does not change or get rid of the delay between powering the device and the display of the boot animation.
if the boot process gets delayed while displaying this message screen, i do not know (but it would make sense to me).

I'm curious, I currently am using a 1st Gen Moto G, and all we need to do is fastboot flash a logo.bin file to get rid of the unlocked warning. Can that be done here, using the logo.bin from the stock ROM?

@alfick3 there is no logo.bin on Nexus devices (I also had Moto G 1st gen. before ), if I understand how it works from thread which I linked above, it is a bootloader part, where is possible to change images, which are responsible for that ugly warning.

Thank you for that clarification.

Related

Chip and red cross

Hello, by mistake, I've flashed my SPL with a wrong version, and after that I was unable to downgrade or to restore with a good SPL. I tried to use RUU, and it brick my phone, I've got a chip and a red cross on a white screen each time it power on my phone.
Do you think it is possible to restore my phone with a HTC debug serial cable?
Thank you!
{
"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"
}
Ok, I solved the probleme, when I start the RUU updater, I hold the action button (track ball) down all the time until it finishes, and now my hero is completly restored!
I hope for those who got the same error will see my post, I was in a very bad trip!
lucky you, i hope i will never see such a sign on my hero... the chip really doesn't look good, more like a dead bug or something
I've just flashed my hero with the wrong SPL, that's break it, but the ROM Update Utility from HTC is very usefull in this kind of case ; I was no longer able to send it sdb requests or reboot on the recovery! But it update the offcial ROM to the latest..

Can't find full kernel version for rooting

Hey I apologize if this is a stupid question, what with the video, and this thread and all which is also giving advice but.... It doesn't seem to apply to me since I have a different model phone. >.>
http://forum.xda-developers.com/showthread.php?t=1383050
So here goes, when I'm trying to find my kernel version all I get is 2.6.35.11, with no other information whatsoever. I reset it to factory settings (I bought it used off of ebay) to see if that may help and there was no such luck. So I took the liberty of taking a screenshot hoping that would you might be able to help me This is only my second android device (my first was a g1 that I rooted back when texts entered information into the terminal) so be gentle.
{
"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"
}
Now I'm not sure what to do at the moment, but any help would be awesome. I would really like to root my phone so I can get all this garbage software off of it. Thanks guys!
Not sure what you are trying to accomplish, you are running 2.3.5 as your android version, you can use SuperOneClick to root it ...
Or you can Use Odin to flash a custom recovery , and root it ...
and then you can install whatever custom ROM you want as long as it is compatible with your phone ...
http://forum.xda-developers.com/showthread.php?t=1321582 easiest way to root your phone
I was going to try and link you to the method I found but I found something on AndroidNZ that I thought would work. I'm sorry if this sounds like a stupid thread, I'll try the things you guys just mentioned.

Bricked Asus Z00ED (missing boot.img)

I am suing TWRP for my phone and i am doing a reset to stock ROM and my phone had been stucked on Asus white logo. I read on some forum that some boot.img had been corrupted, can anyone upload the proper boot.img and other image i need to make my phone boot again.
{
"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"
}
Note : Sorry if this is unclear i am typing this in a hurry. I will update this post again. Thanks!
Since you obviously don't know much about Android phones, the simplest way for you to fix this is probably via ASUS Flash tool. There are guides on how to do that here on XDA.
Shad0wKn1ght93 said:
Since you obviously don't know much about Android phones, the simplest way for you to fix this is probably via ASUS Flash tool. There are guides on how to do that here on XDA.
Click to expand...
Click to collapse
i used adb fastboot tool and what other tools i should use? I also downloaded the firmware for Z00ED and stock ROM from asus what else did i missed? Thanks
Update : Here is my device info. Also, i cant access the oem recovery in fastboot

Red colored "Corrupted" error on boot fixed with Android 8.1 DP?

Not sure if anyone else got this fixed with 8.1 DP, but here is what I found. After flashing the 8.1 DP firmware, the corrupted error was gone and replaced with the normal yellow/orange warning that is typical when you unlock the bootloader. As a test I flashed the Jan 2018 7.1.1 flash, and the corrupted error was still gone! Even relocked the bootloader after re-flashing 7.1.1 to stock, and it worked with no errors, just like out of box stock.
If anyone still has a corrupted error this may help you as it did me. Don't know if it works on 3UK, or other carriers, as Im using T-Mobile USA with the normal version of the razer phone from the Razer web store.
If I understand correctly, you mean this (last image)?
{
"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 that appears, with Razer logos instead of that precaution sign ofc, I understand that the system image got tampered and DM-Verity was active in the boot partition, thus cleaning the device through fastboot solved that.

My htc one m8 bricked.

[IMG="https://drive.google.com/file/d/0B0wLR-Ay7ZvadFJXQmdycy1tejQwa29NTWlWSDNhTXVvaDNF/view?usp=sharing"]
My HTC one m8 bricked. Please suggest me the correct firmware or RUU. Recovery mode not working. Thank you
Its not bricked, its just the relocked bootloader preventing the modified system from running
Re-unlock your bootloader and it should boot ur modified system
{
"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"
}
YahyaChagri said:
Its not bricked, its just the relocked bootloader preventing the modified system from running
Re-unlock your bootloader and it should boot ur modified system
Click to expand...
Click to collapse
I Re-unlocked. and i tried to boot my firmware. I got replay like this image. Please help me.
i tried this firmware : RUU_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4_Radio_1.23.213311491.05G_20.57.4198.02_F_release_420431_signed_2.exe
Image Details.....
Thank you
The pictures don't show. Typing out the error message will work just as well.
Also, we need more info about the device. Do fastboot getvar all, and post the results. Delete IMEI and serial number before posting.
Also, need to know what you were doing when this happened, and what you were trying to accomplish. The OS number being blank on bootloader screen is usually due to using a very old, outdated version TWRP; or some custom ROMs will also make OS number blank.

Categories

Resources