Related
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
Please try to enter the bootloader mode in a bright room as it is very difficult to see in poorly lit environment. Till you enter the bootloader mode your device will not be recognised. Perhaps one of the three keys is getting released..the light button is the usual culprit. Once you are in the bootloader you can reflash.
Thank d_ranade for your answer.
I am sure the screen is 'all black' and I've tried to press the buttons several times.
I think the main problem now is how to enter the Bootloader.
I sometimes find it takes several goes to get into Bootloader mode. If not, have you tried a hard reset?
I've tried whatever i can do. Hard reset is useless too.
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
I have sent you a pm, it should help you.
-Jwrightmcps
Thank Jwrightmcps for your help, but i can not enter the Bootloader ,so can not use mtty to do more.
Unable to start/see bootloader
I seem to have the same problem with my upgraded universal which was working fine for about ten days. Then I installed TomTom on it and again it was all working that evening.
Then, when I turned it on the screen went blank (white), so I re-flashed it, but, part way through the screen went black, so I left it connected for further hour and nothing. I have since been unable to get it to do anything, it is not recognised by activesynch, it will not charge (either from the mains or the USB on either of the batteries) nor will it turn on or respond in any way.
I have unset ‘allow usb connections’. I have tried solidly for +/-10 minutes doing the backlight + on/off button and reset bit - repeatedly, with my wife helping to ensure all buttons were being pressed. All I got was a message from MicroSoft telling me that ‘One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it’. The only positive thing is that every time I do it and depress the reset, the red LED flashes (provided I leave the USB cable in) but at no point have either of us been able to see any writing on the screen.
Any guidance (apart from where to take it for recycling) would be welcome…
It happened to me several times too. Even in the old ROMS. But had learned many things out of it. I removed the battery. Wait for several seconds or maybe minute before placing it back. And after placing it back wait again for some time before doing the "power + light + reset" (bootloader). At some point when I am in the bootloader mode already and reflashing, connected to the PC already, the screen went blank again. So I'm sure that something went wrong again. I repeated the procedure again (removing battery, placing it back etc...) and the reflashing continued. It takes patience (maybe).
After having experienced this so many times, I'm beginning to assume that it is not because the battery is "bad" or there is a problem on the ROM being reflashed. It is on how it (the battery) is connected to the unit. The reason why it does not turn on, charge even if connected to the charger, does not hard reset, does not react to anything... I just don't know.
One thing more, the procedure I said above sometimes does not work at once. But at least I managed to "resurrect" my device several times.
This I am sure, it is not in the ROM that is being flashed or the update...
Hope this helps,
Lelen
lelen, Thanks for your assistance. I tried last night, but it still could not enter the bootloader mode...
I have the same problem =( and i don't know what to do, someone told me that i have to change motherbord to resolve this problem, i hope there are some other solutions.
Dead Uni
I too had this problem. With the device not responding at all and not able to enter bootloader stops mtty from working.
Only way i could get it to work was to take it to an O2 shop to send it away for repair (luckily the O2 XDA range has a 2 year warranty and because its completely dead they cant tell the OS has been modified).
Unfortunatly like the previous post i think it can only be fixed by replacing the mainboard.
Hi all, i found this thread http://forum.xda-developers.com/showthread.php?t=291097&page=6
so many people have the same problem , and nobody found a solution? i can't believe that on all this universals died motherboard, and there is no way to fix it with some special cable or some programm.
yes,i post the last reply of the thread you mentioned above, but nobody can resolve it.
I recommend you remove the battery and leave it over night. Put the battery back on, ensure it is properly mouted and try booting it.
It worked for some, no idea why though. I'm actually suspecting a bad battery mounting, which results in the motherboard unable to detect a battery is iserted, thus refusing to boot.
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
coolbeans252 said:
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
Click to expand...
Click to collapse
i guess thats what i will have to end up doing
anyone goten repairs done in north america?
( i live in western canada)
got the same problem
sofene said:
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
Click to expand...
Click to collapse
hi..please let me know if your device is fixed and how you managed to fix it. my email id is [email protected]
http://forum.xda-developers.com/show...6&postcount=52
So, unluckily today i find myself here lookin' for help with my phone. I had already took a look on other brick threads, but i can't find an appropriate answer to my problem.
I'm (i was) running lineage-14.1-20170602-nightly, i had ne0zone75's TWRP 3.1.0.0-0, and that's how the brick came in a strange way; i was simply on XDA Labs app browsing the forum, when i received a call. I've answered, and when i shut off the call the phone shut off immediately after. I thought it was a reboot, but keeping pressed the power button didn't switched on the phone anymore. So i've tried to remove the battery and re insert it after some minutes, but the only thing i can get is the screen with the samsung logo that goes all black after 5 seconds. I already had other bricks due some errors of mine in the past, but this time it's really difficult.
1: I can't access recovery mode. Ow, how i wish i could.
2: I can access download mode, but after that i reach the ODIN MODE screen with the details of product binary, KNOX, ecc. the phone shuts off again.
3: If i keep the power button pressed, the phone doesn't starts. It only starts if i replug the battery in, but after some seconds it shuts off again.
4: How could a call as another mess up the whole phone?
5: I didn't installed nothing new from at least a week... yesterday an automatic update of the Play Store took place, but except that nothing has been changed. Nothing of nothing! No settings, no apps...
What could i do? Installing Kies with Samsung drivers could help me flashing a stock rom for example? Because at the moment, there isn't too much that i can do with the phone in this state... I hope this little jewel won't have to become a stone to be thrown away. Any help would be great, and really appreciated. Thanks in advance...
Things has got worse. Now my device doesn't starts at all; no vibrations, no signs of life, nothing. I've tried even to put it for 6 hours in my refrigerator, because i've read that the cold temperature could be helpful to fix some broken contacts on some component, but i'm losing hope 'bout it. I supposed that at this point is something hardware-based and not software, because it's just impossible that a call like an other one could be the cause of this hard brick... The only thing is that if connected to my PC, it is being showed as QHSUSB_LOAD. I'll try some methods that i've seen in other forums, like softwares that tries to fix this, but i think that i'll be forced to buy a new device. Neither an usb-jig could help me to force the download mode if the phone is dead in every aspect... the only thing that i still didn't understood, is if a debrick.img on my SD card (sadly i've read that a microSD class 10 with at least 16 GB is required, and i don't have one) could help somehow on a situation like this one of not. Still no one could advice me with some tip, guys
Edit - feel free to close this thread, I have another phone now
Hi,
I'm in a bit of a problem.
I got this m8 that was supposed to turn on but it doesn't. I got a battery replacement and everything and nothing changed. Long story short, I plugged it into a computer and I get Qualcomm HS-USB QDLoader 9008 in Device Manager.
So basically, I've done a bit of recovery through QFIL before. It says in QFIL there is no previous software version. I think I could revive it with all the QFIL files to flash onto the phone. I've seen the HTC M9 has these files somewhere on XDA.
Please, I'd appreciate it if someone could supply me with these files or some other advice.
Thanks,
Jev
I have a similar problem and so far been unable to find relevant files or information on reviving a bricked M8 using QFIL.
Please help.
ludemon said:
I have a similar problem and so far been unable to find relevant files or information on reviving a bricked M8 using QFIL.
Please help.
Click to expand...
Click to collapse
In the 3 years I've had the device and been on this device forum, I've never seen the files posted or linked; nor seen anyone unbrick from this condition.
That said (for the second poster, and not the OP) be sure it's an actual brick; as you haven't described any of the events that led to the current condition (one of the pitfalls of saying "I have a similar problem" and not actually supplying any specifics). The message "Qualcomm HS-USB QDLoader 9008 " will appear anytime the device is not powered on (including a brick, but other conditions as well). It may be simple as charging the phone for several hours, then holding power+vol up for a minute or so, to force the phone to boot.
HTC One M8 bricked
Thank you redpoint73 for your reply. I bought this phone with the problem existing so don't know much about what lead to the condition. The seller did say that he rooted the phone and issued some fastboot commands, but couldn't remember the details.
I have left the phone connected to a charger for more than 24 hours, but the charging LED is not on continuously, nor regular blinking.
When the phone is connected to a charger or computer the charging LED flashes on for about 1 second, then nothing more.
In the case of computer connection the USB connection sound is heard (but never hear the USB disconnection sound) and Qualcomm HS-USB QDLoader 9008 appears in Device Manager.
I have tried all the various combinations of button pressing as recommended in lots of places, with times ranging from 10 seconds to 30 minutes or more.
At one stage I taped all the buttons down and when connected to a charger the LED blinked in a regular manner.....on for 1 second, off for 1 second, on for about 0.5 second, off for 12 seconds, and then the cycle repeated continuously. When connected to a computer in this condition the USB connect sound is heard at each 0.5 second blink.
I am currently looking, with hope, at various flashing utilities for phones with Qualcomm chipsets.
You say that you have not seen anyone unbrick from this condition. Does this apply to the M8 only as there appears to be more information available for the M7 and M9?
Hello All,
I have the exact same issue ...
It started by showing messages like "android core/services has/have stopped". I rebooted, then there was no mobile network connection -> No IMEI.
I had no worries, that happened also in the past and I could solve it with a dirty flash.
Then I went to Recovery, dirty flashed my ROM (Android Revolution), phone rebooted and started building application cache.
At some point, it started, then some more caching and ... boom, blackout.
It doesn`t respond to anything. No power+volume combination, anything.
I have even opened it up and removed the battery connector.
Without battery, when I connect it to the power source, via USB, the RED light turns on for a second and the Off. ..
Also, when connected to the PC, it is identified as : " Qualcomm HS-USB QDLoader 9008 " .
Are there any repair possibilities, besides motherboard replacement ?
Thank you in advance.
dachriss_13 said:
Hello All,
I have the exact same issue ...
Click to expand...
Click to collapse
It's debatable whether the issue is "exactly" the same (can have various causes and outcomes) but the current condition is similar. Therefore, did you try the suggestions already offered?
Try charging for several hours. Then try holding power+vol up for a minute or so, and see if there is any change. Anything coming on the screen is a good sign (even if it doesn't boot up fully).
I don't see anything in your descriptions that would indicate anything you could have done to truly brick it. It's hard to brick this phone just by flashing ROMs. So unless there just happened to be a battery or other hardware failure at the same time, I don't think it's bricked. And a hardware failure while you were booting up a newly flashed ROM would be an awfully strange coincidence.
Thank you for your reply.
When I reach home, I will connect it to the charger, let it sit overnight and afterwards I`ll try to start it via Power+volume up.
I will get back with feedback.
Hello All,
The approach with the charging does not work ... I left it overnight, more that 10 hours, and it`s in the same state; it doesn`t react to anything.
When I plug it to the PC, it recognized as Qualcomm HS-USB QDLoader 9008.
Any ideas or hints are highly appreciated.
Thank you.
Further to my previous post I opened up my phone and check the voltage at the battery connector and it was only 2.6 volts, so the battery was obviously not being charged via USB.
I charged the battery up to a nominal 3.7v using an external charger connected directly to the connector and then tried all the button pushing scenarios again with no joy. With the battery charged the phone is not recognised by a PC and the charging LED does not illuminate at all. The condition described previously is only achieved with the battery disconnected (or with the battery partly or fully discharged).
Hopefully these observations might help someone diagnose what the problem is.
dachriss_13 said:
The approach with the charging does not work ... I left it overnight, more that 10 hours, and it`s in the same state; it doesn`t react to anything.
When I plug it to the PC, it recognized as Qualcomm HS-USB QDLoader 9008.
Click to expand...
Click to collapse
Try another charger, try the button combo with the charger connected (and also not connected), try just power, or power + vol down (hold each button combo for at least a minute). Play around, and see if anything works. A few folks have had luck just messing with different combinations.
If you can't get the phone to power on, into at least bootloader, where isn't anything you can do. It will only ever be read by the PC as Qualcomm HS-USB QDLoader 9008. That is, short of opening up the phone, but that may or may not work, depending on what the problem is (battery, motherboard, etc.).
Strange, you are the 2nd person today on this forum with the similar issue, of apparent brick after just flashing a ROM: https://forum.xda-developers.com/showpost.php?p=73039334&postcount=7
Makes me wonder if the emmc chips are just going bad (as this is getting to be an old phone) and the ROM flash is the last straw (although it was on the brink of failure anyway).
But this is just a guess, at best.
Hi,
I know this has been a really old thread. I only realised I had replies now . Anyway, thanks for the replies, I really appreciate it. But unfortunately, no hope for my device. I have tried everything. When I plug it in to any charger, it just blinks red/orange(I can't tell which colour) once, and then just stays dead. No button combo did anything.
Thanks,
Jev
Hi guys,
this is the second time that LG bricked my phone. I updated my g4 and now it won't boot up anymore. Installed was Android 6.0 and the last security patch was from 2016-08-01. Software version was V20h-EUR-xx. I already had the fun of having the famous bootloop and a screen burn in, so i basically got a new phone in early 2018. Mid 2018 i got the notification of a software update (it said something like stability update and was just 50 MB big) but I didn't have the time to back up my stuff properly so I delayed it till yesterday. Two days ago I was preparing myself for the upcoming android 11 devices, so I saved my photos etc and got most of the stuff out of my phone, then I did a backup through the onboard app (LG bridge won't recognize the phone most of the time and if it does it tries to save the backup temporarily on the phone, which didn't work because of low memory space(on a sidenote wth is the g4 doing with all the memory space anyway)) and saved it on the sd card. After that I updated the phone. A screen appeared with with software update process (1/2) and (2/2) and both completed succesfully. After the reboot it got stuck on the LG animation logo, this is a screen right after the "lg powered by android" screen, and it is stuck there since. I tried to get into recovery mode but was unable to do so.
So yes I have a backup, but afaik no user data gets saved in the app backup, am i correct? This is the reason why I haven't tried to hard reset yet. I thought maybe some bright minds in this forum know a way or solution to this problem.
I have read a little bit about LGUP and TWRP but i don't know if this will help. And i don't know which firmwire i need cause there is a bunch with H815.
What I'm asking is, is there a way to restore the phone without losing my data that is still on the phone?
sry for the long text, let me know if you need additional info
greetings Johnny
tl;dr: LG is producing garbage, please help
UPDATE 1
I was able to get into download mode.
Plug the USB Cable into the PC(not connected to the LG G4)
Have you PC Powered On and Logged in
Power Down the LG G4
Press and Hold the Volume Up Button on the LG G4
While Holding Volume Up, Plug the USB Cable into the LG G4
Continue Holding the Volume Up Button After You See ‘Download Mode’
Let Go of the Volume Up Button When You See the ‘Firmware Update’ Screen on the G4
Right now I'm trying to do the update via LG Bridge and the download mode.
Funnily the update is now 1,68 GB in size while on the phone the size was roughly 50MB iirc.
My free memory space is only about 4GB, so i hope this will suffice.
UPDATE 2
The installation was sucessful but only on my second try. The first time it failed at 81%, so I did it again as I was told via LG Bridge and followed the instruction steps. The second time it worked. After rebooting I got the screen that 80 apps are getting optimized. Took nearly 40 minutes. After that I got in and did a quick check if everthing was alright, saw that some apps weren't installed, so I restarted it and the rest got optimized. Power off again, sim and sd card plugged in and power on. Now everything seems alright and if I'm not mistaken battery life has improved.
So in the end it was a failed update caused by LG and fixed by LG Bridge.
BUT in the meantime I contacted LG customer support and it turns out customer support is on par with their update policy, non existent!
Talked to a guy who didn't understand what I wanted from him, so he gave me a number where I could call. Called there, turned out it's the company who repaired my phone when I had the bootloop and screen burn in. After asking them about technical support, they told me they don't do that, they only repair. I understood, so phoned LG again. The same guy picked up again (is he the only one there?), so I asked again. This time he googled my questions and told me he can't find on google what i'm asking. I thought he has to be kidding but he was serious. No blame to this guy though, he is first level support and obviously not qualified to answer such questions, so I asked if he could redirect me to someone who could answer my questions and help me. Therefore he let me wait in the line to call a colleague so he could tell him my problem and then told me the answer of his colleague. I wasn't satisfied so I insisted to talk to this colleague of him, he said it wasn't possible because of technical reasons, but he phoned his colleague and but both phones together so we could talk (wth haha). Needles to say I didn't understand anything and I was absolutely bewildered about what was going on and the state of the LG support. I tried to convince this guy the he was of no help to me so if I just could call this other guy or be called by him would really help me. Finally he understood and gave in. He wrote down my number and five minutes later the other guy called. Well he was of no help either. Couldn't really answer my questions but could at least explain two things of interest to me. I am still shocked of the state of the LG "support". Don't they have guys who know their products and their software?
Thankfully everthing is fine now and I definitely know that I won't buy an LG smartphone ever again.
(The camera and the screen were really nice though)
greetings Johnny
Hello,
New to the forum, at least posting have been lurking and reading for years, but this will be my first post.
Mi 10T Pro, stuck in bootloop. I have been trying to get it going again and have been having no luck, so I decided it is time to turn to the pros for some help.
Symptoms:
Bootloops 1 or 2 times to the MIUI logo, then boots to the recovery menu
Not possible to turn of completely, bootloops until battery drains completely
Able to get to the fastboot menu
What I have tried:
I had a suspicion that it was a problem with the power button, so i replaced the ribbon but no improvement (Unless new one is bad also?)
Replaced Battery, no improvements
Tried all the button press combinations to try and do hard reboot and so on
About Device:
Software version: Unknown as the phone broke a long time ago, got a replacement and the phone has been sitting in the drawer...
Phone was never rooted or unlocked in any other way
The phone is open and I could unplug battery or try a new ribbon for the power button (I have a new one on hand)
What I would like to achieve:
Save the data that is on the phone.... This is the main thing I would like to do as there is precious pictures of my young kids and so on....
Get the phone working and use it as an emergency device
Options I think are still available in order of how I would like to attempt them:
Do a software recovery, by installing a stock rom, example: (
)
I don't know what version of rom to download as I don't know what version the phone was on
I don't know if this will work since the bootloader has never been unlocked
Anything else possible before next step?
Reset through the reset menu. and cry over all the lost data (
All suggestions are welcome.
Thank you!
this phone is notorious for needing to be reballed after a few years of use. its a trash phone. join any mi 10T groups in facebook and youll see countless users who had to pay specialist technicians to reball their CPU and Memory chips and even then, they still fail after a few weeks/months.
Thank you for your answer ongkal. So you don't think its worth to try to overwrite the loader? I don't want to have to reball if its a software issue, but will if it comes down to it.
Mainly just want to get the files out, went back to samsung after first phone with xiaomi...
I was just looking at the reball videos on youtube and most of the phones are completely dead, mine still turns on but straight into bootloop. Besides they say it might be due to gaming, which that phone has not seen