Ok so here is my situation. I took the OTA to NB1(4.4.2) then I downgraded back to MK2 so I could have root access. Then I reinstalled NB1 stock rom. Now I have root access with stock 4.4.2 on my i337 GS4. Now what I'm trying to do is install clockwork mod recovery or TWRP or any other recovery other than safestrap but I'm not able too or cannot find a way. Has any one had this issue I'm new to this and I am trying to run google edition Roms or customer roms. Also with safestrap(3.71) some roms are enabled but once phone reboots it stay on black screen. Any help or advice is appreciated thank you.:silly:
marvelAVENGER said:
Ok so here is my situation. I took the OTA to NB1(4.4.2) then I downgraded back to MK2 so I could have root access. Then I reinstalled NB1 stock rom. Now I have root access with stock 4.4.2 on my i337 GS4. Now what I'm trying to do is install clockwork mod recovery or TWRP or any other recovery other than safestrap but I'm not able too or cannot find a way. Has any one had this issue I'm new to this and I am trying to run google edition Roms or customer roms. Also with safestrap(3.71) some roms are enabled but once phone reboots it stay on black screen. Any help or advice is appreciated thank you.:silly:
Click to expand...
Click to collapse
You cant install any other recovery besides ss, since our bootloader is locked. You also have not been able to run google edition roms since mf3. You can now only run touchwiz roms.
Kamaole said:
You cant install any other recovery besides ss, since our bootloader is locked. You also have not been able to run google edition roms since mf3. You can now only run touchwiz roms.
Click to expand...
Click to collapse
Got it so if I get my boot loader unlocked I'll be able to run other recoveries and roms?
marvelAVENGER said:
Got it so if I get my boot loader unlocked I'll be able to run other recoveries and roms?
Click to expand...
Click to collapse
At this time you cannot unlock your bootloader. As far as I know, @Hashcode is still trying to get Kexec working with safestrap using jeboo's bypasslkm exploit to load unsigned modules. If he gets that working, we will be able to basically put any kernel we want over the stock kernel. I think ran into trouble with flushing the cache.
Kamaole said:
At this time you cannot unlock your bootloader. As far as I know, @Hashcode is still trying to get Kexec working with safestrap using jeboo's bypasslkm exploit to load unsigned modules. If he gets that working, we will be able to basically put any kernel we want over the stock kernel. I think ran into trouble with flushing the cache.
Click to expand...
Click to collapse
I'll keep an eye out for that thanks.
Q&A for [CM12] [Lollerpop] JFLTEATT Nightly Kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM12] [Lollerpop] JFLTEATT Nightly Kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
noremac258 said:
No love for the jfltecan?
Click to expand...
Click to collapse
Yea I tried even using the jflteatt philz to trick it but the data part failed and system was success. So I didn't bother trying to boot. You can still use Antares however, it is unified.
I am wondering if I can flash Antares and then dirty flash this over to get the system part, I just don't wanna have to go through Odin to stock rigamarole.
cm-12-20141124.1217-jflteatt
Can't get it to boot on my AT&T S4. It tries, black screens, then reboots into AD recovery automatically.
I'm unlocked using T-mobile, but I don't think that should matter.
TWRP v2.7.1.0-- Using stock slot with safestrap disabled (no success on making new slots with safestrap enabled, either).
Lollerpop CM12 - AT&T Samsung Galaxy S4 (SGH-i337) - Unauthorized
Hi,
I tried replying to the CM12 Lollerpop thread but even though I have been utilizing XDA for YEARS, I am still considered a noob due to lack of posts.
Anyway, I just wanted to let the awesome developers know that I tried installing CM12 Lollerpop through TWRP, on my AT&T Samsung Galaxy S4 (SGH-i337) that I have installed ROMs on hundreds of times. For some strange reason that I cannot explain, with the Beta version of CM12 right after I power on the device after installing I see an ! and "AT&T UNAUTHORIZED SOFTWARE HAS BEEN DETECTED" and device went to a black screen after 5 -> 10 seconds. Fortunately I was still able to get back into TWRP after a reboot and home + volume up and successfully completed a restore from a 4.4.4 Beanstalk complete backup I took prior to testing CM12 installation / boot, etc.
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
jkvincent said:
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Click to expand...
Click to collapse
It sounds like you did not flash a Loki-Doki package. Search the AT&T Galaxy S4 forum and you can find it. You need to flash this after you flash your ROM (or anything else) to trick your phone into thinking you have stock software. Some ROMS have this included, which is probably why you have never had to flash this package before, but I would say that most don't. And no, even if the ROM has a Loki package included inside of it, it doesn't hurt to flash it twice so I end up flashing Loki-Doki a lot.
Sent from my GT-I9505G using XDA Free mobile app. Press "Thanks" if I helped!
Unauthorized - Loki & Safestrap
Hi,
I downloaded loki-doki.zip, wiped, installed CM12*.zip, gapps-lp*.zip and applied loki-doki.zip to find the annoying "Unauthorized..." message again. I tried installing loki by itself after a clean reboot. I tried with wiping dalvik + cache and without. Same thing.
After reading up on Loki, I ran into a bit that stated Loki is designed for 4.4.2 and for 4.4.4+ I should be using Safestrap. I downloaded the Safestrap*.apk file, installed it, granted root access and installed Recovery (says Safestrap is built off TWRP).
The first thing I noticed was the TWRP version was still 2.8.1 (I also updated TWRP prior). I went through the same process without Loki. Same "Unauthorized..." message. Tried Loki after. Same message.
I am not sure at this point but I have never had much luck installing Recoveries while being booted into Android. I have always had to install from a .zip in Recovery or use Odin. I'm not convinced Safestrap updated or even if it is the right way to go. What would be really sweet is if the Devs could wrap whatever is needed to get around the "Unauthorized...", into the CM12 installation. Maybe that is asking for too much. I need to still research Safestrap and it is getting late. I do appreciate you pointing out Loki because it got me pointed in the right direction. I kind of forgot about it with the ROMs being Lok'd.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
For those who are on AT&T, this is how I got 11-30 to work. Worked perfectly, except the battery drain.
Install cm12 using TWRP (shouldn't matter, but I used 2.8.0.1), flash gapps if you want, flash ktoonsez aosp 5.0 kernel just updated few days ago. No loki patch needed. Good luck.
Didn't get a chance to test bluetooth, but camera seemed to work.
I am using a AT&T s4 (no safestrap)
Hi, Try installing a kernel. it work for me. Alicard or ktoonz.
Question here
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
StoneyJSG said:
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
thesummoner101 said:
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
Click to expand...
Click to collapse
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
StoneyJSG said:
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
Click to expand...
Click to collapse
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
thesummoner101 said:
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
Click to expand...
Click to collapse
Awesome! Thanks dude. Since I am partial to CWM, I was going to flash PhilZ touch recovery, but from what I have read the ShabbyPenguin recovery is supposed auto loki upon flashing. I also have the loki-doki.zip file for flashing as well just in case.
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
ahmedbatty said:
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
Click to expand...
Click to collapse
How you installed custom recovery in S4 i337 at & t?
Jordan Gonzalez said:
How you installed custom recovery in S4 i337 at & t?
Click to expand...
Click to collapse
I found out that I can't flash any custom ROM or recovery if I have the latest bootloader, so it's locked
Hello all! I am newly signed up but i have been lurking in here for quite a while now. I am like that I usually try not to post and just figure out what I need to do by research and trial and error! But lately I think i may have too much research. I have spent the last week looking up and trying to figure out what I need to do to get what I want lol.
I have a Verizon SM-G900V which has been rooted with towel root, using the flash back to NCG method. I have installed SuperSU, Flashfire, and, BusyBox.
I want to upgrade my OS to the newest version,(5.1 Lollipop I believe?) while retaining root and allowing me to wi-fi tether. What I am not sure about is how to go about this properly. I was about to install Safestrap but I am not sure it is compatible with my build which somehow magically changed to NE when I looked at my About Phone in Settings. I am actually not even sure I need Safestrap either because I have read many conflicting tutorials and info in the past week of research. I am totally new to Safestrap and have never used a custom rom before. I have however rooted my S5 and gotten it to tether fine but then I made sure never to OTA update. Recently was forced to factory restore because if what I assume where Touchwiz problems(The problems have been gone since I reset) and now I would like to see if I can upgrade my OS .
Any help would be awesome and some points in the right direction much appreciated.
SafeStrap is a little inconvenient to use in Lollipop, but it's a great safety net to keep in place. It allows you to take a snapshot of your system and restore it later. If you lack this safety net and something goes wrong with your OS, you have no choice but to start from scratch.
All you have to do to use SafeStrap with Lollipop: flash a KitKat kernel (you can do this with the NL1 flasher app) from the phone while it's running Lollipop, reboot into SafeStrap, and do what you have to do. You then must re-flash a "safestrap-flashable" Lollipop kernel from within SafeStrap before you leave it, or your operating system won't be able to boot.
As for upgrading, see this thread and links within it: http://forum.xda-developers.com/verizon-galaxy-s5/help/help-upgrading-rooted-nk7-verizon-s5-t3302438
Your firmware version is different but it's still KitKat, so all of the same advice applies.
So I would definitely have to flash back to NCG in order to install safestrap right? because I am NE right now
Mrephunk said:
So I would definitely have to flash back to NCG in order to install safestrap right? because I am NE right now
Click to expand...
Click to collapse
Have you try this? you will have root on the latest factory firmware and able to install Safestrap.
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
buhohitr said:
Have you try this? you will have root on the latest factory firmware and able to install Safestrap.
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
I just want to be clear. I should go through all the steps listed in that thread to achieve what I want? Even tho I am on a 4.4.2 build and not a 5.0?
Mrephunk said:
I just want to be clear. I should go through all the steps listed in that thread to achieve what I want? Even tho I am on a 4.4.2 build and not a 5.0?
Click to expand...
Click to collapse
That would work, as it involves flashing a BOK3 factory image and then rooting it.
You could do that, or you could just do the "keep root" method, which I had linked to in the thread I sent you to for explanation. http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
painiac said:
That would work, as it involves flashing a BOK3 factory image and then rooting it.
You could do that, or you could just do the "keep root" method, which I had linked to in the thread I sent you to for explanation. http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
Click to expand...
Click to collapse
So the method you are linking above would be the better route to go, correct? Because the other method would update my bootloader to BOK3 which wont let me downgrade to NCG if I want to easy root again, right?
Sorry for all the questions here I just wanna make sure I get it right.
Mrephunk said:
So the method you are linking above would be the better route to go, correct? Because the other method would update my bootloader to BOK3 which wont let me downgrade to NCG if I want to easy root again, right?
Sorry for all the questions here I just wanna make sure I get it right.
Click to expand...
Click to collapse
Both root methods will work for you. The advantage of the "Keep Root" method I linked to is that you would still be able to downgrade later. As long as you don't flash anything with a BOE or newer bootloader, you can downgrade. So BOD is safe, BOE1, BOG5, and BOK3 can not be downgraded.
painiac said:
Both root methods will work for you. The advantage of the "Keep Root" method I linked to is that you would still be able to downgrade later. As long as you don't flash anything with a BOE or newer bootloader, you can downgrade. So BOD is safe, BOE1, BOG5, and BOK3 can not be downgraded.
Click to expand...
Click to collapse
OK so I am gonna go with your linked method. I dont wanna get stuck with one of those bootloaders. I should still be able to use safestrap with your method right? And tho I have never done it before I was entertaining the idea of flashing a custom ROM. That should still be possible with your method, correct?
Mrephunk said:
OK so I am gonna go with your linked method. I dont wanna get stuck with one of those bootloaders. I should still be able to use safestrap with your method right? And tho I have never done it before I was entertaining the idea of flashing a custom ROM. That should still be possible with your method, correct?
Click to expand...
Click to collapse
You can use SafeStrap with either method. But when you're on Lollipop, you must flash a kitkat kernel to boot into safestrap, then you must re-flash your lollipop kernel BEFORE leaving SafeStrap or you won't be able to boot into Lollipop. It's not as complicated as it sounds.
painiac said:
You can use SafeStrap with either method. But when you're on Lollipop, you must flash a kitkat kernel to boot into safestrap, then you must re-flash your lollipop kernel BEFORE leaving SafeStrap or you won't be able to boot into Lollipop. It's not as complicated as it sounds.
Click to expand...
Click to collapse
Yea I know, all of this sounds complicated but I understand it lol. But would I still be able to use a custom ROM using your method, I dont see why I couldnt, I just want to make sure I am ok?
Mrephunk said:
Yea I know, all of this sounds complicated but I understand it lol. But would I still be able to use a custom ROM using your method, I dont see why I couldnt, I just want to make sure I am ok?
Click to expand...
Click to collapse
Yes. You can use any TouchWiz-based ROM, all of which can be found in the "Verizon Galaxy S 5 Android Development" section of the forum, and no other section.
ROMs can be flashed using SafeStrap or with Flashfire.
painiac said:
Yes. You can use any TouchWiz-based ROM, all of which can be found in the "Verizon Galaxy S 5 Android Development" section of the forum, and no other section.
ROMs can be flashed using SafeStrap or with Flashfire.
Click to expand...
Click to collapse
Im just barely familiar with SafeStrap, and have never ever used FlashFire. Which of the 2 would you say is better to use?
I also wanted to thank you for all this help and answering my constant questions. Thank you very much!
Mrephunk said:
Im just barely familiar with SafeStrap, and have never ever used FlashFire. Which of the 2 would you say is better to use?
Click to expand...
Click to collapse
I have a slight preference for SafeStrap because I am accustomed to using custom recovery environments on previous phones (ClockworkMod Recovery, and later TWRP). SafeStrap is a modified TWRP environment, customized to work within the limitations imposed by the Verizon S5's locked bootloader.
FlashFire can do nearly everything that SafeStrap can do, the difference being is that it functions like an app. It's also more convenient to flash zips if you're on lollipop, because you don't have to **** around with flashing different kernels to boot into it, you just open the app, select the zip, and flash it. The downside to this is that if your OS is completely screwed up and won't boot, you can't access FlashFire.
But if that happens and you have SafeStrap recovery environment installed, you can flash a kitkat kernel with Odin and boot into SafeStrap to restore your nandroid backup, then flash a lollipop kernel and boot into your now-working phone.
For those reasons, I find it advantageous to use both.
---------- Post added at 08:18 AM ---------- Previous post was at 08:18 AM ----------
Mrephunk said:
I also wanted to thank you for all this help and answering my constant questions. Thank you very much!
Click to expand...
Click to collapse
You're quite welcome
painiac said:
I have a slight preference for SafeStrap because I am accustomed to using custom recovery environments on previous phones (ClockworkMod Recovery, and later TWRP). SafeStrap is a modified TWRP environment, customized to work within the limitations imposed by the Verizon S5's locked bootloader.
FlashFire can do nearly everything that SafeStrap can do, the difference being is that it functions like an app. It's also more convenient to flash zips if you're on lollipop, because you don't have to **** around with flashing different kernels to boot into it, you just open the app, select the zip, and flash it. The downside to this is that if your OS is completely screwed up and won't boot, you can't access FlashFire.
But if that happens and you have SafeStrap recovery environment installed, you can flash a kitkat kernel with Odin and boot into SafeStrap to restore your nandroid backup, then flash a lollipop kernel and boot into your now-working phone.
For those reasons, I find it advantageous to use both.
---------- Post added at 08:18 AM ---------- Previous post was at 08:18 AM ----------
You're quite welcome
Click to expand...
Click to collapse
OK so both it is lol. I see in the link to the thread which has the keep root tutorial it has 2 extra files a tether file and a batch de-bloater. I understand what the tether is but what exactly is the de-bloater? Also how do I install them, cause I definitely want the tether? Also, I noticed that my phone has some gone to a NE9 kitkat build, I would have to reflash to NCG, reroot and then install safestrap correct?
Mrephunk said:
OK so both it is lol. I see in the link to the thread which has the keep root tutorial it has 2 extra files a tether file and a batch de-bloater. I understand what the tether is but what exactly is the de-bloater? Also how do I install them, cause I definitely want the tether? Also, I noticed that my phone has some gone to a NE9 kitkat build, I would have to reflash to NCG, reroot and then install safestrap correct?
Click to expand...
Click to collapse
The de-bloater is just a script that deletes unnecessary apps that came pre-installed on the phone. You use it by flashing the debloater zip in either SafeStrap or FlashFire. Personally, I prefer to use Titanium Backup to "freeze" the unwanted apps, because they can be easily reactivated if necessary. Once those apps are deleted by the debloater, you can't retrieve them. Probably everything in the script needs to die anyway, but if you actually like any of the extra stuff that came on your phone you'll want to avoid using that method.
The tether patch is installed the same way, by flashing it, but you only need it if you're staying with the stock OS. If you're installing a custom ROM, don't bother because they will have already implemented it.
If your phone says NE9 but it is rooted, don't worry about it. You'd only need to flash the NCG kernel if you have to use towelroot to regain root access. So just install SafeStrap and/or FlashFire.
Then do a nandroid backup in SafeStrap of your current setup. That way, if something goes catastrophically wrong with your Lollipop upgrade adventure you can, with a little work, get back to where you are now with all of your apps and settings intact.
Then flash the rooted Lollipop image in the "Keep Root" method thread.
painiac said:
The de-bloater is just a script that deletes unnecessary apps that came pre-installed on the phone. You use it by flashing the debloater zip in either SafeStrap or FlashFire. Personally, I prefer to use Titanium Backup to "freeze" the unwanted apps, because they can be easily reactivated if necessary. Once those apps are deleted by the debloater, you can't retrieve them. Probably everything in the script needs to die anyway, but if you actually like any of the extra stuff that came on your phone you'll want to avoid using that method.
The tether patch is installed the same way, by flashing it, but you only need it if you're staying with the stock OS. If you're installing a custom ROM, don't bother because they will have already implemented it.
If your phone says NE9 but it is rooted, don't worry about it. You'd only need to flash the NCG kernel if you have to use towelroot to regain root access. So just install SafeStrap and/or FlashFire.
Then do a nandroid backup in SafeStrap of your current setup. That way, if something goes catastrophically wrong with your Lollipop upgrade adventure you can, with a little work, get back to where you are now with all of your apps and settings intact.
Then flash the rooted Lollipop image in the "Keep Root" method thread.
Click to expand...
Click to collapse
Cool, awesome thank you. So if I am running lollipop, I would have to use Odin to flash a kitkat kernel if I wanted to access to safestrap, right? It would need to be a rooted kernel too, right? Also was wondering if you could point me in the direction of the proper kernels I need. I have seen so many different NCG and other build kernels I am not sure which I should DL.
Mrephunk said:
Cool, awesome thank you. So if I am running lollipop, I would have to use Odin to flash a kitkat kernel if I wanted to access to safestrap, right? It would need to be a rooted kernel too, right? Also was wondering if you could point me in the direction of the proper kernels I need. I have seen so many different NCG and other build kernels I am not sure which I should DL.
Click to expand...
Click to collapse
Yes, flash a KitKat kernel to get into SafeStrap from Lollipop. I don't think it matters which version.
NCG, NE9, NHA, NI2, and NK2 are all KitKat.
OA8, OC4, OD5, OE1, OG5, and OK3 are all Lollipop.
You can use the NI2flasher.apk (but I've seen reports that it doesn't always work), or you can flash it with Odin (which is a little less convenient, but does work well). You should keep an NCG kernel around for re-rooting in case you have to start over, and that one should work for booting into SafeStrap.
Flashing any "kernel only" file won't change your root status. Basically, the kernel is the layer that allows the hardware and the operating system (firmware and such) to communicate with each other. Root access lies entirely within the configuration of the operating system: flashing a kernel will not affect it, but flashing a different firmware will overwrite it.
KERNELS themselves are always safe to flash, but if the operating system can't use it that kernel it will simply get stuck early in the boot sequence. This is always reversible by flashing the proper kernel.
However, be very cautious about FIRMWARE zips, unless they specifically say they're safe for newer bootloaders. Firmware files also contain bootloaders, and flashing the wrong newer (BOE and up) bootloader will burn your bridge back to BOD5 and below, and if you're already on BOE or newer then flashing an older bootloader over it will brick your phone. Stick with jrkruse's "firmware only no bootloaders" files. Currently, his "BOK3 firmware with BOD5 bootloader" is the latest safe version: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527. So, to be clear: Flashing an OE1 or newer bootloader trips a qfuse that makes it impossible to downgrade the bootloader.
For the KitKat kernels, the ones posted here work fine: http://forum.xda-developers.com/showthread.php?t=2784880
For the Lollipop kernels, stick with jrkruse's updated ones that he has in the second post of this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I've found with previous phones that it is advantageous to download and keep such files as soon as I find them, because experience has taught me that they're typically only posted in one place and they tend to disappear as the posters later lose interest in that model.
painiac said:
Yes, flash a KitKat kernel to get into SafeStrap from Lollipop. I don't think it matters which version.
NCG, NE9, NHA, NI2, and NK2 are all KitKat.
OA8, OC4, OD5, OE1, OG5, and OK3 are all Lollipop.
You can use the NI2flasher.apk (but I've seen reports that it doesn't always work), or you can flash it with Odin (which is a little less convenient, but does work well). You should keep an NCG kernel around for re-rooting in case you have to start over, and that one should work for booting into SafeStrap.
Flashing any "kernel only" file won't change your root status. Basically, the kernel is the layer that allows the hardware and the operating system (firmware and such) to communicate with each other. Root access lies entirely within the configuration of the operating system: flashing a kernel will not affect it, but flashing a different firmware will overwrite it.
KERNELS themselves are always safe to flash, but if the operating system can't use it that kernel it will simply get stuck early in the boot sequence. This is always reversible by flashing the proper kernel.
However, be very cautious about FIRMWARE zips, unless they specifically say they're safe for newer bootloaders. Firmware files also contain bootloaders, and flashing the wrong newer (BOE and up) bootloader will burn your bridge back to BOD5 and below, and if you're already on BOE or newer then flashing an older bootloader over it will brick your phone. Stick with jrkruse's "firmware only no bootloaders" files. Currently, his "BOK3 firmware with BOD5 bootloader" is the latest safe version: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527. So, to be clear: Flashing an OE1 or newer bootloader trips a qfuse that makes it impossible to downgrade the bootloader.
For the KitKat kernels, the ones posted here work fine: http://forum.xda-developers.com/showthread.php?t=2784880
For the Lollipop kernels, stick with jrkruse's updated ones that he has in the second post of this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I've found with previous phones that it is advantageous to download and keep such files as soon as I find them, because experience has taught me that they're typically only posted in one place and they tend to disappear as the posters later lose interest in that model.
Click to expand...
Click to collapse
OK rooted phone all went well. Installed Tether patch and now when I connect to wifi it doesnt work. I get a DNS error message in my browser and play store wont work, basically nothing will work when I am connected to wifi. Any thoughts on what to do? Was thinking maybe of going to jkruse's custom rom but not sure if that will help. If I do go to that rom will I need to go back to Kitkat or can I just use a flashfire and flash as is?
Update: The DNS error I seem to have fixed, but my question still stands for the jkruse's ROM. Also is it better to use a custom ROM? I have never really used one, so I am curious.
Ohh and you have been so much help painiac I really appreciate you answering all my questions. I was really at a standstill for a while there. You are truly a helpful person and I thank you.