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
Related
So I did the root keeper wrong and updated, losing root. Anyone else in this club with me? It's only been a few hours and I already miss it.
Atleast I have better pictures though....
Sent from my XT1058 using xda app-developers app
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Abyssul said:
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Click to expand...
Click to collapse
This process is just flashing the firmware through rsdlite which won't happen because it's a downgrade. I tried.
Sent from my XT1058 using xda app-developers app
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
freak4dell said:
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
Click to expand...
Click to collapse
just tried, did not work. fails at the boot.img
Abyssul said:
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
Click to expand...
Click to collapse
first things I tried and doesn't work
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Some of us didn't want root in the first place! #TeamStockMotoX :silly:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Because some of us can't unlock our bootloader.
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Just remember that Retail AT&T and Verizon and MotoMaker AT&T variants aren't able to have their boot loaders unlocked
Sent from my XT1058 using Tapatalk 4
Lost root don't care. Motorola got this phone right. I'm good with stock.
rivlez said:
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
emerica243 said:
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
Click to expand...
Click to collapse
My wifi was messed up in any mode. It wouldn't turn on for some reason. I restored the 17.51 firmware after the botched update messed up my wifi and it worked fine and I actually ended up doing it 2 times since a titanium backup messed up my phone. I was definitely on the 17.54 update. It definitely let me downgrade. How would you like me to prove it to you?
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
sravanz said:
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
Click to expand...
Click to collapse
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Rask40 said:
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Click to expand...
Click to collapse
Me too. My wifi is FUBARED in recovery. It's because we don't have the new kernel and to be technical were using the old system/recovery in our "recovery mode" I think that's why it's working in the regular mode and not recovery mode..... Or that's what I understand. Though I'm probably wrong.
When I upgraded I got a failed upgrade after final boot. Although it still says the newest version. I'm tempted to RSD back like some others have just to try but I don't want a paper weight.
Sent from non rooted motoX :'(
gunnyman said:
Lost root don't care. Motorola got this phone right. I'm good with stock.
Click to expand...
Click to collapse
While I'm kind of excited to see SafeStrap out, and updated (fixes phone/data, etc...), I'm still hoping some attempt is in the works for unlock on at&t.
Regardless, there aren't any custom roms to really flash anyways.
Had I an unlocked bootloader, I'd have a custom kernel in the works, and maybe some custom roms with some TeamAcid love.
Come see, come saw... Patience wins all.
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 ...
On the official google page. I'm a newbie and can't do outside links.
https://developers.google.com/android/nexus/images
Only WiFi out so far it seems..
Am I blind, or did the Google Now launcher disappear? (I set up as new device, as I have both WiFi and LTE, and couldn't see which were which) I thought you just start Google Now and choose to use as launcher (so I can swipe from left to access Now) Someone please remind me?
Otherwise seem smooth (based on all of 5 mins usage. Used latest preview before)
Bah! I had to install Google Now Launcher...
oyoy said:
Only WiFi out so far it seems..
Am I blind, or did the Google Now launcher disappear? (I set up as new device, as I have both WiFi and LTE, and couldn't see which were which) I thought you just start Google Now and choose to use as launcher (so I can swipe from left to access Now) Someone please remind me?
Otherwise seem smooth (based on all of 5 mins usage. Used latest preview before)
Bah! I had to install Google Now Launcher...
Click to expand...
Click to collapse
I guess they chose to have users install the Launcher from the Play Store. I was scratching my head for a minute also.
I've just flashed the stock factory image, word of warning... It took me 10 minutes for it to boot so be patient!
topgeardave said:
I've just flashed the stock factory image, word of warning... It took me 10 minutes for it to boot so be patient!
Click to expand...
Click to collapse
Booting it now, glad someone said something, was wondering what was taking so long.
Mine has taken at least 20 minutes at the initial boot (spinning colors) screen. Anyone else taking very long?
Help!
On wugfresh when i enter the md5, it says mismatch, how do i fix this? Can you post the hash here? I tried the one for razor several times but to no avail.
JeremyNSL said:
Mine has taken at least 20 minutes at the initial boot (spinning colors) screen. Anyone else taking very long?
Click to expand...
Click to collapse
It's normal just wait it out.
i haven't been following my N7 at all since i got the Tab S, but is there root out for 5.0 on this thing yet? i thought i remembred seeing it somewhere ..
Does flashing a factory image relock bootloader and lose root?
Sent from my Nexus 7 2013 using XDA Free mobile app
BrickMeNot said:
On wugfresh when i enter the md5, it says mismatch, how do i fix this? Can you post the hash here? I tried the one for razor several times but to no avail.
Click to expand...
Click to collapse
Same here, searching and can't find anything.
jayochs said:
i haven't been following my N7 at all since i got the Tab S, but is there root out for 5.0 on this thing yet? i thought i remembred seeing it somewhere ..
Click to expand...
Click to collapse
I'm running Scott's build and it has root so yeah it's doable, just don't know how to do it on the factory image.
Root
Is there a stable way to root the official factory image of lolipop? Can I just flash something in recovery like the past? I am not sure what the word is on rooting now that the official images are out.
gleggie said:
Does flashing a factory image relock bootloader and lose root?
Sent from my Nexus 7 2013 using XDA Free mobile app
Click to expand...
Click to collapse
No and yes. You need it unlocked to install the image and they recommend locking it when done but you're not going to want to. It returns it to stock Lollipop so no root.
SuperSU 2.19 beta is working fine for me.
Gesendet von meinem Nexus 7 mit Tapatalk
Can anyone confirm if double tap to wake is working?
gleggie said:
Does flashing a factory image relock bootloader and lose root?
Sent from my Nexus 7 2013 using XDA Free mobile app
Click to expand...
Click to collapse
Correct me if I am wrong but I am pretty sure it won't relock bootloader but it will lose root.
iaguilera14 said:
Correct me if I am wrong but I am pretty sure it won't relock bootloader but it will lose root.
Click to expand...
Click to collapse
Correct mate
mjones73 said:
Can anyone confirm if double tap to wake is working?
Click to expand...
Click to collapse
Nope, its an N6/N9 feature only
gleggie said:
Does flashing a factory image relock bootloader and lose root?
Click to expand...
Click to collapse
You lose root and recovery but your tablet doesn't relock
Thanks for all the quick replies, i'll flash the latest SuperSU after I flash the ROM
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!
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.