I just flashed latest Nougat and wiped my device. I am trying to find out how to re-lock BL. It seems that Fastboot oem lock doesn't work. Anyone know the function to use?
Ascertion said:
I just flashed latest Nougat and wiped my device. I am trying to find out how to re-lock BL. It seems that Fastboot oem lock doesn't work. Anyone know the function to use?
Click to expand...
Click to collapse
Don't do it...
Leave it unlocked... You're just inviting issues you can't fix...
Sent from my PH-1 using Tapatalk
rignfool said:
Don't do it...
Leave it unlocked... You're just inviting issues you can't fix...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I am trying to sell it. If I leave bootloader unlocked, it may deter buyers. Are you saying relocking bootloader when it's 100% stock doesn't work? Why?
Ascertion said:
I am trying to sell it. If I leave bootloader unlocked, it may deter buyers. Are you saying relocking bootloader when it's 100% stock doesn't work? Why?
Click to expand...
Click to collapse
If you are truly 100% stock... Then sure... Lock away...
I'm not going to spell it out... For fear of the stupid...
But substitute 'flashing' for 'oem'...
Sent from my PH-1 using Tapatalk
rignfool said:
If you are truly 100% stock... Then sure... Lock away...
I'm not going to spell it out... For fear of the stupid...
But substitute 'flashing' for 'oem'...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
thanks very much. This worked and device is not bricked! :good:
Ascertion said:
thanks very much. This worked and device is not bricked! :good:
Click to expand...
Click to collapse
If you just flashed Oreo, then it is beta.
Typically you don't lock the boot loader with beta software running.
If something goes wrong, and it can, you potentially won't be able to flash a downgrade.
I understand your reasoning, but it's normally a bad idea.
Although, essential doesn't instruct you to unlock the bootloader to install the Oreo beta builds.
I side loaded mine through the stock recovery and only unlocked a few weeks afterwards.
tech_head said:
If you just flashed Oreo, then it is beta.
Typically you don't lock the boot loader with beta software running.
If something goes wrong, and it can, you potentially won't be able to flash a downgrade.
I understand your reasoning, but it's normally a bad idea.
Click to expand...
Click to collapse
It's all good. I restored to Nougat before I re-locked. :good:
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.
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
I have a major problem, I need to know if it will be possible to flash a custom rom on a nexus 6p. It seems that it will be hard because of that new bootloader.
smilehead said:
I have a major problem, I need to know if it will be possible to flash a custom rom on a nexus 6p. It seems that it will be hard because of that new bootloader.
Click to expand...
Click to collapse
What do you mean? Any bootloader version on this device can be unlocked.
Heisenberg said:
What do you mean? Any bootloader version on this device can be unlocked.
Click to expand...
Click to collapse
Sorry, I'm new to this stuff. I thought they can change the bootloader when you upgrade. Thanks for the help though
smilehead said:
Sorry, I'm new to this stuff. I thought they can change the bootloader when you upgrade. Thanks for the help though
Click to expand...
Click to collapse
The bootloader does get updated. But you can unlock any bootloader, and updating it doesn't lock it again. Take a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Oh, because i was afraid of the phone won't boot because of the android n won't boot if the phone has a unlocked bootloader.
smilehead said:
Oh, because i was afraid of the phone won't boot because of the android n won't boot if the phone has a unlocked bootloader.
Click to expand...
Click to collapse
Nope, nothing like that to worry about. The locked/unlocked status won't stop it from booting.
Thanks. I can now upgrade in peace
Is there a way to Lock the bootloader
Xniperf said:
Is there a way to Lock the bootloader
Click to expand...
Click to collapse
No
Sent from my ASUS_Z00L using XDA Labs
bdwilk said:
No
Click to expand...
Click to collapse
There is, theorically. Sziraqui was talking about it in his unofficial bootloader unlocking method.
And Xniperf, there is a theory that ASUS tracks if device was unlocked by serial number, so, unless you haven't used an app from ASUS, relocking your bootloader won't help you to recover your warranty.
Sent from my ASUS_Z00UD using XDA Labs
darkeyes22 said:
There is, theorically. Sziraqui was talking about it in his unofficial bootloader unlocking method.
And Xniperf, there is a theory that ASUS tracks if device was unlocked by serial number, so, unless you haven't used an app from ASUS, relocking your bootloader won't help you to recover your warranty.
Sent from my ASUS_Z00UD using XDA Labs
Click to expand...
Click to collapse
Do you have any links regarding his works? I havent receive any OTA Updates since I unlocked by bootloader.
thirdfury said:
Do you have any links regarding his works? I havent receive any OTA Updates since I unlocked by bootloader.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
As I said, it's only possible in theory, no one hasn't dumped locked bootloaders yet
Sent from my ASUS_Z00UD using XDA Labs
darkeyes22 said:
https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
As I said, it's only possible in theory, no one hasn't dumped locked bootloaders yet
Sent from my ASUS_Z00UD using XDA Labs
Click to expand...
Click to collapse
tried his work but stucked at boot logo. also tried flashing it with stock recovery but gives a bootloop. Thanks anyway.
Xniperf said:
Is there a way to Lock the bootloader
Click to expand...
Click to collapse
Uh, yes, and I found out by the worst way possible. Since everyone was saying that re-locking the bootloader was impossible, I had the great idea to go to fastboot and type in "fastboot oem lock".
What happened you ask? The bootloader was locked... I had some trouble unlocking it again.
DarkAlpha.Sete said:
Uh, yes, and I found out by the worst way possible. Since everyone was saying that re-locking the bootloader was impossible, I had the great idea to go to fastboot and type in "fastboot oem lock".
What happened you ask? The bootloader was locked... I had some trouble unlocking it again.
Click to expand...
Click to collapse
Yes the right way is flashing stock ROM from adb and with this type that command "fastboot oem lock"
I am set to unlock the bootloader after permanently unlocking this phone. I am worried of the warrning that they talk about concerning the warranty. Is there a way to lock the bootloader up before sending it off for warranty to T-Mobile?
You know you can just restore the phone back to stock, and relock the bootloader right?
OhioYJ said:
You know you can just restore the phone back to stock, and relock the bootloader right?
Click to expand...
Click to collapse
And T-Mobile will never know?
OhioYJ said:
You know you can just restore the phone back to stock, and relock the bootloader right?
Click to expand...
Click to collapse
Also if I flash the international version on my T-Mobile phone, will I be able to flash the T-Mobile version back?
IllyaK said:
And T-Mobile will never know?
Click to expand...
Click to collapse
No, they will never know. I sent phones in that had root, fastbooted all the original firmware and they were fixed and returned to me. Now if you were talking Samsung, that's a different story.
ggrant3876 said:
No, they will never know. I sent phones in that had root, fastbooted all the original firmware and they were fixed and returned to me. Now if you were talking Samsung, that's a different story.
Click to expand...
Click to collapse
Also, is there a way to skip the 7 day wait for the email from OnePlus to be able to unlock the bootloader?
IllyaK said:
Also, is there a way to skip the 7 day wait for the email from OnePlus to be able to unlock the bootloader?
Click to expand...
Click to collapse
That's a no on this
IllyaK said:
Also, is there a way to skip the 7 day wait for the email from OnePlus to be able to unlock the bootloader?
Click to expand...
Click to collapse
I didn't but the T-Mobile version so I wouldn't have to wait on anything.