Hi,
I unlocked the bootloader of my oneplus 9 pro.
After finding out that I cannot use Google Pay anymore I wanted to lock the device again.
When using fastboot oem lock I get the message that my phone has been tampered with and it will not boot.
I tried flashing the stock rom using payload_dumper and locking the bootloader afterward, but no succes.
The only thing I can do at the moment is unlocking the bootloader and using the phone like this.
Does anyone have a solution?
Never mind I found the solution
-> flash the same OTA twice via local system upgrade
-> reboot into bootloader
-> fastboot oem lock
glad you got it sorted!
That is the correct way to lock. But I am typing on a 9 Pro that has Magisk installed with GPay working flawlessly. Running 11.2.6.6
That is weird.
My gpay app would always say that my device was rooted of tampered with.
I followed the guide to install magisk.
After that I flashed a custom kernel.
Used magisk hide on gpay and my banking apps.
I even used the hide magisk app feature and I was still unable to get gpay working.
I removed magisk and still gpay would not work.
I wonder how you got it to work.
Related
Hello, I am having an issue with my wife's Robin. The phone is completely stock other than an unlocked bootloader and unencrypted storage. System, boot, recovery, kernel, etc. are all stock and no root. I have even wiped the system partition and reflashed the system.img for good measure. The device is failing SafetyNet checks, however. This means Android Pay is not working and displays the following error. "Android Pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader, or is running a custom ROM. As a result, Google can't confirm that your device meets Android Pay's security standards." Does anyone else with ONLY an unlocked bootloader have the same issue? Could lack of encryption have anything to do with it? I am puzzled. I have an old Nexus 5 with an unlocked bootloader, rooted, with no encryption and I am still able to toggle root and pass SafetyNet checks. Anyone else have a similar issue? If this is the case, she might as well have root and the advantages (as well as the potential hazards) that come with it.
Your wifes robin has an unlocked bootloader and you had to batch the kernel (boot.img) if she is still running stock os.
This is enough to trigger saftynet. If you want to pass saftynet again I suggest you go back to full stock or you flash magisk
( https://forum.xda-developers.com/apps/magisk ) and the phh supersu module. then you could activate magisk hide in the settings and you will pass saftynet. Thats what I am doing to play Pokemon Go
flyfire04 said:
Your wifes robin has an unlocked bootloader and you had to batch the kernel (boot.img) if she is still running stock os.
This is enough to trigger saftynet. If you want to pass saftynet again I suggest you go back to full stock or you flash magisk
( https://forum.xda-developers.com/apps/magisk ) and the phh supersu module. then you could activate magisk hide in the settings and you will pass saftynet. Thats what I am doing to play Pokemon Go
Click to expand...
Click to collapse
Thanks for the response and link. I ran the OEM unlock command and have since flashed the boot.img from the official Nextbit factory images. So unless that boot.img is itself patched, then I should be stock (other than the unlocked bootloader of course). That is likely the issue, but I want to see if anyone else who is stock with an unlocked bootloader has the same issue.
Then read this: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Then you will understand that an unlocked bootloader by itself can trigger saftynet. magisk removes the the verified boot flag.
Another easy solution is to just lock the bootloader using the oem lock command. This will not wipe the device like unlocking does.
So to be clear, my choices to get SafetyNet to pass are to:
OEM lock thus returning to complete stock or
Flash a modified kernel to suppress the bootloader unlocked flag or
Flash Magisk and phh root and activate Magisk hide
If I do the last option, do I also need a modified kernel or will this hide the bootloader unlock status from SafetyNet with the stock kernel? Thanks for the feedback.
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
I believe you're not able to relock the bootloader until Motorola release a signed bootloader. I had the page once before I'll see if I can find it again and add an edit if I do.
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
Don't relock your bootloader unless you want a brick. Technically you can relock it, but everything has to be legit. You've already voided the warranty, relocking won't reinstate that, all that will happen is you'll be bricked with nothing to do about it because you've locked the bootloader.
Why do you want to relock it?
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
jeffritz1 said:
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
Click to expand...
Click to collapse
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Uzephi said:
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Click to expand...
Click to collapse
So, I did a "fastboot oem lock" and it re locked the bootloader. Restart bootloader, shows locked. Restart phone and still getting a splash screen similar to the one when your unlocked but this time it says "Device has loaded a different Operating System". Continues to boot normally into the system without issues. This was odd so I unlocked again did a Flashall w/ "XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and "fastboot oem lock". Both times said the lock was successful. But I'm still getting this boot splash screen with test reading "Device has loaded a different Operating System". System boots but still fails SafetyNet.
What gives? What am I missing?
From what I can muster up on XDA I can see that "you need a signed boot.img". Does this mean something and how can I find this?
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
jeffritz1 said:
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
Click to expand...
Click to collapse
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
jeffritz1 said:
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
Click to expand...
Click to collapse
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Marcowe said:
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Click to expand...
Click to collapse
Yeah, I was trying to find out if the phone could be reverted back to an out of back state. Another words, no splash screen saying "HEY! I HAVE BEEN MESSED WITH!" like you can on any other phone I have ever owned.
Thanks!
Yes you can
thomas.raines said:
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Click to expand...
Click to collapse
Yes you can , I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
EddiePR said:
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
Click to expand...
Click to collapse
If you do that OTAs will fail
Marcowe said:
If you do that OTAs will fail
Click to expand...
Click to collapse
Yes, you are rigth
So, which of the methods to re-lock did finally work? I was running on Android 8 before, OTA failes for at least 10 times, but suddenly it worked to upgrade to Android 9. Now I am weirdly not passing SafetyNet-check anymore (was working fine on Android 8, GooglePay etc).
Any recommendations? I just need the stupid GPay thing working
I waited the 72 hours and then ran the program on my PC for the Mi Unlock, and then afterwards I wiped the phone clean, flashed TWRP, and put on miui10, forgetting that doing a data wipe resets the Mi Unlock status. Do I really need to reunlock it, cause if so it will delete all my data again..
Edit: It's just odd because on the bootloader screen, 'fastboot oem device-info' shows my bootloader unlocked still, I have Magisk installed, running joeykrim's Root Checker from google play shows root access not properly installed, running flar's DevCheck from google play shows the device rooted, I have BusyBox installed , and lastly, in the Developer options, OEM Unlocking is ticked on, but doesn't say already unlocked, and the Mi Unlock status still shows locked. Lots of conflicting info here, so just a bit wary since this is my first Xiaomi phone.
I went ahead and tried unlocking again with the tool and I get this (see screenshot)
Usually unlocked only once, but if your device is locked again, it can be unlocked without any damage. Don't know what ROM you use If it is a world class ROM, ctf will not pass. For magisk, you have to modify the fingerprint to pass. Try studying. You have to do it. Good luck.
สุรินทร์ พลโธา said:
Usually unlocked only once, but if your device is locked again, it can be unlocked without any damage. Don't know what ROM you use If it is a world class ROM, ctf will not pass. For magisk, you have to modify the fingerprint to pass. Try studying. You have to do it. Good luck.
Click to expand...
Click to collapse
WEll everything is running fine being rooted. MAgisk SAfetyNet passes, rooted apps work fine, but Mi Unlock still shows my phone is 'locked'm but fastboot says it's unlocked. And I'm using the official miui_MIMIX2Global_V10.2.2.0.ODEMIXM_a92827160b_8.0 rom and fw_chiron_miui_MIMIX2Global_V10.2.2.0.ODEMIXM_a92827160b_8.0 firmware
You don't have to worry. I think your device is already unlocked. If the device is still locked, you cannot install twrp.
yeah thats why im confused. everything works fine. i guess i wont worry about it unless i come to a problem
tried the first thread here and rooted my device but i cant managed to keep l1 after unlocking bootloader.
tried clear google apps caches and data
installed safetynetfix module
installed magiskhideprobs module
tried unlocking bootloader with "fastboot oem unlock" and "fastboot flashing unlock" didnt workd
tried magisk and magisk canary
none of them worked does anyone know how can i get L1 back after unlocking bootloader
Thanks
are you on oos 12 ( version c61 ) ???? with the version I didn't manage to have l1 either (with c48 that was no problem with root) but with the c61 nothing helped me either, no matter what I tried, it was always l3
just as this menu is there with the c61 without root and with root this menu simply disappears
ChrisFeiveel84 said:
are you on oos 12 ( version c61 ) ???? with the version I didn't manage to have l1 either (with c48 that was no problem with root) but with the c61 nothing helped me either, no matter what I tried, it was always l3
just as this menu is there with the c61 without root and with root this menu simply disappears
Click to expand...
Click to collapse
yes im using 2123 with c61 update i just bought phone this week so i dont know it was working before or not
Now my phone is locked and I have to enter my mi account password.
But when I enter my password, it just sends me to the same screen again (probably because the app is missing.)
I have no Idea how unlock my phone now?!
It is rooted, but I cant run any adb commands.
I'm on V14.0.2.0. Reflashing didn't help. Is there a way to maybe reinstall the app or to unlock the phone without doing a full wipe?
The problematic apk is com.xiaomi.account (at least I think so, the issue didn't appear immediately and uninstalled other system apps too)
I am very thankful for any kind of help : )
Use Miflash and dont re lock the bootloader(data will be removed).
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
I reflashed my rom, this time wiping all data.
It works now, but my files are sadly gone.
Hallohannes123 said:
Now my phone is locked and I have to enter my mi account password.
But when I enter my password, it just sends me to the same screen again (probably because the app is missing.)
I have no Idea how unlock my phone now?!
It is rooted, but I cant run any adb commands.
I'm on V14.0.2.0. Reflashing didn't help. Is there a way to maybe reinstall the app or to unlock the phone without doing a full wipe?
The problematic apk is com.xiaomi.account (at least I think so, the issue didn't appear immediately and uninstalled other system apps too)
I am very thankful for any kind of help : )
Click to expand...
Click to collapse
Hey how did you root your 11 T
No need for TWRP to root.
Method to be adapted with your rom.
Root Xiaomi 11T pro on latest MIUI 13-Working!
Quick update and guide for those wishing to root their Xiaomi on the lastest stable MUIU 13 since TWRP is no longer working on Android 12 MUIU 13. No need to downgrade version, just use whatever you latest ROM you are on. This should be...
forum.xda-developers.com
Doctet said:
Hey how did you root your 11 T
Click to expand...
Click to collapse
you need to download your firmware, extract the boot.img file, patch it in the magisk manager app and then flash it (fastboot flash boot <boot.img>) in fastboot mode.
look up the official guide for installing root with magisk, works just like any other phone