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?
Related
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
This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.
Do not flash thru CWM... Flash a good GB kernel like "franco.Kernel" but thru PC Odin then u can flash whatever u want from franco's CWM... Good luck
Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.
Ce said:
Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.
Click to expand...
Click to collapse
Flat battery? It's also possible that it's just the screen that's not working. Try entering download mode "blind". So hold power+home+vol down for ~10 seconds, then press vol up. Hook it up via usb and see if Odin can recognize it.
Thanks, didn't think of that. But unfortunately no response from the device.
So now that it looks like your phone is officially bricked, I think you should just take it to Samsung and make up a story. Like you were updating your software with Kies and something happened and the phone is just not booting up.
I am sorry you bricked your note though..
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
musashiro said:
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
Click to expand...
Click to collapse
I would like to but it's very hard when you can't see anything on the screen...
Maybe it's just the battery, try to charge it externally and try a JIG also
Sent from my GT-N7000 using XDA
Just a quick, final, update.
My Note was superbricked. Had to send it to a Samsung Service Center. No additional questions were asked. Samsung replaced the mainboard. Didn't have to pay anything.
Great service!!!
try this out buddy, do it on your own risk!!! anyways you have messed it up.
Ce said:
This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.
Click to expand...
Click to collapse
i was not a member when i commited this mistake. but then big thanks to this community it helped me back from softbrick.
first you do is install a stock kernel of ics on your note go into recovery and just clear cache partition, thats it no wipe/data factory reset.
then,
install the pit file from this thread, also read it completely before proceeding. http://forum.xda-developers.com/show....php?t=1667886 , hoping yours is 16gb version and also read this thread for additional info but its quite complicated for me so im just telling you the direct method and hopefully itll get your note back to work. so once you download the 16gb pit file unzip it and in the unzip folder you will find a separately lying pit of 16gb stating patched-standard thats the one you want.
then,
goto samfirmware and download the latest ics firmware(i downloaded the indian one as it is in file .tar),
unzip it till you get .tar file.
open odin- click pit-select 16gb patched standard pit- check wether repartion is ticked- click pda-select the .tar file you extracted connect your phone and start. this time i wont stop at factory.fs.....
NOTE THAT AFTER THIS PROCEDURE IS COMPLETED SUCCESSFULLY YOUR INTERNAL STORAGE WOULD BE ONLY 8GB INSTEAD OF 11 GB STOCK WHICH YOU WERE GETTING.
I REVIVED MY NOTE THROUGH THIS PROCEDURE. PROCEES AT YOUR OWN RISK.
one your phone is working you'll be able to reset the counter with a jig and get your phone under warranty and get your motherboard changed by teliing at the Samsung Service that you are getting only 8gb instead of 11gb you used to get earlier(warranty only if you had any).
hope this helps mate.
BEST OF LUCK!!
A BIG HUGE THANKS TO hg42.....
Edit: Sorry, but after doing battery-out for a while (tried it earlier, but was apparently too stressed), it came back into download mode. So it's not completely dead, and I will try to see if I can get it working again. Sorry for wasting your time and XDAs space!
So, after 2 years of excellent service I replaced my trusty old i9000 with a brand spankin' new i9300. When doing a thorough reset of my phone prior to selling it, it now has died completely on me. Let's walk through this:
-First off, I went into CWM and did all the wipes and formatted internal SD-card. (Was running AOKP 4.0.4.)
-Secondly, put phone into Download mode and used Heimdall on a Mac to repartition and insert completely stock rom. Followed instructions I found here on how to flash using Heimdall, and downloaded a package named I9000XXJVU which I extracted and did everything according to the specifications. Downloaded a 512.pit-file and used as well.
-Thirdly, and lastly, I tried to flash.
This is what Heimdall said:
[quote="Heimdall]Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...[/quote]
Now, the device is COMPLETELY dead. No Download mode, no nothing. So, what the hell did I manage to f**k up now, and how do I solve it? I had only used Odin in Windows before, and has never had a problem like this.
Edit: Sorry, but after doing battery-out for a while (tried it earlier, but was apparently too stressed), it came back into download mode. So it's not completely dead, and I will try to see if I can get it working again. Sorry for wasting your time and XDAs space!
I think u f..... up the bootloader and that's bad.but try USB-jig u can buy it on ebay and are guides on utube how to use it,if the jig works u can get into download mode then it's easy recoverable.
Try pull out battery and leave it out for 30 min,If u are really lucky u can boot into download mode
Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.
re: not bricked
cronos1388 said:
Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.
Click to expand...
Click to collapse
Your phone is NOT bricked. If it was the screen would not even go on.
Have you tried going into recovery mode (VolumeUP/VolDown/PowerButton)
and once in Recovery Mode do a factory reset or Data Reset forgot what the
exact wording is in the stock recovery.
If you flashed twrp recovery it's ok too, just select "factory reset".
After doing that the phone should no longer display anything about Kies.
If you get to the twrp recovery screen you should be able to flash a stock
rooted rom without any issues.
If all you get is the stock recovery screen then you should be able to odin
flash the official Samsung Note 4 kitkat 4.4.4 NJ7 firmware which you may
need to download the firmware from http://SamMobile.com if you don't
already have it. (be sure you have the correct firmware for the Note 4 N910T).
Be 100% sure that the phone is FULLY POWERED DOWN before going
into Download Mode to avoid odin errors and issues.
Good luck!
Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.
cronos1388 said:
Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.
Click to expand...
Click to collapse
Can you check for the file with md5 before you flash from your phone? I forgot where to dig for this info.
All I I have done before is on my cook rom file, I just open it with WinRAR and test for error. If no error, then its good.
On my Home PC I have a program that will put a check mark next to a file if it matches the md5. I also have Winrar at home.
I was just using the default Windows zip program and I have had problems with that and installers/roms in the past.
The only other things I did different were I removed the SD card and installed the drivers before plugging my phone in instead of letting Windows download them automatically.
I also removed the battery after I left work so it was out of the phone for a couple of hours.
The final thing I did was calm down lol after the initial shock of seeing a softbricked screen on my brand new phone.
I'm all rooted now with TWRP and running Hyperdrive so it's all smooth sailing from this point forward.
You should check md5 on phone once you done transferred to phone from PC
BAD ASS NOTE 4
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...