Related
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
I'm no expert at all but I ran motoapocolyps and if didn't do anything. It will either fail and your phone will be fine or, depending on what update you last took, unlock it. My phone is past due for unlocking the bootloader unless there is a way to downgrade it.
Hi
aviwdoowks said:
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
Click to expand...
Click to collapse
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
aviwdoowks said:
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
Click to expand...
Click to collapse
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
RikRong said:
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
Click to expand...
Click to collapse
"You can't cover up a BL unlock." <- THANK YOU! That is what I was trying to confirm....
I was thinking that since you can do this to cover up the unlocked bl warning: http://forum.xda-developers.com/showthread.php?t=1901444
that you can also do something to cover up the AP screen as well.
Since I'm rooted, and this phone is supposed to get 4.4, I'm not too upset that I can't unlock (Though with 4.4 I'll probably lose root ).. The stock rom is pretty nice on these, and root gives me pretty much anything I want for customization.
Thanks!
dreamersipaq said:
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
Click to expand...
Click to collapse
I am the one confused! I need to learn my codes.
Is it possible to re-lock and unlocked bootloader?
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Reason I ask is because I had it unlocked, got an OTA update from Verizon for kitkat, and soft bricked my phone. Got stuck in a boot loop with the unlocked bootloader warning message.
I just flashed back to 4.0.4 using RDS Lite 6.1.4. Id like to reset the boot loader to locked before updating to kitkat again.
It's not possible to re-lock. I've updated to KK and can confirm that the BL is, in fact, still unlocked.
I have read somewhere that when you unlock the bootloader, it actually physically blows some kind of physical fuse. or maybe I miusread it.
Someone had made a special logo.img you can flash to get rid of that message.
Although if you really want a locked BL phone, I'd be more than happy to trade you.
MxPhenom 216 said:
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Click to expand...
Click to collapse
Not that it helps, but in Australia, we do not get the nasty warning message after unlocking the bootloader. And I think that the phones are actually sold with an unlocked bootloader.
GnatGoSplat said:
Although if you really want a locked BL phone, I'd be more than happy to trade you.
Click to expand...
Click to collapse
:laugh:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Why would you want to do this?
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Is there any way to remove the Bootloader unlock warning ⚠ without relocking bootloader?
Sent from my XT1572 using Tapatalk
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Theres no reason really to relock it. Once its unlocked, the bootloader will show that it was unlocked regardless if you relock it.
atishey23 said:
Is there any way to remove the Bootloader unlock warning without relocking bootloader?
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Yes
Pyramid Head said:
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Click to expand...
Click to collapse
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
psandeepn said:
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
Click to expand...
Click to collapse
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
jason2678 said:
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
Click to expand...
Click to collapse
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
The answer is maybe... it depends what you have changed and what this OTA updater script actually checks for.
We know that a stock bootloader (which can be unlocked, that is not relevant), stock recovery, and stock system image are required to take an OTA. If the system image has been modified it can fail, and we know the updater has the ability to see if /system has EVER been mounted R/W and can fail for that condition although so far it doesn't seem Moto is going that extreme.
We do know a modified logo does not affect an OTA, in fact, you can even relock the bootloader with a modified logo so it must not be a significant check.
jason2678 said:
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
Click to expand...
Click to collapse
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
iks8 said:
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
Click to expand...
Click to collapse
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
acejavelin said:
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
Click to expand...
Click to collapse
You're right sorry
Hey guys, I found this quick and tidy way to get a fastboot console inside the bootloader. You can use it to do stuff like "fastboot format (partition)", etc.
GUIDE:
Go to fastboot mode on your Pixel XL
Open a CMD on the computer in fastboot directory and write in "fastboot flash bootloader pixelcustombootloader.img" (make sure the bootloader is in the directory or else it will not flash!)
Download: s000.tinyupload.com/index.php?file_id=44700284262726497364
Note: I am NOT responsible if this screws up anything.
Also I do NOT know if theres and copyright trouble with this, if there is, Mods go take this down.
I wonder if this is the bootloader that was seen in screenshots that was used to downgrade a Verizon pixel to unlock it?
DR3W5K1 said:
I wonder if this is the bootloader that was seen in screenshots that was used to downgrade a Verizon pixel to unlock it?
Click to expand...
Click to collapse
If the bootloader is locked you can't flash anything or boot anything that isn't signed by Verizon/Google/whoever.
As far as I know there's never been a downgrade workaround available where pixel8 wasn't patched, but could be wrong.
bobbarker2 said:
If the bootloader is locked you can't flash anything or boot anything that isn't signed by Verizon/Google/whoever.
As far as I know there's never been a downgrade workaround available where pixel8 wasn't patched, but could be wrong.
Click to expand...
Click to collapse
There was a guy positing pictures of someone from a cell phone shop where he was recording the procedure that they did to his phone it was a signed bootloader that allowed him to downgrade for an unlock. It was labeled HTC which people thought was weird.
DR3W5K1 said:
There was a guy positing pictures of someone from a cell phone shop where he was recording the procedure that they did to his phone it was a signed bootloader that allowed him to downgrade for an unlock. It was labeled HTC which people thought was weird.
Click to expand...
Click to collapse
Eh.. 3rd party pictures that don't come with a detailed "how to" are 99% BS or marketing.
Like I said I'm not all knowing but I'm pretty in touch with the goings-ons of the pixel and have never heard of a downgrade method for a locked bootloader.
If this shop has a private method of doing so then they sure as hell wouldn't let someone take pictures of the process.
Yea like u said the guy said they were spy shots that he snuck in. Probably bs like you said. I could careless for myself my Verizon pixel is unlocked. Feel bad for those stuck locked though. Wishful thinking I suppose.
Yeah, don't flash your bootloader with anything other than stock google imgs. If your bootloader is messed up, how do you get into fastboot to fix it? Can't change slots either afaik.
Thanks for sharing, this has loads of potential - could be used on-the-go to temporarily recover from the freeze/reboot glitch (flashing stock images tends to lower the probability of the glitch for a day or two), plus we could actually have tetherless TWRP support for Oreo with this as you could use it to fastboot boot the TWRP boot img.
That being said, I'm reluctant to flash a random bootloader on my phone with no info on where it came from. Did you make this? If so is it a patched version of the most recent bootloader? If not, where'd you find it? We need more info.
How unlock New Oreo bootoader C0.92? Motorola site dont do this for this version .... After update to Oreo...my IMEI is 0 ...so i need unlock bootoader to flash twrp and flash EFS! 7.0 unlock ok but 8.1 no
Bootoader can be downgraded?
Yes, if you want hard-brick.
To install TWRP with this put the EFS to return the IMEI, this new bootloader must be unlocked, in the site of the motorola says that the device is not unlockable, with the old bootloader was, and wanted to know if anyone has any idea how To solve this, would I have some way without having to enter the motorola website?
anyone who has upgraded to oreo with the official zip could get on Motorola's website whether the device is unlockable or not? Has anyone tried unlocking the C0.92 bootloader yet? only I who tried and saw that it can not? (I.e.
Thank you for letting us know that unlocking might be a problem after upgrading. I've been waiting to unlock until I get the update, but because of your post I won't have the problem that you did. Your sacrifice wasn't in vain!
I had my doubts whether moto would let us unlock BL easily and promptly, thats why just few days before the official 8.1, I unlocked, twrp+rooted and flashed AEX.
Lucky me.
But I am sure soon there will be some way to unlock BL of 8.1
Till then dont try anythng stupid as u asked about "dwngrading BL" which is potential brick.
Did you select "allow oem unlocking" in developer settings?
I have a untouched bootloader, i wish i had knew this before i installed the Oreo OTA, my G5 Plus is retbr and lenovo/motorola site tells me that my device isn't qualified for unlock too, really sad.
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
motolio said:
Did you select "allow oem unlocking" in developer settings?
Click to expand...
Click to collapse
yes...
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
you did? oO....with bootloader C0.92? tried many times e nothing... unlock have a limite of times on motorolas website?
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
mine bootload codes have 4 lines...in the exemple have 5 lines....
Yeap, tried on my C0.92 bootloader and it didn't let me unlock my phone either. Please Lenovo, don't do this to us.
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
That's great news!
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
ok guys....this guide is true!!! bootloader unlocked now.....thx bro!
Unlocked.... Restaured EFS and get IMEI....but with no signal.... EFS work only with old bootloader...
UncolourTV said:
I just tried again using this guide and about 30 minutes later i got the unlock code, fastboot said it was unlocked, restarted the phone and everything working and good to go. Its twrp time!
Click to expand...
Click to collapse
david.gs.gm said:
ok guys....this guide is true!!! bootloader unlocked now.....thx bro!
Click to expand...
Click to collapse
What's the difference with that guide? Seems to me just like any other Motorola unlocking procedure.
prokaryotic cell said:
What's the difference with that guide? Seems to me just like any other Motorola unlocking procedure.
Click to expand...
Click to collapse
Exactly. There is no other way to get your bootloader unlocked.
Sent from my Moto G5 Plus using XDA Labs
prokaryotic cell said:
What's the difference with that guide? Seems to me just like any other Motorola unlocking procedure.
Click to expand...
Click to collapse
I was trying to unlock using the brazilian website, that is basically the same besides is obviously written in portuguese. The site on the guide seems that is a north american version. It worked, that's what matters.
i unlocked the bootloader, put twrp, flashed my efs and my imei return, ok....but have no signal oO, downgraded to nougat and with EFS, have IMEI and signal ok, only on oreo i dont have signal ... with TWRP flashable Oreo is same.
looking at the *#*#4636#*#* says that the radio is off, I have the IMEI that I got through my backup of EFS, this occurs only in the oreo, in 7.0 when using EFS everything is normal, only the VoLTE is missing.