yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] Character Zero:
So is there something running on the phone after using CASUAL? I am not sure what this means.
[Verizon Samsung Galaxy Note II] LiTDiE:
He means the casual program used to jailbreak would pop up a warning, telling you to come here before proceeding with the jailbreak. Not on your phone.
[Verizon Samsung Galaxy Note II] Character Zero:
Yeah I was confused, once jailbroken I am not sure I what I would use CASUAL for again. Maybe if I took an OTA or something but I plan (and I know other s may not be) to go the custom ROM route.
[Verizon Samsung Galaxy Note II] LiTDiE:
Okay, I'm lost.

Linux user here.

Distro, Linux mint 14.

I have openjdk7 installed. Put phone into usb debug, Fire up Casual, connect phone, and never get the green link connected.

So I tried downloaded Ubuntu 12.10. Running it in Live CD mode.

Install openjdk7. Fire up Casual. And it comes up link connected, green. Problem is, phone isn't connected to the computer at the time.:confused:

Any insight on this?
[Verizon Samsung Galaxy Note II] azbryan3:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

Wow. That was incredibly easy!

Thanks a ton!!
[Verizon Samsung Galaxy Note II] rdeckerr:
Unable to return to stock once OTA Update has been accepted. ODIN Fails to push complete image. I had to use the root66 image to get my phone up and running again. About to test again to see if Kies or ODIN can restore to unrooted stock. If anyone else has run into this, please post.

Also, under the root66 image, only 4 gigs of internal storage are showing up.
[Verizon Samsung Galaxy Note II] BoostedB18C:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

The OP of the thread you linked to has the flashable zip file for cwm. Boot into twrp, flash cwm zip. Reboot into cwm

Sent From My Bean Powered Note2
[Verizon Samsung Galaxy Note II] LiTDiE:
Keep getting this popup.
[Verizon Samsung Galaxy Note II] fofjjsr:
I followed the directions and things seem to have got hung up. Can't tell of it worked.
[Verizon Samsung Galaxy Note II] larry_thagr81:
No

---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------

Are you running root66 stock ROM?

Many people have had success with unlocking there phones when they are running the root66 stock ROM. I didn't realize it myself, but once I looked through my library of ROMs that I had for the Galaxy Note 2, I also realized that I was running root66 stock ROM when I had success with the exploit.

---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------

Have you tried restarting your phone?

Did you turn on USB debugging mode?

Are you running the latest version of Java on your computer?
[Verizon Samsung Galaxy Note II] LiTDiE:
Yes

Yes

and

Yes.

I've tried several versions of java on Linux mint 14 and Ubuntu 12.10

I either, never get the green link from linux mint 14.

Or in Ubuntu, as soon as I start Casual, without the phone being connected, it has the green link.

I'm stumped.
[Verizon Samsung Galaxy Note II] fors8kenAndroid:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

Wow!

This was kind of scary at first with the Note2 being my first Samsung phone. Read Adam's instructions 10 times before plugging the phone in. Worked perfect first try. No issues or error messages. Took right at 4 minutes from launching CASUAL to connecting to Verizon network. Win 7 64 bit and antivirus disabled before starting. Thank's a million Adam!!! larry_thagr81. your instructions were very very helpful too. Thanks again!
[Verizon Samsung Galaxy Note II] AdamOutler:
No. I mean CASUAL will give you a choice: Click a button to bring you here - or - it will bring you here on its own after a countdown.

Either way, You're going here if I flip the kill-switch because i'm not supporting people's ability to read or copy-and-paste.

install libusb. I'm not sure what the package is for Linux Mint. I'm also not sure how to best check if drivers are installed... maybe if nothing has connected after 30 seconds, popup something asking the user to install drivers... apt-get install libusb-1.0-0 on debian.

That's normal. it's fine. That happens on linux when you don't have the MTP set up properly. It's just telling you that you can't access files.

Did it bring you to a custom recover with a big "team win" screen? that's how you know if it worked.

if you just want to root, then just root.
[Verizon Samsung Galaxy Note II] fallingd0wn:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

Worked perfectly on Windows 8. Thanks
[Verizon Samsung Galaxy Note II] gr8dawgs:
Adam, I am on the stock ROM but I had previously rooted with the original ExynosAbuse exploit. Since I am a unix/linux guy (and former physicist who now writes crypto sw), my original attempt was on my primary development machine running Ubuntu 12.04.1 LTS with the latest Java 7. Since I also have adb installed and use it all the time (for off-phone copies of TB backups), I know the USB ports, cable, and connectivity are all good -- I just transferred 1.5 GB from my phone with adb, shutdown the adb server that I had just used, and then tried CASUAL again with the same result - for some reason after the heimdall escalation, it barfs on the connection with the libusb error of -3. (I checked - it is using libusb.0.1-4). Since I do also have an old windows (Vista) box, I have tried it from it as well: installed adb to make sure I'd have good drivers and tested with it, then killed the adb-server I had started and fired up CASUAL and then Odin. Since I was already rooted, I did not flash the BAVBaseline (as per your notes on the download page), but went straight for the gusto with the BackAtcha gzipped tarball. This time it looked promising, but then Odin just "blew up". Since it's a Vista machine, maybe that's a Vista thing. Pulling the battery got me back where I was, so I rebooted the Vista machine and tried one more time with the exact same results. I certainly do appreciate all the effort you've put into this, but so far it's left me pondering my navel. Unless you have another suggestion, at this point I think I'd be willing to send you $100 and fedex the phone to you for the "laying on of hands"!! (If it's relevant, I also have frozen FWupgrade, SDM and keychains in hopes of preventing the OTA, although I did try one quick iteration on the Ubuntu box with them unfrozen.)
[Verizon Samsung Galaxy Note II] rdeckerr:
IMNUTS Rocks!!

Thanks to him and his alternate recovery image (that excluded the sboot.bin which was causing ODIN to fail), I was able to return to stock again.
[Verizon Samsung Galaxy Note II] H3Dude:
Is phone still stock kernel?

Aside from the unlocking, rooting and recovery, is everything else on the phone still the same as the new OTA update after this process. What I mean is, I interpret that after you flash the BAV file, it loads an older kernel so that this process is possible? I'm probably wrong about this. Is the phone still on the older kernel or is it all updated as a stock VRALL4 besides being rooted, unlocked and custom recovery. Thanks in advance.
[Verizon Samsung Galaxy Note II] C1audia:
Pardon me, if I JUST want root, do I just skip the 3rd WIndows Download (Back Atcah Verizon Bootloader)?

Thanks.
[Verizon Samsung Galaxy Note II] larry_thagr81:
If you want to just root, then I believe you can flash the root66_VZW_stock_system file with ODIN after manually putting your phone into downloading mode by turning it completely off and powering it up by pressing volume down, home key and the power button together.
[Verizon Samsung Galaxy Note II] C1audia:
Thanks.

I am currently Stock Rooted with ExynosAbuse.apk, I haven't taken the OTA, but after I do will root66 still work to root?
[Verizon Samsung Galaxy Note II] rdeckerr:
Stock root - not modded

I was stock rooted, no mods. Below may be relevant, it is my saga.

My primary thread trying to figure out how to unbrick:

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

The gist:

1: Returned to stock with imnuts' stock rom @ http://xdaforums.com/showthread.php?t=2040264

2: Allowed the OTA Update to do it's thing.

3: Ran your new JB/root proc for Windows. First time failed, second time hung resulting in a battery pull.

4: Was stuck with the Firmware upgrade has fudged, connect to kies to fix but could still access download mode and for a short while recovery mode with the error stating /system was not found. Kies could not connect.

5: Attempted to redo the stock rom as stated above however it kept failing at the sboot.bin bit.

6: Wanted to see if a different image would flash so I used the root66 mod from droidstyle's guide @ http://xdaforums.com/showthread.php?t=2024207 which worked and got me back into android, though without the ability to activate with verizon and limited to 4gigs of internal storage.

7: Realized that imnuts' alternate restore excluded the sboot.bin bit and it worked. I'm back to stock.

-- 7a: The file download is .xz format. (perhaps meant to be .gz?) Extract it and resulting file will be ODIN compatable .tar.md5

I'll be waiting a bit till I know the re-root method is more stable.

I hope this helps and is relevant. I know at least one other had the same issue I did so this is not an isolated incident.
[Verizon Samsung Galaxy Note II] TonikJDK:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

Use voodoo ota rootkeeper from the party store if you are already rooted. Back up the root, take the ota and restore root of that is all you want. That is what I did.
[Verizon Samsung Galaxy Note II] PsychoSimatic:
So this worked for me, but this morning an update notificiation popped up on my device... Soooo does this exploit let me accept these now? or do i just keep defering??
[Verizon Samsung Galaxy Note II] xdadevnube:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

Once again, fabulous work on the "jailbreak". The community benefits greatly from the work of a few.
[Verizon Samsung Galaxy Note II] AdamOutler:
OK, i just did this procedure in a Windows virtual machne. I had 0 problems.

Considering all the additional problems Virtual Machines causes, there can not be possibly ANYTHING wrong with the exploit or procedure as it is currently. If you're having a problem, it's something you did to your computer or something you did to your device.

If you're having problems.... you're probly on windows. Windows is a PITA. Here's some basic stuff you should know:

1. Flash your device back to stock! totally, every single bit. if you have installed an app that roots and patches, get rid of it by flashing back to stock.

2. Reboot everything.. if you already did, do it again.

3. Make sure USB debugging is turned on (sometimes it turns itself off)

4. Turn off firewalls. ADB uses networking.

5. Try a faster computer. If ADB cannot transfer everything in 15 seconds, your phone's adb connection will cut it off. If you're on a computer that came with Windows XP.. Get a new computer. It takes 5 seconds from the time the device connects to the time it reboots again during the middle part of the exploit.

6. Get a copy of Ubuntu from http://ubuntu.com/download and don't get a copy that's older than your device or you'll have to do updates. 12.10 or higher.
[Verizon Samsung Galaxy Note II] Character Zero:
I know this has been asked a few times but hadn't seen an answer. If you have not accepted the OTA, what is the preferred method of jailbreak. The original or the new?
[Verizon Samsung Galaxy Note II] AdamOutler:
It does not matter. This new method works on both.
[Verizon Samsung Galaxy Note II] Character Zero:
Thanks for confirming.
[Verizon Samsung Galaxy Note II] fofjjsr:
So I finally got everything done. Got my stock root installed. It is still asking me for the update though. If I download it will it unroot me again?

I just used the stock root.

Edit: NVM the OTA update failed. Question answered.
[Verizon Samsung Galaxy Note II] H3Dude:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

Seemed to work without issue. When I try to boot to bootloader in TWRP it just reboots phone. Also, in ODIN mode (done manually) it states Samsung Official, Status Official. Is this normal? I saw Status Custom on someone elses. I do have Root access. It did give me. Warning about flashing custom ROMs though in ODIN mode. Press up to cancel or down to proceed.
[Verizon Samsung Galaxy Note II] delaneybob:
Thanks a TON!!!! It said unsupported but I went ahead anyway
[Verizon Samsung Galaxy Note II] imstu:
OTA question

I just rooted/unlocked yesterday using the old method (Odin) on my pre-OTA phone. I am trying to keep my phone fairly stock at this point (mostly due to being a Noob). My main purpose is to "jailbreak" it so I can update APN info so I can use it for data (internet) overseas. This is critical for me and it was the primary reason I went from my Droid X2 to the Note 2. This morning I saw this post-OTA method and re-rooted using the method here and it worked flawlessly. Then I got thinking...should I have done the OTA after going back to baseline and before doing Backatcha? I hear it gives you more functions (multiple windows etc). Please advise. My phone was scheduled for the OTA tomorrow morning at 0500.

Thank you very much Adam for all your hard work to make this happen!

Stuart
[Verizon Samsung Galaxy Note II] hopesrequiem:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

You could do multiwindow before the ota even dropped? Sorry if I'm misunderstanding you
[Verizon Samsung Galaxy Note II] LiTDiE:
Both Linux mint and Ubuntu have libusb installed.

The phone connects to the computer, it's how I transfered Beans rom to the SD card.

The version of linux mint I'm using is 14, which is a port of Ubuntu 12.10.

Does ADB server need to be running?

-edit-

*****@*****-desktop ~ $ sudo apt-get install libusb-1.0-0
[sudo] password for *****:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libusb-1.0-0 is already the newest version.
The following packages were automatically installed and are no longer required:
libX11-dev libatk-wrapper-java libatk-wrapper-java-jni libice-dev
libpthread-stubs0 libpthread-stubs0-dev libsm-dev libx11-doc libxau-dev
libxcb1-dev libxdmcp-dev libxt-dev x11proto-core-dev x11proto-input-dev
x11proto-kb-dev xorg-sgml-doctools xtrans-dev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.

I have also been trying this on Ubuntu 12.10, through a live dvd. On there, it have the green connected, even when the phone is NOT connected to the computer.
[Verizon Samsung Galaxy Note II] universexda:
Why are doing root66? You have root66 functionality with what you have now. Don't accept the OTA. If you want to flash ROMS or MODS unlock the bootloader with the tools and methods already available for VRALJB in XDA Original Development.
[Verizon Samsung Galaxy Note II] RootedUser:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

What is the point of this jailbreak by the way? Just asking so I know. My bootloader never got locked because I didnt accept the ota.
[Verizon Samsung Galaxy Note II] hopesrequiem:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

The bootloader was locked out of the box. Ota just made it a littlr worse but adam already solved it like a boss.

Thank you so much Adam. Just did this scared as hell. Worked first time with ease. Thanks again
[Verizon Samsung Galaxy Note II] RootedUser:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

Ok, so I take it this permently unlocks the bootloader?
[Verizon Samsung Galaxy Note II] larry_thagr81:
Yes as long as you don't accept any future OTA updates.
[Verizon Samsung Galaxy Note II] nswenson:
Thank you! You saved me a lot of troubleshooting. Same issue, stuck at Nand write. I was stock, except I had installed Chainfire's root exploit and then installed the Verizon OTA, preserving root with Voodoo. I suppose that is what screwed me, having Chainfire root plus Voodoo to restore root.

Thanks again! My bootloader is unlocked and I'm booted into the custom recovery.
[Verizon Samsung Galaxy Note II] FAUguy:
To help people out (that may not know how to root) I posted a news story about it over on PhoneArena, credit given to Adam.

http://www.phonearena.com/news/Root...II-even-after-the-new-software-update_id39153
[Verizon Samsung Galaxy Note II] DroidXcon:
Re: Jailbreak / Root / TWRP Recovery -- Even after update [26JAN13]

From my Galaxy Note 2 via Tapatalk
[Verizon Samsung Galaxy Note II] zeroshadow21:
It worked perfect. Thanks for all the work you guys have put into this.
[Verizon Samsung Galaxy Note II] uwflatlander:
I am using Ubuntu 12.10 and it is not working with me with Sun Java or with the OpenJDK. I keep getting this error after it boots the phone into download mode:

Any idea what I can do to get around this?
[Verizon Samsung Galaxy Note II] Acery:
Thank you for the workaround, Adam.

I was coming from a Droid 3 where I was using Safestrap and one click roots to get things done. It seems the Note 2 was a little more complicated.

I have a question to clear up some misconceptions on my part because I'm so used to working around the boot loader versus working with the bootl oader. Bear in mind I've graduated from the Droid 3 to the Note 2 and the droid three was locked down tight.

My question looks like it was answered earlier but the phrasing was not conclusive for me so I apologize for asking it again on my own terms.

There is no additional memory being used if we are running stock TW after applying your root method as described herein in your OP?

- Yes, I did install the Baseline AND back Atcha patches. I noticed someone else used a different flash after the Baseline flash to avoid the teamwin boot recovery.

Also, the teamwin boot recovery is utilizing the bootloader of the phone directly and it is not a "safestrap" workaround?
[Verizon Samsung Galaxy Note II] AdamOutler:
OK. There's something broken. Update your java. If that does not work, I will post up the development copy I have currently. It looks like your java is out of date. Openjdk-7-jre is the package you need.
[Verizon Samsung Galaxy Note II] brife:
Thanks!

Just got my note2 a week ago and I took the OTA before I know what was good for me. Just worked the magic in the this thread's first post though and it was dead solid simple. Thanks to all that had a hand in it!

Also, my previous experiences with custom recoveries has been CWM and SafeStrap. I haven't spent that much time with TWRP but from what I've seen so far, I like it. :)
[Verizon Samsung Galaxy Note II] blaksmyth:
Success

The process was quick and painless on windows 8. Thank you Adam.
[Verizon Samsung Galaxy Note II] thekyguy11:
Took me several tries, but I eventually got it to work.

The only problem I had which I don't think was my fault (the rest of the problems were), is that every time I wanted to run the CASUAL application, I had to re-download it, or it wouldn't open. I did have my antivirus disabled, to prevent issues there. Anyone else have this issue?

Also, while I was struggling to get it to work, I Odin back to root66, then was able to get everything here working. I did everything listed here, however, it was before accepting the OTA, which will not install now. Should I disable the OTA reminder and not worry about it, or redo everything, post OTA?

Thanks.
[Verizon Samsung Galaxy Note II] nswenson:
You are done. Install a custom rom like CleanRom Ace and you'll have the latest build and avoid the OTA reminders.
[Verizon Samsung Galaxy Note II] Acery:
From what I gather, you need to be on the latest OTA to use this new method.

I used this method after a verizon rep updated my phone "for me" when I went in for a 4g chip since my droid was a 3g phone.

Using the steps in the OP, everything worked for me without issue.

Win 7 64 bit
[Verizon Samsung Galaxy Note II] AdamOutler:
Each time you start CASUAL, it creates a new randomized environment. The chances of collision are 1:7^16 which is roughly a 1 in 30,000,000,000,000,000 chance that anything that happened last time you opened CASUAL would affect anything that happens next time. On top of that, CASUAL should redeploy its environment and clobber most things in its folder.

There's something else going on.
[Verizon Samsung Galaxy Note II] LiTDiE:
Ok, I've now installed ubuntu 12.10 on a seperate partition, updated everything, installed openjdk jre 7, and I'm still having the same problem.

Without the phone connected, when I open casual, it comes up Connected.

The phone is NOT connected, but it's saying it is.
[Verizon Samsung Galaxy Note II] AdamOutler:
Please hit do it and send the log from about>show logs. Put the log in here in

tags.

Do you have any other devices connected? If you do, when you plug in, CASUAL will say "two devices detected please remove a device."
[Verizon Samsung Galaxy Note II] LiTDiE:
Fresh install of Ubuntu 12.10 64bit fully updated.

Java 7u11 installed.
[Verizon Samsung Galaxy Note II] thekyguy11:
So I don't have to worry about the "security hole" or "exynos vulnerability" that everyone was talking about the last few weeks? Did the OTA even address that, or was it just an attempt to stop us from unlocking the bootloader? Thanks guys.
[Verizon Samsung Galaxy Note II] AdamOutler:
Hmm.. it executed adb and returned e

Device List:CritERROR!!!.

CritERROR is a catchall for file not executable/not found.

Other than ADB, things look normal... try this from a terminal... but only if you haven't rebooted.

I want the results from these commands

file /tmp/TempCASUALC9E2FB8B/adb
uname -a
/tmp/TempCASUALC9E2FB8B/adb
/tmp/TempCASUALC9E2FB8B/adb devices

Another thing to try would be get the location of ADB from a working log and replace it with one which works on your system.

I have a feeling it may be related to Linux32 versus Linux 64.
[Verizon Samsung Galaxy Note II] Character Zero:
So in setting up my Live USB I am using Ubuntu 12.10 32 bit. While I won't be jailbreaking the phone until tonight, my test runs of running CASUAL to make sure it is ok, it comes up Disconnected (like it should). Maybe try the 32 bit version of Ubuntu (shot in the dark)

Also in Windows 7 I found that if I installed the 64 bit version of Java, when I ran my 32 bit version of Firefox it couldn't find the Java. So maybe there is some kind f 32/64 bit conflict going on.
[Verizon Samsung Galaxy Note II] LiTDiE:
Image of the output posted below.

Now that I've seen the output, I'm thinking I need 32 bit. Will try after downloading and burning with brasero.
[Verizon Samsung Galaxy Note II] Morkai Almandragon:
I would like to just confirm, If I wanted to completely start over with a fresh Verizon Note 2, I could return to stock LJB, update to LL4, and then follow this to root and "jailbreak"?

Also this looks like once that is done you would have the LL4 update, with the LJB kernel? And which recovery?
[Verizon Samsung Galaxy Note II] LiTDiE:
Ok, Confirming, you NEED Ubuntu 32bit.

Again, 64bit ubuntu will NOT work.

Might want to update the initial post to include that.
[Verizon Samsung Galaxy Note II] Character Zero:
So you got it to work?
[Verizon Samsung Galaxy Note II] LiTDiE:
In the process of doing it now.

Just resetting phone, then going to run exploit.

Will report back in 5-10 minutes.
[Verizon Samsung Galaxy Note II] AdamOutler:
Ok... that's a problem with CASUAL. I need to deploy a 64 bit binary. I have a 64 bit setup, but there's a 32 bit library on my system that handles 32 bit files. I will make an update and post it here. There should be no need to kill-switch.
[Verizon Samsung Galaxy Note II] thepolishguy:
Just to confirm - bc I also am running 64 bit and I also get the "device attached" dialog when the device is not attached...

We will need to download this 64 bit version of Casual and then use that - correct?

Thanks.
[Verizon Samsung Galaxy Note II] LiTDiE:
Ok, well, just to confirm.

I am trying from Ubuntu 32bit with openjdk 7.

Got an error, and had to pull battery to reset.

libusb error of -3

That came up, status went to disconnected, and it hanged.