• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] [OUTDATED][GUIDE][MD7][MG2] Rooting & Recovery for Galaxy S3(VM)

Yes. I also have MG2. After enough problems with CWM I went to TWRP. No issues so far. I did it via Odin.

FYI seems every time I flash via Odin it takes a good 3min to finish - when success appears.

I'm at work now till late. I'll post the Odin TWRP recovery I used. I guess you could go to there website an try the newest sprint version, but I already took that chance and know the one I flashed works.

EDIT HERE:
If you want to use TWRP instead of CWM (I like it better) Flash via Odin this:


http://www.mediafire.com/?y5788dzl1e5ck4h
 
First, thank you for a very informative set of instructions and subsequent thread. Unfortunately I can't get it to work. The process isn't that complicated, so I'm sure I've gotten it right. This is what I'm getting:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
3198 KB/s (1283460 bytes in 0.391s)
[*] Pushing root tools...
3159 KB/s (366952 bytes in 0.113s)
3181 KB/s (1867568 bytes in 0.573s)
2951 KB/s (1578585 bytes in 0.522s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.

Superuser gets installed but the phone isn't rooted. Is there a verbose setting? Any way to get the nature of the failure to display? My new phone runs the following:
Android Version 4.1.2
Baseband Version L710PAMG2
Build Number JZ054K.L710VPAMG2

Any help would be appreciated.

Thanks,
Anthony
 
Berone said:
First, thank you for a very informative set of instructions and subsequent thread. Unfortunately I can't get it to work. The process isn't that complicated, so I'm sure I've gotten it right. This is what I'm getting:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
3198 KB/s (1283460 bytes in 0.391s)
[*] Pushing root tools...
3159 KB/s (366952 bytes in 0.113s)
3181 KB/s (1867568 bytes in 0.573s)
2951 KB/s (1578585 bytes in 0.522s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.

Superuser gets installed but the phone isn't rooted. Is there a verbose setting? Any way to get the nature of the failure to display? My new phone runs the following:
Android Version 4.1.2
Baseband Version L710PAMG2
Build Number JZ054K.L710VPAMG2

Any help would be appreciated.

Thanks,
Anthony
Click to expand...

I personally used Chainfire's SuperSU zip in place of the superuser zip. I have always been partial to SuperSU but that's a matter of preference. You can find the zip here. Just download the flashable zip from this thread and install through recovery: http://forum.xda-developers.com/showthread.php?t=1538053
That should work :)
 
Berone said:
First, thank you for a very informative set of instructions and subsequent thread. Unfortunately I can't get it to work. The process isn't that complicated, so I'm sure I've gotten it right. This is what I'm getting:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
3198 KB/s (1283460 bytes in 0.391s)
[*] Pushing root tools...
3159 KB/s (366952 bytes in 0.113s)
3181 KB/s (1867568 bytes in 0.573s)
2951 KB/s (1578585 bytes in 0.522s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.

Superuser gets installed but the phone isn't rooted. Is there a verbose setting? Any way to get the nature of the failure to display? My new phone runs the following:
Android Version 4.1.2
Baseband Version L710PAMG2
Build Number JZ054K.L710VPAMG2

Any help would be appreciated.

Thanks,
Anthony
Click to expand...

If you look at the batch script, this is the code to run in ADB:

@echo off
cd "%~dp0"

echo [*]
echo [*] Motochopper: Android root exploit (Windows version)
echo [*] v1.1
echo [*] by Dan Rosenberg (@djrbliss)
echo [*]
echo [*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
echo [*] Supports lots of other devices as well. ;-)
echo [*]
echo [*] Before continuing, ensure that USB debugging is enabled, that you
echo [*] have the latest USB drivers installed, and that your phone
echo [*] is connected via USB.
echo [*]
echo [*] WARNING: This will likely void the warranty on your device. I am
echo [*] not responsible for any damage to your phone as a result using this
echo [*] tool.
echo [*]
echo [*] Press enter to root your phone...
pause
echo [*]

adb kill-server

echo [*] Waiting for device...
adb wait-for-device

echo [*] Device found.

echo [*] Pushing exploit...
adb push pwn /data/local/tmp/
adb shell chmod 755 /data/local/tmp/pwn

echo [*] Pushing root tools...
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb install Superuser.apk

echo [*] Rooting phone...
adb shell /data/local/tmp/pwn

echo [*] Cleaning up...
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox

echo [*] Exploit complete. Press enter to reboot and exit.
pause
adb reboot
adb kill-server

From what I can tell, there are no blocked directories that ADB is trying to access. My simple GUESS would be that Samsung already patched the exploit known as "pwn" (maybe with the MG2 update).

EDIT:

I've also tried about three other one-click methods, namely motochopper, debugfs, and SRS Root; and all have failed. Most of the one click methods are exploits that are relatively easy to patch in updates. The only thing that can really breach it is brute force via ODIN. You're actually modifying a partition of the memory: /dev/block/mmcblk0p18 to be exact. This is where the recovery resides.

However, as we all know the downside to ODIN is that you're device status becomes "modified", and OTA updates are out of the question henceforth.
 
After a rookie mistake I got it to work using the PC steps running Parallels on my Macbook. Rooted! Let's see what's next...

Higgs_Boson said:
From what I can tell, there are no blocked directories that ADB is trying to access. My simple GUESS would be that Samsung already patched the exploit known as "pwn" (maybe with the MG2 update).

EDIT:

I've also tried about three other one-click methods, namely motochopper, debugfs, and SRS Root; and all have failed. Most of the one click methods are exploits that are relatively easy to patch in updates. The only thing that can really breach it is brute force via ODIN. You're actually modifying a partition of the memory: /dev/block/mmcblk0p18 to be exact. This is where the recovery resides.

However, as we all know the downside to ODIN is that you're device status becomes "modified", and OTA updates are out of the question henceforth.
Click to expand...
 
Hi everybody, please forgive my noobness. I recently got the (VM) S3 and after completing this awesome and detailed rooting tutorial Im' left wondering "what do I do now?"
Do I make a back up of my phone? What are some of the more important things to do with a newly rooted device. Does anyone have a quick 'Do's and Don'ts of rooting" list?
 
TremLoc said:
Hi everybody, please forgive my noobness. I recently got the (VM) S3 and after completing this awesome and detailed rooting tutorial Im' left wondering "what do I do now?"
Do I make a back up of my phone? What are some of the more important things to do with a newly rooted device. Does anyone have a quick 'Do's and Don'ts of rooting" list?
Click to expand...

Do backup and full nanadroid....
do backup the backup to pc.....
dont flash a kernel not listed has a vm sg3 edition.
dont try a sprint labeled rom from xda...
stick to the roms listed here in the vm section ...
if your rooted MG2 i would suggest freezing the bloat and sticking to stock if your not at least well informed and experienced in how to fix issues.

do read and read some more.
 
Higgs_Boson said:
If you look at the batch script, this is the code to run in ADB:

@echo off
cd "%~dp0"

echo [*]
echo [*] Motochopper: Android root exploit (Windows version)
echo [*] v1.1
echo [*] by Dan Rosenberg (@djrbliss)
echo [*]
echo [*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
echo [*] Supports lots of other devices as well. ;-)
echo [*]
echo [*] Before continuing, ensure that USB debugging is enabled, that you
echo [*] have the latest USB drivers installed, and that your phone
echo [*] is connected via USB.
echo [*]
echo [*] WARNING: This will likely void the warranty on your device. I am
echo [*] not responsible for any damage to your phone as a result using this
echo [*] tool.
echo [*]
echo [*] Press enter to root your phone...
pause
echo [*]

adb kill-server

echo [*] Waiting for device...
adb wait-for-device

echo [*] Device found.

echo [*] Pushing exploit...
adb push pwn /data/local/tmp/
adb shell chmod 755 /data/local/tmp/pwn

echo [*] Pushing root tools...
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb install Superuser.apk

echo [*] Rooting phone...
adb shell /data/local/tmp/pwn

echo [*] Cleaning up...
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox

echo [*] Exploit complete. Press enter to reboot and exit.
pause
adb reboot
adb kill-server

From what I can tell, there are no blocked directories that ADB is trying to access. My simple GUESS would be that Samsung already patched the exploit known as "pwn" (maybe with the MG2 update).

EDIT:

I've also tried about three other one-click methods, namely motochopper, debugfs, and SRS Root; and all have failed. Most of the one click methods are exploits that are relatively easy to patch in updates. The only thing that can really breach it is brute force via ODIN. You're actually modifying a partition of the memory: /dev/block/mmcblk0p18 to be exact. This is where the recovery resides.

However, as we all know the downside to ODIN is that you're device status becomes "modified", and OTA updates are out of the question henceforth.
Click to expand...
Thanks for the informative post. I have the same issue trying to root my Samsung GS3 from Virgin Mobile. It won't mount anything, I am stuck! The phone was purchased in July 2013, I didn't expect the phone will have no Hotspot capability even if I am willing to pay $15/mo to VM. How despicable, VM!
 
So I rooted my phone way back before that update was released, and now I am stuck with my phone telling me there is an update available all the time. Installing the update won't work, and I can't figure out any way to get it to not remind me again... any ideas?
 
MattEnTheHat said:
So I rooted my phone way back before that update was released, and now I am stuck with my phone telling me there is an update available all the time. Installing the update won't work, and I can't figure out any way to get it to not remind me again... any ideas?
Click to expand...

http://androidforums.com/showthread.php?t=763114

Flashing this file through Odin will update your device to the latest build and stop the update notification. You will have to root again after installing the update. The update will not affect your apps or data but you might wanna back up just in case.
 
i tried this method step by step,and after the cmw push i restart and try to go into recovery but,i still have stock recovery,the second time i tried to go into recovery it was CWM,but wouldnt or couldnt see my sd card,i rebooted and tried to go back into recovery and no more CMW,i was back at stock recovery... any suggestions?
 
The stock ROM installs the stock recovery upon boot. Make sure you reboot into recovery without booting the ROM.

As far as the sd card read errors...I'd suggest going with twrp rather than clockwork mod if its available for your variant
 
I apologize if this is posted in the wrong spot or has been addressed before here or elsewhere. I have looked all over for an answer with no luck lol.

After rooting with this guide, I can't get 3g to kick on. Wifi, calls, and texting works fine. However, after rooting the boot animation and sound changed (no more red virgin mobile animation) and under about phone > status the Network heading says "Samsung" instead of Virgin Mobile. Which I find odd because I am positive I flashed no rom or modem.

I did encounter the error where recovery would not mount the sd cards, which I fixed by flashing the alternate recovery elsewhere in this thread. After that, root worked properly, but no mobile data. Here is what I have tried:
Flashing stock unrooted rom (Preparing network displayed in notification panel but never goes away), tried to update prl and profile in the settings menu but neither option did anything when tapped, tried to reactivate phone also from settings menu but it said to call 611 from the handset or another toll free number from another phone to activate, tried replacing the apns-conf.xml with a stock one I found somewhere or other, tried to flash stock modem (would not flash properly either as a zip in recovery or as a tar in odin), tried to flash stock kernel (no effect as I think it was the same kernel), yelling and cursing at it, and flashing stock recovery (would not boot properly or do anything at all).

I am at my wits end. The only theory I have is that somehow it's angry about having a modified device status. The only other thing I can think of is to flash the mg2 kies files I am downloading from the post in the VM SGS3 all things root section, which claims to restore modem, rom and all. Thanks in advance, and I'm sorry to bother everyone, but I hope somebody can shed a bit of light on my dilemma!
 
that network notification thing i freeze samsung dm service it goes away no impact on my phone other then OTA notices i think.
 
xthedakmanx said:
Push this file through ODIN using the PDA option and it'll fix it all for ya

(File here, not allowed to include it in reply for some reason)
Click to expand...

After countless hours of absolute headaches and frustration, I'm so glad I found your post and file about a week or so ago. Great job. I'm a newbie to this stuff and I'm not sure exactly what's conflicting with the ability to use custom kernels, but I was wondering if you could keep us posted on the MidnightRom? Keep us posted if there's any update or whatnot that will grant the ability to use custom kernels in the near future. I'm a bit scared to brick my phone lol :o

Regardless, thanks again for such an immense contribution. I'm surprised no one else on the internet has found a solution to this problem yet; you're the only person so far I've seen pose something helpful that actually works! :D I'm glad to finally be rooted even if I can't customize absolutely everything, at least there's root permission most importantly.
 
emkeene said:
I apologize if this is posted in the wrong spot or has been addressed before here or elsewhere. I have looked all over for an answer with no luck lol.

After rooting with this guide, I can't get 3g to kick on. Wifi, calls, and texting works fine. However, after rooting the boot animation and sound changed (no more red virgin mobile animation) and under about phone > status the Network heading says "Samsung" instead of Virgin Mobile. Which I find odd because I am positive I flashed no rom or modem.

I did encounter the error where recovery would not mount the sd cards, which I fixed by flashing the alternate recovery elsewhere in this thread. After that, root worked properly, but no mobile data. Here is what I have tried:
Flashing stock unrooted rom (Preparing network displayed in notification panel but never goes away), tried to update prl and profile in the settings menu but neither option did anything when tapped, tried to reactivate phone also from settings menu but it said to call 611 from the handset or another toll free number from another phone to activate, tried replacing the apns-conf.xml with a stock one I found somewhere or other, tried to flash stock modem (would not flash properly either as a zip in recovery or as a tar in odin), tried to flash stock kernel (no effect as I think it was the same kernel), yelling and cursing at it, and flashing stock recovery (would not boot properly or do anything at all).

I am at my wits end. The only theory I have is that somehow it's angry about having a modified device status. The only other thing I can think of is to flash the mg2 kies files I am downloading from the post in the VM SGS3 all things root section, which claims to restore modem, rom and all. Thanks in advance, and I'm sorry to bother everyone, but I hope somebody can shed a bit of light on my dilemma!
Click to expand...

Random question (may or may not be relevant). Are you using the US version of the VM GS3? Or another?
 
You must log in or register to reply here.
Back
Top Bottom