Need Urgent Help!! - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi to all.
I have been a Galaxy Note user for about a month.
Tried out lots of different custom firmwares. Moved from one to another many times.
Today I was on a Stock LQ3 ICS Rom I rooted using the cwm.zip and cwmsuper somthing.zip file.
All was fine and I wanted to give Paranoid another try.
I didn't install the franco kernel which the download package came with, instead I had my stock Kernel running.
Booted into recovery and installed CWM.zip update to gain the recovery menu.
Got the recovery menu which looked like the Abysskernel recovery menu.
Then I did the Factory reset/wipe? and then it was doing somthing then it got stuck!!!
Thats it from then I cant install recover anything.
I can still access the Dowload mode. But it wont let me Download the stock firmware to the phone. It gets stuck at factoryfs.img.
This is the log from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000XXLB2_N7000CPWLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img

Why on earth did you wipe data on the stock kernel??
You are super-bricked.
Next time, you will learn to read, read, read! There's stickies for a reason.

Wow thanks.
Any way of getting around it?
I didn't read it anywhere that you weren't supposed to wipe on stock kernel.
I've done a wipe on stick before.
One of the guid by rootgalaxynote actually tell you do a wipe after you've gone to stock.
So I thought wiping it on stock was fine.

langsalang said:
Wow thanks.
Any way of getting around it?
I didn't read it anywhere that you weren't supposed to wipe on stock kernel.
I've done a wipe on stick before.
One of the guid by rootgalaxynote actually tell you do a wipe after you've gone to stock.
So I thought wiping it on stock was fine.
Click to expand...
Click to collapse
The stock ICS kernels use MMC_Cap_Erase command. Basically, in a nutshell, this command causes the firmware in MOST Notes to mess up the eMMc chip, aka brick the phone.
There is a thread in the General section that someone has made a workaround that MAY revive your phone, but it is only partial and probably won't run good. Your only real choice is to take your phone to a Samsung service center and get the motherboard replaced. Your warranty may or may not cover it.
Question:
Do you have a triangle on your screen (on the Galaxy Note boot screen)? This voids the warranty. You said you could get into PC Odin but it fails at factoryfs.img. Did you try multiple times? Some bricks won't come on at all and some do this, but I'm just making sure you didn't only try once. Sorry.

Thanks for your quik detailed reply.
At first I didn't have the triangle but I installed the abyss kernel (because I doing everything to try and revive it) so triangle was back.
Then I googled and found this guy who had found a way around.
He repatitioned it somehow and made it work?
I don't understand the the technical details.
Any ways sort of followed this persons guid and he didn't link it very well
So I did it half correct. Without using this special kernel.
At the phone didn't respond to anything.
So I turned it off and now phone is completely dead.
Lol
That's all I can do. Lol
It's dead. Black screen. Nothing. :'(
Well at least it doesn't show that I hacked it (I guess?) no triangle.
I'll try the place where I bought the phone.
If not I'll take to my insurence and tell them that my computer failed while I was updating the phone. First option will cost nothing. Second Orion will cost me £50 and in the mean time, gotta use iPhone.
Thanks again. I now understand what I did wrong.

langsalang said:
Thanks for your quik detailed reply.
At first I didn't have the triangle but I installed the abyss kernel (because I doing everything to try and revive it) so triangle was back.
Then I googled and found this guy who had found a way around.
He repatitioned it somehow and made it work?
I don't understand the the technical details.
Any ways sort of followed this persons guid and he didn't link it very well
So I did it half correct. Without using this special kernel.
At the phone didn't respond to anything.
So I turned it off and now phone is completely dead.
Lol
That's all I can do. Lol
It's dead. Black screen. Nothing. :'(
Well at least it doesn't show that I hacked it (I guess?) no triangle.
I'll try the place where I bought the phone.
If not I'll take to my insurence and tell them that my computer failed while I was updating the phone. First option will cost nothing. Second Orion will cost me £50 and in the mean time, gotta use iPhone.
Thanks again. I now understand what I did wrong.
Click to expand...
Click to collapse
I think you were trying what I told you about with the repartitioning.
But, it was probably really good that you fried it completely now so they can't tell. Good luck.
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Hey how about hitting the "Thanks" button too, please?

So,one more again,one more again who suffered by eMMC bug by not read through the whole information provided in stickies.
Anybody wish to try something not to be provided by the official,then must always prepare yourself for those hot disclaimers said,OK?
andreww88 said:
I think you were trying what I told you about with the repartitioning.
But, it was probably really good that you fried it completely now so they can't tell. Good luck.
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Hey how about hitting the "Thanks" button too, please?
Click to expand...
Click to collapse
I think that he will even blame/scold right now,instead of thanks.

Related

Galaxy Tab Bricked - Gingerbread update - help please

I am hoping that I have not killed my new Galaxy Tab.
I was following the overcome rom procedure to the letter. Now my tab will not turn on - blank screen and no sign of life - and odin does not see it. This is exactly what happened:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> cache.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
Is there any hope? Do I just try to return it?
So far 40 reads and no replies. I gather it is hopeless. My computer does not see the GT and neither does, of course, Odin.
Have you tried putting it back into download mode again and reflashing
Sent from my GT-P1000 using XDA Premium App
Thank you for replying. Yes, I have tried to reenter download mode. The Tab will not respond to anything I have tried. It is like a "brick."
Sorry i cant be of any help
Sent from my GT-P1000 using XDA Premium App
Have you tried to enter cmw (hold volume up + power on) If you enter it perform a cache wipe and a dalvik wipe and a factory reset
<ID:0/004> dbdata.rfs
<ID:0/004> Set PIT file..
sorry but but its look that u bricked ur tab by your own-self
can u tell me what u put in odin ????
This happen to my tab when i tried to upgrade it. Use odin v1.7 then try to do it again
k0sh said:
<ID:0/004> dbdata.rfs
<ID:0/004> Set PIT file..
sorry but but its look that u bricked ur tab by your own-self
can u tell me what u put in odin ????
Click to expand...
Click to collapse
Thank you for replying.
Yes, I can.
I used gt- p1000_mr.pit.
My source was http://androidfc.com/tips-tricks/in...read-2-3-3-for-samsung-galaxy-tab-7-gsm-only/
older geek said:
Thank you for replying.
Yes, I can.
I used gt- p1000_mr.pit.
My source was http://androidfc.com/tips-tricks/in...read-2-3-3-for-samsung-galaxy-tab-7-gsm-only/
Click to expand...
Click to collapse
dude i want u to tell me what u did exactly i don't wanna read ..
pls tell me what u put in odin and how many times u used it for this installation
k0sh said:
dude i want u to tell me what u did exactly i don't wanna read ..
pls tell me what u put in odin and how many times u used it for this installation
Click to expand...
Click to collapse
Sure.
1. Rooted using SuperOneClick v1.9.1 - worked like a charm.
2. Enabled non-market apps using SuperOneClick v1.9.1 - also worked like a charm
3. Installed SGT-Bootloader-Patch-v1.00.apk and verified bootloaders were fine (status okay)
4. Backed up to SD Drive some apps - Titanium Backup
5. Ran Odin 1.7 in download mode
- set to repartition automatically
- Pressed “PIT” button and selected: gt- p1000_mr.pit
- Pressed “PDA” button and selected: GB_Stock_Safe_v1.tar
- Pressed "Phone" button and selected “JK3 Modem - modem.bin“
locked up for hour first time, reran once when screen above appeared and GT died
Thanks again
How much battery life did the Tab have when you started this process?
Flashing is VERY battery intensive, and if you left it for an hour afterwards, then tried again... that could easily be 30-40% of your battery. If you started with less than 50% there is a good chance you allowed the battery to die during the flashing process. IF that is the case, than yes, it's hard bricked and need's jtagging.
Lucky you, connexion2005 is unbricking a lot of devices these days.... Send him a PM and see if he can't fix it for you.
I also just realized he lives in the same state as me.... HONEYCOMB TESTER HERE!
btyork said:
How much battery life did the Tab have when you started this process?
...
I also just realized he lives in the same state as me.... HONEYCOMB TESTER HERE!
Click to expand...
Click to collapse
Thank you for the help.
If you connect it to pc with no reaction. connect it to the charger, if you saw the pc and decice logo with the yellow exlamnation mark. Then the only way to fix it is through Samsung repair center. Don't worry most probably they will diagnose it as mainboard failure and swap it for you.
Next time, check your bootloader then flash it once, twice, if still did not work try to search over the net, before keeping flashing flashing flashing flashing flashing flashing flashing flashing flashing
Sent from my GT-P1000 using XDA App
solo13 said:
If you connect it to pc with no reaction. connect it to the charger, if you saw the pc and decice logo with the yellow exlamnation mark. Then the only way to fix it is through Samsung repair center. Don't worry most probably they will diagnose it as mainboard failure and swap it for you.
Next time, check your bootloader then flash it once, twice, if still did not work try to search over the net, before keeping flashing flashing flashing flashing flashing flashing flashing flashing flashing
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Thanks.
Assuming I am brave or an idiot (or as is most likely both), is the process I used correct? If I make sure the phone is charged after each step will it work, or is there something else I missed or should do?
I make no guarantees, but yes, your process looks good. Verify the modem is correct and that SHOULD be ok.
No need to charge each step, just make sure you are at 100 when you start and don't leave it alone till it is done.
Sent from my "better than an iPad" tab... Running Overcome GINGERBREAD!!!
Quoting Darkpal:
"THE GB bootloaders are signed yes but are not secured and they are needed for GB to boot making that patch pointless since kernels and mods can be installed whether bootloaders are signed or not"
I think the fact that you patched the bootloader has something to do with the issue you are facing. I think you downgraded the bootloader which is risky.
It's my opinion, not too sure though.
As many people advised here, try to charge the tab for a couple of hours and see if there is any change.
Question: Did you notice any horizontal lines in the tab? (white, green, blue, red...etc)
tupo05 said:
Quoting Darkpal:
"THE GB bootloaders are signed yes but are not secured and they are needed for GB to boot making that patch pointless since kernels and mods can be installed whether bootloaders are signed or not"
I think the fact that you patched the bootloader has something to do with the issue you are facing. I think you downgraded the bootloader which is risky.
It's my opinion, not too sure though.
As many people advised here, try to charge the tab for a couple of hours and see if there is any change.
Question: Did you notice any horizontal lines in the tab? (white, green, blue, red...etc)
Click to expand...
Click to collapse
First, I want to thank you and everyone else who has responded. I may still have a brick, but at least I do not feel as alone.
Second, you may be right about the patch. It is the only thing I did that is different than many other people. That should not have been the case though, as the patch was supposed to report a problem - not make one.
Third, I am tempted to wait for Kies to bring us gingerbread and hex edit this so I can use it as a phone. Seems safer, no?
older geek said:
First, I want to thank you and everyone else who has responded. I may still have a brick, but at least I do not feel as alone.
Second, you may be right about the patch. It is the only thing I did that is different than many other people. That should not have been the case though, as the patch was supposed to report a problem - not make one.
Third, I am tempted to wait for Kies to bring us gingerbread and hex edit this so I can use it as a phone. Seems safer, no?
Click to expand...
Click to collapse
What happened when you charged your tab? Still not recognized by ODIN?
What about the download mode?
SGT Running Overcome 2.0.0 RC1
tupo05 said:
What happened when you charged your tab? Still not recognized by ODIN?
What about the download mode?
SGT Running Overcome 2.0.0 RC1
Click to expand...
Click to collapse
Charging did change a thing. The GT would not turn on, would not go to download mode, was not recognized by the desktop computer or a new laptop and could not be placed in download mode: a true brick.
Because the device was a few weeks old, Samsung is going to replace. I will still need to figure out how to use as a phone.

Help me please!! NAND no WRITE!!

Please who can help me?
I installed the new rom ICS German, but when I tried to return to gingerbeard ODIN PC I get stuck at the following error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLC1_CL1003701_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.img
PLESEE my phone now not working
Does recovery still work for you?
Had the same similar problem when I flashed ICS with a friend of mine a few days ago. Been trying to find out how to fix the phone for a day and a half. Tryed to flash LA6 stockrom and a few other stockroms. But also kept hanging at factoryfs.img everytime. We also weren't able to get into recovery mode anymore, only download mode.
Last night my friend succeeded in getting recovery back operational again by flashing a file via Odin. Still haven't fixed the phone yet, but at least with recovery we'll stand a better chance I think.
So let me know if you still have recovery or not. If not, then I'll try uploading the file that he used to get recovery back for his N7000. At least that way you can try a factory reset or something like that. I'm not sure if I can upload something since that I'm still new here.
All with all, good luck.
Yes i have recovery
buy when i want install a room with install to zip.. not working grrr
did you flashed CF LPY kernel before?
thehackersz said:
did you flashed CF LPY kernel before?
Click to expand...
Click to collapse
yes if you want i can ...
edt: sorry ... i have bad english
I had it
_giggino_ said:
Yes i have recovery
buy when i want install a room with install to zip.. not working grrr
Click to expand...
Click to collapse
Same here.
Have you tryed a factory reset?
I've tryed it, but when I do it just hangs. Another friend of mine recommended me to wipe/format everything except "System".
Haven't tryed this yet though, so I'm not sure what will happen.
I will let you know the outcome later today.
i'm sure you did a cwm wipe while on LPY and now wants to go back to GB?
if so.... sorry to tell you are now a member of the "superbrick club".
when will people learn to read? it's NOT SAFE to do CWM wipe on LPY. DO NOT BELIEVE what others say "it's fine in my case, did it a hundred times". they are simply yanking your chains and they wait until somebody posts a new thread (like this) and off they go snickering in the darkness.
HAXTC said:
Same here.
Have you tryed a factory reset?
I've tryed it, but when I do it just hangs. Another friend of mine recommended me to wipe/format everything except "System".
Haven't tryed this yet though, so I'm not sure what will happen.
I will let you know the outcome later today.
Click to expand...
Click to collapse
ok i wait you.. but in the meantime I continue to seek a solution ...
_giggino_ said:
ok i wait you.. but in the meantime I continue to seek a solution ...
Click to expand...
Click to collapse
Be very careful, you don't have much trial & error room left. Let the next step be spot on and only do so if you are 100% sure. It's better to wait a few days for a good answer than hurry and end up with a brick. I had the exact same problem but the more possible solutions I tried the more the problems increased and since yesterday my Phone is officially a "brick". Because I've tried so much options I no longer can tell the difference what possibilities are OK and what are NOT OK. Lots of succes.
---------- Post added at 03:09 PM ---------- Previous post was at 03:02 PM ----------
praetorius said:
if so.... sorry to tell you are now a member of the "superbrick club".
when will people learn to read?
Click to expand...
Click to collapse
For a lot of "superbrick club members", including me, the problems started/harm was done when even the specialists on this forum were not completely sure what the cause of the problem was and what to do and what not. A few days ago reading threads didn't give consistent answers....that was also part of the problem. Mind you...I don't blame anyone but myself.
This happened before with Angelom's kernel and now again-
PC Odin stuck at Factoryfs.img== SUPERBRICK.
If you have a superbrick, you have kernel/download mode but you CANNOT write to certain blocks of memory card, so its a MOBO replacement!
Sorry guys!
when I tried to install another recovery I went out this screen
photo
anilisanil said:
This happened before with Angelom's kernel and now again-
PC Odin stuck at Factoryfs.img== SUPERBRICK.
If you have a superbrick, you have kernel/download mode but you CANNOT write to certain blocks of memory card, so its a MOBO replacement!
Sorry guys!
Click to expand...
Click to collapse
+1 totally agreed. At least in this thread there are no clueless naysayers that keep arguing that this case is recoverable.
Try to wipe it again but not in CWM but in stock recovery.
_giggino_ said:
when I tried to install another recovery I went out this screen
photo
Click to expand...
Click to collapse
who can help me?
Please i do not want to believe the brick
SquirtingCherry said:
Try to wipe it again but not in CWM but in stock recovery.
Click to expand...
Click to collapse
I tried .. The process takes a long time, is completed, but it always presents the same problem
I have read in another topic if flashing fails at Factoryfs.img then your eMMC is damaged and you have to get the motherboard replaced.
I see a lot of similarities with the problems I had. I think you're also having bad luck, sorry.
i can change kernel,
I can change recovery,
i can flash all but no factoryreset.img
i can entry in download mode...
i can entry in recovery mode...
:'( i'm cry not is possibile this.. my phone have 3 months
my count now is 6 what will I say to assistance?
now i have a stock recovery... stock modem and stock csc
_giggino_ said:
who can help me?
Please i do not want to believe the brick
Click to expand...
Click to collapse
I've the exact message before, that is when I try to flash something in cwmr not knowing that I've lost full root ... Have to flashed back to GB (Rooted Stock LC1) using PC Odin, I think PC Odin is your only option also ...
_giggino_ said:
i can change kernel,
I can change recovery,
i can flash all but no factoryreset.img
i can entry in download mode...
i can entry in recovery mode...
:'( i'm cry not is possibile this.. my phone have 3 months
my count now is 6 what will I say to assistance?
now i have a stock recovery... stock modem and stock csc
Click to expand...
Click to collapse
use a jig and reset your counter, go to samsung service and tell that your phone conked while updating via kies and act as if you had no idea whatsoever and you woke up to a dead phone, they will replace your mother board.

galaxy note stuck at bootscreen

hello,
i was using my note when i got a battery warning and i just continued to use my phone and battery just died ( all normal)
when this morning i tried to charge my phone it appeard to be stuck on the "galaxy note gt-n7000"- screen and i just can't get it to start up
i left it in the charger all day but still no use.
the phone has never been flashed before and runs on official ICS 4.0.3
someone please help me really dunno what to do
I've seen Notes being stuck there, and mostly they are bricked cause of emmc or a corrupted kernel. Are yiu sure didn't flash anything? What was your last activity before your Note died?
vlxdxmxr said:
I've seen Notes being stuck there, and mostly they are bricked cause of emmc or a corrupted kernel. Are yiu sure didn't flash anything? What was your last activity before your Note died?
Click to expand...
Click to collapse
i was just playing a game from android market,
my phone has never been flashed everything was official and working well
what's emmc or the kernel thing,
sorry to ask but i'm a total noob at this.
and is there a way to fix this?
MrPlox said:
what's emmc or the kernel thing,
sorry to ask but i'm a total noob at this.
and is there a way to fix this?
Click to expand...
Click to collapse
hmmm from the sounds of it... your phone is not brick... it just entered into a very deep slumber mode...
one thing you can revive to wake it is perhaps to get a usb jig and revive your phone using it.
Or, you can try Holding the power button down, holding Volume key Down and the Home key all at the same time.....while your phone is plug to the charger...
See if something will come up on the screen....
letters_to_cleo said:
hmmm from the sounds of it... your phone is not brick... it just entered into a very deep slumber mode...
one thing you can revive to wake it is perhaps to get a usb jig and revive your phone using it.
Or, you can try Holding the power button down, holding Volume key Down and the Home key all at the same time.....while your phone is plug to the charger...
See if something will come up on the screen....
Click to expand...
Click to collapse
when i push the volume down+home+power button it goes into download mode and it asks me if i want to restart the phone or continue putting another OS on it
MrPlox said:
when i push the volume down+home+power button it goes into download mode and it asks me if i want to restart the phone or continue putting another OS on it
Click to expand...
Click to collapse
Flash gb rom use pc odin only, after flashing gb rom if still stuck in logo go to recovery mode and wipe data and cache.
jonpaslim said:
Flash gb rom use pc odin only, after flashing gb rom if still stuck in logo go to recovery mode and wipe data and cache.
Click to expand...
Click to collapse
Reflash ICS v4.0.4 its will improve the battery performance via pc odin
well i tried to flash another one but it gets stuck at NAND write and stays there
MrPlox said:
well i tried to flash another one but it gets stuck at NAND write and stays there
Click to expand...
Click to collapse
Which Rom you are trying to flash ? Please post the details...
And I recommend you to flash a pre rooted GB Rom/Directly Rooted GB Rom via PC Odin..
sahilarora2003 said:
Which Rom you are trying to flash ? Please post the details...
And I recommend you to flash a pre rooted GB Rom/Directly Rooted GB Rom via PC Odin..
Click to expand...
Click to collapse
well can you recommend me a good rom pls?
after getting stuck at NAND write when i start up the phone i get the bootscreen with a yellow triangle beneeth it
can some1 give me a step by step tutorial on how to fix it cuz i'm not really experienced in flashing n stuff
only thing i've ever done was rooting an acer liquid
thx in advance
MrPlox said:
well can you recommend me a good rom pls?
after getting stuck at NAND write when i start up the phone i get the bootscreen with a yellow triangle beneeth it
can some1 give me a step by step tutorial on how to fix it cuz i'm not really experienced in flashing n stuff
only thing i've ever done was rooting an acer liquid
thx in advance
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?t=1810954
Follow Dr.Ketan guide,you will be fine...:good:
MrPlox said:
well can you recommend me a good rom pls?
after getting stuck at NAND write when i start up the phone i get the bootscreen with a yellow triangle beneeth it
can some1 give me a step by step tutorial on how to fix it cuz i'm not really experienced in flashing n stuff
only thing i've ever done was rooting an acer liquid
thx in advance
Click to expand...
Click to collapse
http://d-h.st/HJM
Flash it via PCODIN
MrPlox said:
hello,
i was using my note when i got a battery warning and i just continued to use my phone and battery just died ( all normal)
when this morning i tried to charge my phone it appeard to be stuck on the "galaxy note gt-n7000"- screen and i just can't get it to start up
i left it in the charger all day but still no use.
the phone has never been flashed before and runs on official ICS 4.0.3
someone please help me really dunno what to do
Click to expand...
Click to collapse
It should not happen such with you...
If you are out of battery on official ROM, generally by getting it charged back can resolve the issue...
Try to recall, you must Gabe something else...
|Th£ G®£@t [email protected] [email protected]|@x¥ |\|0t€|:banghead:
MrPlox said:
hello,
i was using my note when i got a battery warning and i just continued to use my phone and battery just died ( all normal)
when this morning i tried to charge my phone it appeard to be stuck on the "galaxy note gt-n7000"- screen and i just can't get it to start up
i left it in the charger all day but still no use.
the phone has never been flashed before and runs on official ICS 4.0.3
someone please help me really dunno what to do
Click to expand...
Click to collapse
Did get any help?
I have the same problem.
I wasn't using any custom rom
I have Galaxy Note N7000
i was running stock ICS 4.0.4 (open Germany) [N7000XXLRK_N7000DBTLRK_DBT]
My phone was rooted but with no custom binary counts.
I install beat audio driver and I count restart my phone. it was stuck on the samsung screen
I didnt have any back up so i tried to use Odin and re-flash my stock ICS firmware but its stuck at NAND write start!!!
I have read so many threads but it hasn't helped. it seems like almost everyone is using custom roms
i even got one binary count follow the tutorial on this thread after i flashed a kernel (4pda_kernel.tar) http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Ive also tried stock gingerbread still stock there..
My phone is able to enter recovery mode or download mode or stock in the samsung screen..
PLEASE can someone help with something that works..?
sahilarora2003 said:
http://d-h.st/HJM
Flash it via PCODIN
Click to expand...
Click to collapse
well imma try just flashing stock ics from dr Ketan right now and i'll let you guys know what the result is
well i tried flashing a stock GB rom with odin 1.85 i followed everything step by step an odin gets stuck at zImage:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLA3_REV_05_CL1095424.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALA3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> Sbl.bin
<ID:0/009> param.lfs
<ID:0/009> zImage
i tried other cable, other usb ports even other computer and always same results can anyone help me out plz
MrPlox said:
well i tried flashing a stock GB rom with odin 1.85 i followed everything step by step an odin gets stuck at zImage:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLA3_REV_05_CL1095424.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALA3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> Sbl.bin
<ID:0/009> param.lfs
<ID:0/009> zImage
i tried other cable, other usb ports even other computer and always same results can anyone help me out plz
Click to expand...
Click to collapse
Havent seen any update from u... have u managed to rectify the issue?
nokiamodeln91 said:
Havent seen any update from u... have u managed to rectify the issue?
Click to expand...
Click to collapse
no havan't been able to fix it yet it's a pretty tough issue, now i'm following a guide to completely repartition the phone cuz there might be a bad sector
Try re-flash back with PCODIN and once flashed and still stuck at 'samsung' boot screen, press vol up + home + power button and do a factory reset. Then reboot system/wipe data cache.

[Q] Unrooted Note stuck on Boot screen, Help

Hello, I've had my Galaxy Note GT-N7000 for about a year now. I've never rooted it before.
This morning I was browsing my phone and it just shut off and went to the "Samsung GALAXY Note GT-N7000" boot screen.
I saw on other forms instructions on how to hard reset the N7000 (Remove battery, put back in, then hold Volume up, Power and Home button, then it gives you a menu to choose from)
When I do that it doesn't give me a menu screen, It just goes to the boot screen I described above, or it goes to the little green android man with the rotating object in him, then back to the (GT-N7000) boot screen a few minutes later.
I have a macbook, so I can't use the odin program. (Nor would I know how)
I don't mind wiping all the data from my phone and restarting from the beginning.
I have all the stuff I need (phone numbers) stored on my google account. And I can redownload my main apps I liked.
Any ideas?
Update
I have a windows computer I can use, so I want to use Odin to put the normal firmware back on my phone.
I am having a hard time finding the USA firmware for the GT-N7000. I have been looking all around but cannot seem to find it.
Can anybody help me out?
Check in Samfirmware.com.
No USA firmwares
nokiamodeln91 said:
Check in Samfirmware.com.
Click to expand...
Click to collapse
Thanks, I checked that site, but the don't seem to have USA firmware for GT-N7000? Is there another country's that I can use instead?
You can use any country s rom.
THANKS
nokiamodeln91 said:
You can use any country s rom.
Click to expand...
Click to collapse
Thank you very much I'll go ahead and use the UK one since it will boot in English then.
Any tips on using Odin? Or things I should do or avoid? I don't want to brick my phone by accident.
Use the rom in pda. Don't tick anything else other than default.
You sir, are awesome.
nokiamodeln91 said:
Use the rom in pda. Don't tick anything else other than default.
Click to expand...
Click to collapse
Thank you! That was exactly what I needed to know!
I'm currently downloading the ROM, I will update after I've used ODIN.
Also my phone is at 100% battery in preparation since people said to make sure it was charged before flashing.
Slight Problem...
I'm using Odin v1.85 following the instructions above and it has gotten stuck on "NAND Write Start!" for the past 15 minutes.
It doesn't seem like it is going to do anything. What should I do?
Still? Wait for some more time. Then kill kies processes and run odin as administrator. Boot into download mode again. And try.
I'm windows inept
nokiamodeln91 said:
Still? Wait for some more time. Then kill kies processes and run odin as administrator. Boot into download mode again. And try.
Click to expand...
Click to collapse
I waited about 15 more minutes then held the power button to turn it off. So now it's off and charging again.
These may be really really dumb questions, but:
1) how do i kill kies processes?
2) And how do I run as administrator?
Sorry, I'm sorta windows inept since I've been using a macbook for the past 5 years.
Open task manager and check anything related to kies. Also make sure samsung usb drivers are properly installed. If not or in doubt, download and install kies first. Then plug the phone in and with for the drivers to install.
On the phone and check what is the message on screen, if it's a firmware recovery screen the try connecting with kies recovery option. If still stuck on logo, kill all kies process. Right click on odin and run as administrator. The put phone on download and flash.
Trying it soon
I didn't have kies installed, so I am installing it right now. So once that is installed I will try it out and let you know if it works :fingers-crossed:
Updating right now
I just started updating at 10:28
I downloaded Kies, and the screen wasn't in emergency recovery, so I killed all kies processes and then i put my phone into download mode and started ODIN v1.85 as an administrator and plugged in my phone.
By 10:29 it hit <ID:0/004> NAND Write Start!!
It's 10:45 and it's still on NAND Write Start!!
Here's the whole transcript:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000OXXLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
There must be problem with emmc. Use the pit file method to install correctly. Flash the pit file first with re-partition ticked and others un-ticked. See if it goes successful. Then flash your PDA with re-partition un-ticked and reboot and reset ticked.
Is there any certain pit file thread that you would point me towards?
I been looking and I found a couple, but they all vary a little and I really really don't want to brick my phone.
Use the pit file from Dr ketans flashing guide
nokiamodeln91 said:
Use the pit file from Dr ketans flashing guide
Click to expand...
Click to collapse
I went to Dr. Ketan's post http://forum.xda-developers.com/showthread.php?t=1424997 and downloaded Q1_20110914_16GB.pit
Right now I'm flashing the pit file first with re-partition ticked and others un-ticked.
What should I do if it gets stuck at <ID:0/005> DO NOT TURN OFF TARGET!!?
It's been at that step for about 7 minutes now, and I just want to know what I should do in case it doesn't move past that.
Galaxtus said:
There must be problem with emmc. Use the pit file method to install correctly. Flash the pit file first with re-partition ticked and others un-ticked. See if it goes successful. Then flash your PDA with re-partition un-ticked and reboot and reset ticked.
Click to expand...
Click to collapse
I've been flashing it for about 20 minutes now, using the pit file with only re-partition ticked. It hast't moved past <ID:0/005> DO NOT TURN OFF TARGET!!
Should i be worried, or does re-partitioning with the pit file take a long time?
Was I supposed to have the PDA file in there too while flashing, or just the pit file? I really hope I didn't f this up...
I don't want a really expensive paper weight
DEAD
It was sitting there flashing with the pit file and my friend threw a ball at me and it hit the usb cable and it unplugged my phone from the computer. Then the computer wouldn't recognize my device anymore. I tried to turn my device back into download mode to restart the process but it won't even turn on or show that it is charging when plugged in.
I guess this is the end
Unless anybody out there is a miracle worker.

[Q] Help! phone got bricked!

Dear XDA geniuses, i could really need your help!
for the last month my battery started to run out pretty fast. Couple of days ago i noticed a weird thing, the screen started to flicker, and the phone disconnected itself from the cellular network. And then the worst has happened- the phone just shuts down itself and ever since i cant turn it on.
The only thing i can do is go into download mode, so i switched batteries and tried to install a stock firmware from sammobile with odin.
at first odin failed and told me that there is no PIT partition, i pressed reset and tried again from a different USB and then it told me "operation failed" without any reason. I tried it again and again with different version of odin, different firmware, different cable and every time the same thing- first no PIT partition and then just fail..
Please Help!
GuyTa said:
Dear XDA geniuses, i could really need your help!
for the last month my battery started to run out pretty fast. Couple of days ago i noticed a weird thing, the screen started to flicker, and the phone disconnected itself from the cellular network. And then the worst has happened- the phone just shuts down itself and ever since i cant turn it on.
The only thing i can do is go into download mode, so i switched batteries and tried to install a stock firmware from sammobile with odin.
at first odin failed and told me that there is no PIT partition, i pressed reset and tried again from a different USB and then it told me "operation failed" without any reason. I tried it again and again with different version of odin, different firmware, different cable and every time the same thing- first no PIT partition and then just fail..
Please Help!
Click to expand...
Click to collapse
You probably need to repartition your phone using a PIT file. It is very risky though so do so at your own risk.
ArkThompson said:
You probably need to repartition your phone using a PIT file. It is very risky though so do so at your own risk.
Click to expand...
Click to collapse
do you have a good guide for it? and where i can get a good .PIT file for I9305?
GuyTa said:
do you have a good guide for it? and where i can get a good .PIT file for I9305?
Click to expand...
Click to collapse
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
ArkThompson said:
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
Click to expand...
Click to collapse
Thanks for the help!
Before i try these one, does anyone has a PIT file that you tried on your I9305??
ArkThompson said:
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
Click to expand...
Click to collapse
Did what you offered, but odin got stuck in the "Get PIT for mapping.."
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUFNJ1_I9305XEOFNJ1_I9305XXUFNJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
Tried to reboot my phone and PC, but still stuck. do you have an idea why?
GuyTa said:
Did what you offered, but odin got stuck in the "Get PIT for mapping.."
Tried to reboot my phone and PC, but still stuck. do you have an idea why?
Click to expand...
Click to collapse
Not sure, you could try a different Odin version maybe. I looked around online a bit and some people had luck trying it with a different cable. If that doesn't work then the PIT is probably no good. I could try dumping mine if you want but it will be the first time I've done it so don't blame me if it bricks your phone.
ArkThompson said:
Not sure, you could try a different Odin version maybe. I looked around online a bit and some people had luck trying it with a different cable. If that doesn't work then the PIT is probably no good. I could try dumping mine if you want but it will be the first time I've done it so don't blame me if it bricks your phone.
Click to expand...
Click to collapse
Tried different odin version, it doesn't stuck but says "re-partition operation failed". Tried different cable, didn't help.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUFNJ1_I9305XEOFNJ1_I9305XXUFNJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
looks like i don't have choice but to try you'r PIT file. If that won't work I'm thinking of taking it to a lab, you think they'll be able to fix it?
Thanks A lot for the help!!
GuyTa said:
Tried different odin version, it doesn't stuck but says "re-partition operation failed". Tried different cable, didn't help.
looks like i don't have choice but to try you'r PIT file. If that won't work I'm thinking of taking it to a lab, you think they'll be able to fix it?
Thanks A lot for the help!!
Click to expand...
Click to collapse
I'm starting to think that your eMMC chip is dead so it's possible that your motherboard will need replacing. Try flashing a custom recovery in Odin and seeing if you get any error messages when you boot into it. I can make the file later tonight but it's probably better to try some other things first.
ArkThompson said:
I'm starting to think that your eMMC chip is dead so it's possible that your motherboard will need replacing. Try flashing a custom recovery in Odin and seeing if you get any error messages when you boot into it. I can make the file later tonight but it's probably better to try some other things first.
Click to expand...
Click to collapse
Didn't change much. Tried to flash only the recovery and got "No PIT partition" so i added the PIT file and again "Re-Partition operation failed"
You think its a lost cause? HW problem?
GuyTa said:
Didn't change much. Tried to flash only the recovery and got "No PIT partition" so i added the PIT file and again "Re-Partition operation failed"
You think its a lost cause? HW problem?
Click to expand...
Click to collapse
It's sounding like it might be. I made the file but I haven't tested it or anything. I'll pm you the password for the .zip since I don't want random people flashing it.
ArkThompson said:
It's sounding like it might be. I made the file but I haven't tested it or anything. I'll pm you the password for the .zip since I don't want random people flashing it.
Click to expand...
Click to collapse
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
GuyTa said:
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
Click to expand...
Click to collapse
That sucks, it sounds like it might have been sudden death syndrome or something because of the screen flickering. The last thing you could try is ticking nand erase all as well but that could potentially completely hard brick the phone because if it still fails to write after wiping you could lose your bootloader.
---------- Post added at 12:14 AM ---------- Previous post was at 12:04 AM ----------
GuyTa said:
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
Click to expand...
Click to collapse
I just found this thread http://forum.xda-developers.com/galaxy-s3/help/sudden-death-i9300-t2786220 . You could try doing what he did and put a custom recovery instead of a stock ROM in PDA when using the PIT file but I doubt that it would work.
ArkThompson said:
I just found this thread http://forum.xda-developers.com/galaxy-s3/help/sudden-death-i9300-t2786220 . You could try doing what he did and put a custom recovery instead of a stock ROM in PDA when using the PIT file but I doubt that it would work.
Click to expand...
Click to collapse
I tried it with the last PIT file, still didn't work..

Categories

Resources