I'm running a Canadian Pixel on 7.1, I just unrooted so I could do the OTA to 7.1.1.
The update will download but fails while installing.
I'd like to flash the update myself but I'm unsure how. I'm running Ubuntu. Any help?
Thanks!
Sent from my Pixel using XDA-Developers Legacy app
Hi.. is the update like 200+ mb? if so mine does the SAME thing. Mine is (NDE63X) and you WONT find a OTA or a image for 7.1.1. NO clue
Have either of you tried the OTA images from Google's developer site?
Doesn't bootloader have to be locked to take the OTA? Don't do this if your on Verizon veriant.
Konfuzion said:
Doesn't bootloader have to be locked to take the OTA? Don't do this if your on Verizon veriant.
Click to expand...
Click to collapse
NO it doesn't have to be locked. I don't think there is a Verizon variant in Canada either which is what the OP says they have.
I mentioned the Verizon veriant because people other than the OP will read what I posted.
christanya99 said:
I'm running a Canadian Pixel on 7.1, I just unrooted so I could do the OTA to 7.1.1.
The update will download but fails while installing.
I'd like to flash the update myself but I'm unsure how. I'm running Ubuntu. Any help?
Thanks!
Click to expand...
Click to collapse
See below.
Zeblade said:
Hi.. is the update like 200+ mb? if so mine does the SAME thing. Mine is (NDE63X) and you WONT find a OTA or a image for 7.1.1. NO clue
Click to expand...
Click to collapse
Download fastboot from Google and unzip it.
https://developer.android.com/studio/releases/platform-tools.html
Download the latest full factory images from here and unzip it into your fastboot folder. Edit the flashall bat file and remove the -w so you save your apps and data. Run flashall.Bat You will be stock not rooted and no TWRP when you are done. Put back those items if you want.
https://developers.google.com/android/images
You cannot take OTAs directly once you root, even if you completely unroot. You'll need to sideload (or use the edited factory image as in the post above mine). It's not very difficult, there's a nice guide over here: https://forum.xda-developers.com/pixel/how-to/twrp-root-nmf26u-sideload-guide-t3531616
You'll need to re-root/reinstall TWRP if you want to use that functionality again.
Related
First let me thank this community for the MANY years of great help pushing my devices to their limits. I've never register or posted because I've ALWAYS been able to find my answers with a simple search and really never have much to add.
This time I can't find a good answer. I hope this isn't too much of an amateur question.....
I purchased my Pixel via Verizon (I know....) and have unlocked the bootloader and rooted.
I really don't want to mess with custom ROM's for a while and I still want the latest stock version. How do I update to the latest version without losing recovery and root? Example: I updated to 7.1.1 the other day, then wiped, unlocked, installed recovery and rooted. I went back to 7.1 and don't know how to update to 7.1.1 again or other future versions. I hear that flashing stock rom from Google will wipe recovery and root. Is that correct?
Thanks again for all the years of sharing your experiences.
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
foolie said:
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
Click to expand...
Click to collapse
Thanks for the reply. Follow up question after scanning the toolkit description..... I'll look deeper into it in a bit.
This will retain root? Will using adb to sideload lose root?
I think so. You can just reflash SuperSU in recovery :good:
Farmer Tony said:
First let me thank this community for the MANY years of great help pushing my devices to their limits. I've never register or posted because I've ALWAYS been able to find my answers with a simple search and really never have much to add.
This time I can't find a good answer. I hope this isn't too much of an amateur question.....
I purchased my Pixel via Verizon (I know....) and have unlocked the bootloader and rooted.
I really don't want to mess with custom ROM's for a while and I still want the latest stock version. How do I update to the latest version without losing recovery and root? Example: I updated to 7.1.1 the other day, then wiped, unlocked, installed recovery and rooted. I went back to 7.1 and don't know how to update to 7.1.1 again or other future versions. I hear that flashing stock rom from Google will wipe recovery and root. Is that correct?
Thanks again for all the years of sharing your experiences.
Click to expand...
Click to collapse
That's not possible. If you installed the 7.1.1 update you wouldn't have been able to unlock the bootloader again. So you must have had it unlocked before the update.
aholeinthewor1d said:
That's not possible. If you installed the 7.1.1 update you wouldn't have been able to unlock the bootloader again. So you must have had it unlocked before the update.
Click to expand...
Click to collapse
I updated, then decided to root so I factory reset which brought me back to 7.1...... I didn't even know it wouldn't work on 7.1.1 so I guess I was lucky to have done so. I just thought it would be safer to start with a clean slate.
It wasn't until I noticed I could no longer double tap to see notifications that I realized that was only in 7.1.1 and noticed that I couldn't update to it anymore.
Edit: Maybe when I said "wiped" I should have said "factory reset".
foolie said:
I think so. You can just reflash SuperSU in recovery :good:
Click to expand...
Click to collapse
I figured I could do this as a last resort but would love to side load and just go about my day. Nice to know that there wouldn't be an issue, thanks.
I realize this isn't my thread, but... I flashed factory image to my Pixel but the recovery flashing failed. How can I get stock recovery back on so I can take the update?
Crowick said:
I realize this isn't my thread, but... I flashed factory image to my Pixel but the recovery flashing failed. How can I get stock recovery back on so I can take the update?
Click to expand...
Click to collapse
Use the skipsoft toolkit and try again with a new factory image download.
foolie said:
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
Click to expand...
Click to collapse
sorry I'm a total newb, where is the sideload option? I keep looking but don't see it
mrj0087 said:
sorry I'm a total newb, where is the sideload option? I keep looking but don't see it
Click to expand...
Click to collapse
There's a section 'Updating instructions' in the OTA page (linked above) with instructions. Not for the faint of heart if you're unfamiliar with ADB.
It's on the toolkit options after you select your device.
Do you mean you booted into recovery and reflashed because I've actually been wondering almost exactly what you have.
I have a VZW pixel that I unlocked and rooted via adb/fastboot and I've been wonder if accepting a Verizon OTA would unroot me, and relock the bootloader. The 2nd Verizon update as we know disabled depixel and grayed out the option in dev options but do current OTA updates (not images I downloaded myself) unroot and relock which would prevent me from unlocking and getting root again
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
so its safe to say that the new modem ql2 is pretty much the same sa the previous update?
Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse
For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
You will also have to re-flash TWRP via Odon.
kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.
I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.
I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!
purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??
purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:
Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks
So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!
idk where to post this but here goes.
I have a moto g5 plus and it hasn't got the oreo update yet. How can i force it? I tried using the oreo zip file, but the check for updates button did not detect the file. what do i need to do? I dont know much about android and stuff. all i know is that i have a stock rom with android 7.0. everything stock, no warranty.
sakshamgoyal01 said:
idk where to post this but here goes.
I have a moto g5 plus and it hasn't got the oreo update yet. How can i force it? I tried using the oreo zip file, but the check for updates button did not detect the file. what do i need to do? I dont know much about android and stuff. all i know is that i have a stock rom with android 7.0. everything stock, no warranty.
Click to expand...
Click to collapse
never mind. i finally got the update just now.
sakshamgoyal01 said:
never mind. i finally got the update just now.
Click to expand...
Click to collapse
For future reference, when you download a stock update on any device for yourself and want to flash it, the way it gets applied depends on what type of file you download. The files come in a form that is meant to be flashed using a flashtool on PC or a form that is meant to be flashed in stock recovery.
If you get the stock update zip, it can be flashed in stock recovery.
If you get the full stock firmware update file, it can be flashed via PC.
This applies to most, if not all android devices that get updates.
Sent from my LGL84VL using Tapatalk
Ok I downloaded the May ota payload zip and flashed via fastboot in stock recovery
(adb sideload otamay.zip) renamed zip of course.
Absolutely no problems . i didn't have to update any platform tools or anything.
I read platform 33.0 instead of 34.0 ...I haven't updated any adb drivers since 2000.
Note my bootloader is locked no root.
So in case anyone is not aware us non-rooted pixels can update firmware using adb sideload command in stock recovery.
After i flashed the ota.zip my performance got better. Seems the carrier factory software is slower. Even on my Motorola phones i would flash the retail software and remove the carrier software version.
Always a cleaner android experience imo..
Loving my Pixel 7 Pro on Stock no issues...
jhjhjhjhjhjh said:
So in case anyone is not aware us non-rooted pixels can update firmware using adb sideload command in stock recovery.
Click to expand...
Click to collapse
Every Android can be updated via adb sideload using the correct OTA file. That's quite normal. And a full firmware flash would require an unlocked bootloader and not root.
jhjhjhjhjhjh said:
Seems the carrier factory software is slower.
Click to expand...
Click to collapse
you still have the same firmware installed on your device. it's only updated.
WoKoschekk said:
you still have the same firmware installed on your device. it's only updated.
Click to expand...
Click to collapse
True just wasnt clear on pixel devices thought these devices had a different method of things.
Anyways thanks for clearing it up
I guess all pixels share one firmware across all carriers and regions..
jhjhjhjhjhjh said:
I guess all pixels share one firmware across all carriers and regions..
Click to expand...
Click to collapse
No, they have different builds for other carriers/regions. See here. But it's not possible to change the region/carrier version via OTA. You would need a full firmware for that, but it's not recommended and won't have any benefits for you.
Since you are locked and not rooted, why don't you just update from Settings/System/System update?