yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] stang5litre:
Thanks everyone for your fast responses!!!

I just want to thanks to all of you who answered my post for SS/FF OC1 Conifrmation!!!

I have updated the links with SDM deleted for future users so they don't have to freeze the app or delete.

I also looked over my scripts and both are fine. So have no fear flashing my ROM just please PAY ATTENTION OF ORDER ON FF as FF TRIES TO CHANGE IT BEFORE FLASH. I'll update that in the OP as well even though it's already in there about checking the order. So it comes down to the User just taking their time when flashing. I am taking my family to the Ga Aquarium today so i won't be responding much till later. Those of you who have PM'd me I will respond as soon as I get back. I tried to stay up as long as i could last night so if you didn't get a response it's because I am human and feel asleep. Please remember I am eastern time zone.

Thanks so much for everyone's time and your responses

:)stang5litre:)
[Verizon Samsung Galaxy S 4] Beej1970:
Someone was looking for the open source code for OC1? Here you are :

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SCH-I545_NA

Sent from my SCH-I545 with stang5litre Edition 5.0 on stock OC1
[Verizon Samsung Galaxy S 4] reliant_turbo:
You rock stang......
[Verizon Samsung Galaxy S 4] Nydalxy:
Disregard
[Verizon Samsung Galaxy S 4] forum7803:
You are the best stang
[Verizon Samsung Galaxy S 4] miltblue:
I flashed a couple of times from stock OC1
[Verizon Samsung Galaxy S 4] Joe_6pak:
Try Adaway. Worked like a champ for me :victory:!
[Verizon Samsung Galaxy S 4] Bones519:
Is there any way to get player controls back on the lock screen?
[Verizon Samsung Galaxy S 4] oraixearl:
Wanam xposed
[Verizon Samsung Galaxy S 4] Bones519:
I have looked all through Wanam and can't find that option. Am I missing it somewhere?
[Verizon Samsung Galaxy S 4] Nick_73:
Sir I'd like to thank u for this awesome rom. It's the only one for OC1 that I like. I just have one complaint : the emojis aren't Samsung anymore ? I liked the old ones better is there a way to get them back?
[Verizon Samsung Galaxy S 4] oraixearl:
There is a lock screen shortcut option. Don't know if it's able to put the controls on. Haven't tried, but I have other shortcuts I've used it for. That was my best guess how to do it. My post prob should have read "wanam xposed?"
[Verizon Samsung Galaxy S 4] Tech E Coyote:
New Update Ready to install

Today I received a pop up saying an update is ready to install.

I'm on MDK with Ver. 2 Stang5litre. Love this ROM. Outstanding Job !!!

How is this possible? Do I take the update or?

I'm sorry in advance if I posted this incorrectly..
[Verizon Samsung Galaxy S 4] Hashbang173:
Do not take the update

If it goes through, you will lose your mdk bootloader and probably semi/hard brick your device.

I would recommend freezing the SDM app in an app such as ROM toolbox lite
[Verizon Samsung Galaxy S 4] Tech E Coyote:
SDM

Got it thanx. Do I need to reload the rom now to get the update off the phone? And make

sure to just freeze SDM? Or?
[Verizon Samsung Galaxy S 4] Hashbang173:
Freezing SDM should be enough.
[Verizon Samsung Galaxy S 4] Bones519:
Yeah. It has that, but not player controls on lock screen option. Thanks, though. ☺
[Verizon Samsung Galaxy S 4] Bren123:
Fixed lockscreen wipe cache with app manager in rom toolbox I selected every app set a password rebooted and it worked
[Verizon Samsung Galaxy S 4] stang5litre:
When in your message just hit the left menu key(haptic button) and insert smiley and it will be old style :)
[Verizon Samsung Galaxy S 4] G.moe:
[MENTION=4840281]stang5litre[/MENTION] I'm getting "some symlinks failed" with the new version, using FF on OC1. Whent he phone turns on, I get the "Custom" unlocked padlock screen, then I hear the boot sound, but the screen stays black (no logo or graphics of any kind). I waited 15 minutes before pulling the battery, but no luck.
[Verizon Samsung Galaxy S 4] stang5litre:
SDM

I have fixed this and re uploaded both roms. I would delete SDM. Thats what i did.

The new links have SDM gone. Just a FYI :)

I deleted mine and froze my wifes both work. But the I did upload both roms with SDM gone if you would like to flash that. May make you feel safer.
[Verizon Samsung Galaxy S 4] klabit87:
Just so everyone knows the reason for the black screen but hearing boot sounds and everything is because of the symlink failures.

I am working with another user to try to figure out a solution as well as coordinating with [MENTION=4840281]stang5litre[/MENTION]

The failed symlinks are apparently related to the digitizer and lcd screen drivers, hence no way to interact or see the screen.
[Verizon Samsung Galaxy S 4] NapalmDawn:
So if I odin back to a stock oc1 and root again, will there be another way to come over to Stang 5.0 without having to do flashfire? I'd totally be willing to try it again if the belief is that a new upload will fix the flashfire...flashing (no pun intended). Waiting for the nod from folks here to try again.
[Verizon Samsung Galaxy S 4] Beej1970:
If you're on stock OC1, there is no other way to get on any ROM without Flash Fire.

Sent from my SCH-I545 with stang5litre Edition 5.0 on stock OC1
[Verizon Samsung Galaxy S 4] NapalmDawn:
Alright. Time to odin this thing back to stock pop again.
[Verizon Samsung Galaxy S 4] miltblue:
Glad it worked

Glad it worked for you. I'm also glad to know you only have to do clear cache. Didn't know whether it was cache, data or permission the way I did it.
[Verizon Samsung Galaxy S 4] stang5litre:
For some reason it seems to be a hit or miss with NON MDK users. I have some it works for and some it doesn't. First thing i would do is check permissions. Also when you open up your viper and install the driver and so on don't turn off LPA and reboot. Delete the data on that app and try and reinstall. Let me know

What version of FF are you on? We have also narrowed down that some versions of FF are messing it up. I helped a user last night and he had v21 and it went right through. He was at black screen. Had him odin back to OC1 root get superSU on and then re download the rom. PM me when you are at this point and I'll get you on the Rom. Also [MENTION=1449386]kalbit[/MENTION]87 also found another stable version of FF and its v19.

FF is a must and the only option that OC1 users have. I talked someone through getting on my ROM last night NON MDK. He had FF v21 and it worked fine. Had him odin to OC1 re root, put superSU back on, re download the rom check md5 and then PM me. The key is the order and properly working FF. (new links with SDM removed)
[Verizon Samsung Galaxy S 4] miltblue:
Checked my version after reading this and its version 0.21. I've flashed V1 once from Muniz OC1 and V2 twice from stock OC1 with no problems. Is there a link to FF version 0.21? I downloaded it when it was beta and you had to go thru Chainfire on Google+.
[Verizon Samsung Galaxy S 4] stang5litre:
I just did my wife's phone today so let me check her version i would assume its the newest. IF so i will upload it and share with you. Give me a few got to run to the store :D
[Verizon Samsung Galaxy S 4] biikman:
FF backup possible?

this may have been answered in thread, but I didn't see it. Apologies if so...

is it possible to make a backup, and restore it, similar to safestrap? i saw a backup option but there were to many other options after that and I didnt want to mess up my phone experimenting.

thanks..
[Verizon Samsung Galaxy S 4] G.moe:
I've tried from OC1 all around, kingroot>supersume>FF (FFv19 and whatever is the newest from the store; FFv21, I think). Same issue, some symlinks failed, black screen after the open padlock. It's only been 7 minutes at the time of sending; I'll let it sit for around 25 minutes.

EDIT: I'm also discussing this with [MENTION=4168602]klabit87[/MENTION]
[Verizon Samsung Galaxy S 4] stang5litre:
Ya I am taking to him. It needs to look like this. Please odin and re root and use the new links I have with NO SDM in it. FF has a tendency to move wipe at the end. So you have to do it twice really 4 it to stick. Check Md5 make sure same as afh.

Where is your phone at now? As far as stock oc1 or ?
[Verizon Samsung Galaxy S 4] G.moe:
Already using the new links, and I'm certain that it is in the correct order. Once the FlashFire process begins, wiping is the first action taken. I've checked the hash of all files, and they match. I'm going to try testing a different OC1 tar.
[Verizon Samsung Galaxy S 4] NapalmDawn:
I'm betting this is going to be a failure again. Here is a pic of my flashfire just before I hit the bolt. I just FRESHLY downloaded the kernel and the rom (but not supersu) at 12:30 AM EST (about 30 mins ago). It's hard to watch the actual flashing process because it gets going super fast after the rom but I noted "some changes failed" and that's all I could catch. This time I unplugged it from my PC prior to the flash (full charge) and the display was set to a 10 min time out. Also, all my files are copied directly via USB from my PC to the download folder in the internal memory (no SD card is in it yet)
[Verizon Samsung Galaxy S 4] klabit87:
Flashfire keeps logs. Can somebody with a failed flash send me a log? It should be in the flashfire folder either in internal storage or external
[Verizon Samsung Galaxy S 4] tommykmusic:
All of that is correct.
[Verizon Samsung Galaxy S 4] oraixearl:
Just curious, why are people changing to a 10 minute timeout? Haven't had an issue with the screen timeout while flashing either version. Did someone have a bad flash because it timed out?
[Verizon Samsung Galaxy S 4] G.moe:
Several issues.
[Verizon Samsung Galaxy S 4] klabit87:
Looks like flashfire doesn't have permission to do some operations.

After rooting do you open supersu and make sure the binaries are updated.

Do you have busybox installed?

I know it's not required but it may help I'm not sure.

Do those that have had successful flashes have supersu pro or those that have failed do or don't have it?

According to the logs it didn't have permission to make some symlinks so it just quits trying after a few failed attempts.
[Verizon Samsung Galaxy S 4] G.moe:
I'll try again now with busybox.
[Verizon Samsung Galaxy S 4] klabit87:
I would think that if it were required then it would be noted by flashfire but I don't know.

Just brainstorming.
[Verizon Samsung Galaxy S 4] NapalmDawn:
My super su for SURE is updated. Running the supersu me pro forces it during the switch. Busybox pro is also definitely updated for me as I know it loaded to 100%, I hit install and it was like hey grats! You have everything done!
[Verizon Samsung Galaxy S 4] klabit87:
Ok. I will continue to look into it. There has got to be some reason only a few out of 20+ can't flash this rom.
[Verizon Samsung Galaxy S 4] G.moe:
Before I bite the bullet, do you have any suggestions for SuperSU (default access, su during boot, install to /system, trust system user)? And whether I should use FFv19 or FF from the store?
[Verizon Samsung Galaxy S 4] klabit87:
I think I remember su during boot being important from the keep root method.

I would set default access to grant.

And use the latest ff from the store.
[Verizon Samsung Galaxy S 4] G.moe:
I tried that setup on nc5 wth busybox and on oc1 without. I assume trust system user isn't necessary when default access is grant.
[Verizon Samsung Galaxy S 4] klabit87:
That is only necessary when a system app or function needs root access.

You can try it if you want though.

I will have to look more into this tomorrow though.
[Verizon Samsung Galaxy S 4] G.moe:
Same issue again. Let me know what you think of tomorrow.
[Verizon Samsung Galaxy S 4] NapalmDawn:
Now that I admit is something I didn't do. Mine was still on prompt. I recall back when I had my rezound, there were a few people who had like a certain kind of wafer that would sometimes rear it's ugly head and cause issues. I wonder if those of us that have FF problems (mine was .21 from the store before I flashed) all have a common thread. Anybody hear that knox is now blocking root on the VZW G6s? I swear, between the whole annoyance to get s-off on the rezound and the safestrap setups for the G3 and the G4, I keep picking the most obnoxious phones to get root and unlocked bootloaders (and this is coming from somebody who rooted an HTC Flyer....)
[Verizon Samsung Galaxy S 4] stang5litre:
This looks like to me that when they went to switch to superSU something didn't take right. That's why they are getting denied permissions. Looking into the actual app right now. Maybe I can fix their app. Never know.. looking more into the log and the app. But it's deff not the rom. As people are on it. 30+OC1.

Looking at the log. How did you switch to king to SuperSU? Did you do it by super sume? Or website with terminal emulator? If you used the app this is probably why. If I am not mistaken people were having problems with that app. But of course i don't know what process you used.

Problem isn't your pick of phones. Seems more like your timing is off. Like you are getting the phone's after they have been out for a while and the company has already sent updates to fix all the roots. MDK from the start of s4 and i bought mine months after it came out. Previous device HTC Thunderbolt rooted.
[Verizon Samsung Galaxy S 4] oraixearl:
When I switched king root to supersu I used the terminal emulator method, and then updated the binaries. haven't had any issues with ff. Don't know if this helps anybody, but maybe it will.
[Verizon Samsung Galaxy S 4] G.moe:
I was using Super-SUme. I'll try now with the terminal emulator/script method, and I'll also pull out my sd card.
[Verizon Samsung Galaxy S 4] stang5litre:
SD shouldn't be a issue. But if you were flashing from there try internal. If you have tried both just leave it on sd.

Let me know please. I put my mom's phone in my Rom the day before yesterday using that method and it went right through. FF v21.
[Verizon Samsung Galaxy S 4] G.moe:
I'm still waiting on initial boot, but there was no symlink failures this time, and the Samsung splash is displayed! It seems the issue was Super-Sume in my case; you might want to remove that suggestion from the instructions if others are having that issue.
[Verizon Samsung Galaxy S 4] stang5litre:
Let me know if you get booted taking that app option out
[Verizon Samsung Galaxy S 4] biikman:
Quick bump...

Oops disregard..

Sent from my stang5litre Edition 5.0
[Verizon Samsung Galaxy S 4] stang5litre:
OP updated.
[Verizon Samsung Galaxy S 4] G.moe:
Success! I made it to setup, skipped through, changed default su access to grant, and the rom is working smoothly. Thank you for the clean rom and for helping solve the issue!
[Verizon Samsung Galaxy S 4] stang5litre:
Woot!!!!! No problem at all [emoji48] . Glad we got you going. It may take me a minute but usually I can find the issue. Also helps that [MENTION=4168602]klabit87[/MENTION] helping out.
[Verizon Samsung Galaxy S 4] kauaigs:
Super sume was my issue too...but I had sussessful flashing after removing kingroot with terminal.
[Verizon Samsung Galaxy S 4] G.moe:
I have a new issue now; Action Launcher 3 won't work. I've uninstalled/rebooted/reinstalled multiple times, and it will not launch (immediate crash). Nova Launcher works, though...

Edit: I fixed this by enabling the service under Settings>Accessibility
[Verizon Samsung Galaxy S 4] forum7803:
Portable Wifi Hotspot " on't work "

---------- Post added at 04:15 PM ---------- Previous post was at 04:14 PM ----------

stang5litre Edition 5.0 NON MDK v2 NON-MDK
[Verizon Samsung Galaxy S 4] stang5litre:
Working fine in MDK. I know someone else on SS there's works 2. I can make you a flashable one or you can go to OC1 MODS and [MENTION=3074508]old&slow[/MENTION] has one posted there
[Verizon Samsung Galaxy S 4] forum7803:
this not work for me
[Verizon Samsung Galaxy S 4] forum7803:
v1 can work for me ba v2 not work
[Verizon Samsung Galaxy S 4] stang5litre:
I'm driving atm. I'll re check mine when I get home.
[Verizon Samsung Galaxy S 4] stang5litre:
And just a heads up you would have not got to the point of turning it on if was not hacked. Gives you a verizon msg about activation. . But checking when I get home
[Verizon Samsung Galaxy S 4] forum7803:
my gt-i9505 Wifi Hotspot can work for me
[Verizon Samsung Galaxy S 4] stang5litre:
When at you hotspot screen like you posted. Hit left haptic button and setup. Change the name to whatever you want and WA LA it is working.??
[Verizon Samsung Galaxy S 4] stang5litre:
Please try using the terminal emulator method to switch kingroot and you will have success. ?let me know please

Thanks
[Verizon Samsung Galaxy S 4] forum7803:
can work for me thank you stang:good:
[Verizon Samsung Galaxy S 4] stang5litre:
Np glad everything is worked out [emoji106]
[Verizon Samsung Galaxy S 4] G.moe:
[MENTION=4840281]stang5litre[/MENTION] After setting everything up, the rom is working beautifully, including xposed.
[Verizon Samsung Galaxy S 4] stang5litre:
That's what I like to hear [emoji106] [emoji48] [emoji48] [emoji2]

Let me know if I can assist any further. After you play around with it do you mind leaving a review? 1st page of OP one of the tabs also there is a spot for feature requests as well.

Thanks
[Verizon Samsung Galaxy S 4] biikman:
bump.. thanks!
[Verizon Samsung Galaxy S 4] stang5litre:
This was already addressed. And you just responded to your own message and thanked yourself lol. Not sure if you saw that [emoji38]
[Verizon Samsung Galaxy S 4] biikman:
ya was in a hurry and using my phone... thought maybe it was a yes or no easy answer... i'll search the thread more. thx

(the thanks was for any responses, not for myself lol)
[Verizon Samsung Galaxy S 4] stang5litre:
I thought [MENTION=4168602]klabit87[/MENTION] already answered this for you? Said it was tedious but can be done. Maybe another person but it's a few pages back
[Verizon Samsung Galaxy S 4] biikman:
hmm not that i saw, but will check again.... apologies if i missed it.
[Verizon Samsung Galaxy S 4] stang5litre:
It could have been someone else asking the same question. No apologie necessary
[Verizon Samsung Galaxy S 4] klabit87:
It was for bones519. I'm not sure about the flashfire backup
[Verizon Samsung Galaxy S 4] stang5litre:
Got ya. My mistake [emoji33]
[Verizon Samsung Galaxy S 4] NapalmDawn:
Yeah reading some good proof on this here. Off to try it now!

Edit-We have ROM! Yay finally! I guess it was SuperSu Me all along. Even paid for it :\ Oh well. Thanks for toughing this out Stang!
[Verizon Samsung Galaxy S 4] rpoitras:
The gyro/compass sensor is fixed on this build/kernel, apparently. Was there updated kernel code from Samsung? Just wondering.
[Verizon Samsung Galaxy S 4] stang5litre:
No kernel is the same as v1 [MENTION=4939386]Surge1223[/MENTION] kernel just baked in this time. Instead of Hybridmax
[Verizon Samsung Galaxy S 4] NapalmDawn:
Klab, Stang, Bleej-thank you all for helping me and others get to the bottom of this flashing problem a lot of us had. It was getting pretty frustrating working on rooting this over 3 weekends and knowing you largely weren't doing anything wrong. I appreciate all the effort and help you guys put into getting this resolved. Time to start moving some stuff off the G3 onto this and go forward :)

Anybody got a screenie of what the flashable boot animation looks like? Also, I know it's around somewhere but does anybody have info on running xposed with this rom? Probably going to look at bringing over wanam and maybe a few others.
[Verizon Samsung Galaxy S 4] stang5litre:
Np at all glad to get you on and get to the bottom of it as well. Xposed works great with the rom. I use wanam as well. For xposed you install the apk and flash the zip right after.i have the older one posted back on page 30 something or you can go to non official xposed get the apk and the newest zip. I didn't update because mine works fine. Let me know what you think about it after you play around with it. [MENTION=2026779]gadget![/MENTION] Has a gif somewhere of it
[Verizon Samsung Galaxy S 4] Neffy27:
search here & previous post, search results & stang's
[Verizon Samsung Galaxy S 4] robj749840:
hey guys I have been working on this mod all day , going from SS with NC5 , the rom flashed over very well but when i got into the system it was not rooted, nor could I root with king root, towelroot, or anything. I was wondering if once we complete the flash over SS if the root should be applied with the kernal? Would you need to flash a pre rooted kernal to retain root access? Been searching this thread a lot not really coming up with a good solution. Right now I am sitting with safe strap ready to flash per the instructions again but i fear there will be no root when I get done again. Am I missing something? I found some other pre rooted stock OC1 images floating around the internet but I really like this ROM and would like to use it if I can gain root access. Thanks so much!!

Rob
[Verizon Samsung Galaxy S 4] Neffy27:
It comes rooted already, are you doing the final step, after 5?
[Verizon Samsung Galaxy S 4] klabit87:
did you set the supersu prompt to grant?

if you truly have lost root then you will need to odin back to nc5 and start over.
[Verizon Samsung Galaxy S 4] stang5litre:
I want to say thanks to [MENTION=401740]Gregory[/MENTION], [MENTION=224158]joshua[/MENTION], [MENTION=1590737]edger[/MENTION] and [MENTION=225372]Gary[/MENTION] for your Donations they are Greatly!!! Appreciated !!! Please send me your screen name so I can update OP. ??
[Verizon Samsung Galaxy S 4] robj749840:
Thanks I saw that post but I wasn't sure if I misinterpreted it. The final step is a reboot according to the setup and I did that. I think I lost my root which is why I am going to try again.

When I flashed over SS I did NOT do an internal wipe, just factory reset. That is how you are supposed to do it correct so you do not wipe your rooted kernal?

Thanks

---------- Post added at 09:24 PM ---------- Previous post was at 08:44 PM ----------

Got er working now, thanks guys!
[Verizon Samsung Galaxy S 4] Beej1970:
No I don't. I used the lollipop one from gigle. Works very well.

Sent from my SCH-I545 with stang5litre Edition 5.0 on stock OC1
[Verizon Samsung Galaxy S 4] Clarke33:
OK I'm back up and running and getting ready to try flashing again. On FF should I swipe away everything except wipe, rom, kernel, and supersu, including the everoot and boot boxes? I left them the first time so I'm trying to figure out what I did wrong.
[Verizon Samsung Galaxy S 4] Neffy27:
It indicates what you're asking in the op.
[Verizon Samsung Galaxy S 4] oraixearl:
For ff follow the op exactly. There's a screenshot of how it should look a few pages back. The problem has been how you go about replacing king root with SuperSU. Did you use the terminal emulator and script to change? You need to do that rather than supersume app
[Verizon Samsung Galaxy S 4] Clarke33:
Don't really think so. Step 11 mentioned everroot but I didn't see any mention of the boot normal box. Not trying to be a smart ass but I had something go wrong on the first flash and I'm trying to make sure I have covered all bases.
[Verizon Samsung Galaxy S 4] gadget!:
Here is an animated gif of the animation, it plays one time then good to a loop of a subtle animation just to let you know it's still booting and not hung.

I posted a revert zip a few pages back in case you want to go back.

sent from a Galaxy far far away.
[Verizon Samsung Galaxy S 4] Clarke33:
OK. Maybe that is what happened the first time. I used supersume. Even though I have supersu installed do I still need to use a script from the emulator?
[Verizon Samsung Galaxy S 4] EdrickMG:
Of1 is not supported yet? Thanks
[Verizon Samsung Galaxy S 4] oraixearl:
Yes run the script. Here, follow this - http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
[Verizon Samsung Galaxy S 4] NapalmDawn:
Thank you Gadget.
[Verizon Samsung Galaxy S 4] Clarke33:
OK. I'll try that before I flash again. Thanks