Has my note hardbricked? - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

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)

Related

SGS *Completely* dead

Hello.
I'll get straight to the facts.
I had my phone rooted with Odinv3 using "busybox" (is all i can see on my downloads).
I then went to update to Gingerbread today, but didn't realise I had to un-root the phone!
So this made the phone keep refreshing the samsung galaxy S screen.
I then went to reboot to stock using this thread. Said it passed etc.
Now my phone is completely dead. It won't turn on. Nothing at all when i get it into download mode. No lights turn on. Odin *does* recognise it when I plug it in, the yellow box lights up.
The computer makes a noise to recognise that somethings been plugged in.
But alas nothing on the phone. I've left the battery out and tried it in but nothing.
What can I do please?! I am stuck here. And fear i just have wasted a great sum of money...
Will I be able to take it back on warranty? I haven't had it long, 3 months or so. Would they recognise it has been rooted despite it being put back to stock software.
Thanks. Daniel
You are a bit unclear, can you get download mode with 3 button combo?
Sent from my GT-I9000
tried many times to remove and replace the battery worked for me
sorry for the google translation
I managed to get into download mode by doing a 3 button combo earlier, can't remember what it was but I had to hold three buttons *THEN* fit my battery. THen it went into download mode. I can't remember which combo it was though as i've tried loads before and they didn't work!
It won't do anything now though.
Could i have booted it with a wrong ROM and that's why it won't load?
How come Odin picks it up and it goes through that passing etc?
THis si so annoying.
Volume down/power/home hold til galaxy s logo then release a yellow logo should appear
Sent from my GT-I9000
Sorry for opening an old thread. But i have aproximately the same problem with one exception:
Odin won't regognize my phone.
I was just in the process of installing this rom:
http://forum.xda-developers.com/showthread.php?t=1136449
It got to the first step: "DO NOT POWER OFF DEVICE!!".. and then nothing. Sat there for 15 minutes untill i unplugged it.
shut down the phone using the power button, but now.. its completely dead.
This was offcourse before I realized i had just tried to install a ROM for SGS.. not SGSII.
So.
Odin doesnt recognize the phone.
The phone won't turn on, no matter what I do.
Nothing happens when I try to charge the phone.
I've tried pulling the battery several times, but its just .. dead.
However, when I plug in the battery, the phone seems to get hot. Not very hot, but just slightly above 25 degrees (aprox).
I'm afraid i've f*cked up big time, and have to send it in for a repair..
Anyone have a tip of what I can do ?
(Yes, the battery is charged - not empty).
Have you tried going into download mode again? does the screen power up at all?
My advice is try to leave the battery out for 15-30 minutes, then try getting into Download mode again, with the USB cable already plugged in and ODIN running on your machine.
See if ODIN can detect it and work from there... May be better than nothing. Hope this helps.
kragebein said:
Sorry for opening an old thread. But i have aproximately the same problem with one exception:
Odin won't regognize my phone.
I was just in the process of installing this rom:
http://forum.xda-developers.com/showthread.php?t=1136449
It got to the first step: "DO NOT POWER OFF DEVICE!!".. and then nothing. Sat there for 15 minutes untill i unplugged it.
shut down the phone using the power button, but now.. its completely dead.
I've tried pulling the battery several times, but its just .. dead.
However, when I plug in the battery, the phone seems to get hot. Not very hot, but just slightly above 25 degrees (aprox).
I'm afraid i've f*cked up big time, and have to send it in for a repair..
Anyone have a tip of what I can do ?
(Yes, the battery is charged - not empty).
Click to expand...
Click to collapse
Did you know how to flashing the rom (via CWM) ? You have to notice your battery percentage first.
What exactly were you flashing? CF-root? where did you get it from?
I had the battery out through the night and tried again this morning.. didnt work..
It SEEMS to be completely dead.. (with exception from that the cpu gets hot when battery is plugged in.. )
I tried flashing this:
http://www.multiupload.com/6QNW8P7DTY
I came as far as "Setting PIT file.." "DO NOT TURN OFF" in odin, and then everything stopped.
The battery was at 70% when i started the process.
The phone have only been on for about 20 minutes since.

[HELP] Strange Soft Brick issue

Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
ableeker said:
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
Click to expand...
Click to collapse
You must not have read the whole thing. Not a problem.
The only time I get the Phone ! PC screen is when it's plugged in to the wall. As soon as I unplug it, it goes away and the device won't start up no matter what I try.
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
salahmed said:
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
Click to expand...
Click to collapse
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
MaskedDriver said:
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
Click to expand...
Click to collapse
No dice.. still jacked.
I determined the following scenarios may have happened:
1) The battery died (bad battery) during a software update and messed up the partitions
2) The battery died (bad battery) while he attempted to (unauthorized) root or flash the device, messing up the partitions.
The only thing I'm sure of is the battery is fried so any kind of hacking I can do to the device are for naught. I was able to get it to connect to Odin this morning for about 3 minutes (after having it plugged in to the wall all weekend). During the flash it shut down again bricking it even worse. Now the device won't turn on when plugged in to the wall.
Thanks for the suggestions and help. I'm calling this a lost cause at this point. We're just swapping out the device for a new one. Once that's complete, I may tear the device down and try to do a reset on the main board to see if that does anything, though I doubt that's the case.
Right I had exactly the same problem as you (exactly the same symptoms) but I have now fixed my tablet.
Like you I got to the point where the Tablet had enough charge to actually unplug it and connect it to my PC where I then tried to flash a stock ROM using Odin. About three quarters of the way through flashing the stock ROM the tablet died, disconnected from Odin and I got a message in the task list in Odin advising me that the process had failed. Even weirder my PC did an emergency shut down and restarted in safe mode.
Anyway I tried it again but when I started my machine, once I'd logged onto my desktop I started up Odin as quickly as possibly, selected the .tar file and pressed start as quickly as possible....it worked and my tablet was flashed with a stock ROM. However my battery was still pretty much dead and the first time of charging once it had been flashed with the ROM took about 24hrs plugged in at a mains charger for the battery to reach 100%.
My point is persevere with it and you will fix it. I was at the point where I was about to send it off to be un-bricked but obviously I'm glad I didn't now.
It is a ***** of a brick though, this 'coma brick'.
I've been having these same issue with my friends i800 galaxy tab. Can you chime in and offer some advice?
Sent from my Galaxy Nexus using Tapatalk 2
same problem-solved
I was having the exact same issue. the device screen was completely black when plugged into the computer. I was just about to give up when, all of a sudden the device went to the boot error screen while plugged into my computer. Apparently, it must remain plugged into the computer for about 20-30 minutes. Once this screen appeared, I ran the Heimdall one-click unbrick utility, and like magic, my galaxy tab was working again. Give it a try, and good luck.
MaskedDriver said:
Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
Click to expand...
Click to collapse
I am having this issue with my sch-i800.... phone /!\ pc screen only when plugged into the wall, and no recognition of it on the pc. Any way of fixing it?

[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

[Resolved]Bricked phone or battery problems?

Hello, I'll start with writing all the things i did:
I flashed JenaMIUI v1.29 succesfully then i waited about 30 minutes at the boot image, then I got the battery out, tried again another 10 minutes stuck at the boot image. After that I reflashed JenaMIUI v1.29 wiped data etc...same thing, stuck at boot image, I got the battery out and back in, one time just after turning on the phone ( before the boot image appear). Then I could'nt start the phone in recovery or normal or download mode. After some tries and leaving the phone for a few minutes i managed to start it normally( but still stuck at boot image) , so I wasn't able to get to recovery, one time I managed to power it up with the charger on, it showed a circle 1/4 full and then went to boot image. Now I'm not able to power up the phone at all, I tried getting the battery out and back in several times. When I connect the charger to the phone with no battery in it, it shows a black screen for a second then nothing. I am not able to start it in recovery or any other way. Is this a battery problem or sth like the mother board ? The bin counter is set to 0 (using triange away), can I take it to service ?
One more thing, when i managed to start it normally and was stuck at boot image i pressed all keys(vol up,down,home,power) and went into a black screen saying something with ARM ..idk.
Is this a battery problem or a brick ? What can I do ?
EDIT: I think the problem was caused by pulling out the battery right after powering on the phone, solution...disconnect battery from phone leave it for 10 minutes, hold power button for 30seconds then turn on the phone in download mode and flash stock...that worked for me
Are you stuck on Miui bootanimation?
Now i can't get it to turn on...i tried replacing the battery , but when i press power nothing happens
Edit: I'm pretty sure is battery problems because I pulled out and put in the battery very fast ...
no, never pull out battery while the device is on splash screen. Wait till boot animation at least. In that moment the kernel is being loaded. This is also causing the recovery bug. People get boot-loop and reset their phone by pulling out the battery. It's actually true, it's the same as if you turn off your PC by unplugging it from power cord.
So if the kernel has some problems because i pulled the battery out while it was loading...can I take it to service ? Can they see what ROM I have installed regardless of my 0 bin counter ? Will they give me a new phone or sth ? Will a lie like...I tried to change the grey case with the orange case and the battery fell out while I reseted the phone work ?
EDIT: I managed to "repair" my phone ! I used a method I found on the internet. I hold the power button for 30 seconds ( while the battery was disconnected) and then put the battery in and I managed to get it in download mode and flash stock rom, now everything works great)
Sorry for the inconvenience, i wrongly packed the rom
RageFoxtrot said:
Sorry for the inconvenience, i wrongly packed the rom
Click to expand...
Click to collapse
No problem...i knew the risks I was taking...and as long as everything turned out fine, It's all good.

Note 4 turned off and won't turn back on. Bricked?

I flashed CM 12.1 a while ago and it would sometimes freeze up so I would pull the battery if vol down + power didn't work (which it usually didn't) and then last night it just turned off and never came back on. Sometimes it would boot into download mode and say "failed to do normal boot mmc_read failure" and others it would boot back up no problem. Now I can't get it to boot into Recovery or Download, I've taken the battery out and help down power for a while, then put it back in and help power for a while, tried charging with two cables that both charge my tablet just fine and in two outlets. When I plug the phone into the computer it dings so the PC recognizes a device is being plugged in but it doesn't show up under the file browser. Am I hard bricked? Can I fix it? Should I try to get a new phone?
It's a T-Mobile Note 4 if that helps. I'm still making payments on it but I passed the year mark in February.
shadow105720 said:
I flashed CM 12.1 a while ago and it would sometimes freeze up so I would pull the battery if vol down + power didn't work (which it usually didn't) and then last night it just turned off and never came back on. Sometimes it would boot into download mode and say "failed to do normal boot mmc_read failure" and others it would boot back up no problem. Now I can't get it to boot into Recovery or Download, I've taken the battery out and help down power for a while, then put it back in and help power for a while, tried charging with two cables that both charge my tablet just fine and in two outlets. When I plug the phone into the computer it dings so the PC recognizes a device is being plugged in but it doesn't show up under the file browser. Am I hard bricked? Can I fix it? Should I try to get a new phone?
It's a T-Mobile Note 4 if that helps. I'm still making payments on it but I passed the year mark in February.
Click to expand...
Click to collapse
I looked up that error and there was multiple articles thatvsaid it could be a flash memory error of an EFS problem. Hopefully its something different, as both of those are tricky at best. Its a place to start though.
Install Kies and try the emergency firmware recovery.
Sent from my SM-N910T using Tapatalk

Categories

Resources