yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] otakudeter:
i used odin to flash the downgrade version of oc1 that was included in the bottom of this post. got the kingroot to work, but i have no google apps. not even the play store to continue on in the process of "use Super-Sume Pro to replace Kingroot files with SuperSu"

so now i have no clue how to proceed.
[Verizon Samsung Galaxy S 4] bangdosa:
so you didnt have root before OC1? and what do you mean by botton of this post? you mean Muniz's I545_Downgrade_to_OC1.tar?
[Verizon Samsung Galaxy S 4] otakudeter:
i had root on OC1 before i used flashfire to flash the OF1 version here. thats when i couldn't get past the samsung logo. I have now used odin to flash the I545_Downgrade_to_OC1.tar. the kingroot worked with it, but i'm noticing that i have no google apps so i can't get supersu swapped in to try the flashfire again.
[Verizon Samsung Galaxy S 4] bangdosa:
so at the very least, you can boot, and should have root?

first make sure the OF1 file you have has the correct md5 using the download link and a md5 file checker.

I'll upload a copy of flashfire apk for you to install. you shouldnt have to change to super su, since all it needs is root access, but if you want to, you can follow directions here to remove kingroot for supersu.
[Verizon Samsung Galaxy S 4] otakudeter:
i can't follow those directions without the google play store.
[Verizon Samsung Galaxy S 4] bangdosa:
do you not have a computer and a cable? you can download the files via the computer an transfer them to the phone via a cable or micro sd

here's flashfire apk

you can download terminal emulator from here
[Verizon Samsung Galaxy S 4] ymDroid:
Any issues if I'm rooted on NK1 with the NK1 bootloader.

I see that this package doesn't flash a new bootloader.

Will this OF1 update work with the NK1 bootloader currently on the phone?
[Verizon Samsung Galaxy S 4] bangdosa:
Im sure there was no bootloader change from NC5 until OC1 came out. network signal info in the app store tells you what bootloader you're on.
[Verizon Samsung Galaxy S 4] ymDroid:
It updated. No Issues.

Going to restore all.

The SAMSUNG Info app says I'm on the NK1 bootloader.

PDA version OF1/OF1e

Baseband Version OF1

CSC version OF1

Does lollipop require me to modify my Read/Write permission to use my SDCard with TiBu like the old builds of KIt Kat?
[Verizon Samsung Galaxy S 4] bangdosa:
yep you need to do a sd card fix like kitkat,
[Verizon Samsung Galaxy S 4] ymDroid:
Thank you [MENTION=5668704]bangdosa[/MENTION]..

TIbu is updating my apps.

Need FF24 to reinstall so I can flash the Tether app.

By the way, i used Flash Fire 24 with no issues so far.
[Verizon Samsung Galaxy S 4] ymDroid:
So everything is back up and I flashed the OF1 Tether app via FF24.

I've been installed my apps and restoring items, and every so often I reboot just to keep things fresh.

I just rebooted a few mins ago and the phone froze at the Verizon RED splash screen,. After about 3-5 mins I got a prompt that said " system processes not responding" WAIT or OK. Either choice reboots the phone and it does the same thing.

So i pulled the battery after three times and gave the phone a few mins. After replacing the battery, it booted correctly. The odd thing is that after the battery pull, the Samsung splash screen was the normal official screen, not the CUSTOM lock screen.

The only other thing beside setting up apps was that I froze all the KNOX stuff and SDM.apk.

Any ideas what caused this?

I just installed AD BLOCKER and rebooted and it booted fine with the CUSTOM Samsung screen.

This odd. Hope it's not a recurring issue.
[Verizon Samsung Galaxy S 4] bangdosa:
No idea, might just be from massive installation. probably nothing to worry about. I might wipe cache and devlek though. sometimes when I have weird restart offical samsung screen comes on too.
[Verizon Samsung Galaxy S 4] ymDroid:
Thank you. You've been an amazing help!

What version of Xposed is everyone using one this ROM? I flashed the Deoxed.

I assume that no one is using Safestrap no with this, now that there's Flash Fire? We we just using the the stock recovery for cache wipes? Or does FF have a function?

Thanks again!
[Verizon Samsung Galaxy S 4] bangdosa:
there is a wipe option in flashfire. cache and dalvik.

I don't know much about how its programmed and stuff unfortunately.
[Verizon Samsung Galaxy S 4] ymDroid:
[MENTION=4236380]zero75[/MENTION] Anything special that needs to be done to flash xposed on FF24?

Do you have link to to the Xposed apk/zip you used? I checked the Xposed thread and there seems to a ton on different things going on there.

Thanks in advance.
[Verizon Samsung Galaxy S 4] seadooman:
Order of flashfire?

Another site says to change the default order of flashfire to this? Arrange actions on the main screen of FlashFire App to the following order, rearrange it by tapping and holding the actions:

1st ⇒ Wipe.

2nd⇒ Flash ZIP or OTA Finally Press.

Question do I accept the defaults or adjust the order. Mine comes up with the opposite by default 1st. Flash zip or ota. 2nd. Wipe? Which is correct?
[Verizon Samsung Galaxy S 4] ymDroid:
I don't see how it would matter if FF wipes you phone first then flashes the rom, or if it flashes the rom then wipes.

I would think by wiping last, if the rom flash failed, your original rom would still be intact.

If you wiped first and it failed, then you stuck with a new setup.

All I know is that the default setting worked perfectly for me.
[Verizon Samsung Galaxy S 4] zero75:
Sorry for the delay...

I use [MENTION=4898097]arter97[/MENTION] v6 snapdragon 71 framework with 3.0 alpha 4 apk.

I can provide links when I get to my office.
[Verizon Samsung Galaxy S 4] seadooman:
NC5 straight to OF1

I noticed no one on this forum says anything about changing the order, didn't know if it was a given or not. Think there would be a problem going straight from NC5 to OF1?
[Verizon Samsung Galaxy S 4] ymDroid:
Thereally were not any changes to the bootloader since NC5 or NK1 for that matter, Which I was on. So no, there should be no issues..

Actually, as I understand it, you can go from any build that as long as you currently rooted. Which is anything but OF1 OTA.

If you took the OF1 OTA and are now running the OF1 bootloader and have also lost root, your pretty much screwed.
[Verizon Samsung Galaxy S 4] seadooman:
No still on NC5.
[Verizon Samsung Galaxy S 4] ymDroid:
Are you rooted on NC5?

If so, you should be fine.
[Verizon Samsung Galaxy S 4] seadooman:
Yes, rooted, NC5 boot loader.
[Verizon Samsung Galaxy S 4] ymDroid:
I know this long, hopefully someone knows the answer.

I know this long, hopefully someone knows the answer.

So in term of battery life, the phone was excellent today. 14 hours and I still had 20% left when I got home. Normal usage was snappy throughout the day. There were zero glitches. Used my hotspot, my Jay Bird X Bluetooth head phones, and my Moto 360.

No issues.

The I got home, and as soon as I turned my WiFi back on an ld my Bluetooth off, the phone rebooted. After the first reboot, the phone powered up and turn off. I had to push the power on button. I continued to do this as it kept turning on and turning off again.

My battery was at 15-16% by now., so I plugged the phone in and for some reason, it turned on and stayed on. Each time it power cycled, it came up with the Standard Galaxy S4 boot screen.

So I have a dual band router, but I never used the phone in 5ghz because for some reason, it doesn't work further than 10 feet from the router. The S4 would never automatically connect to 5ghz. It always goes to the 2.4ghz band first.

I noticed that, even though I was a good 40 feet from the router, it had connected to my 5ghz band. Which would have never happened on KitKat.

Considering that this power cycle started as soon as I turned off Bluetooth and turned on the WiFi, I wonder of there's a glitch here with 5.0.1 and the wifi.

I wonder if any of these issues are being caused by being on the NK1 (a KitKat bootloader ) on a Lollipop Rom.

Should I have flashed a Lollipop bootloader with this install? Or does it not matter?

HaS anyone experienced anything like this?

Any help would be greatly appreciated!
[Verizon Samsung Galaxy S 4] SAFWAN TARIQ:
Help required

I HAVE GALAXY S4 I545 WITH 4.4.2 NK1 FIRMWARE i downloaded of1 update from sammobile.com and not instlling it because i m afraid it may lock network i m in pakistan please confirm it lock network or not please
[Verizon Samsung Galaxy S 4] bangdosa:
I doubt it locking you out, but just in case, use muniz' OF1 rom with flashfire if you want to update with the ability to go back down.

You should have NC5 emergency stock by Surge from here to use via ODIN if needed to go back down as well as backing up your apps and data via titanium or through flashfire.

Muniz's stock OF1 roms will clear your data so backup either way.
[Verizon Samsung Galaxy S 4] zero75:
Have you checked your baseband version?

Its possible the bl version is causing an issue, unlikely though as the issue would be more widespread. iirc you had a wifi issue before? Check the file your flashing maybe.

How did it work before you flashed the tether zip?
[Verizon Samsung Galaxy S 4] ymDroid:
Baseband is also OF1.

Really, the only thing that's different is the bootloader. But do I really want to flash a Lollipop bootloader. The only rootable one is OC1?
[Verizon Samsung Galaxy S 4] zero75:
Currently, yes. Given the age of the device, may be the last.

If you decide to go that route you should change your backup strategy in flashfire to "backup all partitions" to recover easily from most issues. If not, kingroot is the only method and then some extra steps to get a clean rom.
[Verizon Samsung Galaxy S 4] ymDroid:
Thanks [MENTION=4236380]zero75[/MENTION]. I don't know if I want to mess with kingroot.

I deleted the 5ghz AP. And when I can home today, I didn't have any issues.

I also kept the wifi and Bluetooth on the whole time, so I didn't have to turn any of the toggles on/off when I came home.

Don't know which of those causedays the original issue, but I'm hoping that this is resolved.

I mean....am I ok to be on the NK1 bootloader with OF1 everything else?
[Verizon Samsung Galaxy S 4] seadooman:
Noob question number 2. When you guys say back up in ff, what are you backing up specifically? Data? or more than that?
[Verizon Samsung Galaxy S 4] seadooman:
.24 FF

Do you need to change dates with the latest version of flashfire?
[Verizon Samsung Galaxy S 4] ymDroid:
Nope.

Works out of the box. No modifications.
[Verizon Samsung Galaxy S 4] Destati:
Registered just to say this. I tried doing the downgrade mentioned in the OP but it failed and soft bricked my phone. No worries, I just installed the official of1 firmware update through odin and got back to where I was. I went full circle, but its recoverable.
[Verizon Samsung Galaxy S 4] mitafoaj:
Kudos

I followed your advice. This worked for me. I did however, end up pulling the battery after about 30 minutes of being stuck on the Verizon logo. Placed battery back in and all is working. Thank you.

foaj
[Verizon Samsung Galaxy S 4] pkopalek:
I don't know if OP wants to update here, but it looks like going from MK2 to OC1/OF1 is a mistake, and you need to go a step up first if you're trying to use FF

http://xdaforums.com/showpost.php?p=60939906&postcount=2

NOw I have to figure out how to get from MK2, and what steps to take before going to OF1. What a crazy mess! Even though I have an unlocked bootloader anyway.
[Verizon Samsung Galaxy S 4] sinner822:
Why would you use Flashfire with your BL?
[Verizon Samsung Galaxy S 4] pkopalek:
Every ROM and tutorial I've found since 2014 seems to only involve FF or SafeStrap.

So I'm really just using whatever methods I can find threads with specific instructions on. Since I don't read anything about unlocked bootladers on any modern threads, I've just been trying to do what needs to be done to get to 5.0.1 even if it's really inefficient.

I followed this: https://www.youtube.com/watch?v=AIRoQKTLeJQ which is from the thread from 2014 about going from MK2 to NC5, and it worked perfectly. Time to go NC5 to OF1!

Now, after doing the OF1 move, as in the OP, following the directions closely, I have the exact same issue this fella has:

I downgraded to OC1 via the OC1 TAR file in the OP. Phone boots up great, and runs on OC1. Kingroot, replace with SuperSU, FlashFire with the directions in this OP..... same issue. Black screen, pulsing blue light. I booted back into recovery and did a wipe data/factory reset (just in case). Once, I got a VZW logo (I waited 20mins on it). Every other time, a black screen with blue pulsating light.

Chalk this up to the another S4 that simply does not seem to 'like' the OF1 update posted in the OP.

Not sure what else to do. But I Odin'd back to OC1, then rooted with kingroot (and sub supersu), then just flashed the OC1 Tether Fix in the [HowTo] Keeproot OC1 thread with FlashFire. Works great. Tether. OC1. Renamed the update samsung thing. Works great. Guess we're using OC1!
[Verizon Samsung Galaxy S 4] blueman189:
Hi all!

FANTASTIC work muniz_ri and chainfire!

Used Flashfire to go from 4.4.2 rooted to OC1 rooted (didn't know OF1 was out) and then to OF1.

*edit*

No one posted what happens AFTER you flash the tether zip with Flashfire. What can I expect? Will it go smoothly on Deodexed?

I'm having two small issues: The close all button doesn't really work... When I press it it freezes and then I have to press the home button to get out of it. Then, when checking recents again, I see that 'phone' is open... but the phone (dialer) app doesn't really fully load either.. I've seen that many people solve issues by clearing various caches from recovery mode. Which caches are safe to clear without wiping any data?

I DID check MD5 before flashing.

The second issue I am having comes up somewhat randomly. I get a notification that says: "Unfortunately, the process android.process.acore has stopped." What does this mean?

Misc. Q.: I used Titanium backup to uninstall some unecessary apps (NFL and Trip Advisor) but their shortcuts still showed in the app drawer and I had to go disable them from the Application Manager.

Thanks!

-blueman189
[Verizon Samsung Galaxy S 4] Cannonball_CO:
OK, so I just had exactly the same problem you both have had - I was at NC5 trying to go to OF1. No go. But after I soft bricked, I didn't downgrade using the OC1 tar file, instead I used this:

http://xdaforums.com/galaxy-s4-verizon/development/odin-5-0-1-lollipop-oc1-t3174850

Then I used Kingroot, replaced with SuperSU, FlashFire with the directions in this OP... and I'm in the setup wizard right now for OF1.

Looks like the main diff - if the two OC1 downgrade tar.md5 files were similar - is that I repartitioned using this:

http://xdaforums.com/showthread.php?t=2290859

Not sure if this is the fix or not, but it's working here.
[Verizon Samsung Galaxy S 4] Joe_6pak:
Any hope of getting this for unlocked MDK bootloader?
[Verizon Samsung Galaxy S 4] pkopalek:
Thank you.

I'm not sure if you linked to it on purpose or not, but that's a TAR file for a Galaxy S 4. Is the link correct?

But I noticed that there are OC 1 tars that are 1.5GB, and then the one that I used was 2.4GB (even though androifilehost says 2.0GB). I think the 1.5 GB version is the 'neutered' version (and I'm not sure what that means or if it makes a difference). Maybe that would have helped.

I have the phone running on OC1, and already got it going and working. I might tackle this another time. Many thanks to the OP, of course, either way. The phone would be on 4.3 without this thread.
[Verizon Samsung Galaxy S 4] Cannonball_CO:
Yeah, the first link is to a GS4 ROM. What the difference between it and the one in the OP, donno, perhaps more partitions included (it is bigger). So yes, technically two differences in my approach - a possibly more complete OC1 install, and a repartition.

Honestly once I got the OC1 install done I was temped to stop, but I figured, I haven't done this in a while, plus *fingers crossed* OF1 might last a while, so I went for it. I totally understand why you would not!

Agreed, much thanks to the OP!!!
[Verizon Samsung Galaxy S 4] MaxPower742:
DEBUGGING

It seems the key to getting Kingroot Desktop to start is enabling debugging mode in developer options. Sure wish someone had told me that, instead of simply stating "Yeah just use kingroot desktop". Then the instructions are in chinese and the pictures don't correlate because they're from an older version of android.
[Verizon Samsung Galaxy S 4] MaxPower742:
kingroot doesn't work

The kingroot desktop version fails with red chinese letters around the only word I can understand, "root". I assume it's saying something like, "We couldn't root after all". Any suggestions on how to improve my chances?

I've tried the oc1 downgrade followed by a factory reset, and I've tried the oc1 full wipe that was previously suggested in this thread.
[Verizon Samsung Galaxy S 4] oka1:
From the Moderator

To in this thread POST ON TOPIC , POST RESPECTFULLY..... or..... DO NOT POST......... Easy

Do not ........ get into personal diatribe.

When writing please post with complete and cogent sentences. Writing poorly increases misinterpretation.

If you are looking to try and root, there are a number of ways to find this info. Try doing a Boolean search in Google.......... you will find a variety of methods to explore ...

e.g. http://www.droidviews.com/install-lollipop-on-verizon-galaxy-s4-and-keep-root/

Also, there is a Kingroot that does come in English, though I am not sure if the S4 version does, I would think so ......

Be kind when posting ... be civil ..... Thanks ~~~ oka1
[Verizon Samsung Galaxy S 4] zaobuv:
This is giving me such a headache. I was on rooted OC1 and used this tutorial to upgrade to stock rooted OF1, but it soft bricked. So I used the OC1 downgrade .tar and have tried rooting with kingroot probably 20 times, with no luck.

This is my problem as well. Really hoping there's another way because I can't live without root
[Verizon Samsung Galaxy S 4] seadooman:
Same here.got a used s4 with oc1 and have tried kingroot stand alone and desktop versions with no luck. Used on 2 different desktops as well. I give up.
[Verizon Samsung Galaxy S 4] pkopalek:
Kingroot (3.0 I used) was very frustrating to get it to work properly.

First of all, USB Debugging was a must (click Build Number in about phone > software info to turn on developer options in the Settings). Also, in Developer options, I turned on 'Stay awake' (Screen will never timeout while charging). Why? Because during the Kingroot process, a pop-up will happen on your phone and ask if you want Google to periodically check out your phone for odd software. You must push DECLINE whenever this pops up. It WILL happen during the Kingroot process.

Second, I believe I already had LG Drivers on my computer (I may have installed it from here: http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html but I'm not sure exactly, it's been a while).

Third, I figured to launch Kingroot (on my computer), THEN click the button on Kingroot (no idea what it said), then plug my phone into the USB port on the computer. Once, I had to change (on the phone) the 'Connected as Installer' to 'Connected as Media Device (MTP)' or Camera (I forget which) and wait several seconds. Once I did, I was in better shape.

Fourth, once Kingroot recognizes the phone (after goofing around with it for a while, like I did -- including unplugging and plugging in the phone several times, and restarting Kingroot several times), I pushed the 'Root' button (does it say 'root' on it? I forget). Then waited, again.

So for Kingroot, it was pushing the button, waiting for Kingroot to recognize the phone, then pushing that button in the center again ("root"?), and waiting for it to go through its process.

Then, I googled around for 'replace kinguser with supersu' script. ALSO, I had to go in manually to Manage Applications to get rid of 'KR Something' (I forget the exact name) that KingRoot had installed on my phone. The script didn't get rid of that.

Warning: Kingroot has been reported to cause people to have their Facebook (and other accounts) hacked, shortly following using Kingroot. I don't trust it, and although I'm thankful that it's there, I immediately saw to replace it with SuperSU. No issues at this point. OC1.
[Verizon Samsung Galaxy S 4] MaxPower742:
OK are you saying that in addition to Kingroot Desktop, we should have the Kingroot app installed on the phone? And you start it on the phone, THEN plug it into the PC (with the Kingroot Desktop software already opened)?
[Verizon Samsung Galaxy S 4] jkennebeck:
looking for this exact solution. I'm stuck on OF1 non rooted of course (used odin and flashed the wrong damned OS, wanted to flash OC1 but downloaded the top file). so if theres a way to go BACK to OC1, then root I'd be eternally grateful for any help

---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------

Were you on OC1 rooted or non rooted?

I'm non rooted on OF1 right now. Sounds like your process might solve my issue.

disregard... saw you said you used flashfire. which means you're rooted. I'm not. still F-ed
[Verizon Samsung Galaxy S 4] jkennebeck:
tried flashing the tar from above. odin fails at the system part.
[Verizon Samsung Galaxy S 4] jkennebeck:
started this process

step 1 went fine. Odin got the green on installing the OC1 kernel

step 2 still working on, can't seem to get kingroot desktop figured out. debugging checked, tried getting it to work as installer, media device and camera (MTP and PTP). can't seem to get it to get to the root screen. i've never used kingroot before and don't have a grasp of chinese so i'm just pushing buttons like the monkey in sputnik.

i'll report back if i have any luck.

ok. eventually i think i got it to recognize the phone but i got a big red x with a circle around it. so no luck.

any other ideas?

checked, not rooted.

---------- Post added at 02:33 PM ---------- Previous post was at 02:10 PM ----------

this fails on me.

did you start with a ROOTED phone?

mine is not. im non rooted OF1. not from ota but sammobile via odin.

and thankfully i can reflash that but i wanted to get back to oc1 for root.
[Verizon Samsung Galaxy S 4] Cannonball_CO:
I started with a rooted GS4 @ VRUFNC5. Tried to take it straight to OF1 and it bombed. Brought it back to stock OC1 as described above (Odin), rooted it with PC Kingroot, then used the OP's method to take it to rooted OF1. It's running great.

IIRC if you are at OF1, non-rooted, then you may be screwed. You can't take it back to OC1, and Kingroot doesn't work on OF1. Sorry... I hope I'm wrong.

---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------

THIS.

Turn on "Stay Awake". I did not have the same difficulty as pkopalek (pop ups?), but my phone wanted to sleep (to save battery) after what 15 or 30 seconds and every time it did this Kingroot barfed. The screen needs to stay on the WHOLE TIME Kingroot is doing its thing.
[Verizon Samsung Galaxy S 4] tlamance:
Had a problem, figured it out. Don't mind me..
[Verizon Samsung Galaxy S 4] BoulderGeek:
Eek, I started on a rooted 4.3 early Kit Kat, running stock rooted (wither muniz_ri or gigilie/googolie).

I screwed up and flashed Stock OC1 Neutered in odin, as the FlashFire flashable rooted version that I installed black screened on boot and never completed.

Now, towelroot, Kingroot apk and Kingroot desktop all fail to gain my root back.

Since i can't even run Titanium Backup, i don't know if the Verizon OTA Updater will try to upgrade this ROM to OF1.

Recommendations?
[Verizon Samsung Galaxy S 4] techguy2002:
I would Odin back to OC1. But before you do what do you see when you turn the phone on while pressing the volume up key?