Hello, not sure if someone has asked the same question before but is it possible to relock the bootloader with a custom ROM and not MIUI official ROM?
The main reason behind the question is I want a pure pixel experience ROM and due to an unlocked bootloader and root, I can't use some banking and company apps even with MagiskHide so I'm thinking of relocking the bootloader and unroot and at the same time maintaining the custom ROM.
I'm using a Pixel Experience ROM btw.
Thank you.
vibranze said:
Hello, not sure if someone has asked the same question before but is it possible to relock the bootloader with a custom ROM and not MIUI official ROM?
The main reason behind the question is I want a pure pixel experience ROM and due to an unlocked bootloader and root, I can't use some banking and company apps even with MagiskHide so I'm thinking of relocking the bootloader and unroot and at the same time maintaining the custom ROM.
I'm using a Pixel Experience ROM btw.
Thank you.
Click to expand...
Click to collapse
Afaik not possible..i mean if u lock bootloader on any custom rom or even official with modifications u will stuck at bootlooop. dm verity
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Which version of magisk are you using, it should be better with hiding stuff in the latest verison
huyizheng said:
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Click to expand...
Click to collapse
Interesting, I am wondering if it is MIUI thing.
malimukk said:
Which version of magisk are you using, it should be better with hiding stuff in the latest verison
Click to expand...
Click to collapse
Thank you, I am using Magisk 18. Some of my apps still force me to close even after I added it in MagiskHide.
huyizheng said:
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Click to expand...
Click to collapse
You dont have to do anything. Simply Install their Rom and IT will Work directly. Used Banking Apps etc without a Problem on their Rom
vibranze said:
Interesting, I am wondering if it is MIUI thing.
Thank you, I am using Magisk 18. Some of my apps still force me to close even after I added it in MagiskHide.
Click to expand...
Click to collapse
I've found with a few apps that I had to turn off USB debugging as well, before it would let me use them. Maybe give that a try.
Related
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
ndarkside93 said:
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
Click to expand...
Click to collapse
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Sent from my sailfish using XDA Labs
nednednerb said:
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Click to expand...
Click to collapse
Very true, but on the pixel with the November update, safety net checks for bootloader unlock, but I think Franco kernel can hide it to pass the check, if there is no root.
I want to have a unlocked bootloader. Don't really need root. I'm guessing device still fails safety net if unlocked? Is custom kernel the easiest way or is there another method. Haven't played around for a year.
Sent from my Pixel 3 using Tapatalk
milan187 said:
I want to have a unlocked bootloader. Don't really need root. I'm guessing device still fails safety net if unlocked? Is custom kernel the easiest way or is there another method. Haven't played around for a year.
Click to expand...
Click to collapse
Custom kernel is the easiest way :good:
Badger50 said:
Custom kernel is the easiest way :good:
Click to expand...
Click to collapse
I'm not a custom kernel. Can you please guide on how to remove the unlocked bootloader message?
varun.gid said:
I'm not a custom kernel. Can you please guide on how to remove the unlocked bootloader message?
Click to expand...
Click to collapse
There is no way to remove it unless you keep the bootloader locked. Sorry man.
I unlocked my bootloader, rooted the device and then decided to re-flash stock since my work apps won't work saying it is rooted. Magisk would not really hide the root from the apps. I left the bootloader unlocked and I see no difference from before I unlocked it. I do not pretend to know anything about safety net
Any recommendation on which ROM should i use for my 1st custom ROM? Is the pixel experience any good? i mean is there any major issues about this ROM? Is it also safe to flash it on my current MIUI version whihc is MIUI 10.2.2.0 PDGMIXM its the global version. I already unlocked my bootloader and currently searching for tutorials on how to install TWRP and which one should I install in this device. Many thanks in advance if anyone responds on this post.
genesismarkus420 said:
Any recommendation on which ROM should i use for my 1st custom ROM? Is the pixel experience any good? i mean is there any major issues about this ROM? Is it also safe to flash it on my current MIUI version whihc is MIUI 10.2.2.0 PDGMIXM its the global version. I already unlocked my bootloader and currently searching for tutorials on how to install TWRP and which one should I install in this device. Many thanks in advance if anyone responds on this post.
Click to expand...
Click to collapse
It depends on how many costumizations you prefer. LineageOS and Pixel Experience do not have many extra features, while e.g. RR, Arrow and Havoc do. I experienced very few bugs in PE and LOS, but I haven't tried other custom roms. LOS has very clear installation instructions, which are also applicable to most other custom roms: https://wiki.lineageos.org/devices/polaris/install
We have an official TWRP version; you can find the instructions and download link on https://twrp.me.
Thanks
I just want to try a new look on my phone. Ill install those roms soon, is it ok to back up this current miui im using if i dont like the rom i installed right?
Yes, but some users (including me) reported failures of restoring full rom backups. So make sure you also use some alternative backup (e.g. the Migrate app) and save your backup files on an external device.
Use a full backup with TWRP. It worked for me every time. However there is a bug with phone protection (unlock code or fingerprint) - and you have to delete it manually in TWRP file manager.
But everything works fine.
danterape said:
Use a full backup with TWRP. It worked for me every time. However there is a bug with phone protection (unlock code or fingerprint) - and you have to delete it manually in TWRP file manager.
But everything works fine.
Click to expand...
Click to collapse
Pretty much easier is removing any PIN or fingerprint authorization before doing the backup.
enzo_cz said:
Pretty much easier is removing any PIN or fingerprint authorization before doing the backup.
Click to expand...
Click to collapse
so by doing what you said after flashing a new rom and it will be smooth sailing right?
genesismarkus420 said:
so by doing what you said after flashing a new rom and it will be smooth sailing right?
Click to expand...
Click to collapse
Not sure I get you. My apologies. Removing any PIN, fingerprint authorization before doing twrp backup is inevitable unless you want to modify your backup file the way somebody above described.
enzo_cz said:
Pretty much easier is removing any PIN or fingerprint authorization before doing the backup.
Click to expand...
Click to collapse
enzo_cz said:
Not sure I get you. My apologies. Removing any PIN, fingerprint authorization before doing twrp backup is inevitable unless you want to modify your backup file the way somebody above described.
Click to expand...
Click to collapse
btw, does unlocking the bootloader affects my phone from getting OTA? im still using the stock rom now MIUI 10.2.2.0 PDGMIXM.
genesismarkus420 said:
btw, does unlocking the bootloader affects my phone from getting OTA? im still using the stock rom now MIUI 10.2.2.0 PDGMIXM.
Click to expand...
Click to collapse
You can still receive OTA updates on the unlocked bootloader as long as you are using official Mi rom and you do not have twrp installed. TWRP may break OTA updates. At best case an OTA will just replace your twrp with stock recovery. Root also should not affect OTA updates. So no problem getting ota even if bootloader is unlocked as far as I am aware of
genesismarkus420 said:
Any recommendation on which ROM should i use for my 1st custom ROM? Is the pixel experience any good? i mean is there any major issues about this ROM? Is it also safe to flash it on my current MIUI version whihc is MIUI 10.2.2.0 PDGMIXM its the global version. I already unlocked my bootloader and currently searching for tutorials on how to install TWRP and which one should I install in this device. Many thanks in advance if anyone responds on this post.
Click to expand...
Click to collapse
I'm in the same case , I had a mi8 and installed a pixel experience and my brother took it and since he use s and until now everything works well he even knows that I changed the rom and that's not miui Lol
Do I bought I used mix 2s and I think I'm gonna install the lineage is because I want security patches and updates on the rom
Checked out realme's website and they state that unlocking and flashing roms does not void warranty but rooting the phone does.So what are the possibilities/things one can do with the phone while unlocking it but not rooting it.
Also is there a safe rooting method which doesnt leave traces after unrooting again? So that the device can be used in warranty.
Thanks in advance for any advice.
If you have Realme 5 Pro (not q) then you can still flash custom rom, recovery or basically anything with adb. It's just you won't be able to do root stuff on your phone but you'll need pc. Still you could flash custom kernel, rom, or ota update. Magisk is called systemless root for it does root your system without touching the system files so after uninstalling it and flashing stock rom realme service shouldn't ever be able to tell that your phone was ever rooted. I live in Hungary and my previous Xiaomi phone was installed with custom rom, kernel and Magisk root. Before taking it to Xiaomi service I did a clean flash, reverted everything to stock and warranty was still good to go. That'd be just an example. Don't know Realme how is with these stuff.
greenys' said:
If you have Realme 5 Pro (not q) then you can still flash custom rom, recovery or basically anything with adb. It's just you won't be able to do root stuff on your phone but you'll need pc. Still you could flash custom kernel, rom, or ota update. Magisk is called systemless root for it does root your system without touching the system files so after uninstalling it and flashing stock rom realme service shouldn't ever be able to tell that your phone was ever rooted. I live in Hungary and my previous Xiaomi phone was installed with custom rom, kernel and Magisk root. Before taking it to Xiaomi service I did a clean flash, reverted everything to stock and warranty was still good to go. That'd be just an example. Don't know Realme how is with these stuff.
Click to expand...
Click to collapse
Thank you so much for the prompt and clear reply.Really did clear a lot of stuff for me. Yes I do have realme 5 pro and the problems was with the audio jack output .Its terrible so wanted to flash dolby and / viper . I'll give adb a go then. Thank you again.
Firebolt1994 said:
Thank you so much for the prompt and clear reply.Really did clear a lot of stuff for me. Yes I do have realme 5 pro and the problems was with the audio jack output .Its terrible so wanted to flash dolby and / viper . I'll give adb a go then. Thank you again.
Click to expand...
Click to collapse
You're welcome. If indeed only root void warranty then you're free to flash to your linking almost everything via usb adb. Except for root ofc.
thank you again for the same.
Firebolt1994 said:
thank you again for the same.
Click to expand...
Click to collapse
After installing twrp via adb you can flash stuff from your sd card. Don't forget to always have a backup zip file of your stock rom in case something goes wrong. And don't forget to use backup in twrp for data partition sometimes when you feel you're about to do something risky that might flip your system's stability. I do that all the time ?*
Yep I will.Its a new phone so more of a reason to take precautions .
Firebolt1994 said:
Yep I will.Its a new phone so more of a reason to take precautions .
Click to expand...
Click to collapse
Exactly. Have fun but take care.
bootloader unlock 7 ROOT
Does bootloader unlock will prevent running of Bank Applications?Can this Realme5Pro be rooted and installed Twrp using Kingoroot/
Waiting with thanks.
Please any one give an advice
TWRP
If TWRP is installed via ADB in my unrooted Rm5P will it become rooted and prevent bank applications?
pnsdhrn said:
If TWRP is installed via ADB in my unrooted Rm5P will it become rooted and prevent bank applications?
Click to expand...
Click to collapse
Magisk has an option to hide from those apps, I used it all the time with secure banking apps
If I unlock bootloader and flash TWRP, can this TWRP can be used as my stock recovery further for flashing zips(not custom ROMs)? Also will Bank apps work in this set up without any problems?
Yes, you can use TWRP to flash anything. Yes, bank apps will work as long as you have magisk installed.
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
I have updated to android 12.. will I need to revert in order to do any flashing?
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
systemshock869 said:
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
Click to expand...
Click to collapse
Well, kind of. It now exists as a Magisk module. You need to install Riru module and LSposed module to get an "Xposed like" feature.
BUT, latest Magisk versions (Beta and Canary who are more compatible with Android 12) now have a new feature called zygisk. That feature is not compatible with Riru and LSposed. So if you're going to LSposed, use latest stable Magisk, which still works.
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
systemshock869 said:
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Click to expand...
Click to collapse
I'm running stock with latest Magisk Canary and besides that, I only use my Addon features module (which adds some cool custom stuff into stock ROM).
systemshock869 said:
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
Click to expand...
Click to collapse
The only ROMs I know that exist for Pixel 4a are ABC and Proton AOSP ROMs. But, if I'm not mistaken, there aren't any ones built for Android 12.
Cheers!
Thanks so much! It's always frustrating, as a casual user, to come back to the mod scene and have to try to re-learn the current meta for both android modding and your particular device by wading through scattered forum posts.
Typhus_ said:
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
JohnC said:
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
Click to expand...
Click to collapse
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
systemshock869 said:
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
systemshock869 said:
Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
Just that some Xposed apps and modules only work with android 10, and I don't see any features of A11 or A12 that I would use.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
systemshock869 said:
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
Click to expand...
Click to collapse
SafetyNet will fail as soon as you unlock your bootloader.
There is a Magisk module provided by kdrag0n that fixes that but the free version, for the time being, needs Riru and Lsposed to work properly. That means you need to root your device using stable Magisk 23.0 if youwant to fixe SafetyNet right away.
The magisk patched boot.img version that I've shared on that post I've pointed out to you is Canary Magisk, where Magisk Hide feature no longer exists and it's incompatible with Riru and LSposed, as I've already said.
I'm running my device with SafetyNet failing and I couldn't care less since it's not problematic for my daily usage. Any app I cannot install through playstore can be installed using apkmirror. As for Magisk hide, it doesn't exit anymore but there's a "App deny list" that works as well to "hide" Magisk from banking apps (for instance).
I'm not using TWRP since there's really no need for it on Pixel 4a.
Everything can be done through fastboot and Magisk.
Anyway, if you really want to have SafteyNet passing, you need to manually patch stock boot.img (that you may find as well on that thread I've shared) with latest Magisk stable and flash that version. Afterwards install Riru, LSposed and SaftyNet fix by kdrag0n.
Cheers!
Typhus_ said:
I'm not using TWRP since there's really no need for it on Pixel 4a.
Click to expand...
Click to collapse
I use TWRP to do image Backups/Restores.
JohnC said:
I use TWRP to do image Backups/Restores.
Click to expand...
Click to collapse
I don't need to do that. Everything I have is backed up on my Google account.
Sure, /data and stuff like games or whatever needs to be downloaded again but, it's fine by me.
Furthermore, I don't use custom ROMs any more. Just stock Pixel ROM with my mods installed and I get by just fine, smooth and happy.
Cheers!
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
Depends on the ROM. LineageOS staff say to install the latest Android 11 image before flashing a LineageOS 18.1 rom. I'd assume that to be true for any other roms based on LineageOS.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Do u have to disable OTA updates to keep from a calamity? If so, are manual updates a pain? Can u retain ur data with manual OTAs?
Zaxx32 said:
Do u have to disable OTA updates to keep from a calamity?
Click to expand...
Click to collapse
Yes.
Zaxx32 said:
If so, are manual updates a pain?
Click to expand...
Click to collapse
No.
Zaxx32 said:
Can u retain ur data with manual OTAs?
Click to expand...
Click to collapse
Yes.
Everytime a new build comes up, download the factory image directly from Pixel Official firmware site, extract it, open flash_all.bat, on the update command you see a "-w" flag. Delete the "-w" and save flash_all.bat. Connect device to PC, reboot to fastboot and run edited flash_all.bat.
If you don't delete the -w, you'll lose your data.
Cheers!
Awesome....thanx!