Related
Ok, let me start by saying that I'm fully capable of updating my phone with a computer, I'm just hoping there is a better way. So far every time I've downloaded a new firmware, update the flash-all.bat and run it, something will fail towards the end of the update and the only way I've been able to successfully update is by using one of those tool kits (forget which one, it's on my computer). I'm not that concerned about all of that with this thread. I'm wondering if there is a way to do it without a PC.
I'm on NMF26O (root, ElementalX, etc) and tried flashing Pure Nexus over the weekend. Since it's based on NMF26V, I kept receiving an error on boot about updating my vendor.img. So I downloaded that firmware, extracted it, and flashed the vendor.img in TWRP. That led to a plethora of other issues that I couldn't resolve by flashing the boot.img, reflashing the rom, ect. Several hours later I ended up flashing the boot.img and vendor.img for NMF26O, restoring my backup, re-installing Elemental, and rooting again.
Since these updates will be coming out every month, and roms will always be based on the latest update, I feel like I'll be pulling out the computer every month, downloading the updates, modifying the flash-all.bat, and running it through the tool, just to be able to update my rom. The first time I forget to update flash-all.bat, I'll lose the 60+ GB's I keep in internal storage. There has to be an easier way. TWRP is capable of flashing images. Has anyone been able to update without using a computer? I don't care if my radio is out dated, or something is mismatched as long as my phone works as intended.
Sent from my Pixel using Tapatalk
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
aholeinthewor1d said:
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
Click to expand...
Click to collapse
I'm on NMF26O. What's the difference between it and NMF26U and why would the vendor image from NMF26V work with NMF26U but not NMF26O?
Seems like all you would need is the /system from the rom, the vendor image, and maybe the boot image (or a custom kernel). I think I'm missing something here.
Sent from my Pixel using Tapatalk
If you install PN its based on NMF26V. So unless you are already on that then you would need to flash the ROM, reboot back to recovery, then flash the NMF26V vendor image.
I'll play devil's advocate here... Yeah there is an easier way, use your Pixel stock and take OTA's. Enjoy a phone that always works, with or without a laptop!
I understand my audience and realize this isn't a popular mantra here but I felt exactly like you did with my 6p and vendor images. I got to the point where I sacrifice root now just for my own sanity. My phone works for me, not the other way around.
What I do is side load the full OTA ( which you can get from the same place you get the factory images ). I only use the fastboot boot version of TWRP so that my stock recovery stays in place. Then all you have to do is boot into the stock recovery, adb side load the OTA file and re root. Then you're fully up to date without worries of your data being wiped :laugh:!
( Although if you look in the flash fire thread from Chainfire, he's working on a version that will let rooted pixels flash otas like normal ones :fingers-crossed: )
I think you guys are missing the point. I have no desire to ever be stock, which rules out the possibility for an OTA in any form.
What I'm trying to figure out is exactly what is necessary to make a custom rom (based on the latest OTA), work if flashed over an older build, without first somehow applying the full OTA. Or is it impossible?
On just about every other phone I've owned, we could piecemeal the files needed for minor updates, along with a custom rom. The only time we'd have to flash a full update is for major updates ( 4 to 5 to 6, etc).
Sent from my Pixel using Tapatalk
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Sent from my Pixel using Tapatalk
joshw0000 said:
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Click to expand...
Click to collapse
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
aholeinthewor1d said:
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
Click to expand...
Click to collapse
I've done it several times tonight. Went from O to U to V, flashed Pure Nexus, screwed up the rom, restored to O, then O flashed back to U and V.
Just flash it like a rom in TWRP RC1. Make sure you flash TWRP again before rebooting if you want to keep it.
Sent from my Pixel using Tapatalk
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
bradld said:
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
Click to expand...
Click to collapse
After flashings the ROM; do you reboot to recovery before you flash the mods? You need to either reboot to recovery or boot to the system at least once before flashing any mods. When you flash a ROM, it gets flashed to the slot that is currently inactive. The mods will get flashed to slot the is currently the active slot. So, if you don't reboot before you flash the mods, they get flashed to the wrong slot. That's about the only thing I can think of that would cause this issue.
robocuff said:
After flashings the ROM; do you reboot to recovery before you flash the mods? You need to either reboot to recovery or boot to the system at least once before flashing any mods. When you flash a ROM, it gets flashed to the slot that is currently inactive. The mods will get flashed to slot the is currently the active slot. So, if you don't reboot before you flash the mods, they get flashed to the wrong slot. That's about the only thing I can think of that would cause this issue.
Click to expand...
Click to collapse
Yes, have rebooted to recovery numerous times. Zips appear to flash and on reboot to ROM, nothing! Zips with save log features return an error as if nothing is writing to memory.
I have returned to factory image and repeated everything, no change.
I have only booted to TWRP for installing zips, and I haven't installed TWRP on my phone. When booting TWRP RC1, I've had it fail to install zips multiple times. I think the times it failed I didn't get the initial opening information. Honestly I didn't look into it very much, because I just booted Alpha 2, and that installs zips just fine when RC1 doesn't work for me. If someone has rooted their phone, I think FlashFire can probably also install zips.
bradld said:
I recently purchased a Verizon Pixel and successfully unlocked it, installed TWRP RC1, ROM and EX Kernel. I notice, however, that I cannot flash any other zips such as Viper4Android, WETA, etc. This makes no sense to me but after trying to flash these other zips (all of which say successful) nothing is ever installed after a reboot and files do not appear in the expected directory locations. Anyone have any idea what I am missing? I have never seen anything like this before.
Thanks!
Click to expand...
Click to collapse
If you flash a mod from a flash made specially for Pixel, it should work. Other zips will not because the system files for the Pixel are in system/system, not just system.
I have a Shield Tablet (post battery fire exchange) and I would like to update it to the newest firmware/os... It is currently rooted, running BitO-Kernel, and stock nvidia rom. I did all the rooting and flashing on this tablet originally, but I never kept it up to date with newer updates. I heard on this forum awhile back that it's not just as simple as flashing a new rom, something about having to flash some other system stuff first or some partition or something. Basically I'm looking for a guide on how to update a Shield Tablet from rooted 5.1.1 to the newest OS version avalible. I tried sreaching the forum, but I couldn't find what I was looking for (maybe I'm not using the right search keyworks).
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20wifi&tx=$additional,shield
redpoint73 said:
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet wifi&tx=$additional,shield
Click to expand...
Click to collapse
Thanks I appreciate the help! Yes it's an original tablet (not the k1). It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root. I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
https://forum.xda-developers.com/shield-tablet/help/how-update-rooted-shield-tablet-to-t3355436
bluegizmo83 said:
It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root.
Click to expand...
Click to collapse
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
bluegizmo83 said:
I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
Click to expand...
Click to collapse
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
redpoint73 said:
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
Click to expand...
Click to collapse
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works. After that, I should be able to flash any current update (like 6.0) also, correct? And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
bluegizmo83 said:
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works.
Click to expand...
Click to collapse
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!
bluegizmo83 said:
After that, I should be able to flash any current update (like 6.0) also, correct?
Click to expand...
Click to collapse
Correct.
bluegizmo83 said:
And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
Click to expand...
Click to collapse
Not 100% sure. It's a full OTA zip, not an incremental update. So in those cases (full OTA) it may not need the preceding update installed. But again, I'm not sure.
redpoint73 said:
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!.
Click to expand...
Click to collapse
Ok thanks again, I appreciate all the help! One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
bluegizmo83 said:
One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
Click to expand...
Click to collapse
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
redpoint73 said:
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
Click to expand...
Click to collapse
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
bluegizmo83 said:
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
Click to expand...
Click to collapse
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
redpoint73 said:
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
Click to expand...
Click to collapse
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
bluegizmo83 said:
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
Click to expand...
Click to collapse
I'm not sure if it matters with the OTA. My feeling is, that it won't matter, and it will still install.
My guess is that in the worst case, the OTA fails, and you have to resort to flashing the recovery OS version.
Hi everyone,
First of all excuse my ignorance. I came from flashing ROM's on the EVO where you could push one button and have root, unlock bootloader, and use ROM Manager to flash custom ROM's.
Now, there's A/B slot.. you have to have a certain version of OOS already on the phone, or flash it twice or some such? Like wtf?
Can someone tell me how to simply install a good custom ROM (I'm on stock Pie right now- OOS). I liked Pixel experience but maybe because it's AOSP it always bricks my phone and I have to use the tool to restore it to stock. Either that, or the phone just boots into stock OOS after a flash like it's not holding the custom ROM. Help
Thanks
Follow instructions in individual ROM thread.
People won't help you here. I still haven't gotten it to work. What ROM do you want to flash?
klym.software said:
People won't help you here. I still haven't gotten it to work. What ROM do you want to flash?
Click to expand...
Click to collapse
lol I see a lot of "that's already been discussed" or "google it..." I'm perfectly capable of performing all of the necessary steps, it's just this A/B shi* that is messing everything up. If someone could kindly instruct me how to flash OOS (since apparently that's what needs to be done) to both slots so that when I flash a custom ROM it will work, I would appreciate it.
And right now I'm trying with Havoc because it's 'Stable' but I also tried Pixel Experience
mikex8593 said:
Follow instructions in individual ROM thread.
Click to expand...
Click to collapse
Unfortunately they don't explain how to flash OOS to both slots, they simply say it needs to be done. And not all of them even say that, even though apparently it's necessary.
Vonsk said:
lol I see a lot of "that's already been discussed" or "google it..." I'm perfectly capable of performing all of the necessary steps, it's just this A/B shi* that is messing everything up. If someone could kindly instruct me how to flash OOS (since apparently that's what needs to be done) to both slots so that when I flash a custom ROM it will work, I would appreciate it.
And right now I'm trying with Havoc because it's 'Stable' but I also tried Pixel Experience
Click to expand...
Click to collapse
There are at least 3 different ways to flash a ROM, and when people give instructions they never specify which method they do it with. They also don't specify how they switch partitions and it leaves people like us with bricked devices
klym.software said:
There are at least 3 different ways to flash a ROM, and when people give instructions they never specify which method they do it with. They also don't specify how they switch partitions and it leaves people like us with bricked devices
Click to expand...
Click to collapse
AMEN. For f sake.. my phone has been bricked twice and I had to MSM it. Things used to be easy back with the EVO.. Now it's like people take pride in being secretive. Do I flash the flash-all thing with vendor and everything to both slots, or just download an OOS zip or what lol
Vonsk said:
AMEN. For f sake.. my phone has been bricked twice and I had to MSM it. Things used to be easy back with the EVO.. Now it's like people take pride in being secretive. Do I flash the flash-all thing with vendor and everything to both slots, or just download an OOS zip or what lol
Click to expand...
Click to collapse
I would give my left nut for a step by step clean treskmod install
To flash on both partitions, yo have to go to TWRP and the main menu, select "Reboot" and below all option you have "slot a" and "slot b" if you click on one of them, you switch the slot and you can Flash stuff on that slot.
JuanMnz93 said:
To flash on both partitions, yo have to go to TWRP and the main menu, select "Reboot" and below all option you have "slot a" and "slot b" if you click on one of them, you switch the slot and you can Flash stuff on that slot.
Click to expand...
Click to collapse
Bless your sweet ass!
I did that, and then ran the flash-all to get OOS on both slots... Do you know if I need to now flash the OTA or anything more complicated, or can I just start doing custom ROMs now?
EDIT: Phone now bricked again after flashing OOS to other slot. Used the same one to flash to B and it was fine, and made sure to reset userdata.. Man, what a headache. I'm gonna throw in the towel unless someone else has an easy answer for this.
try this. go to recovery, select install, choos OOS, then dont flash yet select add zip and select blu twrp. flash. after its done, press the home button (below) the select reboot, choose recovery (this will boot you to slot b) select install again then, OOS, add zip, select blu then flash.
you can also do wipe in advance before you do the steps above. hope this help
Vonsk said:
lol I see a lot of "that's already been discussed" or "google it..." I'm perfectly capable of performing all of the necessary steps, it's just this A/B shi* that is messing everything up. If someone could kindly instruct me how to flash OOS (since apparently that's what needs to be done) to both slots so that when I flash a custom ROM it will work, I would appreciate it.
And right now I'm trying with Havoc because it's 'Stable' but I also tried Pixel Experience
Click to expand...
Click to collapse
Coming from a custom rom named havoc os, here are the onstructions to install this rom, though, I am not sure about other custom roms. First, let me explain what the A/B slots are and how they function. A/B slots exist because they are needed to support seamless updates: If you have a rom booted, obviously, you couldn't flash over the system partition which you have booted, so, the system updater flashes the update to the second system slot and after a reboot, it simply switches the boot slot. Now, with the instructions : To flash OOS firmware to both slots, boot twrp, flash the oos zip that your rom fw is based on (for havoc os it's OB7), after you flash that, flash twrp installer zip and reboot recovery, flash the same oos zip again and flash twrp installer zip again. Reboot recovery again, wipe data and flash the rom zip. After the rom zip file has been flashed, flash twrp installer again and reboot recovery. After that, flash gapps and magisk and reboot system. Enjoy!
Hi,
I have a question about a/b boot partitions/boot slots since i recently reverted to stable October build, from QPR1 beta 3 by manually flashing factory image with flash all script. I unrolled the beta and got an OTA that was supposed to install latest stable October build, but instead it just factory reset my phone with the beta build still installed, so the OTA must have failed. Because of this, i thought that the safest way to return to "stock" was to unlock the bootloader and perform a manual flash of factory image instead.
I did that without any problems and are again running latest October with a re-locked bootloader, but then i read somewhere that people are flashing both partitions with the flash all script. Meaning, running flash all script on active boot slot, then manually changing boot slot and then running flash all script again.
Is this necessary? Should i also do this if i want to be on "the safe side", or does the flash all script flash both slots at the same time?
tap77 said:
Hi,
I have a question about a/b boot partitions/boot slots since i recently reverted to stable October build, from QPR1 beta 3 by manually flashing factory image with flash all script. I unrolled the beta and got an OTA that was supposed to install latest stable October build, but instead it just factory reset my phone with the beta build still installed, so the OTA must have failed. Because of this, i thought that the safest way to return to "stock" was to unlock the bootloader and perform a manual flash of factory image instead.
I did that without any problems and are again running latest October with a re-locked bootloader, but then i read somewhere that people are flashing both partitions with the flash all script. Meaning, running flash all script on active boot slot, then manually changing boot slot and then running flash all script again.
Is this necessary? Should i also do this if i want to be on "the safe side", or does the flash all script flash both slots at the same time?
Click to expand...
Click to collapse
I believe it flashes your inactive partition and then boots to that. That way there is one good partition to boot from if the flash or ota fails in some way. I just flash the update twice if I want to make sure both are the same.
Misterxtc said:
I believe it flashes your inactive partition and then boots to that. That way there is one good partition to boot from if the flash or ota fails in some way. I just flash the update twice if I want to make sure buth are the same.
Click to expand...
Click to collapse
This makes sense
Misterxtc said:
I believe it flashes your inactive partition and then boots to that. That way there is one good partition to boot from if the flash or ota fails in some way. I just flash the update twice if I want to make sure both are the same.
Click to expand...
Click to collapse
By the way, when you say you flash the same update twice, do you mean sideload from recovery over adb the second time?
tap77 said:
By the way, when you say you flash the same update twice, do you mean sideload from recovery over adb the second time?
Click to expand...
Click to collapse
Either one should result the same in the end. I just found it easier to run the flash all script.
tap77 said:
Hi,
I did that without any problems and are again running latest October with a re-locked bootloader, but then i read somewhere that people are flashing both partitions with the flash all script. Meaning, running flash all script on active boot slot, then manually changing boot slot and then running flash all script again.
Is this necessary? Should i also do this if i want to be on "the safe side", or does the flash all script flash both slots at the same time?
Click to expand...
Click to collapse
It isn't necessary but if you want to insure your inactive slot (and therefore both slots) is bootable in case you run into trouble for some reason, then flashing the factory image to the inactive slot will take care of that. If you don't do a lot of flashing or modding, it's probably unnecessary. And if next month you update via OTA, it will put the new build on the opposite slot anyway so you don't have to worry about it. Both slots will be ensured to be bootable.
Additionally, if when you got your phone you took the 0 day OTA, then you will already have a build on both slots.
The way it works is, If you take an OTA or sideload an OTA, that will put the build you are installing on the inactive slot. Flashing the factory image via fastboot, however, does not flash the build to the inactive slot. It only flashes the build to your active and current slot. That's why you see people who want to do what you are asking about switch slots and then flash the factory image again.
Btw, Pixel Flasher has the ability to flash to both slots.
In the end, since you re-locked bootloader and, I'm guessing (?), will just update next month via OTA, you really shouldn't need to worry about doing anything.
Lughnasadh said:
It isn't necessary but if you want to insure your inactive slot (and therefore both slots) is bootable in case you run into trouble for some reason, then flashing the factory image to the inactive slot will take care of that. If you don't do a lot of flashing or modding, it's probably unnecessary. And if next month you update via OTA, it will put the new build on the opposite slot anyway so you don't have to worry about it. Both slots will be ensured to be bootable.
Additionally, if when you got your phone you took the 0 day OTA, then you will already have a build on both slots.
The way it works is, If you take an OTA or sideload an OTA, that will put the build you are installing on the inactive slot. Flashing the factory image via fastboot, however, does not flash the build to the inactive slot. It only flashes the build to your active and current slot. That's why you see people who want to do what you are asking about switch slots and then flash the factory image again.
Btw, Pixel Flasher has the ability to flash to both slots.
In the end, since you re-locked bootloader and, I'm guessing (?), will just update next month via OTA, you really shouldn't need to worry about doing anything.
Click to expand...
Click to collapse
Thanks for the clarification I wasn't 100% positive on the OTA flash vs fastboot.
Lughnasadh said:
It isn't necessary but if you want to insure your inactive slot (and therefore both slots) is bootable in case you run into trouble for some reason, then flashing the factory image to the inactive slot will take care of that. If you don't do a lot of flashing or modding, it's probably unnecessary. And if next month you update via OTA, it will put the new build on the opposite slot anyway so you don't have to worry about it. Both slots will be ensured to be bootable.
Additionally, if when you got your phone you took the 0 day OTA, then you will already have a build on both slots.
The way it works is, If you take an OTA or sideload an OTA, that will put the build you are installing on the inactive slot. Flashing the factory image via fastboot, however, does not flash the build to the inactive slot. It only flashes the build to your active and current slot. That's why you see people who want to do what you are asking about switch slots and then flash the factory image again.
Btw, Pixel Flasher has the ability to flash to both slots.
In the end, since you re-locked bootloader and, I'm guessing (?), will just update next month via OTA, you really shouldn't need to worry about doing anything.
Click to expand...
Click to collapse
Thank you for the clarification!
Lughnasadh said:
It isn't necessary but if you want to insure your inactive slot (and therefore both slots) is bootable in case you run into trouble for some reason, then flashing the factory image to the inactive slot will take care of that. If you don't do a lot of flashing or modding, it's probably unnecessary. And if next month you update via OTA, it will put the new build on the opposite slot anyway so you don't have to worry about it. Both slots will be ensured to be bootable.
Additionally, if when you got your phone you took the 0 day OTA, then you will already have a build on both slots.
The way it works is, If you take an OTA or sideload an OTA, that will put the build you are installing on the inactive slot. Flashing the factory image via fastboot, however, does not flash the build to the inactive slot. It only flashes the build to your active and current slot. That's why you see people who want to do what you are asking about switch slots and then flash the factory image again.
Btw, Pixel Flasher has the ability to flash to both slots.
In the end, since you re-locked bootloader and, I'm guessing (?), will just update next month via OTA, you really shouldn't need to worry about doing anything.
Click to expand...
Click to collapse
One last thing. Before i read your informative answer, i tried to flash the factory image to both partitions, one at the time, and after successfully doing so, i switched the active partition to the other one, believing that there was an OS there, but then the device bootlooped. i was able to recover from this, but does this mean that the flash all script deletes everything on the current inactive slot when flashing?
tap77 said:
One last thing. Before i read your informative answer, i tried to flash the factory image to both partitions, one at the time, and after successfully doing so, i switched the active partition to the other one, believing that there was an OS there, but then the device bootlooped. i was able to recover from this, but does this mean that the flash all script deletes everything on the current inactive slot when flashing?
Click to expand...
Click to collapse
No, it doesn't delete everything on the current inactive slot. You may have needed to boot into the bootloader of your original slot before booting up. When that happens you can also just flash the factory image again and it will boot up.