I have root and twrp recovery but a locked bootloader. The phone is set up perfect.
Can i do a twrp backup, unlock bootloader, then restore twrp backup, or will the bootloader just be relocked when the backup is restored?
I have tried searching but it seems everyone else unlocks bootloader 1st.
thanks in advance
Bootloader status is independent of those partitions so it doesn't matter. Your bootloader won't get automatically locked/unlocked like this...
But remember that all DRM secured features of Sony are gone if you unlock BL (TA partition gets wiped).
I was wondering if there is a way to disable the warning screen or relock the bootloader while keeping the root and recovery.
Everytime i try it it say it can no longer find a valid operating system.
plain and simple, not there is no way for our phones. if your bootloader is unlocked, the warning screen will always show and your bootloader must be unlocked in order for magisk to run and root to be allowed.
Currently no. The reason is that to have root, you have to have a patched boot image, and to have a patched boot image, you need to be able to have an unlocked bootloader to allow flashing of /boot from recovery. "Locked" rooting would involve an exploit that would undoubtedly get fixed quickly. Also, keep in mind that the Pixel 2/XL do not have dedicated recovery partitions, but that recovery itself also resides in /boot.
Hi.
First: Sorry My bad English.
So. The base is: FRD-L09C432 officially upgraded to Oreo. Data partition encrypted, bootloader and FRP unlocked status, TWRP installed and my phone rooted with Magisk. After some read in this and other forums I edited the phone fstab files, to delete data encryption. After edit this files I do a "Format Data" in TWRP. After that the FRP status changed from "Unlocked" to "Locked", and in Settings the "OEM Unlock" disabled and grayed. Bootloader status stay in unlocked. So this is the current state. The Recovery not changeable from TWRP to stock, because FRP-Lock status.
So, My questions is: How do I unlock FRP? If I rollback to Nougat, the FRP is unlock or not, or what? How do I rollback with TWRP? HurUpdater? What can I do, because if I rollback and FRP stay locked, I won't flash back the TWRP. And if this occur, I can't root my phone, and have other problems.
Ideas?
Did you try to unlock bootloader via fastboot?
cococchio said:
Did you try to unlock bootloader via fastboot?
Click to expand...
Click to collapse
bootloader already unlocked. I won't try to relock, because 1 months ago I relocked, and my phone is bricked. Won't boot to system, and just DC-Unlocker helps to bring back my phone to life.
Good to know. I am also bricked but I was able to unlock bootloader via fastboot. I only have access to error mode.
flash via download mode and wifi
hi all,
I have an unlocked bootloader but not root, and the stock ROM (never changed)
I've read this guide to go back to stock but as I'm not rooted or have a custom rom, would it be possible to simply re-lock the bootloader for the nasty boot up screen message to disappear?
cable_guy said:
hi all,
I have an unlocked bootloader but not root, and the stock ROM (never changed)
I've read this guide to go back to stock but as I'm not rooted or have a custom rom, would it be possible to simply re-lock the bootloader for the nasty boot up screen message to disappear?
Click to expand...
Click to collapse
If you just unlock the bootloader without changing any partitions (like boot, system, recovery etc), you can simply relock the bootloader with the unlock code. But by doing that, the phone will fully factory reset, you may lose all data without backup.
Hello again! I have a problem, i have the original firmware and the tool to flash it in case anything goes wrong (MTK Client), so i unlocked the bootloader, the problem is that when you unlock the bootloader, the baseband says (020null) and imei is unknown. I tried to restore my own nvcfg, nvram and nvdata to no luck, when I lock the bootloader, they appear again without flashing anything. So there must be something in the system that checks if you have the bootloader locked or not... I want to know how to disable it because I want to have root (I have rooted it with no issues, but i want my imei you know), i thought init.rc may have something to do with it, here is it (https://gist.github.com/ThePinkLyna/a43e65572896a57af2624610f74d00f2).
By the way my phone is an Alcatel 5007G, MTK 6762. Any ideas in where could be the block? The bootloader? An script in the system? There must be a way, right?
Re-lock the bootloader.
Android can get rooted without having the bootloader got unlocked before.
It's the Android kernel that checks if bootloader is locked or not.
xXx yYy said:
Re-lock the bootloader.
Android can get rooted without having the bootloader got unlocked before.
It's the Android kernel that checks if bootloader is locked or not.
Click to expand...
Click to collapse
How to get root without unlocking the bootloader? Because if i patch boot.img to use with magisk, then it goes into red state because secure boot. I know, the last thing you said, but i was talking about the system, there must be something which checks if the bootloader is unlocked or not and if its unlocked then it blocks the imei, i doubt android does that by default.
well, not answer to your original question, however try bootless-root method. but read warnings about limitations on locked bootloader (do not modify boot, system, ...)
TheAndrew579 said:
How to get root without unlocking the bootloader? Because if i patch boot.img to use with magisk, then it goes into red state because secure boot. I know, the last thing you said, but i was talking about the system, there must be something which checks if the bootloader is unlocked or not and if its unlocked then it blocks the imei, i doubt android does that by default.
Click to expand...
Click to collapse
You can doubt all, it's on you. Also take note that
1. every Android device comes shipped with a recovery partition by default,
2. you can't use a Custom Recovery like TWRP to restore lost IMEI.
are you sure it's bootloader lock state and not Magisk? I have same issue with Redmi 6, when booted in Magisk from fastboot baseband is unknown. normal boot baseband reappear (nothing flashed)
my suspect is magisk mount overlay (have to dig more into)
https://github.com/topjohnwu/Magisk/issues/426
What Magisk version you tried?
xXx yYy > /dev/null
aIecxs said:
are you sure it's bootloader lock state and not Magisk? I have same issue with Redmi 6, when booted in Magisk from fastboot baseband is unknown. normal boot baseband reappear (nothing flashed)
my suspect is magisk mount overlay (have to dig more into)
https://github.com/topjohnwu/Magisk/issues/426
What Magisk version you tried?
xXx yYy > /dev/null
Click to expand...
Click to collapse
Its not Magisk, because the problem starts happening when i unlock the bootloader, when i unlock it (Without installing magisk or flashing anything), and androids appears again, i go to info and it says baseband = 020null and imei unknown, if i flash magisk, then i get root but still no imei.
Im talking about the original firmware, unlocked bootloader = no imei, when i lock it again after uninstalling magisk (By flashing the original boot.img) then the imei appears again.
aIecxs said:
well, not answer to your original question, however try bootless-root method. but read warnings about limitations on locked bootloader (do not modify boot, system, ...)
Click to expand...
Click to collapse
And my android security version is newer, so that method wont work, still, i want root so i can uninstall system apps, so an unlocked bootloader is a must, but how exactly if when i unlock it i lose the imei? Thats the problem
you don't need root to get rid of system apps. this will do it. be careful what you're doing, in case of bootloop the only way left is factory reset. do a backup before.
Code:
adb shell cmd package disable --user 0 <pkgname>
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com