Hi
I have google pixel 3 xl when I try to update July security patch upadat it's say there's no update my pixel is locked bootloader and no root it's original software and I buy it from Canada unlocked
OTA can take 2 weeks to be pushed to all devices
unlock oem bootloader in DEV options
fastboot
unlock device
flash image
reboot
if you want to keep all settings remove the -w in flash all
pacman photog said:
OTA can take 2 weeks to be pushed to all devices
unlock oem bootloader in DEV options
fastboot
unlock device
flash image
reboot
if you want to keep all settings remove the -w in flash all
Click to expand...
Click to collapse
Or just flash the OTA file using the stock recovery and it won't wipe either.
spotmark said:
Or just flash the OTA file using the stock recovery and it won't wipe either.
Click to expand...
Click to collapse
I found doing that sometimes creates issues with system.
Best to flash new image with -w
pacman photog said:
I found doing that sometimes creates issues with system.
Best to flash new image with -w
Click to expand...
Click to collapse
Hmm, interesting. That's the way I do it all the time. No problems. It's basically the same thing as receiving it OTA. I even installed Q4 that way, but in that case I had to wipe coming from Pie.
pacman photog said:
I found doing that sometimes creates issues with system.
Best to flash new image with -w
Click to expand...
Click to collapse
This method will wipe the device or no
If not can you show me the steps ?
Related
Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
New official TWRP build 3.0.0.1 released: https://dl.twrp.me/bullhead/
bmbm said:
Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
Click to expand...
Click to collapse
Yes. You need to flash the bootloader and radio because they have changed. When in doubt, flash all of them except for user data. I follow Heisenberg's directions (below).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Rozalina340 said:
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Click to expand...
Click to collapse
Won't flash-all also write user data, thereby deleting everything? There's likely a reason that the experts on this forum have never recommended to use flash-all. If you follow Heisenberg's directions, everything will be fine, and you won't lose any data.
Edit: here's something stating that flash-all will erase data unless you modify the command.
http://9to5google.com/2015/10/05/ho...nexus-5-nexus-6-nexus-7-nexus-9-nexus-player/
I didn't know Heisenberg's method doesn't erase user's data. My bad then ^^
Sent from my Nexus 5X using Tapatalk
I've flashed the last two updates using flashfire from chainfire. It injects root during the process so twrp is easily installed using flashify. All without using PC (root is of course required for using flashfire)
Skickat från min Nexus 5X via Tapatalk
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)
cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes
treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?
cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?
cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes
treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.
cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.
cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.
OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.
i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days
I'm going to be exchanging my pixel and getting another one. Just curious so I know for the future.. if I flash the full factory image via fastboot does that relock the bootloader? I'm gonna guess that it doesn't but just wanna make sure.
New to adb and fastboot so I've been reading around like crazy trying to learn. Is the only way to lock again to use the actual lock command in fastboot?
Edit: I'm referring to using the flash-all.bat script
Yes, you will have to re-lock the bootloader. Do it with fastboot in the bootloader.
Although, you don't have to re-lock the bootloader before sending your phone back... Especially since it will have the stock image flashed to it.
aholeinthewor1d said:
if I flash the full factory image via fastboot does that relock the bootloader?
Click to expand...
Click to collapse
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
cam30era said:
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
Click to expand...
Click to collapse
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
canemaxx said:
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
Click to expand...
Click to collapse
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
cam30era said:
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
Click to expand...
Click to collapse
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
canemaxx said:
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
Click to expand...
Click to collapse
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
cam30era said:
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Click to expand...
Click to collapse
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
canemaxx said:
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
Click to expand...
Click to collapse
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
cam30era said:
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
Click to expand...
Click to collapse
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
canemaxx said:
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
Click to expand...
Click to collapse
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
cam30era said:
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
Click to expand...
Click to collapse
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
In fact, on Windows I think you can just double click the flash-all.bat file (I'm on Linux, so I'm not 100% positive). Yes to your other questions. As long as nothing goes wrong.
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
Been here for about 4 minutes, is that normal?
canemaxx said:
Been here for about 4 minutes, is that normal?
Click to expand...
Click to collapse
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
cam30era said:
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
Click to expand...
Click to collapse
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
canemaxx said:
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
Click to expand...
Click to collapse
Very good.
You sure like living on the edge...
cam30era said:
Very good.
You sure like living on the edge...
Click to expand...
Click to collapse
Haha thanks again for all your help!! 7.1.1 installed and root is back!! This may be the last time I get to update my phone for a while lol
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
HaxUrMom69 said:
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
Click to expand...
Click to collapse
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Click to expand...
Click to collapse
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
tactical bacon said:
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
Click to expand...
Click to collapse
This is covered in-depth with FAQ #9 of my link above. But in short, each monthly security update brings a new vendor image that must be installed. Each time your rom updates to a new month's security update, you need to install that vendor image. If you flash back to a previous month's rom, you need to flash that respective vendor image. Only exception is if your rom includes the vendor image in the rom zip.
Sent from my Nexus 5X using Tapatalk
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
tactical bacon said:
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
Click to expand...
Click to collapse
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Click to expand...
Click to collapse
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
tactical bacon said:
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
Click to expand...
Click to collapse
I have my stuff in subfolders inside /sdcard
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
I have my stuff in subfolders inside /sdcard
Click to expand...
Click to collapse
Thanks for the help. I just flashed asop extended and everything works fine. Do you have a recommended ROM for stability?
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
xSpartacusx said:
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
Click to expand...
Click to collapse
Your bootloader, radio and vendor should match whatever ROM you want to flash.
Basically you should flash and boot March stock first, set up and set pin
Download rom, twrp installer zip
Remove screen lock pin
Fastboot boot (twrp.img)
Factory reset
Flash rom + twrp installer
Reboot system
If you want to flash a 9 based ROM like carbonrom you'll have to format userdata and flash and boot August factory image then repeat the steps above
Either way you should learn the fastboot commands and do things manually, it comes in handy updating both slots if needed.
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
xSpartacusx said:
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
Click to expand...
Click to collapse
You'll need to relock your bootloader, just make sure you're full stock on both slots or you will brick your phone. I personally don't think it's worth the risk and just update through twrp or fastboot