Hi friends,
Specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Build Number: JDQ39.I545VRUAMDK
Rooted
I have a (what seems to be rare) rooted, stock ROM MDK Galaxy S4 running 4.2.2 (Jelly Bean?). Is there a way to update to Kit Kat (and keep root and my MDK status) so I can play with some of the ROMs I see? I know there are ROMs that apply a Kit Kat update (Hyperdrive RLS16 for ex) and I've tried flashing that, but I can't get any other ROMs to stick after that (Like CyanogenMod Nightlies... can't get that to take. What am I doing wrong??), and sadly there's some little glitches in Hyperdrive that are frustrating to me, so sticking with it is not something I want to do at this point.
I feel like I might get burned for asking this but I'm trying to approach this as methodically as possible and I can't seem to find, even with a good amount of searching through the Verizon G S4 forums, a straightforward explanation of how to do this, or if it's even possible. Am I approaching this in the wrong way or asking the wrong questions?? If so, can someone offer a simple explanation of why what I'm asking is not possible, or (more preferably) how I can approach it another way to get my Android Version updated but not lose root or the versatility that comes with managing to maintain my MDK status?
Thank you all for your help!
I'm not too familiar with aosp roms, but hyperdrive was my daily driver before moving on to the note 4. I last updated to hyperdrive rls 18.1 and it had been good to me. Rls 19 is having mixed reviews and never updated my phone to that version because if some minor glitches. I strongly recommend Rls 18.1. I had no issues with my mdk gs4.
onearmsysiphus said:
Hi friends,
Specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Build Number: JDQ39.I545VRUAMDK
Rooted
I have a (what seems to be rare) rooted, stock ROM MDK Galaxy S4 running 4.2.2 (Jelly Bean?). Is there a way to update to Kit Kat (and keep root and my MDK status) so I can play with some of the ROMs I see? I know there are ROMs that apply a Kit Kat update (Hyperdrive RLS16 for ex) and I've tried flashing that, but I can't get any other ROMs to stick after that (Like CyanogenMod Nightlies... can't get that to take. What am I doing wrong??), and sadly there's some little glitches in Hyperdrive that are frustrating to me, so sticking with it is not something I want to do at this point.
I feel like I might get burned for asking this but I'm trying to approach this as methodically as possible and I can't seem to find, even with a good amount of searching through the Verizon G S4 forums, a straightforward explanation of how to do this, or if it's even possible. Am I approaching this in the wrong way or asking the wrong questions?? If so, can someone offer a simple explanation of why what I'm asking is not possible, or (more preferably) how I can approach it another way to get my Android Version updated but not lose root or the versatility that comes with managing to maintain my MDK status?
Thank you all for your help!
Click to expand...
Click to collapse
What recovery are you using? Clockwork or TWRP? What do you mean by the ROM isn't sticking? Are you getting stuck on a boot screen?
I'm using TWRP and flashed the Google Play Edition ROM which is on 4.4.4 Kitkat with root, I'm still on an MDK bootloader also.
OK, I'll keep that in mind, and thanks for the recommendation.
Any other thoughts on my questions about updating to 4.4.2?
To SkrillaKev - I'm using TWRP. I mean that after I flash Hyperdrive, I'm unable to get any other ROM to flash. It will fail in recovery (Eclipse) or will get stuck on the load screen (as with CynogenMod Nightlies)
I guess an easier question is - Can I flash any custom ROM that is made for 4.4.4 when I'm running 4.2.2??
I'll give the Google Edition ROM a go.
scrillakev said:
What recovery are you using? Clockwork or TWRP? What do you mean by the ROM isn't sticking? Are you getting stuck on a boot screen?
I'm using TWRP and flashed the Google Play Edition ROM which is on 4.4.4 Kitkat with root, I'm still on an MDK bootloader also.
Click to expand...
Click to collapse
Welp.... I wiped system/cache/dalvik and tried flashing Google Play Edition. got a yellow triangle and the message about having software not approved by Verizon and please report to the nearest Verizon store for bar-code tattooing and sterilization lol
Then I re-wiped sytem/cache/dalvik and tried flashing EclipseTW-S4-v4.0.2-KitKatNC5. Now I'm stuck on a boot screen...
At least when I screw something up I screw it up REALLY good.
onearmsysiphus said:
Welp.... I wiped system/cache/dalvik and tried flashing Google Play Edition. got a yellow triangle and the message about having software not approved by Verizon and please report to the nearest Verizon store for bar-code tattooing and sterilization lol
Then I re-wiped sytem/cache/dalvik and tried flashing EclipseTW-S4-v4.0.2-KitKatNC5. Now I'm stuck on a boot screen...
At least when I screw something up I screw it up REALLY good.
Click to expand...
Click to collapse
You got the yellow triangle and message because you have to flash the Loki zip after flashing the ROM . ...here ya go https://www.dropbox.com/s/3m3wclsx6ryynhg/loki-doki.zip?dl=0
heath2805 said:
You got the yellow triangle and message because you have to flash the Loki zip after flashing the ROM . ...here ya go https://www.dropbox.com/s/3m3wclsx6ryynhg/loki-doki.zip?dl=0
Click to expand...
Click to collapse
Many thanks!! I knew I was missing something but didn't have time to get back to that thread before I left work for the day. I'll give that a shot right meow
onearmsysiphus said:
Many thanks!! I knew I was missing something but didn't have time to get back to that thread before I left work for the day. I'll give that a shot right meow
Click to expand...
Click to collapse
No prob... Also I'd let it sit after flashing. You may have to select the correct APN: "Verizon Internet " and change mobile network to "LTE/ CDMA" and reboot. Should stick after that.
---------- Post added at 11:01 PM ---------- Previous post was at 10:52 PM ----------
Just realized this is in the development section lol This thread will probably get moved to Q&A
onearmsysiphus said:
Many thanks!! I knew I was missing something but didn't have time to get back to that thread before I left work for the day. I'll give that a shot right meow
Click to expand...
Click to collapse
Keep MDK!!!! After you flash a ROM. If it gets hung up on boot, hold volume up, home key and power key until the phone resets. Then let it boot up. Don't know why it happens but I have the same problem from time to time and rebooting seems to fix it. I've been using eclipse for 4or5 months now. It's pretty sick
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
heath2805 said:
No prob... Also I'd let it sit after flashing. You may have to select the correct APN: "Verizon Internet " and change mobile network to "LTE/ CDMA" and reboot. Should stick after that.
Did that and it seems to be holding steady. Thanks for the tip there.
---------- Post added at 11:01 PM ---------- Previous post was at 10:52 PM ----------
Just realized this is in the development section lol This thread will probably get moved to Q&A
Click to expand...
Click to collapse
Ooops!! Well, hopefully it'll help someone else with noob problems like me.
Shaftamle said:
Keep MDK!!!! After you flash a ROM. If it gets hung up on boot, hold volume up, home key and power key until the phone resets. Then let it boot up. Don't know why it happens but I have the same problem from time to time and rebooting seems to fix it. I've been using eclipse for 4or5 months now. It's pretty sick
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
Click to expand...
Click to collapse
Oh yes most definitely gonna keep MDK. It's magic lol
onearmsysiphus said:
Ooops!! Well, hopefully it'll help someone else with noob problems like me.
Oh yes most definitely gonna keep MDK. It's magic lol
Click to expand...
Click to collapse
Its also worth about $100 dollars more according to what they are selling for on swappa.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
InUh
Shaftamle said:
Keep MDK!!!! After you flash a ROM. If it gets hung up on boot, hold volume up, home key and power key until the phone resets. Then let it boot up. Don't know why it happens but I have the same problem from time to time and rebooting seems to fix it. I've been using eclipse for 4or5 months now. It's pretty sick
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
Click to expand...
Click to collapse
you just have to make sure you have. Loki enabled recovery and you can pretty much flash anything here most of the roms have an MDKprocedure and all the information is still here for the old bootloader it is just not as common so you will have to look and older discussions as in not the first page there are several pages to each one of these sections if you look at the you can read through all the pages..the threads are organized in the latest they have been posted in so all your information is going to be considered old school until you get educated and then you just pop right into the current roms..I still have an s4 MKD 32...I gave to my significant because I refused to send it in on a trade and for my m8 upgrade on edge...btw I prefer phil recovery latest edition go to the phil thread and read toward the end and you'll find a link to his current inside the recovery in settings you can toggle Loki. Just leave it on.then it is just like any other unlocked phone.....and never flashed anything into this phone using ODIN unless its MDK ...or the latest radios... make sure you do your homework on whatever you are going to flash and Odin because it very well could contain a later bootloader and completely screw you. and the great thing is that we and other like us on MDK are the only ones that get to play with anything in the original development section....and in case you didn't know safestrap is for locked bootloaders not uswell technically we are still locked but Loki is the key. And that key only works on MDK bootloader.....and I'm sorry but I used hyperdrive before and the old lady that is now on the latest more than likely your problems with hyperdrive stem from not having flash the kernel properly in the proper recovery and not having the latest radios flashed to your device.
moderators please move to Q&A
onearmsysiphus said:
Hi friends,
Specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Build Number: JDQ39.I545VRUAMDK
Rooted
I have a (what seems to be rare) rooted, stock ROM MDK Galaxy S4 running 4.2.2 (Jelly Bean?). Is there a way to update to Kit Kat (and keep root and my MDK status) so I can play with some of the ROMs I see? I know there are ROMs that apply a Kit Kat update (Hyperdrive RLS16 for ex) and I've tried flashing that, but I can't get any other ROMs to stick after that (Like CyanogenMod Nightlies... can't get that to take. What am I doing wrong??), and sadly there's some little glitches in Hyperdrive that are frustrating to me, so sticking with it is not something I want to do at this point.
I feel like I might get burned for asking this but I'm trying to approach this as methodically as possible and I can't seem to find, even with a good amount of searching through the Verizon G S4 forums, a straightforward explanation of how to do this, or if it's even possible. Am I approaching this in the wrong way or asking the wrong questions?? If so, can someone offer a simple explanation of why what I'm asking is not possible, or (more preferably) how I can approach it another way to get my Android Version updated but not lose root or the versatility that comes with managing to maintain my MDK status?
Thank you all for your help!
Click to expand...
Click to collapse
I have two suggestions:
First, make sure you flash the loki-doki.zip RIGHT AFTER you flash a new ROM in your zip queue, just like what was suggested previously.
Second, in case anything goes wrong, you should always have a current NANDROID backup first and this emergency wipe TAR on hand for Odin. There have been 4 separate times, in the span of about a week, that I gave myself the unauthorized software screen, and had to do this. So I would emergency wipe back to stock MDK, re-root, use Rashr to flash TWRP 2.7.1.0, and then I'd restore my NANDROID backup from my sd card. Rashr only works for flashing TWRP because only TWRP in that app is already Loki'd.
I'm still using RSL7 and it works great with no glitches I tried the newest one rsl20 and hated its look and didnt like any off the new features so i went back to RSL7, if you have not tried it you may want to, it is very different from RSL20 and imo way better.
Related
I have researched and read through about 20 of the last pages here:
http://forum.xda-developers.com/showthread.php?t=1768142&page=83
I've also tried this thread:
http://forum.xda-developers.com/showthread.php?t=2571171
I still have no luck. I installed through the Goo.im app, reboot into recovery and all i get is downloading.. don't turn off target. I rebooted with the volume down button and chose cancel and it restarts fine now. I do have mk2. Some people said they have issues, and to be honest, do i even need twrp if i don't care if i have to re-flash stock mk2? I've already done it twice through odin because of trying to install roms/messing up my phone. This seemed easier when i had a bionic. I changed roms weekly on that thing, never having an issue.
Also, why doesn't anyone post what versions these things are compatible with? I never see anything like twrp 2.6.3.1 recovery compatible with "xxx version and previous only!" so i try stuff and crap doesn't work. I've been trying to install carbon rom and it appears to be a no go.
Yeah you gotta lot of research to do. Look at any of the stickies in our forum or the other 1,000 people who made threads in this section asking what you're asking.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Yeah you gotta lot of research to do. Look at any of the stickies in our forum or the other 1,000 people who made threads in this section asking what you're asking.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Found a sticky that i did not see before.
So it appears that because i recently got this phone i'm kinda screwed when it comes to an AOSP rom without a custom recovery which isn't possible at this time. Well damn, that sucks. I guess i'm stuck with crappy touchwiz related roms. Ugh.
BlueForce64 said:
Found a sticky that i did not see before.
So it appears that because i recently got this phone i'm kinda screwed when it comes to an AOSP rom without a custom recovery which isn't possible at this time. Well damn, that sucks. I guess i'm stuck with crappy touchwiz related roms. Ugh.
Click to expand...
Click to collapse
Yeah it's a crappy situation. Right now the closest you can get is flashing the Foxhound port. It's AOSP themed. Also Eclipse is AOSP themed.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Yeah it's a crappy situation. Right now the closest you can get is flashing the Foxhound port. It's AOSP themed. Also Eclipse is AOSP themed.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Ah i see. Perhaps i'll find something i like or just stick with stock. Thank you. My apologies for not reading enough. I didn't think to check in the s4 general forum.
BlueForce64 said:
Ah i see. Perhaps i'll find something i like or just stick with stock. Thank you. My apologies for not reading enough. I didn't think to check in the s4 general forum.
Click to expand...
Click to collapse
No problem, just get these threads a lotttttttt lol
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
No problem, just get these threads a lotttttttt lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I could imagine. Seems like a dumb question to ask now that i've read the sticky lol. Those new to the samsung world probably run into the same issues i did. Could be why.
Yeah. On MK2 Verizon locked bootloaders and you can only use safestrap ypu csnt use TWRP. It sucks I tried and bricked my phone before lol
Sent from my SCH-I545 using xda app-developers app
pewds said:
Yeah. On MK2 Verizon locked bootloaders and you can only use safestrap ypu csnt use TWRP. It sucks I tried and bricked my phone before lol
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Can't even begin to guess how many people have come on here after they did that.
XDA has all the answers people just need to read more before they fiddle with a $600 phone lol
Verizon S4
Liquid Smooth 4.4
Sprint S4
Negalite 4.4
No kidding. After bricking a friend's phone, due to not doing my homework ahead of time, I realized the importance of being thoroughly well informed about what you're doing before jumping in and messing with this stuff. XDA has so much information and so much help available if you look around a little bit. Some things may take some searching. I can't thank the community enough for all the help they've been in my endeavors.
Sucks there's no custom recoveries for the locked bootloader S4s. If you install Safestrap, give Hyperdrive a try. I'm on MDK and have run several different ROMs, AOSP and TW. I always find myself coming back to Hyperdrive. I'm on 14 now and it works great. So while it's not the answer you're hoping for, try using Hyperdrive. It allows you to pick and choose elements to install, some of which are ported from AOSP, and you could use a different launcher to give it a little less of a TW feel.
Developer Phone
need some help. I Purchased a used S4 Developer Edition Phone. Problem is it has I545VRUEMK2 on. The phone says its a developer phone on the back buy the battery. But I still cant load a custom recovery. I was told the Boot Loader couldn't be locked on this developer phone. could somebody please point me in the right direction. Thanks.
JME007 said:
need some help. I Purchased a used S4 Developer Edition Phone. Problem is it has I545VRUEMK2 on. The phone says its a developer phone on the back buy the battery. But I still cant load a custom recovery. I was told the Boot Loader couldn't be locked on this developer phone. could somebody please point me in the right direction. Thanks.
Click to expand...
Click to collapse
There was a thread on here I think by Skeetch that's for your phone and I'm pretty sure you're answers are in there... For the life of me I can't find it though. I'll keep looking for you
Sent from my SCH-I545 using Tapatalk
---------- Post added at 12:25 PM ---------- Previous post was at 12:20 PM ----------
http://forum.xda-developers.com/showthread.php?t=2637686
If noone here answers you go to that that... I'm sure he can help
Sent from my SCH-I545 using Tapatalk
JME007 said:
need some help. I Purchased a used S4 Developer Edition Phone. Problem is it has I545VRUEMK2 on. The phone says its a developer phone on the back buy the battery. But I still cant load a custom recovery. I was told the Boot Loader couldn't be locked on this developer phone. could somebody please point me in the right direction. Thanks.
Click to expand...
Click to collapse
Is I545VRUEMK2 the build or baseband? Developer phones have I545OYU (I545VRU is for retail S4's). Developer phones only had the following builds on them: I545OYUAMDK (original), I545OYUEMJ7 and I545OYUEMK2. If your build is one of these then you are ok and someone loaded the retail mode/radio onto it. You can visit my thread which Mistertac referenced and flash different modem and/or radios.
Also, if you want to double check to see whether your phone is still in developer mode, load the phone into Download mode: Power off the phone, then hold the Power Button and Volume down together. When the green warning screen comes up, press Volume Up to accept and enter download mode. The text in the upper left corner of the screen in download mode should list: "Mode: Developer" - small and gray text. To reboot just hold the Power Button until the phone turns off then hold power again to boot back up.
Keep me posted!
Edit: Also the only recoveries I can run with my I545OYUEMK2 DevS4 are Philz Touch Recovery and SafeStrap v3.71 from HashCode which is TWRP based. TWRP by itself boots me directly into Download Mode (was able to load TWRP while on I545OYUAMDK). Assuming your phone is still a Developer Edition device, if you ever have any issues with recoveries putting you into download mode, just use Odin and my thread to download the necessary file to restore boot and/or recovery.
JME007 said:
need some help. I Purchased a used S4 Developer Edition Phone. Problem is it has I545VRUEMK2 on. The phone says its a developer phone on the back buy the battery. But I still cant load a custom recovery. I was told the Boot Loader couldn't be locked on this developer phone. could somebody please point me in the right direction. Thanks.
Click to expand...
Click to collapse
Whomever told you that the boot loader couldn't be locked is mistaken. If you flash a non-developer bootloader onto a developer phone, it now has a locked bootloader. Unfortunately, there's no way to undo that until (unless) the developers figure out how to unlock the bootloader.
Install the "Phone INFO * Samsung *" app from the play store and open it. What does it say for the Bootloader Version?
There's also a "Phone Info" app that can display the bootloader version as well.
Thank you for the reply. Looks like I am sol. That sucks. I have a developer phone with a locked bootloader.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
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?
Q&A for [ROM] 100% Stock I545_OC1 - 5.0.1 (MDK)
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.
Before posting, please use the forum search and read through the discussion thread for [ROM] 100% Stock I545_OC1 - 5.0.1 (MDK). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Installing ROM's
I was wondering since the OTA update that gave Galaxy S4 Verizon users Lollipop, is it possible to install this ROM and then download Cyanogenmod? I'm wondering this because there is Loki in this ROM and as far as I know Loki allows you to install any ROM. Correct me if I'm wrong. Also does flashing this ROM give root access, or is there a separate thread for that? Thanks.
Can I just use CWM recovery to flash this and is there any extra steps that I need to do other than the normal that I usually do when flashing Roms. Im on VRUAMDK bootloader and MDK baseband with CWM version 6.0.4 running Hyperdrive rls 21
Sent from my SCH-I545 using XDA Free mobile app
Ridwan Majid said:
I was wondering since the OTA update that gave Galaxy S4 Verizon users Lollipop, is it possible to install this ROM and then download Cyanogenmod? I'm wondering this because there is Loki in this ROM and as far as I know Loki allows you to install any ROM. Correct me if I'm wrong. Also does flashing this ROM give root access, or is there a separate thread for that? Thanks.
Click to expand...
Click to collapse
If your bootloader is not the MDK version the answer is no. Any bootloader after MDK cannot be exploited with loki. If you don't know which boolloader you have type "getprop ro.bootloader" from within a terminal emulator and the results will tell you.
Okay... So I will respectfully move this question from the main thread of the ROM to here.
Has anyone successfully completed a Tap-n-Pay transaction using Google Wallet?
I am not able to have the reader even recognize the 'tap' much less get to the 'pay'. But on OctOL, I am able to complete these same transactions.
bucklyv said:
Okay... So I will respectfully move this question from the main thread of the ROM to here.
Has anyone successfully completed a Tap-n-Pay transaction using Google Wallet?
I am not able to have the reader even recognize the 'tap' much less get to the 'pay'. But on OctOL, I am able to complete these same transactions.
Click to expand...
Click to collapse
Have you tried any other NFC tasks to see if it's NFC or wallet issue?
I don't use tap and pay so can't help there.
Redflea said:
Have you tried any other NFC tasks to see if it's NFC or wallet issue?
I don't use tap and pay so can't help there.
Click to expand...
Click to collapse
So I have a Note II for my work phone and I just turned on SBeam and transferred a file both directions between the two phones... so I guess it is, in fact, a Google Wallet problem, not a phone/kernel problem. At least on the surface anyway.
Thanks, again for the help.
At least you know NFC can work with the ROM in some applications.
Well... I tried it again and it still will not work with Google Wallet.
Bummer.
Any chance that the kernel posted by Surge might have a tweak that can help with the nfc?
I did go back and confirm that the OctOL Lollipop ROM works flawlessly and actually communicates the transaction more quickly than the TW based Hyperdrive ROM.
Transparent Accuweather Widget
Running MDK. Flashed w/TWRP no problems. But I miss the Transparent Accuweather. Tried flashing a couple mods to no avail. Has anyone installed transparent Accuweather mod with this stock rom? Thanx in advance.
Root
Is there a method to root after flashing the stock ROM? I've been looking but I can't find it.
---------- Post added at 08:57 PM ---------- Previous post was at 08:46 PM ----------
The flashfire link says that there is no beta. Is there another link to use or something else that can be done to install Flashfire?
If you're on 5.0.1 stock unrooted, then you're currently out of luck, I believe, no root/roll-back method.
Anyone Else have problems with overheating?
So I am on MDK rooted flashed TWRP after I flashed this rom. Everything is running smoothly however when I use Bluetooth streaming music in my car and navigation the phone gets extremely hot to the point where I get a cooling down error message. Once that happens the phone goes into closing applications and then eventually gets warm enough to shut down. So at first I thought kernel issue, tried with the Hulk kernel same result. Even on different roms such as Dan's GPE lollipop, the phone heats up and shuts down. I have ODIN back to MDK using a .pit file and NAND erased all on this phone and still the heat has been an issue.
i know its common with these phones to overheat, so I contacted Verizon and had two replacements sent which one was running NG6 and the other OC1. Both overheated and shut down doing the same thing as the MDK baseband phone I originally had. Anybody have any similar situation, or have an idea about what I should try to keep these phones from overheating? As a a side note the phones bloat apps were frozen on the replacements as best I could since neither were rooted. I don't know what I should do since I need the phone for navigation and I don't have an upgrade since I still have unlimited data, and seeing as the replacements are all acting the same, that doesn't leave me too many options with getting a phone that actually works.
Thanks for any help and advise on what I should do.
JCTechie said:
So I am on MDK rooted flashed TWRP after I flashed this rom. Everything is running smoothly however when I use Bluetooth streaming music in my car and navigation the phone gets extremely hot to the point where I get a cooling down error message. Once that happens the phone goes into closing applications and then eventually gets warm enough to shut down. So at first I thought kernel issue, tried with the Hulk kernel same result. Even on different roms such as Dan's GPE lollipop, the phone heats up and shuts down. I have ODIN back to MDK using a .pit file and NAND erased all on this phone and still the heat has been an issue.
i know its common with these phones to overheat, so I contacted Verizon and had two replacements sent which one was running NG6 and the other OC1. Both overheated and shut down doing the same thing as the MDK baseband phone I originally had. Anybody have any similar situation, or have an idea about what I should try to keep these phones from overheating? As a a side note the phones bloat apps were frozen on the replacements as best I could since neither were rooted. I don't know what I should do since I need the phone for navigation and I don't have an upgrade since I still have unlimited data, and seeing as the replacements are all acting the same, that doesn't leave me too many options with getting a phone that actually works.
Thanks for any help and advise on what I should do.
Wife had that message, is your phone in the sun when you are having these issues? I have 0 overheating issues and I even use teather. Rooted MDK and wife's is Verizon non rooted.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
SafeStrap question?
If I rooted my device with ss how do I install this ? Not sure about changing over to twrp or how to. and I want to get rid of the custom lock screen at boot up. any help please and thank you in advance . ok just so everyone knows what I am running http://forum.xda-developers.com/galaxy-s4-verizon/development/rom-echoe-rom-v49-tw-lollipop-t3099930
Hi there... Just bought a Verizon S4 for my wife. Don't know anything yet about flashing it with custom rom. Heard about safestrap, locked boot loader... some complicated stuffs I don't mind with my Note 2.<br />
So can someone give me the right steps coming from a stock NK1? Not yet rooted, not yet flashed... all stock...<br />
Thank you in advance.<br />
<br />
Envoyé de mon SM-N910C en utilisant Tapatalk<br />
---------------<br />
<b>Admin Note: this thread has a dedicated questions and answers section which you can access here -->.</b>
Envoyé de mon SM-N910C en utilisant Tapatalk
Known issues - none = wrong!
There is a very major issue. Non MDK users cannot install Viper4Android because SELinux mode cannot be changed to permissive. Spent all day getting this rom installed and working out the kinks only to find out that Viper4Android cannot be installed due to stock kernel SELinux mode not being able to be changed to permissive.
Nevermind I found fix
beavis5706 said:
There is a very major issue. Non MDK users cannot install Viper4Android because SELinux mode cannot be changed to permissive. Spent all day getting this rom installed and working out the kinks only to find out that Viper4Android cannot be installed due to stock kernel SELinux mode not being able to be changed to permissive.
Click to expand...
Click to collapse
Nevermind I found a fix over at http://androiding.how/how-to-fix-viper4android-selinux-policy-issues-on-lollipop/
I used Recovery Flashable zip w/ FlashFire and got Viper4Android working with this deodexed rom.
Tether Mod Deodex?
I couldn't find the answer to this on the main thread or here - last night when I tried to flash the tether mod over the top of the standard rooted-odexed ROM, the phone booted up and immediately started throwing System errors. I was able to factory reset back to stock, but the tether mod obviously didn't work. Does that mod need to be flashed over the deodexed version of this ROM to work? If not, any other ideas on how to make the tether mod work?
Help
Good evening,
I get lost in all this. Here are my properties:
SCH-I545
Baseband: I545VRUEMK2
Number version: JSS15J.I545VRUEMK2
Android Version : 4.3
I would like to know:
1-) How to install a recorvery on the SCH-I545 already rooted with saferoot...
2-) How to know if my bootloader is to dévérouiller and if not how to make him(it) 3-) How then I to install(settle) the ROMA OC1
I am afraid of scrubbing my telephone.
Thank you for your help
---------- Post added at 09:25 PM ---------- Previous post was at 09:21 PM ----------
Good evening,
I get lost in all this. Here are my properties:
SCH-I545
Baseband: I545VRUEMK2
Number version: JSS15J.I545VRUEMK2
I would like to know:
1-) How to installa recorvery on the SCH-I545 already rooted with saferoot...
2-) How to know if my bootloader is to dévérouiller and if not how to make it
3-) How then I to install) the ROM OC1
I am afraid of scrubbing my telephone.
Thank you for your help
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.
Hey guys thanks for taking your time and reading. I have a Verizon Sch-i545 Galaxy S4 with a OF1 bootloader. I really and when i say really i mean it, really want a deodexed rom. I literally have been searching for days, bricking my device, and much more. All you tech savvy pros out there could you possibly help me i really wanted a deodexed rom just to download xposed and other modules. Please help, thanks again!
Either of Stang5litre's roms work and the Albe95 ports are nice too
whowatchlist said:
Either of Stang5litre's roms work and the Albe95 ports are nice too
Click to expand...
Click to collapse
Well the thing is I've tried stangs 3 times and got a black screen after booting past the Samsung custom bootlogo
I tried stang's, and I could only get one to connect to the network, but it kept giving me a security warning every couple of minutes. Albe's s6 rom works great after turning off the edge features.
@hooks024 @ConfudentialGUI Did you figure it out? I'm trying to figure out why some have trouble and others don't. There has to be a common connection. Let me know.
Nah I didn't even try
recovery kernel to flash on an OF1 build
So if I'm understanding this thread correctly, there is a rom I can install even with an OF1 build? I'll check these suggested roms. Big question to me is flashing a recovery kernel, what is it, where to download and instructions to install flash process.
instead of making a thread to ask i figured id just ask in this one....my girl has an i545pp with 0h7 baseband...... i've been retired from the game for a few years now but wanting know what i could do to unlock it and get here on a custom rom.... her ex has some **** on here i want wiped but though unlocking it and hooking her up would be better than a factory reset
thanks in advance
cicuye said:
So if I'm understanding this thread correctly, there is a rom I can install even with an OF1 build? I'll check these suggested roms. Big question to me is flashing a recovery kernel, what is it, where to download and instructions to install flash process.
Click to expand...
Click to collapse
Finally got it. The first time I used Flash Fire the rom I downloaded was for the MDK build Stang rom. Working back through it I realized what I'd done, checked my download list and flashed everything correctly. I'm going through set up right now. It is so refreshing to not have to look at that damn Verizon boot image! Once again, thanks to all the collaborators and usual suspects that put all this together.
---------- Post added at 03:29 AM ---------- Previous post was at 03:02 AM ----------
cicuye said:
Finally got it. The first time I used Flash Fire the rom I downloaded was for the MDK build Stang rom. Working back through it I realized what I'd done, checked my download list and flashed everything correctly. I'm going through set up right now. It is so refreshing to not have to look at that damn Verizon boot image! Once again, thanks to all the collaborators and usual suspects that put all this together.
Click to expand...
Click to collapse
No Wifi problem has surfaced, clues?
bg260 said:
@hooks024 @ConfudentialGUI Did you figure it out? I'm trying to figure out why some have trouble and others don't. There has to be a common connection. Let me know.
Click to expand...
Click to collapse
Negative. I gave up and went back to albe95's s6 rom.
hooks024 said:
Negative. I gave up and went back to albe95's s6 rom.
Click to expand...
Click to collapse
OK. It's a mystery. I have the same device, but I can switch roms freely. Can you pm me with a description of how you rooted and what you did after. Also, I have tried installing xposed on stang5litre... the result was a reacquainence with my old friend Odin. I would like to figure out why some can flash stang and others cannot.
Thanks.
I have had no trouble with stang's ROM on my phone or my friend's s4... Albe's ROM had some problems that I eventually solved. Still running Stang's ROM