Database Info

[GUIDE]SP Flash Tools Explained with OT-6012

Greeting to all owners of MTK SmartPhones!
As this devices are technically documented mainly on Chinese, I will teach you today something about low-level device flashing using SP Flash Tool. For those who may have some experiences, SP Flash Tool is MediaTek's equivalent tool for low level flashing like Odin on Samsung devices or RK Batch Tool on RockChip SoC.
Introduction 1 - What is low level flash tool
Let's just say: it's deeper than android flashing. This way you can backup and restore all parts of your NAND chip, and all partitions, not just android and kernel specific ones such as boot, system, data, cache but also nvram, uboot and so on, important for GSM radio. There are two main parts: preloader.bin, which is installed in very first block of your device's eMMC chip - it's first program which phone run after cold stard, and windows driver which is host-side part needed for DL/DA protocol utilized by SP Flash Tools. Both are essential. If you don't have preloader.bin in your phone, you may have very hard brick which is unable to revive unless jtagged or board remains dead. So, whatever you are doing, keep in mind that you must always have preloader.bin in your phone. If you are using format tools, don't ever format preloader area. This SP Flash Tool is must have backup option as this is only way for You to make complete backup of all partitions and block devices in your phone. You must note that some files like NVRAM are unit specific, they contains IMEI and GSM callibration data and You can't use that from another phone, even if it's from same manufacturer and model. That is exactly why everyone should have their own full backup made with SP Flash Tool. And why should You use SP Flash tools for restore? If you asking me, I'm happiest when i don't need to, but there are cases when it's only solution, because no matter how hard you brick your phone, as long as preloader sits inside, you will be able to restore it to fully working state this way as opposite for custom recoveries which requires some working partitions (recovery, boot, ...) SP Flash Tool is so powerful that you may install custom recovery even without rooting ie. Let's go see how it works:
For this occasion, I will use my Alcatel one touch idol MINI (OT-6012X) as test device, but this may work also for all MTK smartphone devices with EMMC, but I don't know abot their new UBIFS.
{
"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"
}
Tools needed:
MTK Preloader Drivers - Collection of drivers for MTK Phones
SP Flash Tool - Latest Smart Phone Flash Tool v3 5.1408.00 (20/03/2014)
MTK Droid Root & Tools - Version 2.5.3 needed for splitting dump IMG file into separate partition images and retrieving SCATTER file
Chapter 1 - BACKUP
I'm starting this with assumption You already have drivers installed. If you did not installed drivers, see how to install drivers in Appendix.
1. Shut down your phone with cold start (disable Quick Start/Fast Boot options in shutdown menu or settings)
2. Extract SP Flash Tool you downloaded form URL above and run flash_tool.exe as administrator.
3. Go to Download page and pusth scatter-loading button, than load scatter.txt for You device. You can find this file sometimes in OTA update.zip, or you can create it with MTKDroid Tools but they can be faulty. I provided scatter.txt for Alcatel one touch idol MINI (OT-6012X) as MTKDroid Tools can't generate working scatter for this Alcatel phone.
4. Now navigate to Readback tab and push Add to add new set for read. Save file as ROM_0.img, and for OT-6012X fill other fields just as show on this picture below.
ROM_ALL.img - start address: 0x0000000000000000 and for lenght open scatter.txt and find where /cache partition starts. In my case it's 0x534C0000. This way You will dump all data of your eMMC chip up to cache partition.
Last two eMMC partitions are /cache and /data and we need to add them as well, but separately, beacuse we need all partitions to flash after formatting eMMC. In my case, for OT-6012X it's:
cache.img - start address: 0x00000000534c0000 lenght: 0x09200000
userdata.img - start address: 0x000000005c6c0000 lenght: 0x60000000
Note that I took only first 1.5 GB of data because SP Flash Tool won't let me take more for some reason. But content of /data is not relevant for me, not just because last 0.7 GB was empty space, and I wiped it in recovery right after flashing anyway.
5. Now push Read Back button and connect your phone which is still OFF to PC with USB cable. Soon readback process will start. Depending on your USB speed and configuration it will take up to 45 min or 1h for 3GB im not sure but it's plenty of time to take full dump
6. Once readback is complete you will see green circle as sign all pass well. Congratulations now you have partial dump of your phone memory, you may now disconnect USB, exit SP Flash Tool, and turn on your phone.
Chapter 2 - PREPARING FILES FOR RESTORE
1. Turn on your phone with USB Debugging enabled and installed ADB drivers.
2. Extract MTKDroid Tools and run MTKdroidTools.exe as administrator. Once your phone is detected by MTKDroid Tools you can push Blocks Map button and than you can push Create scatter file button in new window which will popup. This way you can creat scatter file for some devices. With my phone, file which has been generated this way didn't work for an unknown reason, that is why i included this file for download.
3. Navigate to root, backup, recovery tab and push button To process file ROM_ from Flash Tool, and select image dump file you created in previous chapter (ROM_ALL.img). Now MTKDroid Tool will split IMG file into many separate files for each part of eMMC which you will flash later in Chapter 3. If you are asked to create CWM just say No and push Cancel when prompted to input recovery file.
4. Few minuts later you will see "---Task Completed---" in log, and prepared files are located in subdirectory backups of MTKDroid Tool folder. Afterwards you may close MTKDroid Tool. All files are prepared for flashing back into phone as they may bee needed sooner or later.
Chapter 3 - RESTORE
Finally we come to restore but you don't need to take a breath now as this easily could be an easiest step to do
1. Shut down your phone with cold start (disable Quick Start/Fast Boot options in shutdown menu or settings)
2. Run SP Flash Tool again and navigate to tab Download, load scatter.txt for your phone (if you using OT-6012X its included in SP Flash Folder by pressing on Scatter-loading and selecting scatter.txt
3. Double click on each partition and select respectable file from backups folder in MTKDroid Tools you created in Chapter 2. Note that last two partitions (/cache and /data) are located wherever you saved them with SP Flash Tool. See picture for more details:
4. Select Format All + Download from drop-down menu like on picture below. This is essential becasue if you broke partition table, whole eMMC be formatted and all partitions must be rewritten. That is why we need both /cache and /data partitions, all checkboxes must be checked. If you try to unselect single partition you wont be able to do format before flashing.
5. Push Download button and connect your phone (which is off) with PC via USB cable. Process should start, with formating eMMC, and downloading all data respectable. It can take up to 30 mins or so, depending on partition image sizes. After process is finished you will see green circle on screen again. Unplug USB from phone and turn it on.
That would be all.
Appendix - INSTALLING DRIVERS
This going into appendix section as this is needed to be done only once - when You use SP Flash Tool for the very first time. Theoretical background behind this is: we use memory testing routine as it is safe to do and it will initiate preloader to be detected into Windows OS device manager. Once we get new hardware found, we install drivers.
Install adequate drivers from MTK Preloader Drivers via automated setup.
1. Shut down your phone or prepare for cold start if you are in bootloop
2. Run SP Flash Tool and navigate to Memory Test tab
3. Check RAM Test and Data Bus Test ONLY, all other checkboxex must remain clear, than push Start button. DO NOT CHECK EMMC Test!
4. Connect your phone (which is still OFF) and PC with USB cable, afterwards new hardware found wizard should popup. If you installed drivers it should be automatically found, if not, you still may install drivers manually, respectably to device type and OS you are using.
5. Once driver setup is finished, SP Flash Tool will show green circle as signal that RAM is tested and it's ok. If you see red circle RAM is nok.
Addendum - COLD START from BOOTLOOP
If your OT-6012X is in bootloop, try this solution. It it discovered on OT-6012X but may also works for other MTK devices with embedded battery. (devices without detachable battery)
1. Press and hold power button and vol - button together and keep pressed. After 8 sec (when phone turns off) release power button but keep pressed volume - for few seconds more, than release it. Now your phone should stay off.
2. Connect to USB and wait for charging battery few seconds than unplug USB. Now your device is in COLD START state.
3. Now (from cold start state) press volume + and power button at same time, and after phone turns on release power but keep volume + pressed untill recovery loads than restore NAND backup if you have TWRP installed.
If I didn't referred some methods used in this guide it means that they are discovered by myself. If this guide helped you, please don't forget to push thanks button. Have fun.

Hi CyberianIce and thanks for this tutorial, but BitDefender detected a Trojan in MTKDroid_Tools...
With Virustotal (scan of rar archive) : 17 / 51
EDIT : After verification, the same problem is in MTKDroid_Tools official link too but I'm not sure it's a false positive...

paradiselost28 said:
Hi CyberianIce and thanks for this tutorial, but BitDefender detected a Trojan in MTKDroid_Tools...
With Virustotal (scan of rar archive) : 17 / 51
EDIT : After verification, the same problem is in MTKDroid_Tools official link too but I'm not sure it's a false positive...
Click to expand...
Click to collapse
One must turn A/V off when using MTK Droid Root & Tool and SP Flash Tool because they recognize common android exploits (faramir, boromir, etc) as potentially threat. However, that is false alarm, because it is harmless when used for this purpose and absolutely needed for rooting.

CyberianIce said:
One must turn A/V off when using MTK Droid Root & Tool and SP Flash Tool because they recognize common android exploits (faramir, boromir, etc) as potentially threat. However, that is false alarm, because it is harmless when used for this purpose and absolutely needed for rooting.
Click to expand...
Click to collapse
Can you upload somewhere a full backup with all partitions for sp flash tool ?
I have Alcatel 6012x and I bricked it with Sp Flash tool , I used format ALL + download without preloader and others,only cache,userdata and Android ( system ) ,I got an error and now only what can I see it is a blue LED .

Preloader is still alive, you have chance to get things back working if you have Your backup, my files wont help much:
http://forum.xda-developers.com/showthread.php?p=49902338

ok now it is alive,but I do not understand ,it had a very bad signal or what?
Because with Vodafone Romania I do not have signal no where inside of my home,outsite I have signal,and with Cosmote Romania 2G GSM I have 1-2 signal lines and with Cosmote Romania 3G WCDMA everywhere is on roming and I have with it 3-4 signal lines insite of my house .

dfani511 said:
ok now it is alive,but I do not understand ,it had a very bad signal or what?
Because with Vodafone Romania I do not have signal no where inside of my home,outsite I have signal,and with Cosmote Romania 2G GSM I have 1-2 signal lines and with Cosmote Romania 3G WCDMA everywhere is on roming and I have with it 3-4 signal lines insite of my house .
Click to expand...
Click to collapse
It is possible you ruined your GSM calibration data which are located in NAND chip NVRAM. They contains unit-specific GSM radio calibration data and IMEI? How could you format all without preloader? Such operation is hardly possible because if you uncheck any part of emmc, format become regular update of selected partitions.

No that isn't from the last write without preloader , because that problem I had it in the past and for that I tried to re-write the fw
Can I do something ?

Applies to all other phone?

dfani511 said:
No that isn't from the last write without preloader , because that problem I had it in the past and for that I tried to re-write the fw
Can I do something ?
Click to expand...
Click to collapse
Just restore previous backup as described in first post.
EvangelineX said:
Applies to all other phone?
Click to expand...
Click to collapse
Yes but you must obtain scatter.txt for your specific phone.

I think it will work for others phone but not with the scatter from here,if you reed this tutorial he say there it work for others ....
and CyberianIce thank you for this tutorial was helpful

CyberianIce said:
Just restore previous backup as described in first post.
Yes but you must obtain scatter.txt for your specific phone.
Click to expand...
Click to collapse
this phone are not mine it belongs to a friend,today he say me the phone had this problem after when it come from service,they repair the touchscreen , and he doesn't want to sent it back because it stay on service too much (1 mounth)
Can I re-write these files which are responsable with GSM Calibration from NAND?

You don't know that partitions are flashed, which are affected and which are not, and what is for what. How you expect from me to help? You don't know what is problem, and what they did in service. Sorry, this thread is for backup/restore OT-6012 with SP Flash Tool, not for general phone help. If you had NVRAM, protect_f and protect_s backup from your previous backup you could restore that, otherwise don't touch anything.

Is it safe to flash an updated preloader on the same device but different firmware version? E.g. On is running v01 rev and the other device is v02? This is on stock rom and newer bought device has newer firmware

It's never safe to flash preloader, specially if it is from another phone.

Help
Please help. I am new to Android. I bought Alcatel one touch idol mini 6012D with two sim and no sd card. I have installed Twrp and cant update my smart. Please tell how to remove twrp? How to install stock firmware? Please help.

There is no TWRP for dual SIM mode. You tried to flash TWRP from 6012X into 6012D, what for Christ sake you thinked? You need SP Flash Tools backup which is different from this described in this tipic. You have to find stock recovery elsewhere and flash with mobileuncle if your phone can boot at all

guide is best

i think this TUT work on my OT d5 Kitkat 4.4.2 but for some reason SP flash tool did not detect my alacatel D5,,
can you help me,,
im making CWM ,,but when i click read back nothing happens?
and yes i have scatter file generated from MTK driod tool,
driver installed,

what about this error,, "PMT change for the room,it must be downlaoded"

Bricked after Downgrade to Pie, adb not working, pls help

[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"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"
}
Any thoughts please?

I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.

akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.

strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)

who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.

TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.

who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition

[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".

[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
How to fix "Find Device storage corrupted. Your device is unsafe now" ?
(At your own risk... I'm not responsible for damage or brick)​
Required :
- Be rooted and have TWRP installed !
- Miui Fastboot ROM : xiaomifirmwareupdater.
Tutorial :
- Download the Miui Fastboot ROM corresponding to your current Miui version.
- Extract files from the archive downloaded, open "images" folder and copy "persist.img" file in your smartphone Internal Storage (past the file directly in Internal Storage, not in folder !).
- Reboot in Recovery Mode.
- In your TWRP, open the Terminal (in "Advanced").
- Enter this two commands :
Code:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
Code:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
- Reboot your smartphone.
More information :
I got this problem when I restored my Miui backup after try a Custom Android 10 ROM. At each smartphone boot, I got the message "Find Device storage corrupted. Your device is unsafe now", fingerprint unlock was set on "Off", and registered fingerprint(s) was deleted. When I added a new fingerprint, it was registered (until the next boot), but didn't work.
If you do a little research, you can find a other method on some websites where you use fastboot to flash persist.img. I tried and sadly it not work ("FAILED (remote: Error: This image isn't allow download)"):
{
"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"
}
Credit :
- Muz_paray.

My English isn't that good, but thankyou, works great for me, i´m using orange fox not twrp

SkullDead said:
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
How to fix "Find Device storage corrupted. Your device is unsafe now" ?
(At your own risk... I'm not responsible for damage or brick)​
Required :
- Be rooted and have TWRP installed !
- Miui Fastboot ROM : xiaomifirmwareupdater.
Tutorial :
- Download the Miui Fastboot ROM corresponding to your current Miui version.
- Extract files from the archive downloaded, open "images" folder and copy "persist.img" file in your smartphone Internal Storage (past the file directly in Internal Storage, not in folder !).
- Reboot in Recovery Mode.
- In your TWRP, open the Terminal (in "Advanced").
- Enter this two commands :
Code:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
Code:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
- Reboot your smartphone.
More information :
I got this problem when I restored my Miui backup after try a Custom Android 10 ROM. At each smartphone boot, I got the message "Find Device storage corrupted. Your device is unsafe now", fingerprint unlock was set on "Off", and registered fingerprint(s) was deleted. When I added a new fingerprint, it was registered (until the next boot), but didn't work.
If you do a little research, you can find a other method on some websites where you use fastboot to flash persist.img. I tried and sadly it not work ("FAILED (remote: Error: This image isn't allow download)"):
View attachment 4877981
Credit :
- Muz_paray.
Click to expand...
Click to collapse
it doesn't work anymore its says " Invalid spars file format at header magic failed to read spars file" what should do now . tried in orange fox recovery

Svg.Sakib said:
it doesn't work anymore its says " Invalid spars file format at header magic failed to read spars file" what should do now . tried in orange fox recovery
Click to expand...
Click to collapse
I had the same error and found 2 ways to solve it:
1st:
I had flashed the MIUI 11 Rom from August 27 2019. I simply replaced it by the latest stable EU Rom and the error disappeared . Next I flashed the Rom from August 27th back.
2nd:
Find device storage corrupted your device is unsafe now
1. You need Unlocked Bootloader and TWRP. You can boot in TWRP instead of flashing it.
2. Download the fastboot ROM for the device. Extract it and copy persist.img file to the internal memory of the phone. Make sure put the file in internal storage rather than in any folder.
3. Put the phone in fastboot Mode, Power Button and Volume Down key.
4. Boot in TWRP by "fastboot boot twrp.img" command.
5. In the TWRP Main Menu. Go to Advanced ------ Terminal
6. Write the below 2 lines:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
7. Reboot the Phone and check.

Svg.Sakib said:
it doesn't work anymore its says " Invalid spars file format at header magic failed to read spars file" what should do now . tried in orange fox recovery
Click to expand...
Click to collapse
Directly flash it it persist partiton

I have a Xiaomi Redmi 4x with the latest version Miui Global 11.0.2 (NAMMIXM) on Android 7.1.2 N2G47H.
The device is locked and has error: find device storage is corrupted so because of that I can`t add my Xiaomi account to Mi Unlock status and this mean I can't unlock the bootloader, I tried to flash the official ROM again with Mi Flash but is giving me errors so can`t flash the ROM again....
What I can do?

Shepherd_47 said:
I have a Xiaomi Redmi 4x with the latest version Miui Global 11.0.2 (NAMMIXM) on Android 7.1.2 N2G47H.
The device is locked and has error: find device storage is corrupted so because of that I can`t add my Xiaomi account to Mi Unlock status and this mean I can't unlock the bootloader, I tried to flash the official ROM again with Mi Flash but is giving me errors so can`t flash the ROM again....
What I can do?
Click to expand...
Click to collapse
Also booting to twrp is not possible....
Any suggestions?

Shepherd_47 said:
Also booting to twrp is not possible....
Any suggestions?
Click to expand...
Click to collapse
The current recovery is stock recovery

Shepherd_47 said:
The current recovery is stock recovery
Click to expand...
Click to collapse
Did you get any solution, I am sailing on the same boat?

prasanth1947 said:
Did you get any solution, I am sailing on the same boat?
Click to expand...
Click to collapse
Yes
So the solution is to log in to the device on Mi account with the mi account used to unlock the device. So basically you can unlock again the device but with the same Mi account used on the first attempt. If normal log in to Mi account is not possible, try to log in using google (press google icon on the bottom-you must have Google account in the phone, and it must be linked with mi account. After that i just launched miflash_unlock-en-5.5.224.24 and it worked instantly.
I didn't add mi account to mi unlock status even and still was working.
So the key is mi account used for device unlock for the first time- ( DIDN`T WORKED WITH OTHER MI ACCOUNTS)

Shepherd_47 said:
Yes
So the solution is to log in to the device on Mi account with the mi account used to unlock the device. So basically you can unlock again the device but with the same Mi account used on the first attempt. If normal log in to Mi account is not possible, try to log in using google (press google icon on the bottom-you must have Google account in the phone, and it must be linked with mi account. After that i just launched miflash_unlock-en-5.5.224.24 and it worked instantly.
I didn't add mi account to mi unlock status even and still was working.
So the key is mi account used for device unlock for the first time- ( DIDN`T WORKED WITH OTHER MI ACCOUNTS)
Click to expand...
Click to collapse
I will try to post more info about this later, contact me if you need help

Shepherd_47 said:
I will try to post more info about this later, contact me if you need help
Click to expand...
Click to collapse
buy the way this is the solution for UNLOCKING DEVICE, after that is easy, just install Minimal ADB and Fastboot and download recovery for your phone, put recovery in the Minimal ADB and Fastboot folder and open Minimal ADB and Fastboot and run command: fastboot flash recovery recovery.img
after that fastboot boot recovery.img
and you are in TWRP - from there is easy to ,,fix find device storage is corrupt" if you have that error...

working for Redmi Note 7/7S Lavender

Had the same issue with my F3. I know this thread is a bit old. But I am in no really luck. I tried this method but it doesn't work. It says an error " invalid sparse file format at header magic
Failed to read sparse".

ram1MB said:
Had the same issue with my F3. I know this thread is a bit old. But I am in no really luck. I tried this method but it doesn't work. It says an error " invalid sparse file format at header magic
Failed to read sparse".
Click to expand...
Click to collapse
Alternatively, you can flash it with twrp. Copy persist image to internal storage, boot to twrp, select "Flash Image" by pressing the big button located at lower right, select the image file and upon selection the twrp shows another window to choose what are you flashing. Choose "Persist" and slide to flash, it takes just one or two seconds and after that just reboot. I had this problem earlier and fixed by completing these steps.
This thread is very useful. Many thanks to @SkullDead and Muz_paray

ammaralidj said:
Alternatively, you can flash it with twrp. Copy persist image to internal storage, boot to twrp, select "Flash Image" by pressing the big button located at lower right, select the image file and upon selection the twrp shows another window to choose what are you flashing. Choose "Persist" and slide to flash, it takes just one or two seconds and after that just reboot. I had this problem earlier and fixed by completing these steps.
This thread is very useful. Many thanks to @SkullDead and Muz_paray
Click to expand...
Click to collapse
I had this issue as well, thanks a lot for this thread! Fix worked, and I had safely returned to stock.

Worked for me on redmi y1 UGG no sensor, wifi, BT and location was not working post doing this everything started working again, thanks a lot.

taratay said:
I had this issue as well, thanks a lot for this thread! Fix worked, and I had safely returned to stock.
Click to expand...
Click to collapse
i cannot find presist.img file for redmi note 10 mojito. it is not present in rom folder. where to find it

haris43242 said:
i cannot find presist.img file for redmi note 10 mojito. it is not present in rom folder. where to find it
Click to expand...
Click to collapse
Hi haris43242 try this topic https://forum.xda-developers.com/t/persist-file-redmi-note-10.4312093/

my device is MI 11x and I'm facing this issue. I tried all these methods but nothing happens, the error is still there.
also, MI 11x has A/B partition, and TWRP and OrangeFox both don't show the persist partition.
can anyone help me with this?

[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE

Thanks to:
chaosmaster / k4y0z: GitHub / XDA
xyzz / xyz`: GitHub / XDA
Dinolek: GitHub / XDA
How to install:
1. Download the attached file: VD171_MTK-bypass.zip.
2. Extract the file and open the folder.
3. Run and install python: python-3.9.1-amd64.exe.
Keep atention: You need to select "Add Python to PATH" before starting the installation.
{
"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"
}
4. Open cmd or powershell and execute this command:
pip install pyusb pyserial json5
5. Go to the Driver folder and right-click on the cdc-acm.inf file, then click Install and then, close window.
6. Run and install filter wizard: libusb-win32-devel-filter-1.2.6.0.exe.
7. Launch filter wizard.
8. Select Install a device filter and click Next.
9. Connect powered off phone with volume- button to boot in EDL mode.
10. Once you see new MediaTek USB Port in the list, select it and click Install.
Now, you are ready for bypassing EDL !
How to bypass:
1. Go to the Bypass folder. Run the script: bypass.bat.
2. Connect powered off phone with volume- button to boot in EDL mode.
3. Once you get "Protection disabled" at the end, without disconnecting phone and usb, run SP Flash Tool.
4. Once the SP Flash Tool opens, click Options > Options > Connection.
5. Select UART mode and select Baud rate to 921600.
Now, you are ready for flashing !
How to update:
1. Download latest release of the tool: https://github.com/MTK-bypass/bypass_utility/releases/latest
2. Download latest release of payloads: https://github.com/MTK-bypass/exploits_collection/releases/latest
3. Extract the content of both files to the Bypass folder.
Now, you are updated !
How does the bypass work?
Dissecting a MediaTek BootROM exploit
A bricked Xiaomi phone led me to discover a project in Github that uses a MediaTek BootROM exploit that was undocumented. The exploit was found by Xyz, and implemented by Chaosmaster. The initial exploit was already available for quite a while. Since I have managed to revive my phone, I am documenti
tinyhack.com
All Credits To:
chaosmaster / k4y0z: GitHub / XDA
xyzz / xyz`: GitHub / XDA
Dinolek: GitHub / XDA
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
#NoAuth #NoAuthentication #No-Auth #No-Authentication #MediaTek #Xiaomi
#MiAuth #MiAuthentication #Mi-Auth #Mi-Authentication #XiaoMiAuth #free
#XiaoMiAuthentication #XiaoMi-Auth #XiaoMi-Authentication #unbricking
#unbricked #unbrick #unbrickingru #unbrickedru #unbrickru #remoterepair98
#MTK #MT6572 #MT6735 #MT6737 #MT6739 #MT6750 #MT6765 #MT6762
#MT6761 #MT6768 #MT6771 #MT6785 #MT8127 #MT8163 #MT8173 #MT8695

Redmi 10x 5 (ATOM) still not supported
[2021-02-07 06:26:57.702746] Waiting for bootrom
[2021-02-07 06:27:05.293534] Found port = COM3
Traceback (most recent call last):
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\main.py", line 169, in <module>
main()
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\main.py", line 44, in main
device.handshake()
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\src\device.py", line 88, in handshake
self.check(self.read(1), to_bytes(0x5F))
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\src\device.py", line 84, in check
raise RuntimeError("Unexpected output, expected {} got {}".format(gold, test))
RuntimeError: Unexpected output, expected 0x5f got 0xa0
Press any key to continue . . .

kurosaberex said:
Redmi 10x 5 still not supported
Click to expand...
Click to collapse
Unhappy, MT6875 is not supported yet.
Probably it will be supported too soon

VD171 said:
Unhappy, MT6875 is not supported yet.
Probably it will be supported too soon
Click to expand...
Click to collapse
will gladly wait for it hope it comes soon

kurosaberex said:
will gladly wait for it hope it comes soon
Click to expand...
Click to collapse
I hope to see all existing devices supported as well.
This EDL authenticated mode is really disappointing.
We love Xiaomi.
But, we are hostages to Xiaomi. Sad...

Should I Format All + Download??

-glyne- said:
Should I Format All + Download??
Click to expand...
Click to collapse
NO.
Never try to flash in "format all" mode.
Or you will lose all identifications of your device, like imei and mac.
If you are facing "PMT changed" message, your device has an older scatter file inside it.
This is because there is any modification to the scatter file you are using to the scatter file used before.
There are some minor changes to the MIUI 11 scatter file for MIUI 12, but nothing significant.
You can flash using "firmware upgrade" mode.
But, bootloader will be LOCKED again and userdata will be erased.
If you want to backup the state of unlocked bootloader and then restore it.
Just follow this guide before the "firmware upgrade": https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/

VD171 said:
NO.
Never try to flash in "format all" mode.
Or you will lose all identifications of your device, like imei and mac.
If you are facing "PMT changed" message, your device has an older scatter file inside it.
This is because there is any modification to the scatter file you are using to the scatter file used before.
There are some minor changes to the MIUI 11 scatter file for MIUI 12, but nothing significant.
You can flash using "firmware upgrade" mode.
But, bootloader will be LOCKED again and userdata will be erased.
If you want to backup the state of unlocked bootloader and then restore it.
Just follow this guide before the "firmware upgrade": https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/
Click to expand...
Click to collapse
Or if firmware upgrade doesn't work, he can backup IMEI, after format and flash is done, He can flash the persist, protect1 protect2 nvdata and nvcfg partitions which he backup-ed, this way he doesn't lose IMEI, successfully unbricks device.

Communos said:
Or if firmware upgrade doesn't work, he can backup IMEI, after format and flash is done, He can flash the persist, protect1 protect2 nvdata and nvcfg partitions which he backup-ed, this way he doesn't lose IMEI, successfully unbricks device.
Click to expand...
Click to collapse
Don't forget to backup seccfg partition.
It controls the state of locked/unlocked bootloader: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/
Here, you can find the full list of the most important partitions to backup: https://forum.xda-developers.com/t/...lin-device-redmi-10x-4g-redmi-note-9.4229633/

VD171 said:
Don't forget to backup seccfg partition.
It controls the state of locked/unlocked bootloader: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/
Here, you can find the full list of the most important partitions to backup: https://forum.xda-developers.com/t/...lin-device-redmi-10x-4g-redmi-note-9.4229633/
Click to expand...
Click to collapse
Thanks

@VD171 sir i'm on Miui china 12.0.8 when i run libusb and turn off my phone and hold volume - button then connect the cable it boot into fastboot mode instead of booting into edl mode pls help

MerliinTop1 said:
@VD171 sir i'm on Miui china 12.0.8 when i run libusb and turn off my phone and hold volume - button then connect the cable it boot into fastboot mode instead of booting into edl mode pls help
Click to expand...
Click to collapse
Try other combinations, like vol up or vol up + vol down.
I'm not sure, I'm on global 12.0.6.0 and the combination for EDL mode is just vol down.

VD171 said:
Try other combinations, like vol up or vol up + vol down.
I'm not sure, I'm on global 12.0.6.0 and the combination for EDL mode is just vol down.
Click to expand...
Click to collapse
Tried em all still not working sir

MerliinTop1 said:
Tried em all still not working sir
Click to expand...
Click to collapse
Are you sure your device is properly detected?
Are you sure usb driver is properly installed?

VD171 said:
Are you sure your device is properly detected?
Are you sure usb driver is properly installed?
Click to expand...
Click to collapse
Yeah its detected i can hear the detecet sound and i installed the driver u attached

MerliinTop1 said:
Yeah its detected i can hear the detecet sound and i installed the driver u attached
Click to expand...
Click to collapse
Then, I have no ideia what is the problem.
You need to keep trying.

VD171 said:
Then, I have no ideia what is the problem.
You need to keep trying.
Click to expand...
Click to collapse
Ok sir thx for ur attention

MerliinTop1 said:
Ok sir thx for ur attention
Click to expand...
Click to collapse
Try another cable.
Try another usb port.
Try usb 2.0. Try usb 3.0.
Try another computer.
If results are exactly same, probably you have a problem with your device.

VD171 said:
Try another cable.
Try another usb port.
Try usb 2.0. Try usb 3.0.
Try another computer.
If results are exactly same, probably you have a problem with your device.
Click to expand...
Click to collapse
I tried diff ports still same result and i'm using the original cable its still new
I didnt try another computer tbh
But i think the miui china 12.0.8 have something diff.....they may f**kd the edl mode cuz they know its bypass-able however ill wait the new update (A11) which should come soon(1 or 2 days) and try again since it has a new firmware than the previous 12.0.6 firmware and see whats gonna happen
Btw I'm trying to do this just to flash Eng rom and fix imei which i lost when i was trying to flash miui china with sp tool.....imei being lost doesn't effect on edl mode no?

MerliinTop1 said:
I tried diff ports still same result and i'm using the original cable its still new
I didnt try another computer tbh
But i think the miui china 12.0.8 have something diff.....they may f**kd the edl mode cuz they know its bypass-able however ill wait the new update (A11) which should come soon(1 or 2 days) and try again since it has a new firmware than the previous 12.0.6 firmware and see whats gonna happen
Btw I'm trying to do this just to flash Eng rom and fix imei which i lost when i was trying to flash miui china with sp tool.....imei being lost doesn't effect on edl mode no?
Click to expand...
Click to collapse
If you lost your imei, you can't recover it forever.
Only Xiaomi Centre can recover it.
I'm sorry.

How To Guide [CLOSED] POCO X3 PRO{vayu}{Bootloader Unlocked} ROOT-RSA DISABLE-DIAG MODE-EFS RESET-IMEI REPAIR-ENG QCN:{NO NEED BOX}

Hi
in this thread i will show you how to do each of this:
POCO X3 PRO{vayu}
1.TWRP+ROOT
2.RSA DISABLE
3.DIAG MODE
4.EFS RESET
5.IMEI REPAIR
without Any Box.
----------
***********You Will Do it By Your Responsibility and I'm not Responsible for any damage to your Device,Read Thread Carefully and then Do it and try not to mess your device*********
--------
Requirements:
-Iphone 6 Board for its Resistor
-Xiaomi Imei Tool Link
-Qpst Link
-Twrp + EFS Reset Tool Link
-Magisk 23 zip file Link
-Magisk Manager APP Link
-Stock Firmware Link
-Eng Firmware LINK >>>>File Password is : iaasteam.com<<<<<<
--------
I Did All of this Steps and Job Done this Means Its Tested dont Blame me For Any Damage to Your Device
Do it Just if you know What you Do
Not for Newbies
---------------
Some Poco X3 Pro Devices Bootloop After EFS Reset:
it can caused Becuase of Firmware Security or RSA Encryption of Device Imei:
We Have Two Method For this:
1.Flash ENG Rom Then Continue The Steps 1 to 4 and no need root(Because ENG rom have root access already)
2.Do entire Steps on stock Firmware then if it gives error try method 1
But if Not if this methods Work Problem is with the Step 1.RSA DISABLE and you should Check You Resistor
---------------
1.RSA DISABLE
You Should Disable RSA of the Phone To Write Imei on it.
For this
{
"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"
}
Remove this resistor and Change it with Picture 2 from Iphone 6 Board 50k resistor
for better Performance of work you can Measure its kohm by ohm meter it should be 45 to 50k by ohm meter
replace the resistor in picture one with this
------------
First Time We do entire of Job on stock Firmware if firmware security Prevent us to do our work then we flash the phone with eng firmware,and eng firmware no need root just need flash twrp
-----------
2.TWRP + ROOT
Download Reqirment TWRP + EFS RESET TOOL
Reboot phone in fastboot and connect it to pc
run .bat file and press key 1
twrp will be flashed
Wipe/factory reset Phone by twrp if storage not shown for installing packages reboot agian to twrp
Download Magisk zip and Apk from reqirement
****Go to Backup Section of TWRP>Check EFS Partition>Back it up and Copy it to PC for Avoid Baseband null***** And then Continue the other Steps
Connect Phone to pc
Copy Magisk23.zip to phone storage and install it by twrp
Reboot phone to system
and install Magisk Manager
Now phone Should Be Rooted.
Each time you reboot your phone from Recovery to system,TWRP recovery will be deleted onm your phone
when you see your phone rooted
----------
3.DiagPort & QCN Backup & Modify
Download QPST in reqirement
Xiaomi Imei Tool in reqirement
Install Xiaomi Imei Tool
View attachment 5515295
Connect phone to pc in normal Mode
Enable USB Debugging and Select File Transfer mode on phone
Click Open Diag Port now your diag prot enabled
***** Do not use Xiaomi Imei tool QPST******
Install QPST from Reqirements Section
Run QPST Configuration(you can search in start menu for it Because it dont have shortcut in desktop)
QPST Configuration Detect Your phone in diag mode then
Click on Start Clinets>Software Download>Backup
Backup QCN And Xqcn Both(QCN is enough but I suggest you to backup both of them)
when you backed up Qcn
Open Xiaomi Imei Tool
And run QCN Editor
View attachment 5515301
1.select Qcn file you Backed Up
2.Select Registration Method on 2Sim Like in picture
3.Write Imei 1 and imei 2
4.Click Create Button and Save our Modified QCN.
--------------------
4.EFS Reset And Modified QCN Restore(Imei Repair)
Warning:You should Backed up your EFS By TWRP in STEP 2 and Copied it in PC And Then Come To This Step
Reboot your Phone to Fastboot
-Open TWRP+EFS reset .bat file you downloaded in step 2
-press 1 and wait untill phone reboots to twrp recovery
-in the .Bat File Menu press key 2 when phone already is in twrp menu
-Reboot Phone to system Again Now Efs Reseted and Phone Dont Have IMEI
*******If You Dont Replaced Correct Resistor in Step 1 then your phone should give you NV Data Corrupted Error in this Step or Phone Restarts Each Time********
-When Phone Comes Up Enable Diag port Again and run QPST
Run QPST Configuration(you can search in start menu for it Because it dont have shortcut in desktop)
QPST Configuration Detect Your phone in diag mode then
Click on Start Clinets>Software Download>Restore
Select Modified Qcn that you Created By Xiaomi Imei Tool in Step 3 and Push Start.
Wait Untill Progress Done And Phone Reboots.
Now You Should Have Poco X3 pro Dual Imei Repaired.
If you Get Any Error Just Read Troubleshooting Section
--------------------------------
*****************Troubleshooting****************
1-After EFS Reset Phone Restarts and dont Work Correct
A:it can caused by two problem: 1- firmware security 2-Resistor Change Problem
For Firmware Security:
-Download ENG Firmware From Requirement section and Flash it by fastboot
-then Reboot To Fastboot again Flash Twrp recovery and do not try to root ENG firmware(Because it have Root Access by default)
-In Twrp Reset EFS Again In Step 4
-Reboot to ENG firmware and Enable Diag Port and Write Modified Qcn
-Flash Global Stock Firmware i have linked to requirement no diffrence at all you can flash any version of global firmware
***If Again Problem Not fixed It's your 50k Resistor Changing Problem and you should check it***
2-When I Enable Diag Port QPST Can not find my phone
A:Just Check You Drivers And Device Manager
--------------------------------
*****In Some Websites Says You Need ENG QCN for imei repair,No need of ENG QCN Just Modify Phones Original QCN******
--------------------------------
Files Uploaded To mega.nz and Links Stays Alive forever.
--------------------------------
Push Thanks Button,Like if this Guide fixed your problem
If you have a question, feel free to ask and I will answer as soon as possible
***********You Will Do it By Your Responsibility and I'm not Responsible for any damage to your Device,Read Thread Carefully and then Do it and try not to mess your device*********

I have a question, if I have a Poco X3 Pro with a blank imei and an unknown baseband, I don't have the EFS backup or the box where the imei comes from, changing the resistance and following the step-by-step guide could I recover the imei?

felixpaz1992 said:
I have a question, if I have a Poco X3 Pro with a blank imei and an unknown baseband, I don't have the EFS backup or the box where the imei comes from, changing the resistance and following the step-by-step guide could I recover the imei?
Click to expand...
Click to collapse
if problem not with the hardware
yes of course you can fix it
when you remove resistance and disable rsa
and write its original imei on it.
Any change in the imei ID of the device is illegal in most countries, please respect the law.and Also respect XDA Law about it.

I've reverted the OP and thread title as they were, as well as unlocking it, and will PM all appropriate users.
Thank you.

roirraW edor ehT said:
I've reverted the OP and thread title as they were, as well as unlocking it, and will PM all appropriate users.
Thank you.
Click to expand...
Click to collapse
Thank you, I took the time to write this
Thank you for your positive management

After removing the resistor can it be re-installed?

Jssdje said:
After removing the resistor can it be re-installed?
Click to expand...
Click to collapse
no then rsa enabled again

Non of one of your attachment are available please update the pictures of resistor pic
Thanks

mosirezaei said:
Non of one of your attachment are available please update the pictures of resistor pic
Thanks
Click to expand...
Click to collapse
Hi thank you for report i have uploaded them but now the attachments deleted
wait untill tomorrow i will fix it

dashti.95 said:
Hi thank you for report i have uploaded them but now the attachments deleted
wait untill tomorrow i will fix it
Click to expand...
Click to collapse
Hello
I still waiting for the attachment photos of resistors
if you can send it to my email will be great
[email protected],com
thanks bro

backup efs eng firmware mode .backup was saved fsc,fsg,modemst1 and modemst2. after reset efs baseband unknown. flash backup partition in fastboot mode. still baseband unknown.
problem solved by write qcn.

alak said:
backup efs eng firmware mode .backup was saved fsc,fsg,modemst1 and modemst2. after reset efs baseband unknown. flash backup partition in fastboot mode. still baseband unknown.
problem solved by write qcn.
Click to expand...
Click to collapse
Can you give me the qcn please....
Mail : [email protected]

kallumama said:
Can you give me the qcn please....
Mail : [email protected]
Click to expand...
Click to collapse
tomorrow i will send you

I repair 2nd Imei of Poco X3 pro Vayu from UMT RSA method in eng Rom. I get backup of QCN. it shows imei1 0 imei2 (86*************12) but when I flash global rom. it shows NV data corrupt. I again flash ENG rom. write that backup QCN it shows Original IMEI's but when I flashed Global Rom It shows nv data error again. although Original imei of that Phone. I erase efs from Fastboot that also doesn't help me. what is the problem & how to solve it.
can I flash custom rom for mobile work normally without sim?
or custom rom doesn't help?
if any firmware that solve my problem & phone work normally (without sim) kindly tell me.

saqibsm said:
I repair 2nd Imei of Poco X3 pro Vayu from UMT RSA method in eng Rom. I get backup of QCN. it shows imei1 0 imei2 (86*************12) but when I flash global rom. it shows NV data corrupt. I again flash ENG rom. write that backup QCN it shows Original IMEI's but when I flashed Global Rom It shows nv data error again. although Original imei of that Phone. I erase efs from Fastboot that also doesn't help me. what is the problem & how to solve it.
can I flash custom rom for mobile work normally without sim?
or custom rom doesn't help?
if any firmware that solve my problem & phone work normally (without sim) kindly tell me.
Click to expand...
Click to collapse
1.What Flasher you using to flash data?
2.give me a list of files in your firmware directory please list it for me.
I need to know because:
In qualcomm series of xiaomi phones you have a file named *NON-HLOS*
You should use NON-HLOS file from eng Rom not the original file from global rom.(NON-HLOS file is eng modem file)
give me info i will help you

dashti.95 said:
1.What Flasher you using to flash data?
2.give me a list of files in your firmware directory please list it for me.
I need to know because:
In qualcomm series of xiaomi phones you have a file named *NON-HLOS*
You should use NON-HLOS file from eng Rom not the original file from global rom.(NON-HLOS file is eng modem file)
give me info i will help you
Click to expand...
Click to collapse
I have a doubt in which directory of the ENG Rom I find the NON-HLOS file and if I can back it up, I "install" it in the global Rom, would the QCN written when it was in the ENG Rom work?

dashti.95 said:
1.What Flasher you using to flash data?
2.give me a list of files in your firmware directory please list it for me.
I need to know because:
In qualcomm series of xiaomi phones you have a file named *NON-HLOS*
You should use NON-HLOS file from eng Rom not the original file from global rom.(NON-HLOS file is eng modem file)
give me info i will help you
Click to expand...
Click to collapse
I have followed the guide, I was able to recover the original imei that came in the box, I have changed the 50ohm resistor, when I go back to stock rom I have baseband, I have both imei, but I have no signal, if I want to call a message appears saying "deactivate the airplane mode to call"

felixpaz1992 said:
I have followed the guide, I was able to recover the original imei that came in the box, I have changed the 50ohm resistor, when I go back to stock rom I have baseband, I have both imei, but I have no signal, if I want to call a message appears saying "deactivate the airplane mode to call"
Click to expand...
Click to collapse
Its because of qcn you used its not compatible with your device.

dashti.95 said:
Its because of qcn you used its not compatible with your device.
Click to expand...
Click to collapse
I used the published QCN ENG and edited it with the imei that I found in the original box of the equipment, now both imei appear in the global Rom but I have the ghost plane mode, absolutely everything works except the mobile radio

felixpaz1992 said:
I have followed the guide, I was able to recover the original imei that came in the box, I have changed the 50ohm resistor, when I go back to stock rom I have baseband, I have both imei, but I have no signal, if I want to call a message appears saying "deactivate the airplane mode to call"
Click to expand...
Click to collapse
two questions:
1.Which NON-HLOS you used?Stock or Eng?
2.What type of Qcn you used?.xqcn or .qcn?