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.
Related
Hi everyone! I need some help updating my S4. I rooted it awhile back and I'm very much of the mindset of "if it ain't broke, don't fix it," so since it was doing everything I wanted, I've just left it alone and kept dismissing the prompt to install the OTA update. Now I'm having some issues and want some features of the newer versions of Android, so I was looking around for the best way to update it while keeping my root access. All the guides I can find, however, talk about upgrading from 4.3 to 4.4 or 4.2 to 4.3. So I was wondering...
1. What version should I update to? On my last phone, a Droid Bionic, one of the big Android version updates ran so horribly on it that I ended up getting a new phone. Because of that, I'm very nervous about updating my phone and having the performance suffer.
2. There must be a way to go straight from 4.2.2 to whatever version I choose, right? Do I need to go dig up some old guides on how to update my phone so that the most recent guides are relevant?
I hope I'm not being a super noob about this. I tried Googling around, and I'm pretty tech savvy but just haven't had the time to keep up with recent developments, so some guidance would be very helpful!
About my phone:
Verizon Galaxy S4
Model #: SCH-I545
Android version: 4.2.2
Baseband version: I545VRUDMI1
Thanks so much!
Find out what base band you have, MDK, ME7?
If MDK, install recovery download rom.
Anything other check this thread out:
http://forum.xda-developers.com/showthread.php?t=2735172
Advice, better read about the bugs and issues each version has. Once you go up, you cannot go back. Not ever, no never.
Sent from my SCH-I545 using XDA Free mobile app
Well if he is one of those few lucky MDK people he could hop around versions as he please. But most of them already know that *Grin*
Sent from my SCH-I545 using XDA Free mobile app
Batttie said:
Find out what base band you have, MDK, ME7?
If MDK, install recovery download rom.
Anything other check this thread out:
http://forum.xda-developers.com/showthread.php?t=2735172
Advice, better read about the bugs and issues each version has. Once you go up, you cannot go back. Not ever, no never.
Click to expand...
Click to collapse
I put the baseband version of my phone in my original post. It's I545VRUDMI1. Or am I missing something? So that means I should use Odin to flash whatever rom I decide to go with, right? So if I went with something like this 4.4.4 Google Play Edition I can use Odin to put it on my device? But then if I decide I don't like that rom for whatever reason, I can't redo it with any roms based on an earlier version (4.4.2, 4.3, etc), but other 4.4.4 roms would work?
Thanks so much for the help!
Toubabi said:
I put the baseband version of my phone in my original post. It's I545VRUDMI1. Or am I missing something? So that means I should use Odin to flash whatever rom I decide to go with, right? So if I went with something like this 4.4.4 Google Play Edition I can use Odin to put it on my device? But then if I decide I don't like that rom for whatever reason, I can't redo it with any roms based on an earlier version (4.4.2, 4.3, etc), but other 4.4.4 roms would work?
Thanks so much for the help!
Click to expand...
Click to collapse
You need a custom recovery to flash that Play Edition ROM which is not possible with your MI1 baseband.
dodgingpixels said:
You need a custom recovery to flash that Play Edition ROM which is not possible with your MI1 baseband.
Click to expand...
Click to collapse
So how do I know/find which roms will work?
Toubabi said:
So how do I know/find which roms will work?
Click to expand...
Click to collapse
Here's a pretty good thread explaining the different basebands.
http://forum.xda-developers.com/showthread.php?t=2578569
OK, I think I'm starting to get it. So should I use Odin to flash the rom listed under "Recover by re-flashing stock" in this thread? Or should I use safestrap? What's the difference?
Pretty much as the title says.
I just signed up with Verizon last Thursday. Updated on first boot to NK1. Then went and did the instructions for rooting NK1 and adding Safestrap. Now I am seeing that it seems I cannot do anything with this phone? Should I downgrade to be able to install CM11/12 or other ROMs? Is this even possible?
Thanks for the help.
thchipmunk said:
Pretty much as the title says.
I just signed up with Verizon last Thursday. Updated on first boot to NK1. Then went and did the instructions for rooting NK1 and adding Safestrap. Now I am seeing that it seems I cannot do anything with this phone? Should I downgrade to be able to install CM11/12 or other ROMs? Is this even possible?
Thanks for the help.
Click to expand...
Click to collapse
Sorry to break it to you but CM isn't possible for you. Basically, safestrap is your only option. If you want CM, you will need to by a used mdk s4.
Raymondlikesroot said:
Sorry to break it to you but CM isn't possible for you. Basically, safestrap is your only option. If you want CM, you will need to by a used mdk s4.
Click to expand...
Click to collapse
Yeah, that's what I gathered. I do have safestrap installed and installed the official CM11 nightly, as well as another rom but neither one really work. Should it?
As the post that you quoted said, cm isn't possible w/ out a phone that has a mdk bootloader, opposed to nk1, nc5, etc
thchipmunk said:
Yeah, that's what I gathered. I do have safestrap installed and installed the official CM11 nightly, as well as another rom but neither one really work. Should it?
Click to expand...
Click to collapse
Only touchwiz based roms, and a few aosp roms, work with safestrap. tldr: no.
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?
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
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.