Related
Hey guys,
I'm sorry if this question has already been asked, I currently have a verizon Gs4 that is running the new MK2 update. I have been looking around at ROMS online and I would like to install a kit kat rom onto my phone. My question is after rooting am I limited to what type of recovery and roms i can use? My co worker has a GS4 for sprint and uses PHILZ custom recovery.
Can anybody help me with some explanation? I am trying to figure out if it is worth rooting the phone. I also want to make sure I have all my ducks lined up before plunging into the process.
Thank you,
kendeezy said:
Hey guys,
I'm sorry if this question has already been asked, I currently have a verizon Gs4 that is running the new MK2 update. I have been looking around at ROMS online and I would like to install a kit kat rom onto my phone. My question is after rooting am I limited to what type of recovery and roms i can use? My co worker has a GS4 for sprint and uses PHILZ custom recovery.
Can anybody help me with some explanation? I am trying to figure out if it is worth rooting the phone. I also want to make sure I have all my ducks lined up before plunging into the process.
Thank you,
Click to expand...
Click to collapse
No custom recovery exists for mk2...hashcode is working on safestrap recovery but it is buggy at best right now and only works for touchwiz ROMs...others are working tirelessly toward unlock or workaround...mk2 is very new...give it time and read up on mk2...more will come
You can't flash a custom rom or recovery if your on the MK2 update. You can only root MK2. The devs are working hard to make that possible for us that are on the MK2 update.
Sent from my SCH-I545 using XDA Premium 4 mobile app
It is absolutely worth rooting, but being on MK2 your recovery options are limited to Safe strap. Philztouch will only work on the original MDK firmware. I haven't used Safe strap since the Bionic but Hashcode and his work are amazing. Head over to his blog and his thread for more info. If you are just looking to theme your phone you can stay stock rooted and use Xposed with Wanam settings. All of this info is right here on XDA and most likely on the first page of their respective forums. My first recommendation is to read a lot first. Second, before you start the process have all emergency restore files downloaded and ready to go with your device recognized by your computer. (Always have Odin, your current Factory Firmware, and USB drivers ready)
You're on MK2....you can't install a custom ROM. This topic has been discussed many times.
Sent from my SCH-I545 using xda app-developers app
kendeezy said:
Hey guys,
I'm sorry if this question has already been asked, I currently have a verizon Gs4 that is running the new MK2 update. I have been looking around at ROMS online and I would like to install a kit kat rom onto my phone. My question is after rooting am I limited to what type of recovery and roms i can use? My co worker has a GS4 for sprint and uses PHILZ custom recovery.
Can anybody help me with some explanation? I am trying to figure out if it is worth rooting the phone. I also want to make sure I have all my ducks lined up before plunging into the process.
Thank you,
Click to expand...
Click to collapse
Not to be rude, but this has been answered 1,000,000 times, you couldn't have searched or even read a few posts down. The only version of the S4 that can install a custom recovery is MDK. You can root, and Hashcode just released a version of safestrap that works with MJ7, but this just happened. As far as I am aware, only Hyperdrive will work on a phone on MJ7 or MK2.
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
GlitchMob said:
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
Click to expand...
Click to collapse
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
decaturbob said:
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
Click to expand...
Click to collapse
I understand that I need to look into it, but the way things are organized is different. I've been on an S3 for almost two years now and the forums in the S4 are just overwhelming with information that is scattered. Here is an example of what I was hoping for when I came to the S4 section.
http://forum.xda-developers.com/showthread.php?t=1762709
onemeila said:
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
Click to expand...
Click to collapse
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
GlitchMob said:
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
Click to expand...
Click to collapse
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
k1mu said:
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
Click to expand...
Click to collapse
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
GlitchMob said:
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
Click to expand...
Click to collapse
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
k1mu said:
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
Click to expand...
Click to collapse
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
GlitchMob said:
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
Click to expand...
Click to collapse
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Slowbalt said:
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Is there a noticeable difference? If its the same, why upgrade?
I am coming from a similar situation as you. I cracked my screen on my S3 and Asurion replaced it with an S4, which I received on Monday. I thought that I was going to be able to load SlimKat and pick up where I left off, but no.
The posts that k1mu linked are a great starting point. A few of my thoughts that I came to realize this week. These are my ways of looking at it and may not be totally correct.
The bootloader is locked and there isn't a total unlock (yet). Safestrap allows you to crack the door open a little and reach your arm in to grab a few things.
You will need to stick with ROMs that work with the TouchWiz kernel. The post that k1mu referenced has a link to compatible ROMs. You will not be able to load SlimKat, CM, Carbon, etc. Basically any ROM you choose will have TW underneath. Some of the ROMs will try to look like an ASOP, but it is still a TW base.
Safestrap will allow you to create ROM slots where you can try out the ROM to see if you like it. I am still trying to decide what I want to use. Currently I have Hyperdrive as the leader. Everything that I do continues to work. The Eclipse ROM looks good but it is not quite there yet, but he is working on a build in the next couple days. Here is a link to their website with more up to date status. Eclipse . I also looked at the Foxhound ROM and it is good also. For me support and future upgrades are the most important. I am starting to think that i will embrace TW instead of trying to cover it up and will go with Hyperdrive.
If you use TiBu, read this post, especially with Hyperdrive http://forum.xda-developers.com/showthread.php?t=2653044.
The other realization that hit me was that while Safestrap can create partitions for loading different ROMs, each one is restricted to a maximum of a 3GB /data partition. When I tried to restore all of my apps this was quickly used up. It isn't supported by Safestrap to flash to the stock location, but it can and has been done. Since Safestrap isn't doing a flash there are more risks and I think that this should probably be kept to a minimum. This is where you want to test all the candidate ROMs first and then decide which one to use and then flash to the stock location. Obviously this could cause problems with the phone and would use ODIN as a fallback. Unless something get totally hosed and then you are out of a phone.
One thing that I realized a long time ago is that when you change devices you may want to do everything exactly the way it was before. On the phone or even when looking for information. But in most cases it is better to change your processes or work flow to work with the new device than it is to change the device to work in your previous work flow.
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.
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.