Database Users

Help: Always booting to Download Mode

I've got a strange problem with my Tab where it insists on booting into download mode. It says factory mode in the top left rather than odin mode.
The only ways I've found to get around it is either plugging into a computer and flashing something with Odin, either a full rom or just recovery. Then it seems to boot ok. The other way seems quite strange, I just plug in the USB host adapter (without anything plugged into the USB port) and hold the power button till it reboots, then it boots up ok.
The other problem though is that the USB host no longer works when it's booted.
I actually took it back to the shop where I bought it, demonstrated the problem to the shop staff, they sent it away to get look at and by the time the technicians looked at it a week later it was working fine. When they gave it back I even tested the USB host was working and that was fine too. But after a couple days it has started doing it again.
Any ideas what the problem could be? Initially I suspected a faulty plug on the bottom of the unit since that was the only way I could make sense of the USB host adapter making it boot. I'm still thinking it's either that and when they plugged it in to look at it it reconnected a dry joint or something - or that the battery went flat and that reset whatever is causing this.
I'll take it back to the shop again if I have to, but don't fancy another week without my phone, especially if the same thing happens again.

I had a similar problem and I fixed it by letting the battery go flat and doing a factory reset after it re-booted normally.

Can't boot and basically unresponsive after 5.0.1 patch, strange display and keys

After installing the 5.0.1 patch last night, I find myself in a very weird situation with my Nexus 10. Essentially, I can't get it to display anything, or react to any keypresses unless it is being powered via the POGO plug.
When powered with the POGO plug and connected to a computer via USB, I was able to use fastboot to attempt to reflash the 5.0.1 factory image -- however, the screen remained blank the entire time and wasn't backlit. I was able to get the factory image flashed successfully according to fastboot but when it was complete and fastboot said the device was rebooting, nothing happened. I then unplugged the USB cable and POGO cable, and attempted to power it on and got nothing. Despite how long I hold the power buttons, I can't boot into the bootloader or get any response from the device.
If I plug it in via USB, I get nothing -- no charging icons, Windows does not recognize the device is detected and I still don't have any response from the keys. If I remove USB and use the POGO cord, the N10 turns on with the Full Battery/Lightning Bolt icon -- once here, I can hold the power button for 10 seconds and get it to act like it's going to boot but then the only thing the display will do is flash the white Google logo, flicker very briefly, and then immediately power down.
I have tried several different factory images, all with the same results. I'm not sure what could be the problem, as I think I've covered most all my bases. The tablet was never dropped or water damaged and wasn't exhibiting any signs out of the ordinary until last night when 5.0.1 was applied.
Could this ultimately be a battery issue? I did pull the back off and meter the red/black wires of the battery which read 3.85 (the battery is labeled as 3.77 so I'm assuming this is a valid range) so it seems as if it's charged which is what has me so stumped.
If anybody has any insight on what this might be caused from, or things I can try I am open to any and all suggestions! This one really has me determined to solve it!! Thanks for any and all input!

I don't have an answer for you but you can remove the pogo plug from the equation as it is for power only. To the best of my knowledge Google never added the circuitry nor the kernel code to use the pogo plug for software updates.
Sent from my Nexus 10 using XDA Premium HD app

Cannot properly charge my S5

Hi, i just got my Galaxy S5. Somehow i had some charging problems and after it had contact problems and constantly showing "Connected" - "Not Connected" it completly stopped working when i installed Lollipop. I sent it to a repair center and they swapped the charging port and installed KitKat Stock firmware again. Charging now worked, but after some days the error came back again. I reinstalled KitKat via Odin again and now its charging normally. But i know this error will come again and i have no idea how this is possible.
No matter which firmware i got:
- When plugging in the charger while Android is shut down, it shows a battery with a yellow warning symbol. But the phone everytime detects when the charger is plugged in even if its not charging (when Android is running, it doesnt even shows the charger is connected)
- Connection in Download mode via Odin 100% working without any disconnection problems
What the hell is the problem when its not hardware-side and works when i reinstall KitKat?

Push...
Sent my S5 to Samsung and they replaced the charging port. Charging on KitKat WORKED flawless. After Lollipop Update via KIES it has contact error again and does not charge ... Download mode fully working, Charging while Android running NOT working, USB connection not working and charging while Android shut down shows battery error symbol after 1 minute. But it detects that the charger is plugged in when android is shut down....
Sometimes it detects USB and charger but very randomly and for short periods of time. Right now it somehow detected USB connection and works since some minutes after it showed connected disconnected for several times.

Get the phone replaced, it's obviously faulty

*Detection* said:
Get the phone replaced, it's obviously faulty
Click to expand...
Click to collapse
I cannot replace it, only send it to the support again. But it cant be that Download mode is working but depending on the Android version USB and charging is not. This is just not possible and cant be hardware-related.

Don't know if this has been already considered, but: did you try another USB cable and/or another charger ? Maybe its not the phone after all !
Just my 2 cents,
Axel

Uwe303 said:
I cannot replace it, only send it to the support again. But it cant be that Download mode is working but depending on the Android version USB and charging is not. This is just not possible and cant be hardware-related.
Click to expand...
Click to collapse
Of course it can be hardware related, if it was firmware related, it would be happening to everyone

Mi A1 dead, LED blinks on charger, how to revive?

Hi! Similar problems have been posted on the forum before, but none of the solutions worked for me.
Stock Mi A1 with vanilla Oreo (latest official patch), everything stock & vanilla, no hacking, no rooting, no modifications etc whatsoever. All apps installed through google store, nothing fancy.
In short: put my phone into airplane mode about a week ago (battery at 90%), then a few hours into the flight the phone blacked out. Won't react to power button, power+volume up, power+volume down, all buttons, no buttons, any combination of buttons for any length of time. Phone was in my pocket, no physical impact or anything, just "died".
There are 2 signs of life:
- If i plug it to charge the notification LED blinks about 1 / sec
- If I connect it to a computer, it recognizes it as Qualcomm 9008 blabla device.
What I have tried so far and didn't work:
- All imaginable button combinations: no reaction
- Fully charging phone: doesn't help
- Letting battery deplete: doesn't help
- Disassembled the phone, disconnected the battery, put it in charger, reconnected the battery: this fixed the issue for some, didn't work for me.
I GUESS that since the computer recognizes it I could try to "flash" it or whatever, although 1) there are a lot of negative posts about it 2) I have no idea how to do it (which exact ROM, using which exact tool, etc).
I wouldn't mind not losing the data on the phone though, if that is an option: I was about to back up my photos on the flight, but it died before I could have done it.
There is no official Xiaomi support / service where I live, bought the phone while visiting a country which sold it.
Any suggestions?

Small update.
- adb doesn't see the device.
- Miflash sees the device, but dies at "ping via firehose" stage.
-A1 low level backup tool doesn't see the device.
After 2 weeks of googling I have found around 50 forum threads around The Internet with similar issues, but no solution as of yet. Sounds promising!

I had this problem 2 hours ago and fixed with the Disconnect battery, connect charger, reconnect battery (while charger is still connected just to clarify). you tried this fix like this? reconnecting battery while charger is still connected?

Maybe try getting a different battery and connect it, and/or maybe let the battery discharge itself.

KeiFTW said:
I had this problem 2 hours ago and fixed with the Disconnect battery, connect charger, reconnect battery (while charger is still connected just to clarify). you tried this fix like this? reconnecting battery while charger is still connected?
Click to expand...
Click to collapse
Thanks for the replies fellas. I have tried this before. Now I have tried this again just to be sure. Did it multiple times. Disconnect battery, connect charger, reconnect battery. It doesn't alter the phone's state in any way. Doesn't react to buttons, flashes led on charger, shows up as qualcomm 9008 device on PC, but doesn't let me flash anything. Sad.

Qualcomm 9008 is sigh of faulty emmc chip. Bad soldering i guess. Take the device to the service center. My 1 cent op. Regards

Its very simple the solution. The problem is the cable. Try to change the cable, charging the phone and turn it on. I my case works

fusionfan said:
Sad.
Click to expand...
Click to collapse
Have you had any progress? I'm having similar issues with my mi mix 2s.

The answer is to replace the battery. I have two dead batteries for my Mi A1. Both batteries were left in the drawer for several months and upon connecting them to my Mi A1 they showed the dreaded blinking light. After trying to fix this for a day I gave up. I disconnected the battery, the phone booted up right away. Bought a new battery and everything is working again. Hope this helps!

I too had numerous kind of hard bricks with my previous smartphones.
Here are the links that will save your life:
Link 1
Link 2
Link 3
Try the ones that you think fit the most.

I had the same issue just today
removed the battery connector and connected it back without touch any other component
phones working fine now

its bricked and get into edl mode just try to flash with MiFlash tool i have faced this problem some time ago when i flashed an ota with twrp recovery then my phone went dead and when i connect it to pc led blinks and phone recognise in ports as "diagnostic port 9008d" something like that then i install the drivers and flash stock pie rom with MiFlash tool but after successful flashing phone wont boot but after pressing power button for 10 to 15 second phone starts. i have unlocked bootloader so it works for me but i'm not sure it works on locked device try it or use QFIL flash tool from QPST

This happened to me but all i did was charge the phone the whole time.

My Xiaomi A1 had the same issue, I think I have tried all available solution but unfortunately mine still dead, and when I connect the charger it blink.
I guess the ultimate solution is to throw it to a recycle bin.

Galaxy s5 won’t boot up

Please can someone help me with a problem I’m having with my Samsung Galaxy s5.
I put my phone on charge before I went to bed and when I woke up it was still showing a red LED. I knew this was wrong because it should have had enough time to charge and turn green. I had not powered the phone off before putting it on charge and I plugged it into the same USB 3.0 charging lead I have been using for the past six months. I unplugged the phone and pressed the power button to light up the lock screen but it didn’t light up.
I’m thinking possibly something has either shorted or over heated and fried something either on the charging port assembly or one of the chips adjacent to the port while the charger was plugged in. It seems like only a trickle of power is getting through to the phone. When I plug a different USB 2 charging cable into the phone, without trying to power on, the charging icon appears but shows no charge at all in the battery.
I have also tried the spare battery I have but it’s still the same. I know the spare battery is 100% fully charged because I store it in a separate charging/storage box which shows a green LED when it is full. In fact the one which was in the phone at the time is also fully charged according to the charging box. Neither battery has got warm at all inside the phone. I’m confident both batteries are fully charged and totally fine and the problem isn’t with the batteries.
At this point I removed my sim card and also the MicroSD card. I needed the sim to use in my spare phone and I wanted to see if the sd card could be causing the issue but after again trying a normal reboot it made no difference.
I’ve tried several possible things I found on google but nothing has worked. Between each different thing I tried I had to remove the battery for 10 seconds and insert it again to get it out of the boot loop so I could try something else.
Initially when I tried booting into safe mode, then recovery mode and then download mode it brought up the screens for those but in each case after a few seconds the phone powered off and went into a boot loop so I couldn’t attempt any recovery options such as clearing cache etc. Now I cannot even get it to start any of those modes at all and all that happens is the phone does a little vibration, displays the Samsung logo and then just boot loops no matter what I try.
I have tried removing the battery and leaving the phone for a few hours then powering on again but it still just loops.
I have tried pressing and holding Vol-down when plugging it into my PC using a different USB 2 cable and windows acknowledged a phone was plugged in but said it couldn’t connect or recognise the phone and suggested the phone could have a fault.
I don't know if maybe my USB 3.0 lead has a fault that could have caused it or if there could have been some electricity spike while the phone was plugged in, or as I said a component has just fried.
I strongly suspect this is a hardware fault and not a software fault but as I’m not a phone engineer I have no idea about how to trace any possible hardware issues or what might have gone wrong. I would really appreciate any help or suggestions about what the problem might be as this has been a great phone for the last 2 years since I got it and I’d be sad to have to junk it and buy a new one.
Thank you.

I would not junk it yet......
You had mentioned that you go through a lot, just to get phone into Recovery ( " Initially when I tried booting into safe mode, then recovery mode and then download mode it brought up the screens for those but in each case after a few seconds the phone powered off and went into a boot loop so I couldn’t attempt any recovery options such as clearing cache etc. Now I cannot even get it to start any of those modes at all and all that happens is the phone does a little vibration, displays the Samsung logo and then just boot loops no matter what I try." )
OK, just my 2 cents here on this... Why not trying to goto Recovery by pressing and holding the Volume Down (vol-); Home button, and The Power button all at the same time. (yes, if you have a Recovery, and its works, you should be able to boot right into Recovery- >Now, (I would, cause I've been there..) I would also have a PC going with Odin open (Plus the Latest Stock Rom) ... If it works, you would flash the Stock ROM, to clean up anything, giving you all stock, but you can change that of course ...then go from there...
Second, if you can not still get to Recovery.... Have you tried a Stock USB Cable, only asking.... Obliviously something is a miss... with Power... IF phone is off, and you plug it to a power source ... then system has power, and these can power up with just the usb cable, without having the battery in..... Been there. Can add the simple fact, if using just a Micro SD cable, they can bend the Power Board. Believe me (Had to fix the Wife's S5 a few Frinkin' times....) That is why, I say using the Stock Cable, or even a USB 3.0 Cable (like the stock one) does help with power issues when the Micro has bent up the power board...
Will check back and see if this may have you to Recovery or fixed... sure hope this can help you out

Thanks for replying godofsalt.
At the time the phone was plugged in to my USB 3 lead which charges faster and all I can think is that perhaps there could be a fault with the lead or the higher ampage of using this lead caused a circuit to burn out.
I have around a dozen USB 2 leads and I've tried your idea with 3 different ones but none of them will fire up the phone at all with the battery taken out.
I am sure this is going to need some kind of replacement either of the charging port or the motherboard. I don't rate my chances of trying to do it myself and I don't think it will be economic to take it to a shop so I've found a better option by buying the same phone which is second hand but in good condition. That way I know I have all the additional accessories already for probably the same price any shop would charge to fix it.
In future I'll stick to using a decent USB 2 lead on the 1 amp charger I used to use before and hopefully this will not occur again.

G500F battery graphic/boot loop
Had the same problem a few days after installing a 9.0 Rom. My battery is brand new and all cables aren't too aged, so I thought this had to be a physical fault of some kind, but then I had the thought to flash an older bootloader and just like that my battery started taking a charge again and I could boot up. Switched to Flyme os for a while the went back to 9.0 again, with the lastest bootloader and the thing stopped working again. Don't know too much, but I'd try and flash a different bootloader to see if there's any difference. My device failed right at the Galaxy logo, then looped the charging graphic endlessly but would strangely go into download mode and not fail. Don't know if this helps, just thought I'd share my solution.

Thanks for replying henderia93.
My symptoms are very slightly different in that the phone couldn't maintain any of the modes I tried for more than a few seconds before going back to the boot loop again so there was no chance of trying any software fixes including flashing the ROM. Now it won't enter any of those modes at all. I'm certain that's due to only a trickle of power getting through to the main board, not enough to maintain any recovery modes, so there is just enough power for it to attempt to boot, but no more so it just keeps looping, most likely caused by something that has blown while on charge.

MarylinC said:
Thanks for replying henderia93.
My symptoms are very slightly different in that the phone couldn't maintain any of the modes I tried for more than a few seconds before going back to the boot loop again so there was no chance of trying any software fixes including flashing the ROM. Now it won't enter any of those modes at all. I'm certain that's due to only a trickle of power getting through to the main board, not enough to maintain any recovery modes, so there is just enough power for it to attempt to boot, but no more so it just keeps looping, most likely caused by something that has blown while on charge.
Click to expand...
Click to collapse
I ha e taken so many of these a part... Like I may have mentioned, there is a Board, just for the USB (data and power (i still have 2 of them)).... In short, you really have to pretty much take the phone a part. Being very careful with the Screen, and the "Sticky" LEDs and the Home button. There is a lot to it actually.
Like I said, been there done that... Cheap to get, takes some time but it is possible to replace that board. It's a separate board different from the actual main CPU board.
I would have to find it, but I had a manual, for taking these a part.

godofsalt said:
I ha e taken so many of these a part... Like I may have mentioned, there is a Board, just for the USB (data and power (i still have 2 of them)).... In short, you really have to pretty much take the phone a part. Being very careful with the Screen, and the "Sticky" LEDs and the Home button. There is a lot to it actually.
Like I said, been there done that... Cheap to get, takes some time but it is possible to replace that board. It's a separate board different from the actual main CPU board.
I would have to find it, but I had a manual, for taking these a part.
Click to expand...
Click to collapse
While I've been looking for answers about this I've seen teardown videos for the s5 so I can see what the port assembly looks like with it's little PCB behind it. As I have a replacement s5 on it's way all I need to decide now is whether to keep the old handset for spare parts or see if I can follow the teardown video to try and install a new port assembly to get the phone working again as a spare.

MarylinC said:
While I've been looking for answers about this I've seen teardown videos for the s5 so I can see what the port assembly looks like with it's little PCB behind it. As I have a replacement s5 on it's way all I need to decide now is whether to keep the old handset for spare parts or see if I can follow the teardown video to try and install a new port assembly to get the phone working again as a spare.
Click to expand...
Click to collapse
Yep, me too, seen many vids on the tear down. I decided to go a bit more, IMHO, to have an actual manual, PDF, when I did my first one, many years ago. So, can read, and use photos wisely. Seen too many Utube crap, where the break it, destroy it..... crazy!
Well, at this age, not too sure what to do my self. In our case, our present service is cheaper to Keep these. Grandfathered in, and we pay a but less, than going to any other carrier. Plus, these newer phones are not cheap at all.
True, it up to you. hope all goes well.

Sorry I am a novice so please excuse my question.
Are you assuming that the usb port is shorting even when no usb cable is inserted? As you put a fully charged battery in with no change it would seem that the act of charging is not involved.
Have you tried a voltmeter to check the voltage at the battery charging pins?
Have you tried to check the voltage at the two pins commonly used for a wireless charging adapter (to the upper left of the battery) to see what the voltage is?
Sorry if I am off base.