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!
Related
Ok, My Nexus 4 NOT LOCK BOOTLOADER after update for Kitkat, and no lock in any Stock and Customs ROMS !
just stays on: "LOCK-STATE: unlocked"
The commando line fastboot oem lock not work :crying:
help me I'm desperate
Help pls ... how to lock my device ? .-.
Well first of all, why would you like to re-lock your bootloader?
mumaster20 said:
Well first of all, why would you like to re-lock your bootloader?
Click to expand...
Click to collapse
my friend said that the OTA updates require locked bootloader, then I would like to lock it again ...
and how this under warranty, also wanted to make everything from factory
Your friend is wrong. You don't need locked bootloader to get OTA.
To get OTA update, you need stock rom and stock recovery, locked or unlocked doesn't matter.
You can also flash the factory stock image without wiping your data (see link in my signature).
If you have root you can use this app to lock and unlock your bootloader: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
eksasol said:
Your friend is wrong. You don't need locked bootloader to get OTA.
To get OTA update, you need stock rom and stock recovery, locked or unlocked doesn't matter.
You can also flash the factory stock image without wiping your data (see link in my signature).
If you have root you can use this app to lock and unlock your bootloader: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Yes, i understand .... so, my bootloader not lock with the app BootUnlocker, or command line, i tested all methods and nothing :crying:
AndreyVilella said:
Yes, i understand .... so, my bootloader not lock with the app BootUnlocker, or command line, i tested all methods and nothing :crying:
Click to expand...
Click to collapse
I guess something is up with your phone physical memory, but it doesn't matter, it really should not affect your warrenty (but the custom rom and recoveries will). Makes zero different to OTA updates either.
eksasol said:
I guess something is up with your phone physical memory, but it doesn't matter, it really should not affect your warrenty (but the custom rom and recoveries will). Makes zero different to OTA updates either.
Click to expand...
Click to collapse
Ok, thanks, then I can rest easy while the warranty? I just be with a recovery image and also manufactures and without Root?
AndreyVilella said:
Ok, thanks, then I can rest easy while the warranty? I just be with a recovery image and also manufactures and without Root?
Click to expand...
Click to collapse
Honestly, I don't think they care if you have root either, but that's base on other user feedbacks. It seems LG warrenty is picky about other things and not very good from the feedbacks from what I read actually, but I haven't had first hand experience. But people have sent in rooted devices for repair.
I think just have factory image and stock recovery and stock kernel.
Solution !
eksasol said:
Honestly, I don't think they care if you have root either, but that's base on other user feedbacks. It seems LG warrenty is picky about other things and not very good from the feedbacks from what I read actually, but I haven't had first hand experience. But people have sent in rooted devices for repair.
I think just have factory image and stock recovery and stock kernel.
Click to expand...
Click to collapse
Ok, Thanks ! I will continue in Stock image with bootloader Unlocked ...
Exactly like the thread i started for the Shield Tablet, ill be uploading a lot of videos in this thread explaining how to unlock the bootloader, Root the Device and Install Custom Recovery
I'll make sure to test all the ROMs released for the device and upload videos running them to this thread.
Guides / Tutorials (Step by Step)
How to Unlock the Bootloader
How to Root
How to install TWRP/Custom Recovery
Nexus 9 Overclocked results
-------------------------------------------------------------
Videos running different custom ROMs
Ill be testing video, sound, webbrowsing, maps, play store and custom setting(if the rom provides them)
AICP
Candy5
CyanogenMod 12
Dirty Unicorns
Flounder Pure AOSP
LiquidSmoot
Lollipopalooza
Paranoid Android
RASTAPOP
Resurrection Remix
SimpleAOSP
SlimLP
Temasek
--------------------------------------------------------------
You put shield tablet in the thread title....
Sent from my OtterX using Tapatalk
Great looking forward to seeing some videos.
Just got information that my pre-order is delayed to Nov 15 = (
I promise to upload the videos asap when i get my device
EverythingPortable said:
Just got information that my pre-order is delayed to Nov 15 = (
I promise to upload the videos asap when i get my device
Click to expand...
Click to collapse
from who?
USBhost said:
from who?
Click to expand...
Click to collapse
From a local store here in gothenburg. I should have ordered from google
EverythingPortable said:
From a local store here in gothenburg. I should have ordered from google
Click to expand...
Click to collapse
Cool Nexus 9 my next tablet
I just got my 9 today. fastboot oem unlock right out of the box. BRING ON THE REST!!! w00t!!!
I want to point out that in the developer settings there is a tic box for "Enable OEM Unlock" that needs to be checked before you can run the command.
benniebeeker said:
I just got my 9 today. fastboot oem unlock right out of the box. BRING ON THE REST!!! w00t!!!
I want to point out that in the developer settings there is a tic box for "Enable OEM Unlock" that needs to be checked before you can run the command.
Click to expand...
Click to collapse
Getting mine today as well. I've always OEM unlocked immediately and rooted used SuperSU on all my Nexus devices. However, on the latest L Preview for Nexus 5 and 7 Chainfire said you had to install a custom kernel to obtain root due to SELinux changes. Since I'm loathe to run a custom kernel on a new chipset I'm thinking of staying locked for the foreseeable future. Frankly ruins the Android "make it your own" ethos I've ALWAYS valued, but I just ain't gonna put up with tons of growing pains while all this is worked out.....
BillLee3 said:
Getting mine today as well. I've always OEM unlocked immediately and rooted used SuperSU on all my Nexus devices. However, on the latest L Preview for Nexus 5 and 7 Chainfire said you had to install a custom kernel to obtain root due to SELinux changes. Since I'm loathe to run a custom kernel on a new chipset I'm thinking of staying locked for the foreseeable future. Frankly ruins the Android "make it your own" ethos I've ALWAYS valued, but I just ain't gonna put up with tons of growing pains while all this is worked out.....
Click to expand...
Click to collapse
You should just unlock the bootloader out of the box anyway. Will save you much headache down the road when you decide to do it and already have a bunch of data on your device.
Brian706 said:
You should just unlock the bootloader out of the box anyway. Will save you much headache down the road when you decide to do it and already have a bunch of data on your device.
Click to expand...
Click to collapse
This. I always unlock first thing if I have any intentions on doing it at all. Simply because I don't want to lose my data later on. Unlocking is easy and took me 2 minutes on my nexus 9. No reason not to.
Sent from my G3
jreyno10 said:
Unlocking is easy and took me 2 minutes on my nexus 9. No reason not to.
Click to expand...
Click to collapse
"No reason not to" meaning Google doesn't invalidate warranty merely by unlocking, right ?
Nexus were made to be unlocked.
mikereidis said:
"No reason not to" meaning Google doesn't invalidate warranty merely by unlocking, right ?
Nexus were made to be unlocked.
Click to expand...
Click to collapse
+1 there
Oh, that's good to know! This is my first Nexus device.
So, unlocking does not void the warranty in any way?
Scotlac said:
Oh, that's good to know! This is my first Nexus device.
So, unlocking does not void the warranty in any way?
Click to expand...
Click to collapse
Discussing that here: http://forum.xda-developers.com/nexus-9/help/unlocking-bootloader-rooting-n9-void-t2931784
By from HTC and warranty may be affected.
By from Play, and I think warranty is OK.
I'm considering returning mine since I'm underwhelmed for $400, and I'll just relock it and return to stock first.
mikereidis said:
Discussing that here: http://forum.xda-developers.com/nexus-9/help/unlocking-bootloader-rooting-n9-void-t2931784
By from HTC and warranty may be affected.
By from Play, and I think warranty is OK.
I'm considering returning mine since I'm underwhelmed for $400, and I'll just relock it and return to stock first.
Click to expand...
Click to collapse
I think regarding HTC, it depends on what's affected. I don't think that they will deny you a hardware warranty just because you unlocked the bootloader and/or rooted. Unlocking the bootloader is a safe process sanctioned by HTC themselves. Well, on HTC devices anyway. Nexus won't require HTCdev unlock.
They really can't even tell that you rooted or what you've done if you return to stock. All they know is that you unlocked the bootloader at some point. If the phone legitimately malfunctions, they won't deny you a repair/replacement just because you unlocked.
The first videos are now uploaded, hope you enjoy them. Everytime a new cusom rom is released ill upload a videos running the rom. Ill be testing video, sound, webbrowsing, maps, play store and custom setting(if the rom provides them)
Where can I download the script in the videos please?
albsat said:
Where can I download the script in the videos please?
Click to expand...
Click to collapse
Not sure i understand, what script?
EverythingPortable said:
Not sure i understand, what script?
Click to expand...
Click to collapse
There is a bat script in the videos, for bootloader unlock and root install. Where can I download it?
"There's an internal problem with your device. Contact your manufacturer for details
I got this message, I cannot view my files on my computer. I flashed the latest factory image and did a factory reset, flashed the vendor file, but no luck. What else could it be? Drivers?
an internal problem. have you tried reaching out for warranty support?
Already unlocked Bootloader.
640k said:
an internal problem. have you tried reaching out for warranty support?
Click to expand...
Click to collapse
I'm sure since I unlocked my bootloader it wouldn't do me any good, right?
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
09eric09 said:
I'm sure since I unlocked my bootloader it wouldn't do me any good, right?
Click to expand...
Click to collapse
unlocked bootloader does not void your warranty, this has been confirmed by google's csr
dipole said:
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
Click to expand...
Click to collapse
No.
dipole said:
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
Click to expand...
Click to collapse
your advice fixed the problem on my nexus 6p.. thank you
It fixed my problem on Nexus 6p after rooting to Cataclysm
Thanks!!
toenail78 said:
your advice fixed the problem on my nexus 6p.. thank you
Click to expand...
Click to collapse
09eric09 said:
No.
Click to expand...
Click to collapse
dipole said:
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
Click to expand...
Click to collapse
yangqi said:
unlocked bootloader does not void your warranty, this has been confirmed by google's csr
Click to expand...
Click to collapse
superchan08 said:
Thanks!!
Click to expand...
Click to collapse
Hi Guys,
Anyone successfully got rid of this? i've been running Catacalysm with elementalx with no issues. But suddenly i wanted to try layers and one of the layer i tried made me to loop at colorful dots screen that turn into android. But it never turned to android and didn't boot.
i tried to restore nandroid, flash catacalysm again etc., but nothing worked. Finally i had to flash all the factory image (from bootloader to vendor) again. then restored the latest data nandroid. i had my finger print set and following http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 i removed locksettings.db file to successfully get in the system.
however, on every restart i get this error message that my phone has an internal problem and manufacturer to be contacted. I am afraid to flash the nexus 9 fix, as someone reported that its spoiling his touch screen.
Try flashing the vendor img only in fastboot and see if that removes the error message.
steviemch said:
Try flashing the vendor img only in fastboot and see if that removes the error message.
Click to expand...
Click to collapse
Thanks! Easy fix!
Flashing the vendor img didn't work for me.
Is there any other way to do it or do I have to wipe it all and start over?
So, I see that it's based on the build number MMB29X but that's a Nexus 6 build. I have a Nexus 5x. If I flash that vendor image, will it work or mess things up? I've never had to do that before so I'm sort of lost... I'm positive that I downloaded the right build from the CM site. Thanks in advance for the help.
erichjelm said:
Flashing the vendor img didn't work for me.
Is there any other way to do it or do I have to wipe it all and start over?
So, I see that it's based on the build number MMB29X but that's a Nexus 6 build. I have a Nexus 5x. If I flash that vendor image, will it work or mess things up? I've never had to do that before so I'm sort of lost... I'm positive that I downloaded the right build from the CM site. Thanks in advance for the help.
Click to expand...
Click to collapse
Do not flash that nexus 6 image!! Do not flash or install any zip or image that is not expressly for your phone!!
This is the forum for the Nexus 6p. You will have better luck finding the answer to you question somewhere here (Nexus 5x forum). If you have installed an image or zip of any type from anywhere other than that forum (or official google downloads) you are probably going to have a bad day. Good luck.
I didn't even notice.
I'm sorry.
Just opened a Google search link.
Sorry!
erichjelm said:
I didn't even notice.
I'm sorry.
Just opened a Google search link.
Sorry!
Click to expand...
Click to collapse
No worries, mate! I have found solutions to problems in forums that were not for my phone. Just pay attention to where you post you questions. The fact that you are using google first puts you years ahead of some people I've seen posting. Definitely no reason to apologize twice. :highfive:
Found the fix in the form of a ZIP in Nexus 9 forum.
Ha.
Thanks, again!
Can anybody verify that this works for the 6p before I flash a zip and Jack my phone up any further? Lol
How do I find the right vendor img for my nexus 6p?
mrjoeyloke said:
How do I find the right vendor img for my nexus 6p?
Click to expand...
Click to collapse
With a file browser, head to /System/build.prop and look for this line "ro.build.description" and your system software should be listed after the Android version. I believe this is also listed in Settings/About Phone. You can view which Vendor you have installed in /Vendor/build.prop. Make sure both match up each month when you update.
Sent from my Nexus 5X using Tapatalk
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
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Unless you are on the totally stock system then I wouldn't lock your bootloader.
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
mrcooter said:
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
Click to expand...
Click to collapse
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
If you relock your bootloader with anything other than a factory image you will brick your device.
vjyrdy said:
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
Click to expand...
Click to collapse
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
mrcooter said:
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
Click to expand...
Click to collapse
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
zlost1 said:
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
Click to expand...
Click to collapse
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Sent from my PH-1 using XDA Labs
swiftbones74 said:
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Click to expand...
Click to collapse
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
zlost1 said:
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
Click to expand...
Click to collapse
This ain't the rocket and thread forum or the whatever dumb other thing forum so it really doesn't matter what the answer is.
Sent from my PH-1 using XDA Labs
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
zlost1 said:
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
Click to expand...
Click to collapse
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
MOD EDIT
You are one trippy person ? if you really feel the need to post about your LG phone in the mata thread go right ahead buddy.
Sent from my PH-1 using XDA Labs
MOD EDIT
It's worth noting that the Essential PH-1 uses an A/B partition system so any advice given here would not be helpful in the slightest for devices that don't have the same file system. Quickly doing a search of your phone reveals it's not an A/B partitioned system so following advice here could potentially lead to you actually destroying your phone.
could you lock the BL once rooted if in fastboot mode it lists device tampering = false?
Wonderful reply
tech_head said:
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
Click to expand...
Click to collapse
Thanks, this reply should be pinned to the top of the thread. It is crucial information for our dear noobies
swiftbones74 said:
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
Click to expand...
Click to collapse
Just an opinion, but...there are rules for posting in forums that Dev's, no matter how over worked and underpaid/appreciated should follow as well. Teach by example not proxy. Applaud the calm gentleman who responded with eloquent grammar and poise.
NaterTots said:
Unless you are on the totally stock system then I wouldn't lock your bootloader.
Click to expand...
Click to collapse
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
rossrosh007 said:
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
Click to expand...
Click to collapse
I don't know.