Don't have a clue, the link is working fine for me
Sent from another Galaxy on my Note 2 with Tapatalk 2
[Jailbreak][Root][Recovery] Back Atcha Verizon-- update 17MAR13:Windows/Linux
- Thread starter AdamOutler
- Start date
-
- Tags
- development
Sent from another Galaxy on my Note 2 with Tapatalk 2
Did you do this DURING the process? I've had the same issue, where it hangs up in the middle and can't seem to find the phone again and get it to boot back to Android. You are saying you unplugged it, pulled the battery, put it back, plugged it in, it rebooted, and then it WORKED?
I've actually suggested a manual pause where we reboot it, but it didn't dawn on me you could force it in that manner. No wonder you've bricked phones
I did try this--after also bombing out with Windows, and it didn't work. I have no idea how it worked for you.
You pull the battery, reboot and start over.
Also posting your log ("About" -> "Show Log" ) either here or on pastebin.com would help a lot
Sent from my SGH-I747 using xda app-developers app
Last edited:
This is where it stopped on me. First off I already had my back cover off, I unplugged, pulled battery, plugged back in, replaced battery, turned on. As soon as it booted up, the process continued like it was supposed to, and was 100% successful. Also, it was the 3rd try. I tried new usb cables and new usb ports, all with the same result. Which was why I thought screw it, I'll manually reboot it. That is what casual was supposed to do anyway..
---------- Post added at 06:36 AM ---------- Previous post was at 06:33 AM ----------
Bummer, I was hoping someone else would get my same experience. I don't know why it worked for me either. Whenever I do something like this it never goes smooth like everyone else reports.. So I was shocked when it worked..
---------- Post added at 06:45 AM ---------- Previous post was at 06:36 AM ----------
You are one brave dude, I'll give you that!
As I said, I suggested to the developer he allow us to do a manual restart at that point--I guess I didn't think to just try it. You are saying Casual just sat until the phone rebooted into Android, then did it's thing? So, the question is, why does Casual boot into Bootloader in the first place, since it doesn't seem to do anything until it goes back into Android, other than start Heimdall.
I thought the same thing. It looked to me like all it did at first was check your drivers, and install something on your computer, boot your phone into dl mode then when it was time to reboot it gets stuck. And from the responses on here a few others are getting the same hangup. But another guy said he tried what I did without success.. And in answer to your question, yes. Casual didn't seem to care that I had unplugged. Its like it was dormant waiting for the phone to reboot. So when I rebooted it, it acted like it had done it and was successful. So I don't know why it worked for me, but it made sense in my head and it got my phone rooted... So thumbs up for me right?
---------- Post added at 07:03 AM ---------- Previous post was at 06:50 AM ----------
Gotcha, I didn't catch that part..
Last edited:
okay, so that i can get this right; on L4 do i need to flash the previous bootloader before i run Casual?
i was reading the other thread and that's what i got from that thread, but before i did it i wanted to check in here. also should i flash a clean VZW stock rom before i do anything?
I'm confused about the steps to get casual to run correctly.
if needed, I'll post my log later tonight or tomorrow. thanks in advance!
i was reading the other thread and that's what i got from that thread, but before i did it i wanted to check in here. also should i flash a clean VZW stock rom before i do anything?
I'm confused about the steps to get casual to run correctly.
if needed, I'll post my log later tonight or tomorrow. thanks in advance!
CASUAL expects a stock phone, but it will look work on previously rooted phones. I would flash stock, including bootloader.
Sent from my SGH-I747 using xda app-developers app
that's what i figured, my phone is bone stock at the moment. I'm also on the newest 4.1.1 build, i just can't seem to get my computer, or another one to see my note 2. I've installed countless drivers, uninstalled them and then reinstalled them but nothing. so i figured it may just be easier to reinstall Windows and start from there.
You can uninstall the driver pack, but Windows will keep any files it needs for installed devices.
Download USBDeview:
x86: http://www.nirsoft.net/utils/usbdeview.zip
x64: http://www.nirsoft.net/utils/usbdeview-x64.zip
Make sure your phone isn't plugged in, and run USBDeview, under options make sure the only things that are checked are "Display Disconnected Devices" and "Mark Connected Devices". Any devices you see in Green, are connected devices. All the others are disconnected devices, select all "Samsung" disconnected devices and right click -> "Uninstall Selected Devices".
Once that completes (make sure you have Kies or the newest Samsung driver pack installed), plug in your phone. Windows should install the , (assuming you have USB debugging enabled) Samsung Mobile USB Composite Device driver, Samsung Mobile USB Modem driver, Samsung Android ADB Interface driver, and the N7100 driver.
FINALLY!!! it works! got superuser and recovery!
when i first tried casual, it stopped and got stuck on 'downloading'. This happened when it was installing some driver and didnt go through. so i unplugged and the battery, put everything together and it was processing through but failed.
So i tried it once more knowing every driver is installed and it actually booted on its own and flashed everything without a flaw!
Thank you for the support and I am so happy and relieved i got it unlocked and rooted!
This is BEAST!!
when i first tried casual, it stopped and got stuck on 'downloading'. This happened when it was installing some driver and didnt go through. so i unplugged and the battery, put everything together and it was processing through but failed.
So i tried it once more knowing every driver is installed and it actually booted on its own and flashed everything without a flaw!
Thank you for the support and I am so happy and relieved i got it unlocked and rooted!
This is BEAST!!
damn, lucky! I'm still fighting mine. im in the process of attempting to reinstall Windows 7 since its being such a finicky *****, lol
Just as a reminder, guys... if you're having problems, use CTRL-L and hit the pastebin button, then paste the link here. This will give us the log in a readable format.
JR.
OK, I got Casual to run on Windows. It's all about the drivers. My IT guy told me Kies is a terrible program, so I uninstalled it, and then uninstalled the drivers. I then found the Samsung link to the drivers for this phone, and installed them. I tried to find the ADB drivers separately, but without installing the entire Android SDK couldn't, so figured I'd just try what I had. As it turns out, when Casual runs, it will cause the drivers it needs to be installed from the Samsung installer, and it worked flawlessly!!! So, after a long and twisting road, I got Casual to work, and it did the job perfectly!
Thanks for your help. The key, so far as I'm concerned, is to be sure everyone installs the Windows drivers from the Samsung installer, prior to beginning. I think it also helps to follow your suggestion above, and use USBDeview to inspect the phone drivers already on the system, and clean out any Samsung drivers there are, before installing them fresh.
Regarding the Mac, which I tried first, I have no idea what's wrong, but it appears to be related to ADB. I'd be willing to test it if you can make any improvement, and I'll just unplug the phone if it gets going, since it's already jailbroken. I have no idea what the issue might be between a 32 bit and 64 bit Mac, but I do know any Mac less than 5 years old is 64bit.
N
OK, I got Casual to run on Windows. It's all about the drivers. My IT guy told me Kies is a terrible program, so I uninstalled it, and then uninstalled the drivers. I then found the Samsung link to the drivers for this phone, and installed them. I tried to find the ADB drivers separately, but without installing the entire Android SDK couldn't, so figured I'd just try what I had. As it turns out, when Casual runs, it will cause the drivers it needs to be installed from the Samsung installer, and it worked flawlessly!!! So, after a long and twisting road, I got Casual to work, and it did the job perfectly!
Thanks for your help. The key, so far as I'm concerned, is to be sure everyone installs the Windows drivers from the Samsung installer, prior to beginning. I think it also helps to follow your suggestion above, and use USBDeview to inspect the phone drivers already on the system, and clean out any Samsung drivers there are, before installing them fresh.
Regarding the Mac, which I tried first, I have no idea what's wrong, but it appears to be related to ADB. I'd be willing to test it if you can make any improvement, and I'll just unplug the phone if it gets going, since it's already jailbroken. I have no idea what the issue might be between a 32 bit and 64 bit Mac, but I do know any Mac less than 5 years old is 64bit.
N
libusb error: -12
My phone kept running the libusb error: -12 driver error constantly over and over again with cmd popping up infinitely. So i fixed it by following jrloper (credits below).
Follow below
Make sure you are in the download mode (after constant error, you can close Casual and follow below)
Make sure virus protection and firewall is off, just to make sure.
Download 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".
After it is done take out the battery then back in, and power on the phone.
Once on homescreen, Run Casual again and it should work.
Just for reference:
I had these drivers installed prior to running Casual and running into the constant error
http://www.samsung.com/us/support/owners/product/SCH-I605ZWAVZW
(Straight from Samsung VZW Note 2 drivers)
Credits to:
carhauler1969
and
jrloper
http://xdaforums.com/showpost.php?p=40343968&postcount=10
My phone kept running the libusb error: -12 driver error constantly over and over again with cmd popping up infinitely. So i fixed it by following jrloper (credits below).
Follow below
Make sure you are in the download mode (after constant error, you can close Casual and follow below)
Make sure virus protection and firewall is off, just to make sure.
Download 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".
After it is done take out the battery then back in, and power on the phone.
Once on homescreen, Run Casual again and it should work.
Just for reference:
I had these drivers installed prior to running Casual and running into the constant error
http://www.samsung.com/us/support/owners/product/SCH-I605ZWAVZW
(Straight from Samsung VZW Note 2 drivers)
Credits to:
carhauler1969
and
jrloper
http://xdaforums.com/showpost.php?p=40343968&postcount=10
Last edited:
yeah I've had problems getting with adb not seeing my note 2, but prior to that it's see my fascinate so idk what went wrong there
I think I'm ready to try this, but I just want to be smart about this before I jump into this:
-I've rooted my phone with this method, http://xdaforums.com/showthread.php?t=2024207, but I haven't touched any custom recovery, any custom rom or kernel yet, and according to some posts I'm reading here, it shouldn't matter if I've rooted the phone; as long as it's VRALJB or VRALL4, correct?
-As I watch the tutorial for Win users, I'm a bit perplexed at the end; what do I do with TWRP when that pops up? It's a type of custom recovery, OK, but I honestly have no clue as to what it is, what to do with it, etc. Does it replace the bootloader and that will come up everytime I reboot the device? (Let me just put on my flame suit, gimme a sec...)
-Does this disable any possible chance of receiving future VZW OTA updates? Even if I were to manually select "check for software updates"?
-I've rooted my phone with this method, http://xdaforums.com/showthread.php?t=2024207, but I haven't touched any custom recovery, any custom rom or kernel yet, and according to some posts I'm reading here, it shouldn't matter if I've rooted the phone; as long as it's VRALJB or VRALL4, correct?
-As I watch the tutorial for Win users, I'm a bit perplexed at the end; what do I do with TWRP when that pops up? It's a type of custom recovery, OK, but I honestly have no clue as to what it is, what to do with it, etc. Does it replace the bootloader and that will come up everytime I reboot the device? (Let me just put on my flame suit, gimme a sec...)
-Does this disable any possible chance of receiving future VZW OTA updates? Even if I were to manually select "check for software updates"?
Yes Casual will root & unlock all known firmwares on the Verizon Galaxy Note 2 SCH-I605.
Yes it completely disables OTA updates from Verizon.
You can do whatever you want when recovery comes up, reboot the device, make a nandroid backup, flash a custom ROM, or kernel. The only time recovery will come up is if you specifically boot to recovery. Otherwise the boot process is the same as it is now on your rooted stock device, or a stock phone for that matter.
The custom recovery just allows you to make backups, restore backups, or flash custom software and other tweaks on your phone painlessly.
Before doing any of that I'd really suggest you read up on what root actually is, the power it gives you over your device, and the pitfalls of running custom highly modified software on your phone. If you don't know what you're doing you can easily turn your phone into a $600 "brick" i.e. paperweight.
Sent from another Galaxy on my Note 2 with Tapatalk 2
Last edited:
Okay so on my 2012 Imac, I downloaded java and downoaded Casual. Casual Opens and when I plug my Note in I am able to click do it. Now, before I do this is there anything else I should download or do? I'm sort of a noob and cannot find any help on Mac's Thanks!
Thanks!
Of course. I've been reading the basic glossary of every term I can find, and I'm not about to blame the guides I've found so far for not going in-depth on everything. I've just never had an Android device until recently and its methods of establishing administrative permissions are the most unconventional I've seen in any OS (or maybe it's just VZW/TW).
I'll keep browsing for better tips before I do this but I do have a permanent 2-year warranty with my phone, regardless of rooting. I should be safe with screwups, but I prefer to get it right the first time.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
239UPDATE: new version available here http://xdaforums.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.26Troubleshooting
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
- Let everything sit for a bit. CASUAL will generally pop up a troubleshooting message.
- If you're sure nothing has happened for the last 3 minutes, disconnect the USB and restart the device normally.
- Restart your computer
- 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.12You 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
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.
