Related
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.bat WITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.bat WITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Anutter226 said:
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.batWITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.batWITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
I imagine it's overkill but you could just switch the active slot and run flash-all again. As a precaution I would recommend booting into the OS after the first flash-all to make sure it flashed ok. If there happens to be some problem like a bad flash or wrong download you want to be sure that the "other" slot is bootable. Otherwise you might end up with a pair of unbootable slots which could get sticky.
Anutter226 said:
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
then you saw that flash-all.bat flashed both slots
V40 said:
then you saw that flash-all.bat flashed both slots
Click to expand...
Click to collapse
Doesn't flash to both slots on mine
canemaxx said:
Doesn't flash to both slots on mine
Click to expand...
Click to collapse
I believe it flashes to one slot and deletes the data on the other as standard
If you guys would read your terminal output after flashing you would know what gets flashed where. People are making this way to complicated. It is a big change from previous devices but once you know the partitions its pretty easy.
One data slot shared by A + B
Slot A & B have separate partitions for
-Vendor
-Bootloader
-Radio
-Modem
-Boot
-System
Flashall.bat flashes your active slot and installs system_other.img to the inactive system partition and wipes data, unless you edit the flashall.bat and erase -w.
Thats it. Now, how people are handling the two slots is another story. I keep both slots identical. Having two different bootloaders is a recipe for bricks in my opinion.
FWIW, I endorse the post above this one. I would only add if you get in trouble flash all without the -w and then change the active slot and flash all without the-w again.
Golf c said:
Having two different bootloaders is a recipe for bricks in my opinion.
Click to expand...
Click to collapse
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
5.1 said:
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
Click to expand...
Click to collapse
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Golf c said:
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Click to expand...
Click to collapse
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
5.1 said:
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
Click to expand...
Click to collapse
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Golf c said:
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Click to expand...
Click to collapse
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
5.1 said:
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
Click to expand...
Click to collapse
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Golf c said:
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Click to expand...
Click to collapse
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
5.1 said:
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Click to expand...
Click to collapse
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Golf c said:
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Click to expand...
Click to collapse
Hey,
I did it just to show something to someone earlier. I don't need dual boot either...
One ROM is enough in my opinion.
Ok, time to hit the bed. See you later...
Cheers...
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
TonikJDK said:
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
Click to expand...
Click to collapse
And I don't even use it because I have never taken an OTA. lol!
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
canemaxx said:
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
Click to expand...
Click to collapse
No need since it ia working but you get into Fastboot mode then
Fastboot set_active a
Flash L, flash April bootloadee.
Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol
Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.
is it worth factory resetting device with this latest update?
Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.
jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.
bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?
animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.
The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 4 (and A9 for a/b slots), hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. I always thought corruption must have been there before, but now I'm not so sure.
update: flashed the last build from November using flash.android.com and was able to get my system back. 2nd flash for that build worked.
Alekos said:
The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 9, hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. Corruption must have been there before, but now I'm not so sure.
If anyone has any fastboot tricks - I'd try anything at this point.
Click to expand...
Click to collapse
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back
mac796 said:
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back
Click to expand...
Click to collapse
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message.
I tried flashing 4 different Factory Image builds (flashing manually the Factory Image not ota). The android flash tool (webiste) completes but same message appears after it restarts.
Alekos said:
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
I tried flashing 4 different Factory Image builds. The android flash tool completes but same message appears after it restarts.
Click to expand...
Click to collapse
You're trying to flash with fastboot right? Use that Android flash tool. You'll see a link to it in the factory image page. I went through the same thing you did, I got the corrupt device. at the very end It'll ask you to Lock the bootloader just don't do it if you want to stay unlocked.
Oh maybe I misunderstood you tried that and it's not recognizing it
mac796 said:
Oh maybe I misunderstood you tried that and it's not recognizing it
Click to expand...
Click to collapse
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.
Alekos said:
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.
Click to expand...
Click to collapse
That's no good. Hope it works out. I had a hell of a time getting mine back too
mac796 said:
That's no good. Hope it works out. I had a hell of a time getting mine back too
Click to expand...
Click to collapse
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
a few reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.
Alekos said:
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
Lots of reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.
Click to expand...
Click to collapse
I'm glad you got out of it
I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section
victoraran said:
I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section
Click to expand...
Click to collapse
so if I didn't have "OEM unlocking" enabled - I'd have a brick right now. just actually trying to help someone else that also got the corruption message and can't get back into Android to enable oem unlock. Recovery doesn't work (like my situation).
What a mess...
That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.
Battery life is awesome, still on 44% at half 10 at night from half 6 this morning
prohibido_por_la_ley said:
That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.
Click to expand...
Click to collapse
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Well in the 4 years of me being on Android I've never had it happen.
I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.
JodyBreeze901 said:
I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.
Click to expand...
Click to collapse
same
Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Why not just adb sideload the OTA image, rather then flashing on both slots the factory image? It just sounds a bit of a hassle to me.
I know, I used to fastboot flash without -w my nexuses as well, but that was before the OTA images were available.
prohibido_por_la_ley said:
Well in the 4 years of me being on Android I've never had it happen.
Click to expand...
Click to collapse
yeah it's super rare. been flashing images and ota's since Nexus 4. But it happens.
I usually get the updates right away but sometimes I'll update the ota. I usually reflash the factory image every year after the beta. just seems odd how it corrupted the device. couldn't get into the system at all (or recovery/rescue modes).
yolandabecool said:
same
Click to expand...
Click to collapse
apparantly it has something to do with Bluetooth? I don't know how, but if you can get into safe mode and disable Bluetooth, clear cache/data for it and update all your google service apps, it can fix it (keeping Bluetooth off while restarting phone in regular mode) - but I couldn't load Android.
The trick to getting into Safe Mode is this: Turn off the device. Hold down power and and as soon as you see the "G" Logo, hold volume down. it will directly boot you to Safe mode. cool little trick. you'll have to manually enable wifi because it gets turned off.
At this point, if you can, enable OEM Unlocking. at least you'll be able to save the device if anything serious happens (like what I went through). the pixel repair website also works but I couldn't get into "Rescue Mode"
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
I had same problem
I had no issues. Same process... Recovery, ota sideload, reboot, let it finish setting up, patch boot.img extracted from full image, reboot into bootloader and flashed boot sector. All is fine.
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
I think you can just use the flash tool. Check the appropriate options and it should wipe everything and return it to stock. It looks like you can even use it to lock bootloader again, if you wanted to. This was my first time using it. I may play around with it on one of my old pixels. Never had a use for it before, but came in very handy this week. Probably good for me if I know a bit more about it and how to use it.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
Within the guide is this post and I'm sure many other posts.
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Here's the guide: https://forum.xda-developers.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/
Thank you all, I figured out that online flash tool is a thing. I got it now.
hpower1 said:
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
Click to expand...
Click to collapse
Did you check the downloaded files via checksum?
If you update via OTA, whether via delta or sideload, you CANNOT interrupt the boot process, otherwise the device assumes the update has failed.
Additionally, if you try to use an older boot image, you'll get the same result.
The recommended means of update is either delta OTA + install to inactive slot in Magisk, or factory image + patch new boot image in Magisk.