[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
I've yet to get Wallet to work on LJB, LL4, or MC3. I've tried every method I can find.


Sent from my SCH-I605 using Tapatalk 2
I will have to confirm this with @Ralekdev, but we do break the chain of trust and change the keys at the highest level. It may affect use of Wallet, but this device was never certified to work with Wallet. I don't think any Verizon device is.
 
  • Like
Reactions: manbat

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,808
0
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
This version of casual will unlock the VRAMC3 firmware, the latest official release from Verizon. So, if you want rooted/unlocked stock then update first. Though I believe Casual will still unlock both VRALJB & VRALL4.


Sent from my SCH-I605 using Tapatalk 2
it was reported that the last version worked with all known firmwares. If that is true, and I'm not going to test it, this will work with all known firmwares.

Theoretically it should work with everything, but I've just not tested yet.
 

pwa2600

Member
Sep 13, 2008
5
0
0
Question

Do I need Odin, and a stock ROM in order to use casual? Where might I find the ROM needed, and I also am completely stock, and have received the most recent OTA update.

Thank you.
 

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,808
0
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
64bit. I did a md5sum and came up with the same hash as dev-host.

I opened the script to see where it was stopping. It appears to hang after this line:

Code:
$HEIMDALL flash --pit "$ZIPFILEsch-i605-16gb.pit" --repartition --BOOTLOADER "$ZIPFILEsboot.bin" --8 "$ZIPFILEboot.img"
Since the next line is having adb wait for the device to come back up I did a battery pull to "restart" and let the phone come back up and then let casual finish.

The first time I didn't get any other prompts. It seemingly finished like your vid shows. I noticed that root didn't stick (tried adb remount and adb shell and wasn't able to su). I tried it a second time and got the popup from this line:

Code:
$IFNOTCONTAINS 3.0.31-414933 $INCOMMAND shell "cat /proc/version" $DO $USERCANCELOPTION Improper kernel, I have detected an unsupported kernel\n  You may continue if you are rooted. Otherwise click stop\n and restart the procedure.
And even though for some twisted reason I did laugh out loud when I was reading the script I didn't get the error on the line that follows that one.

It's weird cause the first thing I did was watch your vid and thought, "dang that's too easy; much easier than having to execute term functions like with the S3..."

Let me know what other info you need. I'm glad to help any way I can.

EDIT: Just re-read your post as I started re-thinking about this again after this post. I thought the heimdall command was successful (even though I saw the error on the screen it says success). Now I understand what the error means after reading your post. The script I have in the jar file appears to be the correct command to be executed in download mode. From what I remember about CASUAL in reading one of your earlier articles you can push updates for it to download, correct? Can I check that it is getting the latest script at runtime or what it is going to execute?
do this:

Code:
sudo rm `which heimdall`
then rerun CASUAL. I think the problem is that you have an old version of Heimdall on your system. The --repartition command is expecting a parameter and its trying to use --BOOTLOADER :). heimdall is still in an RC version and I think you're running RC1.
 
  • Like
Reactions: mikejr83

lovem

Senior Member
Feb 26, 2013
72
10
0
note 2 unlock

message it got: and phone stuck on downloading do not turn off target !!
-------------------
Rebooted & tried another cable in another USB socket & it seamed to work to completion.
 
Last edited:

mikejr83

Senior Member
Dec 10, 2010
362
125
0
do this:

Code:
sudo rm `which heimdall`
then rerun CASUAL. I think the problem is that you have an old version of Heimdall on your system. The --repartition command is expecting a parameter and its trying to use --BOOTLOADER :). heimdall is still in an RC version and I think you're running RC1.
Worked. Like a boss!

Thanks a ton for another super easy one click tool!
 

pwa2600

Member
Sep 13, 2008
5
0
0
Great Job! / Question

Adam,

I want to say, you and the other developers have done an outstanding job! It worked great. The question I have is, the area I am currently in, I would have a 4G signal, but since rooting/unlocking, I only have a 3G. Would this be due to the rooting/unlocking; and if so, do you know what I need to do, to resolve this?

Thank you.

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

Adam,

I want to say, you and the other developers have done an outstanding job! It worked great. The question I have is, the area I am currently in, I would have a 4G signal, but since rooting/unlocking, I only have a 3G. Would this be due to the rooting/unlocking; and if so, do you know what I need to do, to resolve this?

Thank you.
Adam,

As you were, it is 4G again!

Thank you,
 

FAUguy

Senior Member
Mar 1, 2011
921
137
0
South FL
I So you want to reflash a locked bootloader, just to try to unlock it again?

Sent from my SGH-I747 using xda app-developers app
Last night I used ODIN 3.07 to flash back to the original JB stock ROM, then did the OTAs to MC3, rooted it and unlocked it just fine.
Even though the Wallet doesn't work, today I tried to get one of the MultiWindow mods to work, and it boot-looped the phone.
So I went back to ODIN to see if I could flash it back to stock JB again, and now ODIN doesn't even see the phone connected?
Is the because ODIN doesn't work with MC3, or because I rooted/unlocked it?
What can I do at this point to get it back to the original ROM?

EDIT:
Nevermind, I looked in Device Manager and to roll-back the driver that was installed during Adam's root, back to the Samsung driver, now ODIN sees it.
 
Last edited:

jrloper

Senior Member
Jul 29, 2011
335
207
0
Logan, OH
Last night I used ODIN 3.07 to flash back to the original JB stock ROM, then did the OTAs to MC3, rooted it and unlocked it just fine.
Even though the Wallet doesn't work, today I tried to get one of the MultiWindow mods to work, and it boot-looped the phone.
So I went back to ODIN to see if I could flash it back to stock JB again, and now ODIN doesn't even see the phone connected?
Is the because ODIN doesn't work with MC3, or because I rooted/unlocked it?
What can I do at this point to get it back to the original ROM?

EDIT:
Nevermind, I looked in Device Manager and to roll-back the driver that was installed during Adam's root, back to the Samsung driver, now ODIN sees it.
https://www.youtube.com/watch?v=zzghcV8HVVk

Sent from my SGH-I747 using xda app-developers app
 

carhauler1969

Senior Member
Mar 16, 2010
696
277
0
Purmela,Texas
I will have to confirm this with @Ralekdev, but we do break the chain of trust and change the keys at the highest level. It may affect use of Wallet, but this device was never certified to work with Wallet. I don't think any Verizon device is.
Don't get me wrong, I'm not saying that Casual caused this problem with Wallet. It's a known fact that Verizon blocks it on their network on all NFC capable devices. I got it to work once while on 4.1.1, since updating to a 4.1.2 ROM it fails every time no matter what hack, or combination of hacks I try. I've had to completely wipe & reflash my phone twice today due to screwing around with the build.prop so much it would no longer boot :mad::banghead::mad::banghead:
It just pisses me off that they block truly useful apps for no apparent effing reason.
/end rant

Didn't mean to derail your thread. :eek:

Sent from my SCH-I605 using Tapatalk 2
 
Last edited:

ganggreen777

Senior Member
Oct 28, 2010
1,009
103
0
YEA!!!!!

me too nuthin i mean NUTHIN is working . I have tried ( on my laptop) evry usb port evry cable I have and ESPECIALLY the one I have been using that I know works for stuff like this....

The information box scrolls up so fast that I have no idea what it is saying (but I do catch a glipmse) that there is failure in there somewhere. I let is sit for like 5-10 min. I unplug and it says what others have been posting about a fail of some sorts.....I have the most up to date OTA and it was posted in Droid Life that Casual has been 'updated' so I can get unlocked and rooted and ...........ITS NOT HAPPENING....I have tried evrything the op says of what to do if it is not working so....

WHAT now---is this not going to work for me and others (many others) it seems like

it says this:

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

carhauler1969

Senior Member
Mar 16, 2010
696
277
0
Purmela,Texas
YEA!!!!!

me too nuthin i mean NUTHIN is working . I have tried ( on my laptop) evry usb port evry cable I have and ESPECIALLY the one I have been using that I know works for stuff like this....

The information box scrolls up so fast that I have no idea what it is saying (but I do catch a glipmse) that there is failure in there somewhere. I let is sit for like 5-10 min. I unplug and it says what others have been posting about a fail of some sorts.....I have the most up to date OTA and it was posted in Droid Life that Casual has been 'updated' so I can get unlocked and rooted and ...........ITS NOT HAPPENING....I have tried evrything the op says of what to do if it is not working so....

WHAT now---is this not going to work for me and others (many others) it seems like

it says this:

Heimdall Error Report] Detected:
Heimdall failed to initialize protocol; Script halted
[/Heimdall Error Report]
Log or it didn't happen....


Sent from my SCH-I605 using Tapatalk 2
 

FAUguy

Senior Member
Mar 1, 2011
921
137
0
South FL
https://www.youtube.com/watch?v=zzghcV8HVVk

Sent from my SGH-I747 using xda app-developers app
Yeah, did that.
So I was able to get the JB stock ROM to install, then did OTA to LL4 and then OTA to MC3, but
after it installed the MC3, it is stuck on a boot-loop.
Now when I try to flash again in ODIN, to fails:
Get PIT for mapping,
Firmware update start,
boot.img
NAND write start
FAIL.