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

Root [Virgin Mobile] Android 4.4.2 VM SPH-L710

sean19661 said:
Ok you guys twisted my arm so I'm now Knox up on the mk5 100 % stock on 4.3 not rooted or custom recovery will wait to see if vm kit Kat gets pushed.
Click to expand...

Same here. My question is... I would like to go ahead and put a custom recovery and root but is there a way to backup stock recovery and be able to restore it without using Odin to put the stock 4.3 tar back on, which will erase everything again? And is it even possible to put the stock 4.3 tar back on with Odin again without bricking??
 
If your on stock mk5 I would let it sit because you will trip Knox might not be able to get vm kit kat. I will be leaving my mk5 complete stock and wait
 
jdsingle76 said:
When you flashed the MK5 modem while on the ND8 bootloader, I'm assuming it didn't work? I will look to see if I have a knox'd up version of MK5 around. If not, it will be easy enough to cook it up. And I am not sure if anything gets deleted but I wouldn't think so. And the updater script should have plenty of room, especially if you're replacing lines one for one.
Click to expand...

The MK5 modem is not recognized by the ND8 bootloader when you're trying to use it in the system, however, it patched up just fine to NDC with the OTA zip and now it's recognized as NDC. As far as the KNOX'd version of MK5, if you don't already have one, it's not a big deal. I just wanted to make sure that all of the patches were getting applied properly. Basically, the updater script throws some "INSTALLER_ERROR" messages every time it tries to patch something that either doesn't exist or doesn't match what it thinks it should be. This includes the kernel that is in the MK5 zip, the kernel in the 'wifi fix' zip, and the kernel in the stock TAR (don't worry, I didn't try to ODIN back to MK5, just extracted the boot.img from the tar).

Since the kernel won't patch, I flashed KT747 kernel.

I eventually got it to work. As far as running out of space, the updater script deletes a bunch of files, then it patches a bunch of files, then it extracts a bunch of files. Also either patches or overwrites some system partitions (aboot, mbn, modem, boot, etc.). Obviously an oversimplification but anyway, it runs out of space on the /system partition while extracting files. I don't know why, but it does. I deleted a few system apps from the MK5 zip and re-ran the updater and that seems to have appeased it. I had to delete a few system apps and some splash screens. Now I'm trying to find a way to remove some enough non-critical system apps to free up enough space for the updater-script to just run straight through. Once that's done, I'll upload a ZIP for people on ND8. Should work great. :)
 
vinnievegas said:
My question is... I would like to go ahead and put a custom recovery and root but is there a way to backup stock recovery and be able to restore it without using Odin to put the stock 4.3 tar back on, which will erase everything again? And is it even possible to put the stock 4.3 tar back on with Odin again without bricking??
Click to expand...

sean19661 said:
If your on stock mk5 I would let it sit because you will trip Knox might not be able to get vm kit kat. I will be leaving my mk5 complete stock and wait
Click to expand...

But is it possible??
 
moonknightus said:
The MK5 modem is not recognized by the ND8 bootloader when you're trying to use it in the system, however, it patched up just fine to NDC with the OTA zip and now it's recognized as NDC. As far as the KNOX'd version of MK5, if you don't already have one, it's not a big deal. I just wanted to make sure that all of the patches were getting applied properly. Basically, the updater script throws some "INSTALLER_ERROR" messages every time it tries to patch something that either doesn't exist or doesn't match what it thinks it should be. This includes the kernel that is in the MK5 zip, the kernel in the 'wifi fix' zip, and the kernel in the stock TAR (don't worry, I didn't try to ODIN back to MK5, just extracted the boot.img from the tar).

Since the kernel won't patch, I flashed KT747 kernel.

I eventually got it to work. As far as running out of space, the updater script deletes a bunch of files, then it patches a bunch of files, then it extracts a bunch of files. Also either patches or overwrites some system partitions (aboot, mbn, modem, boot, etc.). Obviously an oversimplification but anyway, it runs out of space on the /system partition while extracting files. I don't know why, but it does. I deleted a few system apps from the MK5 zip and re-ran the updater and that seems to have appeased it. I had to delete a few system apps and some splash screens. Now I'm trying to find a way to remove some enough non-critical system apps to free up enough space for the updater-script to just run straight through. Once that's done, I'll upload a ZIP for people on ND8. Should work great. :)
Click to expand...

I guess my question is..What were you trying to accomplish? Just get ndc modem working? Meaning you now have nd8 boot loader but created a flashable ndc modem that allows you to overwrite the nd8 modem? But the build still shows as nd8, correct?
 
jdsingle76 said:
I guess my question is..What were you trying to accomplish? Just get ndc modem working? Meaning you now have nd8 boot loader but created a flashable ndc modem that allows you to overwrite the nd8 modem? But the build still shows as nd8, correct?
Click to expand...

Actually, I got the installer to patch up the MK5 system to NDC. So the only thing ND8 on my phone is the bootloader. (At least, until I go back to my Conquest ROM. This is just for fun, not for permanence.)

Just wanted to say also that your MK5 installer runs out of space while installing, too, according to the recovery log.

Code: 
minzip: Extracted file "/system/xbin/wget"
minzip: Extracted file "/system/xbin/which"
minzip: Error writing 4096 bytes from zip file from 0xbeb4f914: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/xbin/whoami"
set_perm: chown of /system/etc/dbus.conf to 1002 1002 failed: No such file or directory
set_perm: chmod of /system/etc/dbus.conf to 440 failed: No such file or directory
about to run program [/system/xbin/busybox] with 4 args
--install: applet not found
run_program: child exited with status 1
script result was [/system]

I think it's because instead of symlinking the busybox and toolbox applets, it appears to actually install a separate copy of busybox/toolbox named to each applet. I'm going to try it out and see what happens. The following code added to the updater-script (as well as removing the duplicate applets from the actual ZIP file) should fix it:

Code: 
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
        "/system/xbin/adjtimex", "/system/xbin/arp", "/system/xbin/ash",
        "/system/xbin/awk", "/system/xbin/base64", "/system/xbin/basename",
        "/system/xbin/bbconfig", "/system/xbin/blkid", "/system/xbin/blockdev",
        "/system/xbin/brctl", "/system/xbin/bunzip2", "/system/xbin/bzcat",
        "/system/xbin/bzip2", "/system/xbin/cal", "/system/xbin/cat",
        "/system/xbin/catv", "/system/xbin/chattr", "/system/xbin/chgrp",
        "/system/xbin/chmod", "/system/xbin/chown", "/system/xbin/chroot",
        "/system/xbin/clear", "/system/xbin/cmp", "/system/xbin/comm",
        "/system/xbin/cp", "/system/xbin/cpio", "/system/xbin/crond",
        "/system/xbin/crontab", "/system/xbin/cut", "/system/xbin/date",
        "/system/xbin/dc", "/system/xbin/dd", "/system/xbin/depmod",
        "/system/xbin/devmem", "/system/xbin/df", "/system/xbin/diff",
        "/system/xbin/dirname", "/system/xbin/dmesg", "/system/xbin/dnsd",
        "/system/xbin/dos2unix", "/system/xbin/du", "/system/xbin/echo",
        "/system/xbin/ed", "/system/xbin/egrep", "/system/xbin/env",
        "/system/xbin/expand", "/system/xbin/expr", "/system/xbin/false",
        "/system/xbin/fdisk", "/system/xbin/fgrep", "/system/xbin/find",
        "/system/xbin/flash_lock", "/system/xbin/flash_unlock",
        "/system/xbin/flashcp", "/system/xbin/flock", "/system/xbin/fold",
        "/system/xbin/free", "/system/xbin/freeramdisk", "/system/xbin/fsync",
        "/system/xbin/ftpget", "/system/xbin/ftpput", "/system/xbin/fuser",
        "/system/xbin/getopt", "/system/xbin/grep", "/system/xbin/groups",
        "/system/xbin/gunzip", "/system/xbin/gzip", "/system/xbin/halt",
        "/system/xbin/head", "/system/xbin/hexdump", "/system/xbin/id",
        "/system/xbin/ifconfig", "/system/xbin/inetd", "/system/xbin/insmod",
        "/system/xbin/install", "/system/xbin/iostat", "/system/xbin/ip",
        "/system/xbin/kill", "/system/xbin/killall", "/system/xbin/killall5",
        "/system/xbin/length", "/system/xbin/less", "/system/xbin/ln",
        "/system/xbin/losetup", "/system/xbin/ls", "/system/xbin/lsattr",
        "/system/xbin/lsmod", "/system/xbin/lsusb", "/system/xbin/lzcat",
        "/system/xbin/lzma", "/system/xbin/lzop", "/system/xbin/lzopcat",
        "/system/xbin/man", "/system/xbin/md5sum", "/system/xbin/mesg",
        "/system/xbin/mkdir", "/system/xbin/mke2fs", "/system/xbin/mkfifo",
        "/system/xbin/mkfs.ext2", "/system/xbin/mkfs.vfat", "/system/xbin/sh",
        "/system/xbin/mknod", "/system/xbin/mkswap", "/system/xbin/mktemp",
        "/system/xbin/modinfo", "/system/xbin/modprobe", "/system/xbin/more",
        "/system/xbin/mount", "/system/xbin/mountpoint", "/system/xbin/mpstat",
        "/system/xbin/mv", "/system/xbin/nanddump", "/system/xbin/nandwrite",
        "/system/xbin/netstat", "/system/xbin/nice", "/system/xbin/nohup",
        "/system/xbin/nslookup", "/system/xbin/ntpd", "/system/xbin/od",
        "/system/xbin/patch", "/system/xbin/pgrep", "/system/xbin/pidof",
        "/system/xbin/ping", "/system/xbin/pkill", "/system/xbin/pmap",
        "/system/xbin/poweroff", "/system/xbin/printenv", "/system/xbin/printf",
        "/system/xbin/ps", "/system/xbin/pstree", "/system/xbin/pwd",
        "/system/xbin/pwdx", "/system/xbin/rdev", "/system/xbin/readlink",
        "/system/xbin/realpath", "/system/xbin/renice", "/system/xbin/reset",
        "/system/xbin/resize", "/system/xbin/rev", "/system/xbin/rm",
        "/system/xbin/rmdir", "/system/xbin/rmmod", "/system/xbin/route",
        "/system/xbin/run-parts", "/system/xbin/rx", "/system/xbin/sed",
        "/system/xbin/seq", "/system/xbin/setconsole", "/system/xbin/setserial",
        "/system/xbin/setsid", "/system/xbin/sha1sum",
        "/system/xbin/sha256sum", "/system/xbin/sha512sum",
        "/system/xbin/sleep", "/system/xbin/sort", "/system/xbin/split",
        "/system/xbin/stat", "/system/xbin/strings", "/system/xbin/stty",
        "/system/xbin/sum", "/system/xbin/swapoff", "/system/xbin/swapon",
        "/system/xbin/sync", "/system/xbin/sysctl", "/system/xbin/tac",
        "/system/xbin/tail", "/system/xbin/tar", "/system/xbin/taskset",
        "/system/xbin/tee", "/system/xbin/telnet", "/system/xbin/telnetd",
        "/system/xbin/test", "/system/xbin/tftp", "/system/xbin/tftpd",
        "/system/xbin/time", "/system/xbin/timeout", "/system/xbin/top",
        "/system/xbin/touch", "/system/xbin/tr", "/system/xbin/traceroute",
        "/system/xbin/true", "/system/xbin/ttysize", "/system/xbin/tune2fs",
        "/system/xbin/umount", "/system/xbin/uname", "/system/xbin/uncompress",
        "/system/xbin/unexpand", "/system/xbin/uniq", "/system/xbin/unix2dos",
        "/system/xbin/unlzma", "/system/xbin/unlzop", "/system/xbin/unxz",
        "/system/xbin/unzip", "/system/xbin/uptime", "/system/xbin/usleep",
        "/system/xbin/uudecode", "/system/xbin/uuencode", "/system/xbin/vi",
        "/system/xbin/watch", "/system/xbin/wc", "/system/xbin/wget",
        "/system/xbin/which", "/system/xbin/whoami", "/system/xbin/xargs",
        "/system/xbin/xz", "/system/xbin/xzcat", "/system/xbin/yes",
        "/system/xbin/zcat");

# TOOOLBOX
symlink("toolbox", "/system/bin/getevent", "/system/bin/getprop", "/system/bin/hd",
        "/system/bin/iftop", "/system/bin/ioctl", "/system/bin/ionice",
        "/system/bin/log", "/system/bin/lsof", "/system/bin/md5", 
		"/system/bin/nandread", "/system/bin/newfs_msdos", "/system/bin/notify",
        "/system/bin/ps", "/system/bin/r", "/system/bin/reboot",
        "/system/bin/schedtop", "/system/bin/sendevent", "/system/bin/setprop",
		"/system/bin/smd", "/system/bin/start", "/system/bin/stop",
		"/system/bin/vmstat", "/system/bin/watchprops", "/system/bin/wipe");
 
You mean my mk5 zip? The stock tar shouldn't have anything busybox related, I thought. Lol, I'm confused. You on hangouts?
 
vinnievegas said:
How is it done through kies?
Click to expand...

You have to do a emergency recovery via kies under the tools tab or if you have the mg2 or mk5 tar file you can use Odin also but if you have the mk5 with Knox boot loader on your phone you can't got back to mg2 4.1.2 with the mg2 boot loader
 
Hi All,

I did read back a few pages here and there but still am confused,all the terms and what not. I just want kitkat running on my phone and able to keep root privileges . Now i can't remember the details but i did root my phone and i have philz recovery. Im using a stock rom i think?(looks the same since i bought the phone) . Now the update for virgin mobile kitkat was just pushed to me so i figured itd download just like 4.3 did. Well it didnt lol i read that other people tried the same. Anyways, how would i go about getting kitkat on my phone in the easiest way possible?im sorry for bothering you guys with questions you most likely have answered already.

thanks <3
 
moofnman said:
Hi All,

I did read back a few pages here and there but still am confused,all the terms and what not. I just want kitkat running on my phone and able to keep root privileges . Now i can't remember the details but i did root my phone and i have philz recovery. Im using a stock rom i think?(looks the same since i bought the phone) . Now the update for virgin mobile kitkat was just pushed to me so i figured itd download just like 4.3 did. Well it didnt lol i read that other people tried the same. Anyways, how would i go about getting kitkat on my phone in the easiest way possible?im sorry for bothering you guys with questions you most likely have answered already.

thanks <3
Click to expand...

Because you were rooted and running custom recovery, the update didn't take. You have to be 100% stock to get an OTA to flash. However, as you've read, it seems that even after flashing back to stock mk5 users are not able to flash the kk OTA. So you can either flash the Sprint nd8 tar they cnexus put out over at XDA, and root that, or wait until someone captures the Boost/VM kk tar.
 
peter counias said:
Yes I was 100% stock and it still didn't take don't know way !!!
yes Knox flag was tripped !!
Click to expand...

So you flashed back using my MK5 tar and it gave you the update notice? And you tried flashing and it failed? Hmmm..I'm telling you, it sounds like something with Knox then. I don't know what else it can be! I'm assuming you got the dhd.ko module error 7?
 
It booted into stock recovery started to install an then the android fell over an that was that !!
yes it has to be knox related !!
 
jdsingle76 said:
Because you were rooted and running custom recovery, the update didn't take. You have to be 100% stock to get an OTA to flash. However, as you've read, it seems that even after flashing back to stock mk5 users are not able to flash the kk OTA. So you can either flash the Sprint nd8 tar they cnexus put out over at XDA, and root that, or wait until someone captures the Boost/VM kk tar.
Click to expand...

Ah i see. Thanks a million for that :3 i guess ill just wait.Shouldnt be long now anyway since we should be in the last stages of the update rolling out. thumps up for you lol
 
I just want to be clear -

I have the 4.3 stock (non-knox) with MK5 and Philz and have the update notification.

Can people confirm the following:

1. If I attempt to update from my current state, it will fail.

2. If I use Odin and return back to the stock recovery via the links in this thread, it will trip knox and I will, again, not be able to update

In conclusion, there is no way for me to get to 4.4.2 using the Virgin Mobile update?

Thanks
 
seabiscuit68 said:
I just want to be clear -

I have the 4.3 stock (non-knox) with MK5 and Philz and have the update notification.

Can people confirm the following:

1. If I attempt to update from my current state, it will fail.

2. If I use Odin and return back to the stock recovery via the links in this thread, it will trip knox and I will, again, not be able to update

In conclusion, there is no way for me to get to 4.4.2 using the Virgin Mobile update?

Thanks
Click to expand...

Try plugging into kies and see what it says first. But from what everyone's saying, no, there isn't. The OTA keeps failing, even on stock mk5 tar. Is your Knox tripped?
 
I have a SGS3 VM I put back to 100% MK5 stock using Odin, except, Knox is tripped. I tried several times to update "adb sideload" and any other way I could think of using the update MK5_to_NDC I found yesterday here a few pages back. ALWAYS started but aborted when It got to "verifying system"
"finding update package
opening update package
verifying update package
installing update
verifying current system
patch/system/lib/modules/dhd.ko has unexpected contents
E:error in /tmp/update.zip (status 7) installation aborted"

This morning I got my hands on another SGS3 VM 100% stock, however the only difference is KNOX was NOT tripped. The "update" installation went through with NO problem. The phone is now "Android Version 4.4.2", Baseband Version L710VPUCNDC", and "Build Number K0T49H.L710VPUCNDC"

I used the "adb sideload <name-of-file> command in the cmd window to install the update.

It appears we will need a MK5_to_NDC tar file to update, if KNOX is tripped. Or maybe someone with more experience than I could look at the current update file and take out the command for the update file to look to see if KNOX has been tripped.

Thought I would share with others who are having trouble getting the update file to work.
Thank you.

edit:
I also checked with Kies for an update with the phone that was NOT Knox flagged. Kies still did not list any update for the phone.
 
You must log in or register to reply here.
Back
Top Bottom