Develop Bugs

Sony Xperia Z1 Compact won't turn on - just red flashing light (still in warranty)

Hello All,
I had about 40% battery yesterday evening and in the morning I found phone turned off.
Tried to turn on - no luck.
Plug to the wall charger - a red light appeared and started blinking in a loop (3s red, 1s pause, 3s red etc.)
Tried with different charger - same as above.
Conected to laptop through USB - red light as normally when charging but no battery icon and scrren still black. Tried to turn on and blinking come back.
I left on charging for a while and tried hard reset (power button + volume up) - nothing.
Tried also a magic reset buttonnear the SIM card slot it vibrates 3 times but it didn't turn on
Thank you in advance for your answers.

Try to charge your phone using the wall charger for at least one full day. If that still doesn't work, try getting into fastboot mode(Vol up while inserting USB into PC), and check if you get a fastboot device. If so, try reflashing the stock via flashmode. If not, I think your battery is dead.
(I had an issue like that on my N4 once, but never on my X1C.)

Hello Jayc94,
If Max1220 tips doesn't work, just use the warranty.
I had the same issue as you, and i sent it back 3 times, using the warranty. As far as i remember, you don't have to pay anything.
My advice, when you get it back from the repair shop, in the package, you have an intervention report. Check exactly what they did. Follow their procedure to reboot your phone, and see what happens few days after.
For me, one week after they sent me back the phone, the same issue was happening again, until the 3rd time. At that time, intervention reports shows they changed battery and antenna, with some other stuff. Until now, i don't have any issue again..
I wih you good luck.
cmartinez.

Qualcomm HS-USB QDLoader 9008 is all that is left from my M8

Hi,
my M8 doesn't turn on anymore. Already tried to change the battery, already tried to start it with VOL+ vor a couple of minutes, tried VOL+ and VOL- for a couple of minutes - nothing. I can't get into bootloader, i can't boot the phone - BUT:
- After connecting the phone to the PC a device "Qualcomm HS-UB QDLoader 9008 (COM10)" shows up
- When putting the charging cable only half the way in the charging LED turns on for 1-2 seconds and then off again
- When trying to do the VOL+ and Power method the charging LED turns on very short every 10-15 seconds as long as i hold the keys
Is it completely dead? Or can i try to flash something with qualcomm tools from here? Its a non-provider phone (HTC_102 i think) and the android variant.
The last thing i did was htcdev unlock after i got it from htc repair where they replaced the motherboard. i installed twrp and then miui7 and after this viperrom and leedroid. With miui it turned on but not every time (i don't know why) but after leedroid it doesn't even get into bootloader.
I don't think this is rom related and more of a hardware issue but maybe you have some ideas. The phone seems to be dead anyway, so let's try something.
Thanks

Dacoco said:
- When putting the charging cable only half the way in the charging LED turns on for 1-2 seconds and then off again
- When trying to do the VOL+ and Power method the charging LED turns on very short every 10-15 seconds as long as i hold the keys
Click to expand...
Click to collapse
What color charge LED?

Orange

Dacoco said:
Orange
Click to expand...
Click to collapse
I have the same issue. Same indicators. Just happened after charging overnight phone seems completely dead. Tried everything. (Light trick, Volume Up & Down w/ Power)

For the most part, if you've charged the phone for several hours, and all your are getting is orange/red LED (I would call it red, but maybe I'm not remembering it correctly) and the button combos don't work, its probably bricked.
Try holding power+Vol up for a minute or so (it will sometimes take that long to reboot, in certain circumstances). Also try Power+Vol up+vol down (but it sounds like you did already).
Also try the button combos with or without the charger attached and plugged in. In can think of at least one user, that had success with the charger plugged in, when they had lost all hope.
Basically, the device will come up with the Qualcomm Download message on your PC anytime the phone is not powered on. So it can be an emmc failure, or a dead battery. You can try replacing the battery, but that can just end up as a disappointment (which looks like may be the case for the OP). Or you can even have the Qualcomm message come up, if the charge is too low. I've had that happen once, gave me a heart attack. Red LED, and no response to button combos. I let it sit on charger for a few hours, then holding power+vol up for a minute made it boot, much to my relief.
---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------
Dacoco said:
Orange
Click to expand...
Click to collapse
I would have been more hopeful if it was a green LED, appearing for a second when you connected the charger. That would have made me think maybe the charge port is just loose.

Same problem
having the same problem and i have noticed that when I plug it to pc then I shows qgusb dloader and when I press power button or any other button combination then I stop showing as qgusb dloader it appears as device is unplugged and then if I replug it then it won't show anything nor led neither qhusb..But after 10 min or so if I plug it then it again shows led and qhusb and I have also noticed one more thing that if I plug it in charger then led just blink for some microseconds but when I plug it to pc led blinks several times dim solid for 2 3 seconds is there any hope?
I reached this stage by installing unknown ROM .
By the way I have one more HTC one M8 but its from different career (at&t) and it's also rooted and custom rom installed but its in very bad condition just working but i m thinking about replacing motherboard or battery so i can fix it it this idea succesfull ?

narshi shukla said:
I reached this stage by installing unknown ROM .
Click to expand...
Click to collapse
What do you mean "unknown"? Do you mean, you can't remember exactly which ROM you flashed?
I presume you don't mean you flashed something, without knowing what it is.
Do you remember anything about the ROM?
What carrier version of the M8 are you talking about?
S-on? If so, its hard to brick this phone with s-on.

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
Please don't post the same question to multiple threads. One place is enough. It makes it confusing to those trying to help you, and it's therefore against forum rules.

Understood, won`t happen again.
Thank you.

HTC M8 Dead. Doing strange things. Help appreciated.

Hey all,
Got a second hand HTC M8 in an auction yesterday and it was marked as being faulty. The usual.
Plugged into my 5V 2A charger. Orange LED came on for about 5 seconds then goes off.
Tried again and again. Eventually got it to stay solid Orange for about 5 minutes before it went off.
Plugged it into my PC and it installs "Care Suite Emergency Recovery".
And that's where I am stuck. I google Care Suite and all I get is stuff related to Nokia.
However, I did come across one that says that it's a "Dead Boot" - Bricked in other words.
Just thought if there is anyway to save this device. Even though it is old, it would be still nice to get it going again.
And I have tried Key combos and nothing (P, V Up, V Down for a minute etc).
I have no idea if the previous owner tried to root the phone or anything. It's anyone's guess.
Any help would be gladly appreciated.
Thanks!

Try charging for several hours (such as overnight) on wall charger (not connected to PC). Then try power+vol up for a minute or 2. Or just power button for a minute or 2.
I don't know what "Care Suite Emergency Recovery" is. But it's normal to get the Qualcomm download mode message when connecting to PC whenever the phone is powered off. That message (Qualcomm download mode) also appears in the case of a true brick (JTAG or new motherboard needed). But it doesn't definitely mean a brick. It just means the PC can't talk to the phone, and that happens if the phone is simply powered off, or battery dead.
I'm assuming/guessing the message "Care Suite Emergency Recovery" is a similar or same symptom.

Ultimate Bricked Zuk z2

I was flashing the zui with qfil and now my zuk is with a black screen and vibrate every 32 seconds
Qfil error: https://imgur.com/a/pUjb3IB

Chewbaccaun said:
I was flashing the zui with qfil and now my zuk is with a black screen and vibrate every 32 seconds
Qfil error: https://imgur.com/a/pUjb3IB
Click to expand...
Click to collapse
Well use this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/lenovo-z2-plus-zuk-z2-plus-hard-brick-t3713126

JV Spartacus said:
Well use this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/lenovo-z2-plus-zuk-z2-plus-hard-brick-t3713126
Click to expand...
Click to collapse
problem solved

Nothing helps..?
(I will post this also here, cos no one answered @ zukfans yet)
Hi! I think I need to ask help now.
I've managed to hard brick my Z2 with QFIL trying to update the phone from zui 2.something to 3.5. Well obviously that did not end up good.
My phone went to a stage described in some cases: White light blinking every 15 seconds or something and phone vibrating. Ok, I tried to shut the phone down by keeping and releasing after second blink. Did not work. Then I tried to hold for two or more minutes. It seemed to work first but suddenly also that didnt work (kept power pushed for ten minutes or more). Ok, the I made the cable described here. I did a jumper cable from my usb extension cord. Windows reacted to the phone but did not recognize it. Nothing showed up in device manager or QFIL or MiFlash. The phone keeped on vibrating and a left it like this for the night. I guess battery ran out and phone finally shutdown.
I continued and same results. One time windows recognized a unknown device for some seconds but it did not show up in device manager or MiFlash. After that nothing. Now the phone only blinks the light. It vibrates only when trying to charge it or plugged in PC. I don't now if it's on or not. Anyways, the same results with windows: reaction, but no recognition. I've tried to pull usb out and change to another slot etc.
Also I've installed Zuk 1.05 drivers, MiFlash and tried also with Qualcomm drivers. Uninstalled everything and tried again. Nothing seems to help.
Could this be because of Windows 7? Or bad extension cord? Or what...? Any advice would be appreciated.
edit: It was not Windows problem I guess. I installed fresh Windows 10 with no help. Actually worse. No Windows is not reacting at all. Maybe it's the jumper cable I created. I didn't want to ruin my only USB-C.
edit: Ok. Back to Win7. Now there is no reaction at all also in Win7. The phone vibrates when connected to pc. Otherwise phone seems to be off. No lights flashing. If power is held down white led flashes briefly but no vibration.
edit: Now if I connect the phone to laptop the led blinks every 0.5 seconds... I have no idea how turn the phone off. It seems to be off while not touched because nothing is happening...

@Pelepako
Try this,just a copy paste
2.0). Turn off the phone. If the phone boots up (reboots) then immediately to point 2.1
2.1). Put wire on the 2nd contact on the left
. And together with the wire insert into the PC (at the same time the phone is already connected by cable).
2.2). After 5-10 seconds, take out the usb plug with the wire. Remove the wire and insert the plug back.
2.2.1). If you do not have a bootlap, but it hangs on MI, on the boot process, etc. Hold the POWER button and insert the USB plug with the wire into the usb port. The screen goes out and you get what you want.
3.1). Your device in EDL mode.
3.2). Click REFRESH in Miflash and see your device in COM format.
3.3). Flash firmware at your discretion.

Thanks for the instructions.
Still nothing. Windows 10 does not recognize the phone in any way. The phone vibrates almost immediately when plugged in. Then nothing. Sometimes (before) I got Windows to recognize it as "unknown device".
2.0 Turning off the phone. I'm unpluggin the battery. I guess that does the job? At least nothing is flashing or vibrating.
2.1 I inserted a paper clip as in the picture.
Dunno if it's a driver thing. I've installed different Zuk driver version, Qualcomm, MiFlash, QFil, ADB.. you name it. I've turned on the Test Mode in Windows (driver signature). I've tried two different cables. One of them is the original. Tried the paper clip trick and the wire connect trick. Nothing is working. There has to be some flaw that I'm not noticing. Can't be the only one who really got his phone bricked...
About the drivers:
Ive installed zuk 1.05. Is it ok? Tried also 1.06 and 1.08.
How to install ADB. I've used ADB installer and installed system-wide. Should I also install the device driver (Google)?
Qualcomm drivers. Cannot manually install. With Miflash etc. some Qualcomm drivers get installed.
Do I need to install Fastboot and ADB "executables"? Where do I need these in my situation? Nowhere?
What abou QFIL? Is it necessary if I'm using MiFlash?
narshi shukla said:
@Pelepako
Try this,just a copy paste
2.0). Turn off the phone. If the phone boots up (reboots) then immediately to point 2.1
2.1). Put wire on the 2nd contact on the left
. And together with the wire insert into the PC (at the same time the phone is already connected by cable).
2.2). After 5-10 seconds, take out the usb plug with the wire. Remove the wire and insert the plug back.
2.2.1). If you do not have a bootlap, but it hangs on MI, on the boot process, etc. Hold the POWER button and insert the USB plug with the wire into the usb port. The screen goes out and you get what you want.
3.1). Your device in EDL mode.
3.2). Click REFRESH in Miflash and see your device in COM format.
3.3). Flash firmware at your discretion.
Click to expand...
Click to collapse

Ok. Just found out that the only 2.0 port is broken. There is no second pin. At least anymore. I might have broken it in some point.
Other reason for malfunctioning could be the circuit board of the phone. The previous owner in all his wisdom had glued the battery cover with super glue. As I opened it it ripped of some of those circuit materials that conduct electricity. The broken part is near the usb port of the phone. Maybe if I put the cover back it will work cos the ripped parts are still glued to the back cover..

So back to the issue.
The broken part of the phone seems to be speaker so it should not affect the connection I guess. I also fixed with conductive silver paint. Still, no help.
Just found out that the charger and probably also the cable are not original ones. Maybe this is the reason for this is not working. I cannot come up with any other solutions. Now I would need to know which usb cable would qualify for the procedure. How can tell which is a proper cable before buying it? Also does the micro-usb cable work if I have the convertor dongle (Samsung made)?
edit:
Ok. Sometimes the led blinks every 0.5 sec. Sometimes phone vibrates every fifteen or something seconds. Only way to get the computer to react is with modded usb extension cord -> green to black. This way Windows recognizes an unknown device. That's it. I cannot install Qualcomm drivers for this or do anything else. This way Windows makes this connected sound every 0.5 seconds and the phone led blinks. After a while it stops and the phone is marked as "unknown device". Also if I connect the phone to a charger it blinks all the time (0.5s) and vibrates occasionally. Then after a while the led calms down and blinks every 15 seconds. And then back to 0.5s with vibration. All these symptoms seem unclear and I haven't found anyone suffering from same kind of problems...
Really am I the first that really bricked this one? I didn't even use the phone yet. Just checked it and tried to update the system cos it was old version.
I assume that the phone has to be off after disconnecting battery cable so that should not be the problem here.

@narshi shukla
I turned the phone off by removing battery. It does not reboot after shut down before I connect it to computer. Few seconds after connecting to pc it vibrates shortly. Nothing else happens after that. Same with and without the wire.
I've tried so many different methods that I'm giving up with this I guess. Am I the only one who got his phone permanently bricked. After all I tried to flash by following instructions. The flash failed and phone went on crazy vibration and screen on for some seconds after that it was vibrating every 15 seconds. Then suddenly it stopped doing that. Now it does only if I plug it to pc or charger.
The "black green wire trick" is strange. If I only connect those two wires nothing new happens BUT if I connect green to black and black to green by tying instead only touching the phone vibrates and led blinks every 0,5 seconds and windows also makes the connection sound even though it is not working.
narshi shukla said:
@Pelepako
Try this,just a copy paste
2.0). Turn off the phone. If the phone boots up (reboots) then immediately to point 2.1
2.1). Put wire on the 2nd contact on the left
. And together with the wire insert into the PC (at the same time the phone is already connected by cable).
2.2). After 5-10 seconds, take out the usb plug with the wire. Remove the wire and insert the plug back.
2.2.1). If you do not have a bootlap, but it hangs on MI, on the boot process, etc. Hold the POWER button and insert the USB plug with the wire into the usb port. The screen goes out and you get what you want.
3.1). Your device in EDL mode.
3.2). Click REFRESH in Miflash and see your device in COM format.
3.3). Flash firmware at your discretion.
Click to expand...
Click to collapse

Fastboot won't connect to Nexus 7

I have an issue very similar to this thread: https://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/unable-to-nexus-7-fastboot-mode-t3966600
I got mine for parts on ebay with "power issue." It had low battery and it charged up fine overnight, but when it boots up to either system or recovery it just stays on the Google logo.
It boots into Fastboot fine, but it will not connect to my computer. Computer has the lastest Manjaro linux with android-tools and connects to my Xiaomi Mix 2S fine, but neither "fastboot devices" or "lsusb" will show anything about the nexus, in USB 2 or 3 ports.
I opened it and reseated the silver cable between the boards, and also tried several different micro-usb cables, no dice. The port and circuit boards look completely fine. The screw seals show that it has been taken apart before.
I was not able to boot it to enable usb debugging, does fastboot need that?
Update: I did actually get it to boot, when I opened it I unplugged the battery and held the power button for a while to drain all the power. Fastboot still does not work, but I was able to factory reset it and install the last two updates. Curiously, I cannot connect to it with USB, maybe the data lanes are dead? And then after using it a half hour, it froze and I had to hold the power button to turn it off, and now its back stuck at the google logo.

Ekterm said:
I cannot connect to it with USB, maybe the data lanes are dead?
Click to expand...
Click to collapse
Measure the data lanes:
https://forum.xda-developers.com/showpost.php?p=80212550&postcount=4
and
https://forum.xda-developers.com/showpost.php?p=80218074&postcount=6
It's a different USB issue but the measurements must be the same.