I would like to install a custom ROM. But I really hate that screen when you first boot saying you have unlocked your phone blah blah. I would like to install a custom ROM with my boot loader unlocked. After it's up and running I want to re lock it so that message does not appear on boot. Also is it possible to disable the DM- verity check message as well when booting with a custom ROM? The goal is to have a custom ROM on the phone with no warning messages at all about anything.
That's not possible. To be able to re-lock you need a kernel that is signed for the locked bootloader which effectively makes it impossible to run any ROMs using any other kernel and recovery than stock OOS and also makes it quite a mess to update ROMs as you would have to unlock bootloader everyone to run TWRP and also unlocking and relocking also factory restores the phone everytime so you would lose all your data all the time. ?
It's possible to remove the DM message at boot. Look in the stickied Q&A thread for details.
Related
I need help with figuring how to solve my problem. Whenever I try to reboot it boots straight to hboot/fastboot. I can't update my system because of it. Can't unlock because it freezes at the screen where I choose to unlock or not. What should I do??
What have you done to your phone so far?
Have you unlocked your bootloader?
Have you installed TWRP Recovery?
Have you rooted your phone?
Have you flashed any new roms or kernels?
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle)
Please give a detailed description of the things you have done, the results of each of these things if any, and when your phone started rebooting straight to HBoot.
Also, is your phone the 32 bit US model, or the 64 bit Europian/Australian model?
There's still a chance your device's firmware is recoverable, but you probably shouldn't try anything until you get some advice from someone who has a lot of knowledge and a detailed description of how you ended up where you're at.
Good luck!
What have you done to your phone so far? I have unlocked it before, but end up re-locking it after failing to root it.
Have you unlocked your bootloader? I did and relocked it.
Have you installed TWRP Recovery? Couldn't and Can't
Have you rooted your phone? No
Have you flashed any new roms or kernels? No
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle) I can't enter recovery.
I have no .img files when entering hboot. I can't unlock because it freezes after choosing the unlock option. It shows entering recovery at the stop and a discalimer message at the botto and goes no where
How to fix the issue
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
bcbradley12 said:
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
Click to expand...
Click to collapse
You should not just lock the boot loader without first reinstalling the stock recovery! When you go to use the RUU if it doesn't see the stock recovery it's going to fail... First reinstall the stock recovery and then OEM lock then you can use the RUU!
P.S. I have no idea why you're replying to some post from 2014... This post was almost a year ago lmao...
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
bcbradley12 said:
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
Click to expand...
Click to collapse
OK but why are you replying to and worried about a post from a year ago?!?
Hey guys i was hoping someone out there can help me out. My phone just got the message to update to 5.0.1, but when i tried to update it, it would reboot then load to around 40% of the update then say error with a little android on his back with a red triangle on his stomach. So i thought this was because of my phone being rooted and unlocked, so i unrooted it and locked it using Nexus Root kit, and when i tried to update the phone to 5.0.1 it still gives me that error message. Some things to note my phone was ATT and i did delete the ATT bootloader immage and all of there ringtones when my phone was rooted. Please help
You mean AT&T Boot animation image?
Thats exactly why your OTA failed because you did changes to your /system/.
This is why I say if someone is going to do changes to /system/, you may as well flash a custom ROM because when you get OTAs, you're going to end up in your current position. There are a number of ways to approach this issue,
1) Return back to stock by flashing factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Unlock your bootloader -> Flash TWRP -> Flash a custom rom, kernel (optional), gapps, supersu
Either or will get your phone booting again.
zephiK said:
You mean AT&T Boot animation image?
Thats exactly why your OTA failed because you did changes to your /system/.
This is why I say if someone is going to do changes to /system/, you may as well flash a custom ROM because when you get OTAs, you're going to end up in your current position. There are a number of ways to approach this issue,
1) Return back to stock by flashing factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Unlock your bootloader -> Flash TWRP -> Flash a custom rom, kernel (optional), gapps, supersu
Either or will get your phone booting again.
Click to expand...
Click to collapse
Will doing the first thing you say bring back the AT&T Boot animation image, because i think i need it to go get a new phone, i think my phone is defective because the speakers with make random popping noises and will have white noise coming out from them even when im not playing anything.
Hello everyone, i am pretty bad at english so dont judge me becouse of this, and i am also noob here
So, i have problem. Why i cannot enter into recovery mode? I want to flash custom rom in my phone, i already have succesfully rooted with this method http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-10-5-1-0-283-t2872873 and now i want custom rom, but i cant flash it becouse i cant enter in recovery mode, whats the problem? And another question, did i need unlocked bootloader for custom roms? What if i need it but i have already rooted? Did its big risk to unlock bootloader for already rooted phone? Sorry guys i am noob here, thanks for help!
First, did you install any recovery like CWM or TWRP or Phil...
on the page it talks about XZDualRecovery: you may choose any other if you prefer
if not there is no GUI based recovery in Sony Software and you need to install them separately.
Since you have already Rooted the Phone..
1. Start with This, go to the below link and backup your TA partition
http://forum.xda-developers.com/showthread.php?t=2292598
This backup is very important if you want to revert back to factory image so keep it safe. WITHOUT THIS BACKUP DO NOT UNLOCK YOUR BOOTLOADER
2. Only on successful backup of TA, think about unlocking your bootloader. from your dialer dial *#*#7378423#*#*, and check if you have "Bootloader unlock allowed: Yes"
Unlocking the bootloader means you can install any of the ROM's available for your phone. If you don't want to unlock or cannot unlock then you may be restricted ROM's with Sony Kernels only.
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
happimeal said:
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
Click to expand...
Click to collapse
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Thank you for a great explanation.
If you ask the people at xposed modules they may be able to do something maybe....
5.1 still displays bootloader unlocked message.
cschmid44 said:
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Click to expand...
Click to collapse
I have installed h815 KDZ files using LGUP. When i reboot it still displays Bootloader unlocked message. I can not use bootloader unlock/lock guide as I have bootloader unlocked.
Any other means to get rid of the message.
bump for way to relock h815
suppose I unlock my bootloader, install custom recovery like TWRP and now, If I wish to RE LOCK my bootloader ( dont ask why), is it necessary to have the STOCK recovery installed before relocking or custom recovery will be fine?
Thanks.
Relocking the bootloader is NOT recommended. That said, you can and should keep TWRP if you choose to lock it.
Oh okay. I read somewhere that if you choose to re lock your bootloader you have to go FULL STOCK ( ROM + Recovery). I guess that might not be the case for nexus devices?
Relocking the bootloader will wipe your data, but it doesn't play cop and make sure everything is stock. All the bootloader does is pass off control of the device from the low level firmware that we cannot access to either the recovery or Android itself. Locking the bootloader only ensures that the possessor of the device cannot change the contents of the partitions from outside the device using ADB. A device with TWRP and a locked bootloader can still install custom ROMs, and possibly even root.
However, there is practically zero reason to ever lock the bootloader once unlocked, leaving people to wonder why you would want to.