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.
Related
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 7 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
VRUFNC2 ("NC2")
VRUFNC5 ("NC5")
There's another release that was apparently a leak or limited release, MG7.
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on. The best way to tell what bootloader you have is to install an app - "Phone INFO *Samsung*" and "Phone info" will both tell you what build and bootloader you have.
The "Developer Edition" devices have "I545OYUA" build numbers versus the consumer versions, which start with I545VR.
Once you're on a particular build, it is not possible to downgrade to an earlier release. The single exception to this is that you can flash MJ7 over MK2, but that's it.
If you're past MDK, you can't bypass the bootloader until an exploit is found.
If you start flashing things without verifying that it's for the release on YOUR phone, you risk bricking it. There's dozens of youtube videos telling you how to flash custom recovery on your phone that WILL NOT WORK unless you're on the MDK bootloader. Be sure to comment in the youtube thread after they assist you with bricking your phone.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
For NC2 and NC5, you can't currrently root unless you downgrade the baseband to MK2.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recovery will not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
k1mu said:
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
Click to expand...
Click to collapse
this really needs to be a sticky as we all know how many aren't taking the time to more than a cursory check in these threads
---------- Post added at 06:16 AM ---------- Previous post was at 06:09 AM ----------
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is the original MDK baseband. Not checking first before flashing will often break your phone.
If you need to know what baseband you're on, use "Settings", "More", "About phone" and scroll down to the "Baseband Version".
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're on the MDK baseband. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
k1mu, I also created a step by step guide (with links) that walks you thru the entire process of going from ME7/MI1 to MJ7 by flashing the wipe tar image of MJ7, installing your saferoot, safestrap and HD11
http://forum.xda-developers.com/showthread.php?t=2579278
I was feeling pretty bad for all the people that were messing up their phone becasue od not understanding the entire process.
Props to you both ! The only thing I would emphasize for MDK users is to get yourself educated (plenty of threads) on the Loki process. The proper use of it when flashing unfamiliar recoveries or kernels can save alot of headaches (trust me I know !!)
Bumping
Sent from my SCH-I545 using XDA Premium 4 mobile app
MJ7
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
sixtythreechevy said:
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
Click to expand...
Click to collapse
nope updating modem changes what your baseband version says.
For those who are unsure if you can install the custom recovery:
The BUILD must be MDK not the MODEM. If you are running different build you can flash different modems. Just because you have the MDK modem does not mean you can flash a custom recovery.
Yeah you can flash any baseband at any time you like...that's your radio/modem. You can also flash a new build as long as your bootloader remains on MDK. For example, I'm running a stock MJ7 ROM but I'm still Loki'd on the MDK bootloader.
Sent from my SCH-I545 using Tapatalk
ok heres my issue
Delete
What really matters here is what Bootloader you're running. Since updating the modem changes the Baseband string, that can't be used to tell if a phone is locked. I've updated the OP to say Bootloader version and to explain how to get to the Bootloader version.
FordNate said:
I'm MDK on the GS4 and believe me i knew about the whole Verizon/At&t/TMO long time ago (smarter than the average near and able to laugh at people when they do do things like that) ok so my issue i tried updating my recovery earlier to philz 6.08 from just CWM 6.0.44 (?). It soft bricked my phone. I just spent 7 hours getting it back to operational order. I tried everything under the sun, u name it i probably did it, but i kept with Verizon packages only. Trying to find a stock image of MDK is impossible to say the least. Good news though. its up and running again only issue i lost root
Root the first time was simple and maybe took 20 minutes. Now i cant get motochopper or any other exploit to to work. Phone "see's" that a program is trying to get access but does not allow me to accept it, only offers to reboot now or later. Help a man out here.. I'm still on mdk just cant get root back. yes i check usb debug even toggled it a couple times. Verify apps unchecked and unknown checked.. Dang Stock is not good.
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
tkacer said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
Click to expand...
Click to collapse
yes and got it running again with root
Happy 4 ya - nothing worse than a borked phone !!!!
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
dbinnc said:
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
Click to expand...
Click to collapse
Install the MK2 no-wipe from here.
I want to bump this thread so we can use the OP as a starting point for a stickie guide concerning verizon S4 and what you need to know for modding your phone.
Naddict will be assisting in getting the sticky set up. This will be a WIP and will NOT be a thread to post questions. Lets get all our smart people contributing with info and links as needed to help all those who wish to mod their phone from not repeating all the same errors and bricking.
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 5 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on.
If you start flashing things without verifying that it's for YOUR phone, you risk bricking it.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
Excellent! Thank you!
Developers edition bootlader
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
kerryh420 said:
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
Click to expand...
Click to collapse
I'm pretty sure you'll need to root first. Also I'm not sure standard twrp is what you need for the Dev edition. They are lokied and I don't believe you have a need for that. That being sailing not exactly sure what your process for rooting will be or which recovery you need.
Maybe this thread will give you some insight.
http://forum.xda-developers.com/showthread.php?t=2339849
Then research about flashing roms on the Dev. Edition. It will be different for you.
Sent from my SCH-I545 using XDA Premium 4 mobile app
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.
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
Confirmed. Just ODIN'd back to MJ3 from the VRUAND3 update and regained root using Saferoot.
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Sent from my SCH-I605 using XDA Free mobile app
mrraya said:
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1
Be sure to thank @droidstyle for taking the time to make this guide
Another confirmation, Odin'd back to MJ9 from ND3 then used saferoot to root.
Can also confirm working for me and rooted also. Does anyone know how we can stop the OTA notification or do we just ignore it?
stop the ota notification note 2
Ostate24 said:
Can also confirm working for me and rooted also. Does anyone know how we can stop the OTA notification or do we just ignore it?
Click to expand...
Click to collapse
Change
FWupgrade.apk to FWupgrade.bak
SDM.apk to SDM.bak
I am not allow to post a link at this time so do a search on "stop the ota notification note 2"
Regain root, ND3 question,Correct MJ9, ODIN7
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
This is what I have been looking for except it says to "REGAIN" root.. I have never had it (ROOT) to start with.. So will this still work?
and
where do I get the correct MJ9 since I did not get it off my phone before I lost it.?? or am I ODIN back to out of the box state which is VRALJB?
Odin 7 or Odin 9
I have read ODIN7 ? but Odin9 is newest as far as I can tell...want to double check.
thanks so much!!!!
mrraya said:
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Click to expand...
Click to collapse
thebat1 said:
This is what I have been looking for except it says to "REGAIN" root.. I have never had it (ROOT) to start with.. So will this still work?
and
where do I get the correct MJ9 since I did not get it off my phone before I lost it.?? or am I ODIN back to out of the box state which is VRALJB?
Odin 7 or Odin 9
I have read ODIN7 ? but Odin9 is newest as far as I can tell...want to double check.
thanks so much!!!!
Click to expand...
Click to collapse
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
I am pretty sure it doesn't matter if you rooted under MJ9 or not. I was able to Odin without root and I wouldn't see why not being rooted when on MJ9 would not enable you to use Odin (since the whole point of Odin is to flash Samsung phones). I'd make a Helium backup just in case though.
You can read the thread I linked and posted by iooooooc to find out how to reflash. It's the same one I used. It has links to Odin and the MJ9 firmware (look for "VRUEMJ9 4.3" with the warning "ONLY USE THIS IF YOU TOOK THE 4.3 OTA!!") and the PIT file you'll need.
You can also read about and get links to all flavors of Odin (you need v3.07 for the VZ Note II) here: http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Finally, to root, here's the main thread for Saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
Everything I read is pretty straightforward.
I also haven't received any notification to upgrade back even though I haven't used the .bak renaming method which is interesting.
Worked great!!!! Thanks for the links guys!!!
Worked Here Too!
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
I decided to bite-the-bullet after reading your post, and all I had to do was re-root as well. All said and done it took me 30 minutes tops to have my phone back. I also used Kingo last time, but after ND3, the version of Kingo I used to root MJ9 didn't recognize the phone and the latest version was so full of dire warnings I immediately aborted.
Thanks guys!
dbalman said:
I decided to bite-the-bullet after reading your post, and all I had to do was re-root as well. All said and done it took me 30 minutes tops to have my phone back. I also used Kingo last time, but after ND3, the version of Kingo I used to root MJ9 didn't recognize the phone and the latest version was so full of dire warnings I immediately aborted.
Thanks guys!
Click to expand...
Click to collapse
I just received a replacement for my broken Note 2, which I previously had rooted with N3bula. To root my old phone, given it came with 4.1, I just had to Odin the MJ9 files, and then flash N3bula with TWRP . When I got my replacement, it updated to ND3 before I realized what was going on. Does anyone know what files I actually need to flash to get back to MJ9 from ND3? I found a file called I605VRUEMJ9.tar on one of the links posted recently. Since the actual ROM on the phone is the stock 4.3 rom, I assume I don't need to worry about system.img. I don't know about boot.img, cache.img, recovery.img, sboot.bin. I am confident I should flash tz.img, modem.bin, hidden.img.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:21 PM ----------
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
Is there a particular reason you wish to use safestrap rather than continuing to use Kingo? Is Kingo not working?
Thx!!
nbock01 said:
Worked great!!!! Thanks for the links guys!!!
Click to expand...
Click to collapse
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
Neither of those links are good.
Thanks!!
@Skilover
If you go to Droidstyle's guide here: http://forum.xda-developers.com/showthread.php?p=34891181 , and then go to section 1b of the guide, you can revert back to MJ9 by following the guide's instructions. You'll want to use the stock file for (VRUEMJ9 4.3) if you're wanting to revert back from ND3.
After you get back to MJ9, you can get root access with saferoot..... Here's the link to saferoot-- http://forum.xda-developers.com/show...php?p=48392009
Sent from my SCH-I605 using XDA Premium 4 mobile app
Amazing..WTG, XDA!
New user here. Been reading a bunch of posts lately as I finally got around to trying to root my SCH-1605, which I have through VZW. For a long time, my big concern was interference on the VZW side. Finally, warranties expired and the urge peaked... just in time for the ND3 OTA update. I tried a couple of methods I found - no success. Finally stumbled on some threads that basically said - ND3 = Out of Luck.
Then I found this post.. :victory:
Truly awesome. Worked like a charm. Looking up good info on locking down the OTA pushes next.
My observations of the differences between my previous attempts and what was missing:
My first attempts:
I neglected to include the 16GB PIT file referenced in the links above (** Note: a few guides I popped across mentioned making sure that only "Auto Reboot" and "F. Reset Time" are checked. When you include the PIT file, it will auto-check "Re-Partition". I left this checked, and it worked like a charm. Can't speak as to the offset of UNchecking this, as - like I said - I left it checked)
I used a different .md5 file that would flag as a fail despite my efforts (I was using a CF autoroot md5). I'm fairly certain this failed due to the OTA update, though it may have been the lack of a PIT file. If someone could provide some more info there, I'm totally open to listen!
Bottom line - my experience was pretty painless after doing adequate research. Thanks a ton! :highfive:
_______________________________________________________________________________________________________________________
I also came across some info stating that the downgrade to the MJ firmware might flag the KNOX (I believe?) or a similar issue. Anyone run across any of those issues using these methods? If someone has a quick link to how I could check this for myself, I'd be very appreciative.
@Tangescence
Glad to hear you had success with rooting . This link should help you check on your knox counter status:
http://forum.xda-developers.com/showthread.php?p=48758233&highlight=odin#post48758233
If "Knox Warranty Void" is at zero, you didn't trip the counter.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Knox warranty void: 0
Confirmed. The flashback left KNOX WARRANTY VOID: 0
Lists as Samsung Official Binary with a System Status of Custom.
Looks good!
I know this is a bit of a side tangent, but safestrap should work with MJ9 and saferoot to allow custom ROMs despite the locked bootloader - right?
Again, many thanks to the community!
Right, safestrap was designed to be used for people with the locked bootloader on a rooted MJ9. Here is the safestrap thread: http://forum.xda-developers.com/showthread.php?p=51616723
I don't know a lot about safestrap, but I believe the ROM slots are not working yet so you'll have to install a custom Rom over the stock ROM if you want to use it. You'll have to do more research to make sure you know how to use it if you want to give it a go.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
Right, safestrap was designed to be used for people with the locked bootloader on a rooted MJ9. Here is the safestrap thread: http://forum.xda-developers.com/showthread.php?p=51616723
I don't know a lot about safestrap, but I believe the ROM slots are not working yet so you'll have to install a custom Rom over the stock ROM if you want to use it. You'll have to do more research to make sure you know how to use it if you want to give it a go.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome - I'll be researching it tonight and tomorrow. Will post to the safestrap thread with my results and probably a heads up here to redirect. Again, tons of thanks!
Confirmed working
My Verizon Note 2 broke so under warranty I got a replacement device with the latest VRUAND3 build installed. It literally drove me nuts because I was so used to having the advantage of a rooted device with the bootloader unlocked. After doing some research, I came across the information on this thread and it helped me with having at least root access which allows me to take advantage of my Titanium Backup and other apps tailored to rooted devices.
Thank you very much for this post. I hope the devs will one up on Verizon and give the community the ability to have a unlocked bootloader soon. I like the connection speed and coverage with Verizon but their method of controlling how their customers use their devices is just annoying. I paid good money for this phone Verizon! I'm going to do what I wish to do with it to make it unique and personal to me. They just don't seem to understand that. Once again... Thanks. ROOT 4TW!
gee1000 said:
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
I am pretty sure it doesn't matter if you rooted under MJ9 or not. I was able to Odin without root and I wouldn't see why not being rooted when on MJ9 would not enable you to use Odin (since the whole point of Odin is to flash Samsung phones). I'd make a Helium backup just in case though.
You can read the thread I linked and posted by iooooooc to find out how to reflash. It's the same one I used. It has links to Odin and the MJ9 firmware (look for "VRUEMJ9 4.3" with the warning "ONLY USE THIS IF YOU TOOK THE 4.3 OTA!!") and the PIT file you'll need.
You can also read about and get links to all flavors of Odin (you need v3.07 for the VZ Note II) here: http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Finally, to root, here's the main thread for Saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
Everything I read is pretty straightforward.
I also haven't received any notification to upgrade back even though I haven't used the .bak renaming method which is interesting.
Click to expand...
Click to collapse
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.
Hello Everyone,
I'm a first time poster but have been reading this site for weeks trying to find the answer to my questions. I've acquired a good bit of info but still wanted to clarify some things before I take the plunge.
I'm currently using a Verizon GS4 (I-545) running rooted stock MK2 jellybean. I rooted ~2 years ago to get rid of the bloatware and just never bothered upgrading/keeping up with the firmware updates. There are some new apps that won't work on my phone, but are working on my wife's stock GS4 on OF1. I'd like to upgrade my firmware (and keep root) so that I don't have to keep stealing her phone.
I've come across several threads discussing upgrading from one baseband to the next - none quite match my scenario. Most threads talk about how to upgrade and keep root but now that I'm late to the party, it seems like root methods have been discovered for all stock firmware versions (even OF1 by flashing OC1 kernel, rooting, and flashing back to OF1 kernel). So with this in mind, can I just skip all the complicated stuff and just use Odin to flash OF1 and then follow Edgardo_Uchicha's OF1 root method?
If I can use Odin to flash OF1, will the file I load in the "AP" slot also includes the proper modules, bootloaders, etc. to upgrade everything to OF1? Will it do a factory reset/wipe or will I keep all my data like an OTA? As for getting the Odin file, it looks like I should just use the Samsung site to get it directly?
If I can use the Odin method, are there any drawbacks? If I don't like lollipop I realize I'm stuck and can't go back, but is there anyway to upgrade and be able to go back (downgrade)?
Thanks again for your help!
Mike
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Edgardo_Uchiha said:
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Click to expand...
Click to collapse
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
mike2914 said:
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
Click to expand...
Click to collapse
Try wiping via recovery, if I'm not wrong this package does not wipe your phone so maybe there are some leftovers that are messing up the new system
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
mike2914 said:
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
Click to expand...
Click to collapse
Download and install terminal emulator, the run these commands:
1. su
2. getprop ro.bootloader
Awesome! I was able to confirm I'm still using the MK2 bootloader. Thanks for all your help!