Nah.. TWRP detected a problem and threw up a generic error. The problem was that we assigned generic permissions.Taking a deep breath...here we go
---------- Post added at 06:05 PM ---------- Previous post was at 05:32 PM ----------
Worked like a charm. Booted right into TWRP. Lost root - but TWRP fixed it
I actually don't have access to disable the virus scanner. Can I run this from a virtual linux machine?Looks like your virus scanner trashed CASUAL before you even ran it. Disable your virus scanner.
K. I think the problems Windows users are having may be a bug we introduced while troubleshooting.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.
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.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
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.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.
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 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.
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.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 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 itGoing to be first time trying this but will this erase everything on my Phone?
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.Going to be first time trying this but will this erase everything on my Phone?
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.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?
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 SDCARDGoing to be first time trying this but will this erase everything on my Phone?
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".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