Related
1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK! Also, updating to v4.5.141 and than unlocking the bootloader will also cause a hard brick!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
3.Xoom ICS release
The release of ICS for the Motorola Xoom does not help in any major way to the development of ICS on the Atrix.
Explanation/Elaboration: Yes, we do need the ICS kernel for Tegra 2. Yes, the Xoom uses Tegra 2. No, they are not the same. The atrix uses the Tegra 250 AP20H while the Xoom uses the Tegra 250 T20. Yes, the one on the Atrix is slower, but more importantly, different! (Thanks live4nyy!)
4.Carrier Unlocking the Atrix (NOT BOOTLOADER UNLOCK)
This is less of a myth, more of a guide. If you CANNOT unlock the Atrix even with the code provided (I can/will not provide), do NOT keep trying. All you are doing is wasting the number of tries you can try before the phone will not accept any more tries. What you should do is flash to an AT&T rom/radio and try again. This is assuming you want to unlock the AT&T version of the Atrix of course. Once unlocked, the Atrix can be flashed to your hearts content and will not be re-locked. (Thanks Abu-7abash!)
Any other widely mistaken facts about the atrix you want corrected?
Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head
matthew5025 said:
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.
UFOs > Bigfoot
matthew5025 said:
1.Bootloader!
When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible.
Click to expand...
Click to collapse
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?
stang5150 said:
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?
Click to expand...
Click to collapse
eFuse is an IBM invention. I posted a lengthy explanation of this a long long time ago after verifying the Atrix was using eFuse technology. When you read eval's explanation it is very accurate, except that you cannot "burn a bit". You could "set a bit" which sends the signal to overload the hardware circuit.
Carrier can specify they want a locked bootloader or not. I believe the method could be up to the manufacturer, but carrier may also specify type of bootloader lock. Of course, manufacturer may have an internal policy that all phones have a locked bootloader, but include provisions for unlocking it.
eFuse does not blow a fuse per se. This implies there is an actual fuse in the phone. eFuse (electronic fuse) is a circuit built into a chip inside the phone. When you unlock the bootloader a very small electrical charge is sent to that circuit and simply overloads it and burns it out. eFuse technology is not solely used for bootloaders. They are in many more electronic devices than you may think. eFuse is both software and hardware based. Software sends the signal, hardware circuit is blown, software checks this circuit on boot-up, when the circuit cannot be completed the software knows this, and reports, in the case of a phone, that the bootloader is unlocked.
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
---------- Post added at 12:31 PM ---------- Previous post was at 12:25 PM ----------
ifalldownalot said:
UFOs > Bigfoot
Click to expand...
Click to collapse
This ^^^^^^^! LOL
matthew5025 said:
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Well as far as I know UK version is safe to flash back to froyo. I went back from 2.3 to froyo sbf few times myself and few other people confirmed this aswell.
/edit
Never upgraded OTA so my post is useles...nice!
matthew5025 said:
1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Oem lock ******
Tried?
Sent from my MB860 using XDA App
Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL
Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk
jgc121 said:
Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head
Click to expand...
Click to collapse
Thanks! Its annoying the way they keep repeating the same stuff over and over again isn't it? Drives me up the wall!
live4nyy said:
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.
Click to expand...
Click to collapse
Thanks! Will include that point!
CaelanT said:
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
Click to expand...
Click to collapse
The reason I created this thread is so that the next time I want to correct someone, I just link them here, instead of typing out the whole thing again.
On a separate note, I see you are really active on in the Atrix community, helping others. I would like to thank you, a person who is knowledgeable, taking time to answer their questions. Can't say the some about myself.
guidoido004 said:
Oem lock ******
Tried?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
?
ssmr2t said:
Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL
Click to expand...
Click to collapse
Isn't it next Saturday? And the iPhone is the "hottest" phone here, accessories for iPhones, yes, Atrix, little.
Abu-7abash said:
Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
Thanks! Will include that!
Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there
ssmr2t said:
Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there
Click to expand...
Click to collapse
hey, hey, hey. get a room, you two. keep this thread myth related.
I heard that the exploit was patched, but I have a different sort of question.
Is the patch completely impenetrable? I'm willing to go learn android / google code or whatever I have to do to try to unlock it myself. I know of fastboot cords and such, but my knowledge is extremely basic. I'd have a LOT to learn.
Before I attempt it, I'd just like to hear from you knowledgeable veterans out there. Is it an impossible dream? I'm hoping it's just an incredibly long process or time consuming and that's why no one has done it yet. :fingers-crossed:
I'll just say this: go for it. However the experts, even the one that found the original unlock, have said that the hole is patched and that it will be impossible to open again. However, one more person looking won't hurt anything.
RikRong said:
I'll just say this: go for it. However the experts, even the one that found the original unlock, have said that the hole is patched and that it will be impossible to open again. However, one more person looking won't hurt anything.
Click to expand...
Click to collapse
Thank you. :good:
I know some people have asked about porting AOSP to the Fire TV. It's probably still a long way off, but I have managed to get it to start booting and have the boot animation display. Some stuff crashes early on, and then later in the boot, other things crash because that first thing is missing. And then it just constantly bootloops... but it's a start.
Spectacular!
My main goal is to get a full-fledged modern Linux OS with access to running my Android apps inside a window while having real-time access to Linux and all of its programs.
Thanks rbox! You're awesome! That's exactly what i wanna in my box.
I think that you can enable the "donante" in your profile, i would like to donate to reward your wonderful work!
I too would like to donate.. As well as test.. Willing to capture and submit log files. How are you booting this ROM? Unlocked boot loader on the way?
LittleBear1981 said:
I too would like to donate.. As well as test.. Willing to capture and submit log files. How are you booting this ROM? Unlocked boot loader on the way?
Click to expand...
Click to collapse
I enabled the paypal donate in my profile but it seemed a little tacky to me to have it on all my posts. So here is a donate link.
As for how I'm booting this, right now very haphazardly. In the end it will require an unlocked bootloader but jcase is the one that has to provide that. Technically, it does work with the stock kernel and I am playing around with some ideas for booting into recovery with the locked bootloader. But hopefully jcase will be able to provide the unlock soon.
rbox said:
In the end it will require an unlocked bootloader but jcase is the one that has to provide that. Technically, it does work with the stock kernel and I am playing around with some ideas for booting into recovery with the locked bootloader. But hopefully jcase will be able to provide the unlock soon.
Click to expand...
Click to collapse
IMO, it seems like jcase has no interest in releasing it. He's already said he doesn't care about the community. Just does what he does for the challenge, and I guess publicity. I could go on with more to support my theory, but don't want to come across a complainer, as no one owes us anything.
Agreed, no one owes us anything.. That said.. Jcase wherever you are.. I would like to send you 25$ (US) too. I do not ask for support.. Just the means.. The knowledge. Thanks again everyone.
LittleBear1981 said:
Agreed, no one owes us anything.. That said.. Jcase wherever you are.. I would like to send you 25$ (US) too. I do not ask for support.. Just the means.. The knowledge. Thanks again everyone.
Click to expand...
Click to collapse
he also seems to be a man of few words, so its possible hes still waiting on amazon to fix the security vulnerability before he releases it, thats the last thing he said here before he went silent, either way tho, good job RBOX, and everyone else helping.
Luxferro said:
IMO, it seems like jcase has no interest in releasing it. He's already said he doesn't care about the community. Just does what he does for the challenge, and I guess publicity. I could go on with more to support my theory, but don't want to come across a complainer, as no one owes us anything.
Click to expand...
Click to collapse
Very, very true. E-publicty ruined that guy. Its awesome to see someone still working on this box though, gj Rbox hopefully your work will lead to greater things in the future.
So it's booting all the way. I'm not sure why there is a black bar on the right side.
rbox said:
So it's booting all the way. I'm not sure why there is a black bar on the right side.
Click to expand...
Click to collapse
Are you booting from a USB stick?
jocala said:
Are you booting from a USB stick?
Click to expand...
Click to collapse
I'm actually booting it off my network right now with NFS and loop mounts. I suppose I could use a similar method to boot it from USB. I'm thinking about creating a system based on 2nd-init which some phones with locked bootloader use. Hopefully the unlock will be released before I have to do that though.
rbox said:
I'm actually booting it off my network right now with NFS and loop mounts. I suppose I could use a similar method to boot it from USB. I'm thinking about creating a system based on 2nd-init which some phones with locked bootloader use. Hopefully the unlock will be released before I have to do that though.
Click to expand...
Click to collapse
Good luck. A rescue stick for the aftv would be mighty handy.
I've worked on 2nd init for some Motorola phones back in the day.. The trick is finding a script that is not in /system that runs from init early in the boot process...
FireTV + AndroidTV
I know it is a basic question, but theoretically if you get the 2nd Init working, we could port an AndroidTV ROM into the FireTV and use it as such, right?
At the end the remote control has also the Voice functionality.
Just wondering or am I missing something?
Fgarcor said:
I know it is a basic question, but theoretically if you get the 2nd Init working, we could port an AndroidTV ROM into the FireTV and use it as such, right?
At the end the remote control has also the Voice functionality.
Just wondering or am I missing something?
Click to expand...
Click to collapse
It depends on the sourceness of Android TV (probably not open source), the availability of a system dump, and the hardware compatability. I'm not sure what you are saying about the remote control... but it doesn't have "voice functionality", it has a microphone and the system software has the support for the voice.
It seems that unlock won't be released from Jcase:
https://twitter.com/TeamAndIRC/status/505926495835922434
(it's about Kindle HDX, but it's the same case as FTV).
So... Help us rbox kenobi, you're our only hope!
Who or what exactly is responsible for the prevention of the unlocker getting released?
Wouldn't it be a middle finger to their consumers if Amazon was actually the cause of this trajedy?
krasny2k5 said:
It seems that unlock won't be released from Jcase:
https://twitter.com/TeamAndIRC/status/505926495835922434
(it's about Kindle HDX, but it's the same case as FTV).
So... Help us rbox kenobi, you're our only hope!
Click to expand...
Click to collapse
Seems I was finally able to get TWRP to display on the screen. Unfortunately it was only for a second and then it crashed and rebooted. But I'm making progress. Unfortunately I had some family issues to take care of this weekend so I didn't have as much time as I had hoped.
retroben said:
Who or what exactly is responsible for the prevention of the unlocker getting released?
Wouldn't it be a middle finger to their consumers if Amazon was actually the cause of this trajedy?
Click to expand...
Click to collapse
Of course Amazon is the "cause". They don't want you unlocking it, hence the reason it's locked in the first place. Unfortunately it looks like the DMCA is preventing the unlock from being released.
krasny2k5 said:
It seems that unlock won't be released
Click to expand...
Click to collapse
You may not need an unlocker.
As a simple test unpack recovery, modify icon_error.png, repack, dd to recovery partition and reboot recovery.
I'd be interested to know if this works on releases other than 51.1.0.2
I look through the threads and mostly what I see is T-mobile got a root. Other updates show regular roots but no mention of it applying to Sprint. Threads directed to Sprint don't say nor show much. Anyone can assist in getting a link or update for the root. I am looking very forward to it and also a mod for the DAC audio. For some reason it seems like an over rated feature as audio isn't that high as advertised and mind you I have the earphones that come free with the purchase.
I'm sure you'll see word either in the development section or in this thread. They'll need to get around a locked bootloader first.
Thanks Doug
douger1957 said:
I'm sure you'll see word either in the development section or in this thread. They'll need to get around a locked bootloader first.
Click to expand...
Click to collapse
They won't need to get around it. I don't think you WILL get around it, ever. So.
pro_granade said:
They won't need to get around it. I don't think you WILL get around it, ever. So.
Click to expand...
Click to collapse
that's what most said with the Galaxy S7 and LG G5 but they they're both rooted now
Snipars said:
that's what most said with the Galaxy S7 and LG G5 but they they're both rooted now
Click to expand...
Click to collapse
The Note 7 was rooted without unlocking the bootloader. I don't understand the under the hood specifics, but where there's a will...
Patience people. Contemporary Android is a maze of security protocols in order to get root. Not just the bootloader, but also SELinux policy, capability bounding, file-size checks, and so on. When an OEM tries to lock down a device. Really tries....It becomes hell. The phone only went on sale a week ago.
I'd suggest reading the following tale one fellow posted about his weeks long effort to chroot his Asus tablet. NOTE-his tablet had an unlocked bootloader and fastboot command access. Both are things we don't have.
https://www.thanassis.space/android.html
Skripka said:
Patience people. Contemporary Android is a maze of security protocols in order to get root. Not just the bootloader, but also SELinux policy, capability bounding, file-size checks, and so on. When an OEM tries to lock down a device. Really tries....It becomes hell. The phone only went on sale a week ago.
I'd suggest reading the following tale one fellow posted about his weeks long effort to chroot his Asus tablet. NOTE-his tablet had an unlocked bootloader and fastboot command access. Both are things we don't have.
https://www.thanassis.space/android.html
Click to expand...
Click to collapse
Not to be discouraging, but it took 18 months to get an unlocked bootloader on the Verizon Note 4.
douger1957 said:
Not to be discouraging, but it took 18 months to get an unlocked bootloader on the Verizon Note 4.
Click to expand...
Click to collapse
Oh I remember.
Me? I'm fairly well happy unrooted. About 95%
I'm not sure what is up, this isn't a new thing, but people keep coming to me (1-2 a day) with this issue.
If your phone isn't stock, DO NOT RELOCK your bootloader. You will 'soft brick' it, and at this time there is no easy route to fixing it.
If you are on EE UK, Verizon or another carrier blocking bootloader unlocks, and you used dePixel8 to unlock it, DO NOT relock your bootloader unless you are sure you don't want it unlocked again.
Finally, dePixel8 is UNSUPPORTED. Don't come to me if you can't get it to work, don't come to me if you used it them messed up your phone by flashing something bad or whatever. Its on you.
What's the fix if this does happen?
infamousjax said:
What's the fix if this does happen?
Click to expand...
Click to collapse
There isn't one and no guarantee there will be one. Don't do this.
tw1tch175 said:
There isn't one and no guarantee there will be one. Don't do this.
Click to expand...
Click to collapse
Fair enough. Thanks
This should be pinned!!
Mods?
It was all just an illusion
Interesting.. glad this didn't happen to me. I did relock my bootloader once because i was having issues activating my SIM card. I wanted see if that was the reason. Once i did manage to get the SIM activated i went through the process of unlocking using the dePixel8 method again. I guess i won't be doing that again.
Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.
Cataire said:
Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.
Click to expand...
Click to collapse
This isnt a new warning, its pretty much standard "Dont relock with non stock firmware".
JTAG is a no go, would have to attack to the ufs and rewrite at the best least the boot.img
Eh things happen. I know better now. And now I need to learn how to make it right
I don't understand why anyone WOULD relock the bootloader of not stock
318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
Some people are not as experienced as us. Not hard to imagine, just noobs, no offense guys. You live and learn, no biggie. I say respect them and help them, I say welcome noobs.
If we expect our community to grow, we need to be respective of new comers.
318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
Alpione said:
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
Click to expand...
Click to collapse
This is honestly the biggest reason I can see as to why this happens
Sent from my Pixel XL using Tapatalk
DELETED
ScytheSniper said:
First of all, I'd like to say thanks to all the hard work put into the dePixel8 BL unlock.
With that said, I would like to say a couple things about this particular statement.
1. It is slightly misleading, you can relock your bootloader and still unlock it again under the right circumstances. If your software is all stock and you use dePixel8 after relocking, it will unlock again.
2. This statement contradicts the previous one. You should probably avoid telling people "they can never unlock their bootloader again if they relock it" if there is ANY possibility that they can. After reading this statement from you in the unlocking thread I spent about 2 hours scouring threads to find out if this statement was always true, which it is not.
Again, thank you for all the hard work on getting this unlock out. The intent of my post here is only to help improve communication of potential problems.
Click to expand...
Click to collapse
There is nothing misleading about the post. The statements are true. Wait til tomorrow, when complaints start coming in about how people cant seem to unlock.
DELETED
ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
I'm not sorry. You are lacking information/knowledge on the subject. The OP statement is accurate.
The statement was made with good reason, based on fact and prior knowledge. You will see why tomorrow, when people start complaining.
DELETED
ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
The next security release should rollout tomorrow... And with that there will be a fix for VZW models preventing depixel8 from working. So IF you relock your bootloader after taking this update, we'll you'll be SOL. It's only misleading if you don't have prior knowledge of pretty much anything android.
I mean of course you can lock and unlock as many times as you want right NOW. Tomorrow will be a different story I guarantee.... But go ahead and be our guinea pig. I for one just say thank you @jcase and @beaups and listen to their advice. They've been around a long time and given us lots of goodies. I don't question them.
ScytheSniper said:
If I am lacking in knowledge and information why am I able to unlock and relock my bootloader at will on my Pixel purchased at Verizon?
Click to expand...
Click to collapse
I'm guessing you dont understand how depixel8 works.
I'm guessing you dont realize that google could remotely nix this in the butt any any moment
I'm guessing you are unaware of NDE63X at this point and it's effect on the situation.
Why don't you lock your bootloader for a few days, then try? or just sit back, watch ppl ignore the PSA, then start compaling about being stuck locked.