Related
Okay so I am a bit of a noob at flashing ROMs and such, but I really want to do it and get my Galaxy S4 (on verizon) as close to pure android as possible. I tried flashing three ROMs. The first was liquidsmooth got the right zip file and everything flashed it in ROM slot 3 on safestrap and went to reboot and it did not work, it came of with some trippy screen and did not load. I then tried flashing Hyperdrive but did this in the stock rom slot and that worked fine. So I tried doing the same thing with CyanogenMod flashing it in the stock rom slot and rebooting but it came up with the trippy screen just like it did when I tried flashing liquidsmooth.
I am a little bit of a noob with this stuff so some help would be great
http://forum.xda-developers.com/showthread.php?t=2702682
nincman said:
Okay so I am a bit of a noob at flashing ROMs and such, but I really want to do it and get my Galaxy S4 (on verizon) as close to pure android as possible. I tried flashing three ROMs. The first was liquidsmooth got the right zip file and everything flashed it in ROM slot 3 on safestrap and went to reboot and it did not work, it came of with some trippy screen and did not load. I then tried flashing Hyperdrive but did this in the stock rom slot and that worked fine. So I tried doing the same thing with CyanogenMod flashing it in the stock rom slot and rebooting but it came up with the trippy screen just like it did when I tried flashing liquidsmooth.
I am a little bit of a noob with this stuff so some help would be great
Click to expand...
Click to collapse
you need to research what you can do and can not do....before you turn your phone into a door stop....
http://forum.xda-developers.com/showthread.php?t=2606501
http://forum.xda-developers.com/showthread.php?t=2630040
nincman said:
Okay so I am a bit of a noob at flashing ROMs and such, but I really want to do it and get my Galaxy S4 (on verizon) as close to pure android as possible. I tried flashing three ROMs. The first was liquidsmooth got the right zip file and everything flashed it in ROM slot 3 on safestrap and went to reboot and it did not work, it came of with some trippy screen and did not load. I then tried flashing Hyperdrive but did this in the stock rom slot and that worked fine. So I tried doing the same thing with CyanogenMod flashing it in the stock rom slot and rebooting but it came up with the trippy screen just like it did when I tried flashing liquidsmooth.
I am a little bit of a noob with this stuff so some help would be great
Click to expand...
Click to collapse
Well if nothing else maybe you'll get familiar with Odin lol
Sent from my SCH-I545 using Tapatalk
Thanks!
Mistertac said:
Well if nothing else maybe you'll get familiar with Odin lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for all of your help!:laugh:
decaturbob said:
you need to research what you can do and can not do....before you turn your phone into a door stop....
http://forum.xda-developers.com/showthread.php?t=2606501
http://forum.xda-developers.com/showthread.php?t=2630040
Click to expand...
Click to collapse
So can u just use the normal SSv3.65 app after in rooted my S4 and just flash custom roms on different slots that are compatible with the Touch wiz kernal?
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
So can u just use the normal SSv3.65 app after in rooted my S4 and just flash custom roms on different slots that are compatible with the Touch wiz kernal?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
you have to use the safestrap version for your firmware....
decaturbob said:
you have to use the safestrap version for your firmware....
Click to expand...
Click to collapse
Oh ok. And another thing is after I root my S4 (Mk2) it says Ill get some custom flag thing during boot up? What does that mean? And once I go to a Kit kat ROM can I go back to stock 4.3? Like if I put the ROM on Stock Slot and i wanna go back to Original stock like i am now. Any way i can do that?
Sent from my SCH-I545 using Tapatalk
I'm sure Decaturbob will also answer you but. .
The custom flag/splash screen just means your phone has detected that is been modified. No biggie at all.
And you're not going to be able to load a Kit Kat rom just yet. They are working on a way to do it I heard but for now you're only going to be able to run TW roms based off your current build MK2.
There is no down grading your stock rom either.
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
Oh ok. And another thing is after I root my S4 (Mk2) it says Ill get some custom flag thing during boot up? What does that mean?
Click to expand...
Click to collapse
That's correct. The phone has an application that scans for modified system files and will detect that you're rooted. Then, when you boot, it'll show an image of an open padlock and the word "Custom" for a few seconds before continuing the boot.
Some people freak out over that. However, you don't have much choice here. If you want it rooted, then you're changing files on the ROM. That's customizing it, and will be detected. If you don't want it to show up as "Custom", then you want a factory stock device.
RECKLESS PAIN said:
And once I go to a Kit kat ROM can I go back to stock 4.3? Like if I put the ROM on Stock Slot and i wanna go back to Original stock like i am now. Any way i can do that?
Click to expand...
Click to collapse
No. First, it's fairly likely that taking the Kit Kat 4.4 update will fail if you've modified your phone. You'll need to return it to very close to stock for 4.4 to apply cleanly.
Second, if you go to Kit Kat, your phone will be unrooted, Safestrap recovery will be removed, and you'll be stuck with a kernel that currently is not rootable. If you have a Verizon or AT&T phone (or any other with a locked bootloader), you won't be able to root it at the moment, so won't be able to do anything else.
Once VZ releases 4.4, we'll work on ways to get past factory stock, but that's not guaranteed to be successful until we see what VZ gives us.
Edit: And no, once you've updated to Kit Kat, you can't downgrade to 4.3. You'll need to use ROMs compatible with the 4.4 kernel.
k1mu said:
That's correct. The phone has an application that scans for modified system files and will detect that you're rooted. Then, when you boot, it'll show an image of an open padlock and the word "Custom" for a few seconds before continuing the boot.
Some people freak out over that. However, you don't have much choice here. If you want it rooted, then you're changing files on the ROM. That's customizing it, and will be detected. If you don't want it to show up as "Custom", then you want a factory stock device.
No. First, it's fairly likely that taking the Kit Kat 4.4 update will fail if you've modified your phone. You'll need to return it to very close to stock for 4.4 to apply cleanly.
Second, if you go to Kit Kat, your phone will be unrooted, Safestrap recovery will be removed, and you'll be stuck with a kernel that currently is not rootable. If you have a Verizon or AT&T phone (or any other with a locked bootloader), you won't be able to root it at the moment, so won't be able to do anything else.
Once VZ releases 4.4, we'll work on ways to get past factory stock, but that's not guaranteed to be successful until we see what VZ gives us.
Edit: And no, once you've updated to Kit Kat, you can't downgrade to 4.3. You'll need to use ROMs compatible with the 4.4 kernel.
Click to expand...
Click to collapse
So right now since I got the Verizon Galaxy S4 (Mk2) there is no root for it? and would my safest thing to do is not even root it/ put custom ROM right? I just got it and it doesn't have insurance but I don't wanna mess up a great phone like this.
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
So right now since I got the Verizon Galaxy S4 (Mk2) there is no root for it? and would my safest thing to do is not even root it/ put custom ROM right? I just got it and it doesn't have insurance but I don't wanna mess up a great phone like this.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
MK2 can be rooted - click here.
Once rooted, you can install custom ROMs using Safestrap.
You really should, however, start here as that sticky thread will explain a lot of what you're asking.
Use eclipse 3.0 touchwiz. Almost AOSP
Search upgrade/downgrade safestrap and read and read again. I currently on NC2 and I am debating on trying downgrade but it seems very involved for the couple of AOSP rom that can be patched and used with safestrap and mk2. Still not sure whether I am willing to lose the WI - FI.
Sent from my SCH-I545 using Tapatalk
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.
Hello, not new to rooting and such but I'm a little confused. Just got this Note 2 after breaking my G2. I'm on ND7, managed to root and install safestrap. I've made a stock back up and flashed over my stock as there is no rom slot support yet. I've flashed Alliance 30 and it worked well. My question is, can I flash other Rom's like Wilson's CM12? My bootloader is still locked. Is there a safe way to unlock it? I've searched and found that if you have a locked bootloader you can't flash kernels. I think? Not trying to be annoying. Just confused. I haven't used safestrap since my old Razr days, lol. Any help would be awesome. Thanks in advance. ..
Sent from my SCH-I605 using XDA Free mobile app
I think you can flash any rom using safestrap. The only ones I tried so far are DN3 and Alliancerom. They flashed with no problems. I would like to add on to this question though, Can I flash any mods using safestrap?
Right. Or kernels for that matter? It's strange because there's some people with unlocked bootloader's, some with safe strap, and some just plain old stock rooted (which was a pain in it's self).
Sent from my SCH-I605 using XDA Free mobile app
Did a little more digging into the thread, basically if your bootloader is locked, the only Rom's that you can flash are those with the same build and kernel that you are currently on. So you were right. As far as flashing mods with safestrap, still unsure. ???
Sent from my SCH-I605 using XDA Free mobile app
No other ROMs besides the above mentioned? Seems almost worth sending it to that company to downgrade
any group pricing?
Installed Mocha DrIzzle, liking it so far except the network speed mod
If I couldnt stand to be without telelphone....
stoph8n24 said:
No other ROMs besides the above mentioned? Seems almost worth sending it to that company to downgrade
Click to expand...
Click to collapse
I'd be on the "Send it Off" wagon.
I've seen destructions for using ODIN to flash a KIES image in, and then go about fixing it that way but many many more posts saying this is impossible.
What I'd like to know, if I have to go with the same darn kernel etc, is how the everloving **** to get rid of ALL and I mean *ALL* of the crapware/verizonware/amazonware/etc and completely strip the touchwhiz down to just what I need....
This phone thing is a nasty addiction....:cyclops:
stoph8n24 said:
No other ROMs besides the above mentioned? Seems almost worth sending it to that company to downgrade
Click to expand...
Click to collapse
Anyone know if there is a list? I was just given this phone. I rooted it, but also stuck with the locked boot loader. I did install Safestrap and did a back up, and was able to create a ROM slot, but that is all I've done so far.
Since I'm "developmentally chsllenged" (I can follow instructions, but I can't do any development work or anything) I try to just go with trusted info, which has worked so far. I just came from a RAZR Maxx HD with CM12 and am not happy with the way this phone runs.
I'm in the same boat as you guys, and I believe you can only flash 4.4.2 ROMs. That's what I gathered from the Safestrap thread. However, you can (and should) backup your stock ROM in Safestrap and flash other ROMs over that.
I'm currently using Alliance, and it's decent. Nowhere near the amount of modifications as CyanideL, which is really what I want, but can't install because it's currently on Android 5.x.
Ridiculous what Samsung has done to this phone. Glad it was relatively cheap though, good lesson to avoid any manufacturer who locks the bootloader in the future.
Does anyone know if we can just flash an older version of the stock ROM? Couldn't we odin, or something, down to 4.1.x and go from there?
adobrakic said:
I'm in the same boat as you guys, and I believe you can only flash 4.4.2 ROMs. That's what I gathered from the Safestrap thread. However, you can (and should) backup your stock ROM in Safestrap and flash other ROMs over that.
I'm currently using Alliance, and it's decent. Nowhere near the amount of modifications as CyanideL, which is really what I want, but can't install because it's currently on Android 5.x.
Ridiculous what Samsung has done to this phone. Glad it was relatively cheap though, good lesson to avoid any manufacturer who locks the bootloader in the future.
Click to expand...
Click to collapse
I have SS and did a back up, but I thought I read about people running into problems and then bricking? I think they got them back after doing some stuff but since I am no where as talented with this stuff I try to be cautious. I've rooted and SS' ed a Bionic and ran several ROM's on that one until replacing it with a RAZR Maxx HD that I rooted (and was able to take advantage of the exploit before they pushed a patch and unlocked the bootloader).
If I can just flash over the stock ROM safely, then I'll get flashing right away
I read the issues with bricking as well, but I think those people were trying to flash 5.x ROMs. I agree about wanting to avoid it though. I have a HTC One S that I saved from being bricked a few times, but I don't even wanna have to go through the process of that for the Note 2. Here's the Safestrap thread, if you're a little wary and would like to read more about it.
As far as I can tell, you should be good with flashing 4.4.2 ROMs, since that's what I did and we seem to have the same config (4.4.2 Note 2, Safestrap 3.72). The only thing I wonder is what TWRP you have. I have the latest 2.7.0.x. If that's what you have, you should be just fine with flashing a 4.4.2 ROM over the stock ROM.
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.