Related
Of course S7 on Tmobile gets unlocked the day it updates to 7.0 but I want to drop a cleaner rom on it, I hate the T-Mobile/Samsung crap that just eats space and battery.
I have enabled developer mode, turned on USB Debugging and enabled the OEM Unlock.
I have tried Odin 3.12.3 and 3.10.6 ( which comes with Chain fire ).
Before and after trying a factory reset, I am completely unable to replace the recovery with TWRP or chainfire or even just drop a new rom on it. When I try to use Odin, I get an error message " Complete(Write) operation failed" or " Complete(AUTH) operation failed". I've tried running Odin as Admin, I've rebooted my computer and the phone multiple times and tried 4 different USB cables ( thick and thin ) which all pass data at a good speed.
Any thoughts? This is getting annoying.
Nomadadon said:
Of course S7 on Tmobile gets unlocked the day it updates to 7.0 but I want to drop a cleaner rom on it, I hate the T-Mobile/Samsung crap that just eats space and battery.
I have enabled developer mode, turned on USB Debugging and enabled the OEM Unlock.
I have tried Odin 3.12.3 and 3.10.6 ( which comes with Chain fire ).
Before and after trying a factory reset, I am completely unable to replace the recovery with TWRP or chainfire or even just drop a new rom on it. When I try to use Odin, I get an error message " Complete(Write) operation failed" or " Complete(AUTH) operation failed". I've tried running Odin as Admin, I've rebooted my computer and the phone multiple times and tried 4 different USB cables ( thick and thin ) which all pass data at a good speed.
Any thoughts? This is getting annoying.
Click to expand...
Click to collapse
Hi mate
yes a few..
First you are in the wrong forum check here
https://forum.xda-developers.com/tmobile-galaxy-s7
Second you can root a snapdragon S7 BUT even so your bootloader is still locked , therefore you cant flash TWRP or any custom rom....
Sorry mate
Hi, I´m not in the business of unlocking phones, just looking how to SIM unlock my personal phone. Would you please explain what does it mean the bootloader is locked? With that issue in mind, that prevents me to SIM Unlock the phone?
MAX 404 said:
Hi mate
yes a few..
First you are in the wrong forum check here
https://forum.xda-developers.com/tmobile-galaxy-s7
Second you can root a snapdragon S7 BUT even so your bootloader is still locked , therefore you cant flash TWRP or any custom rom....
Sorry mate
Click to expand...
Click to collapse
fbolzoni said:
Hi, I´m not in the business of unlocking phones, just looking how to SIM unlock my personal phone. Would you please explain what does it mean the bootloader is locked? With that issue in mind, that prevents me to SIM Unlock the phone?
Click to expand...
Click to collapse
Carrier lock is what would prevent you from using your SIM in the phone if it's not the right carrier. You'll either need to call the carrier of the phone (Verizon, AT&T etc) to unlock it or use an online unlocker like http://updato.com/unlock but I don't know how reliable these are.
Bootloader lock is what OP is experiencing, which prevents you modifying the boot image, so you can't put TWRP or custom ROM's on a bootloader that's locked.
This means that at the time there is no way to unlock bootloader and flash any custom roms, in order to unlock SIM on G9030T?
Beanvee7 said:
Carrier lock is what would prevent you from using your SIM in the phone if it's not the right carrier. You'll either need to call the carrier of the phone (Verizon, AT&T etc) to unlock it or use an online unlocker like ----- but I don't know how reliable these are.
Bootloader lock is what OP is experiencing, which prevents you modifying the boot image, so you can't put TWRP or custom ROM's on a bootloader that's locked.
Click to expand...
Click to collapse
fbolzoni said:
This means that at the time there is no way to unlock bootloader and flash any custom roms, in order to unlock SIM on G9030T?
Click to expand...
Click to collapse
Correct, at this stage there is know no way to unlock the bootloader and flash any custom roms.
You'll need to follow normal carrier unlock procedure
Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.
The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse
i get a message saying "cant update from sd card?"
yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard
Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.
JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse
Hey guys! I haven't seen any other guides about this so here you go. How to use Engineering mode in the G965U and G965U1. Engineering mode doesn't let you do much, but if you're interested in testing some root methods it is definitely worth your interest. The two things that are most interesting to me is that SELinux is in Permissive and the OEM unlocking option appears, but it seems enabling OEM unlock does nothing. Still, all the files for the regular S9+ software is there, it just seems to boot a different mode. If someone can figure out how to make the normal UI and settings show up and inject root this could be our method. DON'T DO THIS IF YOU DON'T MIND RISKING MESSING UP YOUR DEVICE. USE A GOOD USB CABLE AND ONLY FLASH THE RIGHT FILES FOR YOUR MODEL. YOU HAVE BEEN WARNED.
Screenshots:
https://i.imgur.com/Uynre9O.jpg
https://i.imgur.com/h1MGsNJ.jpg
https://i.imgur.com/zYyno9m.jpg
So first. Go ahead and download the ENG boot and CSC for your device HERE and HERE. These files are courtesy of @wolfgart . Please give him thanks on his post, all credit goes to him for his work.
Second, extract both zips and you will have two .tar.md5 files. You need the latest odin to install this. I was unable to restore to stock with regular odin but patched odin let me return to stock. Download it HERE.
Go ahead and download the latest stock firmware as well. There a plenty online but I suggest using one from HERE as it worked for me.
Extract the firmware zip and reboot your phone into download mode by holding Bixby + Vol Down + Power. Plug in and open up odin and select the CP, BL, and USERDATA from the stock firmware and use the ENG boot file for AP and Combination file you downloaded earlier for CSC. Hold on to that stock firmware because you'll want to be able to return easily. Go ahead and start the flash process in ODIN. This will take a few minutes. If you have an MD5 error simply remove the .MD5 from the end of the filename for AP and/or CSC.
That's it! If all goes well you will have ENG boot. It isn't much right now but I'm sure with all your brilliant minds it could be the pathway to something much bigger.
"Allow the bootloader to be unlocked"? It can't be that easy on Snapdragon, can it??
EDIT: My bad, missed the part where you said it doesn't seem to do anything. I'd just delete this if XDA allowed me to.
LinneaDenVarg said:
"Allow the bootloader to be unlocked"? It can't be that easy on Snapdragon, can it??
EDIT: My bad, missed the part where you said it doesn't seem to do anything. I'd just delete this if XDA allowed me to.
Click to expand...
Click to collapse
LOL no problem! I'm sure most of the devs probably already have this set up I just threw this guide together since there isn't one yet. It gives us some extra opportunities to tinker around and as far as I know it's pretty safe to use it doesn't even trip knox.
That's it! If all goes well you will have ENG boot
hjfgdsg said:
That's it! If all goes well you will have ENG boot
Click to expand...
Click to collapse
Yup..... Now root.. and the wait continues. This isn't anything experienced people didn't already have. This is a nightmare waiting to happen for a n00b. Don't mess with this unless you know what you're doing.
hey need some help with ENG BOOT for N976U
found a site that claims to have it just wanted so help in pm
thatruth132 said:
hey need some help with ENG BOOT for N976U
found a site that claims to have it just wanted so help in pm
Click to expand...
Click to collapse
Should probably ask in the note 10 threads this is for s9 and +
I would like to know if it is working on Android 10 I have a sm-g965u Verizon been attached and if it is necessary to unlock the bootloader?
osvaldo3091 said:
I would like to know if it is working on Android 10 I have a sm-g965u Verizon been attached and if it is necessary to unlock the bootloader?
Click to expand...
Click to collapse
No it is not And you cannot unlock this devices bootloader All the U W And U1 are permantly locked with no hope of unlock
TheMadScientist said:
No it is not And you cannot unlock this devices bootloader All the U W And U1 are permantly locked with no hope of unlock
Click to expand...
Click to collapse
I understand, what I would like to know is something I have this device is a sm-g965u with csc xaa is from Verizon I am in RD the security patches take a long time to arrive and the updates too.Do you think if i change the firmware to sm-g965u1 i would receive updates Faster? Thanks greetings
osvaldo3091 said:
I understand, what I would like to know is something I have this device is a sm-g965u with csc xaa is from Verizon I am in RD the security patches take a long time to arrive and the updates too.Do you think if i change the firmware to sm-g965u1 i would receive updates Faster? Thanks greetings
Click to expand...
Click to collapse
Not necessarily It just depends who gets their updates out the fastest Sometimes U1 is faster others carrier is faster then U1 unlocked
TheMadScientist said:
Not necessarily It just depends who gets their updates out the fastest Sometimes U1 is faster others carrier is faster then U1 unlocked
Click to expand...
Click to collapse
Ok I understand thanks for the explanation I think I would not benefit from changing firmware. I explain something to you: I have this mobile and when they gave it to me the active csc was the vzw and I looked for a tutorial and managed to change it to xaa which is the one used in my country for unlocked device, the device doesn't have a Verizon app not anything like that but when I was in vzw it had already been updated to the April security patch but as I changed the csc I only received the March one and to be able to update the patch I had to install a firmware with the updated patch greeting again
Hello, I have a Galaxy S7 G930P with what I believe is the v7 bootloader on Oreo.
I've only rooted a couple times before so I'm not super experienced but this phone is worth nothing to me so I will (and have been I think) risk bricking the phone. From what I understand this is a locked bootloader, so I cannot root it at all, or at least that's what I'm seeing. When I try flashing it with many different APs including engineering ones with multiple failures in Odin.
Depending on which files I'm attempting to flash, I either get and AUTH or a RQT CLOSE error in Odin.
The error on the phone says SW REV CHECK FAIL.
It's a little late in my timezone so my writing is probably horrendous, if you need anymore information I'll be back on in the morning to supply anything else. Thanks!
also please don't roast me, I'm new to this...
BertMcfallen said:
Hello, I have a Galaxy S7 G930A with what I believe is the v7 bootloader on Oreo.
The bootloader says "PRODUCT NAME: SM-G930P", although the marking on the back of the phone says SM-G930A.
I've only rooted a couple times before so I'm not super experienced but this phone is worth nothing to me so I will (and have been I think) risk bricking the phone. From what I understand this is a locked bootloader, so I cannot root it at all, or at least that's what I'm seeing. When I try flashing it with many different APs including engineering ones with multiple failures in Odin.
Depending on which files I'm attempting to flash, I either get and AUTH or a RQT CLOSE error in Odin.
The error on the phone says SW REV CHECK FAIL.
It's a little late in my timezone so my writing is probably horrendous, if you need anymore information I'll be back on in the morning to supply anything else. Thanks!
also please don't roast me, I'm new to this...
Click to expand...
Click to collapse
The solution to your issue would be patching your boot img in magisk in tar format and then flashing that img via odin
([emoji3590]09-09-18[emoji3590])
PoochyX said:
The solution to your issue would be patching your boot img in magisk in tar format and then flashing that img via odin
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Ah yes I've heard of magisk, I will start researching that right now. Thank you very much!
BertMcfallen said:
Ah yes I've heard of magisk, I will start researching that right now. Thank you very much!
Click to expand...
Click to collapse
Anytime
([emoji3590]09-09-18[emoji3590])
From what I've read, you can't get root on sprint and/or bootloader v7
https://forum.xda-developers.com/showpost.php?p=77655646&postcount=882
https://forum.xda-developers.com/showpost.php?p=77663944&postcount=901
https://forum.xda-developers.com/showpost.php?p=77665353&postcount=902
The only root methods for the snapdragon/USA models is by using engineering bootloaders, but you have to be on the right bootloader to flash over to the engineering bootloader, which there doesn't seem to be a v7 engineering bootloader out there
Beanvee7 said:
From what I've read, you can't get root on sprint and/or bootloader v7
https://forum.xda-developers.com/showpost.php?p=77655646&postcount=882
https://forum.xda-developers.com/showpost.php?p=77663944&postcount=901
https://forum.xda-developers.com/showpost.php?p=77665353&postcount=902
The only root methods for the snapdragon/USA models is by using engineering bootloaders, but you have to be on the right bootloader to flash over to the engineering bootloader, which there doesn't seem to be a v7 engineering bootloader out there
Click to expand...
Click to collapse
Yeah, unfortunately I am also seeing the same things elsewhere. Thanks for the help.
BertMcfallen said:
Yeah, unfortunately I am also seeing the same things elsewhere. Thanks for the help.
Click to expand...
Click to collapse
Someone with root can patch your img with magisk and you can flash it in odin and it wont work however due to the fact you have a locked bootloader i believe once you flash it in Odin you will get unauthorized binary alert and your phone won't boot
([emoji3590]09-09-18[emoji3590])
Attached are pictures of the error messages I'm getting. I've tried everything I come across on these forums, and nothing seems to fix the issue. Does anyone know how to get around this?
eddieofny said:
Attached are pictures of the error messages I'm getting. I've tried everything I come across on these forums, and nothing seems to fix the issue. Does anyone know how to get around this?
Click to expand...
Click to collapse
There should be a PIT file packaged into the AP.tar. You need to extract this and use it in the PIT tab in Odin.
See this guide
V0latyle said:
There should be a PIT file packaged into the AP.tar. You need to extract this and use it in the PIT tab in Odin.
See this guide
Click to expand...
Click to collapse
That's exactly what I did that caused it to throw these error messages
eddieofny said:
That's exactly what I did that caused it to throw these error messages
Click to expand...
Click to collapse
Are you using the correct firmware?
V0latyle said:
Are you using the correct firmware?
Click to expand...
Click to collapse
I guess I should have specified this in the original post. I'm trying to convert it from T-Mobile firmware to carrier unlocked firmware, which is exactly why I was trying to repartition the devices. Right now, it has TMB firmware on it, I'm trying to put XAA firmware on. I'm using the latest version of Patched Odin to try and accomplish that, and to the best of my knowledge, none of the files are corrupt.
eddieofny said:
I guess I should have specified this in the original post. I'm trying to convert it from T-Mobile firmware to carrier unlocked firmware, which is exactly why I was trying to repartition the devices. Right now, it has TMB firmware on it, I'm trying to put XAA firmware on. I'm using the latest version of Patched Odin to try and accomplish that, and to the best of my knowledge, none of the files are corrupt.
Click to expand...
Click to collapse
Ah. Are you following a specific guide that tells you to do this? Carrier unlocking is generally done by the carrier in question. If you're the original owner of the device, contact TMobile and ask them to unlock your phone for use on another network. Your account must be paid off and in good standing to do this.
You can't unlock a phone simply by flashing new firmware, at least not to my knowledge.
A brief search through your post history shows that you already asked the relevant question, so it would appear that you're attempting to do something no one recommended without the knowledge that it will work.
It's better to ask questions before you try to do something you don't really know anything about, because the knowledge and expertise held by many here on XDA can save you a lot of pain. Trying to do things your own way can result in your device becoming no more useful than the average pebble.
As I said above, you cannot carrier unlock a device by flashing different firmware. It is hardware locked to the TMobile network, and to unlock it, the original owner and account holder must contact TMobile for the unlock code.
There are professional methods that can perform an unlock but this is not in the realm of the average user, and those tools are not available here.
V0latyle said:
Ah. Are you following a specific guide that tells you to do this? Carrier unlocking is generally done by the carrier in question. If you're the original owner of the device, contact TMobile and ask them to unlock your phone for use on another network. Your account must be paid off and in good standing to do this.
You can't unlock a phone simply by flashing new firmware, at least not to my knowledge.
Click to expand...
Click to collapse
It's not to carrier unlock it, the phone is already carrier unlocked. But the TMO firmware does not allow for OEM unlocking and comes with a ton of bloatware as well. From all the research I've done, flashing unlocked firmware solves both of those problems
eddieofny said:
It's not to carrier unlock it, the phone is already carrier unlocked. But the TMO firmware does not allow for OEM unlocking and comes with a ton of bloatware as well. From all the research I've done, flashing unlocked firmware solves both of those problems
Click to expand...
Click to collapse
What research where?
Is this a Snapdragon device?
You shouldn't need to repartition your device to flash a different CSC. However, flashing firmware with a different CSC won't enable OEM unlocking.
V0latyle said:
What research where?
Is this a Snapdragon device?
You shouldn't need to repartition your device to flash a different CSC. However, flashing firmware with a different CSC won't enable OEM unlocking.
Click to expand...
Click to collapse
No, it's a MediaTek device. Honestly, I've read so much stuff, I wouldn't be able to remember where. I've read alot from here, as well as Stack Overflow and pretty much anywhere on the internet that looked like it had answers. I came away with the impression that carriers could choose to remove OEM Unlocking from their firmware, but that non-carrier firmware as a general rule of thumb would have that option available. As it stands, I don't have OEM Unlocking in my Developer Options at all
eddieofny said:
No, it's a MediaTek device. Honestly, I've read so much stuff, I wouldn't be able to remember where. I've read alot from here, as well as Stack Overflow and pretty much anywhere on the internet that looked like it had answers. I came away with the impression that carriers could choose to remove OEM Unlocking from their firmware, but that non-carrier firmware as a general rule of thumb would have that option available. As it stands, I don't have OEM Unlocking in my Developer Options at all
Click to expand...
Click to collapse
Well...Yes and no.
There are a couple of properties that determine whether OEM Unlocking is visible: ro.oem_unlock_supported which is set at build time, and sys.oem_unlock_allowed
The first one is generally set at build time. The second one can be dynamic, like if the OEM/carrier wants the device to normally be unlockable, but wants E.T. to phone home to determine whether it should be allowed.
It's hard to say what the circumstance is here. But, in most cases, simply flashing different firmware will not permit unlocking the bootloader; in fact, a locked bootloader will generally prevent flashing anything but the firmware intended for that specific device.