[Q] Updating Verizon S4 - Verizon Samsung Galaxy S 4

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.

Related

[Q] ME7 with Unlocked Bootloader Upgrade to MJ7?

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.

[Q] Currently on MI1 with a few Questions

Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
madtomatoes said:
Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
Click to expand...
Click to collapse
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Your only recourse is odin the full wipe stock image back and start over.
I suggest a thorough reading of the forum threads here first so you know better what to do.
I have a guide in the general forum here that lists steps to go from ME7 to MJ7 and root, install safestrap 3.65 and HD11....I'm not sure how it would play with your MI1 base phone so proceed at your own risk
decaturbob said:
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Click to expand...
Click to collapse
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
madtomatoes said:
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
Click to expand...
Click to collapse
that sounds about right. When you do HD12, be sure you have the safestrap version....

[Q] Can I flash back to 4.1.2 after using the 4.3 leak since I was rooted? on a i605

Good Morning everyone. I need to flash back to 4.1.2 to get my phone looked at. Is it possible to re-root after I get my phone back? I see people are having problems using casual and getting a partition 60 missing? or something on that order any help would be greatly appreciated.
jimbo15482 said:
Good Morning everyone. I need to flash back to 4.1.2 to get my phone looked at. Is it possible to re-root after I get my phone back? I see people are having problems using casual and getting a partition 60 missing? or something on that order any help would be greatly appreciated.
Click to expand...
Click to collapse
When you say "flash back to 4.1.2", do you mean just flash a stock 4.1.2 ROM, or use ODIN to restore your phone to factory locked condition?
As long as the phone does not accept the 4.3 OTA then casual will still work. If the 4.3 OTA gets installed on your phone, then you will not be able to unlock the bootloader again. You can still achieve root access, but not unlock, which will prevent you from being able to install custom roms.
I just want to make sure I've got this right. I've done the VRUEMJ9 4.3 OTA update. If I flash back to the stock VRAMC3 4.1.2 build using ODIN, I still won't be able to unlock my bootloader?
If so, I wish I'd known this before I took the OTA update. On my old phone, I could just sbf to an older build and that took care of any problems. I thought that it would be the same with this phone, but I guess not. Frustrating.
GreenRaccoon said:
I just want to make sure I've got this right. I've done the VRUEMJ9 4.3 OTA update. If I flash back to the stock VRAMC3 4.1.2 build using ODIN, I still won't be able to unlock my bootloader?
If so, I wish I'd known this before I took the OTA update. On my old phone, I could just sbf to an older build and that took care of any problems. I thought that it would be the same with this phone, but I guess not. Frustrating.
Click to expand...
Click to collapse
That is the case, unfortunately. From the research I've done it would seem the bootloader on this device cannot be downgraded. The files we have available to flash via ODIN do not change the bootloader, they are not full images. And yes it is frustrating, several of my family members were not the happy with the 4.3 OTA and were ready to take the custom ROM plunge, too late.
Jiggabitties said:
That is the case, unfortunately. From the research I've done it would seem the bootloader on this device cannot be downgraded. The files we have available to flash via ODIN do not change the bootloader, they are not full images. And yes it is frustrating, several of my family members were not the happy with the 4.3 OTA and were ready to take the custom ROM plunge, too late.
Click to expand...
Click to collapse
Is there a way to track down the full bootloader img for older versions?
palmbeach05 said:
Is there a way to track down the full bootloader img for older versions?
Click to expand...
Click to collapse
Not that I know of.
Sent from my SCH-I605 using xda app-developers app

[Q] How to ROM an older S4 (ME7)?

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.

Flashing question for my Sprint Note 3

I'm currently rooted on 4.3 MJ4. Yes I'm outdated and decided to finally update. I'm going to flash to stock 4.3 MJ4. My questions is, after I flash to stock 4.3 MJ4. Can I flash NC5 from MJ4? Or would I have to do it in these steps ( MJ4 then NAB then NC5? ).
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
evilvoice said:
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
Click to expand...
Click to collapse
Awesome! Thanks! I am trying to flash a stock rom, but thought I would need to go in steps instead of instantly flashing to the most current version.
As for my plan: I'm rooted and on a custom rom. I want to go back to stock rom and then root again and flash to either cm12.1 or cm13. From what I've read, I cant flash to either cyanogenmod roms until I was on either lollipop or higher. I was also thinking, would it work if I was to flash a rooted current version of a stock rom, that way I don't have to flash a stock rom and break root and have to root it again?
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
evilvoice said:
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
Click to expand...
Click to collapse
What is the PH1 rom? I've already flashed to stock NC5 so far and lost root.
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
evilvoice said:
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
Click to expand...
Click to collapse
EDIT: I went ahead and used the Full Restore. Fortunately, it did not WIPE any data. YEAH! And it looks like I am on my way to an updated NOTE3.
Hello. My Note3 is on 4.3. It was rooted a couple of years ago, but out of use since Oct 2015. I still want to use the Note3 for non-cell phone operations, browsing, camera, etc. I want to upgrade, but the OTA is locked out.
I am lost on all of the many, many posts on how to updated a rooted Note3, but most of them are outdated. I have it mostly backed up as far as handwritten notes, photos, etc. But I don't really want to have to start from scratch if I don't have to.
I am currently reviewing rwilco's one click options. There are two software packages listed in his directory. One of them is dated 02/27/15 and is called nodata restore. Will this keep from wiping the phone as opposed to the fullrestore exe posted 04/12/14 vs the tar posted 02/27/15.
I am not a complete dodo, but I am having a hard time getting this phone unrooted and updated.
Thanks for any detail instructions or links to the best way to update this as of 9/5/2016!!!
Everything you need to know is explained here. http://forum.xda-developers.com/galaxy-note-3/general/guide-how-to-disable-air-command-pop-t2960839
Sent from my SM-N920C using XDA-Developers mobile app

Categories

Resources