[Jailbreak][Root][Recovery] No You Verizon -VRAMC3 --update 10MAY13

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,808
0
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
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
Nah.. TWRP detected a problem and threw up a generic error. The problem was that we assigned generic permissions.
 
  • Like
Reactions: greekgod1021

ShotgunSam

Senior Member
Dec 12, 2010
148
9
0
Huntsville
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
 
Last edited:

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,808
0
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
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.
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:
  • Like
Reactions: manbat

2strokenut

Senior Member
Sep 4, 2011
121
14
0
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
 

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,808
0
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
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.
 
  • Like
Reactions: manbat

2strokenut

Senior Member
Sep 4, 2011
121
14
0
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.
 

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,808
0
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
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?
 

2strokenut

Senior Member
Sep 4, 2011
121
14
0
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.
 
  • Like
Reactions: manbat

ztotherad

Senior Member
Aug 17, 2011
2,784
616
193
Illinois
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?
 

carhauler1969

Senior Member
Mar 16, 2010
696
277
0
Purmela,Texas
Going 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.


Sent from another Galaxy on my Note 2 with Tapatalk 2

---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------

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?
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:

Jgun33

Member
Aug 5, 2008
24
1
0
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'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".