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

Root [Boost Mobile] KitKat ND8 update

Lol... I would do it and give it to you myself but I don't wanna take the Knox on the s3, I'm still Knox free. even though when I got the S5, I voided the Knox warranty within the first 20 minutes of when I got home just to root the phone... lol

Sometimes I just don't make sense to myself 😕
 
Lol... I would do it and give it to you myself but I don't wanna take the Knox on the s3, I'm still Knox free. even though when I got the S5, I voided the Knox warranty within the first 20 minutes of when I got home just to root the phone... lol

Sometimes I just don't make sense to myself 😕

Lol.... No worries. Just trying to help you guys out.
 
Here's the md5 checksum from my zip, that should tell if it was a bad upload:
9ee50aa41691eac8a3933c2560057657

I was running the de-knoxed stock boost version of mk5. Update has to be for boost, doesn't it?
 
Here's the md5 checksum from my zip, that should tell if it was a bad upload:
9ee50aa41691eac8a3933c2560057657

I was running the de-knoxed stock boost version of mk5. Update has to be for boost, doesn't it?

It should work on either boost or VM just like the mk5 update did.
 
Here's the md5 checksum from my zip, that should tell if it was a bad upload:
9ee50aa41691eac8a3933c2560057657

I was running the de-knoxed stock boost version of mk5. Update has to be for boost, doesn't it?

That's the md5 I got for your download and it failed to flash via recovery over the stock firmware that was provided earlier in this thread. I believe the problem is actually with the stock firmware provided. After I odin the firmware and go into recovery mode my little android dude has fallen down and it's in manual mode.
 
That's the md5 I got for your download and it failed to flash via recovery over the stock firmware that was provided earlier in this thread. I believe the problem is actually with the stock firmware provided. After I odin the firmware and go into recovery mode my little android dude has fallen down and it's in manual mode.

Sorry guys, dunno what it could be. I lost the original file from my /cache/ folder, so I can't check the md5 of it. But I still had the very first copy I made to /sdcard, and I rechecked the checksum there, and it's exactly the same. (Used ES to make that first copy/paste, and it appeared to work fine with no errors.)

I'm going to remove the link from above, since the file isn't working.
 
Sorry guys, dunno what it could be. I lost the original file from my /cache/ folder, so I can't check the md5 of it. But I still had the very first copy I made to /sdcard, and I rechecked the checksum there, and it's exactly the same. (Used ES to make that first copy/paste, and it appeared to work fine with no errors.)

I'm going to remove the link from above, since the file isn't working.

Let me copy it first. It may come in handy someday. And has anyone on Boost tried this or only VM?
 
I'm on Boost Mobile. I might further speculate that since 4.3 had two separate versions, one with Knox and one w/out that perhaps there are two OTA updates available and since Dave has the no-Knox version, that might be why it's failing on my stock MK5 with Knox.
 
Let me copy it first. It may come in handy someday. And has anyone on Boost tried this or only VM?

I restored the link in my post, and just added a caveat at the end. Plenty of space on my google drive, so I'll just leave it out there, in case it helps anyone.
 
I'm on Boost Mobile. I might further speculate that since 4.3 had two separate versions, one with Knox and one w/out that perhaps there are two OTA updates available and since Dave has the no-Knox version, that might be why it's failing on my stock MK5 with Knox.

The mk5 that doesn't have Knox is mine, not an official OTA. The only OTA had Knox imbedded in it. I just removed it.
 
Since none of the available Boost OTA's seem to work on the Boost 4.3 firmware that was posted, I think I'll just wait for a 4.4 tar, if we ever see one that is :)
 
In case anybody wants it, I've cooked up a version that will flash in custom recovery. I'm going to upload it to AFH shortly. I'll post the link here.

I don't have a Boost phone so I can't say for sure, but it looks like the OTA is looking for a Virgin Mobile phone (D2VMU) in the assert checks at the beginning of the updater script. Is the Boost model # different? I was under the impression that it was D2BST or something to that effect.
 
In case anybody wants it, I've cooked up a version that will flash in custom recovery. I'm going to upload it to AFH shortly. I'll post the link here.

Cooked up a version of what? You have to be careful because if they aren't already on the KK boot loader with NDC modem and NDC boot loader(which you can only get from the OTA at this point), it won't work and may brick you...Just be careful is all I'm saying.
 
Here are my results:

Phone Status - Stock Boost Mobile firmware 4.3 from Kies

Downloaded the OTA provided in this thread and attempted to flash via recovery, and it failed. Tried to sideload the same OTA file with ADB and it failed in the exact manner as the first failure.

The error happens during 'Verifying current system..."

"/system/lib/modules/dhd.ko" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
 
Here are my results:

Phone Status - Stock Boost Mobile firmware 4.3 from Kies

Downloaded the OTA provided in this thread and attempted to flash via recovery, and it failed. Tried to sideload the same OTA file with ADB and it failed in the exact manner as the first failure.

The error happens during 'Verifying current system..."

"/system/lib/modules/dhd.ko" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.

Thanks Deven. That seems to be the consensus. That dhd.ko is the Wi-Fi module and I'm not sure why it's not reading correctly. I have some very sharp guys looking into it and I'm sure we'll get it worked out. So everyone reading this....is it safe to say that no one who has ever rooted, whether they tripped Knox or not, has not successfully flashed the ota, either from Samsung, sideload, or sd card? That about sum it up?
 
Sums it up for me! :)

Just wondering, can a Boost Mobile 4.4.2 tar be created from the source available at http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SPH-L710. The file listed as: Model:SPH-L710_NAVersion: L710VPUCNDC File: SPH-L710_NA_KK_Opensource.zip should be Kitkat for Boost Mobile and VM.

That's just the kernel source, and good work on the grab, but there's someone already uploading it! But it's never a bad idea to have an uploading account for stuff. I use Android file host, exclusively.
 
For those folks on Boost or VM who flashed the Sprint ND8 Kit Kat tar, I have good news. I just risked sleeping on the couch to see if the NDC tar would flash over the ND8 bootloader, and not only did it flash, but it saved all of the data, just like an OTA upgrade does. She snagged it back before I was able to re-root and such, but just know, it DOES flash over it just fine, just takes awhile. Good luck!
 
For those folks on Boost or VM who flashed the Sprint ND8 Kit Kat tar, I have good news. I just risked sleeping on the couch to see if the NDC tar would flash over the ND8 bootloader, and not only did it flash, but it saved all of the data, just like an OTA upgrade does. She snagged it back before I was able to re-root and such, but just know, it DOES flash over it just fine, just takes awhile. Good luck!


LOL!!!! Bro, I am laughing so freaking hard right now after reading the part about you taking the risk of sleeping on the couch!!!

Thanks JD. You Da Man Bro! :D
 
Back
Top Bottom