Database Users

Unable to flash back to stock! Help please?

So, I'm trying to flash back to stock, (either GB or ICS, at this point it doesn't really matter), and PC Odin fails to flash every time it tries to write the factoryfs.img
The only way I can get myself back to a working device is if I do a battery pull, go back into download mode, re-flash CWM and do a recovery back into CM9.
I have tried mobile Odin as well, and again, the flash fails when it reaches factoryfs.img. Are my partitions all screwed up? If so, how can i fix that?
Thoughts? Help? Thanks!

What rom were you on?

Jade Eyed Wolf said:
So, I'm trying to flash back to stock, (either GB or ICS, at this point it doesn't really matter), and PC Odin fails to flash every time it tries to write the factoryfs.img
The only way I can get myself back to a working device is if I do a battery pull, go back into download mode, re-flash CWM and do a recovery back into CM9.
I have tried mobile Odin as well, and again, the flash fails when it reaches factoryfs.img. Are my partitions all screwed up? If so, how can i fix that?
Thoughts? Help? Thanks!
Click to expand...
Click to collapse
You may have a partial brick then same as per this thread
I hope I am wrong and you solve your problem ASAP without any damage
Best of luck

Note_E said:
What rom were you on?
Click to expand...
Click to collapse
IMILKA's CM9 nightly.

Jade Eyed Wolf said:
IMILKA's CM9 nightly.
Click to expand...
Click to collapse
Well there is your problem. Has nothing to do with lpy like the fear mongers blindly think. Toss another one due to CM9...

And like I mention above, it's really weird, I can CWM and still use my device just fine, but if I want to flash new firmware, it freaks out. All I can do is re-flash Chainfire's CWM recovery and restore back to where I was...

Note_E said:
Well there is your problem. Has nothing to do with lpy like the fear mongers blindly think. Toss another one due to CM9...
Click to expand...
Click to collapse
Yeah, I didn't think it had anything to do with LPY, because I still had the same issue when trying to go back to KKA.

Jade Eyed Wolf said:
And like I mention above, it's really weird, I can CWM and still use my device just fine, but if I want to flash new firmware, it freaks out. All I can do is re-flash Chainfire's CWM recovery and restore back to where I was...
Click to expand...
Click to collapse
Beginning of emmc corruption. Not fried just yet. Some recover with pit file then flashing stock gb
Good luck to you bro

Note_E said:
Beginning of emmc corruption. Not fried just yet. Some recover with pit file then flashing stock gb
Click to expand...
Click to collapse
See, that's what I was thinking too... Where can I get the correct .pit file though? I have stock KKA already downloaded; that's what I've been using for a while now for any time I have had to flash back to GB stock for whatever reason.

I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...

Jade Eyed Wolf said:
I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...
Click to expand...
Click to collapse
Looking now. I one you need is around here somewhere

Jade Eyed Wolf said:
I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...
Click to expand...
Click to collapse
Hope this helps

Princeomi said:
Hope this helps
Click to expand...
Click to collapse
I'll give that a try. Thanks!

Just foud one in another thread http://forum.xda-developers.com/showpost.php?p=26009909&postcount=22

I was going to flash stock LC1 via pc odin cos I'm currently on LPY and I'd like to go back to GB. And I think I should ask before flashing that will it work and should I do something else than just hit lc1 in pda and flash?
Sent from my GT-N7000 using xda premium

Princeomi said:
Hope this helps
Click to expand...
Click to collapse
Sadly, those files are packaged in .7zip format. I'm at work right now, and I don't have the admin rights to install 7 zip just to extract it. Can you re-pack and post here in a regular .zip file please?

Jade Eyed Wolf said:
Sadly, those files are packaged in .7zip format. I'm at work right now, and I don't have the admin rights to install 7 zip just to extract it. Can you re-pack and post here in a regular .zip file please?
Click to expand...
Click to collapse
Here it comes

cs_allu said:
I was going to flash stock LC1 via pc odin cos I'm currently on LPY and I'd like to go back to GB. And I think I should ask before flashing that will it work and should I do something else than just hit lc1 in pda and flash?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Just flash it, if its a 3 file package put all the 3 files in their respective place, if its one file, put it in pda and flash and also make sure Kies is not running in the background

Well, at least this time the stock flash worked insofar as it completed. However, when the device reset, it went ahead saying "Installing packages" and such, and then it error'ed out saying something like there was invalid argument and it couldn't do something, then I was landed back at the stock recovery. I selected to reboot the system, and now I'm stuck at the Samsung boot animation; just keeps running indefinitely... What now?

Jade Eyed Wolf said:
Well, at least this time the stock flash worked insofar as it completed. However, when the device reset, it went ahead saying "Installing packages" and such, and then it error'ed out saying something like there was invalid argument and it couldn't do something, then I was landed back at the stock recovery. I selected to reboot the system, and now I'm stuck at the Samsung boot animation; just keeps running indefinitely... What now?
Click to expand...
Click to collapse
Hold power button and try to keep rebooting.

[Q] S4 Bootloop, Can enter download but not recovery

Hi,
I have been searching and searching. I tried to install a kernel to my phone, its been forever so i don't remember which one.
It just reboots every 5 seconds without any screens coming up. I can not get into recovery mode
I can get into download mode and have flashed stock I337UCUAMDB_ATTAMDB_I337UCUAMDB with odin, but it doesnt fix anything.
What can I do to get to stock recovery and fix my phone?

What happens if you put it on download mode and then cancel with vol down

It falls back into the bootloop of restarting every 5 seconds with no screens coming up. No entry into recovery.

And if you pull the battery and put it back in does it try to boot?

What firmware were you on and was it loki'd if you were on mdl?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!

megatilter said:
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
Click to expand...
Click to collapse
When did it start doing what's it's going. Did you do anything before hand? Do you know what firmware you where on before you tried odin? Was it mdb?

"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.

megatilter said:
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
Click to expand...
Click to collapse
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA

jd1639 said:
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
Click to expand...
Click to collapse
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i've never seen a kernel hard brick a device or corrupt the recovery partition. i also rarely see a user flash a file and not remember what they just flashed. he/she possibly flashed an incompatible kernel or flashed a non-loki'd kernel without flashing loki-doki. either way, recovery would still be accessible to correct this issue. i feel that there is more to this.
OP, see jd's jtag post above.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Great news! You got lucky, make sure you read and learn on xda. And always know what you flash.

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Care to share how you got Kies working? I have a similar problem and I can't get Kies to recognize my phone.

Fix!
So What you gota do
1. Pull Out Battery Put back in
2.Go To Download Mode
3. Download The TWRP.tar For Your Phone
4.Run Odin as Admin, Tick Pda, for pda select the TWRP.tar
5. Hit Start, Then Pull Out battery put it back in
6.Get A Micro Sd And Put The Cyanogenmod Rom, and the gapps the ones for your phone
7.Insert microsd in phone
8. Boot Recovery and go to mounts and mount the microsd
9, Go Advansed, file manager, ext sd, And Copy the cyanogenmod and the gapps to internal storage
10. Flash the cyanogen mod and the gapps. DO THIS PART CAREFULLY OR MIGHT HARD BRICK!
11. Reboot And youl boot to cyanogenmod! OH yeah! Replay if this helped or if you have any problems

[Q] Help Cant install Cyanogen

Ok Im not really sure what i am doing wrong I read alot of websites but just cant really find the problem im encountering. I downloaded 10.2 via computer and transferred to SD card, I rebooted into recovery and I wiped data/factory reset. Then I install update from sd card option and select the 10.2 cyanogen option. Everything starts then it goes something like "failed to verify whole signature", then it just ends up restarting as a new device. I have clockwork, goo manager (which I didnt do anything with). under clockwork I have TWRP set up.
To be honest i have no clue really what Odin is, and thought (as most walkthrus didn't comment) that odin was an alternative to flashing but not required?
I have rogers galaxy s4.. any help would be appreciated!!!

need more info
brotherhood8 said:
Ok Im not really sure what i am doing wrong I read alot of websites but just cant really find the problem im encountering. I downloaded 10.2 via computer and transferred to SD card, I rebooted into recovery and I wiped data/factory reset. Then I install update from sd card option and select the 10.2 cyanogen option. Everything starts then it goes something like "failed to verify whole signature", then it just ends up restarting as a new device. I have clockwork, goo manager (which I didnt do anything with). under clockwork I have TWRP set up.
To be honest i have no clue really what Odin is, and thought (as most walkthrus didn't comment) that odin was an alternative to flashing but not required?
I have rogers galaxy s4.. any help would be appreciated!!!
Click to expand...
Click to collapse
what firmware version do you have...MF3, MDL, MDB.... if your one mf3 how did you get cwm??? if not then just find another rom or re download it from cyanogenmod and make sure you have the right file to flash
hope i helped

He has rogers which is Canadian
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

ohhh
HiTideBlastoise said:
He has rogers which is Canadian
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
so why doesnt he just redownload it from somewhere else it might be a bad source....if its cyanogen then idk what to say......

Roms will not flash

Hello, I just recently rooted my note 3 and used safestrap to install roms. So far I have tried to install Hyperdrive and Jelly beans. neither will flash correctly. They go through the entire process and say sucessful. But then they say "unable to mount '/system," and "unable to mount '/systemorig."
Any help would be greatly appreciated.

Oh hell, now it wont even let me restore my backup. It was before. When i try now it says E: Unable to mount '/system. 5 times. Ugh. This blows. Cant reboot either. tells me no os installed.

Are you trying to install on the stock slot?
Sent from my SM-N900V using Tapatalk

DJ0224 said:
Oh hell, now it wont even let me restore my backup. It was before. When i try now it says E: Unable to mount '/system. 5 times. Ugh. This blows. Cant reboot either. tells me no os installed.
Click to expand...
Click to collapse
Did this on my tablet formatted the system and my internal memory on accident. Try downloading via a computer or tablet or other phone a ROM onto a Micro SD card then flash your ROM that way, that's what I had to do hopefully that will work for you. Sounds like your running with no ROM installed at all and you might of erased or corrupted your back up. Good luck!

ODIN... its not the end of the world.... at least not that i think so.

z06mike said:
Are you trying to install on the stock slot?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Yes, I am installing on the stock slot. I fixed everything with odin and re rooted and everything. Roms will install successfully now but will not boot When I start the phone i get a black screen. That's it.

What version of SS do you have installed?
Sent from my SM-N900V using Tapatalk

z06mike said:
What version of SS do you have installed?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
SS 3.72. I took the nc4 OTA. I used towel root, the newest version of chainfire supersu, installed busy box, then I installed SS 3.72. Everything worked great. I read that romslots will not work in 3.72 so I did a backup and i've tried to install Hyperdrive, Jelly beans (which i learned will not work since its 4.3 based BUT it still installs), and Eclipse. They all install but do not boot at all. Restoring my backup works fine though,

DJ0224 said:
Yes, I am installing on the stock slot. I fixed everything with odin and re rooted and everything. Roms will install successfully now but will not boot When I start the phone i get a black screen. That's it.
Click to expand...
Click to collapse
That is pretty much what i am encountering as well. I have stock backed up and i can boot into that if i need to but installing another rom on the stock slot or slot 1 is fine but the problem is booting. It will go up to the screen where it shows safestrap screen and then i just get a blank black screen. I left on for over 10min and nothing.
I got slot 1 to work by toggling the memory allocation to maximum. I believe it is unsupported at this point 3.72? somewhere I read that. You can only install rom on stock slot at this time. I tried installing on both but nada.
The system not mounting I get as well but sometimes it lets me check it and sometimes it does not let me check it. Dunno why.

I had the system not mounting problem, I returned to stock with odin and I dont have that issue anymore. The only problem I have now is the roms not booting.

Bump.
Anybody find anything useful? Im still having the same issue.

[Q] Help a noob, cannot boot after trying to flash stock rom

So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw

i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.

rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing

i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you

fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.

only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.

ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.