Strange i don't see them on my Google on Verizon, did you accidentally install the verizon factory image when you flashed .37
How To Guide [CLOSED] Firmware is out! Get your root on!
- Thread starter V0latyle
- Start date
- Status
I'm on the Pixel 5. I have had this happen every time I factory reset my device, when I perform the restore from Google backup. I'm not using the Verizon firmware - which doesn't contain the apps anyway.
I"m running the Google P6 but VZW is my carrier so maybe that's why it gets reinstalled. I think there are some startup files somewhere but without root they can't be deleted. The "My Verizon Services" app (under system apps) is particularly insidious as they can get into your phone and see what you are running, when it was installed, when and if you reset your phone, stuff like that. And now they just sent an email saying that if you don't opt out they will monitor everything you do online, website visits, questions asked, interests etc. How many of these went into the junk email and people are unaware of it. I actually thought you needed to opt in to this crap and not have to opt out. The Verizon enhanced experience I think they call it.
Hoping someone can help. New phone, did the inital setup, developer mode, OEM unlock etc etc. All fine until I got to this stage "fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img>"
It seemed to flash ok but at the end it had the following error message:
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2614 MB) to disk... took 28.133s
archive does not contain 'product.sig'
Sending 'product' (2677008 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Then it tried to boot.
Now I am in bootloop hell!
It tries ot boot but I only get as far as the the bootloader is unlocked and software integrity blah blah blah screen. When it tries to boot I see the google screen then back to this.
I can get back to Fastboot Mode and it states it's unlocked however if I try the fastboot flas vbmeta again I get this:
Invalid sparse file format at header magic
Sending sparse 'vbmeta_a' 1/1 (60856 KB) OKAY [ 1.405s]
Writing 'vbmeta_a' (bootloader) image size (2386472960) biffer than partition size (65536)
FAILED (remote: 'failed to flash partition (vbmeta_a)')
fastboot: error: Command failed
Any idea's on how I can solve this?
It seemed to flash ok but at the end it had the following error message:
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2614 MB) to disk... took 28.133s
archive does not contain 'product.sig'
Sending 'product' (2677008 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Then it tried to boot.
Now I am in bootloop hell!
It tries ot boot but I only get as far as the the bootloader is unlocked and software integrity blah blah blah screen. When it tries to boot I see the google screen then back to this.I can get back to Fastboot Mode and it states it's unlocked however if I try the fastboot flas vbmeta again I get this:
Invalid sparse file format at header magic
Sending sparse 'vbmeta_a' 1/1 (60856 KB) OKAY [ 1.405s]
Writing 'vbmeta_a' (bootloader) image size (2386472960) biffer than partition size (65536)
FAILED (remote: 'failed to flash partition (vbmeta_a)')
fastboot: error: Command failed
Any idea's on how I can solve this?
If you are replying to me, thanks, but could you please give me some further detail. Cheers.
I had the same thing happen to me, I had to send my back for warranty and I tried to Flash back to stock and I got that system is corrupt. the only way I could get out of it was using the android flashing tool. The tool and how to use it are on the Google site where the factory images are
Thanks that helped, I am now back to square one ready to stuff it up again! LOL. Appreciate all your help,
I'm glad you're going again . I had the same problem no matter what I Flashed no matter what fastboot command I threw at it I could not get out of that corrupt system without that android Flash tool. I'd never used it before either but it was pretty simple.
- Jun 2, 2012
- 7,804
- 17,195
If you haven't already, check out the step by step in my sig. Pretty much detailed steps that have worked for 82 bazillion Xda members
I did, I used both of these threads and a video YouTube, so I am all rooted but everytime I reboot I get the unlocked error message is that normal? or can i remove it?If you haven't already, check out the step by step in my sig. Pretty much detailed steps that have worked for 82 bazillion Xda members
- Jun 2, 2012
- 7,804
- 17,195
Glad everything's good on your end.
That bootloader unlocked message has been around forever. Disregard it.
Just wanted to stop bye and say thanks so much for the help and the instuctions. All setup with font's, adaway, hidden from pay and banking apps etc. Perfect and couldn't have done it without the help of this thread. 
hey giys just got the phone its unlocked from best buy i am able to click on oem unlock bootloader. but the verison for firmware is (SD1A.210817.037.A1 which is verizon factory image weird. is it safe to you use (SD1A.210817.037.A1 boot.img for root? thx in advnce
What carrier are you on? If Verizon, then yes. Better yet, use this one 12.0.0 (SQ1D.211205.017, Dec 2021, US carriers)
What is the difference between 12.0.0 (SQ1D.211205.016.A1, Dec 2021) and 12.0.0 (SQ1D.211205.017, Dec 2021, US carriers).
My phone is bootloader unlocked. I was planning to flash 12.0.0 (SQ1D.211205.016.A1, Dec 2021), but maybe I should use the other version.
Does anyone have a definitive answer on which source to use with a Bootloader unlocked phone on Verizon?
My phone is bootloader unlocked. I was planning to flash 12.0.0 (SQ1D.211205.016.A1, Dec 2021), but maybe I should use the other version.
Does anyone have a definitive answer on which source to use with a Bootloader unlocked phone on Verizon?
- Status
Top Liked Posts
-
There are no posts matching your filters.
-
45Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image.
Any update method can be used. If you've already disabled verity/verification, simply don't worry about it at next update; no need to re-enable.
I am closing this thread.
On Android 12, boot verification must be disabled in order to run a patched boot image. Unfortunately, if you have never disabled it before, it will require you to wipe data. To be clear:
***************************************************
PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
***************************************************
However, if you don't want to lose your data, you can "live boot" the patched image as long as /vbmeta and /boot are stock. This will allow you to use temporary root. DO NOT attempt to Direct Install Magisk to the boot image.
For subsequent updates, it is imperative that you do not allow the device to boot into system before you have disabled Verified Boot.
What this means: If you sideload the OTA, IMMEDIATELY reboot to bootloader and reflash /vbmeta with --disable-verity and --disable-verification. If you dirty flash the factory image, make sure you add these two switches to the command.
If you fail to do this, and allow the device to boot into system, you WILL have to wipe data to disable it again.
IF YOU ARE ROOTED, DO NOT USE AUTOMATIC UPDATES AS THIS WILL REFLASH /VBMETA WITHOUT DISABLING BOOT VERIFICATION!
Factory Images
OTA Images
Latest Magisk Canary
- On your device, enable Developer Options (tap build number 8 times), and enable the OEM Unlocking toggle. Reboot to bootloader:
-
Code:
adb reboot bootloader - Unlock bootloader:
Code:fastboot flashing unlock - Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img
and vbmeta.imgfrom this zip. Flash vbmeta:
Code:fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img>- Allow the device to boot into Android. Once you have Magisk installed, copy the boot.img and patch it in Magisk, then copy it back to your PC.
- Reboot to bootloader.
- Flash patched boot image:
Code:
fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img> - Reboot into system.
- Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img from this zip.
- Reboot to bootloader.
- Update bootloader and radio if they are out of date. BE CAREFUL, A MISTAKE CAN BRICK YOUR DEVICE! If you update the bootloader, remember to reboot back to bootloader so that the update reads the correct bootloader version.
- Update system:
Note: If you get an error for bootloader/radio version, this means you need to update bootloader and/or radio; go back to step 3.Code:fastboot update --disable-verity --disable-verification <drag and drop image-device-buildnumber.zip here> - Allow the device to boot into Android. Copy the boot.img and patch it in Magisk, then copy it back to your PC.
- Reboot to bootloader.
- Flash patched boot image:
Code:
fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img> - Reboot into system.
I personally do not recommend updating via OTA Sideload, as you would have to download and extract the factory zip anyway.AUTOMATIC OTA WILL LOSE ROOT AND REQUIRE A WIPE TO ROOT AGAIN.
- Sideload the OTA. When complete, IMMEDIATELY reboot to bootloader.
Reflash vbmeta:Code:fastboot flash vbmeta --disable-verity --disable-verification <vbmeta.img>- Boot to system and allow the update to complete.
- Patch and flash the boot image.
Note: If you run into a bootloader message
failed to load/verify boot images
this means you forgot to disable verity and verification. Reflash vbmeta with the --disable options.
If you run into this recovery message
This means that verity and verification were not disabled before, and a wipe is required to proceed.11
1. Download both the OTA AND the factory zips.So, what exactly are then the steps to flash the OTA without losing root and without wiping everything again?
Currently I'm with Magisk Alpha (Safetynet passed) on .015 firmware.
2. Extract boot.img and vbmeta.img from the factory zip.
3. Patch the new boot.img in Magisk and copy it back to your PC.
4. Reboot into recovery and sideload the OTA
5. When the update completes, you'll still be in recovery. DO NOT REBOOT. Select "Enter fastboot"Code:adb reboot sideload adb sideload ota.zip
6. In fastboot, flash vbmeta:
7. Now flash boot:Code:fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
8. Reboot, you should come into the new update with root.Code:fastboot flash boot magisk_patched-23xxx_xxxxx.img
Remember: You get ONE CHANCE, and ONE CHANCE ONLY to flash /vbmeta while in fastboot. If you do something wrong, you will either have to wipe data, or go without root.7015 rooted to 036 no wipe update
- Download the factory image.
- Copy boot.img to your phone. Patch with Magisk.
- Edit Flash-all.bat
remove -w and add --disable
fastboot update --disable-verity --disable-verification image-raven-sd1a.210817.036.zip - Run Flash-all.bat
- Boot (don't flash) patched image
fastboot boot magisk_patched-xxxxx.img - Launch Magisk and tap Install, then Direct Install.
5November OTA/factory images are live!
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
5
In all fairness, this is exactly what my instructions are:I think you made the same mistake as me, you extracted the factory image archive, and tried to patch the resulting bootloader-raven-slider-XXXXX.img directly thinking it was the file to patch as it began by "boot" and had the ".img" extension.
If that's the case, from the factory archive extraction you have to then extract the image-raven-XXXXXXX.zip archive, containing the final "boot.img" file to patch.
@V0latyle you may want to develop a little bit this part in the OT tutorial, as we might won't be the only ones making this mistake
I'm not really trying to make something idiot proof, there's a certain point where limited knowledge and experience is a good reason to NOT try something. If you're unlocking your phone and messing with software, you SHOULD know what you're doing, and at the very least how to fix it if something goes wrong. This forum is not official support, no one here bears any liability whatsoever, and I don't want to give inexperienced and unfamiliar people the impression they can do something that's way outside of their realm of understanding - just like I wouldn't tell someone how to service their brakes if they don't know the difference between a jack and a jackstand.
I guess what I'm saying is, if you mistake the bootloader image for the boot image, you probably shouldn't be doing any modifications to your device.
