Related
My bootloader allowed lock says no but o2 on pay monthly say I can still unlock my bootloader. They took my imei number and are processing the lock and I have to wait for a email and this can take 7 working days to process. Has any one else done this? As I'm still in my 14 day peace of mind and might send back but they do say will be able to unlock my bootloader
Edit
Just had a email to unlock my phone to any network so just unlocked and it still says bootloader unlock allowed no
But they said I could, do I just try it?
Sent from my C6603 using xda premium
I hope you have done it like this?
http://forum.xda-developers.com/showthread.php?t=2153261
Took me seven seconds yesterday to get the unlock key on mail
danlivesey said:
My bootloader allowed lock says no but o2 on pay monthly say I can still unlock my bootloader.
Click to expand...
Click to collapse
No they don't, the code you have isn't for unlocking the bootloader, just the SIM.
Before even trying to unlock the BL, I'd suggest your TA partition just in case.
Mine also said no at first, but I was still able to unlock it.
Dsteppa said:
Before even trying to unlock the BL, I'd suggest your TA partition just in case.
Mine also said no at first, but I was still able to unlock it.
Click to expand...
Click to collapse
Who did you get the phone from? Mine is from Three UK and resolutely does not let me unlock the bootloader. Did you use the Sony method? Which rom etc?
nikc0069 said:
Who did you get the phone from? Mine is from Three UK and resolutely does not let me unlock the bootloader. Did you use the Sony method? Which rom etc?
Click to expand...
Click to collapse
Hmm stock Rom unbranded, bought it in the Netherlands. Most people here that bought the same phone aren't able to unlock their BL, maybe I just got lucky. The trick that worked for me was simply rooting the phone.
Dsteppa said:
Hmm stock Rom unbranded, bought it in the Netherlands. Most people here that bought the same phone aren't able to unlock their BL, maybe I just got lucky. The trick that worked for me was simply rooting the phone.
Click to expand...
Click to collapse
I think you did just get lucky or you just got a sim free handset by the luck of the draw. Which root method did you use? Someone else posted that they tried a specific combo of roms and two tries to unlock before it worked but never fed back any more info so it is possible there is an exploit somewhere.
nikc0069 said:
I think you did just get lucky or you just got a sim free handset by the luck of the draw. Which root method did you use? Someone else posted that they tried a specific combo of roms and two tries to unlock before it worked but never fed back any more info so it is possible there is an exploit somewhere.
Click to expand...
Click to collapse
Used the one I attached, can't really remember the topic.
Need to have USB debugging on.
Cheers. And the exact process? Step by step. I know it is tedious but it may be the tiniest thing (eg when you detached the usb cable or whether the sd card was in) that holds the secret.
Sent from my C6603 using xda premium
nikc0069 said:
Cheers. And the exact process? Step by step. I know it is tedious but it may be the tiniest thing (eg when you detached the usb cable or whether the sd card was in) that holds the secret.
Click to expand...
Click to collapse
Give up chasing it, if it was at all possible then it would have been figured out by now.
nikc0069 said:
Cheers. And the exact process? Step by step. I know it is tedious but it may be the tiniest thing (eg when you detached the usb cable or whether the sd card was in) that holds the secret.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
I really don't remember, since I've unlocked my BL I just flash a zip to get root back.
I firmly believe in Xda being able to make the impossible, possible. And there are no flawless systems. However I get what you mean, and don't think anyone is going to push on it now. Xperia Z is still a great phone and here is hoping the upcoming Google Edition will give us with locked bl more choice.
Sent from my C6603 using xda premium
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
Hey guys, so my mom was using the Turbo yesterday when she was prompted to an update. Now according to a few searches there was a soak test out or something? Not sure, since I have the Turbo 2. But regardless, she went to apply the update and now that phone won't boot up. It lights up with the M logo screen and then goes to andy where he's got the rotating box in his belly, and underneath it says "Erasing...". I can't get to any of the other options from the screen where you hold Volume Down while powering up. All of the options lead to the same erasing screen. The phone will reboot after two or three minutes and go back to the same thing. Been doing this for hours. I have it sitting on a charger and will take a look at it when I come back from work but I'm wondering how to remedy this? I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use. Not familiar with ADB so if that's the route I have to go, I'd appreciate a write up on how to use it. Willing to install custom firmware if I have to as well. I just need to get the phone working asap. My mom works nights and she is currently phoneless, so this is a safety concern of mine.
Also that screen where you hold Volume Down, it says battery okay and all that but it says the phone software is modified. Not sure why, I know that she completely incapable of doing that. And I didn't modify anything when I had the phone. Not that is matters though, it's out of warranty so Verizon or Moto probably won't be too useful.
Any and all help appreciated. Currently not in the position to buy a new phone so I'd prefer fixing this one up if I can. Thanks!
Xelios029 said:
I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use.
Click to expand...
Click to collapse
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Never, which is why I'm confused why it says software status modified. The sunshine and mofo mods were released after I upgraded to the turbo 2 so I never even had a chance. But thank you though! Really appreciate it, I was scared that some part of the memory had failed or something. My only question from here is how do I get the phone into the mode to required to RSD it? Because even if I select the bootloader option from that screen where you hold volume down while powering up, it goes to that erasing screen no matter what.
EDIT: Got home from work and downloaded all the files. RSD 6.1.5, Motorola Device Manager for the drivers, and the FXZ file. No dice. It won't recognize the device in RSD even though windows is making that sound when a device is connected. No luck on RSDLite 6.2.4 either.
EDIT2: Okay ugh, now I don't know what to do. Turns out RSD didnt detect it because the cable was not directly plugged into the motherboard. Took me a while to figure that out. So I got it detected and I flashed that file you put above and I'm still having the same problem. It reboots once everything is finished flashing and then goes back to the "Erasing..." screen.
EDIT3: SUCCESS!!! Thank you so much! I swear I was thinking I was going to have to replace the phone. Let it sit at the Erasing screen after flashing it for a bit and it eventually rebooted itself and started the Droid splash screen. What a huge relief! Hopefully these updates help with someone else who may run into the same problem.
Glad it worked for you!
And it helped you were persistent.
ChazzMatt said:
Glad it worked for you!
And it helped you were persistent.
Click to expand...
Click to collapse
Thanks again, much appreciated!
ChazzMatt said:
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Click to expand...
Click to collapse
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
KARIM9377 said:
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
You have to ask them. I don't know. But we've been surprised before by their talent.
ChazzMatt said:
you have to ask them. I don't know. But we've been stories surprised before by their talent.
Click to expand...
Click to collapse
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
KARIM9377 said:
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
Click to expand...
Click to collapse
Every time Sunshine released an update to force unlock the Droid Turbo bootloader, Verizon releases an OTA "security update" to block it.
This next rant is not towards you but to other longtime Droid Turbo owners... (Like anyone who has owned a Droid Turbo for over two months. Anywhere from 2 months - 2 years.)
People just need to UNLOCK their bootloaders before taking any updates. NEVER, NEVER, NEVER take an OTA update. If there's anything worthwhile it will be posted HERE on XDA and you can flash it manually. Just unlock your bootloader and you don't have to worry about Verizon "blocking" Sunshine because your bootloader will already be unlocked!
Heya,
I just recently got a hold of this tablet a few days ago and looked for a OEM unlock switch, which obviously wasn't there, both because it's a Verizon variant, and because it's a snapdragon variant. I've been researching for awhile and found combo files to unlock the OEM switch for this model, but everybody seems to get this model confused for some reason. I tried flashing one using odin and got a SW REV check failed [Boot]Fused 2 > Binary 1. I'm guessing I need to downgrade this tablet back down to android 8 since I updated it to android 9. Before I do that, I want to see if flashing the old firmware will be a waste of time or not and to see if there is a combo file or ENG boot file I can flash to get OEM or at least root unlocked. Something to get rid of all this Verizon bloatware and get rid of the Verizon boot animation with just a stock one. Hope I get a decently fast response.
Dclay2005 said:
Heya,
I just recently got a hold of this tablet a few days ago and looked for a OEM unlock switch, which obviously wasn't there, both because it's a Verizon variant, and because it's a snapdragon variant. I've been researching for awhile and found combo files to unlock the OEM switch for this model, but everybody seems to get this model confused for some reason. I tried flashing one using odin and got a SW REV check failed [Boot]Fused 2 > Binary 1. I'm guessing I need to downgrade this tablet back down to android 8 since I updated it to android 9. Before I do that, I want to see if flashing the old firmware will be a waste of time or not and to see if there is a combo file or ENG boot file I can flash to get OEM or at least root unlocked. Something to get rid of all this Verizon bloatware and get rid of the Verizon boot animation with just a stock one. Hope I get a decently fast response.
Click to expand...
Click to collapse
theres not really any support for that tablet.. u can flash combo but so ur aware its not possible to downgrade.. u need a newer combo firmware that is same rev as the firmware ur on..
there is no eng firmware from what i can tell.
I've found several sites that have the firmware I need, but they're all locked behind a paywall. They're only like, $3 but I don't feel like entering my card info on these sites. Might just bite the bullet and get me a throwaway card. My baseband version is T387VVRU2BTB2. REV0.4. maybe somebody can find one for free out there. If not, I'll probably just pay the $3 and stop being stingy with my money.
Dclay2005 said:
I've found several sites that have the firmware I need, but they're all locked behind a paywall. They're only like, $3 but I don't feel like entering my card info on these sites. Might just bite the bullet and get me a throwaway card. My baseband version is T387VVRU2BTB2. REV0.4. maybe somebody can find one for free out there. If not, I'll probably just pay the $3 and stop being stingy with my money.
Click to expand...
Click to collapse
I'm also looking for some firmware to possibly bypass FRP on my SM-T387V. Did you end up fbuying the firmware? Did it work?
I have a sm-t307u and while not the same device I'm unable to flash combo files due to a new token security measure. So, no OEM Unlock, no bootloader unlock, and no combo flashing in ODIN.
we now order to unlock bootloader??
Fastboot oem unlock?? Is correct??
fastboot flashing unlock
EtherealRemnant said:
fastboot flashing unlock
Click to expand...
Click to collapse
this command does not work
Read this thread:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
Is your phone detected in fastboot?
doc.K said:
Is your phone detected in fastboot?
Click to expand...
Click to collapse
Yes.. and oem unlock development manager
Α14 firmware
alxioa said:
this command does not work
Click to expand...
Click to collapse
Then update your platform tools.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Thanks ..work. new update
Does this work for T-Mobile USA version NE2217?
tr4sh80 said:
Does this work for T-Mobile USA version NE2217?
Click to expand...
Click to collapse
No, and OnePlus seems to have no interest in updating its unlock token page since the 9 Pro. I have asked several times and no one in cust. service has any idea what's going on months after release of the NE2217.
I only bought the 10 Pro because I expected to be able to unlock the bootloader, as I did easily with the 8. At this point, I'm looking to sell the 10 Pro.
I upgraded from an unlocked 7 pro. I only got the T-Mobile version because they gave me too good of a deal to pass up. Honestly I'm pretty happy with it stock. There's not much you really need root for anymore unless you're developing. It was a big plus back in the day but not so much anymore.
Does anyone live in USA?, need favor.
icherub said:
No, and OnePlus seems to have no interest in updating its unlock token page since the 9 Pro. I have asked several times and no one in cust. service has any idea what's going on months after release of the NE2217.
I only bought the 10 Pro because I expected to be able to unlock the bootloader, as I did easily with the 8. At this point, I'm looking to sell the 10 Pro.
Click to expand...
Click to collapse
it'll depend on when T-Mobile gives the ok. T-Mobile is subsidizing your phone so you need to play by their rules.
tr4sh80 said:
I upgraded from an unlocked 7 pro. I only got the T-Mobile version because they gave me too good of a deal to pass up. Honestly I'm pretty happy with it stock. There's not much you really need root for anymore unless you're developing. It was a big plus back in the day but not so much anymore.
Click to expand...
Click to collapse
Honestly if a service provider is going to tamper with the device, just don't bother with them.
I'm in the UK but the crap I've seen people have with T-Mobile and Verizon is just insane, avoid them like the plague.
I think you'd be better off converting a Chinese phone and that's something I'd avoid more than sleeping on the opposite side of the bed to amber heard.
Go global, unless theres a fool proof way to make it to global.
EE in the UK did this on the Sony z1, I ended up bricking my device, so I sent it back via a third party retailer.
Original - EE.
Retailer - carphone warehouse.
They sent me an unlocked version, with a normal bootloader.
Not sure if that's an option for you. A little convaluted but certainly worked for me.
alxioa said:
Thanks ..work. new update
Click to expand...
Click to collapse
does it worked ? with 9 pro all worked great. here its not working.
The token unlock page is finally updated to include the T-Mobile variant, NE2217!