Related
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
bump
same as u..but differ phone model.(N9589)
had a few upgrd...til the recent brick it.
Tried a few version of flash tool and still the same
Joshafc said:
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
Click to expand...
Click to collapse
Same problem here - tried to install stock firmware and got this error...
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thank you for your reply, but this doesn't help... ;(
Anyone?
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
vessk0 said:
Anyone?
Click to expand...
Click to collapse
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Schumi_wk said:
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Click to expand...
Click to collapse
I haven't heard about that. Maybe its a fake email. Did it say what the fault was?
Joshafc said:
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
Click to expand...
Click to collapse
How to format the nand with sp flash tool, I use the latest version?
And can you point me to good original stock ROM?
Thank you!
lolet said:
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
Click to expand...
Click to collapse
I tried reinstalling drivers, also tried other drivers, but this doesn't help...
I've had the same problem with the following installation Sp Tools
SP_Flash_Tool_exe_v3.1316.0.150
Rom: MP_mt89_v9_iocean_ousheng_jb2_20130520-184014_zhongyeqing_PC
http://d-h.st/ESX
Iocean X7 Youth
I don't have the same problem but i flashed the latest version of official rom for iOcean x7 Youth : 03 july 2013 : and wtf no more internal sdcard only the rom stockage. So i can't download anything, i can't use camera .
On the official website, I read that before flashing the 20 may 2013 rom one and the 03 July 2013 one, your baseband version have to be 23/04 or higher( you have to flash the 23/04 official rom first). This is only avalaible for the YOUTH version.
So tomorrow i will try what i said below to see if i have internal sd card again.
noob question::: since the iocean x7 young and turbo are the same phones...only different clock rates...will flashing the firmware for turbo on iocean x7 young work??assuming that the mtk6589T and mtk6589 are the same chipset only different clock rates??
Micromax A116 (Cant flash Rom)Brick Problem Solved
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thanks a lot. My Micromax a116 was brick. Now its alive.
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
DaniPhii said:
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
View attachment 2243401
Click to expand...
Click to collapse
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
SP flash tool shows in the statusbar which driver it is using.
mistraller said:
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
Click to expand...
Click to collapse
Yes, you got it
SP Flash Tool couldn't find my phone, but now it works
It's exactly a windoze driver problem.
Going to devicemanagement, in LAN-Devices I a had an Alcatel device,
chosing driver by hand and use the mtk usb driver, now Flashtool finds the phone
Thanks a lotttttttt....
shiv.kbh said:
Thanks a lot. My Micromax a116 was brick. Now its alive.
Click to expand...
Click to collapse
Thanks a lot man i unbricked my bolt a58 with this...thanks thanks...
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
buzz-27 said:
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
Click to expand...
Click to collapse
Finally the solution it was in the good files versions, I used this one :
- OS : WIN10
- Tools: SP Flash tool V5.1744
- Driver : MTK V1.0.8 and install DRIVER AUTO 1612
- FIRMWARE : ac70-20180912-1740-New
Hello buzz-27, it would be great, if you could tell me, where you can download the Firmware - same problem here Thank you!!!
buzz-27 said:
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
Click to expand...
Click to collapse
Hi,
I have recently bricked my AC70HELLO and tried uncessefully to flash stock firmware (from firmwarefile.com/archos-hello-7 ) but always got STATUS_DA_HASH_MISMATCH (with SP Flash Tools V5.1924 and V5.2020) or STATUS_BROM_CMD_SEND_DA_FAIL (with SP Flash Tools V5.1744) errors (with MTK_AllInOne_DA or DA_PL defaults DA).
Could you please share the Download Agent and the stock firmware from Archos ?
I have asked Archos for it in vain, they respond me "Sorry we don't have any FW available for this device. Thanks for your understanding," which got me a bit mad... I mean if my device's constructor doesn't have its stock firmware then who does ?
Here's the "latest" fimware from Archos http://update.archos.com/AFMv2/downloads/ac70hello_archos/20181101.075911/update.zip
Does anybody happen to have a reliable guides and reliable downloads to flash other firmwares to this Hello 7?
I tried several guides but somehow they are inconsistent, incomplete or simply not working. Some say I need TWRP without a link to a working image, others say I could use fastboot which generates "not allowed in locked state". I found out myself that I could work around that error by running "fastboot oem unlock" but after flashing, my Hello keeps hanging in a boot loop. (also after "fastboot oem lock")
Fortunately with @fraenK 's link, I could revert back to stock.
I have been using the Pixel Experience 10 GSI ROM from Expressluke so far. Other GSI ROMs should work as well. https://forum.xda-developers.com/t/gsi-expressluke-built-gsis.4003457/
fraenK said:
Here's the "latest" fimware from Archos http://update.archos.com/AFMv2/downloads/ac70hello_archos/20181101.075911/update.zip
Click to expand...
Click to collapse
Thanks but this is unusable without a working recovery wich I don't have since I'm bricked (corrupted logo.img so crash before booting in anything) would you know where I could find the download agent to use with sp flash tools ?
Archatos said:
Does anybody happen to have a reliable guides and reliable downloads to flash other firmwares to this Hello 7?
I tried several guides but somehow they are inconsistent, incomplete or simply not working. Some say I need TWRP without a link to a working image, others say I could use fastboot which generates "not allowed in locked state". I found out myself that I could work around that error by running "fastboot oem unlock" but after flashing, my Hello keeps hanging in a boot loop. (also after "fastboot oem lock")
Fortunately with @fraenK 's link, I could revert back to stock.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ -> how to install a GSI (with fastboot or TWRP)
https://forum.xda-developers.com/t/aosp-10-0-2019-12-06-quack-phh-treble.3992559/ -> AOSP with or without gapps and stock GSI rom (if I recall correctly before bricking, the Hello 7 needs an arm64 A-only image)
Hello,
If I can help you, I create a zip file with Driver, Firmware and the compatible SP_Flash for this firmware.
I flashed my Hello with success and I don't sure of all step, cause many test before sucess.
Just put WIN10 in "Test Mode" can help
http://dl.free.fr/getfile.pl?file=/Zn8HQVpO
press "Valider et télécharger le fichier"
Now I am in GSI Android and the Hello work perfectly !
I got same problem with Archos hello 10 version where can i find stock rom for this device? @fraenK @buzz-27 maybe you know?
urkelz said:
I got same problem with Archos hello 10 version where can i find stock rom for this device? @fraenK @buzz-27 maybe you know?
Click to expand...
Click to collapse
http://update.archos.com/AFMv2/downloads/ac101hello_archos/20181114.085412/update.zip
Thanks alot @fraenK downloading now. Anyone got a DA file I can use? Probably will get DA hash mismatch.
Hi everyone,
I bricked my Archos Hello 7 by trying to flash TWRP.
I'm looking to flash my device but it's hard to find informations for this device and nothing works for me.
I tried with SP Flash tool V5.1744 and few drivers versions without results.
I always have STATUS_DA_HASH_MISMATCH or BROM_CMD_SEND_DA_FAIL.
Every time I plug my device, the detected USB is the "Mediatek PreLoader USB VCom", do you think it's the good driver ?
@buzz-27 can you (or someone else) upload your file again, the link on Free is dead.
@Dawnowl444 did you solve your flashing problem ?
Thanks guys.
CameleonTH said:
Hi everyone,
I bricked my Archos Hello 7 by trying to flash TWRP.
I'm looking to flash my device but it's hard to find informations for this device and nothing works for me.
I tried with SP Flash tool V5.1744 and few drivers versions without results.
I always have STATUS_DA_HASH_MISMATCH or BROM_CMD_SEND_DA_FAIL.
Every time I plug my device, the detected USB is the "Mediatek PreLoader USB VCom", do you think it's the good driver ?
@buzz-27 can you (or someone else) upload your file again, the link on Free is dead.
@Dawnowl444 did you solve your flashing problem ?
Thanks guys.
Click to expand...
Click to collapse
Hi,
My AC70HELLO is still bricked unfortunately. I've got a corrupted logo.bin and no way to flash stock rom except with SP Flash Tool. But I can't get passed STATUS_DA_HASH_MISMATCH error.
I tried this utility without much success...
GitHub - MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
With --force I still get STATUS_DA_HASH_MISMATCH and the utility says "Device secure boot: False ; Device serial link authorization: False ; Device download agent authorization: False" wich is weird...
Let me know if you got any more luck with that than me.
If your AC70HELLO is'nt really bricked you can try to flash back stock recovery via fastboot.
Hi Dawnowl444,
Thanks for your tips, I gonna try with bypass_utility but without hope .
Maybe we need to do some hardware tweak to allow to flash the device.
There is here a French tutorial to disassemble the Hello 7. http://rnc.free.fr/hello7/hello7.html
In the firmware I found online, the file Checksum.ini refers to the version 1708 of SP Flash Tool, I tried with itn but without success, maybe it can be successful for you.
Unfortunately, I can't boot into recovery mode, that's why I try to flash with the Flash Tool.
If I succeeded to flash my device I will let you known.
buzz-27 said:
Hello,
If I can help you, I create a zip file with Driver, Firmware and the compatible SP_Flash for this firmware.
I flashed my Hello with success and I don't sure of all step, cause many test before sucess.
Just put WIN10 in "Test Mode" can help
http://dl.free.fr/getfile.pl?file=/Zn8HQVpO
press "Valider et télécharger le fichier"
Now I am in GSI Android and the Hello work perfectly !
Click to expand...
Click to collapse
Hello @buzz-27 , could you upload the file again?
I was try update my Hello 7 and now it restarting continuously.
Hello, is not possible immediately but I try to push the file in a few weeks or before maybe.
Ok thanks. By mistake I'm flashed the Hello 10 ROM in my Hello 7, and now it restarting continuously. I can enter in fastboot but I cannot flash the ROM - error: FAILED (Remote: not allowed in locket state) Do you know another way to flash the correct firmware? I can not enter in recovery mode.
Hello guys for Hello device
Link below with SP tool, Driver and Firmware for Hello 7 this pack work on my Hello 7.
Upload files for free - Restore_Archos_AC70Hello.zip - ufile.io
Download Restore_Archos_AC70Hello.zip for free from ufile.io instantly, no signup required and no popup ads
ufile.io
enjoy !
Thanks buzz-27, unfortunately, it didn't work for me.
Can you tell us which DA did you use ? I have tried all DA from the SP Flash tool with no results.
Maybe we have a different model/revision, mine has the FCC ID : SOVAC70HELLO
Hello, after a week waiting for unlocking the phone, i tried to install twrp unnoficial following a guide on the web... now the phone is totally bricked., it dosnt go into recovery mode only fastboot and after 10 seconds it restarts, i have adb installed properly on the pc, it detects my old poco f1 but the x3 gt isnt recognized and reboots after 10 seconds...
have anyone experienced this, or know of a possible solution? i really need help
ohh adding more info... maybe i messed up the boot partition, cause extracting the rom and looking at the flash_all.bat it says boot_ab and i did to boot... after this it entered the loop, it was recognizing the phone but i tried installing the room via miflash, gave error everytime i tried and now it isnt being recognized plus after 10 sec in fastboots it restarts... there is no charging battery creen just the loop
Just get a new device now
lol i dont want tooo... was thinking bout that
well... slowly, step by step using SP flash tool i am now able to see the poco logo and charging batery again... algo into fastboot i can get... gonna keep this updated in case anybody has this issue
btw.. there are 3 files i cannot flash, it gives error...
dpm_a.img
cust.img
rescue.img
rescue.img says mismatch, but i extradted the files from the downloaded poco rom, dows anybody know thy this happen?
well almost fixed... i managed to flash the room a while ago... now it can go into recovery mode, but says NV corrupted, any idea?
it can only boot into fastboot and recovery... i supose as it has something corrupted it wont boot into the system
Hello! (Read it fully)
I had the same problem, but i finally got it. First download the 12.5.7.0 rom from this page (Fastboot rom)
Xiaomi Poco X3 GT (chopin) Stock Firmware Collections
On this page, we will share all the latest Xiaomi Poco X3 GT (codenamed chopin) firmware flash files. To flash the firmware file, you need Xiaomi Mi Flash
www.getdroidtips.com
Then, go to Mi Flash Tool (also download from that page). The version you need is 20210226
Then unzip the rom as many times as it needs, and copy it (the most decompressed folder) to the desktop. Then, launch Mi Flash tool and install the drivers in drivers page. In the right corner you need to select "Clean all". And.... FLASH!
It solved my problem. I had the same as you. If your computer doesn't recognize your device, stay in fastboot 30 minutes and it will turn off automatically (with usb unplugged) or if it says no digest file found, turning off in 5 seconds turn it off.
I hope this can solve your problem.
Edit: Then update the firmware to 12.5.8.0 OTA way. Don't obey people saying stupidities like "Buy a new one". This is a forum, to help people, and if u don't know the solution, DON'T SAY ANYTHING
Bye
Ocelado said:
Hello! (Read it fully)
I had the same problem, but i finally got it. First download the 12.5.7.0 rom from this page (Fastboot rom)
Xiaomi Poco X3 GT (chopin) Stock Firmware Collections
On this page, we will share all the latest Xiaomi Poco X3 GT (codenamed chopin) firmware flash files. To flash the firmware file, you need Xiaomi Mi Flash
www.getdroidtips.com
Then, go to Mi Flash Tool (also download from that page). The version you need is 20210226
Then unzip the rom as many times as it needs, and copy it (the most decompressed folder) to the desktop. Then, launch Mi Flash tool and install the drivers in drivers page. In the right corner you need to select "Clean all". And.... FLASH!
It solved my problem. I had the same as you. If your computer doesn't recognize your device, stay in fastboot 30 minutes and it will turn off automatically (with usb unplugged) or if it says no digest file found, turning off in 5 seconds turn it off.
I hope this can solve your problem.
Edit: Then update the firmware to 12.5.8.0 OTA way. Don't obey people saying stupidities like "Buy a new one". This is a forum, to help people, and if u don't know the solution, DON'T SAY ANYTHING
Bye
Click to expand...
Click to collapse
eres español?
Ocelado said:
eres español?
Click to expand...
Click to collapse
Ocelado said:
yeah i speak spanish... well i will try, i flashed using sp flash tool, maybe its different using miflash?
Click to expand...
Click to collapse
i wanted to root my x3 gt but the unnoficial twrp around is what bricked my phone ahahaha
Hi bro! This is an unofficial twrp that works for me
POCO X3 GT TWRP
Download POCO X3 GT TWRP for free. None
sourceforge.net
Ocelado said:
Hi bro! This is an unofficial twrp that works for me
POCO X3 GT TWRP
Download POCO X3 GT TWRP for free. None
sourceforge.net
Click to expand...
Click to collapse
how did you installed, fastboot? what partition name did u use? i followed a guide that said recovery but x3 gt uses rescue i believe... this is wht bricked me
ohh btw i installed an enginering rom and now i was able to get into the phone... sadly on info, i have no mac address no imei... do someone know how to fix this?
Ocelado said:
Hi bro! This is an unofficial twrp that works for me
POCO X3 GT TWRP
Download POCO X3 GT TWRP for free. None
sourceforge.net
Click to expand...
Click to collapse
i flashed it to boot like the site says, but there is no recovery now... i can get into the system but no twrp recovery holding vol up and power
Rynhe said:
ohh btw i installed an enginering rom and now i was able to get into the phone... sadly on info, i have no mac address no imei... do someone know how to fix this?
Click to expand...
Click to collapse
you must turn on wifi to see mac address
Gaderg1992 said:
you must turn on wifi to see mac address
Click to expand...
Click to collapse
nope it wont let me.. i turn it on and does nothing...
I installed twrp on boot partition, and if you can't enter twrp reflash it.
Ocelado said:
I installed twrp on boot partition, and if you can't enter twrp reflash it.
Click to expand...
Click to collapse
man you are right.. idunno what hapened.. suddenly it jst booted in twrp
gl i hope i can help you. If you need more help just write here
Ocelado said:
gl i hope i can help you. If you need more help just write here
Click to expand...
Click to collapse
thanks... do you know of any custom rom for x3 gt? i cant use miui cause it says cant connect to google server at forst boot config
iv tried many gsi but none of these bots up after flashing to system
No... I don't know any rom...
2 things: have you installed the global rom? Try the global. Else, try skipping the logging in and then try it by entering gmail or in settings
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"
Did you try using Qualcomm's QPST software like described here: https://c.mi.com/thread-3527044-1-1.html
I literally unbricked two Mi A3 phones this morning that had been so screwed up one was boot looping and the other was so bad it wouldn't show the charging light or even boot, nothing would show on the screen at all. I followed this on both phones and I now have two working Mi A3 again.
Pyro556 said:
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"
Click to expand...
Click to collapse
Hello, im trying to convert it to CCe9 miui12, and I have the same message, even with different cables and PCs.
have you figure it out ?
STALKER18 said:
Hello, im trying to convert it to CCe9 miui12, and I have the same message, even with different cables and PCs.
have you figure it out ?
Click to expand...
Click to collapse
no mate i could not find any way out
dephekt said:
Did you try using Qualcomm's QPST software like described here: https://c.mi.com/thread-3527044-1-1.html
I literally unbricked two Mi A3 phones this morning that had been so screwed up one was boot looping and the other was so bad it wouldn't show the charging light or even boot, nothing would show on the screen at all. I followed this on both phones and I now have two working Mi A3 again.
Click to expand...
Click to collapse
I did try the qflash , it shows
download fail firehose fail fhloader fail process fail
Pyro556 said:
no mate i could not find any way out
Click to expand...
Click to collapse
Hi friend!
do you still having that Issue ? i might have the solution PM me
for those who still have only EDL mode as the last hope, I have a solution.
I have tried all the available solutions on XDA... QFIL.. MiFlashTool all mentioned vesions, Drivers, PCs, Cables etc...eventually I just disconnected the Screen cable (after battery's one) the one on the right side of the battery port. started the flash like mentioned with mi flash tool and the phone on EDL (vol + vol -, enter the cable). it runs smoothly took 177s to finish and the phone is back to A11 stock
Pyro556 said:
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"
Click to expand...
Click to collapse
@Pyro556 Thread closed as you've created a subject matter related thread in March 2022:
Mi A3 hard bricked
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even...
forum.xda-developers.com
And I've also closed this thread created by you yesterday respectively on Sunday:
[CLOSED] Mi A3 hard bricked
I guess the bootloader is locked , i am not sure , it was bricked due to the Android 11 update , i unbricked it twice using mi flash and update through system update but it got bricked again and this time it's showing the error "write time out...
forum.xda-developers.com
[CLOSED] Mi A3 not flashing , error "write time out device may be disconnected"
My mi A3 was bricked after the Android 11 update , i unbricked it twice using flash tool and test point method through edl then when the device was on , i updated it through system update , thinking that the update might remove the corrupted...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5, post only ONCE and post in existing threads instead of creating new ones! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
I was using dotOS on my redmi 5 plus (redmi note 5) when suddenly while playing game my froze and after trying to restart it it got stuck on boot screen (MI logo). And when I tried to open TWRP ( which was already intalled on my device) it also stuck on TWRP starting window. then I tried to flash TWRP again on my phone via mi flash tool but it showed on status error: writing 'sec' FAILED (remote : "flash write failure") . Please help it is my primary phone and I was unable to use it since last 2 days.
GirishHardia said:
I was using dotOS on my redmi 5 plus (redmi note 5) when suddenly while playing game my froze and after trying to restart it it got stuck on boot screen (MI logo). And when I tried to open TWRP ( which was already intalled on my device) it also stuck on TWRP starting window. then I tried to flash TWRP again on my phone via mi flash tool but it showed on status error: writing 'sec' FAILED (remote : "flash write failure") . Please help it is my primary phone and I was unable to use it since last 2 days.
Click to expand...
Click to collapse
@GirishHardia
Welcome to XDA. I hope you'll always find and get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to
Xiaomi Redmi Note 5 / 5 Plus Questions & Answers
Ask your questions about the Xiaomi Redmi Note 5 and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
I almost tried to flash 3 different roms on my redmi 5 plus but it always showed error:Writing 'sec' FAILED:remote"flash write faliure". Please help me to overcome this error
GirishHardia said:
I almost tried to flash 3 different roms on my redmi 5 plus but it always showed error:Writing 'sec' FAILED:remote"flash write faliure". Please help me to overcome this errorView attachment 5623507
Click to expand...
Click to collapse
Check here that everything is correct
GirishHardia said:
I almost tried to flash 3 different roms on my redmi 5 plus but it always showed error:Writing 'sec' FAILED:remote"flash write faliure". Please help me to overcome this errorView attachment 5623507
Click to expand...
Click to collapse
Make the path to the firmware shorter, like c:/vince
joke19 said:
Make the path to the firmware shorter, like c:/vince
Click to expand...
Click to collapse
We tried that, didn't work. I went to Mi service center nearby they told to change the motherboard and it costs 3,600/- What to do now
GirishHardia said:
We tried that, didn't work. I went to Mi service center nearby they told to change the motherboard and it costs 3,600/- What to do now
Click to expand...
Click to collapse
could you post the miflash log?
GirishHardia said:
I almost tried to flash 3 different roms on my redmi 5 plus but it always showed error:Writing 'sec' FAILED:remote"flash write faliure". Please help me to overcome this errorView attachment 5623507
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes then only MiFlash tool works. Now what do you want? Do you want stock rom or custom rom? Reply asap so that we can solve your problem don't pay 3600 unnecesarily. Your device is healthy.
Hello,
I have the exact same problem, OrangeFox Recovery is stuck at the logo, booting the device normally makes it stuck at MI logo too.
MiFlash shows the same error "flash_write_failure", but, cmd shows that the flashing was a success (or "done").
Any ideas?
UPDATE: here's the log:
Same error too, I think it's internal memory issue :'(
billouetaudrey said:
Same error too, I think it's internal memory issue :'(
Click to expand...
Click to collapse
did you guys managed something? My old mi a1 has the same problem. I think internal memory is dead
I have the same error for Redmi 7A. The brief description is below -
I was using Nusantra OS for Redmi 7A (I really don't know the version which I was using but the official website claimed it was latest). AOD was enabled and suddenly my screen froze and tried to reboot the phone abnormally, after that it stuck into a boot loop. When I tried to flash it from my pc it gave me this error, the error is attached with this reply/message. This phone is my primary phone, I am not able to use it since 5 days please help. As some @NOSS8 replied, that to check if everything is correct from here I verified it too, everything is correct and fine. But the error will show up each time I try to flash it from, the classic version (miflashtool) or the flash_all.bat version. I will attach the log and screenshot for the following. Please help!
Gibbron1 said:
I have the same error for Redmi 7A. The brief description is below -
I was using Nusantra OS for Redmi 7A (I really don't know the version which I was using but the official website claimed it was latest). AOD was enabled and suddenly my screen froze and tried to reboot the phone abnormally, after that it stuck into a boot loop. When I tried to flash it from my pc it gave me this error, the error is attached with this reply/message. This phone is my primary phone, I am not able to use it since 5 days please help. As some @NOSS8 replied, that to check if everything is correct from here I verified it too, everything is correct and fine. But the error will show up each time I try to flash it from, the classic version (miflashtool) or the flash_all.bat version. I will attach the log and screenshot for the following. Please help!
Click to expand...
Click to collapse
Post the full Miflash log
NOSS8 said:
Post the full Miflash log
Click to expand...
Click to collapse
I shut down my pc rn, will update this message tmrw at 12:00PM IST or b4 that, sorry for incovinience
The MiFlash log is attached with this message
dunzing_master said:
Is your bootloader unlocked? If yes then only MiFlash tool works. Now what do you want? Do you want stock rom or custom rom? Reply asap so that we can solve your problem don't pay 3600 unnecesarily. Your device is healthy.
Click to expand...
Click to collapse
I have the same problem in redmi 7a
Flash write failure and they told me
You need to change the motherboard
Gibbron1 said:
I have the same error for Redmi 7A. The brief description is below -
I was using Nusantra OS for Redmi 7A (I really don't know the version which I was using but the official website claimed it was latest). AOD was enabled and suddenly my screen froze and tried to reboot the phone abnormally, after that it stuck into a boot loop. When I tried to flash it from my pc it gave me this error, the error is attached with this reply/message. This phone is my primary phone, I am not able to use it since 5 days please help. As some @NOSS8 replied, that to check if everything is correct from here I verified it too, everything is correct and fine. But the error will show up each time I try to flash it from, the classic version (miflashtool) or the flash_all.bat version. I will attach the log and screenshot for the following. Please help!
Click to expand...
Click to collapse
I have the same problem on redmi 7a
And also they told me change the motherboard
Did you get another solution?
abdeneo said:
I have the same problem on redmi 7a
And also they told me change the motherboard
Did you get another solution?
Click to expand...
Click to collapse
Sorry pal you need to get another phone it's a hardware problem, if you need to get it fixed you must have patience
Gibbron1 said:
Sorry pal you need to get another phone it's a hardware problem, if you need to get it fixed you must have patience
Click to expand...
Click to collapse
Is there another way to fixed other than change the motherboard?!
abdeneo said:
Is there another way to fixed other than change the motherboard?!
Click to expand...
Click to collapse
Mine also same problem,i think after flashing the custom rom not made for Redmi 7A, perhaps the device Id has overwritten so that the stock rom could not recognize the original Id
@GirishHardia @Gibbron1
did you guys find any solution?