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
Related
I am sorry to be so damn noobish but i need help lol... Ive watched so many youtube videos with josh dew and read so many posts and downloaded so many roms. I know I am probably missing just one step and if someone can help me I would be so appreciative.
my note 3 is rooted with twrp installed. i want to change my rom , my main goal is to get unlimited hotspot unlocked.... when i try to install a rom it says KERNEL is not SEANDROID ENFORCING, I then put it all back to stock then root then install twrp.
I think i have maybe a wrong kernel? What do I need to do?
TheWreckHER said:
I am sorry to be so damn noobish but i need help lol... Ive watched so many youtube videos with josh dew and read so many posts and downloaded so many roms. I know I am probably missing just one step and if someone can help me I would be so appreciative.
my note 3 is rooted with twrp installed. i want to change my rom , my main goal is to get unlimited hotspot unlocked.... when i try to install a rom it says KERNEL is not SEANDROID ENFORCING, I then put it all back to stock then root then install twrp.
I think i have maybe a wrong kernel? What do I need to do?
Click to expand...
Click to collapse
There is nothing wrong. It says that only if you are not using a pure stock kernel.
Sent from my SM-N900P using Tapatalk
JonSCSL said:
There is nothing wrong. It says that only if you are not using a pure stock kernel.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
But it just reboots constantly never starts up
TheWreckHER said:
But it just reboots constantly never starts up
Click to expand...
Click to collapse
I need a little more information from your phone in order to accurately help you.
What version of stock TW were you running when you rooted (prior to flashing a ROM)?
Based on what you're describing, you most-likely were on Jellybean (MJ4) when you did your rooting and installed TWRP.
What is your bootloader version?
You can see this on the same boot-up screen where you see the "KERNEL is not SEANDROID ENFORCING" message.
What is your TWRP version?
Some ROMs need the newest version of TWRP in order to install correctly. For our phone, older versions of TWRP (2.6.X.X) can only be used to install Jellybean (MJ4) Roms, while the newer versions of TWRP (2.7.X.X) can only install KitKat (NAB, NC5) Roms.
What ROMs have you been trying to flash?
This will help us understand if there are issues with what you're installing.
The main reason I ask these questions is that there is a very specific way of upgrading from Jellybean (MJ4) to KitKat (NAB, NC5) on our phones. Most people (like myself) rooted on other phones and aren't used to the bootloader restrictions Samsung introduced on the Note 3, so we expect to just upgrade from MJ4 to NC5 like it's no big deal.
Also, there's the issue with TWRP... because of the whole bootloader thing, one version of TWRP cannot work for both JB and KK Roms. It's just the way it is... We've helped plenty of people who were trying to flash KK Roms on an older version of TWRP, only to have errors and bootloops.
Hope this helps!
Check out "WiFi Tether Router"
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter This works, for me, on stock rooted nc5. It's a paid app. Follow the settings directions in the description to get all the settings right for your phone. It works and isn't difficult to set up. I have nc5 stock rooted. Custom recovery isn't needed for this. You must have root for it to work.
A reboot after using is a good idea. Otherwise, no complaints. Works on 4g.
Tethering eats battery life and creates heat. If you plan to use it for awhile, I suggest plugging in a charger. Keep the phone out in the open so it can keep cool and get good signal. Charging and tethering with create heat. Nothing to worry about if you don't put the phone in a hot place while using it.
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.
[Q&A] [ROM] Echoe ROM v49 - TW - LOLLIPOP - CUSTOMIZED - DEBLOATED - DEODEXED - FAST
Q&A for [ROM] Echoe ROM v49 - TW - LOLLIPOP - CUSTOMIZED - DEBLOATED - DEODEXED - FAST!!!
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] Echoe ROM v49 - TW - LOLLIPOP - CUSTOMIZED - DEBLOATED - DEODEXED - FAST!!!. 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!
SuperSU?
Hello, thanks for all your hard work. Does the ROM come with root access? Thanks in advance for the reply.
notonmdk said:
Hello, thanks for all your hard work. Does the ROM come with root access? Thanks in advance for the reply.
Click to expand...
Click to collapse
yes and busybox.
Has anyone been able to fix text messaging?
text messages
aznjosh said:
Has anyone been able to fix text messaging?
Click to expand...
Click to collapse
I have also been having issues with text messaging. will probably try and downgrade and wipe factory reset in safestrap and see if that resolves my issues. May also try fresh install again.
I can receive text but not send them
I installed this ROM earlier today. So far I love this ROM. However, I can't send text. I have received them but just can't send them. Any help would be appreciated.
Texting doesn't work for me either
Just flashed this ROM tonight, very slick I like it a lot but I have similar problems with no texting. It appears that my verizon APN is incorrect and when I try to edit it manually it doesn't fix the problem either. Not sure why the option to add another one is grayed out though so I can't make a new APN or edit the APN via the GUI. Had to use ES file explorer to try and edit /system/etc/apns-conf.xml
Anyone else having issues getting into Safestrap? Been having no problems with the ROM other than the inability to send texts, but I just noticed today I can't seem to get into Safestrap. Whenever I restart my phone, the Safestrap screen pops up 4 times, and even if I hit reboot into Safestrap all four times, the phone just boots up normally.
welker85 said:
Anyone else having issues getting into Safestrap? Been having no problems with the ROM other than the inability to send texts, but I just noticed today I can't seem to get into Safestrap. Whenever I restart my phone, the Safestrap screen pops up 4 times, and even if I hit reboot into Safestrap all four times, the phone just boots up normally.
Click to expand...
Click to collapse
Yeah I had the same problem so I went back to kitkat for now.
Great rom! Wiped data and no issues to report.
I am curious how to remove the little data usuage in the top left corner though, I've checked everywhere I can think of and cant find the app via titanium to remove.
Thanks!
just making sure
I read that this is compatible with all s4 versions..that being said it should be safe for a tmobile s4 that's currently running an i9505 rom Right? Also if that's the case do I really need safestrap and/or downgrade and upgrade modem?
SS loaded, broken lock says custom and won't boot
I followed instructions it never booted, and the adb isn't working so i can't flash update, here's my question also about the sms and mms , is there a version of lolipop that fully works ? ok got my adb re-installed and phone finally took update and rebooted and I am now using the phone but still no sms send
Hoodrocka said:
I read that this is compatible with all s4 versions..that being said it should be safe for a tmobile s4 that's currently running an i9505 rom Right? Also if that's the case do I really need safestrap and/or downgrade and upgrade modem?
Click to expand...
Click to collapse
Yes, I actually know of someone running this on a T-Mobile S4. He said he's not had any problems at all. Wi-Fi, data, tether, bt, and sms/mms all working. Take that back...He was having an issue with Safestrap bootlooping 3-4 times before successfully booting the system. But he just uninstalled Safestrap and resolved the issue.
SMSC
Does anyone know how to check the SMSC on lollipop?
Hoodrocka said:
I read that this is compatible with all s4 versions..that being said it should be safe for a tmobile s4 that's currently running an i9505 rom Right? Also if that's the case do I really need safestrap and/or downgrade and upgrade modem?
Click to expand...
Click to collapse
hoodrocka your able to flash custom kernels. just install the ROM via your im guessing TWRP recovery and flash your kernel. I used this ROM on TMobile APNs with MetroPCs worked fine. Some verizon ppl are reporting issues with mms and different things. not having your device I havent been able to test this extensively but with my other ROM Ports Flashing to AT&T, T-Mobile, Sprint etc was possible. you might have to flash kernel, modules, apns or modem to get it fully working. but yes fairly confident itll work for any S4 however when I tried to inform the public about the possibility of a unified US S4 division and post my ports to multiple dev sections I had my threads closed and files pulled for not including a kernel in the ROM package.... lol I tried to tell them that we were beyond all that forced kernel crap but they persecuted all the same
---------- Post added at 07:05 PM ---------- Previous post was at 06:34 PM ----------
androidnoob333 said:
Great rom! Wiped data and no issues to report.
I am curious how to remove the little data usuage in the top left corner though, I've checked everywhere I can think of and cant find the app via titanium to remove.
Thanks!
Click to expand...
Click to collapse
pick a different UI from the aroma installer the one you picked has net data option envoked
Still no change for me on the SMS/MMS front as I still can't send from messaging app or hangouts.
Hey guys. Anyone about to get Viper4Android Fx working with this ROM?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------
Also, a fix for the SMS issues has been found http://forum.xda-developers.com/showthread.php?p=60868269
Sent from my SCH-I545 using XDA Premium 4 mobile app
Thanks MetaMav
The fix for SMS/MMS found by metamav worked for me. I put the files in /system/lib and I am now able to text and send pics with tetra sms. Thanks metamav for finding the fix and gigilie for making an awesome rom!!!!
Side note when I started my phone google maps would crash, I had to update maps for the problem to go away.
Post by metamav
-----------------------------------------------------------------
MetaMav
Working SMS and MMS!
I did some research on other S4 forums, and came across the Sprint S4 development section. They were having the exact same issue with their lollipop ROM's. Their solution, ironically, was to extract a few of the lib files from the released Verizon S4 ROM from @muniz_ri to fix their SMS and MMS problem. However, this has not been implemented into any of their 5.0 TW ROM's as of yet. It is currently a fix posted by @troyboytn. It only involves pushing some files via a root file explorer and changing a couple file permissions.
Here is the link to the post: http://forum.xda-developers.com/show...&postcount=281
(And a big thanks to @thastaniard who assisted with the fix)
It also seems we both have the same issue with the default Samsung messenger app when implementing this fix. You cannot send MMS from it. However, you can use either Hangouts or Textra to send SMS and MMS just fine. I have not tested receiving MMS, but I wanted to get this out for other people to try.
@gigilie I imagine this fix could be implemented in your next release (if you haven't already found this solution). It could also be converted into a flashable zip, I just don't have the time right now to make one. There may also be a solution for the default messenger app and sending MMS.
On a side note, does anyone know how to enable "None" as the screen lock? The options for "Swype" and "None" are grayed out in the settings. I have changed security settings and tried different kernels, but nothing works.
How do I properly install
I'm rooted on OC1, but how exactly do I install this rom? I don't have safestrap as I'm aware it is not compatible on LP. And I saw I have to flash the downgrade tar. Is that through odin? And after that what's next?
777agic said:
I'm rooted on OC1, but how exactly do I install this rom? I don't have safestrap as I'm aware it is not compatible on LP. And I saw I have to flash the downgrade tar. Is that through odin? And after that what's next?
Click to expand...
Click to collapse
Well, I am confused at that part Also.
I would just downgrade to nc5, flash the ROM in safestrap, boot into Download and do the upgrade, and boot. If you want xPosed, you will have to find Muniz_ri's method of a temporary safestrap to flash the fix by arter97
Here's a kernel for the Canadian variant of the Note Edge with root support, init.d, and added TCP Congestion methods via defconfig and ramdisk edits.
Prereq:
-Have a means to get back to stock software. This includes an Odin flashable TAR or a recovery flashable ROM.
-[size=+2]Make sure you have a BACKUP![/size]. I cannot stress this enough. While I am certain you won't run into any trouble with the kernel, it's always good to have a backup of your system (including kernel[boot in twrp]) beforehand.
Instructions:
-Download SuperSU beta from here
-Download the kernel: BeastMode 1.1 for the Galaxy Note Edge (Canada, SM-N915W8)
Place both the kernel and SuperSU beta onto your internal or external storage.
Reboot into TWRP.
Flash kernel.
Flash SuperSU.
Reboot and profit.
-Know a bit of knowledge about how to restore your system or what this root enabled kernel will provide. I won't be able to reply to PMs asking me questions. You should know a bit about what you're doing before you do it.
Source code: This uses the Sprint source code, which is available in the Stockish ROM thread.
I'll test for you, I'm going to the docs now but when I get home I'll gladly be the guinea pig (currently have not taken the 5.1.1 update) I understand you may not have the answer(s) to the following questions but I'm just wondering the following: does/will the unofficial Xposed mod work with 5.1.1, will/does ViPER4Android work on 5.1.1, is your kernel selinux-Permissive (?), other than that I'm confident that you and I can overcome/workaround "noob" situations, (I have my edge working perfectly right now but I'm not only doing this for me it's our whole small community (SM-N915P), I'll be losing access to Emotion kernel (totally am not happy about that), but anyway before I take the update is it at all possible to just flash the 5.1.1 modem, firmware, etc (and as long as my bootloader remains at 5.0.1 I can ODIN back or did samsung destroy that luxury for us too)
dinaps86 said:
I'll test for you, I'm going to the docs now but when I get home I'll gladly be the guinea pig (currently have not taken the 5.1.1 update) I understand you may not have the answer(s) to the following questions but I'm just wondering the following: does/will the unofficial Xposed mod work with 5.1.1, will/does ViPER4Android work on 5.1.1, is your kernel selinux-Permissive (?), other than that I'm confident that you and I can overcome/workaround "noob" situations, (I have my edge working perfectly right now but I'm not only doing this for me it's our whole small community (SM-N915P), I'll be losing access to Emotion kernel (totally am not happy about that), but anyway before I take the update is it at all possible to just flash the 5.1.1 modem, firmware, etc (and as long as my bootloader remains at 5.0.1 I can ODIN back or did samsung destroy that luxury for us too)
Click to expand...
Click to collapse
hah, great questions and let me start out by saying .....i made a huge noob mistake :'(
Xposed doesn't work with touchwiz on 5.1.1.....yet (i didn't bother reading before i got excited about 5.1.1 on the note 4)
Not sure if viper works
On the Note 4, you cannot downgrade at all after taking 5.1.1 (made that mistake when I was on a downgradeable bootloader and kitkat...)
I'm currently using CM because I cannot use touchwiz without xposed and i cannot fathom using this phone without my modules.
So yeah, I went from the perfect phone ......to crap. I wish we still had someone providing leaks. An engineering bootloader would probably solve all of this.
I would love to test it but not ready til they get xposed working first
ill test it pm link pls
Hi Freeza, I'll like to test the Kernel. Thanks.
Thanks Freeza...testing now.
Freeza i test the kernel
So far I've had 3 random phone reboots.
i want to test it ...
---------- Post added at 11:49 AM ---------- Previous post was at 11:37 AM ----------
can anyone provide me the link ?
Tester on 5.1.1 here
Sent from my SM-N915P using XDA Premium HD app
where is the link for beta kernel ?
I would be willing to test.
freeza said:
hah, great questions and let me start out by saying .....i made a huge noob mistake :'(
Xposed doesn't work with touchwiz on 5.1.1.....yet (i didn't bother reading before i got excited about 5.1.1 on the note 4)
Not sure if viper works
On the Note 4, you cannot downgrade at all after taking 5.1.1 (made that mistake when I was on a downgradeable bootloader and kitkat...)
I'm currently using CM because I cannot use touchwiz without xposed and i cannot fathom using this phone without my modules.
So yeah, I went from the perfect phone ......to crap. I wish we still had someone providing leaks. An engineering bootloader would probably solve all of this.
Click to expand...
Click to collapse
@freeza: Thanks for responding to our request to mod the Edge kernel. I'm with you--I can't use the phone without Xposed. Here's to hoping that Xposed will support TW LP 5.1.1 soon....
Hi Freeza....Appreciate your work in providing a test kernel for 5.1.1 and root, and am more than willing to test it out. I am a very long time phone tester and never permanately bricked a phone proud to say. :good:
freeza said:
hah, great questions and let me start out by saying .....i made a huge noob mistake :'(
Xposed doesn't work with touchwiz on 5.1.1.....yet (i didn't bother reading before i got excited about 5.1.1 on the note 4)
Not sure if viper works
On the Note 4, you cannot downgrade at all after taking 5.1.1 (made that mistake when I was on a downgradeable bootloader and kitkat...)
I'm currently using CM because I cannot use touchwiz without xposed and i cannot fathom using this phone without my modules.
So yeah, I went from the perfect phone ......to crap. I wish we still had someone providing leaks. An engineering bootloader would probably solve all of this.
Click to expand...
Click to collapse
Hey freeza u mind messaging me that kernel I just want to extract it and compare it to Emotion kernel and stock 5.0.1 kernel
Hey freeza. As I'm testing out root on a Note Edge on 5.1.1 myself I've come across something that may be of note to you. I've gotten permissive SELinux and root. But the baseband is unknown, the phone gets no signal, and it reboots after about a minute of being booted into android. I've tracked it down to the TIMA RKP settings but that's as far as I've gotten. Hope this gives you some tips on where to look to iron out any issues you come across. If I solve the issue beforehand I'll post back.
I want Test it..
Freeza,
And testers just wanted to see what the status is and if this kernel will help. Im getting about worried about being 2 updates behind especially when one is to fix the stagefright update.
Im in a tricky place as i need my phone rooted for work, but cant keep a vulnerability like that open...
Does this kernel work?
Thanks,
Adan
Sent from my SM-N915P using XDA Free mobile app
would like to test
would like to test
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.