yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] -Lawless:
No I read it and understood that it meant that if you upgraded to OC1 BL it would no longer work.

I guess I was also confused by the very first line in the OP that states "**You can begin the following process from any Build/ROM but you must already have Root Access. Safestrap Users must flash from "Stock" Slot Only**"

See I had the first version without wifi and thought that now I could flash the new updated version via SS.

Anyway, it appears that SS isn't going to work at this point.

I have everything working now via Flashfire and maybe soon SS will work again.

Thanks.
[Verizon Samsung Galaxy S 4] techguy2002:
So your saying that pit file will actually work for a successful downgrade?
[Verizon Samsung Galaxy S 4] rslu2:
I couldn't get the downgrade to stick. Failed 3 times. Used the full wipe pit file and the nc5 downgrade stuck with Nc5 bootloader. Ymmv.
[Verizon Samsung Galaxy S 4] meazz1:
is the USB cable known good one?
[Verizon Samsung Galaxy S 4] rslu2:
A good USB cable is critical. Even if the cable charges the phone, it isn't necessarily good for odin
[Verizon Samsung Galaxy S 4] npjohnson:
The old KitKat logo? What are you talking about, the boot animation?

No matter what bootloader you are on to begin with, when you flash this (In FlashFire, or SafeStrap,, you will have OC1 everything, except your Bootloader, which will be NK4. It doesn't matter if you are on ME7, MI1, MJ7, MK2, NC2, NC5, NK1, NK4, or even MDK (though, god forbid you would flash this if you were on MDK, as you would lose your LOKI exploit & the ability to use a custom kernel. If you are on MDK, use the version of this ROM intended for MDK in the Development Section of this very forum.)

The only exception to this, of course is if you have the OC1 Bootloader (only way you would have this is to have taken the OTA), in which case, you cannot flash this for two reasons; you cannot have root, another being that the NK4 bootloader would fail to flash.

You are not unable to downgrade! ODIN would throw a different error than that which you received. "REMOVED" means just that, the PC/ODIN lost the connection to the phone, on a bad USB port/bad cable, it often fails at the flashing of System.img.ext4 (as it is the largest of the partitions).

You need to try a different PC, and a different USB cable. Some people may tell you to re-download the TAR, and, although that couldn't hurt to try, ODIN seems to like the MD5 sum that the TAR provides to self-check it's integrity, telling me that your TAR is just fine. Another tip off to that, is that many of your partitions flash successfully, it just fails when it starts flashing the system partition.

You need to stop saying that you cannot downgrade, when in fact you can! Nothing is different about the NK4 bootloader that you have, then the NK4 bootloader I have.
[Verizon Samsung Galaxy S 4] toyosup88:
So I'm still having trouble using most root apps. Any busybox app install will cause the phone to crash and reboot. Now when to use adaway it crashed the phone as well... What is causing this?
[Verizon Samsung Galaxy S 4] SellswordShev:
Anyone else having trouble with smart lock? It works about 30% of the time for me, tried with multiple different bluetooth devices and the screen locks pretty frequently even while I'm using the device (like bluetooth speakers).
[Verizon Samsung Galaxy S 4] techguy2002:
Got the phone back down to NC5 Finally!

Tried a different computer obviously different USB ports. My issue is resolved. Thanks for the good work on this Muniz going to retry it in a bit to get upgraded. Sorry if I came off like a jerk.
[Verizon Samsung Galaxy S 4] 06sharpshot:
I could very well be wrong but it may just be an issue with 5.0. I know xposed had a lot of issues with the new runtime so that may apply to other root apps.

Edit: I'd also really like to give a big thanks to [MENTION=4708661]muniz_ri[/MENTION] and all the other devs that continue to pour tons of work into these devices. It's awesome to still have such an active dev community on a device that is a few years old now.
[Verizon Samsung Galaxy S 4] EM EN:
hmmmmmm
[Verizon Samsung Galaxy S 4] vermont03:
can't thank you enough, it worked perfectly. starting to wish i didn't wipe my phone before i tried a different cable. lesson learned.
[Verizon Samsung Galaxy S 4] JeeperDon:
Anyone else notice that the lock screen 'how much time do I have to swipe' is not the same all the time, often really short, goes back to black in 2 seconds at times?
[Verizon Samsung Galaxy S 4] Likkleskip:
Yesss it happens all the time with me
[Verizon Samsung Galaxy S 4] carzaddict:
ssssoooo.....i did the update, i followed the steps like I was supposed to do. I was on NC5 when I started (rooted).

Now my phone is frozen on the samsung boot screen. its been about 7 minutes now. What can i do?

just an FYI....i had safestrap recovery but the app itself was not installed. could this have caused a problem?

update: I tried flashing NK1 Recovery file (and not the bootloader) in ODIN and now I am stuck in a bootloop. It keeps going into Android Recovery..... Dammit....what should i do now?

update #2 - I used the neutered OC1 file and thankfully it saved my phone! its working fine now! although im pretty sure i lost root, time to figure out how to get it back
[Verizon Samsung Galaxy S 4] ATGkompressor:
I am as well trying to pinpoint what's causing it. But I think that "Smart Stay" has something to do with it.

Turning Smart Stay on will keep the screen on if ur looking at it, off if not. So if your not aware that it is on (which I think it is by default?), it will seem random.
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
just did the update, followed the steps and it works beautifully. i have no issues yet. lollipop makes touchwiz not look that bad :) is xposed lollipop working here?
[Verizon Samsung Galaxy S 4] zakkxx:
Exact same thing happened to me. Strange how some phones work no problem, and some don't.
[Verizon Samsung Galaxy S 4] rp1226:
No xposed yet due to changes in how Samsung implemented and changed ART.
[Verizon Samsung Galaxy S 4] xprobert:
Help.

How do i fix the Wifi ?

I turn it on, all it goes back to off.

Is that why my tether does not work too?
[Verizon Samsung Galaxy S 4] JeeperDon:
Thats exactly it, sort of scary actually. If the phone's is square to my face, directly facing me, the lock screen stays on a long time, apparently so I can read all the stuff presented. If not 'facing' me, it dies in a couple seconds. Now that I know how it works, I'll leave it.

Another lockscreen 'issue'... why oh why can't you double tap (or any action actually) a lock screen widget to bring up that app? It works that way on my Nexus 9 running 5.0.1.
[Verizon Samsung Galaxy S 4] Osama Chishty:
anyone getting this?

Should I update this or not I keep getting it...
[Verizon Samsung Galaxy S 4] rp1226:
I think its because the lockscreen is not AOSP. It is touchwiz... Some features are different.
[Verizon Samsung Galaxy S 4] dgutierrez04:
You must have the old rom he uploaded. Muniz_ri already fix the problem in the new rom. Go to the OP and download the rom again and flash it. Ur wifi should start working again.

---------- Post added at 07:25 AM ---------- Previous post was at 07:15 AM ----------

Well I updated it. And nothing happen I still have root. Lol.
[Verizon Samsung Galaxy S 4] -Lawless:
totally normal.
[Verizon Samsung Galaxy S 4] xprobert:
Now it is stuck on the Verizon logo.
[Verizon Samsung Galaxy S 4] MarkusMcNugen:
Same thing happened to me. I ended up doing a full wipe Odin restore to NC5. Rooted and made sure not to install safestrap. Then tried again and got to the boot animation then looped. Should have just restored back to NC5 when it didn't work and waited for a lollipop root ;) That's what I did.
[Verizon Samsung Galaxy S 4] dgutierrez04:
Did u used flashfire to flash the rom?
[Verizon Samsung Galaxy S 4] klabit87:
I never allow the security policies to update.

Anything related to a security update is bound to have adverse affects on any customization we may want to do.
[Verizon Samsung Galaxy S 4] Zelmo88:
Finally got around to flashing OC1. Process in the OP worked flawlessly. I was on NK1 rooted with no safestrap. Wireless tether seems to be working also, without flashing the fix. Great work muniz_ri and all involved! I may just keep my S4 a little longer!
[Verizon Samsung Galaxy S 4] carzaddict:
So I think at the state that I am in (unrooted neutered OC1)....I have the option of going back to NC5, rooting and then flashing OC1 again, or I can wait for a lollipop root.

I will wait a week or 2 incase a root method comes out, if not I will do the NC5 route again.
[Verizon Samsung Galaxy S 4] xprobert:
Yes i did,

Tried again now it is stuck on the samsung galaxy s4 screen
[Verizon Samsung Galaxy S 4] techguy2002:
This method works!!!!
[Verizon Samsung Galaxy S 4] dgutierrez04:
http://xdaforums.com/galaxy-s4-verizon/general/i545vrugoc1neuteredfullodin-tar-t3098956 used that method to get ur phone back and running. Than downgrade to NC5 to get root again than do the lollipop update again
[Verizon Samsung Galaxy S 4] Eddie Hicks:
Thanks a million for this ROM. A couple of weeks ago I flashed stock ROM without root in anticipation of getting Lollipop OTA. Once I was able to upgrade to Lollipop I noticed this thread. I was surprised to see that there was root for Lollipop already. The hardest part for me was getting root back on my phone. After flashing NC5 and running Towelroot I went into a boot loop. Using ADB reboot download I was able to flash NK1 and finally Lollipop. I already have Lollipop rooted on my Galaxy tab S and it's great having it rooted on both devices now. I was thinking about getting a S6 but with Lollipop it's like getting a new phone and I'll probably keep it another year.
[Verizon Samsung Galaxy S 4] 06sharpshot:
I was running Eclipse rom on the stock slot of safestrap on NC5 and I attempted this and got stuck on the "Galaxy S4" boot screen. I am using ODIN to restore NC5 and will not install safestrap in hopes that that fixes it. I'll update this post if it works this time around.

Edit: It worked. Anyone getting stuck on the Galaxy S4 screen on boot should restore NC5 and try it from stock.
[Verizon Samsung Galaxy S 4] gildan27:
I was coming from rooted MK2 and this did not work for me. FlashFire ran fine, the screen went black, and then it booted the standard Android Recovery. I selected Reboot and it took me back to the OS. I unrooted and tried to take the update to NC5, but it wouldn't install.

I ended up using ODIN to flash NC5, then tried the update to OC1 here again and it worked.

Also of note is that the "Enable su during boot" option appears to require the Pro version of SuperSU.

Thank you very much!
[Verizon Samsung Galaxy S 4] zero75:
Um... misquoted my bad.

Seeing WiFi issues after deep sleep with and without framework changes on one device atm. The usual disable/enable fixes it. The other 2 seem fine still.

Just making note. When I can get the device in question, I'll try and track it down.
[Verizon Samsung Galaxy S 4] i8qbert:
I noticed the "close all" button in the task switcher seems to have stopped working. Anyone else having this issue? I am fairly certain it worked for a few days. Everything else is working fine.

Edit..seems to be a Nova Launcher issue. Thanks!
[Verizon Samsung Galaxy S 4] techguy2002:
Noticed another issue with writing to the SD card not being possible. I downloaded sdfix from the play store and ran it and rebooted issue is resolved.
[Verizon Samsung Galaxy S 4] skiinginbend:
All good here

Works great all installed and updated tonight, no bugs found so far. Thanks so much for you hard work. :good: :good:
[Verizon Samsung Galaxy S 4] KKShiz:
I was a fool. I recently had a hardware issue with my S4 and was fortunately under the 1 year manufacturer warranty. I received my replacement S4 the day lollipop was available. I checked for updates and continued to update until it stated I was up to date. I know better than to receive OTA updates. No idea what I was thinking. Oh well, them's the breaks.
[Verizon Samsung Galaxy S 4] bangdosa:
So I'm on NK1 build at the moment rooted using the downgrade to NC5/towelroot method. I don't have safestrap installed in my phone atm. I did get flashfire as required by the original post. currently downloading I545_OC1_Stock_Rooted_ROM_wNK4_BL zip file.

I had a couple questions before going through with the update to OC1 this way.

1. WIll this wipe my phone (internal storage or apps+data)? Should I backup things I want before updating using titanium backup?

2. I went through to about the first 15 pages of the post, it seems that there was an error for Wifi for the initial version that was fixed. Is there no problems with wifi now?

3. will going to OC1 via this allow me to go back to NK1 if there are any problems?

4. what is I545_OC1_TetherAddOn used for? There was some mention of it on the forums but didn't really understand it is it something that's needed for mobile hotspot?

Sorry if these are noobish questions, I don't use root often, but still like to have it in order to backup my apps and stuff, so I don't know it very well. Plus being a bio student don't help with understanding all the stuff that makes up Android OS.
[Verizon Samsung Galaxy S 4] ahmed.zubair:
Gesture Sensor ?

I checked out the gesture sensor but its not working . Any fix or suggestion to calibrate in lolipop ?? :confused:
[Verizon Samsung Galaxy S 4] Zelmo88:
We were all noobies once!

1. Yes, using the instructions in the OP will wipe apps and data. It will not wipe internal storage, just be careful NOT to check that box in the wipe section. I would recommend backing up your apps and data before upgrading......always!!!

2. Wifi works great for me! I believe the developer fixed this in the most recent OC1 download file.

3. Yes, you should be able to go back to NK1 if you want after using this process. This process keeps the NK1 bootloader.

4. The Tether Add-on enables the mobile hotspot, however, my mobile hotspot worked after flashing the new OC1, so I didn't need to flash the Tether AddOn. I think the developer may have included it in the most recent OC1 download file.

Be sure to follow the instructions carefully, missing a step will definitely cause problems!

Good luck!
[Verizon Samsung Galaxy S 4] sportytony:
That is basically how my phone was except I had changed my boot screen and with exposed and wan am changed a couple of things. I always back up with titanium anyway. I put everything back as close to stock rooted before I took the plunge. Then followed exactly as op and it is AWESOME! adding the ether will allow you to hotspot your phone without the Big Reds warnings. Also works like a charm. Bear in mind you should have unlimited data for tethering. no issues whatsoever! (for me) also some of your original apps might not be restorable as they are not yet compatible with lollipop, they are still kit kat only.
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
So im still working great but i just noticed a minor issue. whenever you hold home and it goes to recent apps, if you press close all it sort of freezes and goes to a random app
[Verizon Samsung Galaxy S 4] bangdosa:
Alrighty! thanks for your response! I'll get to it after I finish backing up my apps then, hopefully without any mistakes during the update.

Ok, so some apps are possibly incompatible with lolipop since the app developer may not have updated it to lolipop. I was wondering about what you mean by having unlimited data to tether . I use mobile hotspot occasionally when I want to use my tablet to view something in a no free wifi spot or on the highway. Does the tether add on give more functionality to this? if you could explain the difference between tether and hotspot, that would be great.
[Verizon Samsung Galaxy S 4] sinner822:
Can't go directly from MK2 to OC1. Although you could have upgraded to NC5 while keeping your MK2 bootloader. Then bump up to 5.0.1.
[Verizon Samsung Galaxy S 4] gildan27:
As mentioned in my post, I unrooted and attempted to take the OTA update to NC5 and it did not work. Likely this would work for other people in that situation, though.
[Verizon Samsung Galaxy S 4] ATGkompressor:
Tether and hotspot are essentially one in the same. Whereas tethering is accomplished via Bluetooth and hotspot is done wirelessly. But they both do the same thing which is broadcast your mobile data signal. As long as you're not gaming or doing other data intrusive actions, you'll be ok without unlimited data.
[Verizon Samsung Galaxy S 4] i8qbert:
Are you using a third party launcher (nova, apex etc)? I noticed when using nova launcher and pressing close, I would be taken back the stock launcher. A press of the home button brought nova back. Kinda of annoying but tolerable.
[Verizon Samsung Galaxy S 4] JeeperDon:
Don't press 'Close All', it's about the only bug in this whole thing. I get odd behavior on Google Now launcher. :D
[Verizon Samsung Galaxy S 4] Camp As A Champ:
God bless you man, worked like a charm. I factory reset before however, but I did that as my NK1 ROM was getting buggy.
[Verizon Samsung Galaxy S 4] seadooman:
Noob?. Does this work on the locked bootloader Verizon sch-i545?
[Verizon Samsung Galaxy S 4] blazin_phattys:
Bootloader Questions

First off, let me begin by saying thank you for your work on this ROM. I've been hesitant to take the OTA because I refuse to lose root now and possibly forever.

Before I flash the rom using your app, I'd like to know a few things...

1. As far as I can understand, the NK4 boot loader is a 4.4 bootloader, so does that take away from the performance and functionality of the ROM vs 5.0 on a 5.0 bootloader.

2. If I flash this rom, I have to downgrade to the NC5 bootloader, use Towelroot, and reflash the NK4 bootloader, correct? If so, where can I find the files for the NC5 bootloader and NK4 bootloader?

Sorry if these questions have been answered already. I skimmed the thread, but I don't think these were addressed specifically.
[Verizon Samsung Galaxy S 4] dgutierrez04:
Yes. The bootloader has always been lock except for the MDK bootloader. But if u proceed I recommend to used flashfire. Follow the OP. Everything should work fine on the rom. Just follow steps carefully.
[Verizon Samsung Galaxy S 4] mitafoaj:
...

Just wanted to say thank you for your work. I had issues at first, but following everyone's instructions got me back on track. Thank you all for all the great support [MENTION=4708661]muniz_ri[/MENTION]
[Verizon Samsung Galaxy S 4] ejohn3288:
If I currently have mdk bootloader, and follow these steps, will I lose mdk bootloader and root?
[Verizon Samsung Galaxy S 4] sinner822:
You will lose MDK!

There is another thread for MDK
[Verizon Samsung Galaxy S 4] dgutierrez04:
Yes u will lose MDK. follow this thread for u.

http://xdaforums.com/galaxy-s4-verizon/development/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
[Verizon Samsung Galaxy S 4] bangdosa:
following up on my previous posts, I got it to update to OC1 sucessfully =). Currently restoring data and stuff. I was wondering if anyone knows if lollipop also needs to do a sd card patch like kit kat. I think I remember reading that lollipop restored some sdcard privileges that kitkat took away, but not sure.
[Verizon Samsung Galaxy S 4] newkydawg:
Yeah, Lollipop restored some privileges but I still had an issue so I ran a Play Store app called SDFix https://play.google.com/store/apps/d...=nextapp.sdfix and it fixed my SD Card write problem. App says it's for KitKat but it works on Lollipop.
[Verizon Samsung Galaxy S 4] rp1226:
Same. I had to download an SD card fix from the play store.
[Verizon Samsung Galaxy S 4] seadooman:
OTA 5.0.1

I didn't mention that I had originally took the OTA of 5.0.1 which may change things. I have heard if you screw up "like I did" and take an OTA that's it no going back? True or False?
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
Ya i just happen to be running Nova
[Verizon Samsung Galaxy S 4] rbird2:
SDCard Fix also worked for me with Lollipop.
[Verizon Samsung Galaxy S 4] seadooman:
Okay I found the answer, oops not reading enough. But still confused on which file I need to flash. I allowed the OTA of 5.0.1 and I am not rooted. this sentence has me confused which file do I need?

5. If you do not already have root access flash the Full Wipe NC5 Odin .tar (Caution!: do not flash if you took the OC1 ota update), root with Towelroot, then proceed with the above process.

Or

I545_OC1_Stock_Rooted_ROM_wNK4_BL

Thanks in advance for your help. Made the mistake of taking an OTA when I shouldn't have.
[Verizon Samsung Galaxy S 4] dgutierrez04:
Well I hate to say it but ur screw. There's no going back for now. Until there's a way to find root for lollipop. So don't try to root it if not u will boot loop ur device.
[Verizon Samsung Galaxy S 4] seadooman:
So once there's root for 5.0.1 then this would work?
[Verizon Samsung Galaxy S 4] dgutierrez04:
Once they find root for lollipop it would used a different method to root it. But until now ur stuck wit no root.
[Verizon Samsung Galaxy S 4] woodardhsd:
Just flashed this using FlashFire. How long should the black Samsung screen with the padlock stay on? My phone has been hung up there for 10 minutes.
[Verizon Samsung Galaxy S 4] sinner822:
Add to platform.xml for card fix

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_r" />

<group gid="sdcard_rw" />

<group gid="media_rw" />

</permission>
[Verizon Samsung Galaxy S 4] dgutierrez04:
If ur device hasn't boot up yet. Flash this tar. Than get root again and attempt again to flash lollipop.

http://xdaforums.com/galaxy-s4-verizon/general/i545vrugoc1neuteredfullodin-tar-t3098956
[Verizon Samsung Galaxy S 4] woodardhsd:
This is clearly not working for my phone. The first time I tried, the phone rebooted and got hung on the black Samsung screen with the padlock.

I did a clean install using the instructions here: http://xdaforums.com/showthread.php?t=2735172 I did the full wipe method. Phone started up fine. Used towelroot and confirmed root with rootchecker. Installed supersu from the playstore. I updated the supersu binaries and told it to disable knox. It hung there while trying to disable know, so I restarted the phone, and tried to disable knox again. It was successful in disabling knox almost immediately. I also enabled su at boot.

I downloaded flashfire, copied the zip file to the phone, followed all the flashfire instructions exactly. The phone rebooted again, but this time got stuck on the Samsung Galaxy S4 screen. I just odin'd back to NC5 again. Think I'll stay there for a little while longer.
[Verizon Samsung Galaxy S 4] bretrick30:
Once upgraded, is it possible to go back to NC5?
[Verizon Samsung Galaxy S 4] muniz_ri:
Guys, please read the OP including the Notes section. Most common questions are answered there.
[Verizon Samsung Galaxy S 4] npjohnson:
You are likely ordering the steps wrong in flshfire, wipe needs to be at the top! If wipe is on the bottom, it will hang at the Samsung screen!
[Verizon Samsung Galaxy S 4] sinner822:
Guarantee that is 99% of all Flashfire problems.
[Verizon Samsung Galaxy S 4] muniz_ri:
That is exactly what I suspected so late last night I removed the wipe instructions from the OP and uploaded a new ROM which will automatically perform an FDR during the flash. So far its been downloaded almost 100 times with only one reported failure.

Not much more that can be done to avoid User error.