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?
Related
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
Greetings, everyone. I'm unable to boot my Realme U1, after a recent unwise decision of relocking its bootloader after flashing a custom boot image i found over this thread: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683
I hadn't encountered locked bootloaders before, so I realised it isn't supposed to work with android pie, which resulted in a system crash.
Now i'm unable to get the device recognized by my pc at all,and it keeps saying that the current boot image is destroyed and cannot boot.
Also, only recovery mode is working.
Any suggestions on what i must do to fix this?
any kinda help would be greatly appreciated
and thanks
I also have exact problem no solution till now!!!
ps1084 said:
Greetings, everyone. I'm unable to boot my Realme U1, after a recent unwise decision of relocking its bootloader after flashing a custom boot image i found over this thread: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683
I hadn't encountered locked bootloaders before, so I realised it isn't supposed to work with android pie, which resulted in a system crash.
Now i'm unable to get the device recognized by my pc at all,and it keeps saying that the current boot image is destroyed and cannot boot.
Also, only recovery mode is working.
Any suggestions on what i must do to fix this?
any kinda help would be greatly appreciated
and thanks
Click to expand...
Click to collapse
This u read?
https://www.getdroidtips.com/stock-rom-realme-u1-firmware/
Please reply
I accidentally hard bricked my realme u1 while I am rooting it.
Any solution please reply.
ps1084 said:
Greetings, everyone. I'm unable to boot my Realme U1, after a recent unwise decision of relocking its bootloader after flashing a custom boot image i found over this thread: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683
I hadn't encountered locked bootloaders before, so I realised it isn't supposed to work with android pie, which resulted in a system crash.
Now i'm unable to get the device recognized by my pc at all,and it keeps saying that the current boot image is destroyed and cannot boot.
Also, only recovery mode is working.
Any suggestions on what i must do to fix this?
any kinda help would be greatly appreciated
and thanks
Click to expand...
Click to collapse
Hey man!
It's not a hardbrick, its soft brick.
If you can access recovery then flash a custom recovery, then flash the original boot.img and recovery.img, then reboot to COS recovery flash your ozip and reboot this should fix it!
Hope this helps!
Hi there I am new to this forum and I don't know that I am posting at right place . I have my Ralme U1 phone hard bricked and unable to turn on not Even it is detecting the charger. but when I connect it with my PC and hold power button for 7 to 9 second the device manager shows Realme Preloader as the device name and it stays there only for 2 seconds and then it again gone. Is anyone have the solution on how to unbrick it Please Help!!!!
DHANOLA said:
Hi there I am new to this forum and I don't know that I am posting at right place . I have my Ralme U1 phone hard bricked and unable to turn on not Even it is detecting the charger. but when I connect it with my PC and hold power button for 7 to 9 second the device manager shows Realme Preloader as the device name and it stays there only for 2 seconds and then it again gone. Is anyone have the solution on how to unbrick it Please Help!!!!
Click to expand...
Click to collapse
Hello Mate!
I hard Bricked Realme U1 over 2 times and recovered it!
MTK chipset devices are easy to unbrick.
I would love to help you, anyway to contact??
[email protected]#$ said:
Hello Mate!
I hard Bricked Realme U1 over 2 times and recovered it!
MTK chipset devices are easy to unbrick.
I would love to help you, anyway to contact??
Click to expand...
Click to collapse
You can contact me by mail: [email protected]
DHANOLA said:
You can contact me by mail: [email protected]
Click to expand...
Click to collapse
Hello Everyone!! It has been two years for me to be in this situation. I get mail from many of those who have a similar problem. So I am here, providing the solution to how I solved this solution.
For the solution, you may, first of all, join the given below Telegram. Link from anybody's phone and ask there for your problem or describe your problem in the group someone will help you out. The group icon has been attached.
Just connect to them on telegram and tell your issue they will surely help..
Telegram link
https://t.me/RealmeU1
Or search for Realme U1 group in telegram
Group icon attached
If then also you need help, please contact me by my mail. As mentioned in the above chat reply,
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
Hello guys,recently i tried to custom rom my mi 11 lite 5g(renoir)with pixel expirience i flashed the rom and hit reboot.I got a blank screen.Plugged it in and... QLOADER so i tried flashing it with mi flash tool,didint work,some error with hello packets.So i tried qfil And... SAHARA ERROR i literally tried reinstallig drivers reinstalling qfil,qpst even got and downloaded EVERY SINGE qfil verision and still nothing.Please i need urgent help!Here are some logs
You need a paid server to be able to flash the device
In addition, it should be Find My Device OFF
wdym paid server?
Ezzikmc said:
Hello guys,recently i tried to custom rom my mi 11 lite 5g(renoir)with pixel expirience i flashed the rom and hit reboot.I got a blank screen.Plugged it in and... QLOADER so i tried flashing it with mi flash tool,didint work,some error with hello packets.So i tried qfil And... SAHARA ERROR i literally tried reinstallig drivers reinstalling qfil,qpst even got and downloaded EVERY SINGE qfil verision and still nothing.Please i need urgent help!Here are some logs
Click to expand...
Click to collapse
Now i have another error:ERROR: It took 10.03100000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Ezzikmc said:
wdym paid server?
Click to expand...
Click to collapse
MasterLA said:
You need a paid server to be able to flash the device
In addition, it should be Find My Device OFF
Click to expand...
Click to collapse
Now i have another error:ERROR: It took 10.03100000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Quote Reply