Question Having problems flashing vbmeta - Samsung Galaxy A12

i’ve been wanting to install a custom rom on my A12 Nacho (A127F) but when i flash vbmeta.tar it fails in odin, and when i try to flash twrp the phone bricks itself because there is no vbmeta.
any help?

someone_. said:
i’ve been wanting to install a custom rom on my A12 Nacho (A127F) but when i flash vbmeta.tar it fails in odin, and when i try to flash twrp the phone bricks itself because there is no vbmeta.
any help?
Click to expand...
Click to collapse
to what slot do you flash VBMETA?
In ODIN flash twrp in AP slot, and nulled VBMETA in userdata slot.
That's all

i flash vbmeta on userdata, so basically what i have to flash is twrp on ap and vbmeta on userdata?

someone_. said:
i flash vbmeta on userdata, so basically what i have to flash is twrp on ap and vbmeta on userdata?
Click to expand...
Click to collapse
correct

it still failed

someone_. said:
it still failed
Click to expand...
Click to collapse
TWRP and VBMETA needs to be flashed together.
TWRP in AP slot, VBMETA in userdata slot.

Related

Problems getting back to stock from boot loop after trying to root.

First I unlocked the bootloader, and then I tried to use chainfire's root method by flashing the boot-to-root-img through fastboot. The phone will no longer boot to system and I cant seem to get google's factory image to install via fastboot. The flash-all would only flash the bootloader and radio, but would fail after that. I also cannot manually flash the stock system.img file. I get an error that reads " remote: data too large ". Not sure how to get out of this so any help would be GREATLY appreciated.
Did you manually flash the boot and system.img to each slot?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Fastboot flash system_a system.img
fastboot flash system_b system_other.img
Use these commands assuming your boot slot is slot_a...if your boot slot is slot_b then use
Fastboot flash system_a system_other.img
fastboot flash system_b system.img
Hope this helps!!!
You need to update your fastboot version....then the system file will flash for you. Only the newest supports large files.
Sent from my Pixel using Tapatalk
maulich said:
You need to update your fastboot version....then the system file will flash for you. Only the newest supports large files.
Click to expand...
Click to collapse
Good call...totally forgot about that man
BakedTator said:
Good call...totally forgot about that man
Click to expand...
Click to collapse
Thanks to both of you! I actually did get my phone to boot up just before you replied by flashing to boot.img to both slots. Just installed TWRP and flashed superSU after that to get root. All is well now!

Android 12 Beta 2 Root Question

Hello.
I had root in beta 1 by flashing a modified boot image patched by magisk (after wiping my device and disabling verification on vbmeta with fastboot). I was able to boot into the system no problem and root was achieved.
Now that I have flashed Beta 2, I'm not able to root. I tried flashing disable verification with vbmeta but it won't go past the Google logo. It says the data is (damaged). I tried flashing just the modified boot image of Beta 2 (from magisk) and it says it's not able to verify the boot image. I also tried booting into the boot image, flashing magisk directly through the app, but when it reboots, it gives the same error.
The only thing I haven't tried is factory reset my data.
Any help would be appreciated, thanks.
Don't use the beta. That's why it's a beta there's always bound to be issues
thatsupnow said:
Don't use the beta. That's why it's a beta there's always bound to be issues
Click to expand...
Click to collapse
Will I have to wipe my data after flashing the modified vbmeta?
Machuda said:
Will I have to wipe my data after flashing the modified vbmeta?
Click to expand...
Click to collapse
I would just to be sure that all traces are gone
I ran into the same problem until I used the flash tool and disabled verity and verification. If you don't do this, you'll be unable to boot if you have a modified boot image.
To root Android 12 you have to flash the beta image and than do this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
And I think when you do a update, its broke the disabled verity & verification.
I find this and you can to update with this command
fastboot update --disable-verity --disable-verification image-redfin.zip
Click to expand...
Click to collapse
but I don't know I its work.

how to flash stock rom using twrp

yeah I need to flash stock rom because because my current rom is kinda buggy I downloaded the stock rom from a site and it contains these: boot.img, dtbo.img, metadata.img, recovery.img, super.img, userdata.img, vbmeta.img, vbmeta_samsung.img and fota.zip
I'm guessing it's either super.img or userdata.img because they are the biggest files please let me know
A Stock ROM typically comes as ZIP-file and gets flashed by ADB Sideload method: TWRP isn't needed for this.
jwoegerbauer said:
A Stock ROM typically comes as ZIP-file and gets flashed by ADB Sideload method: TWRP isn't needed for this.
Click to expand...
Click to collapse
don't have a pc with me rn that's why I gotta do it with twrp lolq
itsukii said:
don't have a pc with me rn that's why I gotta do it with twrp lolq
Click to expand...
Click to collapse
Flash each individual IMG file by selecting it and selected which partition is for the IMG file eg: vbmeta goes to vbmeta_a if ur on a/b and youre on slot a
areallydumbperson said:
Flash each individual IMG file by selecting it and selected which partition is for the IMG file eg: vbmeta goes to vbmeta_a if ur on a/b and youre on slot a
Click to expand...
Click to collapse
so I gotta flash everything before the os would work at all?
I suggest you to flash using fastboot.
Safe and secure.

Question I do everything correctly to root but it keep booting in to the bootloader

My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
What device are you talking about ?
f1tm0t said:
What device are you talking about ?
Click to expand...
Click to collapse
Tab p11 4gig
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
f1tm0t said:
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
Click to expand...
Click to collapse
Threr is no twrp sadly
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
mingkee said:
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
Click to expand...
Click to collapse
I tried it i flashed patched boot.img only in fastbootd still boots me in to the bootloader
LSS4181 said:
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
blocky3321 said:
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
Click to expand...
Click to collapse
Which Magisk version did you use? From what I can tell any official Magisk version should work.
I haven't really tested the recent builds of vvb2060's Alpha or huskydg's Delta... so if you're using these versions I can't really help you much...
Additionally, you need to check which slot you are now, and through fastbootd check which slot actually has system, vendor and such. Normally the super partition only has enough size for one slot. You may have entered a wrong slot that doesn't have usable system.
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
Getting Started: What's Your Device ?
Tab p11 4gig
Device->settings->About : Model & Hardware -> Lenovo ??? (Tb-j606f,TB-J616F...) In your case stiker on box or on back.
mingkee said:
who told you to flash vbmeta.img?
Click to expand...
Click to collapse
???

How to install root?

I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
doveman said:
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
Click to expand...
Click to collapse
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
NOSS8 said:
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
Click to expand...
Click to collapse
Yeah, I downloaded the correct ROM (miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip) and extracted the boot.img from that.
Renaming magisk.apk to magisk.zip and flashing it just installs the app doesn't it, it doesn't root the phone as far as I'm aware.
I followed the instructions here, which say that you should only tick the "Patch vbmeta in boot image” option when patching the boot.img in Magisk if the device does NOT have a separate vbmeta partition. The Poco X3 does have a separate vbmeta partition,, so I didn't tick that option.
Installation
The Magic Mask for Android
topjohnwu.github.io
I've tried the "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" command with four different versions of fastboot that I've got, dating from 2016 to 2020, and they all reject the "--disable" switches as an "unknown option".
I tried it without those options, so I flashed the patched boot.img and then did "fastboot flash vbmeta vbmeta.img" but after rebooting Magisk still shows that root is not installed.
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot​
Size: 5.3 GB​
Release Date: 2021-11-09​
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz​
NOSS8 said:
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot​
Size: 5.3 GB​
Release Date: 2021-11-09​
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz​
Click to expand...
Click to collapse
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
doveman said:
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
Click to expand...
Click to collapse
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Check:
https://forum.xda-developers.com/t/...n-vendor-dynamic-partition-enable-rw.4238807/
https://forum.xda-developers.com/t/q-h-safety-way-to-unlock-bootloader-flash-recovery-root.4198719/
NOSS8 said:
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
doveman said:
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
Click to expand...
Click to collapse
What happens if you try to root from the Magisk app?
NOSS8 said:
What happens if you try to root from the Magisk app?
Click to expand...
Click to collapse
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
doveman said:
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
Click to expand...
Click to collapse
No functional TWRP for this device.?
NOSS8 said:
No functional TWRP for this device.?
Click to expand...
Click to collapse
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
doveman said:
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
Click to expand...
Click to collapse
Strange case as strange as the number of threads has this subject for this device.
NOSS8 said:
Strange case as strange as the number of threads has this subject for this device.
Click to expand...
Click to collapse
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
doveman said:
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
Click to expand...
Click to collapse
This phone is rootable, surely an oversight or an error somewhere.
NOSS8 said:
This phone is rootable, surely an oversight or an error somewhere.
Click to expand...
Click to collapse
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
doveman said:
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
Click to expand...
Click to collapse
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
NOSS8 said:
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
Click to expand...
Click to collapse
I've already got TWRP recovery flashed. I guess I'll have to flash the ROM again and start from scratch.
I tried flashing super.img but that didn't fix it. In the end, going into ADB Sideload mode in TWRP and flashing the 2.7GB recovery version of the ROM with
"adb sideload miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" fixed it without losing any data.
I still can't root it though. I've tried the "install Magisk (root)" option in TWRP and renaming magisk.apk to magisk.zip and installing that in TWRP, but it still shows "Installed N/A" in Magisk and Root Verifier says "Root permission not granted or Superuser App Missing" but then it says "Superuser App: 25.25:MAGISKSU", so it's the root permission that isn't granted.
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
NOSS8 said:
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
Click to expand...
Click to collapse
I thought so but I've reflashed the patched boot.img and done
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
and
"fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img"
in case it needed that too, but Magisk still shiows "Installed N/A"
I tried installed SR5-SuperSU-2.82 zip from TWRP to see if that would get it rooted,, but it couldn't even install that, it just gave some error.

Categories

Resources