I just got an S4, and it seems like the I545VRUFNG6 model is quite new, correct?
I've rooted it, but can anyone confirm that there are no custom kernals,ROMs, or recoveries for this model yet, right? I guess I'll have to wait until they are developed? If there are ROMs and kernals for this model, could someone point me in the right direction? I can't seem to find any.
Thanks
There are no custom recoveries and you should stick with the stock kernel only. If you are rooted, then try and install Safestrap and pick a ROM to try out. Make sure to backup your stock slot first if you decide to use it.
Endalyor said:
I just got an S4, and it seems like the I545VRUFNG6 model is quite new, correct?
I've rooted it, but can anyone confirm that there are no custom kernals,ROMs, or recoveries for this model yet, right? I guess I'll have to wait until they are developed? If there are ROMs and kernals for this model, could someone point me in the right direction? I can't seem to find any.
Thanks
Click to expand...
Click to collapse
Have you tried Safestrap 3.75? That is supposed to work with the ng6 update
Hightower24 said:
Have you tried Safestrap 3.75? That is supposed to work with the ng6 update
Click to expand...
Click to collapse
I do have safestrap 3.75, it works, but I can't find any ROMs that work
I downgraded to NC5, and still I can't get any ROMs to work properly.
What isn't working?
Hightower24 said:
What isn't working?
Click to expand...
Click to collapse
There seems to be problems with the wifi, and also some ROMs, after turning on, an error box would pop up saying something like android.process has stopped, and won't go away, etc. I've been trying to fix a SIM car problem, as I've posted in another thread, but I'm thinking it must be a hardware problem...But it's unrelated to the SIM card reader, because I've tried replacing that twice now. Oh well, guess it's the motherboard.
Use giglie's wifi fix and that will get the wifi working. Which rom is giving you the fc's?
Related
Is this downgrading from ME7 to MDK possible? If so please guide me in the right direction.
Its not possible... Once you take the update theres no going back...
Sent from my SCH-I545 using xda premium
So I am new to the s4 and rooting. I really want to install the Hyperdrive ROM. I have been researching and researching what to do and I think i have found my answer for now and im not happy about it.
From what i gathered, since i installed the update and I am now on ME7, there is no root method bc they locked the phone down. Is this correct?
hondabomdc5 said:
So I am new to the s4 and rooting. I really want to install the Hyperdrive ROM. I have been researching and researching what to do and I think i have found my answer for now and im not happy about it.
From what i gathered, since i installed the update and I am now on ME7, there is no root method bc they locked the phone down. Is this correct?
Click to expand...
Click to collapse
Use the search button...this has been posted about a 1000 times...but yes you can root it but no custom recovery.
hondabomdc5 said:
So I am new to the s4 and rooting. I really want to install the Hyperdrive ROM. I have been researching and researching what to do and I think i have found my answer for now and im not happy about it.
From what i gathered, since i installed the update and I am now on ME7, there is no root method bc they locked the phone down. Is this correct?
Click to expand...
Click to collapse
You can root, but cant install custom recoveries or roms.
bfmetcalf said:
You can root, but cant install custom recoveries or roms.
Click to expand...
Click to collapse
Thanks for being kind and thanks for the info. I did state that I was new and have been looking. I could have started a whole new thread but instead asked the question in here. I do want to install the Hyperdrive rom but since with ME7 you cant install roms...looks like i wont be rooting until somebody gets this figured out. Again, thanks for being cool and answering my question.
y can't we just odin back to mdk?
Stauf99 said:
y can't we just odin back to mdk?
Click to expand...
Click to collapse
because of the bootloader will only allow signed packages to be installed on the phone and checks against older firmware and will not allow it. Unless you have the signed key you ain't flashing anything unless we find a workaround.
magneticzero said:
Use the search button...this has been posted about a 1000 times...but yes you can root it but no custom recovery.
Click to expand...
Click to collapse
So why is there ROMs for the ME7 build if they can't be flashed?
This [email protected] sucks!
So, I'm stuck on ME7 as well (32GB S4, otherwise I'd just go down to the store and swap it, complaining about something -- seems they don't stock them at any local corporate stores).
I'm coming from a Samsung Galaxy Nexus, and we have OMAP-Flash, which is like a low-level PROM flashing tool from the Samsung R&D team, and I could fix even a DEAD, or bricked phone with that. Is there something like that here to get back the original bootloader? I cant believe we're stuck on this crap... How 'bout a 2nd-init like my Droid-x days, or something slick like SafeStrap on the RAZR family?
...Just thinkin' "out loud".
IMGetwired said:
So, I'm stuck on ME7 as well (32GB S4, otherwise I'd just go down to the store and swap it, complaining about something -- seems they don't stock them at any local corporate stores).
I'm coming from a Samsung Galaxy Nexus, and we have OMAP-Flash, which is like a low-level PROM flashing tool from the Samsung R&D team, and I could fix even a DEAD, or bricked phone with that. Is there something like that here to get back the original bootloader? I cant believe we're stuck on this crap... How 'bout a 2nd-init like my Droid-x days, or something slick like SafeStrap on the RAZR family?
...Just thinkin' "out loud".
Click to expand...
Click to collapse
Short answer is 'no' - you're currently stuck with root as your best option. Hopefully this will change in the not-too-distant future.
Sent from my SCH-I545 using xda app-developers app
Yeah, this does suck.
Seems like we need someone to pick up the Dragonboard 8074 development kit to help us figure this out...even then, I'm sure Samsung has so many mods in there it'd be nuts to reverse engineer... Ugh, I'm so impatient! :silly:
Slimfast35 said:
So why is there ROMs for the ME7 build if they can't be flashed?
Click to expand...
Click to collapse
Because there for people that didn't get robbed by Samsung and update through the evil over the air update lol
Slimfast35 said:
So why is there ROMs for the ME7 build if they can't be flashed?
Click to expand...
Click to collapse
You're not quite understanding what a rom is and is not. There is no such thing as a rom for ME7. There are roms that use the ME7 base. They are flashable only by those who have the MDK bootloader. When a build number is listed for a rom, it is the build that the rom is based from.
Sent from my SCH-I545 using Tapatalk 4
Slimfast35 said:
So why is there ROMs for the ME7 build if they can't be flashed?
Click to expand...
Click to collapse
The ROM's that the devs based on MDK have been updated with the ME7 code just like any good developer does. But the bootloader those users have is still from their MDK (original) install. Once you go ME7 you can never go back, downgrade, crossgrade or get beyond the bootloader, for now anyways. Someone will find a way.
Nm
hey guys whats going on.. its been a long time since i had a GS4.. i ended up switching to the LG G2 so my time is focused on them forums..
my father has a gs4 and he uses it 95 percent of the time for work. his bluetooth MUST be able to work in his truck for work.
he had no problems when he was on 4,2... Ever since he switched to 4.3, weird things started to happen. on outgoing calls only, it would ring twice and then it would say "call complete" and it would throw the call off bluetooth... the call still goes through in the phone, however it ends on the bluetooth.. it happens on 70% of the calls he makes..
After tracking down this issue, and let me remind you, the bluetooth is the stock one that comes in dodge trucks (UConnect), i came up with this.... the dealer said the software on the bluetooth was up to date.... verizon replaced his s4 with another one. We got the other one and same issue. As another test, i used my mothers s4, which is on 4,3, and guess what?? same problems.. I then tried my G2 running 4.4 and it works fine.. I tried another rooted s4 that wasnt on 4.3 ,and that worked flawlessly as well... We tried all our phones on another bluetooth device and they all work. It just seems like that UConnect doesnt like something in android 4.3... I reseached a little more on the dodge forums and to my surprise i seen this..
http://www.wranglerforum.com/f40/android-4-3-issues-with-uconnect-472897.html
It seems like the issues lie on android 4.3 and a CDMA network phone..
So i read everything in this forum about how the recovery/root works and i see that this update locked down the bootloader bad and we cant go back, and i must use safestrap for anything custom.
So where do i go from here? Is there any way to safestrap a 4.2 rom, while staying on my 4.3 baseband successfully? Given my problems that i said above, im very open to suggestions. I need to get everything working for my dad.. Thanks in advanced!
joemagistro said:
he had no problems when he was on 4,2... Ever since he switched to 4.3, weird things started to happen. on outgoing calls only, it would ring twice and then it would say "call complete" and it would throw the call off bluetooth... the call still goes through in the phone, however it ends on the bluetooth.. it happens on 70% of the calls he makes..
http://www.wranglerforum.com/f40/android-4-3-issues-with-uconnect-472897.html
It seems like the issues lie on android 4.3 and a CDMA network phone..
Click to expand...
Click to collapse
You have to be on 4.2 to be able to run 4.2 as far as I know. Anyone please feel free to correct me, I won't mind. I wanted to run 4.2.2 AOSP roms on my safestrapped Verizon Galaxy S4 and I couldn't get it past the boot screen. I do believe however that you if you can find a stock rom for 4.2 that has the better version of bluetooth, you might be able to push it to system/app. I wish you luck.
SwiftLeeO said:
You have to be on 4.2 to be able to run 4.2 as far as I know. Anyone please feel free to correct me, I won't mind. I wanted to run 4.2.2 AOSP roms on my safestrapped Verizon Galaxy S4 and I couldn't get it past the boot screen. I do believe however that you if you can find a stock rom for 4.2 that has the better version of bluetooth, you might be able to push it to system/app. I wish you luck.
Click to expand...
Click to collapse
interesting.. im not sure what changed from 4.2 to 4.3 as far as bluetooth, but if its something that can easily be pushed, im curious to know.. soo suggestions are welcomed.. thanks!
joemagistro said:
interesting.. im not sure what changed from 4.2 to 4.3 as far as bluetooth, but if its something that can easily be pushed, im curious to know.. soo suggestions are welcomed.. thanks!
Click to expand...
Click to collapse
Well I've tried flashing it on Safestrap MK2. I know you can't downgrade from MK2, which is the 4.3 update I believe. You can try hyperdrive on safestrap. It's still 4.3 on RLS12 but the base is MJ7 so maybe that will do something? You need safestrap 3.7.1, baseband modules from the safestrap OP or website, and Hyperdrive RLS12.
I can't suggest it as I have not done it, but you can also try pushing a 4.2 version of uconnect on 4.3 stock. Just remember to backup the 4.3 uconnect in case anything goes sideways.
SwiftLeeO said:
Well I've tried flashing it on Safestrap MK2. I know you can't downgrade from MK2, which is the 4.3 update I believe. You can try hyperdrive on safestrap. It's still 4.3 on RLS12 but the base is MJ7 so maybe that will do something? You need safestrap 3.7.1, baseband modules from the safestrap OP or website, and Hyperdrive RLS12.
I can't suggest it as I have not done it, but you can also try pushing a 4.2 version of uconnect on 4.3 stock. Just remember to backup the 4.3 uconnect in case anything goes sideways.
Click to expand...
Click to collapse
uconnect isnt in the phone.. its the name of the bluetooth device in the truck.. the phone connects just by turning the phones bluetooth on..
and what do i hear about people flashing roms, such as hyperdrive, and playstore doesnt work??
joemagistro said:
uconnect isnt in the phone.. its the name of the bluetooth device in the truck.. the phone connects just by turning the phones bluetooth on..
and what do i hear about people flashing roms, such as hyperdrive, and playstore doesnt work??
Click to expand...
Click to collapse
I guess it would depend on your device model... I've never had a single issue with Hyperdrive 12 or 13 on my verizon mk2 i545
SwiftLeeO said:
I guess it would depend on your device model... I've never had a single issue with Hyperdrive 12 or 13 on my verizon mk2 i545
Click to expand...
Click to collapse
just for the helll of it, ill root the phone, safestrap it and go with hyperdrive.. ill see if that changes anything... the rls13 is updated to mk2 firmware?
joemagistro said:
just for the helll of it, ill root the phone, safestrap it and go with hyperdrive.. ill see if that changes anything... the rls13 is updated to mk2 firmware?
Click to expand...
Click to collapse
Yes it is. Use saferoot so you don't trip KNOX. If you need to reset to stock for warranty just search vzw samsung galaxy s4 stock mk2
I am sorry to be so damn noobish but i need help lol... Ive watched so many youtube videos with josh dew and read so many posts and downloaded so many roms. I know I am probably missing just one step and if someone can help me I would be so appreciative.
my note 3 is rooted with twrp installed. i want to change my rom , my main goal is to get unlimited hotspot unlocked.... when i try to install a rom it says KERNEL is not SEANDROID ENFORCING, I then put it all back to stock then root then install twrp.
I think i have maybe a wrong kernel? What do I need to do?
TheWreckHER said:
I am sorry to be so damn noobish but i need help lol... Ive watched so many youtube videos with josh dew and read so many posts and downloaded so many roms. I know I am probably missing just one step and if someone can help me I would be so appreciative.
my note 3 is rooted with twrp installed. i want to change my rom , my main goal is to get unlimited hotspot unlocked.... when i try to install a rom it says KERNEL is not SEANDROID ENFORCING, I then put it all back to stock then root then install twrp.
I think i have maybe a wrong kernel? What do I need to do?
Click to expand...
Click to collapse
There is nothing wrong. It says that only if you are not using a pure stock kernel.
Sent from my SM-N900P using Tapatalk
JonSCSL said:
There is nothing wrong. It says that only if you are not using a pure stock kernel.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
But it just reboots constantly never starts up
TheWreckHER said:
But it just reboots constantly never starts up
Click to expand...
Click to collapse
I need a little more information from your phone in order to accurately help you.
What version of stock TW were you running when you rooted (prior to flashing a ROM)?
Based on what you're describing, you most-likely were on Jellybean (MJ4) when you did your rooting and installed TWRP.
What is your bootloader version?
You can see this on the same boot-up screen where you see the "KERNEL is not SEANDROID ENFORCING" message.
What is your TWRP version?
Some ROMs need the newest version of TWRP in order to install correctly. For our phone, older versions of TWRP (2.6.X.X) can only be used to install Jellybean (MJ4) Roms, while the newer versions of TWRP (2.7.X.X) can only install KitKat (NAB, NC5) Roms.
What ROMs have you been trying to flash?
This will help us understand if there are issues with what you're installing.
The main reason I ask these questions is that there is a very specific way of upgrading from Jellybean (MJ4) to KitKat (NAB, NC5) on our phones. Most people (like myself) rooted on other phones and aren't used to the bootloader restrictions Samsung introduced on the Note 3, so we expect to just upgrade from MJ4 to NC5 like it's no big deal.
Also, there's the issue with TWRP... because of the whole bootloader thing, one version of TWRP cannot work for both JB and KK Roms. It's just the way it is... We've helped plenty of people who were trying to flash KK Roms on an older version of TWRP, only to have errors and bootloops.
Hope this helps!
Check out "WiFi Tether Router"
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter This works, for me, on stock rooted nc5. It's a paid app. Follow the settings directions in the description to get all the settings right for your phone. It works and isn't difficult to set up. I have nc5 stock rooted. Custom recovery isn't needed for this. You must have root for it to work.
A reboot after using is a good idea. Otherwise, no complaints. Works on 4g.
Tethering eats battery life and creates heat. If you plan to use it for awhile, I suggest plugging in a charger. Keep the phone out in the open so it can keep cool and get good signal. Charging and tethering with create heat. Nothing to worry about if you don't put the phone in a hot place while using it.
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?
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.