Related
I've read that when unlocking the bootloader with "fastboot oem unlock" it sets s-off. Is possible to set it again to s-on for warranty purposes?
In the wikipedia says that:
Once the user accepts the terms the protocol is enabled and a security flag showing that the device has been unlocked is permanently set.
Click to expand...
Click to collapse
Did you try "fastboot oem lock" ?
Sent from my Galaxy Nexus
milltronics said:
Did you try "fastboot oem lock" ?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
No, I still have the bootloader locked and would like to know before if is even possible.
Yes, fastboot oem lock will relock the bootloader.
Sent from my Galaxy Nexus using xda premium
El Daddy said:
Yes, fastboot oem lock will relock the bootloader.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
And that is what preserves warranty? I mean, after installing official rom and relocking that's it?
scandiun said:
And that is what preserves warranty? I mean, after installing official rom and relocking that's it?
Click to expand...
Click to collapse
Should be.
Depends, though. I returned my GNex with AOKP build twenty something, franco's kernel and what not.
S-on/s-off is only an htc thing I believe. Only htc phones have that from my understanding, not Samsung phones and especially no nexus phones regardless of manufacturer.
RogerPodacter said:
S-on/s-off is only an htc thing I believe. Only htc phones have that from my understanding, not Samsung phones and especially no nexus phones regardless of manufacturer.
Click to expand...
Click to collapse
You refreshed my mind just right now. The s-on and s-off is a HTC thing, I saw it on htc subforums.
I've tested 'fastboot oem lock' and does relock the bootloader, provided that you have stock rom installed. So this will preserve warranty.
Thank you.
RogerPodacter said:
S-on/s-off is only an htc thing I believe. Only htc phones have that from my understanding, not Samsung phones and especially no nexus phones regardless of manufacturer.
Click to expand...
Click to collapse
Well, you are half right. It is an HTC term and it refers to the NAND lock. Other manufacturers use locks as well -- Motorola being a prime example.
However, you are wrong about no Nexus devices being S-ON. The Nexus One is an S-ON device. Yes, it has an unlockable bootloader, but it is not relockable, and you did not have write (and in some cases, read) access to all the partitions.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Well, you are half right. It is an HTC term and it refers to the NAND lock. Other manufacturers use locks as well -- Motorola being a prime example.
However, you are wrong about no Nexus devices being S-ON. The Nexus One is an S-ON device. Yes, it has an unlockable bootloader, but it is not relockable, and you did not have write (and in some cases, read) access to all the partitions.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I presume it is the "oem" command that does the trick
scandiun said:
I presume it is the "oem" command that does the trick
Click to expand...
Click to collapse
On HTC devices, in order to get true S-OFF, you need a special SIM card, or SIM emulator to write directly to the NVRAM, which contains the security flag. Not sure on Motorola devices, as I don't believe anyone has figured it out yet.
On HTC devices, using the "oem" qualifier after "fastboot" gives you access to a huge list of other fastboot commands, but only with an engineering bootloader flashed. Some examples: dumping partitions straight from fastboot, flashing partitions not normally written to, etc.
On the Galaxy Nexus (using a shipping bootloader), it seems that the only "oem" commands available to us are lock and unlock.
How long will we have to wait?
Lol
btort1 said:
How long will we have to wait?
Click to expand...
Click to collapse
You never have to wait to unlock the bootloader on a Nexus device.
You can unlock it by simply enabling usb debugging in developer options (and enabling oem unlock option if present) then boot to fastboot and do a fastboot oem unlock in a command prompt. Follow the on screen prompt and you will be bootloader unlocked (your system will be wiped).
If you got a bit lost by those instructions you can use my android toolkit to do everything automatically *HERE*.
Mark.
ITGuy11 said:
Lol
Click to expand...
Click to collapse
Can we have a bounty for it? I got $100 to donate
jk
mskip said:
You never have to wait to unlock the bootloader on a Nexus device.
You can unlock it by simply enabling usb debugging in developer options (and enabling oem unlock option if present) then boot to fastboot and do a fastboot oem unlock in a command prompt. Follow the on screen prompt and you will be bootloader unlocked (your system will be wiped).
If you got a bit lost by those instructions you can use my android toolkit to do everything automatically *HERE*.
Mark.
Click to expand...
Click to collapse
Made this page before researching
Sorry it's my first nexus device (came from moto x pure) and I thought it was the same as motorola and asking for a token It's actually much faster and easier haha
btort1 said:
Made this page before researching
Sorry it's my first nexus device (came from moto x pure) and I thought it was the same as motorola and asking for a token It's actually much faster and easier haha
Click to expand...
Click to collapse
Congrats on your first Nexus device! Nexus devices are easier in everything
mskip said:
You never have to wait to unlock the bootloader on a Nexus device.
You can unlock it by simply enabling usb debugging in developer options (and enabling oem unlock option if present) then boot to fastboot and do a fastboot oem unlock in a command prompt. Follow the on screen prompt and you will be bootloader unlocked (your system will be wiped).
If you got a bit lost by those instructions you can use my android toolkit to do everything automatically *HERE*.
Mark.
Click to expand...
Click to collapse
0.0 said:
Congrats on your first Nexus device! Nexus devices are easier in everything
Click to expand...
Click to collapse
Thanks, yeah I wish I tried a Nexus sooner. In 2013 I came from an iphone 4s to S4, xperia z1, s5, m7, g3, note 4, g3 again, htc desire eye, xperia z3c, moto x pure and now a nexus 5x! (I know I lost a few hundred bucks from depreciation and reselling )
What turned me away from the nexus 5 before was the battery drain people kept complaining about. I wish I just went ahead and bought one, I'd probably still be using it instead of trying out all those phones...especially the ones with touchcrap ui :crying: After owning 5.5+ inch phones, I've realized phablets aren't for me.
Nexus 5x with 6p specs would have been my perfect phone but this will do until next year
oh common
jk[/QUOTE]
As title suggests, didn't know if this is possible or not.
Nitemare3219 said:
As title suggests, didn't know if this is possible or not.
Click to expand...
Click to collapse
I recommend against it. What's your reason for wanting to do this? There's really not much benefit to doing it.
But it's certainly possible and simple to do.
jollywhitefoot said:
I recommend against it. What's your reason for wanting to do this? There's really not much benefit to doing it.
But it's certainly possible and simple to do.
Click to expand...
Click to collapse
I may be wanting to return my 10 - was a purchase directly from HTC. Just not sure if it fits my wants as a device. Their return policy doesn't say anything about reusing unlocked devices, but I felt that may be bad if I returned it unlocked.
Nitemare3219 said:
I may be wanting to return my 10 - was a purchase directly from HTC. Just not sure if it fits my wants as a device. Their return policy doesn't say anything about reusing unlocked devices, but I felt that may be bad if I returned it unlocked.
Click to expand...
Click to collapse
Well if you received an unlocked code from htcdev, they will be able to tell you unlocked it, so I'm not sure how much it matters. Also, even if they didn't check the htcdev database, when you relock, your bootloader will show "relocked" instead of "locked".
I'm not sure what their return policy is on unlocked devices. Good luck.
Oh, and if you want to relock it, just go to download mode and enter "fastboot oem lock" in a command window.
Moderator Information,
I have removed the above two posts. The commands given are device specific commands. If used on another device, it could brick the phone.
If you want to relock your bootloader for warrenty, you'll have to S-OFF first and use some device-specific procedure(which hasn't released yet) to make it completely stock-like again.
Stephen said:
Moderator Information,
I have removed the above two posts. The commands given are device specific commands. If used on another device, it could brick the phone.
Click to expand...
Click to collapse
thank you I apologize for the mishap
Mark112887 said:
thank you I apologize for the mishap
Click to expand...
Click to collapse
As an aside if you do run that specific command on this device you will end up with some serious problems.. the adb echo command of the past devices is more.
Sent from my HTC6545LVW using Tapatalk
jollywhitefoot said:
Well if you received an unlocked code from htcdev, they will be able to tell you unlocked it, so I'm not sure how much it matters. Also, even if they didn't check the htcdev database, when you relock, your bootloader will show "relocked" instead of "locked".
I'm not sure what their return policy is on unlocked devices. Good luck.
Oh, and if you want to relock it, just go to download mode and enter "fastboot oem lock" in a command window.
Click to expand...
Click to collapse
I tried "fastboot oem lock" but it bounced back with a failure saying it's an unknown command. I tried a few other commands as well.
Fastboot flashing lock
Fastboot lock_bootloader (which was in the command list )
Fastboot OEM relock
But none worked. Need help.
Rijul30 said:
I tried "fastboot oem lock" but it bounced back with a failure saying it's an unknown command. I tried a few other commands as well.
Fastboot flashing lock
Fastboot lock_bootloader (which was in the command list )
Fastboot OEM relock
But none worked. Need help.
Click to expand...
Click to collapse
You can use All in one toolkit to relock bootloader
https://forum.xda-developers.com/htc-10/development/tool-htc-10-m10-one-toolkit-v1-0-t3538317
adriano25028 said:
You can use All in one toolkit to relock bootloader
https://forum.xda-developers.com/htc-10/development/tool-htc-10-m10-one-toolkit-v1-0-t3538317
Click to expand...
Click to collapse
Will it wipe the device ?
Rijul30 said:
Will it wipe the device ?
Click to expand...
Click to collapse
Yes.
adriano25028 said:
Yes.
Click to expand...
Click to collapse
Thanks !
Hello,
i'am wondering what the best approach to root a MZP. What i understand there is a procedure via "fastboot oem get_unlock_data" and get a key from Motorola. And a second via Developer Settings ->" OEM unlock".
What is the difference?
thanks
klofisch
klofisch said:
Hello,
i'am wondering what the best approach to root a MZP. What i understand there is a procedure via "fastboot oem get_unlock_data" and get a key from Motorola. And a second via Developer Settings ->" OEM unlock".
What is the difference?
thanks
klofisch
Click to expand...
Click to collapse
Neither of them have to do with rooting, they have to do with unlocking the bootloader, which is the first step. Then you need to flash a customer recovery like TWRP, then you can flash SuperSu and have root.
ah right. ok,...but what does "OEM unlock"
klofisch said:
ah right. ok,...but what does "OEM unlock"
Click to expand...
Click to collapse
It used to have to be done via a command, not it is built into Developers options.
Here read this to to better understand what unlocking your bootloader will entail.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Once your bootloader is unlock, then follow this one to flash TWRP and properly root.
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
RenaldiDroidXDA said:
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
Click to expand...
Click to collapse
I think your problem is you used 'fastboot oem unlock' instead of 'fastboot flashing unlock.'
Well, now I see the problem.
Now I need to know how to fix it .-.
RenaldiDroidXDA said:
Well, now I see the problem.
Now I need to know how to fix it .-.
Click to expand...
Click to collapse
did you enable usb debugging in developer options?
lucky_strike33 said:
did you enable usb debugging in developer options?
Click to expand...
Click to collapse
Yes, I did. adb works quite well enough, but fastboot detects nothing.