yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] dgutierrez04:
That website is exactly what muriz has on his OP. they just went into more detail wit pictures. But I'm glad it work for u. Remember Bootloader NK4 you can downgrade. Anything higher than NK4 bootloader you can't downgrade. But I'm glad it work for u :)
[Verizon Samsung Galaxy S 4] carzaddict:
how can I check my bootloader version?
[Verizon Samsung Galaxy S 4] dgutierrez04:
Download this app from the playstore.

Check out "Phone INFO ★Samsung★"

https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
[Verizon Samsung Galaxy S 4] BoulderGeek:
Finally working great

For some reason, i was one of the 1%, twice.

On the third attempt, I was able to flash the OC1 _NK4 package and have it clear the verizon red screen of death.

Everything is great, except that even after twice flashing the OC1 tether enabler zip in FlashFire, I still get the VZW subscription check when i enable mobile hotspot. It had been working flawlessly in NC5.

Any script or config file editing I can do in vi to make hotspot work?

Thanks very much to muniz_ri. Sorry if I sounded frustrated before. My fault for hacking on it away from odin.
[Verizon Samsung Galaxy S 4] mikeandamy1013:
volume issues?

I posted that flashing via op went well, my issue is with volume. I see that it's an issue with lollipop. I was wondering if anyone has the issue and or a fix. I tried rebooting, tried sliding the volumes down and up again but still my in call volume is so low and my ringtones/notifications are very low.
[Verizon Samsung Galaxy S 4] muniz_ri:
Glad it's working and I uploaded a new Tether file yesterday. Try and redownload.
[Verizon Samsung Galaxy S 4] BoulderGeek:
Muniz_ri: Perfect!

You're my personal hero. My own personal Jesus.

Worked great as soon as I flashed it. Whatever the change was, it was important.

Thanks so much! All of my Lollipop dreams fulfilled.
[Verizon Samsung Galaxy S 4] VidMasterEon:
I might as well add in my experience in that upon using flashfire i got a screen saying there is software unauthorized by verizon on the phone instructing to turn off and take to the store. I was able to odin it back to NC5 and am currently trying again
[Verizon Samsung Galaxy S 4] lath19:
I was also a member of 1% club. ODIN back to NC5 and tried again, this time with success. Thanks OP.
[Verizon Samsung Galaxy S 4] muniz_ri:
No worries. Also, too late for you but I believe that I finally have resolved the issue affecting the "1%." Will upload new ROM overnight.
[Verizon Samsung Galaxy S 4] tshelby73:
Those of us using the old ROM and tether that is working is their a need to update either.

Sent from S4 using the better than it was then they jacked it again Tapatalk
[Verizon Samsung Galaxy S 4] Osama Chishty:
how about 5.0.2

there is any difference between 5.0.1 or 5.0.2? my friend have sony experia z series he got update few days ago and his android version is 5.0.2. ao there is any more updates samsung planning to pull out :confused:
[Verizon Samsung Galaxy S 4] BoulderGeek:
My Samsung Galaxy Tab Pro 10.1 has been on 5.1.1 for weeks. It just depends what sources have been tuned and prepared for each platform. With the locked bootloaders and mystery features of Verizon, developers have a different set of code to work with than unlocked devices present.
[Verizon Samsung Galaxy S 4] muniz_ri:
Nope.
[Verizon Samsung Galaxy S 4] ChadXDA:
Rom working fine just everytime I reboot it says: "Android is upgrading starting apps" is this normal?

Thanks,

Chad
[Verizon Samsung Galaxy S 4] muniz_ri:
No, sounds like the rom failed to wipe data or you restored incompatible data. A factory data reset should solve it.
[Verizon Samsung Galaxy S 4] moonglows:
I can confirm that the new uploaded file as of this morning flashes just fine. I didn't want to be the first confirmed test on the new file but I just couldn't wait any longer. Great job muniz_ri! Will keep you posted if any future issues :good:
[Verizon Samsung Galaxy S 4] ATGkompressor:
I've been running this build for a few weeks (well, since it came out) and it has been the most stable, fastest, and functional Rom I've ever ran. I've only had one force close (YouTube) which I believe was just a fluke because I've had nothing else before/since to crash. Tether works flawlessly without flashing the add-on. Bluetooth, mobile data and Wi-Fi are very stable and it doesn't skip a beat when auto switching between Wi-Fi and mobile data. Battery life is surprisingly good given the fact that many are reporting the opposite. This is the longest I've ever ran a fully stock ROM. Contrary to popular opinion, I think Samsung actually did an exceptional job on theming touchwiz-lollipop. I was definitely skeptical as to how all the bright colors in "lolliwiz" were going to impact battery life. Great job on this [MENTION=4708661]muniz_ri[/MENTION]!
[Verizon Samsung Galaxy S 4] The Grand Pooh-Bah:
All went well until the reboot. It stopped at the the Samsung splash screen and stopped. Had to pull battery. I then reloaded the original stock with full wipe via instruction at the bottom. This is the second go around of trying to get 5.0 with root without success.
[Verizon Samsung Galaxy S 4] meazz1:
I have been using this ever since it came out and have had no issue.

Thanks [MENTION=4708661]muniz_ri[/MENTION].
[Verizon Samsung Galaxy S 4] BoulderGeek:
Perhaps try a new download (from an alternate mirror?). I'm not sure what changed with mine. I went back and forth several times, borking it with FlashFire and then restoring with Odin.

Eventually it took it and made it through the Verizon splash.

Rinse and repeat.
[Verizon Samsung Galaxy S 4] muniz_ri:
I uploaded a new ROM yesterday morning that I hoped resolved the freeze upon reboot issue. I guess I was not successful.
[Verizon Samsung Galaxy S 4] brandonpa:
Using this method I was unsuccessful multiple times. My phone would just hang at the "Samsung Galaxy S4" screen and not do anything. So I ended up using Gogolie's method with this stock rooted rom and it loaded up fine. However, I am curious as I am having issues with the lock screen. The phone runs decently, however, I setup my lock screen with a pin and it sets up ok. But as soon as I reset it goes back to a swipe screen and I have to go back and set it up again to be a pin screen. Also does this rom allow for another equalizer and where would I find that setting in this rom to be able to change it? Thanks for everything and hopefully I can get this to work out. The Pin screen would be a deal breaker for me to stick with the older system until updates happen. But hopefully I won't have to as someone may have the answer.
[Verizon Samsung Galaxy S 4] muniz_ri:
When did you download the ROM? The lockscreen/pin issue usually happens when running new firmware on an old bootloader. If that is the case it can usually be resolved by editing build.prop as follows: security.mdpp=none to #security.mdpp=none
[Verizon Samsung Galaxy S 4] brandonpa:
Just downloaded it a couple of days ago and loaded it up today. I will try to edit the build.prop with that parameter then. Thanks a bunch for replying back.
[Verizon Samsung Galaxy S 4] smalco44:
I downloaded the zip anout 2 hours ago and flashed with the latest ff. I had root prior to the flash. I was stuck at the galaxy s4 screen for 15 min. I pulled the battery and got the same thing. Is there instructions to recover? Whatd i do wrong?
[Verizon Samsung Galaxy S 4] brandonpa:
Just checked the system build file and it is just like you mentioned to change it: #security.mdpp=none Do you have any other possible suggestions? Thanks.
[Verizon Samsung Galaxy S 4] Peiteman:
Thanks worked like a charm no problems at all.
[Verizon Samsung Galaxy S 4] muniz_ri:
Flash the NC5 .tar linked in the OP.
[Verizon Samsung Galaxy S 4] smalco44:
Just did that with full wipe and PIT. Did towel root, installed supersu and then started again from start of OP. Waiting on OC1 download. Anything I need to do differently from the steps above, or same as last time?

---------- Post added at 10:19 PM ---------- Previous post was at 09:51 PM ----------

went ahead and did the steps again and it appears to have worked. I think I'd recommend the ODIN flash w/ full wipe and PIT to everyone, first, before trying this method.
[Verizon Samsung Galaxy S 4] dgutierrez04:
Need help

I am on OC1 Bootloader. My brother accidentally rebooted into safestrap so now I am stuck in a bootloop. does anyone know how to get it to boot normal. Or get safestrap uninstall any help would be appreciated.
[Verizon Samsung Galaxy S 4] fxwrangler:
I'm having the same issue... Have u tried Factory Reset yet?
[Verizon Samsung Galaxy S 4] Failrunner:
Check this out!

[YOUTUBE]38IZchr098E[/YOUTUBE]
[Verizon Samsung Galaxy S 4] Redflea:
http://xdaforums.com/showthread.php?t=3109276
[Verizon Samsung Galaxy S 4] ChadXDA:
Yes but I just redownloaded the Rom today flashing it now, and will post how it behaves.

Chad

---------- Post added at 06:27 PM ---------- Previous post was at 05:58 PM ----------

I just reflashed the rom as before. My phone is stuck at the Samsung Custom unlock screen for over 20 mins. I pulled the battery and I'm stuck at this point. Anyone have an idea what I should do to get back going?

Chad
[Verizon Samsung Galaxy S 4] npjohnson:
Just an FYI. First ROM you ever uploaded worked for me with FF, and using the Wipe option, and then moving it to the top.

Messed it up trying to build an AOSP ROM for the stock kernel.

Re-downloaded the latest ROM (From Today, you may want to date the Stock-Rooted ROM's in the future :p), flashed clean NC5.tar through ODIN, re-rooted, DL'd SuperSU, Updated Binaries, Disabled KNOX (through SuperSU), Installed as System app, enabled SU During Boot.

Then Used FF to install the ROM. Seemed to work just dandy, went though all the steps and then said rebooting, then rebooted and hung at the Samsung screen indefinitely, multiple battery pull and reboots later, no dice. Thought it was a bad DL, so I red-downloaded, re-ODIN'd and followed all of the above steps, and tried again... 3 times. All resulted in indefinite hangs at the Samsung screen. So, I booted to recovery (Read out OC1, yay!) and wiped data and cache, then rebooted, still no dice.

I began to try to debug the issue. I looked in Download mode and it read out NK4, meaning that aboot flashed fine, and has a valid signature (meaning we can assume that the following partitions flashed successfully; aboot, sbl2, sbl3, tz,& rpm (we can assume all of these flashed and were successful/not corrupted because if they weren't present/valid, the device wouldn't boot to download mode, instead we would be greeted by the "FIRMWARE UPGRADE ERROR ENCOUNTERED::CONNECT TO KIES", this pops up if all partitions below aboot are intact, but aboot is screwed up, or QCOM DL Mode if SBL's/TZ/RPM is screwed up.

Next step in figuring this out, the next piece of the boot sequence, the kernel (boot.img), so I extracted the boot.img from the .zip and used tar & md5 to make an ODIN flashable TAR.MD5, then flashed it. Flash succeeded. Rebooted, no luck.

This makes me think that the error lies in the system.img.ext4 flashing method. I've wondered if the way that the newest FF update (0.18) changed how ext4 files are handled is what is causing these Samsung Screen hangs.

Next step for me is to use FF 0.15 (pre-ext4 patch), and try again from fresh NC5 (again). If that doesn't work though, I'm thinking that the ext4 has issues itself.

Just though I'd report my findings.
[Verizon Samsung Galaxy S 4] muniz_ri:
Here is a test for the system file....extract it from the ROM, place the raw .img onto your device and flash using FF's "Flash firmware" option and include the wipe.
[Verizon Samsung Galaxy S 4] npjohnson:
Assuming I will also have to flash the OC1 Kernel in ODIN. Will try to do so.

---------- Post added at 02:44 AM ---------- Previous post was at 02:42 AM ----------

Actually, a better way to test it may just be to reflash the old zip and see if it works.
[Verizon Samsung Galaxy S 4] muniz_ri:
Yes, you will need the new kernel. No, that assumes the issue is the .img. Could be FF's flash .zip or ota option.
[Verizon Samsung Galaxy S 4] npjohnson:
Think I figured it out, FF wipes Data, Cache,& SYSTEM. Which your wipedata.sh doesn't do... might be why.

EDIT: That isn't it. I was just able to flash the ROM dated APR-30 without wiping through FF, but wiping Data & Cache through Recovery.

---------- Post added at 02:54 AM ---------- Previous post was at 02:51 AM ----------

Ok. I'll reflash it from NC5, using FF's FW Update to flash the ext4, and then use ODIN to flash the OC1 kernel.

Just wanna help figure this out.

---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------

FF didn't like the ext4. It seemed to flash, but upon reboot (after flashing the OC1 kernel in DL Mode), it didn't boot.
[Verizon Samsung Galaxy S 4] muniz_ri:
No Vz boot screen? Just successfully flashed today's .img on my m919. Will wait to hear from others.
[Verizon Samsung Galaxy S 4] npjohnson:
No, it jumped to the Samsung Custom Padlock screen and hung there. I'll happily try again.

EDIT: ODIN'ing back to stock to try again. Also worth noting, when I used the new zip through FF, it retained the "Samsung Galaxy S4" bootscreen, meaning the custom flag wasn't set. But when I used the Old APR-30 zip, it came up with Samsung Custom, and booted successfully.
[Verizon Samsung Galaxy S 4] muniz_ri:
Could be a bad upload, idk. Will have better idea once others chime in.
[Verizon Samsung Galaxy S 4] muniz_ri:
Did you download the ROM to your PC or device? Once on your device did you copy/move it from one folder/storage to another?
[Verizon Samsung Galaxy S 4] PartyDroid:
Samsung Lock

ODIN'ing back to stock to try again. Also worth noting, when I used the new zip through FF, it retained the "Samsung Galaxy S4" bootscreen, meaning the custom flag wasn't set. But when I used the Old APR-30 zip, it came up with Samsung Custom, and booted successfully.

______________________________________________________________________________________________________________________

Mine and my wifes' phone has the same thing we did the FF v.17 and we get the lock and when I do the FF v.18 it hangs on the Big Red screen so I redid ours and loaded from the FF v.17 with the lock but working fine. I am looking forward in getting read of the Lock screen for good.

[MENTION=4708661]muniz_ri[/MENTION] I loves your work!!!!!!!
[Verizon Samsung Galaxy S 4] d_c_foster:
Success Times 2

Just updated both my wife's S4 and mine with absolutely no issues! Thanks for the hard work and dedication you provide us.
[Verizon Samsung Galaxy S 4] The Grand Pooh-Bah:
I ran the full wipe version again this morning, reloaded towelroot, SU and FF. Ran a freshly download copy from the phones download file. Again it hangs at the stock Samsung screen. Came back to town to download everything again. This time I'm saving all my downloads to my SD CARD.

When I get back home I'll try it once again, unless someone finds a solution in the meantime.
[Verizon Samsung Galaxy S 4] muniz_ri:
Try downloading to a pc then transer to your device.
[Verizon Samsung Galaxy S 4] muniz_ri:
No worries. Did you download the ROM directly to your device or other method? thx.
[Verizon Samsung Galaxy S 4] muniz_ri:
Thx. Can you please let me know if you downloaded the ROM you successfully flashed to your device or pc? I'm trying to see if there is a pattern here.

I am showing 127 downloads and only a couple reported failures. Don't know what is causing the 2 -3% failure rate
[Verizon Samsung Galaxy S 4] PartyDroid:
pc i dont know how from my phone. i am doing your yesterday rom now. and stuck on Samsung Boot screen with FF 17

I used your original rom with doing the wipe and dragging it up then flash the rom. this is the only one that works for me. on the other hand my wifes' phone i can use your up to date rom on hers. but not mine for some reason.i think my phone is funny. I am doing NC5 .tar now and going to retry your yesterday rom again.
[Verizon Samsung Galaxy S 4] npjohnson:
PC, then transferred the first time. On phone the second. Both resulted in a hang at the Samsung screen.
[Verizon Samsung Galaxy S 4] sharkie405:
Worked like a charm! Quick and easy! Thank you!
[Verizon Samsung Galaxy S 4] muniz_ri:
Added new ROM to OP which uses a different updater-binary if you would like to test. thx
[Verizon Samsung Galaxy S 4] PartyDroid:
flashing now

Start Time: 11:31pm Samsung Screen Stuck on Samsung Screen 11:34pm

Redoing NC5 again

---------- Post added at 11:39 PM ---------- Previous post was at 11:31 PM ----------

@muniz_ri can you create a rooted OC1 .tar file would that be easyer then having to update everytime? just asking. I know you are hard at work in trying to make this right forevery one of us. I am happy with your work to. but I am just asking.
[Verizon Samsung Galaxy S 4] muniz_ri:
Sorry, impossible to make an rooted flashable .tar due to locked bootloader. thx for testing.
[Verizon Samsung Galaxy S 4] PartyDroid:
no problem can you please send me the original rom with the Wipe please i have so many of the updates and none of them are working. I would like to reinstall the first one please at least I know tht one works for me.
[Verizon Samsung Galaxy S 4] The Grand Pooh-Bah:
I ran it the third time and it made it to the Verizon screen. Went and took a power nap. Came back and it works!!!! YEAH!:good:
[Verizon Samsung Galaxy S 4] muniz_ri:
I am going to put up an "alternative" method for those having the freeze upon reboot issue that should work everytime. Stay tuned...
[Verizon Samsung Galaxy S 4] muniz_ri:
New method added to OP. Follow directions carefully and it will work each and every time!
[Verizon Samsung Galaxy S 4] PartyDroid:
I copy the instructions word for word and i am stuck on samsung boot screen for 11 mins now redoing NC5 again.

Still did not work will try again later for now I am back on the original rom you first loaded. 8:45am
[Verizon Samsung Galaxy S 4] muniz_ri:
The new files use all stock, signed images only from the official full odin .tar. Will wait to hear others experience but it just may be a problem with FF.

In the meantime I suggest uninstall FF and redownload latest version from Play.
[Verizon Samsung Galaxy S 4] PartyDroid:
are you suggesting that i download ff v.18?
[Verizon Samsung Galaxy S 4] muniz_ri:
If you have been holding onto and reusing the same FF apk then yes, download a new copy.
[Verizon Samsung Galaxy S 4] PartyDroid:
i used ff 17 & 18 new and it did not work. i even redownloaded them this morning to see if new ones would work and no go sorry.
[Verizon Samsung Galaxy S 4] BigMike497:
Just tried your alternative method with a rooted Verizon S4 and it worked perfectly. I mistakenly extracted the files and loaded it on to my sd card, then realized that I should of kept it in it's original form. It did exactly as you stated. Was a little worried at the Verizon screen but it turned out fine. Thank you very much.
[Verizon Samsung Galaxy S 4] schmeerdawg:
no root on OC1

Hi all.

I have read through and followed the directions in OP.. I wipe to NC5, towelroot, verify root, flash with flashfire, and phone boots up in OC1 just fine.... however no root. I've done it 3 times in the last 2 days with the exact same results.. Any idea where I'm going wrong? It's driving me bananas :eek:... Thanks.
[Verizon Samsung Galaxy S 4] npjohnson:
Muniz! Great news! I think I figured out why the results are so 50/50.

FF runs under root user context, but for some reason, fails to keep the device awake while flashing, so I tested it out.

Took my screen timeout setting, moved it to two minutes, flashed the file, and it failed. Retry, same result. So then I moved my screen time out up to ten minutes, boom, worked great, did then same again, boom, success. That would account for the 50/50 results that some people are having, as different users have different timeouts.

I think FF is mishandling the device wanting to go to sleep, and panicking, then rebooting prematurely. When this happens, FF appears to be successful, but instead of displaying "rebooting.." It just reboots. For me, every time it has actually displayed "rebooting..." It has been successful, and I was only able to achieve that with the screen timeout set to 10 minutes.
[Verizon Samsung Galaxy S 4] muniz_ri:
That makes so much sense. Other Users experiencing issues please validate and set your screen timeout to 10 mins and report back. Thx.
[Verizon Samsung Galaxy S 4] i8qbert:
Something I learned a lot time ago. Set screen to not sleep while charging in Dev options any time I flash things.
[Verizon Samsung Galaxy S 4] sharkie405:
Off Topic, Sorry...

I am correct in my understanding that there are no recoveries for Verizon Samsung Galaxy S4s on 5.0.+ (OC1), besides stock?

I've already upgraded via muniz_ri's method with Flashfire. After upgrading I've been playing around with things and have already soft bricked my device once. To get back to OC1, I had to Odin flash NC5, then repeat this thread's method to get back to OC1.

I know the number rule of tinkering with one's phone is always make a nandroid backup, but we can't do that on OC1, can we? Safestrap doesn't work anymore and that was our only choice. I know I can make a backup using Flashfire, but I doubt that backup would be flashable through the stock recovery. So, if I were to make a backup via Flashfire, then soft brick my phone, would I only be able to flash my back up after I had Odin'ed back to a functioning ROM?

Any clarification on the matter would be greatly appreciated. Sorry for the off topic post...
[Verizon Samsung Galaxy S 4] muniz_ri:
Look into MultiSystem. There is a learning curve and getting used to but allows you to run a virtual rom that you can modify/mess with while keeping your stock system safe. If you brick your virtual rom you can easily boot back into stock and start over...
[Verizon Samsung Galaxy S 4] muniz_ri:
Based on the number of downloads today and the lack of reported failures I believe that the freeze upon reboot issue has been resolved thanks to [MENTION=5848265]npjohnson[/MENTION]. Is there any need for the the more cumbersome firnware.tar method that I posted yesterday? Does anyone prefer that method?
[Verizon Samsung Galaxy S 4] Osama Chishty:
Already on OC1 5.0.1

i used your first method . i downloaded rom on 1 may and i and using lollipop 5.0.1 now just want to know can i try new rom on same OC1 or i need to go back to nc5 or nk1 ?
[Verizon Samsung Galaxy S 4] eridapo:
[MENTION=4708661]muniz_ri[/MENTION],

Is there a "pre-rooted" tar package available so I can use Odin to flash instead of FF.... I saw you did one for the Sprint L720, and I was wondering if perhaps one was available for the i545.
[Verizon Samsung Galaxy S 4] RisingSkylar:
Ergh, I'm having the freeze upon reboot issue now too. There are so many resources that explicitly warn *not* to downgrade to Android 4.4.2 from Android 5.0.1, but I assume that this is an exception because we're using the bootloader from 4.4.2 in order to retain root? I'll read back through the thread, but to clarify, how exactly do I get myself out of this situation? Do I just start over with the process outlined here: http://xdaforums.com/galaxy-s4-verizon/general/how-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613?[How-To] Root I545_NK1 - 4.4.2 (12-1-2014)?
[Verizon Samsung Galaxy S 4] klabit87:
Have you been able to get anything to flash using MultiSystem? I've made a stock rooted deodexed zip and haven't been able to flash it. Flashfire starts up and never really flashes.

The only thing I've been able to do is create the stock.img with the app.

I even mounted the img and swapped everything so I could have a deodexed IMG but it would get stuck at the Verizon screen and somehow it wiped my system settings.

Just wondering how much you have played with it.

Thanks for your great work [MENTION=4708661]muniz_ri[/MENTION] and [MENTION=5848265]npjohnson[/MENTION]

By the way my intentions are to leave the stock alone and do all custom modifications on the virtual rom.