• 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

BoomBoom53 said:
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.
Click to expand...

That's an awesome update man! Thanks for sharing. You've confirmed my suspicions completely. Now we know where the issue lies! And what we need to do. Wait for it to show up on kies and catch it! Was the untripped phone pure stock or flashed to mk5 using the stock tar?
 
BoomBoom53 said:
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.
Click to expand...

There's no command that checks to see if KNOX has been tripped. The updater is stopping at a kernel module. If you have used the MK5 zip to flash back to stock, have flashed a custom kernel, or even if you use the MK5 wifi fix, it changes the kernel and kernel modules. I'm working on a modified updater that will bypass such checks. However, it's worth noting that my updater will not flash the NDC bootloader and won't flash the NDC modem unless you downgrade your modem to the MK5 modem. It's really only meant for people who are on an ND8 ROM and want to go to NDC.
 
I really want this update haha. I'm pure stock, non rooted, system recovery. Still haven't gotten anything. I wish I someone could upload somewhere:(
 
moonknightus said:
There's no command that checks to see if KNOX has been tripped. The updater is stopping at a kernel module. If you have used the MK5 zip to flash back to stock, have flashed a custom kernel, or even if you use the MK5 wifi fix, it changes the kernel and kernel modules. I'm working on a modified updater that will bypass such checks. However, it's worth noting that my updater will not flash the NDC bootloader and won't flash the NDC modem unless you downgrade your modem to the MK5 modem. It's really only meant for people who are on an ND8 ROM and want to go to NDC.
Click to expand...

You say that it changes the kernel modules, but flashing the stock tar through Odin should wipe it clean I would think. Are you saying there's some type of residual left behind that's causing it to fail? I have never heard of not being able to flash back to stock and have an update fail like this. The dhd.ko is the Wi-Fi module in the kernel, so somehow by not being 100 percent, never rooted, never anything, it's blocking it, and from what I've read, the only explanation I can come up with is Knox...
 
dennytechno said:
I really want this update haha. I'm pure stock, non rooted, system recovery. Still haven't gotten anything. I wish I someone could upload somewhere:(
Click to expand...

If you've never rooted or flashed Cwm, then you are the perfect candidate to grab the tar for us through kies once it becomes available! Patience is the key :)
 
I'm also 100% stock I took the mk5 update that was pushed to my phone I also look into my download mode it say warranty bit is 0 still waiting for ota update before I flashes the ota I used triangle away to reset the counter everything says official
 
jdsingle76 said:
You say that it changes the kernel modules, but flashing the stock tar through Odin should wipe it clean I would think. Are you saying there's some type of residual left behind that's causing it to fail? I have never heard of not being able to flash back to stock and have an update fail like this. The dhd.ko is the Wi-Fi module in the kernel, so somehow by not being 100 percent, never rooted, never anything, it's blocking it, and from what I've read, the only explanation I can come up with is Knox...
Click to expand...

Yeah, Knox doesn't do anything to the kernel modules. The kernel in the MK5 zip file doesn't work for everybody (hence the 'mk5 wifi fix'). I don't know about the stuff in the ODIN tar because I never tried it. All I can tell you is that if the updater finds a file that doesn't match the checksum that it's looking for, it's gonna spit out an error and stop. The asserts at the top of the updater-script are what cause this. Remove the asserts, and you can get through 99% of the update, but it still won't update the kernel so you'd need a custom kernel. As far as I can tell, the ND8 kernel and KT747 kernel work just fine.
 
sean19661 said:
I'm also 100% stock I took the mk5 update that was pushed to my phone I also look into my download mode it say warranty bit is 0 still waiting for ota update before I flashes the ota I used triangle away to reset the counter everything says official
Click to expand...

Again, like I asked in the other post, try to hold out for the kies push....If you have the patience :) It'll benefit a lot of folks, for sure!
 
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...

1. Yes
2. True
In conclusion, true
 
jdsingle76 said:
That's an awesome update man! Thanks for sharing. You've confirmed my suspicions completely. Now we know where the issue lies! And what we need to do. Wait for it to show up on kies and catch it! Was the untripped phone pure stock or flashed to mk5 using the stock tar?
Click to expand...


It came from "Assurant Solutions". Replacement phone for a lost phone insurance claim. It came MK5, 100% stock untripped.
 
jdsingle76 said:
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?
Click to expand...

My knox should not be tripped since I went straight from 4.1(?) to the 4.3 update with knox removed.

If I move back to the stock bootloader through Odin (per your link in a few other posts), would this trip knox?
 
If kies finally gets the ota 4.4.2 where do you pull it from. dose kies create a temp folder when is the tar actually there ?
 
seabiscuit68 said:
My knox should not be tripped since I went straight from 4.1(?) to the 4.3 update with knox removed.

If I move back to the stock bootloader through Odin (per your link in a few other posts), would this trip knox?
Click to expand...

No, it will not trip Knox, but don't be surprised if the OTA notification doesn't appear, and the update.zip fails. Seems nobody that isn't fresh from the factory stock can get the update to stick
 
Reverted back to the knoxed 4.3 version. If I go into download mode it shows warranty bit as 0 does that mean I didnt trip knox installing custom recoveries and the unknoxed version of 4.3?
 
sean19661 said:
If kies finally gets the ota 4.4.2 where do you pull it from. dose kies create a temp folder when is the tar actually there ?
Click to expand...

That recovery through Kies idea to snatch the tar may be a viable option, if someone wants to try it. I personally have never done a recovery through Kies, but it may work. And yes, it drops it in your tmp folder and then flashes it from there. The key is to have that folder open(and empty) prior to accepting the Kies update, then as soon as it's done downloading to your temp folder, copy and paste it to another folder or your desktop before it disappears.
 
6burgh said:
Reverted back to the knoxed 4.3 version. If I go into download mode it shows warranty bit as 0 does that mean I didnt trip knox installing custom recoveries and the unknoxed version of 4.3?
Click to expand...

That is what that means. Since you didn't have Knox before, and flashed the KNox free version of MK5, there was no knox bootloader to trip. However, now that you are on the Knox bootloader, it will trip if you flash CWM and try to root through Odin. So my advice, if you want the update, don't trip knox and see if it comes through successfully with a No knox tripped phone. But like moonknightus said, that may not work either, since you have rooted before, changed kernels, etc...may have to wait for the tar like everyone else to update.
 
dennytechno said:
My friend has the update. Can I get it from her phone
Click to expand...

It would be worth trying to catch the tar through Kies by doing a firmware recovery. That would put the NDC tar in your temp folder and you could "catch" it before it flashes to her phone(in theory). Play around with it...it'd certainly help a TON of folks if someone could catch that tar!
 
jdsingle76 said:
It would be worth trying to catch the tar through Kies by doing a firmware recovery. That would put the NDC tar in your temp folder and you could "catch" it before it flashes to her phone(in theory). Play around with it...it'd certainly help a TON of folks if someone could catch that tar!
Click to expand...

I'm trying to. My son is pure stock just waiting until he gets the notice. Tried to get the kies to update him over the weekend not luck yet. Any trick you have to aid capture are welcome
 
John762 said:
I'm trying to. My son is pure stock just waiting until he gets the notice. Tried to get the kies to update him over the weekend not luck yet. Any trick you have to aid capture are welcome
Click to expand...

Here's a quick guide on how to snag the OTA tarball from Kies before it flashes itself to your phone. I haven't heard of anyone officially getting it yet, but I'm sure it'll be here soon. Timing is everything, so make sure you're quick before the file deletes itself!
1. Click on Start->Run, enter %temp% and press ENTER. First thing before you go into Kies, clear this folder out.
2. Keep that explorer window open and handy. I also suggest open another to where you want to copy it to(create new folder on desktop and keep it open).
Open Kies, let it download. As soon as it starts flashing, look for a folder with the tarball or search for .tar.md5 in the %temp% folder you have open. Copy/paste it to your new folder. Done. Congrats, you
 
You must log in or register to reply here.
Back
Top Bottom