Related
I recently bought an AT&T S4 I337 and I really hate the locked bootloader (and lack of cyanogenmod goodness).
On my last phone, an LG Nitro HD, the method used to unlock the bootloader was to force-flash it to a different carrier's LG image for a similar model which happened to have an unlocked bootloader.
I wonder if it's been tried on the S4... I think I remember reading that T-mobile didn't lock thier loader and since t-mobile uses the same modem type (IIRC), I wonder if one could use ODIN to flash said image (and use the update bootloader option to slip the unlocked bootloader)?
I'm probably crazy for even asking... but I didn't recall reading that this hadn't been tried.
Not a clue in the world, but I'm crossing my fingers.
ratdude747 said:
I recently bought an AT&T S4 I337 and I really hate the locked bootloader (and lack of cyanogenmod goodness).
On my last phone, an LG Nitro HD, the method used to unlock the bootloader was to force-flash it to a different carrier's LG image for a similar model which happened to have an unlocked bootloader.
I wonder if it's been tried on the S4... I think I remember reading that T-mobile didn't lock thier loader and since t-mobile uses the same modem type (IIRC), I wonder if one could use ODIN to flash said image (and use the update bootloader option to slip the unlocked bootloader)?
I'm probably crazy for even asking... but I didn't recall reading that this hadn't been tried.
Click to expand...
Click to collapse
Sorry to burst your bubble, but due to physical hardware limitations this will never work. I would go into details but it's fair plastered around the forum as to why this wouldn't work. If it where this simple we'd have unlocked the bootloader ages ago.
ratdude747 said:
I recently bought an AT&T S4 I337 and I really hate the locked bootloader (and lack of cyanogenmod goodness).
On my last phone, an LG Nitro HD, the method used to unlock the bootloader was to force-flash it to a different carrier's LG image for a similar model which happened to have an unlocked bootloader.
I wonder if it's been tried on the S4... I think I remember reading that T-mobile didn't lock thier loader and since t-mobile uses the same modem type (IIRC), I wonder if one could use ODIN to flash said image (and use the update bootloader option to slip the unlocked bootloader)?
I'm probably crazy for even asking... but I didn't recall reading that this hadn't been tried.
Click to expand...
Click to collapse
This has been mentioned and covered many, many times.
Ah. I personally didn't see it mentioned anywhere when I searched but with the ocean of threads around here, I could understand them being buried.
Well, **** then.
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs
Hello everyone
Here's my problem and my idea:
I bought T-Mobile Galaxy S7 on ebay about a week ago (Stock QC1 firmware) and now I'm in need of sim unlock, which I can't, my device's unlock fails every time through Device Unlock app
I've searched through the web past two days and found no solution whatsoever. Every service is down for now and I cannot find any ways to unlock my phone.
So, here's what I thought: Maybe here's someone who can actually develop or figure out a solution for this since many solutions are available for S6/S6e and many other t mobile phones, but not for S7.
I can be tester and provide any files/dumps if needed or anything you guys ask.
I believe I'm not the only one with this problem and if we try hard enough, we can do this. Many people can benefit from this also, so let's be useful.
To mods, if you believe this is a wrong place to post this thread, please move it where it belongs.
Thanks to you all.
So your idea is just to look at other device solutions? [emoji1]
Sent from my iPhone using Tapatalk
I guess that's the part of it
Cheers
We probably wont see a direct unlock solution on these T-Mobile/MetroPCS QUALCOMM based Galaxys for some time. The older models you mentioned are Exynos based CPUs, they are being unlocked all the time. Unlock app or trusted server for imei unlock is our only solutions for now.
Sent from my SM-N920P using Tapatalk
installerrev said:
Hello everyone
Here's my problem and my idea:
I bought T-Mobile Galaxy S7 on ebay about a week ago (Stock QC1 firmware) and now I'm in need of sim unlock, which I can't, my device's unlock fails every time through Device Unlock app
I've searched through the web past two days and found no solution whatsoever. Every service is down for now and I cannot find any ways to unlock my phone.
So, here's what I thought: Maybe here's someone who can actually develop or figure out a solution for this since many solutions are available for S6/S6e and many other t mobile phones, but not for S7.
I can be tester and provide any files/dumps if needed or anything you guys ask.
I believe I'm not the only one with this problem and if we try hard enough, we can do this. Many people can benefit from this also, so let's be useful.
To mods, if you believe this is a wrong place to post this thread, please move where it belongs.
Thanks to you all.
Click to expand...
Click to collapse
I stand with you. I think a bounty would be appropriate. I go loads of s7 and s7 edge to unlock. I may be at a huge loss if no unlock comes
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
stuntman112 said:
We probably wont see a direct unlock solution on these T-Mobile/MetroPCS QUALCOMM based Galaxys for some time. The older models you mentioned are Exynos based CPUs, they are being unlocked all the time. Unlock app or trusted server for imei unlock is our only solutions for now.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I believe of we have alot of people working toward it something interesting would come out if it. Considering s8 is also there, more people Wil be requiring unlock. It's only a matter of time
Factory reset your phone, then try to use the device unlock. You can select temporary unlock or permanent unlock. Once you are done you will have a sim unlocked device.
stuntman112 said:
We probably wont see a direct unlock solution on these T-Mobile/MetroPCS QUALCOMM based Galaxys for some time. The older models you mentioned are Exynos based CPUs, they are being unlocked all the time. Unlock app or trusted server for imei unlock is our only solutions for now.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Actually, MetroPCS s7 & s7e device unlock is available for $20 and Qualcomm S6 and below is also unlockable, there are many remote unlock services on ebay/various websites for those devices.
I've been* trying to unlock my S7 since April but no luck.
I know this issues with t-mobile Quallcomm Galaxys are about locked bootloader but that's the only thing I found out.
If someone can make bounty pool or something similar, I would gladly participate.
*edit
KillerClaw321 said:
Factory reset your phone, then try to use the device unlock. You can select temporary unlock or permanent unlock. Once you are done you will have a sim unlocked device.
Click to expand...
Click to collapse
Lol. How many factory resets required? I still haven't gotten unlocked.
jazzdglass said:
Lol. How many factory resets required? I still haven't gotten unlocked.
Click to expand...
Click to collapse
You using the latest version not rooted?
KillerClaw321 said:
You using the latest version not rooted?
Click to expand...
Click to collapse
Yup. I'm on android 7.0. I could go back to 6.0.1 too. Why do you think this is a method to unlock? You need to connect to Tmobile database to unlock. Merely factory reset won't do anything. It's all in the cloud
jazzdglass said:
Yup. I'm on android 7.0. I could go back to 6.0.1 too. Why do you think this is a method to unlock? You need to connect to Tmobile database to unlock. Merely factory reset won't do anything. It's all in the cloud
Click to expand...
Click to collapse
I know, however when I had issues with the device unlock app a fresh install of the latest version worked and I was able to temporarily unlock for a month.
I did it just now after a factory reset, rooted and running no BS Rom...
T-mobile
I went through the same ordeal. I had to actually call t-mobile and get a representative to unlock it using the phone's IMEI number so it could be used on all carriers. Call them, I'm sure they will unlock it for you. That t-mobile unlock app doesn't do anything. Also under developer options, you need to check OEM unlock before you call t-mobile.
-Just my two cents, Bob
KillerClaw321 said:
I know, however when I had issues with the device unlock app a fresh install of the latest version worked and I was able to temporarily unlock for a month.
Click to expand...
Click to collapse
My device asks for active cellular connection in order to get temporary unlock, but I can't get carrier signal since phone is locked.... are you T-Mobile customer and were you using their sim card? I am not.
Boobteg4642 said:
I went through the same ordeal. I had to actually call t-mobile and get a representative to unlock it using the phone's IMEI number so it could be used on all carriers. Call them, I'm sure they will unlock it for you. That t-mobile unlock app doesn't do anything. Also under developer options, you need to check OEM unlock before you call t-mobile.
-Just my two cents, Bob
Click to expand...
Click to collapse
Called them maybe 10 times, even used their facebook page. Every single customer representative said phone is fully paid and nothing is blocking it but they can't help me because I'm not actual / original phone owner on their database, and person I purchased this phone from has no idea what unlock is, he's impossible to deal with. Maybe you have any tips for me?
Thank you everybody for taking your time and helping us.
Just a quick update, I just flashed latest G930U firmware and after SIM card insertion, phone asks for unlock code, which of course I have no idea what it is
KillerClaw321 said:
I did it just now after a factory reset, rooted and running no BS Rom...
Click to expand...
Click to collapse
I think you and @boobteg have a paid off devices eligible for unlock. What you need to know ow is that the device unlock app doesn't work on custom roms. It requires a stock rom. There are some of us who are not eligible for unlock.
Any progress?
none so far
Same Solution
Hi! im having the same problem, i cant unlock my s7 tmobile with device unlock app, every place i try say it that the service is down. II flashed with the g930U, now the smartphone ask me for an unlock code, there is anyway to find that "unlock code" to unlock the phone in this way? Or maybe installing an non stock rom is possible to unlock the phone?
Help!! i cant use it in my actually country
morpheus1978 said:
Hi! im having the same problem, i cant unlock my s7 tmobile with device unlock app, every place i try say it that the service is down. II flashed with the g930U, now the smartphone ask me for an unlock code, there is anyway to find that "unlock code" to unlock the phone in this way? Or maybe installing an non stock rom is possible to unlock the phone?
Help!! i cant use it in my actually country
Click to expand...
Click to collapse
For now, no way to unlock..
gretting and salutations,
I recently traded my iphone 6 plus with a busted screen to a store for a galaxy s7, which is still under warrenty so im hella stoked. Anyway, love the phoone. Would like to root and flash something vanilla. or as vanilla as i can get.
I have an att model g930A, unlocked and on t-mobile.
I've been looking in the forums and im not seeing alot of roms for the att model, which i guess is different than the international version.
any insight??
As i said, id like the be as vanilla as i can get.
wifi calling is not required and neither is VOLTE.
-As long as tethering works, im fine.
Yes the US models are using a Qualcom CPU instead of exynos and have a locked bootloader which makes custom ROMs near impossible.
I believe you can flash stock ROMs with Odin, that's about it.
Beanvee7 said:
Yes the US models are using a Qualcom CPU instead of exynos and have a locked bootloader which makes custom ROMs near impossible.
I believe you can flash stock ROMs with Odin, that's about it.
Click to expand...
Click to collapse
there is an option under developer options for oem unlock and i read that unlocks the bootloader.
i dont mind the phone as it is but id like to debloat or just flash straight android. no bloat.
You can find a thread here https://forum.xda-developers.com/ga...covery-official-twrp-galaxy-s7-t3458579/page3 discussing the unlocking of bootloader.
According to a post in early May it still hasn't been done for US models.
Really thinking about flashing the U firmware but I'm worried about my unlock.
I couldn't go thru att but I did pay for a code, if that matters. Reading on the forum it should be fine if you got it thru att but IDK what my process is classified as.
Hey folks,
I am new to the rooting scene and was hoping someone could give me some guidance on how to properly root my S7 model G930VL. I've read people say that the bootloader cannot be unlocked while others said it can by simply turning on OEM unlock? Do I really have to flash another firmware in order to root and if so, how would I do that?
Thank you for your time.
Riyita said:
Hey folks,
I am new to the rooting scene and was hoping someone could give me some guidance on how to properly root my S7 model G930VL. I've read people say that the bootloader cannot be unlocked while others said it can by simply turning on OEM unlock? Do I really have to flash another firmware in order to root and if so, how would I do that?
Thank you for your time.
Click to expand...
Click to collapse
all the VLs ive seen use safestrap (i have a G900VL and its the same issue). Ive tried flashing so many different versions of S5 firmware that its becoming hopeless. I know youre talking about a S7 and im talking about a S5, but the issue should be at the very least similar. If the bootloader is locked and isnt unlockable, then all youre left with is safestrap
youdoofus said:
all the VLs ive seen use safestrap (i have a G900VL and its the same issue). Ive tried flashing so many different versions of S5 firmware that its becoming hopeless. I know youre talking about a S7 and im talking about a S5, but the issue should be at the very least similar. If the bootloader is locked and isnt unlockable, then all youre left with is safestrap
Click to expand...
Click to collapse
Hi,
Thanks for the reply back. I actually just ordered a SM-G930F international variant which I was under the impression is much, much easier to root, right? The bootloader is automatically unlocked by turning on OEM in dev settings?
Riyita said:
Hi,
Thanks for the reply back. I actually just ordered a SM-G930F international variant which I was under the impression is much, much easier to root, right? The bootloader is automatically unlocked by turning on OEM in dev settings?
Click to expand...
Click to collapse
yep and yep. you might have to contend with the 168 hour thing, but other than that it should be a cakewalk. The 168 hour thing is where the bootloader toggle wont switch unless you let it sit powered on for 168 hours. I.E., just dont reboot it for 7 days then toggle the unlock