Hi guys.
I finally got the notification I was dreading: I can now do a system upgrade to Pie. But shall I?
Even disregarding the learning curve and the mixed comments, I'm weary that one or more of my apps would not be fully compatible yet and would give me trouble.
So my question is: if I decide to go back for any reason, can I do so by simply flashing an Oreo factory image and get to keep my data, or maybe by restoring an Oreo nand backup?
Or is it more complicated by that because of the rollback protection thingy I've been hearing about?
BreadedChicken said:
Hi guys.
I finally got the notification I was dreading: I can now do a system upgrade to Pie. But shall I?
Even disregarding the learning curve and the mixed comments, I'm weary that one or more of my apps would not be fully compatible yet and would give me trouble.
So my question is: if I decide to go back for any reason, can I do so by simply flashing an Oreo factory image and get to keep my data, or maybe by restoring an Oreo nand backup?
Or is it more complicated by that because of the rollback protection thingy I've been hearing about?
Click to expand...
Click to collapse
Interesting question that has two answers. There are those that say you can by clean fastbooting the factory image, and there are those that say you can't because of the bootloader and google's stupid roll back prevention. I've read about people rolling back before, but have never tried it personally. I suppose you could fastboot the last DP5 to get a taste of 9.0, then roll back to 8.1 if you don't like it. Your call my friend.
I have also never tried it but if it works it's likely not that easy because of the mentioned Bootloader Lock.
Either way my approach would be to find out if those apps that are important to you would work on pie by searching the Forums or play store comments.
Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
Badger50 said:
Interesting question that has two answers. There are those that say you can by clean fastbooting the factory image, and there are those that say you can't because of the bootloader and google's stupid roll back prevention. I've read about people rolling back before, but have never tried it personally. I suppose you could fastboot the last DP5 to get a taste of 9.0, then roll back to 8.1 if you don't like it. Your call my friend.
Click to expand...
Click to collapse
That question does not really have two answers; you *can* roll back the system/bootloaders/firmware, you *cannot* roll back the userdata, which means that in order to retain the majority of your data, you would have to restore userdata from a backup, and that, of course, will only contain the data up to the point that the backup was made.
Anti-rollback features really only apply to someone trying to take advantage of an old security vulnerability by "upgrading" to an older system build. You can't do that on a locked system.
For what it's worth: Yes; if you have an unlocked bootloader.
Code:
fastboot unlock_critical
is a must (flash-all writes over the bootloader)
If everything is unlocked, it is as simple as:
(from the directory the 8.1 factory image is extraced to)
Code:
adb reboot bootloader
fastboot -aa
flash-all
(hold down vol-dn button when it gets to userdata and release once it boots back into bootloader)
Code:
fastboot -ab
flash-all
Once complete it should boot into Oreo.
...obviously this will not work on Verizon devices.
Thank you gentleman. Now I have ammo for when someone says your can't downgrade!
Related
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk
So I might have gotten a nice stroke of luck here. Got a Pixel XL from Verizon with no intentions to do any modifying of any kind. I took the OTA update to 7.1.1. A few weeks later, I finally dove into the forums to see what kinda development we got going for this phone. I read that the bootloader is forever locked. Since buying the phone, I had tons of freezes, crashes, and reboots. I sent the phone in to Verizon and got my replacement with 7.1! I unlocked the bootloader and I couldn't hold true to my initial plans of not modifying it. Currently I have a Verizon Pixel XL, bootloader is unlocked, twrp, franco r6 kernel, root. On build NMF26O. What is the best/quickest method for updating with these monthly security patches and such?
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Step 9
joooe said:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Step 9
Click to expand...
Click to collapse
Either I'm going crazy or just plain dumb, but there's only 8 steps when I go to that link
jdpro22 said:
Either I'm going crazy or just plain dumb, but there's only 8 steps when I go to that link
Click to expand...
Click to collapse
You are right LOL. There is no Step 9 :laugh:
I myself am not clear yet, but I think you need to flash stock recovery and kernel and then you could take the OTA update and install it. That will be the easiest. But I always like to do it clean, so I download the OTA and then sideload it via ADB. Obviously I take a backup before and then restore it.
But just make sure that there is a way to restore stock recovery, I am not clear about that part, stock boot.img is easy to find and flash, I don't know whether that restores the stock recovery too or not.
Start at step 4 here: https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Just remember to delete "-w" from flash-all.bat so your data is not wiped!
I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?
There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
savi0 said:
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
Click to expand...
Click to collapse
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
5.1 said:
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
Click to expand...
Click to collapse
To clarify your meaning... The May Verizon OTA does or does not break root?
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
savi0 said:
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.
Click to expand...
Click to collapse
Hello,
If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...
savi0 said:
Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
5.1 said:
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
Click to expand...
Click to collapse
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Hey,
As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.
Cheers...
5.1 said:
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
Click to expand...
Click to collapse
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
sliding_billy said:
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...
Normally, we won't have to wait too long to get back TWRP/Root.
Cheers...
sliding_billy said:
I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
Hello,
I don't understand what you mean when you say:
alluringreality said:
That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update
Click to expand...
Click to collapse
If you have issues, just sideload the latest OTA from Google here:
https://developers.google.com/android/ota
Instructions are available on this page.
Good luck...
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.
Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
PrettyPistol555 said:
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
Click to expand...
Click to collapse
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
shagbag913 said:
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
Click to expand...
Click to collapse
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
PrettyPistol555 said:
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
Click to expand...
Click to collapse
Yep.
Hi, recently I bought my Moto Z2 Play (XT1710-09).
I really wanted to root my phone, but because of some weird bug, it soft-bricked it. Fortunately I had Absolute backup of whole internal storage so I have Original files.
Also I have not flashed TWRP, I have only fastbooted TWRP (Which is propably why I soft-bricked my phone)
So my question is very easy. Is it possible to lock bootloader if I have recovered back whole system and all it's files by stock files with which it (Moto Z2 Play XT1710-09) arrived?
Also the phone is fully functioning at the moment, with original files mantionet above, but it can't make working OTA updating process. And it's pain in ass, because the update manager is still apearing with new update...
So I have decided to lock bootloader even if it means to wipe all personal data and factory reset. Just for sake of getting rid of that stupid OTA updatete fullscreen pop up, that I have a new update waiting to be downloaded and installed.
You may ask as well "Why do you want to lock bootloadert insted of buying Titanium backup pro and freezing that update manager". The reason is simple. I'm afraid of rooting my phone again, because last time, it soft-bricked it and next time, it may full-brick it.
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Surely there is a fastboot command somewhere (which I think I saw in another thread) without having to flash some firmware?
https://forum.xda-developers.com/showpost.php?p=77270030&postcount=9
So that does mean. As long as I have 100% of stock files with which it come to me, it will lock?
julesism said:
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Click to expand...
Click to collapse
Every firmware I try fails to lock my bootloader, validation fails because non of them are above the security level of my device before I unlocked. Is there any newer firmwares ?
Hey everybody,
sorry for the new thread, but I feel like the risk of getting my fresh device bricked is too high if I'm not taking reassuring measures - especially considering the kinda confusing instructions posted here. And yes, I read them all.
I'm getting my P6Pro Replacement Device tomorrow. Since I think that it will still be on A12 I need to upgrade; since I used my previous 6 Pro rooted I wanna root the replacement device too.
What would be the best way to achieve this? Should I just take the normal update route, then unlock the bootloader, change the slot and use flash-all there to flash the factory image to the inactive slot? Or is unlocking the bootloader at that moment too risky? I'm well versed with the factory image update process due to me updating that way on a monthly basis with root, so that would be the most familiar way.
What I dont get in most of the instructions here, is that I'd still be booting up A13 after upgrading with one partition still being on A12. Isnt that the thing that I want to avoid, since a failed boot up with A13 would result in the A12 partition being loaded and thus a bricked phone.
@roirraW "edor" ehT described in his post with regarding this topic here https://forum.xda-developers.com/t/...tral-repository.4352027/page-52#post-87291469
how you include a line that prevents the system from booting up after flashing the first partition and then describes in the step for step instruction how he boots up the system after flashing the first partition where would i insert that line in the flash-all script? After the mentioned line and create a new line or really directly behind it?
Thanks all for clearing that up!!
xflowy said:
Hey everybody,
sorry for the new thread, but I feel like the risk of getting my fresh device bricked is too high if I'm not taking reassuring measures - especially considering the kinda confusing instructions posted here. And yes, I read them all.
I'm getting my P6Pro Replacement Device tomorrow. Since I think that it will still be on A12 I need to upgrade; since I used my previous 6 Pro rooted I wanna root the replacement device too.
What would be the best way to achieve this? Should I just take the normal update route, then unlock the bootloader, change the slot and use flash-all there to flash the factory image to the inactive slot? Or is unlocking the bootloader at that moment too risky? I'm well versed with the factory image update process due to me updating that way on a monthly basis with root, so that would be the most familiar way.
Click to expand...
Click to collapse
Hello!
If I were doing it fresh from a brand new Pixel 6 Pro, I would unlock the bootloader first thing. This will wipe your phone, but it's brand new out of the box and doesn't hurt anything.
Then from running Android I would:
Code:
adb reboot bootloader
then
Code:
fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img
Once that's done, I would flash-all.bat from the Android 13 factory image zip. In this particular case, I would even leave the "-w" in the flash-all.bat, but it's up to you. Just don't forget that the -w is still in there, in case there's some reason for you to use the same flash-all.bat yet again, but don't want to wipe later.
xflowy said:
What I dont get in most of the instructions here, is that I'd still be booting up A13 after upgrading with one partition still being on A12. Isnt that the thing that I want to avoid, since a failed boot up with A13 would result in the A12 partition being loaded and thus a bricked phone.
Click to expand...
Click to collapse
Not partition, one slot. As long as you do the:
Code:
fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img
xflowy said:
@roirraW "edor" ehT described in his post with regarding this topic here https://forum.xda-developers.com/t/...tral-repository.4352027/page-52#post-87291469
how you include a line that prevents the system from booting up after flashing the first partition and then describes in the step for step instruction how he boots up the system after flashing the first partition where would i insert that line in the flash-all script? After the mentioned line and create a new line or really directly behind it?
Thanks all for clearing that up!!
Click to expand...
Click to collapse
That post of mine you linked to is already ancient news (relatively speaking with all the posts we've had about Android 13) and although correct, it's not 100% necessary to fully flash Android 13 to both slots, it's only important to flash the Android 13 bootloader to both slots.
You'll be fine. You're welcome!
xflowy said:
Isnt that the thing that I want to avoid, since a failed boot up with A13 would result in the A12 partition being loaded and thus a bricked phone.
Click to expand...
Click to collapse
The new ARB fuse only gets lit (ARB counter started), so to speak, after you boot into A13. So if you updated to A13 but the update failed and you weren't able to boot into A13 you would be safe because you didn't actually boot into A13 yet.
But as @roirraW "edor" ehT , the best way to alleviate any worries is to flash the A13 bootloader to both slots before anything.
And make REAL sure...if you use a patched boot that you made previously...make sure it was made from AFTER you took the A13 update. Flashing to both slots and then rooting with the wrong patched boot image will make u headbutt your desk until ur half unconscious...don't ask me how I know...I'll just deny.
Guys, just to be clear again.. I did like you proposed and flashed the A13 Bootloader to both slots, then flashed the A13 update to the active slot (a) and am now on 13.
So now, when I'm about to update to the september sec. update, I just go the normaly way via updating with a factory image that I used to to? Or should I flash the september update to both slots now to be sure?
@roirraW "edor" ehT @Lughnasadh thank you again! <3
xflowy said:
Guys, just to be clear again.. I did like you proposed and flashed the A13 Bootloader to both slots, then flashed the A13 update to the active slot (a) and am now on 13.
So now, when I'm about to update to the september sec. update, I just go the normaly way via updating with a factory image that I used to to? Or should I flash the september update to both slots now to be sure?
@roirraW "edor" ehT @Lughnasadh thank you again! <3
Click to expand...
Click to collapse
If you flashed the A13 bootloader to both slots, and verified that they were flashed to both slots, then yeah, you can update to the September build the way you normally do. If via flashing the factory image, you'll still have A12 on the other slot (b) but that's ok because you have the A13 bootloader on that slot to protect you.
So basically, with the A13 bootloader on both slots you can carry on normally and not have to worry about the ARB/eFuse fiasco.