Related
Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
CatThief said:
[solved] Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
Click to expand...
Click to collapse
There's actually 4 different builds.
See here for what's what
Yep, I did that. There is no description there for "N" but I found out "B" is the one I want.
I always get Failed to udate, try again when installing the ota via settings.
Juli112 said:
I always get Failed to udate, try again when installing the ota via settings.
Click to expand...
Click to collapse
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
alluringreality said:
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
Click to expand...
Click to collapse
Did you update already. I read somewhere since the may update that if you have bootloader unlocked, rooted, and another kernel you get bootloops?
Is that true? I'm still on April security update and been using stock rom, just unlocked bootloader, rooted, and using elementalx kernel
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
alluringreality said:
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
Click to expand...
Click to collapse
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Nope. twrp.img must be firstly boot into the phone, then via this temporary twrp,you can install twrp.zip from your phone.
kazemitsui said:
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
CatThief said:
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
Click to expand...
Click to collapse
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
TENN3R said:
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I used twrp-3.0.2-0-RC1-fastboot-sailfish.img because it was the only version that was stable for me from the start. When the January update came out I tried the current TWRP at that time (it was an RC3, can't remember the version) and while others had no problems I had an experience of my own that I'm not keen on repeating.
As for SuperSU, I installed SR5-SuperSU-v2.78-SR5-20161130091551.zip then updated to the latest 2.82 from Google Play.
I know, newer releases may work now, but I was only going to try something newer if my "old" method failed. Like I said, I only boot to TWRP, I don't flash it. I just want root.
kazemitsui said:
i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
TENN3R said:
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
alluringreality said:
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
Click to expand...
Click to collapse
I just flashed TWRP through my computer I couldn't bother trying to figure out if FlashFire will flash TWRP or not haha
So i just got a Pixel 2 and got it rooted last night and moved all my stuff over before realizing i can get 8.1. I tried to get the latest stock from google but when i tried to run the .bat file (after removing the -w to prevent wiping) it started then failed saying something about needing something with a 59 in the file and the one i was using had 69.
Is there another way to do it? like unrooting, taking the OTA then rerooting? right now it says "couldnt update, installation problem". Is this from usign magisk? i know in the past id have to freeze the ota with TiBu.
mainly just looking for a way to get 8.1 without loosing all my stuff and having to copy it all back again.
Are you trying to skip some of the monthly updates?
Some believe the updates to be incremental, others do not. Update to the next month's update from the one you're on, until you're to the current June update.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Are you trying to skip some of the monthly updates?
Some believe the updates to be incremental, others do not. Update to the next month's update from the one you're on, until you're to the current June update.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
oh ****, theres no better way? thats over 10gb of files
So I just went through this. I bought my pixel 2 and updated from the September to November builds via flash. Then I got lazy and got a little behind on my updates.
There was something about the transition to 8.1 (December) that got a little wonky with regard to successfully flashing the bootloader.
What I did was I downloaded the December OTA update 8.1.0 (OPM1.171019.011, Dec 2017) and flashed that directly through "Apply Update through ADB"
Once that OTA has been flashed factory images such as the most recent one you were trying to flash should work. I successfully went directly from December to May. Just remember to remove the "-w" flag from the .bat file to avoid the wipe.
You won't lose all your stuff but you will need to re-root by flashing and installing Magisk.
The instructions from this thread are good:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Hope this helps.
Best,
JasonVaritekMVP said:
So I just went through this. I bought my pixel 2 and updated from the September to November builds via flash. Then I got lazy and got a little behind on my updates.
There was something about the transition to 8.1 (December) that got a little wonky with regard to successfully flashing the bootloader.
What I did was I downloaded the December OTA update 8.1.0 (OPM1.171019.011, Dec 2017) and flashed that directly through "Apply Update through ADB"
Once that OTA has been flashed factory images such as the most recent one you were trying to flash should work. I successfully went directly from December to May. Just remember to remove the "-w" flag from the .bat file to avoid the wipe.
You won't lose all your stuff but you will need to re-root by flashing and installing Magisk.
The instructions from this thread are good:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Hope this helps.
Best,
Click to expand...
Click to collapse
awesome, thanks! ill check it out
also, off topic, how do you get into twrp? doing the volume down and power just takes you to the bootloader screen and going to recovery ends up just leading to the stock recovery. I had to fastboot into twrp to get back. It also wouldnt let me backup which is an whole different issue.
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
vaeevictiss said:
awesome, thanks! ill check it out
also, off topic, how do you get into twrp? doing the volume down and power just takes you to the bootloader screen and going to recovery ends up just leading to the stock recovery. I had to fastboot into twrp to get back. It also wouldnt let me backup which is an whole different issue.
Click to expand...
Click to collapse
JasonVaritekMVP said:
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
Click to expand...
Click to collapse
yea that looks different. i just installed the twrp zip file from inside twrp.
and i dont need to unroot first right? this does it automatically?
JasonVaritekMVP said:
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
Click to expand...
Click to collapse
EDIT: Scratch that. i ended up just doing that sideload of the ota like you suggested and im good to go now!
thanks again!
deleted, not needed
Hey xda,
I'm on a new P3 on build pd1a.180720.030 and following this guide here: XDA Root Guide and after installing the Magisk installer zip script I get stuck on the Google Logo screen. So after that I tried flashing the boot.img from the factory image to no avail and ended up having to do a flash-all . Now don't want to go down that road again, so has anyone found what is wrong or needs to be updated about this guide?
This might need to be moved to Q&A
For anyone in the same position, I took the OTA for November, and after I booted into TWRP using the .img, before I opted to keep System Read Only, this time I chose to Allow Modifications. It worked this time!
FUZER384 said:
Hey xda,
I'm on a new P3 on build pd1a.180720.030 and following this guide here: XDA Root Guide and after installing the Magisk installer zip script I get stuck on the Google Logo screen. So after that I tried flashing the boot.img from the factory image to no avail and ended up having to do a flash-all . Now don't want to go down that road again, so has anyone found what is wrong or needs to be updated about this guide?
Click to expand...
Click to collapse
I'm in the same situation. Any solutions?
neoss119 said:
I'm in the same situation. Any solutions?
Click to expand...
Click to collapse
Are you on Sep or November build?
Sent from my Pixel 3 using Tapatalk
I was on December build. I figured it out, you need to have a pass-code before installing/entering recovery. At least that's what the guide from Pixel 3 XL says. After having a pass-code it worked.
I didn't a passcode, after I got off the G screen logo by doing a flash-all from the December build (you can remove the -w if you don't want to wipe data) I went through the process again. When you boot into TWRP with the img, Make sure to Allow System Mod instead of Keep read Only. Then just install Magisk
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
Here you go.
https://developers.google.com/android/images
More info:
https://support.google.com/pixelphone/thread/27557681?hl=en
Does anyone have the boot.img available (for Magisk purposes)? Thanks
vonDubenshire said:
Does anyone have the boot.img available (for Magisk purposes)? Thanks
Click to expand...
Click to collapse
You don't need it follow the thread about updating and keeping root.
https://forum.xda-developers.com/pixel-4-xl/how-to/guide-update-retain-root-t4003839
vonDubenshire said:
Does anyone have the boot.img available (for Magisk purposes)? Thanks
Click to expand...
Click to collapse
Boot.img is always nested in the image file. Just extract it, transfer to your phone and patch. There is another thread for those who cannot, or do not want to patch their own.
wolfu11 said:
You don't need it follow the thread about updating and keeping root.
https://forum.xda-developers.com/pixel-4-xl/how-to/guide-update-retain-root-t4003839
Click to expand...
Click to collapse
I've tried that method previously and it didn't work for me. I just extract the boot.img, patch it then flash it. It only takes a few minutes.
I didn't lose root & yeah thanks for the extraction tip -- I have just barely been on and wondered if anyone had it ready to go when I had five minutes to sit & flash.
Thanks for all that tho lol.
I will wait for a patched boot.img because if I do it it never work and stuck on boot logo.
Stupid question:
Coming from a Nexus 6 my ol' Shamu hasn't got a monthly update and I've been flashing custom ROMs for so long I've forgotten. Does Google post the update that I can install or do I just need to follow the guide to reinstall the unpatched boot.img and wait to take it directly to my phone?
TIA
swear0730 said:
Stupid question:
Coming from a Nexus 6 my ol' Shamu hasn't got a monthly update and I've been flashing custom ROMs for so long I've forgotten. Does Google post the update that I can install or do I just need to follow the guide to reinstall the unpatched boot.img and wait to take it directly to my phone?
TIA
Click to expand...
Click to collapse
Yes, Google post an update you can install.