Database Develop

[Q] Semi bricked I9000

Hello everyone,
Two days ago I try to make a firmware update to Gingerbread trough Kies.
After everything is finished the phone start, shows the main logo (the white one), start that animation with "S" and come on a black screen. Time to time he vibrate 2 or 3 times and only the back and menu buttons are illuminated.
1. Cannot use 3 buttons to get into download or recovery mode
2. Cannot put the phone in USB debugging (obviously)
3. For unknown reason I cannot instal ADB drivers (win7 shows the yellow triangle)
4. Samsung drivers are installed on Modem and USB (shows Samsung)
5. On "devices" , can be seen but again no ADB
6. ODIN see it on com8 but again for some reasons it wont work (probably because he work in download mode )
7. SDK is installed
8. ADB shows "no devices found"
9. No other button combination works (home+down , up+down +battery in + USB plugged ... etc)
Any suggestion/help ?
Thank you very much for reading and hopefully Ill get some help
Best regards,
Andrew

Have you tried "emergency reset" or whats it called in Kies?
Did you have the 3-button combo before the flash?
If so try to remove the battery and then with it removed press the combo and insert the battery-
Maybe you refer to that in number 8?
A JIG will for sure help you to get into download mode.
Good luck.
/qsec

Hello and thank you,
3 buttons combo didnt work before
Kies stays with the status "connecting" but no phone shows up in it.
Thankx,
Andrew

You in the UK .
Gingerbread no update via Kies its not released yet .
Kies has Firmware recovery or some such tab.
Was your phone lagfixed ..
Did your phone have custom rom .
Current condition of phone looks like you need download recovery jig from front page .
Or if no lagfix no custom rom then Samsung service centre failed Kies flash .
jje

Yes lag fixed OCLF
And Kies said something about firmware update. I do have Froyo 2.2 and the logical thing was Ginger so thats why i thought it is.
Thank you,
Andrew

antraian said:
Yes lag fixed OCLF
And Kies said something about firmware update. I do have Froyo 2.2 and the logical thing was Ginger so thats why i thought it is.
Thank you,
Andrew
Click to expand...
Click to collapse
Lagfix a no no thats what F*** your phone .
Froyo 2.2 next update 2.2.1
Download recovery jig .
jje

JJEgan said:
Lagfix a no no thats what F*** your phone .
Froyo 2.2 next update 2.2.1
Download recovery jig .
jje
Click to expand...
Click to collapse
Never had any problems with lagfix, but i guess if you do things in the wrong order without removing it before upgrading.
OP, did you follow any instructions, or just do it blind?

Never had any problems with lagfix
Your choice but failing to remove lagfix before flashing is a well posted problem on XDA .
jje

This is very true.
It was stupid of me flashing with lag fix installed evendo I read that YOU MUST remove lagfix before do it ....
Cheers,
Andrew

antraian said:
This is very true.
It was stupid of me flashing with lag fix installed evendo I read that YOU MUST remove lagfix before do it ....
Click to expand...
Click to collapse
Worse, you flashed without enabling 3 button combo prior. Due to that you're unable to get into download nor recovery mode unfortunately. So unless that emergency firmware option in Kies won't help you will have to build or buy yourself a jig dongle/cable which is plugged into the phone by USB to force download mode. Check on ebay UK, there are surely some people selling professionally built ones for just a few pounds (got one myself from US for just $7 or so).
Once you have that, re-flash with Odin.
And once your phone is OK again, get that 3 button combo working! I used this method successfully. Soft bricked the first time thanks to using USB hub instead of direct USB as it wasn't mentioned in the stickies sadly. Yet thanks to the Jig I got prior I tried again and flashed my phone to enable 3 button combo forever.
P.S.: there is something else very vital I came across recently and am glad I saw it in time: backup of the /efs folder which contains IMEI etc:
http://forum.xda-developers.com/showthread.php?t=859914
(I hope that's mentioned in the stickies somwhere but if so I would have seen it unless I missed one)
After reading in these forums for hours before trying my very first flashing I might want to write a comprehensive guide...

[Q] Captivate Soft Brick - Need a rooted Odin solution.

Hi
My brother (a no-geek) has a captivate, and lives in a different city (I donot have physical access to the phone). He visited me few weeks ago and I installed CM-7 on his phone, i know my bad. Some of his videos were not working, so i asked him to update to the latest CM-7 build. He download the build, saved it on int sd_card and used ClockWork Recovery to install the selected ROM. Upon reboot it entered in never-ending splash screen. I found couple of odin ROMs, and posted him link, we tried to flash them, but no good.
Status --
The COM ports are detected, but the process at times halts at <SET PARTITION> at times at <SET UP>... at times all thread completed successful would show up as soon as hitting START.
I dont have a captivate, can someone please suggest a sure shot solution and post me a link for ODIN, with a root rom. I am using Team Whiskey on my Vibrant, and I prefer stable modified ROM because of its features and power.
I can explain him the process on skype using desktop sharing, but the ROM should be good. Thankyou very much in advance.

if he can access recovery, try wiping everything thru recovery then start again

Phone is in Soft Brick state.
Phone is in Soft Brick state. So i cannot boot into the phone and go to CW recovery.

What he needs is just a stable usb connection that's how he got to this point, bad communication between the phone and computer. On cm7 I beleive you need the nexus s drivers installed. Also make sure it's plugged into a usb port that's attached directly to the motherboard (back of pc, port 1 on laptop)

@studacris
I think the drivers are already installed good. The connection is also good, as i can the COM port detection in the ODIN, with one of the boxes changing its colour from NO-COLOUR to YELLOW-COLOUR.
I think the ROM builds are not good. They go action-less during flashing, actually nothing (progress bar) comes on phone, it keeps showing the Downloading screen, endlessly. Odin usually is stuck at at <SET PARTITION> at times at <SET UP>...
Can someone post a link for a test one click odin. Well i would prefer one click.

You did try DG's JF6 one click, thats the only one I use, how are you establishing dowload mode on the phone or are you even doing this.

REMY4223 said:
I would suggest to Odin back to stock then update to Froyo via Kies.
Click to expand...
Click to collapse
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament

Ragin Caucasian said:
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Click to expand...
Click to collapse
+1 If you read the OP the problem is he can't flash back to stock he is having problems flashing anything period, @ the OP correct me if I'm wrong but I have a strong hunch that you are leaving out some pretty crucial steps, I have a feeling that you are not putting the phone into download mode, I also believe that you are gonna need to make a jig and pay a visit to your brother to help him out especially if its bricked the same way mine just was flashing with cm7 roms. But if you are getting a com port to show without having to put in download mode then you are farther along in the boot process. If this is the case you may be able to adb into recovery do a full wipe excluding /boot and reflash. Will the PC recognize the phone with it in its current boot locked state? If so then recovering should be somewhat of a breeze.
http://forum.xda-developers.com/showthread.php?t=829392 read this post it may help otherwise there are tons others

- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.

viveksharma2108 said:
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
Click to expand...
Click to collapse
Try putting the phone into download mode after you open Odin. Which version of Odin is this? Also, installing the nightly build of CM7 again often fixes the boot loop on the newer builds. I would try that if you can get to recovery.
Sent from my SGH-I897 using XDA Premium App

[Q] OH NO! Another noob bootloop thread :p

Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus

I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.

ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...

Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again

I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.

For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App

cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...

Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA

TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business

*removed double post

studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.

You have to hit enter at the Right moment, it takes practice

Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA

Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA

If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.

Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )

How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.

Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA

Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.

When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium

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