Root Help, I need some advanced thinkers. - Nexus 6P Q&A, Help & Troubleshooting

For work I have to use mobileiron, which detects everything from root to the unlocked bootloader. I am not sure if it simply detects the unlocked bootloader or detects because of the warning that comes up, I would guess its the latter.
So not only can't I root, I can't unlock my bootloader in the current state. At the very least I would like to enable wifi tether, and I would do that through TWRP but then I can't unlock my bootloader. So way to relock without wiping.
So I guess the question is for people who don't know about MobileIron is will we be able to unlock the bootloader without setting off any other options? or is there way to at least edit build.prop without root or unlocked bootloader?
I guess ideally if I could root without unlocking the bootloader then unroot that would solve my problems. Thoughts anyone?

Here is a thought, although it might fail. You could unlock your bootloader, boot TWRP without flashing(fastboot boot twrp-rgvrg.img), make your changes, then boot back into the bootloader and relock it.
Still can't say for sure it would work and it will virtually guarantee your userdata be wiped.

Buy a second phone for work related purposes
I'd never spend so much on a phone just to let my company lock it down

You could always test out various configs and see what trips the software or not. You might be able to keep TWRP and root just turned off via supersu and everything work. Similar to android pay. You might not even be able to unlock the bootloader. Anything in between in possible.
Regardless it is pretty trivial to go back to stock and get everything locked back up again. So there is little risk in trying.
If it were me I'd try root and see if it worked. No? Ok, try to disable root with supersu. Will work or not. If not then make your host file edits for adaway and such and then completely remove root. See if that works.
You can also try to unlock the bootloader now as stock and see if it impacts the software. See exactly where it trips and prevents you from using it. Then work from there.
If nothing works, go back to 100% stock and lock the bootloader again. At least you gave it a go and had some fun for the evening. If I had to guess something in between will work and you can work around the limitations.

Related

Is it possible to root 4.3 locked bootloader without wiping all data

I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.
absinthesummer said:
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.
Click to expand...
Click to collapse
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Many thanks for a recent concise and informative post!
I was mainly being lazy with regards to not wanting to wipe everything and start again! I have helium installed to back everything up, guess Ill try to get a clear day to do it all........
GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hmm, wow thanks for the info. I never knew that! I just remember my first N7 every post said Step 1:Unlock your bootloader... lol had I known there was a way around it I might have tried it! But my first 16gb and my later 32gb were both unlocked and rooted within hours of buying them, so perhaps I just wasn't motivated enough to look for it.
I could see how or why that would be desirable though I guess... before I bought my S3, I had an LG L9 that the only way you could unlock the BL was to root then flash/update (LG Update tool hack) the firmware meant for the international version of the phone, which mirrored(!!!) the entire display both horizontally and vertically. Then fastboot the oem unlock and unlock the best way you could with that kind of touch screen lol, THEN re-flash standard rooted firmware for the US back over it... Seriously NOT worth it! Because even if the mirroring went away with the right firmware, the boot logo would still be mirrored and it was possible your screen would not return to normal. So forget about any warranty at that point. But, I gotta hand it to the devs on that device- now they were some motivated folks. They went to a lot of trouble to unlock that BL. You could root and install CWM without unlocking, but if you flashed CM and it was buggy or something, there was no turning back to stock. We were left with mods only unless we wanted to do alll that work.
That just reminds me how thankful I am for my S3 and N7s.

Questions about bootloader and otas

I'm getting a 6p for Christmas and I have a question.
Say the 6p is on Marshmallow, and I decide to unlock the bootloader (just that, no root or anything) on MM. Will I be able to update to 7.1.1 via ota (no I don't want to sideload or flash) without issues? Or is there a process to it like updating bootloader, vendor, radio or whatever else. Or does the Ota file contain the updated boot.img and vendor etc.
ricbaez said:
I'm getting a 6p for Christmas and I have a question.
Say the 6p is on Marshmallow, and I decide to unlock the bootloader (just that, no root or anything) on MM. Will I be able to update to 7.1.1 via ota (no I don't want to sideload or flash) without issues? Or is there a process to it like updating bootloader, vendor, radio or whatever else. Or does the Ota file contain the updated boot.img and vendor etc.
Click to expand...
Click to collapse
Yes, you can unlock then update via OTA. OTAs patch every partition permitted there are no modifications done to system and boot.
Sent from my Nexus 5X using Tapatalk
ricbaez said:
I'm getting a 6p for Christmas and I have a question.
Say the 6p is on Marshmallow, and I decide to unlock the bootloader (just that, no root or anything) on MM. Will I be able to update to 7.1.1 via ota (no I don't want to sideload or flash) without issues? Or is there a process to it like updating bootloader, vendor, radio or whatever else. Or does the Ota file contain the updated boot.img and vendor etc.
Click to expand...
Click to collapse
Why would you want to unlock the bootloader if you don't intend to root or install a custom recovery? I don't understand what the benefit is.
jhs39 said:
Why would you want to unlock the bootloader if you don't intend to root or install a custom recovery? I don't understand what the benefit is.
Click to expand...
Click to collapse
I actually intend to install megapixel rom
jhs39 said:
Why would you want to unlock the bootloader if you don't intend to root or install a custom recovery? I don't understand what the benefit is.
Click to expand...
Click to collapse
@ricbaez
No disrespect, but I would say why would you NOT unlock the bootloader on a Nexus? Especially when you first get the phone because unlocking wipes it. Unlocking the bootloader allows you to use MANY more tools in the event your phone boot loops or becomes unresponsive. There are dozens of threads where people are completely screwed because they did NOT unlock the bootloader and so cannot salvage their device with ADB/Fastboot. If you bought a Nexus, one of the selling points is that Google ALLOWS the owner to unlock the bootloader right in the Dev Options! Even if the OP is not going to root or install a custom recovery, if he/she does not unlock the bootloader, they are going to be S.O.L. if the phone won't boot. There are many examples of this since Google has gone to the monthly security OTA's and updates. Or... simply put, if you are unlocked you can flash full Google images and use ADB/Fastboot. If you are locked, you can only sideload an OTA with the stock recovery and that hasn't been working out well for so many people here on XDA.
To the OP. Recommend you unlock your bootloader first thing which will wipe the phone and start you out fresh. Unlocking the bootloader will not prevent you from receiving OTA's. Make sure your Google login works properly. Login. Logout. Login. Then do whatever the F you want with your phone, knowing you will have serious options to recover in the event things go south for any reason. Next would be installing TWRP. Good luck!
v12xke said:
@ricbaez
No disrespect, but I would say why would you NOT unlock the bootloader on a Nexus? Especially when you first get the phone because unlocking wipes it. Unlocking the bootloader allows you to use MANY more tools in the event your phone boot loops or becomes unresponsive. There are dozens of threads where people are completely screwed because they did NOT unlock the bootloader and so cannot salvage their device with ADB/Fastboot. If you bought a Nexus, one of the selling points is that Google ALLOWS the owner to unlock the bootloader right in the Dev Options! Even if the OP is not going to root or install a custom recovery, if he/she does not unlock the bootloader, they are going to be S.O.L. if the phone won't boot. There are many examples of this since Google has gone to the monthly security OTA's and updates. Or... simply put, if you are unlocked you can flash full Google images and use ADB/Fastboot. If you are locked, you can only sideload an OTA with the stock recovery and that hasn't been working out well for so many people here on XDA.
To the OP. Recommend you unlock your bootloader first thing which will wipe the phone and start you out fresh. Unlocking the bootloader will not prevent you from receiving OTA's. Make sure your Google login works properly. Login. Logout. Login. Then do whatever the F you want with your phone, knowing you will have serious options to recover in the event things go south for any reason. Next would be installing TWRP. Good luck!
Click to expand...
Click to collapse
You are right. I wasn't aware that people were having boot loop issues on phones running stock Android but that apparently is the case. But as long as USB Debugging and Allow OEM Unlock are ticked in the developer options you should be able to unlock the bootloader later through ADB if you need to. I assumed the warning about my phone being insecure since my bootloader is unlocked that pops up every time I boot was there for a reason. There is no security issue created by unlocking your bootloader?
jhs39 said:
You are right. I wasn't aware that people were having boot loop issues on phones running stock Android but that apparently is the case. But as long as USB Debugging and Allow OEM Unlock are ticked in the developer options you should be able to unlock the bootloader later through ADB if you need to. I assumed the warning about my phone being insecure since my bootloader is unlocked that pops up every time I boot was there for a reason. There is no security issue created by unlocking your bootloader?
Click to expand...
Click to collapse
It's cool, and I respect your decision to stay locked if you decide that is best for you. I suppose you could set Allow OEM unlock in Dev settings AND USB debugging in USB just in case, but if for some reason you could not boot, unlocking bootloader would then wipe userdata and your backups would be gone before you could transfer them off. In the end it's up to the individual to choose security vs, recoverability. Many ppl are getting locked out of their phones in the interest of security (or just the default settings). As it turns out, they were just trying to perform a monthly security update and hosed their phone. Stock rom, stock recovery, unrooted. Every Nexus phone I've owned (Galaxy?) has been unlocked so that I could use all the tools available to get myself out of a bind if needed. I don't give a sh!t about the boot up warning, because I know that my nandroid and FF backups can get me back home in the event of a lockup. Unlocking will not stop you from receiving OTA's if you are stock. Even if you are not, unlocking will allow you to use ADB, custom recoveries, toolkits, etc. If you end up in a bootloop and your bootloader is locked you are S.O.L. plain and simple. Each to their own though... if you need encryption and value high security of your data over recoverability then you may want to stay bootloader locked. As owners of a Nexus phone we have that option. Many others do not. Cheers my friend!
Thank you guys everything was successful, unlocked it in no time, downloaded 7.1.1 and it's perfect. NOw time to flash twrp and MegaPixel Rom

Relocking bootloader without bricking

Hey all.
So I've installed LineageOS just fine - the unlocking guides around here are mostly clear enough. Certainly not as easy as I've been used to for Nexus and OnePlus devices though! I've been using the 'official' TWRP 3.0.4.1 and not any of the other (now often links removed) unofficial versions.
I've also got my hands dirty with EDL mode and have totally reflashed a couple of times while playing around.
So on to my question. Basically I have an email client for work (Good for Enterprise) that detects unlocked bootloaders as 'root' (even though I'm not rooted), so I would like to relock my bootloader.
However, as soon as I use 'fastboot oem lock' it instantly bricks my phone. It goes straight into EDL mode, from which it cannot return. No bootloader, no recovery mode, no booting of system. Completely dead. All button combos attempted etc.. The only way back that I've found is to flash a whole new system image in EDL, and start over.
So, have I missed something (a signed recovery?) that makes this happen? Are there some verifications that the bootloader does while locked that fails because there's a custom system and recovery in place?
Is there anything I can do about this? Am I doomed to use stock for as long as I need to use this darned app?
Thanks very much!
Yes you need to be completely stock to lock BL.
Also if you want to stay unlocked, you can use MAGISK to hide root for your mailing app.
Thanks for the replies. I actually don't have, and never have had, root. So the only thing it can possibly be detecting is either the custom ROM itself (or rather, not a factory one from some list they maintain) or the unlocked bootloader. So I doubt MAGISK will work, because there's no root there to hide in the first place
(In case it wasn't obvious, we're talking about Good for Enterprise here).
The blackberry mobile device management system (earlier called GFE) doesnt care if bootloader is unlocked, it just checks whether you have a custom recovery (twrp) and that is enough to flag your system as rooted.

Pros/Cons of Rooting Moto G5 Plus!?

I wish to root my phone(XT1686) but intend to keep the stock ROM(no bootloader unlock).
Is there any advantage in doing so? And will OTA updates be affected?
yourSAS said:
I wish to root my phone(XT1686) but intend to keep the stock ROM(no bootloader unlock).
Is there any advantage in doing so? And will OTA updates be affected?
Click to expand...
Click to collapse
It is not possible to root without unlocking the bootloader on this device...
If you don't have a specific reason to root, don't do it.
And once rooted, you cannot accept any OTA... most likely case if you do it will just fail, worst possible case it bricks (which can happen but is extremely rare).
To answer the question in your title, about the advantages of rooting...
Rooting gives you near full access to your device, and thus the ability to customize it beyond the options provided to you via the default interface. Also, some apps provide additional features on rooted phones. For example, some security programs recommend rooting your device so that it can more forcefully integrate itself with the device to protect against malware, hacking, etc. I tend to install a security package that works better on a rooted device, as well as make use of features that tend to only work on a rooted device, such as folder mounting from the internal SD card to the external one. Also, allows me to access system files that are unavailable otherwise, allowing me to customize certain sounds (or copy them at least).
If you decide you want to root your device, make sure you understand the steps to take BEFORE trying it. That means when you come across a guide on how to do it, make sure you get all the files that will be required and reading through the instructions step by step. If any of the steps sound like it will leave you lost on what to do, then DO NOT do any of it. Also, make sure you read the comments for the guide as well, looking for any mention of issues encountered and consider if you might encounter those issues as well. For example, if it causes issues for devices that use a particular carrier and you use that same carrier, you might want to leave well enough alone. Compare your phone version numbers with what others report having issues with (kernel, baseband, build, etc). Anything that someone has an issue with where their phone somehow matches up with yours in some way, take that as a sign to investigate deeper, so as to avoid having any issues yourself.
For the most part, unless you have a need or desire for a feature/function that requires rooting your device, don't mess with it. I'm not kidding, as one mistake can leave you without a working phone and without any options for returning/replacing it.
Thanks for the replies & warnings.
I'm not a noob so I know the risks of rooting. So maybe I should have rephrased it-
What are the advantages of rooting Moto G5 plus specifically?
Say like in terms of mods and other stuff? Also, is it possible to unroot once rooted- I mean to ask if it's possible to revert the state to factory mode with bootloader locked and stock ROM so that device will be eligible for OTA updates again?
yourSAS said:
Thanks for the replies & warnings.
I'm not a noob so I know the risks of rooting. So maybe I should have rephrased it-
What are the advantages of rooting Moto G5 plus specifically?
Say like in terms of mods and other stuff? Also, is it possible to unroot once rooted- I mean to ask if it's possible to revert the state to factory mode with bootloader locked and stock ROM so that device will be eligible for OTA updates again?
Click to expand...
Click to collapse
Bootloader lock is not relevant to OTA's. You might be able to relock, but the fact it was once unlocked cannot be hidden, it will always be very clear that it was unlocked.
Unrooting is easy, the issue arises undoing what you did with root, undoing them all depends what you changed.
I don't know of any reasons specific to this device to root.
acejavelin said:
Bootloader lock is not relevant to OTA's. You might be able to relock, but the fact it was once unlocked cannot be hidden, it will always be very clear that it was unlocked.
Click to expand...
Click to collapse
If the OEM knows I've unlocked bootloader, why will it push OTAs to my phone even though I've locked bootloader on my end? So isn't bootloader lock status relevant for OTA?
yourSAS said:
If the OEM knows I've unlocked bootloader, why will it push OTAs to my phone even though I've locked bootloader on my end? So isn't bootloader lock status relevant for OTA?
Click to expand...
Click to collapse
No, the status of your bootloader is not relevant... Moto will notify you of an available update and happily attempt to apply it regardless if your bootloader is locked or not.
What matters is if the boot or system partitions is changed, if there is ANY change to those, among other things like if the radio version or recovery versions don't match or the partition table is changed, the update will fail. If you flash any custom recovery it will fail as well.
On this subject I mention a slight con which is that some banking or financial apps might complain to you if they detect root. I have maybe 10 different bank and credit apps installed and all work flawlessly except 1. The Huntington Bank app wont allow me to use fingerprint login but otherwise the app is fully functional like mobile deposits. Just wanted to mention to be aware.

Help I wanto to Re-Lock the bootloader

Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
sorry for my english..
Thanks
ross92 said:
Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
sorry for my english..
Thanks
Click to expand...
Click to collapse
Check this thread, and follow local update method, then you need only of a command to lock the bootloader:
https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795
I just locked the bootloader for my OnePlus 6t. Follow the steps given below.
1. Backup all the important data. I am not responsible for any data loss!!!
2. Remove security lock screen (pin/pattern) or any thing
3. Download the stock rom from https://oxygenos.oneplus.net/OnePlus6TOxygen_34_OTA_020_all_1904032212_38e22c8b9abd42e3.zip
and transfer it to your phone.
4. Boot into twrp recovery.
5. flash the downloaded zip
6. Once done, reboot the system.
7. Now, boot back into the fastboot. (you can enable advance restart from developer mode for easy boot into fastboot)
8. Run fastboot oem lock
9. You will be presented with two options on phone screen. Select the one that says lock the bootloader.
10. It will wipe everything.
11. Once you in the system, enable developer mode and make sure that oem unlock is turned off. If not, turn it off and restart your phone.
And, you are done.
Let me know if it helps or if you have any question/concern.
MDM Tool in my opinion the easiest and quickest way to go back to 1000% stock. It will re-flash every partition on the phone so it's like brand new again. Using the MSM Tool guarantees that everything is back to stock and should restore the Widevine version back to L1 or whatever it was originally.
A question please
Once you lock again your phone, does it loose the root????
I mean, I have a Xperia 10 with the bootloader unlocked , it is root as well. Now root permissions for special aps work fine, but Google Pay is unusable, it does not work anymore. I hid root with xposed framework and rootCloak, but Google Pay still does not work now because the bootloader is unlocked...
As you should know, it is possible to lock the phone again... and many of those phones that relock their bootloaders keep the root permissions...
However , in my case, with Xperia devices (bq and xiaomi happen de same) is you lock the bootloader again, the phone resets, everything dissapear and root is eliminated. What is a really disaster.
As you have heard, the majority of phones, if you lock them again the root continues working, at least the apps that you gave them root permissions they continue working as they used to. But in my case this is different....ç
So please,
Is there any possibility to Lock my bootloader again without loosing the Root in my Xperia?????
Thousand of thanks!!!!
Bardok84 said:
A question please
Once you lock again your phone, does it loose the root????
I mean, I have a Xperia 10 with the bootloader unlocked , it is root as well. Now root permissions for special aps work fine, but Google Pay is unusable, it does not work anymore. I hid root with xposed framework and rootCloak, but Google Pay still does not work now because the bootloader is unlocked...
As you should know, it is possible to lock the phone again... and many of those phones that relock their bootloaders keep the root permissions...
However , in my case, with Xperia devices (bq and xiaomi happen de same) is you lock the bootloader again, the phone resets, everything dissapear and root is eliminated. What is a really disaster.
As you have heard, the majority of phones, if you lock them again the root continues working, at least the apps that you gave them root permissions they continue working as they used to. But in my case this is different....ç
So please,
Is there any possibility to Lock my bootloader again without loosing the Root in my Xperia?????
Thousand of thanks!!!!
Click to expand...
Click to collapse
Go ask in Xperia threads
Striatum_bdr said:
Go ask in Xperia threads
Click to expand...
Click to collapse
Yes I did:
https://forum.xda-developers.com/xperia-10/development/help-how-to-lock-bootloader-loosing-t3965829/post80203451#post80203451
Also I asked for help here:
https://forum.xda-developers.com/android/help/how-to-lock-google-pay-xperia-rooted-t3965637
https://forum.xda-developers.com/galaxy-nexus/themes-apps/app-bootunlocker-nexus-devices-version-t1731993/page66
https://forum.xda-developers.com/galaxy-nexus/themes-apps/app-bootunlocker-nexus-devices-version-t1731993/page66
This is the only Thread where I could find some information about locking a bootloader again. Yes , this is dedicated to xiaomi 6t, but locking bootloaders is something common.
The only thing I want is to lock my Bootloader again without loosing Root permisions. Xperia devices seem to RESET everything when you lock the booloader automatically...., but perhaps there is another way.... a possibility to lock the bootloader without the phone is reset (loosing root permissions) ....
I asked for some help here. I regret any inconvenience that could may be caused on this thread with my message.
Regards
Nobody have your phone here how could we help you? Each phone has its specific behavior
If you relock a OnePlus phone you reset everything, like when you unlock it and it's logical. A locked bootloader is meant to ensure safety of data, safety that can't be provided with root access. Locked BL and root are antinomic.
Striatum_bdr said:
Nobody have your phone here how could we help you? Each phone has its specific behavior
If you relock a OnePlus phone you reset everything, like when you unlock it and it's logical. A locked bootloader is meant to ensure safety of data, safety that can't be provided with root access. Locked BL and root are antinomic.
Click to expand...
Click to collapse
Thank you for your message and understanding. So in Oneplus devices happen the same. So once you unlock the bootloader you loose Google Pay forever because it does not work wit BL unlocked...
Some users suggested me to lock again the bootloader,
Imagine:
- I become Root. Then I modify some apps
- I give to some apps root permissions.
- I lock the bootloader again.
- I won't be able to modify my phone anymore, but all those apps that were given root permissions, Will they be kept in the phone although it has BL locked again.
would it be like this?
or all changes you did while being root would dissapear with everything?????
If So... there is no exit what I see..., We have to choose between being Root users.... or being stock with Google Pay. It is a Pity.
I was not sure if all Phones reset and erase everything when you lock the bootloader .... but as I can see here, this is the reality. Root users loose Google PAY definitely.
Is there any option to solve this??
thanks again for your attention.
regards
Bardok84 said:
Thank you for your message and understanding. So in Oneplus devices happen the same. So once you unlock the bootloader you loose Google Pay forever because it does not work wit BL unlocked...
Some users suggested me to lock again the bootloader, but if I do that, as you have said, the Root and everything will be erased because the phone resets everything. So... there is no exit what I see..., We have to choose between being Root users.... or being stock with Google Pay. It is a Pity.
I was not sure if all Phones reset and erase everything when you lock the bootloader .... but as I can see here, this is the reality. Root users loose Google PAY definitely.
Is there any option to solve this??
thanks again for your attention.
regards
Click to expand...
Click to collapse
I'm unlocked and rooted c and Google pay works perfectly with Magisk
Striatum_bdr said:
I'm unlocked and rooted c and Google pay works perfectly with Magisk
Click to expand...
Click to collapse
Does google pay work??? What did you do in magisk exactly to achieve that???
I rooted my xperia using Magisk..., is there any tutorial or info that you suggest to me to follow ? or what should I do in magisk options???
I have 10 days with my phone stopped, trying and trying to make Google Pay works....Maybe this is happening to me because my Xperia uses Android 9.0.... or Magisk should make google pay work even being in android 9.0?
First Google pay recognized Root, and the app stopped working. I hid it using xposed and RootCloak
Then, Google pay recognized Bootloader. But now... I dont know what to do to hid bootloader unlocked for Google..., Google pay recognises it is unlocked... a disaster and a nightmare for me, I dont know what to do...
Thousand of thanks, I really thankfull for your help.
Regards

Categories

Resources