Related
Just received my Solar Red U11. Is there any reason not to unlock the bootloader right away?
I'm not planing on rooting it or installing any custom ROMs anytime soon, but I'm also not 100% sure I'm gonna be keeping the phone (few things I need to see if I can get used to).
Should I just unlock it now so I don't have to (potentially) wipe my device at a later date?
Thanks!
techboy10 said:
Just received my Solar Red U11. Is there any reason not to unlock the bootloader right away?
I'm not planing on rooting it or installing any custom ROMs anytime soon, but I'm also not 100% sure I'm gonna be keeping the phone (few things I need to see if I can get used to).
Should I just unlock it now so I don't have to (potentially) wipe my device at a later date?
Thanks!
Click to expand...
Click to collapse
if you decide to unlock at a later date you can back up your stuff to your computer unlock then put it back.all the other stuff is your choice, me, mine is unlocked out of the box.
it only wipes your internal, not the ext_sdcard
At some point, one of the future updates could prevent you from unlocking it. That would eliminate the
ability to modify your phone's software. If you'll never do that, probably doesn't matter if unlockable.
The only downside is the orange reminder splash screen that is displayed on boot-up.
Aldo101t said:
if you decide to unlock at a later date you can back up your stuff to your computer unlock then put it back.all the other stuff is your choice, me, mine is unlocked out of the box.
it only wipes your internal, not the ext_sdcard
Click to expand...
Click to collapse
Aldo, how do you back up data & /or app settings of 3d party apps fm a device w/locked Bootloader & no root?
Also, what & how much boot delay is there if you unlock bootloader - I saw someone post a pic that shows the screen in text mode & a warning abt startup not beginning for 5 seconds.
Also, please clarify, HTC gave warnings about losing the Fingerprint capability if you unlock the bootloader; I just want root,so I can run Titanium B/U & some root-needed apps- put really like the Fingerprint feature- was that an old warning? The posted HTC warning says you can'telock the bootloader- but I just saw someone talk abt re-locking their bootloader bc they want to sell the device as clean.
Any help much appreciated, TIA oldwolf
Boot loader won't effect your fingerprint scanner....never heard of had that.
The warning about losing fingerprint scanner functionality on HTCDev refers to the One Max (2013), and only to that device AFAIK.
Negative effects of unlocked bootloader
Has anybody found HTC U11 losing OEM applications, sound and camera quality or other pre installed applications after unlocking the bootloader? Also please tell me whether the unlocking procedure is same for Android oreo udate.
Thanks.
sudheersharma said:
Has anybody found HTC U11 losing OEM applications, sound and camera quality or other pre installed applications after unlocking the bootloader? Also please tell me whether the unlocking procedure is same for Android oreo udate.
Thanks.
Click to expand...
Click to collapse
Go to developer options ( on setting) and allow unlocked bootloader ,,,ok finish
Unlocking the bootloader has no adverse effects. You can still update ota. If the bootloader is ever unlocked there is no reason to relock it unless you are returning the phone to the store.
Hi,
I have once rooted my google pixel, but I changed my mind, and decided to unroot it and lock the bootloader.
I chose "lock" in the twrp menu, and I entered an endless loop.
Now the bootloader is locked and won't boot. The phone just splashes the initial screen and off, a few seconds after that, splashes the screen, and off,.....repeatedly. It looks like as soon as the initial "GOOGLE" screen appears, the phone resets itself.
I turned on with the volume down button on, and connect to the desktop computer (I use linux with adb and fastboot installed which work perfectly) and enter "fastboot flashing unlock", but it returns
Code:
$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.009s
I also tried to enter recovery mode, but it began to splash initial screen on and off again.
How can I recover from this situation?
Thanks in advance!
edit:
"fastboot flash recovery twrp-3.3.0-0-sailfish.img" now returns like this.
Code:
$ fastboot flash recover twrp-3*img
Sending 'recover' (31000 KB) OKAY [ 0.892s]
Writing 'recover' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.074s
edit2:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Thanks. I'll give it a try. I'm almost abandoning.....
junglism93 said:
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Click to expand...
Click to collapse
I tried it now. Most of the procedures were fine, but the important parts (write .img) failed. I attach the logfile. I abandoned....
maverick6664 said:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Click to expand...
Click to collapse
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
matusala said:
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
Click to expand...
Click to collapse
I've learned. "Don't root. Don't unlock bootloader."
@matusala you can unlock the bootloader and flash stuff as you did on the nexus line of devices. I'm on Q beta 5 with bl unlocked, I've had lineage running on it for a while and also had magisk etc installed. The key with these pixel A/B slot devices is that your system must be 100% stock before relocking the bootloader. If it is not It will end up bricked as you will no longer have a working boot image or recovery as they are in the same partition. The rule is to never relock the bootloader unless you are 100% sure that your system is 100% back to full stock.
I certainly won't be re locking my bootloader, ever!
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
matusala said:
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
Click to expand...
Click to collapse
I unlocked my bootloader back on stock pie, i have it on mine but it's greyed out as already unlocked so no idea on that one! My knowledge on A/B slot ain't great, it's just what I've read on here re the pixel bricking scenario so I didn't do the same when I unlocked my bootloader etc. I doubt running a separate ROM on each slot works as when you perform an update it will write to slot a or b (the slot you aren't using) and then hop onto the updated slot upon reboot, alsoif the update borks you can roll back to the previous slot and still have a working system.
That's about as far as my knowledge of it goes mate
Leaving the bootloader unlocked doesn't void the warranty or things like that, also it's a life saviour if *anything* goes wrong, even with official updates. Why not leaving that on?
The lesson here is not "don't root" or "don't unlock the bootloader", cause with an unlocked bootloader you can recover from pretty any kind of software malfunction.
Unfortunately, with a locked bootloader I've never seen anyone succesfully recover the device, cause you cannot send commands.
maverick6664 said:
I've learned. "Don't root. Don't unlock bootloader."
Click to expand...
Click to collapse
Hmmm......correction.
I would say:
"Root with caution. Otherwise don't root."
Rooting doesn't necessarily cause a trouble. Usually it helps. But my Google Pixel used to show alert screen message upon every boot. It's a bit messy.
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.
It seems these pixel phones are garbage compared to nexus line. Those were so much better!
matusala said:
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.!
Click to expand...
Click to collapse
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
TENN3R said:
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
Click to expand...
Click to collapse
I followed this guide and it worked. It unlocked my bootloader. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Now option is greyed out again in "off" position but it says "Bootloader already unlocked"
Maybe i got verizon model but in cell-unlocked state, because seller had written that it's unlocked. He meant provider lock of course.
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
junglism93 said:
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
Click to expand...
Click to collapse
Good luck @matusala from me also, and don't give in the first "Don't keep bootloader unlocked' alert screen!! Otherwise you might fall into a bad luck "bricked pixel" like me!
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
Nice to hear that. It was a good lesson to me. I have two xperia's (after google pixel dies, I bought one.) Somehow xperia's are not re-lockable. It is also mentioned in Sony Xperia forum. I guess it must be a warning from Sony. :laugh:
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
BTW, "adb oem lock" doesn't work with xperia. Sony seems to like leaving their products unlocked.
maverick6664 said:
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
I'm sure that is safe if you're updating from full stock to full stock, with mods on board a relock is almost suicidal and the threads about bricked pixels back that up.
If you don't like the warning screen, do what I do, don't watch your phone reboot
Click to expand...
Click to collapse
[S8+] Purchased a stock AT&T S8+ in a lot. It has latest bootloader and bad IMEI....
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
I used this video to figure out how to get the OEM Unlock option.
(input this after youtube url) watch?v=zhNhyT4F3e8&t=133s
Hopefully this helps.
domiluci said:
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
Click to expand...
Click to collapse
There is no OEM unlock on us snap dragon devices. Locked boot loader. Closest you will get is the combination firmware. But the OEM unlock in that does not work trust me on this. The imei is cert coded to the hardware. And can't be discussed on xda how to change. It's possible. But not by just anyone. The combination files are nougat. But their not going to help you out in this situation
I've had my Zenfone 6's bootloader unlocked for quite a while, but I relocked it a couple of days ago using the "fastboot oem asus back" command.
Everything went as expected and the phone did a reset. However, I can now not add any sort of lock to the screen.
Whenever I add a pattern, pin or password, the settings app crashes. Because I can't add one of these, I also cannot add fingerprint...
I've tried doing another factory reset without any luck and the phone seems to be working fine in all other ways...
Can anyone help?
Ask Asus team on ZenTalk. I haven't seen anything related in there. They should be able to clarify the issue.
Downgrade to pie and then let it upgrade to Q again. Fixed it for me when unlocking the bootloader. Something about locking/unlocking bootloader on Q breaks the fingerprint sensor but Pie doesn't have the issue.
DaConcho said:
Downgrade to pie and then let it upgrade to Q again. Fixed it for me when unlocking the bootloader. Something about locking/unlocking bootloader on Q breaks the fingerprint sensor but Pie doesn't have the issue.
Click to expand...
Click to collapse
Yes, what DaConcho said worked for me, trust him
Anyone in the US tried downgrading to pie using the firmware on Asus site?
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.