Database Info

Sim unlocking question

Hello, I just bought an Alcatel Onetouch idol 3, from my Romanian provider(Vodafone), as I saw in other threads over here, everyone's talking about sim unlocking on websites, but my question is..
Is there any way to unlock the sim via bootloader, or flashing another firmware ?
Thank you

I also tought of the next way:
Unlock bootloader via WinDroid, gain the supercid, then use the windows update utillity to make an firmware update to an unlocked firmware
What you think ?

Scutariu said:
I also tought of the next way:
Unlock bootloader via WinDroid, gain the supercid, then use the windows update utillity to make an firmware update to an unlocked firmware
What you think ?
Click to expand...
Click to collapse
No one has reported on this forum to my knowledge a successful sim unlocking from a provider purchased idol 3. Here in USA it comes out unlocked from Amazon. I think you are confusing bootloader and sim unlock because I know of no "firmware" method of sim unlocking short of having the unlock code....although I certainly could be wrong Since you have only so many tries the best method is get your provider to give you the unlock code. Here in the USA you can get one from your provider if your account is in good standing and it's been 90 days since your last request. Most folks tell them they are going overseas and want to be able to use the phone....something similar might work for you?.

I went to my provider, and checked it there, the unlocking code was 60e, because the contract was still available, anyway..
I went to a GSM, and the guy took me 10e to unlock it xD

Can anyone verify if nougat root of Verizon S6 posted on androidinfotech is legit?

I have been watching for a root method for awhile and found a method posted on androidinfotech. I am not familiar with the site and don't know if it is legit and am not brave enough to be the first to try it. Anyone have insight? Been out of the game too long.

I tried to flash this through Odin v3.10.6. Although the image failed to flash, it didn't brick the device. The instructions on the guide stated that the bootloader had to be unlocked, which AFAIK is not possible as of now. For anyone who is interested in seeing the article, it was located here: http://www.androidinfotech.com/2017/05/root-samsung-galaxy-s6-verizon-sm-g920v-nougat.html

There was never a way to unlock the bootloader on the Verizon s6. Article must be totally confusing another model.

My thought is someone bought a unlocked phone (Best Buy was selling them when I got my S6) and used Verizon as carrier, so technically he would have a unlocked bootloader on Verizon.

But the same page of cf autoroot, da support what is not that is ... In theory will never be able to unlock the bootloader?

Now You Can Root s6 Verizon Nougat Follow this :
https://forum.xda-developers.com/verizon-galaxy-s6/general/root-nougat-s6-verizon-t3710864

How To Root S7 930U on TMobile Network???? I've searched xda and youtube

So my s7 930u is here. I've found hundreds of methods on here and youtube and odin just fails..
Who has rooted their s7 930u android 7.0 phone. And what exact method did you use. This is getting ridiculous

tried this https://www.youtube.com/watch?v=KawiIZ4bAV8
annnnnnnd now my phone is bootlooped
im flashing 7.0 stock firmware (latest update) with odin 3.12.10
seemed to be the only odin that flashed bl + ap + cp + csc correctly for me
if anyone has the latest method used to root this phone id greatly appreciate a link or tut

removed

removed

Since the US models have a locked bootloader, it's much harder to root than international. I think they'll reject anything from Odin that isn't official firmware.
You might have more luck in the US/Snapdragon specific sections of the forums, near the bottom: https://forum.xda-developers.com/galaxy-s7

Beanvee7 said:
Since the US models have a locked bootloader, it's much harder to root than international. I think they'll reject anything from Odin that isn't official firmware.
You might have more luck in the US/Snapdragon specific sections of the forums, near the bottom: https://forum.xda-developers.com/galaxy-s7
Click to expand...
Click to collapse
I thought oem unlock was unlocking the bootloader? I can simply do that in developer options.

OEM unlock as in the developer settings menu? That toggle only works on Exynos (930F/FD/W8) devices, on Snapdragon (930U/V/T/P/A) it doesn't actually do anything. SD bootloader has and likely will always be hard locked.

Beanvee7 said:
Since the US models have a locked bootloader, it's much harder to root than international. I think they'll reject anything from Odin that isn't official firmware.
You might have more luck in the US/Snapdragon specific sections of the forums, near the bottom: https://forum.xda-developers.com/galaxy-s7
Click to expand...
Click to collapse
Beanvee7 said:
OEM unlock as in the developer settings menu? That toggle only works on Exynos (930F/FD/W8) devices, on Snapdragon (930U/V/T/P/A) it doesn't actually do anything. SD bootloader has and likely will always be hard locked.
Click to expand...
Click to collapse
So why all the tutorials and YouTube videos on all the different methods of rooting snapdragon s7 if the bootloader doesn't unlock for root. Wtf

I've never watched them so I can't say, but I would assume they would use round about methods to do it? For example Exynos is simply flash TWRP on with Odin, then flash a SU zip.
Do the youtube videos tell you to do that with the snapdragon models, or is it some arbitrary multi step process? The only way I can imagine rooting Snapdragon is exploiting security flaws. I've also seen mentions of flashfire but I don't know what it does.
Like I said you'd have better luck going to the AT&T/T-mobile/Verizon etc sections. This area of the forum is mostly for Exynos.

I don't even know what this phone classifies under.
It was a Verizon phone, with Verizon logo on back.
Unlocked.
Now it's on TMobile Network.

aarongotgame said:
I don't even know what this phone classifies under.
It was a Verizon phone, with Verizon logo on back.
Unlocked.
Now it's on TMobile Network.
Click to expand...
Click to collapse
Isn't there a method to unlock a bootloader?

Carrier unlocked just means you can use it on any carrier network, which is you've got.
But bootloader lock is at a firmware level, and can't be done for any US model S7.
Since all the US models are basically the same, any guide in any of their sections should work for any other model. Yours is a G930V but you can use any guide or firmware from any other US model S7.

You need to root using an engineering bootloader. Not sure if there's a version compatible with the latest update.
You will have problems, as eng BL is not stable, and your battery will not charge past 80%.

So basically is really difficult/impossible Root a 930u? and more difficult flash with a custom firm?
Investigating because just buy a Samsung S7 gm-930u and want to debloat it.
How can i know if is a snapdragon? I am on new zealand not US.

Rooting is difficult, flashing custom firmware, as in a ROM is basically impossible on snapdragon SoC's. With a locked bootloader you can't modify the boot image which is needed for ROMs.
To check your model boot into download mode by turning it off, then pressing and holding vol down + home + power. In there it will tell you your model, being in new zealand you should be on a SM-G930F or FD unless you grey imported.
Same button combo for ~10 secs gets you out of download mode.

Yes is the grey and is 930U pitifully.
So I should sell it and buy another one haha
Thanks for the advice.

Question Is it possible to unlock the bootloader by flashing a BL file that is unlocked?

I have a A125U that I can't unlock the bootloader of. There's no OEM unlock option in the Developer Options, there's no way to unistall system updates to try the date/time thing to get OEM unlock, nothing else I've tried has worked at all. I even tried flashing A125F firmware to no avail, of course. I was thinking, the BL file is the bootloader, is there a way to flash a bootloader that's already unlocked? Or is that not how this works?
If not, does anyone know how to get OEM unlock to show on the A125U? It's been driving me insane.

Not possible unfortunately

no

LOOOOOOOL
This is the biggest lie I've ever seen in my life!!! of course it,s possible ddd. Everything is possible especially this. Trick to your issue, is just that you have to corssflash to the Canadian firmware on your A125U which is the US model. But that doesn't matter, that's nothing because those 2 phones run on the same hardware so the firmware operates with both. Even the SW_REV value doesn't do anything in that situation. You can take the U models and flash it to W(Canada) but that's useless because then you're locked out of natively unlocking the PBL. Just grab the Canadian firmware and crossflash it via heimdall or patched Odin which is the same thing. Erase old NAND.
Also don't think that stuff like this isn't possible, of course it is. You just have to try harder and harder until you get the result you're stasifed with. There is community with a bunch of us enthusiasts (discord server link is on my profile). Don't be scarred to ask here on xda and there in the server. Also you can dm me for help, I'll help you, don't worry.
Hope I helped, be sure to ask if misunderstood or need more help. Also check out some stuff i wrote on this forum. It's very helpful and interesting.
Stay safe,
Krypton

Question Can anyone tell me how to get my A125U to accept a repartition?

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.