Develop Bugs

mi 6 imei and meid gone

i was playing the qpst tool and my imei and meid is gone, it seems like my qpst version is old to write imei to the mi6. but now i can not recover it to its original state. what should i do?
if i copy sdf and sde blocks back to the phone, will it fix it, or should i rewrite qcn file with the qpst tool (qcn file can also be corrupted because of the wrong version qpst tool).
i need to rewrite imei, meid to recover the phone. is there any other tool for it?

Bro, use QPST 460 ver. First dd modemst1, modemst2 and fsg partitions, restart the phone, then restore this xqcn: mega.nz/#!vQ1zyART!bXiW0JY1RGWRdHRZZGo4toUOSZiVqEJjMUdyrI8u97Q

magş said:
i was playing the qpst tool and my imei and meid is gone, it seems like my qpst version is old to write imei to the mi6. but now i can not recover it to its original state. what should i do?
if i copy sdf and sde blocks back to the phone, will it fix it, or should i rewrite qcn file with the qpst tool (qcn file can also be corrupted because of the wrong version qpst tool).
i need to rewrite imei, meid to recover the phone. is there any other tool for it?
Click to expand...
Click to collapse
Did you fix it?

Help
Hello does this solution work with such a small xqcn file ?
mekato said:
Bro, use QPST 460 ver. First dd modemst1, modemst2 and fsg partitions, restart the phone, then restore this xqcn: mega.nz/#!vQ1zyART!bXiW0JY1RGWRdHRZZGo4toUOSZiVqEJjMUdyrI8u97Q
Click to expand...
Click to collapse

Any solution ?
Hint* if you try to flash with Mi FLASH PRO tool in recovery mode it will read IMEI from the phone !!
So IMEI is still written on the phone but where and how to recover back ?!

Hi all !
So IMEI, Baseband unknown and MAC address is gone.
No any backup of it !
Have unlocked bootloader, twrp, xiaomieu rom and phone is rooted.
Following "web find" solutions when tried to backup or restore qcn with QPST (v. 2.7 474)
only getting:
"Memory backup failed"
"Disk error writing to file"
When tried to "dd if=/dev/zero of=/dev/block/sde 34 (sdf4, sdf5)
getting "no space left on device"
(no sense, only trying to wipe, not to write anything)
Also tried the same through terminal on twrp and getting same no space error !
Any idea why, or any other way to recover Imei ?
Thanks !!!!

Kiki.G said:
Hi all !
So IMEI, Baseband unknown and MAC address is gone.
No any backup of it !
Have unlocked bootloader, twrp, xiaomieu rom and phone is rooted.
Following "web find" solutions when tried to backup or restore qcn with QPST (v. 2.7 474)
only getting:
"Memory backup failed"
"Disk error writing to file"
When tried to "dd if=/dev/zero of=/dev/block/sde 34 (sdf4, sdf5)
getting "no space left on device"
(no sense, only trying to wipe, not to write anything)
Also tried the same through terminal on twrp and getting same no space error !
Any idea why, or any other way to recover Imei ?
Thanks !!!!
Click to expand...
Click to collapse
contact me to fix it: fb.me/HomXiaomiColombia

Flasing GSI in realme 3 [Guide][Updated:21-08-19]

Note:
Please take full twrp backup of your phone before you proceed with the below steps
Steps to Flash GSI:
You can follow one of the two methods to flash GSI in Realme 3
Fastboot Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2a. Commands to execute in fastboot mode:
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
fastboot reboot
TWRP Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2. Copy system.img file to your sdcard.
3. Boot your phone to TWRP.
4. Press Install - > Install Image button -> Select the System.img file -> Select System Image-> Swipe to Flash
5. Format Data and then Wipe Cache, Dalvik Cache
6. Reboot, Done.
I used gsi from here (use aosp_arm64, download aosp_arm64-img.zip from artifacts tab and extract and flash system.img only):
https://ci.android.com/builds/branches/aosp-pie-gsi/grid
{
"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"
}
Incase you want to go back to stock follow the same process and flash stock system.img instead of gsi system.img
stock system image: https://www.androidfilehost.com/?fid=1395089523397966778
GSI List(use ARM64 AB or A/B images):
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
ADB Installer tool: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445

what Custom rom did you user sir ?

jeffalaiza said:
what Custom rom did you user sir ?
Click to expand...
Click to collapse
AOSP

fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i flash the gsi rom in gsi list of a-only partition ?

jeffalaiza said:
can i flash the gsi rom in gsi list of a-only partition ?
Click to expand...
Click to collapse
You have to use ab gsi for realme 3 phone, but if you are downloading from ci.android.com, use aosp_arm64

fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i use this rom for daily driver that less of bugs ?

myeganz said:
can i use this rom for daily driver that less of bugs ?
Click to expand...
Click to collapse
I have not used that aosp gsi for much time, so not sure whether it is good for daily usage or not.
You can give it a try and see

What the meaning of veritydecrypt?

jeffalaiza said:
What the meaning of veritydecrypt?
Click to expand...
Click to collapse
Its a file ,link is there in the OP,
https://www.androidfilehost.com/?fid=6006931924117905745

How can i know my device use A,B, or AB ?

Link A.14 .ozip
@fawazahmed0 please link a.14 ozip file? thanks

My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
Click to expand...
Click to collapse
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata

After flashing any rom i lost my cellular network did not showed sim card, i tried to flash stock back, but it was same,
I tried doing fastboot erase nvdata and nvram, now it recognises sim but no network coverage. Is there something I'm missing?

krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
Click to expand...
Click to collapse
android Q ba yung GSI na to bro?

(This problem is solved now, it's just for future reference)
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot

fawazahmed0 said:
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
Click to expand...
Click to collapse
Is magisk root now stable?

yametekudasai said:
Is magisk root now stable?
Click to expand...
Click to collapse
yeah

Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.

my realme 3 1821 is only black screen .. can you tell me why?

Tấn Ho said:
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
Click to expand...
Click to collapse
I tried many GSI ROMs, but VoLTE and Fingerprint works in none of them, execept for these two, everything else seems to work, in Havoc OS atleast

RN8P unknown baseband version

Love (how the hell can you love a machine??? - sorry, I guess I have NO imagination, maybe you can ...) this phone. BUT!! After backing up and restoring using LR TWRP a number of times, then using fastboot to flash_all the original ROM a number of times when I got into flashing problems, my cavalier approach backfired in one of these repetitive actions. Surprisingly, at least to me, I have both IMEI's listed on the status page, but a constant "unknown baseband" version. SIM setting is grayed-out, and I am only on WiFi. Flashing the original ROM (V 10.4.2.0) fixed nothing. Tried V 10.4.1.0, but I can't downgrade: luckily the phone wasn't bricked. Flashed Havoc V 2.9, hoping all partitions would be overwritten, then flashed MIUI V 10.4.2.0, but no change.
Have found no solution from Hovatek (stated flashing original ROM usually repairs the unknown baseband issue), or other sites searched from Google. Any procedure to solve this MTK issue on this phone would be most appreciated.

fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.

Wow!! Thank you so much! I will follow each step and report what I've found.
So impressed with the detail you have given; thanks to have experts such as you willing to share.
Later ....

Crescendo Xenomorph said:
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Click to expand...
Click to collapse
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.

ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695

Coffeemi said:
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Click to expand...
Click to collapse
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.

ppthom said:
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
Click to expand...
Click to collapse
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app

You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.

Coffeemi said:
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have NOT "properly saved a backup file" with the modem partitions, and that is where my trouble lies. I am also not being reminded to set the SIM card info when booting up after flashing the stock 10.4.2.0 ROM, which is strange, because a week ago I was able to go back-and-forth between my restored backed-up files and the stock ROM. On first booting the stock ROM, I was reminded every 10 seconds that my SIM card was not correct (my card is only 3G and the default SIM setup was for LTE), interferring with setting up my WiFi for authenticating my Xiaomi account. Now, with an unknown baseband, the SIM is not recognised by the stock ROM, I can enter my WiFi account without interference; and there no entry for the baseband and nothing for the IMEI numbers.
As soon as my "not proper backup" is restored, the IMEI numbers are set correctly, but no baseband.
My goodness, I will see if anyone online can flash the stock zip file remotely and see if that corrects the problem.
Hey, thank you for paying attention to my problem, and I very much appreciate your time on this.

wang1chung said:
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Click to expand...
Click to collapse
Thank you fellow Canadian :good:; I will try this as well. So great to have all these suggestions from people who know a hell of a lot more than I do. Thank you both Coffeemi and wang1chung.

ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
Better to use LR TWRP, it's the best for Xiaomi phone.
Sadly it's only available for Android 10 version. Better upgrade as Android 10 still way better than their 9 (too much bug).
Link to A10 LR-TWRP: https://mega.nz/file/Ad4TUTTA#_xT16vOzYK-O8qaWEHPYxfdi4wNpK5Ang9maN5iO_-U
If no error being corrected then sadly I dunno more except for hardware issue (baseband chip is broken, I saw one case in Mi Community forum). Hope not this case. :crying:
You're welcome friend. The Move Certificate module is for AdGuard actually, its to clear those network being monitored notification when you use AdGuard's HTTPS filtering.

Thank you Coffeemi, wang1chung and of course Crescendo Xenomorph. You've all paid attention to this problem, and it is very much appreciated.

Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.

ppthom said:
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
Click to expand...
Click to collapse
Can you provide me the steps. Because I'm having the same vesion but with IMEI Invalid. My phone accidently got update to MIUI 11 and the Baseband got ruined.!!!

Somehow Android 10 in this phone will corrupt something in nvdata if you do modification on the fly (somehow like they unable to load it properly, thus no baseband with corrupted BT MAC).
How to know if your BT MAC is corrupted? It'll default to 00:00:46:00:00:01.
BT MAC should be one step above WIFI MAC (if your WIFI MAC is AC:1C:05:AC:43:01, your BT should be AC:1C:05:AC:43:02).

Found the culprit: any Magisk version greater than 20.3 will cause this error on MTK devices.
Solution: use Magisk 20.3 stable, it's the only fix till the devs come up with the fix.

[GUIDE] How to properly use the SP FLASH TOOL for MERLIN ? (Redmi Note 9 / Redmi 10X 4G)

Warnings:
- If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again !
- NEVER try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI and MAC.
- Keep your backup files safe and secure ! If you can, encrypt them.
- Never try to share your backups or your security and privacy will be compromised.
- USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
Downloads:
- SP Flash Tool (Windows): https://spflashtools.com/category/windows
- SP Flash Tool (Linux): https://spflashtools.com/category/linux
- Download-Agent (DA) file: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
- Scatter file: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
- (Optional) ReadBack file: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
Alternative Downloads:
If you are having problems for flashing on Windows with sp flash tool, give a try on these versions:
- SP Flash Tool v5.2020 https://spflashtools.com/windows/sp-flash-tool-v5-2020
- SP Flash Tool v5.1920 https://spflashtools.com/windows/sp-flash-tool-v5-1920
- SP Flash Tool v5.1916 https://spflashtools.com/windows/sp-flash-tool-v5-1916
1. Extract (or install) SP Flash Tool.
2. Extract Download-Agent (DA) file to the SP Flash Tool home folder.
3. Copy the Scatter file to the SP Flash Tool home folder.
4. If you've downloaded the ReadBack file and want to make backup of your device, copy the ReadBack file to the SP Flash Tool home folder. If not, skip this.
5. Run SP Flash Tool.
6. Select Download tab.
7. Click Choose button for finding the Download-Agent and select the Download-Agent (DA) file.
8. Click Choose button for finding the Scatter-loading and select the Scatter file.
9. Click Options in the menu bar. And then select Option.
10. In General tab, UNCHECK "LIB DA match" and UNCHECK "Storage Lite Cycle".
{
"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"
}
Done !
Now you are ready for to flash, to format or to readback whatever you want.
How to properly solve the errors of the SP FLASH TOOL ?
If you are facing any error or any problem using the SPFlashTool, try this guide: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/

whats the difference between sp flash tool and xiaomi flash tool?

dokja28 said:
whats the difference between sp flash tool and xiaomi flash tool?
Click to expand...
Click to collapse
MiFlash uses fastboot writing.
SP Flash Tool uses eMMC writing.

Oh so if i want to flash older miui version for example I'm on global 12.0.6 and i want to flash 12.0.3 global what would i use so that my bootloader cant be lock

dokja28 said:
Oh so if i want to flash older miui version for example I'm on global 12.0.6 and i want to flash 12.0.3 global what would i use so that my bootloader cant be lock
Click to expand...
Click to collapse
Try using sp flash tool.
But if you are on V12.0.5.0 or higher, you need to bypass authorization and flash in EDL mode: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/

dokja28 said:
whats the difference between sp flash tool and xiaomi flash tool?
Click to expand...
Click to collapse
Xiaomi flash tool is an official tool specifically only for Xiaomi devices, it can flash in fastboot mode and download mode both.
Sp flash is an unofficial tool which works for almost every device with Mediatek chipset, and it can flash only in download mode.

help this is what happening after i inserted the device

definitelynotgeddd said:
help this is what happening after i inserted the device
Click to expand...
Click to collapse
You are using wrong DA file.
See "Download-Agent (DA) file" in "Downloads".

@VD171
Probably an unusual question:
I hate android 10/11, they simply abuse of "security" bs and prevents us of doing what we want with our phones.
Is it possible to get rid of dynamic partitions and install some android 9 (Pie) from old days of freedom?

Jazzda said:
@VD171
Probably an unusual question:
I hate android 10/11, they simply abuse of "security" bs and prevents us of doing what we want with our phones.
Is it possible to get rid of dynamic partitions and install some android 9 (Pie) from old days of freedom?
Click to expand...
Click to collapse
Do you mean some rom like GSI ?
I have no ideia, my friend.
But, android 9, 10, 11 and 12 are totally compatible.
So, I think yes, you can.

VD171 said:
Do you mean some rom like GSI ?
I have no ideia, my friend.
But, android 9, 10, 11 and 12 are totally compatible.
So, I think yes, you can.
Click to expand...
Click to collapse
Yes, I mean GSI, but without the super partition, where every partition goes to root (boot, system, vendor, userdata, etc)

Jazzda said:
Yes, I mean GSI, but without the super partition, where every partition goes to root (boot, system, vendor, userdata, etc)
Click to expand...
Click to collapse
Just try and then tell us the result.

help me redmi note 9 hard brick 3 months. can't access fastboot, help me redmi note 9 hard brick 3 months. can't access fastboot, not edl, and can't enter recovery, my redmi note 9 restarted 2x. the last solution was to use sp flash and as a result there was a notification like ininot edl, and couldn't enter recovery, I restarted my redmi note 9 twice. the last solution is to use sp flash and as a result there is a notification like this

Ray Gaming said:
help me redmi note 9 hard brick 3 months. can't access fastboot, help me redmi note 9 hard brick 3 months. can't access fastboot, not edl, and can't enter recovery, my redmi note 9 restarted 2x. the last solution was to use sp flash and as a result there was a notification like ininot edl, and couldn't enter recovery, I restarted my redmi note 9 twice. the last solution is to use sp flash and as a result there is a notification like this
Click to expand...
Click to collapse
Try to flash other MIUI versions in firmware upgrade mode.
Good luck

VD171 said:
thank you for helping me, and my device has come back to life. so long. and I downloaded a lot of firmware and I'm using this firmware QJOMIXM_20200512.0000.00_10.0_global_53a4483cec.tgz. and the bootloader status becomes locked again. I didn't back it up. I'm looking for UBL instances let me know friends
Click to expand...
Click to collapse

Ray Gaming said:
thank you for helping me, and my device has come back to life. so long. and I downloaded a lot of firmware and I'm using this firmware QJOMIXM_20200512.0000.00_10.0_global_53a4483cec.tgz. and the bootloader status becomes locked again. I didn't back it up. I'm looking for UBL instances let me know friends
Click to expand...
Click to collapse
Good work, my friend.
I suggest you to unlock bootloader once you can and then, backup it following my guide:
[GUIDE][UNLOCK] How to restore the state of UNLOCKED BOOTLOADER in MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
It works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G - Probably some others Xiaomi devices How to backup: Step 1: Unlock your bootloader. Step 2: Backup partition: seccfg You can backup it using the SP FLASH TOOL, TWRP or copy it with...
forum.xda-developers.com

How can restore unlock boot status after backup seccfg?

MA7MOD_GSM said:
How can restore unlock boot status after backup seccfg?
Click to expand...
Click to collapse
Just follow the guide and select the seccfg partition to download only.

VD171 said:
Just follow the guide and select the seccfg partition to download only.
Click to expand...
Click to collapse
so I'm flashing the romglobal v11.0.9 then I flashed the md1img from rom_eng but waht I do is replace the one on the global rom nd the flash it because if I load the entire rom_eng it says that I have to flash erase all but I can't still use maui meta

So can i
VD171 said:
MiFlash uses fastboot writing.
SP Flash Tool uses eMMC writing.
Click to expand...
Click to collapse
So can I use miflash to flash my Merlin and will i need to pass any authorisationnif i want to downgrade from 12.5.5 to 11.0.2?

[GUIDE][MTK] How to bypass detection for UNLOCKED BOOTLOADER ?

WARNINGS:
First of all you should BACKUP IMEI.
Remember to NEVER touch the NVRAM.
People who does NOT backup imei or touches the NVRAM, are susceptible to the loss of IMEI.
If you try to share NVDATA between different devices, it may cause bootloop due verification of IMEI (slot1).
If you already lost IMEI, you probably may need to write IMEI again.
Works with:
Xiaomi Redmi Note 9 and ALL other MediaTek devices which uses SECCFG for unlocking/locking bootloader.
How does it work ?
After you turn on the device, the booting procedures checks if the device is unlocked and if there is any modified partition.
If your device is locked and any partition is modified, the device will not boot.
If your device is unlocked, the device will boot perfectly.
On booting, the device verifies if the device is unlocked or not, inside the partition: SECCFG.
After booting procedures, the partition SECCFG can NOT be read.
Due this, some variable settings are written to the partition NVDATA, because the system can read the partition NVDATA.
These variable settings contain details about locked/unlocked bootlader as many other details about the developer settings and some sensitive data like IMEI, Wifi MAC and Bluetooth MAC.
So, we just need to mix an unlocked SECCFG together a locked NVDATA.
How to do ? (Without formatting data)
1. Be sure to have UNLOCKED BOOTLOADER.
2. Backup the partition: SECCFG.
3. Format the partition: SECCFG. (Begin Address: 0x17800000 Format Length: 0x800000)
4. Format the partition NVDATA. (Begin Address: 0xc4a2000 Format Length: : 0x4000000)
5. Boot the device. It will write a new NVDATA.
6. Turn off the device.
7. Flash the partition SECCFG (with UNLOCKED BOOTLOADER).
Done !
{
"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"
}
How to do ? (Formatting data)
1. Be sure to have UNLOCKED BOOTLOADER.
2. Backup the partition: SECCFG.
3. Backup your files and data, if you want.
4. Now, RE-LOCK BOOTLOADER. Or just erase the partition: SECCFG.
5. Format user data. It will erase NVDATA too.
6. Boot the device once, you don't need to accept terms or enter in system. It will write a new NVDATA.
7. Turn off the device.
8. Flash the partition SECCFG (with UNLOCKED BOOTLOADER).
Done !
Useful links:
VD Infos: Capture device infos and details with an ULTRA root/magisk/riru/xposed DETECTOR
https://forum.xda-developers.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/
Scatter file for flashing using flash tool to MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
What should I backup before trying to customize my MERLIN device
https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
How to restore the state of UNLOCKED BOOTLOADER in MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
How to properly solve the errors of the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
Read Back file for backuping using flash tool from MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
DA files for flashing to MERLIN using FLASH TOOL
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
How to properly use the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/
Credits:​VD171​

Thank you for your contribution, I am a newbie in the subject of smartphones but I would like to know if with these modifications of your tutorial the momo application still detects the bootloader unlocked?
momo-v4.0.1.apk
drive.google.com

enzokart19 said:
Thank you for your contribution, I am a newbie in the subject of smartphones but I would like to know if with these modifications of your tutorial the momo application still detects the bootloader unlocked?
momo-v4.0.1.apk
drive.google.com
Click to expand...
Click to collapse
Since momo is closed source, you should not care for its results.
Momo uses many and many detections by native methods and they are hidden to anyone.
So, no one banking app can use momo detections.
But, the answer is: NO, momo can NOT detect unlocked bootloader using my method. And no other app or any other method can detect unlocked bootloader using my method.
Enjoy
Ps: Momo is already on version 4.3.1:
Magisk alpha
如果 「代码注入」 仍有假阳性情况，请入群反馈，感谢。
t.me

VD171 said:
Since momo is closed source, you should not care for its results.
Momo uses many and many detections by native methods and they are hidden to anyone.
So, no one banking app can use momo detections.
But, the answer is: NO, momo can NOT detect unlocked bootloader using my method. And no other app or any other method can detect unlocked bootloader using my method.
Enjoy
Ps: Momo is already on version 4.3.1:
Magisk alpha
如果 「代码注入」 仍有假阳性情况，请入群反馈，感谢。
t.me
Click to expand...
Click to collapse
Excellent thank you very much. Do you know if there is any way to do the same on snapdragon devices?

enzokart19 said:
Excellent thank you very much. Do you know if there is any way to do the same on snapdragon devices?
Click to expand...
Click to collapse
I have no ideia, I'm sorry.

All ok

Does safetynet hardware attestation work with this method??

0xf331dead said:
Does safetynet hardware attestation work with this method??
Click to expand...
Click to collapse
No

Flashing Magisk, enabling Zygisk and installing Universal SafetyNet Fix also hides unlocked bootloader.

hi i apolodize. is there a way to unlock the bootloader without using a mi account ?
because i use only my redmi with wifi and dont have a sim card to do it (and dont want to leave my infos on a chineese site)
ty

alcadon said:
hi i apolodize. is there a way to unlock the bootloader without using a mi account ?
because i use only my redmi with wifi and dont have a sim card to do it (and dont want to leave my infos on a chineese site)
ty
Click to expand...
Click to collapse
Try mtkclient:
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com

ty btw i forget to precise im under w7 64...

Windows 7 does not support python 3.9, but I think that 3.8 will also work. If not, you can use ReLiveDVD v4.

Deleted

hi do u think mediatek bootloader unlock works with python 3.8 ?
i put the 2 dll it asked but got an 0xc000007b error....

will try re live dvd ty

btw do u know what is this menu in chineese access by usb and vol+ ?

alcadon said:
hi do u think mediatek bootloader unlock works with python 3.8 ?
i put the 2 dll it asked but got an 0xc000007b error....
Click to expand...
Click to collapse
I do not know what did you mean. I only think that it should work, but not tested. It may work or not.
alcadon said:
will try re live dvd ty
Click to expand...
Click to collapse
It's the best solution.
alcadon said:
btw do u know what is this menu in chineese access by usb and vol+ ?
Click to expand...
Click to collapse
I don't know which menu you are describing, but on some Xiaomi devices there is a menu that allows you to reboot to bootloader, recovery, fastbootd etc and do some tests. I think it is part of MIUI Recovery. On some phones it is in Chinese by default (mostly those bought in China, but also some bought outside China), but you can change the language to English by pressing the 中文 button.

well i get my wife sim card so i did the normal way... must wait 168 hours... willNEVER buy one of thopse ****S again