I keep getting that annoying OTA message to update my phone but I don't know if it will lock me out of CFW possibilities. I'm on unrooted VRUAME7 and want to upgrade to a new version and install CFW (which I had a while ago until I lost root). But it seems everyone is already on the newest firmware and I don't know how to upgrade to a point where it is possible to still do root and CFW.
RootTheWorld said:
I keep getting that annoying OTA message to update my phone but I don't know if it will lock me out of CFW possibilities. I'm on unrooted VRUAME7 and want to upgrade to a new version and install CFW (which I had a while ago until I lost root). But it seems everyone is already on the newest firmware and I don't know how to upgrade to a point where it is possible to still do root and CFW.
Click to expand...
Click to collapse
First off, CFW isn't the correct term, Custom ROM is.
Second, if you want 4.3, upgrade incrementally to MK2, if you want 4.4, upgrade to NC5, not NG6! Although you can Root NG6, SafeStrap (the only option for custom recovery, TWRP + CWM doesn't work!) doesn't work on NG6 yet. So I personally use NC5 w/ Eclipse 4.0.2 in my Stock Slot, and GPE (SafeStrap edition) in my ROM Slot 1.
The boot loader with the highest chance of unlock is... well none. I and many others think that there may never be an Unlock for our Boot loader. however, for a Bootloader bypass (Still running AOSP/CM ROMs), I would stay on MK2 or NC5, as those two boot loaders both have a hack to enable custom modules, and therefore kexec (which loads custom ROMs on locked boot loaders), though exec is a WIP for both as of yet. Seems like NC5 is the main development platform though.
npjohnson said:
First off, CFW isn't the correct term, Custom ROM is.
Second, if you want 4.3, upgrade incrementally to MK2, if you want 4.4, upgrade to NC5, not NG6! Although you can Root NG6, SafeStrap (the only option for custom recovery, TWRP + CWM doesn't work!) doesn't work on NG6 yet. So I personally use NC5 w/ Eclipse 4.0.2 in my Stock Slot, and GPE (SafeStrap edition) in my ROM Slot 1.
The boot loader with the highest chance of unlock is... well none. I and many others think that there may never be an Unlock for our Boot loader. however, for a Bootloader bypass (Still running AOSP/CM ROMs), I would stay on MK2 or NC5, as those two boot loaders both have a hack to enable custom modules, and therefore kexec (which loads custom ROMs on locked boot loaders), though exec is a WIP for both as of yet. Seems like NC5 is the main development platform though.
Click to expand...
Click to collapse
I think you stated the question in your answer better than I asked it
How can I incrementally upgrade without going all the way to the latest ROM? I'm searched for incremental update and ame7 to but neither worked.
RootTheWorld said:
I think you stated the question in your answer better than I asked it
How can I incrementally upgrade without going all the way to the latest ROM? I'm searched for incremental update and ame7 to but neither worked.
Click to expand...
Click to collapse
OTA is in incremental I believe. I had to go ME7 ==> MI1 ==> MK2 and it took about half an hour.
Related
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7 Build. However, all the bloatware that remains on the phone is making me want to flash Cyanogenmod.
Problem:
Using ROM Manager (which has always worked on my previous phones) every time I flash into recovery mode it flashes onto Samsung Recovery 3e NOT into TWRP, which I have flashed on my phone and need to use to install any custom ROMS.
Could anyone tell me how to disable Samsung Recovery 3e so I can use TWRP and flash the new ROM?
Or how, using Samsung Recovery 3e, I can flash a new ROM?
Aury said:
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7 Build. However, all the bloatware that remains on the phone is making me want to flash Cyanogenmod.
Problem:
Using ROM Manager (which has always worked on my previous phones) every time I flash into recovery mode it flashes onto Samsung Recovery 3e NOT into TWRP, which I have flashed on my phone and need to use to install any custom ROMS.
Could anyone tell me how to disable Samsung Recovery 3e so I can use TWRP and flash the new ROM?
Or how, using Samsung Recovery 3e, I can flash a new ROM?
Click to expand...
Click to collapse
Your only option at present is Safestrap. It's the only recovery that allows custom roms on the ME7. Developer is Hashcode.
http://forum.xda-developers.com/showthread.php?t=null
Also a thread about Roms that work with Safestrap. CM is not one of them. But you will enjoy Hyperdrive, Eclipse and others. Everything from a near AOSP to TouchWiz to the max.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
wtherrell said:
CM is not one of them.
Click to expand...
Click to collapse
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
alburdet619 said:
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
Click to expand...
Click to collapse
With the original build, (MDK), there was an exploit that let you bypass the bootloader, so you could flash any ROM. Since the updates, (ME7 and MI1) that exploit has been locked and there is no way, as of now, to bypass the bootloader. Also, there is no way to go back to MDK once the phone has been updated. The only option for ME7 and MI1 users is to use Safestrap, with the appropriate kernel module, and flash TW ROMs only.
alburdet619 said:
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
Click to expand...
Click to collapse
It is not possible to install CyanogenMod on any revision later than MDK at the moment.
They're building CM for the S4 for those fortunate enough to have revision MDK, which has a bootloader that can be bypassed.
Aury said:
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7Build.
Click to expand...
Click to collapse
I see your question has been answered, let me add a little information that may save you reading a few billion posts here!
The Galaxy S4 has a locked bootloader that cannot be unlocked so far.
There is a workaround called Loki that bypasses the bootloader to allow a new bootloader such as CM or TWRP to be flashed.
The ME7 build "fixed" the exploit that Loki used to bypass the bootloader so you're now stuck with the stock bootloader.
Start reading up on SafeStrap, that allows some TouchWiz ROMs to be flashed to the SD card but, so far, no non-TW ROMs work.
Sorry but at least some devs are still working on unlocking the bootloader, let's hope they are successful.
Hi,
So I have a SGS4 with ME7 and and unlocked bootloader. I am looking to upgrade to MJ7(4.3?) and be able to keep my full root. Is there a good way to do such a thing yet? Most info I see says MJ7 is only for safe strap, I have a custom recovery so I am not sure if it will work or if it is worth it. Please advise and help me....
Thank you in advance!!!
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I have CWM Touch Recovery V1.0.3.5 with my ME7 phone so it sounds like I should probably not take the update... I am pretty sure I don't have safestrap. I was on MDK then updated to ME7 and kept my unlocked bootloader and root. I just wish there was a way I could get 4.3 or 4.4... I will keep reading and searching... Thank you.
sonnycohopie said:
I have CWM Touch Recovery V1.0.3.5 with my ME7 phone so it sounds like I should probably not take the update... I am pretty sure I don't have safestrap. I was on MDK then updated to ME7 and kept my unlocked bootloader and root. I just wish there was a way I could get 4.3 or 4.4... I will keep reading and searching... Thank you.
Click to expand...
Click to collapse
You updated the radio I take it? That will show you on ME7 but have the MDK bootloader. Thus leaving your TWRP intact.
So anyway, I'm looking for the same thing. Not happening right now
kdo23 said:
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Super Sam Galaxy said:
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Click to expand...
Click to collapse
You didn't have stock me7 which was my meaning. You had an me7 rom I think is what you're saying.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
You didn't have stock me7 which was my meaning. You had an me7 rom I think is what you're saying.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well, it wasn't stock ME7 for sure. I think it changed to ME7 when I first flashed Hyperdrive, but was that way for a while on every ROM I flashed after Hyperdrive so whatever change Hyperdrive made seemed to be permanent. Or else I may have just been flashing ROM's that were ME7 by coincidence - do all ROM's explicitly set the baseband or do some just use whatever is already on the device? I don't really understand basebands too well. Anyway, sorry about the mix-up, I wasn't aware you were referring to stock. I sure hope that someone is able to figure out a workaround that allows for a custom recovery because I really like KitKat and I suppose we won't be seeing any TW based KitKat ROM's until Samsung releases an update first. My understanding is that Safestrap only works with TW.
I find a certain degree of irony in the fact that I've never permanently damaged a device when rooting or flashing ROM's (which is pretty good for a noob like me), yet I've done something even worse just by inadvertently allowing an update that came straight from the manufacturer! Why do they have to make things so complicated? :crying:
Super Sam Galaxy said:
Well, it wasn't stock ME7 for sure. I think it changed to ME7 when I first flashed Hyperdrive, but was that way for a while on every ROM I flashed after Hyperdrive so whatever change Hyperdrive made seemed to be permanent. Or else I may have just been flashing ROM's that were ME7 by coincidence - do all ROM's explicitly set the baseband or do some just use whatever is already on the device? I don't really understand basebands too well. Anyway, sorry about the mix-up, I wasn't aware you were referring to stock. I sure hope that someone is able to figure out a workaround that allows for a custom recovery because I really like KitKat and I suppose we won't be seeing any TW based KitKat ROM's until Samsung releases an update first. My understanding is that Safestrap only works with TW.
I find a certain degree of irony in the fact that I've never permanently damaged a device when rooting or flashing ROM's (which is pretty good for a noob like me), yet I've done something even worse just by inadvertently allowing an update that came straight from the manufacturer! Why do they have to make things so complicated? :crying:
Click to expand...
Click to collapse
Baseband is separate, your rom base is what we were referring to. The baseband change happened with a file you flashed for sure but likely not hyperdrive but a radio file. With a custom recovery you could have had mj7 baseband and custom recovery. Look at build number in the future.
Sent from my SCH-I545 using Tapatalk
Edit: build number can change too with a rom. Mdk is the only starting stock firmware which can be exploited to allow a custom recovery. Since you had one it meant you rooted on mdk and should not have odined to a later release.
Super Sam Galaxy said:
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Click to expand...
Click to collapse
Absolutely impossible to have a custom recovery on an ME7 boot loader. You could've flashed a ME7 radio or a ME7 based rom such as HyperDrive but your boot loader is still MDK. Which is why you lost your recovery, you flashed the wrong factory image.
Sent from my SCH-I545 using XDA Premium 4 mobile app
kdo23 said:
Baseband is separate, your rom base is what we were referring to. The baseband change happened with a file you flashed for sure but likely not hyperdrive but a radio file. With a custom recovery you could have had mj7 baseband and custom recovery. Look at build number in the future.
Sent from my SCH-I545 using Tapatalk
Edit: build number can change too with a rom. Mdk is the only starting stock firmware which can be exploited to allow a custom recovery. Since you had one it meant you rooted on mdk and should not have odined to a later release.
Click to expand...
Click to collapse
I figured out the part about not flashing to a later release after the fact, unfortunately. It was simply a matter of not thoroughly researching and it's a pretty big bummer now because I can't flash! But I suppose worse things can come of not researching, like bricking and thankfully that hasn't happened yet (though I'm certainly going go be more careful in the future). Thanks for explaining about all the baseband/radio stuff, that is a bit over my head. Sure hope an exploit for ME7 (or a way to revert to MDK) is found soon, though from the sound of it that isn't likely.
Hi guys, long time lurker but first time poster.
I'm currently on MDK, rooted with TWRP recovery, and was interested in updating to the latest OS. I have a few questions:
1) Is it currently worth the update to MJ7?
2) How would I go about resetting the recovery and Android to stock? Haven't found much info for the recovery, and I don't want to brick my phone by screwing something up, and from what I understand I have to go back to the stock recovery before updating to MJ7.
Thanks in advance!
no0od13s said:
Hi guys, long time lurker but first time poster.
I'm currently on MDK, rooted with TWRP recovery, and was interested in updating to the latest OS. I have a few questions:
1) Is it currently worth the update to MJ7?
2) How would I go about resetting the recovery and Android to stock? Haven't found much info for the recovery, and I don't want to brick my phone by screwing something up, and from what I understand I have to go back to the stock recovery before updating to MJ7.
Thanks in advance!
Click to expand...
Click to collapse
Why would you want to update that will lock your bootloader down? You can still run all custom ROMS based on new firmware kernels without updating....I definitely would not
no0od13s said:
Hi guys, long time lurker but first time poster.
I'm currently on MDK, rooted with TWRP recovery, and was interested in updating to the latest OS. I have a few questions:
1) Is it currently worth the update to MJ7?
2) How would I go about resetting the recovery and Android to stock? Haven't found much info for the recovery, and I don't want to brick my phone by screwing something up, and from what I understand I have to go back to the stock recovery before updating to MJ7.
Thanks in advance!
Click to expand...
Click to collapse
Don't update your bootloader. There's no reason at all to do that, and there's no going back if you do. A locked bootloader gives zero benefits, excluding perhaps KNOX but I wouldn't call that a benefit.
You can update your modem without updating your bootloader by downloading one and flashing in TWRP: http://forum.xda-developers.com/showthread.php?t=2487298
There are some improvements since MDK in those. You'll want either 1545VRUEMJ7_modem.zip or I545VRUEMK2_modem.zip from the modems only section.
If you want the latest TouchWiz, you'll need to be on MDK to get it since Verizon still hasn't released a 4.4 update. http://forum.xda-developers.com/showthread.php?t=2674280
If you just want the latest android, try the GPE rom: http://forum.xda-developers.com/showthread.php?t=2643031
Note that if you update your modem, your phone will show *MJ7 or *MK2 in About Phone -> Baseband. That does not mean you don't have the MDK bootloader. You can always use this app to check your bootloader version: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Bootloader -> Definitely stay on MDK.
Modem -> Go ahead and update, it won't affect your ability to flash roms or reduce your resale value. Plus, you can go backwards with modems if you want; you can't with bootloaders.
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
uniroot said:
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
Click to expand...
Click to collapse
1. DO NOT TAKE THE OTA
2. read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick.
Sent from my SCH-I545 using XDA Free mobile app
I've been researching this for a couple of days, and obviously I'm missing some details.
Why not take the OTA for 4.4.x? What am I missing? What's the issue?
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
uniroot said:
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
Click to expand...
Click to collapse
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
joshm.1219 said:
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
Click to expand...
Click to collapse
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
uniroot said:
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
Click to expand...
Click to collapse
It should, but not always. Also you have to use the unroot from the supersu app.
---------- Post added at 01:27 PM ---------- Previous post was at 01:27 PM ----------
Oh and the tar files are here: http://forum.xda-developers.com/showthread.php?t=2735172
I recommend using Odin 3.09
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
uniroot said:
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
Click to expand...
Click to collapse
No, you only need the unroot if you try the OTA. Nothing else needs to be done to use the tar file with Odin, but I would recommend backing up important data to an external SD and flashing the full wipe file to ensure you have a clean system.
Latest OTA "patches" TowelRoot
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
~JohnnyB~ said:
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
Click to expand...
Click to collapse
Towelroot works on NC5, the latest OTA for this device. Towelroot came well after the OTA. If we get another firmware update, I'm sure it will patch towelroot.
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Saint Isaiah said:
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Click to expand...
Click to collapse
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
joshm.1219 said:
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
Click to expand...
Click to collapse
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Also, what in the world does it mean to "Loki" a ROM after installing it? Kinda confused there
Saint Isaiah said:
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Click to expand...
Click to collapse
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
joshm.1219 said:
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
Click to expand...
Click to collapse
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Saint Isaiah said:
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Click to expand...
Click to collapse
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
joshm.1219 said:
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
Click to expand...
Click to collapse
Awesome, thanks Josh! This might make a great sticky for the "what is Loki?" newvies and explaining the importance of MDK for those still on it and not sure why.