Develop Bugs

[Q] HELP! Having problems installing apps after installing new ROM

I've just rooted my phone and flashed the leeDroid ROM successfully, however a few days after flashing the ROM, my phone is unable to install any apps successfully. There is always a sign saying "Installation of xxxx is not successful"
Anyone have solutions to this problems? Do not really know what to do here

Try to factory reset your phone: settings>SD & Phone storage>Reset
If that doesn't solve it, download the ROM again and reflash it. And make sure you flash FULL-WIPE-1.3.zip first!

If you don't want to have to flash another app (for wiping data etc.) you can just do this from recovery where you can decide what needs wiping (between ROM's and re-installs though wipe everything).
Just my personal preference.
Sent using witchcraft via XDA Developers App.

sandmouse said:
I've just rooted my phone and flashed the leeDroid ROM successfully, however a few days after flashing the ROM, my phone is unable to install any apps successfully. There is always a sign saying "Installation of xxxx is not successful"
Anyone have solutions to this problems? Do not really know what to do here
Click to expand...
Click to collapse
I had a similar issue & FIX posted here: http://forum.xda-developers.com/showthread.php?t=1054073
Not sure if will work for you, but maybe a few ideas.
Edit: Usually clearing Market cache, reboot into cwm recovery & delete dalvik does the trick, but for me, Gmail was part of the problem as well.
Sent from my Desire HD using XDA App

Foladko said:
Try to factory reset your phone: settings>SD & Phone storage>Reset
If that doesn't solve it, download the ROM again and reflash it. And make sure you flash FULL-WIPE-1.3.zip first!
Click to expand...
Click to collapse
FULL-WIPE = the most effective solution for the all the problems!!
in adition he can do "formats" in the paragraph "mounts and storage" (if I don´t forgot the location )
This way already you insure yourself of having a hyper-clean ROM

Cannot Restore/Install ROMs

So I installed the 12/09 Nightly of CM10 and ever since I cannot Restore or Install any ROMs. My Recovery is TWRP 2.3.1.1. It seems as though I cannot Wipe Cache, Dalvik, Factory Reset or System Wipe either. When I am using the latest installed ROM after a couple hours all of my apps force close, including Trebuchet leaving me to reset my phone.
When I reset and go into Recovery, I can restore backed up ROMs or new ones and when I reboot I am still on 12/09 CM10 with no errors until after a couple hours go by. I have tried installing CMW with no luck and re-installing TWRP with no luck. I have also tried the unrooting/unbricking method using Odin with no luck.
I am stuck on CM10 12/09 Nightly and my TWRP isn't helping in any way. I don't know if anyone else has ever run into this problem. Please help if you can.

Did you somehow loose super user? It sounds like a permission thing. When you install a new rom watch closely to what it says. You have to be getting some kind of error.
Hope this helps, good luck

Have you tried re rooting then re flashing twrp?
Sent from my liquid smooth t989

onlychevys said:
Did you somehow loose super user? It sounds like a permission thing. When you install a new rom watch closely to what it says. You have to be getting some kind of error.
Hope this helps, good luck
Click to expand...
Click to collapse
It still asks for super user when I go into a root application. I have tried installing supersu and it fails when trying to update the binary files. It has to be an error. Is it possible that my recovery could have become corrupt? I can't even download a new version of CM10. Every time I tried installing clockwork through rom manger is force closes all my apps and I am still on twrp. I have even tried installing with terminal emulator as well with no luck.

skaroger867 said:
Have you tried re rooting then re flashing twrp?
Sent from my liquid smooth t989
Click to expand...
Click to collapse
Yeah I tried re rooting using odin back to ICS with no luck. I tried unrooting using odin as well that would put me back to gingerbread. I have tried just about everything I can think of. My next option to try is pushing files through adb.

[Q] Cannot flash anything

T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.

moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium

soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.

moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium

Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?

Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.

OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place

moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.

meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...

moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.

i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem

meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?

Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?

moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.

I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418

Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.

moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.

moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium

went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?

moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.

You need to give more info on the error
Sent from my SGH-M919 using Tapatalk

serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.

Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app

spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.

Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?

Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.

Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.

Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?

So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.

Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.

To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.

Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.

Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3

I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?

Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something

Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement

GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)

My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.

You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.

Im still here having problems booting 4.4.2

In all my previous posts requesting help of why my phone wont boot 4.4.2 ive never gotten a clear answer or any troubleshooting steps.
when i flash 4.4.2 with any recovery it goes to rom logo and doesnt boot past that. the only rom ive been successful with flashing is omni rom. whats the difrence between omni rom and any other regular 4.4.2 rom/
all i want to do is use carbon kk i had 4.4.2 working once before i flashed 4.3 and the wifi fix and after i flashed the wifi fix my phone stopped booting into 4.4.2 ever since ive been trying to get a odin wifi fix removal for my phone. i want to see if that will fix it but no one will help
also in cwm recovery upon wiping
you get an android_secure not found or somthing like that

zachdees said:
In all my previous posts requesting help of why my phone wont boot 4.4.2 ive never gotten a clear answer or any troubleshooting steps.
when i flash 4.4.2 with any recovery it goes to rom logo and doesnt boot past that. the only rom ive been successful with flashing is omni rom. whats the difrence between omni rom and any other regular 4.4.2 rom/
all i want to do is use carbon kk i had 4.4.2 working once before i flashed 4.3 and the wifi fix and after i flashed the wifi fix my phone stopped booting into 4.4.2 ever since ive been trying to get a odin wifi fix removal for my phone. i want to see if that will fix it but no one will help
also in cwm recovery upon wiping
you get an android_secure not found or somthing like that
Click to expand...
Click to collapse
The android secure issue you see is actually nothing. It is stating it cant find that directory on you sdext partition which you dont have unless you partition your sdcard.
Now why you cant boot 4.4 is kind of odd. I have gone between all versions for our phone aosp and touch wiz without any problems. I would suggest installing twrp and then running billards back to stock mc2 with counter reset (located in development section). Make sure you read the op for that thread and follow his directions. After flashing that before rebooting flash a root.zip (dont use twrp's root). Once your booted you can use odin or an app to flash cwm or philz (6.07.9 recommended) then you can flash any 4.4 you want. Just remember to wipe/format your internal sdcard (data/media) before going to 4.4.
Sent from my SPH-L900 using XDA Premium 4 mobile app

My phone won't let me format the internal sd card it seems like Its locked or something also I've done back to stock 5 times and no luck

Which recovery and how are you trying to format internal?
Sent from my SPH-L900 using XDA Premium 4 mobile app

Do what jlmancuso said. This will format your internal sd as well. Just go back to stock unrooted MC2 and don't bother with flashing the root till its back up and running stock unrooted. Once you do that use the Samsung Note 2 Toolkit (version 2 not 3) and choose the ALL IN ONE Root,recovery, busy box, etc option and choose the twrp recovery not clockwork. Once you get it rooted and on twrp recovery, immediately flash Phil's recovery. 6.07 version (or whichever version that has already been recommended). Then wipe everything as usual including dalvic, cache, internal sd. Then flash stock rooted MK4 in lorjay's thread. then use ODIN on your PC to flash the wifi fix. Do a prl and update profile while on stock rooted MK4. Once you are at this point you can then flash any KK rom and it should work fine. just make sure you set your phone down and let it complete the initial boot as it sometimes takes a few minutes to boot. If this does not work then you're screwed LOL. Good luck.

tx_dbs_tx said:
Do what jlmancuso said. This will format your internal sd as well. Just go back to stock unrooted MC2 and don't bother with flashing the root till its back up and running stock unrooted. Once you do that use the Samsung Note 2 Toolkit (version 2 not 3) and choose the ALL IN ONE Root,recovery, busy box, etc option and choose the twrp recovery not clockwork. Once you get it rooted and on twrp recovery, immediately flash Phil's recovery. 6.07 version (or whichever version that has already been recommended). Then wipe everything as usual including dalvic, cache, internal sd. Then flash stock rooted MK4 in lorjay's thread. then use ODIN on your PC to flash the wifi fix. Do a prl and update profile while on stock rooted MK4. Once you are at this point you can then flash any KK rom and it should work fine. just make sure you set your phone down and let it complete the initial boot as it sometimes takes a few minutes to boot. If this does not work then you're screwed LOL. Good luck.
Click to expand...
Click to collapse
The red additional steps are unnecessary and make little sense. Otherwise, yup.
I'm of the hunch-ish opinion that it is the "wifi fix" that causes lots of these problems in the first place. Most everyone who flashes 4.4.2 builds and that has issues usually share the common thread of having that "wifi fix" on their phone....and that is a hunch, yes, purely on my part. In any case MK4 (radio, ROM, etc) is in no way needed to flash 4.4.2 builds.

I Have done every flash to stock with counter reset. and no matter how many times ive tried it still bootloops i need a DIRECT WIFI FIX REMOVAL

There is no such thing. All the wifi fix is a flash of the param.bin which is in the mk4 odin file. Also those who took the ota have it. It in no way effects aosp!
Are you flashing anything besides the 4.4 rom?
Sent from my SPH-L900 using XDA Premium 4 mobile app

Are you also performing the data wipe and factory reset AFTER FLASHING THE ROM AND GAPPS? Many miss this required step.
Sent from my SPH-L900 using xda app-developers app

thunderwagn said:
Are you also performing the data wipe and factory reset AFTER FLASHING THE ROM AND GAPPS? Many miss this required step.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I have never had to do that but it wont hurt to try it.
Sent from my SPH-L900 using XDA Premium 4 mobile app

i have always payed close attention to that step. im almost to the point of selling my phone for the note 3 this journey is almost over

zachdees said:
i have always payed close attention to that step. im almost to the point of selling my phone for the note 3 this journey is almost over
Click to expand...
Click to collapse
That is definitely a good idea...considering that last I knew Note 3 has yet to get working 4.4.2 builds.