Database Develop

Odin stuck at factoryfs.rfs

I am trying to flash back to stock but odin just sits at factoryfs.rfs
I'm not sure what to do now. It will not power up normally at this point.
I can go into downloader but it just hangs at the same point.
Any suggestions for me?

texasryno said:
I am trying to flash back to stock but odin just sits at factoryfs.rfs
I'm not sure what to do now. It will not power up normally at this point.
I can go into downloader but it just hangs at the same point.
Any suggestions for me?
Click to expand...
Click to collapse
Try plugging into your computer with a different USB port, my work computer loves to do that crap and sometimes it just takes a reboot or port switch to make it work

Same problem, fixed it by running ODIN under administrator privs

hobolooter said:
Same problem, fixed it by running ODIN under administrator privs
Click to expand...
Click to collapse
right click on the file and run as administrator. If u using window 7. I solved the prob like that.
Sent from my SAMSUNG-SGH-I897 using XDA App

OK had already tried running as admin privs. Tried different port after a reboot and still no joy.
Then decided to try on one of my XP boxes and that did the trick. Thanks for getting me to think in another direction.
Up and running on Froyo and all is well.
This community is great!!

i'm running as admin, but have the same exact problem. changing ports doesn't help either.

On Windows 7, try running it in Compatibility Mode for Windows XP (Service Pack 2).

Same problem
Hi guys, i've got the same problem and i've tried everything it feels like. It just wont go past factoryfs. Anyone that can helt me?

junkyhlm said:
Hi guys, i've got the same problem and i've tried everything it feels like. It just wont go past factoryfs. Anyone that can helt me?
Click to expand...
Click to collapse
Stock cable sometimes helps too, I noticed that ADB will not stay connected with one of my cables but will work just fine with the stock cable. Crazy, but others have noticed it too.
Also, this is the wrong section.

Thread moved to Q&A.

l7777 said:
Stock cable sometimes helps too, I noticed that ADB will not stay connected with one of my cables but will work just fine with the stock cable. Crazy, but others have noticed it too.
Click to expand...
Click to collapse
Hate to bring up an old thread, but I could not find this until I typed a title for a new post. Even google couldn't find it. Just saying this fixed mine and I passed some thanks around for you guys!
Oh, and that my phone won't even try to connect unless I use the stock cable and one specific USB port on the front of my compy.

I am having this exact issue now. . . . I tried everything mentioned on here.
Swapped ports
Swapped cables (one is OEM)
Ran as Admin(Windows 7)
Ran compatibility to Windows XP SP2
Still nothing
Stuck at 2/3rds of the way when updating the factory image.

i'm having the same exact problem. i've tried flashing both the DI18 and DI07 from this page and it gets stuck 2/3 of the way thru factoryfs.rfs... what is strange is that i can flash to DK28 without a problem. i'm using odin3 v1.61.
my phone was stock until today when i flashed into the DK28 then converted to ext4. then i flashed the Frankenstein ext4 rom with clockwork. everything worked fine but i didn't realize i couldn't restore all my data from my original rom so now i'm trying to go back to those recover apps and settings from my original rom. could anything i have done today had anything to do with this problem? i've tried all of the above troubleshooting steps as well. i'm using windows but i'm considering trying heimdall on ubuntu if this problem keeps up
EDIT: i'm trying heimdall but the first step is to extract the .tar rom... the DK28 extracted fine but there were errors with my DI18 and DI07. looks like my problem might be a bad rom
FINAL EDIT: yep, sorry. i re-downloaded the eclair rom and it flashed fine. on the bright side, this forced me to use heimdall and i think i'll be using that from now on so i dont have to boot into windows all the time

Same problem
I had midnightROM 2.9.2 EXT4 installed.
Tried to odin flash back to stock Froyo and it stuck on factoryfs.rfs. Also, screen turns completely one color. Now it's purple.
Is this because the phone was formatted to EXT4 and now odin is trying to write in rfs format?
If so, how do I reformat phone to rfs? Of course the phone doesn't work or boot up so it has to be done through odin or Heindall.
Any other choices? I have Linux to use if needed.
I tried DI07 & DI18. Same results.
Thanks!
Knife
UPDATE-RESOLVED: 12 hours later.... After blue, yellow, purple burgundy and green screens. It finally worked. I monkeyed around with it, but not sure what the problem or solution was. Some things I did:
1. I downloaded another stock D28 and used Firefox's "Downloadthemall" extension, which ensured a checksum match.
2. In odin 1.61, I flashed a pit (non-victoria) only with "partition" box and reboot checked. It did something and completed.
3. Then, I used the one USB port that I hadn't tried - the one my wireless USB ant was inserted.
4. Did the victoria pit with "partition" and reboot checked and it worked!
5. This was after several fresh re-installations of 64-bit drivers in Vista 64-bit Home Edition.
Not sure what did the trick, but I suspect it had something to do with partitioning. I assume because I had previously converted to EXT4, there was trouble with just flashing rfs to it. Perhaps the first (or second) partition reformatted that area of the permanent phone drve.
Immediately, I put no-journal, 2.9.3, 3.1 theme-blue-ASOP and viper apocalypse theme on SD (titanium sdk & last back-up, and Launch-pro back-up already on SD). I followed instructions and CW3'd the phone. After EXT4 convert self-ran, I Did not reboot and flashed no-journal. Then, Did not reboot and flashed 2.9.3.. Re-boot. Turn off and turn on. Turn off and 3-finger to CW3. Flashed Midnight 3.1 them. Reboot. Turn off and turn on. Turn off and 3-finger to CW3. Flash Viper apocalypse theme. Re-installed apps one by one from titanium. Entered Launch-pro code. Restored Launch-Pro back-up.
Update: The rom pooped on me today while moving moveable apps to SD. It tried to shut down (9% bat remaining) and looped in the android boot immage. Nice green cloud circles, btw. Got it to main screen and everything FC's, including Launch Pro. It works a little bit in Launcher, but everything is force closing over and over again. I am going to wipe 3x and reinstall 2.9.3. Geeze, I came from 2.9.2 and life was good. I think 2.9.3 might be a booger until our beloved creater picks at it...some more. I'm looking forward to 3.0 ;-)
3 minutes later.....Wow, just went to midnight thread and I see 3.0 has arrived. Hurray, the booger is gone.

Was having this issue. Could not for the life of me get past the factory part, but luckly I used my school netbook and it worked.

Run as admin
run as admin worked for me

I had a problem where Odin got stuck at the factoryfs.rfs stage using Windows 7. Running as admin didn't work. I swapped USB ports, set it to run in XP service pack 3 compatability mode, and ran as admin. That worked.

Sorry to bump an old thread but it appears i have the same problem
Flashing back from MIUI 1.6.10
Stuck at factory.rfs before turning pink/blue/grey/black/Burgundy
Did ran it under admin and compatibly mode. same thing happened.

Hi, i've got the same problem with a i5800, problems with odin seems to depend of the computer of the user.
However instead of switching pcs, i used an app called "Sandboxie", don't know what is does exactly, but it helped me with other rebel apps too.
Just open sandieboxie and drag the odin .exe to the sandboxie window, choose Default box and click ok.
I fixed the problem with that, maybe i only was lucky, but you loose nothing trying, good luck!

41LY45 said:
Sorry to bump an old thread but it appears i have the same problem
Flashing back from MIUI 1.6.10
Stuck at factory.rfs before turning pink/blue/grey/black/Burgundy
Did ran it under admin and compatibly mode. same thing happened.
Click to expand...
Click to collapse
Dont be sorry. You deserve a cookie for not opening a new thread.

[Q] Big problems with my Galaxy....Help needed!!

Since yesterday my Galaxy S got stuck. It doesnt start anymore.
What happened?
I flashed my rom to the newest ICS. Everything went well and I used it a couple of days. Yesterdaymorning I did wiped the battery stats and cleared the Davik cache. I rebooted and it got stuck in the bootscreen.
I tried to got in recoverymodus but that was not possible. Bootscreen was all I saw.
Then I tried the downloadme. That is working BUT odin did not see my phone and KIES did also not recognize it. I have the right drivers. When my phone was working it was also not recognized because I am afraid the USB port is not good anymore.
Does anyone have tips?

wvawijk said:
Since yesterday my Galaxy S got stuck. It doesnt start anymore.
What happened?
I flashed my rom to the newest ICS. Everything went well and I used it a couple of days. Yesterdaymorning I did wiped the battery stats and cleared the Davik cache. I rebooted and it got stuck in the bootscreen.
I tried to got in recoverymodus but that was not possible. Bootscreen was all I saw.
Then I tried the downloadme. That is working BUT odin did not see my phone and KIES did also not recognize it. I have the right drivers. When my phone was working it was also not recognized because I am afraid the USB port is not good anymore.
Does anyone have tips?
Click to expand...
Click to collapse
can you go to recovery?

unfortunately not.
if i do the 3button trick the sreens stays on the bootscreen.

Change your drivers to the Nexus drivers in OP of TH ICS thread and try a different USB port.
Once in odin flash the initial CM7 kernel without reboot then go into recovery and reflash CM9.

installed nexusdrivers.
still nothing happens.
any other suggestions?
thx for the help!!!

Different USB port?

tried all 4 and another laptop
also used different cables.
almost start crying

-prereq-
install samsung drivers for your device and windows install type (x32/x64). It's quite important that you install 64 bit drivers on a 64 bit box and not 32, because they are ****ty and work 7/10 times used.
1. be sure to use the same port.
2. be sure to use ONLY the original cable that came with your phone
3. Make sure your phone is able to enter download mode. (Vol down+Home+Power)
if it does, it should install your drivers without issue about then.
4. If you can't use odin to restore your pda/csc/modem, then use heimdall. If that fails, you need to commandprompt heimdall into flashing with 512.pit + required files (refer for help to the heimdall readme included in their install) file after unpacking pda,modem,csc into the heimdall commandline exe.
If 4 does not work you need to unbrick it via 1clickbrick. It's a jar file you donwnload, dblclick and use.

thx for trying to help me. but I am afraid my USB port (mini) on my galaxy is not working. Tried 4 computers, several drivers but stil no connection possible.
Any other suggestions?

wvawijk said:
thx for trying to help me. but I am afraid my USB port (mini) on my galaxy is not working. Tried 4 computers, several drivers but stil no connection possible.
Any other suggestions?
Click to expand...
Click to collapse
Did you indtall usb drivers?
Sent from my GT-I9000 using XDA App

Try flashing the EZBase with Odin in Download Mode. Then report back
Sent from my GT-I9000 using Tapatalk

thx but the problem is : odin does not work.... it does not recognize my phone.... and I use the right drivers....
can it be because I work on isc rom?

When i was on ics (bootloop), ich have downloaded the Samsung USB drivers (exe.) and flashed via odin jvu...
Sent from my GT-I9000 using XDA App

@ aakaashjois
damn....it didn't work with the EZbase pitfile.....:-(

Unusual
wvawijk said:
@ aakaashjois
damn....it didn't work with the EZbase pitfile.....:-(
Click to expand...
Click to collapse
Are you sure? did your phone appear as 'added' after you out it in d/l mode? follow these steps...this is a sureshot method dude.
http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
Good Luck!

any of the computers find it as new hardware?

amadeus_l said:
Are you sure? did your phone appear as 'added' after you out it in d/l mode? follow these steps...this is a sureshot method dude.
http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
Good Luck!
Click to expand...
Click to collapse
No added unfortunately..... starting to give up.......

hackandmore said:
any of the computers find it as new hardware?
Click to expand...
Click to collapse
Nope..... I am afraid I lost my Galaxy...... :-(

Had the same problem on Windows machines - for some reason two of my Windows powered computers stopped recognizing my phone. Tried different drivers for no effect, so I gave up and tried it on linux and successfully flashed new kernel using heimdall.
I don't know if this is a legitimate solution because it's like going around the problem instead of solving it, but if everything else fails, try different operating systems.

try charging it..does it charge?
if it doesnt then go in a service and ask them to take a look at it.they will do that for a pack of cigarettes in their extra time.if its fixable and cheap(dont think of replacing the entire motherboard...sell this one for parts and buy another one, or find one with broken display and take em both to a service and tell them to replace the screen from your phone to the other)

so my brother brought me his semi bricked n7000 "btw i searched and googled"

so my brother brought me his semi bricked n7000 "btw i searched and googled"
well, yesterday my brother brought me his cellphone which doesn't boot anymore, he wanned to install a custom rom since he saw that i have a fast one (galaxy s I)
so when i asked him what he did , he said he followed all the steps in rootgalaxynoteDOTcom/galaxy-note-roms/kingdroid-ics-rom-v3-0-for-galaxy-note-gt-n7000-best-ics-romtouchwiz-ux/[/url]
but then, his phone didn't boot, so he wiped - reset factory setting, which i read is a BIG NO when you're flashing ICS.
so whats done is done, i am trying to get it back , i can boot in recovery mode/download mode ... i tried out many kernels like AbyssNotekernel42RedTouchCustomLogo or speedmod, and downloaded at least 4 or 5 GB stock roms.
sadly , if odin flash is successful, it stuck on (samsung galaxy note gt-n7000) black srcreen, reboots few times then stays still...
if the odin flash wasn't successful , it keeps stuck on data.img and never goes beyond that .
i did all the steps i could find, wiped data after installed stock GB rom and rebooted, nothing worked
i even used rogue_ET-recoveryonly , and i think it went along format all the way, but still nothing happened after that.
the only thing i haven't tried yet was the repartition + pit file, i couldn't find the PIT , most of the roms have pda/modem/csc ... so if anyone can help out, i would really appreciate it ..
thanks

First thing you should do is check other threads about that around here.
If you can get it into download mode, you could give flashing with Odin a try. If it doesn't get stuck at factory.fs, then you're not superbricked.
If it does get stuck, then you have 2 more hopes:
- HOPE 1
- HOPE 2
If those don't work either...I'm afraid it's off to the Samsung Service center for a shiny new motherboard.
Best of luck to you and hope you get your Note up and running as soon as possible...

thanks, no it doesn't get stuck at factoryfs at all , i did check out most of the threads here, and most of them say "go back to GB with odin and if its stuck on samsung gt-n7000 boot screen just go back with recovery mode and then wipe data / cache " but never worked, so i thought i should ask around here
i'll check out the threads you posted and see what i can come up with

weird, i used the 16gb pit - repartition (check)
and i flashed it with SGN_XX_OXA_KJ1_FACTORYFS through odin.
and its still the same, the flashing with odin was successful and everything went fine, no hanging , no delays or what so ever. after it restarts its stuck on the black samsung galaxy note gt-n7000 screen
im gonna wipe data / cache again but i doubt that would fix anything.
so any idea what could be wrong? specially when the flashing process went fine?
i've already tried like 4 stock roms ,
arabic uae , europe , saudia and the SGN_XX_OXA_KJ1_FACTORYFS
i wonder if i need to put something in boot space in odin "just a thought"
ive tried downloading roms from here [STOCK ROMS] N7000 All stock ROMs + install + Root guide All at 1place,Latest ICS LQ3
and here [STOCK ODEX PRE ROOTED ROMs] for Odin PC no counter & triangle
any ideas?

For OP:
If you are not stucking while flashing from PC Odin then you are not superbricked.
I think you got corrupted /system or other partition; I saw another thread where OP was getting this sort of hang due to filesystem corruption which can't mount.
Entropy512 gave simple dd command based solution for erasing initial 1MB of partition.
Try searching for corrupted filesystem/partition related information. I can't recall exact thread title, sorry.
I hope this will help.
I found the post/thread for you to check: http://forum.xda-developers.com/showpost.php?p=27102526&postcount=16

thanks for the reply , even think i flashed the abyss and the 4pda_kernel i still can't get anything when i do adb devices >.>
so im trying to figure out whats wrong

johar123 said:
thanks for the reply , even think i flashed the abyss and the 4pda_kernel i still can't get anything when i do adb devices >.>
so im trying to figure out whats wrong
Click to expand...
Click to collapse
Should try to install/reinstall samsung usb driver package. or try reinstall Kies also provide drivers for Note.
If driver is install properly: when connect with PC using usb cable it need to be shown under hardware management as something like "android composite adb interface" or something like that.

johar123 said:
thanks for the reply , even think i flashed the abyss and the 4pda_kernel i still can't get anything when i do adb devices >.>
so im trying to figure out whats wrong
Click to expand...
Click to collapse
Also are you trying to connect adb after booting the phone ? Means in a stuck state ? I think you can try enabling ADB thing from CWM rather than trying to boot phone fully.

hmm i can't find an option in CWM that suggests that , still searching
also im trying to find roms that i can install from CWM , are there any GB roms that can be directly installed from CWM ?
thanks.

johar123 said:
hmm i can't find an option in CWM that suggests that , still searching
also im trying to find roms that i can install from CWM , are there any GB roms that can be directly installed from CWM ?
thanks.
Click to expand...
Click to collapse
Hi: I understand he means boot the phone into CWM and then connect to PC in that environment. adb need to be run from PC while the phone is booted into CWM recovery.
Still, most of the custom roms are in the .zip format and can be install using CWM. they just now become a bit more difficult to find since dev move on to ICS/CM9 roms. Still try to find some GB roms in the forum such as: rocket GB, litening GB, xtralite GB....
This is the link for Rocket rom GB. Better try v22 than v23.
http://forum.xda-developers.com/showthread.php?t=1380284
Check rom:
http://download.checkrom.com/roms/a...oteHD_V3.zip?iframe=true&width=950&height=420
cheers,

forest1971 said:
Should try to install/reinstall samsung usb driver package. or try reinstall Kies also provide drivers for Note.
If driver is install properly: when connect with PC using usb cable it need to be shown under hardware management as something like "android composite adb interface" or something like that.
Click to expand...
Click to collapse
done that already.. everyone is saying is "get into recovery mode" >.>

johar123 said:
done that already.. everyone is saying is "get into recovery mode" >.>
Click to expand...
Click to collapse
Yes, recovery mode is in CWM. (in case you have not done it: Enter recovery by,from phone power off: pressing volumeup + home + power and release power when see samsung letter while still hole the other two buttons.)

forest1971 said:
Hi: I understand he means boot the phone into CWM and then connect to PC in that environment. adb need to be run from PC while the phone is booted into CWM recovery.
Still, most of the custom roms are in the .zip format and can be install using CWM. they just now become a bit more difficult to find since dev move on to ICS/CM9 roms. Still try to find some GB roms in the forum such as: rocket GB, litening GB, xtralite GB....
cheers,
Click to expand...
Click to collapse
thanks for the reply, i've done it many times, when im in the CWM screen, the adb devices still doesn't show anything >.> maybe im using a wrong kernel? what kernel you guys suggest?

johar123 said:
thanks for the reply, i've done it many times, when im in the CWM screen, the adb devices still doesn't show anything >.> maybe im using a wrong kernel? what kernel you guys suggest?
Click to expand...
Click to collapse
hmm. that should be still the problem with usb driver. Have you checked under hardware management if it show the device as "samsung composite adb interface" yet?
kernel should not be the problem with connecting adb. It is the problem with usb driver for Note. Sometime Win7 have problem with driver. You may want to search for another package of samsung usb driver on the web.
I did put some links of GB roms in the post in the previous page. maybe try them first if any luck.
Also try to restart computer to see if the driver issues get solved.
Got to go. Hope that you can solve the problem. GL.

forest1971 said:
hmm. that should be still the problem with usb driver. Have you checked under hardware management if it show the device as "samsung composite adb interface" yet?
kernel should not be the problem with connecting adb. It is the problem with usb driver for Note. Sometime Win7 have problem with driver. You may want to search for another package of samsung usb driver on the web.
GL.
Click to expand...
Click to collapse
thanks, i restarted my pc , reinstalled kies, and now it shows under device manager
now i connect to the phone through adb , i appreciate you pointing it out
which method you think i should go for 1st? this one
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
or unzipping a rom and then pushing it all through adb?
i think i'll go for removing and repartitioning manually, hopefully it'll work
thanks again guys , i'll post the updates here,
lol, my brother called me and he's like "if u can't fix it by the end of the night, fk it, dont bother yourself with it" but to be honest, im too stubborn, i hope i can fix it

looks like deleting and adding partitions back through parted kinda work, for the first time i was able to pass the boot screen after i installed rocketrom from CWM
however, its been 1/2 hour since im stuck on rocketrom loading screen it keeps looping and looping.. i wonder if i should wait more.. or should i try another rom?

finally got rid of the verification -.- was kinda annoying thats why i didn't bother editing posts,
anyways, rocketrom didn't work, so i decided to flash a stock rom instead , the flash through odin went fine, it was great to be able to wipe data without getting stuck , however, it keeps going though samsung animation over and over, i think im gonna leave it like this one the charger till morning, i wonder if it'll be the same
guess i have to google for "samsung loop" , i wonder why this keeps happening though -.-

-.- leaving it for 6 hours on samsung logo animation didn't do the trick , still looping when i woke up, so i guess i'll do some more search on why this is happening.

You have checked partitions and see no error that means the problem lies somewhere else, not partitions. I have no idea yet, but for me I would try some different roms. Small roms have more chance to work, that is the feedback I got from some people:
- try check rom in the link I sent
- try paranoid android which is CM9, or asylum
- extralite
cheers.

forest1971 said:
You have checked partitions and see no error that means the problem lies somewhere else, not partitions. I have no idea yet, but for me I would try some different roms. Small roms have more chance to work, that is the feedback I got from some people:
- try check rom in the link I sent
- try paranoid android which is CM9, or asylum
- extralite
cheers.
Click to expand...
Click to collapse
thanks buddy, i appreciate your help, the partition "USED" to give me error when i did the check 9 10 11 , but after removing the partition and reformatting them (and i also removed the cache partition) now its working fine "i suppose" i didn't do another check, but i might will now that you mention it.
i already tried rocket rom, didn't work, stock rom didn't work, so i'll give the others a try at least it doesn't get stuck on the boot screen, but its stuck on the animation logo which is an improvement
thanks again

[i9000b] BSOD - Phone ! Computer Screen

I had Android 4.0.3 (IceCream Sandwich) on my Galaxy S GT-I9000B (I did install it through Odin, nothing went wrong), but is was laggish (too much for it to handle, I think) and after a few months, I decided to roll it back to 2.3.3 (Gingerbread).
I started the process to install the firmware through Odin3 v1.85 - the file I download (from sammobile.com/firmware, had only one file that I used on the PDA space.
Odin recognized my phone and I started to install it, but after a while my phone was stuck on the downloading screen (2 hours of installation, I tought that something went wrong).
I then turned my phone off to try and install again, but when I turned it on, there were a Phone - exclamation mark - Computer Symbol.
I can get it to dowlonad mode (Volume Down+Home+Power), but when I plug it to the pc, it says "unknown device" and it can't find drivers for it.
I think I have the latest drivers from Samsung (I had from Kies and I re-downloaded a file somewhere from this forum named SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.exe).
It appears that since windows can't install the drivers, Odin doesn't recognize the device - it was recognizing it before, when I was installing the firmware.
Now I'm stuck - I tried anything I saw in this forum and in other places - I did even pray for a miracle, but it didn't work
I know that there must be a way, but I don't know how.
Before I forget, I'm using Windows 7 Ultimate x64.

If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.

KainFromNod said:
I know that there must be a way, but I don't know how. Before I forget, I'm using Windows 7 Ultimate x64.
Click to expand...
Click to collapse
Ok, k4Z3666, has given you a starting point...the phone is still in download mode but without a booting ROM, so its OK, the problem is your PC, USB cable or USB port. If you want to be quick about it, just try on a lap top..if not a simple Reboot of PC ( after removing power cord) and Phone (after a battery Pull), and a switch to a different USB port at the back of PC can solve this for some...for other solutions try these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 anything else you may need can be found on My Android collections., link below

k4Z3666 said:
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
Click to expand...
Click to collapse
I tried other USB Ports and also rebooting. It was working just fine - it seems like a driver problem to me.
My notebook is dead, but I'll try using someone else computer.
Does Odin runs in Windows XP? I might try it in my virtual box - I doubt that it will work, but it is the best thing I have to do untill tomorrow.

I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]

KainFromNod said:
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah

Ok, I'm posting it here just to leave a reply and reference for future generations, as my problem was solved.
xsenman said:
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
I used a firmware from my country (available here: sammobile.com/firmware/?page=3&model=GT-I9000B&pcode=ZTO&os=1&type=1#firmware) and I wiped the cache (I'm not sure what this means, but I believe it is the 2 options on volume up+menu+power)
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
Click to expand...
Click to collapse
k4Z3666 said:
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
Click to expand...
Click to collapse
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
yahyoh said:
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Click to expand...
Click to collapse
ICS wasn't faster here - it was laggish and always crashed some common apps (gallery, music player). I believe that the firmware wasn't completely "done" as it was being adapted from another version (my phone is brazilian) and some functionalities that it has (i.e. digital TV) wasn't available.
What I done to correct the boot was simple (I found a tutorial in a brazilian site, so it had all the roms that I needed).
1) Used a PIT and a stock rom to get it back to factory version;
2) Upgraded to Froyo (original) - That was kind of a mistake, the tutorial said to do it because then KIES would update it automatically to Gingerbread. The phone was fully functional, but KIES said that it couldn't update it (it recognized the phone and everything).
The tutorial stoped there, but since I had the ROM, I used Odin to install Gingerbread (the one that was looping) and it was done.
Now I need to remember how to root it because there are some dumb apps who can't get away (i.e. Orkut app, some demo games).
Thank you all for the help!

KainFromNod said:
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
Click to expand...
Click to collapse
From recovery you can always try to flash another kernel, that would probably resolve things too. Anyways the problem's solved, glad to help

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.