[Q] Low batt, Bricked - Official ICS - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi guys,
My note recently decided to brick on me recently and i have no idea how it happened.
I had superuser on GB before i updated to official ICS through the samsung app on the phone. Everything is stock ICS and nothing has been modified.
It happened right after my phone went low batt, the phone went to critical mode and i turned it off for about 2 hours. When I turned it on it was stuck on the "Samsung GT N7000" screen for about 5mins, decided to pull the battery out and it wouldn't turn on since.
I have disconnected the battery, waited a few minutes and inserted a different charged battery and still no go. I have tried just charging it for about 4 hours and nothing aswell. Also tried booting by power + vol up+down and power + vol up + home. I cant get it to recovery mode.
Any clue if this is fixable? Or should i just go ahead with the warranty?

Related

[Q] Help Please - Battery ran out...phone keeps restarting even in download mode.

Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Keep it plugged in for a few hours and see if this fixes it.
I have quite the same issue with my SGS i9000. Im running on slim bean 4.1.2 i think and semaphore (quessing the same as above)
So the battery got drained to zero. I charged the battery to full capacity while my phone was turned off. It did this okay and charged battery to 100%. Then i booted my phone only to find out it to start looping in boot. (Start screen to semaphore and then restarts.)
i removed the battery for about an hour, and rebooted the phone but it didn't help at all.
Can't get into recovery (vol up + home + power), though it did go into download mode.
snapper.fishes Keep it plugged in for a few hours and see if this fixes it.
Click to expand...
Click to collapse
As i plugged my phone in in to charger it shows as the battery would be empty,but it doesn't begin to charge it.
Ill be happy to answer if i forgot to mention something important according this matter.
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
ill try that.
Thanks for the quick answer. Now lets see if that helps..
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
jwpil said:
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
Click to expand...
Click to collapse
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
I also can't enter recovery, doesn't have time to boot that far. If it is like mine then you will be unable to stay in download mode for long enough to flash anything...if you can get to download and it not reboot again, you have some hope. You could possibly flash a different kernel via odin, semaphore possibly, and see if that helps, but if not you would have to flash back to stock and re-root etc (data will be lost). I will report back when i get a new battery and see if that is the issue (Friday Hopefully), I feel it might be battery issue because my ROM had been running perfectly for days and it started when i let battery completely discharge.
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
Flashing will only delete app data. All your photos and music files will remain.
Just an update... Battery hasn't arrived yet due to snow here. But just by chance I left the phone bootlooping without charger in and it randomly decided to not bootloop. Was able to flash stock with odin root, upgrade to CM 10.1 and restore my nandroid. Oh well.
Sent from my GT-I9000 using xda premium
jwpil said:
Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Click to expand...
Click to collapse
[SOLVED]
I recovered my Galaxy Y(s5360) by flashing another kernel from recovery mode in those few seconds for which recovery mode was starting...
I tried that but got soft brick, not enough time to flash kernel image. My power button is now broken so I feel that it may have been stuck in the on position. Think it's stuck in off now. Oh well
Sent from my GT-I9000 using xda premium
Hi I have the same problem on my Asus tf101 the battery ran out during upgrade and now it is looping on Asus title screen pls help me

stuck on M logo + green led after hard reset

RAZR I on ICS (rooted in November last year, and not messed about with anything else since then)
- yesterday battery went down very quickly from 60% to 5% within 3-4 hours (i took maybe 5-6 photos during that time, no phone calls or internet use)
- annoyed with battery drain i decided to reboot it, thinking that something is not right...
- phone will not boot now, stuck on M logo.
- tried to hard reset (power + vol down for 10 sec), it will reset, screen is black and green led in on constantly, led goes off if i put it on charge, but nothing else is happening, green led comes on again if i switch off charger.
- if i hard reset it again from this state holding power and vol down again fo 10 seconds, green led switches off
- can't access boot menu to do full wipe
Anybody had similar symptoms and managed to get it going?
If no easy solution then i suppose i will have to send it back on warranty..
Regards
Seb
I happened jelly bean but put it off to charge your cell if you press vol + and load on to show the logo release the power along down the vol +
Sent from my XT890 using xda premium

[Q] Help with Xperia T - Can't Boot

Hello and how are you?
I recently flashed the latest doomkernel on my phone, installed a rom and all was working fine. However my batter dropped to 0% and now the phone is not booting up. I had it charged for 10 hours (twice) and when I press power button the red light flashes twice. I was not able to imitate a battery removal (power+vol up) so I removed the battery itself, waited and recharged. The phone is detected as a USB device by the pc, but I cannot flash anything since it turns off.
My carrier says this is a broken motherboard/mainboard
Has anyone experienced such issue? any help?
Mainboard is fine. Battery has to low voltage. I think the device cannot charge the battery, when it's turned off. You must charge the battery somewhere else.

Has my note hardbricked?

Yesterday i was recording video on my note, and when i stopped recording, it got stuck on the screen. after waiting for some time, i had to hard reset my phone. I pressed the power button for a few seconds and phone shut down. But it refused to start up,however hard i have tried. I tried booting to recovery and download mode....but still nothing happened. It refused to enter recovery or download mode...:crying:
I got home and tried to connect to my pc, nothing hapened. I tried charging it, but no signs of charging. Tried ADB, couldnt recognize my device...
I was on Aylum 4.4.1(6 DEC nightly) using herna's kernel and rooted using SuperSU 1.80. No extra mods installed. Was running fluidly for 2 days...no freezes,etc. And suddenly died....
Please guys help me out. Is my note bricked?
Try removing the battery and waiting 10 minutes. After that then put the battery back in and try to boot it up. If that doesn't work then try a different battery in your phone or try to recharge you current battery through a recharger (you can buy them on ebay)

[Q] Help! Incredible s not booting

So, here's the whole story. My phone's display cracked after it fell. But everything was working normally and the touch response was as good as ever. Being the grade A procrastinator that i am, i used the phone for a few weeks delaying taking it to service. One day the phone charged out. I charged it fully but it wouldn't turn on(but it used to vibrate on pressing the power button like it usually does when switching on). I took out the battery and switched it on again...i did this for about 10 times when it powered on. I continued using it when again one fateful day it charged out overnight (i forgot to charge it when battery was less than 10%). It wouldn't turn on again even after taking out the battery and switching on... for like a 50 times. Then i booted into recovery by pressing vol down and power and then after 10 seconds again pressing vol down then enter(since recovery is the second option in hboot). So, now i'm perplexed..was it the display that's not working?..and then it booted into recovery and the display was perfect. I performed a clean wipe and re-installed the rom that i had been using(Vivokat). The problem persisted. Why is the display working only when the phone is booted into recovery?? Then i decided to unroot the phone and then installed the stock ruu..now as you know the recovery is stock HTC's..i can't boot even into recovery. any suggestions?

Categories

Resources