Related
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)
Noob question I know but I've tried reading up on the subject as much as I can - I still don't fully understand what exactly the locked loader does to this phone (aside from making it more difficult to root) and would really appreciate a brief explanation.
As I understand now the phone can be rooted, ROMs can be loaded (but they have to be specific to the VZW S3 right?), and full recovery options as well. Basically wondering what the disadvantages are and if they're more significant than just a little more work to root/mod the phone? Much thanks!
It prevents root access, you know jail breaking. You can't control your rom. You use the one provided to you by Verizon with all their bloatware. You can't change what software was delivered to you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
It prevents changing boot.img
Sent from my SCH-I535 using xda app-developers app
saucyzest said:
Noob question I know but I've tried reading up on the subject as much as I can - I still don't fully understand what exactly the locked loader does to this phone (aside from making it more difficult to root) and would really appreciate a brief explanation.
As I understand now the phone can be rooted, ROMs can be loaded (but they have to be specific to the VZW S3 right?), and full recovery options as well. Basically wondering what the disadvantages are and if they're more significant than just a little more work to root/mod the phone? Much thanks!
Click to expand...
Click to collapse
A locked bootloader is ultimately intended to prevent you from potentially costing the carrier $money$ by:
Bricking your phone and then playing dumb when you return it for an exchange. (people on xda opening admit to this kind of fraud. kinda sad. you brick it you keep it!, or buy another)
Modifying your phone and then blaming bugs on the carrier. A support vampire.
Assuring content providers they've made exclusive deals with that their content is "secure".
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
jmacko said:
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
Click to expand...
Click to collapse
Thank you for this explanation, I found it helpful to hear such an analogy.
jmacko said:
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
Click to expand...
Click to collapse
Thanks that really helped. So in the example of Jelly Bean -sounds like we need to wait for Verizon to release a version of it? Do all custom ROMs as well have to be based off of the VZW file that checks ok with the bootloader?
I'm really only concerned with Jelly Bean (knowing how long VZW takes to release stuff) and that wifi nag screen, I want to punch someone in the nose every time i see it...I will check out that presentation over lunch, would love to learn all about the details.
interesting and helpful topic.. however.. i thought i understood the locked bootloader situation on my droid bionic i could flash any rom i wanted to in conjunction with bootstrap wich i believe to be a bootloader by pass based recovery but no kernals were able to be flashed that is what i understood to be a locked b.l was not overclocking or custom kernals maybe i was wrong this whole time..
Bfitz26 said:
interesting and helpful topic.. however.. i thought i understood the locked bootloader situation on my droid bionic i could flash any rom i wanted to in conjunction with bootstrap wich i believe to be a bootloader by pass based recovery but no kernals were able to be flashed that is what i understood to be a locked b.l was not overclocking or custom kernals maybe i was wrong this whole time..
Click to expand...
Click to collapse
Weird this is how i understood it as well. I'm coming from the Droid X2 and thanks do DK we had cm9 up and running with ICS but the bootloader was locked down. I took it that bootstrap is a recovery tool that works in a way of when your phone is off and you plug it in you boot up to the bootloader. This would allow you to re-flash a rom if your current one was corrupt.
So in my mind you can run different roms and different android versions its just harder to get them on the phone. But from what i've seen you cant flash a new kernal if the bootloader is locked.
Maybe i miss understood this if so i really would like to know fully how this works
On the verizon gs3 the locked bootloader is keeping us from flashing a custom kernel thru odin...we can root and flash a custom rom / recovery but it has to utilize the stock kernel currently. Our bootloader debacle is nothing like moto devices and I wish folks would stop comparing the 2!
droidstyle said:
On the verizon gs3 the locked bootloader is keeping us from flashing a custom kernel thru odin...we can root and flash a custom rom / recovery but it has to utilize the stock kernel currently. Our bootloader debacle is nothing like moto devices and I wish folks would stop comparing the 2!
Click to expand...
Click to collapse
Exactly, what a locked bootloader will allow you to do will vary on different phones and firmwares. I've known some which would not even allow you to flash a recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
I really hope we get the bootloader unlocked would love to see cm on this phone with some of invisblek's great kernels. btw will I be able to even usrge "set cpu" to overclock and under clock with verizon stock kernal or can this be done with tweaks in the build.prop file, forgive me if this sounds stupid its been a while and I am a samsung's odin first time user.
Sadly this is the outcome of Americans NOT buying a device without a subsidy from the carrier.
Kind of like whining about NOT getting the best Porterhouse steak when buying with food stamps......
I would love to see an end to carrier subsidies.
~~~Sent from the 23rd century, thru a Samsung Onehunglow powered by Walmart brand Higgs Boson particles. (Aisle 27)~~~
I am disappointed in samsung they start to look like Apple can not my apps to my sd card write that they have locked that 2
From what I have read, the answer is no but I have some more questions so I guess Id ask anyway.
Transformer was very expensive and I have more than a year of warranty left. On the other hand I would very much like some of the features that require root. What action is possible to roll back? Unlocking, rooting or flashing a custom rom? I need to unlock the device before I can root it right?
I would use a number of features that rooting allows, but my main desire is to be able to use keyboard dock and mouse or even a gamepad as game controllers. Only program that can do that (joy2touch) requires root. But if I had root I guess I would try Cyanogenmod too because I can only see people praising it for how greatly it improves experience.
Also, there is lots of information around here but its still not dumb enough for someone who just wants to root a device but has no idea where to start (its pretty confusing). So sorry in advance for possibly asking obvious questions.
3DeX said:
From what I have read, the answer is no but I have some more questions so I guess Id ask anyway.
Transformer was very expensive and I have more than a year of warranty left. On the other hand I would very much like some of the features that require root. What action is possible to roll back? Unlocking, rooting or flashing a custom rom? I need to unlock the device before I can root it right?
I would use a number of features that rooting allows, but my main desire is to be able to use keyboard dock and mouse or even a gamepad as game controllers. Only program that can do that (joy2touch) requires root. But if I had root I guess I would try Cyanogenmod too because I can only see people praising it for how greatly it improves experience.
Also, there is lots of information around here but its still not dumb enough for someone who just wants to root a device but has no idea where to start (its pretty confusing). So sorry in advance for possibly asking obvious questions.
Click to expand...
Click to collapse
If you just want root to use joy2touch, then your warranty is still good. If you unlock your device, then your warranty is voided... you can find more information about unlock and root here.
http://forum.xda-developers.com/showthread.php?t=1833212
Good luck..:fingers-crossed:
Yes but, there is rooting for either unlocked devices or devices running ICS or lower. And whatever rooting for JB I found (im running newest OTA) is only for unlocked devices as well. As I understand it, rooting does not void the warranty but unlocking does? Does that mean im screwed? I dont even know the difference between unlocking and rooting...
3DeX said:
Yes but, there is rooting for either unlocked devices or devices running ICS or lower. And whatever rooting for JB I found (im running newest OTA) is only for unlocked devices as well. As I understand it, rooting does not void the warranty but unlocking does? Does that mean im screwed? I dont even know the difference between unlocking and rooting...
Click to expand...
Click to collapse
A rooting is allowed you to access your system files so you can modify them as will. A unlocking is allowed you to install custom rom and recovery. Someone else may have a better explaination for you.
No, you still can root your device if you have a bootloader .8 or earlier. If you have the latest bootloader, you can downgrade and root it..
LetMeKnow said:
No, you still can root your device if you have a bootloader .8 or earlier. If you have the latest bootloader, you can downgrade and root it..
Click to expand...
Click to collapse
Rooting exploits a bug in the kernel, not in the bootloader, so it's the ROM/kernel build 10.6.1.14.8, not the bootloader build. But it's always the same on locked devices anyway.
Uhm... you are confusing me even more. So is there a rooting guide that doesnt involve unlocking, can be reverted or doesnt void warranty, and works with newest stock OTA?
To my knowledge I dont have any kind of bootloader.
_that said:
Rooting exploits a bug in the kernel, not in the bootloader, so it's the ROM/kernel build 10.6.1.14.8, not the bootloader build. But it's always the same on locked devices anyway.
Click to expand...
Click to collapse
Thanks _that. What I meant is the latest firmware from Asus.
@3DeX
1. Download the Asus firmware 10.6.1.14.8
2. Backup your personal data and everything that you like to keep to your computer or your external SD.
3. Make sure that your battery is full so it is not shutdown during the installing process..
4. Unzip it once because there is another zip file insde it.
5. Copy the second zip file to the root directory of your internal SD.
6. Reboot your tablet.
7. After reboot, you will see the downgrade notification in the lower right corner.
8. Click on the downgrade notification and follow the instructions.
9. During the installing process, Do not try to turn it off. It will reboot by itself when the installation is completed. It may take 2 to 3 minutes..
10. Use motochopper to root your device.
Good luck..
Good afternoon people of XDA,
Today is the dawn of a new day. A day where we begin the road to unlocking the bootloader to something that many believe is unlockable. Me and a few other users are starting a bounty to bring the incentive to life for all active developers. You can find my previous thread here. Now, when I say progress has been made, I mean that we have gotten into fastboot, we have donation incentives and we already have root so our tools are there we just have to find the exploit. Every day people are finding new exploits furthering our cause into reaching our goal. Now to the developers who want to pursue this, I've very much so tried to get active commands in fastboot but basically its just a dead fastboot for right now. The board on this phone and technologies behind it are so similar to its predecessors that somethings got to give. If you are interested in this cause, i.e. donating or deving on it, please contact me here, or email me at [email protected]
This is in our grasps friends. Spread the word, grab your fellow developers and lets get this thing to be a free wad of cash for whoever can bust it. Lets do this.
Attached is the spreadsheet for the current donations.
this kind of things never work...i mean, you make a donation and the people or the persons behind the scenes when getting high values like 400-500$ then buy a new phone and move on letting the desired phone to get development in the trash!!
Noooo, people should see, if a year old phone never came to life in development in the first 6-8 months then the development for it is dead and if you like to custumize the phone and flash things you need to move to a more flashable-friend device!
I have to agree with this. The Tmobile version has unlocked bootloader yet barely no development. What would make me that unlocking VS990 bootloader would all of a sudden spur development.
beavis5706 said:
I have to agree with this. The Tmobile version has unlocked bootloader yet barely no development. What would make me that unlocking VS990 bootloader would all of a sudden spur development.
Click to expand...
Click to collapse
I personally (and I think many other users) don't really need cooked roms. With gravity box, xposed and some other apps, I can "cook" my own rom (and believe me, it won't be that hard). All we need is a method for rooting. Using an android without rooting is even worse than an iphone without jailbreaking since iphones are undoubtedly smoother
presariohg said:
I personally (and I think many other users) don't really need cooked roms. With gravity box, xposed and some other apps, I can "cook" my own rom (and believe me, it won't be that hard). All we need is a method for rooting. Using an android without rooting is even worse than an iphone without jailbreaking since iphones are undoubtedly smoother
Click to expand...
Click to collapse
Indeed, a rooting method for version above MM is the most importing thing for us rather than flashing custom rom. However, system-less root is need to root MM or above and this is required modifying boot.img, therefore, bootloader unlocking is need. Unless, we have found a way to sign the modified boot.img to deceive the offical bootloader.
ivangundampc said:
Indeed, a rooting method for version above MM is the most importing thing for us rather than flashing custom rom. However, system-less root is need to root MM or above and this is required modifying boot.img, therefore, bootloader unlocking is need. Unless, we have found a way to sign the modified boot.img to deceive the offical bootloader.
Click to expand...
Click to collapse
What did you mean by "unless"? Have you found an evidence that MM bootloader is unlockable or not?..
presariohg said:
What did you mean by "unless"? Have you found an evidence that MM bootloader is unlockable or not?..
Click to expand...
Click to collapse
I mean even if the bootloader is not unlockable, somethings can be done to let us perform the same things just like bootloader is unlocked.
For example, some dev in G2 and G3 have released a tool called "Bump!" before that can sign any third party image and let it able to be run on offical locked LG bootloader.
source: http://forum.xda-developers.com/lg-g3/orig-development/bump-sign-unlock-boot-images-lg-phones-t2935275
But of course, since LG have fixed the bug, we can no longer do the same tricks now.
In China, there is name ???he has lg tool, this tool can unpack repack kdz tot, add root in tot.
This is weibo id http://m.weibo.cn/u/1684239753
Need help
andy_zhang said:
In China, there is name ???he has lg tool, this tool can unpack repack kdz tot, add root in tot.
This is weibo id
Click to expand...
Click to collapse
Hey, So I've been working to be able to get root, so far I have added root to the system.img and that's all done, I need this tool to be able to repack. Can anyone, or you, contact him and get this tool? This would be so helpful for me to get root and release it!!!!
abine45 said:
Hey, So I've been working to be able to get root, so far I have added root to the system.img and that's all done, I need this tool to be able to repack. Can anyone, or you, contact him and get this tool? This would be so helpful for me to get root and release it!!!!
Click to expand...
Click to collapse
What version of Android you are going to add root? I wonder that you cannot simply add root in /system after Android 6.0.
ivangundampc said:
What version of Android you are going to add root? I wonder that you cannot simply add root in /system after Android 6.0.
Click to expand...
Click to collapse
I'm trying different things but still i need to figure out how to repack a tot to find out what's going to work!! Does anybody know how to get that application?
abine45 said:
I'm trying different things but still i need to figure out how to repack a tot to find out what's going to work!! Does anybody know how to get that application?
Click to expand...
Click to collapse
For MM, unless you've found a way to get the SELinux context needed, repacking the system image will not work.
anyone having any luck with rooting MM?
I think at this point what we really need is a small set of testers who have a good insurance policy on their phones and are willing to risk bricking their phones. We've got the outline of a method which looks viable, but the details haven't been worked out and is hence likely to produce a few bricks before we get it working.
Sorry for dropping of the face of the planet for the past two months. In testing with my device it ended up being FUBAR after wiping my aboot completely and with that the phone would not boot to anything but a black screen. I sent it into LG and after some time they finally just replaced my motherboard. But the absolute sad part is that they have me upgraded to 6.0 which absolutely is crushing my world. SO until further notice I will not be testing the unlocking of the bootloader anymore but I will make efforts here in a few weeks to start work on rooting the device. @alvislee[email protected]
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