Database Develop

Soft BRICKED A2 (bootloop)

I have bricked my A2 today. I first unlocked the bootloader then insatlled GCAM.
everything was fine, but i tried to install XPOSED (sdk 27) from Magisk module, then rebooted from magisk. My set is stuck at android one animation.
I downloaded official firmware of A2 and tried to flash via mi flash tool, always gets an error of "FLASH_DEVCFG_A ERROR" . Then i tried by clicking on "flash_all_except_data.bat" file, cmd just opened and closed very soon, Same thing happended with "flash_all_lock.bat" ,again cmd just opened and closed.
Still my phone is stuck at Android one animation, and i cant flash or boot my set.
EDIT :: USED. /FASTBOOT -W TO UNBRICK PHONE

Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4

minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
should i flash only those images? because i have some more image files than the llist, kindly check the screen shot

minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Now stuck at devcfg
PS C:\Users\KSN\Desktop\platform-tools> fastboot flash devcfg_b C:\Users\KSN\Desktop\images_V9.6.10.0.ODIMIFE_8.1\images\devcfg.img
target reported max download size of 536870912 bytes
sending 'devcfg_b' (47 KB)...
OKAY [ 0.005s]
writing 'devcfg_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.007s
bluetooth_a , bluetooth_b was flashed successfully

try fastboot flashing unlock_critical

munchy_cool said:
try fastboot flashing unlock_critical
Click to expand...
Click to collapse
This appears everytime . :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Syed Shahriar said:
This appears everytime . :/View attachment 4581400
Click to expand...
Click to collapse
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot

munchy_cool said:
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
Click to expand...
Click to collapse
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please

Syed Shahriar said:
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Click to expand...
Click to collapse
GOT THESE ERROR::
PS C:\adb> fastboot flash system_a C:\adb\images\system.img
error: cannot load 'C:\adb\images\system.img'
my system iso is there in that location
but successfuly done fastboot flash vendor_b C:\adb\images\vendor.img
and fastboot flash vendor_a C:\adb\images\vendor.img

What are you even doing with all those commands
You need to download latest ADB, that is the first that you need to do, and second, copy all of the images from stock rom to your adb folder, it will be easier for commands to work.
And then start your cmd.exe with administrative privileges (right click on cmd in search bar of windows start, and "run as administrator").
Then move yourself from directory to your adb directory with commands from DOS, like "cd.." for going back from directory, and "cd nameofdir" to go into directory.
So move yourself in adb directory, then type the commands from the upper link to flash those .img one by one.
Oh yes, one other thing, you need to check if you see your mobile device in fastboot, did you install correct drivers.
When you are in adb folder, in cmd type fastboot devices, and you should see your mobile connected, if not, then you can type all you want, the phone is not recognized with pc connection.

Right, so... follow this guide to make sure you've unlocked your bootloader successfully. After you've finished, also add in the command "fastboot flashing unlock_critical". I'm not sure why it didn't work for you in the first place - but I know for a fact it works, because I did it to my own A2.
Make sure you've installed adb/drivers as attached by that link above. Why? 'Cause that's what I did, so I know it should work.
Then go here, extract the files to the same folder as platform-tools (the adb and fastboot tools folder), and run flash-all.bat.

Hey bro i do it too, tô solve, just do a fastboot unlock_critical
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585

I had the same issue, no OS installed.
Adb Sideload and OTG didn't worl no matter what I tried.
I followed this thread, and it worked properly without errors, not even one.
It took me 5 minutes to recover my dead MiA2 device to a smooth original/official ROM built.
Locled OEM, rebooted the device and everything is working perfectlt.
Thank you all for the info.

Cant flash TWRP - error: device '(null)' not found in adb

Hi all.
I would not be writing this topic if everything I did havent failed.
I tried every possible solution to this I was able to find on the internet - nothing has worked so far.
I tried doing this on different PCs - same result.
I flashed Syberia ROM but didnt like it so decided to go with MIUI 9.7.10.12. I already had TWRP at that time but when I flashed MIUI everything erased, I mean everything - data, storage, TWRP everything.
System works fine but I am unable to flash TWRP with constant message: error: device '(null)' not found.
ADB device not found but fastboot works and ADB shows device connected. The phone is authorized with USB debugging turned on, drivers installed on PC, TWRP image file is correct. I am lost :/ dont know what to do.
Please help

there is no need to flash recovery via adb. twrp should be flash from fastboot. turn off your phone, hold volume down and power for few seconds and phone will boot in fastboot mode.
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
and done.

sunilromy said:
there is no need to flash recovery via adb. twrp should be flash from fastboot. turn off your phone, hold volume down and power for few seconds and phone will boot in fastboot mode.
and done.
Click to expand...
Click to collapse
Where should I type in the command if not in ADB?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I go manually to recovery (vol up + power) the phone reboots to stock recovery so the TWRP is not installed. I tried different versions of TWRP. no progress

Type
Fastboot reboot
and now you can go to twrp recovery by manually .. Power off phone, volume up + power
Or you can also do this

sunilromy said:
Type
Fastboot reboot
and now you can go to twrp recovery by manually .. Power off phone, volume up + power
Or you can also do this
Click to expand...
Click to collapse
fastboot reboot --> phone goes to system
vol up + power --> stock recovery
the problem is TWRP is not flashing :/
it is not USB debugging problem, not USB drivers problem.
The other thing is I can go to fastboot through ADB only when im on CHARGING MODE, it doesnt work on MTP MODE where it should.

brother you just flashed twrp successfully in the screenshot you posted, point is miui, dont let it stick when you boot to system and reboot.
you should, do this. go to fastboot
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
you can flash other modded recovery which will stick. like zcx

sunilromy said:
brother you just flashed twrp successfully in the screenshot you posted, point is miui, dont let it stick when you boot to system and reboot.
you should, do this. go to fastboot
you can flash other modded recovery which will stick. like zcx
Click to expand...
Click to collapse
thx, that command worked

but why I cant go to TWPR using vol up + power?

fastboot boot twrp.img doesn't work for me, after it just black screen with MI logo and "Unlocked" for a long time...
can't enter twrp in any way after success flashing :crying:

Need help with this. Can't sideload with adb fastboot is working fine though.

How can I solve "FAILED (remote: This partition doesn´t exist error)"?

From TWRP > tap Advanced > Terminal > run command: mkdir -p /data/media/0/
Copy the rom to your phone internal storage from pc
Install by finding the transfered rom in the internal storage.

Flash Magisk boot Failed

Hi,
Followed the guide but getting this error. I unlocked boot loader but when tried to flash magisk boot. This error comes. I am on latest Build .Is that be a problem ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

alwynjoshy said:
Hi,
Followed the guide but getting this error. I unlocked boot loader but when tried to flash magisk boot. This error comes. I am on latest Build .Is that be a problem ?
Click to expand...
Click to collapse
Put the patched.img in your platform-tools folder. If it still doesn't work with..fastboot flash boot magisk_patched.img.....then try using command prompt instead of power shell :good:

Badger50 said:
Put the patched.img in your platform-tools folder. If it still doesn't work with..fastboot flash boot magisk_patched.img.....then try using command prompt instead of power shell :good:
Click to expand...
Click to collapse
I tried putting in the folder, still the same error, Will try with using CMD

alwynjoshy said:
I tried putting in the folder, still the same error, Will try with using CMD
Click to expand...
Click to collapse
Your doing this in bootloader mode as well correct?? ?

Yea bro, you see the command, "fastboot devices"

Only thing I can think of at the moment is make sure your fastboot/adb files are the latest ones.
In case you need to download them
https://developer.android.com/studio/releases/platform-tools

alwynjoshy said:
Yea bro, you see the command, "fastboot devices"
Click to expand...
Click to collapse
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img

Jiggs82 said:
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img
Click to expand...
Click to collapse
Thanks buddy. It worked for me. Also found one more command, but didn't try, posting just for the info.
fastboot flash —slot=all boot magisk_patched.img

Jiggs82 said:
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img
Click to expand...
Click to collapse
Deleted

Jiggs82 said:
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img
Click to expand...
Click to collapse
I only flash slot a, So is there any downside if I didn't flash B slot?

Where to get vbmeta.img, and did I use the correct boot img?

Hi,
I don't have a vbmeta.img at hand, but I have a "vbmeta_a" and "vbmeta_b" partition checked by the command written in the install instructions.
So how can I continue with this?
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
So the question is where do I get vbmeta.img from?
And just to be sure:
I'm on LineageOS18.1, unlocked bootloader. The install instructions of Magisk tell me to patch a "boot image". But which one?
The LineageOS installl instructions mention a "vendor boot img", this one: https://wiki.lineageos.org/devices/sake/install#flashing-the-vendor-boot-partition
Is this correct?
Or otherwise, where to get the boot image out of https://download.lineageos.org/sake ? I just see this inside the zip:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or is boot image = recovery image? LineageOS does provide a recovery image:
that is flashed into boot partition like this:
fastboot flash boot <recovery_filename>.img
So is this the one I need to take to patch?

Ok, I found out that you actually can extract the boot.img from the payload.bin using this instructions: https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas
So now I have a boot.img from there. Is this the correct one?
I am still a bit puzzled because LineageOS install instructions let me install the recovery into the boot partition, acting as a de-facto boot image:
fastboot flash boot <recovery_filename>.img
Yes, they actually let me do this and it worked fine, see https://wiki.lineageos.org/devices/sake/install#temporarily-booting-a-custom-recovery-using-fastboot
So then which should I choose? <recovery_filename>.img? boot.img? Or sake_vendor_boot.img? It's so confusing...
And I found out that boot.img and the <recovery_filename>.img are actually almost the same files. Only like a few ~50 bytes differ. So in LineageOS terms, <recovery_filename> is actually a boot image.
But still sometimes a few bytes can make a difference between working phone and brickwall. So I will still wait for a conformation which one I should choose.
Also still open question about vbmeta.img?

Mario545 said:
where do I get vbmeta.img from?
Click to expand...
Click to collapse
usually inside rom.zip :

loopypalm said:
usually inside rom.zip :
Click to expand...
Click to collapse
Yes, indeed, thanks. After extracting the payload.bin, a vbmeta.img was present.
But, and maybe I am a bit overcautious here, what is the purpose of flashing the unmodified stock vbmeta.img again? I mean I didn't see any instructions to acutually modify the vbmeta.img. Did I miss something?

Mario545 said:
Yes, indeed, thanks. After extracting the payload.bin, a vbmeta.img was present.
But, and maybe I am a bit overcautious here, what is the purpose of flashing the unmodified stock vbmeta.img again? I mean I didn't see any instructions to acutually modify the vbmeta.img. Did I miss something?
Click to expand...
Click to collapse
use the one present in custom roms
vbmeta is flashed to prevent the system from restoring the default recovery

It worked! I didn't brick my phone! Thank you so much for your answer.
To summarize, if you are on ASUS Zenfone 8 + LineageOS 18.1, and you are confused which image to patch:
Recovery image NO!
Vendor boot image NO!
boot.img extracted from the LineageOS zip by following https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas YES!
And this extraction process also gives you the vbmeta.img you need to flash (unmodified!).

Mario545 said:
ASUS Zenfone 8
Click to expand...
Click to collapse
twrp is available for that phone
no need to complicate the simple tasks ^......^

General [CLOSED] ⚗️AOSP(SHARED)CrDroid V8.8 - UNOFFICIAL by DigiGoon

A12.1​Flashing instructions​adb reboot bootloader
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
fastboot reboot recovery
in recovery wipe data(factory reset)
then select apply update from adb
and from pc sideload rom.zip and reboot
DOWNLOAD
https://dl.androidrom.dev/?dir=roms/crdroid/milahaina
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Others AOSP ROM
https://forum.xda-developers.com/t/shared-aosp-rom-a13-by-ipsbhangu.4483171/
https://forum.xda-developers.com/t/aosp-shared-evolutionx-v6-7-unofficial-by-preet0608.4486623/​

why this rom isn't in the developement thread?
Is it because it's shared?

Edmondo Occhipinti said:
why this rom isn't in the developement thread?
Is it because it's shared?
Click to expand...
Click to collapse
Nope,as long as the developer does not publish it on XDA it will remain shared. (I also shared the Siberia and I deleted the thread as soon as the official one arrived). That's all.

NOSS8 said:
Nope,as long as the developer does not publish it on XDA it will remain shared. (I also shared the Siberia and I deleted the thread as soon as the official one arrived). That's all.
Click to expand...
Click to collapse
So shared roms go on the General section?

Edmondo Occhipinti said:
So shared roms go on the General section?
Click to expand...
Click to collapse
yeap ,because i am not a developer.

Hello.
Someone try it ?

I tryied to install it, but a get an error when i try to flash boot a_b.img, cmd said that s not a *. Img

Cengiz67 said:
I tryied to install it, but a get an error when i try to flash boot a_b.img, cmd said that s not a *. Img
Click to expand...
Click to collapse
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced - flash current TWRP.

So :
Flash and boot twrp ok
Tryin' to do :
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
Say that is not booting and vendor img

Cengiz67 said:
So :
Flash and boot twrp ok
Tryin' to do :
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
Say that is not booting and vendor img
Click to expand...
Click to collapse
Img must be in the same folder as the command.
try to install platform tools and put the img inside.
check syntax.

I did it but doesnt work

Cengiz67 said:
I did it but doesnt work
Click to expand...
Click to collapse
Post a screenshot of the CMD
Install with commands or with the TWRP but not both.

OK when i try again i ll post it

Does screen mirror work properly in this rom?
Or what are the current and known bugs?

Anyone use this ROM as a daily driver?

Update
https://dl.androidrom.dev/?dir=roms/crdroid/milahaina

THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Senior Moderator