yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Redflea:
I thought that Lollipop fixed the SD card access/write issues by allowing apps to access both their folders and other folders on the SD card. Several articles I just saw in a search confirm that.

So is this edit still required? I haven't been blocked from moving files around w/Root Explorer.

Regarding the above edits, the first two are already there in my platform.xml file.

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

<group gid="sdcard_r" />

<group gid="sdcard_rw" />

</permission>

The media permission is in the permission below:

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

<group gid="media_rw" />

</permission>

So it looks like the edits aren't necessary on lollipop, or am I missing something?

Thanks.
[Verizon Samsung Galaxy S 4] sinner822:
Don't look the same to me.

But if it is working. Run with it.

Wasn't working on mine. Titanium Backup wouldn't backup to sd card.
[Verizon Samsung Galaxy S 4] Redflea:
Interesting, zero issues with TB for me.
[Verizon Samsung Galaxy S 4] muniz_ri:
May be your custom kernel?
[Verizon Samsung Galaxy S 4] mike.s:
Ditto. I just had to change to "Document Provider Storage" under Backup Location.
[Verizon Samsung Galaxy S 4] npjohnson:
Some manufacturers have it fixed.
[Verizon Samsung Galaxy S 4] PMac10000:
Running hot after upgrade?

For those who find their battery draining at an alarming rate after Lollipop upgrade, and their phone feeling noticeably hotter when it didn't before... In my case, I found that "Exchange Service" was the culprit, sucking around 20% of the battery... draining it at twice the pre-upgrade rate. I recommend following the steps in this thread, specifically the post by "demonashes" : http://forums.androidcentral.com/t-galaxy-note-2/327810-battery-drain-issue-exchange-services-data.html

The problem is with the Exchange server, rather than your phone's client SW. But it's easily fixable, and after fixing, Exchange battery usage dropped from 20% to about 3%, and my phone cooled off right away. Good thing too, because I wouldn't suffer through a phone with such a poor battery life.

In my opinion, this is a serious problem that Microsoft and Android need to solve ASAP, otherwise their plan for corporate dominance dies a quick death of embarrassment.
[Verizon Samsung Galaxy S 4] waffleking:
Infrared IR Blaster now broken

I have been running this Lollipop upgrade for about a week. Everything is running great except I noticed that now the IR Blaster is NOT working!

muniz_ri, Can you look into fixing this?
[Verizon Samsung Galaxy S 4] woodardhsd:
Not sure what steps you mean. What is this wipe at the top, not the bottom? The instructions don't say anything about wiping.

I didn't do any of this until yesterday morning. The instructions that are there now were the ones I used to try to flash. I'm 100% sure I followed the instructions.
[Verizon Samsung Galaxy S 4] newkydawg:
Mine works fine with WatchOn so pretty sure it's not a "Muniz" issue.
[Verizon Samsung Galaxy S 4] tst1212:
muniz_ri you rock!

I was on NK1 with Safestrap, on Stock Slot, no other slots used. Followed the simple instructions and got the v5, thanks!

Quick question, do we need to disable anything to make sure we don't get OTA updates that might remove root?
[Verizon Samsung Galaxy S 4] muniz_ri:
Try again, keep in mind FF is still BETA so it may fail once in a while.
[Verizon Samsung Galaxy S 4] dgutierrez04:
Freeze SDM on system apps.
[Verizon Samsung Galaxy S 4] JeeperDon:
I, and it appears others, are annoyed that the lockscreen isn't as robust as the prior 4.4.2. A long while ago I had used Teslacoil's 'WidgetLocker Lockscreen' (same people making Nova Launcher), so I put it back on. Status bar is back with icons and I have on-lockscreen icons to kick off a couple specific apps. and a weather widget too. :D
[Verizon Samsung Galaxy S 4] PizzZak:
Woke up this morning to an update notification and by 10 AM I am upgraded and root with no problems. Thank you muniz_ri! :good:
[Verizon Samsung Galaxy S 4] tst1212:
No option to Disable/Freeze.

I assume renaming the SDM.apk to SDM.bak, then reboot should cover it? That way if I wanted an OTA, could just reverse?
[Verizon Samsung Galaxy S 4] dgutierrez04:
Yes that is correct. You can also do that. And like you say just reverse it back when you want the OTA Update.
[Verizon Samsung Galaxy S 4] Redflea:
never heard of this being kernel related, so doubtful.

I don't remember having to do anything, but it could well be I made that change in TiBU and have just forgotten. However root explorer never had any issues.

From what I've read, apps need to be updated to work with the new lollipop security on SD card writing. So it could be that some folks are using apps that haven't been updated yet where as the ones I've been using have been updated for the support.

The fix is actually provided in the Android lollipop Code by Google, (if you search you can find a response from the Google team regarding the SD card write issue and the fact that they were changing it in lollipop) so for it to be manufacturer-specific they would have to be removing that fix for some reason. That is possible of course. There a lots of annoying manufacturer changes to stock Android Code out there that continue to piss us off, right? :)

I switched to the Nine app, which provides excellent exchange syncing for emails, contacts, calendars, and tasks, etc., a nice UI, and also different exchange security options too. Its really nice, you should take a look at it if the built in exchange app bothers you too much.

Check out the Next lockscreen replacement. It's actually made my Microsoft, surprisingly, but it's really quite good, has some nice features, allows you to add icons to launch different apps from the lock screen , depending on where you are, and many other customizations. Quite well done.
[Verizon Samsung Galaxy S 4] LockdownInc:
Group Message issue

Has anyone had the issue of "Group Messages" not going out unless the "Group Message" checkbox is unchecked. Texts sent as individual messages go through, but not as a Group Message. Other than that and that it took me 3 trys to the the update to "stick", the 5.01 has worked good.

Any ideas what the issue is with the "Group Messages" not being sent?
[Verizon Samsung Galaxy S 4] sinner822:
Many have had an issue with sd card write. So to say the problem was corrected by Google would be incorrect.
[Verizon Samsung Galaxy S 4] mikeandamy1013:
OP worked great for me. no issues to report.

thanks to all that worked on this!!
[Verizon Samsung Galaxy S 4] npjohnson:
You may have downloaded the old ROM (that doesn't auto wipe the device), and flashed it assuming it was. Re-download, and try again following the OP instructions.
[Verizon Samsung Galaxy S 4] Redflea:
The fix requires apps to be updated to use the new process...Some may not be updated to do so, intentionally or otherwise. So even if it's perfect, mileage may vary. :)

I have had no issues personally with writing to the SD card.
[Verizon Samsung Galaxy S 4] sinner822:
Guess we will all sit back and be impatient about the next Rom you code.
[Verizon Samsung Galaxy S 4] tshelby73:
Installing this ROM is a complete wipe not an upgrade correct?

Is this the same as stock update with all the included apps just with root?

Thanks

Sent from S4 using the better than it was then they jacked it again Tapatalk
[Verizon Samsung Galaxy S 4] muniz_ri:
Correct, the ROM will wipe all data and is completely stock.
[Verizon Samsung Galaxy S 4] Mo6152:
I keep getting stuck on the Samsung Screen. I tried twice now.

I loaded ChainFire and added the zip as instructed, then started the process. Am I missing something? I attained root on NC5 and followed this method to retain my root.

I downloaded yesterday, so it's not the old copy of the ROM.
[Verizon Samsung Galaxy S 4] muniz_ri:
If you can go back to NC5 and stand by. I am trying to get to the bottom of these failures and will upload a new ROM shortly.
[Verizon Samsung Galaxy S 4] muniz_ri:
The new ROM has been added to the OP.
[Verizon Samsung Galaxy S 4] Mo6152:
Thanks. Just out of curiosity, what did you change?
[Verizon Samsung Galaxy S 4] muniz_ri:
Only the way the script mounts and unmounts system in an attempt to find the optimal script for FF.
[Verizon Samsung Galaxy S 4] Mo6152:
I see. I looked at the zip file and the script it contains. So is the zip basically different files from different versions of the official ROMs put together (old bootloader files with new other ROM files) and a script to install them? Or are there other custom content other than the scripts (custom meaning not straight from Samsung)?

I haven't been following the Android dev scene for a few years.
[Verizon Samsung Galaxy S 4] muniz_ri:
Hmm...not even close, lol. Let me know if the latest version works for you. Good luck!
[Verizon Samsung Galaxy S 4] tshelby73:
Worked perfect for me with the version before last. I did a clean Odin to nc5 before upgrading.

Sent from S4 using the better than it was then they jacked it again Tapatalk
[Verizon Samsung Galaxy S 4] wetwaterdog:
FYI....started with odin and installing the full wipe NC5 download. including pit file install (prior to that I removed my sd card and did a full format).

installed Tr for root. then Supersu (supersu indicated a fail to disable Knox, but i just ignored the message...seems fine...not sure what I should have done?)

installed Flashfire and then followed directions for wnk4_bl file....

flashed tetheraddon, and life is good....everything seems fine....

only thing I notice so far is when connected to say voicemail, on speaker, and entering pw or codes, speaker cuts out....

Other than that, so far, all is well.....thanks!
[Verizon Samsung Galaxy S 4] muniz_ri:
Thx, yes it works the vast majority of times. The problem that I am trying to solve for is that 1 in 100 time when it will hang upon reboot after flashing. It may just be a bug in FF.
[Verizon Samsung Galaxy S 4] abrusco:
I followed all the steps, i am rooted on NC5 with HyperDrive rls20 and safestrap installed

Now the phone gets stuck on Samsung Logo for 30minutes.

Any solution?
[Verizon Samsung Galaxy S 4] muniz_ri:
See the post right above yours. Try pulling battery then reinserting. Other than that the solution is to Odin back to NC5 and start over. I will add note to the OP.
[Verizon Samsung Galaxy S 4] abrusco:
Reinsert battery not work for me.

Install nc5 ( http://xdaforums.com/showthread.php?t=2735172 ), root , install supersu and star over.

Everything Ok now!

Thanks!!!

One question: In 4.4.2 i use app MoreLocale 2 to Enable hidden languages on verizon, but dont work in 5.0. Is there any other option?
[Verizon Samsung Galaxy S 4] Dudash:
I just wanted to throw in my 2 cents about the whole "wiping before flashing" deal, I've used Muniz's methods to update 2 Verizon S5's to both of the Lollipop updates they've released and I just used this method to update my brother's Verizon S4 to Lollipop. I even used his first method that involved installing the ROM and then restoring your backed up data in Safestrap and I can confirm that the same method works for FlashFire. At least for me. Before following his instructions, I back up my data partition in FlashFire, then proceed with the update and after it fully boots, I restore the data partition in FlashFire and everything works fine after Android fully loads up. It is most likely a "better safe than sorry" method by wiping everything but I just wanted to let everyone know that if you wish to try to backup and restore your data after the update, it may very well work and save you loads of time reinstalling and re-setting up your phone.
[Verizon Samsung Galaxy S 4] RJswanee:
What if Odin isn't working to flash NC5?

I've tried time and again to flash NC5 through Odin. It says it succeeds, and the phone reboots, but then it's stuck in an eternal boot loop that requires a factory reset to stop. Wiping the cache partition doesn't solve the problem. Any help would be greatly appreciated!

I'm running NK4 build (I've avoided 5.0.1 as of yet, but it's trying to Lollipop my phone). I've tried using Odin v3.07 and v3.09. I've tried flashing CF Auto-Root, to no avail (Odin gives me a FAIL! (Auth) message with that). I can't even flash it back to NK1. Help!
[Verizon Samsung Galaxy S 4] sinner822:
Download a fresh full wipe NC5 file. Make sure not to rename the file. If you use no wipe it will bootloop.
[Verizon Samsung Galaxy S 4] RJswanee:
Finally Got It

Thank you very much. I finally got it to stay on long enough, enough times, to get Towelroot to successfully root my phone. Flashed NK1 (couldn't find an NK4) back on once it stayed on long enough to get confirmation from Root Checker that it was rooted. NK1 flash worked fine. Phone is now successfully rooted, running 4.4.2.
[Verizon Samsung Galaxy S 4] natethegreat86:
VRUGOC1

I'm wondering if anyone is working on an actual root method for this firmware, obviously there's a way to keep root but what about the rest of us that were already stuck on this firmware and have no way of gaining root. Please muniz or someone save the rest of us stuck without root or those who foolishly took an ota etc. There's had to be vulnerabilities in 5.0.1 that can be leveraged to gain root.
[Verizon Samsung Galaxy S 4] skepticmisfit:
galaxy s6 has a root exploit called ping-pong root now, it wasn't indicated to support other devices yet, but there's a bit of hope for you guys. next time, be patient
[Verizon Samsung Galaxy S 4] alv24:
I cant get Bluetooth to work
[Verizon Samsung Galaxy S 4] xtacybyme:
Thanks for this,

i just came from safestrap, rooted

Worked great!

Just a quick question please...

do we need to worry about updates? and loosing root? can updates be disabled?

Thanks
[Verizon Samsung Galaxy S 4] i8qbert:
Updates can be "disabled" by moving SDM.apk out of the system/app folder. I like to create a folder on my SD card named back up apps and put it there in case I ever need it. You will need a root file manager to do it. I like root explorer personally.
[Verizon Samsung Galaxy S 4] BoulderGeek:
No success for me

Coming from rooted NC5 with NG6 modem package. Every thing has been stable and fine for months, but I have been waiting for 5.x with root and tether.

Followed OP instructions. Got new Samsung 5.0 splash animation, but then permanent hold (and hot battery) on the red Verizon boot screen. Battery out, reset, back to Odin for NC5 reinstall.

Tried it again, this time fiddling with the Flashfire options, reboot menu, etc. Same result.

Flashing via Odin back to NC5 went fine. Just need to freeze the OTA. Unsure why I am not having success when so many people get it to work the first time?
[Verizon Samsung Galaxy S 4] muniz_ri:
if you decide to try again, from NC5 flash the ROM with safestrap. No need to wipe. Let me know if that works for you.
[Verizon Samsung Galaxy S 4] BoulderGeek:
Well, now I have rendered the phone unusable.

I'm at work, and my Odin PC is at home. I thought that I could do it all with what I had on my phone storage. Safestrap 3.73 wouldn't install right, and failed to give the SS recovery chooser. So, i went to SS 3.71.

From SafeStrap 3.71, I could get into TWRP and flash OC1 rooted .zip. On boot, it does get past the red Verizon splash. You get a ton of "Unfortunately..." FCs. it never comes up to lock screen or desktop. Just remains black.

I can boot to recovery, and it says that the recovery mode is OC1. I can't access the built in storage, only the sdcard. unfortunately, internal is where my zip files are. For whatever reason, SafeStrap doesn't interject, now, so I am stuck with stock recovery and no SS. Ah, I get it, I am on OC1 and that's normal for OC1 & SS.

So, until I can odin back to NC5 again, I am phoneless. :( Grr.

EDIT: So, i see that the problem is that SafeStrap 3.71 (which is the only version which will work) cannot mount or umount /system. So, any zips which i try to flash from SS go to /dev/null.

Any way around this? i'd rather have tether on rooted NC5 than OC1, if I have to choose.
[Verizon Samsung Galaxy S 4] G.moe:
If you knew what you were doing, that wouldn't be a concern. Unless you have another phone to use, wait until more research is done with this.
[Verizon Samsung Galaxy S 4] yellowcooln:
That's the plain.
[Verizon Samsung Galaxy S 4] muniz_ri:
Update....a tester flashed the OC1 bootloader after flashing the rom to confirm it would resolve the wifi issue. Test failed, the issue seems more complex. Stay tuned....
[Verizon Samsung Galaxy S 4] carzaddict:
What is the lowest baseband version that can be used for this?

I am running NC5 rooted
[Verizon Samsung Galaxy S 4] jam0688:
awesome work you guys! great to see the test sip up for lollipop. sucks that wifi isnt working though. imma wait till the issue is resolved though before i try. is there a way to create a flashable zip of the oc1 modules that would maybe fix the wifi? i know in the past versions of stock its been a kernel or module issue. im probably sure youve guys have thought of that though so ignore this if you have lol anyways keep up the good work.
[Verizon Samsung Galaxy S 4] gildan27:
I'm on MK2.

When you say that the NK4 bootloader allows for downgrading your firmware at any time, does that mean I could take the OTA update to Lollipop (loosing root), downgrade to MDK, then re-root per http://wiki.cyanogenmod.org/w/Install_CM_for_jflte and install whatever ROM I want? Does the tripped qfuse mentioned on that page not apply to downgrades from NK4, or am I misunderstanding what is being said?
[Verizon Samsung Galaxy S 4] CAG-man:
Flashfire has a backup feature but this likely will not help you for your concern. However you can try to backup the data partition only in Flashfire. Others may not agree with me, I however have found KIES (now SmartSwitch) to be my best friend. When upgrading to Lollipop from KitKat keeping root on the various Galaxy devices. It will backup all your data and then will transfer it in when you are on Lollipop. Flawless everytime.
[Verizon Samsung Galaxy S 4] muniz_ri:
I have only confirmed that the NK4 bootloader allows a full Odin downgrade to NC5. I have not looked into firmwares prior to NC5.

If you take the OC1 ota update, which will also update your bootloader to OC1, you will no longer be able to do a full Odin downgrade to any previous firmware versions.

Additional note added to the OP.
[Verizon Samsung Galaxy S 4] yellowcooln:
Thanks! I will use that when updating to Lollipop.
[Verizon Samsung Galaxy S 4] xprobert:
how do I get my wifi tether working again
[Verizon Samsung Galaxy S 4] npjohnson:
Didn't want to quote the OP, for WiFi, have you tried hot rebooting? That fixes WiFi on AOSP style ROMs on the TW kernel. Another one to try would be from a root terminal, to lsmod and see if the WiFi (dhd) module loads. If it does, "rmmod dhd.KO" and then run "insmod dhd.KO" and see if WiFi start funtioning.
[Verizon Samsung Galaxy S 4] muniz_ri:
I do not own the device so unable to try but others should definately try.
[Verizon Samsung Galaxy S 4] N4styN1ghtm4r3:
Alright, so here us my situation and I would be thankful for any help and/or advice. I had the s4 flashed to a fresh nk1 install, trying to get the update. I don't have a Sim card because it isn't activated, so I thought maybe that is why I couldn't get it. I tried kies and software update, which just says it is temporarily unavailable repeatedly. So, I took a risk and updated with the first part of the update using the update.zip that's being posted. It was successful and I am now on nk4 baseband. I still can't get the ota update, temporarily unavailable, and kies says I'm up to date, initialize and upgrade firmware says it isn't supported.

So what can I do now, it would be nice to obtain and keep root using this method, though obviously I heavily rely on wifi. I don't find it necessary to have root for now though, I know a new method will be found. I just want to get it to lollipop, one way or the other. I forgot to mention I have tried verizon upgrade assistant as well, with no luck.

Any suggestions?
[Verizon Samsung Galaxy S 4] Charlie115:
Please don't take this wrong but I almost think this might want to be moved to the developer thread cause that would be a more positive outcome by people that know what they're doing and would save on the redundant " MY WIFI IS NOT WORKING HOW CAN I FIX IT" !! LMFAO
[Verizon Samsung Galaxy S 4] muniz_ri:
Lol, regardless of location I believe that is unavoidable.
[Verizon Samsung Galaxy S 4] muniz_ri:
Moved to OP.
[Verizon Samsung Galaxy S 4] jam0688:
Great job muniz. Imma go ahead and download and install and ill let ya know what happens. And what's working and what's not. What changes were made in difference from the first test build?
[Verizon Samsung Galaxy S 4] muniz_ri:
I completely recreated the rom to make certain no mistakes were made. Also updated to SuperSU BETA v2.49.

Someone may also want to flash with Safestrap after a full wipe to eliminate the possibility that FF is the issue. If so you will need to boot into download mode after flashing and flash the I545_OC1_Stock_Kernel.tar.md5 in Odin.
[Verizon Samsung Galaxy S 4] jam0688:
Awesome. I got it downloading now. Wifi is pretty slow so it's gonna take a bit lol. Will post results when I can and let you know.

---------- Post added at 10:09 PM ---------- Previous post was at 09:57 PM ----------

Aight. I gotcha Muniz. Will report back.
[Verizon Samsung Galaxy S 4] JFam5:
Fully up and running! Good work Muniz_ri. Everything you do for the Galaxy line is appreciated.

So far everything is working as advertised.

Thanks!

I used the flashfire method and it was fine. Phone got really hot during Art build but nothing to do with your work.
[Verizon Samsung Galaxy S 4] natethegreat86:
That's good news that there's hope and I didn't take an over the air this s4 was given to me already updated unfortunately :( I'll keep an eye on the ping pong development, fingers crossed maybe that will be our ticket.
[Verizon Samsung Galaxy S 4] alv24:
Has anybody else been able to get viperforandroid to work
[Verizon Samsung Galaxy S 4] xelim317:
This is awesome. Thanks for the work!

I was wondering where that slimmer version was though. I downloaded the rom in the OP, but it was not debloated like you said it was earlier. Perhaps you didn't debloat this version?

Again, thanks for the work. It's running great so far.

Also, does anyone know the best way to customize now that we don't have access to xposed?
[Verizon Samsung Galaxy S 4] xtacybyme:
Thank You!
[Verizon Samsung Galaxy S 4] ForevermanRGPC:
I was on echo 39.1, SS 3.72. All I did was back up in TB, factory wipe, flashed rom, and most importantly flashed OC1 kernel in Odin..no problems or issues everything works. Debloted with TB..did both mine and my wife's in about 20 minutes. Been running for a week, thanks for this.
[Verizon Samsung Galaxy S 4] SnyderGuy:
Worth It?

Is it worth it to upgrade from a heavily modified kitkat (HyperdriveRLS21) with xposed to this stock rom?

Is there a list of known issues?

Is EchoeROM v49 reliable enough to flash after this?

I'm all ready, I have 2 nandroids (Safestrap 3.7.5 and Flashfire), a full titanium backup, manual/cloud backups of all my media. Is it really worth it? I've heard it's amazingly smooth and pretty but I'm also reminded of the lack of customization (such as no transparent recents..)
[Verizon Samsung Galaxy S 4] ForevermanRGPC:
Recents,drop down and app drawer are transparent
[Verizon Samsung Galaxy S 4] Bwanna:
OMG. but it works. Started from NK4

I took the FIRST OTA update and ended up with NK4. DAMN!

This is what I did.

1. Copy I545_OC1_Stock_Rooted_ROM_wNK4_BL.zip to your SD card

2. ODIN Full NC5 Wipe. (don't both with no wipe it produces errors)

3. Installed and ran Towelroot, then rooted

4. installed SuperSu (free) and ran that. VERIFY YOU HAVE ROOT

5. Installed FlashFire and installed I545_OC1_Stock_Rooted_ROM_wNK4_BL.zip

(https://www.androidfilehost.com/?fid=23991606952601185)

viola' It works.

Here are the instructions for Flashfire: http://www.droidviews.com/install-lollipop-on-verizon-galaxy-s4-and-keep-root/