Q: What if relock booloader and OEM unlocking is disabled from developer option - Essential Phone Questions & Answers

I'm always a bit hesitate to relock bootloader if I'm on custom rom or rooted. I'm wondering what will happen if:
1. bootloader relocked.
2. OEM unlock is disabled from Developer option
3. device goes into bootloop or cannot boot up
At this point, does this mean device is essentially hard bricked since in fastboot, there is nothing I can do?

You should never, ever relock a bootloader if you are on a custom rom or rooted.

That's the thing. I'd very much wanna get LOS and Android pay working. If not locking bootloader, Android pay will not pass SafetyNet check.
Sent from my PH-1 using Tapatalk

Rooted with magisk it will pass the SafetyNet checks.

as mentioned above if you are interested in having custom roms or rooting your phone you should not relock your boot loader, you are risking bricking your phone. There have been ways with Magisk(and other roots) on other devices (havent tried with the PH-1) to be rooted and still pass safetynet checks, bootloader should only ever be relocked if you are running 100% stock. Even when running stock i prefer to have the bootloader unlocked being able to flash a different recovery is worth having to pull out a card to pay for stuff (for me).

nrage23 said:
Rooted with magisk it will pass the SafetyNet checks.
Click to expand...
Click to collapse
It seems magisk 14.3 having some issue for SafetyNet.
It works right after phone boot up, SafetyNet works. After certain time, it failed. Only reboot phone can make it works again.

As far as I know if your on stock ROM rooted and bootloader unlocked, ANDROID PAY will work with MAGISK

imna357 said:
As far as I know if your on stock ROM rooted and bootloader unlocked, ANDROID PAY will work with MAGISK
Click to expand...
Click to collapse
thanks. I'll check it out.
I'm currently using Oreo beta along with the magisk boot image prepared by invisiblek and seeing this SafetyNet issue. Maybe Nougat stock is better in handling this situation.

Related

Any root method for C432B380?

I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377

Oreo Future Updates, will it re-lock bootloader

Will future OTA Oreo updates re-lock the bootloader. I unlocked mine to root using ADB tools. I then installed MagiskManager 5.6.0, It worked then it asked if I wanted to install Magisk v15.3. I tried to install v15.3 but after it said Magisk was not installed and at the same time I also found I had lost root. The phone appears to work OK so rather than mess about with flashing a new Oreo rom, I wanted to know if the next OTA update will automatically lock the bootloader.
Also, will it cause any harm if I try and re-root.
amzazine said:
I wanted to know if the next OTA update will automatically lock the bootloader.
Click to expand...
Click to collapse
No
amzazine said:
Also, will it cause any harm if I try and re-root.
Click to expand...
Click to collapse
Depends on what your are doing
There are a couple of guides on here that deal with installing Magisk.
I'm not sure why it happened, but after using Magisk Manager and then trying to install Magisk v15.3, my A1 has lost root. The bootloader is still unlocked and I don't want to mess with the phone any more as its only a couple weeks old and has the original ota Oreo update. Is it possible to re-lock the BL by using ADB tools. If I put A1 into fastboot mode, connect A1 phone to win10 PC and enter adb command into powershell, then input... ' fastboot oem lock ' would that work or is it more complicated. I should add that it says Magisk is not installed I assume this is because I have lost root, when I try to re-install, it wont.
Another question. Is it safe to use ADB to lock the bootloader, or would I have to use Magisk Manager, even though it wont install it.
Also, will re-locking the bootloader wipe all data and effectively reset the phone.
Just read this post so not very confident.

Can we flash custom rom without rooting the Mi A1 ?

Flashing the custom rom with rooting the device make the device less secure and we cannot use the internet banking applications so , can we flash the custom rom without rooting the device ! If, yes then what will be the procedure !?
altafalam540 said:
Flashing the custom rom with rooting the device make the device less secure and we cannot use the internet banking applications so , can we flash the custom rom without rooting the device ! If, yes then what will be the procedure !?
Click to expand...
Click to collapse
Jajajajajaja sorry but your question is very funny????
But no, it's not possible install custom ROM without root
I would think one can flash when booted into TWRP. One needs to be unlocked though.
The custom ROM you flash does not need to be rooted either.
In fact one can boot into TWRP from fastboot. So one does not even need TWRP on the device itself.
You do not need to root your device to use a custom ROM. But if you wanna flash GApps, then you need to root your device or it may not work as intended.
Wrong, Gapps can be installed from TWRP which has unlimited access to the system partition. In that sense, TWRP is "rooted". But this has nothing to do with the installed firmware being rooted or not.
altafalam540 said:
Flashing the custom rom with rooting the device make the device less secure and we cannot use the internet banking applications so , can we flash the custom rom without rooting the device ! If, yes then what will be the procedure !?
Click to expand...
Click to collapse
Wow this thread exploded with mis-information.
You can install custom ROM's unto your device via TWRP, as well as flash GAPPS and any custom kernels, mods etc you'd like WITHOUT having to gain superuser access within the ROM itself.
You WILL however require to unlock your bootloader that, at least as far as I know, WILL trigger safety net and thus render certain applications (like said banking apps) unusable. To avoid this you can flash magisk, an alternative root solution that also masks certain aspects of the device that allows the device to pass safetynet while retaining root.
There are plentiful amounts of tutorials out pretty much everywhere that will allow you to easily unlock your bootloader, install twrp and root w/ magisk if desired, etc.
DECHTECH said:
Wow this thread exploded with mis-information.
You can install custom ROM's unto your device via TWRP, as well as flash GAPPS and any custom kernels, mods etc you'd like WITHOUT having to gain superuser access within the ROM itself.
You WILL however require to unlock your bootloader that, at least as far as I know, WILL trigger safety net and thus render certain applications (like said banking apps) unusable. To avoid this you can either A. Relock your bootloader after flashing custom rom (should work) or B. Flash magisk, an alternative root solution that also masks certain aspects of the device that allows the device to pass safetynet while retaining root.
There are plentiful amounts of tutorials out pretty much everywhere that will allow you to easily unlock your bootloader, install twrp and root w/ magisk if desired, etc.
Click to expand...
Click to collapse
I don't think you can relock the bootloader when on a custom rom. This will probably brick your device since it will fail the checks of the locked bootloader and then you will have a bricked device with a locked bootloader.
So yeah, you also spread some misinformation I suppose which is even more dangerous than what the other users suggested.
+1, no way you can relock your bootloader after installing a custom firmware. Bootloop guaranteed.
michkost858 said:
I don't think you can relock the bootloader when on a custom rom. This will probably brick your device since it will fail the checks of the locked bootloader and then you will have a bricked device with a locked bootloader.
Click to expand...
Click to collapse
Lannig said:
+1, no way you can relock your bootloader after installing a custom firmware. Bootloop guaranteed.
Click to expand...
Click to collapse
Could have sworn you could do this but I guess I was wrong, sorry for that.
Edited original post.

G950F Pie Root

Will the current version of TWRP and Magisk work or should I wait a while?
Acclaiming said:
Will the current version of TWRP and Magisk work or should I wait a while?
Click to expand...
Click to collapse
Twrp is device specific not android version specific
Magisk generally works with all android versions
If you can unlock your bootloader your set to go
TWRP works on 955F on pie beta, but as I said there, it doesn't work on rooted or debloated devices.You can use TWRP, but without root.
I have pie. Twrp recovery, rooted magisk 18 and heavily debloated. Works fine.
Don't listen to him
how did they do it to root it? I have android foot beta 950F, thanks
is there an tutorial to root pie??? cos i unlocked bootloader, (oem Unlocker) but in downloadmode i still get the rmm prenormal message....
lambik333 said:
is there an tutorial to root pie??? cos i unlocked bootloader, (oem Unlocker) but in downloadmode i still get the rmm prenormal message....
Click to expand...
Click to collapse
This should help with the RMM state,twrp and root. As far as I am aware it's still the same process as with Oreo/nougat
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Very Interseting
Im sorry, but please can you explain how you done it?
I don't know if the Aroma debloater will work with it oder other mods like dolby atmos und build.prop tweaks..
still93 said:
I have pie. Twrp recovery, rooted magisk 18 and heavily debloated. Works fine.
Don't listen to him
Click to expand...
Click to collapse
Hi,
Does anyone know if it is currently possible to flash the update from twrp without a reset and maintain root? Or if root if possible how to achieve it?
I have the same question, any way to do it without wiping all data..? or rooting without TWRP impossible? like kingroot or something.
Pie update (official) messed my s8 and it got stuck on bootloop, i had to flash trough odin and now i have broken knox forever, great.. I don't want to wipe all data again and I would like to possibly unroot if i root.

Unlocked bootloader, no root: how to fix GPay?

I've unlocked bootloader with the official tool but didn't do root. Now I have trouble with GPay saying that my device cannot be used for paying.
I don't need root now. So, the question is: is there any way to relock bootloader without rooting the device, installing TWRP, Magisk etc? Or, maybe, can I just trick GPay into believing that everything's fine without relocking?
Any response would be strongly appreciated.
Booolat said:
I've unlocked bootloader with the official tool but didn't do root. Now I have trouble with GPay saying that my device cannot be used for paying.
I don't need root now. So, the question is: is there any way to relock bootloader without rooting the device, installing TWRP, Magisk etc? Or, maybe, can I just trick GPay into believing that everything's fine without relocking?
Any response would be strongly appreciated.
Click to expand...
Click to collapse
If you don't need root, why did you unlock it in the first place? You can't relock your bootloader if you have unlocked it with official tool. But by installing Magisk, you can use GPay. If you don't need root, disable it in Magisk settings.
anagramgenius said:
If you don't need root, why did you unlock it in the first place? You can't relock your bootloader if you have unlocked it with official tool. But by installing Magisk, you can use GPay. If you don't need root, disable it in Magisk settings.
Click to expand...
Click to collapse
I was trying to resolve some strange unmanageable issue with BT headphones volume and sound quality by installing Ainur module. But somehow it resolved on its own during the unlocking process (due to reset, I guess).
Anyway, I've got the answer: no GPay without root and Magisk. Thank you!

Categories

Resources