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

Search This thread

Rhainor

Member
Aug 21, 2009
35
1
Did u try a different usb cable?
Did u start CASUAL 1st?
Did u try a different usb port?
Do u have usb debugging checked?
As I said previously:
SB Debugging is enabled (dev options screenshot here), Windows can access files on the phone, and ADB run from command-line can detect and control the device (tested by running 'adb devices' and 'adb reboot'), but Casual still says "Link status: Disconnected".

I've tried three different USB cables (including the brand-new one that came with the phone), four different USB ports, and even a separate computer, both without pre-installing drivers and with; none of this made any difference.
Yes, I started Casual first.
 
Last edited:

cnmsales

Senior Member
Jan 3, 2011
298
12
Can someone please help? Thanks in advance for any guidance.

Pastebin Log: http://pastebin.com/4VJDbsBD
Windows & 64bit.
USB Debug is enabled.
Samsung drivers are installed and device is recognized when plugged in.
Upon hitting the DO IT button, phone reboots into Andy android screen with message saying "Downloading... Do not turn off target!!"
Root tool then errors out forces a pastebin. Error on tool is as follows:

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]


done


Pastebin log is found below.

http://pastebin.com/4VJDbsBD
 

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,815
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
Can someone please help? Thanks in advance for any guidance.

Pastebin Log: http://pastebin.com/4VJDbsBD
Windows & 64bit.
USB Debug is enabled.
Samsung drivers are installed and device is recognized when plugged in.
Upon hitting the DO IT button, phone reboots into Andy android screen with message saying "Downloading... Do not turn off target!!"
Root tool then errors out forces a pastebin. Error on tool is as follows:

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]


done


Pastebin log is found below.

http://pastebin.com/4VJDbsBD
paste was removed
 

a4_h23

Member
Apr 7, 2010
16
0
Just wanted to mention that it didn't work for me on Mac (10.8.4). Had phone in ADB mode, had 2 different cables to try with (both high quality cables), and even restarted comp and switched USB ports. Never got it to work on Mac. Kept getting an error with Heimdall.

Worked on Windows 7 via Parallels though, easily. Didn't have a single problem.
 

fallen00sniper

Senior Member
Jan 4, 2012
826
147
Everett
www.androidfilehost.com
I had the same issue until I installed the drivers directly from samsung website, if you have any drivers associated with the phone, remove them, if they are windows drivers leave them alone, the ones from samsung website will work and make sure your using a port in the back of your computer or near the power jack if on a laptop.

If anti virus is blocking and is like avast, put it to sleep for a while.
 

biyobe

Senior Member
Apr 29, 2011
319
27
Denver
Can someone please help? Thanks in advance for any guidance.

Pastebin Log: http://pastebin.com/4VJDbsBD
Windows & 64bit.
USB Debug is enabled.
Samsung drivers are installed and device is recognized when plugged in.
Upon hitting the DO IT button, phone reboots into Andy android screen with message saying "Downloading... Do not turn off target!!"
Root tool then errors out forces a pastebin. Error on tool is as follows:

[Heimdall Error Report] Detected:
Heimdall failed to initialize protocol; Script halted
[/Heimdall Error Report]

I was getting a similar error but my virus scan kept popping up to block it. Turned of virus scan and worked fine
 
  • Like
Reactions: carhauler1969

cnmsales

Senior Member
Jan 3, 2011
298
12
I was getting a similar error but my virus scan kept popping up to block it. Turned of virus scan and worked fine

Thanks for the info. I only have MS Security Essentials and am pretty sure real time protection was turned off. Getting ready to try it again, and will post the pastebin if it doesnt work.

---------- Post added at 08:52 PM ---------- Previous post was at 08:47 PM ----------

I was getting a similar error but my virus scan kept popping up to block it. Turned of virus scan and worked fine

Welp, that did the trick. That was the 2nd attempt I had tried to root. Guess I forgot to turn off AV. Thanks for the tip.
 
  • Like
Reactions: carhauler1969

mekeleee

Member
Sep 14, 2010
41
2
hey adam..asked for a collab months back..regarding brd n btrack5r3....easy peasy...now we do kali linux..in case u get bored/wanna challlenge us/u self for a change,...
 

BoostedB18C

Senior Member
Sep 19, 2012
1,313
808
San Jose
What's the point of restating the obvious, unless you're the one who called MS to report this as a malware? Obviously this has nothing to do with the security of Windows and should be called into MS to have them remove it as a threat.

Here you go.

It's the Windows UAC permission elevator I use. Rather than sign my own binaries, I have a pre-signed application that lets me bring up that Yes/No box and run other applications. It's effective consididering I'm not a Windows programmer. If zadig begins signing their binary properly, I can remove that. However, i wouldn't worry about it. it's not malware, it's something which any old malicious application programmer COULD use as malware so your virus scanner flagged it.

Sent From My Sticky Note, Too?
 
Last edited:
  • Like
Reactions: E:V:A

jvaldez33

Member
Sep 16, 2013
15
0
Hello All,

I have successfully flashed another Note II over the weekend and have verified my computer, cable and USB ports are working fine. I too am stuck. After reading nearly 20 hours of posts and looking at different site, downloading different ROM Versions and different PIT files I run into the same problem on one phone. They started a new tread for me here: http://forum.xda-developers.com/showthread.php?p=45910703#post45910703

I read one article that stated the ROM might be "read only" and I'm unsure how to get around this problem. Here is my situation... I can SUCCESSFULLY flash my rom (according to Ordin) but when my phone goes to reboot it simply turns off. I am also unable to get to the "system recovery menu" and reset the device. Ay suggestions would be greatly appreciated.
 

BoostedB18C

Senior Member
Sep 19, 2012
1,313
808
San Jose
Hello All,

I have successfully flashed another Note II over the weekend and have verified my computer, cable and USB ports are working fine. I too am stuck. After reading nearly 20 hours of posts and looking at different site, downloading different ROM Versions and different PIT files I run into the same problem on one phone. They started a new tread for me here: http://forum.xda-developers.com/showthread.php?p=45910703#post45910703

I read one article that stated the ROM might be "read only" and I'm unsure how to get around this problem. Here is my situation... I can SUCCESSFULLY flash my rom (according to Ordin) but when my phone goes to reboot it simply turns off. I am also unable to get to the "system recovery menu" and reset the device. Ay suggestions would be greatly appreciated.

In the OP there is a link for the newer version of Adams casual thread. Also, you didn't start a new thread, you just posted in one of Adams threads.

Sent From My Sticky Note, Too?
 

AlpineMan

Senior Member
Aug 6, 2008
1,769
951
Thank you for this Adam! I just have to ask...any plans in jailbreaking the Verizon Galaxy S4, too?

Thanks!

Sent from my SPH-L900 using Xparent SkyBlue Tapatalk 2
 

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,815
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
In the OP there is a link for the newer version of Adams casual thread. Also, you didn't start a new thread, you just posted in one of Adams threads.

Sent From My Sticky Note, Too?

Yep.. Keep in mind that the nightlies are unstable. For example, I had to disable kill-switching and updates two days ago in order to make things work properly without try-catching a null-pointer exception. However, aside from on-the-fly updates and kill-switch(which has never been used on this exploit), the nightlies are way better than the stable here.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 239
    UPDATE: new version available here http://forum.xda-developers.com/showthread.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.
    45
    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
    26
    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.
    12
    You probly caught it in the middle of a commit. try this: http://d-h.st/6c6

    This is CASUAL Revision 311. This includes quicker startup, a full Open Source stack of software, no Odin, auto-downloads, auto-executes, and it works on Windows and Linux. For Windows you have Drivers and MSRedist (both installed by CASUAL), this is a one-click procedure. We are working on making it easier by the day and expect the next release to be even easier. For now, the driver requires you to select "Gadget Serial" and hit install.

    I will bump this up to the first thread now because I've already tested on Window and Linux. Droid Modder X said he would have a video out soon.
    7
    there no way to unlock boot loader on odin another way ?
    Please stand by. I expect to have everything working again today. The purpose of the down-time is to ensure there will be no Downtime in the future. I'm working on it now...

    Basically, its down because jrloper and myself are reworking and upgrading. the CASUAL repository system. It will soon be infinitely expandable and able to pull resources from anywhere.

    An unfortunate side-effect of this is Quality Control takes a bit of time.. as we test, its getting better, faster, accommodating for more errors, performing more troubleshooting, becoming safer and even accounting for errors in data transfer across the internet.

    Its almost ready.