Im sure there has been a lot of discussion on this, but I am interested in experimenting a little on this issue and havent been able to find much through searching the forum.
What I have determined is that running "fastboot oem lock" asks to first disable the security before proceeding.
Running "fastboot getvar security" shows that the security variable is set to "on"
I'm assuming that the security is turned off by running a task command using "fastboot oem task(appropriate task number to disable security here)" the only issue is im not sure what the task number is for the nexus one and am too afraid to try some educated guesses for fear of bricking.
My thinking is that once the task number for disabling security is found, then we can run "fastboot oem lock" to re-lock the bootloader, then run the correct task number to re-enable security and done, phone is back in its original locked state. Am I over-simplifying this??? Would love to hear some thoughts.
Little searching and you can see that this question has been beaten to death, revived and beaten to death again and again...
Only those with the "Holiday" edition with the S-OFF on the bootloader can relock their N1's.
No one has been able to find a way around this with non-holiday editions (the retail version).
Related
Hello!
I've recently got into a big problem while doing stuff I don't know much about (and probably in the wrong way, because of that...). So, let's get to the problem, shall we?!
Well, I wanted to root my Moto G4 Plus (XT1640) but I had never done anything like it, so my phone was basically the way it came out of the factory. Before all of this, my phone was using Nougat 7.0.1 (I do OTA updates). I installed TWRP and followed the steps (even some from this forum). However, at that point my phone was boot-looping in the screen "Your bootloader has been unlocked, your device can't be trusted. Your phone will boot in 5 seconds.". Despite the warning, my phone didn't boot. After a while, screen got black and the only way I could use the phone was while in the bootloader. Then, I've made wipes through the Recovery, hopeful that it'd help, but it didn't. Finally, I surrendered and went looking for an original stock ROM I could flash and maybe get things working again. Found SOME ROM that's probably the right one ("XT1640_ATHENE-RETBR_MPJ24.139-50_cid50_subsidy-DEFAULT_CFC.xml.zip") (I'm from Brazil, btw). Great, downloaded, followed steps in the forum to flash it, great, it boots again! Can login to Google, default settings stuff, etc... HOWEVER.
Then, with my phone working again, I wanted to get rid of the nasty boot screen that said my device can't be trusted, etc. So I looked it up and tried to reflash the same stock ROM as above, but now doing it so I could re-lock the bootloader. To do that, I repeated the flashing commands but added the command "mfastboot oem lock" at the end (also used "mfastboot oem lock begin" as the 1st command). Then the CMD said I had to retype the command to apply. Did that, but then the following message showed: "Waiting for signed boot.img, enter the command again" or something like that (didn't printscreen, sorry). Then I reentered the command a 3rd time and then it said "Please flash a signed ROM" or something. So, basically, it failed. After that, repeating the command just showed the last message again. Unhappy, but hopeful, I entered "mfastboot reboot" to reboot my phone. So, got back into the phone (still with the nasty "Your bootloader has been unlocked" warning) and then I basically gave up. I'm now trying to install an OTA update (for Nougat, since the ROM I installed is 6.0.1) but the WiFi download is REALLY slow (and the problem is not my internet, since I've tried downloading a couple of files in my PC to test it).
So my biggest fear is that I have a ROM that's not REALLY meant for my phone (despite looking EVERYWHERE for it) and that's causing problems with the WiFi. Maybe the OTA update is just slow in the server-side, but I'd like to know. Is there a way to get the ROM I got when I bought the phone (that EXACT SAME ONE)?! I wonder if there's a problem because of Motorola/Lenovo regional things. Otherwise, the phone works (gets 4G signal, making calls and downloading Play store updates is as far as I've tested for now). And I would also like to know if there's a way to relock the bootloader in my case(since when I tried those errors I've mentioned above happened)? What I seemed to have done is downgrade a version (since I was in Nougat and then installed a stock ROM that's 6.0.1) and I don't know where to go from here. Thanks a lot, guys! Sorry for the long post, I just wanted to describe the events in order.
There is no official source for you to get a rom. This is not a nexus. I wonder why people always want to relock bootloaders! (it seems in your case only for the 5 seconds warning). As far as i know only modem can differ but roms...
Do you still have TWRP?
if so: if you are on an N modem right now try to flash an N custom rom. If you are on an M modem flash an M custom rom.
KEEP YOU BOOTLOADER UNLOCKED and also:KEEP "OEM UNLOCKING" in developers options ENABLED AT ALL TIMES! (the last step will prevent you from a 72 hours lockout from your Google account.)
There are other ways to get rid of the bootloader warning. (flash a custom logo.bin)
Hello yall,
So as many of you should already be aware that the OEM Unlock missing button is kinda permanent in Bootloader U4/August Update. So no matter how long; you cannot get passed the jail time.
I have been looking forward to lock back my OEM lock to be able to use Google Pay and have my device certified in play store but I cannot turn it back on and it's a security flaw in my opinion as locking OEM means tighter security actually.
I have got in touch with samsung technician and they confirmed the feature is removed in the current update and there is no work around.
I have tried flashing combination Rom for U4 Bootloader but OEM Unlock is still missing in dev options.
Now the question is; Has anyone in this big world found a solution to this? To turn OEM Unlock off in Bootloader 4?
Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!
dlehmanusa said:
Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!
Click to expand...
Click to collapse
You need to download the latest stock firmware either from Samsung or Sammobile and use Odin to flash it. DO NOT DISABLE OEM!!!! That has nothing to do with locking the bootloader. Flashing the stock ROM will do that. The OEM enable only disables the FRP lock which makes you login with the same google account used BEFORE a factory reset. If you are sure you know that account login and password, the FRP lock isn't a problem.
edit: The problem with the FRP lock is that people will often create a new google account login and password when first setting up their tablet. And because you only have to do that once, they tend to forget one or the other. Then, if they do a factory reset without the OEM enabled, they are locked out of the tablet.
Thanks for the detailed information and clarification. Your help is much appreciated!
The T510 doesn't have a locked bootloader.
ashyx said:
The T510 doesn't have a locked bootloader.
Click to expand...
Click to collapse
No, but it does "lock" the tablet from getting OTA updates.
I have reflashed the stock firmware however I'm still receiving the following message during boot..."The bootloader is unlocked and the software on this device cannot be verified". Is there a way to remove this message? I am planning to return the device and I want to reset everything. Thanks!
I have this phone (ASUS_A009 ZenFone 5 V500KL Live) and I've yet to find a reliable resource to unlock the bootloader. I sure rooting the phone won't be a problem but the bootloader has been the time consumer today. Am I just missing something here. I've done every method I ran across on XDA pertaining to ZenFone. I am about to attempt to flash firmware with an image for the only other phone similar to this one (except the VZW part). I say that because when you look up "ASUS_A009 specs" in Google you'll get the V520KL but upne further investigation I found otherwise. There is talk about the ENG Firmware Allowing for OEM unlock through fastboot. I grabbing at air here.
RawAmphetamine said:
I have this phone (ASUS_A009 ZenFone 5 V500KL Live) and I've yet to find a reliable resource to unlock the bootloader. I sure rooting the phone won't be a problem but the bootloader has been the time consumer today. Am I just missing something here. I've done every method I ran across on XDA pertaining to ZenFone. I am about to attempt to flash firmware with an image for the only other phone similar to this one (except the VZW part). I say that because when you look up "ASUS_A009 specs" in Google you'll get the V520KL but upne further investigation I found otherwise. There is talk about the ENG Firmware Allowing for OEM unlock through fastboot. I grabbing at air here.
Click to expand...
Click to collapse
For Oem unlock, go to settings, then about phone, them software version and tap 7 times on that. Then go back to settings and tap on developer options. Then inside developer options, tap oem toggle. After this do unlock process with computer
Hi everyone, i’m having an extremely weird issue with my Samsung J5 Prime (SM-G570Y/on5xelte). First of all; sorry for bad english, this post will be a bit long.
So i want to unlock OEM, to install custom recovery and custom ROM (and being able to login with google account from gms (Google Play Service app)).
i activate developer options.
Then go to Settings > Developer Options, but OEM Unlock is missing (i did'nt have the screenshot of the settings), i already try every method to reappear it but nothing worked.
Trying my luck, im rebooting my phone to download mode, on there i didn’t see any text that says OEM Unlock, i tried to flash OrangeFox Recovery using ODIN. And suprisingly it worked, i even double-checked it by actually booting to recovery. i did'nt expect it to work though...
Then i install RadicalQuack Custom ROM, and do some root-level customization.
But as soon as i try to login Google account from Google Play Service (this didnt affect web login or any other login) on Stock/Custom ROM, and reboot the phone... my phone was FRP locked, i was shocked because my configuration isn’t even backed up.
I have to flash stock rom in download mode, get to setup, login google, remove the account, then i can get rid of FRP lock.
And at this point is where everything is confusing.
If i use stock rom without any changes, the "OEM Unlock" option is'nt appearing at all.
But if i use custom ROM (in this case i use RadicalQuack), the "OEM Unlock" option Appears (until i remove "ro.frp.pst" in build.prop)
So i can do anything but CANNOT login using Google Account from Google Play Services or get FRP locked and All data destroyed.
Now my question is, is it safe to enable "Unlock OEM"? Because i dont know if OEM Unlock is currently enabled or not, i dont know how to check if the bootloader is actually locked, i dont want to get locked forever on samsung stock and bloated shtt again.
PS:
Somehow... i can login Google account without getting FRP locked by:
Unlocking OEM (on the custom ROM ofcourse, since it won't be visible on stock ROM anyway...)
and removing "ro.frp.pst" (especially "ro.frp.pst=/dev/block/persistent") on /system/build.prop, /system/vendor/build.prop, /vendor/build.prop
what did you do?
Hiii, what did you do? I need to unlock oem un my j5 prime
Same Problem Happens to me But Now How you use custom rom without getting frp lock please Tell I Have Also J5 prime And Same Happens to me also I need to flash stock rom from which my custom rom get erased