[Q] CASUAL/odin will not detect Note 2 - Verizon Samsung Galaxy Note II

Long story short, using 2 different computer, 2 different USB cables, and several different USB ports, I cannot get either casual or odin to detect my phone. The computers themselves recognize it, but neither program will. I have spent hiurs going through threads and try whatever I have found but nothing has changed this. Please help, I'll answer any questions you have regarding this as I'm sure more info is neccessary, but at this point I just don't know what to do and am about to go back to my DNA if I can't get this straightened out. Thanks for any help/suggestions.

jewboy69 said:
Long story short, using 2 different computer, 2 different USB cables, and several different USB ports, I cannot get either casual or odin to detect my phone. The computers themselves recognize it, but neither program will. I have spent hiurs going through threads and try whatever I have found but nothing has changed this. Please help, I'll answer any questions you have regarding this as I'm sure more info is neccessary, but at this point I just don't know what to do and am about to go back to my DNA if I can't get this straightened out. Thanks for any help/suggestions.
Click to expand...
Click to collapse
Have you installed Kies? If so try uninstalling it and then redownloading and reinstalling. Thats what worked for my friend with his N2, maybe it'll help you.
Alsoif you're on WinXP it Casual wont work from what I have gathered.
Sent from my SCH-I605 using XDA Premium HD app

nope...
I have uninstalled/reinstalled kies, and the 2 computers I've used are running win7/8. Thanks but it's gotta be something else.
shangrila500 said:
Have you installed Kies? If so try uninstalling it and then redownloading and reinstalling. Thats what worked for my friend with his N2, maybe it'll help you.
Alsoif you're on WinXP it Casual wont work from what I have gathered.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse

jewboy69 said:
I have uninstalled/reinstalled kies, and the 2 computers I've used are running win7/8. Thanks but it's gotta be something else.
Click to expand...
Click to collapse
Some computers just don't play well with Odin, Casual, Hemidall, and/or the Note 2. On my work computer I've done everything under the sun to get it going with Casual, and it just fails on one item or another. However a second computer at work and one of my home computers work like a champ. You might just have two bummer machines for the process. When it does work, it is a thing of beauty.
If I were you I wouldn't go back to the DNA. I really love that phone, but I haven't once regretted switching to the Note 2. Once you get used to the size, things like the stellar battery life and availability of customization options come into focus.
Sent via Note2 with XDA Premium

Related

[Q] USB Problem - KIES not recognizing the phone

-----------------------------------------------------------------------------------------------------------------
So I am on stock but somehow, KIES wont work. It keeps saying connecting, but wont go further than that.
USB debugging is unchecked so I am sure that it not the problem. I heard T-Mobile for ICS upgrade, so I just wanted to be prepared for ICS update for ATT, but idk, why KIES is not working.
Any suggestions?
Bent USB prong in the phone? I've had to adjust mine several times since I got it launch day. Or hardware failure. When my USB was bent it could still charge via a wall charger
Sent from my SGH-I777 using Tapatalk 2
yeah I think it works when i use at a certain angle.
I am trying to go back to the stock rom and hopefully i can return it, but for some reason Odin is not recognizing it. I mean the yellow box of COM:0 does not show up in the "I777UCKH7-CL503881-No-BL.exe"
Do you know the reason for this?
Missing driver.
IIRC I believe you were supposed to install KIES and another Samsung driver...but I remember using my phone on a netbook without it and it worked...
Try installing the USB driver on the official samsung website? I can't post links yet or I would link it...
jjack0310 said:
yeah I think it works when i use at a certain angle.
I am trying to go back to the stock rom and hopefully i can return it, but for some reason Odin is not recognizing it. I mean the yellow box of COM:0 does not show up in the "I777UCKH7-CL503881-No-BL.exe"
Do you know the reason for this?
Click to expand...
Click to collapse
There can be multiple possible reasons. You've eliminated some of them. Could be a failing usb port on the phone, bad cable, etc.
If you can't get usb to work, you can flash back to stock using mobile odin. I assume you are rooted. Just download the one-click downloader to your phone over wifi, or use dropbox or something to get it onto your phone. Mobile odin will recognize and flash from the one-click downloader. There is even a guide in the general section on how to do this.
creepyncrawly said:
There can be multiple possible reasons. You've eliminated some of them. Could be a failing usb port on the phone, bad cable, etc.
If you can't get usb to work, you can flash back to stock using mobile odin. I assume you are rooted. Just download the one-click downloader to your phone over wifi, or use dropbox or something to get it onto your phone. Mobile odin will recognize and flash from the one-click downloader. There is even a guide in the general section on how to do this.
Click to expand...
Click to collapse
Creepy just posted this while I was getting you the link for the guide to return to stock with no PC: http://forum.xda-developers.com/showthread.php?t=1691659.
I returned to stock, and I think I figured out the problem as well.
The problem I am quite sure is the USB port on the phone. Like I said, when I keep the USB cable connected at a certain angle, it works just fine.
I will just have to live with it now I think because ODIN displays custom binary installed and the count is 2, so I dont think ATT will let me exchange the phone for a new one.
jjack0310 said:
I returned to stock, and I think I figured out the problem as well.
The problem I am quite sure is the USB port on the phone. Like I said, when I keep the USB cable connected at a certain angle, it works just fine.
I will just have to live with it now I think because ODIN displays custom binary installed and the count is 2, so I dont think ATT will let me exchange the phone for a new one.
Click to expand...
Click to collapse
ehhh, its worth a try. Thats a hardware failure, the one that samsung is known for. Mine is starting to go out too.
I've returned 1 rooted phone with this issue, and warranty'd 1 rooted one that had a broken LCd.
These were Infuse's but same damn samsung problem.
MotoMudder77 said:
ehhh, its worth a try. Thats a hardware failure, the one that samsung is known for. Mine is starting to go out too.
I've returned 1 rooted phone with this issue, and warranty'd 1 rooted one that had a broken LCd.
These were Infuse's but same damn samsung problem.
Click to expand...
Click to collapse
Yeah I am surprised these hardware problem are so common.
No wonder most people are crazy about Apple sells so many iPhones
I had the very same issue as you are describing.
All you need to do is tweak the USB port a little. Did mine about 3 or 4 months ago and have not had to touch it since.
Use a small precision screw driver, fold a couple layers of Kleenex over the tip and gently bend it towards the screen side of the phone.
It WILL work perfect after that.
Sent from my SGH-I777 using xda premium
dschreiber69 said:
I had the very same issue as you are describing.
All you need to do is tweak the USB port a little. Did mine about 3 or 4 months ago and have not had to touch it since.
Use a small precision screw driver, fold a couple layers of Kleenex over the tip and gently bend it towards the screen side of the phone.
It WILL work perfect after that.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Will try it for sure. Thank you for mentioning which way to bend the port towards. lol
So I am on stock but somehow, KIES wont work. It keeps saying connecting, but wont go further than that.
USB debugging is unchecked so I am sure that it not the problem. I heard T-Mobile for ICS upgrade, so I just wanted to be prepared for ICS update for ATT, but idk, why KIES is not working.
Any suggestions?
jjack0310 said:
So I am on stock but somehow, KIES wont work. It keeps saying connecting, but wont go further than that.
USB debugging is unchecked so I am sure that it not the problem. I heard T-Mobile for ICS upgrade, so I just wanted to be prepared for ICS update for ATT, but idk, why KIES is not working.
Any suggestions?
Click to expand...
Click to collapse
Try uninstalling/reinstalling. That would be my first step.
Sent from my SGH-I777 using xda premium
dschreiber69 said:
Try uninstalling/reinstalling. That would be my first step.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I did that like two times already.
I even flashed a different stock Rom. I mean I started with The kernel + rooted UCKH7
but then since it didnt work, I tried Kernel + cache + rooted UCKK6 package from:
forum.xda-developers.com/showthread.php?t=1286432

[Q] Trouble Syncing AT&T S3 to Kies on PC... Anyone else?

Title says it all. I've tried re installing 20 times(not literally) and re installing the drivers, rebooting the phone, the computer, nothing. Had no problems with my S2. Anyone else having similar issues and a possible work around? Thanks.
I had the same issue and swore it was my phone. I tried different cables and even a factory reset, however I plugged in my phone into my work laptop and it synced up just fine.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I also had this issue. Randomly one day I connected it however and kiss said connecting and all of a sudden it was working. Have you tried to remove the drivers in safe mode?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Same issue here but I'm using sprint version
Sent from my SPH-L710 using xda app-developers app
dmize said:
I also had this issue. Randomly one day I connected it however and kiss said connecting and all of a sudden it was working. Have you tried to remove the drivers in safe mode?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Haven't tried removing them in safe mode. Sorry to sound stupid but what difference does it make removing them from safe mode? I'll give it a whirl but all the errors I get are on the phones end. I couldn't even copy music to my sdcard. I had to remove it, use the adapter and load it right on it from the port on my laptop.
statusnone said:
Haven't tried removing them in safe mode. Sorry to sound stupid but what difference does it make removing them from safe mode? I'll give it a whirl but all the errors I get are on the phones end. I couldn't even copy music to my sdcard. I had to remove it, use the adapter and load it right on it from the port on my laptop.
Click to expand...
Click to collapse
statusnone said:
Title says it all. I've tried re installing 20 times(not literally) and re installing the drivers, rebooting the phone, the computer, nothing. Had no problems with my S2. Anyone else having similar issues and a possible work around? Thanks.
Click to expand...
Click to collapse
romulusram said:
I had the same issue and swore it was my phone. I tried different cables and even a factory reset, however I plugged in my phone into my work laptop and it synced up just fine.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Had the same issues as well. Tried different cables including the one in the box, deleted and tried to reinstall drivers, checked regedit, and finally called Samsung Advanced Tech support, what a joke by the way. After 20 minutes said our only option is to do a factory reset which is exactly what I didn't want to do. But, it is fixed for now...

My phone is partially a dud

I don't know how many times I posted because of this, but I think I'm done trying to fix it.
My phone, regardless of ROM, computer, or cable, etc, will isn't seen by any computer
I've installed all the drivers (through HTC sync) multiple times and on multiple computers. I've tried new roms, stock roms, nothing. New cables old cables, nothing. I've even formatted my SD cards and tried that way, nothing. I've tried the wireless ADB, and I get "<waiting for device>" which of course is never going to be found. I don't really think there's anything else I can do at this point but assume that it's my phone's USB port is damaged, can I replace that though?
Any ideas? And also someone could tell me about replacing hardware on this phone, that'd be great.
Thanks anyone.
ο χάκερ said:
I don't know how many times I posted because of this, but I think I'm done trying to fix it.
My phone, regardless of ROM, computer, or cable, etc, will isn't seen by any computer
I've installed all the drivers (through HTC sync) multiple times and on multiple computers. I've tried new roms, stock roms, nothing. New cables old cables, nothing. I've even formatted my SD cards and tried that way, nothing. I've tried the wireless ADB, and I get "<waiting for device>" which of course is never going to be found. I don't really think there's anything else I can do at this point but assume that it's my phone's USB port is damaged, can I replace that though?
Any ideas? And also someone could tell me about replacing hardware on this phone, that'd be great.
Thanks anyone.
Click to expand...
Click to collapse
Does it charge over USB?
AshtonTS said:
Does it charge over USB?
Click to expand...
Click to collapse
You mean if I plug it into a USB port will it charge?
Yes
All I know is that in my experience my phone stopped showing when I installed HTC drivers. It only came back up when I reinstalled windows. Try more computers before you determine it as a physical defect
Sent from my ADR6425LVW using xda app-developers app
cincyelite22 said:
All I know is that in my experience my phone stopped showing when I installed HTC drivers. It only came back up when I reinstalled windows. Try more computers before you determine it as a physical defect
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I have tried 5, and I'm positive it isn't a problem with any of them.
If it charges over USB I have a hard time thinking the USB port has issues... There is one common denominator over the 5 computers you have tried
I had the same issue, unfortunately it was an issue with the USB port. I went through many, many cables and PCs ( xp, vista, win7) and I finally gave up. Called big red and got a warranty replacement
Sent from my ADR6425LVW using Tapatalk 2
AshtonTS said:
If it charges over USB I have a hard time thinking the USB port has issues... There is one common denominator over the 5 computers you have tried
Click to expand...
Click to collapse
I appreciate your input, but I seriously doubt it.
Computer 1: very old, used 3 other phones, all no problems, ReZound isn't seen
computer 2: not used much, used 1 other phone with it, ReZound ins't seen
Computer 3: Brand spanking new, ultimate specs, fresh driver intallation, ReZound isn't seen (also had 2 different software versions installed - Win 7 Home Premium and Ultimate)
Computer 4: Not used, barely a year old, fresh driver install, ReZound still isn't seen
Computer 5 - Laptop: Same deal, newdriver, nothing.
TheBr0ken said:
I had the same issue, unfortunately it was an issue with the USB port. I went through many, many cables and PCs ( xp, vista, win7) and I finally gave up. Called big red and got a warranty replacement
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I don't have warranty
I think I'm screwed
ο χάκερ said:
I appreciate your input, but I seriously doubt it.
Computer 1: very old, used 3 other phones, all no problems, ReZound isn't seen
computer 2: not used much, used 1 other phone with it, ReZound ins't seen
Computer 3: Brand spanking new, ultimate specs, fresh driver intallation, ReZound isn't seen (also had 2 different software versions installed - Win 7 Home Premium and Ultimate)
Computer 4: Not used, barely a year old, fresh driver install, ReZound still isn't seen
Computer 5 - Laptop: Same deal, newdriver, nothing.
Click to expand...
Click to collapse
Idk man I always have trouble with the drivers for windows.. That's why I use a Mac anyway does it say like android device or android 1.0 or HTC USB Device or something to that effect when you plug it in WITHOUT installing the drivers?
AshtonTS said:
Idk man I always have trouble with the drivers for windows.. That's why I use a Mac anyway does it say like android device or android 1.0 or HTC USB Device or something to that effect when you plug it in WITHOUT installing the drivers?
Click to expand...
Click to collapse
Nothing, the phone doesn't even realize it's being connected, although if you restart the phone with a cable plugged in (whether or not it's plugged into a wall or computer) the phone pops up with the options to charge only, etc. None of the options do anything though.
ο; χάκε;ρ;29430152 said:
I don't have warranty
I think I'm screwed
Click to expand...
Click to collapse
Just tell them it's a defect with the rezound they'll replace it with a refurb. They cover it as long as its not physical damage you did which isnt your case.
Sent from my ADR6425LVW using xda app-developers app
cincyelite22 said:
Just tell them it's a defect with the rezound they'll replace it with a refurb. They cover it as long as its not physical damage you did which isnt your case.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
And what about the software changes? I can't RUU back because I can't re-lock or run the .exe
ο χάκερ said:
And what about the software changes? I can't RUU back because I can't re-lock or run the .exe
Click to expand...
Click to collapse
Brick it
ο; χάκε;ρ;29430152 said:
I don't have warranty
I think I'm screwed
Click to expand...
Click to collapse
How can you not? Us it physically damaged? Factory warranty should have you covered if not
Sent from my ADR6425LVW using Tapatalk 2
TheBr0ken said:
How can you not? Us it physically damaged? Factory warranty should have you covered if not
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Because he rooted it
ο; χάκε;ρ;29430501 said:
And what about the software changes? I can't RUU back because I can't re-lock or run the .exe
Click to expand...
Click to collapse
Why can't you? It's time consuming but you can. Run the ruu to get yourself back to stock. Lock the bootloader and s-on. Then you will be stock, unrooted and bootloader will say either relocked or tampered or whatever. Root it. S-off with junipbear but do not install the modified hboot. Then ruu again. You will now be completely stock, unrooted and bootloader will say locked. Worked perfectly fine for me.
Sent from my ADR6425LVW using Tapatalk 2
TheBr0ken said:
Why can't you? It's time consuming but you can. Run the ruu to get yourself back to stock. Lock the bootloader and s-on. Then you will be stock, unrooted and bootloader will say either relocked or tampered or whatever. Root it. S-off with junipbear but do not install the modified hboot. Then ruu again. You will now be completely stock, unrooted and bootloader will say locked. Worked perfectly fine for me.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I can't lock my bootloader because I can't make contact with my computer through a usb cable, that's the whole problem
AshtonTS said:
Brick it
Click to expand...
Click to collapse
That's what I was thinking actually
Erase everything so it doesn't even turn on, then just be like "Iunno what happened"
ο; χάκε;ρ;29430276 said:
Nothing, the phone doesn't even realize it's being connected, although if you restart the phone with a cable plugged in (whether or not it's plugged into a wall or computer) the phone pops up with the options to charge only, etc. None of the options do anything though.
Click to expand...
Click to collapse
If your phone doesn't realize it's plugged in, then you got a defect.
Verizon usually doesn't check for unlock/root and many people have successfully gotten replacements for rooted phones.
Sent from my ADR6425LVW using xda app-developers app

[Q] Bricked fassy - tried everything

So, I've been trying for months to fix this thing. Read every post I could find so I wouldn't have to ask for help. Yet here I am. On my knees.
The lowdown:
-Fascinate was not previously rooted.
-Odin will not recognize it.
-Had some issues with the drivers b/c of windows 8, but was able to install from zadig using advanced startup options to bypass driver verification.
-Tried to flash back to stock gingerbread with Heimdall 3 times. Said it was successful everytime. I did use the same usb port that I used for the drivers and it is on the motherboard. And I used stock cable.
-When I try to boot up the phone after flash attempts, some text scrolls across the screen and it says something about "data wipe not successful." It scolls quickly, so I'm not sure what all it says. (One of my first attempts invloved trying to install cwm, so maybe that's why scrolling txt? It looks similar)
-Now, it boots to the little android dude with a white box and an arrow pointing out of it. I'm developing murderous feelings towards him.
In conclusion, I am a noob but have tried to educate myself as much as possible. Please be gentle.
Any ideas out there?
Have you followed this guide? http://forum.xda-developers.com/showthread.php?t=1238070
Read through this.
Sent from my SCH-I500 using xda app-developers app
noobchef said:
Have you followed this guide? http://forum.xda-developers.com/showthread.php?t=1238070
Read through this.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
I'm assuming you're referring to section 5? I have read through that guide, but odin doesn't recognize the phone.
OK. Last time that happened to me it was a cable issue. I had to use a cable i got from a store. Try to put it in download mode and plugging it into the wall before your computer.
Sent from my SCH-I500 using xda app-developers app
The older androids are much easier to brick, the newer ones have more sophisticated bootloaders and other controls to make it less likely to brick. By the time you're hard-bricked, I've seen recovery from there but it's not looking great. You'd probably need some hardware based solution like jtag or the unbrickable. Check my post a few days ago about a really bad experience with that -- don't make my mistakes.
Thanks for the replies. I have a couple other cables, so I'll give them a try and also try dl mode in wall before the computer. I probably won't buy another cable since I'm due for an upgrade in a couple months and am surviving with a continuum (yikes!).
@ yunoworkandroid So much for the unbrickable fascinate, right? lol

[Q] I'm Convinced...

that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Well I guess the rest of us that followed Adam's thread and were easily unlocked and loading ROMs daily are magicians or something?
Try a different USB port and a different computer. I could not get it to work at all on one PC in Windows or Linux, but it worked first try as soon as I tried it on my laptop.
Yes you caught us it was all a huge conspiracy to get you to brick your phone. The hundreds of people that have said they used the program where all in on it.
Sent from my SCH-I605 using xda app-developers app
dmonger11b said:
Yes you caught us it was all a huge conspiracy to get you to brick your phone. The hundreds of people that have said they used the program where all in on it.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Dude, you weren't supposed to tell him!
Honestly if you can't run casual at this point, you shouldn't be doing it at all. I say this because when a "real" problem comes up you won't be equipped to handle it. Then you really will be SOL.
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
Honestly if you can't run casual at this point, you shouldn't be doing it at all. I say this because when a "real" problem comes up you won't be equipped to handle it. Then you really will be SOL.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
BINGO!!
Yea maybe try a different computer. I tried my laptop multiple times and it didn't work but once I did it on my surface pro it worked right away
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
ztotherad said:
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
Click to expand...
Click to collapse
It'd be easier to get a Linux boot able CD or make one than do all that...
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
It'd be easier to get a Linux boot able CD or make one than do all that...
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
yup definitely thought about that as well actually. in which i may just end up doing. is java 7 good to use with casual?
ztotherad said:
yup definitely thought about that as well actually. in which i may just end up doing. is java 7 good to use with casual?
Click to expand...
Click to collapse
That's what I have on my machine. I had no issues with casual, although that was several months ago.
It's not fair to be pissed at people who make the tools. You root at your own risk. Every post and every user will tell you that.
Sent from my SPH-L710 using xda app-developers app
WindroidApps said:
It's not fair to be pissed at people who make the tools. You root at your own risk. Every post and every user will tell you that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
this is so true! you do all this crap at your own risk. and I'm willing to take this risk, and not blame the awesome devs for your problems
5w3d15h said:
that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Click to expand...
Click to collapse
I hear apple calling for thier long lost customer :good:
droidstyle said:
I hear apple calling for thier long lost customer :good:
Click to expand...
Click to collapse
that's the best line I've heard today.
If you go the Linux route, just be sure to update the lib files, as stated in the casual thread. Linux worked perfectly for me, and I am a complete noob at this stuff.
Sent from my SCH-I605 using Tapatalk 2
ztotherad said:
that's the best line I've heard today.
Click to expand...
Click to collapse
Haha sup man? Glad to see ya made the jump up to the note 2!
mcp2009 said:
Yea maybe try a different computer. I tried my laptop multiple times and it didn't work but once I did it on my surface pro it worked right away
Click to expand...
Click to collapse
ztotherad said:
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
Click to expand...
Click to collapse
Yep ive been through this to and finnally got it to work on my moms laptop. Our desktop is the only one I can use odin on and my moms laptop is the only one I can use casual on. When I have some spare time (or feel like it lol) im gonna try loading up a fresh install on windows 7 on 1 of my spare hard drives and see what happens from there. But for now im not really woried about it, just gonna roll with the flow.
Sent from my SCH-I605 using Tapatalk 2
5w3d15h said:
that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Click to expand...
Click to collapse
I feel your pain but hang in there and keep trying. It took me 3 days and several hours to find the right combination that finally worked. If you follow the dev thread for a few days, you'll see that most everyone having problems eventually gets it to work through a combination of trial and error and support from the devs.
If you haven't already, try the driver suggestions in the last several pages of the dev thread. This seems to be helping quite a few others. Another thing to try is running the Casual jar file from an admin command prompt instead of double clicking the file. This worked for me.

Categories

Resources