Hello I was wondering if I could be pointed in the right direction. I was recently cursed with Samsung's knox crap because I didn't start messing with rooting until after the 4.3 update. Knox clicked and I am forever sick with 4.3. Except, I recently got a hold of a spare jtag connector from a friend. It is not a riff box it is an msp430-jtag connector. Would there be anyway way to hook this to my computer and write over 4.3 with an unlocked 4.3? Would I lose download mode or anything? I found a video of some guy decompiling 4.3 stock from a mini s4 and if you simply delete aboot.img sm1 sm2 and sm3 it fully gets rid of Knox. That is my goal with the jtag. Is there any software I can use that will read the storage? Well a jtag work in the first place or did Samsung find a way to prevent that too. Thanks!!!
bobbyofna said:
Hello I was wondering if I could be pointed in the right direction. I was recently cursed with Samsung's knox crap because I didn't start messing with rooting until after the 4.3 update. Knox clicked and I am forever sick with 4.3. Except, I recently got a hold of a spare jtag connector from a friend. It is not a riff box it is an msp430-jtag connector. Would there be anyway way to hook this to my computer and write over 4.3 with an unlocked 4.3? Would I lose download mode or anything? I found a video of some guy decompiling 4.3 stock from a mini s4 and if you simply delete aboot.img sm1 sm2 and sm3 it fully gets rid of Knox. That is my goal with the jtag. Is there any software I can use that will read the storage? Well a jtag work in the first place or did Samsung find a way to prevent that too. Thanks!!!
Click to expand...
Click to collapse
That could work on anything other than our phone model. Tampering with the bootchain at all will cause an instant hardbrick because of the locked bootloader. We have the only variant with a locked bootloader on 4.3.
We have no such thing as an unlocked 4.3 bootchain, but if you had one your idea would work perfectly. You just overwrite the original chain and it'll boot, but flashing anything currently available with a riff box except the vrucml1 bootchain will hardbrick the device.
Sent from my SCH-I535 using Tapatalk 2
To add it is not Knox that locked the bootloader. It is Qualcom code that burnt the Q-fuse on the processor making it non rewritable through that particular fuse. Only way to unlock from my understanding would be to be able to route through another fuse as there are like 4 of them. This enables Samsung to modify the bootloader a limited amount of times.
I'm still wondering if we could boot with the insecure boot loader if we "bricked" the 4.3 one then boot from sd with the insecure one. Does the debrick image hold all of the boot chain or is it just the part that seems to be easily bricked? Sure if that could work we would be dependent on the sd card but that wouldn't matter for a lot of people. I have another related question that someone might be able to answer. Is it possible to use the debrick image on a thumb drive connected with a otg cable?
ThePagel said:
I'm still wondering if we could boot with the insecure boot loader if we "bricked" the 4.3 one then boot from sd with the insecure one. Does the debrick image hold all of the boot chain or is it just the part that seems to be easily bricked? Sure if that could work we would be dependent on the sd card but that wouldn't matter for a lot of people. I have another related question that someone might be able to answer. Is it possible to use the debrick image on a thumb drive connected with a otg cable?
Click to expand...
Click to collapse
The debrick image doesn't have a bootchain. It's just a stock system image that the bootchain verifies and force boots into.
The bootchain is still present through the regular mechanism through the system checks (ie: fuses, chips) and knows it's booting a correct system image, you can't force a bootchain through an external SD card.
Sent from my SCH-I535 using Tapatalk 2
Taking it to verizon?
BadUsername said:
That could work on anything other than our phone model. Tampering with the bootchain at all will cause an instant hardbrick because of the locked bootloader. We have the only variant with a locked bootloader on 4.3.
We have no such thing as an unlocked 4.3 bootchain, but if you had one your idea would work perfectly. You just overwrite the original chain and it'll boot, but flashing anything currently available with a riff box except the vrucml1 bootchain will hardbrick the device.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
youtube.com/watch?v=75DKAGNstbM
I did not mean using a bootchain I know it'll brick it I have made that mistake before and it is possible to come back from it by the way. If you watch this video he takes the current 4.3 rom and removes knox and the bootloader and reflashes it. Of course he was able to do this because he didn't trip knox in the first place which I have. But my goal with the JTAG would be to write over the memory bypassing the processor and flash a deknoxed 4.3 from there. Also I just found out that apparently some law went through which requires your carrier to unlock the bootloader for you if you take it to them and ask. Does anybody know of this? It would make sense that it says please take your phone to an authorized verizon dealer when the bootloader stops you. If that is true and I take my phone to them, would there be a way to record everything they are flashing onto my phone without hiding a usb sniffer so that we can figure out how to unlock this crap? Thanks.
bobbyofna said:
youtube.com/watch?v=75DKAGNstbM
I did not mean using a bootchain I know it'll brick it I have made that mistake before and it is possible to come back from it by the way. If you watch this video he takes the current 4.3 rom and removes knox and the bootloader and reflashes it. Of course he was able to do this because he didn't trip knox in the first place which I have. But my goal with the JTAG would be to write over the memory bypassing the processor and flash a deknoxed 4.3 from there. Also I just found out that apparently some law went through which requires your carrier to unlock the bootloader for you if you take it to them and ask. Does anybody know of this? It would make sense that it says please take your phone to an authorized verizon dealer when the bootloader stops you. If that is true and I take my phone to them, would there be a way to record everything they are flashing onto my phone without hiding a usb sniffer so that we can figure out how to unlock this crap? Thanks.
Click to expand...
Click to collapse
That law is for the sim unlock and 99% of Verizon store employees and customer service reps will have no idea how to help you with any problem.
ThePagel said:
That law is for the sim unlock and 99% of Verizon store employees and customer service reps will have no idea how to help you with any problem.
Click to expand...
Click to collapse
Are sure? because I found someone on the forums last night who said he went to verizon and they unlocked his bootloader. let me dig for it. I am definitely going to verizon tomorrow and trying for myself.
ThePagel said:
That law is for the sim unlock and 99% of Verizon store employees and customer service reps will have no idea how to help you with any problem.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2683469
Here the guy talks about asking verizon about the bootloader.
bobbyofna said:
http://forum.xda-developers.com/showthread.php?t=2683469
Here the guy talks about asking verizon about the bootloader.
Click to expand...
Click to collapse
He asked over a phone call, he was never given an unlocked bootloader. And his information isn't correct.
They will have no idea what you're talking about in a store, but if you can get a hold of a unlocked bootloader, you should ask for an S4 one also then head over to their forum to collect the $5000 bounty.
Cut me a small chunk for pointing you in the right direction though. I'd be happy with $200 or so.
Trust me, they aren't required to give you anything to unlock your bootloader. They are only required to unlock the phone for global use following termination of a plan, and the phone is already unlocked to do that.
Sent from my SCH-I535 using Tapatalk 2
fuse
Prdog1 I also have knox how can I go about modifying the fuse?
DJBurner said:
Prdog1 I also have knox how can I go about modifying the fuse?
Click to expand...
Click to collapse
You won't be able to do this without hardware knowledge and complex programming understanding.
Highly experienced developers are working on this (maybe) , there's no documented method on hardware modification for that process.
Sent from my SCH-I535 using Tapatalk 2
Thanks
Thank you very much
BadUsername said:
You won't be able to do this without hardware knowledge and complex programming understanding.
Highly experienced developers are working on this (maybe) , there's no documented method on hardware modification for that process.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Related
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
This probably can't be done, but just wondering if it's even been thought about yet.
The stock VRUCML1 bootloader is signed and is unable to be modified in any way. However, a developer edition phone should have a modified bootloader in place already that allows custom software to be flashed.
Isn't it possible to dump the developer edition bootloader? If that's dumped, then using Odin or a jtag service to install the bootloader on a normal phone could possibly unlock the phone. That way the bootloader isn't really modified, but completely replaced.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
This probably can't be done, but just wondering if it's even been thought about yet.
The stock VRUCML1 bootloader is signed and is unable to be modified in any way. However, a developer edition phone should have a modified bootloader in place already that allows custom software to be flashed.
Isn't it possible to dump the developer edition bootloader? If that's dumped, then using Odin or a jtag service to install the bootloader on a normal phone could possibly unlock the phone. That way the bootloader isn't really modified, but completely replaced.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This wouldn't work as it has to do with the device specific files. Its the same thing that stops people on sprint or t-mobile being able to flash ROMS from Verizon or at&t. Also when Samsung released there new update they tripped whats called the q-fuse, this fuse, once blown trips a system flag that makes the bootloader check the signature of each file during boot. Unfortunately once this is tripped there is no going back. This is why the boot loader on the 4.3 update is locked.
I've searched high and low and I'm not able to find a non-tripping version of root. I don't want any fancy roms just rooted stock. Help.<br/>
Nope no way to keep Knox as of now.
But the root method that's out there. Will just flash a recovery and root. It's shouldn't f change the system image. (I could be wrong but last I check.)
I like to keep Knox just in case I need to exchange the phone for any reason
Whats the best method if you have a USA AT&T note edge?
Looking for a way to root without tripping Knox as well...
Someone should start a pledge thread for it, that should get the devs interested...
Beach_Head said:
Looking for a way to root without tripping Knox as well...
Someone should start a pledge thread for it, that should get the devs interested...
Click to expand...
Click to collapse
Probably won't come for a while since not alot of devs have the phone yet.
NitroSS said:
Whats the best method if you have a USA AT&T note edge?
Click to expand...
Click to collapse
There is no current way to root the N915A. AT&T has it locked and so far no one has bothered to try to get it unlocked to achieve root.
Sent from my Samsung Note Edge using Tapatalk
In the same boat witha 915FY , willing to chip in if needed.
I'm sure I read it somewhere, just can't remember ATM....but there is a way to reactive Knox After rooting correct? I have the tmobile n915t.
strboy said:
I'm sure I read it somewhere, just can't remember ATM....but there is a way to reactive Knox After rooting correct? I have the tmobile n915t.
Click to expand...
Click to collapse
Dont think so mate... else what would be the point ? or even the hold up here ? just root and reset ?
If it were possible it woulda been announced by now i guess...
strboy said:
I'm sure I read it somewhere, just can't remember ATM....but there is a way to reactive Knox After rooting correct? I have the tmobile n915t.
Click to expand...
Click to collapse
As I understand it, KNOX flag is basically written as a "fuse". Once it's triggered, there's no going back.
And everyone, for the love of all things good and pure, AT&T and Verizon have locked bootloaders and there are NO root methods currently available. KNOX is irrelevant.
Finally, for anyone wondering about a non-KNOX-tripping method for actually ROOTABLE devices, nope. Not yet as far as I know. But why? Carriers still service phones that have the flag tripped.
jooniloh said:
As I understand it, KNOX flag is basically written as a "fuse". Once it's triggered, there's no going back.
And everyone, for the love of all things good and pure, AT&T and Verizon have locked bootloaders and there are NO root methods currently available. KNOX is irrelevant.
Finally, for anyone wondering about a non-KNOX-tripping method for actually ROOTABLE devices, nope. Not yet as far as I know. But why? Carriers still service phones that have the flag tripped.
Click to expand...
Click to collapse
In theory yes , you still get serviced but that mostly depends on the IQ of the person on the other end.
Im currently in Portugal. I took my note 3 to service and the knox was tripped . Battery Issue. They refused . I called customer service. They refused.
"If you tampered with the device, its your own fault"
I explained in other countries its still serviced , in France for example.
"this is not other countries , this is not France."
I have a 915FY now and , if possible , I would like to avoid this situation.
siriom said:
In theory yes , you still get serviced but that mostly depends on the IQ of the person on the other end.
Im currently in Portugal. I took my note 3 to service and the knox was tripped . Battery Issue. They refused . I called customer service. They refused.
"If you tampered with the device, its your own fault"
I explained in other countries its still serviced , in France for example.
"this is not other countries , this is not France."
I have a 915FY now and , if possible , I would like to avoid this situation.
Click to expand...
Click to collapse
Hmm I see. I wasn't aware of that issue. The service centers here have seen that the KNOX flag is tripped on my devices and still serviced them. All I can say is, pretty much everything that works for the note 4 (except roms) has been compatible with the edge (including root tools, TWRP, recovery-flashable mods, system file tweaks, etc.), so if any progress is made on finding a non-KNOX-tripping method, you're gonna see it on the Note 4 forums first. I'd keep an eye on that for any updates concerning your model.
I was hoping Geohots work on TowelRoot might be adapted somehow for 4.4.4 and eventually used for Note4/edge.(it stopped working for anything over 4.4.2 i was told)
I heard hes working for google now so he cant help anymore...
siriom said:
I was hoping Geohots work on TowelRoot might be adapted somehow for 4.4.4 and eventually used for Note4/edge.(it stopped working for anything over 4.4.2 i was told)
I heard hes working for google now so he cant help anymore...
Click to expand...
Click to collapse
Towelroot was only ever supposed to work on the S5. That it worked on anything else at all was chance. Anyways, it hasn't been updated in ages so don't hold your breath. If you really need root, I'd just go with one of the available methods. If you need it serviced, flash a stock ROM, go to a service center for your carrier, and act stupid. Don't start talking about root and all that. That has worked 100% of the time for me. When you took it in for service in the past (when they didn't service it) was your phone still rooted or have a custom recovery installed?
Hello all I recently got a sprint S5 activated on boost mobile and so far I am really enjoying it and I was wondering what it takes to unlock this device for root capabilities. Such as how to unlock the bootloader and S-Off and how to install TWRP.
Go here:
http://forum.xda-developers.com/showthread.php?t=2737724
wc4r said:
Go here:
http://forum.xda-developers.com/showthread.php?t=2737724
Click to expand...
Click to collapse
Sweet thanks for the link now is there an RUU method or in other words, returning the phone to complete factory stock?
Familiarize yourself with Odin. It's a PC program used to flash things like the stock tar file, which is similar to HTC's ruu.
metalfan78 said:
Familiarize yourself with Odin. It's a PC program used to flash things like the stock tar file, which is similar to HTC's ruu.
Click to expand...
Click to collapse
Alright thanks you I should have enough information now to root my phone and restore it back in case I want to restore it back to normal. Now does the bootloader need to be unlocked and do Galaxys have the S-Off option. (I came from an HTC phone which is why I am using HTC terms lol. This is also my first Galaxy Phone)
I've had HTC phones before as well, so I totally understand. There is no s-off needed. The only locked bootloaders are on Verizon and AT&T. The only concern on samsung phones is tripping the Knox counter, which only affects warranty claims (and not always).
metalfan78 said:
I've had HTC phones before as well, so I totally understand. There is no s-off needed. The only locked bootloaders are on Verizon and AT&T. The only concern on samsung phones is tripping the Knox counter, which only affects warranty claims (and not always).
Click to expand...
Click to collapse
Oh alright thank you i just wish every android phone had the same way of rooting so i don't have to learn new terms and install new drivers lol. Well ok time to go root and install cyanogenmod on this 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