Post Reply

[Jailbreak][Root][Recovery] Back Atcha Verizon-- update 17MAR13:Windows/Linux

OP AdamOutler

26th January 2013, 05:00 AM   |  #1  
UPDATE: new version available here http://forum.xda-developers.com/show....php?t=2272066.

FIRST!!! First jailbreak under the new 2012 DMCA Excemption that is. First "Android Jailbreak" ever... Gah that name erks me... Anyway, You’re here to legally Jailbreak your Verizon Galaxy Note 2.

Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. This is not only the first release of this new Exploit, but it’s also a beta-test of CASUAL. I expect problems... however this will be addressed with updates. See the About CASUAL section below.

We decided to start a new thread becasue the old unlock method is tried and true on Windows with VRALJB. This method is based on a totally new exploit.


Overview
You are expected to be STOCK.... Stock anything, but stock. This will install a stock kernel and that may affect non-stock roms. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?.

Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. If Microsoft VC Redistributable is required, click next, next, next. Make sure you're connected to the internet.

Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:

Mac Users: Mac works easierr than any other system at the time of this release on 32bit systems. Please report problems.


Download
CASUAL(R465b) Back Atcha Verizon CASUAL is used to automate the process. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler. To run CASUAL you need Java. Do you have Java?


Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware Thanks to DroidModderX.




Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful.



About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.


Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
25JAN13: Initial release.
25JAN13: put your device into download mode automatically on Windows. Windows users, let me know if this is annoying. -auto CASUAL update
26JAN13: Instruct Windows users to install the proper bootloader -- auto CASUAL update
26JAN13: more concise directions --auto CASUAL update
7MAR13: Initiated beta test of one-click operation on all platforms!
17MAR13: Cross-platform Heimdall is now in effect with CASUAL R311b
20MAR13: Removed mac blocker from script --auto CASUAL update.
6APR13: kill-switch activated as most of repository has been restructured and drivers/dependencies will not be deployed. This will be resolved soon with a new version.
7APR13: New version includes better driver support via jrloper's CADI and on-the-fly updates for drivers and more. 32/64bit Heimdall for Mac is now supported. Several irrelevant command line features were added as well.
18APR13: CASUAL R417 Several fixes with improved logging and pastebin support thanks to jrloper
2May13: killswitch for old versions implemented.
Last edited by AdamOutler; 11th May 2013 at 02:15 AM.
The Following 238 Users Say Thank You to AdamOutler For This Useful Post: [ View ]
26th January 2013, 05:03 AM   |  #2  
Senior Recognized Developer
Thanks Meter: 380
 
32 posts
Join Date:Joined: Sep 2010
Donate to Me
More
Ironically I probably wouldn't have noticed the hole used this time had they not added the blacklisting of the old versions. Looking at the code for that gave me a push in the right direction
Last edited by Ralekdev; 26th January 2013 at 08:27 PM.
The Following 45 Users Say Thank You to Ralekdev For This Useful Post: [ View ]
26th January 2013, 05:33 AM   |  #3  
Troubleshooting
70% of problems with CASUAL involve USB cables and USB ports. All other problems can be tracked back to Windows XP.

CASUAL Stops and my phone is in Odin Mode/Download Mode
Use a different USB cable and a different USB port. Personally, I have two USB cables which work for everything and anything but they fail when it comes to Odin/Download Mode.

CASUAL displays Disconnected and won't let me press the button
Put your device into ADB mode. Settings>Developer Options>USB Debugging

CASUAL is not working and it's not something above
Did you install drivers? If you installed drivers, you need to uninstall and delete them. You don't need them because Windows installs them. Actually, they're poisonous, and some drivers install themselves with a future date which causes them to be un-upgradable. This means, you've shot yourself in the foot. You can run Samsung Kies and do the troubleshoot connection wizard, or you can go to device manager and uninstall the driver + delete driver.

CASUAL is not working and I'm absolutely sure it's not a driver issue
  1. Let everything sit for a bit. CASUAL will generally pop up a troubleshooting message.
  2. If you're sure nothing has happened for the last 3 minutes, disconnect the USB and restart the device normally.
  3. Restart your computer
  4. Try again using a new stock USB cable, on a different USB port, preferably located in the back of the computer.

I just want to annoy you
First grab a hammer and go outside into the back yard and hit yourself repeatedly in the head. If you do not have a hammer, borrow one from your neighbor. If you don't have a yard, borrow one from your neighbor. If you don't have a head, mission accomplished.
Last edited by AdamOutler; 14th April 2013 at 07:55 PM.
The Following 25 Users Say Thank You to AdamOutler For This Useful Post: [ View ]
26th January 2013, 05:33 AM   |  #4  
Mac version will not be available tonight. I can continue troubleshooting on 1.3.2 to make it work sometimes, but we need Heimdall 1.4.2 built for Mac properly in order to add support.... and that would be the magic bullet. Any mac developers? Here's the source we need built: https://github.com/Benjamin-Dobell/Heimdall Just the command line "heimdall" app is required in mpkg format.
The Following 2 Users Say Thank You to AdamOutler For This Useful Post: [ View ]
26th January 2013, 05:42 AM   |  #5  
cleveratticus's Avatar
Senior Member
Flag North Little Rock
Thanks Meter: 5
 
112 posts
Join Date:Joined: Feb 2011
More
Re: Jailbreak Your Verizon Galaxy Note 2 -- Even after update
I'm still available for testing. I'll be up all night.

Sent from my SCH-I605 using XDA Premium HD app
The Following 2 Users Say Thank You to cleveratticus For This Useful Post: [ View ]
26th January 2013, 06:03 AM   |  #6  
Junior Member
Thanks Meter: 3
 
6 posts
Join Date:Joined: Jul 2008
U DA MAN
Thanks Adam!!!

I have had this phone for a week and the Verizon rep F'ed me up the arse by installing the latest update without even asking me about it.

I worked with your last instruction before I finally realized I was hosed and had no hope.

Imagine my surprise when you announce this update just yesterday!!!!!!!!

I will be working on this first thing in the morning. The only reason I am not doing this now is the king of beers has ahold of me. But not enough to keep me from expressing my gratitude. Expect a dontation!!!!!!!!!!!
Last edited by gwbaker; 26th January 2013 at 06:08 AM.
The Following 3 Users Say Thank You to gwbaker For This Useful Post: [ View ]
26th January 2013, 06:40 AM   |  #7  
M@|ice's Avatar
Senior Member
Flag Noblesville, Indiana
Thanks Meter: 138
 
1,132 posts
Join Date:Joined: Dec 2010
More
any ideas what im doing wrong? im doing something obviously that im not supposed to be....
Attached Thumbnails
Click image for larger version

Name:	fail.jpg
Views:	9042
Size:	196.9 KB
ID:	1677354  
The Following User Says Thank You to M@|ice For This Useful Post: [ View ]
26th January 2013, 06:43 AM   |  #8  
cleveratticus's Avatar
Senior Member
Flag North Little Rock
Thanks Meter: 5
 
112 posts
Join Date:Joined: Feb 2011
More
tried to use the windows version on the family computer.
that is the single most frustrating fail i have encountered.

---------- Post added at 12:43 AM ---------- Previous post was at 12:40 AM ----------

Quote:
Originally Posted by M@|ice

any ideas what im doing wrong? im doing something obviously that im not supposed to be....

Yup. Same here.

Sent from my Nexus 7 using XDA Premium HD app
The Following User Says Thank You to cleveratticus For This Useful Post: [ View ]
26th January 2013, 06:44 AM   |  #9  
Member
Flag Denver
Thanks Meter: 9
 
46 posts
Join Date:Joined: Jan 2013
More
I'm sure I'm just noobing it up...

I flashed back to stock with the BAV baseline and Odin 3.07.

I ran Casual. Everything seems to go fine. Phone reboots to "Downloading, Do not turn off target!!" message.

I flash Suckit Bootloader, and get the following failure in Odin:

<ID:1/004> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> recovery.img
<ID:1/004> NAND Write Start!!
<ID:1/004> FAIL!

Should I bury my head in the sand in shame for an obvious mistake?
The Following 2 Users Say Thank You to Psyanide For This Useful Post: [ View ]
26th January 2013, 06:46 AM   |  #10  
M@|ice's Avatar
Senior Member
Flag Noblesville, Indiana
Thanks Meter: 138
 
1,132 posts
Join Date:Joined: Dec 2010
More
Quote:
Originally Posted by Psyanide

I'm sure I'm just noobing it up...

I flashed back to stock with the BAV baseline and Odin 3.07.

I ran Casual. Everything seems to go fine. Phone reboots to "Downloading, Do not turn off target!!" message.

I flash Suckit Bootloader, and get the following failure in Odin:

<ID:1/004> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> recovery.img
<ID:1/004> NAND Write Start!!
<ID:1/004> FAIL!

Should I bury my head in the sand in shame for an obvious mistake?

thats exactly what im seeing.

i was certain i was doing it all in the correct order.

The Following 3 Users Say Thank You to M@|ice For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes