Database Users

[Q] [Wind] I tried flashing FoxHound ROM, and soft-bricked my phone. Any fixes?

Alright... where to begin? Lets start at what happened around yesterday. Prior to the whole weekend, I had CyanogenMod 10.1 installed on my rooted S4. Come Friday, I start to miss some of the stock Samsung features such as Air Gestures, Smart Stay, the stock Samsung camera, and all that. So, I install WanamLite (a custom rom) on my phone. It's good and all but for some reason, the Smart Stay isn't working. To fix this, I go online and start digging; I find people saying "yo, revert back to the original firmware and re-install the Rom, that should fix your LTE problem." I think to myself, "maybe this could help me too." And that's exactly what I do. I go online to SamMobile and download this ROM (http://www.sammobile.com/firmwares/?page=1&model=SGH-M919V&pcode=0#firmware). It installs with Odin and I was able to get back to the Stock Samsung firmware. I then proceed with my plan and install WanamLite; that also worked. So I'm all happy and stuff 'cause Smart Stay finally works but, shortly after fiddling with the re-stocked device, I get bored again. So, I start searching the forums for another rom to replace WanamLite (it was a good rom, but I wanted to try something else before settling down on it).
I find this ROM in the XDA-Developers S4 forum: http://forum.xda-developers.com/showthread.php?t=2303239. I try installing it; it works fine. But then, I notice that half my SD card is used up. So, I go into TWRP and click on Format Data (I'm not too sure about the name, I had CWM prior to the re-installation of Samsung stock firmware). After resetting the Data, I boot back into the phone and notice that the default layout is Easy Mode. (On the bright side, I freed 4 GB from my SD card). Easy Mode's incredibly annoying, so I wrestle with the phone for a while to change the launcher to Nova launcher, but to no avail. In the end, I decide to reflash the FoxHound ROM. I place the rom on my phone and boot into TWRP. That's where the problem comes. I selected: wipe cache, wipe delvic cache, wipe data. Then I wiped the cache and data, flashed the rom and, after that is when the phone started refusing boot up. From then on, it just displayed Samsung Galaxy S4 logo on the screen whenever I tried to start it.
What I tried to fix the issue: Re-installing the stock samsung firmware. (I think I ended up screwing up the phone even more with this. Before, I had TWRP installed but I couldn't boot into it, now I don't have any custom recovery installed and I still can't boot into the phone).
I can access the Download Mode and use Odin. I cannot boot into the recovery. When I hold Volume Up + Power + Home, it just says recovery in blue above the logo, and then, the phone reboots.
So, any ideas on how to fix it?
TL;DR: Tried installing FoxHound Rom. I wiped Delvic Cache, Cache, and Data, and after flashing the rom, the phone refused to boot up; it gets stuck on the Samsung logo. Before flashing, I did Format Data. After being unable to boot into the phone, I tried to flash the Stock Samsung Firmware on my S4. Nothing worked. Any ideas on how I should proceed?

splitinferno said:
So, any ideas on how to fix it?
Click to expand...
Click to collapse
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"

psycovirus said:
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
Click to expand...
Click to collapse
I've already tried flashing the Stock Samsung Firmware using Odin, it didn't work. Also, I'm having no luck with Kies; it won't connect. Any other suggestions? :/
EDIT 1: Okay, so here's the deal right now: I was able to flash TWRP using ODIN. This granted me access to my recovery, somehow. So right now, I have the FoxHound_GearEngine0.2 ROM installation files on my SD card and I am booted into the recovery. What should I do? Should I try flashing again? For now, I'll just wait for a response.
EDIT 2: Out of curiosity and impatience, I tried flashing FoxHound but got an error:
Updating Partition Details
E: unable to mount data
E: unable to mount internal storage
TWRP v. 2.5.0.3

Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else

maazali said:
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
Click to expand...
Click to collapse
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.

UNBRICKED
splitinferno said:
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
Click to expand...
Click to collapse
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.

Hahah nice job
Sent from my GT-I9505 using xda premium

splitinferno said:
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Click to expand...
Click to collapse
Next time don't wipe data in custom recovery because it will corrupt your data which would most probably end with not booting past the Samsung logo, if you want to wipe in a custom recovery for now you have to manually wipe system, cache and dalvik cache located in mounts in cwm recovery (not sure where to find it in twrp).
You should read a little before messing with things in recovery.

Ahahah that's funny because something similar happened to me. And I was going to suggest doing a factory reset via recovery because that's how I resolved my problem, then I see you did just that! (Y)
Sent from my GT-I9500

[Q] Stuck at boot screen after TWRP asking if I want to install SuperSU

I have to think I'm not the first to be in this situation but my searches didn't turn up anything that looked familiar.
I rooted the stock phone and installed TWRP 2.6xx a month or two ago with no issues. Everything's been running great and I decided it was time to make another backup using TWRP.
After a successful backup I wiped dalvik and cache out of habit and went to reboot -- TWRP said I was not rooted and wanted to know if I wanted to install SuperSU? This question was unexpected since I'd been rooted for a long time, and I decided to just say yes. The phone rebooted and stopped at the Samsung Galaxy S4 boot screen. I did up-volume reboot to recovery, but it seemed to hang at the TWRP blue screen -- I later discovered it will eventually get to the menu after a minute or two of the blue screen. I tried wiping cache and dalvik again and rebooting -- every time I try to reboot now it asks if I want to install SuperSU -- whether I say yes or no seems to make no difference -- I've tried both several times. Every time it hangs at the Samsung boot screen, or it takes forever to get to TWRP if I'm booting to recovery.
I've tried wiping cache, dalvik and data with no improvement. I finally tried formatting data, but again no improvement. I also tried restoring my backup several times and wiping cache and dalvik but still stuck.
I prior to today's problems I'd used TWRP a number of times and I don't recall it asking the SuperSU question, so I am thinking that is the key to this problem, and I'm wondering if anyone knows what it means?

You need to go to 2502 twrp, 26+ has hanging problems and possible Partition issues, also what rom are you on? Do you need to flash super su along with the rom /gapps?
Here's the twrp forum for us SPH-L720
The last page has a download link for the most stable build for us good luck!
http://forum.xda-developers.com/showthread.php?t=2262999

I'm running what came on the phone, just unlocked, rooted, and installed TWRP.
I ran CM10.1 on my previous phone and currently on my tablet, but my impression from running it previously is CM is a downgrade in voicemail functionality (you get these annoying text messages and have to call the voicemail), and I'm assuming it doesn't support the special GS4 hardware features like being able to hover your finger.

OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.

Nerva said:
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Click to expand...
Click to collapse
How did you root? CF auto root also installs SuperSU
Do you have a back up from when you were rooted? IF twrp keeps giving you problems, use cwm, are you able to get past the Samsung boot..

Yeah that's what I did back when I rooted it months ago. I tried running CF auto root again today and it didn't work, so I ran it from Odin and it did work that time, but there was no change -- still hangs on the Samsung boot screen, although now I'm back to the stock recovery. So I tried installing the stock MF9 firmware from Odin -- still hangs on the boot screen. I don't know what to do at this point...

After mf9 install avd stock recovery did you factory reset

Yes, I did a factory reset -- followed the video instructions by qbking77. Still hangs on the boot screen.

Take out battery.. Put back in. Go to stock recovery, holding all 3 buttons volume up factory reset.. If you used odin abd flashed mf9 it should fix you?
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Well I guess I tried man, someone who has more knowledge should chime in now
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
This
http://forum.xda-developers.com/showthread.php?t=2400192

Im also stucked with the same problem!! After flashing my rom succesfully it just ask ur device is not rooted swipe to install!! I tried all the posiblities!! but i stuck with the boot image!! pls help me!!

From experience it sounds like you should head over to sammobile and Odin back to stock and start fresh.
1. Odin to stock
2. Root phone
3. Put desired recovery
4. Flash ROM (be sure to read dev install instructions some require reboot of recovery after wipe)
5.try to restore backup (best if you flash ROM that is backup then restore backup)
6.if you went into nae or ng2 you cannot downgrade to me
7.google has many solutions
Sent from my SCH-I545 using XDA Free mobile app

Sorry for necro, but did anyone figure out a solution to this? This just happened to me.

Just Reflash it
We have the same issue, tried to install supersu binary, after installing through twrp recover, my phone went bootloop, as i've tried to search the internet, the issue doesn't fix by by most of the users unless they reflash their device. though its a bit hassle starting from zero, but atleast, you got ur device back

This helps me:
1. Run Odin on your computer and, after entering download mode on your phone, establish a connection between your devices with the help of the USB cable.
2.Note: for download mode – power off your smartphone and then press and hold, at the same time, the Power, Volume Down and Home buttons.
3.Odin will try to recognize your device; if everything works as expected, on the program the “added” message will be displayed and the ID:COM field will be turned yellow, or blue. (Note: if that’s not happening, unplug the USB connection, close Odin, force restart your phone and reinstall the USB drivers on your computer before retrying the steps from above)
4.From the program click on the “PA” button and load the custom recovery image; don’t check Re Partition and Auto Reboot options.
5.When done, click on “start” and wait while TWRP recovery is being added on your phone
6.In the end, Odin will display the “pass” message and the ID:COM filed will be turned green (or other color) with message - RESTART; you can then remove the USB cord and reboot your smartphone.

I have had this prob on a few things , if you have a backup,flash any mod that will go to the device will do then run the backup and reflash should work .and if you have twrp try to reformat all but the system and see if that helps.
Good luck.

Hi to everyone.
Today, I installed the TWRP and the ROM and both were installed correctly on a Le Pro3 X722. The problem started when the Google services were updating. Suddenly, the phone restarted and entered in a bootloop. I was not even able to enter the TWRP. The page freeze on LE-Recovery logo and then crashed (fill full of lines). I disconnected the battery for a while and then, I was able to enter the TWRP for 2 time but recovery crashes in few seconds. I wanted to wipe and install a clean rom but I cannot enter TWRP anymore.
Please, Is there someone that could help me?
Thank you very much in advance
PS. My phone is not recognized via ADB. I tried with the AIO Tool but my device is not detected.

Hi, I followed the whole process for Qfil explained here:
Leeco Le Pro3 x720 Hard Brick
So the phone was running lineageos 15.1 nightly from 22.08 which i guess was kind of really unstable (even opening twitter in the morning could turn off the device. It could be turned back on right away though), xposed framework v90 w/yt...
forum.xda-developers.com
Installation was correct but nothing change in my phone:
- same start page and bootloop
- Same problem trying to access the recovery.
Now, i can connect via fastboot and I would like to install a fastboot rom (preferable EUI stock 20) but I cannot find one. All links are dead.
Thank you very much in advance

[Q] i9505 (jgedlte) fails to boot system after installing ROM

I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?

Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.

Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).

[Q] Problem after flashing CF-Auto Root S5 SMG900F

Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance

Mike130784 said:
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Click to expand...
Click to collapse
Boot to recovery, wipe the caches, reboot, see how you get on then

*Detection* said:
Boot to recovery, wipe the caches, reboot, see how you get on then
Click to expand...
Click to collapse
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing

Mike130784 said:
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Click to expand...
Click to collapse
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal

*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
i used Odin3-v3.07
but after flashing the root everything worked installed superSU and updated it and its binaries and installed busybox,.
it all stopped working after i went into Stock Recovery and back
id prefer not to do a factory reset Wipe,. unless i really have to to fix it ,.
im going to try reflash with the latest version then,.
i have swapped SD card to galaxy tab to put the Flashable touch recovery on the SD card, and swapped back to the phone so i could Flash the Recovery when im in stock ,.
but ill try flashing Root with latest Odin first.. thank you

*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
the new odin is a bit less informative (to me as beginner)
i managed to use AP to flash the root again
all goes fine , it reboots
and its now upgrading android as it says and opening app's
then Black screen again,. i klick a button,. and it shows me again all the STOPPED msg's of all internal apps that are crashing,. litterally all apps,
what can i do ?

If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--

*Detection* said:
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
Click to expand...
Click to collapse
i cant fix persmission in stock recovery and flashing the philz touch recovery didnt work something about not verify signature,.
al i can do i guess is wipe data factory reset ,.but im affraid it wont fix anything

Try TWRP recovery instead
http://teamw.in/project/twrp2/229
No reason a factory reset won't fix things, worst comes to worst, flash the whole ROM again from ODIN, that will fix everything as it wipes and reinstalls the lot
Grab a stock ROM from sammobile

Thank you for all your replys mate..
I managed to get it working again by doing a factory reset in stock recovery after I flashed root with latest odin
Even tho it was my last resort there was nothing else I guess .
I'm not sure tho if this will happen again when I go back to recovery like I did when this all happend the first time while I actually want to flash a more advanced recovery then stock recovery ..
But I'll take my chances and just leave it as it is
Again thank you for your help and suggestions .
This thread could be closed
Sent from my SM-G900F using XDA Free mobile app

Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery

*Detection* said:
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
Click to expand...
Click to collapse
i have actually ,. i installed the TWRP u mentioned,. by taking there app from the Playstore,. and flashed the new recovery, within android and without rebooting (just in case)
im used to the old CWM thats why i first wanted the Touch recovery as its based on it,
but always open for trying new things
Thank you

Good stuff
Id say the whole entering recovery / apps crashing thing was a problem with the ODIN version you used to root, too old for Lollipop is my guess, so I wouldn't worry about entering recovery again.

Problem with Resurrection_Remix_LP_v5.4.6, camera and TWRP

Ok, so I've been Resurrection_Remix_LP_v5.4.6-20150530-hlte.zip for quite some time now, probably since not long after it's release, and it pretty much liked it. Except for the occasional seemingly random "auto reset" of android/app settings and preference (such as forgetting all my saved wifi ssid) after a random crash/reboot.
Starting last week, the camera became problematic, often failing to start entirely (error message, "could not connect to to camera"), or could connect to the back camera, but freezes when i try to switch to front camera. I tried wiping data with TitBak and it worked again, but the problem comes back a while later. Is this a software or hardware problem?
Anyway, I finally decided to upgrade the the latest RR and wanted to upgrade TWRP from 2.8.5 as I go along. Since the existing version fits the requirement for TWRP install...
Code:
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
... I went ahead and did it, with the standard 3 wipes (couple of times) and then the recovery flash. Turns out it didn't work and the phone just keeps freezing at the first screen with Note3 logo and the red/blue/yellow test at the top left saying booting to recovery. It never did!
I then tried to reflash the recovery using odin with the .tar file, it flashed fine and auto re-booted back into the launcher (everything's gone of course). But I still needed to go back into recovery mode to either flash a higher version of TWRP, or install the newer RR.
Still, it gets stuck and wont go to recovery no matter i used the hardware button method, or recovery button in the power menu, or adb reboot recovery.
What's wrong!?!??!

c'mon guys, give me something.

You have flashed newer RR how it goes back to older version after you odin twrp?. Or you mean currently it's the latest, just in the future you need to update to the newest?. Did you flashed the correct rom zip for your phone?. I mean hlte for n9005 and the rest for other variants. I haven't flash 'google like' roms for long not sure it's still different zip for each variants.
Sent from my SM-N920C

I haven't even got to the point of flashing the ROM so it's still on the old RR.
I need to know how to upgrade to the latest TWRP first.

Then why 3 wipes?. If you wipe system you have no rom in the phone.
Sent from my SM-N920C