Database Info

help| hard bricked my h830 after trying to flash another rom..

i rooted my phone and i wanted to switch rom for it,i flashed h850 rom rebooted device and it wont boot...i figured im on qualcomm 9008 mode in my computer so what can i do?
please please help me!!
thanks in advance..

Put it into download mode and restore the device via LGUP+TOT file, or if you made a backup, just reboot into recovery and restore your backup...

Dark Nightmare said:
Put it into download mode and restore the device via LGUP+TOT file, or if you made a backup, just reboot into recovery and restore your backup...
Click to expand...
Click to collapse
You probably didnt understand me well.. I cant put it in any mode...it wont turn on on any condition..

You said you rebooted twice, that tells me the device powers on, therefore, by doing a battery pull, holding the recovery or download mode button combos and powering up should get you into the desired mode. IF its not powering on at all:
1. Try charging the battery externally and try again.
2. See if the device is being recognized by a pc, if so there is hope that resting the device and trying again may work or we can see what mode it is in via adb/fastboot to get the device into a recoverable mode.
So....

Dark Nightmare said:
You said you rebooted twice, that tells me the device powers on, therefore, by doing a battery pull, holding the recovery or download mode button combos and powering up should get you into the desired mode. IF its not powering on at all:
1. Try charging the battery externally and try again.
2. See if the device is being recognized by a pc, if so there is hope that resting the device and trying again may work or we can see what mode it is in via adb/fastboot to get the device into a recoverable mode.
So....
Click to expand...
Click to collapse
The computer recognizes my device as qualcomm 9008

I have the same problem. My phone is dead only shows Qualcomm 9008.

Silly... If it's not for your phone why would you flash it??? Might have to wait for the official kdz from lg assuming you can some how get it into download mode. Or simply use your insurance for a new device. Expensive lesson learned

Maybe you can try the lg mobile support tool, since a tot file is available LG may have the stock kdz file available now, so try the recovery option for the mobile support tool.

Pretty sure that Qualcomm message thing is the true hard brick...
Sent from my pretty nifty brand new LG V10

This might sound stupid and it is usually for devices which have problems turning on or similar. I think is better to try anything that not trying all the options.
Why dont you try removing the battery, then close the module part without the battery. Press and hold the power button for at least 30 seconds. then release it. then put the batttery back on and try to make it boot into download mode. Chances are slim but the chance still there. This worked with my Samsung galaxy s5 after i flashed a rom that claimed to be for all models including the tmobile version when it clearly was for the g900f version . and i decided to try what i have done with other types of electronics and it worked.

Just tried on my phone. No go. Still dead. Trying lg repair. Hope I can get it fixed and not cost a arm and a leg.

Here is a guide to recover from 9008 mode
Here is a tool to extract kdz from tot
I've not read through these all the way, but if the PC sees it at all, it's not truly bricked... It might just be a pain in the ... to get it fixed. Those 2 links are good starting points for you. I hope you get this resolved.

I have the same error... My LG g5 H860 no turn on only connect in the PC on mode Qualcomm HS-USB QDLoader 9800.
Any idea or solution to resolve this?
Thx
BR

Dark Nightmare said:
Put it into download mode and restore the device via LGUP+TOT file, or if you made a backup, just reboot into recovery and restore your backup...
Click to expand...
Click to collapse
same issue just that my lgg5 tm is stuck on the firmware update for trying to root via lgup/tot file now not even lg bridge reads the phone it wants to then it says can not odetect nothin has worked

Sprint Samsung S8+ qualcomm mode

Hi my name is Miguel and im new to xda and i have a serious problem so i bought my phone and i was using it a mp3 and stuff since i live over seas i tried to region unlock it and in the process bam phone restarted and nothing but a black screen i plug in my phone to my charger nothing happens i plug it in to my pc something happens but not on the phone but on the pc it started downloading drivers i can tell you what the bubble said because i came to europe for vacation and im staying here for a while but a friend of mine said your phone lost his boot-up and it wont do anything unless you buy a medusabox and get all the files im buying the medusabox or whatever but where can i get the files from he told me you need 4 files with ones are they any ideas?

What were you doing to region unlock it?
If you hold down the bixby, power, and volume down buttons, can you get into download mode?

I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.

ragarcia87 said:
I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.
Click to expand...
Click to collapse
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+

The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
huawei asker/fixer said:
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+
Click to expand...
Click to collapse

Brittanyporter said:
The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
Click to expand...
Click to collapse
This is very old but no all bricks dont leave in edl the devices also have groind points. All of us that tested the edl repair use qfil or the recovery script which i use on mine. You need a bit more than just the bootloader for repair. A whole barrage of sperate partitions as well as the programmer xml

https://drive.google.com/file/d/1CFRc7RljFHX1oN4WdDLUR3b3BmaGnNAc/view?usp=drivesdk

Need help! No fastboot!

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?

Bricked Poco X3 NFC (Surya)

Hi, i think my phone is hard bricked or something, after updating to android 11 i lost root and the orangefox recovery wouldn't ask me for the decryption key, i tried flashing the custom recovery again but it didn't work, but somehow booting the recovery worked and tried to install magisk. Well after installing magisk, my phone got into bootloop. Everything ok as long as i could into recovery to format the phone if in any case something wrong happened, since i installed a custom recovery and a kernel, i decided to flash the stock rom, but then the MIflashtool said that it couldn't flash xbe file, for some reason i decided that i turning off the phone would be a great idea but it never powered on again. Also in my computer appears as Qualcomm HS-USB QDloader 9008, after several errors and mi unauthorized account i don't know what else to do. I investigated a little bit and i guess is into edl mode without using test points.
I hope someone can help me, thanks in advance
PS: I'm thinking on sending it to service center to fix it, but i'll lost my data. If i just could manage to boot into recovery i'd made a backup and later recover it.

i think you should send it to service center there is no other way the only way is flash the phone with edl

aymen peter said:
i think you should send it to service center there is no other way the only way is flash the phone with edl
Click to expand...
Click to collapse
That's what i going to do, don't want to mess with the phone more than i did. Thanks for the response.

Oneplus 8T HARD BRICKED ! HELP !!!

Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.

alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk

LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up

alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up

alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation

LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.

just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!🤭
forum.xda-developers.com

alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.

So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.

alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.

BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot

Thanks for sharing that - much appreciated.

alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate

LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.

alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!

alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!

NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps