Related
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that
How come this is possible?
New User... Maybe said:
How come this is possible?
Click to expand...
Click to collapse
This is not possible BL must be unlocked for any kind of flashing or installing twrp.
Sent from my Redmi Note 7 Pro using XDA Labs
hackermssharma said:
This is not possible BL must be unlocked for any kind of flashing or installing twrp.
Click to expand...
Click to collapse
I just realized that when I boot up the phone, it shows the "Redmi by Xiaomi" and below it says unlocked, (IDK if it has any relation). But the Developer options say that BL is locked and OEM Unlocking can be enabled. What does this mean?
This is same with me miui 11 stockrom
Magisk flashing creats bootloader locked
If i uninstall magisk it show unlocked again
Even Netflix installation works by this in playstore
New User... Maybe said:
I just realized that when I boot up the phone, it shows the "Redmi by Xiaomi" and below it says unlocked, (IDK if it has any relation). But the Developer options say that BL is locked and OEM Unlocking can be enabled. What does this mean?
Click to expand...
Click to collapse
Well that's cos at one point you had unlocked your bootloader and might have dirty flashed MIUI or used fastboot images, which aren't able to recognise the state. But in reality it remains unlocked and it just shows locked in the settings.
Naveenthemi said:
Well that's cos at one point you had unlocked your bootloader and might have dirty flashed MIUI or used fastboot images, which aren't able to recognise the state. But in reality it remains unlocked and it just shows locked in the settings.
Click to expand...
Click to collapse
Ohhh! Thanks! I'm learning so much.
Naveenthemi said:
Well that's cos at one point you had unlocked your bootloader and might have dirty flashed MIUI or used fastboot images, which aren't able to recognise the state. But in reality it remains unlocked and it just shows locked in the settings.
Click to expand...
Click to collapse
Yes true. It is unlocked. The unlocked message at boot verifies that bl is unlocked.
Sent from my Redmi Note 7 Pro using XDA Labs
hackermssharma said:
Yes true. It is unlocked. The unlocked message at boot verifies that bl is unlocked.
Click to expand...
Click to collapse
I apologize if this is a bit too late, but I have a follow up question. Can I try to unlock the bootloader even if it's really unlocked just to connect my account to my phone or something like that?
New User... Maybe said:
I apologize if this is a bit too late, but I have a follow up question. Can I try to unlock the bootloader even if it's really unlocked just to connect my account to my phone or something like that?
Click to expand...
Click to collapse
If it's unlocked, the Mi account is already linked tho.
Even if you try you won't see a difference, maybe the unlocked symbol might come up.
Naveenthemi said:
If it's unlocked, the Mi account is already linked tho.
Even if you try you won't see a difference, maybe the unlocked symbol might come up.
Click to expand...
Click to collapse
So I won't have any problems doing it? The thing is I bought my phone with the BL already unlocked.
New User... Maybe said:
So I won't have any problems doing it? The thing is I bought my phone with the BL already unlocked.
Click to expand...
Click to collapse
Woah. Unauthorised seller eh. Are you sure you are running the Orginal MIUI? The reason Xioami started locking away the bootloader was cos of these unauthorised sellers, unlocking the device and flashing it with an outdated ROM. You should try, Go to Developer settings, link your current Mi account and then proceed to unlock. Or if it says an acc is already linked, lock the bootloader (only if on MIUI Stock, Custom ROM would lead to a bootloop), and now go link your account. (Do take backups before proceeding)
Naveenthemi said:
Woah. Unauthorised seller eh. Are you sure you are running the Orginal MIUI? The reason Xioami started locking away the bootloader was cos of these unauthorised sellers, unlocking the device and flashing it with an outdated ROM. You should try, Go to Developer settings, link your current Mi account and then proceed to unlock. Or if it says an acc is already linked, lock the bootloader (only if on MIUI Stock, Custom ROM would lead to a bootloop), and now go link your account. (Do take backups before proceeding)
Click to expand...
Click to collapse
Well, I did flash the latest MIUI Indian Global ROM a few weeks back so maybe I am running Original MIUI?
But I'm still gonna try to "unlock" it. And is there an option to keep all data after the unlock?
EDIT: I just read the Mi Unlock Tool's disclaimer and how they say some features won't work after the unlock. I mean, I know mine is unlocked but I think I'll just keep those features.
New User... Maybe said:
Well, I did flash the latest MIUI Indian Global ROM a few weeks back so maybe I am running Original MIUI?
But I'm still gonna try to "unlock" it. And is there an option to keep all data after the unlock?
EDIT: I just read the Mi Unlock Tool's disclaimer and how they say some features won't work after the unlock. I mean, I know mine is unlocked but I think I'll just keep those features.
Click to expand...
Click to collapse
Usually the first time you unlock it wipes your internal storage , but it doesn't wipe it in the subsequent unlocks (as far as I've tried). Yep it doesn't actually affect any system functions.. everything is as smooth as before..Find my device works fine as well..the only risk is that if your device gets stolen they could easily wipe MIUI and bypass that account lock by flashing a custom ROM.
Hello,
I couldn't unlock the bootloader as the OEM unlocking's disabled and i can't access system! Everything's erased!
Any help????
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
junglism93 said:
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
Click to expand...
Click to collapse
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
eldeen said:
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
Click to expand...
Click to collapse
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
junglism93 said:
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
Click to expand...
Click to collapse
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
eldeen said:
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
Click to expand...
Click to collapse
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
AndroidNazi said:
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
Click to expand...
Click to collapse
Thanks for help, but could you please show me how to do that?
eldeen said:
Thanks for help, but could you please show me how to do that?
Click to expand...
Click to collapse
Make sure you have the latest fastboot. On the bootloader your phone will either say "slot a" or "slot b" and you should type "fastboot --set-active=b" if you are on slot a or "fastboot --set-active=a" if you are on slot b
still didn't fix the problem... any probable solutions please?
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.