[tosinwashere]

The Wifi on my phone wasn't turning on, even after factory reset, so I reflashed stock ROM via Odin (v3.07)
I got stuck in a bootloop, and after factory reset via the stock recovery + wipe of cache partition, it was still stuck.
I then re-flashed the stock ROM. Still stuck.
Tried using Kies 3, with the firmware upgrade and installation tab. Said something about not supporting my phone when I was prompted to plug it in. (SM-G355H; Samsung Galaxy Core II Duos)
I then found an unofficial version of CWM v6 for my phone (there's no official support), and quickly flashed that (via Odin 3.09; which is what I use from this point on), forgetting that my phone was no longer rooted. I wiped davlik cache and data. Still stuck. Then I rooted my phone. Stuck.
Then I reflashed stock ROM (this time, I downloaded from another website) (to test my luck, I tried seeing if simply a factory reset and cache wipe would work. It did not) rooted my phone, and flashed CWM. Wiped davlik cache. Still stuck.

By the way, when I wipe davlik cache it says:
Warning: no file_contexts
E:unknown volume for path [/sd-ext]
Davlik Cache wiped.

Any ideas on what to do now? I can't send it to a manufacturer / repair store where I live. I'm thinking maybe I should untick Auto Reboot and/or F. Reset Time when flashing, use an earlier version of Odin or the ROM itself, or maybe there is something I can do with ADB? I'm not very familiar with it, but I'm more than willing to learn. I just need some direction...

[Golfdriver97]

Welcome to the forums. Try this: Pull the battery for a few minutes. Then reboot normally. If that doesn't work, try pulling the battery again, and reboot into recovery by pressing volume up and power at the same time. Release when you see the Samsung logo.

[tosinwashere]

Reboot into recovery and do what? The normal reboot didn't work. I've factory reset and wiped cache more times than I can count.

[Golfdriver97]

Sorry, to clear the cache. I should have been more clear. Have you tried redownloading the file?

From an AOSP M8

[tosinwashere]

Yeah, I redownloaded the file, then the stock ROM from another website. Same thing.
I've also used Kies. It didn't recognize my phone.

[Golfdriver97]

Sorry about the delay. Do you have the most up to date drivers installed for your PC?

From an AOSP M8

[tosinwashere]

I finally fixed the bootloop via Kies. I had to ignore the notification that said my device wasn't supported and just left it there overnight. Apparently the ROM version for my country was not the one I was supposed to be using, since it was probably imported.

-----

Why was the title of the thread changed? I had been trying to reply to this thread for a while but it kept telling me something about a security code.