yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] seadooman:
Hands Free S-Voice

I like an idiot took the ota when it first came out of OC1> I found that S-Voice that I use daily " I live in California so I spend 3 hrs a day commuting" would not announce who was sending me a text, or ask if I wanted to respond or cancel. After many trys by Verizon and samsung it was determined that OC1 didn't support S-Voice? Long story short they replaced my phone which had nc5 and I was able to root and avoid the headache. Would anyone be so kind as to see if S-Voice works on OF1. Just need to know if with data on,hands free on and s-voice when you get a text does it announce it and give you the option to reply.. This post may not belong here but please someone that has OF1 can you check.

Thank You in advance.
[Verizon Samsung Galaxy S 4] sob372:
Can i flash of1 deodex w twrp?
[Verizon Samsung Galaxy S 4] mookeyj79:
I have some answers regarding the downgrading process. I currently have a stock OF1 flashed via ODIN.

I did as instructed. Here is the following errors i receive:

From ODIN:

<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> NON-HLOS.bin
<ID:0/007> modem.bin
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)

From the device:

SYS REV CHECK FAIL(S) : Refer 2 > Binary 1
SECURE CHECK FAIL : system

Then I'm returned to System Update Failed screen.

Both files flashed successfully, but KingoRoot failed. UPDATE: KingRoot also failed.
[Verizon Samsung Galaxy S 4] 47_MasoN_47:
Does anyone know if the built-in Android encryption works with root with this build? I never could get my rooted OC1 to encrypt - it just soft bricked every time.
[Verizon Samsung Galaxy S 4] reliant_turbo:
I'm unable to run flashfire under of1 right now.

It bombs out when opening. Don't know why.

I'm on this rom with the s6 themer enabled, debloated based on the oc1 list. Was fiddling with that database that enables the different particle effects.

Can someone look at this log cat for me. I'm not sure what all of it means.

I tried v21 and v19. Both crash

Brian
[Verizon Samsung Galaxy S 4] reliant_turbo:
Oh yeah and it did work cause I used it to flash xposed and the tether add on and the lollipop animation.
[Verizon Samsung Galaxy S 4] techguy2002:
Did you reset your phones date before 6/1/2015?
[Verizon Samsung Galaxy S 4] reliant_turbo:
i didnt do that at first but was able to flash files just fine. this just happened all of a sudden.

Brian

---------- Post added at 08:43 PM ---------- Previous post was at 08:23 PM ----------

..... even though it worked with the date set to the current date in the past, i tried setting the date prior to june.... i set it to may 1.

it worked. thanks.

i saw the date requirement at the beginning of the thread and i thought that was only for v19.

i cleared cache and data on v19 and uninstalled it. then i installed v21.

bombed out on launch.

then i set the date to may 1. worked like a charm.

flashing the 5x5, continuous scroll TW launcher right now........

........worked.

so those that think like me (dumbly) "im not on V19, i can leave my date alone.."..... think again.... that is if flashfire bombs out. :)

Brian
[Verizon Samsung Galaxy S 4] seadooman:
Can flashfire be used to downgrade? Used flashfire to upgrade to of1 but I hate it.
[Verizon Samsung Galaxy S 4] phil0sophic:
What did you upgrade from? If OC1 what is the difference you dislike?
[Verizon Samsung Galaxy S 4] seadooman:
It made s_voice really buggy.sometimes it works other times it doesn't.I flashed from nc5 4.4.2. If I could get s voice to work I could get used to it. But I use it daily, I live in CA. And spend 3 hrs a day stuck in a traffic jam.
[Verizon Samsung Galaxy S 4] reliant_turbo:
just a note about flashfire v21..... it "expired" sept 1 cause its beta. set the date to 8-31-15 or before for v21 to work. read it in another thread. thats why when i was on v21, it all of a sudden didnt work.... yesterday.... 9-1-15...

Brian
[Verizon Samsung Galaxy S 4] stang5litre:
I wouldn't recommend using it to do that as things change...order and all that stuff. If you were on nk5 before why not use safe strap? Also for your S voice are you running stock OC1? If so might want to try another Rom. To se if your s voice is still running better.
[Verizon Samsung Galaxy S 4] seadooman:
Started w/ nc5 used flashfire to go to OC1 then to OF1, rooted. I would like to go back to NC5. Think it would be safe to just ODIN back? I have seen other members talking about other roms but I am a little leary since this phone has a locked bootloader and I'm not sure if I can do that safely. I havn't found any forums were that subject is posted clearly. I'm still on NC5 boot loader.
[Verizon Samsung Galaxy S 4] phil0sophic:
I don't use svoice sorry, (I live inrual Arkansas no traffic here). Is was curious what could be different... Perhaps someone here uses it on OCI without issue....

Anyone?
[Verizon Samsung Galaxy S 4] sob372:
You should be able to safely odin back to nc5 as long as you didn't change from the nc5 bootloader.

Open terminal emulator,

Type su [enter]

Getprop ro.bootloader [enter]

That will tell you which bootloader you're on

---------- Post added at 04:12 PM ---------- Previous post was at 04:06 PM ----------

Can anyone tell me if I'll have problems flashing with twrp
[Verizon Samsung Galaxy S 4] stang5litre:
As long as your on nc5 just odin back to that. And re root and pick your rom or stay stock.

I don't use s voice enough in my rom to tell you. What do you use it for and I can test it

Sorry for off topic in thread
[Verizon Samsung Galaxy S 4] seadooman:
S-Voice

I set s-voice to answer texts and calls while driveing. I dont use bluetooth or a headset.. I just sit the phone on my dash. So it goes turn on data,handsfree and s-voice. I normally can send a text or 2, but when receiveing a text on 4.4 it woulds announce who was sending the text and ask if i wanted to read or cancel. Now once the text is received all I get is the "sound" that set up for a text w/ nothing else. this happened with the first update of OC1 but I was hoping the issue was resolved w/ OF1.

I keep hearing about different roms? But have not been able to find them. Is there a separate forum for these that I haven't found yet?
[Verizon Samsung Galaxy S 4] stang5litre:
Just look in the development section.

Not promoting my rom here just showing you what I mean

http://xdaforums.com/showthread.php?t=3132555
[Verizon Samsung Galaxy S 4] seadooman:
Will this rom work w/ flashfire?
[Verizon Samsung Galaxy S 4] stang5litre:
Yes. But there are others as well. Just showing you where they were hiding at [emoji6] . But you are welcome to try it out. [emoji48]
[Verizon Samsung Galaxy S 4] sob372:
....but will it flash w twrp ??
[Verizon Samsung Galaxy S 4] stang5litre:
I flashed mine through Twrp look at my signature. Yes TWRP compatible. [emoji106] PM me with questions about it. Don't want to keep putting in the wrong thread.

Sorry for off topic.
[Verizon Samsung Galaxy S 4] mikeyjj:
Updated i545_OF1 - 5.0.1 and Keep Root

Sorry if im in the wrong place, Im a strait up noob at this. I have an i545 that was vrugoc1 5.0.1(ota) with kingroot. Needed to fix probs that came with the 5.0.1, so I did the OF1 keep root update & it worked great but I lost my wifi. I rebooted twice and still no change. Please help if possible and thanks in advance!
[Verizon Samsung Galaxy S 4] stang5litre:
Check to make sure your wifi modules are there.
[Verizon Samsung Galaxy S 4] mikeyjj:
Thank for replying, sorry, should've been more specific. After the keep root update I signed in 2 my gmail back-up cause its suppose to bakup wifi settings & all but had 2 re add my home wifi because the wifi scanning never finds it. I'v re added it 6 r 7 times, reset router multiple times & fone always says its not in range & doesn't even try to connect. Also it does try connecting 2 my neighbors wifi from 150ft away
[Verizon Samsung Galaxy S 4] Fadtydawg:
I have tried both odex and de'odexed, both stuck at splash screen. Followed the instructions perfectly. Will not work for me. I'm on OC1 rooted. Sch-i545. Original OTA OC1 then rooted with kingroot. I do have the device system firmware updater frozen with titanium backup. Could that be my issue or is it b/c the odex and de'odexed have a different bootloader from the original OTA of the OC1?

Thanks for the hard work Muniz_ri !!
[Verizon Samsung Galaxy S 4] stang5litre:
Have you replaced kingroot with superSU? Not sure on muniz_ri 's rom. But on mine you have to make sure the order is right or you won't boot. I don't think his has that so it should be easier. FF is very finicky.
[Verizon Samsung Galaxy S 4] Fadtydawg:
Yes I have.
[Verizon Samsung Galaxy S 4] stang5litre:
Sorry [MENTION=4708661]muniz_ri[/MENTION] just trying to help out. ?

---------- Post added at 05:32 PM ---------- Previous post was at 05:29 PM ----------

Check the md5 to make sure you didn't get a bad download against his afh. If they match your good on the download and we can move on from there
[Verizon Samsung Galaxy S 4] Fadtydawg:
How would I check the md5?
[Verizon Samsung Galaxy S 4] stang5litre:
On his afh it should have a md5 number underneath the download. As far as your download are you on a Linux machine or windows?
[Verizon Samsung Galaxy S 4] Fadtydawg:
I found the md5 for muniz_ri.

I'm on my device so I have terminal emulator install..Linux is that ok? My file is the OC1 factory file from sammobile.com for the sch-i545 . I Odin that file after first attempt of stalled splash screen.
[Verizon Samsung Galaxy S 4] stang5litre:
This is just a example .

su

cd sdcard

md5sum NAME_OF_FILE
[Verizon Samsung Galaxy S 4] Fadtydawg:
App store md5 calculator.

Results, top one Muniz_ri stock rooted,

Bottom one is the factory file from sammobile.com
[Verizon Samsung Galaxy S 4] stang5litre:
Ok so does that match his afh?
[Verizon Samsung Galaxy S 4] Fadtydawg:
Mabey we are confused here. The one on top is the muniz_ri md5 I used to upgrade with ff when splash screen stuck over 30 min. The md5 i downloaded and ran matched.

The 2nd one I posted was for OC1 I'm running now. I thought you were asking if those matched. My bad.

Definitely what I downloaded and tried to run matched.
[Verizon Samsung Galaxy S 4] stang5litre:
Ok ya sorry definitely miss understood. Have you tried flashing anything else just to see? You should be on version 21 if I am not mistaken. Not sure why if your following muniz_ri instructions why you keep sitting there. Did you try pulling the battery to make it boot? I have heard some say they pulled battery and it fixed for them. 2 times I believe they did it. Not on this rom but because of FF
[Verizon Samsung Galaxy S 4] Fadtydawg:
Yup, pulled battery several times. Tried wiping cache etc.. I'm just don't get it. Ive Rooted several phones,custom roms etc. Just at a loss here. Afraid to flash anything else. Re-do on the device is a pain. Miss safestrap.
[Verizon Samsung Galaxy S 4] stang5litre:
Just odin back without wiping data. [emoji6]

Then it's not that bad. Had to do that to my wife's phone. Besides re flashing or trying another rom not sure what to tell you. Muniz_ri roms are solid. I used to be on his before I made mine. So not sure why you are having such a issue. It's just one file to flash. But FF likes to change oder right before you flash to making wipe at the end. I bet that's what happening to you. But you have to be willing to try
[Verizon Samsung Galaxy S 4] Fadtydawg:
Thanks for taking the time out to help. Very much appreciated. I'll give that a shot.
[Verizon Samsung Galaxy S 4] EdrickMG:
If you update from sammobile it's like you have updated your bootloader to the most update one which has patched king root and other things... Some users report have rooted with other methods... But maybe flash fire is like stuck without a solid root... I don't update from sammobile because is like take OTA updates... Instead always use roms from xda like stange or Muniz, you can try to recover with Odin and try several methods to gain root hope you success
[Verizon Samsung Galaxy S 4] stang5litre:
Np at all let me know if it works. If not we can try another route. You are on OC1 correct? Not OF1? If so what he wrote doesn't apply. Thought we already established you were on OC1.

Ya page 13 you said your on OC1.
[Verizon Samsung Galaxy S 4] F1a5hP01ntX:
Not sure if it's still an issue, but try changing your screen timeout to 10 mins before flashing with FlashFire. The screen turning off was causing the flash to fail and resulted in hangs and bootloops
[Verizon Samsung Galaxy S 4] trashcompactor:
Root OC1 with NK1 BL

I read through the posts but didn't see anyone that has my issue. I started with OC1 rooted with the NK1 bootloader and used the OP and FF v21 (with date changed) to get to OF1 rooted. Then the first restore that i did from Titanium Backup caused my phone to hang on the verizon screen. Then I used the OP instructions to I545_Downgrade_to_OC1.tar but now I have OC1 without root. I know the OP said to use KingRoot but I don't trust it. Is there any other way to get to OC1 with root (preferably Deodexed)? I checked with a terminal emulator and I still have the NK1 bootloader. I would normally think to go back to NC5 but those instructions are to root NK1, not OC1wNK1 bootloader. Any help is appreciated.
[Verizon Samsung Galaxy S 4] techguy2002:
You can always do it with kingroot with oc1 and then upgrade with the of1 deoxed file. It's been pretty stable.
[Verizon Samsung Galaxy S 4] jdelphiki99:
If you're on NK4 or earlier, can you also restore back to NC5 and use towelroot, to avoid paying $4 for supersume? Not that I have a problem with paying for an app, but I'd rather donate that money to a dev who's stuff I'll actually be running than an app I don't technically need.
[Verizon Samsung Galaxy S 4] skepticmisfit:
yes. they didn't increase the qfuse counter until oc1 so nk4 and all previous kk builds can be downgraded to nc5
[Verizon Samsung Galaxy S 4] trashcompactor:
Thanks jdelphiki99 and skepticmisfit, so i flashed NC5 and now my phone won't go past the Samsung galaxy S4 initial screen. It hangs there for a bit then reboots into recovery. Any ideas?

Update: Used odin to flash the I545_Downgrade_to_OC1.tar.md5 again and now my phone is booted again and back to OC1 without root. The OP says to use KingRoot but they don't like the verizon S4 on their support list (at least under i545). Any help would be great.
[Verizon Samsung Galaxy S 4] Nick3193:
OK, I've tried this twice now with the deodexed version of the ROM. Both times after I click the lightning bolt and say OK, the screen goes black for a few minutes (as expected) then reboots to Android system recovery. The little robot is lying down with a warning symbol and says "No command."; at the bottom it says "Manual Mode" and that it successfully applied the VZW csc (whatever that is). At the top my options are to reboot, apply update from ADB, apply update from manual storage, wipe data/factory reset/wipe cache, or apply update from cache. I'm upgrading from MK2 (with that bootloader), rooted. Any suggestions? Rebooting from here just takes me back with no changes to my phone (that I can see). I'm using the deodexed version so I can reinstall Xposed once I've upgraded. Any suggestions? I'll ask this over in the Flashfire support thread as well.

Thanks in advance for any assistance!
[Verizon Samsung Galaxy S 4] sinner822:
Odin the kernel if you don't have of1 use oc1

Edit: scratch that. you have to come from nc5.
[Verizon Samsung Galaxy S 4] traco1:
Do not see this question anywhere. OK My s4 i545 keeps bugging me to upgrade something to correct overflow underflow problems. I have root & flashfire. Now Flashfire doesn't work anymore. I uninstalled & reinstalled still no good. Now @ 1 point I hit the upgrade by mistake. After a few seconds it said it could not upgrade & stopped. Don;t no if this is the problem or not. How can I get Flashfire working again? Do I need to re Odin & start over . What a pain!!!
[Verizon Samsung Galaxy S 4] sinner822:
Delete sdm.apk w/root Explorer and clear cache.
[Verizon Samsung Galaxy S 4] Nick3193:
Flashfire isn't working because the beta version expired. Set your system date back to before 8/31 and it'll work fine.
[Verizon Samsung Galaxy S 4] Ghoshnik:
Worked For Me. Thanks!

Flashed OF1. No issues. also flashed hotspot addon. Worked great. Kept root. Just had to set date back before 9/1 to get FlashFire to work.
[Verizon Samsung Galaxy S 4] trashcompactor:
muniz_ri, could you update the OP to say that KingRoot won't work for Verizon S4s due to the locked bootloader?
[Verizon Samsung Galaxy S 4] Fadtydawg:
Kingroot works if OC1 or earlier ..just not on of1 yet.
[Verizon Samsung Galaxy S 4] K-Rat:
The downgrade doesnt work on OTA OF1 phones, just tested it.
[Verizon Samsung Galaxy S 4] EdrickMG:
Doesn't work if you took OTA, Verizon patch it, any rom from xda doesn't upgrade bootloader so you can always downgrade
[Verizon Samsung Galaxy S 4] 47_MasoN_47:
Just tried to flash the deodexed version. My phone's been sitting at the Samsung splash screen with the "Custom" icon for about 10 minutes. Is something wrong or is this expected?

---------- Post added at 10:12 AM ---------- Previous post was at 09:53 AM ----------

Just pulled the battery. Powered back on and it's still sitting at the "Samsung <unlocked lock> Custom" screen. What do I do now?

I hate screwing with this stuff. I'm glad that there are people out there that give us root, but good lord I hate dealing with this crap. Every freaking time.

EDIT MORE:

Googled around and found guides to Odin back to the thing like the first post says to unbrick. Did that but now when I run kingroot it has some chinese junk and says to push some buttons on the phone to do something. What is it telling me to do?

EDIT AGAIN:

Took a guess and enabled developer mode. Still got a bunch of prompts from the software. I just clicked bits until it said it was done. Now it seems to be rooted but it's boot looping. Keeps saying "Process system isn't responding. Do you want to close it?" Regardless of what option I pick it just loops again. Anyone?
[Verizon Samsung Galaxy S 4] Fadtydawg:
I had the same issue. Odin factory OC1 if that is what you were running not (of1) find OC1 file on Sammobile.com. Takes a while to download. Odin flash file then root with kingroot. Once you are rooted and running again, I was told to set sleep screen for 10 min or more on the device and try to flash the de'odex again with flash fire. I didn't try. But that's a solution anyway.
[Verizon Samsung Galaxy S 4] BoulderGeek:
FlashFire v.23 force closes on me, even after clearing data and cache on the app. Phone is VZW i545 with OC1, rooted, runing muniz_ri's 5.0.1 OTA repack.

I have changed the date to July 10, 2015 (even though I am using the regular version, not beta). Freeloader Pro features on or off, it FCs every time I hit the "Flash Zip or OTA" action item.

Can I flash in Recovery (on OC1)?

Currently trying to update to FlashFire v.24 but Play store won't DL over my LTE or WiFi at work. gaaah EDIT: Oh, whoops, perhaps if I turn NTP back on and have a proper timestamp the Play Store will work? Yep.

OK, leaving this here, in case it helps some other schlub:

Upgrade Flash Fire to version .24. That fixed my FC issue and allowed flash.
[Verizon Samsung Galaxy S 4] 47_MasoN_47:
Ok, I Odin'd again to OC1. It didn't data wipe, and seemed to work fine. Kingrooted again and was able to reboot and such without the phone exploding. I've run Super-Sume and everything seems ok at the moment... I'll change the screen timeout and try to flash the update again later.

Thanks!
[Verizon Samsung Galaxy S 4] Fadtydawg:
Very welcome. Keep us all posted if the 10 min sleep time works. Thumbs up.
[Verizon Samsung Galaxy S 4] 47_MasoN_47:
It did :) Happily running OF1 now! Thanks for the assist. I still don't really get why this blew up the first time round. Glad its working now though. It's nice to be able to see the numbers on the pin screen instead of white squares.
[Verizon Samsung Galaxy S 4] GogoplataMMA:
I don't get it. I followed the directions... but now I'm stuck on a blank screen with my LED fading in and out while colored blue. It's been stuck like this for 35 minutes. I tried a battery pull and put it back in but nothing. No Verizon screen at all. Just a blinking blue light. I am coming from a rooted version of the previous update released that upgraded Android. Am I bricked? I used the regular ROM, not the DeODEXED ROM. I used FlashFire v24.

EDIT: The Verizon screen did come on after 40 minutes, but so far it has been an hour and it hasn't booted beyond the Verizon logo. I'm not sure if I should just keep waiting or not... What can I do?
[Verizon Samsung Galaxy S 4] techguy2002:
Should have read the first post it says to use version 19 and has a download link. Try to get into download mode and see if you can use either the the nc5 downgrade or oc1 neutered file to get your phone operational.
[Verizon Samsung Galaxy S 4] GogoplataMMA:
I've used FlashFirev19 as well. I ODIN'd back to OC1, used KingRoot to root the phone, then used Super-Sume to get rid of KingRoot. Then flashed the OF1 Stock ROM. Everything went fine, phone restarted, got the Samsung logo, but then it went dark again and has stayed dark. No Verizon logo. Stuck again. Looks like I'll have to ODIN back and just forget it. I'll just keep hitting "Install Later" every day on that annoying update popup. :\

EDIT: I'll try one more time using this "neutered" version I found called "I545VRUGOC1_Neutered_Full_Odin.tar"

http://xdaforums.com/galaxy-s4-verizon/general/i545vrugoc1neuteredfullodin-tar-t3098956

EDIT 2: I've ODIN'd the Neutered version of OC1 successfully.

I've enabled Unknown Sources to be installed.

I did the KingRoot/Super-Sume rooting method.

I then entered Developer Settings and enabled USB Debugging and Mock Location. (Just something I always do)

I installed FlashFire v19.

I then used I545_OC1_Batch_DeBloater to remove all the default junk installed on the phone just so it ran smoother.

Restarted the phone again, back into the OC1.

I then manually changed my date and time in settings to August 18th to get FlashFire working.

I loaded the OF1 ROM, following the directions in the main post.

I flashed, it showed scrolling text, then went to a FlashFire screen where it installed the OF1 ROM.

It rebooted, but there was nothing but a black screen(again, still).

The black screen hangs while the LED indicator flashes blue over and over.

It does not reach the Verizon logo unless I do a battery pull.

Once I reach the Verizon logo, it freezes there doing nothing.

I'll pull the battery again and end up with the same exact results - a frozen Verizon logo.

No progress can be made and I will have to stay on OC1 instead of the upgrade to OF1 until there's a fix for the issue.
[Verizon Samsung Galaxy S 4] Zelmo88:
I was able to upgrade to OF1 from OC1 rooted without problems using Flashfire v24 and the odexed ROM. Did not have to set my system date back. Worked perfectly the first time. Everything seems to be working fine! Many thanks to muniz_ri for the post!
[Verizon Samsung Galaxy S 4] GogoplataMMA:
I'm jealous! Lol. My phone just doesn't like this OF1 update for some reason. Can't update. :(

Oh well, guess it isn't that huge of a deal to just keep pressing "Install Later" everyday.

Did you also use ODIN3 v3.10.7? I wonder if the ODIN version can be an issue, hm.
[Verizon Samsung Galaxy S 4] techguy2002:
Did you set the screen timeout to more than 10 minutes before running flashfire?
[Verizon Samsung Galaxy S 4] GogoplataMMA:
I did. Each time I tried. It didn't help unfortunately.

I'm back and loaded on OC1 again perfectly fine, but my phone just does not want to take the OF1 update for some odd reason. There's nothing wrong with my phone so I can't figure out how others can do it perfectly fine.