Related
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
This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!
Did this method work for your....
LysolPionex said:
This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!
Click to expand...
Click to collapse
which variant you use?
angel8502 said:
which variant you use?
Click to expand...
Click to collapse
SM-960F/DS.
But I just got the "Only Official released binaries are allowed to be flashed" message, so I might get to try this method again myself, lol.
How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten
beatbreakee said:
How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten
Click to expand...
Click to collapse
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?
LysolPionex said:
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?
Click to expand...
Click to collapse
take a pic n post it of download mode
elliwigy said:
take a pic n post it of download mode
Click to expand...
Click to collapse
Just a close up, nothing else relevant in the screen.
LysolPionex said:
Just a close up, nothing else relevant in the screen.
Click to expand...
Click to collapse
most likely is the rmm state
elliwigy said:
most likely is the rmm state
Click to expand...
Click to collapse
That makes sense with what I found last night in another thread. I think I used an old version of the rmm Mesa bypass too, so we'll see what happens. In another 5 days...
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
This is the first time I've seen a clear explanation off all of this. Thank you for that!
What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..
Regikitten said:
What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..
Click to expand...
Click to collapse
I'm not familiar with it, but I assume he's talking about this: https://forum.xda-developers.com/ga...ollection-combination-rom-samsung-s9-t3782737
There are a couple other threads about it in the S9 forum.
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?
LysolPionex said:
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?
Click to expand...
Click to collapse
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all
elliwigy said:
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all
Click to expand...
Click to collapse
Lol, so I'm at 182 hours uptime, but the OEM option isn't in dev options...do I risk going to download mode to see RMM status?
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance
Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
askader said:
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance
Click to expand...
Click to collapse
Will appear within 5-7 days since you flashed stock ROM.
ZoiraP said:
Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
Will appear within 5-7 days since you flashed stock ROM.
Click to expand...
Click to collapse
Did it solved after 7 days?
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I do have a computer, a Windows 10 Pro
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
sliding_billy said:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
Click to expand...
Click to collapse
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
coolhandz said:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
Click to expand...
Click to collapse
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
sliding_billy said:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
Click to expand...
Click to collapse
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
sliding_billy said:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
Click to expand...
Click to collapse
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.
eec007 said:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Click to expand...
Click to collapse
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
bobby janow said:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
Click to expand...
Click to collapse
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
eec007 said:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
Click to expand...
Click to collapse
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.
eec007 said:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
Click to expand...
Click to collapse
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
eec007 said:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Click to expand...
Click to collapse
They're right to mention that relocking a modified device can result in a brick.
Your best bet is to go to https://developers.google.com/android/images#taimen
Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.
Would suggest to do this anyway, no matter future unlock status.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...
Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said.
turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.
Hi,
I have recently bought a T-mobile version of OP7T. Even though T-Mobile unlocked the network permanently, I still didn't like T-mobile branding at the start, plus I wanted Stock OxygenOs. So what did I do?
(No root and No TWRP)
1. I've Unlocked the bootloader via the method in this post. Stage-1
2. I have flashed the stock rom which I downloaded from this post. Stage-2
3. Phone loads up perfectly fine and now I have stock OOS. to make sure everything is fine, I also did a factory reset and re-flashed the stock rom to make sure there's no track of previous roms.
4. I then wanted to relock the bootloader in order to keep my device safe and enjoy having a normal device like any others without the ugly message at the startup.
5. So I put it in fastboot mode and executed "fastboot flashing lock" or "fastboot oem lock" and it gave me the options and I locked the bootloader.
6. after this, I can't do anything else. it keeps showing me the page where it says Your device is corrupt. It can't be trusted and will not boot and in order to get rid of I need to keep unlocking the devices relfashing everything and the rest of the story.
I've read all the accurate and inaccurate infos on forums where another guy claims when he did turn everything to stock (recovery + rom + factory reset) things go back to normal and he's done. in my case it doesn't work.
Please help me, how I can be able to relock the bootloader without running into Your device is corrupt. It can't be trusted and will not boot.
Thanks.
First I think no help is stupid, since that is the regular way of doing it. Second you should have read extensively before doing what you did. T-mobile is very specific device. What he probably didn't mention is that you need the original rom t-mobile branded, since you need original software to be able to relock bootloader. I would recommend use msm- tool to recover you device. Read carefully and next time just be sure that what you are doing is informed.
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
bahadorkh said:
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
Click to expand...
Click to collapse
That was my point in order to relock your device you must have the original firmware that the phone came with if it's t-mobile. Installed in both slots. Then you can relock you device.
Please try this thread
[OP7T T-MOBILE][OOS 11.0.1.5 HD63CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
After the first boot you must update via OTA, then after the 7T reboots you can go back into the bootloader and relock it. I'm typing this message out on my T-Mobile 7T running the Global OOS 11 version. _ANY_ modification to the system whatsoever will cause the "Device is Corrupt" error, due to a mismatch of the keys used by OnePlus to sign the firmware. I've attached a screenshot of my "About phone" section as proof of the conversion, however, I can't show proof of my bootloader's state because I don't have access to a PC at the moment and *#*#7378423#*#* didn't work, neither did *#*#7378423*#*#. If I remember to the next time I'm near a PC I'll add proof of that too.
For further reading see::
1.) https://source.android.com/security/verifiedboot/boot-flow#locked-devices-with-custom-key-set
And
2.) https://source.android.com/security/verifiedboot/dm-verity
P.s. I do realize that I'm almost a year late to this discussion, but I thought knowing would/could still be useful to someone.
Hi i've got a question. I recently purchased the A5 2017 (A520F) secondhand and i want to put a custom rom on it. I have unlocked and flashed tons of phones and tablets in the past so i'm far from a newbee.
My phone has "Bootloader OEM unlock" in dev options.
When i go into odin download mode (vol-, home+power) i dont get any message regarding "RMM state: Prenormal". FRP is unlocked.
Does this mean i'm all set to flash anything without the RMM.zip?
I'm having the latest security patch Jan2020 and Oreo bootloader. Knox is 0x0. Are there any other ways to check RMM state?
JMailuhu said:
Hi i've got a question. I recently purchased the A5 2017 (A520F) secondhand and i want to put a custom rom on it. I have unlocked and flashed tons of phones and tablets in the past so i'm far from a newbee.
My phone has "Bootloader OEM unlock" in dev options.
When i go into odin download mode (vol-, home+power) i dont get any message regarding "RMM state: Prenormal". FRP is unlocked.
Does this mean i'm all set to flash anything without the RMM.zip?
I'm having the latest security patch Jan2020 and Oreo bootloader. Knox is 0x0. Are there any other ways to check RMM state?
Click to expand...
Click to collapse
Reboot device just to check that OEM unlock is still enabled.
Yes, Bootloader OEM unlock switch is still activated.
JMailuhu said:
Yes, Bootloader OEM unlock switch is still activated.
Click to expand...
Click to collapse
Then read a guide like this, there are other workarounds though https://forum.xda-developers.com/t/...e-prenormal-on-oneui-android-pie-9-0.3911862/ but don't flash custom binaries while you don't bypass RMM prenormal status.
Yeah this requires a linux distro so i guess for that method i have to run linux in a VM or dualboot on another partition.
However, it still doesn't explain why i don't have a RMM message. Maybe RMM is gone altogether (not sure if thats possible tho).
Anyway thanks for your replies.
JMailuhu said:
However, it still doesn't explain why i don't have a RMM message. Maybe RMM is gone altogether (not sure if thats possible tho).
Click to expand...
Click to collapse
What do you mean with? You said RMM appears like prenormal.
SubwayChamp said:
What do you mean with? You said RMM appears like prenormal.
Click to expand...
Click to collapse
No i said i did NOT have any message regarding RMM state in download mode
JMailuhu said:
No i said i did NOT have any message regarding RMM state in download mode
Click to expand...
Click to collapse
Oh, sorry, I read bad, and nothing about KG?
It means you don't have remote restrictions, even with FRP.
In this case, you are able to flash custom binaries.
No problem bud, happens to the best of us. Nope nothing about KG either. I wil try and flash twrp etc. Worst case i'll flash back official firmware. Thanks for the help!
Solved: There was no RMM/KG on the device at all so i went and flashed TWRP and Rise-Q OneUI 2.5. Everything went smooth as butter.
Good, if it is not present in download screen, then in this device, either RMM/KG are not implemented.