Hello everyone,
SO I have the Verizon Galaxy S4, Model NUmber SCH-I545
As the title states, I want to try to install a custom ROM, one based on Lollipop, but I've never done anything like this before, and am concerned with certain things:
1 - Are there even many ROMs based on Lollipop that are stable, and wont be a hassle/annoyance?
2 - I've never flashed a ROM before, am not familiar with the process and have heard bad things about Verizon Samsung phones when it comes to these type of things.
I will give you guys all the info I can though.
First off, I AM rooted. I rooted my S4 using towelroot. It was scary easy. Downloaded towelroot from phone browser, let it do its thing. Checked with root checker, then downloaded SuperSU and Titanium Backup, Greenify etc. Thats all Ive done with root.
So what this means is that everything else on my phone is completely stock. Besides the fact that I am rooted by means of towelroot, and I use a Nova launcher, not TouchWiz plus other aesthetic stuff like a custom icon theme (which I doubt matters here), everything on the phone is completely stock.
I did kinda mess around with deleting some verizon bloatware with titanium backup though. Honestly cant remember what I deleted, I just remember I was pretty careful about downloading pre installed apps that I never used, like amazon services and verizon services, no android system things. Phone works fine. Except that there has been a Verizon software update that just will not work no matter what I do. It doesnt give me a detailed enough error message to find out what the problem is. I think it is a verizon update and not an android update. It will boot into recovery and look like the update works, but the progress bar stops and update always fails. This has been present for months now at this point.
So, with this information, what should I do if I want to install say, the CyanogenMod 12 nightly build for the Verizon galaxy s4? Is installing this rom worth it? Ive heard nightly builds can be annoying and buggy. I dont really want that, but would like Lollipop, or at least would like to try CyanogenMod. I think CM 10.2 based off Jelly Bean is the most recent that is deemed "stable" for the verizon S4.
Im sorry for the length of this post, but please, if someone could hold my hand and baby me through this I would appreciate it so much.
Thank you and I look forward to hearing from someone.
You can, it depends on what buildnumber/bootloader you have.
If you are running the MDK build of android (settings --> about device --> build number --> last few letters/numbers) then you can flash any rom made for the S4, but you will have to use the Loki exploit found at http://forum.xda-developers.com/showthread.php?t=2292157 . If you are running the latest version (NC5, NJ6, NK1) then you have to use Safestrap as your custom recovery found at http://forum.xda-developers.com/showpost.php?p=56030788&postcount=2281 . You can't flash any lollipop ROMS using safestrap, unfortunately.
Oh i see. Well i just checked my phone and it is one of the builds that requires safestrap like you said. Is it possible to install the MDK?
connorjb said:
If you are running the MDK build of android (settings --> about device --> build number --> last few letters/numbers) then you can flash any rom made for the S4, but you will have to use the Loki exploit found at http://forum.xda-developers.com/showthread.php?t=2292157 . If you are running the latest version (NC5, NJ6, NK1) then you have to use Safestrap as your custom recovery found at http://forum.xda-developers.com/showpost.php?p=56030788&postcount=2281 . You can't flash any lollipop ROMS using safestrap, unfortunately.
Click to expand...
Click to collapse
Oh i see. Well i just checked my phone and it is one of the builds that requires safestrap like you said. Is it possible to install the MDK?
People are working on an exploit which allows you to install MDK but as of now there is no way
connorjb said:
People are working on an exploit which allows you to install MDK but as of now there is no way
Click to expand...
Click to collapse
Oh ok, well alright thanks. Hopefully this will be possible soon. If it takes long enough my contract is up so ill just get a new phone
Related
Hi,
I have a Verizon Samsung Galaxy s4 with build number JSS15J.I545VRUEMK2, and I recently rooted it so I could run the Google Play Edition Rom. From various threads and guides I knew that I needed to use SafeStrap because you can't use CWM recovery on an MK2 device. After a couple of attempts installing the GPE Rom, I found out that the GPE roms i could find only work with SafeStrap and an ME7 device. Furthermore, I found out that the only ROM that works with and MK2 device is Hyperdrive 11. I was wondering if there is any way around this or, alternatively, if there are any plans to fix this.
Thanks in advance.
walkerna22 said:
Hi,
I have a Verizon Samsung Galaxy s4 with build number JSS15J.I545VRUEMK2, and I recently rooted it so I could run the Google Play Edition Rom. From various threads and guides I knew that I needed to use SafeStrap because you can't use CWM recovery on an MK2 device. After a couple of attempts installing the GPE Rom, I found out that the GPE roms i could find only work with SafeStrap and an ME7 device. Furthermore, I found out that the only ROM that works with and MK2 device is Hyperdrive 11. I was wondering if there is any way around this or, alternatively, if there are any plans to fix this.
Thanks in advance.
Click to expand...
Click to collapse
First of all. .the only way around is to hope our devs who pretty much do the work on their spare time...look at what can be done...Second their nothing broken that needs a fix.
If you want ability to load different roms buy the dev phone.
safestrap enabled, Hyperdrive driven
decaturbob said:
First of all. .the only way around is to hope our devs who pretty much do the work on their spare time...look at what can be done...Second their nothing broken that needs a fix.
If you want ability to load different roms buy the dev phone.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Thanks for the reply,
Just for clarification, are you saying that if I load hyperdrive, then I'll be able to load the GPE rom with safestrap?
Thanks
walkerna22 said:
Thanks for the reply,
Just for clarification, are you saying that if I load hyperdrive, then I'll be able to load the GPE rom with safestrap?
Thanks
Click to expand...
Click to collapse
Can't run gpe..
safestrap enabled, Hyperdrive driven
Would this work?
http://forum.xda-developers.com/showthread.php?t=2343355
dogginsteed said:
http://forum.xda-developers.com/showthread.php?t=2343355
Click to expand...
Click to collapse
You need a custom recovery to load any ROM. Problem with the build you are running is you cannot install a custom recovery because the bootloader is locked down tighter than Fort Knox. Devs are working on a solution and hopefully they will succeed. Don't hold your breath though as it may take a long while.
Until then, you can root, uninstall and de-crapify the bloatware and crapware from the phone. Change the launcher to GEL and get something closer to a GPE phone. Done all this to my S4 and it runs much more smoothly and gives me excellent battery service.
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
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
vaindil said:
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
Click to expand...
Click to collapse
its not possible. ONLY mdk builds will work.
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
vaindil said:
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
Click to expand...
Click to collapse
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Surge1223 said:
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Click to expand...
Click to collapse
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
Yep
Sent from my my Lollipopped S4
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
you can install hyperdrive rom
its not lolipop but its worlds better then stock ...
also there is a chance of getting the 5.01 GPE edition rom running when Samsung releases the lolipop update for the vz s4
that would at least give us a working lolipop kernel to use with the gpe rombase
and hey you never know there could be a exploite in the lolipop rom/kernel that lets us get kexec working
Basically safestrap loads after the kernel but early enough to replace point to a different root for the system. So we can load what ever system we want... But are stuck with the kernel the phone booted. If the system is based on the stock kernel this is fine... But when it starts making calls to custom kernel stuff you will have trouble.
So Cyanogenmod only provides the GUI? I've installed CM on two B&N tablets and I've been asked to root a new Verizon Samsung Galaxy S4. I've assumed that, because it's new, it will have I545VRUFNK1 4.4.2. I rooted my VSG s3 years ago to 4.3 and there was no going back on that one. It looks like it's the same with VSG s4. So, if CM provides only the GUI, then a rooted VSG s4 can still access Google Apps? What is the concern with with TW based ROMs? Is it the recovery/backup feature or only being stuck with the VSG s4 GUI?
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
This explains why I bricked my phone when I tried to flash CM12...
ryant35 said:
This explains why I bricked my phone when I tried to flash CM12...
Click to expand...
Click to collapse
haha yeah, that could maybe potentially probably be the issue. Just maybe.
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Lockett said:
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Click to expand...
Click to collapse
Nope, in order to get CM, you'll need to be on MDK. Samsung prevents downgrading.
btw. the baseband version doesn't matter much. Its the bootloader version that is the toughie.
Boo! I just picked up my S4 yesterday after a 5 month run of using Windows Phone so I'm trying to figure this phone out. I'm on NK1 and trying to figure out how to root now.
vaindil where did you find a VRUFNK1 compatible version of Safestrip?
So I have had my S4 since about a month after launch. Not long afterwards I received the OTA notification. I rejected it and froze the SDM.APK and stopped getting the notification. Fast-forward to recently. I am thinking about getting a stereo for my truck that has Google Auto, but my phone is not compatible. I believe it is because I am running version 4.2.2. Is there a way that I can upgrade to Lollipop, keep root and keep my current apps installed?
Thanks,
Dan
bumpncarstereo said:
So I have had my S4 since about a month after launch. Not long afterwards I received the OTA notification. I rejected it and froze the SDM.APK and stopped getting the notification. Fast-forward to recently. I am thinking about getting a stereo for my truck that has Google Auto, but my phone is not compatible. I believe it is because I am running version 4.2.2. Is there a way that I can upgrade to Lollipop, keep root and keep my current apps installed?
Thanks,
Dan
Click to expand...
Click to collapse
Best thing you can do is install the Custom CyanogenMod 13 ROM for S4 KitKat.
Sent from my SCH-I545 using Tapatalk
bumpncarstereo said:
So I have had my S4 since about a month after launch. Not long afterwards I received the OTA notification. I rejected it and froze the SDM.APK and stopped getting the notification. Fast-forward to recently. I am thinking about getting a stereo for my truck that has Google Auto, but my phone is not compatible. I believe it is because I am running version 4.2.2. Is there a way that I can upgrade to Lollipop, keep root and keep my current apps installed?
Thanks,
Dan
Click to expand...
Click to collapse
chaotic_jose said:
Best thing you can do is install the Custom CyanogenMod 13 ROM for S4 KitKat.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If you're still on MDK bootloader, you can flash TWRP and then install a custom ROM. CM 13 works. I also like OctOS 6.0.
If you're on any other bootloader, however, you're stuck with safestrap and TouchWiz-based ROMs.
flamadiddle said:
If you're still on MDK bootloader, you can flash TWRP and then install a custom ROM. CM 13 works. I also like OctOS 6.0.
If you're on any other bootloader, however, you're stuck with safestrap and TouchWiz-based ROMs.
Click to expand...
Click to collapse
How do I find out what bootloader I am on? In the about phone it says "Secure Boot Status Type Samsung" Also my baseband Version is I545VRUAME7
If my research so far is correct, looks like I am stuck with safestrap and touchwiz based roms?
It may matter, I am on Verizon.
Thanks
Dan
bumpncarstereo said:
How do I find out what bootloader I am on? In the about phone it says "Secure Boot Status Type Samsung" It may matter, I am on Verizon.
Thanks
Dan
Click to expand...
Click to collapse
When you go to Settings --> About Phone, the last three letters of your Baseband version are what we're talking about. If it ends with MDK, you can bypass the security checks on the locked bootloader via the Loki patch.
Edit
Just saw your update. Yeah, you have the ME7 bootloader, which means you're out of luck for non-TW ROMs. Sorry. Check the ROM List for Safestrap-compatible ROMs. The Safestrap thread has instructions on how to use it.
flamadiddle said:
When you go to Settings --> About Phone, the last three letters of your Baseband version are what we're talking about. If it ends with MDK, you can bypass the security checks on the locked bootloader via the Loki patch.
Edit
Just saw your update. Yeah, you have the ME7 bootloader, which means you're out of luck for non-TW ROMs. Sorry. Check the ROM List for Safestrap-compatible ROMs. The Safestrap thread has instructions on how to use it.
Click to expand...
Click to collapse
Thanks for the information.
flamadiddle said:
When you go to Settings --> About Phone, the last three letters of your Baseband version are what we're talking about. If it ends with MDK, you can bypass the security checks on the locked bootloader via the Loki patch.
Edit
Just saw your update. Yeah, you have the ME7 bootloader, which means you're out of luck for non-TW ROMs. Sorry. Check the ROM List for Safestrap-compatible ROMs. The Safestrap thread has instructions on how to use it.
Click to expand...
Click to collapse
Famadiddle
I installed safestrap with no problem. I am looking at the list of available roms and there doesn't appear to be many options for me. I am coming from a stock 4.2.2 and it seems that they require you to come from 4.4.x, the one that specifically say ME7, the download link was out of date. Am I misinterpreting the pre-req's? With a custom rom, do you have to stay within your version? IE i have to stay 4.2.2, and I can't go to 4.4?
Thanks again.
Edit,
So I bit the bullet and installed this one here:
http://forum.xda-developers.com/showthread.php?t=2415780
don't really see what all the commotion was about. everything was still the same, seems to have installed over top of my stock rom. It did install something though because the about phone screen has different stuff in it.
Dan
bumpncarstereo said:
Famadiddle
I installed safestrap with no problem. I am looking at the list of available roms and there doesn't appear to be many options for me. I am coming from a stock 4.2.2 and it seems that they require you to come from 4.4.x, the one that specifically say ME7, the download link was out of date. Am I misinterpreting the pre-req's? With a custom rom, do you have to stay within your version? IE i have to stay 4.2.2, and I can't go to 4.4?
Thanks again.
Edit,
So I bit the bullet and installed this one here:
http://forum.xda-developers.com/showthread.php?t=2415780
don't really see what all the commotion was about. everything was still the same, seems to have installed over top of my stock rom. It did install something though because the about phone screen has different stuff in it.
Dan
Click to expand...
Click to collapse
AFAIK, you can install other versions of (Safestrap-compatible) ROMs. If you only install ME7 ROMs, then you're only getting modified versions of the same stock software you already had. I have not used Safestrap myself, so your questions about it will get better answers on the Safestrap thread.