Ever since I unlocked and rooted my phone, it no longer will hold a Bluetooth connection with my car. It'll connect and then drop completely every time. Anyone else experiencing this? Or know a way to fix it?
I'm not able to find a guide of how to remove root on this phone. Do you know of any?
Am I the only one with bluetooth problems after root? I don't see anyone else with the issue.
You are not the only one, there are many complaints on the Pixel user forum!
Also many on the Android Auto discussions.
I tried connection before I was rooted and got immediate failures, but I never tried prior to unlocking the bootloader.
cam30era said:
Download the factory image (same one that's currently on your phone), unzip it and fastboot flash the stock boot image.
Or download SuperSU v2.78 SR3, flash it and then use the "unroot" feature in the app.
Click to expand...
Click to collapse
Or simply flash one of the modded kernels in the development section they will knock out root.
Anthony825 said:
Am I the only one with bluetooth problems after root? I don't see anyone else with the issue.
Click to expand...
Click to collapse
Never had any Bluetooth issues after rooting what so ever
pcriz said:
Never had any Bluetooth issues after rooting what so ever
Click to expand...
Click to collapse
I agree. However, OP did state that his XL connected via Bluetooth prior to rooting, but not after.
cam30era said:
I agree. However, OP did state that his XL connected via Bluetooth prior to rooting, but not after.
Click to expand...
Click to collapse
I was just responding to his quoted post of are other people having issues
I just got a group of Google updates and thought I would try my Bluetooth/Android Auto connections again.
Everything works just the way I expect it to!
Life is good again!
DIXZ06 said:
I just got a group of Google updates and thought I would try my Bluetooth/Android Auto connections again.
Everything works just the way I expect it to!
Life is good again!
Click to expand...
Click to collapse
Anthony825 said:
Ever since I unlocked and rooted my phone, it no longer will hold a Bluetooth connection with my car. It'll connect and then drop completely every time. Anyone else experiencing this? Or know a way to fix it?
Click to expand...
Click to collapse
That's a good point, are you on the latest firmware for your device/region?
Mine straight up drops connection immediately to any bluetooth device I hook it up to.
I'm on Verizon. Are the most recent updates still able to be rooted? And would updating relock my bootloader?
November update won't lock your bootloader.
Related
[Q&A] [ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleD
Q&A for [ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
will there be an update to the PurpleDrake method on the D851 with the new 10m update? for it to work properly?
YOu can still get rooted if u are on 10m. I did. It wont exit properly so u will need to pull the battery after it is done.
Nsx93 said:
YOu can still get rooted if u are on 10m. I did. It wont exit properly so u will need to pull the battery after it is done.
Click to expand...
Click to collapse
Correct. However, it does not install TWRP, nor the custom Boot.IMG to prevent triggering the root counter. I too would like to see an update to include these items.
tribalartgod said:
Correct. However, it does not install TWRP, nor the custom Boot.IMG to prevent triggering the root counter. I too would like to see an update to include these items.
Click to expand...
Click to collapse
I see your concern.. you can manually install twrp but i have no idea bout the boot.img
i did all except that. Someone mentioned you can flash back to stock and it will fix the root counter. If you ever need to send in your phone that is... but i do understand its easier if this would be one package kind of thing.
IDK how to even check that yet. LOL. I have already rooted and unrooted, just to familiarize myself with the process.
Does this root method work on the t-mobile D851 10M
johnny quest said:
Does this root method work on the t-mobile D851 10M
Click to expand...
Click to collapse
Yes, but as stated above, it will glitch. The glitch just freezes on the permaroot steps. Once this happens, removing the battery and rebooting still keeps your device rooted. With 10M, currently, you will have to manually install TWRP. I recommend downloading the IMG file online, and using Flashify to flash it.
tribalartgod said:
Yes, but as stated above, it will glitch. The glitch just freezes on the permaroot steps. Once this happens, removing the battery and rebooting still keeps your device rooted. With 10M, currently, you will have to manually install TWRP. I recommend downloading the IMG file online, and using Flashify to flash it.
Click to expand...
Click to collapse
Thank you for the response. Do you think its worth rooting since 5.0 is coming out soon? I still want to root but will I have to unroot in order to get the 5.0 upgrade? or better yet, will the LG get the upgrade any time soon. Sorry for these questions. And also, since this phone has the top notch camera resolution, will rooting affect the camera?
johnny quest said:
Does this root method work on the t-mobile D851 10M
Click to expand...
Click to collapse
johnny quest said:
Thank you for the response. Do you think its worth rooting since 5.0 is coming out soon? I still want to root but will I have to unroot in order to get the 5.0 upgrade? or better yet, will the LG get the upgrade any time soon. Sorry for these questions. And also, since this phone has the top notch camera resolution, will rooting affect the camera?
Click to expand...
Click to collapse
I unrooted to ensure I get the update. If you are rooted, and have not turned off OTA, you might get the OTA, and it might break something. I personally like the LG camera better than any other so far. Another reason I went back to stock. Rooting and keeping the stock OS, should leave the camera alone. If you flash a different ROM, your mileage may vary.
We should be getting 5.0 before the end of the year, officially. LINK
tribalartgod said:
I unrooted to ensure I get the update. If you are rooted, and have not turned off OTA, you might get the OTA, and it might break something. I personally like the LG camera better than any other so far. Another reason I went back to stock. Rooting and keeping the stock OS, should leave the camera alone. If you flash a different ROM, your mileage may vary.
We should be getting 5.0 before the end of the year, officially. LINK
Click to expand...
Click to collapse
I really appreciate your response. Thank you I will make sure that I have OTA on and maybe root and leave stock.
LG G3 D851: Root before or after Lollipop
My question is do I root now while on Android 4.4.2 or will I be safe to wait until after Lollipop has rolled out? I really want root but I'm afraid that it may not be an option after the update. Any guidance will be appreciated! Thanks in advance!
Waiting for device...
Hey, sorry to bug you. I cannot seem to get past Waiting for device...
I've installed the recommended drivers package, I've made sure it's in PTP mode, USB debugging connected, drivers appear to've installed properly: nothing. Just sits there.
Anything I could be missing? D851 running 4.4.2, Windows 7
SAMMMMMM said:
Hey, sorry to bug you. I cannot seem to get past Waiting for device...
I've installed the recommended drivers package, I've made sure it's in PTP mode, USB debugging connected, drivers appear to've installed properly: nothing. Just sits there.
Anything I could be missing? D851 running 4.4.2, Windows 7
Click to expand...
Click to collapse
Did you change the port number in device manager?
tribalartgod said:
Did you change the port number in device manager?
Click to expand...
Click to collapse
No, perhaps I didn't. Is there a long and detailed explanation of how to use this rooting tool? The first post doesn't mention anything about a port change.
SAMMMMMM said:
No, perhaps I didn't. Is there a long and detailed explanation of how to use this rooting tool? The first post doesn't mention anything about a port change.
Click to expand...
Click to collapse
My apologies, that's for restoring stock... I see in your posts, you have it set to PTP... Mine was set to MTP. While "waiting for device" was on screen, I unplugged and replugged the phone. Aside from that, seems like you have done everything else properly...
Anyone else having issues making backups of AOSP ROMs? The backup folder is empty.
---------- Post added at 05:16 PM ---------- Previous post was at 04:55 PM ----------
datdirtyscrew said:
Anyone else having issues making backups of AOSP ROMs? The backup folder is empty.
Click to expand...
Click to collapse
Looks like its only when backing up to external SD. Internal backs up fine.
tribalartgod said:
My apologies, that's for restoring stock... I see in your posts, you have it set to PTP... Mine was set to MTP. While "waiting for device" was on screen, I unplugged and replugged the phone. Aside from that, seems like you have done everything else properly...
Click to expand...
Click to collapse
I mean I'd be more frustrated if I wasn't waiting for lollipop to drop, so I'm shelving this for now, but I hope it isn't a persistent nag.
Sent from my SM-N900T using XDA Free mobile app
PurpleDrake issue
i was just rooting my G3 with purpledrake, and while it was doing the permaroot part, purpledrake closed on my computer and now my phone is stuck on a screen showing a red hand with a cross through it and a usb cord plugged into the side of a phone. What should i do?
Anyone know what this is for?
Jrocker23 said:
Anyone know what this is for?
Click to expand...
Click to collapse
Hm. 612 megs. That could be....well let's see.
Sent from my Nexus 6 using Tapatalk
Installed and currently on the Android is upgrading/Optimizing apps screen...... Hopefully won't take too much longer.
software repair patch for 5.1 as told by vzw customer service. what it is repairing i dont know
3.10.605.7 / Base: 2.12.C1144073
Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/
SnoStorm said:
Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/
Click to expand...
Click to collapse
One can only wonder what the heck verizon does to their software such that it requires a 612meg security patch huh?
Anyhow.. Time to use that nandroid i posed in the dev section to accept the OTA.. -or- I will post an updated one later this evening.
Probably 600mb of updated NFL bloatware included and the rest just the security update.
Any word yet on whether this is really just a 612Meg security patch?
jtommyj said:
Any word yet on whether this is really just a 612Meg security patch?
Click to expand...
Click to collapse
yup, nothing special
Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.
baune7 said:
Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.
Click to expand...
Click to collapse
are you SOFF? if so, you will be fine
Yes.. I'm s-off and unlocked. So after it updates, will it still be rooted? Or would I havery to re-root it? I'm just worried because my cable Internet isn't working for a few days and I need my wifi tether. Thanks
Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=sharing
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=sharing
gumbyx84 said:
Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=docslist_api
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=docslist_api
Click to expand...
Click to collapse
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk
dottat said:
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted.
Update: I decided to just to a factory reset. Thankfully it worked and I am at the latest firmware.
So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.
baune7 said:
So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.
Click to expand...
Click to collapse
I'm pretty sure you need stock recovery to take an OTA.
SigLover21 said:
I'm pretty sure you need stock recovery to take an OTA.
Click to expand...
Click to collapse
Ok.. Thanks.. I'll have to check into that
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
niko26 said:
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
Click to expand...
Click to collapse
Good place to start https://plus.google.com/+Chainfire
danw_oz said:
Good place to start https://plus.google.com/+Chainfire
Click to expand...
Click to collapse
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
niko26 said:
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
Click to expand...
Click to collapse
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
danw_oz said:
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
Click to expand...
Click to collapse
Thanks for your comment.
I was not asking why he was not replying to my questions - I've got total sympathy for that because the number of messages he might get must be insane.
My question still stands: Obviously Flashfire is not yet aware of the different layout of partitions on the Pixel phones. Does it still work correctly? If not, did Chainfire say anything about Flashfire being fixed to work with the pixels? I couldn't find anything, that's why I'm asking here.
I assume any announcement on it working on the Pixel will be made when it works on the Pixel. Much like superSU. (hope that doesnt sound like an ass thing to say) it's just the way things have been. unless someone else works on something and it looks like they are going to beat another dev to the punch, you don't usually see any info, much like boot-loader unlocks, rooting of a certain phone etc.. i.e when there is a bounty and team blahblah looks like they gonna take the glory, BANG! suddenly there's a solution that said dev was already working on secretly but wasn't planing on releasing any time soon but since there's competition, kinda thing. Know what I mean?
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
Hey just curious what you mean by this. I know that TWRP has some bugs but I thought everything with SuperSU was worked out
I'm thinking they are still working on having them coexist without one wiping the other
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
No they work fine, especially SuperSU. TWRP is in alpha but works for installing and most other things but backup and restore does not yet.
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
Wow, that was like week number one.
You're waaaaaay behind on updates.
Lol then we should get on chain fires case
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
What? SuperSU working perfectly with twrp. As others said twrp still in alpha and some features are iffy, but SuperSU is solid.
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
CZ Eddie said:
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
Click to expand...
Click to collapse
My apologies. T-Mobile, US - added to profile. Thanks for the suggestion!
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
You can sideload the update via ADB supposedly.
I've never used that method though.
I just flash the entire update on top of my old OS using flashboot and my guide here:
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Make sure to remove the -w from the script if you don't want your old data/apps wiped.
Then re-root your phone afterwards.
Nothing to worry about there if it's not a Verizon phone.
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
I do it like in this guide http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
s1dest3pnate said:
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
Click to expand...
Click to collapse
No, no downside at all. Flash all without the -w is how most people do it. It could even be argued that it is better.
Sent from my Pixel XL using XDA Labs
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
ClassickWORLD said:
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
Click to expand...
Click to collapse
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Badger50 said:
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Click to expand...
Click to collapse
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
While I haven't done it personally, I've seen several people do just that from stock recovery. At worst, the install will fail and nothing will be changed. Unlocking the bootloader is mainly for flashing factory images and rooting, not OTA's. Just follow the instructions from Google and see what happens. In your current situation, you really have nothing to lose.
https://developers.google.com/android/ota
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??????
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
You do want the February one. It's for all phones including Verizon.
Badger50 said:
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
Click to expand...
Click to collapse
So I can flash that with no radio issues? I thought OPM1 is google, OPM2 is Telus only, and OPD3 is Verizon only? I have a Verizon P2XL
Edit: I think I've found my issue. The person who had the device before me must have sideloaded 8.1.0 (OPM1.171019.018, Feb 2018)" to this device and that may be the reason for the error. I am thinking because that's not the Verizon P2XL firmware but the Google P2XL device firmware.
michaelbsheldon said:
You do want the February one. It's for all phones including Verizon.
Click to expand...
Click to collapse
Ok gotcha. Downloading now as we speak.
Badger50 said:
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??
Click to expand...
Click to collapse
Lol I still have my trusty ol' Nexus 6P as my secondary device.
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
ClassickWORLD said:
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
Click to expand...
Click to collapse
Fixed and you're a happy camper, right?
P.S. try a factory reset to complete this
You guys are great. The sideload fixed the problem! I truly appreciate you guys. Thanks a lot.
ClassickWORLD said:
Lol I still have my trusty ol' Nexus 6P as my secondary device.
Click to expand...
Click to collapse
Ok bruh, your forgiven :laugh: Did you get your problem fixed?
Oooops....never mind. I see that you did :good:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
tradermatt said:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
Click to expand...
Click to collapse
There is no method to unlock the Verizon P2XL!!
Just wondering when the new security update will be out as I feel the last one is making my battery drain quite a lot. Tried all the normal routine stuff and still nothing specially after two factory resets. Here is hoping that with the new software it will be fixed
Hey Goku80, judging solely by past-trends, it should most certainly be out today.
It's live guys! https://dl.google.com/dl/android/aosp/crosshatch-pq3a.190801.002-factory-15db810d.zip
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
BoboBrazil said:
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
Click to expand...
Click to collapse
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
ota is not here yet
Goku80 said:
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
Click to expand...
Click to collapse
The OTA can be flashed using stock recovery. No wipe.
spotmark said:
The OTA can be flashed using stock recovery. No wipe.
Click to expand...
Click to collapse
True but means I need to use ADB which I don't have a pc
Goku80 said:
True but means I need to use ADB which I don't have a pc
Click to expand...
Click to collapse
You can flash it as long as your BL is unlocked. It has nothing to do with root. You still need to use the flash-all batch file though, so a computer is still necessary.