Database Users

Next Atrix Bootloader is UNLOCKABLE

As you've probably seen, the2dCour has a very tasty morsel of what's to come for us all. He's one of the many great people in #moto-atrix, including Jug6, Edgan, Sogarth, unknown, Brandon15811, and helpful friends, Pauly, dasmoover, cranch, YellowGTO and more, who have been helping me poke at the Atrix for many weeks. Also, if I know anything at all (I don't) it's thanks to [mbm] and Skrilax and xvilka and the others who implemented the hard work of 2nd init and kexec and beat their head against Motorola's signature chain on the previous generation of phones.
But our biggest thanks go to Motorola. A very friendly 'community-minded engineer' at Motorola posted an interesting message in hex on their support forums yesterday. Turns out, maybe it's no joke after all.
(http://forum.xda-developers.com/showthread.php?t=1134786)
This got me to thinking. I was already looking through some of the ascii / hex of the bootloaders. Search for VOID and you'll find something completely new in the HKTW (Hong Kong / Taiwan) build, which is not in the CGs for any prior Atrix bootloader:
Code:
$ strings CG42.img | grep INFO
...
INFOUnlocking your device can permanently VOID your warranty.
INFOThis process cannot be reversed. If you wish to proceed,
INFOreissue the unlock OEM command containing the unique ID
INFOof your device:
On Edgan's engineering phone, the HKTW build enables a command you may all be familiar with:
fastboot oem unlock
It looks as if it asks you to issue the command twice, after giving you a unique ID (based on your phone) you must enter in. Surrounding parts of the CG suggest this will wipe your userdata much like a "fastboot -w" currently does. Our hypothesis about the fuses may also be backwards, and it is unlocking which burns a fuse, thus making this an operation which "cannot be reversed."
So, I think we can all look forward to Gingerbread's release for many reasons!!!
PS. Beyond voiding the warranty, or access to support, such an operation could potentially make your phone ineligible for OTAs, future retail .sbfs, etc... and we do not yet know which carriers will get it. So don't get TOO excited
PPS. If this is headed to the official release, I'd like to give a HUGE thanks to Irwin Proud and all the others who petitioned Motorola to make this happen!
But there's no time to rest. Now we must pressure all the carriers!

Confirmed working for AT&T users!! Eval emailed me the good news this morning, so we tried it on leaked GB for the Atrix 4G on AT&T.
http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
I tested it out on my Gingerbread beta builds.

This is excellent news everyone.
Be patient, we need to see if this update hits all our devices, but when it does, I guarantee there will be no shortage of Roms and Mods that will come as a result.
I actually think Motorola may see a spike in sales when 2.3.3 hits their Atrix phones.
Thank you everyone who showed your support for the Unlock Motorola campaign and went out of their way to make their voices heard. Together we stand and together we claim victory.
Thank you Motorola.

Intresting

Yay!
Of course, the question becomes... what next?

Sogarth said:
Yay!
Of course, the question becomes... what next?
Click to expand...
Click to collapse
Now that Moto's on our side I will (proudly) use my lapdock. How's your awesome Webtop2SD with my mknod sdcard hack going?
But yes, someone must do the much more time-consuming work of porting CM or other AOSP forks. And we have to pray AT&T lets this happen...

eval- 4 president

eval- said:
But yes, someone must do the much more time-consuming work of porting CM or other AOSP forks. And we have to pray AT&T lets this happen...
Click to expand...
Click to collapse
When this happens, I WILL pinch myself to make sure I'm not dreaming!!

If Bell, lets say, got this and at&t didn't, would we be able to somehow port it?
Swyped from my HoneyGlowed Atrix

Way to guy team This kicks ass!
P.S. the2d is a troll..but a damn good one.

Has this been actually verified, (is there a way to verify on an engineering phone?), as unlocking a bootloader, or is this at the moment still speculation as to what might be possible after the GB update?
Could this just be Moto laying the groundwork for a future update which unlocks the bootloader without us having to do it ourselves voiding warranties, etc?

wakka wakka wakka
crossing fingers

wow! That's awesome news! Can't wait to hear if it's verified.

Verified -- http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
Video in a bit.

kennethpenn said:
Verified -- http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
Video in a bit.
Click to expand...
Click to collapse
Im cheesing so hard right now
Sent from my Moto Atrix using XDA Premium App

Very interesting! Of course, if we have Gingerbread, not much point in CM7 for me, is there an ice cream sandwich or whatever in between or after any time soon from the CyanogenMod bunch?
Cheers!

kennethpenn said:
Confirmed working for AT&T users!!
http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
I tested it out on my Gingerbread beta builds.
Click to expand...
Click to collapse
Holy freakin hell!!! Awesome just awesome!! Can ATT actually stop this from happening though?

joshyy_rey said:
Im cheesing so hard right now
Sent from my Moto Atrix using XDA Premium App
Click to expand...
Click to collapse
I have a raging clue right now

Just as I put my Atrix up for sale . Good news if the OTA comes out like this. I'll keep it and see i think!

Now let's get that CWM Recovery on it!

I Don't Believe On The Motorola Promise About That Unlockable Bootloader

hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...

Its unlocked for ever
Sent from my MB860 using Tapatalk

Andrew149 said:
Its unlocked for ever
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
you mean locked!? right? lol

Er, dude you really need to read a little bit more on Development forum D:...
Its already unlocked!
Cheers

tan G said:
hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...
Click to expand...
Click to collapse
Moto said they are going to do it. They already dont it on the leaked future builds, not to mention the one Kenn is running which is an ATT GB. Not to mention this is the same way the did it on the Xoom. Theres nothing to worry about, its unlocked 4 ever.

lol - it's already done.

knigitz said:
lol - it's already done.
Click to expand...
Click to collapse
His point is he thinks its going to be removed from the final build. He states he is already unlocked himself.

LOL Someone needs to read through the forums. Bootloader is unlocked already.

Agree with Jay ... some one needs to read the OP ^_^ LOL
I, maybe just optimistically, think they will. The backlash, *****ing, low sales, the fact they said they would, and the fact that we have it already all points, IMO, to them releasing it. Motorola exec. - "Well the kids already have it so lets release it and make us look good." If they are on our side, at least give us what we want, they sell more. DROID - ground breaking - unlockable - sold like hot cakes. ATRIX - ground breaking - locked - not so much
posted via Atrix in lapdock

Does it really matter? For those that actually want an unlocked bootloader, they can get it in the dev forum. For the average user who will still get the OTA update, they probably didn't care about the bootloader to begin with.

Yaotl said:
Does it really matter? For those that actually want an unlocked bootloader, they can get it in the dev forum. For the average user who will still get the OTA update, they probably didn't care about the bootloader to begin with.
Click to expand...
Click to collapse
yup and average users will not probably bother coming to xda.
@OP
you are 2-3 months late regarding the creation of this topic.

madnav said:
yup and average users will not probably bother coming to xda.
Click to expand...
Click to collapse
I'm guess i'm still an 'average user' when it comes to android, but this is where I came to become a superuser (pun intended). I don't think i'm ready to mess with the HK build yet, but I definitely plan to flash a few ROMs when the official unlocked GB update comes through. And if it gets yanked before the final release, hopefully i'll know enough by then to use kenneth's version, or if worst comes to worst, the HK build.

zoso28 said:
I'm guess i'm still an 'average user' when it comes to android, but this is where I came to become a superuser (pun intended). I don't think i'm ready to mess with the HK build yet, but I definitely plan to flash a few ROMs when the official unlocked GB update comes through. And if it gets yanked before the final release, hopefully i'll know enough by then to use kenneth's version, or if worst comes to worst, the HK build.
Click to expand...
Click to collapse
It's not like the HKTW build is as unstable as the build TBH gave us. The only things that don't work is the front facing camera, and fingerprint sensor.
I just didn't restore from a backup, and you can fix the WebTop. So my phone is running fine, and it seems even more stable than FroYo (Besides the obvious bugs)

tan G said:
hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...
Click to expand...
Click to collapse
It really dose not matter if thay include the unlockable bootloader in every update or not. As long as their is a way for it to be done. Thats all the matters. Really only the N1 could be unlocked without much of any hassle. You just needed to know what commands to run,
Once its unlocked. Its unlocked. Cant go back. And just because you flash back to 1.57 or 1.83 and it no longer says "Unlocked" at the top. It is. All you need to do is flash the pudding and it will put those little words back.

pmcnano said:
Er, dude you really need to read a little bit more on Development forum D:...
Its already unlocked!
Cheers
Click to expand...
Click to collapse
this is not the case for other atrix versions than att

JayRolla said:
Moto said they are going to do it. They already dont it on the leaked future builds, not to mention the one Kenn is running which is an ATT GB. Not to mention this is the same way the did it on the Xoom. Theres nothing to worry about, its unlocked 4 ever.
Click to expand...
Click to collapse
that build is a build for developer and developer devices, there is no garantee that it will be the same for user-end releases, anyway I really hope for all people that you're right.
the sbf used to unlock our phone now (att) has been packed by someone in the dev team may by eval or 2dc... or both

JayRolla said:
His point is he thinks its going to be removed from the final build. He states he is already unlocked himself.
Click to expand...
Click to collapse
thumbs up! that's what I said

I will always have an unlocked bootloader

tan G said:
thumbs up! that's what I said
Click to expand...
Click to collapse
tang no matter what update motorola does in the future they wont be able to take away the unlock already created. with that said this post is useless, and a mod should close it, this will give the wrong idea to anyone coming to the forum looking for the unlock. who knows what motorola will bring in the future, fact remains, is unlocked and it aint going back.
"Pandora dosnt go back in the box man - he only comes out!!!!"

Dont feed the troll!!!!!!

4.5.91 Upgrade - Is there a "no flash back" warning?

Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408

Of course not, why would Motorola put in a warning like that. Motorola never excepts you to flash back to an older firmware.
Sent from my MB860 using XDA App

CaelanT,
I updated to gingerbread on rooted atrix 4.1.83. I did not notice any warning as you are hoping. Though the phone's root privilege is no more, Motorola has enabled the sideloading and I am happy with that.
Sent from my MB860 using XDA App

Are you serious?
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)

Technically, people shouldn't be able to flash back... we're not supposed to have RSD software or SBFs to flash in the first place.

ebaychuck said:
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)
Click to expand...
Click to collapse
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!

So the boot loader on the OTA is still Locked?!!!

yeah you could try that argument. they could give you the run around that you flashed using stuff not from their site or from their customer service portal and there could be some line in the warranty that would cover their ass from that stuff. but hey, worth a shot.

I updated to ota 4.5.9.1 during the soak and there was a big warning on the website, but nothing that I remember seeing when I downloaded and installed the software. They know the risk obviously. Surprised they wouldn't cover their behind during the install.
Sent from my MB860 using XDA Premium App

sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
Yes it is.
Beamed from WinBorg 4G via XDA Premium

CaelanT said:
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!
Click to expand...
Click to collapse
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.

ebaychuck said:
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.
Click to expand...
Click to collapse
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...

sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
From what I've been reading, yes...

ccrows said:
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...
Click to expand...
Click to collapse
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.

ebaychuck said:
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.
Click to expand...
Click to collapse
I've seen the Motoblur "improvements", but you still need an account, which is BS. Plus its a waste of time to freeze things in TiBU.
Between the last OTA that bricked many phones and the current Motoblur BS, I hope we can get Vanilla Gingerbread on this device more than ever. This will definitely be my last Motoblur phone I ever purchase.
Don't get me wrong I like Motorola a lot, but I also like to have a drama free phone...

I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...

Nah.
ccrows said:
I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...
Click to expand...
Click to collapse
Even with the few problems i'm enjoying having GB.. I guess I just like something new to look at.
I only miss a few things.
- The Happenings page that used to be attached to contacts. It was nice to be able to see the last post a friend made when calling them.
- Access control in Wireless Tether. (I can't remember if it worked on the Atrix or just my previous phone)
- Working Wired Tether..
- Setting review time on the camera.

CaelanT said:
Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
"Hi Motorola, I'm using non-public tools that have been leaked, and non-public SBF files that have been gotten in an unofficial capacity to downgrade my phone after the latest update. I'm not breaking my warranty, am I?"

motorola razr M prototype?

hi everyone, so i recently saw motorola razr m. the thing is, it had motorola markings on it like it is some kind of prototype or test device. it was running jellybean. just the markings were a bit curious, if someone can shed some light on what it was. thanks !

mikeverne said:
hi everyone, so i recently bought a second hand motorola razr m. the thing is, it has motorola markings on it like it is some kind of prototype or test device. it works totally fine, gsm unlocked and its running jellybean. everything runs as it should, just the markings are a bit curious. ive attached a pic to see if someone can shed some light on what it is. thanks !
Click to expand...
Click to collapse
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757

Somber73 said:
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757
Click to expand...
Click to collapse
yea i saw that too. but that doesn't really tell me anything apart from the fact that other phones like mine were also sold(which i already knew).

It would be best to just drop the subject. You have something rare, and if you want to keep it, I would keep it quiet. The guys on the Motorola forum are launching a pretty big investigation into this. I would delete your pic and edit your OP. Don't get me wrong, I DO NOT condone illegal activity, but there is a reason these are out in the open...

Regardless of the circumstances surrounding where or how he got the phone, there ought to be someplace where this guy can get answers as to its origin or what it is exactly without everybody overreacting.
Sent from my XT907 using xda app-developers app

It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!

It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta

cellzealot said:
It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!
Click to expand...
Click to collapse
thank you! and btw, that wasn't me who posted in the official forums lol. thats the lase place i would think of posting if i had a prototype haha.
sloosecannon said:
It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thank you! and yea, i agree.

that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.

jco23 said:
that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.
Click to expand...
Click to collapse
uh, actually im pretty sure he is telling the truth. its sort of a Pakistani craigslist.

RSD is proprietary software, owned by Motorola. While I know it's very easy to find online, it's not intended for public use. The rules of this site forbid discussion of software installation or use unless that software is distributed by Motorola or one of its partners.
That pretty much sums it up. Had he come to xda, he'd have gotten help. He didn't seem too open to helping the Motorola guys out though, so they didn't help him. Don't see why he would lie about that, he's just a poor guy who wants his confidential Motorola property to work for him... By asking the people that someone stole it from... Yeah...
Sent from my XT907 using Tapatalk 4 Beta

guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?

dasche said:
guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?
Click to expand...
Click to collapse
Nope. Since it's factory unlocked, you should be able to install TWRP and go about flashing whatever you want. It might be a wiser choice to buy a regular handset, since you want have Motorola property all over the front.

[PSA] Read before relocking your bootloader

I'm not sure what is up, this isn't a new thing, but people keep coming to me (1-2 a day) with this issue.
If your phone isn't stock, DO NOT RELOCK your bootloader. You will 'soft brick' it, and at this time there is no easy route to fixing it.
If you are on EE UK, Verizon or another carrier blocking bootloader unlocks, and you used dePixel8 to unlock it, DO NOT relock your bootloader unless you are sure you don't want it unlocked again.
Finally, dePixel8 is UNSUPPORTED. Don't come to me if you can't get it to work, don't come to me if you used it them messed up your phone by flashing something bad or whatever. Its on you.

What's the fix if this does happen?

infamousjax said:
What's the fix if this does happen?
Click to expand...
Click to collapse
There isn't one and no guarantee there will be one. Don't do this.

tw1tch175 said:
There isn't one and no guarantee there will be one. Don't do this.
Click to expand...
Click to collapse
Fair enough. Thanks

This should be pinned!!
Mods?
It was all just an illusion

Interesting.. glad this didn't happen to me. I did relock my bootloader once because i was having issues activating my SIM card. I wanted see if that was the reason. Once i did manage to get the SIM activated i went through the process of unlocking using the dePixel8 method again. I guess i won't be doing that again.

Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.

Cataire said:
Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.
Click to expand...
Click to collapse
This isnt a new warning, its pretty much standard "Dont relock with non stock firmware".
JTAG is a no go, would have to attack to the ufs and rewrite at the best least the boot.img

Eh things happen. I know better now. And now I need to learn how to make it right

I don't understand why anyone WOULD relock the bootloader of not stock

318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
Some people are not as experienced as us. Not hard to imagine, just noobs, no offense guys. You live and learn, no biggie. I say respect them and help them, I say welcome noobs.
If we expect our community to grow, we need to be respective of new comers.

318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.

Alpione said:
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
Click to expand...
Click to collapse
This is honestly the biggest reason I can see as to why this happens
Sent from my Pixel XL using Tapatalk

DELETED

ScytheSniper said:
First of all, I'd like to say thanks to all the hard work put into the dePixel8 BL unlock.
With that said, I would like to say a couple things about this particular statement.
1. It is slightly misleading, you can relock your bootloader and still unlock it again under the right circumstances. If your software is all stock and you use dePixel8 after relocking, it will unlock again.
2. This statement contradicts the previous one. You should probably avoid telling people "they can never unlock their bootloader again if they relock it" if there is ANY possibility that they can. After reading this statement from you in the unlocking thread I spent about 2 hours scouring threads to find out if this statement was always true, which it is not.
Again, thank you for all the hard work on getting this unlock out. The intent of my post here is only to help improve communication of potential problems.
Click to expand...
Click to collapse
There is nothing misleading about the post. The statements are true. Wait til tomorrow, when complaints start coming in about how people cant seem to unlock.

DELETED

ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
I'm not sorry. You are lacking information/knowledge on the subject. The OP statement is accurate.
The statement was made with good reason, based on fact and prior knowledge. You will see why tomorrow, when people start complaining.

DELETED

ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
The next security release should rollout tomorrow... And with that there will be a fix for VZW models preventing depixel8 from working. So IF you relock your bootloader after taking this update, we'll you'll be SOL. It's only misleading if you don't have prior knowledge of pretty much anything android.
I mean of course you can lock and unlock as many times as you want right NOW. Tomorrow will be a different story I guarantee.... But go ahead and be our guinea pig. I for one just say thank you @jcase and @beaups and listen to their advice. They've been around a long time and given us lots of goodies. I don't question them.

ScytheSniper said:
If I am lacking in knowledge and information why am I able to unlock and relock my bootloader at will on my Pixel purchased at Verizon?
Click to expand...
Click to collapse
I'm guessing you dont understand how depixel8 works.
I'm guessing you dont realize that google could remotely nix this in the butt any any moment
I'm guessing you are unaware of NDE63X at this point and it's effect on the situation.
Why don't you lock your bootloader for a few days, then try? or just sit back, watch ppl ignore the PSA, then start compaling about being stuck locked.