My phone wouldn't power on so I got it repaired at a phone repairs shop. The guy there thought there was a software error because he saw the error triangle on bootup. He was mucking around with it in download mode when I got there, I said not to worry about it, paid for the repairs and left.
The phone will not boot, and will not go into recovery or download modes with the respective key combinations
UNLESS
I have it plugged into a power source, in which case I can enter download/recovery mode, but when I try to boot the phone I just get the empty battery picture with the loading circle appearing periodically.
--- Possible solution: bad battery
I have flashed CWM onto the phone using odin in download mode and have flashed .zip roms that were previously working before this debacle, but again the phone won't boot onto the newly installed rom.
I have tried flashing the correct stock rom using odin but the phone won't boot this way either.
When I take the battery out and connect the phone to a power source it is non-responsive.
Apart from a batter problem (which I will be able to test tomorrow), what could be the cause of this problem, and how might I be able to fix it?
Sounds like a JTAG (but don't get your hopes up) or a motherboard replacement job (more likely) to me. If the phone won't boot at all/shows no signs of life, something is majorly wrong. As to what that is, nobody here could tell you that with certainty because we don't have the phone in front of us, but if it's not booting at all either the NAND is buggered or something else on the MB has crapped itself.
Cross your fingers it's just a simple battery issue, but it doesn't sound like it.
MistahBungle said:
If the phone won't boot at all/shows no signs of life
Click to expand...
Click to collapse
What does being able to access recovery mode/download mode contribute to this? The phone works to a degree, it seems, it just won't boot to an OS.
How might I go about troubleshooting the hardware?
(Might as well use this as a learning experience)
Right. Sorry. Just re-read your OP. Still sounds like the NAND is stuffed, which explains why you've tried flashing flashing stock/CWM & phone still won't boot normally. One thing you could try is search for Hopper8's 'Odin troubleshooting' thread, and flash the 3 part firmware linked in that thread. If the phone still won't boot normally after that, it's pretty much a certainty that you'll need to replace the MB at least, which leads to the next paragraph...
Also, if you find the 'booting when plugged into charger but not with battery' thing is still happening even with a new battery, that suggests whatever circuitry is responsible for taking zzz's from the battery & powering the device is (also) faulty/damaged. You could also try the obvious & clean the battery contacts with some isopropyl alcohol. The most common charging/power type problems we see here is the USB board/port dying. But if the phone is slightly functional whilst on charger, it probably isn't that, still might be worth replacing though given how quick/cheap/easy it is to do. There could be a short/whatever causing at least some of the problems, and it wouldn't be the first time a faulty USB board has caused that/manifested itself in less obvious ways than what we normally see (I.E causing the problems you're seeing rather than causing intermittent charging problems or phone rebooting randomly on its own or whatever).
In that case, try the service manuals for the device; these have been posted here before & can also be found with a Google search. They have detailed schematics/parts lists/walk throughs of the most common repairs w/pics, and might help if you want to have a go at fixing it yourself.
Thanks for the response.
I'm in the process of downloading the three part firmware to test later in the night.
Providing that fails, I'll look into part supplies and start researching how I can, if at all, repair this myself.
On the topic of faulty USB boards- I had my phone serviced a few months ago for just that, and it worked fine, but in the weeks leading up to this event my phone HAD been rebooting itself semi-regularly, although I put this down to a software issue rather than a hardware issue. I'll get my hands on the service manual for the I9100 and start reading up.
In the meantime I can just get a cheap burner Nokia that won't play up on me for the next 20 years.
Interesting. In that case, given the other alternatives are more expensive (assuming the 3 part firmware & new battery doesn't fix things), it may just be a case of another dodgy USB board & you might want to start there.
If you can't find the manuals anywhere, let me know & I'll see if I can dig them up from an external drive I have stashed away somewhere (don't have it handy now, but will dig it up tomorrow for you if necessary).
Yep, unlike current technology, old phones like that just seem to work no matter what you throw at them
The three part firmware flashing has moved things along slightly- after it finished the stock SGS2 boot screen appeared for a second or so and while leaving it on the charger it will cycle between showing the grey loading battery and an android with a loading bar underneath, which is progress from before. It is still unresponsive when disconnected from the power- I have procured the service manual and will look into disassembly/diagnostics when I have some small enough tools. I'll still try using a different battery when I can, but it probably isn't the issue.
Clean the battery contacts hard with a pin
Sent from my GT-I9100 using xda premium
I woke up few days before while I was keeping my Galaxy S3 in the charger and found out no electricity, however, I found out that the green LED is blinking too fast. I pushed the power button to get it unlocked but it didn't respond. I had to hold the power button to force it restarting (as usual in such cases) after unplugging it from the charger (for any expected power return back to source), however, the phone turned dead. It is no more powering on, I replaced the battery with another one, I used the charger when power is back, another charger and connected the USB to PC and nothing happened! I left the battery off the phone for several hours but it didn't work, though.
The phone is now hard bricked but would this case be a system board failure (high voltage) or just the bootloader became malfunctioning? Since the phone is out of warranty, I opened up the case, removed the battery and opened it and removed the system board carefully (I'm a Computer Engineer and took my precautions). Then I used a multimeter continuity check to make sure there are any charges. I applied it to the power button and the multimeter read 1 with high sound while any other part to read very high value with no sound.
I had to send it to the official Samsung repair shop for checkup and they told me it might be a system board or software issue (they didn't explain but I understand something regarding the bootloader/EFS...etc) and a system board would cost about 330 USD!! I should know what happened by tomorrow and decided I won't replace the board at all in such a price but I'm assuming it's a hard-brick.
1- The LED was blinking before I had to force hold power button to get the phone restarted, hence I think it didn't get high voltage from power source.
2- Would force holding power button to get the phone restarted to cause a power damage to the motherboard?
3- Would force holding power button to get the bootloader malfunction?
4- The multimeter's continuity test I performed has any sign/meaning?
5- Since I have a custom ROM with root (I did installed tens of custom ROMs before with tens of root/unroot) and I didn't suffer a problem, my local stock Samsung firmware yet before MG4, would this be a problem if it's a bootloader issue for them to use JTAG or whatever to copy bootloader information? (Modems after MG4 has another store location for EFS rather than earlier once)
Any tips / feedback would be most appreciated.
Before anyone says "this has been answered a million times" and posts a link, I want to assure you that I have read every single thing I can here on xda before posting.
The current status of my DNA is unknown to me. The device is rooted and has been for quite a while. It is S-OFF and has been for 3 years. The bootloader is UNLOCKED and has been for 3 years. The recovery is TWRP (most recent version for the DNA). The ROM it was running was santod040's GPE ROM for the DNA. It was running that rom for 6 months.
The device had no Sim card in it. It was used primarily as a backup device if I needed it and to play a few gaming apps that I have multiple accounts with (clash of clans). The device was used only on wifi for gaming. No apps were downloaded to the device prior to the device failure. No websites were visited prior to failure. 360 security was on the device as the primary antiviral app.
Symptoms that created current affliction:
None that I know of
Current affliction(s):
Will not power on
PC USB will not recognize (running Windows 10 - HTC Sync is NOT installed on my computer)
Will not hard reset
Will not boot to bootloader
Will not charge on AC power with original HTC charger (led flashes but never goes solid)
Will not charge on AC power with alternative triple shielded cables (led flashes but never goes solid)
Will not charge with any cable via PC USB (led flashes but never goes solid)
Possible remedies to affliction that have been attempted:
Volume down and power button simultaneously - FAILURE
Volume up and power button simultaneously - FAILURE
Both volume up and down with the power button simultaneously - FAILURE
Holding power button to reset manually - FAILURE
ADB - FAILURE
Boot to bootloader - Not possible for the moment
Boot to recovery - Not possible for the moment
Power up - FAILURE
The only thing it does is flash the amber led light when attached to AC or the PC via the charge cables (I have tried many)
Any and all help or solutions to at least get it back to recovery or the bootloader would be appreciated. I have the RUU 1.15 and a stock original backup saved to the PC. If I can get to at least recovery I should be able to sideload or oem lock the device and run the RUU. But for now I can't even get a screen.
Please help in any way you can and I thank you all in advance for any assistance rendered.
I don't know,but i can only assume that the battery is dead. You can buy new battery and try to replace it yourself. I bough battery replacement for my Droid DNA in case something happens from aliexpress : http://www.aliexpress.com/item/orig...rfly-droid-dna-htl21-bl83100/32260653385.html
HTC Droid DNA Battery Replacement Guide: https://www.youtube.com/watch?v=aFCvGcG0dVs
I give just a guess.
it seems, like cirios83 said, battery is "dead", i.e. battery is alive, but it self-locked by controller on very low voltage level.
why?
something makes battery drain. in my case it was unexpectedly died sound chip tf9887. time of replacing take over 1-2 hour in service (if they have an donor).
beffore going to service you can take off a back lid, disconnect the battery and measure resistance of supply chain. it must be close to infinity.
if it is not. you will know at least, that mainboard is in trouble.
this is example of one of many reasons why phone is "dead"
cirios83 said:
I don't know,but i can only assume that the battery is dead. You can buy new battery and try to replace it yourself. I bough battery replacement for my Droid DNA in case something happens from aliexpress : http://www.aliexpress.com/item/orig...rfly-droid-dna-htl21-bl83100/32260653385.html
HTC Droid DNA Battery Replacement Guide: https://www.youtube.com/watch?v=aFCvGcG0dVs
I give just a guess.
Click to expand...
Click to collapse
Since the phone is a uni body design, I have never looked into actually taking it apart. We do have a few places where I live that specialize in repairs and such, but I am not completely sure that the battery is the issue, it had one other problem that developed about a year and a half ago. That problem was the loudspeaker on the back no longer produced sound.
Perhaps there is a loose connection in the hardware itself causing it to no longer function. It's not a pressing matter as I do have another backup device or two. I'm just a little disheartened that it's no longer functioning.
Hi everyone,
I used a month ago my redmi note 4 before the job without worries.
During the morning I wanted to watch something on my phone and no way to turn it on.
Having charged the phone all night, I tell myself that this is not a charging problem.
I tried to restart my phone by pressing the long power button, recovery or fast boot and despite these 3 manipulations there I see only the notification led that lights up red intermittently as the power button is pressed.
I tried to find solutions but no way to find something that would change things.
I used revengeos for a month so it should not come from improper handling.
Can the phone be cracked like that when it worked a month or is it just a fault of the battery? I see only the red notification led when the cable is connected and no sign when it is not.
Battery has been changed and it's the same as before. I've bought an edl to test but no change.
I don't know if I do something wrong but I tested a lot of things found on google search.
Phone isn't recognised correctly in device manager error 43
What do you think of this problem and do you have a solution to offer me?
thank you in advance
Up
Do you know where I can find solutions about this problem?
Thx
Hi folks,
First things first: I know there are a lot of threads concerning the "red light of death" for Huawei and other devices. I already read so many of them that my head is spinning xD However, I have some questions left and I need to distract myself from getting crazy due to the possible loss of data on my phone (and I have to wait at least until Tuesday for any news regarding the phone...)
What happend?
- Phone restarted while surfing
- Went into a bootloop
- Tried a soft reset
- Tried eRecovery --> Not succesfull
At this point I had to leave the train and the phone had turned off anyway. Wanted to charge the phone at the airport and back up recent data. Removed the protective cover and noticed that the battery was bloated. Since I was afraid I unplugged the phone and came to the conclusion that the phone doesn't work due to the defective battery. Back at home I ordered a new battery - didn't help. Phone won't turn on, softboot doesn't work. I only see a solid red LED when I try to charge it. Bought another battery - nothing. Went to a repair shop: This is the point where I start to have questions
They are all very nice at this place and maybe everything will turn out fine but I just can't wrap my head around certain things.
At first they also wanted to check for a defective battery and possible repairing errors since I replaced it myself. Today they called and let me know that the new battery is alright and they now want to order a new screen module. Later today I went to their shop to ask how much everything will cost and also to ask them about the procedure. I asked them why they want to change the display. Answer: Since the battery is fine, we believe the screen cable got damaged when taking out the old battery - its a common issue because the cable is underneath the glued battery. Once the new screen module is ordered there is a good change that it'll work and we can save your data. Note that I don't have to pay for the new screen, since I said that I only want the data back and that I don't need the phone back fully working. So I don't think they suggested it for the sake of making money.
I have indicated that I suspect a hardware problem, but the guy said the motherboard is fine. He continued to explain, that since the red LED is on and the mainboard as well as the battery are fine they assume a problem with the screen.
My questions:
How can they check if the logicboard "is ok" (I asked if they can do micro soldering and since they can't I doubt they can measure the components). Are there easy ways to exclude an hardware error on the board?
Is it possible that the phone doesn't start, vibrate, is not detected by the PC all because of a faulty screen? Any ideas why the LED is visible then?
Doesn't the red solid LED indicate charging? So how come I "charge" while not being plugged in? (LED stays red all the time)
My initial problem wasn't a possibly ruined screen cable/connection but a bloated battery. It just cracked the backcover open but nothing happened to the screen --> Is it possible at all that the bloated battery killed the display module?
If anyone has read this far: It would help me if you speculate with me about the problem, share your experiences or help me in any other way. Somehow I have to pass the time until next week and I'm going insane xD
Thank you so much!
Sydney_