[Q] Completely dead N7000. Hardbrick I think. - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi

It is exactly this: just another bricked Note thread.

ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi

Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?

If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.

I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.

nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?

I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.

froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?

AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.

Part of the "hardware" is your battery...

Related

[Q] Bricked Verizon tab, black screen of death after trying to flash stock firmware

Well, I've bricked my three week old Verizon galaxy tab trying to flash the stock firmware back to the device to try and get the recent Verizon update working, which has been failing consistently. I've thoroughly read through every thread on the forum I could about the black screen of death, so I understand there's a good chance I'm pretty screwed here. I have a couple more questions on the subject, but I understand that I might not be able to get answers for them past the information that's already available.
I'll start by describing my setup and how the flashing process went wrong. I was using the stock Verizon ROM with Boushh's Voodoo Plus kernel v3, converted to ext4 of course. After the recent Verizon update failed to install on my Tab I followed through all the suggestions on the CDMA VZW Tab update thread, downloaded the update zip, put it on the sdcard, ran from rescue manager, unrooted, reflashed stock, wiped data and cache, re-ran from rescue manager at first boot... nothing worked. Things went really wrong when I tried flashing the entire ROTO backup of the Verizon stock ROM. I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
* I've seen it suggested that the tab be left to drain for days or weeks, but not many reports that this worked out in the end. My battery was at about 45% percent when this whole thing went down. Should I even bother waiting? My only alternative at this point is to send the thing to Samsung for repairs which breaks my heart. Verizon won't replace it as I've had it for over two weeks.
* Could a homemade USB jig help me in this situation? I have some soldering experience but I heard that it won't help if the screen won't turn on. Ideally I'd buy it online, but I couldn't find one for the Galaxy Tab on ebay.
That's it I guess, but any information you can offer pertaining to this problem would be appreciated. Thanks!
to be honest, i do not know why people think they can brick the tab.......the only way is to throw it from a building.
Just go to overcome forum and follow this (i 'bricked' my tab a 1000 times):
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
1.Get a stock rom package (any of Rotohammer's firmwares will work)
2.Get P1_add_hidden.zip attached to this post and extract the P1_add_hidden.pit file
3.Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
4.Put P1_add_hidden.pit in Pit slot
5.Check repartition box
6.Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
7.After this, the Tab will reboot normally. Shut it down and return to download mode.
you also get the link for the p1 file you need.......easy
This sounds like very useful information, thank you. I'll definitely do this if I can get the Tab to respond to anything I do, which I can't so far. It won't turn on regardless of what volume button I press or not press. I'm pretty sure I had it connected to the PC while trying to put it in download mode just to see if it would be recognized as USB device despite the screen not turning on, but I'll try again to make sure when I get home.
Edit: Yeah, no luck. Not recognized as a USB device, which makes sense seeing as the screen doesn't even turn on.
I am having the same issue... My daughter put my computer to sleep while I was flashing back to stock using heimdall. Any luck getting your Tab to power on?
nirslsk said:
I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
Click to expand...
Click to collapse
same problem
If your tab is showing any sign of life then you are not bricked and just need to keep at it until you find a solution. When you have exhausted all other resources you can send it off to get it fixed. I ended up bricking my tab when a flash was interrupted to the point that there was no sign of life at all. I found someone here who could fix it for $50 and had it back within the week working as it should. I highly recommend his service as a last resort.
His screen name is connexion2005 and here is a link to his profile.
http://forum.xda-developers.com/member.php?u=1602851

[Q] Build 1012: Which ODIN to use?

I'm on a warranty exchanged 1012 build Captivate. I initially decided to go ahead and flash a new ROM to it, and proceeded to do so using Odin 1-click like I had done so many times in the past with my old 1008 build Captivate. Odin hung for quite some time, and I feared the USB cable I was using was faulty to a certain degree. No biggie, just restart the process and all would be good.
That wasn't the case here though. It simply doesn't boot anymore. I believe it to be a soft brick as there is an image available on the screen. It's the wretched cellphone --- computer screen. I attempted to reboot into download mode like I had done using the VOL+/VOL- and USB insert method, but all that appeared was this symbol. I was simply trying to restore to stock 2.1, as this Captivate came with stock 2.2.
I've even built a JIG, a couple actually, using varying resistors. The first JIG I built before attempting the ODIN flash that killed my phone. Prior to flashing ODIN, the JIG appeared to work brilliantly. It put my phone into download mode about two seconds after contact. Now all it does is bring up that damn cellphone --- computer screen.
What is strange is that the phone, when plugged into the computer after I attempt to put it into download mode using my JIG(s), the computer will play that sound that it plays when it recognizes a USB device. In addition to that, if I plug it in when ODIN is open, ODIN recognizes the phone and displays a yellow block with "0:[COM11]" in it.
I went ahead and downloaded the necessary things from this thread:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
and began trying to flash to stock using his instructions. So far ODIN appears to be running, but is stuck at modem.bin.
Maybe its not making any progress at all, but I'd like to hope so. Does anyone know if the 1012 batch can get into download mode using a method outside of the normal key presses and JIGs? Any recommendations for me to revive this Captivate? I did enjoy the fact that it didn't shut down on me every 30 minutes. The GPS still sucked on it though. But I need to bring it back to life, just don't know what other options there are. As far as I know, if the screen presents you with an image of any sorts, its just a soft brick and CAN be recovered.
Can't use one click with your build number. You would need to use full odin. There are numerous articles here on how to do that.
mrhaley30705 said:
Can't use one click with your build number. You would need to use full odin. There are numerous articles here on how to do that.
Click to expand...
Click to collapse
Yeah, found out the hard way. I do wish there was a stickied post that broke down the build numbers and the various caveats of each build number, including tried and proven methods of restoring to stock and other things.
My situation was quite strange, as ODIN appeared to recognize the phone even though it only displayed the "cellphone --- computer" icon. I'm wondering if the failed flash screwed up the download mode graphic and replaced it with the "cellphone --- computer" graphic? Either way, it didn't "appear" to actually be in download mode, it was.
That screen only means that a flash was incomplete. Flashing anything even a modem successfully will get rid of that screen, granted your kernel/rom was broken so it wouldn't have booted properly but that screen would've went away, replaced by a bootloop. so to fix it completely to an up and running state an entire rom package is needed. Like you used.
Just informing you that, that screen isn't the **** your pants moment. that time comes when the phones does absolutely nothing, as long as there is ANYTHING you are 99% of the time ok. That 1% is when your usb port on the phone is broken, or your pc drivers just all of a sudden decide to extend their arms and give you the figner, or you try odin again with the same faulty connection that gave you the bad connection/incomplete flash and that time it hangs on the bootloaders and bricks it.
Odin recognizes my phone in all modes except completely off: booted, recovery, download and I just tested the phone...!...pc screen on purpose by yanking the chord during a kernel flash got that screen of coarse cause the flash was incomplete. But unless the phone is in download mode it doesn't initiate download protocol and odin will hang on setting up connection.
You can't really have a guide line for what works on what builds for any certainty because every phone of a certain build doesn't behave the same way.
I have 3 captivates I flash. 1, a 1010, and 2 are 1012s all of them have no issue whatsoever with odin one click. It's just the luck of the draw...
I recently had this EXACT issue. The way i fixed it was building a jig out of 3 100k 1/4w resistors and forcing my phone into download mode.
Studacris helped me out there!
if your still having issues, its http://forum.xda-developers.com/showthread.php?t=1079000
I also just went through this. I just had to keep trying. The jig is what saved me.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Completely unresponsive.

Alright, so the title may say a similar problem a lot of people have with the Note 4. But my situation is different. Unlike the problems of boot loop, button response, and other issues, my phone is completely wiped. I tried everything. Battery removal, charging, buttons, every mode pattern, etc. No response... at all.
I looked everywhere, I googled different word phrasings to hopefully find someone with the same issue... sadly, I didn't.
Here's what happened:
I got the Note 4, tried updating it. Idiot me didn't think of updating on my computer, not on my phone, but I did on the note anyways. I tried updating and it went into download mode, and in the top left, it says stuff like "can't do normal boot" "mmc read failed" stuff like that. Now I read somewhere that it was a corrupted firmware and should be replaced. I know the problem, but I can't do anything.
Is this a hard brick?
KoreanJoker said:
Alright, so the title may say a similar problem a lot of people have with the Note 4. But my situation is different. Unlike the problems of boot loop, button response, and other issues, my phone is completely wiped. I tried everything. Battery removal, charging, buttons, every mode pattern, etc. No response... at all.
I looked everywhere, I googled different word phrasings to hopefully find someone with the same issue... sadly, I didn't.
Here's what happened:
I got the Note 4, tried updating it. Idiot me didn't think of updating on my computer, not on my phone, but I did on the note anyways. I tried updating and it went into download mode, and in the top left, it says stuff like "can't do normal boot" "mmc read failed" stuff like that. Now I read somewhere that it was a corrupted firmware and should be replaced. I know the problem, but I can't do anything.
Is this a hard brick?
Click to expand...
Click to collapse
If you able go to download mode then flash stock firmware via odin.
Or use kies...
Trex888 said:
If you able go to download mode then flash stock firmware via odin.
Click to expand...
Click to collapse
I tried to. I somehow got it to the download screen. I tried flashing the firmware. Said I was missing pit partition. So i grabbed one and tried again. I don't have a pit binary, and that's beyond my knowledge...
sloanster said:
Or use kies...
Click to expand...
Click to collapse
Tried Kies, it said it didn't recognize my phone. It's seen on the cpu as QHSUSB_BULK or something
check this thread out http://forum.xda-developers.com/note-4-tmobile/help/galaxy-note-4-n910t-fixed-hard-bricked-t3466547
I had an issue where my phone was totally unresponsive. no charging light, wouldnt turn on, couldnt even get to download mode and the 2nd debrick image worked for me. The whole process seemed like voodoo but it worked. Also the PIT file is there if you need just that.
If you are having that QHSUSB_BULK issue check this one out... here
JHaste said:
check this thread out http://forum.xda-developers.com/note-4-tmobile/help/galaxy-note-4-n910t-fixed-hard-bricked-t3466547
I had an issue where my phone was totally unresponsive. no charging light, wouldnt turn on, couldnt even get to download mode and the 2nd debrick image worked for me. The whole process seemed like voodoo but it worked. Also the PIT file is there if you need just that.
If you are having that QHSUSB_BULK issue check this one out... here
Click to expand...
Click to collapse
I would love to try this, but I don't have another note 4 to get a backup image from? Know anyone who has that to share? It's pretty personal hahaha
I don't know if this will help, but when I try to get it to recovery mode, it goes to an android with "installing system update." Issue is, I'm pretty sure the update download is broken. Is there something I could do there to fix it?
Thank you all for your suggestions... but it fixed itself? It was hard bricked, KIES wasn't picking it up, Odin couldn't flash it, mmc_read fail, no recovery, etc.... and now it's better? Thoughts?

Sudden Death GS3 I9305T

I am having a sudden sudden death problem on my device, but in my research I only knew a solution for the I9300 model through a XXELLA bootloader for android JB, and I did not find anything related to this for my device.
I wonder if you also have a solution to the problem on this device that I have.
Someone to help me?:crying:
Oshmar said:
I am having a sudden sudden death problem on my device, but in my research I only knew a solution for the I9300 model through a XXELLA bootloader for android JB, and I did not find anything related to this for my device.
I wonder if you also have a solution to the problem on this device that I have.
Someone to help me?:crying:
Click to expand...
Click to collapse
Can you specify what exactly do you mean by "Death"?
Does the phone boot into download mode or recovery mode?
Does it make anything when it's connected to charger?
The device stops in the logo, it simply does not initialize, it goes into normal download mode, but even after the process of installing the rom (numerous attempts) it initializes, but after 2 minutes it goes back to the dead state, ie, And stuck in the logo.
Oshmar said:
The device stops in the logo, it simply does not initialize, it goes into normal download mode, but even after the process of installing the rom (numerous attempts) it initializes, but after 2 minutes it goes back to the dead state, ie, And stuck in the logo.
Click to expand...
Click to collapse
Stuck at what logo, splash screen logo or boot animation logo?
Well, i suggest u to flash back to tock rom using odin and start again from there.. U might want to repartition you phone too. to repartition, pit file is required, google it and you'll find one.. Good luck.
Oshmar said:
The device stops in the logo, it simply does not initialize, it goes into normal download mode, but even after the process of installing the rom (numerous attempts) it initializes, but after 2 minutes it goes back to the dead state, ie, And stuck in the logo.
Click to expand...
Click to collapse
If Odin fails to flash the stock rom, try flashing with another version of Odin like v3.07 or v3.09, and try other cable and other USB Port, also try flashing the stock rom with a pit ONLY if the error in Odin's log is related to repartitioning.
MigoMujahid said:
If Odin fails to flash the stock rom, try flashing with another version of Odin like v3.07 or v3.09, and try other cable and other USB Port, also try flashing the stock rom with a pit ONLY if the error in Odin's log is related to repartitioning.
Click to expand...
Click to collapse
Just what I did, flashing in other versions, for version v3.09 the installation was successful, however when starting to configure account, wifi and etc. Restart by yourself and freeze the logo again.
This is very strange because there is no malfunction in the device, the card is intact. I believe that version 4.1.2 is the most appropriate for this device, since I have seen many reports of people warning not to upgrade to 4.4 because of this problem.
But now it does not make any difference, I'm going to trade it for an Optimus G touch that I really needed to get LG to work.
Oshmar said:
Just what I did, flashing in other versions, for version v3.09 the installation was successful, however when starting to configure account, wifi and etc. Restart by yourself and freeze the logo again.
This is very strange because there is no malfunction in the device, the card is intact. I believe that version 4.1.2 is the most appropriate for this device, since I have seen many reports of people warning not to upgrade to 4.4 because of this problem.
But now it does not make any difference, I'm going to trade it for an Optimus G touch that I really needed to get LG to work.
Click to expand...
Click to collapse
It might be a hardware issue, don't you think?
Coming from Samsung for being anything ... this device was stopped a long time, only took it to use a month and a half, I left Samsung a long time, I had hardware problem years ago with two devices of the brand, S4 GT-i9505 - GT-i9500, since then never again, more like my LG E977 is only with the touch screen failing, I found a service shop with interest in this GS3 and I will exchange it for the touch screen of the E977.

Note can't be flashed by Odin

Once upon a time my Note stopped booting (was on a custom ROM, can't easily recall which - but it had been working okay for quite a while). I didn't worry too much about it, because I already had a new phone - so I just put the Note away in the closet saying to myself, when I find some time I'll flash to stock and take it from there.
Fast forward a couple of years, and my no longer new phone has failed (bricked itself for no good reason), so I reach for the Note, download an official Samsung ROM and fire up Odin. Phone's in download mode, Odin sees it as it should, so I proceed to flash. Odin hangs on "nand write start" and does nothing at all for 20 minutes or so.
Then I remembered that years ago I had repartitioned the Note's NAND for better storage usage, so I found a stock PIT file and told Odin to repartition before flashing. Same result.
So the TL;DR: download mode works, neither ROM nor recovery boots, Odin recognizes the phone in download mode (sometimes), but can't flash (just hangs). Any suggestions?
Hi,
I have the same problem, any progress for you?
/RR
svpan said:
Hi,
I have the same problem, any progress for you?
/RR
Click to expand...
Click to collapse
No progress at all. Had other stuff to do. It would be fun to revive this old toy though. But I'm short of ideas. I guess that with d/l mode working, but unable to flash, the NAND storage is probably toast? That wouldn't be fixable?

Categories

Resources