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.

[ROM][UNOFFICIAL][PNX_sprout][11] LineageOS 18.1

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
First Time Install / Clean Flash
Ask to get your bootloader unlocked first! - t.me/NokiaX7
(All your data including the one in internal storage will be removed, so proceed with a caution! Or a backup )
MAKE SURE TO BE ON THE LATEST FIRMWARE/UPDATE BEFORE FLASHING
Also download vbmeta.img
Use the following command in fastboot to boot TWRP-
Code:
fastboot erase system
fastboot erase userdata
fastboot erase vendor
fastboot erase boot
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash boot twrp.img
*Now hold down the Vol+ button and Power button* while at the same time you enter this command-
fastboot reboot
*When the phone vibrates or androidone screen comes for 1-2 sec, leave the buttons*
After phone boots to TWRP, enter the password if encrypted.
Transfer boot.img to phone and flash it to both slots
Flash NikGapps or OpenGapps(Optional)
Flash Magisk(optional)
Format Data
Reboot
Downloads :
lineage-18.1-20210808-UNOFFICIAL-PNX_sprout
TWRP.img
Bugs :
None found, you tell me!
Hella Thanks to @zskynet_09 for all the trees!
Sources :
Kernel

Thread closed.
Let us know when you are ready foe us to re open.
Thanks
MOD EDIT THREAD REOPENED AS LINK WILL BE ADDED

[ROM][11][PNX_sprout][DISCONTINUED] PixelExperience Plus [AOSP]

{
"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"
}
PixelExperience Plus for Nokia 8.1 [PNX_sprout]
What is this?
PixelExperience Plus is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
HDR
GCam(not included)
GPay, BHIM(Use magisk hide and for gpay hide magisk by changing name)
Super Smooth
Instructions
First Time Install / Clean Flash
Ask to get your bootloader unlocked first! - t.me/NokiaX7
(All your data including the one in internal storage will be removed, so proceed with a caution! Or a backup )
MAKE SURE TO BE ON THE LATEST FIRMWARE/UPDATE BEFORE FLASHING
Also download vbmeta.img
Use the following command in fastboot to boot TWRP-
Code:
fastboot erase system
fastboot erase userdata
fastboot erase vendor
fastboot erase boot
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash boot twrp.img
*Now hold down the Vol+ button and Power button* while at the same time you enter this command-
fastboot reboot
*When the phone vibrates or androidone screen comes for 1-2 sec, leave the buttons*
After phone boots to TWRP, enter the password if encrypted.
Transfer boot.img to phone and flash it to both slots
Flash Magisk(optional)
Format Data
Reboot
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download ROM
Download TWRP
Credits
zskynet09 for trees
@sei for testing and screenshots
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
PE BUILDS BY ME HAVE BEEN DISCONTINUED IN FAVOUR OF EVOX.
Android OS version: 11.0.0_r29
Security patch level: August 2021
Build author/Device Maintainer: @DS1884
Source code: https://github.com/PixelExperience
Kernel code: Kernel

Does it has Google Photos Unlimited Storage?

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 ^......^

[TUTORIAL] Revive your hardbricked M3 and revert back to EMUI 5/ Android 7

WARNING​
This tutorial is only for you who have hardbicked your M3 (BTV-DL09). This is the last option you have. If you still access any method or at least fastboot, please consider to use any other method.
Once again it is the last method to revive your device
As usual DO IT WITH YOUR OWN RISK. I WILL NOT RESPONSIBLE FOR ANY DAMAGE OF YOUR DEVICE
Scenario:
For some reason your device is hardbricked and nothing userfull method suitable to bringging back you device
Tools :
IDT Application can be downloaded here
Board Software can be downloaded here
ADB Software
HUAWEI APP Extractor can be downloaded here
Tools to open your device screen
USB cable
STEP 1:
Revive your device into basic firmware using IDT
Please refer to this tutorial to doing that. Your test point can be found by opening your screen device. please be careful when you open it.
{
"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"
}
This method will bring you to the basic firmware of this device (EMUI 2).
From here, your SIM will be locked. (I'm still dont know how to unlock, but everyting work well)
STEP 2
Update to EMUI 4
To do that you can use one of the following method:
a. Using dload
b. Using fastboot (I use this method because i dont have SD Card or USB OTG ), so i will explain this method.
You can download the firmware here
After downloaded, ectract UPDATE.APP from dload folder using APP Extractor.
Extract following files to your ADB folder:
- BOOT.IMG
- CUST.IMG
- SYSTEM.IMG
- FASTBOOT.IMG
- RECOVERY.IMG
Now we will flash IMG file.
* Boot into fastboot by connecting your device using USB cable
* open CMD then locate to your ADB folder
* type following command
Code:
adb devices
//to check connected devices
adb reboot fastboot
//you rdevice will reboot into fastboot mode
fastboot devices
//check connection
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash fastboot fastboot.img
fastboot reboot
Now disconnect your device. Your device should reboot system and running Android 6 EMUI 4.1
NOTE : First boot will take long time, so be patient
STEP 3
UPDATE TO EMUI 5 ANDROID 7
To do that we need to install TWRP. First you can download this version of TWRP for EMUI 4
You can refer to this tutorial to install TWRP
Download this OEM info
Copy oem info folder to SD Card or USB OTG. Place it in the folder TWRP/BACKUPS/<SERIAL NUMBER>
You can find SERIAL NUMBER on about tablet>>status>>SERIAL NUMBER
Download firmware BTV-DL09C100B307 form here and extract two zip file into SD Card/USB OTG root folder
Put in your SD Card/USB OTG
Now reboot into recovery > restore > locate your OEM info folder > restore.
Install update.zip
Install update_data_full_hw_eu.zip
Wipe
reboot system
First boot will took longer than first boot and you see Huawei logo if success
Congratulation, your device now running Android 7 EMUI 5.0.1
Optional you can install TWRP for android 7 here