Database Info

2.3 rootable? Maybe not? Who knows....

Has anyone thought that maybe google has made 2.3 unrootable? Scary thought i know, but its kind of like a cat and mouse game with the developers and google/manufacturers with root patches.
Maybe google finally will put the nail in the coffin here?
WOOT. It's rooted, im happily wrong.

It's a developer phone, so why would Google want to make devs waste time trying to root.

could it be possible that Google enable root access by default, then?

djfoo000 said:
could it be possible that Google enable root access by default, then?
Click to expand...
Click to collapse
Definately not.

Dev phones have always been rootable, i doubt that will change.
The phones that have trouble being rooted are always manufacture customized ones.

it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.

jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
I'd bet that it will be rooted BEFORE!

The developer build on my Nexus One is already rooted. I don't imagine the release build will be any different from all of the previous OTAs.

jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
You are correct.

Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.

fastboot oem unlock

FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Your right, as of now I don't think Samsung locked any of their phones, but the only thing Samsung has on this phone is the hardware aspect. All the software aspect is by Google.

FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Then how do you explain threads like this (on the samsung galaxy sub forums):
[HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!]
It seems like you have carrier/sim lock and root confused. Just like nearly every phone on the market, they are locked. You will also need root to do anything that says "please root your phone". They do not ship this way...

I'm sure it will be rootable... Google doesn't want to block out developers

Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?

Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
Very true

Look right above the Youtube icon.... http://www.google.com/nexus/#!/features

luckyduck69 said:
Look right above the Youtube icon.... http://www.google.com/nexus/#!/features
Click to expand...
Click to collapse
that's unlocked for carriers with gsm...that's not root. Simply meaning it will work with at&t or tmobile by changing the sim card. Root lets you edit system files and a custom recovery to flash roms

Lmao no one so far in this thread should get one of these developer phones as you plainly do not understand what you are doing here when it comes to deciding what the difference is between root permissions and unlocked to all networks.
lets put it this way, if you are one of the above who are having trouble, dream on and steer clear from the prospects of rooting all together
unless that is you fancy yourself a very expensive paperweight?

Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
This command unlocks your bootloader on the N1/N-S allowing you to flash custom roms, but visibly voids your warranty (bootloader screen shows that it's unlocked)

USCC V20 (US996) Bootloader Unlock/Root Discussion

Just a thread for the few USCC people here - I've tried to UL the bootloader using TMO instructions - no go. It will reboot into the bootloader but it asks for the unlock.bin key (fastboot oem unlock returns an unknown command error). So at least theirs that much
Phone will also boot into recovery, and I get the associated normal options there (clear, mount /system, wide device/cache, load update via ADB, load update via SD, view recovery logs, etc). Interesting thing happens when I select "run graphics test" from the recovery menu - it gives an error, then the "no command" icon, then multicolor circles rotating - but it says "erasing" then "installing system update" then goes back to the recovery menu. Not sure if it's normal, but it's interesting.
I'm not a dev or a software guy really, but would like to hear some thoughts on the USCC version...would love to have root like the TMO - especially since it will get into the fastboot menu. Wish I knew more so I could be more help.

Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.

Killah1994 said:
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Click to expand...
Click to collapse
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...

elliwigy said:
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
Click to expand...
Click to collapse
There you go, knew I was getting something mixed up.

us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Sent from my LG-US996 using Tapatalk

jayochs said:
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Click to expand...
Click to collapse
if u read my previous post u can see i said the uscc BL is locked lol like everyone else

I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?

Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.

Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
does he have a copy of the debug kernel? you can pm me a link if possible thatd be great so we can take a look at it.. if it is an eng kernel, it could potentially help to root other variants with locked BLs
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
---------- Post added at 02:41 AM ---------- Previous post was at 02:41 AM ----------
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out

@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.

Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
hopefully you are able to as it shouldnt really take any time at all lol.. it would really help a lot of ppl out if it is in fact a debug kernel..
the root we have is a temp tcp root shell using a context we cant really do anything we need to do at all so it was pretty much a dead end so far

Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
I will pay you for the debug files

I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.

Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
you wont b doing anything to the phone.. if u have an adb root shell would just be copying a few files from the phone.. we can even tell you exactly what commands to use to make it easy.. we can invite you to a google hangout even so we can explain each step

Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
Whay are you asking for the phone?

I was looking to get what I spent for it, around $800

elliwigy said:
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
Click to expand...
Click to collapse
yeah, the US cellular us996. it's different from the American unlocked us996. according to LG anyway, it lists it as two different phones.
I'm not on a US cellular one. I'm in an unlocked one with Verizon. the post above you said unlocked had unlocked bootloader. mines as unlocked as you get, and it doesn't have an unlocked bootloader.
Sent from my LG V20 US996

http://developer.lge.com/community/...nuId=38&contsTypeCode=QUE&prodTypeCode=MOBILE
Make yourselves heard. Let LG know we want the bootloader to be unlockable on the US996. I've talked to their live chat and they claim that they "didn't know people would want to unlock their bootloader". Show them we do.

Abumarf said:
I was looking to get what I spent for it, around $800
Click to expand...
Click to collapse
Ok if you download terminal emulator and type in get prop and send me the screen shots so i can verify it is indeed a debug kernel i will buy it from you but i would like to have proof of debug kernel

Sure, here it is: https://drive.google.com/file/d/0BwI6DTQJV37Ob1BwRkRab0xPRkk/view?usp=drivesdk
Also the phone is already up on Swappa
---------- Post added at 08:45 PM ---------- Previous post was at 08:36 PM ----------
@rickberg forgot to tag you

Flash Google store Pixel image over Verizon Pixel phone???

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

[Q] I want to get my hotspot enabled, so do I need to root to do this?

Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!

If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.

FernBch said:
If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.
Click to expand...
Click to collapse
Yes sprint and bought directly from play store.
Guess I'll start with this tool eH?
forum.xda-developers.com/pixel/development/tool-skipsoft-android--google-t3482761
Problem is, I already updated via OTA to latest version. Am I screwed?

Screwed?? If you mean BL locked, no. I have the Verizon branded variant but unlocked, rooted, and flashed SU. When I saw NMF26Q was available from Google I downloaded it, installed via flash-all from fastboot, then rerooted and flashed SU again no problem.

chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
Please look at OP install instructions in this thread.
Please look at OP install instruction in TWRP thread.
I guess you aren't on Telus in Canada or your hotspot would work. When you give no information, too hard to help. But I read this forum so even though I don't have Sprint or Verizon as my provider, I know there are many threads about turning hotspot on for unlimited data plans. Guidance: read those threads too!
Then ask for specific guidance. I don't want to reread for 25 min to find and copy and paste to spoonfeed when you should read. Much nicer to fill in a few missing spots than hold your hand not having a clue of your technical knowledge and skills.
Happy holidays.
Specific guidance: update SDK tools before you start!
Sent from my sailfish using XDA Labs

so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?

chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk

chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Nothing to worry about. I just ignore it.

joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That's Verizon's equivalence of "Sorry sucka, you're on your own!"

chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?
Click to expand...
Click to collapse
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk

joetheshmo said:
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)

chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.

robocuff said:
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.
Click to expand...
Click to collapse
Which tether hack? This one? http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
If so, I have not done any tether hack yet....still reading since there are multiple ways to do it. (sprint variant/google play store)

chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
No, having SuperSU means you are no longer stock. You need all stock images to lock bootloader.
If you need a locked bootloader for Android Pay or some other apps. Install one of the customer kernels, they hide it. You still need to remove SuperSU though. From what I've seen its a bit harder to hide that for now. So you can root, make change for hotspot and remove root.
Otherwise nothing hurts to have your bootloader unlocked. It gives you more options if anything ever goes wrong. You need unlocked bootloader to even load Google factory images.
PS. I'd recommend Franco kernel as it imporoves battery life.
Sent from my Pixel using Tapatalk

chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in “wireless & networks” and you are ready to go:laugh:

eos9d said:
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in �wireless & networks� and you are ready to go[emoji23]
Click to expand...
Click to collapse
Depending on his plan, he may not have that option. Many do not, hence still need the tether hack.

Sim unlock solution developmet for T-Mobile S7 G930T

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..