yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] enkrypt3d:
yes this is what his exploit does so you can load custom recovery's and roms.......without it u can't do either of those.

---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------

Thats what I had to do - when casual put it into download mode i flashed the bootloader & the verizon files thru ODIN and it worked.... it did not wipe any of my data. It took me to the TWRP recovery which I'm not a big fan of so I rebooted and flashed CWM thru ROM manager and then I installed Cyanogenmod 10... so far so good....

LTE speeds are pretty horrible still (not blaming this rom I had this issue on stock as well)

Are there any new modems / kernels that we can try to improve network performance? Thx adam! great work
[Verizon Samsung Galaxy Note II] AdamOutler:
This isn't a ROM and there should be no discussions of ROMs, modems, apps, or data speeds in this thread they are 100% irrelevant. Find an appropriate topic in general and discuss it there, or start your own new thread in Q&A.
[Verizon Samsung Galaxy Note II] AdamOutler:
CASUAL is a language. This particular CASUAL is for unlocking the boot loader. I think you're using the version I posted as a beta. You should be using Back Atcha Verizon.
[Verizon Samsung Galaxy Note II] universexda:
Wow. I thought your login not the bootloader state of a device determined your Google Play Store access, etc. If bootloader state determines Google Play Store access, that would mean your access is limited to a device. Can't you use the same account at the store if you have say a Note 2 and a Galaxy Tab?
[Verizon Samsung Galaxy Note II] enkrypt3d:
I wasn't saying it was..... :confused: I was referring to cm10 which I know is off topic and wasn't asking any questions regarding cm10.

I'm not some noob like you probably think I am........ but again thanks for the bootloader unlock and the quick turn around you saved my phone from being soft bricked yesterday with the baseline bootloader...:good::good:
[Verizon Samsung Galaxy Note II] larry_thagr81:
How long this it take to flash the backatacha verizon file?
[Verizon Samsung Galaxy Note II] Carnyewest592:
Hey, before I installed this I was able to hookup my phone to my pc and see all the folders like the System/apps folder. After I installed this now when I hook my galaxy note 2 up to my pc I can not find these folders?!?! Anyone know how to fix this or make those folders show back up on my pc? I'm trying to find the system folder and its like it never existed. However, on my phone I can see it in Titanium or root explorer. When I usb to my pc tho it only shows about 6 folders and the system folder isn't one of them.
[Verizon Samsung Galaxy Note II] enkrypt3d:
it doesn't take long at all... I noticed that it hung on me when I was just trying to flash it w/o casual running... so I started over with casual and let it do its thing first, then launched odin (this is from win7) and then flashed the new backatchaverizon file... then it reboots into TWRP. That should get u sorted out hopefully. I did have to pull the battery though when casual wasn't running b/c I'm guessing I was trying to load the unlocked bootloader w/o running the exploit first which is what casual does.... good luck!
[Verizon Samsung Galaxy Note II] ElChibo:
my issue is when i flash the rom. Your tool worked great to unlock the bootloader and everything i had no problems there. its when i use recovery to flash a rom it gives me an error stating that its not a i605. That the build prop doesnt match the device. I would assume that i might be able to fix this by flashing a recovery via odin because my bootloader is unlocked but i am unsure.
[Verizon Samsung Galaxy Note II] AdamOutler:
This thread is not to support your choice of ROM. This thread enables you to flash ROMs. As I stated before, go somewhere else like the stickies in VZW Gnote 2 Android Development.
[Verizon Samsung Galaxy Note II] carhauler1969:
I did this exactly as you suggested an got this:

CASUAL's AUTOMATED DRIVER INSTALLER

This program uses libwdi by Pete Batard

Compatible Windows Version Detected...
Getting Device List...
Device List Aquired...
Parsing...
Target Device Found:"Modem" Found at:( 04E8:685D )
Preparing Driver...
Driver Prepared...
Installing Driver...
Driver Install Failed...
Target Device Found:"dg_ssudbus" Found at:( 04E8:685D )
Preparing Driver...
No Target Devices Detected...
Quiting...
Press Any Key To Continue...

same as before, no change :confused:
[Verizon Samsung Galaxy Note II] jrloper:
Alright I'm going to post a debug version, later this evening. If you're willing to help me out I'd appreciate the output from it.

In the mean time, if you would like to finish jailbreaking, do as before (placing your phone in download mode)

Use Zadig

http://sourceforge.net/projects/libwdi/files/zadig/zadig_v2.0.1.160.7z/download

Select "Options" -> "List All Devices"

Then from the dropdown Select "Gadget Serial", then click "Replace Driver".

That should allow you to run CASUAL without further hiccups. Once you reboot your phone.
[Verizon Samsung Galaxy Note II] carhauler1969:
Absolutely, I'd be glad to help. Just hit me up on GTalk @ carhauler1969@gmail.com.

And thanks for the alternate method, I'm anxious to get it unlocked today before I go back out on the road. I've already soft-bricked it once trying an older method, it's back up now though. Thanks again! :cowboy:

Oh, by the way which driver do I need to install with Zadig libusbK or libusb-win32?

EDIT: Thank you!!! :cool: :D :cowboy: Finally got it unlocked & custom recovery installed!!! woOT!!!
[Verizon Samsung Galaxy Note II] jrloper:
Sorry I should have mentioned that it didn't matter which driver you selected, they are all compatible.

Here is that debug version I said I would post. It contains CADI.exe and run.bat, extract both files to the same folder; Place your phone in download mode, then execute the "run.bat", you won't see anything on your screen; once the windows closes itself, you will have a new file "cadi.log", please email its contents to me jrloper@gmail.com

https://cadi.googlecode.com/svn/trunk/CADI/Release/cadi-debug.zip

Thanks again :)
[Verizon Samsung Galaxy Note II] mwep:
No ADB After Install

I ran the Windows installed on a Brand New Note 2 and it seems to have completed just fine.

However; even with Debugging Selected, ADB is not responding.

I have factory reset, pulled battery, tried different cables.

Any suggestions ?
[Verizon Samsung Galaxy Note II] AdamOutler:
Try a different USB port or computer.
[Verizon Samsung Galaxy Note II] mwep:
Tried multiple ports and cables. It must be a driver problem.

I dont see my phone under My Computer either. I do see it in Device Manager.

I tried reinstalling the Samsung Drivers but it hasn't helped.

Also removed KIES.

Any other suggestions ?
[Verizon Samsung Galaxy Note II] AdamOutler:
under device manager remove the driver with your device in download mode and connected.

right click Computer>manage>Device manager>usb devices>right click it, uninstall driver> Also delete driver.

Then try again from the start.
[Verizon Samsung Galaxy Note II] mwep:
That worked!!

As soon as I selected Uninstall (plus delete driver) Windows instantly recognized the device again but this time it loaded the proper drivers and I am able to access the device via My Computer and I confirmed that with Debugging I am able to connect via ADB.

Thanks!!
[Verizon Samsung Galaxy Note II] carhauler1969:
Donate button not working?

After successfully unlocking & rooting my N2 with Casual yesterday I wanted to make a donation to show my support for y'all, but the donate button in Casual 401b is causing Casual to freeze when I click it :crying: If there's another way, or donate link I'll gladly use that. Thanks for all that you guys do :D

Edit: I do realize there are individual donate links on each of your profiles (Adam & jrloper), but was looking to make a donation to the project group/team.
[Verizon Samsung Galaxy Note II] jrloper:
There are unnamed parties as well, donations should go to Adam. He disperses them from there.
[Verizon Samsung Galaxy Note II] carhauler1969:
Done and done, confirmation #2TF64484PD537321X. Thanks again for all of the help yesterday :cowboy:
[Verizon Samsung Galaxy Note II] Oh_wow:
I'm sorry but I'm still stuck at the pc not seeing the i605. I've read and re-read, gone back to pre update and re-updated to vrall4 only to get "adb cannot ack", uninstalled/reinstalled samsung/windows drivers, uninstalled/deleted usb device drivers, tried with debugging on and off, tried r401b multiple times (or more) and nothing. I was able to unlock using adam's original method (the 1st one!). I've got to missing something. Please, ANY help would be appreciated as I am running out of hair and patience. Thank you in advance.

I've also tried several cables and several usb ports and used system restore to go back to 8 different restore points to try for a fix..ok, I'm desperate.
[Verizon Samsung Galaxy Note II] carhauler1969:
Sounds like the system path is not correct to me.
[Verizon Samsung Galaxy Note II] Oh_wow:
delete
[Verizon Samsung Galaxy Note II] marcustaz:
Adam, forgive me if this has been asked before but does casual disable OTA updates? I ask because someone posted this in the do not accept ota updates thread a new build 4.1.2:VRAMC3

Unless they are selectively rolling out the updates every time I check it says no new updates available...

http://xdaforums.com/showthread.php?p=40248062
[Verizon Samsung Galaxy Note II] AdamOutler:
Yeah, you can't install updates after this. it will download, but not install.
[Verizon Samsung Galaxy Note II] krustytheclown:
I'm having issues rooting my Verizon Galaxy Note 2. I'm attempting to use the BackAtchaVerizon Casual (rev 401b) program. When I open the program, and connect my Note 2, it gives me a message saying device not paired. As I understand it, the casual program should reboot the phone into download mode, and do everything on its own. If I click "All Set and Done", it doesn't reset my phone and Casuals shows a message that says "Rebooting into download mode Error: Device offlineWaiting for Downoad Mode device...Heimdall v1.4 RC2)

If I manually manually phone into download mode, and then connect it, I still see the Device Not Paired popup, but it seems like it tries to go through the process, and reboots my phone. Casual displays the same "device offline" message, but then displays Uploading BOOT 100% successful and reboots the device. At the top of the window, it says there is an error, but it looks like Casual worked.

Help me please!

Drivers are installed, phone is on 4.1.1, Developer options and usb debugging are on.
[Verizon Samsung Galaxy Note II] hredder:
I got option then list all device's but I cannt see gadget serial in the drop down menu. .at all..what am I doing wrong?

Never mind I found the zip file and ran the .bat file. .casual works perfect now
[Verizon Samsung Galaxy Note II] carhauler1969:
It's not in the options tab, once you select list all devices, in the main Window below the options tab there's a bar with another drop down menu, click that and you'll see gadget serials in there. That is provided your phone is in download mode, and connected to your PC via USB, and the PC can "see" your phone.
[Verizon Samsung Galaxy Note II] hredder:
Thanks for the reply. ..I found the cadi.zip file and ran the. Bat file and casual worked perfect. ..thanks for trying to help me
[Verizon Samsung Galaxy Note II] jrloper:
adb cannot communicate with your device, this is normally the result of a bad USB cable.

If you have the cable that came with your phone that is the preferred cable to use.

Alternatively try a different USB port, preferably a port on your motherboard (i.e. not a front desktop port)
[Verizon Samsung Galaxy Note II] carhauler1969:
I believe there's a problem with Win 8. After you helped me the other day with my phone, I used the same method to try and unlock the wife's N2 today. For the life of me I could not get my laptop (Win 8) to see her phone. I ended up copying Casual & Zadig to my wife's laptop (Win 7) to get her phone unlocked and rooted. I still cannot get ADB to run on my laptop again :confused:

I used the factory USB cable just as I did the other day on my laptop.
[Verizon Samsung Galaxy Note II] krustytheclown:
I switched to the OEM cable, and connected to a port on my motherboard. Casual still pops up the not "paired message".
[Verizon Samsung Galaxy Note II] jrloper:
:

Honestly that wouldn't surprise me, just because I hate Windows 8 lol.

Has your laptop been rebooted?

try (from a command prompt):

cd C:\Program Files (x86)\Android\android-sdk\platform-tools\
adb kill-server

The computer not seeing her phone really sounds like a bad/wrong driver install.

open Device Manager check for "Samsung Android Device" under "Universal Serial Bus devices" or any flagged devices.

If you find either right click on the device and Select "Uninstall", when you get the dialog confirmation, check the "Delete driver software for this device", then select "Scan for hardware changes" from the "Actions" menu

---------- Post added at 11:12 PM ---------- Previous post was at 10:58 PM ----------

lol, ok well you're just full of good news.

What's your host OS ?
[Verizon Samsung Galaxy Note II] krustytheclown:
Windows 7 Ultimate
[Verizon Samsung Galaxy Note II] carhauler1969:
The laptop was cold booted this morning when I got up. My path is different due to the method of install & the SDK bundle I installed. However, using the correct path, copied and pasted in the command prompt yielded "windows cannot find the path specified" or something to that effect. :confused: at this point since I did nothing to alter the path to the SDK...

^^^^^This hit the nail on the head and corrected the problem entirely for me. I now have ADB working again, but Samsung Mobile MTP Device is flagged with a driver problem. Odd since I have the Samsung official drivers installed.

Once again you've helped me out of a jam, I really appreciate it, and will continue to follow this thread and help where I can. :D
[Verizon Samsung Galaxy Note II] jrloper:
Ok, does Windows recognize your device? (mount phone internal storage) normally you would get an Autorun prompt when the phone is initially connected.

---------- Post added at 11:53 PM ---------- Previous post was at 11:51 PM ----------

Always glad to help
[Verizon Samsung Galaxy Note II] krustytheclown:
Windows isn't recognizing the device at all. This is weird, it has in the past, as I pulled pictures and video off the phones storage.

I've changed the usb setting from installer to media device or camera, and windows will make the sound that it knows something was connected, but then the phone doesn't show up in my computer at all.
[Verizon Samsung Galaxy Note II] jrloper:
Arrr it be driver problems yee be havin! Sail ur way to Device Manager it be right around Control Panel bend.

Ok enough pirate talk, lol ...too much Spongebob today.

Yeah go into Device Manager in the Control Panel (or start -> run -> devmgmt.msc) look for any flagged devices, or "Samsung Android Device" under "Universal Serial Bus devices". If you find either right click on the device and Select "Uninstall", when you get the dialog confirmation, check the "Delete driver software for this device", then select "Scan for hardware changes" from the "Actions" menu.
[Verizon Samsung Galaxy Note II] krustytheclown:
I've uninstalled it and reinstalled it. I saw you mention that to an earlier poster. Didn't help.

There is an unknown USB controller item in the device manager, that I can't fix for some reason. That has been there since I built this computer, and hasn't caused an issue before this.
[Verizon Samsung Galaxy Note II] jrloper:
hmmm...

ok, extract this zipfile and run the program I setup the *.cfg file for what I need to see. Right click on any item in the list and select "HTML Report - All Items" which will create a file called "report.html" in the same directory.

Email me that file ( jrloper@gmail.com ) and I will email you back in the morning (its 1am here, :silly: so I'm heading to bed), so we aren't cluttering up this thread going back-n-forth.
[Verizon Samsung Galaxy Note II] soba49:
EDIT: I figured out some of this, but the i605 PIT file I was using makes no mention of identifiers 82 or 60, could I have the wrong PIT?

EDIT2: I did have the wrong PIT. Doesn't match the one I downloaded directly from my phone, which does have entries for 82 and 60. So, Nevermind. A little unnerved that the one I downloaded previously was wrong, but all is well here as far as CASUAL goes.

EDIT3: They're not sectors, they're identifiers in the PIT stored on the phone. I wasn't complaining about CASUAL, I was just confused because I had never seen heimdall used via identifier before.

.........

Just a belated question.

Earlier in your script you were running:

heimdall flash --8 boot.img
heimdall flash --82 swagBoot --60 recoverThis

Typical heimdall command lines I've seen use --recovery, --pit, --cache with a filename.

heimdall flash --kernel zImage --verbose

Looks like you were using --<partition_identifier> <filename>

Where do the numbers come from? Are they sectors taken from the appropriate PIT file?
[Verizon Samsung Galaxy Note II] AdamOutler:
No one is having problems with heimdall or ADB unless they have messed up drivers installed.
[Verizon Samsung Galaxy Note II] jrloper:
The numbers are the partition identifiers

So:

heimdall flash --82 swagBoot --60 recoverThis

flashes swagBoot to partition with the idetifier 82, and recoverThis to partitiion with identifier 60

if you do:

heimdall print-pit --no-reboot

You will see where the numbers come from.

--recovery, --pit, --cache are optional commands where heimdall will attempt to determine the correct partition for you.
[Verizon Samsung Galaxy Note II] AdamOutler:
I updated the FAQ
[Verizon Samsung Galaxy Note II] travisn000:
Just an FYI..

..I had some issues with running this in PCLinuxOS.. I got a bunch of errors related to gksudo and dpkg, neither of which is used in PCLinuxOS. Perhaps the description or troubleshooting post should list these as a requirement (or the script could test for them & their alternatives.)

Thanks.
[Verizon Samsung Galaxy Note II] AdamOutler:
You need to install gksudo and dpkg. I cannot account for every operating system. I think the instructions should have sufficed. If you have a problem, check with your OS developer, or use a different OS.
[Verizon Samsung Galaxy Note II] syntrix:
Probably covered already....

Windows 7 x64 here, got an error to run as administrator right after the redist c++ installation.

Phone was in download mode, nowhere to go in the java app. Rebooted and reran, things were just fine. BTW, no native option to run java in admin mode unless command line.

Worked great rerunning after a reboot out of download mode.:good::good:
[Verizon Samsung Galaxy Note II] soba49:
So your adb isn't seeing your phone:

[ERROR]List of devices attached

You're on windows 7. If it were me. I'd download fresh drivers from Samsung:

http://www.samsung.com/us/support/owners/product/SCH-I605ZWAVZW?#

Then I'd focus on getting ADB working*. CASUAL isn't going to be able to work its magic without that. When "adb devices" lists your device in shell underneath that "List of devices attached", you'll know that your cable/drivers/etc. are all in working order.

* You could expect CASUAL to run ADB for you, but you could instead take measures yourself. For instance you could install the android SDK or the ADT Bundle.
[Verizon Samsung Galaxy Note II] carhauler1969:
Definitely a driver issue since ADB cannot see the phone.

I rooted my VZW Note 2 successfully after fiddling with drivers, and some help from jrloper the dev of CADI . Two days later I attempted to root the wife's VZW Note 2 using the same laptop, cable, and USB port and got the same results as you. It *IS* a driver issue.

See this post http://xdaforums.com/showthread.php?p=40270632 for instructions on how to fix it, thanks go to jrloper for making it easy :)

^^^^^This guy is dead on the money :thumbup::thumbup: :)
[Verizon Samsung Galaxy Note II] jrloper:
This definitely looks like a bad cable/connection. Try the OEM cable (if possible) and a motherboard USB port (if possible)

Adam has at least a dozen cables that won't work with his Note 2 and Heimdall, but work for every other device.

There is no magic fix for the "Protocol initialisation failed" problem, I wish there was. You can run Heimdall a thousand times getting "Protocol initialisation failed" and on that next try it just goes through like nothing. Give that a try, let me know... I'll try come up with something :eek:

P.S.) Please use

tags when posting logs

[QUOTE="soba49, post: 40342224, member: 3150303"]So your adb isn't seeing your phone:
[B][ERROR]List of devices attached [/B]

You're on windows 7. If it were me. I'd download fresh drivers from Samsung:
[URL="http://www.samsung.com/us/support/owners/product/SCH-I605ZWAVZW?#"]http://www.samsung.com/us/support/owners/product/SCH-I605ZWAVZW?#[/URL]

Then I'd focus on getting ADB working*. CASUAL isn't going to be able to work its magic without that. When "adb devices" lists your device in shell underneath that "List of devices attached", you'll know that your cable/drivers/etc. are all in working order.

* You could expect CASUAL to run ADB for you, but you could instead take measures yourself. For instance you could install the android SDK or the ADT Bundle.[/QUOTE]

Installing Kies is the best way to get drivers, you should Uninstall and previous driver pack prior to installing it of course.
Neither the SDK or ADT bundle are needed/desired for CASUAL to operate properly.

[QUOTE="carhauler1969, post: 40342756, member: 2431822"]Definitely a driver issue since ADB cannot see the phone.
I rooted my VZW Note 2 successfully after fiddling with drivers, and some help from jrloper the dev of CADI . Two days later I attempted to root the wife's VZW Note 2 using the same laptop, cable, and USB port and got the same results as you. [B]It *IS* a driver issue.[/B]
See this post [url]http://xdaforums.com/showthread.php?p=40270632[/url] for instructions on how to fix it, thanks go to jrloper for making it easy :)

^^^^^This guy is dead on the money :thumbup::thumbup: :)

;)
[Verizon Samsung Galaxy Note II] andrewjt19:
Can't get ROOT and Custom Recovery

So I wanted to do a fresh start and flashed Imnuts ODIN restore file (which happens to be VRALJB) and have been trying to obtained root and unlocked bootloader through CASUAL but keep getting this error message:

ERROR: Failed to access device. libusb error: -12Installing drivers

It keeps doing this until it finally says it could read the device. I have reinstalled the drivers many times and the usb cable is not bad. Also have used different ports, no go. As of now I am unable to acquire root through this method or the Toolkit method. Any ideas? I'm using Windows 7 32bit but also have Ubuntu 12.04LTS of which I haven't tried yet.

Edit: So I was able to get CASUAL to work on Ubuntu, thank the Lord. Queued perfectly.
[Verizon Samsung Galaxy Note II] carhauler1969:
Try this:

^^^^^That worked for me a few days ago, twice in fact.
[Verizon Samsung Galaxy Note II] pgzerwer:
Bit of a scare when I got a message saying had to run in Administrator mode and then stopped - showing as disconnected on the Casual window. Held my breath, disconnected, pulled the battery, restarted, reconnected, hit run and whew, all went great. Extraordinarily easy once I got past the momentary panic of maybe having to take the phone back to Verizon with nothing but the green android on screen. Win 7 64
[Verizon Samsung Galaxy Note II] andrewjt19:
Awesome. Thanks.
[Verizon Samsung Galaxy Note II] jrloper:
CASUAL won't show connected when your device is in Odin/download mode. Sounds like the driver install didn't execute. You may manually try to install drivers following the instructions here:

http://xdaforums.com/showthread.php?p=40196594

Or run CASUAL as Administrator from an elevated cmd prompt.