Develop Bugs

[Q] what does "E:error in TMP/sideload/package.zip (status 7) mean?

Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake

themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
As far as I can tell, I believe it means you're rooted still. I had the same problem so I Odin'd stock UVALH2 and then installed the leak without issue.

Not trying to hijack this thread but have been wondering why do you guys try to install leaks throw stock recovery. It is super easy to root this phone. Why not root install custom recovery then jush flash leaks?
Sent from my SGH-T999

Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.

Aerowinder said:
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Click to expand...
Click to collapse
Same here, I didn't come from a stock rom. Oh well.

So are you flashing the deodexed roms then?
Im talking about the actual ota you download from somewhere like sammobile.
It patches the existing system (UVDLI8 patches UVALI5) if anything is modded in UVALI5 the patch wont work, or if it does it can cause problems.
If you're flashing roms from development section then yes you can flash normally with custom recovery. But those roms are based on the otas, they're not the actual otas themselves.
Sent from my SGH-T999 using xda app-developers app

I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.

Yeah i tried everyway possible. The only way that worked was going uvahl2 thru odin, and then thru stock recovery i applied the ota jb uvdli7 from external sd. It was the only way to get it to work. I think the reason why the error message was coming up was because even though i unrooted my phone, the phone status still said "modified". Once i reflashed hl2 and it didn't say modified it updated the leak.

I think its going to take a video to prove you don't need stock recovery for this operation.

Aerowinder said:
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Click to expand...
Click to collapse
Lol! Im just usually online when they drop! Theres only been a couple where I wasn't.
If cwm touch recovery does flash these otas as is then it just means they've disabled the check the ota does to verify the system meets the requirements. Or they just disable the recovery check/patch to protect their own recovery. I hope its the latter.
Not saying it cant be done but till now I hadn't heard of it. I use TWRP (just personal preference) but actually never bothered to try with it becsuse too many people early on got errors like the OP when anything wasn't matching stock.
I use Mobile Odin for the otas since it not only allows me to meet the stock requirements but it also injects root so you never have to worry about rerooting or anything.
At this point I just want to know how CWM does the otas. Does it completely disable the system check, or just the recovery part of that check.
Sent from my SGH-T999 using xda app-developers app

The zip file still runs the verification process. I've always done it properly, so I don't know what a flashing failure looks like. I have a background in programming, and I'm an amateur for sure, but I suspect that when the update checks for stock recovery, it thinks CWM is the stock recovery. I'm not sure of the code behind this, but I equate it to user-agents in browsers. CWM is saying it is stock recovery, OTA update accepts that, or some such. Without seeing the code, I can't say for sure, but this is my guess.
You get the option to disable the recovery patch, and to keep root when you attempt to exit recovery after the OTA flash.
I never saw much use for Mobile Odin. I did buy it, because the dev is amazing, but I've never used it. It allows you to flash zip files? I've always just done it through CWM. I flash everything through CWM... even other recoveries.

However it does it, I guess it works. Only reason I wanted to know if it bypassed the entire check is because that could cause problems for the more inexperienced.
Yeah, I love Chainfires work. The ability to flash zips with Mobile Odin was just added a few weeks ago and has worked flawlessly for me.
Sent from my SGH-T999 using xda app-developers app

fix it
you need to flash your kernel to man. most stock kernel wouldnt work with cyanogenmod. Update your kernel with unofficial kernel that are compatible with your device

raaaaarrrr!!!
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.

atheistics1 said:
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
Click to expand...
Click to collapse
Well, first, there is not an Odin flashable 4.3 file, but you said you tried to flash MDL? Not sure what this is exactly. The most likely issue is you are using an incompatible recovery. Probably one that is too old.

I think you are totally confused between odin flashable files and recovery flashable files....

Okay so maybe this will help...omni version is jfltecan...which is Canadian and my baseband is l720vpuemja ...that's sprint which my phone is...I'm getting no data...and I'm not able to revert back to 4.3 or 4.2.
Sent from my SGH-I337M using XDA Premium 4 mobile app

you should probably consider asking in your devices forum. if you use anything here youll likely brick.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2

wolverine
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
Just downgrade to 4.0.4 and install cwm then flash it through it. it works for me.

[Q] Unable to flash Stock ROM

I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks

Is it supposed to use T999 firmware?

Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium

re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL

Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?

Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.

newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.

Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.

tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414

newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!

How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7

Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app

Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done

Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app

You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium

Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app

No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium

Sprint GS3 Flashed to Page Plus??

OK I got the phone flashed over to Page Plus. But for the life of me I can't get into EPST ##3282#. No matter what I do the keypad dialer will not open this menu.
YouTube & Play Store will not work over data.
I'm on Freeza stock MD4 rom . Stock phone keypad
I googled and I've read that the ###3282# code was blocked in the MD4 update. So I'm assuming that I need to flash a rom that was b4 the MD4.
Could someone please tell me what rom I'm looking for?
Or unless someone knows a different way to get into EPST?
Thanks a million
Sent from my EVO using Tapatalk 4

My SPH-L710 was flashed to pageplus 4 days ago. What i had to do, was go to a stock, unrooted rom, let them do the flashing process, and then restore a nandroid of a different rom. I do not suggest rooting the stock rom after the flash, because it broke my wifi. I did a factory reset using Philz CWM, i wiped the dalvik cache. I rebooted the phone, rerooted, and rebooted. Still no wifi with stock MD4 that was rooted using the GS3 all in one tool.
I restored a nandroid of The Peoples Rom, and Mother of all Roms. My calls, texts, and 3G data all work with both roms. I do not know about MMS, because i do not use MMS. TPR and MOAR are both prerooted ROMs.

scoot0073 said:
OK I got the phone flashed over to Page Plus. But for the life of me I can't get into EPST ##3282#. No matter what I do the keypad dialer will not open this menu.
YouTube & Play Store will not work over data.
I'm on Freeza stock MD4 rom . Stock phone keypad
I googled and I've read that the ###3282# code was blocked in the MD4 update. So I'm assuming that I need to flash a rom that was b4 the MD4.
Could someone please tell me what rom I'm looking for?
Or unless someone knows a different way to get into EPST?
Thanks a million
Sent from my EVO using Tapatalk 4
Click to expand...
Click to collapse
If you decide to go the earlier version (before MD4) route go to Billard412's thread. One flash solution. Read the OP carefully.
Billards412's thread here:
MD4, MD1 for both 16 & 32 gb versions
Here:
http://forum.xda-developers.com/showthread.php?t=1904099
Nearly Last page of Billard's thread
LJ7 for both 16 and 32 gb versions Here:
http://forum.xda-developers.com/showthread.php?t=1904099&page=62
BE SURE to give billard thanks for the work he's done!

Do you know which version came on this phone 16gig?
That Billards412 offers
Thanks
sent from my HTC Evo LTE cm10.2

scoot0073 said:
Do you know which version came on this phone 16gig?
That Billards412 offers
Thanks
sent from my HTC Evo LTE cm10.2
Click to expand...
Click to collapse
This thread http://forum.xda-developers.com/showthread.php?t=1904099 has a stock MD4 that also resets your flasg count. Not that the second part matters in this case. The ROM is confirmed to be stock, unrooted, and MD4 update. No surprises like messed up features or random reboots. Its a clean MD4. I would suggest making sure you have a nandroid for whatever ROM you want to use as your daily driver. So, nandroid your daily driver, go back to stock, and then restore your nandroid. Thats that i did. my talk, text, and 3G work. As far as i know, switching ROMS DOES break MMS. Of you cannot live without MMS, im afraid youll have to remain stock as far as i know. The person that flashed my GS3 wrote their own software, and has years of experience in the business. I am not saying he knows every trick, but ive been told that it is impossible to properly flash the GS3 while it has a ROM with certain custom features, or OC/UC.

Thanks, I done flashed like 4 different roms since the Page Plus flash and everything still works sms/mms/3g on each one. Her daily driver is Cm10.2 on this phone.
The guy told me if I flash a rom avoid firmware as that would wipe or corrupt the Page Plus flash. And he would charge me to have a refreshing.
He got everything flashed except he couldn't get into the ##3282# to program whatever he needed to in there.
sent from my HTC Evo LTE cm10.2

But I get home and flash a stock unrooted rom via recovery hopefully to see if the ##3282# works if so then take it back so he can finish
sent from my HTC Evo LTE cm10.2

esn/meid zeros out when flashing custom roms.

Hello Everyone,
I am having the weirdest issue, this has never happened to me before. Everytime i try to flash a custom rom it goes through and boots and everything runs smoothly but i have no service. When i check my device information in the settings menu my MEID is zeroed out as well as my prl, phone number, etc everything just turns to zeros. when i flash back to stock mk4 everything is back. I can flash any rom based off mk4 and everything will work fine. but any other rom aosp, cyanogenmod, etc i get zeroed out. anyone know what the issue may be or how i can prevent this from happening. I have tried multiple roms all have the same issue.

First check the obvious and make sure you are flashing the correct AOSP ROM for the Sprint Note 2 aka SPHL900.
If that's all good then you might need to start over and odin flash the stock MC2 with flash counter reset (found in development forum). After that use the Note 2 ToolKit found in original development forum and reroot your phone with it. At the same time you will also need to make sure you choose the ALL IN ONE (root, insecure boot image & recovery) option. Once you complete this you will want to immediately flash a current recovery such as Phil's 6.07.9 so have that zip already on your memory card before you start anything. Once you have a current 4.3 compatible recovery then reboot the stock rooted MC2 and immediately go to dialer and dial ##72786# to do a hands-free activation. This will ensure all your phone's provisioning is done before going to a different rom. Once that's done you can flash your rom of choice. Done
FYI: AOSP ROMS have specific instructions for install and initial setup so follow the OP's instructions. Also you must SKIP the phone activation portion upon initial setup of some AOSP ROMS. I just wanted to point that out in case you didn't know.

Your lucky that happen to my phone but the stuff don't come back . So now i have a mini tablet
Sent from my LG-LS980 using XDA Premium 4 mobile app

I have tried these things and still the same issues.
bonebeatz1234 said:
Your lucky that happen to my phone but the stuff don't come back . So now i have a mini tablet
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

threesix10 said:
I have tried these things and still the same issues.
Click to expand...
Click to collapse
try installing LJ4 and then re-flashing. MD4 caused that issue for me. Check my post in this forum too, and add your results.

[Q] Wanting to upgrade firmware

Im still running the Whompasaurs rom. Its such a good rom I haven't ever been able to get away from it. Now that 4.4.2 is getting more TW roms, I had a few questions.
Im getting great performance from my Whomp rom, is the TW 4.4.2 roms any faster, or do they eat up more resources and are generally slower?
The only thing that's making me nervous about just doing it is the upgrade process. It sounds like unrooting to stock and taking the official sprint OTA to 4.4.2 is better for the phone, but I don't want any of that Knox crap on there. Can I just Oden to a custom 4.4.2? It looks like I can, but then I will need to flash the WiFi fix, correct? I see the info out there, but everywhere I have seen some of it mentioned, its kind of scattered throughout a few post or in different threads. I was kind of hoping to get an all in one answer so I didn't have any doubts or questions.
I use to be a heavy flasher, but once I got on Whomp, I haven't really been around much and I am kinda rusty. I don't have another phone to fall back on and want to make sure I'm not going to brick it.

spotopolis said:
Im still running the Whompasaurs rom. Its such a good rom I haven't ever been able to get away from it. Now that 4.4.2 is getting more TW roms, I had a few questions.
Im getting great performance from my Whomp rom, is the TW 4.4.2 roms any faster, or do they eat up more resources and are generally slower?
The only thing that's making me nervous about just doing it is the upgrade process. It sounds like unrooting to stock and taking the official sprint OTA to 4.4.2 is better for the phone, but I don't want any of that Knox crap on there. Can I just Oden to a custom 4.4.2? It looks like I can, but then I will need to flash the WiFi fix, correct? I see the info out there, but everywhere I have seen some of it mentioned, its kind of scattered throughout a few post or in different threads. I was kind of hoping to get an all in one answer so I didn't have any doubts or questions.
I use to be a heavy flasher, but once I got on Whomp, I haven't really been around much and I am kinda rusty. I don't have another phone to fall back on and want to make sure I'm not going to brick it.
Click to expand...
Click to collapse
Well you can jump to custom 4.4.2 without upgrading. First you need to backup your internal sdcard because it needs to be wiped for best results. In 4.4.2 the directory structure is changed and without wiping you will end up with two internal sdcard directories (one you wont see but it will take up a bunch of your space). As far as speed things will be just as fast on 4.4.2 unlike the crappy 4.3 we had before.
Needed files
1. Philz 6.07.9 recovery or cwm (twrp will not work)
2. Wifi fix for 4.3/4.4.2
3. Custom 4.4.2 rom
Steps
1. Connect to pc and backup internal sdcard
2. Flash philz (done with odin or in recovery)
3. Boot philz and backup current rom (backup to external sdcard because internal will soon be wiped)
4. Factory reset clean for new rom
5. Under mounts choose format /data and data/media
6. Reboot your recovery (very important) this will make philz create it needed directories (it will ask if you want to root ignore it)
7. After reboot flash your custom rom
8. Boot into download mode
9. Odin wifi fix
Phone will reboot automatically after wifi fix is flashed. Now you setup your rom. I suggest that you do not use a backup app to restore any apps or data. Download everything you can fresh from playstore. Many apps and their data has changed since 4.1.2 and will lead to major issues if restored.
Now one thing about custom 4.4.2 roms. They all have the S5 dialer which has a lag on first call after boot. If you place a call (to voicemail is fine) after every boot you wont have any problems till you reboot.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Thank you for being so clear. Looks like it is what I was expecting but like I said I wanted to be sure. I do know that there is a new philz recovery as of July. I should be okay using that correct? Or is there a reason I need the version you mentioned?
Sent from my SPH-L900 using XDA Free mobile app

spotopolis said:
Thank you for being so clear. Looks like it is what I was expecting but like I said I wanted to be sure. I do know that there is a new philz recovery as of July. I should be okay using that correct? Or is there a reason I need the version you mentioned?
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
I have 4.4.2 Stock Rooted with Knox removed. I keep downloading your wifi patch, but everytime I try to load it into odin, it says the binary is invalid. any ideas?

spotopolis said:
I have 4.4.2 Stock Rooted with Knox removed. I keep downloading your wifi patch, but everytime I try to load it into odin, it says the binary is invalid. any ideas?
Click to expand...
Click to collapse
You are using pc odin and not mobile odin? Also try odin 1.85 or 3.07. Also you might have a bad download.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
You are using pc odin and not mobile odin? Also try odin 1.85 or 3.07. Also you might have a bad download.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried 307 and 309. Downloaded on phone the transferred to pc, no good. Tried downloading patch on pc from several different mirrors, no good, tried on laptop on WiFi, no good. They all give the invalid binary error. Tried running Odin in admin and without. I'm on win 8.1 x64. Have the Samsung USB drivers installed. No keis.

spotopolis said:
I tried 307 and 309. Downloaded on phone the transferred to pc, no good. Tried downloading patch on pc from several different mirrors, no good, tried on laptop on WiFi, no good. They all give the invalid binary error. Tried running Odin in admin and without. I'm on win 8.1 x64. Have the Samsung USB drivers installed. No keis.
Click to expand...
Click to collapse
Try this file http://d-h.st/6qX you will need to extract the rar file before you flash it.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Try this file http://d-h.st/6qX you will need to extract the rar file before you flash it.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That worked perfectly and I am up and running! Thank you for all your help :highfive:

spotopolis said:
That worked perfectly and I am up and running! Thank you for all your help :highfive:
Click to expand...
Click to collapse
Cool. Now enjoy the new NE2 rom out there. FYI you can run any rom (tw 4.1-4.4.2 and aosp 4.1-4.4.4) without any changes. Only thing you should do is wipe your internal sdcard (in philz go to mounts.. format /data /data/media) when you flash a new rom and this will keep you from have some weird issues (also backup your internal data such as pics, vids, etc.. before you format).