Related
Hello everyone i need some help. I got verizon s3 from ebay and when i turn it on theres opened lock shows on screen with the word unlocked on the bottom. What is it stands for and how can i get rid of it? Everytime i search on google i get discussions about bootloader. Is that what it is? Thanks up front for any info.
Sent from my SAMSUNG-SGH-I317 using xda premium
Leo2005 said:
Hello everyone i need some help. I got verizon s3 from ebay and when i turn it on theres opened lock shows on screen with the word unlocked on the bottom. What is it stands for and how can i get rid of it? Everytime i search on google i get discussions about bootloader. Is that what it is? Thanks up front for any info.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Try to reboot couple times, make sure the message is legit. If it is, unlock means your phone is unlock (bootloader unlocked), which means you could flash custom rom/kernel etc... It's a good thing for people who like to play with custom rom.
Well...thats for my girl who doesnt want any custom rom and dont want to have any extra signs. My note 2 from att has a custom rom and doesnt show any signs on boot. Is this lock for verizon only? Thanks for reply.
Sent from my SAMSUNG-SGH-I317 using xda premium
buhohitr said:
Try to reboot couple times, make sure the message is legit. If it is, unlock means your phone is unlock (bootloader unlocked), which means you could flash custom rom/kernel etc... It's a good thing for people who like to play with custom rom.
Click to expand...
Click to collapse
Of the bootloader is unlocked then the screen week quickly flash. Not show unlocked I would guess it means dim unlocked.
Sent from my SCH-I535 using xda app-developers app
bootloader
The unlocked icon means that the boot loader is unlocked. This is what show up on all Verizon smartphones that have the boot loader unblocked. This is actually a good thing as it will allow you to use a custom ROM, set root privileges, and delete the garbarge-ware that is included on you phone that you probably will never use.
1seniorgeek said:
The unlocked icon means that the boot loader is unlocked. This is what show up on all Verizon smartphones that have the boot loader unblocked. This is actually a good thing as it will allow you to use a custom ROM, set root privileges, and delete the garbarge-ware that is included on you phone that you probably will never use.
Click to expand...
Click to collapse
No on the s3 if the boot loader is unlocked the initial screen with only Samsung will flash very quickly.
If it boots and the Samsung shows and has an unlocked lock that says custom under it, then you have a modified system WITH A LOCKED BOOT LOADER. By unlocking the boot loader this will go away.
I have no idea what the lock with unlocked under it means; however if you're sortied about it OP go into the development thread and follow droidstyle's guide to restore it back to bone stock.
Sent from my SCH-I535 using xda app-developers app
Sounds more likely about sim card. I flashed the phone back to stock because it was freezing all the time then did factory reset and its asking for activation. Tried to activate at the store and it doesnt activate...freezing up after couple min. So i guess it is something to do with sim unlock?
Sent from my SAMSUNG-SGH-I317 using xda premium
It means there is custom software on the phone, but the bootloader is NOT unlocked.
The custom software could be as simple as having Root access, or it could be a full custom ROM. You have two options to make it go away:
1) Unlock your Bootloader
2) Return to fully stock. http://forum.xda-developers.com/showthread.php?t=1867253
Just got mine today and it looks like the value is NO even I have allowed OEM unlock in developer options. A quick search showed if the value is no, you will never be able to unlock.
A very bad news for me. A few questions:
1. is that really not possible to unlock it? Who shall I contact? Sony or Carrier?
2. Can I root with locked Bootloader? And flash TWRP and ROMs?
Thanks
Kan
No, there is no way to root or unlock your bootloader if it reads 'No' on 'bootloader unlock allowed?'
seanwuk said:
Just got mine today and it looks like the value is NO even I have allowed OEM unlock in developer options. A quick search showed if the value is no, you will never be able to unlock.
A very bad news for me. A few questions:
1. is that really not possible to unlock it? Who shall I contact? Sony or Carrier?
2. Can I root with locked Bootloader? And flash TWRP and ROMs?
Thanks
Kan
Click to expand...
Click to collapse
I would RMA the device if it's not unlockable.
Unless u don't want to modify anything ever.
Did u got it branded from your network provider?
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
I would RMA the device if it's not unlockable.
Unless u don't want to modify anything ever.
Did u got it branded from your network provider?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
RMA means what, return? I got this from an individual, no way to return but to resell.
The carrier is Bell, a Canadian carrier. I don't see their logo on the phone.
DannyCanuck said:
No, there is no way to root or unlock your bootloader if it reads 'No' on 'bootloader unlock allowed?'
Click to expand...
Click to collapse
I had lots of devices before. Most of them allow root with unlock bootloader. Sony is an exception?
seanwuk said:
I had lots of devices before. Most of them allow root with unlock bootloader. Sony is an exception?
Click to expand...
Click to collapse
Yes it is.
On older Z series it was possible to root on stock kernel and therefore Unlocking bootloader wasn't required for rooting.
Since Z5, they implement Sony RIC and DM-VERITY, which prevents modification to system and therefore root.
To root, we need a kernel supporting root inside the boot image.
We can't flash any kernel other than stock (signed by Sony) on locked bootloader.
seanwuk said:
RMA means what, return? I got this from an individual, no way to return but to resell.
The carrier is Bell, a Canadian carrier. I don't see their logo on the phone.
Click to expand...
Click to collapse
That's a bumm.
RMA means sending phone back and receive the money in return.
Did the seller told u it's carrierlocked phone?
Mostly on carrier locked phones there's no sticker or logo from the carrier visible on the outside.
U can try to contact Bell and explain them what's the problem. In some cases a carrier can unlock it for u. (they might charge a little fee for it)
Good luck!
Sent from my E6653 using XDA-Developers mobile app
seanwuk said:
RMA means what, return? I got this from an individual, no way to return but to resell.
The carrier is Bell, a Canadian carrier. I don't see their logo on the phone.
Click to expand...
Click to collapse
If you've got the Bell Z5 then you're in the same boat as myself. No way to unlock the bootloader, thus no way to root, meaning I can have ZERO fun with this device. I even paid Bell for a SIM Unlock thinking it might trigger the bootloader unlock option to change to 'Yes' Allowed, but no such luck.
DannyCanuck said:
If you've got the Bell Z5 then you're in the same boat as myself. No way to unlock the bootloader, thus no way to root, meaning I can have ZERO fun with this device. I even paid Bell for a SIM Unlock thinking it might trigger the bootloader unlock option to change to 'Yes' Allowed, but no such luck.
Click to expand...
Click to collapse
So I guess you have contacted Bell for unlocking it but no success? Even we would like to pay a fee for it?
langeveld024 said:
Yes it is.
On older Z series it was possible to root on stock kernel and therefore Unlocking bootloader wasn't required for rooting.
Since Z5, they implement Sony RIC and DM-VERITY, which prevents modification to system and therefore root.
To root, we need a kernel supporting root inside the boot image.
We can't flash any kernel other than stock (signed by Sony) on locked bootloader.
That's a bumm.
RMA means sending phone back and receive the money in return.
Did the seller told u it's carrierlocked phone?
Mostly on carrier locked phones there's no sticker or logo from the carrier visible on the outside.
U can try to contact Bell and explain them what's the problem. In some cases a carrier can unlock it for u. (they might charge a little fee for it)
Good luck!
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for sharing with me. You are very knowledgeable. I bought from a guy who bought from Bell. I doubt Bell will actually support my request. I will try to use it for a bit and resell if I cannot live without root. I have been using root devices since HTC G1.
All phones from carriers usually have locked bootloaders, except for nexus devices. This is why you never buy from a carrier if you want custom roms.
seanwuk said:
Thanks for sharing with me. You are very knowledgeable. I bought from a guy who bought from Bell. I doubt Bell will actually support my request. I will try to use it for a bit and resell if I cannot live without root. I have been using root devices since HTC G1.
Click to expand...
Click to collapse
It's worth trying, just see how they react
I got pretty used to root too, since my first Android a galaxy S i9000 lol
Though, when I bought this phone (my second Sony) I decided to use it without root too and in the beginning it was a bit of a struggle but later I didn't miss it at all.
I only unlocked my bootloader after a few months, just to use another kernel.
You can disable most (if not all) bloatware via settings.
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
It's worth trying, just see how they react
I got pretty used to root too, since my first Android a galaxy S i9000 lol
Though, when I bought this phone (my second Sony) I decided to use it without root too and in the beginning it was a bit of a struggle but later I didn't miss it at all.
I only unlocked my bootloader after a few months, just to use another kernel.
You can disable most (if not all) bloatware via settings.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
I think Android 6 did a good job controlling app permissions. But thats the thing as you mentioned, you cannot try variety of optimizations from community. sigh.
My boootloader unlock status is also NO.
Is there anyway to flash Androplus kernel with own recovery via fastboot flashtool to get recovery and than trough him install super su zip and with that way root Z5?
Allek84 said:
My boootloader unlock status is also NO.
Is there anyway to flash Androplus kernel with own recovery via fastboot flashtool to get recovery and than trough him install super su zip and with that way root Z5?
Click to expand...
Click to collapse
If this or anything simmilar possible?
Sent from Xperia Z5
Allek84 said:
If this or anything simmilar possible?
Sent from Xperia Z5
Click to expand...
Click to collapse
Unfortunately not only way is change the device to one that says Bootloader unlock allowed YES the only carrier/network I know of that supply devices with unlockable Bootloaders for all there handsets whether payg or contract is three UK+Ireland as they only supply devices that are sim free network unlocked devices like what you would get from Sony store one of the main reasons I'm with them
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
With it being Black Friday, Verizon is selling the Pixel for a great price. I was wondering if it's possible to unlock the bootloader, flash a stock update from Google (not Verizon) to the phone, all while keeping Android Pay and being able to update the day a new update comes out? If this is possible how would I go about it? If I can't have Android Pay I can live without, but will I still be able to have the unlocked bootloader permanently along with the Google updates? Thank you! :good:
tidall said:
With it being Black Friday, Verizon is selling the Pixel for a great price. I was wondering if it's possible to unlock the bootloader, flash a stock update from Google (not Verizon) to the phone, all while keeping Android Pay and being able to update the day a new update comes out? If this is possible how would I go about it? If I can't have Android Pay I can live without, but will I still be able to have the unlocked bootloader permanently along with the Google updates? Thank you! :good:
Click to expand...
Click to collapse
No, no, no and no.
bobby janow said:
No, no, no and no.
Click to expand...
Click to collapse
Was the bootloader unlock (dePixel8) patched?
Coronado is dead said:
Was the bootloader unlock (dePixel8) patched?
Click to expand...
Click to collapse
Not sure, but I believe at some point it will be. This is not the device to buy if you want an unlocked bootloader with root.
I just joined the $240 Verizon Nexus Pixel club and have always unlocked, rooted and used custom Roms for every single device I've bought from Google. If there is an easy way to convert a Verizon Pixel to a Google Pixel I would be all over it. But maybe this is that one time that I'm going to stay stock.
Coronado is dead said:
Was the bootloader unlock (dePixel8) patched?
Click to expand...
Click to collapse
No, it hasn't been patched as of the November update. I took the update and unlocked with no problem. http://theroot.ninja/depixel8.html Note that it says... "Unexpectedly, dePixel8 was not patched in NDE63X. Have fun". Do it now while you still can.
I can confirm that the Verizon Pixel can be unlocked. I got a 128gb today for $15/month. I have grandfathered unlimited data so this is the first Verizon promo phone I've bought in a while. Unlocked, flashed TWRP, rooted, and enabled tethering.
joshw0000 said:
I can confirm that the Verizon Pixel can be unlocked. I got a 128gb today for $15/month. I have grandfathered unlimited data so this is the first Verizon promo phone I've bought in a while. Unlocked, flashed TWRP, rooted, and enabled tethering.
Click to expand...
Click to collapse
So how would one go about doing this? And would you have to relock the bootloader and unroot to update?
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
joshw0000 said:
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Just a word of caution if you're going that route.
http://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614
bobby janow said:
Just a word of caution if you're going that route.
http://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614
Click to expand...
Click to collapse
Yes that's pretty common. Been that way since the original Nexus. You shouldn't ever re-lock unless you're returning for warranty. And if you do if should happen right after you flashed stock firmware.
Sent from my Pixel using Tapatalk
joshw0000 said:
Yes that's pretty common. Been that way since the original Nexus. You shouldn't ever re-lock unless you're returning for warranty. And if you do if should happen right after you flashed stock firmware.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
No that's not correct. I unlocked, locked, unlocked and relocked my Nexus 5x recently. I was testing SafetyNet with an unlocked bootloader which failed all the time. So I finally relocked and left it that way. The Verizon Pixel is not like that. I think because you have to use a program to unlock and not just do it in bootloader.
However, you are correct in that you shouldn't relock your bl unless you have flashed the stock firmware, specifically recovery. Relocking and unlocking will wipe everything on your device, sdcard included.
joshw0000 said:
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Will I be able to flash updates all while keeping the bootloader unlocked? Or will updates relock my bootloader and soft brick my phone?
tidall said:
Will I be able to flash updates all while keeping the bootloader unlocked? Or will updates relock my bootloader and soft brick my phone?
Click to expand...
Click to collapse
Updates won't relock.
Sent from my Pixel using Tapatalk
---------- Post added at 05:32 PM ---------- Previous post was at 05:30 PM ----------
bobby janow said:
No that's not correct. I unlocked, locked, unlocked and relocked my Nexus 5x recently. I was testing SafetyNet with an unlocked bootloader which failed all the time. So I finally relocked and left it that way. The Verizon Pixel is not like that. I think because you have to use a program to unlock and not just do it in bootloader.
However, you are correct in that you shouldn't relock your bl unless you have flashed the stock firmware, specifically recovery. Relocking and unlocking will wipe everything on your device, sdcard included.
Click to expand...
Click to collapse
I don't know for sure but I think the reasoning for not relocking is that Verizon/Google will likely patch the DePixel8 exploit in future builds.
Sent from my Pixel using Tapatalk
joshw0000 said:
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
joshw0000 said:
Updates won't relock.
Sent from my Pixel using Tapatalk
---------- Post added at 05:32 PM ---------- Previous post was at 05:30 PM ----------
I don't know for sure but I think the reasoning for not relocking is that Verizon/Google will likely patch the DePixel8 exploit in future builds.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Where will I be able to download updates and how would I flash them? ( sorry for all the questions I haven't had an Android in a while )
tidall said:
Where will I be able to download updates and how would I flash them? ( sorry for all the questions I haven't had an Android in a while )
Click to expand...
Click to collapse
Here on XDA. Probably with Fsstboot.
Sent from my Pixel using Tapatalk
joshw0000 said:
Here on XDA. Probably with Fsstboot.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Would I download the Verizon version or just the completely stock Google version?
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.