Database Info

Xoom 4g Stuck at Red M

My Xoom is a 3g that I sent in to have the 4g upgrade. Ive been running different roms for a couple years, decided to go back to stock the other day. I followed some steps I found at xda about how to do that, It was some version of honeycomb.
Anyways, after a reboot of the xoom It is stuck at the red M. I cannot get into recovery, cannon use adb commands. However, fastboot is working. What can I try next? After spending hours googling it, this doesnt seem real uncommon. But most of the links on how to put on a new bootloader with something called avalance 1.35 seem to be broke. Any ideas?

Your Xoom does not have an OS installed, nor a recovery.
Need to fastboot the stock images.

Mjamocha said:
Your Xoom does not have an OS installed. Flash a custom ROM
Click to expand...
Click to collapse
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.

ArXane said:
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.
Click to expand...
Click to collapse
yeah, i corrected my last comment.
hmmm .... odd

Mjamocha said:
yeah, i corrected my last comment.
hmmm .... odd
Click to expand...
Click to collapse
I have done the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
I got the files from the Motorola Support site.
I also used the RSD Lite to try and push factory image.

ArXane said:
I have done the following:
Click to expand...
Click to collapse
you forgot the last command
fastboot oem lock

Mjamocha said:
you forgot the last command
fastboot oem lock
Click to expand...
Click to collapse
Sorry, I have done that one also.

are you using the correct stock images for the 4G version?

Mjamocha said:
are you using the correct stock images for the 4G version?
Click to expand...
Click to collapse
Here are the links I have tried:
http://www.randomphantasmagoria.com/firmware/xoom/trygon4g/
HLK75D
I also tried the motorola image: MZ602_HLK75D that I had to request from Motorola.

It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.

Mjamocha said:
It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.
Click to expand...
Click to collapse
WIll try, thank you. Ever heard of everest 1.5 bootloader? It looks like that may be a common fix. All the links I find are broken.

Nope.... flashing HRI66 didnt change anything. Still cannot ADB, still doesnt boot.

no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298

Mjamocha said:
no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298
Click to expand...
Click to collapse
Tried flashing recovery with the stpes agove, same deal, cannot get into recovery. WIll try the LORD tool and will let you know.

Soft bricked shield tablet PLEASE HELP!

So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.

okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader

Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"

danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha

Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.

Okay will try that. Thanks man.

Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5

Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.

Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.

Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5

Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?

Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.

koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?

Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?

Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.

koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader

Moto G3 boots into recovery every time I power on device

I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.

ItsWoffles said:
I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
Look at this thread
https://forum.xda-developers.com/2015-moto-g/help/reboot-bootloader-mode-t3653547

melp57 said:
Look at this thread
https://forum.xda-developers.com/2015-moto-g/help/reboot-bootloader-mode-t3653547
Click to expand...
Click to collapse
Do I need to type in fastboot oem fb_mode_clear while re flashing stock firmware again like I would to relock the bootloader?

ItsWoffles said:
Do I need to type in fastboot oem fb_mode_clear while re flashing stock firmware again like I would to relock the bootloader?
Click to expand...
Click to collapse
Actually it's not an issue, the command
Code:
fastboot oem fb_mode_set
makes the phone boot into bootloader mode instead of starting android. To undo this, you'll just have to type in-
Code:
fastboot oem fb_mode_clear
. No need to flash the whole firmware again if this is the only problem.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Actually it's not an issue, the command
Code:
fastboot oem fb_mode_set
makes the phone boot into bootloader mode instead of starting android. To undo this, you'll just have to type in-
Code:
fastboot oem fb_mode_clear
. No need to flash the whole firmware again if this is the only problem.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Where do I type this command in? Using ABD and fastboot? Do I just go into the bootloader and plug my phone into my PC, then open up ABD and fastboot and type in that command or what do I do? Is that the only command I need to type in? Sorry, I'm a noob to this kinda stuff!

ItsWoffles said:
Where do I type this command in? Using ABD and fastboot? Do I just go into the bootloader and plug my phone into my PC, then open up ABD and fastboot and type in that command or what do I do? Is that the only command I need to type in? Sorry, I'm a noob to this kinda stuff!
Click to expand...
Click to collapse
Reboot the phone into bootloader mode. To do this, power off the phone, press and hold power+volume down button till it shows up.
Plug the phone into PC, open command prompt from the folder where adb.exe and fastboot.exe are present, and type that command (only that one is needed). Disconnect the phone and try rebooting to see if it boots correctly.
Broadcasted from Zeta Reticuli

ItsWoffles said:
I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
I think u flashed recovery to boot..

mg_jishad said:
I think u flashed recovery to boot..
Click to expand...
Click to collapse
If that was the case, you could never boot the phone into Android... the OP stated that he can select continue and start the device normally. It is most likely stuck in fastboot fb_mode like @Gravemind2015 stated.

Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....

Uncle Waldo said:
Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....
Click to expand...
Click to collapse
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot

acejavelin said:
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot
Click to expand...
Click to collapse
Shouldn't that make the phone stay at bootlogo as the kernel and ramdisk are overwritten by TWRP code? @Uncle Waldo stated that the phone is looping into TWRP after *moto update action*. So what I am able to figure out is that this is a OTA-on-stock-rom-with-custom-recovery situation. I am a litte doubtful though as google says the phone boots into kernel from recovery (which is evident here) instead of kernel from boot partiton (source), so you may be 100% correct here too
@Uncle Waldo : If that is indeed the case (i.e moto issued an update and since rebooting the phone it's just looping into TWRP and giving an error) then I'd recommend that-
Flash stock boot.img as @acejavelin suggested
Flash stock recovery.img (as TWRP can't nstall stock ROM updates)
This is assuming that the /system partition was never modified in any way. If the update still fails in stock revovery, I'd guess that the whole system has to be restored to a non-modified state (i.e flashing the full firmware). You can try flashing all without doing the 'fastboot erase' part though, but i'd recommend you to backup your files using TWRP when you can.
links-
Link to the flashing guide is here
Link to the firmware index is here
command to install recovery -
Code:
fastboot flash recovery recovery.img
command to flash boot.img-
Code:
fastboot flash boot boot.img

Uncle Waldo said:
Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....
Click to expand...
Click to collapse
If it is because of an update, you can't accept it while on TWRP... If you did, try to access the TWRP menu and if you can't boot TWRP from.fadtboot (not flash) and wipe caches... It should boot normally after that.

ACE; moto has been operating for sometime now fine
acejavelin said:
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot
Click to expand...
Click to collapse
You believe this could be my problem as the moto boots just fine and it's only started this problem when I installed the following update.
Motorola > android security updates version 24.211.14.en.US
After this install and reboot it appears to work just fine and then shortly reboots into TWRP from here the only correcting action that stops the reboot loop is "RESTORE".
After restoring and reboot the moto is back to operating as before and at some point I get the same message to install the security updates and the dance begins anew.
If reflashing the stock boot image via fastboot could correct my problem > then I am all ears Ace, as it's been sometime since I ventured into android ville and any help in this matter thanks...

Uncle Waldo said:
You believe this could be my problem as the moto boots just fine and it's only started this problem when I installed the following update.
Motorola > android security updates version 24.211.14.en.US
After this install and reboot it appears to work just fine and then shortly reboots into TWRP from here the only correcting action that stops the reboot loop is "RESTORE".
After restoring and reboot the moto is back to operating as before and at some point I get the same message to install the security updates and the dance begins anew.
If reflashing the stock boot image via fastboot could correct my problem > then I am all ears Ace, as it's been sometime since I ventured into android ville and any help in this matter thanks...
Click to expand...
Click to collapse
You edited the original question after I replied... Read my follow-up answer. You can't take an OTA with TWRP installed, just start TWRP and wipe caches and then don't accept any further OTA.

Ace; I missed that one
acejavelin said:
You edited the original question after I replied... Read my follow-up answer. You can't take an OTA with TWRP installed, just start TWRP and wipe caches and then don't accept any further OTA.
Click to expand...
Click to collapse
Your correct I missed that one, a BC moment (before coffee) sorry.
Okay in the fog of my memory I do now remember the OTA prohibition as I said it's been a piece of time.
I've done as instructed and all is well again, but will this nag screen appear again as it has done.
Question > How do I shut the motorolia OTA update off, so I don't get their stupid never ending nag screen everytime that I look at phone?
Thanks for your help...
---------- Post added at 05:13 PM ---------- Previous post was at 04:33 PM ----------
Ace I figured it out thanks for all your help...

Phone boots into fastboot, system files corrupted

Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?

Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.

Both failed. I attached the errors I recieved.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com

I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.

crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/

It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.

Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?

Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.

That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .

crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!

Question Why i cant updated latest QPR A13 for my pixel 6a

after download and reboot apprear this error..refer photo..

Try shutting it down, entering fastboot mode and flashing it from here.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
ok thanks..no need unlockboot loader rite?

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader

ctfrommn said:
You can't flash anything with a locked bootloader
Click to expand...
Click to collapse
ok thanks..hmmm..

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
For Android Flash Tool you need to have OEM unlocking enabled in developer options, but don't need to actually have the bootloader unlocked beforehand. The tool will unlock your bootloader during the process (assuming you are able to unlock the bootloader, e.g. not a Verizon model). It will also lock it afterwards if you choose to do so.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
already try..still not work

Boi. said:
already try..still not work
Click to expand...
Click to collapse
You probably need to be more specific. What exactly happened after using Android Flash Tool? How did you initially try to install QPR1B1? Are you using the latest Platform Tools? Do you have the latest USB drivers installed? Have you tried using an A to C cable using a USB 2.0 port?
If you're flashing environment is set up correctly, you can also try sideloading the OTA image.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...

Pakabidu said:
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Click to expand...
Click to collapse
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...

Pakabidu said:
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Click to expand...
Click to collapse
That is really weird behaviour for a Pixel device. I update using the stock rom method for all my pixels and never had issues. I have the Pixel 6 and the only instance I got the device is corrupt when I tried to roll back the November update to the October update causing a bootloop.
I wonder if there is something wrong with the 6A and some people having issues with the oem unlocking being greyed-out. Hopefully, Google will fix the issue with a future patch or monthly update.