Related
Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
This thread is for those who have troubles but have no idea what to try. If you're new in playing with Android Roms, you'd better read this. No exact operation would be introduced here, because only directions are provided and further work should be searched by yourself as I'm not Mr. Knowall.
Here, trouble means problems except the cases you can boot to system (they're issues) or hardware damage. Make sure your phone has been charged or any battery related problem is considered to hardware side.
Besides, if you are holding a T-Mobile H932, you should be extremely careful with anything below, because any mistake may push your phone into hell. Especially, there is currently no usable 9008 firehose file for it even you ask a professional repairman.
First, backup everything important regularly to a secure place instead of phone storage, especially private files and EFS partition which contains IMEI, MEID, etc. If possible, write down the IMEI, MEID, S/N, WiFi MAC address, Bluetooth MAC address of your phone for potential future need of restoration.
Then I assume you have unlocked bootloader. If not, go to (WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions) when you can still boot to system. If you cannot boot to system already with bootloader locked and cannot perform unlocking introduced there, maybe you can jump to the section of download mode or 9008 mode and give it a trial, BUT I CANNOT ensure your phone would return normal.
There are four important modes related to our topic: Recovery, Fastboot, Download and Qualcomm 9008 (Preload for MTK). Risky and inconvenience is increasing in order. Read this: Collection of mode entries with hardware key combination (maybe for most LG models) to learn how to enter them without booting to system.
Recovery is stored in the partition with the same name. You need custom builds like TWRP or OrangeFOX to flash in, or you only have a stock one with the single function of master reset. For most cases, if you can enter all the four modes, use this first. Make a backup before flashing anything with Rec, and if the thing you flashed in leads to bootloop or anything abnormal, you can easily get the original partitions back. But if you performed incorrect operations and such a restoration doesn't work, you should consider wipe cache, dalvik cache and data (backup if not yet). If not work still, try to flash in fresh rom packages. If not work again, go to the section of download mode.
Fastboot is mainly used to flash in some partitions like recovery, boot and unlock. There is some limitations that many partitions cannot be flashed in here. If you have never used this mode before, you may need to manually update the corresponding driver on your computer (caution that if you're facing the problem of "waiting for device", it's usually driver issue). Some firmwares miss this function, so it's often recommended to switch firmware for custom rec installing.
Download mode is mostly used to deal with kdz files. You need LG phone driver and dev patched LGUP (or some other tools with similar functions). If LGUP cannot recognize a phone already in download mode, it's usually the problem of driver or LGUP patcher. Be careful when using LGUP. If any interrupt during the process of downloading firmware, you need go to 9008 mode. Do not use chiperase unless you know what to do after that. Here again dump can backup partitions. Refurbish and partition dl are most widely used. This mode can solve most troubles unless you cannot enter here. If that really happens, move on to the ultimate mode, 9008.
9008 is the last chance before sending your phone to repair. Only recommend to recover other modes, but if you're familiar with it, you can do almost everything in this mode as in other modes. Again driver and tool are needed. Recommend QPST since it's made by Qualcomm, but it's not released publicly. Search and download from some reliable sources. The driver needed should be contained in the package with the tool. Somebody may tell to use QFIL, but if you have not installed it please install QPST and use the built-in QFIL instead of a standalone one, or problems would probably find you. To use this mode, you need the corresponding firehose file. See this: LG V30 Unbrick guide (Qualcomm EDL 9008 Mode, Hardbirck, with no download mode) for file download (none for H932 yet). You do not need XML file if the partition table is not broken. To verify it, open QFIL built in QPST, set configuration to UFS mode, open Tools -> Partition Manage and see if it's correctly displayed. If yes, only flash in partitions related to bootloader and recovery to get other modes back. The partitions can be found in twrp flashable stock firmware or early backups, or you can extract from kdz using LG firmware extractor. Only the worst damage to storage needs full download with XML generated from kdz using extracting tools.
If all modes above cannot save your phone, you may consider hardware damage and that needs professional knowledge, so our forum cannot help.
Good luck.
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
djzero86 said:
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
Click to expand...
Click to collapse
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
avdo06 said:
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
Click to expand...
Click to collapse
Nope, if you flash a rom that contain those partitions it will be over writed.
Read carefully the instructions, the dev remark this point clearly in the mega post
In the past, I would edit the updater script to remove whichever partition updates I didn't want, such as boot.
Does that work with MIUI 11? I guess I could try it out, only flash the system partition and see what happens. Anyone else try?
OP, did you flash both preloader, lk and lk2 before rebooting?
Try this:
I was in a similar situation. I unbricked my phone by downloading the SP flash tools with the DA file specifically for the MT6785 (The note 8 pro's chip). here's the link to download it: https[colon]//easyfirmwares[dot]com/index.php?a=downloads&b=file&id=603
Just extract and follow the directions to unbrick your device on the megathread. Hopefully this helps.
* Also, this won't work if you don't have the preloader and lk images flashed, as said in the megthread. *
edit: Replace [colon] with " : " and [dot] with " . "
I pulled my phone back from the dead. I read in a thread somewhere that this guy had the same situation as me. He downloaded miflash pro (black icon). So I did the same. There is a tab inside miflash for sp flash tool. When I connected my phone it immediately started flashing. The phone rebooted with the firmware I chose ( which is 11.0.3.0 PGGEUXM). Since this thread is from last year (when I have more time I'll post the link here), I think that it MIGHT work for bricked RN8P's that don't have the preloader/lk files flashed. But it's just a thought. Anyway, like I said, my phone was dead, wasn't reacting to anything, I had no fastboot and SP Flash Tool that I had downloaded from the official website kept giving me errors each time I connected with USB. It could be that particular versions of SP Flash had some misunderstandings with my PCs (tried two PCs and three versions of the SP tool). I was so desperate and I had already ordered a Redmi Note 8T from Amazon. But then I read this post and it worked! :silly: :laugh:
i need an auth. mi account to flash my firmware back. can anyone help me please?
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
I can access my fastboot but how do i flash stock rom ? Prior to this i was able to flash global version but got brick when i install twrp
If i flash a different rom it just says anti rollback
By the way my unit is china variant any response will be apperciated
I have eea 11.0.2.0 android 10 and the twrp is diferent than android 9...
Test with this version of twrp..... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
Brother i hace muy phone bricked now i downloaded mi pro Italian versión, i havent fastboot only blackscreen pc cant read phone only on edl, i disconnected battery and still not getting fastboot, so mmy question is where to find that miui android 10 tgz ROM ? For install and try ? I got same error Brome and auth permission , i payed 25$ and i got scamed, i cant find that android 10 ROM that you mentioned
I do as you say but it's not work
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
poster74 said:
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
Click to expand...
Click to collapse
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
avdo06 said:
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Click to expand...
Click to collapse
poster74 said:
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
Click to expand...
Click to collapse
Looks like it's not hardbricked anymore, that's great. You should check out other threads on the RN8 Pro about what to do next.
It works flawlessly AND i had preventive loader (Android 9, Global 11.0.6)
However, note following points;
1. if you get your battery drained it wont charge in preloader mode. so you have to flash the original preloader/lk files as well else, you can uncheck preloader, lk1 and lk2.
2. For future, DONT EVER LET YOUR PHONE BATTERY EVER DRAIN TO ZERO, else possibly you might have to flash whole rom again. (you can try simply restoring preloader)
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
dont work!for me
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
i do this step and when press volume + and connect my mi account authotised but after it take error such
STATUS_BROM_CMD_STARTCM_FAIL(0XC0060001) ...
...in devices manager in laptop(windows 10) when press and connect phone show mediatek usb port... but flash do not start!!!
tanx for you giud and response
hello
zumboy said:
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
Click to expand...
Click to collapse
do you resolve that problem?? i got the same (same wrong twrp install) & i think our only chance to resolve this is with authorised account
If you accidentally formatted your device , then how to restore imei
How to deal with: Download not complete error
Sn writer
Elaborate more with Download part
Download Not Complete: something blah blah blah after 10s, 0*92655 something something...
Sn writer / Maui Meta doesn't work for null imei for realme3.
Thanx
The device on which I am flashing the firmware is REALME 3, I used SP Flash tool for flashing, while flashing with SP Flash flash tool, the tool show EMMC unknown,but the flashing completes successfully,
then after pressing power ON, this message appears at the bottom ,
Download Not Complete! Please press Volume+ and power key for 10s to power off. Then download again. Otherwise will block here 60s until shutdown automatically. error code : 0*9925669( I can't see the last digit bcoz of the glass cover).
PLS GUIDE.THNX
Give possible solution for imei
@yas8say , has provided possible solution, I will try that next time I'll get this error. In thread brick repair by @ATDteam .
If you can use SP flash tools, SN writer DOES work on your fone, but it's figuring out a certain timing and sequence of events. that prove my point. Your at the point you need to be, it's waiting on you doing what I'm trying to say... your too demanding wanting the quick fix...
Everytime you post pauses me in case I need to change what I write to you, so slow down, your distracting me lol
Sn Writer is actually a pain to use, and there are many versions. But I learnt a sneaky fast path with it's appearing to not work. It does work, but kind of in reverse of what you think it does.
Sn Writer, strange but true, calls 'serial' as in serial number, 'barcode' in some versions, so some think because they cant see 'serial' that it wont work. I know because at first, I did. Took me a while to learn this.
Load up Sn Writer, it'll ask to load a file, the window that opens should be where you see MTK DA ALL IN bin, select it. Then choose scatterfile from stock firmware.
Now set correct attestation keys found in stock rom, your aftersales stock, with your attestation keys /google keys blah blah...
You then have to choose what you want to flash. If you see serial, that is NOT what you want to flash, you have to flash BARCODE! (your fones serial number) I know you said IMEI, but in order, SN writer flashes BARCODE before IMEI 1, so you MUST flash serial and mac PACKAGE given in stock rom?
So what I do is open the window to type in BARCODE box, my serial number.
Imei 1 is obvious, but you MUST do imei 2 as well, or it will add a few digits to imei 1's mac, put it in imei 2 that may not corespond to your attestation key.
Over to fone.
I turn my fone OFF, hit start in SNWriter, and plug phone into pc, and wait. You can tie your hands to your chair for a min, because if you interupt this TIMING...
Just when you think it wont work, folks give up. Wait that wee bit longer... it will show pass or fail. If its all genuine stock, it cant fail, only impatience caused by not knowing this sequence, and SN's bug-inesss
I'm too tired right now, and I see you posting again lol, my eyes are dry and its sleep time, and since you think it wont work, I'll catch up later today on this post, beacuse I'm gettin ratty with myself lol
Patience.. I'll be back...
Ank Sak said:
@yas8say , has provided possible solution, I will try that next time I'll get this error. In thread brick repair by @ATDteam[/USE
[/QUOTE]
Click to expand...
Click to collapse
HI
If you have successful in booting up your device try rooting it with magisk and find the .bin file in /data/nvram and edit it !
yas8say said:
HI
If you have successful in booting up your device try rooting it with magisk and find the .bin file in /data/nvram and edit it !
Click to expand...
Click to collapse
Ank Sak said:
Give possible solution for imei
Click to expand...
Click to collapse
I have faced this too, but luckily i had already taken a backup from recovery of nvram ,nvcfg, nvdata partitions .After flashing the recovery i just restored the partitions.
SO, GUYS IF YOU CAN BOOT INTO RECOVERY FIRST THING YOU HAVE TO DO BEFORE FLASHING ANY PARTITION IS TO MAKE A BACKUP OF THEM
yas8say said:
HI
If you have successful in booting up your device try rooting it with magisk and find the .bin file in /data/nvram and edit it !
Click to expand...
Click to collapse
The unique problem I am facing is that I was able to flash the firmware, but I couldn't do anything after that because I did format which resulted in """ null imei """ without it the in-depth test app doesn't work, so the after process of bootloader unlocking and then rooting is unachievable, I can't downgrade with official ozip file given in realme website, I did that and it resulted in hard brick( basically without unlocking bootloader I can't do sh*t) , my device is up & running but without imei the further processes are stalled, I will try the method of using sn writer mentioned here..the repair guy even mentioned something about bin fine not found so he couldn't write imei, I have successfully used Maui Meta & SN Writer to write imei of my other mediatek chip containing device , but it didn't worked on realme3, yes you may have solved my problem of "" Download not Complete"" I have posted two pictures in the brick repair thread by @ATDteam . Thanx.
I will try to repair imei and post the outcome here.
2 years ago I formatted by other mediatek chip device lenevo and it did show NVRam error in wifi, after repairing imei it didn't show , & now this mediatek chip device realme does show NVRam error in wifi :: -- NVRAM WARNING: Err =0*10
Ank Sak said:
The unique problem I am facing is that I was able to flash the firmware, but I couldn't do anything after that because I did format which resulted in """ null imei """ without it the in-depth test app doesn't work, so the after process of bootloader unlocking and then rooting is unachievable, I can't downgrade with official ozip file given in realme website, I did that and it resulted in hard brick( basically without unlocking bootloader I can't do sh*t) , my device is up & running but without imei the further processes are stalled, I will try the method of using sn writer mentioned here..the repair guy even mentioned something about bin fine not found so he couldn't write imei, I have successfully used Maui Meta & SN Writer to write imei of my other mediatek chip containing device , but it didn't worked on realme3, yes you may have solved my problem of "" Download not Complete"" I have posted two pictures in the brick repair thread by @ATDteam . Thanx.
I will try to repair imei and post the outcome here.
Click to expand...
Click to collapse
If you want to unlock bootloader just use mtkclient ,its very simple.
And if you want my imei files i can provide you but you got to have twrp installed.BTW where are you from?
Tried mtkclient & mtksu app , didn't work, first I will write imei, then use in-depth test, then unlock bootloader, then downgrade, then root using mtksu.. fingers crossed
Ank Sak said:
Tried mtkclient & mtksu app , didn't work, first I will write imei, then use in-depth test, then unlock bootloader, then downgrade, then root using mtksu.. fingers crossed
Click to expand...
Click to collapse
What error did you faced when using mtkclient?
yas8say said:
What error did you faced when using mtkclient?
Click to expand...
Click to collapse
I cannot boot in fastboot mode ( I forgot to tell , in realme )
Mtk client:: shows this...
Daxflash - uploading stage 1 from mtkallinone_ da_5.2136.bin
Preloader
Preloader- [lib] : ?[ 31mError on DA_send cmd?[0m
Daxflash
Daxflash- [lib] : ?[31mError on sending DA.?[0m
Main
Main - [lib] : ?[31mError uploading da?[0m
Device formats,
First time some error
Now I ran second time python mtk xflash seccfg unlock
And now bootloader is unlocked !!! Cheers
I don't want to brick and I want to root , what must I do , pls give in steps.. Thnx
Should I directly install twrp img then magisk zip??
Orange state
Device is unlocked blah blah blah( same as lenevo)
But no fastboot mode
When use adb reboot bootloader
This comes up
The serial is not match
Fastboot_unlock_verify fail
Should I try using in-depth test app??
Ank Sak said:
Should I directly install twrp img then magisk zip??
Orange state
Device is unlocked blah blah blah( same as lenevo)
But no fastboot mode
When use adb reboot bootloader
This comes up
The serial is not match
Fastboot_unlock_verify fail
Should I try using in-depth test app??
Click to expand...
Click to collapse
TRY this:
python mtk w recovery recovery_name.img
then boot into recovery.
yas8say said:
TRY this:
python mtk w recovery recovery_name.img
then boot into recovery.
Click to expand...
Click to collapse
My device is realme3, it's on Android10 c.17, will I will be able to root with magisk ? Ok I will try.
No straight business,
Ok i tried, gave same error preloader dax main. .., so I switched off , as soon as the device turns off n pressed all three buttons to go into brom mode, the other cmd with python command ran and wrote twrp Spartan recovery,, then switched on, key combo didn't work, bcoz it was showing ' the serial is not match......' so I typed adb reboot recovery, it booted to realme UI recovery.
Surely have to downgrade to Android 9 to root & install recovery
Hi everyone, days ago I posted on the forum that I had a bootloop, I could not enter fastboot or recovery, well, I managed to install the rom by sp flash tool without errors, but now I get the error "nv data is corrupted" as seen in the video that I attach, anyone know of a viable solution? What is free and do not have any other problem and my phone back to normal? Because I can enter fastboot and maybe download or twrp or download pixel experience or a rom, What do you recommend?
Your browser is not able to display this video.
I have the same problème did u solve it ?
with me we are in 3, please share if you find something !
you reached a solution so wished and few seconds later you get into nightmare back again !
Same here, but on redmi 9. I guess i made a mistake thaough, i tried to install EU rom and then this happened. Did you make this mistake too?
after otg update of miui 13 it happens. maybe @VD171 help us ?
same here
after updates got a boot loop with no access to recovery or fastboot,
after successful flashing, i got NV corruption.
every year a redmi phone with updates problem
redmi phones are a mess with updates
coliotte said:
same here
after updates got a boot loop with no access to recovery or fastboot,
after successful flashing, i got NV corruption.
every year a redmi phone with updates problem
redmi phones are a mess with updates
Click to expand...
Click to collapse
Me too
We need to send a message to Xiaomi support and let them know about this issue so that they can provide a solution for this problem in the future. They are the producer of this phone and can provide a remote tool for nvram repair
Redmi note 9 merlin will receive the MIUI 14 update and still supported by Xiaomi
Found a good solution I sold it to a repair shop for parts and got an iPhone already updated that iPhone and guess what IMEI is still there .
Recovered by simple way first install Engineering rom after that downgrade to 12.5
devjmi said:
Recuperado de manera simple primero instalar la ROM de ingeniería después de esa degradación a 12.5
Click to expand...
Click to collapse
Have you tried this method?
I already put it to the test to see if it revived my redmi note 9 but apparently it continues the same without any result, what's more, it is not capable of flashing the engineering ROM either.
coliotte said:
same here
after updates got a boot loop with no access to recovery or fastboot,
after successful flashing, i got NV corruption.
every year a redmi phone with updates problem
redmi phones are a mess with updates
Click to expand...
Click to collapse
Yes I did, you can try searching how to flash engineering rom on dead phone on youtube
Good news people, I found how to revive our bricks with nv data corrupted, it is a simple solution, but that is if our device is going to be left without IMEI, or baseband, but it will turn on and work again, staying with MIUI 11 as a system, in the next comment I will leave the step by step and from now on I will continue investigating how to restore the IMEI and the base band of the equipment.
Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)
mrdeivid said:
Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)
Click to expand...
Click to collapse
Helo, what's the pass for the file? Thank's
Password plz
mrdeivid said:
Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)
Click to expand...
Click to collapse
Pass- HALAB_HT_TECH
I have 3 Solutions for this problem :
1) - After flash firmware to latest MIUI with official file, use Unlocktool [https://unlocktool.net/] to flash the firmware and restore nvram data (if already backup the NVRAM config)
VIDEO :
- IF NOT use Pandora tool [https://z3x-team.com/products/pandora/] (for repair imei (if didn't have nvram data *but need to search for new IMEI)
VIDEO :
- THIS IS FREE VERSION FOR REPAIR IMEI
VIDEO :
2) (if still bootloop or stuck) Remove plate
video :
OR
3) This is the last options, need to disassemble the device, and replace the capacitor next to CPU
VIDEO :
i hope that help
HackerSecMY said:
i hope that help
Click to expand...
Click to collapse
thanks man, but I have a question, the unlock tool is paid. Second, if I do and fix that, can I go back to MIUI 13?
mrdeivid said:
Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)
Click to expand...
Click to collapse
Thank you so much! I've spent months trying to find a solution and this one was the only one that worked
I've still got the IMEI issue, but at least it works now.