Database Develop

** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly **

Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
I DO REALIZE THAT MOST OF THESE LINKS ARE BROKEN, PLEASE SCAN THE THREAD TO FIND UPDATED LINK. I'M NOT VERY ACTIVE ANYMORE, SORRY!
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO Woodrube):
JFD ODIN Images from Samsung (PDA)
Stock JFD Image
512 PIT File (PIT Extract first!)
Stock 512Pit
ODIN
Odin3_v1.0.exe.zip
Click to expand...
Click to collapse
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.
Hope you enjoy, this is my first guide, please don't flame. Any comments or suggestion is suggest, or if you have your own method I'll also post it
POST YOUR RESULTS!
-Steven
The only forums this guide should be posted on is XDA, DZ, and PHANDROID under the username DRAIKZ and EXPLOSIVE. If it helped you, feel free to donate a coke or two!
​

Nice Guide! One thing I noticed is that the color is overdone and instead of helping with reading it has the opposite effect. Made everything look semi-messy and crowded.

good guide..
one question though, the PIT file is the one for the Tmobile JFD file. would that affect any unlocked vibrant? I mean, would it lock the phone back to Tmo??
thanks for sharing,
Cheers

I thought there's no fix to a phone which is really BRICKED? oh well, everything's possible at this time.

Please be more descriptive in your terms of "brick(ed)". The term bricked is meant that your phone isb rendered COMPLETELY & UTTERLY USELESS, FOREVER! The phone will never get used again... Hence.... Brick!?
I like the guide just think it would better off with more descriptive details of what caused the phone to boot loop or not boot.

Ok let me fix up the terms when I get home. I don't think you can ever make the vibrant utterly useless haha. Android phones are nearly impossible to brick
Sent from my SGH-T959 using XDA App

angel6677 said:
good guide..
one question though, the PIT file is the one for the Tmobile JFD file. would that affect any unlocked vibrant? I mean, would it lock the phone back to Tmo??
thanks for sharing,
Cheers
Click to expand...
Click to collapse
I'm not too sure as I do not have an unlocked phone myself and was wrong the same thing a few days back.
Sent from my SGH-T959 using XDA App

Is there a fix for the brick where the phone does not turn on at all amd does not even respond to the usb in the phone like for example plugging in the phone a wall charger and not even a grey battery or a little circle symbol?
Sent from my SGH-T959 using XDA App

Yeah, read the info under the "HARD BRICK" section Good luck, it should work as that also happened to me, I had it fixed with the method I listed up there.
If you need help or some questions answered during the process, I'll be online for another hour or so, or just PM me

OP. Can you add the soldering option as well? Would be good to have it in here. Added this Guide to the WIKI.

swehes said:
OP. Can you add the soldering option as well? Would be good to have it in here. Added this Guide to the WIKI.
Click to expand...
Click to collapse
Will do and thanks for the add
Now off to find the soldering guide x]

what do you do when you use odin and it STILL boots back to the samsung screen??

If the black screen doesn't change after like 15 minutes, then just do the whole process all over again. It could just mean a bad install
Even programs messes up sometimes
Goodluck!

Remember, please post your results so I can see how I can improve this guide!

So, i think i have actualy made a brick. I was running macnut r12/a13 kernal for about a week and had some issues with the overclock so i figured i would just flash aver itself as that has fixed a few issues in the past. booted into clockwork, flashed the rom, no worries. Hit reboot system and it hung at the vibrant/i9k boot screen. At this point i was still not worried. Here is where it gets fun. My Phone will now not boot into recovery, i have been trying now for about 4 hours. I can boot into download mode, but i can not get odin to see my phone. On the same PC, odin sees other vibrants, just not mine. If i turn on the phone it just boot loops at the vibrant/i9k screen. My pc makes the usb plug/unplug noise as it boot loops turning on and off with the vibrant/i9k screen telling me that the drivers could not be installed. If i plug my gf's vibrant in, i have no issues and odin gives me a com port. Any suggestions?

THANKS dude only if if you posted this before when my vibrant was soft bricked... I sent it back I didn't know what to do hehe!
Also a question... if I do this.. will it remove root and everything also does my phone HAVE to be soft/hard bricked to use these methods because I might want to just use the soft brick Odin thing when I want to get back to normal without being soft bricked...
Sent from my SGH-T959 using XDA App

@ Adam, have you tried installing the drivers manually? If not, then I don't know what to say =/ But I'm SURE people around here can offer some help
@Rider, You're welcome, and yes it does remove everything, and yes it does work even when you're not stuck in bootloops

draikz said:
@ Adam, have you tried installing the drivers manually? If not, then I don't know what to say =/ But I'm SURE people around here can offer some help
thanks for your reply
If odin recognizes one vibrant( the working one, my gf's) and not the other(my bootlooping) do you still think its a driver issue.
Macnut is a amalgam of almost all the galaxy s's. when my phone booted it would startsaying vibrant, then flash i9k. i did install kies thinking it would have some drivers for the i9k. I will try monkeying with the drivers a bit and let you know.
Click to expand...
Click to collapse

Ok, try playing around with the USB cable, trying different USB ports, too.

No problem, remember to post your results once you try it

[Q] Help! I don't know what I did to my phone! Can anybody help me?

I've been browsing for a while all over google and this site and still can't find anything that can help me so I'm asking.
I'm a basic Captivate user with no experience with flashing and rooting, but I saw Serendipity7 and thought the instructions were simple enough to follow on the weebly site. I downloaded the ROM files and the Installation files and extracted them. I followed the instructions perfectly by installing the drivers for my phone, opening Odin3 1.7, selecting the PDA, PHONE, CSC and PIT files then put my phone in download mode. I waited for the ID:COM to pop up then hit start. The blue bar on my phone and the one in Odin started working for about 30 seconds to a minute, not even the first box was done, then my phones screen turned straight blue, and Odin3 said it failed. The popup in the corner of the computer screen then said that my phone is no recognized for some reason.
Now my phone opens to the boot screen that says
"GALAXY S
gt-i9000
SAMSUNG"
and it just sits there. I can't get into download mode, and when I plug it to charge the screen with the battery level freezes and sits there.
Can somebody help me? I am a serious noob here that assumed simple directions were easy to follow (who knew they weren't?).
Thanks a million

Looks like Odin failed(again) you need to try to get into download mode again. Might need a jig.don't ask me about the jig tho cause i never had to use one. And I got mine when it came out.
Sent from my SGH-I897 using XDA Premium App

That happened to me once after flashing Firefly. Because we had a postal strike at the time I couldn't order one but I followed this guide and made my own and it worked perfectly. http://forum.xda-developers.com/showthread.php?t=819551

Yea, just try to reflash. There are 3 ways to get into download mode again. See this post. Number 3 always worked for me the best.
http://forum.xda-developers.com/showthread.php?t=819105
If you keep having problems with Odin, try Hemidell.
http://forum.xda-developers.com/showthread.php?t=1191094

You have I9000 bootloaders pull the battery reinsert and download mode should be volume down and power no usb cable insertion needed...

Yea you're definitely gonna be able to fix that quickly. Redo flash get into download mode either holding down volume down and inserting usb or hold down and hit power.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

Were the GB bootloaders even installed?
Sent from my GT-I9000 using XDA App

Thanks everyone who helped out, one thing tho...
None of the key combos are working for me so I'm just gonna us the jig fix to get into download. I know I need to use a 300k ohm resistor but does it matter if I use a 1%, 2% or a 5% resistor?
Thanks again

^ I've used 1/4 watt 5% tolerance with success.

All gone wrong.

Something really gone wrong for me here and have a feeling I have a brick.
1. Flashed ROCKET ROM-V19-XXLA4 from external sd using CWM.
2. Flash was confirmed rebooted.
3. Got Bootloop (Rocket Logo)
4. Could boot into download mode but PC not seeing device.
5. Removed battery for over 1 min.
6. Still no difference, the device just cant be seen. Even after reinstalling the drivers. via Kies trouble shooting.
Anyone have any ideas??

exceluk1 said:
Something really gone wrong for me here and have a feeling I have a brick.
1. Flashed ROCKET ROM-V19-XXLA4 from external sd using CWM.
2. Flash was confirmed rebooted.
3. Got Bootloop (Rocket Logo)
4. Could boot into download mode but PC not seeing device.
5. Removed battery for over 1 min.
6. Still no difference, the device just cant be seen. Even after reinstalling the drivers. via Kies trouble shooting.
Anyone have any ideas??
Click to expand...
Click to collapse
Did you follow hus advuce to a t.
Did you have a backup
Can yiuget into recovery via vol up.home.power if si restore last working config.
Failing that its odin and stock rom
Its virtually impossible to brick a samsung phone yesvit can occur but v v unlikely
Sent from my GT-N7000 using xda premium

I can boot into "Odin Mode" but the device is just not responding via USB.
I do have a backup on an external device but without being able to boot into CWM or My laptop to recognise the device im stuck.....

exceluk1 said:
I can boot into "Odin Mode" but the device is just not responding via USB.
I do have a backup on an external device but without being able to boot into CWM or My laptop to recognise the device im stuck.....
Click to expand...
Click to collapse
So if you open odin on pc making sure kies is closed fully inc tray icon and then plug the phone in it does not show in odin as ready ir cinnected
Sent from my GT-N7000 using xda premium

I had the same problem today, but it worked when i did this:
- Volume down + Home + Power
- Do not press continue yet
- Open Odin
- Connect it to the computer
- Choose Continue on the Note
Now the computer should install two new drivers (modem and another one), and then the phone will pop up on the computer.

Odin is seeing :- 0:[COM4]
Thanks so much really thought I'd bricked it. Forgot all about Odin A Beer and a thanks to you both.
Just a note, not sure what went wrong but I had to flash a full stock ROM including the Modem, Code and Multi to get it working again.

exceluk1 said:
Odin is seeing :- 0:[COM4]
Thanks so much really thought I'd bricked it. Forgot all about Odin A Beer and a thanks to you both.
Just a note, not sure what went wrong but I had to flash a full stock ROM including the Modem, Code and Multi to get it working again.
Click to expand...
Click to collapse
Well least ya back up and running thats all that matters.
I can now sleep Didnt want to leave ya hanging lol
We have all had that scare moment when it goes wrong but so sweet when she boots up again
Sent from my GT-N7000 using xda premium

2nd attempt took all of 5 - 6 mins with no issues at all

[Q] Unable to make changes

I am unable to make permanent changes to my T679 Exhibit II and need some help. Here are the symptoms.
1. Any changes in Settings go back to previous settings after a power on/off cycle.
2. When attempting Factory Data Reset, the phone just turns off or seems like it's off (display is black).
3. Attempting to enter Stock Recovery results in the same black screen after the Samsung logo is displayed.
4. Tried flashing CWM 6.0.1.2 with ODIN. Although I get a Pass indication, I can't get into any recovery mode.
5. Tried flashing stock UVLG3 with ODIN. Although I get a Pass indication, The old Rom remains unchanged.
Otherwise, the phone seems to operate normally. I can make and receive calls, gps, bluetooth, and wifi works. Files written to an external SD card are okay. Files written to the internal SD disappear after a power on/off cycle.
Any ideas?

Hmm Odin is hit and miss, sometimes I have no problems other times it won't work at all
Sent from my SGH-T679 using xda app-developers app

Tried ODIN again
Thanks for looking into the problem.
I tried UVLG3 with Odin again. Although, it says Passed, I'm not sure anything is getting written. Everything is finished writing at about 20 seconds after starting and then the phone is reset. At this time the phone's screen goes black. I'm not sure if the phone is off or what's happening. If I press the power switch, I'll get the Samsung logo and a normal boot up after about 13-14 seconds. On a regular power on sequence, I get the Samsung logo after about 5 seconds.

Keep trying cwm via Odin, I know I only had to do cwm once and it worked fine. Also make sure you have the proper drivers installed, a quick search of Google will help with that.
Sent from my SGH-T679 using xda app-developers app

Odin again
I tried Odin again (many times) with a different tar file. With the new file, the time to complete all the writing takes approximately 4.5 minutes vice 20 seconds with the old file. There must be a glitch with the original tar or ops file. The file sizes are about the same, 600MB. The results are the same also... no change to the ROM. It's like the ROM is write protected. Even the clock starts off at the same time every time I power up the phone. Anyone have any ideas?

I would just do cwm the Odin stock is possible corrupt.
Sent from my SGH-T679 using xda app-developers app

Odin/cwm
tazmaniondvl said:
I would just do cwm the Odin stock is possible corrupt.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Do you mean flashing CWM with Odin? I've tried many different combinations but nothing works so far. The main rom doesn't change and I get a black screen when I go into recovery. Funny thing... when I'm in the black recovery screen, my computer will sense that the phone is there if I plug in the USB cable. Also, when I tried ADB, reboot or reboot recovery takes me to the black screen.
The only screens I get are download, memory dump, and the normal 2.3.6 operating system. No permanent changes can be made to the operating system and I can't get into recovery. When I write the CWM zip file to the internal SD, I can see it with my laptop and also with the Files app on the phone. However, the file disappears when I power the phone off and then back on. Like I said before, it's like everything is write protected.

When you are doing cwm via Odin it has nothing to do with your internal SD, you should save the Odin file to your computer, if you follow the instructions on the page you get cwm Odin file, you should have no problem, I just did cwm from Odin and it worked just fine. But if you miss a step you will still get a pass but in reality it failed. If it does not work for you then there is a problem on your device I have never ran into.
Sent from my SGH-T679 using xda app-developers app

Odin
tazmaniondvl said:
When you are doing cwm via Odin it has nothing to do with your internal SD, you should save the Odin file to your computer, if you follow the instructions on the page you get cwm Odin file, you should have no problem, I just did cwm from Odin and it worked just fine. But if you miss a step you will still get a pass but in reality it failed. If it does not work for you then there is a problem on your device I have never ran into.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I did not mean to say that I was trying Odin by copying the file to the internal SD. I was just trying to illustrate the read only characteristics of the phone. I've done Odin downloads before but the first thing that I tried to revive this phone was to copy the CWM zip over to the phone thinking that I would flash CWM and then reset/reflash the phone with CWM.

Since you can't do cwm flash. That's why I recommend you try cwm via Odin.
Sent from my SGH-T679 using xda app-developers app

Odin/cwm
tazmaniondvl said:
Since you can't do cwm flash. That's why I recommend you try cwm via Odin.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
I did try it. I thought I mentioned that CWM via Odin only took about 4 seconds to do the write (I didn't).
I would like to mention that one thing does change... the clock/calendar does update (I thought it didn't). It doesn't keep any changes that were made to the phone (manually or automatically via network) before turning it off. I just noticed that when I turned it on today, the date was Aug 17, 2012. Yesterday it was Aug 16. So some changes are being kept.

There is a cwm flashable zip for stock recovery. Why not just use that? After the 2.3.6 update there is really no need for Odin with this phone.
Sent from my SGH-T679 using xda app-developers app

He can't get to recovery at all
Sent from my SGH-T679 using xda app-developers app

Tried something different
I tried to gain root via ADB. I pushed and executed psneuter and also gingerbreak. The two programs seemed to execute (get several lines of messages for each program before stalling), though not to completion. Each one hung after executing partially. The funny thing is after a power off/on cycle, when I use adb again and navigate to the directory that I pushed psneuter and gingerbreak to (/data/local/tmp), the directory is empty. I don't quite understand why all changes made to this phone are just temporary. Any change stays only until the next power off/on cycle. Any ideas?

tazmaniondvl said:
He can't get to recovery at all
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Just reread thread, my bad. I didn't catch that. Sorry.
Sent from my SGH-T679 using xda app-developers app

Stuck at bootscreen, no recovery mode, download mode works, Odin3 stops at kernel

Hi to everyone who's reading this.
I have got stuck with an Note GT-N7000 from a friend. It was running the original Samsung firmware and never flashed before. Now the device is stuck at the bootscreen.
If I press the Home+VolUp+Power, it just flashes the bootscreen (see IMG_20131006_212031.jpg) then the screen is black again and shortly after that the boot screen shows again. For comparison if I just press power then this short flash doesn't happen. But the same bootscreen is shown.
I have tried to flash PhilZ-cwm6 recovery, but Odin3 stops at "NAND Write Start" no error line or anything (see Odin3.jpg). After an reboot there was that yellow triangle indicating a modification of the firmware. But no change to the problem.
To provide as much info as possible I also attached a photo of the label below the battery (see IMG_20131006_211932.jpg).
The device is older than 2 years now, so there is now warranty.
The behavior is somehow similar to:
http://forum.xda-developers.com/showthread.php?t=2466339
I'm a little bit afraind i could brick it even while trying to repartition the phone.
http://forum.xda-developers.com/showthread.php?t=1667886
Another thread discribing pit, but i'm not stuck at factoryfs. May this apply to me too?
http://forum.xda-developers.com/showthread.php?p=26285877
Thanks in advance for any help.
Regards Marco

Stuck at flashing kernel? Hmmm. Try a different USB cable, front port, kill all kies processes is any, try a different PC.

Friendly word of advice, blank out your imei from the second image.
Sent from my C6833 using XDA Premium 4 mobile app

nokiamodeln91 said:
Stuck at flashing kernel? Hmmm. Try a different USB cable, front port, kill all kies processes is any, try a different PC.
Click to expand...
Click to collapse
Ok, I tried the same procedure on my notebook using the cable from my Wonder with the same result. As I'm using the drivers that came with Windows Update, I have no kies installed anyways. I Tried to install the drivers from this thread http://forum.xda-developers.com/showthread.php?t=1424997. But I think my system isn't using them.
Could that Microsoft provided drivers be the problem?
As the battery only has 3.1 volts with no change over several hours of charging and the phone doesn't enter the download mode anymore with a battery low error. I'll first try to replace it with a new one. Maybe that's that cause after all. I just hope the charging circuits aren't broken.
SpyderTracks said:
Friendly word of advice, blank out your imei from the second image.
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, for that advice! Didn't know that the IMEI can be used to blacklist stolen devices (Wikipedia). Someone might do a prank with it.

para756 said:
Ok, I tried the same procedure on my notebook using the cable from my Wonder with the same result. As I'm using the drivers that came with Windows Update, I have no kies installed anyways. I Tried to install the drivers from this thread http://forum.xda-developers.com/showthread.php?t=1424997. But I think my system isn't using them.
Could that Microsoft provided drivers be the problem?
As the battery only has 3.1 volts with no change over several hours of charging and the phone doesn't enter the download mode anymore with a battery low error. I'll first try to replace it with a new one. Maybe that's that cause after all. I just hope the charging circuits aren't broken.
Thanks, for that advice! Didn't know that the IMEI can be used to blacklist stolen devices (Wikipedia). Someone might do a prank with it.
Click to expand...
Click to collapse
Don't think the ms drivers work at all for proper connection.
Sent from my C6833 using XDA Premium 4 mobile app

SpyderTracks said:
Don't think the ms drivers work at all for proper connection.
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, i got the new battery and I've got the windows drivers working. But still with the same result. Any other ideas?
Should i try a different Flash file?
I allready downloaded the an original firmware but i'm afraid to do even more damage, if I don't wipe data and cache. So I wanted to flash the recovery first.
Are there any other steps that i have to do first? Maybe i'm missing something.

Have you installed kies? If not, install that first. It will install all three required drivers. Then go to task manager and kill all process that relates to kies. Then reboot the phone into download mode and flash again. You can also try the firmware you downloaded using original Pit file with repartition.

nokiamodeln91 said:
Have you installed kies? If not, install that first. It will install all three required drivers. Then go to task manager and kill all process that relates to kies. Then reboot the phone into download mode and flash again. You can also try the firmware you downloaded using original Pit file with repartition.
Click to expand...
Click to collapse
I had no keys installed, but I did now. Unfortunately I think the drivers in mentioned before seam to be the same.
Meanwhile I also tried to flash the original firmware and a Gingerbread Firmware form that brick safe install thread. In comparison to the CWM there is no progress on the green bar, just 2 pixel. I thought that I might have not waited long enough, but for that CWM flash the bar was completed for at least 10 minutes.
As I Installed Kies now I saw that option that allows a firmware update through kies. But it doesn't seam to initialize the update, quite similar to the behavior Odin shows.
I don't' like messing around without a way to identify that I have the right set of drivers installed. I tried to find some information about the drivers through the forum search and Google, but so far with no result.
I attached the drivers I use. If you (or someone else) did this before and got a working configuration, would you be so kind and make some screenshots of the drivers you use?
The same game with the the USB-Cable, has someone a correct wiremap, that I could check? (obviously not easy for the mini-USB connector)
By PIT-File you mean the "Pit file for 16GB model" from this thread? http://forum.xda-developers.com/showthread.php?t=1424997 or just the checkbox Re-Partition? That's really the last thing I want to try now, because I know to less about internal structure of the device. If Re-Partition fails and the downloader (Power+VolDown+Home) is on that partition I might kill the last point I can modify this Note ATM.
Just something more i want to add: Odin doesn't show that blue progress bar. I never used Odin before, but i searched for the process on YouTube and i just guess that Odon mode on the Galaxy Note it should show that bar too.
Meanwhile I also tried to flash a Krenel zImage with heimdall (The Kernel zImage is linked from the recovery CM tells to use in the installation process with heimdall). As Heimdall brings it's own drivers and behaves similar, I would guess, that the drivers at not the problem anyways.

How did you flash the gb rom? You need to try a rom flash using odin. Yes I mean the 16 gb pit if you have the 16 gb note.
Do you have access to Cwm recovery?
---------- Post added at 02:55 AM ---------- Previous post was at 02:52 AM ----------
Odin 3+ has a blue progress bar and old odin has green. When flashing firmware the download mode on phone also shows a green progress bar which is the indication of write.
When you connect the phone in download mode does your phone screen say "downloading"?

nokiamodeln91 said:
How did you flash the gb rom? You need to try a rom flash using odin. Yes I mean the 16 gb pit if you have the 16 gb note.
Do you have access to Cwm recovery?
Click to expand...
Click to collapse
To flash GB I followed this thread http://forum.xda-developers.com/showthread.php?t=1763151 to step 10.
The Phone was stock before it broke. I just hope i didn't confuse you. I tried several aproaches now.
All the roms i tried so far have been single file roms.
The 1st thing i did was trying to flash PhilZ-cwm6 recovery.
Then I replaced the battery, because odin download mode stated the battery is beeing low.
I repated the process with different versions of the drivers provided in this forum and by kies.
After that i tried different Firmware versions.
And finally i tried heimdall because it seams to be a good alternative to Odin.

Yes I am a bit confused. May be not because of your steps but too much to read..
Is recovery mode accessible? As your last post say Cwm recovery flash.
When the phone is in download mode, what's displayed on the screen?

nokiamodeln91 said:
Yes I am a bit confused. May be not because of your steps but too much to read..
Is recovery mode accessible? As your last post say Cwm recovery flash.
When the phone is in download mode, what's displayed on the screen?
Click to expand...
Click to collapse
OK i'll try it short
Recovery never was accessible. Download mode ist shown by the screenshot in the 1st post. Only the counter went up to 9.

There is no download mode screenshot in the first post. Could you post again.

nokiamodeln91 said:
There is no download mode screenshot in the first post. Could you post again.
Click to expand...
Click to collapse
I'm verry sorry, that was my fault. I added it to the 1st post. It's getting late for me.

Yeah. Just saw it. All looks fine. I cannot find a reason why odin is not flashing even the kernel. If bricked, it's usually in the system partition, then also kernel should be flashed successfully.
Tried changing the use cable?

nokiamodeln91 said:
Yeah. Just saw it. All looks fine. I cannot find a reason why odin is not flashing even the kernel. If bricked, it's usually in the system partition, then also kernel should be flashed successfully.
Tried changing the use cable?
Click to expand...
Click to collapse
Yeah, tried 2 cabels and 2 PCs so far...
I will report the result's here when I tried the repartitioning. So have a good day/night and thanks for your time.

I'm sorry if this was already covered. If you flash JUST philz with Odin, can you get into recovery?
Sent from my GT-N7000 using Tapatalk 2

AndroidSlave said:
I'm sorry if this was already covered. If you flash JUST philz with Odin, can you get into recovery?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yep, that was the 1st thing I was trying. But I cant flash philz or anything else. Thats all the problem.
I'm thankfull for anyone who gives it a try.

para756 said:
Yep, that was the 1st thing I was trying. But I cant flash philz or anything else. Thats all the problem.
I'm thankfull for anyone who gives it a try.
Click to expand...
Click to collapse
Just throwing ideas out and sorry if you're already doing it...
I always run Odin as administrator.
I would personally start from scratch regarding drivers, delete kies and Samsung drivers, then go into device manager and check there aren't any remaining ms drivers. Reboot and reinstall kies, then shut down kies processes.
I always put the Odin folder on root of c.
The symptoms point to driver issues I think, that's where you usually see this kind of behaviour.
Sent from my C6833 using XDA Premium 4 mobile app

OK, I SuperBricked (no ODIN) it now. For others with the same symptomes, don't use Re-Partition. As I won't try it with JTAG maybe the device goes to eBay. Thanks to everyone and don't worry, it would have been broken anyways.
Maybe if someone is in the same situatuon: Try harder on different cable/drivers/os before using a Pit file.