Database Users

[Q] Why...?? CONFUSING!!!!!

I honestly don't know where to start, I bought the Samsung galaxy s4 i337m from virgin mobile, and use it with my Bell carrier. I was browsing the internet when I come to a video that states that you can flash i9505 roms on my i337/i337m phone! So silly of me to try that, it actually worked. When I was tired of that ROM, I go on this forum thread and look for another ROM, a ROM that is i337m cooked, and it soft bricked my phone, 3 times for 3 different i337m ROMS, at this point I have absolutely no clue what is going on with my phone, is the bootloader unlocked? WTF IS LOKI?? WHY does a i9505 ROM work on my phone, and a i337m cooked ROM does not, I just need some answers!! I have been flashing my phone with ROMs since my s1 and now the s4 comes along and completely wipes any knowledge I had before I got the phone, if anyone can help me on which ROMS I can and/or can't flash, that would be great, sorry for english not my first language!

Read and do some research. Just because you flashed a number of other phones doesn't mean you know how to flash this one. Every phone is different. It would also help to know what roms you flashed that didn't work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.

TheAxman said:
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
Click to expand...
Click to collapse
I still don't understand, I have the north american version of the i337m from Canada....

Dragosmp said:
I still don't understand, I have the north american version of the i337m from Canada....
Click to expand...
Click to collapse
What roms did you try to flash? Where did you get them? The boot loader is not locked and they should flash. Did you check the md5sum? They could be bad downloads.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Loki is needed for phones purchased through at&t. The Canadian version is the same phone, but without a locked boot loader, so the Loki hack is not needed.
What I have found is that some of the custom recoveries don't wipe out the phone properly. Try using Odin and go back to stock, wipe, then restart fresh
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app

Matridom said:
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'd do the full wipe before flashing. If you wipe after DON'T wipe system or you'll be in trouble.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Actually, I totally found that the Loki fix was needed for my Canadian i337m device (Bell). Many ROMs wouldn't work without it; they'd just get stuck in the boot logo (including SlimRom and CyanogenMod).
Just flash the ROM, then flash the Loki-Fix and you should be good to go.
If you're seriously stuck and you can't get back into your custom recovery, let me know and I'll help you out.

Now I am confused. Why would the I337m need a loki anything?
It is not needed. I surprised it even flashed.

TheAxman said:
Now I am confused. Why would the I337m need a loki anything?
Click to expand...
Click to collapse
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.

Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
Do you know what your stock firmware was before you started flashing custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?

jd1639 said:
Do you know what your stock firmware was before you started flashing custom roms?
Click to expand...
Click to collapse
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
TheAxman said:
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
Click to expand...
Click to collapse
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.

Te3k said:
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Click to expand...
Click to collapse
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.

Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
Which custom recovery are you using to flash with and how did you get it on your phone?

Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
This is just not true. No way. Friggin way weird.

scott14719 said:
Which custom recovery are you using to flash with and how did you get it on your phone?
Click to expand...
Click to collapse
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!

Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
And this procedure worked for you? You said you had to loki, where did that come in?

TheAxman said:
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
And this procedure worked for you? You said you had to loki, where did that come in?
Click to expand...
Click to collapse
Phone identified as i337m from settings menu prior to any flashing. Model number under battery matches: Model: SGH-I337M / IC: 649E-I337M.
Using Loki came in where I found that flashing ROMs wasn't working. I had already rooted and tried to unlock the phone through the debug menu. Unlocking didn't work, but rooting did and I could load custom recoveries without problem. I thought that I should try flashing other ROMs to see if I could unlock the device through their debug menus, but no luck. The first ROM I tried to flash was a SlimRom nightly. That one appeared to flash properly (recovery said "success"), but upon reboot I got stuck in a boot loop. I then went back to recovery and messed around trying to flash other ROMs and ran into the same issue persistently. I eventually panicked and Odined back to stock ROM and kernel (numbers previously mentioned). Everything was fine after I figured out how to make Odin work. (I even learned how to make signed-MD5 tarballs with Cygwin to try to make flashing recoveries and roots simpler by using Odin.) After wondering why I couldn't flash any custom ROMs, I dug around a bit and found out that some ROMs' first-posts mentioned that certain fixes had to be applied—some of which were labelled ROM-specific (e.g. GOLDENEYE-i337m-FiX-XXUBMF8) and others that just said that they required a Loki fix, and sometimes provided a link to download it. At the time I didn't know what Loki was, and I wasn't understanding why certain ROMs would come pre-"Lokified" (brain was full after hacking around for >6h). So in the moment it made no sense not to try flashing that to see if it would help. Lo and behold, it worked! I started flashing Loki after every ROM install from then on out. Previously not-working ROMs that I had already tried suddenly worked just fine (I didn't redownload them; I kept the same zip files and just started flashing the Loki Fix after each of them to make them work).
It's still the case that when I want to flash a new ROM, I wipe everything from recovery and flash the ROM. If it doesn't boot, I flash the Loki Fix and then it does boot properly.

Is running a rom in the stock slot safe

TLDR: Would it be safe to run Beans B5 in stock?
As long as I verify I have a clean backup.
I am new to the note 3 and haven't been a part of the root community for over a year. I do my research though before I make any changes.
Verizon SM-N900V currently running Beans B5 in rom slot 2. Backup of rooted stock in slot 4. Hyperdrive is in slot 1, but I don't plan on using is as a daily.
What are the benefits of the stock slot of a SS slot?
Sent from my SM-N900V using XDA Premium 4 mobile app

Personally, I wouldn't install a custom ROM in the stock slot. That gives me something to fall back on in case something goes wrong.
Running a ROM from a slot other than stock will cause the storage of your device to be read incorrectly. But don't worry, you still have access to all of it, the system just reads it wrong.

It's fine running in stock slot. You can use ODIN to get back to stock if necessary, then re-root, install safestrap, and start over - same as if you had a note 2 or other phone with unlocked bootloader.

I'm running Bean's build 4 on my stock slot. All the others are empty and everything is running awesome. I love it. Only one bad thing, there is nothing else to do to my phone now cause I'm happy with the way it is.
Take a sec and hit thanks if I helped or if you're in a good mood!

bskarpa said:
I'm running Bean's build 4 on my stock slot. All the others are empty and everything is running awesome. I love it. Only one bad thing, there is nothing else to do to my phone now cause I'm happy with the way it is.
Take a sec and hit thanks if I helped or if you're in a good mood!
Click to expand...
Click to collapse
I've been wondering the same thing. I just ODIN'ed back to MJ7 Stock and updated to MJE then rooted. I would like to use my ROM in stock slot, but there are so may people that say no and others that say they do.

Xirix12 said:
I've been wondering the same thing. I just ODIN'ed back to MJ7 Stock and updated to MJE then rooted. I would like to use my ROM in stock slot, but there are so may people that say no and others that say they do.
Click to expand...
Click to collapse
Just depends how much work you want to do if something breaks. I flashed on stock slot because I have no problem using Odin to get stock back and trying again. (And little things like memory showing full bug me) Though I haven't actually had to do that yet.

ginger man said:
Just depends how much work you want to do if something breaks. I flashed on stock slot because I have no problem using Odin to get stock back and trying again. (And little things like memory showing full bug me) Though I haven't actually had to do that yet.
Click to expand...
Click to collapse
Oh.... well in that case I don't mind it. I used to ODIN back to stock and reroot multiple times on the GS4 since I had problems with it. Rooting the Note 3 is so easy it's not as much work as the traditional way of rooting (ADB and entering commands).
Thanks
Question:
I have flashed a custom ROM to Slot 1. Can I delete Slot , wipe Stock Slot and flash a ROM to it? Or should I ODIN to stock, reroot and then flash ROM to Stock Slot?
Sent from my SM-N900V using Tapatalk

Xirix12 said:
Oh.... well in that case I don't mind it. I used to ODIN back to stock and reroot multiple times on the GS4 since I had problems with it. Rooting the Note 3 is so easy it's not as much work as the traditional way of rooting (ADB and entering commands).
Thanks
Question:
I have flashed a custom ROM to Slot 1. Can I delete Slot , wipe Stock Slot and flash a ROM to it? Or should I ODIN to stock, reroot and then flash ROM to Stock Slot?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I don't see why that wouldn't work. Try it out and if doesn't then Odin to stock and start over. Just back up what you need just in case.

ginger man said:
I don't see why that wouldn't work. Try it out and if doesn't then Odin to stock and start over. Just back up what you need just in case.
Click to expand...
Click to collapse
True I'll try that now.
Edit: been on Stock Slot for well over 7 hours now and I have to say everything seems to be running smooth. I can also see my exact remaining memory.
Sent from my SM-N900V using Tapatalk

[Q] Revert to stock rom

ok so i have installed JellyBeans rom and im not liking it. im on base version JSS15J.N900VVRUBMJE.
how do i get back to the most updated stock rom on note 3?

Am assuming that you are using SafeStrap. If so, boot to recovery. Go into boot options and activate the "stock" slot. Then, if you want to, you can go in and delete rom slot that you have beans installed on.
Once you activate the stock slot, you'll know it because it will tell you with red text across the top of the screen.
Then just reboot.
IF YOU INSTALLED BEANS ROM ON THE STOCK SLOT, you need to download a copy of the stock odex or deodex rom that beans put together in the dev thread. If this is the case, let us know if you need help before going any further!
♢NoteIII♢

Yes I made a new slot for beans and still have the stock one open. Thanks ill just use the stock slot. Now what about me getting the latest updated stock rom and still keep root, how would I do that?
Sent from my SM-N900V using XDA Premium 4 mobile app

spetzuu said:
Yes I made a new slot for beans and still have the stock one open. Thanks ill just use the stock slot. Now what about me getting the latest updated stock rom and still keep root, how would I do that?
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So the rooted rom on your stock slot is what version?
♢NoteIII♢

LeftyGR said:
So the rooted rom on your stock slot is what version?
♢NoteIII♢
Click to expand...
Click to collapse
MI9

spetzuu said:
MI9
Click to expand...
Click to collapse
Eh...
Best way would mean you'd need to redo root. And that way would be with odin. Unless someone else has a better way?
♢NoteIII♢

ive tried finding out the benefits of the updates that have rolled on on the note 3 and i cant seem to find any... although i have seen people complaining about the battery life and what not.
do you know where i could get a complete list of what the updates bring to phone? because if its nothing major ill just stick to MI9

Honestly, it will be different for every person. Because even though we all have the same phone, Every Phone is just a little different. For example, I am on the current update and felt I needed to because I was having issues with wifi. But if you are on the original firmware, which you are, and you can find no problem with your phone that you would like to see fixed then I honestly don't see any point in updating your firmware if you do not want to. I know that the current version addresses problems people were having with wifi. Along with some other minor changes.
Now having said that... If you encounter any quirks or problems with any current custom ROMs that are listed in the development section, it may be due to the fact that they are built on the current firmware version while you are still two versions behind.
♢NoteIII♢

Easiest way to 4.4.2?

I'm wanting to update my gf's M to 4.4.2 and am wondering the easiest way to go about it. It's currently rooted and running a custom ROM, but she doesn't care about any of that. Could I just download the sbf and used RSD Lite to flash it? Or would I need to flash an earlier build and then take the OTA? I'm not worried about keeping root or an unlocked bootloader, but would there be any way to keep her Candy Crush data (that's the only thing on the phone that means anything to her)?

Yea just grab 4.4.2 KitKat and flash it with rsd. . then flash SuperSU or use towelroot to get root back
Sent from my XT907 using XDA Premium 4 mobile app

Awesome! Any chance at saving her game data? I was going to try Helium, but I remember that Moto broke it.

stick1300 said:
Awesome! Any chance at saving her game data? I was going to try Helium, but I remember that Moto broke it.
Click to expand...
Click to collapse
Titanium Backup attempts to recover/restore app data. It works on about 75% of apps I try, but some lose their data.

ezknives said:
Yea just grab 4.4.2 Kitkat and flash it with rsd. then flash towel root to get root back
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will this work if I already have an unlocked bootloader (from the exploit in Jelly Bean)?

thad137 said:
Will this work if I already have an unlocked bootloader (from the exploit in Jelly Bean)?
Click to expand...
Click to collapse
Sure will. You will lose root but not the unlocked bootloader.
Sent from my DROID RAZR M using Tapatalk

You can edit the .xml file so that it doesn't wipe userdata, and that should let her phone keep all its settings, apps, data, etc. It'd definitely be smart to also back that stuff up with TB as well, though. If you do edit the .xml that RSD Lite uses to flash, make sure to use something like Notepad++, and not just Windows Notepad. I think you also have to edit out the getvar line if you're flashing over a non-stock ROM. If you've done the NV edit with RadioComm, supposedly you can also delete the modemst1 and modemst2 lines, and you shouldn't have to redo the GSM hack.

Is there a way a person could flash just the bootloader in RSD instead of wiping my custom rom?

thad137 said:
Is there a way a person could flash just the bootloader in RSD instead of wiping my custom rom?
Click to expand...
Click to collapse
I've seen some reports that you can do the boot.img file, but it softbricks most devices. I'd suggest just backing up your stuff and flashing stock and then go back to your ROM. Or just leave it, unless its CM11.
Sent from my DROID RAZR M using Tapatalk

thad137 said:
Is there a way a person could flash just the bootloader in RSD instead of wiping my custom rom?
Click to expand...
Click to collapse
I believe the answer would be no... I think your asking if you could go from the jb bootloader to the kk one or vise versa via rsd by only flashing the boot loader and keep your current ROM... if that's the case no as the Roms (not sure how it all works) have become dependent on which boot loader you have... So the ROM your on probably will not function if you could flash just the boot loader... Like as I'm on kk I can't use PAC man as it needs the jb boot loader or whatever... And if your on jb (last I checked) you can't use the newer builds of kitstalk... So your best bet would be stay as you are or flash the whole thing IMHO...but I may be wrong
Edit... That's the second time we have started a reply at the same time @xKroniK13x you get it out faster tho....

ezknives said:
I believe the answer would be no... I think your asking if you could go from the jb bootloader to the kk one or vise versa via rsd by only flashing the boot loader and keep your current ROM... if that's the case no as the Roms (not sure how it all works) have become dependent on which boot loader you have... So the ROM your on probably will not function if you could flash just the boot loader... Like as I'm on kk I can't use PAC man as it needs the jb boot loader or whatever... And if your on jb (last I checked) you can't use the newer builds of kitstalk... So your best bet would be stay as you are or flash the whole thing IMHO...but I may be wrong
Edit... That's the second time we have started a reply at the same time @xKroniK13x you get it out faster tho....
Click to expand...
Click to collapse
At least we post similar responses! ?
Sent from my DROID RAZR M using Tapatalk

xKroniK13x said:
I've seen some reports that you can do the boot.img file, but it softbricks most devices. I'd suggest just backing up your stuff and flashing stock and then go back to your ROM. Or just leave it, unless its CM11.
Sent from my DROID RAZR M using Tapatalk
Click to expand...
Click to collapse
ezknives said:
I believe the answer would be no... I think your asking if you could go from the jb bootloader to the kk one or vise versa via rsd by only flashing the boot loader and keep your current ROM... if that's the case no as the Roms (not sure how it all works) have become dependent on which boot loader you have... So the ROM your on probably will not function if you could flash just the boot loader... Like as I'm on kk I can't use PAC man as it needs the jb boot loader or whatever... And if your on jb (last I checked) you can't use the newer builds of kitstalk... So your best bet would be stay as you are or flash the whole thing IMHO...but I may be wrong
Edit... That's the second time we have started a reply at the same time @xKroniK13x you get it out faster tho....
Click to expand...
Click to collapse
Thanks I'll just go ahead and go through the entire process of flashing everything for the new version of Paranoid Android.
UPDATE: I manually flashed everything but "system" and "recovery" and then flashed dhacker's recovery from here ( loki.rombitch . com/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img ) then I flashed the Paranoid Android update and everything is working.

thad137 said:
Thanks I'll just go ahead and go through the entire process of flashing everything for the new version of Paranoid Android.
Click to expand...
Click to collapse
Paranoid has a 3.4 kernel ROM? How did I miss that?!

xKroniK13x said:
Paranoid has a 3.4 kernel ROM? How did I miss that?!
Click to expand...
Click to collapse
heres a link..http://www.drdevs.com/devs/?dir=cj360/Aospa

xKroniK13x said:
Paranoid has a 3.4 kernel ROM? How did I miss that?!
Click to expand...
Click to collapse
I'm still new, so I can't link it, but... http://forum.xda-developers.com/showthread.php?t=2696606
(second post) (I think he meant 07-02-2014)

5318008 said:
You can edit the .xml file so that it doesn't wipe userdata, and that should let her phone keep all its settings, apps, data, etc. It'd definitely be smart to also back that stuff up with TB as well, though. If you do edit the .xml that RSD Lite uses to flash, make sure to use something like Notepad++, and not just Windows Notepad. I think you also have to edit out the getvar line if you're flashing over a non-stock ROM. If you've done the NV edit with RadioComm, supposedly you can also delete the modemst1 and modemst2 lines, and you shouldn't have to redo the GSM hack.
Click to expand...
Click to collapse
Yeah, I read about this in another thread and it worked fine. She's now on stock 4.42 and has her treasured Candy Crush data.
Now, if I could just get her wifi working again. I've done so much reading about the issue lying in the /persist (and/or /prima) folder, but, even after trying multiple "clean" copies of it and fixing permissions and everything else people have suggested, I can't get it working again.

I wish I could help there but I don't have any useful info to offer. I've heard a number of complaints about the WiFi on KK on the Razr M, so I don't think it's just you. I heard they're testing another KK update, maybe it'll fix it when it rolls out. I did notice that the time I tried flashing the KK radio onto my stock JB, it totally broke my WiFi and I had to flash back.

5318008 said:
I wish I could help there but I don't have any useful info to offer. I've heard a number of complaints about the WiFi on KK on the Razr M, so I don't think it's just you. I heard they're testing another KK update, maybe it'll fix it when it rolls out. I did notice that the time I tried flashing the KK radio onto my stock JB, it totally broke my WiFi and I had to flash back.
Click to expand...
Click to collapse
It stopped working when she was still on JB. I had hoped updating would fix it, but no such luck. The only way I managed to get it working in the past was by reflashing the ROM that was on the phone, but it stopped working again after a few weeks.

Upgrading to 5.0 from NI2

Does 5.0 not suck enough to do this yet? My new car has AndroidAuto and I want to use it but can't with my current 4.4.4 verison. Last I read, 5.0 sucked and everyone was trying to downgrade. I'm currently rooted with xposed framework and would miss not being able to turn my phone into a hotspot so hopefully that's possible by now too. What exactly do I need to do?

If you are on N12 you can get to 5.0 rooted. There are many threads on this. Have a search around!
I used a method by Jkruse, and now can even use safestrap without ODIN.
Sent from my SM-G900V using XDA Free mobile app

ridenickel9 said:
If you are on N12 you can get to 5.0 rooted. There are many threads on this. Have a search around!
I used a method by Jkruse, and now can even use safestrap without ODIN.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Is there a dedicated thread for the Jkruze method? I see him referenced here but I don't see anything about his method so far.

I used this as I was already rooted on N12. At the bottom of the first post here:
http://forum.xda-developers.com/showthread.php?p=62333947
If you are not rooted you likely want to start here:
http://forum.xda-developers.com/showthread.php?p=53447240
Warning/disclaimer: read everything before attempting anything to your phone....multiple times. These links / help may ruin your phone. Be careful

Ok, I get the process now after reading but I don't know how to SafeSTrap on NI2 if I'm already rooted. The instructions aren't clear on that, the title says you'll be able to use SafeStrap without ODIN but if I'm already rooted on KK then it just tells me to boot into safestrap...
Do I need to install SS? Do I need to disable xposed if/when I install it?

Ok I'm in SS now and I'm not sure if I should flash over the stock ROM or use a ROM slot. Thoughts? I already made a backup of the entire system and these phones have useless internal memory so I wanted to save space by wiping/installing over the stock ROM. Are there drawbacks to that?

If your rooted, you should have safestrap installed. When you boot your phone do you get a screen that pops up after the S5 screen?
It would show a image and have 2 buttons. One option would be recovery.

I didn't have it but I do now. My main question is about the slots, should I overwrite the stock one or install along side? Don't really have the storage to keep the stock slot but also don't know if doing that will do something irreplaceable.

Since you can load a stock 5.0 rooted ROM I'd do the stock slot... however, that's your call. Make sure you follow instructions to get right kernel and such.
Will you ever need 4.4.4 again ? Even so, long as you don't update the bootloader and can see it in Odin you can always rebuild.
Remember, once your on 5.0 with the newer kernel you can only get to safestrap by flashing the n12 kernel. U can do it by using odin, or lollipop safestrap application if applicable.
Sent from my SM-G900V using XDA Free mobile app

berfles said:
I didn't have it but I do now. My main question is about the slots, should I overwrite the stock one or install along side? Don't really have the storage to keep the stock slot but also don't know if doing that will do something irreplaceable.
Click to expand...
Click to collapse
I don't think the slots were ever working before the dev quit working on it.

Ok cool, that's what I wound up doing anyway and already had to test my backup to see that it worked (it does). Thanks for the help, I'm now on 5.0 and still rooted. Maybe my next step will be xposed, but the only thing I really used on that was the tethering and it already seems to work in this ROM.

Awesome! Glad to hear all is well.
Sent from my SM-G900V using XDA Free mobile app