Database Develop

Stuck after bad rom flash, odin wont recognize

So heres the synopsis on what my issue is:
first of all-
phone: Samsung Captivate build 1010
current OS: (botched install of Darky 8)
problem: no recovery menu capability, stuck in reboot loop (will not go past ATT Logo), can go into download mode but odin does not see the phone
I botched a Darky 8 install. I attempted to install the rom to my captivate via rom manager but to no avail. I then decided to give the install a try via clockwork and had luck. the rom was not to my liking so I went to mount the internal sd and proceeded to delete all files internally to make a fresh odin install possible (as I always do). It was at the time of restarting my phone that I realized the rom I install was accidently the I9000 rom on my captivate, thus forth being a possible source of my issue. Currently I have a phone that is stuck in a reboot loop any time I plug it into a power source, or attempt to power it on. While in said loop the phone will not go past the ATT logo, and as it cycles, at the I9000 screen a robot voice pops up saying restore system. Ive attempted to reflash back to stock with the stock captivate odin3 OCD, but I am having no luck with the phone being recognized by odin (run as admin). I am currently running Mac OSX 10.6 with windows vista on Virtual Box 4.0, and have had luck previously with flashing the phone back to stock after I decided to try new versions of cognition. Currently my phone can only go into download mode and not recovery due to the boot loop. please help asap, this my only means of communication with my family on the other side of the states

Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.

CB650 Wolf said:
Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.
Click to expand...
Click to collapse
going to try, redoing my virtual box in hopes that it was something stupid, and also trying the other usb port on my macbook.

Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App

butchatbg said:
Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.

s0n1cm0nk3y said:
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.
Click to expand...
Click to collapse
Try using ADB..

Edit...misread

rickysa2000 said:
Try using ADB..
Click to expand...
Click to collapse
sadly I wished that work, I tried using adb reboot recovery, and in the attempt, the phone was not able to be detected. Should this be done in hopes to catch it at the right time in the boot loop or in download mode. Ive tried both.

So can you still get into Download mode? If so I would suggest finding another computer to use. For some reason, last week, my PC that I have been using to flash for months decided not to recognize my phone in download mode.
So I switched to my laptop, loaded the ROM. I tried reinstalling drivers and all kinds of stuff but nothing worked. I backed up my PC and re-imaged it and it's working again.

Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.

avgjoegeek said:
Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.
Click to expand...
Click to collapse
Odd I was told your perfectly fine to do so, and then from there do an odin flash. Ive done it before, but oddly enough I think what screwed me was because I did it during while in the rom, vs while in 2.1. I just wanted to try to get a clean slate. doing the master clear code from samsung never really deletes the left overs from say clockwork and such on my internal sd.

problem was the virtual machine, plugged it into a friends computer and all was done within a couple of mins. leave it to emulation falling short :/

[HELP] SGS stuck at Odin!

Hi all,
I messed up my SGS GT-I9000 yesterday. i was running Darky's Gingerbread & accidentally flashed a theme meant to be for Froyo, and as a result got stuck into a boot loop.
I flashed back the Darky's resurrection to fix the problem but something happened during the Odin process and the phone soft bricked.
Now, I don't get the battery charging sign when connected in power off, there's no response on power button, no response on 3 button recovery combo.
But I am able to get to download mode through 3 button combo. I have tried diff Odins with diff firmwares (stock / resurrection etc) but every time the progress stucks at Factoryfs.rfs (with a teeny bit of blue progress bar on the device).
I have tried different methods on the net but nothing seems to be working since yesterday.
Is there any hope? would really appreciate any help

why are you posting this is the dev section?

Belong to Q&A's. Use 3 file firmware and tick repartition in odin and you are good to go.

junooni said:
Hi all,
I messed up my SGS GT-I9000 yesterday. i was running Darky's Gingerbread & accidentally flashed a theme meant to be for Froyo, and as a result got stuck into a boot loop.
I flashed back the Darky's resurrection to fix the problem but something happened during the Odin process and the phone soft bricked.
Now, I don't get the battery charging sign when connected in power off, there's no response on power button, no response on 3 button recovery combo.
But I am able to get to download mode through 3 button combo. I have tried diff Odins with diff firmwares (stock / resurrection etc) but every time the progress stucks at Factoryfs.rfs (with a teeny bit of blue progress bar on the device).
I have tried different methods on the net but nothing seems to be working since yesterday.
Is there any hope? would really appreciate any help[/QUOTE
I had same problems, try flashing on a Windows XP system
that was the right solution for me! ...I'm on Windows 7 64, this makes randomly problems for me
Regards
Sonic76
Click to expand...
Click to collapse

sonic76 said:
junooni said:
Hi all,
I messed up my SGS GT-I9000 yesterday. i was running Darky's Gingerbread & accidentally flashed a theme meant to be for Froyo, and as a result got stuck into a boot loop.
I flashed back the Darky's resurrection to fix the problem but something happened during the Odin process and the phone soft bricked.
Now, I don't get the battery charging sign when connected in power off, there's no response on power button, no response on 3 button recovery combo.
But I am able to get to download mode through 3 button combo. I have tried diff Odins with diff firmwares (stock / resurrection etc) but every time the progress stucks at Factoryfs.rfs (with a teeny bit of blue progress bar on the device).
I have tried different methods on the net but nothing seems to be working since yesterday.
Is there any hope? would really appreciate any help[/QUOTE
I had same problems, try flashing on a Windows XP system
that was the right solution for me! ...I'm on Windows 7 64, this makes randomly problems for me
Regards
Sonic76
Click to expand...
Click to collapse
i've been flashing roms upto thrice a day on the same system with no problems.
the issue started when i flashed the froyo version of the Valle-mod honeycomb theme onto a gingerbread rom by mistake.
Click to expand...
Click to collapse

You can belive me, flash with n Windows XP machine and your problem gone!
Regards
Sonic76

sonic76 said:
You can belive me, flash with n Windows XP machine and your problem gone!
Regards
Sonic76
Click to expand...
Click to collapse
The OS has no effect on how well ODIN works. Go spread your no fact assumptions somewhere else.

sonic76 said:
You can belive me, flash with n Windows XP machine and your problem gone!
Regards
Sonic76
Click to expand...
Click to collapse
hmmm you're so sure about this that i guess its worth a try. got nothing to lose as it is. now i gotta get my system rebuilt with xp
btw, since the phone doesn't even charge, and i've been trying a million ways to revive it since yesterday, the batt just died and now even Odin is out of the question as the set doesn't charge the battery.
Just made myself a portable desktop charger to charge the battery. lets hope i find a solution soon

Furry Atom said:
The OS has no effect on how well ODIN works. Go spread your no fact assumptions somewhere else.
Click to expand...
Click to collapse
But your 64bit system has an affect, but if you know the problem why ask
for help here?
cheers

Derptard said:
But your 64bit system has an affect, but if you know the problem why ask
for help here?
cheers
Click to expand...
Click to collapse
I'm not the OP. I didn't ask anything.
Oh and BTW having an x64 system still won't affect ODIN. Because x64 versions of windows have an emulation layer that runs x86 apps natively.
If that were the case then every single video game I own except for Crysis wouldn't run properly on my computer.

Furry Atom said:
I'm not the OP, idiot. I didn't ask anything.
Oh and BTW having an x64 system still won't affect ODIN. Because x64 versions of windows have an emulation layer that runs x86 apps natively.
If that were the case then every single video game I own except for Crysis wouldn't run properly on my computer.
Click to expand...
Click to collapse
Sorry, i have read wrong! ;-)
I has had the same problem like junooni, Odin stucks and the phone ends withe an display in different colors, some people says that they have nor problem with Odin 1.3 on 64bit systems, but i had no luck, i flashed many times without a problem with Odin 1.8 and Windows7 64bit but from one day to the other
Odin sucks! ...I take an old WindowsXP machine from a friend and
i have noo problem to reactivate my phone!

Furry Atom said:
I'm not the OP. I didn't ask anything.
Oh and BTW having an x64 system still won't affect ODIN. Because x64 versions of windows have an emulation layer that runs x86 apps natively.
If that were the case then every single video game I own except for Crysis wouldn't run properly on my computer.
Click to expand...
Click to collapse
thanks for your help guys but i guess i've got to keep looking....not willing to give up so easily

Flash jm9.
Sent from my GT-I9000 using XDA Premium App

woolf clubs said:
Flash jm9.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
a link would be appreciated

Try to remove the battery for a few minutes before every flashing using Odin for your case.

junooni said:
a link would be appreciated
Click to expand...
Click to collapse
Everything's on samfirmware.com . Please don't tell me you started flashing custom roms without knowing that.

erm~
Just.. put ur phone in download mode and use odin flash..
flash the official firmware 2.2... then its will not brick..

I think u mess up your kernel and partition what you can try is open kies and connect your phone that's a option on kies for recovery try it else you have to bring your phone to ssc.

Have the firmwares you've tried contained a (modem, CSC, and Code) part?
Also what is ticked in odin?

Ibanez33 said:
Have the firmwares you've tried contained a (modem, CSC, and Code) part?
Also what is ticked in odin?
Click to expand...
Click to collapse
i have the stock firmware from samfirmware.com which is just the PDA file.
I also found a bootloader file in one of the threads that is supposed to have 'phone bootloader update' ticked in Odin.
i've tried in every possible combination but no response. the device doesn't even charge the battery. i can get into download mode but that's about it

[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

[Q] N7000 bricked - No USB connection possible

ok first things first, imma noob, and i did a stupid thing.
It started in last summer when i wasnt able anymore to connect the N7000 to my WIN 7 64bit (probably after an update to ICS /JB).
Well since i never needed to transfer files (64GB-sdxc) i didnt care much about it. but then in last times my phone/ram cache was full of so much unblockable bootloaded crapware so that i wanted to switch from a official 4.1.2 firmware to cyanogen. But since my USB wasnt working it wasnt that easy.
Side note: the USB-port was ****ed up before (short-circuit, screen woke up due to fake-loading). i fixed that by luck and some dark magic.. so of course i thought the connection problem were because oif the broken jack.
The day before yesterday i tried for 8 hours anything i could find to install another bootloader and flash CM (CWM / TWRP / Triangle away / minimal adb/fastboot etc.); didnt work, CWM seemed to boot up but loading failed all the time at 1/3rd of the bar at screen went black.
Yesterday my friend came over and i tried to use his USB-jack to connect my phone to my Pc, which failed. THEN i put the "broken" one from mine in his N7000; that was efficacious, everything worked fine, so the USB-jack wasnt the problem.
Later i had, out of frustration, moronism, and anger, the glorious idea to download and flash another (older) Kernel via mobile odin to install an old gingerbread stock rom on it afterwards.
That was stupid as i know now, all i can do now is enter download mode, but without USB-connectivity and the stock bootloader with the options reboot system / update from sd / wipe data / wipe cache / test redbend fota(FS) and boot, which stucks at the N7000-screen.
After i managed to **** things up i found an article which describes my (now former) USB-problem perfectly. it says to put in a special number combination on the phone to get to phoneUtil and then switch from modem mode to pda mode. i knew this screen before but i couldnt find it at the preferences on JB.
Now comes my question: What could be done to unbrick my phone? is there any help?

Can you not try another USB cable? Try cleaning out the pins and see if it works. Then flash speedmod.
Sent from my GT-N7000 using Tapatalk

backstreetboy said:
Can you not try another USB cable? Try cleaning out the pins and see if it works. Then flash speedmod.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
>Just to clarify: with USB-Jack i mean the USB-Port with the connector to the motherboard; sorry if i misused the word
I dont think so cause we used only his cable when he was here and my phone neither connected with mine nor with his USB-Jack, but both Jacks worked on his phone.
Pro-question: Is there a difference between (usual) USB-connection in booted mode and connection in download mode? i mean is download mode something like a "safe mode" where the USB doesnt need to run on 100% availabilty? Should i try to find the phone via Odin in downdload mode again by using his cable? i dont think this could work else.

Samsung galaxy note gt-n7000 bricked. Need HELP!!
The phone shows " Firmware upgrade issue encountered an issue. Please select recovery mode in Kies & try again". I cant go to recovery mode ie. vol up+home+power. THings I have tried:
1. with Kies the device isnt recognised. I have updated the driver as well.
2. with odin every thing fails... flashing "all samsung recovery.tar", flashing stock jelly bean, flashing .pit file
I have googled for days and tried many things but isnt working. Need help