Related
Hey guys, I'm getting a locked G2 but don't know if the boot loader will be locked too. Do you have any idea how to check that before purchase? What will be the limitations of the locked boot loader and is it possible to unlock it. Can you explain with few words what wold my options be? I really like the G2 but I might opt for the N5 at the end.
Every G2 has a locked bootloader. Mut every G2's locked bootloader can be bypassed with loki. So in short yes you will be able to flash stuff.
Sent from my LG D802
So the bootloader doesn't matter if you can flash a custom recovery, right ? I mean - what limitations will the locked bootloader bring in the long run, as I'm expecting to use the device for 2 years (buying on contract) ? I read some posts that there are some G2-s with unlocked bootloader and I'm a bit puzzled...
4.2.2 bootloader can be bypassed with a loki patch. You can root, use custom recovery, ROMs, the lot.
4.4.2 has the loki exploit patched and only root is possible so far.
Any idea if the device might ship with 4.4.2 pre installed?
Sent from my iPhone using Tapatalk
axlastro said:
Any idea if the device might ship with 4.4.2 pre installed?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
eventhough it is preinstalled, you can still flash a kdz file to go back to 4.2.2 (to achieve root & custom recovery) :good:
Well that is really good news !
Sent from my iPhone using Tapatalk
Hey guys, so I own a Nexus 6 (shamu) not a 6p, but just a curiosity question. I was told that the dm verity for the 6p was in the bootloader and not the kernel, it's built into the kernel on the shamu and the solution is just a custom kernel to remove the message, as for the 6p, is there a known way to remove those messages seeing as it is in the bootloader this time around? Nobody want's to corrupt a bootloader, or you're screwed! Lol
No.
Gytole said:
No.
Click to expand...
Click to collapse
Not at all possible yet?
H4X0R46 said:
Not at all possible yet?
Click to expand...
Click to collapse
Still no.
Thanks guys for your responses! Appreciate it! It was a super noob question, but like I said, I own a shamu and it's different. Thanks!
H4X0R46 said:
Hey guys, so I own a Nexus 6 (shamu) not a 6p, but just a curiosity question. I was told that the dm verity for the 6p was in the bootloader and not the kernel, it's built into the kernel on the shamu and the solution is just a custom kernel to remove the message, as for the 6p, is there a known way to remove those messages seeing as it is in the bootloader this time around? Nobody want's to corrupt a bootloader, or you're screwed! Lol
Click to expand...
Click to collapse
dm verity is part of the kernel. it can be seen in the linux tree. the bootloader just has a message about being unlocked. i was able to disable dm verity in AOSP when compiling android, without modifying the kernel. just a command in the fstab tells it to verify. the message in the boot loader is just to make sure you know it is unlocked.
dl200010 said:
dm verity is part of the kernel. it can be seen in the linux tree. the bootloader just has a message about being unlocked. i was able to disable dm verity in AOSP when compiling android, without modifying the kernel. just a command in the fstab tells it to verify. the message in the boot loader is just to make sure you know it is unlocked.
Click to expand...
Click to collapse
So a simple command can disable verity messages in this case? The others in the thread here were saying it's pretty much impossible.
H4X0R46 said:
So a simple command can disable verity messages in this case? The others in the thread here were saying it's pretty much impossible.
Click to expand...
Click to collapse
No. A simple command does not disable verity, but modifying boot does. The messages that you get about "possibly corrupt" are from the boot loader. If relocked, then it would go away.
It lamens terms it is saying "Hey i'm vulnerable! Read what you do before you flash that Galaxy S9 Rom on me!"
I honestly don't mind the message, and its only on screen for 3 seconds...I don't get the big deal.
And you can't compare phones....the Nexus 6 and Nexus 6P....are different phones....they use different everything and google is movong towards a more secure android experience so expect a plethora of corrupt this and broken that messages. Haha
I actually borked my friends Nexus 6 for a good 5 minutes a few months back because I didnt know you had to flash a modified boot and all we did was root it! But lesson learned and not one problem since!
But the message won't go away, it's to tell the next person you sell it to you did stuff to it. That's what she said.
Gytole said:
It lamens terms it is saying "Hey i'm vulnerable! Read what you do before you flash that Galaxy S9 Rom on me!"
I honestly don't mind the message, and its only on screen for 3 seconds...I don't get the big deal.
And you can't compare phones....the Nexus 6 and Nexus 6P....are different phones....they use different everything and google is movong towards a more secure android experience so expect a plethora of corrupt this and broken that messages. Haha
I actually borked my friends Nexus 6 for a good 5 minutes a few months back because I didnt know you had to flash a modified boot and all we did was root it! But lesson learned and not one problem since!
But the message won't go away, it's to tell the next person you sell it to you did stuff to it. That's what she said.
Click to expand...
Click to collapse
Yea, not so much comparing the phones, just using the Nexus 6 as an example. Yea the 6p is definitely different from the older Nexus models, and I remember someone saying something about an efuse thing you can trip and can't reverse, much like Samsung phones. How does this work? Is it like Samsung where it will always say it's been tampered with forever?
H4X0R46 said:
Yea, not so much comparing the phones, just using the Nexus 6 as an example. Yea the 6p is definitely different from the older Nexus models, and I remember someone saying something about an efuse thing you can trip and can't reverse, much like Samsung phones. How does this work? Is it like Samsung where it will always say it's been tampered with forever?
Click to expand...
Click to collapse
I guess I am very confused at why you're asking this...are you truing to figure out if the message means its corrupt? Because it more than likely isn't...it is just warning of possoble corruption you can has.
And you do lnow fuses can't be fixed once they're blown...you should have answered your own question haha
Gytole said:
I guess I am very confused at why you're asking this...are you truing to figure out if the message means its corrupt? Because it more than likely isn't...it is just warning of possoble corruption you can has.
And you do lnow fuses can't be fixed once they're blown...you should have answered your own question haha
Click to expand...
Click to collapse
Yea, the messages i know are just to let you know, the fuse is what i was wondering about. Kind of how the older Galaxy phones, the flash counter was able to be reset with the triangle away app and root, the nexus 6p is permanent? Yea, some noob questions, but it's because I own a shamu and never had to worry about any of this new stuff lol
H4X0R46 said:
Yea, the messages i know are just to let you know, the fuse is what i was wondering about. Kind of how the older Galaxy phones, the flash counter was able to be reset with the triangle away app and root, the nexus 6p is permanent? Yea, some noob questions, but it's because I own a shamu and never had to worry about any of this new stuff lol
Click to expand...
Click to collapse
No, the Nexus 6P is not permanent unlock. You can easily relock. There is no "unlock counter" or a "flash counter". I have mine unlocked the fuse I have read about elsewhere is still NOT blown. If you do call up google for support and you are unlocked, rooted, and/or custom ROM, then their first trouble shooting will be to download and flash the factory images. If the flashing of factory images does not fix your problem, then they will step up from there. Like replacing the phone. Unlike Samsung.
dl200010 said:
No, the Nexus 6P is not permanent unlock. You can easily relock. There is no "unlock counter" or a "flash counter". I have mine unlocked the fuse I have read about elsewhere is still NOT blown. If you do call up google for support and you are unlocked, rooted, and/or custom ROM, then their first trouble shooting will be to download and flash the factory images. If the flashing of factory images does not fix your problem, then they will step up from there. Like replacing the phone. Unlike Samsung.
Click to expand...
Click to collapse
Cool! So the Qfuse isn't even blown by installing custom files and unlocking the bootloader? I've read other places that people said you can never relock your bootloader, glad that's not true!
H4X0R46 said:
Cool! So the Qfuse isn't even blown by installing custom files and unlocking the bootloader? I've read other places that people said you can never relock your bootloader, glad that's not true!
Click to expand...
Click to collapse
I just used "fastboot flashing unlock", but I think if you use "unlock_critical" it might blow. I am not going to do this.
The "unlock_critical" allows you to flash a custom bootloader and radio. This may help if you want to flash a bootloader without the corrupt message, but it is only visible for a few seconds in booting. Flashing a custom bootloader is very risky. Not worth it for me. Bad bootloader flash or bad bootloader code and no fastboot after, thus no flashing stock bootloader.
Most will only need "unlock" to flash vendor, system, boot, and recovery.
dl200010 said:
I just used "fastboot flashing unlock", but I think if you use "unlock_critical" it might blow. I am not going to do this.
The "unlock_critical" allows you to flash a custom bootloader and radio. This may help if you want to flash a bootloader without the corrupt message, but it is only visible for a few seconds in booting. Flashing a custom bootloader is very risky. Not worth it for me. Bad bootloader flash or bad bootloader code and no fastboot after, thus no flashing stock bootloader.
Most will only need "unlock" to flash vendor, system, boot, and recovery.
Click to expand...
Click to collapse
So on the 6p, you need unlock_critical to flash the radio? Doesn't every factory image come with a new radio file? So you may have to blow the qfuse if you want the newest bootloader and radio file?
H4X0R46 said:
So on the 6p, you need unlock_critical to flash the radio? Doesn't every factory image come with a new radio file? So you may have to blow the qfuse if you want the newest bootloader and radio file?
Click to expand...
Click to collapse
He means "custom" (third-party/unsigned) ones. Official ones are okay.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
He means "custom" (third-party/unsigned) ones. Official ones are okay.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Click to expand...
Click to collapse
Same for stock radio? Yea, I wouldn't even risk flashing a custom Bootloader to anything! Not worth the consequences lol
H4X0R46 said:
Same for stock radio? Yea, I wouldn't even risk flashing a custom Bootloader to anything! Not worth the consequences lol
Click to expand...
Click to collapse
Same goes for the radio. I forgot to say that you can flash the factory ones no problem. They are signed.
dl200010 said:
Same goes for the radio. I forgot to say that you can flash the factory ones no problem. They are signed.
Click to expand...
Click to collapse
Thanks guys!
So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk
Before I get this phone. Does anyone on AT&T know if they white-listed this device for VoLTE?
Also, can we re-lock the bootloader like Nexus Devices or once the bootloader is unlocked it can never be re-locked again?
Thanks
mohan_kr said:
Before I get this phone. Does anyone on AT&T know if they white-listed this device for VoLTE?
Also, can we re-lock the bootloader like Nexus Devices or once the bootloader is unlocked it can never be re-locked again?
Thanks
Click to expand...
Click to collapse
You can relock the bootloader if you want to unroot and return to stock.
Read this thread https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877.
gee2012 said:
You can relock the bootloader if you want to unroot and return to stock.
Read this thread https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877.
Click to expand...
Click to collapse
Thanks I posted the question there..as I did not get a definitive answer. When I say relock, i want the behavior like the Nexus phones where it will do another wipe after the fastboot lock and fastboot mode shows correct lock status. Used to have one plus 1 and once unlocked you could never relock the bootloader..
mohan_kr said:
Before I get this phone. Does anyone on AT&T know if they white-listed this device for VoLTE?
Also, can we re-lock the bootloader like Nexus Devices or once the bootloader is unlocked it can never be re-locked again?
Thanks
Click to expand...
Click to collapse
AT&T only supports VoLTE on AT&T branded phones. So unfortunately, no.
Sent from my OnePlus 3T using XDA Labs
MrMeeseeks said:
AT&T only supports VoLTE on AT&T branded phones. So unfortunately, no.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
par for the course w/ that company. I think they have taken the mantle from Verizon as being the biggest jerks. If it wasn't for their iPhone business, they'd be sunk. They have done a fabulous job of raising the prices of all things DirecTV too. ugh.
I have unlock and rooted my phone at one point and returned everything to stock image two years ago. Recovery is the android recovery. The Nexus 6p had multiple OTA upgrades from Android 7 to 8.1.0 . Do I need to flash the factory image or can I just lock my bootloader via fastboot ?
I'm going to sell the phone and I was thinking of locking the bootloader before sending it out.
desilva79 said:
I have unlock and rooted my phone at one point and returned everything to stock image two years ago. Recovery is the android recovery. The Nexus 6p had multiple OTA upgrades from Android 7 to 8.1.0 . Do I need to flash the factory image or can I just lock my bootloader via fastboot ?
I'm going to sell the phone and I was thinking of locking the bootloader before sending it out.
Click to expand...
Click to collapse
You can lock the bootloader since you're using the stock rom. Please be sure to remove your email accounts from the phone prior to selling the device.
Factory Reset Protection will prevent any new buyers from using the device without inputting your email and password credentials to first sign into the device.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You can lock the bootloader since you're using the stock rom. Please be sure to remove your email accounts from the phone prior to selling the device.
Factory Reset Protection will prevent any new buyers from using the device without inputting your email and password credentials to first sign into the device.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Perfect ! So it doesnt matter that it's been updated multiple time (OTA) as long as it's stock rom ? Sorry I dont want to brick it prior to sending to the seller. Appreciate the respond !
desilva79 said:
Perfect ! So it doesnt matter that it's been updated multiple time (OTA) as long as it's stock rom ? Sorry I dont want to brick it prior to sending to the seller. Appreciate the respond !
Click to expand...
Click to collapse
Nah, not at all. You're welcome!
Sent from my Nexus 5X using Tapatalk