Related
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ??
This methode work with So Flashtool ?
I'm going to make SPflashTool working. I have some issue
Riadh300 said:
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ?
Click to expand...
Click to collapse
Thanks for your enthusiasm but my method does not Unlock the bootloader so you should change your thread title.
As I told you I will open a thread when the method is fully tested by a few advanced user's who are testing it now and you will be given full credit for all your help.
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
bigrammy said:
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
Click to expand...
Click to collapse
Thanks for this informations ! ?
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
Actually, spflashtool bypasses the bootloader in this instance, so the bootloader is untouched and you still flash twrp
---------- Post added at 08:35 AM ---------- Previous post was at 08:02 AM ----------
bigrammy said:
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
Click to expand...
Click to collapse
Not to be pessimistic, but you do realise that even with all your precautions,people will still not read properly and will still brick their phones, no matter how many precautions you take. Even if you had an app that requires you to click one button to do everything,there are still people who will do it wrong. That said I think I know of one or 2 people in this Nokia 3 forum who were able to recover their phones using spflashtool AFTER the phone couldn't even be detected by their pc, even OST flashing was not possible .
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
redweaver said:
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
Click to expand...
Click to collapse
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
bigrammy said:
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
Click to expand...
Click to collapse
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
bigrammy said:
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
Click to expand...
Click to collapse
So how did you get your phone back anyway?
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
redweaver said:
So how did you get your phone back anyway?
Click to expand...
Click to collapse
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
OK, one thing though, before flashing the recovery you might want to do a backup of the stock recovery if you don't already have one. That's what I did, so after I got root, flashed back my stock recovery. Magisk is the root manager ,
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
bigrammy said:
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
Click to expand...
Click to collapse
oh you mean you went through hoops to get your phone back? I thought you would say you got a stock recovery somewhere and flashed using spflashtool or used the ost method. I didn't actually expect you to outline the steps you used. BTW, first time I flashed twrp AFTER unlocking bootloader, I got stuck in a recovery bootloop too. I had to flash my phone with OST then retry the process again.
One other thing, I think OST is actually a propriety software that is supposed to work for lots of phones, at least I know that users of other non mediatek Nokia phones also use it to recover their phones (with the corresponding stock images of course)
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
Magisk hide allows you get OTA's see the Magisk thread and yes it will work on any android version.
@redweaver
I am glad you got out of the loop but your clearly a more advanced user hence why I ask you to test. :good:
The OST is very convoluted for use on MediaTek devices and is very unnecessary it also requires unnecessary FIH software to be installed on the phone to work properly.
They likely choose this method to work across different SoC's but it's not what MediaTek use SPFlashTool is MediaTeks own software.
EDIT: Sorry lost internet for a while then.
I continue: Good news is I do not think they will be able to remove SPFlashTool use as it's binary on device which lives on a none volatile area ram chip or radio chip and is loaded at the factory so I doubt it can be updated via a OTA. :fingers-crossed:
Sony actually replaced this and this is the only device I have been unable to recover and even Sony were replacing the boards of bricked devices but if they had left the Mediatek binary in there it would not of been a issue as SPFlashTool would of been able to recover them. :good:
guys, old thread, i know, different device, i know, but ive been in the dark and this is what most resembles my issue.
any hints would be appreciated, read all 2 pages, can you believe it? im a very average xda enthusiast.
worries out of the way, my sincere thanks beforehand follow.
issue
carrier doesnt get in the way
oem doesnt get in the way
oem unlock toggle, check, adb debugging, you and i know the drill, no driver/cable issues
cannot for the life of me unlock bootloader, this one would take the newer command, however i tried them all ive come accross to no avail
output encourages me to unlock first, howwever not a clue is given as to how to accomplish it. this isnt the flash a file type of unlocking, either, at least not oem provided. going nuts.
go ahead and feel free to issue "advanced" directions (meaning, like your voicemail, instead of "for voicemail configurations press 8" and just "configurations 8"
spreatrum, not mtk
x120c
came with oreo go, treble enabled per getprop
i dont know what else, please
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Blackion said:
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Click to expand...
Click to collapse
If there's an option for OEM Unlock in developer settings enable that to disable FRP
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
reflash the stock fw using odin
Not sure
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Blackion said:
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Click to expand...
Click to collapse
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
corvasce03 said:
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
Click to expand...
Click to collapse
I used smartswitch when I encountered frp lock
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
1eStar said:
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Click to expand...
Click to collapse
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
kiwigi said:
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
Click to expand...
Click to collapse
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
corvasce03 said:
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
Click to expand...
Click to collapse
@corvasce03
Thanks.
I think I got back allright except this here and I used exactly the same stock(file) as a year ago
Someone Help My Soul!!!
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Cirphrank said:
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Click to expand...
Click to collapse
It stops someone stealing your phone, wiping it, installing new firmware and using it as if it was new. If you know the gmail and password you put on the phone to access the play store then you just need to re-enter it after the phone restarts. FRP will only kick in if you have flashed new firmware to the phone.
I have a new firmware flashed on the phone.
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Cirphrank said:
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Click to expand...
Click to collapse
I'm not sure what you mean. If you have a Google account on the phone that you know the email and password to, then just reboot the phone. FRP lock will only activate if you flash new firmware to the phone without removing the Google account first.
Your device should only have 1 Google account registered on the device which let's you access Play store etc. If there is more than one, you need to delete the ones you don't know the email and password to.
Okay...
Oh, okay, now I am getting the rationale.
Albeit, when I flashed in the new custom firmware, it started give me the undo changes by restarting your phone notification, like it did the first time ever that I got the lock. I didn't click it, activated an app that discarded the notification rather.
Now it makes me doubt if I had really removed my mail before flashing the phone.
hey
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
stasikkk777 said:
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
Click to expand...
Click to collapse
Yeah you've messed it up by not signing out of account before unistalling xposed. When you say 3 different rom's do you mean stock or custom?
Even in this state you should be able to flash a stock rom to the device with Odin and it will ask you to type the google email and password after boot.
Always turn off FRP lock before modifying the phone, it's a really annoying feature.
I know I'm probably out of luck here, but I've seen some mention of some kind of "Q method" for unlocking the bootloader so I was curious if I missed something along the way and there's a method to unlock the bootloader that doesn't involve requesting the BL unlock code from T-Mobile/OnePlus?
I'd really like to install TWRP so I can root with magisk and enjoy rooted stock, but requesting that code instantly voids the warranty even if you never use it and this phone hasn't been on the market long enough yet to be certain there aren't some defects that might pop up and I don't want to get stuck paying the insurance deductible for something a warranty request would normally take care of for free.
Again, I know I'm probably asking the impossible, but is there some new method (all forum searches have returned the normal method) to unlock the BL without signaling T-Mobile that I'm being a cheeky monkey?
Unlocking the bootloader can be done without getting a code from OnePlus by converting your T-Mobile device to the international version, but this still requires a SIM unlock (which as far as I know does not void your warranty).
While the second poster is right.....you are also right about the Q method u need dp3 just somewhere around here you could even Google it that's how I found it. Basically use the msm tool to flash international rom (done without root or unlocking bootloader because it's a stock ROM) then u flash "Q" dp3 once done then boot into it go to settings tap build number 7 times to developer settings then you can tap "oem unlock" is fastboot command to unlock the bootloader. Then from there you can pretty much flash back to regular oos android 9 root it etc.... Im sure there is a Guide somewhere. But that is the gist of it
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/
Here u go?
Thanks to both of you for answering my question! And it was even the answer I was hoping for! Now I can root my phone and just restore the original Bootloader if I need warranty service, just like the old days!
Hah. And now, while trying to find a way to do this on the OnePlus 9 the top Google result is my own thread for doing it with the OnePlus 7 Pro
Hey, i have android 10 stable installed in my phone. Just before i updated my phone (while i still was on 9.0.9), i also unlocked my bootloader, nothing else, no twrp or root. Now i would like to relock my phone again, because google pay is not working anymore, and im not willing to root my phone, because updating problems all the time etc. so can i relock my bootloader just by using command "fastboot oem lock" on fastboot mode? or do i have to do something else before that? also, is there possibility to brick phone somehow? if so, is there a way to fix it, while using OOS with android 10? i know this is stupid question but i hope someone could anwer it. Its not first time, when something is changed due new android update, and all previous guides are wrong.. =/
only reason i unlocked my phone, was that when i had oneplus 1, it bricked somehow oneday, and only way to get it back working, was empying whole phone, but there was possibility to recover data, if bootloader is unlocked, but i didnt have that, so i lost everything.. so i unlocked this one, to prevent that problem, but now i have new, because Android Pay is not working..
I think you can use "Fastboot oem lock" as always, but it will wipe all your data (It's no way to skip that). I think it won't brick your phone
Yes, it won't brick your phone, just wipe your data.
Relocking succeed, thank you..
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.