Hi, I accidentally bricked my phone flashing the wrong image.
Now i can't turn off the phone, cant access to recovery or fastboot. (device doesn't respond when i click any button).
'Poco' logo is in loop. Anyone knows a way to install a ROM? Any way to access fastboot in this situation?
Try pressing the buttons for a long time. It resulted for me to get to recovery mode, but no to download mode. Sometimes it works.
I bought a poco x4 gt like that too, hoping to get it fixed, I believe the way to get it is via EDL mode and miFlas, but for now miflash still doesn't recognize the image of the poco x4 gt. I hope that in some future update I will recognize it.
i have same problem
Same problem here
did anyone was able to find a fix? or at least locate the test points for EDL?
mtk devices use a different way to access edl mode. in my case I access the edl mode, the computer recognizes it, the software recognizes it, but when running it says that SPflash still does not work with the scartter version of the rom that I downloaded
how did you manage to boot into edl mode? i tried several hw key combinations but it gives me "preloader handshake failed" or several BROM error.
i think my scatterfile seems ok. its just the brom/edl connection.
when you turn it on with the volume button less pressed and it connects quickly to the pc install the MTK driver and then run the python where it will read the brom
Mine already fixed
butaw1 said:
Mine already fixed
Click to expand...
Click to collapse
what did you do?
if any one want to fix his poco x4 gt bootloop only. can't reach fastboot or recovery. at first you need auth to bypass dim 8100 security. i found a person on github name Rafon he fixed my phone and it's working perfectly right now. his username on telegram is @Rafon24
same issue
the only way of fixing is through an authorized xiaomi account sadly
i however found a way to turn it off when nothing works:
press all 3 buttons (volume up, down and power for like 20 seconds)
and then it will turn off
Related
I was on Crdroid and wanted to get back into Miui since there was weekly miui 12 version now. Downloaded it and flashed it but it would not boot. I remembered on poco i had that i needed to flash latest miui andro 9 before flashing latest miui andro 10 for some reason so i got back into twrp and did it. After reboot it went into some sort of boot loot and i lost any recovery and fastboot. Cant get into edl for that matter also. Anyone has any suggestion?
Can you elaborate a bit more, when you try to boot into fastboot with the button combination, does it work?
Do you get any indications when trying to turn on your phone?
malimukk said:
Can you elaborate a bit more, when you try to boot into fastboot with the button combination, does it work?
Do you get any indications when trying to turn on your phone?
Click to expand...
Click to collapse
Button combination gives me blank screen and revovery gives MI logo and just that until it rebots and stays like that in some loop. I can get into test mode after opening it to try QFill flashing but i forgot about account authorisation thing. I do not have any type of service center in my country that wants to deal with this. Issue is probably due to anti rollback policy in 2s. So i need solution to flash somehow thru qualcomm port but aparently only wth that account that has authorisation.
Thats where i got till now. Spent a whole day also at 4pda trying to find solution but nothing there worked for me
scudteshka said:
Button combination gives me blank screen and revovery gives MI logo and just that until it rebots and stays like that in some loop. I can get into test mode after opening it to try QFill flashing but i forgot about account authorisation thing. I do not have any type of service center in my country that wants to deal with this. Issue is probably due to anti rollback policy in 2s. So i need solution to flash somehow thru qualcomm port but aparently only wth that account that has authorisation.
Thats where i got till now. Spent a whole day also at 4pda trying to find solution but nothing there worked for me
Click to expand...
Click to collapse
Oh that's unfortunate! I think that in this case you will need to find someone with an authorized account that will flash it for you remotely. There have been some people around here offering that service for a small fee but it might be worth paying as that might be the only way to fix it.
Same thing happend to me, first time i tried using custom rom. i dont know what exactly happened. i think its have something common with anti-rollback feature. I sent the divice to OFFICIAL service center.... I told them "use mi flash tool and authorised account to flash fastboot rom in edl" These OFFICIAL trained technicians... ehm idiots... change whole mother board.... atleast they count it as warrasnty repair.... there is one guy on reddit who succesfull unbricked his device via "shady bussines" (there is also contact on reddit page)... some guys offer xiaomi unbrick services via teamviewer. you can give it a try: https://www.reddit.com/r/Xiaomi/comments/ftix9v/shady_services_unbrick_with_mi_authorised_account/ EDIT: its last reply reddit (hope its allowed to post links)
note: you can put yr device in edl mode by pressing powerbutton. im not sure if its pressing or holding. (yr phone need to by connected to pc, then mi flash detect the phone if all drivers are instaled, it should be shown in "windows device manager" as PORT named "qualcomm hs-usb qdloader 9008")
if you dont have authorised acc. this will happen https://imgur.com/a/oJVpKEl so you need someone with authorised account who will unbrick yr phone via teamviewer [Sorry for my bad english]
Ijust dont understand why xiaomi dont allow user flashing in edl mode... or just make harder to brick phone... i had oneplus and i never bricked it. bricking xiaomi is just super easy thank to their stupid anti-rollback and other b****its. i will never use custom rom on xiaomi again. i will dont buy xiaomi again
Did you try the MI Flash app? ...try to fastboot and check if mi flash works
Also try fastboot(combo-buttons only) and see if you can see the phone (cmd -> fastboot devices) ...if you see a device then you are good to go
If you have a fastboot miui rom you can use my guide: https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/weird-behavior-boot-loop-random-t4086703
It's like using MI flash program but doing it manually - if mi flash gives you issues or else
P.S. CMD MUST be with administrator rights of course!
Hi Guys,
got a big problem here today. after installing on orangefox a miui11 stable rom suddenly flashlight went on and it stopped to install it... i was like WTF? so i have go to reboot to the recovery and my mix 2s DIED.
now
1) battery is drained
2) no fastboot (black screen on vol down + power key)
3) no recovery (black screen on vol up + power key)
4) bootloop on miui logo
any idea?
Model:Huawei p40 lite
Hello, recently I flashed most propably bad firmware version and now the device seems to be soft bricked.
Black screen, no vibration while pressing power button, nothing.
However when I connect phone to PC, it does detect a device, I download HiSuite and device gets detected as Sooner ADB interface, but via HiSuite shows that recovery is not supported within the model.
ADB is also installed but devices show no devices at all.
When I press power button and volume down it seems to enter another state but device name/driver is the same. No fastboot.
It seems like it is not dead at all but I would have to use somekind of flash tool.
Any ideas would be appreciated
Thanks
Hi, is there a solution?
I need a solution to. Someone?
I am in the same situation. Is there someone to help?
After playing with some custom ROM, my device is stuck in EDL mode. i.e Stuck in primary bootloader. I cannot get to the secondary bootloader. either, recovery mode or fast boot mode.
Solution and issues faced.
Solution 1: Flash original Rom via Mi flash tool.
Issues: Xiaomi restricts the user to flash room when the device is in EDL mode. After some research found only authenticate accounts can install ROM in EDL mode via the mi flash tool. It will ask for EDL authentication. that I don't have access to.
I think the only solution is to somehow reverse back to fast boot or recovery mode and install back the rom.
Has anybody faced such issue and know the solution.
simonastani said:
After playing with some custom ROM, my device is stuck in EDL mode. i.e Stuck in primary bootloader. I cannot get to the secondary bootloader. either, recovery mode or fast boot mode.
Solution and issues faced.
Solution 1: Flash original Rom via Mi flash tool.
Issues: Xiaomi restricts the user to flash room when the device is in EDL mode. After some research found only authenticate accounts can install ROM in EDL mode via the mi flash tool. It will ask for EDL authentication. that I don't have access to.
I think the only solution is to somehow reverse back to fast boot or recovery mode and install back the rom.
Has anybody faced such issue and know the solution.
Click to expand...
Click to collapse
Your device can't be stuck in EDL mode timeless, to get it out of there, you just have to disconnect it from the PC and press the three buttons at the same time for about 10 seconds.
A different thing is that your device can't enter to fastboot nor recovery. Firstly get it out from EDL mode and see which modes are available after that.
SubwayChamp said:
Your device can't be stuck in EDL mode timeless, to get it out of there, you just have to disconnect it from the PC and press the three buttons at the same time for about 10 seconds.
A different thing is that your device can't enter to fastboot nor recovery. Firstly get it out from EDL mode and see which modes are available after that.
Click to expand...
Click to collapse
My secondary bootloader files are corrupted and can't get to it. Have only access to EDL mode. Can't get back to fast boot or recovery mode. The only option found is to somehow install flashable firmware via QFIL and get back to the secondary bootloader to access the flash tool of vendor-specific devices.
simonastani said:
My secondary bootloader files are corrupted and can't get to it. Have only access to EDL mode. Can't get back to fast boot or recovery mode. The only option found is to somehow install flashable firmware via QFIL and get back to the secondary bootloader to access the flash tool of vendor-specific devices.
Click to expand...
Click to collapse
Well, to be clear and not put effort where no results have to be expected; there’s no a secondary bootloader, this device have a fastboot mode (accessed usually pressing PWR + volume down buttons), a recovery mode (usually accessed pressing PWR + volume up), an EDL mode (usually accessed on an unlocked device pressing the two volume buttons at same time while connecting to PC or through test point method), and additionally a user space friendly fastbootd mode that only can be accessed using either ADB or fastboot command, also can be accessed through some custom recoveries in the PWR menu.
If you are totally sure you tried all the combination keys indicated WHILE your device is off, then you have to move it to the next:
- Search for a patched Firehose file either for your specific device or from a device with the same motherboard that can work too onto your device, this is to bypass the Mi account authorization or to work in qfil.
- Search for an engineer firmware for your device, if something exists have to bypass the Mi Flash tool restriction.
SubwayChamp said:
Well, to be clear and not put effort where no results have to be expected; there’s no a secondary bootloader, this device have a fastboot mode (accessed usually pressing PWR + volume down buttons), a recovery mode (usually accessed pressing PWR + volume up), an EDL mode (usually accessed on an unlocked device pressing the two volume buttons at same time while connecting to PC or through test point method), and additionally a user space friendly fastbootd mode that only can be accessed using either ADB or fastboot command, also can be accessed through some custom recoveries in the PWR menu.
If you are totally sure you tried all the combination keys indicated WHILE your device is off, then you have to move it to the next:
- Search for a patched Firehose file either for your specific device or from a device with the same motherboard that can work too onto your device, this is to bypass the Mi account authorization or to work in qfil.
- Search for an engineer firmware for your device, if something exists have to bypass the Mi Flash tool restriction.
Click to expand...
Click to collapse
My device is poco x3 pro. unable to find the patched firehose file..
simonastani said:
My device is poco x3 pro. unable to find the patched firehose file..
Click to expand...
Click to collapse
Man, you are not reading well, it's not so simple like that, I can't give you the exact solution in your hands but I giving you the direction that you have to take in order to find some solution and avoid taking it to a service center, not all countries have one at hand like mine.
- Search for a programmer firehose similar to your device if the exact for your model doesn't exist.
- Search for a programmer firehose for sm7150, it's the same as yours. Take a look here https://www.droidwin.com/patched-firehose-file/
- Search for an engineering/combination ROM for your device (it must be specific for your device, not for a similar one), this is one example https://testedrombd.com/poco-x3-pro-eng-fix-firmware/ some engineering ROM have the ability to bypass restrictions, not always, but it is worth to give it a try.
- And the last resort, exploiting/modifying/editing firehose vulnerabilities, read this https://github.com/bkerler/edl
SubwayChamp said:
Man, you are not reading well, it's not so simple like that, I can't give you the exact solution in your hands but I giving you the direction that you have to take in order to find some solution and avoid taking it to a service center, not all countries have one at hand like mine.
- Search for a programmer firehose similar to your device if the exact for your model doesn't exist.
- Search for a programmer firehose for sm7150, it's the same as yours. Take a look here https://www.droidwin.com/patched-firehose-file/
- Search for an engineering/combination ROM for your device (it must be specific for your device, not for a similar one), this is one example https://testedrombd.com/poco-x3-pro-eng-fix-firmware/ some engineering ROM have the ability to bypass restrictions, not always, but it is worth to give it a try.
- And the last resort, exploiting/modifying/editing firehose vulnerabilities, read this https://github.com/bkerler/edl
Click to expand...
Click to collapse
Yeah. Its not simple. Prior to giving link ,I have tried those methods. Thanks for the information
From my findings.
1. Patch programmer firehose file for sm7150 not found anywhere. Tried using different patch firehose file of other compatible devices that uses 860 chipset. Unsuccessful result.
2. Tried Engineering ROM of Vayu. Unable to bypass restrictions. It ask for edl authentication same as of vendor specific rom. I think the reason is xiaomi restrict user to flash room via edl mode. Still searching some way to bypass authentication.
3. Last resort. modifying firehose and hex files. Need a lot of research.
Didn't find any solution for poco x3 pro specific devices in community.
Can We install 860 chipset flashable frimware of oneplus via QFIL . Need to tried that one. Is it possible.?
simonastani said:
Yeah. Its not simple. Prior to giving link ,I have tried those methods. Thanks for the information
From my findings.
1. Patch programmer firehose file for sm7150 not found anywhere. Tried using different patch firehose file of other compatible devices that uses 860 chipset. Unsuccessful result.
2. Tried Engineering ROM of Vayu. Unable to bypass restrictions. It ask for edl authentication same as of vendor specific rom. I think the reason is xiaomi restrict user to flash room via edl mode. Still searching some way to bypass authentication.
3. Last resort. modifying firehose and hex files. Need a lot of research.
Didn't find any solution for poco x3 pro specific devices in community.
Can We install 860 chipset flashable frimware of oneplus via QFIL . Need to tried that one. Is it possible.?
Click to expand...
Click to collapse
QFIL is slightly outdated, so it needs a special programmer, even I don't know if it can work for new UFSs (or a limited range of them) it used to work for devices with eMMCs.
Xiaomi restricts users to flash in EDL mode using Mi Flash tool (the restriction can't apply beyond this tool).
A firmware from other device definitely will brick it.
Research if the PX3P has a counterpart device, I mean Xiaomi released every year a certain model for Global and the same model (with other name) as it happened i.e. with the Mi A3 and the MiCC9 and other models though, in this case it could be possible that the programmer file for this model could work for you.
Also, I saw on the OnePlus thread a tool capable to flash through EDL, maybe replacing the files it could work, I didn't try it yet.
E eu fui passar a .eu via Fastboot no meu e tava demorando dms... fui e fechai o CMD, e matei meu celular
After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?
From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.
So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.
BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version
Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com