[GUIDE] Restoring 'Persist' partition to fix all kinds of (sensor) issues - Xiaomi Redmi 5A Guides, News, & Discussion

[GUIDE] Restoring 'Persist' partition to fix all kinds of (sensor) issues - Xiaomi Redmi 5A Guides, News, & Discussion

Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Code:
fastboot %* flash persist "%~dp0images\persist.img" || @echo "Flash persist error" && exit /B 1
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Now edit the line to look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="[B]persist.img[/B]" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Code:
persist 0x8932e19d
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
Code:
cd "Paste copied path here"
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
Code:
fastboot oem edl
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.

Hey there,
The accelerometer on my Redmi 5A was messed up badly after a few miui.eu rom flashes and none of the other custom roms would boot up too. I found your guide to be very helpful and to the point. I was able to flash the stable rom successfully which fixed the sensors. Huge thanks to you! .
---------- Post added at 07:08 AM ---------- Previous post was at 06:58 AM ----------
Hey there,
The accelerometer on my Redmi 5A was messed up badly after a few miui.eu rom flashes and none of the other custom roms would boot up too. I found your guide to be very helpful and to the point. I was able to flash the stable rom successfully which fixed the sensors. Huge thanks to you! .

sanchaz12 said:
Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Now edit the line to look like this:
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.
Click to expand...
Click to collapse
We can just flash the sensorfix zip via twrp

NaAnBcEhEuL9A8K7 said:
We can just flash the sensorfix zip via twrp
Click to expand...
Click to collapse
link >???

ahked.ragab said:
link >???
Click to expand...
Click to collapse
I dont have link, got it from https://t.me/Redmi_5a

this method worked, at first I was confused, I was looking for ways to fix it. after I found this, this worked. thanks man

hi, can I flash the persist.img file via adb in fastboot.

Here is the link for sensorfix.xip
https://drive.google.com/file/d/1ZgaWydW4c7Eo5vuRw_Vhc6EVmBFThNV2/view
Give me thanks
---------- Post added at 08:46 AM ---------- Previous post was at 08:40 AM ----------
sanchaz12 said:
Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Code:
fastboot %* flash persist "%~dp0images\persist.img" || @echo "Flash persist error" && exit /B 1
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Now edit the line to look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="[B]persist.img[/B]" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Code:
persist 0x8932e19d
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
Code:
cd "Paste copied path here"
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
Code:
fastboot oem edl
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.
Click to expand...
Click to collapse
You don't need to this much sh*t !
Just flash the provided zip via twrp.
You won't loose data

thank you Asif the legend ?. however i found a alternate way to fix it. fastboot or edl mode or normal twrp are not able to access the persist location. i flashed orage fox recovery to mount persist location. then in miui official fastboot rom i got persist image. and i am able to flash it via new recovery. all sensors are working fine now.

Welcome

Atif the legend sir you are truly legend thank uh so much. I tryed many things to fix this problem but now all sensors working fine. Thanks for your help.

How to quit edl mode? i received the hello error, and then even when i do press power and vol down i cant reboot it
---------- Post added at 12:35 PM ---------- Previous post was at 12:10 PM ----------
sanchaz12 said:
Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Code:
fastboot %* flash persist "%~dp0images\persist.img" || @echo "Flash persist error" && exit /B 1
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Now edit the line to look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="[B]persist.img[/B]" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Code:
persist 0x8932e19d
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
Code:
cd "Paste copied path here"
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
Code:
fastboot oem edl
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.
Click to expand...
Click to collapse
Help plz? it shows the qualcomm on devices manager but i cant quit edl mode and gives me that error from hello message, holding power plus anything does not reboots it

jasonhelene said:
How to quit edl mode? i received the hello error, and then even when i do press power and vol down i cant reboot it
---------- Post added at 12:35 PM ---------- Previous post was at 12:10 PM ----------
Help plz? it shows the qualcomm on devices manager but i cant quit edl mode and gives me that error from hello message, holding power plus anything does not reboots it
Click to expand...
Click to collapse
You may have to hold the buttons for up to 30 seconds for the phone to reset, longer than usual.

Mimax 3
Hi, I need to know if this process is valid for a MiMax 3 with Chinese rom and with closed bootloader.
I have the phone without being able to activate Wi-Fi, sim and bluettoh and I think it's because of the persist partition ...
I can put the phone in edl mode. Please help

I wasn't aware lol

Hi,
I have no idea how to extract the MIUI11 beta file to MI 6X, I wanted to use its tutorials but the download link doesn't open, could you tell me which program used to edit this persist.img file? Or if you can make this file available. I have but it works only with MIUI 10 and I'm on MIUI 11.

Is using EDL mode without unlock bootloader?
I have same issue.
I get same issue error (find device is…. your device unsafe)
But , All the sensors are not work.
#proximity sensor
#Auto rotation
#Camara(full Black Screen)
#Youtube
#Flash light
Are not working….
Please help me.
_______________________________________
Is i am using flash the phone without unlock bootloader Using EDL mode.
Please help me.
_____________________________________

thankyou so much sir it worked can you help me with lost imei and simcards not working

i cant make it work
Vinod Banwala said:
thankyou so much sir it worked can you help me with lost imei and simcards not working
Click to expand...
Click to collapse
what did you do? at me says comething like cant do, cause its only read disk, when goes to the persist drive help

How can i do to make my own sensorsfix.zip?
Give me thanks
---------- Post added at 08:46 AM ---------- Previous post was at 08:40 AM ----------
You don't need to this much sh*t !
Just flash the provided zip via twrp.
You won't loose data[/QUOTE]
Friend i want to make my own file to flash in other device (MI 9T Pro), can you show us how try it. I did extracted the files into persist.img, but i didn't find the sns.reg, file included in your .zip.
This instruction could help to many people with this problem.
Thank u so much. :good:

Related

Dell Venue 7: Won't Boot After Replacing frameworks-res.apk

Dell Venue 7 BOOT PROBLEM
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730

ManXXXX said:
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730
Click to expand...
Click to collapse
You need to flash again the stock rom, the factory reset won't work.
You can found it here http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2 and flashing through fastboot
I don't know what frameworks-res.apk you used, but maybe you forgot set the right permissions, or maybe you took the files for other device.

DL VN 7
Is there some tutorial for flash with fastboot??, i never did it, and i don't want destroy some other..

Go here to Dell's opensource site.. http://opensource.dell.com/releases/...loper-edition/

Link
No working link

ManXXXX said:
No working link
Click to expand...
Click to collapse
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake

ADB Driver
Isrks said:
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake
Click to expand...
Click to collapse
When i installing the driver, always: Install failed, i have Windows 10 and i added language code

ManXXXX said:
When i installing the driver, always: Install failed, i have Windows 10 and i added language code
Click to expand...
Click to collapse
I found this around here, is for windows 8 but maybe useful for Windows 10
https://software.intel.com/en-us/android/articles/how-to-install-intel-usb-driver-for-android-devices-on-windows-8

ADB Driver
Nah nah this, i think ADB driver.

ManXXXX said:
Nah nah this, i think ADB driver.
Click to expand...
Click to collapse
unfortunately i don't have a computer with windows 10 so i can't solve easily.
i found this googling, so with a little of faith :fingers-crossed: , is the same error than yours http://android.stackexchange.com/questions/118823/how-to-install-adb-drivers-on-windows-10-opoit's for the OPO, but is about the same "intalling adb driver", so could work
in a dessesperate attempt, you can use the update usb drivers in "myKit_BATCH" typing "1" after typyng "ACCEPT"

I fixed it with 15 seconds installer!, i gng try to fix tablet

But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit

ManXXXX said:
But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit
Click to expand...
Click to collapse
Ahh that's add driver not recognize your tablet, I suppose that you connect in fastboot mode,
Try using the option of update the adb driver in Mykit_BATCH, you don't lose nothing trying.
Other option is trying the dell's method http://opensource.dell.com/releases/Venue_8_3830_CloverTrail_plus/developer-edition/Download the pdf file and read the instructions from page 2 to page 9 if still not working
here is the sdk tools for windows that the pdf wants

I downloaded SDK tools, i installed Google usb driver, because it say not installed, when it was installing it said: Disable adb driver, ineffectual, error code -1, but after install it work good, so i will test with this, when no i will try another way, that u wrote here

Finally, tried method, no work, finally, update ADB no working for me, cuz installation always fail, next one DELL method, working but i found problem, dell wrote update driver via google extra with codes, BUT
My first code: USB\VID_413C&PID_B119&REV_????, ????, i think there is something wrong
My second code: USB\VID_413C&PID_B119, i think this one is alright, but then up

Finally with dell next page i'm in!, but my kit no working, in every command shut down, so i using windows cmd, it working too

Mhm bruh, no i'm in flash system, sending 'system' awesome, but it's more than 2 minutes , when it will work, omg u r awesome

Bruh, yay, i did it, thq u r master <33

ManXXXX said:
Bruh, yay, i did it, thq u r master <33
Click to expand...
Click to collapse
Are you telling that the dell method works?
The good new is that your tablet is back (with some problems in the way but work, ). after all now you know how to flash through fastboot. If anyelse goes wrong again, you know what to do
NOTE: Maybe your want to replace the framework-res again, but only will work if is for your device. So i recomend that you modify your stock framework-res by yourself (you can use images or xmls from other sources to your framework-res, this should be safer) using apktool manually or a program (there are some of them in xda, choose your favorite )

Yay 50% of dell method worked, just 50% because Dell have tutorial for setting up ADB service, after it i used your tut, thanks, and believe me i will not test it NEVER again.

[SOLUTION] Remove CM BootLogo After Flashing Radio.zip and restore MI BootLogo

Hi Guys,
People are getting CM bootlogo after flashing CMRadio.zip. And yes, I also flashed Radio.zip and got CM bootlogo instead of MI bootlogo.
So, here I am giving a easy tutorial to restore MI bootlogo after flashing radio.zip.
Note: I am not responsible for any software or Hardware damage. Do it on your risk. I have done this method and it worked for me.
Requirements:
1) You need Fastboot & ADB Files Package on your PC.
2) Drivers properly installed on PC, so it can detect your phone in fastboot mode.
3) Mibootlogo image file. (It's attached in this post, download it and place in adb folder.
-------------------------------------------------------------------------------------------------------------------------------
Now Come to the procedure.
--> Download the attached image file (splash.img) from bottom of this post and put it in ADB folder.
--> boot your phone in fastboot mode.
--> attach your phone to computer after booting in fastboot mode.
--> now go to ADB folder. Shift Key + right click on mouse and select 'Open Command Window Here' option.
--> Now, type below this code
Code:
fastboot devices
SEE ATTACHED THUMBNAIL BOTTOM OF THIS POST, FOR REFERENCE.
--> if you can see 'fastboot' device in the list, it means you are good to go to next step. [If you can't see your 'fastboot' device in list, it means your phone is not detected. Please check if you have installed drivers properly and try again].
--> Once you can see your device in list, type the below code and hit enter.
Code:
fastboot flash splash splash.img
--> Once it's done. Again type:
Code:
fastboot reboot
--> Congrats , you have successfully restored your MI bootlogo. :good:
press THANKS button if I helped you in anyway. :victory:

Tutorial was spot on mate. Manage to get rid of that fugly logo and put back the Mi logo .

Done!
It's very easy, thank you very much!

This is exactly what I was looking for for the past week. Thank you bruh
And also, is it possible to make your own photo and put it as splash img?

{s3rious} said:
This is exactly what I was looking for for the past week. Thank you bruh
And also, is it possible to make your own photo and put it as splash img?
Click to expand...
Click to collapse
+1
Enviado de meu Redmi Note 3 usando Tapatalk

ZTE BLADE V9 AntiBrick

This is an guide for when you bricked your ZTE Blade V9, or you destroyed OS without being able to flash with recovery mode(go to step 9).
There are some hacked webservers with articles and shady downloadlinks about this topic, use brain.
I think it can work with an locked oem, because i locked it at some piont earlier.
If your phone isnt showing up as device, give it 1-2 minutes.
Your Phone works even when its showing a black screen.
You do that on your own risk, Iam no ZTE developer.
1. Read the guide, know what you are doing.
2. Download "ZTE Terminal Software", "adb,fastboot,emmc", "ZTE drivers", Stock Rom (update.zip).
Also some "aboot" chinese-factory-testing-firmware which at least gets the phone booting (emmc_appsboot.mbn) from unofficialtwrp at page zte-blade-v9-twrp-3-2-root.
3. Prepare you stock system.img file from the stock rom to flash later. Get an dat to img converter (I used sdat2img.py [email protected]) and extract the img. Rename it to system.img.
4. Boot phone in download mode, the display may be dark but its there ... depends on your damage. Power + Vol- (If it wont work, try starting it normally)
5. Run PortManager from Terminal Software.
6. See COM4(DIAG) -> if anything other adjust drivers in Device Manager. "ZTE 3G Phone AT" should be the right one. There are also some Qualcomm usb drivers which work.
7. Select Port from PortManager as LINE1 USB in "ZTE Terminal Software".
You should now see COM3(DIAG) in ZTE Terminal Software.
8. Use emmcdl on COM3 to flash. Exclude recovery if you have a working/modded one.
I used the original recovery from the stock rom. (emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b aboot emmc_appsboot.mbn & emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b recovery recovery-orig.img)
9. Boot phone in recovery mode. Power + Vol+
10. Select "Reboot to bootloader".
11. Find your phone in ">\ fastboot devices".
12. Get the flashscript from file "\META-INF\com\google\android\updater-script" in the stock firmware "update.zip".
Get all extract commands like "package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");" ;
13. Transfer them into fastboot flash commands and reflash all partitions. (exclude recovery if you have a working/modded one)
Flash your system.img file (step 3) to "system" .
If needed do the same with "vendor".
14. unlock oem.
15. Try restarting your Phone.
16. ???
17. Success !
18. Disable any updates from ZTE, update 1.4 will go good but 1.5 bricks the phone.
18.2 I updated to 1.5 and bricked the phone, because its a "mayor update".
18.3 Follow steps 4 to 8 and only flash the emmc_appsboot.mbn from the STOCK ROM .
19. Do a backup.
Known bugs:
- Wifi cant start -> try reflash (flash system first or including "vendor") or use simcard and hope that ZTE Android update will fix it.
- oem seems locked and unlocked at the same time - ?
Greetings

-deleted-

HELp new phone i buy 2 days ago i erased os by mistake with twrp how to fix ? :(

HELP! new phone xiaomi mi a3 i buy 2 days ago i erased os by mistake with twrp how to fix ? whatsapp me please 0040757161888

rombull said:
HELP! new phone xiaomi mi a3 i buy 2 days ago i erased os by mistake with twrp how to fix ? whatsapp me please 0040757161888
Click to expand...
Click to collapse
Don't panic. Follow these steps.
1. Reboot to fastboot mode by holding down power button and volume down button.
2. Download MiFlash [https://c.mi.com/thread-1329226-1-0.html] and Official firmware Fastboot ROM [https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489]. For firmware fastboot ROM, make sure you grab the correct version of the ROM, if your phone is Europe version, the. choose Europe version of the ROM, and vice versa.
3. Make sure you've installed the required drivers like adb. Open MiFlash, then locate to drivers in the top menu, click on install and wait.
4. Now extract the firmware Fastboot ROM file using WinRAR. You should get a laurel_sprout V10.3.X.0.PF...... (something like that) named folder.
5. Open command prompt in adb folder. Connect your phone to PC, then type "fastboot set-active a" without quotations. You should successfully set your phone slot to "a".
5. Back to MiFlash, click open and select the firmware folder. (Do not select anything inside the folder). Click "refresh" and make sure your device shows up as random numbers. Select flash_all_and_lock option in bottom right side of MiFlash. Than hit "Flash". Sit back and wait.
The phone should reboot and back to the official state. Feel free to reply if you have any questions.

MarcusMario0605 said:
Don't panic. Follow these steps.
1. Reboot to fastboot mode by holding down power button and volume down button.
2. Download MiFlash [https://c.mi.com/thread-1329226-1-0.html] and Official firmware Fastboot ROM [https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489]. For firmware fastboot ROM, make sure you grab the correct version of the ROM, if your phone is Europe version, the. choose Europe version of the ROM, and vice versa.
3. Make sure you've installed the required drivers like adb. Open MiFlash, then locate to drivers in the top menu, click on install and wait.
4. Now extract the firmware Fastboot ROM file using WinRAR. You should get a laurel_sprout V10.3.X.0.PF...... (something like that) named folder.
5. Open command prompt in adb folder. Connect your phone to PC, then type "fastboot set-active a" without quotations. You should successfully set your phone slot to "a".
5. Back to MiFlash, click open and select the firmware folder. (Do not select anything inside the folder). Click "refresh" and make sure your device shows up as random numbers. Select flash_all_and_lock option in bottom right side of MiFlash. Than hit "Flash". Sit back and wait.
The phone should reboot and back to the official state. Feel free to reply if you have any questions.
Click to expand...
Click to collapse
If he has TWRP it's easy. Just download OS on sdcard and flash it

MarcusMario0605 said:
Don't panic. Follow these steps.
1. Reboot to fastboot mode by holding down power button and volume down button.
2. Download MiFlash [https://c.mi.com/thread-1329226-1-0.html] and Official firmware Fastboot ROM [https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489]. For firmware fastboot ROM, make sure you grab the correct version of the ROM, if your phone is Europe version, the. choose Europe version of the ROM, and vice versa.
3. Make sure you've installed the required drivers like adb. Open MiFlash, then locate to drivers in the top menu, click on install and wait.
4. Now extract the firmware Fastboot ROM file using WinRAR. You should get a laurel_sprout V10.3.X.0.PF...... (something like that) named folder.
5. Open command prompt in adb folder. Connect your phone to PC, then type "fastboot set-active a" without quotations. You should successfully set your phone slot to "a".
5. Back to MiFlash, click open and select the firmware folder. (Do not select anything inside the folder). Click "refresh" and make sure your device shows up as random numbers. Select flash_all_and_lock option in bottom right side of MiFlash. Than hit "Flash". Sit back and wait.
The phone should reboot and back to the official state. Feel free to reply if you have any questions.
Click to expand...
Click to collapse
at the line 5 .
G:\Xiaomi MI A3\ROOT MI A3 DIC 2019\ROOT MI A3 10.3.12>fastboot set-active a
fastboot: usage: unknown command set-active
think i am doing wrong something ...

rombull said:
at the line 5 .
G:\Xiaomi MI A3\ROOT MI A3 DIC 2019\ROOT MI A3 10.3.12>fastboot set-active a
fastboot: usage: unknown command set-active
think i am doing wrong something ...
Click to expand...
Click to collapse
your ADB id old. download new version

rombull said:
at the line 5 .
G:\Xiaomi MI A3\ROOT MI A3 DIC 2019\ROOT MI A3 10.3.12>fastboot set-active a
fastboot: usage: unknown command set-active
think i am doing wrong something ...
Click to expand...
Click to collapse
Try using this command, if still not working, download the latest adb from Android SDK and try again.
fastboot --set-active=a

Poco x4 GT bootloop(no fastboot or recovery)

the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please

Hi, did you manage to solve this problem?
What have you tried with mtk client?

hi, I still haven't solved the problem. In mtkclent, I tried to flash the "boot.img" file through brom mode

If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!

Tria13 said:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Click to expand...
Click to collapse
Please PM me if you want your device to be flashed using authorised Xiaomi Server.

I have the same device and I bricked it a while ago by flashing twrp and booting to recovery
From my understanding edl flashing can only be done with an authorized xiaomi account. I don't have one so I had to pay someone on telegram who had one and who could unbrick it. He used a modified version of SP Flash Tool. Although he struggled a bit he got it fixed the next day after I downgraded to windows 10. If you want to avoid bricking this device I recommend you don't use twrp altogether or be very cautious and only use twrp builds from the official telegram group. Compatibility depends on the kernel and android version. For now aosp-based roms have issues with the gpu anyways. (always under 100% load)
Also there is a mtk bootprotect magisk module which might help. (I don't think it will if you flash wrong twrp tho)
I hope these informations are somewhat useful

WolfnHex said:
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Click to expand...
Click to collapse
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.

Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
The thing is ---- Auth bypass is not yet available for your chipset type MT6895.
We have to wait until we can bypass auth to flash using SP Flash tool.

Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
im sorry to hear this
mvikrant97 is right. MT6895 is currently unsupported. you just have to wait

mvikrant97 said:
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
Click to expand...
Click to collapse
Hi, sorry I didn't see your post earlier. Can you solve your phone problem with an authorized Xiaomi Server? You can write your telegram or something else by which I can write to you. Thanks for the answer

Better Mobile App

welcome