Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos
Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..
You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.
hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM
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