OK guys so I just got my OG Droid in the mail the other day. I rooted it with SOC, installed my ROM Manager Premium,installed CWM Recovery, did a factory data reset,then installed the newest CyanogenMod 7.1. I have been searching the threads and doing homework and I know the Motorola Milestone bootloader is still locked but is the Droid bootloader still locked? I just wanted to ask the question since I could not find a specific thread about this(hence me starting a new one). Can the Droid bootloader be unlocked? I'm also looking to update my radio and PRL. I have the newest SDK, I have QPST, QXDM, and CDMA Workshop on my computer so I know how to change the PRL already but would like some more insight into this from somebody more experienced with the OG Droid than myself. Any help from anybody is GREATLY appreciated! I may have posted in a wrong place but I could not find a specific thread about the "Droid Bootlader" Thanks in advance!
Yes, the bootloader is unlocked. We wouldn't have proper CyanogenMod support if it wasn't. What do you specifically need to know about flashing?
Sent from my un-throttled, 1.1ghz OC'd, fully flashed cricKet Moto Droid running CM7.1 using XDA Premium App
You can flash a different ROM without the bootloader being unlocked just to let you know but if you have any info on how to unlock the bootloader for S-OFF I would greatly appreciate it!
This might be what you're looking for:
http://forum.xda-developers.com/showthread.php?t=1259403
T-Mode, AKA "Diagnostic Mode" for flashing the radio - hold T while powering on your Droid.
I don't claim to be an expert, or even knowledgeable - this just looked obvious to me.
gTan64 said:
This might be what you're looking for:
http://forum.xda-developers.com/showthread.php?t=1259403
T-Mode, AKA "Diagnostic Mode" for flashing the radio - hold T while powering on your Droid.
I don't claim to be an expert, or even knowledgeable - this just looked obvious to me.
Click to expand...
Click to collapse
I have read that thread and I do appreciate your help but I'm looking for how to unlock the bootloader for S-OFF. I had S-OFF on my older Sprint HTC Hero200. Once again,help from anybody is greatly appreciated!
gTan64 said:
This might be what you're looking for:
http://forum.xda-developers.com/showthread.php?t=1259403
T-Mode, AKA "Diagnostic Mode" for flashing the radio - hold T while powering on your Droid.
I don't claim to be an expert, or even knowledgeable - this just looked obvious to me.
Click to expand...
Click to collapse
Hey, I wrote that! Haha.
Sent from my un-throttled, 1.1ghz OC'd, fully flashed cricKet Moto Droid running CM7.1 using XDA Premium App
D1 does not have unlocked bootloader
So I've been searching literally all day on how to unlock a Droid1 bootloader and have come to find out that the Droid1 bootloader is locked just as well along with the rest of the Droids in the Droid Line. This is very unfortunate but hopefully Motorola will unlock their bootloader's pretty soon and the rest of the information will take place in this thread.
Here is what I do know:
To access bootloader on Droid1: Hold D-Pad Up while you press the power button.
My bootloader version is 2C.7C
Thanks for help from anybody who participated in this!
andy_lowe02 said:
So I've been searching literally all day on how to unlock a Droid1 bootloader and have come to find out that the Droid1 bootloader is locked just as well along with the rest of the Droids in the Droid Line. This is very unfortunate but hopefully Motorola will unlock their bootloader's pretty soon and the rest of the information will take place in this thread.
Here is what I do know:
To access bootloader on Droid1: Hold D-Pad Up while you press the power button.
My bootloader version is 2C.7C
Thanks for help from anybody who participated in this!
Click to expand...
Click to collapse
The bootloader for the D1 has never been locked.....doy.
Sent from my MB855 using xda premium
+1 when i read this i was like what the bootloader has never ben locked for the d1 i think it was the last phone that motorola made that had an unlocked one
bmx24 said:
+1 when i read this i was like what the bootloader has never ben locked for the d1 i think it was the last phone that motorola made that had an unlocked one
Click to expand...
Click to collapse
When the D1 came out it was meant to be a direct competitor to the iphone of the time. One of its biggest selling points was it's "hackability"...but I do believe it's one of the only, if not the only phone in the "Droid" lineup that has come with a unlocked bootloader stock...some others have been unlocked rather quickly and some not at all.
Sent from my MB855 using xda premium
Just randomly checking out this section and came across this thread. The Droid Charge also has an unlocked bootloader. Those are probably the only two phones in the Droid line to be unlocked. However, the LG Revolution also is unlocked.
As far as S-On/Off, I've only seen that on HTC phones. I'm no expert, so don't quote me on that.
no the first droid incredbile is unlocked too but the droid one was probably the last phone that motorola made that was unlocked
bmx24 said:
no the first droid incredbile is unlocked too but the droid one was probably the last phone that motorola made that was unlocked
Click to expand...
Click to collapse
Motorola would sell alot more phones if they had left their bootloader unlocked and an option to turn blur on/off , xoom bootloader was unlocked im pretty sure but xoom 2 will probably have a locked bootloader and honeyblur
i think motorola and google should be the only ones to make an android phone... if any other maker wants an android phone then they have to use asop and have stick update polices and that each device gets upgraded for atleast 2 or three years to the newest asop code base.
Google_Nexus said:
i think motorola and google should be the only ones to make an android phone... if any other maker wants an android phone then they have to use asop and have stick update polices and that each device gets upgraded for atleast 2 or three years to the newest asop code base.
Click to expand...
Click to collapse
That would be like having 5 Nexus phones a month.
I don't think all the manufacturers should ship with AOSP, but they should make it easy for people to put AOSP on it, as some people like Sense/Touchwiz etc, while some people don't.
And of course, they should definitely make AOSP updates available.
(Why would you want Motorola?! They've locked most of their bootloaders and haven't provided an option to unlock them.)
andy_lowe02 said:
So I've been searching literally all day on how to unlock a Droid1 bootloader and have come to find out that the Droid1 bootloader is locked just as well along with the rest of the Droids in the Droid Line. This is very unfortunate but hopefully Motorola will unlock their bootloader's pretty soon and the rest of the information will take place in this thread.
Here is what I do know:
To access bootloader on Droid1: Hold D-Pad Up while you press the power button.
My bootloader version is 2C.7C
Thanks for help from anybody who participated in this!
Click to expand...
Click to collapse
S-ON and S-OFF is only for HTC Devices
Related
I really HATE to have to post this and I will do so quite reluctantly....
I am certainly NOT a noob when it comes to Android, rooting, etc. But, the X is my first Moto android phone. I recently purchased mine via CTO with the AT&T Kitkat leak already installed. The person I bought it from claims there is NO WAY to gain root. He said he installed the leak via stock recovery.
The leak I'm running is 140.44.3.ghost_att.ATT.en.US.
Can anyone who's kind enough and well versed in Moto devices explain to me HOW I can how I can gain root on this leak and/or get Safestrap TWRP installed and if not, will I still be able to receive OTA updates being that the bootloader is locked and the stock recovery is intact? I just don't understand enough about Moto devices. I've searched and searched and can't really find the answers myself otherwise I wouldn't post here on XDA like the moron that I am.
I have a hard time accepting that I can't gain root despite not being able to unlock the bootloader. I realize that certain versions are only compatible with Safestrap (I hope I'm understanding that correctly) but, again I don't understand enough of how Moto's work. I've always had Samsung's or HTC's which are SUPER easy to use via ADB, etc.
Any help is greatly appreciated.
t3chn0s1s said:
I really HATE to have to post this and I will do so quite reluctantly....
I am certainly NOT a noob when it comes to Android, rooting, etc. But, the X is my first Moto android phone. I recently purchased mine via CTO with the AT&T Kitkat leak already installed. The person I bought it from claims there is NO WAY to gain root. He said he installed the leak via stock recovery.
The leak I'm running is 140.44.3.ghost_att.ATT.en.US.
Can anyone who's kind enough and well versed in Moto devices explain to me HOW I can how I can gain root on this leak and/or get Safestrap TWRP installed and if not, will I still be able to receive OTA updates being that the bootloader is locked and the stock recovery is intact? I just don't understand enough about Moto devices. I've searched and searched and can't really find the answers myself otherwise I wouldn't post here on XDA like the moron that I am.
I have a hard time accepting that I can't gain root despite not being able to unlock the bootloader. I realize that certain versions are only compatible with Safestrap (I hope I'm understanding that correctly) but, again I don't understand enough of how Moto's work. I've always had Samsung's or HTC's which are SUPER easy to use via ADB, etc.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Have you read this thread? It should give you a headstart if you haven't.
RagnaParadise said:
Have you read this thread? It should give you a headstart if you haven't.
Click to expand...
Click to collapse
Thanks Ragna... I haven't. I appreciate the help greatly. Moto's are so different from anything I'm used to and being that I am not starting out from a stock position makes it even more confusing.
Sent from my Nexus 5
t3chn0s1s said:
Thanks Ragna... I haven't. I appreciate the help greatly. Moto's are so different from anything I'm used to and being that I am not starting out from a stock position makes it even more confusing.
Sent from my Nexus 5
Click to expand...
Click to collapse
You might want to check out whether your phone is bootloader unlockable. I think you should be able to flash 4.4 on it completely soon, I would suggest holding out until then.
By the way, welcome to the Moto X camp.
Sent from my Moto X using Tapatalk
RagnaParadise said:
You might want to check out whether your phone is bootloader unlockable. I think you should be able to flash 4.4 on it completely soon, I would suggest holding out until then.
By the way, welcome to the Moto X camp.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
If he has an att moto x then it has a locked bootloader.
t3chn0s1s said:
Thanks Ragna... I haven't. I appreciate the help greatly. Moto's are so different from anything I'm used to and being that I am not starting out from a stock position makes it even more confusing.
Sent from my Nexus 5
Click to expand...
Click to collapse
To get back to stock all you need to do is download the 4.2.2 stock firmware images and then use rsdlite to install them... Assuming you have adb anyway configured, it only takes a few minutes.
From there you can do a fresh install of the 4.4 ota or take the steps to get 4.4 ota with root.
AT&T Moto X rocking rooted 4.4
theraffman said:
If he has an att moto x then it has a locked bootloader.
Click to expand...
Click to collapse
I wasn't certain because it was flashed over. I'm running on a Verizon ROM and frankly I wouldn't have known it was a Latin America version if I got it like that. So... Oh well. I suppose the probability that it is an AT&T version is much higher. In that case, OP's SOL for a bootloader unlock. Lol
Sent from my Moto X using Tapatalk
theraffman said:
If he has an att moto x then it has a locked bootloader.
To get back to stock all you need to do is download the 4.2.2 stock firmware images and then use rsdlite to install them... Assuming you have adb anyway configured, it only takes a few minutes.
From there you can do a fresh install of the 4.4 ota or take the steps to get 4.4 ota with root.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
I'm just reading your post now but, this is exactly what I did... I just used RDS Lite to return to stock 4.2.2 and then OTA'd to 4.4 and now I'm gonna use jcase's exploit to gain root. THANKS SO MUCH FOR THE INFO GUYS!
theraffman said:
If he has an att moto x then it has a locked bootloader.
To get back to stock all you need to do is download the 4.2.2 stock firmware images and then use rsdlite to install them... Assuming you have adb anyway configured, it only takes a few minutes.
From there you can do a fresh install of the 4.4 ota or take the steps to get 4.4 ota with root.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
RagnaParadise said:
You might want to check out whether your phone is bootloader unlockable. I think you should be able to flash 4.4 on it completely soon, I would suggest holding out until then.
By the way, welcome to the Moto X camp.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Thanks Ragna. I appreciate the info and being the "welcome wagon", LOL. Yeah - I'm obviously on the AT&T version (not a Dev Edition) so my BL is unlockable which - is complete bulls**t. I don't get why Moto has to pull this crap or why AT&T gives a rats ass what we do with our phones.
I was able to root my Verizon on 4.4 Just take your time and read thoroughly.
It's sort of a rough set of instructions not for the faint of heart.
SYNSYNACKACK said:
I was able to root my Verizon on 4.4 Just take your time and read thoroughly.
It's sort of a rough set of instructions not for the faint of heart.
Click to expand...
Click to collapse
Yea... So I've read. Telnet is SO old school... Was kinda surprised to see that as part of the process. I haven't yet taken the plunge but will probably eventually go for it. Just a little confused since I'm already on stock 4.4 so I'm not sure if I should start at step 1 or what. Oh well... I'll figure it out. Thanks for the suggestions.
Sent from my Nexus 5
besides the chinese connection which may or may not be working , I dont need the spam nor do I need links having access to PP accounts . I guess my Moto X will continue to be a paperweight , My Note OG will continue to be my DD , since it has never failed me . Too bad Android is going the way of the proprietory scams (apple,windows ) and I dont blame the Devs like some people in here , , ya gotta figure if Microsoft, Google, Apple or HP ,Oracle see's what these guys are doing and says "I want that kid " , "yore hred kid , but you cant release anymore code to the public, trust me you'll be compensated well" , why wouldnt they take that offer ?
Just wish there was something else we could do ?
Get the Dev Edition
Sent from my XT1060 using Tapatalk
It's AT&T that refuses to allow Motorola to unlock their model ...
I've seen nothing but happy customers from the Chinese code seller...the phones he could unlock anyway.
So a bit of spam, or an unlocked bootloader..... Seems most go for the unlock.
As said, dev edition is your only other choice. Sell the one you have and you'll be most of the way to the DE cost.
I don't know of anyone on here who has gotten any spam using the PayPal method with the Chinese guy. If you don't have an unlockable version or a dev version, it will likely be the only possibility ever. Motorola have locked these things down tight.
Vintage144 said:
I guess my Moto X will continue to be a paperweight
<snip>
Just wish there was something else we could do ?
Click to expand...
Click to collapse
Well, you could start by buying phones that actually suit your needs. Some versions of the X were bootloader-locked. This was known from the outset. So whose fault is it that you own a "paperweight"? It's not the developers, or Google, or Microsoft, or anyone else.
You could have bought a dev edition. You could have bought from a carrier who allowed unlocking. You could have skipped the X altogether... so, why?
I'd like it if Big Red offered more unlockable phones, but I go into any phone purchase with eyes wide open. I decided the Moto X suited my needs even bootloader-locked. So you won't hear any complaints from me: it's my own fault if I don't like it. I don't hear a lot of Ford F350 owners complaining about their gas mileage, and there aren't a lot of Prius drivers that think their car is a paperweight because it can't haul a boat.
Vintage144 said:
I dont need the spam nor do I need links having access to PP accounts
Click to expand...
Click to collapse
I used the Chinese PayPal method and haven't received any spam what so ever, only a single email with my code. Would highly recommend that option to anyone.
wasnt referring to spam from the chinese guy and that would be the option Id take , as for the paperweight , should have stayed with stuff I know like Samsung and HTC anyway , theyve never let me down , there isnt some are some arent!
No disrespect intended.....but you didn't like the X three months ago even, why haven't you just sold it????
Just curious.
I used the chinese MM method. Sent the payment via paypal as instructed and received the code less than 24 hrs later.
Unlocked BL, rooted phone, and installed GravityBox today. Noticed literally no extra lag so far and the increase in functionality, customization, and my satisfaction of the phone has increased exponentially.
If you're worried about spam, can't you just make a temporary email account?
jamesino said:
I used the chinese MM method. Sent the payment via paypal as instructed and received the code less than 24 hrs later.
Unlocked BL, rooted phone, and installed GravityBox today. Noticed literally no extra lag so far and the increase in functionality, customization, and my satisfaction of the phone has increased exponentially.
If you're worried about spam, can't you just make a temporary email account?
Click to expand...
Click to collapse
Where can I find that Chinese mm method?
androiddoglover6969 said:
Where can I find that Chinese mm method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177
Only generally works with phone made in 2014 though. Check the lower right corner of the sticker on your box for the manufacture date.
jamesino said:
http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177
Only generally works with phone made in 2014 though. Check the lower right corner of the sticker on your box for the manufacture date.
Click to expand...
Click to collapse
Semi off topic:
If I rooted my phone to 4.4.2. and I have a bootloader locked, doing a factory reset will entitle me to keep my root? Or will I lose it?
And what if I do a factory reset on my rooted moto x on 4.4.2 when my bootloader is unlocked. Will I be able to keep my root when doing factory reset? I am trying to get rid of this "com.motorola.process.system" because I've tried wiping cache and dalvik and safemode and date and time method doesn't work.
androiddoglover6969 said:
Semi off topic:
If I rooted my phone to 4.4.2. and I have a bootloader locked, doing a factory reset will entitle me to keep my root? Or will I lose it?
And what if I do a factory reset on my rooted moto x on 4.4.2 when my bootloader is unlocked. Will I be able to keep my root when doing factory reset? I am trying to get rid of this "com.motorola.process.system" because I've tried wiping cache and dalvik and safemode and date and time method doesn't work.
Click to expand...
Click to collapse
See my reply to this same question you asked in another thread. You're out-of-luck.
Please follow my instructions in the other thread. You'll have to re-flash the stock 4.4.2 rom, and you will NOT be getting root back without BL unlock.
Sorry...its posted all over this forum that you cannot take the 4.4.2 OTA - it patches the BL exploits we used.
samwathegreat said:
See my reply to this same question you asked in another thread. You're out-of-luck.
Please follow my instructions in the other thread. You'll have to re-flash the stock 4.4.2 rom, and you will NOT be getting root back without BL unlock.
Sorry...its posted all over this forum that you cannot take the 4.4.2 OTA - it patches the BL exploits we used.
Click to expand...
Click to collapse
I didn't take the 4.4.2 OTA...
---------- Post added at 10:45 AM ---------- Previous post was at 09:55 AM ----------
samwathegreat said:
See my reply to this same question you asked in another thread. You're out-of-luck.
Please follow my instructions in the other thread. You'll have to re-flash the stock 4.4.2 rom, and you will NOT be getting root back without BL unlock.
Sorry...its posted all over this forum that you cannot take the 4.4.2 OTA - it patches the BL exploits we used.
Click to expand...
Click to collapse
Alright. Just bought the unlock bootloader service.
If you want a bootloader unlock for AT&T Moto X, you could just get the Rogers Moto X.
They are both XT1058 and the Rogers one is bootloader unlockable on the Motorola website. I unlocked 3 there myself.
scorpion667 said:
If you want a bootloader unlock for AT&T Moto X, you could just get the Rogers Moto X.
They are both XT1058 and the Rogers one is bootloader unlockable on the Motorola website. I unlocked 3 there myself.
Click to expand...
Click to collapse
Good call, but hopefully that'll be useful for those with that 1058 model. I am on XT1049.
scorpion667 said:
If you want a bootloader unlock for AT&T Moto X, you could just get the Rogers Moto X.
They are both XT1058 and the Rogers one is bootloader unlockable on the Motorola website. I unlocked 3 there myself.
Click to expand...
Click to collapse
That's what I have. Unlocked on moto site.
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
jiv101 said:
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
Click to expand...
Click to collapse
There are two separete issues. One is what you're describing, and one is the device just completely dying - "you can't even get to fastboot". The first one has thread here, as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no cause :/
JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Tasssadar said:
as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no no cause :/
Click to expand...
Click to collapse
Are they sure of what bootloader versions they had?
I know this is a Nexus device but it has a Motorola bootloader. It is safest not to downgrade the bootloader OR the partition table from my experience with the Moto X. I know there were some exceptions and that is how jcase was able to get root on at least one bootloader version, but the general rule was don't try to downgrade the bootloader or the partition table to stay out of trouble.
I was thinking of making a post on General with this advice in it for people to help them stay out of trouble:
1) know your bootloader and partition table versions before you flash anything and if you aren't sure what will happen, do not attempt to downgrade either the bootloader or the partition table; and
2) make sure OEM unlock and USB debugging are enabled before you flash anything.
I understand that the advice above may be overkill for those who know what they are doing, but clearly people who don't know what they are doing are bricking their devices. I feel bad for them and don't want to see more people in that situation.
I was bricked by CM. Last nexus I had with cm was galaxy nexus so I don't know how cm is done on nexus 5 but why do they reflash bootloader and radios on each update. It wasn't that way before. Thats what bricked my device. I just got confirmation that I'm getting my replacement device.
akellar said:
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Still a Motorola bootloader
rootSU said:
Still a Motorola bootloader
Click to expand...
Click to collapse
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Fair enough
So I think I'm finally going to need to get a new phone soon. But I can't afford anything high end ATM. So I'm thinking about gting a 64gb tubro that can be unlocked, but I'm wondering if there is any reason I should settle for 32gb and gt a moto maxx instead. I think I read U can't unlock relock and unlock again with the xt1254 but I dnt see needing to do that anyway. Anything else I should know about hacked turbo vs officially unlocked maxx?
1) Be best if you keep using model numbers like in your title, instead of names like "Turbo", "Moto Maxx". There's two Turbos (Droid Turbo XT1254, Moto Turbo XT1225), there's two Moto Maxx even (XT1250, XT1225). Using model numbers keeps it straight.
2) If you get an XT1254 64GB, you are looking at Amazon, eBay, Swappa? Be aware some people have sneakily locked their bootloaders back before selling. I don't know why. If I were buying, I would pay more money for an unlocked bootloader -- the hard work and cost has already been done. You will need to see proof of bootloader status. If the bootloader has been locked back, it's worthless for you.
Also, you would need to see proof the phone has not already been upgraded to the OTA update pushed out by Verizon in May -- SU4TL-49, unless the seller can show you the bootloader is indeed unlocked. A lot of people who took the OTA before unlocking their bootloaders are now selling them due to their screwup.
Sunshine bootloader unlock exploit ($25) only works with SU4TL-44 (Lollipop 5.1) . If the phone has not been upgraded to Lollipop 5.1 and is still on 4.4.4 Kitkat, you can update it to SU4TL-44 using a file in this forum. But you would have to be careful not to take OTA updating it to SU4TL-49.
3) An XT1250 (U.S. Moto Maxx) doesn't have any conditions like that, but comes in 32GB only.
K I gotcha. either way I want something new and I have no problem doing the work myself. I found one on the bay and it's on su4tl44, I'll have to have him show me the boot loader. What is it if it's relocked status code 3?
TheWhiteChallenger said:
K I gotcha. either way I want something new and I have no problem doing the work myself. I found one on the bay and it's on su4tl44, I'll have to have him show me the boot loader. What is it if it's relocked status code 3?
Click to expand...
Click to collapse
XT1254 Droid Turbo owners would know much better than me on this.
One of the forums says this:
http://forum.xda-developers.com/nex...sh-factory-images-nexus-6shamu-t2954008/page4
0 is locked
2 is relocked
3 is unlocked
Click to expand...
Click to collapse
I've never re-locked bootloader, so I don't know. Once unlocked I keep it that way...
Same here, that's y I hoping U guy would help. So it soundz like if I gt the right build number and it's not relocked, and I don't ever relock it, I should be golden. I can gt a 64gb xt1254 cheaper then the xt1250 with only 32gb I just don't want to mess myself over.
TheWhiteChallenger said:
Same here, that's y I hoping U guy would help. So it soundz like if I gt the right build number and it's not relocked, and I don't ever relock it, I should be golden. I can gt a 64gb xt1254 cheaper then the xt1250 with only 32gb I just don't want to mess myself over.
Click to expand...
Click to collapse
Sounds like you are doing it right.
TheWhiteChallenger said:
K I gotcha. either way I want something new and I have no problem doing the work myself. I found one on the bay and it's on su4tl44, I'll have to have him show me the boot loader. What is it if it's relocked status code 3?
Click to expand...
Click to collapse
If its been relocked you can still reunlock it as well its just a little bit trickier and there is a chance of bricking your device if not done properly bur as long as you have a computer with fastboot adb installed you should be good. I have never reunlocked myself but have read and helped others in reunlocking there own its in the forum here somewhere. So no matter what as long as you can get that turbo on su4tl44 you should be set.
Grynch13 said:
If its been relocked you can still reunlock it as well its just a little bit trickier and there is a chance of bricking your device if not done properly bur as long as you have a computer with fastboot adb installed you should be good. I have never reunlocked myself but have read and helped others in reunlocking there own its in the forum here somewhere. So no matter what as long as you can get that turbo on su4tl44 you should be set.
Click to expand...
Click to collapse
Then that's new information I haven't kept up with. Earlier some people re-locked for unknown reasons and they were told they were out of luck. It was a one-time only process.
Here's the thread you are talking about:
http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081
Seems iffy. Better to not have a re-locked bootloader in the first place.
Thus far everyone that has followed beaups unlock instructions it's worked for. I think the issue is it's not something as simple as adb boot loader unlock
Sent from my DROID Turbo using XDA-Developers mobile app
So I bought the phone just now. Paid quite a lot because they don't exist in my country , but I've wanted it since it got out, and it's in like brand new condition so ehhh, why not I said..
Just checked and phone is on Marshmallow 24.81.5quark_verzion.verzion.enUS
Tried Kingroot and sunshine to at least achieve temproot , they both failed.
What are my options right now here?
Thanks!
No unlock options right now if you are on stock 6.0.1 with a locked bootloader.
ChazzMatt said:
No unlock options right now if you are on stock 6.0.1 with a locked bootloader.
Click to expand...
Click to collapse
Thanks for reply! I guess I'll just live with it. Iphone in motorola's body lol. But for discussions sake, any way to downgrade? I know flashing bootloader triggers the "fuse" but I was succesfull with some weird bootloader downgrades in the past wtih 201M (Japanese softbank version of Razr M) and IS12M (JP KDDI version of Droid Razr).
Only problem is, this phone is way to expensive for me to experiment..
Ej?iSixo said:
Thanks for reply! I guess I'll just live with it. Iphone in motorola's body lol. But for discussions sake, any way to downgrade? I know flashing bootloader triggers the "fuse" but I was successful with some weird bootloader downgrades in the past wtih 201M (Japanese softbank version of Razr M) and IS12M (JP KDDI version of Droid Razr).
Only problem is, this phone is way to expensive for me to experiment..
Click to expand...
Click to collapse
Hmmmm... then you were very lucky because gospel around here is you can never downgrade the Motorola bootloader. If you could downgrade bootloader, then everyone would go back to version where Sunshine worked! First Sunshine worked on Lollipop SU4TL-44 (November 2015), then everyone who procrastinated rushed to take SU4TL-49 (May 2016), hoping it was Marshmallow. Nope, it was just a Verizon "security" update to stop Sunshine from working. They had SIX MONTHS to unlock their bootloader and they didn't do it! Then everyone complained and said if only Sunshine worked on "49", they wouldn't procrastinate anymore. BOOM. A few months later (july 2016) Sunshine found another exploit and it works also on Lollipop "49".
But we are STILL seeing people now taking the Marshmallow OTA (November 2016) without unlocking bootloader first. Not you, you said you bought it with it already installed...
One of the Sunshine team members said he briefly glanced at the 6.0.1 OTA and it might not be impossible to unlock the bootloader. But no promises and no ETA. I don't think this phone is a high priority anymore. This is now a 2-year old phone. Still GREAT, but other newer phones get attention. There's been Sunshine for it since November 2015 and most everyone who wants it has had a chance to get it.
ChazzMatt said:
Hmmmm... then you were very lucky because gospel around here is you can never downgrade the Motorola bootloader. If you could downgrade bootloader, then everyone would go back to version where Sunshine worked! First Sunshine worked on Lollipop SU4TL-44 (November 2015), then everyone who procrastinated rushed to take SU4TL-49 (May 2016), hoping it was Marshmallow. Nope, it was just a Verizon "security" update to stop Sunshine from working. They had SIX MONTHS to unlock their bootloader and they didn't do it! Then everyone complained and said if only Sunshine worked on "49", they wouldn't procrastinate anymore. BOOM. A few months later (july 2016) Sunshine found another exploit and it works also on Lollipop "49".
But we are STILL seeing people now taking the Marshmallow OTA (November 2016) without unlocking bootloader first. Not you, you said you bought it with it already installed...
One of the Sunshine team members said he briefly glanced at the 6.0.1 OTA and it might not be impossible to unlock the bootloader. But no promises and no ETA. I don't think this phone is a high priority anymore. This is now a 2-year old phone. Still GREAT, but other newer phones get attention. There's been Sunshine for it since November 2015 and most everyone who wants it has had a chance to get it.
Click to expand...
Click to collapse
Yeah I read whole how to unlock bootloader thread, from 1st to last page but havent' seen anything marshmallow specific so I opened this topic..
Yeah , I was also surprised, but I spent around 1 month working on it , and it was only working with specific firmwares (fastboot files).
Yeah I wish I checked little more about that issue , I would check phones OS and probably not buy when I see it's MM.. Oh well, no going back now.. Thought that verzion's control freak behavior stopped by the time of droid turbo( used some verzion motorola phones in the past) especially when google bought motorola.
I hope people don't see this phone as outdated, because there is no way it can be called that. Many people including myself figured it like a replacement for nexus , and I think it deserves at least root exploit..
Also asked in Sunshines thread about support for marshmallow , got rather unclear response:
Me:Will there be support for droid turbo on marshmallow? Just purchased the phone, didn't know unlocking bl was possible only on lolli... Thanks
jcase: Known at this point,
EDIT: damn I write yeah a lot lol. P.s if mods want to delete topic because it's useless, feel free. Thanks!
EDIT 2: By checking system updates looks like phone was updates 3 days ago so 1 day before I bought it .. Arrrghhhh!!!
BTW I just remembered, "old" Droid 's ( xt910 ,xt912 etc) bootloader was never ever unlocked , but there was a way around it. Safestrap recovery by Hashcode , which I'm sure you all know about. The project is scraped because dev is busy , but I really wonder if anything like that is possible on droid turbo. I also wonder how does it work exactly and what gets bypassed.
From users standpoint: you installed apk which then installed recovery that "bypassed" locked bootloader and allowed you to install /load custom roms, kernels , radios , root etc.. You could even install more OS's at same time like on another "partitions".
hm...
EjđiSixo said:
BTW I just remembered, "old" Droid 's ( xt910 ,xt912 etc) bootloader was never ever unlocked , but there was a way around it. Safestrap recovery by Hashcode , which I'm sure you all know about. The project is scraped because dev is busy , but I really wonder if anything like that is possible on droid turbo. I also wonder how does it work exactly and what gets bypassed.
From users standpoint: you installed apk which then installed recovery that "bypassed" locked bootloader and allowed you to install /load custom roms, kernels , radios , root etc.. You could even install more OS's at same time like on another "partitions".
hm...
Click to expand...
Click to collapse
sorry for keeping this post alive, but i really really miss Safestrap when i had the Moto Droid Razr, you could have up to 4 different ROMs installed and it took minutes to swap between them. Man those were the good ole days haha
Edit: added word droid
weaver11b said:
sorry for keeping this post alive, but i really really miss Safestrap when i had the Moto Razr, you could have up to 4 different ROMs installed and it took minutes to swap between them. Man those were the good ole days haha
Click to expand...
Click to collapse
I remember being frustrated about never-unlockable bootloader while using safestrap at same tame and then realised, hey wait! What do I need unlocked bootloader anyway , everything works perfect and functionality is even better than on most modded phones (at the time).
Having something like this on droid turbo would make it a perfect phone in my opinion, and for years to come.. Wonder whats the dev's view on droid turbo on that..
Anyway I was playing a little, all within "safe zones" regarding the downgrading . With litlle modding I could flash bootloader.img from QUARK_VERIZON_5.1_SU4TL-49_cid2_subsidy-DEFAULT_CFC.xml.zip and most of partitions related to bootloader I collected from various locations,all from SU4TL but it's obviously not important..
So basically what I can't flash to downgrade is :
gpt.bin
boot.img
system files (system,img_sparsechunk.0 , 1 , 2 etc).. I will investigate more.
Started finally actually using phone , all bloatware can be disabled, so it's actually pretty ok for now. Phone feels awesome ..
Mods , please delete this topic in purpose of cleaning, I'm gonna open 2 topics regarding downgrading experiment and making SBF of new Marshmallow OTA