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.
Related
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
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.
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
uniroot said:
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
Click to expand...
Click to collapse
1. DO NOT TAKE THE OTA
2. read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick.
Sent from my SCH-I545 using XDA Free mobile app
I've been researching this for a couple of days, and obviously I'm missing some details.
Why not take the OTA for 4.4.x? What am I missing? What's the issue?
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
uniroot said:
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
Click to expand...
Click to collapse
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
joshm.1219 said:
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
Click to expand...
Click to collapse
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
uniroot said:
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
Click to expand...
Click to collapse
It should, but not always. Also you have to use the unroot from the supersu app.
---------- Post added at 01:27 PM ---------- Previous post was at 01:27 PM ----------
Oh and the tar files are here: http://forum.xda-developers.com/showthread.php?t=2735172
I recommend using Odin 3.09
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
uniroot said:
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
Click to expand...
Click to collapse
No, you only need the unroot if you try the OTA. Nothing else needs to be done to use the tar file with Odin, but I would recommend backing up important data to an external SD and flashing the full wipe file to ensure you have a clean system.
Latest OTA "patches" TowelRoot
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
~JohnnyB~ said:
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
Click to expand...
Click to collapse
Towelroot works on NC5, the latest OTA for this device. Towelroot came well after the OTA. If we get another firmware update, I'm sure it will patch towelroot.
I'm looking for some help/advice. I did search and didn't find anything on this although I would think it would have been covered before so my apologies if I missed it and it's already been answered.
I'm currently running Stang5Litre 5.0 OC1 V2 which I installed with Flashfire and I'm having a lot of issues with Good For Enterprise and it's root check. I can get it to work with Xposed as long as I stay on an old version of Good, but I've had two accidental upgrades that triggered a compliance failure and it's a long process with my work to get a new pin to get it going again. Using the detach from market in Titanium doesn't stick. I'm also interested in using Android Pay and can't get that to work at all. So I'm now considering getting rid of root. There isn't that much I do anymore that truly requires a rooted phone other than I really like being able to get rid of all the bloat and being able to freeze and unfreeze in Titanimum.
So my question is what options do I have? Can i fully unroot a debloated ROM or would I need to flash a stock unrooted OC1 ROM? Also, is the fact that my Samsung boot screen shows as unlocked an issue? I know that simply removing SuperSU isn't enough. I don't want to do anything that is going to prevent me from changing my mind down the road and going back to a rooted ROM which I know means not installing anything after OC1.
Any help would be appreciated.
Thanks
After doing a little more research on Good, I think I have no choice but to flash a completely stock unrooted ROM. Apparently it checks too many things to simply remove Root. So what are my options for going back to stock and still keeping the ability to root down the road if I choose?
Thanks
Hi,
I am completely new to custom Android ROMs. I have a Verizon Galaxy S4 with OF1 update. I managed to root my phone using KingRoot, but I'm trying to figure out how to create some kind of backup of my stock ROM. Basically I want to be able to restore my phone back to factory default if I ever run into problems. I read that once I delete something with root, then I cannot get it back again... hence I want the ability to restore my phone to original factory default. I know the GS4 is an old phone now, but I want to squeeze a year of life before I get a new phone (and get some experience with modding Android).
A lot of guides on the internet seem to be suited for older versions of Android on the Galaxy S4, so I didn't find them helpful. Can anyone give me a starting point?
jjhl said:
Hi,
I am completely new to custom Android ROMs. I have a Verizon Galaxy S4 with OF1 update. I managed to root my phone using KingRoot, but I'm trying to figure out how to create some kind of backup of my stock ROM. Basically I want to be able to restore my phone back to factory default if I ever run into problems. I read that once I delete something with root, then I cannot get it back again... hence I want the ability to restore my phone to original factory default. I know the GS4 is an old phone now, but I want to squeeze a year of life before I get a new phone (and get some experience with modding Android).
A lot of guides on the internet seem to be suited for older versions of Android on the Galaxy S4, so I didn't find them helpful. Can anyone give me a starting point?
Click to expand...
Click to collapse
I'm not by any means promoting my videos but I have a few YouTube videos that walk you through the process to get rid of KingRoot and install SuperSU and Install Flashfire. With Flashfire, you can backup your stock ROM for future use. Here are some video links: https://youtu.be/LAENraWBNVM and https://youtu.be/g31TkZE6Vp0
With Flashfire, I would recommend playing around with a couple custom ROMs out there from @stang5litre
Sent from my Nexus 5X using XDA-Developers mobile app
http://forum.xda-developers.com/galaxy-s4-verizon/general/guide-sch-i545-vrugof1-look-t3395833