Hey guys, bought a pixel 3 from swappa. Got a good deal because it was bootloader unlocked and the guy didn't know how easy it was to fix. Received it today. I had downloaded the June images a few days ago when I bought it. I fastboot -w it first. I then flashed factory images. Let it reboot. Back to fastboot, set to other slot and repeated factory images and-w. All went well. Back to fastboot and locked bootloader. Everything works including Google pay but when I try to update to July via ota or q beta it fails. Every time. What's up?
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Hey guys, bought a pixel 3 from swappa. Got a good deal because it was bootloader unlocked and the guy didn't know how easy it was to fix. Received it today. I had downloaded the June images a few days ago when I bought it. I fastboot -w it first. I then flashed factory images. Let it reboot. Back to fastboot, set to other slot and repeated factory images and-w. All went well. Back to fastboot and locked bootloader. Everything works including Google pay but when I try to update to July via ota or q beta it fails. Every time. What's up?
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
i have the same issue my phone would not update to july nor Q it gives me no valid operating system
could you please write me the followed steps to recover stock
thnaks
eldode said:
i have the same issue my phone would not update to july nor Q it gives me no valid operating system
could you please write me the followed steps to recover stock
thnaks
Click to expand...
Click to collapse
Is your bootloader unlocked? If not you need to try and adb an ota.
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Is your bootloader unlocked? If not you need to try and adb an ota.
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
bootloader is locked
i need it to install ota automatically from system update
i gives me installation error
could you please help me
jmtjr278 said:
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Did you relock bootloader after updating, cause I need Google pay
eldode said:
bootloader is locked
i need it to install ota automatically from system update
i gives me installation error
could you please help me
Click to expand...
Click to collapse
If bootloader is locked you need to download adb and latest ota images. Boot phone into bootloader, go to recovery, hold volume up and press power until menu appears, apply update from adb, open terminal, give the command to sideload ota, adb sideload file_name.zip. Let it do it's thing. Reboot
Sent from my Pixel 3 using Tapatalk
phuzzeeoyster said:
Did you relock bootloader after updating, cause I need Google pay
Click to expand...
Click to collapse
Yes, I relocked bootloader for the same reason
Sent from my Pixel 3 using Tapatalk
Related
Like it has rolled out last night I didn't received it yet. I keep on hitting the "check now" button but still don't see any update for my nexus. How long does it take roll out on each and every device. I'm located in Pakistan.
Sent from my Nexus 5 using XDA Free mobile app
they are rolling out OTA's in phases. first 1% of all the devices get it, and they slowly increase the number of devices to push to.
Just flash the factory images. Quicker than waiting for the ota
factory image wipe out everything... :/
wahur1 said:
factory image wipe out everything... :/
Click to expand...
Click to collapse
That's awesome, be patient
wahur1 said:
factory image wipe out everything... :/
Click to expand...
Click to collapse
Not if you flash each part manually and don't wipe the phone
EddyOS said:
Not if you flash each part manually and don't wipe the phone
Click to expand...
Click to collapse
unlocking bootloader doesn't wipe out everything ? last time i did it wiped out everything.
wahur1 said:
unlocking bootloader doesn't wipe out everything ? last time i did it wiped out everything.
Click to expand...
Click to collapse
Yes if done by fastboot. No if done by app on your phone, but that requires root.
wahur1 said:
unlocking bootloader doesn't wipe out everything ? last time i did it wiped out everything.
Click to expand...
Click to collapse
But if you've already unlocked the bootloader it's not an issue
Other option is download the OTA from the OTA thread and flash it manually in the stock recovery using sideload
EddyOS said:
Not if you flash each part manually and don't wipe the phone
Click to expand...
Click to collapse
EddyOS said:
But if you've already unlocked the bootloader it's not an issue
Other option is download the OTA from the OTA thread and flash it manually in the stock recovery using sideload
Click to expand...
Click to collapse
sideload doesn't wipe out anything ? my phone is completely stock. no root and bootloader is still locked.
wahur1 said:
sideload doesn't wipe out anything ? my phone is completely stock. no root and bootloader is still locked.
Click to expand...
Click to collapse
If you're 100% stock the sideload won't touch any data. It'll be like the OTA was delivered to your phone
lolipop in my nexus havnt come
It has been 3 weeks since i bought my Nexus 5 n my phone is still 4.4.4 kitkat.lolipop hasnt come,,what to do???
uzairzeb98 said:
It has been 3 weeks since i bought my Nexus 5 n my phone is still 4.4.4 kitkat.lolipop hasnt come,,what to do???
Click to expand...
Click to collapse
Sideload it, or wait. That's it! ?
Please help i am trying to flash stock rom but i am getting remote failure error
anujdevrani said:
Please help i am trying to flash stock rom but i am getting remote failure error
Click to expand...
Click to collapse
Bootloader unlocked?
acejavelin said:
Bootloader unlocked?
Click to expand...
Click to collapse
is unlocking the bootloader required for flashing stock rom???
anujdevrani said:
is unlocking the bootloader required for flashing stock rom???
Click to expand...
Click to collapse
Not if it's the identical version... Although the error your receiving is common when this is the case.
Can you give a screenshot of the flash attempt from start to finish?
Sent from my MotoG3 using Tapatalk
acejavelin said:
Not if it's the identical version... Although the error your receiving is common when this is the case.
Can you give a screenshot of the flash attempt from start to finish?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
It came with the lollipop version.. Now i am trying to flash the mm one...currently i have the mm one installed on the device but its not booting up
But mm has two builds available 6.0 and 6.0.1... I am not sure which one is currently installed... However the one i am trying to flash is 6.0.1
anujdevrani said:
It came with the lollipop version.. Now i am trying to flash the mm one...currently i have the mm one installed on the device but its not booting up
Click to expand...
Click to collapse
The version it shipped with not relevant, you must use the same version that is currently installed.
Were you able to successfully flash? Did you do the factory reset before starting the process (boot will fail if you don't)?
Sent from my MotoG3 using Tapatalk
acejavelin said:
The version it shipped with not relevant, you must use the same version that is currently installed.
Were you able to successfully flash? Did you do the factory reset before starting the process (boot will fail if you don't)?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
How do i reset the phone.... I am unable to boot to recovery
..
anujdevrani said:
How do i reset the phone.... I am unable to boot to recovery
..
Click to expand...
Click to collapse
If the bootloader is locked (and oem unlocking was not previously enabled), you can't start recovery, and you can't flash the identical version via fastboot... Your device is bricked and needs to be repaired/replaced by Moto. You should contact their customer service.
Sent from my MotoG3 using Tapatalk
acejavelin said:
If the bootloader is locked (and oem unlocking was not previously enabled), you can't start recovery, and you can't flash the identical version via fastboot... Your device is bricked and needs to be repaired/replaced by Moto. You should contact their customer service.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Okk... I guess i have to now.
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
SpitFire727 said:
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
Click to expand...
Click to collapse
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
SpitFire727 said:
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
i removed a bunch of bloatware. mostly sprint junk
SpitFire727 said:
i removed a bunch of bloatware. mostly sprint junk
Click to expand...
Click to collapse
Then an OTA may fail, depending on what the update script checks for. I would flash back to pure stock to be safe.
Sent from my Motorola XT1575 using XDA Labs
i don't have a pre rooted backup :/
SpitFire727 said:
i don't have a pre rooted backup :/
Click to expand...
Click to collapse
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
could you walk me through all the steps i need too take?
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
moving discussion to Q&A..
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so i did all the steps, i updated too 6.1. but now i face a new problem, no devices are found in adb when in boot loader mode. it is detected while the phone is started up though.. in the progress of trying too fix this.
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
SpitFire727 said:
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
Click to expand...
Click to collapse
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
acejavelin said:
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
Click to expand...
Click to collapse
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
SpitFire727 said:
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
Click to expand...
Click to collapse
The TWRP img file needs to be on the computer in the fastboot directory. Start the bootloader and type 'fastboot devices' to make sure the device is recognized, then 'fastboot boot twrp.img' (remember to use the actual filename in place of twrp.img)
Sent from my Motorola XT1575 using XDA Labs
Make sure you don't update to 7.1.1 on a locked bootloader for the Verizon model otherwise, the depixel8 exploit will no longer work. It was confirmed by the developers of it already as you can check at their site and see as well. Now me personally I enjoy stock so I don't care but I figured for people with the Verizon model like me would care to see this.
Do not attempt to downgrade or any other methods of rooting until you see a tested and working method by one of the XDA devs in the Android Development forums for the Pixel.
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
macboss said:
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
Click to expand...
Click to collapse
If you're unlocked it shouldn't have re-locked it?
Sent from my Pixel using Tapatalk
macboss said:
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
Click to expand...
Click to collapse
I'm pretty sure the boot to root doesn't work with TWRP. Use a factory image if possible and try to install TWRP and use the SuperSU zip instead.
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
joshw0000 said:
If you're unlocked it shouldn't have re-locked it?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing... The update in general wouldn't have gone through if it was rooted.
so how do I update if I'm unlocked and have twrp installed? I'm assuming I shouldn't take the OTA update?
Bought my pixel from the Google store. Pixels from the Google store, are the bootloader's locked or unlocked?
Sent from my Pixel XL using Tapatalk
They are locked upon purchasing however, you can easily unlock them.
jreink01 said:
Bought my pixel from the Google store. Pixels from the Google store, are the bootloader's locked or unlocked?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Archangel said:
They are locked upon purchasing however, you can easily unlock them.
Click to expand...
Click to collapse
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Sent from my Pixel XL using Tapatalk
jreink01 said:
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Click to expand...
Click to collapse
If you are have a phone from Verizon it is required to have unlocked bootloader to obtain root.
So if it is a Verizon phone and you take 7.1.1 update - you won't be able to get root
km8j said:
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
Click to expand...
Click to collapse
Yes
Sent from my Pixel using Tapatalk
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
mrj0087 said:
so how do I update if I'm unlocked and have twrp installed? I'm assuming I shouldn't take the OTA update?
Click to expand...
Click to collapse
I side loaded the OTA and went through the process again have twrp and root
Sent from my Pixel using Tapatalk
I bought my device from UK, i got it unlocked and rooted but without TWRP recovery, what is the best option for me to install the update ?
And does it erase my device ?
Thanks in advace ...
I'm running Build : NDE63V
guandms said:
I bought my device from UK, i got it unlocked and rooted but without TWRP recovery, what is the best option for me to install the update ?
And does it erase my device ?
Thanks in advace ...
I'm running Build : NDE63V
Click to expand...
Click to collapse
With an unlocked BL, you're pretty free to do whatever you want. I've done it multiple ways; to me, the most straightforward steps are:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Enjoy!
km8j said:
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
Click to expand...
Click to collapse
Yes, but just reroot. Works fine.
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
jreink01 said:
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
On a Google Store pixel, you can always unlock your bootloader. You are posting in a vzw pixel revelent thread, depixel8 and any talk on the subject doesn't apply. Don't get confused.
Sorry, didn't know i was in a Verizon thread.
Sent from my Pixel XL using Tapatalk
epic4grooted said:
Yes
Sent from my Pixel using Tapatalk
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
I side loaded the OTA and went through the process again have twrp and root
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Sorry I'm confused. So use adb side load in twrp? So I'm doing adb reboot recovery then adb side load OTA.zip once in twrp? Then I have to reflash twrp and root?
Download the OTA zip from Google run flash all it then go through the steps to reroot and install twrp
Sent from my Pixel using Tapatalk
I unlocked the BL using dePixel8 last Wed. when I picked up my Pixel. It updated to NDE63X via OTA after I unlocked BL. Received OTA update to NMF260, downloaded and installed it last night via normal OTA process. BL unlock is unchanged: unlocked status.
It helps if the phone is plugged in and on WiFi since it is a 260MB download.
So far 7.1.1 works great.
epic4grooted said:
Download the OTA zip from Google run flash all it then go through the steps to reroot and install twrp
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
got it
Brand new Pixel 2. Unlocked bootloader and rooted with Magisk with no issues. Decided to return the phone. Booted into fastboot and ran the command to lock the bootloader and got stuck in fastboot with an error that I forgot to write down. I tried to reboot and now I'm just stuck on the white screen with the Google logo and the loading bar going on the bottom. I am able to boot back into bootloader.
Any ideas?
Thanks
Flash factory image and make sure your platform tools is updated i.e. adb and fastboot.
Sent from my walleye using XDA Labs
dobbs3x said:
Flash factory image and make sure your platform tools is updated i.e. adb and fastboot.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.
Even trying to sideload the OTA I get an error that the bootloader is the wrong version.
Ok, so now tried unlocking the bootloader again but still the same error that it's the wrong bootloader version.
thenags said:
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.[/QUOTE
You should post those errors here, they will help.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse
dobbs3x said:
thenags said:
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.[/QUOTE
You should post those errors here, they will help.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse
This is what I'm getting no matter what I do;
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
I'm currently trying this;
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
The script from that thread actually got me booting again but with bootloader unlocked. Let's see if I can lock it without it breaking again.
Alright. Back in action.
Thanks dobbs3x for the moral support lol.
For anyone in the future with a similar issue go to this thread and follow the steps;
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761