I want to update everything except leave the bootloader on 7.1. Will this work?
LoliSmith said:
I want to update everything except leave the bootloader on 7.1. Will this work?
Click to expand...
Click to collapse
Why would you leave the 7.1 bootloader? As long as you're unlocked, you can flash the whole factory image...
Cheers...
5.1 said:
Why would you leave the 7.1 bootloader? .
Click to expand...
Click to collapse
Because Verizon. I want to be able to relock but not lose the ability to unlock again.
LoliSmith said:
Because Verizon. I want to be able to relock but not lose the ability to unlock again.
Click to expand...
Click to collapse
You should do some reading. It doesn't work like that. If you ever lock your bootloader you will never be able to unlock it again. No reason to lock it anyways.
aholeinthewor1d said:
It doesn't work like that. If you ever lock your bootloader you will never be able to unlock it again. No reason to lock it anyways.
Click to expand...
Click to collapse
I don't think you are correct. If you leave the bootloader on 7.1, you should be able to unlock it again using depixel8.
Where has anyone done what I am proposing to do - upgrade everything but the bootloader to 7.1.1 and leave the bootloader on 7.1? No one has done it. So no one knows.
im pretty sure you have to manually relock the bootloader,so updating to 7.1.1 shouldn't matter.
They cant relock your bootloader through software is what i was told by depilxel 8 developer.
I am updating to 7.1.1 right now just to get back to factory state need google support.
cant be reached on most custom roms.
No current stock rooted roms exist,so fresh start is needed.
LoliSmith said:
Because Verizon. I want to be able to relock but not lose the ability to unlock again.
Click to expand...
Click to collapse
As soon as you update to 7.1.1 and you are locked, you will not be able to unlock again with depixel8. I don't care if you have a bootloader from 2 years ago. You probably should decide once and for all if you want the device secure and locked or unlocked. Otherwise at some point you will be in a pickle.
Sent from my Pixel using XDA-Developers Legacy app
There's always a way to find out. Let us know how it goes.
You should not be locking you're bootloader if it's not necessary. And depixel8 pushes stuff to system in order to enable allow oem unlocking. These things may not work on newer systems regardless of the bootloader version.
LoliSmith said:
I don't think you are correct. If you leave the bootloader on 7.1, you should be able to unlock it again using depixel8.
Where has anyone done what I am proposing to do - upgrade everything but the bootloader to 7.1.1 and leave the bootloader on 7.1? No one has done it. So no one knows.
Click to expand...
Click to collapse
Your OP implies you can update everything else except the bootloader leaving you free to lock and unlock whenever you want which is 100% not true. There are new threads about this every week all the info is there. If you are on 7.1 you can unlock with dePixel8. Yea technically you could relock and unlock again ONLY while on 7.1 but there is 0 reason to. If you aren't 100% stock when locking you are going to have issues. Also if you're phone installs an OTA while you have the bootloader locked then you are 100% screwed and won't be able to unlock again. Either unlock it and never lock it again or don't bother. You're making something very simple overly complicated.
bobby janow said:
As soon as you update to 7.1.1 and you are locked, you will not be able to unlock again with depixel8.
Click to expand...
Click to collapse
Has anyone done this without updating the bootloader or are you just speculating?
bobby janow said:
I don't care if you have a bootloader from 2 years ago.
Click to expand...
Click to collapse
What are you basing this on? Has anyone every updated everything except the bootloader and then relocked or are you just speculating?
LoliSmith said:
Has anyone done this without updating the bootloader or are you just speculating?
/QUOTE]
Nope, we are all waiting for you to tell us how it goes.
Click to expand...
Click to collapse
aholeinthewor1d said:
Your OP implies you can update everything else except the bootloader leaving you free to lock and unlock whenever you want which is 100% not true. There are new threads about this every week all the info is there. .
Click to expand...
Click to collapse
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
aholeinthewor1d said:
Also if you're phone installs an OTA while you have the bootloader locked .
Click to expand...
Click to collapse
I never take OTAs so that isn't an issue for me.
LoliSmith said:
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
I never take OTAs so that isn't an issue for me.
Click to expand...
Click to collapse
You can't.. it doesn't work like that. Go ahead and try if you want. There are countless threads about the bootloader. With all the knowledgeable​ people here do you think they somehow just overlooked something so simple? There are 5 bootloaders total actually. Once you install 7.1.1 you will not be able to unlock again. Multiple people have told you this but you seem to not believe anyone so go ahead and prove us wrong.
aholeinthewor1d said:
You can't.. it doesn't work like that..
Click to expand...
Click to collapse
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
It's a simple question. Either people have actually done this before, or you are just speculating.
aholeinthewor1d said:
There are countless threads about the bootloader. .
Click to expand...
Click to collapse
But has anyone updated everything but left the bootloader on 7.1?
aholeinthewor1d said:
Once you install 7.1.1 you will not be able to unlock again.
Click to expand...
Click to collapse
Again, there is a difference between updating everything to 7.1.1 and updating everything except the bootloader. Huge difference.
LoliSmith said:
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
It's a simple question. Either people have actually done this before, or you are just speculating.
But has anyone updated everything but left the bootloader on 7.1?
Click to expand...
Click to collapse
Again. You can't.
aholeinthewor1d said:
Again. You can't.
Click to expand...
Click to collapse
You've tried? Anyone else has tried?
So are you saying if I leave the bootloader on 7.1 and update everything else the phone won't work?
LoliSmith said:
You've tried? Anyone else has tried?
So are you saying if I leave the bootloader on 7.1 and update everything else the phone won't work?
Click to expand...
Click to collapse
There is more than one bootloader which is what you are not understanding. There are 5. No one is certain exactly what 7.1.1 changed but if you flash any part of it (not just the bootloader) then you won't be able to unlock again.
aholeinthewor1d said:
There is more than one bootloader which is what you are not understanding.
Click to expand...
Click to collapse
Why does that make a difference?
I am on the original bootloader, never updated anything.
Related
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Fastboot flashing lock? Or oem lock?
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
Fastboot flashing lock? Or oem lock?
Click to expand...
Click to collapse
It's that simple? Just run the fast lock command?
shibbnasty said:
It's that simple? Just run the fast lock command?
Click to expand...
Click to collapse
I think lol it's been awhile since I locked a phone
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
I think lol it's been awhile since I locked a phone
Click to expand...
Click to collapse
I guess I should have mentioned as well it's a Verizon pixel xl and I had to use depixel8 to unlock it
shibbnasty said:
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Click to expand...
Click to collapse
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
lyall29 said:
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
Click to expand...
Click to collapse
All I have done is unlock it. I have not flashed any kernels or mods or anything.
shibbnasty said:
All I have done is unlock it. I have not flashed any kernels or mods or anything.
Click to expand...
Click to collapse
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
lyall29 said:
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
Click to expand...
Click to collapse
Thank you very much!
@shibbnasty. Actually, relocking the bootloader may not wipe data. I can't remember. Let me know if it does or not.
Yes it does.
Rank N00b here... just getting that out of the way.
Device: Verizon Pixel XL
Build: NDE63X
Bootloader: unlocked via dePixel8 (done after Nov update)
So the phone is stock and I'm not really keen on modding right now. I don't want to use a alpha build of TWRP and SuperSU seems to be in flux too. These aren't criticisms by the way; I realize this a very new handset and those kinds of tools take time to develop. Nothing happens overnight.
So, anyway, my phone is currently unlocked and I'm wondering if I'm not better off relocking it? As a stock unit, it should still get OTA's, right? Like I said, total n00b here...
@loaba,
There's absolutely no reason to relock your bootloader, unless you are annoyed by the Google bootloader unlock warning during boot, or if you are planning on returning it or selling it. Otherwise, leave it unlocked. Gives you much greater flexibility to recover if something goes wrong.
@cam30era,
Thanks for the reassurance.
loaba said:
@cam30era,
Thanks for the reassurance.
Click to expand...
Click to collapse
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
michaelbsheldon said:
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
Click to expand...
Click to collapse
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
loaba said:
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
Click to expand...
Click to collapse
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
michaelbsheldon said:
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
Click to expand...
Click to collapse
About the OTA's - that was my big concern for now. Cool.
OP - thread derailed... sorry, man.
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Khanusma said:
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Click to expand...
Click to collapse
Most of the custom kernels fix that. Root is the hard one to hide.
Anyone know if it's possible to downgrade from 7.1.1 so I can run depixel8 and unlock the bootloader?
ashish8 said:
Anyone know if it's possible to downgrade from 7.1.1 so I can run depixel8 and unlock the bootloader?
Click to expand...
Click to collapse
I'm not Verizon but I have some experience and can tell you 100% no doubt that you're stuck if you're on the latest update from Verizon and do not have an unlocked bootloader.
There is no way to go back just to unlock the bootloader.
Sorry.
@CZ Eddie is right. No way to go back with a locked bootloader on a VZW phone running 7.1.1.
CZ Eddie said:
I'm not Verizon but I have some experience and can tell you 100% no doubt that you're stuck if you're on the latest update from Verizon and do not have an unlocked bootloader.
There is no way to go back just to unlock the bootloader.
Sorry.
Click to expand...
Click to collapse
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL
grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Click to expand...
Click to collapse
I'll defer this question to the more Verizon knowledgeable.
My suspicion is you're good to go but I'm only 70% sure about that.
CZ Eddie said:
I'll defer this question to the more Verizon knowledgeable.
My suspicion is you're good to go but I'm only 70% sure about that.
Click to expand...
Click to collapse
grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL
Click to expand...
Click to collapse
It will not re-lock your bootloader. I'm on Verizon with the Verizon variant of the Pixel XL. I took the 7.1.1 update and my bootloader stayed unlocked.
grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL
Click to expand...
Click to collapse
Updates can't lock your bootloader.
thecarp1975 said:
It will not re-lock your bootloader. I'm on Verizon with the Verizon variant of the Pixel XL. I took the 7.1.1 update and my bootloader stayed unlocked.
Click to expand...
Click to collapse
airmaxx23 said:
Updates can't lock your bootloader.
Click to expand...
Click to collapse
Thanks guys! Just wanted to be absolutely sure.
Sent from my Nexus 6 that thinks it's a Pixel XL
is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?
raybonz420 said:
is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?
Click to expand...
Click to collapse
It's not necessarily impossible --nobody seems to have a 100% understanding of what the dual slots are doing on this phone. People who were on custom Roms and rooted have reported successfully taking a stock OTA update without boot looping their phones, although it did wipe out root and the custom recovery. But it's not a great idea to do it the way you suggest and basically hope you get lucky. You would be much better off unlocking the bootloader at least temporarily and flashing a full stock image from Google.
raybonz420 said:
is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?
Click to expand...
Click to collapse
No, because you would not be able to properly sign the file you created so your phone would reject it. The whole Certificate signing thing is what I speak of, if the file isn't signed with a google cert the ota would fail.
TonikJDK said:
No, because you would not be able to properly sign the file you created so your phone would reject it. The whole Certificate signing thing is what I speak of, if the file isn't signed with a google cert the ota would fail.
Click to expand...
Click to collapse
could it be signed using chainfires AVB?
raybonz420 said:
could it be signed using chainfires AVB?
Click to expand...
Click to collapse
No, an ota has to be signed by google.
If you have no plans to root the phone is there any reason to unlock the bootloader?
It would probably break Safety net and Android pay. BUT if you're unlocked, you have ability to flash factory images. That could be beneficial something goes really bad and your device won't boot up. You're also less secure with it unlocked.
Sent from my marlin using XDA Labs
You can always lock and unlock the bootloader when you want.
I would say you should at least have the option checked on in the Developer settings.
So just in case something happened and you can't fully boot the phone. you can still get into it and unlock the bootloader and do what you need to do.
This happened to a friend of mine where something happened and couldn't fully boot and couldn't unlock bootloader cause the option was never checked.
I don't believe the unlock option stays enabled after it boots up.
I would argue why WOULDN'T you unlock the bootloader? Regardless of rooting, an unlocked bootloader is a safety net for when things go south. Phone decides to bootloop tomorrow? No big deal, flash the latest images via fastboot and start from scratch.
Sure there's the counter argument of the phone being much less secure and vulnerable in the hands of a person who is tech savvy and stole/found your device. I'm not worried about my phone being stolen so I ALWAYS unlock my bootloader.
Pain-N-Panic said:
I would argue why WOULDN'T you unlock the bootloader? Regardless of rooting, an unlocked bootloader is a safety net for when things go south. Phone decides to bootloop tomorrow? No big deal, flash the latest images via fastboot and start from scratch.
Sure there's the counter argument of the phone being much less secure and vulnerable in the hands of a person who is tech savvy and stole/found your device. I'm not worried about my phone being stolen so I ALWAYS unlock my bootloader.
Click to expand...
Click to collapse
or just flash the full OTA image without an unlocked bootloader.
mngdew said:
You can always lock and unlock the bootloader when you want.
Click to expand...
Click to collapse
Does re-locking the bootloader wipe the phone?
foosion said:
Does re-locking the bootloader wipe the phone?
Click to expand...
Click to collapse
Yes, it does. That's why you should unlock or lock the bootloader when flashing factory images.
mngdew said:
Yes, it does.
Click to expand...
Click to collapse
Thanks
mngdew said:
That's why you should unlock or lock the bootloader when flashing factory images.
Click to expand...
Click to collapse
I don't understand what you mean by this.
You have to unlock the bootloader to flash a factory image and you can eliminate the w flag so that flashing the factory image won't wipe the phone.
uicnren said:
or just flash the full OTA image without an unlocked bootloader.
Click to expand...
Click to collapse
Very true. If the phone goes into booploop due to a bad zip or whatever other reason you have a bricked device with no options to recover.
It's healthy for me to unlock my Bootloader ASAP on XDA!
Unlocking the bootloader was always the very first thing I did when I got a new phone. However, I use Android Pay all the time, and Google seems very determined to break AP for unlocked bootloaders with every new patch. Sure, someone usually finds a way to get it working again, but that sometimes takes time, and I simply use AP too much to deal with it. As long as AP won't work officially with an unlocked bootloader, mine stays locked unless I'm flashing an image, and even then, gets locked right after. Luckily, OTAs are posted by Google now, often at the same time as the Factory Images, so it hasn't really been an issue for me.
akenis said:
It would probably break Safety net and Android pay. BUT if you're unlocked, you have ability to flash factory images. That could be beneficial something goes really bad and your device won't boot up. You're also less secure with it unlocked.
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
Thank you what actually is compromised when phone is unlocked?
uicnren said:
or just flash the full OTA image without an unlocked bootloader.
Click to expand...
Click to collapse
How can you flash with a locked bootloader?
painfree said:
Thank you what actually is compromised when phone is unlocked?
Click to expand...
Click to collapse
Data?
https://www.google.com/amp/s/www.ho...unlocking-your-android-phones-bootloader/amp/
Sent from my marlin using XDA Labs
painfree said:
If you have no plans to root the phone is there any reason to unlock the bootloader?
Click to expand...
Click to collapse
If you ever contemplate going onto the Verizon network, when you first boot up after placing VZN sim into the phone,
the ability to ever unlock again is eliminated. You could relock it, but it will have the Unlock option in Developer
Option greyed out forever after that. I would unlock it maybe because of Verizon thing, but also to be able to flash factory a image in case I ever mess up the phone.
michaelbsheldon said:
If you ever contemplate going onto the Verizon network, when you first boot up after placing VZN sim into the phone,
the ability to ever unlock again is eliminated. You could relock it, but it will have the Unlock option in Developer
Option greyed out forever after that. I would unlock it maybe because of Verizon thing, but also to be able to flash factory a image in case I ever mess up the phone.
Click to expand...
Click to collapse
As long as you have the Google version it should never grey out on you at least that's how it was with the first pixels. I have Verizon I've never had it grey out.
jt3 said:
Unlocking the bootloader was always the very first thing I did when I got a new phone. However, I use Android Pay all the time, and Google seems very determined to break AP for unlocked bootloaders with every new patch. Sure, someone usually finds a way to get it working again, but that sometimes takes time, and I simply use AP too much to deal with it. As long as AP won't work officially with an unlocked bootloader, mine stays locked unless I'm flashing an image, and even then, gets locked right after. Luckily, OTAs are posted by Google now, often at the same time as the Factory Images, so it hasn't really been an issue for me.
Click to expand...
Click to collapse
This. Android Pay is pretty convenient and I always told myself I didn't need it compared to unlock+root. Wish Google would allow AP with unlocked bootloader but I can understand why they don't from a security standpoint.
Sent from my Pixel 2 XL using Tapatalk
foosion said:
Thanks
I don't understand what you mean by this.
You have to unlock the bootloader to flash a factory image and you can eliminate the w flag so that flashing the factory image won't wipe the phone.
Click to expand...
Click to collapse
When you unlock the bootloader, phone is wiped automatically.
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pixel-2-xl/development/tool-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
oliverfongftw said:
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
Click to expand...
Click to collapse
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
If you have the stock recovery and can boot into it you can adb sideload the most recent ota zip.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
ram4ufriends said:
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
Click to expand...
Click to collapse
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
You can get the bootloader lock status simply by booting into the bootloader. Locked or unlocked? You don't "think" it has a working recovery is not good enough to help you. If it does have a stable recovery, you can flash the OTA. If it does not and the bootloader is locked you are S.O.L. and the phone is dead. Follow this video and let us know.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
If you can hold down volume and hit power to get into bootloader and choose Recovery, you can fix this phone.
Go here: read instructions at top. You will be booting to bootloader, then to recovery, then choose Apply Update from ADB.
Then give adb OTA command as described. Don't skip or modify any step.
https://developers.google.com/android/ota
I am in this exact same situation. Did you ever figure it out? Or did anyone figure it out?
Got this exact problem with a locked bootloader and no recovery, any solution?
0x0null said:
Got this exact problem with a locked bootloader and no recovery, any solution?
Click to expand...
Click to collapse
How did you lose the recovery with a locked bootloader?
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
How did you lose the recovery with a locked bootloader?
Click to expand...
Click to collapse
Got it that way thinking i could use recovery to recover the phone
0x0null said:
Got it that way thinking i could use recovery to recover the phone
Click to expand...
Click to collapse
It came without a recovery.
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
mookiexl said:
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
Click to expand...
Click to collapse
Locked bootloader wont let me use the script.
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Strephon Alkhalikoi said:
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Click to expand...
Click to collapse
Yea, your on point. Only edl firehose may save me
0x0null said:
Locked bootloader wont let me use the script.
Click to expand...
Click to collapse
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
mookiexl said:
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
Click to expand...
Click to collapse
It Unlocks only if 'oem unlock' is engaged from the booted system.
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Which is exactly why it should never be in the locked position...
Sent from my Pixel 2 XL using XDA Labs
0x0null said:
Yea, your on point. Only edl firehose may save me
Click to expand...
Click to collapse
and save me to. I try to find firhose for my pixel 2xl but I didn't find it. Hope someone can provide QFIL Firmware to save as.
Sent from my MI 9 using Tapatalk
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Did you try? I used it with no 0S installed so oem unlock couldnt have been engaged.
Has anyone figured out how to unlock the bootloader on the LGM710ULM? I have google fi and my warranty has just expired, so I was trying to install linux on my phone, but I cant find out how to unlock the bootloader anywhere.
AverytheFurry said:
Has anyone figured out how to unlock the bootloader on the LGM710ULM? I have google fi and my warranty has just expired, so I was trying to install linux on my phone, but I cant find out how to unlock the bootloader anywhere.
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568
Went through these steps last night. Now bootloader unlocked and rooted with magisk.
way2aware said:
https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568
Went through these steps last night. Now bootloader unlocked and rooted with magisk.
Click to expand...
Click to collapse
Are you sure it worked for the LGM710ULM
AverytheFurry said:
Are you sure it worked for the LGM710ULM
Click to expand...
Click to collapse
Indeed I am, although my phone now believes that its a LM-V350ULM. Please go to the thread I linked you to. It really works
way2aware said:
Indeed I am, although my phone now believes that its a LM-V350ULM. Please go to the thread I linked you to. It really works
Click to expand...
Click to collapse
The only thing that is from the v350ulm is the bootloader.. You can fix that by reflashing the ULM kdz or backing up the stock abl_a img before flashing the v350ulm bootloader then restoring it..
But its no big deal