Description
Edit: as of 11/9/14 these zips are broken. Their Updater Binary was corrupted in the zipping process. I would not recommend using these as of now, and I am away from my PC till next week, will fix it when I get back.
Hey Guys,
I noticed quite a few people asking about NG6 ROM's and why there is a lack thereof.
Well... NG6 and Safestrap don't get along. And the NG6 Kernel is buggy and causes random reboots, and although these can be fixed through XPosed.... why upgrade to something that is less stable than what you already have?
Not all in NG6 is bad though... the Modem/Non-HLOS/Recovery/System Apps do have some perks, like better LTE Support, a much speedier switch between WiFi/LTE/CDMA, for Verizon Support reasons, your Recovery will state NG6, Kid's Mode, and some other upsides.
So I present... The Unified Custom ROM NG6 Partial Updater!
It upgrades your Recovery*/Non-HLOS***/Modem/System Apps** to NG6 from any firmware!
*=Not included in MDK version
**= Not ready for human consumption yet (need some more time to compare files to that of Hyperdrive/Eclipse/etc.)
***=Only Included in the version for the NG6 Bootloader
This /DOES NOT/ Upgrade your BootLoader, and you will be just as ready for @Surge123 an Co.'s Kexec as anyone on NC5 will.
Tested on
MDK- - Perfect; Tested by a bud on MDK, not much to report because all the MDK version does is upgrade Modem , tested on the CM/AOSP Hybrid in the Org. Dev. Section.
MI1 - Untested
ME7 - Untested
MK2 - Perfect; Had to flash Gogolies NG6 WiFi Fix as well... but thatwas most likely due to ROM Compatibility, tested on Eclipse 3.0 (4.2.2 Version)
NC5 - Perfect (My combo of choice, Eclipse 4.0.2)
NG6 - Perfect (Duh. Stock ROM)
Credits
@Surge123 for pulling the Modem and NON-HLOS, @gogolie for the WiFi Fix, Myself for pulling Recovery.img, and I used @Muniz-ri 's Recovery Updater-Script to check out how NON-HLOS is flashed.
Instructions
Flash via Safestrap -- If on 3.72 (Any Variant) click "Remove Recovery" from inside your current Safestrap (Because 3.72 DOES NOT work with this!) and install 3.75 for the SCH-i545 (If looking to run a 4.4.x ROM), or 3.71 for the SCH-i545 (If looking to run a 4.3.x ROM), also, in my own finding, if you are on @Surge1223's 3.82 Beta w/ Kexec, it works as well.
MDK: https://drive.google.com/file/d/0B1rm1VFiz_2FWE1jbHJLdkRWak0/view?usp=sharing
ME7-MI1-MK2-NCx: https://drive.google.com/file/d/0B1rm1VFiz_2Fdl9rRGF3UEtMV00/view?usp=sharing
NG6: https://drive.google.com/file/d/0B1rm1VFiz_2FMzNhVE02bFdZQWs/view?usp=sharing
XDA:DevDB Information
Unified Updater, Tool/Utility for the Verizon Samsung Galaxy S 4
Contributors
npjohnson, npjohnson, Surge1223, gogolie/giglie, Muniz_ri
Version Information
Status: Stable
Current Stable Version: 0.1
Stable Release Date: 2014-11-03
Current Beta Version: 0.2
Beta Release Date: 2014-11-09
Created 2014-11-04
Last Updated 2014-11-03
I did this like a month-ish ago... Why is this just now being posted?
Nonetheless, good work.
SnyderGuy said:
I did this like a month-ish ago... Why is this just now being posted?
Nonetheless, good work.
Click to expand...
Click to collapse
Well I am sure that there are 100's of people still on an NC5 ROM that haven't done anything with NG6.
I actually debated putting a note to senior members that said something like "Yes. You could have done this for yourself, this is for junior members and new people." XD
npjohnson said:
Well I am sure that there are 100's of people still on an NC5 ROM that haven't done anything with NG6.
I actually debated putting a note to senior members that said something like "Yes. You could have done this for yourself, this is for junior members and new people." XD
Click to expand...
Click to collapse
Nah, what you posted was fine the way it is nice to see people contributing around here :thumbup:
npjohnson said:
Well I am sure that there are 100's of people still on an NC5 ROM that haven't done anything with NG6.
I actually debated putting a note to senior members that said something like "Yes. You could have done this for yourself, this is for junior members and new people." XD
Click to expand...
Click to collapse
I was just surprised this was just now being posted, I figured this had been done by everyone. But your post was of up-most quality either way
Am I able to update? I'm rooted and have safestrap 3.71 installed and working. I just want to get a little more current with the base I am running. Sure do feel like I am way way past due and seeing all the new awesome android releases, I am sort of envious . Can anyone help me out with info on how I would go about getting up to the latest and greatest version?
P.S. Also would like to fix the issue with not being able to move or delete/edit etc files on my external SD. I am only able to when using Root Browser but even then it isn't consistent.. At all!
fafinaf said:
Am I able to update? I'm rooted and have safestrap 3.71 installed and working. I just want to get a little more current with the base I am running. Sure do feel like I am way way past due and seeing all the new awesome android releases, I am sort of envious . Can anyone help me out with info on how I would go about getting up to the latest and greatest version?
P.S. Also would like to fix the issue with not being able to move or delete/edit etc files on my external SD. I am only able to when using Root Browser but even then it isn't consistent.. At all!
Click to expand...
Click to collapse
Ok, to do what you want, upgrade to NC5 (with Odin or OTA), because this isn't bootloaders, or non-hlos. To get those either OTA or Odin to NC5.
Related
SCH-i545 (VZW GS4) - I haven't updated to KitKat (4.4) because I'm concerned that each upgrade is going to make the bootloader even harder to unlock. Right now, I'm on MK2. I'd like to have KitKat, and I'd like to go with CyanogenMod (can't...bootloader), and my attempt at trying SafeStrap and Hyperdrive ended with me having to reload the stock ROM. I'm sure I screwed it up somewhere. I've never had any issues loading CyanogenMod on any of the other phones I've rooted (HTC Eris and HTC Incredible 2). As much as I'd like to upgrade my OS, I don't want to do it at the expense of the ability to load whatever ROM I choose.
Patiently waiting for the bootloader to get cracked open,
David
There are 10 types of people in the world: those who understand binary and those who don't.
What safestrap version and what hd version were u using?
Sent from my SCH-I545 using Tapatalk
SS version 3.71, not sure of the Hyperdrive version. SafeStrap loaded fine; it was when I attempted to put Hyperdrive on that things went awry. I know I had the latest available versions when all this was done on 10 March 14.
There are 10 types of people in the world: those who understand binary and those who don't.
KaHOnas said:
SS version 3.71, not sure of the Hyperdrive version. SafeStrap loaded fine; it was when I attempted to put Hyperdrive on that things went awry. I know I had the latest available versions when all this was done on 10 March 14.
There are 10 types of people in the world: those who understand binary and those who don't.
Click to expand...
Click to collapse
Most of us never had issues with install of hd..when people did have issues usually bad downloads or selection of too many options in aroma....hd 15 was very stable for 4.3...mk2 users..though I went with Baja rom v 1.34 in the end before moving onto kitkat platform.
Sent from my SCH-I545 using Tapatalk
Hey check out this thread it allows you to upgrade to 4.4.x while retaining your bootloader. If you need extra help pm me. I'll help with installing hyperdrive 16
Thanks, both of you. I know I screwed something up with the HD install. I've never used SafeStrap before. I'm fairly confident with CWM and CyanogenMod, though. I chalk it up to inexperience.
Thanks for the offer as well, jake.99x3. When I get ready to do it again, I'll look you up.
And, what was that link for the KitKat upgrade sans bootloader update?
There are 10 types of people in the world: those who understand binary and those who don't.
KaHOnas said:
Thanks, both of you. I know I screwed something up with the HD install. I've never used SafeStrap before. I'm fairly confident with CWM and CyanogenMod, though. I chalk it up to inexperience.
Thanks for the offer as well, jake.99x3. When I get ready to do it again, I'll look you up.
And, what was that link for the KitKat upgrade sans bootloader update?
There are 10 types of people in the world: those who understand binary and those who don't.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2726868#52094900
If you wanna stick on MK2 bootloader surges method does not change the bootloader. You can go from 4.3 to 4.4 and back and forth. I did it this weekend. As long as you dont OTA to NC5 (ur bootloader changes to NC5). So if ur staying on mk2 hoping it gets cracked u can still stay on it and go to kitkat and then back down to 4.3 lol
Q&A for [ROM][Official][4.4.4] CyanogenMod 11.0 Nightlies for the Verizon Galaxy S4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth fixes in VRUFNG6
I saw today that Verizon released an updated build (VRUFNG6) that supposedly contains bluetooth fixes. Does anyone know if these are going to be Touchwiz-specific and/or if they could be pulled and incorporated into the current CM11 nightlies?
Many are reporting terrible bluetooth connectivity and related issues, so just thought I'd ask.
consultcory said:
I saw today that Verizon released an updated build (VRUFNG6) that supposedly contains bluetooth fixes. Does anyone know if these are going to be Touchwiz-specific and/or if they could be pulled and incorporated into the current CM11 nightlies?
Many are reporting terrible bluetooth connectivity and related issues, so just thought I'd ask.
Click to expand...
Click to collapse
They have been "kangbanged" from NF3 and merged today. You can see this awesome goodness in the 10/13 nightly.
See here:
http://www.cmxlog.com/11/jflte/
Look under to be included in next nightly. The new camera fix has also been merged.
Post Content Edited. Sorry, I was frustrated and had a moment of weakness.
The silence is deafening.
Just load m9. It's perfect. Eventually you'll lose the urge to Crackflash and enjoy your s4 for what it is (a pretty good 2 year old phone).
There are 4 v*rizon phones out there that 'do it for me'. I just need to figure out which one is the least 'Verizoned'. In really not too anxious though. I like my s4.
Installing Cyanogen on Verizon Galaxy S4
Hello all,
Now that this NG6 update recently pushed to my phone has made it practically unusable, I've decided it might be time to install a custom ROM. Alas, the handy Cyanogen "one-click" installer does not support my phone Since I'm new to this and really afraid of bricking my phone, I've come here just to get some assurance.
I've seen this post which gives instructions on how to install, but one thing concerns me. This link from the CM website gives pretty different instructions, and moreover adamantly warns that the build version of your phone must be I545VRUAMDK, which mine is not. Why the discrepancy in instructions?
Why is installing an alternate kernel necessary to obtain a root? Can Towelroot not be used (does that app involve installing an alternate kernel)? Is the motochopper app listed necessary to root the device in a "certain way"? Is the clockwork app the only CM supported app to make a recovery image, or can I use another standard like TWRP? And what part of this process that they list absolutely requires you to be on that build version???
I know, I have no idea what I'm doing. Please advise, or at least point me in the right direction! Also, I know the original post says that asking about rooting is off topic here, but it's only part of my question, and sort of relevant in this case because the official CM installation instructions suggest some kind of compatibility concern.
Many thanks!
I am running CM11 Nightly and the only modification I have made to the actual file system is deleting the DSP Manager apk in system/app because it was taking precedence over other equalizer apps I was trying out. Long story short, I couldn't find an equalizer that boosted the bass correctly as well as the equalizer built into the stock S4 Touchwiz did. So, I reflashed the DSP Manager apk through CWM. Now, neither Google Play Music nor Apollo will play my music on the external SD card. And for my last question, why are no equalizers working correctly with bass boost? When I have either a preset or use the bass booster slider bar in any equalizer (including DSP Manager) it just makes my music crackle. Its not my headphones either, as they worked perfectly on Touchwiz. Thanks in advance for your reply.
evesira said:
Hello all,
Now that this NG6 update recently pushed to my phone has made it practically unusable, I've decided it might be time to install a custom ROM. Alas, the handy Cyanogen "one-click" installer does not support my phone Since I'm new to this and really afraid of bricking my phone, I've come here just to get some assurance.
I've seen this post which gives instructions on how to install, but one thing concerns me. This link from the CM website gives pretty different instructions, and moreover adamantly warns that the build version of your phone must be I545VRUAMDK, which mine is not. Why the discrepancy in instructions?
Why is installing an alternate kernel necessary to obtain a root? Can Towelroot not be used (does that app involve installing an alternate kernel)? Is the motochopper app listed necessary to root the device in a "certain way"? Is the clockwork app the only CM supported app to make a recovery image, or can I use another standard like TWRP? And what part of this process that they list absolutely requires you to be on that build version???
I know, I have no idea what I'm doing. Please advise, or at least point me in the right direction! Also, I know the original post says that asking about rooting is off topic here, but it's only part of my question, and sort of relevant in this case because the official CM installation instructions suggest some kind of compatibility concern.
Many thanks!
Click to expand...
Click to collapse
Since it sounds like you updated to NG6 via a VZW OTA update CyanogenMOD is unfortunately out of your reach. CM needs a custom recovery such as CWM or TWRP and they can only be installed on a GS4 that is running the MDK bootloader. The later versions are locked down and only a SafeStrap compatible ROM can be installed.
FernBch said:
Since it sounds like you updated to NG6 via a VZW OTA update CyanogenMOD is unfortunately out of your reach. CM needs a custom recovery such as CWM or TWRP and they can only be installed on a GS4 that is running the MDK bootloader. The later versions are locked down and only a SafeStrap compatible ROM can be installed.
Click to expand...
Click to collapse
Thank you for the response. I actually solved my problems a couple of days ago. I'll post them here for posterity.
Regarding those Cyanogen instructions, they say that you should only attempt this on the MDK build, but they don't say why. Are the particular tools they suggest using incompatible? No, Cyanogen itself is only compatible with the MDK build of the I545 Verizon S4 (US), for the reasons that Fern explained above. Took me some forum snooping to actually determine that one.
For those who are going through the horrors of the NG6 update, but don't want to wait until the rumored fix in early December, do what I did. See this thread:
http://forum.xda-developers.com/showthread.php?t=2735172
The no-wipe version didn't work for me unfortunately. It booted with all my stuff still in tact, but errors constantly popped up making the phone unusable. I had to do the full wipe, which gets rid of all your apps and personal data (unless it's on the SD card I believe). So try the no-wipe first, and if it doesn't work, back up all your data and apps, then do the full wipe.
Download Odin 3.09 (no need to root first), and use the full wipe ROM from the thread and watch the video for instructions. That will get you back to NC5, the previous working version before the NG6 fiasco. However, you still need a way to stop the update from happening again. Oddly, some users get a "no thanks" option, but I didn't get that. I had to root, which I had never done before. On your phone, google towelroot, go to the site, click the lambda, download it, install it (in settings allow android to install apps from unknown locations other than the app store), press "make it rain". Still on your phone, install SuperSU from the app store and go through that process. Then buy the Titanium Backup Pro app from the app store, find the SDM.apk, and freeze it. This should stop the update prompt from happening!
Now that you had to wipe your phone and root it (possibly for the first time if you're like me), reinstall all your old apps and move your data back. And since you're now rooted, you might as well take advantage of it. Download the Xposed framework, and install some useful modules for it like Wanam, NoMapTips, Disable Clear Defaults Dialog, and more. Then you can get rid of a lot of annoying TouchWiz bull**** like "loud volume can damage your hearing" warning, low battery warning, and etc.
Hopefully this helps someone who has no Android "modding" experience like myself, and saves them some research.
Cheers
For clarity, the reason that you can only run CM on a MDK device is the MDK bootloader is the only one that can be exploited by a process called loki to allow flashing a custom recovery. All later bootloaders have had this exploit blocked (Thank Big Red). Because of this the only option is SafeStrap. On MDK ONLY this allows one to flash custom kernels and recoveries which are required in order to flash any AOSP ROM such as CyanogenMOD.
Cm11 m12/rc1
I can't remember where, but I read something about the next milestone build being available around November 7th, and that it may even be labeled as a release candidate instead. Obviously there's been no such release and the CyanogenMod blog hasn't been updated in almost a month.
Has anyone heard anything about a release date for M12/RC1?
consultcory said:
I can't remember where, but I read something about the next milestone build being available around November 7th, and that it may even be labeled as a release candidate instead. Obviously there's been no such release and the CyanogenMod blog hasn't been updated in almost a month.
Has anyone heard anything about a release date for M12/RC1?
Click to expand...
Click to collapse
I guess I should have just waited a day... M12 is now up!
At first glance on the download web page, I thought Galaxy S4 version is unsupported since the begining of the year. You should really post the information that you are building unified build to the download page.
xuhdev said:
At first glance on the download web page, I thought Galaxy S4 version is unsupported since the begining of the year. You should really post the information that you are building unified build to the download page.
Click to expand...
Click to collapse
Its hard to miss on the first page of the thread.
" CyanogenMod:
Nightly:*http://download.cyanogenmod.org/?dev...w&type=nightly
As of 20140218 we are doing unified builds. Get them here:
Unified Nightly:* http://download.cyanogenmod.org/?dev...e&type=nightly "
Sent from my SCH-I545 using Tapatalk
TMYINC said:
Its hard to miss on the first page of the thread.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If you know Cyanogenmod, you would probably go to the cyanogenmod download page directly but not visit from here, right?
xuhdev said:
If you know Cyanogenmod, you would probably go to the cyanogenmod download page directly but not visit from here, right?
Click to expand...
Click to collapse
I do know CM. That's why I know the download page has been different since Feb. 18th. I always stay I'm touch here for updates, bug reports, or just to answer questions. I wasn't trying to be rude.
Sent from my SCH-I545 using Tapatalk
TMYINC said:
I do know CM. That's why I know the download page has been different since Feb. 18th. I always stay I'm touch here for updates, bug reports, or just to answer questions. I wasn't trying to be rude.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I'm not saying you don't know. "You" means someone. Not everyone sees xda as official document; neither do I. But I found the official wiki, so the problem I mentioned should not be a problem.
Deleted
nobody here is responsible in any way if you break your phone. It was your fault. Figure it out yourself.
Before I begin, I would like to explain the usage of build numbers. There are 4 Kitkat firmwares and 2 Lollipop firmwares. The last three letters of the build number are used to identify the specific build (everything before that is device code stuff)
Kitkat builds are as follows:
NC5
NG6
NK1
NK4 (generally unused, as this was a preparation update for Lollipop)
Lollipop builds are as follows:
OC1
OF1
The easiest way to root is by being on a kitkat firmware and root the firmware itself using a kernel swap method, or downgrading to NC5 and using Towelroot.
OF1 IS ROOTABLE. CLICK HERE FOR INFO
OC1 is rootable through the usage of Kingroot (desktop version only): LINK HERE
YOU CAN NOT USE ANY CUSTOM RECOVERY (TWRP, CLOCKWORKMOD) WITH LOLLIPOP. NOT EVEN SAFESTRAP (it's too buggy and requires flashing the nc5 kernel to even get into)
(mdk users need not apply)
ROM info available in 2nd post.
Flashing ROMs
You can not flash CyanogenMod or any ROMs based off of its source code! Those are only for the MDK bootloader.
UPDATE: If you are on the OC1/OF1 bootloader, you can only flash TouchWiz Lollipop ROMs.
Two pretty solid ROMs for lollipop are:
[PORT][ROM] Albe95 S6 FULL PORT 4.6 [S6/Edge Plus/N5 FEATURE PORT] (UPDT 31/10/15)
stang5litre Ediition 5.0 OC1 MDK,SS,FF/OC1/OF1
I surely appreciate this post. Kit Pop was the only one that peaked My interest but after seeing this I will be back at it. The o.p.s often don't list if the rom is Safestrap compatible so I shy away.
Thanks
Nice write up and in for future updates on OC1 roms. Really hoping for an eclipse-style update to OC1. I hate touchwiz.
Sent from my Eclipse'd S4
Thanks
I can not get this goddamn Kingroot to work on OC1 Lollipop. Any suggestions guys? I've tried it a dozen times.
thesame here... i cannot get this Kingroot to work on my phone...
I read in this thread: http://forum.xda-developers.com/galaxy-s4-verizon/general/rooted-galaxy-s4-t3158098/page1 that it is possible, but nothing for me...
Nice.
I don't see Kitpop(I finally got my APN issues sorted out)
Someone Sticky this. I think I opened 15 threads with people saying they boned themselves with OC1... People need to know how cruel Verizon is.
hey guys
so Samsung has had this program for a while where they automatically update the security policy (specifically, SELinux, things relating to root privileges, etc) and they may have updated that system component to make kingroot not work. I was patient enough to stay on KitKat until some rooted lollipop ROMs came out, thus having the older bootloader so I can downgrade to nc5 and root that way. next time, all of you oc1 people who tried kingroot but failed, be patient!
if you are rooted and for some reason get a security policy update, you won't lose root. if you're not rooted and an update got rolled out to you, you're SOL. Samsung usually rolls these out without user intervention in the background
AYGM said:
thesame here... i cannot get this Kingroot to work on my phone...
I read in this thread: http://forum.xda-developers.com/galaxy-s4-verizon/general/rooted-galaxy-s4-t3158098/page1 that it is possible, but nothing for me...
Click to expand...
Click to collapse
So the PC version of king root worked for me. You'll have to guess what the buttons mean though because it's all in Chinese
will any of these roms work with flashfire and the oc1 update?
Eclipse (a TouchWiz KK ROM with a really thorough AOSP theme, my personal favorite)
HyperDrive RLS21 (TouchWiz Kitkat, super customizable
Empty Galaxy (you might like this guy's theming to TW, it's pretty awesome!)
firenemesis7 said:
will any of these roms work with flashfire and the oc1 update?
Eclipse (a TouchWiz KK ROM with a really thorough AOSP theme, my personal favorite)
HyperDrive RLS21 (TouchWiz Kitkat, super customizable
Empty Galaxy (you might like this guy's theming to TW, it's pretty awesome!)
Click to expand...
Click to collapse
no unfortunately. eclipse and hyperdrive are based off of KitKat and empty galaxy only works on the mdk bootloader at this time.
your options on oc1 are stang5litre edition and muniz_ri's stock/deodexed ROMs
So basically if I (actually a friend of mine) is on NK4 4.4.2, the best way to root is to upgrade to lollipop via the verizon OTA update, then use Kingroot to root?
But what if I want cyanogenmod on the phone? Should I root a different way...how?
pfunk26 said:
So basically if I (actually a friend of mine) is on NK4 4.4.2, the best way to root is to upgrade to lollipop via the verizon OTA update, then use Kingroot to root?
But what if I want cyanogenmod on the phone? Should I root a different way...how?
Click to expand...
Click to collapse
Don't do that!
There is a method to downgrade to NC5, gain root, and upgrade without losing root. Search the Dev forum.
Sent from my stang5litre Edition 5.0 using XDA Free mobile app
If you're past MDK (which NK4 is past MDK) you can't use CM. You can only use Safestrap ROMs for KK, and OC1 ROMs for locked bootloaders using Flashfire.
updated OP to reflect new OF1 update.
OF1 (minor update that mainly fixed the Stagefright bug) is not rootable and the qfuse counter has been increased, meaning no downgrading to OC1 (yet)
Almost October 2015, and still no hopes for an AOSP-styled Lollipop. :sad:
aleggsue said:
Almost October 2015, and still no hopes for an AOSP-styled Lollipop. :sad:
Click to expand...
Click to collapse
Agreed. Lollipop was a game changer, but seemingly in a bad way..
bkkzak said:
Agreed. Lollipop was a game changer, but seemingly in a bad way..
Click to expand...
Click to collapse
in my opinion, touchwiz became more usable, but for people who have locked bootloaders who want custom roms (like me) are basically stuck on KitKat. oh well at least I have a choice, sorry for those who don't.
Sent from my SCH-I545 using Tapatalk
I'm currenty using fre3 ROM version 2.26 4.4.4 NK4
My phone is starting to have issues so time to wipe and start again. I've been reading (for days as always) but there's more than the usual issues that happen when you're away from the site for a few months (links to dead ROMs etc) with devs getting booted for breaking rules. I missed all the drama!
Really looking for advice on a stable ROM with hotspot, and it'd be nice to have a MWM too. Preferably one where the thread is not locked and links are current. I've rooted a few phones over the years and am familiar with odin, but instructions are always good for someone at my (somewhat low) level of understanding.
syco123 said:
I'm currenty using fre3 ROM version 2.26 4.4.4 NK4
Click to expand...
Click to collapse
I just upgraded from MJ4 to the NK4 rom you're on (I'm always happy with freeza's work). I tried out Lollipop but ended up downgrading back to NK4 until OC5-OK2 roms seem worth flashing or until Xposed framework is fully supported. I'm also interested in what people would recommend as an upgrade. I've seen Sac's N5 Port mentioned a lot but I've yet to try it out.
Kompster said:
I just upgraded from MJ4 to the NK4 rom you're on (I'm always happy with freeza's work). I tried out Lollipop but ended up downgrading back to NK4 until OC5-OK2 roms seem worth flashing or until Xposed framework is fully supported. I'm also interested in what people would recommend as an upgrade. I've seen Sac's N5 Port mentioned a lot but I've yet to try it out.
Click to expand...
Click to collapse
I just reinstalled fre3 which will continue to do me fine. Disappointing after a year to not see an upgrade, but I'm not paying, so I'll take what I can get .
BTW Kompster I think Sacs was the Dev who got in trouble with mods. I tried Sacs Norma, but it wouldn't connect to network. I wasn't a fan of the ROM either so only played with it for an hour or so. I have it backed up, but returned to fre3.
Would still welcome advice/opinions on a more recent ROM.
UPDATE: SOLVED, as of 07 FEB 2016; I needed to find an .MD5-compiled ROM with an NC5 bootloader; my last working bootloader was NC5 and using Odin to flash ROMs with other bootloaders had failed.
My phone has been rooted for over 2 years now and I've run a handful of ROMs, with Hyperdrive probably the most stable of the lot. Last fall I was losing some functionality (bad microphone) and I figured I might as well try a new ROM in case that helped. I install CM 12 and life was okay. I set it to download updates (mistake) and it upgraded me from CM 12 to CM 13. Much as I like the new Marshmallow features, my S4 steadily degraded in function over time, to the point where I stopped making or receiving phone calls.
Last week half of my installed apps disappeared, and attempting to install anything through the Google Play store failed. No clue how that might happen, but I knew it was time to flash a new ROM.
That was when I discovered I could no longer boot into TWRP; it hung on the TEAMWIN logo screen. Then I started getting the Verizon screen claiming it had detected unauthorized software.
Since I could no longer operate the phone, I went ahead and put it into download mode and ran Odin3 v3.10.7 and used that to flash an OC1 ROM, the only one I had that was in .MD5 format.
Now I can't get past a bootloop that leaves me hanging at the Verizon logo screen.
Any thoughts?
What is your bootloader right now? And/or what was it while on Hyperdrive?
Edit: wait....I see where u Odin'd oc1...was it the stock image? If so u may have flashed the oc1 boot.img. If that's the case, I suggest you download FlashFire and read up on it. Because if u were on nc5 or anything before you should be able to ODIN back down. But if u have an oc1 bootloader you're permalocked.
Huh. I tried to respond to this hours ago. Didn't upload, apparently.
Anyhow, thanks for responding. I have not been able to get an .MD5 version of the stock image to flash. The only complete .MD5 I've successfully downloaded is called "I545VRUGOC1_Neutered_Full_Odin.tar.md5". The last ROM running on this device was CyanogenMod 13, which is Android 6 with NC5 kernel.
I'm currently attempting to download "VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5" but it is slow going.
As for FlashFire, how could I install it to my phone? I cannot get past the bootloop. Odin seems to be my only option for flashing at this point, right?
Have you tried going to recovery after flashing OC1? maybe there are some leftovers of previous process, if your phone can go into recovery you should try to do some wipes
Edgardo_Uchiha said:
Have you tried going to recovery after flashing OC1? maybe there are some leftovers of previous process, if your phone can go into recovery you should try to do some wipes
Click to expand...
Click to collapse
Great suggestion; unfortunately, TWRP is blocked by the Verizon notice now (the one that tells you Verizon's identified unauthorized software on the phone).
Okay, I'm going to try an NC5.MD5 that I was able to download. Here's hoping it moves this process forward....
I can help you! I have everything! PM me here, or send me a message on hangouts!
Sent from my SCH-I545 using Tapatalk
Cincinnatux said:
Huh. I tried to respond to this hours ago. Didn't upload, apparently.
Anyhow, thanks for responding. I have not been able to get an .MD5 version of the stock image to flash. The only complete .MD5 I've successfully downloaded is called "I545VRUGOC1_Neutered_Full_Odin.tar.md5". The last ROM running on this device was CyanogenMod 13, which is Android 6 with NC5 kernel.
I'm currently attempting to download "VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5" but it is slow going.
As for FlashFire, how could I install it to my phone? I cannot get past the bootloop. Odin seems to be my only option for flashing at this point, right?
Click to expand...
Click to collapse
You're on the right path. ODIN the nc5 full wipe. And from there you can use Safestrap to flash whatever. But I'm wondering if you've locked the bootloader to oc1 or of1. If that's the case, you can go to sammobile.com and register and sign-in and download any factory image flashable thru ODIN.
The nc5.md5 worked! It's not particularly stable (yet), but at least the phone boots up and seems to work.Thanks to those who took the time to read over the issue and offer suggestions!
May i ask how you had cm13 running on nc5? @Cincinnatux
klabit87 said:
May i ask how you had cm13 running on nc5? @Cincinnatux
Click to expand...
Click to collapse
Yeah me too?!...I was confused throughout this whole post, but I'm glad he took the advice and got nc5 full wipe. Does the trick everytime (on a downgradeable bootloader of course).
ATGkompressor said:
Yeah me too?!...I was confused throughout this whole post, but I'm glad he took the advice and got nc5 full wipe. Does the trick everytime (on a downgradeable bootloader of course).
Click to expand...
Click to collapse
Perhaps I am mistaken. I had NC5 the last time I had checked, which was when I installed CM12. Sometime around December or so CM12 upgraded itself to CM13. The only thing I remember having to change was GAPPS, moving that from 5.1 to 6.0.
Cincinnatux said:
Perhaps I am mistaken. I had NC5 the last time I had checked, which was when I installed CM12. Sometime around December or so CM12 upgraded itself to CM13. The only thing I remember having to change was GAPPS, moving that from 5.1 to 6.0.
Click to expand...
Click to collapse
Regardless of whether it was CM12 or CM13, I would still like to know how you did it and where you got the files from.
Thanks.
klabit87 said:
Regardless of whether it was CM12 or CM13, I would still like to know how you did it and where you got the files from.
Thanks.
Click to expand...
Click to collapse
While I used to troll XDA for ROMs, for CM I'm sure I went to their website and downloaded whatever was current at the time, which was a Lollipop ROM. I used TWRP to install, but I no longer have any of my notes for that install so I couldn't verify any of this, really.
Cincinnatux said:
While I used to troll XDA for ROMs, for CM I'm sure I went to their website and downloaded whatever was current at the time, which was a Lollipop ROM. I used TWRP to install, but I no longer have any of my notes for that install so I couldn't verify any of this, really.
Click to expand...
Click to collapse
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
klabit87 said:
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
Click to expand...
Click to collapse
That's what I was assuming as well. When I had the s3, I was able to install a cm Rom thru Safestrap. Actually the other thread we were in by mohammad.afaneh, he was a dev on the Safestrap for s3 and got it to support a cm Rom, but it didn't have working data signal or Wi-Fi.
ATGkompressor said:
That's what I was assuming as well. When I had the s3, I was able to install a cm Rom thru Safestrap. Actually the other thread we were in by mohammad.afaneh, he was a dev on the Safestrap for s3 and got it to support a cm Rom, but it didn't have working data signal or Wi-Fi.
Click to expand...
Click to collapse
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
klabit87 said:
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
Click to expand...
Click to collapse
I don't think it was kexec. But go to the s3 forums and/or search his afh. We could probably modify it, or figure out exactly what he changed and incorporate it into the SS we have. Depending on what he changed, it may be possible to implement nc5flasher, gain support for AOSP bases (aka get them to boot). But in order to have a fully functional modem/firmware, the kernel would need to be built from source. I do know there is a thread (I think in s4 unified development) on a proof of concept project that will enable insecure modules on locked bootloaders. I could be wrong about the actual forum it's in and exactly what's involved. I believe it can be done, it's just gonna take many minds focused on a common goal with positive intent.
PS. There's a bounty and it would be nice if we could do it.
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
SORRY FOR HIJACKING YOUR POST @Cincinnatux!!!!!
klabit87 said:
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
Click to expand...
Click to collapse
No, he modded CM enough to work with SS...
klabit87 said:
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
Click to expand...
Click to collapse
Just to reduce my ignorance a little, maybe one of you can point out the error in my thinking/memory. I thought NC5 vs MDK vs OC1 was whatever was listed in About Phone as the Baseband Version, right? While my phone was MDK at the time of purchase (July 2013), I changed the baseband a few times while upgrading to newer flavors of Android. My current baseband is I545VRUFNC5, which is what I remember it being last fall as well. Where am I mistaken? Thanks!
Cincinnatux said:
Just to reduce my ignorance a little, maybe one of you can point out the error in my thinking/memory. I thought NC5 vs MDK vs OC1 was whatever was listed in About Phone as the Baseband Version, right? While my phone was MDK at the time of purchase (July 2013), I changed the baseband a few times while upgrading to newer flavors of Android. My current baseband is I545VRUFNC5, which is what I remember it being last fall as well. Where am I mistaken? Thanks!
Click to expand...
Click to collapse
Baseband does not equal bootloader.
You can update the baseband no problem but can't update the bootloader without being able to go back.
There is an app that you could use to check your bootloader called samsung phone info I believe our something like that.