Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
I see its been a few days and no one has replied so I will do my best to share what knowledge I have. I've been heavily flashing custom ROMs on my ASUS tablet now for the better part of a year and just got my Verizon GS4, so I have alot of the same questions as you.
1) I'm going to answer this in two parts.
Nandroid, in my experience, refers to the type of backup, not necessarily the process by which to backup. Most common recoveries, including ClockworkMod and TWRP have a feature to create a 'nandroid backup'. This can take some time and files can be quite large, as they copy pretty much every single file on your device; almost like creating a snapshot of your device in that moment in time.
To answer the later part of this question, (typically speaking) once you unlock a bootloader you cannot re-lock it, but that could be different for phones (my knowledge in phones is limited). And yes, using a nandroid backup will back up your device with root access, but using a tool such as Rom Toolbox, you can easily un-root (the program features a 'permanent unroot option'). For one, I would imagine that flashing the stock kernel would overwrite the root, as like you said earlier in the post the current root exploit works by flashing a pre-release kernel, applying root to the device, then re-flashing the current stock kernel. Another way to lose root is to get an over-the-air (OTA) update. You will see programs like OTA Rootkeeper that work to circumvent this, but in your case that may be a valid way to cover your arse in case you need to return it under VZW warranty (it is for this reason that I always buy Best Buy protection plans, because they could care less about the software state about your device [Disclaimer: I worked for Geek Squad so I have /somewhat/ intimate knowledge in this matter])
2) I just rooted my GS4 a few days ago, and nothing I read indicated that the all-in-one tool would unlock the bootloader. If you read the documentation about Loki, he explains this fact. I just found a good video (although it uses TWRP and GooManager instead of ROMManager and CWM) explaining that there isn't a bootloader "unlock" just yet; rather its a workaround to the bootloader that allows us to get custom ROMs on our devices (video is here)
3) "Bricking" a device means rendering the device useless; it won't operate to any fashion that it is useful to you, so its no better than a brick or a paper weight, etc. I would imagine you can re-flash a stock verizon ROM/kernel to restore any screw-ups, but keep in mind this device was released less than three months ago and any development is relatively new. Yes, we have had other Galaxy S series phones, but the S4 has this whole KNOX nonsense that is specifically designed to prevent the kinds of activities we do here on this forum
I really hope that helps. If I said anything that is incorrect, please please feel free to correct it so that at least we can all learn the proper information.
Thanks,
Opethfan89
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
DarkMenace said:
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
Click to expand...
Click to collapse
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
opethfan89 said:
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
Click to expand...
Click to collapse
I'm not n sure. It's the only one I ever used for banner blocking. You use the files with Odin as well after they are extracted.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Related
My device: Vzn Galaxy S4 (ME7 build)
I've rooted the phone, installed things like ROM Manager and Titanium backup, but insofar as I understand things ... its not safe (or recommended at least) to flash a custom ROM until the bootloader is unlocked and I have a custom recovery installed. Further, as I understand things, that isn't possible with ME7.
Anyhow, new to the Android and rooting world, and so I wanted to know if I got things right ... and if not, best process for backing things up, flashing ROMS, and getting back to where I started should I so desire.
Thanks much.
wgpubs said:
My device: Vzn Galaxy S4 (ME7 build)
I've rooted the phone, installed things like ROM Manager and Titanium backup, but insofar as I understand things ... its not safe (or recommended at least) to flash a custom ROM until the bootloader is unlocked and I have a custom recovery installed. Further, as I understand things, that isn't possible with ME7.
Anyhow, new to the Android and rooting world, and so I wanted to know if I got things right ... and if not, best process for backing things up, flashing ROMS, and getting back to where I started should I so desire.
Thanks much.
Click to expand...
Click to collapse
DO NOT FLASH A ROM ON STOCK RECOVERY!!!
their is a $3,000 bounty for just root + recovery for a good reason.
No you can't flash a custom recovery or roms if your phone installed the ME7 ota update. Titanium backup is your best bet to remove bloat and backup apps/data. if anything goes wrong you can always flash back to stock ME7 via odin.
No way, you are stuck until a patch, or a fix is done for the bootloader.
Only flash if you want to brick your phone and not have it covered by warranty. Once you have the ME7 bootloader, you no longer have the ability to flash roms, recoveries, kernels, etc.
Sent from my Nexus 7 using Tapatalk 4
I had to send my phone back because of a defect with the power. anyways, they sent me back a refurbished S4 and i only updated it to firmware MI1, realizing i had 2 software updates available. My first thought was about rooting, because i had wanted to root my phone until i realized i had MJ7 or whatever the latest one was and wasn't fond of the ideas. My question to you guys is, should i root my S4 and stay on MI1? is there a way i can do this and bypass the warranty void in the system?
All versions are rootable, even the MK2 that came out recently. The only reason so far to stay old is for ROM loading.
I for one am totally ok with never seeing another alternate ROM again, after two years of ROMing my Galaxy Nexus and the two years before that ROMing an Incredible.
When you say ROM loading, can you elaborate? Do the benefits of rooting at this software stage outweigh the benefits of the more recent ones? are some ROMs not compatible with higher softwares? because i remember MJ7 came up as "custom" and i most importantly don't want to trip my warranty, if possible. Especially because i just got this phone and don't want them to add to the bill if they see that the warranty got tripped before they even received my original S4.
Any rooting will bring up the 'custom unlock icon.
A ROM is a completely standalone full operating system custom made by developers that know how to make them. They are usually based upon Google's Open Source Android operating system source code with customization to suit the developer. It requires the phone to be not locked down to be able to install a ROM. When the phone is not locked down, a 'Custom Recovery' can be installed. Custom recovery is needed to load a ROM into the phone. Only the originaal S4 firmware, the MDK level from back in June, can have a custom recovery.
Rooting lets you run apps requiring root, such as the popular Titanium Backup, Root Explorer, and many others.
Rooting just lets you pretty much do whatever you want within the installed OS, but just not replace the OS. As I said, all the firmware loads for the S4 to date are rootable.
JeeperDon said:
Any rooting will bring up the 'custom unlock icon.
A ROM is a completely standalone full operating system custom made by developers that know how to make them. They are usually based upon Google's Open Source Android operating system source code with customization to suit the developer. It requires the phone to be not locked down to be able to install a ROM. When the phone is not locked down, a 'Custom Recovery' can be installed. Custom recovery is needed to load a ROM into the phone. Only the originaal S4 firmware, the MDK level from back in June, can have a custom recovery.
Rooting lets you run apps requiring root, such as the popular Titanium Backup, Root Explorer, and many others.
Rooting just lets you pretty much do whatever you want within the installed OS, but just not replace the OS. As I said, all the firmware loads for the S4 to date are rootable.
Click to expand...
Click to collapse
Yeah, i just didn't want to void the warranty. I think i am going to root my s4 tonight. any suggestions?
ImportedPerfection said:
Yeah, i just didn't want to void the warranty. I think i am going to root my s4 tonight. any suggestions?
Click to expand...
Click to collapse
If sort of depends what you want to do. If you want the flexibility to run custom ROMs with Safestrap, you should stay on ME7 or MI1.
If you're on MI1 and want to root it, can you please try the rooting technique in this thread? I'm curious if it'll work on MI1.
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, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
there are a lots of guide but everyone say a different method. OK I AM A NOOB OF MODDING.
but is quite difficult to understand guides that are different in this way:
1) some indicates to just use an apk autorooting the device
2) some do require to change thekernel + manually install the superuser apk
3)not permanent root....
4) others......
so, please be patient......:angel: i only want to find a "normal" root method.......and IF POSSIBLE a root that could allow me to easily UNroot the device to be able to update my firmware OTA in the moment samsung will update our great device to kitkat
If you are a noob at modding don't even bother with rooting. Its dangerous and BTW I think your firmware has KNOX which the GMega doesn't have a workaround.
Sent from my GT-I9200 using Tapatalk
realista87 said:
hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
Click to expand...
Click to collapse
If you are brave enough you can try it using this tutorial
http://forum.xda-developers.com/showthread.php?t=2574953
But read it thoroughly and if you do not understand one thing though - do not attempt to try.
Read forums and learn till you can understand what you are doing lest you have quite expensive paperweight... I am not responsible for what you do with your phone!
my previous phone was rooter, the optimus 3d and the ascend mate.
i don't need toor for extreme modding but just to install a custom recovery for a nandroid backup and for use SOME APP THAT REQUIRE root to work properly.
i never installed a recovery but i read everywhere that it is a lot usefull in case of some errors, to restore the previous backup made 1:1 (nandroid)
Every modding attempt must start from root and (optionally) custom recovery. In fact - rooting itself is modding and quite heavy from system point of view. If you want to change ONE THING in system, you have to root your phone. Doing this you are tripping 'warranty flag' and from now on your warranty is void.
If you have firmware with KNOX and new bootloader - tripping this flag is irreversible. But as long as you do not attempt to flash older firmware (before KNOX) it does not affect the operation of the system. Trying to flash older firmware makes your phone softbrick because of tripping security mechanism in new bootloader.
If you already rooted your phone it is resonable to flash custom recovery and by this have wide possiblity making backups of your whole system (nandroid backup) or flashing custom ROMs
Hello. I have done quite a bit of searching, just can't find a similar enough post to tag on some questions. Sorry if this has been asked...but I did look over a month of posts, and google searching.
I have a Note 3 from September, rooted in October...not sure how I got it done...but I jumped the gun and unrooted it with SU thinking I would be able to OTA to 4.4.2. Nope!
So, I am stuck on 4.3.
My big question is how can I get to 4.4.2 with OUT starting over on the phone.
I guess this is a backup question. I have some settings turned on that indicate that a back up is going somewhere, but I can't confirm, and I don't know what all is backed up.
Pictures are backed up, but I would hate to lose them. They are on SD card anyway...so I realize I could take the card out, but something I read suggested I might lose even the micro-simm card contents. Not sure how that would be possible.
But what about things like Quick Notes, and S Note, and Contacts, and all of my apps that I have installed, and settings for those apps.
When I rooted back in October, it worked with out disrupting anything.
How can I get that to happen now WITH an upgrade to 4.4.2 AND getting it rerooted?
If I can't upgrade with out wiping it clean, I am probably going to stay put. So, then what is the best way to root to get "Wifi Tether Router" back working...as it is the only thing I need the phone rooted for.
Finally, what is the difference between NC5 and NC5D. I saw a recent post of somebody else asking it...but none of the replies gave an answer.
Thanks for any feedback.
I don't know if this will help, but you can give it a try. First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ). Ok, I would go to Samsung Firmware, and download the latest version of 4.4.2 NC5 to your PC. I would backup that copy of 4.3 on your device to your sdcard then if have an ext sdcard copy it there, or copy that backup to your pc. Most of your Pics and data should be in that backup, that you can copy back later with a file explorer like Root Explorer. Now do a factory wipe. Then take the NC5 zip you got from sammie and extract it to a file on your desktop this will change it to a .tar file. Find a copy of Odin v1.85 don't use the 3.09 version on the Samsung website if possible. Cool, reboot your device into download mode, start odin, plug in your device to your PC. Now, load that extracted file on your desktop into PDA odin, and click start. It will take minute to read Md5 then start installing. You will lose root and recovery !!! Your new bootloader will have KNOX 0x0. So, you will have to start over with the root process, but isn't that half the FUN !!! Chainfires v1.94 supersu will root NC5. As for the difference between NC5 and NC5D, It is my understanding they are the same. The D stands for a version of NC5 that was used by Samsung employees ( i.e. programmers and developers ) in the development of NC5. :fingers-crossed::fingers-crossed:
Lokerd, I see you have read my response. Great!!! I would add the you can root 4.4.2 NC5 several ways. As I said above Chainfires v1.94 SuperSu, and One click autoroot, and Towelroot for 4.4.2. All should root your device without tripping KNOX. However, as soon as you flash a new custom recovery like TWRP or Philz CWM ( my favorite ) it will trip KNOX. If you are out of warranty no biggie, besides you need a custom recovery if you want to get back to your 4.3 backup. ( By the way remember you need the same recovery (i.e. TWRP or CWM ) that you made the 4.3 backup with, now on NC5 just a newer version. This will make it easier to recover the 4.3 backup later. They say the most popular recoveries will recover each others backups, but that is rarely the case.
jimzweb1 said:
First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ).
Click to expand...
Click to collapse
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
lokerd said:
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
Click to expand...
Click to collapse
Well, if you are out of warranty, and you don't care about KNOX go ahead and upgrade. But, consider this: One, so where clear the only reason for the 4.3 backup is to get to your pics and data at a later time. Here is a link about trying to go back http://forum.xda-developers.com/showthread.php?t=2630514 Once you install 4.4.2 NC5 ( this will include a new kernel, bootloader, baseband, and OS ) you CANNOT go to back to 4.3. If you try to install the 4.3 backup after you have upgraded to NC5 you will soft brick your phone. Then, there's KNOX what is KNOX, KNOX is security software written by the NSA for Samsung. Now I'm not saying its spyware, but Samsung is !!! You can go to Samsung's website and all the info about KNOX you need is there.
To answer your last question, no. You have to go through all the motions.
If it was me, knowing what I know now. I would stay at 4.3, install an engineering bootloader (read up on bootloaders they are not forgiving if you mess up ) then try to upgrade basebands. Here is a link for NAB engineering bootloader which should be 4.3, http://forum.xda-developers.com/showthread.php?t=2655674 Here is the link for a NC5 baseband, http://forum.xda-developers.com/showthread.php?t=2701837 I believe this will improve your 4G lte.
Last, what I'm running. I run Note 3 "Sprint" 4.4.2 NC5 ( no choice bought the device new with that OS, voided my warranty the second day I owned it ). Rooted with Philz CWM recovery ( hltespr v 6.12.9 ) KNOX disabled and removed. I definitely like 4.4.2 NC5 a lot better than 4.3 my daughters Note 3 had 4.3 before I upgraded to 4.4.2 and rooted it. Here is my XDA website http://forum.xda-developers.com/showthread.php?t=2770729 so if you do upgrade this is a good place to start.
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
lokerd said:
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
Click to expand...
Click to collapse
Cool, your version of 4.3 should be NAB and no KNOX. If this is the case then you should be able to root, and return back to stock, if you have say a hardware issue with your device and have to return it under warranty. So, according to your last post image on 10/24/2013 you used CF Autoroot, if you want to read up here is the link to that http://forum.xda-developers.com/showthread.php?t=2466423
Now to get to the latest version of CF Autoroot you need to go to ChainFires ( CF ) repository here is the link http://autoroot.chainfire.eu/ just find the model of your phone and click on File to download. Put that file on your desktop, now go to your android downloads copy and paste Odin v1.85 to your desktop. Click on Odin extract, and open it, now click on PDA a box will open, now select desktop and click on CF Auotroot. It should come up in Odin next to PDA. Now boot your device into download mode, then connect to your PC. In the upper left hand box will light up COMM: with some number in green, blue, or yellow doesn't matter just telling you that a connection was made. Now click start on the bottom of Odin, sit back and watch the magic!
When it says pass your done. Now reboot your phone if doesn't do it by itself go to your app drawer and see if SuperSu is there. To install the Recovery just follow the same steps just substitute the recovery .tar file in place of CF Autroot. I see you have ChainFires v1.65 SuperSu the latest version is v2.01 here is the link http://forum.xda-developers.com/showthread.php?t=1538053. If you use CF Autoroot it will probably install the latest version of SuperSu automatically.
I see on 10/25/2013 you downloaded CWM recovery for hltespr ( sprint ) here is the link for Philz CWM http://forum.xda-developers.com/showthread.php?t=2596001 the latest version for sprint is 6.12.9 I don't use his unified all in one recovery version, I use the sprint version, but the choice is yours. :fingers-crossed:
jimzweb1 said:
Cool, your version of 4.3 should be NAB and no KNOX.
Odin v1.85 to your desktop.
Click to expand...
Click to collapse
Thanks for the continued help. Just about ready to reroot the thing.
So, you mention using 1.85...is that only because that is what I have? The latest CF-Auto-Root came with 3.07 but I had already downloaded 3.09 a couple of days ago trying to figure stuff out. I also saw a warning about using the latest Odin...but I think it applied to trying to do the Kindle Fire, which I determined was 3.3 and not able to be rooted with out a special cable, which I have ordered.
Anyway, does it matter if I use the 3.07 that came with the latest version of CF-A-R? Should I use 3.09? Or def stick with 1.85.
EDIT #5: I end up using 1.85 and the original Root, then the new ROOT. So, does it matter that I used the Root from October vs the newest one or older Odin vs. newer? I have it up now, so it is just a matter of tryingt o figure this out.
BTW, I thought I had bricked my phone...went back and read YOUR instruction again, and got it restarted. The instructions on the main CF-A-R thread do not make it very clear.
Thanks a bundle!
Great !!! It doesn't matter which version of Odin you use, as long as it gets the job done. As for CF Autoroot, after your done rooting and boot the device back up. It my take awhile but you will automatically be asked update your apps, and SuperSu will update binarys at that time.