yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] huwarrior:
Here is what I have done and the above will not work:

1.) Got a new Note 2 last week

2.) It immediately did an OTA update which I accepted

3.) I tried Casual Unlock/Root with no success, kept getting errors that weren't related to my computer/cable (stuff like PIT errors and failed writes)

4.) I Odin back to Root66 Stock, I am now rooted and stock VRALJB

5.) I try Casual again and still get similar errors, I am rooted but cannot get unlocked no matter what I try

My only guess from all of this is that when I took that OTA it locked up my Bootloader in some way that can't be exploited (yet).

Any ideas?
[Verizon Samsung Galaxy Note II] carhauler1969:
Re-read the OP as Adam added a note at the top that the current VRAMC3 OTA update is not currently un-lockable. They are working on it ;)

Sent from another Galaxy on my Note 2 with Tapatalk 2
[Verizon Samsung Galaxy Note II] bostonbassman78:
Man I really hope my replacement note 2 is not on the new build
[Verizon Samsung Galaxy Note II] BoostedB18C:
Dont worry they havent had enough time to update replacements yet
[Verizon Samsung Galaxy Note II] 4st3risk:
Thanks! That solves it.
[Verizon Samsung Galaxy Note II] pimpsalot69:
I only want root on vramc3 i havent unlocked my bootloader icame back to root66 stock with injected root and it updated before
[Verizon Samsung Galaxy Note II] huwarrior:
So, even though I have Odin back to stock before the OTA the fact that I took the OTA sealed up my bootloader?
[Verizon Samsung Galaxy Note II] dannymac77:
Same here... believe most of the bottom stuff is pastebin upload failed. Prob work's firewall... =/

Initialising connection...

Detecting device...

Claiming interface...

Setting up interface...

Checking if protocol is initialised...

Protocol is not initialised.

Initialising protocol...

ERROR: Protocol initialisation failed!

Releasing device interface...

[Heimdall Error Report] Detected:

Heimdall failed to initialize protocol; Script halted

[/Heimdall Error Report]

Server returned HTTP response code: 502 for URL: http://www.pastebin.com/api/api_login.php

[CRITICAL]null

null

java.lang.NullPointerException

java.lang.NullPointerException

at CASUAL.Pastebin$API.checkResponse(Pastebin.java:107)

at CASUAL.Pastebin$API.login(Pastebin.java:122)

at CASUAL.Pastebin.doPosting(Pastebin.java:61)

at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:198)

at CASUAL.CASUALScriptParser.executeOneShotCommand(CASUALScriptParser.java:85)

at CASUAL.HeimdallTools.doHeimdallShellCommand(HeimdallTools.java:105)

at CASUAL.HeimdallTools.doHeimdallShellCommand(HeimdallTools.java:117)

at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:494)

at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)

at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:121)

at java.lang.Thread.run(Unknown Source)

A critical error was encoutered. Please copy the log from About>Show Log and report this issue

[CRITICAL]CASUAL scripting error

$HEIMDALL flash --8 "$ZIPFILEboot.img"

CASUAL scripting error

$HEIMDALL flash --8 "$ZIPFILEboot.img"

java.lang.RuntimeException: CASUAL scripting error

$HEIMDALL flash --8 "$ZIPFILEboot.img"

java.lang.RuntimeException: CASUAL scripting error

$HEIMDALL flash --8 "$ZIPFILEboot.img"

at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:73)

at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:121)

at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.NullPointerException

at CASUAL.Pastebin$API.checkResponse(Pastebin.java:107)

at CASUAL.Pastebin$API.login(Pastebin.java:122)

at CASUAL.Pastebin.doPosting(Pastebin.java:61)

at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:198)

at CASUAL.CASUALScriptParser.executeOneShotCommand(CASUALScriptParser.java:85)

at CASUAL.HeimdallTools.doHeimdallShellCommand(HeimdallTools.java:105)

at CASUAL.HeimdallTools.doHeimdallShellCommand(HeimdallTools.java:117)

at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:494)

at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)

... 2 more

A critical error was encoutered. Please copy the log from About>Show Log and report this issue

CASUAL experienced an error while parsing command:

$HEIMDALL flash --8 "$ZIPFILEboot.img"

please report the above exception.
[Verizon Samsung Galaxy Note II] polo2883:
I am also getting errors trying to get this to run.... I am on 4.1.1
[Verizon Samsung Galaxy Note II] zeavott:
failed

detected the phone awesome.

Failed on me unfortunately...

sorry about long paste... didn't want to hijack the thread

http://pastebin.com/3jurqs8r
[Verizon Samsung Galaxy Note II] carhauler1969:
Log or they can't help you...

Sent from another Galaxy on my Note 2 with Tapatalk 2
[Verizon Samsung Galaxy Note II] Mibuix0r:
Nevermind bad USB cable :p
[Verizon Samsung Galaxy Note II] droidstyle:
why would you accept a ota update when its posted all over the forum not to?
[Verizon Samsung Galaxy Note II] craigbailey1986:
Most dont read the forum until after we get the phone. I check to see if root is attainable before I purchase but the update had already downloaded before I left the store. And the forum didnt say not to until we showed him casual didnt work on the new update. He even told one person that it did before he later corrected himself...
[Verizon Samsung Galaxy Note II] AdamOutler:
If anyone wants to try something for the latest firmware...

1. flash this with Odin on a NEW, unused usb port. One which you've never flashed using Heimdall. http://d-h.st/Uz7

2. run CASUAL as usual on your usual USB port.

This is a test to bypass the latest version of firmware, let me know if it works. If it doesn't work, then we've got something coming in a couple of weeks.
[Verizon Samsung Galaxy Note II] droidstyle:
I guess I dont fall into the most category then :p

I have yet to accept one ota update on any of the 3 galaxy devices I have owned.
[Verizon Samsung Galaxy Note II] mtran13:
Sorry if this has been addressed, where in Odin do I run this file?
[Verizon Samsung Galaxy Note II] chumba8:
do i got a older replacment phone that had the old software i flashed this and everything worked fine is there a way to check if the bootloader is actually unlocked
[Verizon Samsung Galaxy Note II] BoostedB18C:
So are you confirming that adams new test successfully rooted and unlocked bootloader on your MC3 OTA?
[Verizon Samsung Galaxy Note II] scoobntaz1996:
Yes I would like confirmation as well that this new thing you tried worked on the new 4.1.2 firmware?
[Verizon Samsung Galaxy Note II] BoostedB18C:
Im already "jailbroken" but you can try it and see if it works then confirm for others. No harm in trying
[Verizon Samsung Galaxy Note II] carhauler1969:
Boot to TWRP recovery.

Sent from another Galaxy on my Note 2 with Tapatalk 2

---------- Post added at 05:00 AM ---------- Previous post was at 04:58 AM ----------

If you read through his post and the log he pasted it clearly says it was successful.

Sent from another Galaxy on my Note 2 with Tapatalk 2

---------- Post added at 05:10 AM ---------- Previous post was at 05:00 AM ----------

If you read the lines from your log I quoted between the <snips> you can clearly see the device keeps disconnecting & reconnecting. You either have a bad cable or a bad USB port.

Sent from another Galaxy on my Note 2 with Tapatalk 2
[Verizon Samsung Galaxy Note II] marcustaz:
Gents, my wife took the update without me knowing and now I'm at the flashing logo. Cannot get into recovery but can get into download mode. Sadly I do not have a backup and well I'm hoping there is something I can try to save myself from all the time to try and get her phone back to where she had it... Or do I just bite the bullet and flash a stock rom and start all over?
[Verizon Samsung Galaxy Note II] craigbailey1986:
Yes I am confirming that it does indeed work... dont use the same port as odin though.... well atleast it wouldnt work with the same port as odin for my laptop

:good::good::good::good:
[Verizon Samsung Galaxy Note II] AdamOutler:
Awesome. We will have a new version of the BackAtchaVerizon going tonight.
[Verizon Samsung Galaxy Note II] Githrog:
If you read the lines from your log I quoted between the <snips> you can clearly see the device keeps disconnecting & reconnecting. You either have a bad cable or a bad USB port.

Sent from another Galaxy on my Note 2 with Tapatalk 2[/QUOTE]

Thank you for the response. I just don't think that is the problem. It seems hard to believe that I have tried 4 different usb cords including the original that came with my n2 and I tried all 8 usb ports on my desktop. Then I tried all 3 ports on my laptop and still no go. And why will odin connect but casual won't? It just doesn't make sense. Today I will go buy a new usb cord and try that but does anyone have any other ideas besides bad usb cord or port. Because I don't have tons of pc's laying around to try new usb ports. Thanks again

Sent from my Verizon GN2
[Verizon Samsung Galaxy Note II] jdec529:
If anyone gets a chance could u help me with the log I posted above. Thanks
[Verizon Samsung Galaxy Note II] carhauler1969:
I see a couple of things going on here. One your device keeps connecting/disconnecting in the first part of your log, judging by it changing state from 1 to 0 several times. Try a different cable & or a different USB port, or both.

Two, libusb error -12 says you do not have the correct drivers installed. And because of that Heimdall failed to initialize, & thus halted the process. This may be able to be corrected by using the Zadig utility, it's in the paperclip at the beginning of this thread. For instructions on how to use Zadig search jrloper's or my posts, as we have posted these instructions numerous times in the last few weeks.

Sent from another Galaxy on my Note 2 with Tapatalk 2

---------- Post added at 11:15 AM ---------- Previous post was at 11:08 AM ----------

Based on the log you posted, on the port & cable you were using at the time the log was generated, the connection kept getting interrupted, it's right there in black & white in your log. I understand your frustration, but I can only go by the one log that you posted, and in that log USB connection issues *were* the problem period.

Before buying yet another cable, and since you say that you've tried 12 different ports on two PCs, maybe, just maybe there's dust & debris in the connectors causing the problem. Try blowing the ports & connectors out with canned air. It doesn't take much to mess up a USB connection. And the stock Samsung USB cable that came with the phone is the best one to use. ;)

Sent from another Galaxy on my Note 2 with Tapatalk 2
[Verizon Samsung Galaxy Note II] marcustaz:
Adam or anyone willing to help as I stated a few post ago my wife took the update this morning and now I'm stuck with the flashing logo screen. will there be a way to recover this with the new script you going to release tonight or do I have to do a full wipe and lose all the data. quite as a lot of pictures on the internal memory excetera. I don't ask a lot, I'm just asking for some advice on how to go about this. Please help if you can.

It seems like at the moment the only thing I can access it download mode when I try to put the phone in recovery mode I get the same flashing logo like I do on a normal boot up.

Thanks
[Verizon Samsung Galaxy Note II] 911junkie:
well I'm not in a good spot. Log is attached.

Used the latest version R465 and now I'm bricked. When trying to boot up it just boot-loops on the logo (1/2 second then bootloops). In download mode and my computer can't see it (drivers loaded, tried several cables, so it's not that)

Wondering if R465 was fully tested with the DMC3?

EDIT: I went into Device and Printers to see what, if anything, is getting picked up by the computer when plugged in. I'm getting "Gadget Serial" - thinks it's a modem. So cables are working but ODIN can't see device.
[Verizon Samsung Galaxy Note II] marcustaz:
Try a different USB port on the same position and my computer sees the phone without a problem. Correction of terms I dont think you're bricked...
[Verizon Samsung Galaxy Note II] AdamOutler:
Wipe cache. If that dosnt work, wipe data. This is nothing.
[Verizon Samsung Galaxy Note II] jrloper:
FYI, that's not a brick.

---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------

Which logo? the:

SAMSUNG

SAMSUNG GALAXY NOTE

or the Animated booting logo

If its the last one, do a Cache/Data wipe from recovery.
[Verizon Samsung Galaxy Note II] 911junkie:
I'm encouraged but exactly how can I wipe cache/data if I can't access recovery?

The logo I am referring to is the Samsung Galaxy Note II logo. Lasts approx. 1/4-1/2 sec before looping. Can't access recovery. IIRC, log will show that the failure occurred when uploading the recovery file.

Thanks for the help.

---------- Post added at 07:36 PM ---------- Previous post was at 07:34 PM ----------

I've tried all the ports. Rear ports caused computer to install Samsung drivers. Still can't see the phone in ODIN and can't reach via ADB.
[Verizon Samsung Galaxy Note II] scoobntaz1996:
Well I can say that when mine did this I ran the pit file in the odin section and ran odin and it fixed the bootloop. you will be rooted with super user installed but still on stock recovery. Hope that helps. Just waiting for the update on casual till then at least my phone is working lol.
[Verizon Samsung Galaxy Note II] marcustaz:
Once it installed the drivers did you reboot the phone in Dl mode again and keep it on that port? I noticed once rebooting into Dl mode can sometimes sometimes fix this... Not saying it will work for you but it did for me...

---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------

Its the 2nd the SAMSUNG GALAXY NOTE

I cannot seem to get into recovery... Would love to do it and have many times but when I hold the volume up / power /home
[Verizon Samsung Galaxy Note II] marcustaz:
GOT IT!!! I said screw it and fiqured I had nothing to lose.. This is what I did

1) Flashed a pit file

2) Flashed the stock recovery

3) Flashed the pit file again

Ok so I had the 2nd flashing logo as asked by jrloper, it would flash for a milli sec and just loop, could not get into recovery only Dl mode. When I flashed the PIT file the same logo appeared but this time it stayed ON steady and not flash but the phone would stay stuck there and would not make it to the 3rd boot logo. So next I flashed the stock recovery ( it was previously on CWM 6.3.0) and still it was stuck on this 2nd logo, so I figured I would repeat the 2 processes again so 3rd I flashed the PIT again and bang this time the phone booted into 4.1.2.... Root is gone but man who cares I got the wife's pictures back and thankfully out of the proverbial dog house lmao!!!

jrloper thanks man for responding!

Here are the files I used

Hope this helps out some other poor soul ib the same boat thanks to VZW...
[Verizon Samsung Galaxy Note II] 911junkie:
No luck. Perhaps the OP can chime in. My issue is that ODIN doesn't see the phone in DL mode.
[Verizon Samsung Galaxy Note II] jrloper:
lol, I was uploading something to flash a recovery for you.

Glad you got it worked out.

---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------

You'll need to remove the driver that CASUAL uses to re-use Odin.

https://www.youtube.com/watch?v=zzghcV8HVVk

Let me know if that doesn't work.
[Verizon Samsung Galaxy Note II] marcustaz:
Thanks dude, appreciate you taking the time to help us all out including Adam... I have helped out in the glass repair section for the S3 and the emails never stop now lol. Thanks again for helping, what makes XDA what it is the best community around!
[Verizon Samsung Galaxy Note II] 911junkie:
Dude you are the ****ing man. That fixed it. Mad props to you. Thank you. Have a burger and a beer on me.

Add'l info: If someone was to be in the same position as me, after you follow the youtube video instructions above, simply bring up ODIN and flash the .pit file. Since 4.1.2 is locked, there is no flashing of the PDA/Stock software - ODIN will fail. The PIT file will get things back in order and allow you to use the stock ROM.

Thanks again.
[Verizon Samsung Galaxy Note II] Githrog:
Based on the log you posted, on the port & cable you were using at the time the log was generated, the connection kept getting interrupted, it's right there in black & white in your log. I understand your frustration, but I can only go by the one log that you posted, and in that log USB connection issues *were* the problem period.

Before buying yet another cable, and since you say that you've tried 12 different ports on two PCs, maybe, just maybe there's dust & debris in the connectors causing the problem. Try blowing the ports & connectors out with canned air. It doesn't take much to mess up a USB connection. And the stock Samsung USB cable that came with the phone is the best one to use. ;)

Sent from another Galaxy on my Note 2 with Tapatalk 2[/QUOTE]

Thank you so much for the tips. When I get off work I will try cleaning my ports and I have one more pc I can try to use.

Sent from my Verizon GN2
[Verizon Samsung Galaxy Note II] Noobism:
Ya i had a similar issue, got back to stock 4.1.1, ran Casual after, failed on the recovery step :( then had to reflash. So i'm stuck on stock atm. Any idea's why it failed on recovery?
[Verizon Samsung Galaxy Note II] ForeverSupra:
The link is down, does anyone mind sending me the files? Trying to unlock/root a buddys phone.

Edit: Actually Dev Host is down.
[Verizon Samsung Galaxy Note II] bostonbassman78:
Dont try it on the new build cause I dont think they got it working yet I am waiting myself just got my replacement phone today pre installed with 4.1.2
[Verizon Samsung Galaxy Note II] marcustaz:
Houston we have a problem. jrloper or anyone experienced here, would love your opinion here. My sister comes over this evening and I had her phone exactly setup like my wife's. So before accepting the update I restore the stock boot loader. Once there I reboot and accept the update. Phone reboots and the progress bar is there doing its thing... About halfway through the screen goes blank like it powered down and the rest is history... The phone is dead, no battery charging icon no Dl mode, no recovery only thing I get out of it is the faint red led conning out of the proximity sensor region, So I think it is hard bricked and I am just trying to confirm it is and if there is anything I can do before I call VZW for a replacement...
[Verizon Samsung Galaxy Note II] jrloper:
Pull the battery out for 15 seconds, replace it and try to reboot it.

Was there enough charge on the battery prior to accepting the update?
[Verizon Samsung Galaxy Note II] marcustaz:
Tried for 15 sec and then some... Battery was 80% ...
[Verizon Samsung Galaxy Note II] jrloper:
Windows XP isn't supported.
[Verizon Samsung Galaxy Note II] AdamOutler:
Hey guys [MENTION=2918486]Ralekdev[/MENTION] and I have posted the new version here: http://xdaforums.com/showthread.php?t=2270374

This exploit continues to work on the old versions if you have not performed the latest OTA update. If you have updated in the last week, this CASUAL will not help you.. Go here: http://xdaforums.com/showthread.php?t=2270374
[Verizon Samsung Galaxy Note II] jrloper:
Hrm.... Does it vibrate or anything when you hold down the power button for like 10sec?
[Verizon Samsung Galaxy Note II] marcustaz:
Nada, just get a faint red led that flash approx every 8 sec if I keep power held down... Boy she is pissed at me... Any other suggestions? Adam care to chime in? Am I calling Verizon to give them an earful and try and get a phone? I did read on VZW official forums about the 4.1.2 bricking one...
[Verizon Samsung Galaxy Note II] Githrog:
What a minute, what?

So your saying that casual is not compatable with windows XP?
[Verizon Samsung Galaxy Note II] jrloper:
I'll pm you shortly with a work around. technically its the drivers included with CASUAL that don't support XP.

---------- Post added at 10:17 PM ---------- Previous post was at 10:12 PM ----------

Its a long shot, but it worked on my HTC Inspire, when it had very similar symptoms. Leave the battery out over night, then put it back in the morning, plug it in and let it charge foot an hour. Try to turn it on.
[Verizon Samsung Galaxy Note II] Githrog:
Thank you so much

I just wanted to say thank you so much. Everyone just kept blaming it on my usb wire or ports. I knew 3 different machines with XP all couldn't have bad usb ports. I appreciate all your help.
[Verizon Samsung Galaxy Note II] AdamOutler:
Verizon broke it. Its not your fault man. They are updating their bootloaders too much. If you can't get to download mode there's nothing we can do. I looked for an UnBrickable SD/Mod for the device but I couldn't get it to register. Verizon broke it. Verizon can fix it. They made the choice to update booloaders.

NEW JAILBREAK VERSION HERE: http://xdaforums.com/showthread.php?t=2270374
[Verizon Samsung Galaxy Note II] marcustaz:
Thanks dude I'll try but I doubt it will work... If it does though I'll let you know for sure...

I'd figured it was hard bricked... man vzw sucks.... what is the damn point in locking us out, I mean come on, this isn't an Iphone is it?? Guess I'll call in tomorrow and give them an earful... Oh well thanks for responding and confirming.
[Verizon Samsung Galaxy Note II] jrloper:
With Heimdall that error there really isn't anything that can be done, I its just a fluke thing.
[Verizon Samsung Galaxy Note II] bostonbassman78:
Are u guys having anyluck with the newest casual im itching to get my unlock on lol
[Verizon Samsung Galaxy Note II] carhauler1969:
Thread is currently locked, so no.

Sent from another Galaxy on my Note 2 with Tapatalk 2
[Verizon Samsung Galaxy Note II] bostonbassman78:
Dang its all good though ty guys for all that u do for rhe community
[Verizon Samsung Galaxy Note II] jrloper:
I'm not exactly sure what the problem is, I haven't spoken with Adam since last night before he locked the thread. I don't own a Note 2, so I can't do any testing on the new release. Just have to wait and see what he figures out. :(
[Verizon Samsung Galaxy Note II] bostonbassman78:
I pasted my log to pastebin lastnight under the same name bostonbassman78 I also tried it once after I pick up my daughter from school I will try again I got a pm from someone that said they gained root from it lastnight but im looking for root and unlock I know the old one took me a couple tries to get it to work
[Verizon Samsung Galaxy Note II] joshw0000:
Anybody having driver issues on their computer after using the Casual version posted in this thread? I unlocked a Note 2 a few days ago and I had to uninstall my existing drivers and let Casual install them to get it to work. Now I can't get my computer to see either of my Notes unless they're in Camera mode WITHOUT usb debugging enabled. I've removed and reinstalled drivers, let the PC install them automatically, downloaded current adb/fastboot drivers and installed manually, everything I can possibly think of. No matter what, it's only recognized in Camera mode w/o debugging enabled (both phones). Win 8 64 bit.

I can connect to my work computer and both phones are detected in every mode( w/ or w/o usb debugging). W7 64 bit.

Any suggestions on getting it working on my W8 machine again?

Sent from my SCH-I605 using Xparent Green Tapatalk 2
[Verizon Samsung Galaxy Note II] carhauler1969:
With the phone connected via USB open device manager and un-install drivers in Universal Serial Bus Controllers for anything related to your phone, when prompted also delete driver software. Then disconnect & reconnect your phone and let Windows install the correct drivers. That should fix it. I had the same problem with Win 8 x64 myself.

Sent from another Galaxy on my Note 2 with Tapatalk 2