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
Related
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Morphie said:
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Click to expand...
Click to collapse
Something like this happened to me a week ago. I have Nexus S 4G. So, I ordered USB Jig from usbjig.com and now I have download mode. It worked! :laugh:
You can buy USB Jig from that site, or build it yourself, or borrow it from someone.
So today, I tried to install TWRP onto a standard, 4.0.4 Samsung Stellar. Followed the instructions, went through Odin, and it failed with auth errors. Well, crap. Reboot the phone, get into there, and try to use GooManager to do it for me. I let it do the standard OpenBootloader or whatever, didn't work. So then I tried EZ-Unlocker. Unlocked just fine, until I turned off the phone. Try booting it, nothing happens; no vibration, no sound, no screen, nothing. I thought this was a dead battery (The battery was running at literally, 3% after I used EZ-Unlocker), so I plugged it in. No red light. Take out the battery, slap it back in. Same result, nothing happens to the phone. Well, crap. Try holding the power button again, nothing happens. Connect it to my computer and it reads it as some QUSB or whatever; look that up, download and installed a driver file for Qualcomm, and now Odin3Execution recognizes it, but Odin 3.07 doesn't. However, I still cannot use Odin to try flashing a new ROM onto it or anything because I cannot get into Odin mode. I was thinking of buying a USB jig to get it into Odin, but I want to confirm with someone else that this is a full hard-brick and not me being stupid.
tl;dr: Stellar doesn't boot at all; power button unresponsive, cannot get into recovery or download/odin mode; computer recognized it as QHSUSB_DLOAD, installed drivers to get it to be recognized as a Qualcomm HS-USB QDLoader 9008 at COM7. Very similar to http://forum.xda-developers.com/showthread.php?t=822939 but just a different phone.
edit: I found this: http://rootzwiki.com/topic/109153-howto-unbrick-a-bootloader-bricked-stellar/ but the download link times out. I'm willing to try this since it may solve the problem. Does anyone know where I can find a mirror of the download link?
edit2: I just sent a PM to invisiblek here on XDA.
edit3: And thanks to invisiblek, I managed to get it into download mode! Solved; if you want the stella-unbrick file, shoot me a PM and I'll upload it somewhere.
I an also looking for solution and need your help.
Sent from my SCH-R830 using XDA Free mobile app
Sch-i200 bricked download page required
hello
could you give the download link where I can find bricked soln. as such I bricked my stellar and I want to use it in India so I want to unlock it too.
Kindly help and hope to get back from you soon
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
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol
I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.
Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient
Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore
The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers
you should be able to repair preloader from bootrom mode (BROM)
How to enter bootrom mode. I am sorry if it is a noob question
Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html
Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved
you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.