Casual will not connect to the phone - Verizon Samsung Galaxy Note II

So, I have this issue since yesterday.
Casual will not connect to my phone.
I had Kies installed yesterday, but Kies did not recognize my phone also.
I had drivers downloaded directly from Samsung, and reinstalled them 3 times. Yesterday, for a brief moment, I managed to have Casual connected but apparently missed a step and am still not unlocked.
Steps taken:
antivirus and firewall disabled
tried several different usb cables. Including brand new one
tried ports available
reinstalled drivers
had bootstrap launched or not
Debugging enabled
Does not matter - phone does not connect to Casual. Also, Casual hangs and refuses to shut down, I have to force close it. I have 2 versions, both with same results. Antivirus, btw, treats Casual as a trojan.
Suggestions? Phone is rooted as of yesterday. I get all kinds of weird messages - device Id can not be found (on PC). Phone tells me that a program is missing on PC for file transfer, as in Service Pack 3, or Windows Media Player. Tired. I am running Windows 7. Had PC and phone rebooted several times. Same result. Odin connects to phone just fine.
Oh, and in addition. After about 5 minuters, Casual will connect to the phone, but pressing DoIt button produces no results.
Lat question: Casual says "Put your device into ADB mode". ????????

---

Try the last post. Maybe it will work. Also you really could have just used your other thread without a new one.
http://forum.xda-developers.com/showthread.php?p=38959999
Sent from my SCH-I605 using Tapatalk 2

---

I know. But I was always told that you get better results by separating issues into threads. Otherwise, it all gets muddied.
Btw, Casual is working. It's Pushing SuperSU app now. I am past base install via Odin. Problem is - it is moving not even at snail speed, it is moving at a bit per minute speed. Must be something with USB ports. I should have gone for rear USB ports, they are directly in mother board. Can't touch it now, don't want to f something up. I had to do it once on my Droid Charge.
Pushing Exynos Abuse now. I reckon, I'll get there by midnight, ha-ha.

---

Well I would have helped in either thread. In sure you know but always use usb in back, but at least it's working
Sent from my SCH-I605 using Tapatalk 2

---

I know. Late now. What threw me off was that I had it all going yesterday off front ports. Now I am stuck, no point in messing it up now. It's pushing something...

---

Last question. Backatcha goes under bootloader in Odin, not under PDA, right?

---

ukrkoz said:
Last question. Backatcha goes under bootloader in Odin, not under PDA, right?
Click to expand...
Click to collapse
If that's what casual said. I've been unlocked since before the ota so I'm not sure.
Sent from my SCH-I605 using Tapatalk 2

---

kintwofan said:
If that's what casual said. I've been unlocked since before the ota so I'm not sure.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
OK. That's what I was told by a good Samaritan. About 50% load done. Setting permissions.. I'll get there eventually. Thanks, kintwo..

---

ukrkoz said:
OK. That's what I was told by a good Samaritan. About 50% load done. Setting permissions.. I'll get there eventually. Thanks, kintwo..
Click to expand...
Click to collapse
Not a problem my man
Sent from my SCH-I605 using Tapatalk 2

---

It's done. 2 hrs.

---

ADB MODE?
a member asked earlier about CASUAL, and when it asks you to put phone in ADB Mode... no one addressed it and I need to know as well. I cant get CASUAL to notice the phone is connected. Installed the SDK, the drivers there, tried installing the drivers from samsung, no luck. Nothing is working. Yes the phone is in set to USB Debugging. Tried every USB on this pc.

---

cadgrad2010 said:
a member asked earlier about CASUAL, and when it asks you to put phone in ADB Mode... no one addressed it and I need to know as well. I cant get CASUAL to notice the phone is connected. Installed the SDK, the drivers there, tried installing the drivers from samsung, no luck. Nothing is working. Yes the phone is in set to USB Debugging. Tried every USB on this pc.
Click to expand...
Click to collapse
Why did you download the SDK?
As for drivers CASUAL installs its own so you shouldn't have to worry about that.
Is your antivirus off?
What is your OS?
Is Java the latest edition?
Which version of CASUAL are you using? Try one of the nightlies from Adams goo.im page.
Have you tried different USB cords?
Have you tried a different PC?
Sent from my SCH-I605 using XDA Premium HD app

---

Why did you download the SDK? Downloaded it to make sure I had drivers correct. All drivers are updated as of now. Still a no go though. Disconnected error. I restarted everything over here including my grandmas pacemaker
As for drivers CASUAL installs its own so you shouldn't have to worry about that.
Is your antivirus off? YES
What is your OS? Windows 7 Home Premium
Is Java the latest edition? Yes, Fresh Install
Which version of CASUAL are you using? Try one of the nightlies from Adams goo.im page. CASUAL R701 Nightly
Have you tried different USB cords? Yes, went out and bought another one just to make sure, Currently using the stock.
Have you tried a different PC? Looking for another PC atm.
Sent from my SCH-I605 using XDA Premium HD app[/QUOTE]

---

Soft Bricked?
So went to a new pc, everything seemed to go well..... now phone is stuck in bootloop. Heres the log:
Created Folder:C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\
Picking Jar File:/C:/Users/Michael/Desktop/NDROID/CASUAL-BackAtchaVerizon-Revision311b.jar
Found Windows Computer
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\Elevate.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinApi.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinUsbApi.dll
File verified.
sleeping for Windows ADB start
Found: WindowsLinux Galaxy Note 2 Jailbreak
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\-adb_usb.ini
File verified.
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
Control Change requested but lock is set.
OMFGWOOT GUI running!
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Searching for scripts
Updating Scripts for UI
From Resource: true
--WindowsLinux Galaxy Note 2 Jailbreak--
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
Exiting comboBoxUpdate()
Extracting archive....
Unzipping Superuser.apk
Control Change requested but lock is set.
Unzipping boot.img
Unzipping busybox
unknown
Device List:List of devices attached
Unzipping dependentinstaller.sh
Unzipping exploit
Unzipping exynos-abuse
Unzipping recoverThis
Unzipping rootGN.sh
Unzipping su
Unzipping swagBoot
Unzipping viewmem
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
Controls Enabled status: false
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 75
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
/SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak not found in repository.
Reading [email protected]
new command: $MAC $HALT $ECHO This version of CASUAL cannot support mac
new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
COMMAND processed - C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe Are you sure?, This is your only warning.
You will be Unlocked and Rooted. Your device will
reboot once and then again into Odin mode. You
will then flash the Suck It Verizon Odin Bootloader
package.
new command: $ECHO Rebooting into download mode
SCRIPT COMMAND:$ECHO Rebooting into download mode
Received ECHO command$ECHO Rebooting into download mode
Rebooting into download mode
new command:
new command:
new command:
new command: $ADB reboot download
SCRIPT COMMAND:$ADB reboot download
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
return from ADB:error: device not found
new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\libusb-1.0.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe
File verified.
detected!
###executing real-time command: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe###
Waiting for Downoad Mode device.Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--------LINK REMOVED------
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
-LINK REMOVED-----
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%

19%


38%


57%


76%


95%


100%Ending session...
Releasing device interface...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--link removed---
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
----link removed---
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%19%38%57%76%95%100%Ending session...
Releasing device interface...
ERROR: Failed to confirm end of file transfer sequence!ERROR: BOOT upload failed!ERROR: Failed to send end session packet!
new command:
new command:
new command: $ECHO Your device should be rebooting into Android now.
SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
Received ECHO command$ECHO Your device should be rebooting into Android now.
Your device should be rebooting into Android now.
new command: $ADB wait-for-device
SCRIPT COMMAND:$ADB wait-for-device
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
shangrila500 said:
Why did you download the SDK?
As for drivers CASUAL installs its own so you shouldn't have to worry about that.
Is your antivirus off?
What is your OS?
Is Java the latest edition?
Which version of CASUAL are you using? Try one of the nightlies from Adams goo.im page.
Have you tried different USB cords?
Have you tried a different PC?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse

---

cadgrad2010 said:
So went to a new pc, everything seemed to go well..... now phone is stuck in bootloop. Heres the log:
Created Folder:C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\
Picking Jar File:/C:/Users/Michael/Desktop/NDROID/CASUAL-BackAtchaVerizon-Revision311b.jar
Found Windows Computer
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\Elevate.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinApi.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinUsbApi.dll
File verified.
sleeping for Windows ADB start
Found: WindowsLinux Galaxy Note 2 Jailbreak
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\-adb_usb.ini
File verified.
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
Control Change requested but lock is set.
OMFGWOOT GUI running!
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Searching for scripts
Updating Scripts for UI
From Resource: true
--WindowsLinux Galaxy Note 2 Jailbreak--
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
Exiting comboBoxUpdate()
Extracting archive....
Unzipping Superuser.apk
Control Change requested but lock is set.
Unzipping boot.img
Unzipping busybox
unknown
Device List:List of devices attached
Unzipping dependentinstaller.sh
Unzipping exploit
Unzipping exynos-abuse
Unzipping recoverThis
Unzipping rootGN.sh
Unzipping su
Unzipping swagBoot
Unzipping viewmem
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
Controls Enabled status: false
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 75
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
/SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak not found in repository.
Reading [email protected]
new command: $MAC $HALT $ECHO This version of CASUAL cannot support mac
new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
COMMAND processed - C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe Are you sure?, This is your only warning.
You will be Unlocked and Rooted. Your device will
reboot once and then again into Odin mode. You
will then flash the Suck It Verizon Odin Bootloader
package.
new command: $ECHO Rebooting into download mode
SCRIPT COMMAND:$ECHO Rebooting into download mode
Received ECHO command$ECHO Rebooting into download mode
Rebooting into download mode
new command:
new command:
new command:
new command: $ADB reboot download
SCRIPT COMMAND:$ADB reboot download
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
return from ADB:error: device not found
new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\libusb-1.0.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe
File verified.
detected!
###executing real-time command: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe###
Waiting for Downoad Mode device.Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--------LINK REMOVED------
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
-LINK REMOVED-----
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%
19%
38%
57%
76%
95%
100%Ending session...
Releasing device interface...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--link removed---
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
----link removed---
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%19%38%57%76%95%100%Ending session...
Releasing device interface...
ERROR: Failed to confirm end of file transfer sequence!ERROR: BOOT upload failed!ERROR: Failed to send end session packet!
new command:
new command:
new command: $ECHO Your device should be rebooting into Android now.
SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
Received ECHO command$ECHO Your device should be rebooting into Android now.
Your device should be rebooting into Android now.
new command: $ADB wait-for-device
SCRIPT COMMAND:$ADB wait-for-device
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
Click to expand...
Click to collapse
Run Casual again, that seems to fix it for a lot of people. Some people run it as many as 5 times and then everything's gravy.
Sent from my SCH-I605 using XDA Premium HD app

---

((SOLVED))
((SOLVED))
I figured the partition got screwed up as CASUAL wouldn't run. I ran just the stock .pit using Odin3 v3.07 to clear up the issues and restarted back at a rooted stock. Flashing a CWM now as preferred Recovery.
......aannndd now I get the Verizon Triangle, telling me that I need to take my device in to a center... smh
shangrila500 said:
Run Casual again, that seems to fix it for a lot of people. Some people run it as many as 5 times and then everything's gravy.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse

---

cadgrad2010 said:
((SOLVED))
I figured the partition got screwed up as CASUAL wouldn't run. I ran just the stock .pit using Odin3 v3.07 to clear up the issues and restarted back at a rooted stock. Flashing a CWM now as preferred Recovery.
......aannndd now I get the Verizon Triangle, telling me that I need to take my device in to a center... smh
Click to expand...
Click to collapse
Be careful with CWM, there seem to be a lot of issues with it on our phone because it isn't updated very often. TWRP is the most stable so if you end up having issues just flash the latest zip from here:
http://goo.im/devs/OpenRecovery/t0ltevzw/
Or use Goo Manager to install it.
Sent from my SCH-I605 using XDA Premium HD app

---

Might need to start over from stock
cadgrad2010 said:
((SOLVED))
I figured the partition got screwed up as CASUAL wouldn't run. I ran just the stock .pit using Odin3 v3.07 to clear up the issues and restarted back at a rooted stock. Flashing a CWM now as preferred Recovery.
......aannndd now I get the Verizon Triangle, telling me that I need to take my device in to a center... smh
Click to expand...
Click to collapse
Most people in this situation have to flash back to stock using Odin. They flash Root66 or the alternate restore. I suggest flashing alternate restore, doing the OTA and then run Casual again.