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..
Related
So Far came this far with the chimera tool
This didn't brick your phone?
It didn't root mine, but it didn't brick it. Device status is custom.
And... I lose my wifi connections on boot
Prfndhatrdofman said:
This didn't brick your phone?
Click to expand...
Click to collapse
Havent gotten to rooting mine. Because i am using the trail version, i used it to check my phone info. Now i have to wait 3 hrs to use the root functionality.
more info on how the trail-license works:
https://chimeratool.com/help/Trial-License
maheshwar said:
Havent gotten to rooting mine. Because i am using the trail version, i used it to check my phone info. Now i have to wait 3 hrs to use the root functionality.
more info on how the trail-license works:
https://chimeratool.com/help/Trial-License
Click to expand...
Click to collapse
Man, that is some shady looking **** right there. Let me know how it goes haha.
Tried root it failed on me.
My guess is as of right now it only works for the N920AUCU1AOGG firmware, it is the original firmware that came when the phone was introduced. Now everyone is rocking the N920AUCU2AOJ1 firmware that came out some time in between September - December.
If you search for the firmware available in chimera root tool, the one they have is the original one OGG. I guess the only way for this to work is to downgrade then run the utility.
how do I stop the now constant security warnings, and dropping of wifi on reboot?
Russ77 said:
how do I stop the now constant security warnings, and dropping of wifi on reboot?
Click to expand...
Click to collapse
Getting the same myself.
maybe I'll try the unroot option after my 3 hours runs out? don't see much harm in hacking this thing up anymore...
factory reset via recovery and restoring from smart switch did nothing. other than wipe away my screen and app drawer settings :'p
---------- Post added at 08:03 PM ---------- Previous post was at 07:53 PM ----------
sultan.of.swing said:
Getting the same myself.
Click to expand...
Click to collapse
package Disabler pro is your friend for the security warning thing. just disable security log agent
That works for the message, Thinking about trying to Odin to OGG and try root again when the 3hrs is passed
sultan.of.swing said:
That works for the message, Thinking about trying to Odin to OGG and try root again when the 3hrs is passed
Click to expand...
Click to collapse
supposedly chimera can flash OGG.
Russ77 said:
supposedly chimera can flash OGG.
Click to expand...
Click to collapse
sultan.of.swing said:
That works for the message, Thinking about trying to Odin to OGG and try root again when the 3hrs is passed
Click to expand...
Click to collapse
I was wondering about this tool. Let us know what you guys come up with. I might give it a shot. It's already a plus that it didn't leave you with a brick[emoji106]
Sent from my SAMSUNG-SM-N920A using Tapatalk
Read my post http://forum.xda-developers.com/att-galaxy-note5/general/root-files-t3328432
Sunderwear said:
Read my post http://forum.xda-developers.com/att-galaxy-note5/general/root-files-t3328432
Click to expand...
Click to collapse
Thanks for the info
Sent from my SAMSUNG-SM-N920A using Tapatalk
Welp, lost my EFS/IMEI
sultan.of.swing said:
Welp, lost my EFS/IMEI
Click to expand...
Click to collapse
if nothing boots up, take it to the local best buy they can re flash the whole os.
maheshwar said:
if nothing boots up, take it to the local best buy they can re flash the whole os.
Click to expand...
Click to collapse
It boots into the OS just fine but there is no IMEI and the baseband now says unknown
Whew, Complete ODIN back to the newest firmware fixed it.
sultan.of.swing said:
It boots into the OS just fine but there is no IMEI and the baseband now says unknown
Whew, Complete ODIN back to the newest firmware fixed it.
Click to expand...
Click to collapse
Apparently a quick factory reset will restore it , back up your data doe.
https://www.youtube.com/watch?v=Z37W8w79EV0
maheshwar said:
Apparently a quick factory reset will restore it , back up your data doe.
https://www.youtube.com/watch?v=Z37W8w79EV0
Click to expand...
Click to collapse
Yep, doing that now, LOL.
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?
If I flash the play store version to my Verizon one will I be able to bootloader unlock? Or would I need to be bootloader unlocked to flash. I'm on feb5 security patch so I can't use depixel8
Shadowops34 said:
If I flash the play store version to my Verizon one will I be able to bootloader unlock? Or would I need to be bootloader unlocked to flash. I'm on feb5 security patch so I can't use depixel8
Click to expand...
Click to collapse
You need to be unlocked to flash it, so unfortunately you are done.
TonikJDK said:
You need to be unlocked to flash it, so unfortunately you are done.
Click to expand...
Click to collapse
Is there going to be anyway in the future to bootloader unlock? Or can I downgrade? Just spent $540 to root lol
Shadowops34 said:
Is there going to be anyway in the future to bootloader unlock? Or can I downgrade? Just spent $540 to root lol
Click to expand...
Click to collapse
You can't downgrade. It is very doubtful that there will be a way. I suppose it is possible but it doesn't seem anyone is even working on it.
TonikJDK said:
You can't downgrade. It is very doubtful that there will be a way. I suppose it is possible but it doesn't seem anyone is even working on it.
Click to expand...
Click to collapse
Well that sucks,that was a waste lol
I can't believe there is still at least one new thread a week about the same thing.
Shadowops34 said:
Well that sucks,that was a waste lol
Click to expand...
Click to collapse
If it was such a waste why not just return it and pay the $35 restocking fee? Then buy a Google device and unlock it, root it and most likely brick it like half the other people have. And even better yet, research it next time before you buy anything so you don't need to come here and start yet another Verizon thread. And if you can't do any of the above then just enjoy the device as is since you really don't need an unlocked bootloader or root to get the full Pixel experience.
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
aholeinthewor1d said:
I can't believe there is still at least one new thread a week about the same thing.
Click to expand...
Click to collapse
Amazing.
If you are stuck in a bootloop on the Verizon version because you locked yourself out of adb mode, there is an answer. When you load up the phone go into fastboot mode and type fastboot continue
This will actually let you get into the phone before it does its crazy bootloop again and throw you out of adb.
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!!
Hello I was rooting my Moto g6 play and made the awful mistake of not backing up efs partition ( I know Dumb). I got it all done and booted up and now unknown imei. I was wondering if there where any tech savvy people on here that would know how to fix this problem. I know the Imei and if I fastboot getvar I can see the iemi. Plzz help thanks.
dill902 said:
Hello I was rooting my Moto g6 play and made the awful mistake of not backing up efs partition ( I know Dumb). I got it all done and booted up and now unknown imei. I was wondering if there where any tech savvy people on here that would know how to fix this problem. I know the Imei and if I fastboot getvar I can see the iemi. Plzz help thanks.
Click to expand...
Click to collapse
Just flash stock firmware. thats a pretty big mistake to make lol I'm pretty sure I made it quite clear in my guide to backup at least 2 or 3 times. But just flash stock firmware using the commands at the bottom of my guide. Even if the bootloader is locked the commands will work to reflash it still. The need links for stock firmware is also in the guide. And I will say this. If you took the newest update before rooting then you will have to wait for that firmware to be uploaded because its not uploaded yet.
ninjakira said:
Just flash stock firmware. thats a pretty big mistake to make lol I'm pretty sure I made it quite clear in my guide to backup at least 2 or 3 times. But just flash stock firmware using the commands at the bottom of my guide. Even if the bootloader is locked the commands will work to reflash it still. The need links for stock firmware is also in the guide. And I will say this. If you took the newest update before rooting then you will have to wait for that firmware to be uploaded because its not uploaded yet.
Click to expand...
Click to collapse
Thanks man and i know im kicking myself. would you happen to know twhat the newest update is?
dill902 said:
Thanks man and i know im kic,king myself. would you happen to know twhat the newest update is?
Click to expand...
Click to collapse
The newest build is only a few days old so it will be nearly impossible to find online. And it has a different baseband and radio than the previous build. But the October update is OCP27.91-150
As long as the imei isn't zero you should be able to get service back. I had the same issue when I flashed an older firmware like a moron. But when I took the update again, I got service back. I don't recommend it because I may have just been lucky, but no matter what don't flash the gpt, asdspo(?) And bootloader with the older firmware. It'll mess your life up.
Ok i guess ill have to wait it out. Tried to flash stock and still unknown imei and no base band version so guessing it was updated. Thank guys!
dill902 said:
Ok i guess ill have to wait it out. Tried to flash stock and still unknown imei and no base band version so guessing it was updated. Thank guys!
Click to expand...
Click to collapse
Try taking the update again over WiFi if you can. You shouldn't have an issue as long as you're back to stock. But the update is only 3 days old so you may have a chance.
---------- Post added at 04:44 AM ---------- Previous post was at 04:25 AM ----------
ninjakira said:
Just flash stock firmware. thats a pretty big mistake to make lol I'm pretty sure I made it quite clear in my guide to backup at least 2 or 3 times. But just flash stock firmware using the commands at the bottom of my guide. Even if the bootloader is locked the commands will work to reflash it still. The need links for stock firmware is also in the guide. And I will say this. If you took the newest update before rooting then you will have to wait for that firmware to be uploaded because its not uploaded yet.
Click to expand...
Click to collapse
@ninjakira Would my modem.img backup be of any use here? Or anything else? I don't know what is stored where.
Starkiller2 said:
Try taking the update again over WiFi if you can. You shouldn't have an issue as long as you're back to stock. But the update is only 3 days old so you may have a chance.
---------- Post added at 04:44 AM ---------- Previous post was at 04:25 AM ----------
@ninjakira Would my modem.img backup be of any use here? Or anything else? I don't know what is stored where.
Click to expand...
Click to collapse
Idk man i try to update and says its upto date i have the xti922-9 says im on OCP27.91-62
dill902 said:
Idk man i try to update and says its upto date i have the xti922-9 says im on OCP27.91-62
Click to expand...
Click to collapse
Ok so mine won't help then. I'm XT1922-7.
Starkiller2 said:
Try taking the update again over WiFi if you can. You shouldn't have an issue as long as you're back to stock. But the update is only 3 days old so you may have a chance.
---------- Post added at 04:44 AM ---------- Previous post was at 04:25 AM ----------
@ninjakira Would my modem.img backup be of any use here? Or anything else? I don't know what is stored where.
Click to expand...
Click to collapse
At this point no it's gonna need a full reflash of the firmware. I was having issues with my service and went and flashed the OEM file from the 2nd update through fastboot and did the erase carrier command and got my service fixed. Could try that.
---------- Post added at 05:22 AM ---------- Previous post was at 05:14 AM ----------
dill902 said:
Idk man i try to update and says its upto date i have the xti922-9 says im on OCP27.91-62
Click to expand...
Click to collapse
If you have the xt1922-9 then that means you have the att version if I'm not mistaken. If so just go to the links in my guide for stock firmware in the att folder. It has both the firmware your on plus the updated firmware from September which is ocp27.91-62-3 plus my guide will help you achieve root. Just please read it all
ninjakira said:
At this point no it's gonna need a full reflash of the firmware. I was having issues with my service and went and flashed the OEM file from the 2nd update through fastboot and did the erase carrier command and got my service fixed. Could try that.
---------- Post added at 05:22 AM ---------- Previous post was at 05:14 AM ----------
If you have the xt1922-9 then that means you have the att version if I'm not mistaken. If so just go to the links in my guide for stock firmware in the att folder. It has both the firmware your on plus the updated firmware from September which is ocp27.91-62-3 plus my guide will help you achieve root. Just please read it all
Click to expand...
Click to collapse
I flashed bout those firmwares and still nothing i dont understand whats going on or if im messing something up somewhere in the process. It flashes an everything seems to be ok other than the Imei unknown which causes the phone not to read my sim card if im not mistaken. Thanks for taking the time to try and help.
Starkiller2 said:
The newest build is only a few days old so it will be nearly impossible to find online. And it has a different baseband and radio than the previous build. But the October update is OCP27.91-150.
Click to expand...
Click to collapse
Baseband is software. Radio is a piece of hardware. The piece of hardware that gets your carrier's signal. It can't be upgraded without physically altering the phone. Even then it would need to be the same exact radio because the stock drives probably wouldn't work, and the chances of a dev making a version for 1 person with a different hardware would be slim to none.
Starkiller2 said:
@ninjakira Would my modem.img backup be of any use here? Or anything else? I don't know what is stored where.
Click to expand...
Click to collapse
If you want him to have your Imei number, you could but thats not a good idea.
Xplorer4x4 said:
Baseband is software. Radio is a piece of hardware. The piece of hardware that gets your carrier's signal. It can't be upgraded without physically altering the phone. Even then it would need to be the same exact radio because the stock drives probably wouldn't work, and the chances of a dev making a version for 1 person with a different hardware would be slim to none.
If you want him to have your Imei number, you could but thats not a good idea.
Click to expand...
Click to collapse
Thanks for correcting me. I'll be sure not to try again.
So what you guys are saying is I f-ed up and need to buy a new phone? Lol
dill902 said:
So what you guys are saying is I f-ed up and need to buy a new phone? Lol
Click to expand...
Click to collapse
Try flashing stock firmware. If that doesn't work there are other options still.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Try flashing stock firmware. If that doesn't work there are other options still.
Click to expand...
Click to collapse
Thanks I flashed every rom for my model and still nothing. Driving me crazy have to use an old junker phone till I find a solution lol
dill902 said:
Thanks I flashed every rom for my model and still nothing. Driving me crazy have to use an old junker phone till I find a solution lol
Click to expand...
Click to collapse
You were flashing a gsi not a rom. Even then a rom and even less so a gsi, doesn't contain all the same data as what stock does.
Sent from my Moto G6 Plus using Tapatalk
Xplorer4x4 said:
You were flashing a gsi not a rom. Even then a rom and even less so a gsi, doesn't contain all the same data as what stock does.
Click to expand...
Click to collapse
O ok well can you point me in the right direction to download the rom? Or whatever I need to download.
Starkiller2 said:
The newest build is only a few days old so it will be nearly impossible to find online. And it has a different baseband and radio than the previous build. But the October update is OCP27.91-150
As long as the imei isn't zero you should be able to get service back. I had the same issue when I flashed an older firmware like a moron. But when I took the update again, I got service back. I don't recommend it because I may have just been lucky, but no matter what don't flash the gpt, asdspo(?) And bootloader with the older firmware. It'll mess your life up.
Click to expand...
Click to collapse
Hello, as a bigger moron i flashed an older firmware because the networks were going nuts ( mobile data didn't connect even though i had an imei, and wifi and bluetooth just went on and off constantly). Now I don't have IMEI nor wifi(idk why it doen't work to get an ota update). What should I do?
I have a Moto G6 plus RETAR (Argentina) and the new update is not online because it went online today in the morning.
Thank you in advance
PD: I realized this thread is for the moto g6 play, anyway i believe you colud help me, plz I am desesperate
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
Xplorer4x4 said:
You were flashing a gsi not a rom. Even then a rom and even less so a gsi, doesn't contain all the same data as what stock does.
Sent from my Moto G6 Plus using Tapatalk
Click to expand...
Click to collapse
Hello, as a moron i flashed an older firmware because the networks were going nuts ( mobile data didn't connect even though i had an imei, and wifi and bluetooth just went on and off constantly). Now I don't have IMEI nor wifi (idk why it doesn't work, to get an ota update). What should I do?
I have a Moto G6 plus RETAR (Argentina) and the new update is not online because it went online today in the morning.
Thank you in advance
PD: I realized this thread is for the moto g6 play, anyway i believe you colud help me, plz I am desesperat