So I have tried to pass the gcam into my miA2 device and it seems that i have made a mistake within A/B partitions, because there is a trouble installing february security patch. I tried to flash my device with miflash tool but it shows an error:Flash devcfg_a error
what is wrong with my device?
Related
EDIT: Hey guys, so since the previous post I have tried numerous things - most notably manually flashing the system, boot and recovery images directly with fastboot. While I was able to do this (using B361 and currently B320) the phone got stuck in a bootloop even though the official recovery successfully did a factory reset and cache wipe. I am fairly certain that if I can get the rollback image to flash I will be able to revert back to stock - but currently this is proving to be difficult. Flashing the rollback image directly with dload fails and I'm currently considering flashing the image through fastboot. Checking the image on firmware extractor tool shows the following:
CRC
CURVER
EFI
RECOVERY
RECOVERY2
VERLIST
VERSION
What extracted image will I be able to flash through fastboot? Thanks for any help in advance
Hey guys,
Firstly I have read through and tried all the usual methods of trying to get back to stock (MM or Nougat) after upgrading to B361. I am currently unable to flash any images through the dload method (not rollback, not nougat, anything). What I've tried flashing (all failed):
L19C185B361 (full)
L19C185B220 (full)
L19C185B210 (full)
L19C185B320 (OTA)
Official rollback image
This is the path I followed:
L19C185B210
MM LOS
L19C185B220
L19C185B320
L19C185B361
(Tried to reflash L19C185B361, failed)
Rollback, failed
TWRP L19C185B220, messed up system partition
Rollback still failed
L19C185B220 still failed
L19C185B361 still failed
Currently running a TWRP flash of L19C185B321, a beta leak image that doesn't work properly
The TWRP running is the Nougat TWRP (MM TWRP not working) leading me to be believe that there is still an official Nougat presence somewhere on the system. I hace an unlocked bootloader, fastboot and adb access but no root. Any help will be greatly appreciated as I've been struggling for over 10 hours now.
Bump - changed the thread question in the hope of getting help
I tried to flash android 10 based gsi for my coolpad but after wiping system,the new gsi didnot managed to get flashed.
Since I was using aosp android 9 pie beforehand,so i tried to flash that,which was working before the wipe, but it was also showing errors after errors so i downloaded the stock firmware and tried to flash the rom through twrp but the terminal stuck at patching system image unconditionally.
I tried to flash rom with fastboot and qfil with no success.
Here's what's happening:
I'm currently on stock V11.0.14 on both slots, magisk rooted and data is encrypted.
Both slots are bootable, and PBRP (recovery) successfully detect and decrypt data partition.
Not sure why, but if I try the usual process to update, uninstall magisk and apply System Update, it always fail, I've reflashed the stock ROM on both partitions and got the same result.
Then I tried to manually flash the full rom (any version greater then V11.0.14) to the inactive slot but it always fails to boot.
Something that I've noticed is that if I boot PBRP with the updated partition active, it fails to detect that the data partition is encrypted and I think that Android is facing the same problem, the updated version isn't detecting the encryption as well.
If I flash V11.0.14 back, it boot.
Any suggestions/solutions rather than full data wipe?
Cheers!
Just today I wrote comment on problems with updates to versions >= 11.0.15.0 :
December 2020 Security Update now available
Hy, December Update out now. Greets
forum.xda-developers.com
As for TWRP - I regard as working 2 versions only:
https://forum.xda-developers.com/t/recovery-unofficial-teamwin-recovery-project.4209151 by @Nebrassy
and older https://forum.xda-developers.com/t/...-mi-a2-jasmine_sprout-by-d4e8ede8f1f2.3941096 by @d4e8ede8f1f2
I unlocked the bootloader and flash Pixel Experience 12L. Now I want to go back to MIUI 13 and lock. MiFlash shows Antirollback error. I even flash Pixel Experience Android11, and MiFlash shows the same error.
I tried newest Fastboot firmware and nothing works.
You need to edit the .bat files and remove the anti-rollback check script manually. This happens to many people too changing ROMs. Don't worry, removing the anti-rollback check isn't harmful because ARB isn't active in the device yet. If you want, you can flash the latest MIUI recovery rom temporarily through custom recovery then try to use MiFlash.
1> The Shamshung recent firmware upgrade CWD1 might have some patches that makes rooting problemtic. I flashed TukiROM1.2 with Magisk 26.1 (boot.img patch method) the first time and it worked but as soon as I connected to wifi somehow it upgraded to Magisk Delta (thats how I came to know about the existence of Magisk Delta). Both Magisk 24.3 & 26.1 are not surviving reboots even after flashing (Magisk.OTA.persistence-v1.zip). So staying rooted on a stock factory rom is still an issue. I will try TukiRom1.3 though I request OP to compress the ROM file from 2.7GB to lesser if possible.
2> GSI RAW image files don't go past the bootlogo screen. I tried system image files Elixir, LPOS, Crdroid, EvolutionX, Derpfest etc., none of them booted no matter what dmverity or multidisaabler etc. I flashed before or after. The same raw images used to boot on the same device when it was Andoid 11 but now on Andoid 13 Stock Factory ROM CWD1 GSI images dont boot.
3> Since Magisk is either bootlooping the device after reboot/ After flashing Magisk/or Magisk patched images not surviving reboots, so when I flash the Stock boot image it goes straight to download mode with Vbmeta signed using public key etc errors, or if I flash Magisk patched boot image from TWRP it stuck on Shamshung logo.
4> I have tried some of Dev Roynas ROMs [https://sourceforge.net/projects/a51-builds-by-royna/files/] but they all end up with [TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")] also same error through Sideload.
5> I tried (systemrw_1.32_flashable) by Dev Lebigmac but since the altercation between XDA & Lebigmac on March 2023 he got banned from XDA, I cant get hold of (systemrw_1.4_flashable) to try to check if CWD1 Update is RO-Rom and anything other than 1UI5.1 based wont flash etc.
If anyone has any solutions for CWD1 Factory Stock Rom pls assist. TIA