Before I buy, just like the title says, any problems or hiccups with unlock and root?
Thanks
Droid_Nut said:
Before I buy, just like the title says, any problems or hiccups with unlock and root?
Thanks
Click to expand...
Click to collapse
Not if it's a google version device. Just make sure it is before you buy :good:
Badger50 said:
Not if it's a google version device. Just make sure it is before you buy :good:
Click to expand...
Click to collapse
Great, I already have a Google Fi model in the shopping cart at the Google store. :good:
Droid_Nut said:
Great, I already have a Google Fi model in the shopping cart at the Google store. :good:
Click to expand...
Click to collapse
Nice! Let us ol P2XL users know if you need any help unlocking and rooting. There are many helpful threads to help you on your way. :good:
Badger50 said:
Nice! Let us ol P2XL users know if you need any help unlocking and rooting. There are many helpful threads to help you on your way. :good:
Click to expand...
Click to collapse
Thanks Badger, what is the best thread to start with?
Droid_Nut said:
Thanks Badger, what is the best thread to start with?
Click to expand...
Click to collapse
No problem bruh. Here you go :good::good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So I wont see my Pixel until next week, what is the latest stock update, pie or oreo? Once it wears on me, I will probably try a custom rom.
Droid_Nut said:
So I wont see my Pixel until next week, what is the latest stock update, pie or oreo? Once it wears on me, I will probably try a custom rom.
Click to expand...
Click to collapse
Latest stock is 9.0 and has been since last August :good:
Fedex had delivery scheduled for Tuesday due to some problem in Tennessee, so I did not bother looking at the tracking today, and they did attempt delivery, and I missed it.
Anyways, where is the best place on the phone to put all the install files so they don't get wiped, since we don't have an external SD?
In my Nexus I have 0, or sdcard?
Droid_Nut said:
Fedex had delivery scheduled for Tuesday due to some problem in Tennessee, so I did not bother looking at the tracking today, and they did attempt delivery, and I missed it.
Anyways, where is the best place on the phone to put all the install files so they don't get wiped, since we don't have an external SD?
In my Nexus I have 0, or sdcard?
Click to expand...
Click to collapse
Anywhere on your internal storage will be fine. But here's the deal, when you get your device, unlock it ASAP before you set it up too much, or put any data on it. Unlocking the bootloader is going to wipe your device. Once done, then go to town setting it up. You can do updates with fastboot or OTA's that will not wipe your internal storage data :good:
So I am going to get it, add sim, test it, unlock it, boot the TWRP image from PC, make a nandroid backup, copy backup to PC, boot TWRP image, install latest Pixel factory image, install Magisk, install TWRP zip, reboot system, profit!
How does that sound?
BTW Badger, you are awesome, I wish you had a donate link, you helped me with my 6P, and maybe other devices. :good:
Droid_Nut said:
So I am going to get it, add sim, test it, unlock it, boot the TWRP image from PC, make a nandroid backup, copy backup to PC, boot TWRP image, install latest Pixel factory image, install Magisk, install TWRP zip, reboot system, profit!
How does that sound?
BTW Badger, you are awesome, I wish you had a donate link, you helped me with my 6P, and maybe other devices. :good:
Click to expand...
Click to collapse
Thanks bruh, I appreciate the kind words, but it's just fun for me to help folks out.
As far as when you get the device, I'd fire it up, do a minimal setup, then check to see if you get an OTA update, which I think you will, then unlock the bootloader, then go back and set it up, then do your twrp stuff :good:
Badger50 said:
Thanks bruh, I appreciate the kind words, but it's just fun for me to help folks out.
As far as when you get the device, I'd fire it up, do a minimal setup, then check to see if you get an OTA update, which I think you will, then unlock the bootloader, then go back and set it up, then do your twrp stuff :good:
Click to expand...
Click to collapse
So will it get multiple updates, or just the latest?
Droid_Nut said:
So will it get multiple updates, or just the latest?
Click to expand...
Click to collapse
Probably just the latest. Then again, I haven't taken an OTA in years
Badger50 said:
Probably just the latest. Then again, I haven't taken an OTA in years
Click to expand...
Click to collapse
Usually it takes all available updates, one at a time until it gets to the latest. You have to reboot between each one. I guess I can check against the factory image site, and see how many it needs and if its a lot, flash the latest image?
Droid_Nut said:
Usually it takes all available updates, one at a time until it gets to the latest. You have to reboot between each one.
Click to expand...
Click to collapse
Ah, gotchya. Well then depending what version your on, you could either fastboot to the latest monthly or flash the OTA in twrp :good:
Well, one of the dirt bags at FedEx stole the device only out of the box. Seems to be common.
https://www.reddit.com/r/ProjectFi/comments/a1s8wo/another_pixel_3_stolen_from_the_fedex_shipping/
Droid_Nut said:
Well, one of the dirt bags at FedEx stole the device only out of the box. Seems to be common.
https://www.reddit.com/r/ProjectFi/comments/a1s8wo/another_pixel_3_stolen_from_the_fedex_shipping/
Click to expand...
Click to collapse
Are you flippin kidding me man! What a rotten piece of worm ridden filth that dude is! Sorry to hear that my friend. That just plain SUCKS! I hate thieves!! ?
Too bad it's not the olden days! :good:
And Google seems to treat each case as if the consumer stole the product out of the box, like what am I going to do with a phone that has a locked IMEI?
Droid_Nut said:
And Google seems to treat each case as if the consumer stole the product out of the box, like what am I going to do with a phone that has a locked IMEI?
Click to expand...
Click to collapse
Well I hope they work it out for you and treat you right my friend! :good:
Related
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
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
sniperIT said:
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
Click to expand...
Click to collapse
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
metpage said:
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
Click to expand...
Click to collapse
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
sniperIT said:
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
Click to expand...
Click to collapse
I would try and get your money back, chances are you could have brought a stolen phone.
Darke5tShad0w said:
I would try and get your money back, chances are you could have brought a stolen phone.
Click to expand...
Click to collapse
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
sniperIT said:
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
Click to expand...
Click to collapse
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
sniperIT said:
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
Click to expand...
Click to collapse
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok thank you very much I am in the process, will update once it is complete.
N
sniperIT said:
Ok thank you very much I am in the process, will update once it is complete.
N
Click to expand...
Click to collapse
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
sniperIT said:
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
Click to expand...
Click to collapse
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
16GB unfortunately.
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
PiousInquisitor said:
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
Click to expand...
Click to collapse
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
sniperIT said:
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
Click to expand...
Click to collapse
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
PiousInquisitor said:
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
Click to expand...
Click to collapse
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
sniperIT said:
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
Click to expand...
Click to collapse
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
PiousInquisitor said:
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
Click to expand...
Click to collapse
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
sniperIT said:
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
Click to expand...
Click to collapse
Bummer. Im out of ideas.
What message do you exactly get when trying to execute something via fastboot?
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
nozzleman_85 said:
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
Click to expand...
Click to collapse
Not if you have a locked bootloader
Cozzeck said:
Not if you have a locked bootloader
Click to expand...
Click to collapse
How would I go about doing this, I have a Verizon pixel xl that's unlocked and I am on the X update and would like to revert to P
shibbnasty said:
How would I go about doing this, I have a Verizon pixel xl that's unlocked and I am on the X update and would like to revert to P
Click to expand...
Click to collapse
What's the point of returning to P?
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
What's the point of returning to P?
Click to expand...
Click to collapse
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
shibbnasty said:
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
Click to expand...
Click to collapse
Well first you need to unlock your bootloader: http://theroot.ninja/depixel8.html
After that, download the P factory image from Google's site and follow instructions to install. Just remember to backup stuff you want (photos, files, anything saved on storage) because unlocking will perform a factory reset.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Well first you need to unlock your bootloader: http://theroot.ninja/depixel8.html
After that, download the P factory image from Google's site and follow instructions to install. Just remember to backup stuff you want (photos, files, anything saved on storage) because unlocking will perform a factory reset.
Click to expand...
Click to collapse
Already unlocked and downloaded the images and tried to install as the directions but during the process it says boot.img and recovery.img is missing even though I did exactly what it said.
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
Not really sure what I'm doing wrong at this point and I'm stuck
Did you copy the files into the fastboot and adb program file?
They need to be in there for it to work.
shibbnasty said:
Already unlocked and downloaded the images and tried to install as the directions but during the process it says boot.img and recovery.img is missing even though I did exactly what it said.
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
Not really sure what I'm doing wrong at this point and I'm stuck
Click to expand...
Click to collapse
Your using an outdated ADB and Fastboot (like 99% of the people on this forum).
Here is the latest: https://dl.dropboxusercontent.com/u/31360541/platform-tools-version_1.0.36-API_25.zip
Scott said:
Your using an outdated ADB and Fastboot (like 99% of the people on this forum).
Here is the latest: https://dl.dropboxusercontent.com/u/31360541/platform-tools-version_1.0.36-API_25.zip
Click to expand...
Click to collapse
Thank you, worked after that and I am back to P but unfortunately my flash is still not working correctly. Sucks in passed the 14 day return so I'll get a refurbished when the phone is practically brand new.
shibbnasty said:
Thank you, worked after that and I am back to P but unfortunately my flash is still not working correctly. Sucks in passed the 14 day return so I'll get a refurbished when the phone is practically brand new.
Click to expand...
Click to collapse
There might not be any refurbished phones to send you so you might luck out. Better to try now than later when they have a big stock of returned phones. Or I'm crazy and you'll get one either way...
Jacobk85 said:
There might not be any refurbished phones to send you so you might luck out. Better to try now than later when they have a big stock of returned phones. Or I'm crazy and you'll get one either way...
Click to expand...
Click to collapse
Yea I'm really hoping not to get a refurbished. I'm gonna do my best to see that I get a new one but if not I guess oh well. I have a 32g really blue model so not sure if they even have any new ones.
shibbnasty said:
Yea I'm really hoping not to get a refurbished. I'm gonna do my best to see that I get a new one but if not I guess oh well. I have a 32g really blue model so not sure if they even have any new ones.
Click to expand...
Click to collapse
Thanks for hijacking my thread dude....
nozzleman_85 said:
Thanks for hijacking my thread dude....
Click to expand...
Click to collapse
Sorry man....
shibbnasty said:
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
Click to expand...
Click to collapse
Doubt you'd get a refurbished unit at this point, you'd still get one from replacement stock set aside for early issues.
nozzleman_85 said:
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
Click to expand...
Click to collapse
You will need to unlock your bootloader. Why do you need to downgrade though? You can root and install TWRP on nde63x.
cambunch said:
You will need to unlock your bootloader. Why do you need to downgrade though? You can root and install TWRP on nde63x.
Click to expand...
Click to collapse
I realized that after a little research.. that's my fault..
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!!