[Jailbreak][Root][Recovery] No You Verizon -VRAMC3 --update 10MAY13
- Thread starter AdamOutler
- Start date
-
- Tags
- development
Nah.. TWRP detected a problem and threw up a generic error. The problem was that we assigned generic permissions.
Enabling UAC +running the command from command prompt using administrator still gives me the same error. Here is an updated link, in case something changed.
http://pastebin.com/K0s3jynW.
http://pastebin.com/K0s3jynW.
New cable didn't work
anytime I plug my device into a USB port, Windows will detect, say it is one thing, then unmount and detect it as SCH-I605
Once it gets the device into download mode, it mounts it one time and shows it as Samsung gadget serial
---------- Post added at 01:08 PM ---------- Previous post was at 12:34 PM ----------
Reinstalled Drivers, used a new cord, same errors.
http://pastebin.com/yfDSg7sf
anytime I plug my device into a USB port, Windows will detect, say it is one thing, then unmount and detect it as SCH-I605
Once it gets the device into download mode, it mounts it one time and shows it as Samsung gadget serial
---------- Post added at 01:08 PM ---------- Previous post was at 12:34 PM ----------
Reinstalled Drivers, used a new cord, same errors.
http://pastebin.com/yfDSg7sf
Last edited:
I actually don't have access to disable the virus scanner. Can I run this from a virtual linux machine?
K. I think the problems Windows users are having may be a bug we introduced while troubleshooting.
Until we get this fixed, Windows users
Here is the CASUAL Automated Driver Installer. https://android-casual.googlecode.com/svn/trunk/repo/CADI.exe
If you find yourself looping, run this with your device in Download Mode, connected to the USB port you intend to use.
Last edited:
Unable to recognize device after CASUAL
This is the second time after using the CASUAL jailbreak that I'm unable to get MTP or ADB to work. I think CASUAL's Automated (USB)Driver Installer is the culprit. After it installs the driver and everything is done I can no longer get my Win7 computer to recognize my note 2. It wont recognize any samsung phone, at all. I got around this the first time by uninstalling the samsung drivers and reinstalling an older version, however, with my new Note, nothing is working. It will install the samsung android driver and stop there.
I'm out of ideas. I cannot be the only one having this issue.
thanks
This is the second time after using the CASUAL jailbreak that I'm unable to get MTP or ADB to work. I think CASUAL's Automated (USB)Driver Installer is the culprit. After it installs the driver and everything is done I can no longer get my Win7 computer to recognize my note 2. It wont recognize any samsung phone, at all. I got around this the first time by uninstalling the samsung drivers and reinstalling an older version, however, with my new Note, nothing is working. It will install the samsung android driver and stop there.
I'm out of ideas. I cannot be the only one having this issue.
thanks
You're not supposed to install CADI over ADB. That's for Download Mode only. Uninstall the driver and delete from device Manager. You can also use a Linux Live CD until we get Windows fixed.
I didn't do that, I let the program run as intended. It boots into download then asks to install the driver, it won't proceed unless I let it install the driver. Sorry, I should have clarified.
So it asked you to install the driver and then it worked? Or you installed the driver manually? Your two posts leave MANY more questions than you're answering. Did it work? Did you download the driver? Were you sitting there hitting no when it asked you to hit yes?
I apologize, I ran the CASUAL and after it booted into download mode It then asked to install the driver for hiemdall or whatever it is, I had to choose yes or it would not proceed. After it installed, the phone was rooted and bootloader unlocked, just fine.
possibly stupid question, should those who are unlocked already relock and flash the new bootloader or is there real no big change between the vraljb bl and mc3?
i know for the last version it didn't, but i can't account for this version. id want to say no, but I'd wait for Adam to answer it
The only things changed are the bootloader is unlocked, custom recovery installed, and superuser is injected. All of your data, settings, apps, homescreens, etc, etc will remain intact.
Sent from another Galaxy on my Note 2 with Tapatalk 2
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
Why? Why risk it if you're already unlocked? You already have the capability to flash the updated firmware without the need to lock, and then unlock the bootloader. If you just want the latest software flash beanstown106's rooted stock rom, and the VRAMC3 modem.
The bootloader itself has no benefit whatsoever to the end user other than to lock us out of being able to do what we want with our devices.
Sent from another Galaxy on my Note 2 with Tapatalk 2
Last edited:
Nothing will be erased from your phone, however as with always before doing anything to your phone you should make a nandroid backup on an SDCARD
Sent from my SGH-I747 using xda app-developers app
I'm in the same boat. Before CASUAL, my Note 2 talked to my computer fine, I could transfer files back and forth, see it in explorer, etc. Since then, none of my cables or ports will let me access my device except to "connect as camera".
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
148NOTICE: This will not work on the latest firmware updates. Flashing will cause bootlooping and you will have to reload software.
If CASUAL brought you here, your version is outdated.
Well, this has been quite the saga thus far...
Us: Suck It Verizon (exploit)
them: Suck it XDA-Developers (OTA patch)
Us: Back Atcha Verizon (exploit)
them: Stop it XDA (OTA Patch)
Us: No You! (exploit)
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. CTRL+L>Pastebin> come back here and press ctrl+V. We need a log or it didn't happen. 70% of the time when someone posts a general description, we need more information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
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. Make sure you're connected to the internet.
Windows 8 is supported but you must install drivers for Download Mode first. See this post
Windows XP IS NOT supported! If you can make Windows XP work, share the knowledge. XP is 12 years old now, Microsoft and I both discontinued support for Windows XP.
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:
NOTE: Linux 32/64 bit Heimdall may require an update. I will be taking care of it this weekend. If it works, please let me know so I can remove this message.Code:sudo apt-get install openjdk-7-jdk gksu dpkg
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUAL(R515b) No You 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?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
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. While the video uses an old version, the procedure is mostly the same.
image
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.
8May13: After last the issues with this release, I spent 5.5 hours updating to VRAMC3 and .1 testing this package. . It works well, I assure you.. I assume the previous release had a bad MD5. I apologize for any inconvience.
9May13: Initial Release
10May13: Fixed windows driver issue. Added clearer instruction messages to wait (fixed "hanging"). Added better error handling. CASUAL R492 -- killed old versions14
Use Zadig with your phone in download mode.
http://sourceforge.net/projects/libwdi/files/zadig/zadig_v2.0.1.160.7z/download
Options->List All Devices
Select "Gadget Serial" from the dropdown
Click Replace driver
Retry CASUAL.
Also get PM me a link to your newest log, I have to get this CADI issue with Windows 8 figured out.
Sent from my SGH-I747 using xda app-developers app11F.A.Q.
//TODO
General
//TODO
Windows :
//TODO
Linux :
//TODO
Mac OS X :
Heimdall keeps failing with "ERROR: Claiming interface failed!"
You need to disable the default USB drivers with the following commands:
Code:sudo kextunload -b com.apple.driver.AppleUSBCDC; sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl; sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;8Dont post logs here. They're ugly. Use pastebin. Please remove all of that. I specifically said not to post that.
Try it again with a better cable. I see it is disconnecting and reconnecting repeatedly. That's a bad cable if I've ever seen one... Odin mode does not have error correction like ADB. Its really picky about having good cables and a good USB port.
When this works, please post that it worked.6I've bumped R515b to the first post. All previous versions are not supported. Again.. Log or it didn't happen. And the log must say R515b in it
R515b http://d-h.st/vNS
