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
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
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7 Build. However, all the bloatware that remains on the phone is making me want to flash Cyanogenmod.
Problem:
Using ROM Manager (which has always worked on my previous phones) every time I flash into recovery mode it flashes onto Samsung Recovery 3e NOT into TWRP, which I have flashed on my phone and need to use to install any custom ROMS.
Could anyone tell me how to disable Samsung Recovery 3e so I can use TWRP and flash the new ROM?
Or how, using Samsung Recovery 3e, I can flash a new ROM?
Aury said:
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7 Build. However, all the bloatware that remains on the phone is making me want to flash Cyanogenmod.
Problem:
Using ROM Manager (which has always worked on my previous phones) every time I flash into recovery mode it flashes onto Samsung Recovery 3e NOT into TWRP, which I have flashed on my phone and need to use to install any custom ROMS.
Could anyone tell me how to disable Samsung Recovery 3e so I can use TWRP and flash the new ROM?
Or how, using Samsung Recovery 3e, I can flash a new ROM?
Click to expand...
Click to collapse
Your only option at present is Safestrap. It's the only recovery that allows custom roms on the ME7. Developer is Hashcode.
http://forum.xda-developers.com/showthread.php?t=null
Also a thread about Roms that work with Safestrap. CM is not one of them. But you will enjoy Hyperdrive, Eclipse and others. Everything from a near AOSP to TouchWiz to the max.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
wtherrell said:
CM is not one of them.
Click to expand...
Click to collapse
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
alburdet619 said:
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
Click to expand...
Click to collapse
With the original build, (MDK), there was an exploit that let you bypass the bootloader, so you could flash any ROM. Since the updates, (ME7 and MI1) that exploit has been locked and there is no way, as of now, to bypass the bootloader. Also, there is no way to go back to MDK once the phone has been updated. The only option for ME7 and MI1 users is to use Safestrap, with the appropriate kernel module, and flash TW ROMs only.
alburdet619 said:
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
Click to expand...
Click to collapse
It is not possible to install CyanogenMod on any revision later than MDK at the moment.
They're building CM for the S4 for those fortunate enough to have revision MDK, which has a bootloader that can be bypassed.
Aury said:
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7Build.
Click to expand...
Click to collapse
I see your question has been answered, let me add a little information that may save you reading a few billion posts here!
The Galaxy S4 has a locked bootloader that cannot be unlocked so far.
There is a workaround called Loki that bypasses the bootloader to allow a new bootloader such as CM or TWRP to be flashed.
The ME7 build "fixed" the exploit that Loki used to bypass the bootloader so you're now stuck with the stock bootloader.
Start reading up on SafeStrap, that allows some TouchWiz ROMs to be flashed to the SD card but, so far, no non-TW ROMs work.
Sorry but at least some devs are still working on unlocking the bootloader, let's hope they are successful.
Hi all,
Today I set aside my 900T and purchased a 900V on a contract. I got it home and Rooted it within minutes using Towel Root. I'm not 100% sure about Safestrap. I have never owned a locked bootloader phone before this, so this is new territory for me.
I want to be able to install a Modded Stock ROM at the very least, safely. I would also like a Custom Recovery for Nandroid backups.
Does anyone have any suggestions, tips or advice they may want to share? My 900T was owned outright, this V is under contract (no warranty obviously) so I just want to be that much more safe is all. The Rooting process was easy peasy, which surprised me. Is there anything I should be aware of when I install SafeStrap?
Thanks everyone. Glad to be back on the Verizon Network again.
Welcome to the locked bl club. Install safe strap. Download any TouchWiz rom and reboot. At the ss splash screen tap recovery. It's like twrp. Backup. Then do a factory reset. Install rom. Reboot to download mode. Odin the nc2 kernel. Reboot and enjoy!
What's gained or lost by flashing the NC2 kernel? Just curious. It's on build NC4 now.
Ed Murray said:
What's gained or lost by flashing the NC2 kernel? Just curious. It's on build NC4 now.
Click to expand...
Click to collapse
You are already on nc4 so don't bother with nc2 it is of no use to you. The good news is that you can use titanium backup to debloat your stock setup.
[I just realized I'm in the wrong subforum, please move to Verizon i535 forum, thanks]
My initial intention was to backup the phone before attempting to install Cyanogenmod on it.
I ran towelroot and installed Rom Manager, and flashed the custom recovery.
Upon attempting to enter recovery, it's telling me that some non-Verizon system software is detected so I can't even get in there to backup my phone. I researched and apparently after 4.2 all the bootloaders are locked and cannot be rommed. That sucks, but anyway, this thing is already running 4.4.2 (just got in from Ebay purchase).
How can I get back the stock recovery? I've searched all over the forums but can't quite find what to do. Something with Odin and a stock image? Does that exist for 4.4.2?
TIA
You can get stock recoveries on the net but if you cant flash it you need to go to samsung-updates.com and download the latest rom for that device, flash it with odin then re root it. If there's a cf-autoroot for it you should use that, otherwise any other recommended method.
If your lastest rom on the website is earlier than 4.3 then dont worry about efs etc as custom roms dont change that
If it IS 4.3 or later do not flash anything lower than 4.3. This is because you dont know what the last stock version was.
Going back to stock via odin should solve any issues with all sammy devices. Common sense and reading a lot goes a long way.
Dont forget to reset to factory when flashing back to stock, most common cause of boot loop.
Sent from a stolen phone!
I'm currently rooted on 4.3 MJ4. Yes I'm outdated and decided to finally update. I'm going to flash to stock 4.3 MJ4. My questions is, after I flash to stock 4.3 MJ4. Can I flash NC5 from MJ4? Or would I have to do it in these steps ( MJ4 then NAB then NC5? ).
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
evilvoice said:
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
Click to expand...
Click to collapse
Awesome! Thanks! I am trying to flash a stock rom, but thought I would need to go in steps instead of instantly flashing to the most current version.
As for my plan: I'm rooted and on a custom rom. I want to go back to stock rom and then root again and flash to either cm12.1 or cm13. From what I've read, I cant flash to either cyanogenmod roms until I was on either lollipop or higher. I was also thinking, would it work if I was to flash a rooted current version of a stock rom, that way I don't have to flash a stock rom and break root and have to root it again?
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
evilvoice said:
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
Click to expand...
Click to collapse
What is the PH1 rom? I've already flashed to stock NC5 so far and lost root.
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
evilvoice said:
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
Click to expand...
Click to collapse
EDIT: I went ahead and used the Full Restore. Fortunately, it did not WIPE any data. YEAH! And it looks like I am on my way to an updated NOTE3.
Hello. My Note3 is on 4.3. It was rooted a couple of years ago, but out of use since Oct 2015. I still want to use the Note3 for non-cell phone operations, browsing, camera, etc. I want to upgrade, but the OTA is locked out.
I am lost on all of the many, many posts on how to updated a rooted Note3, but most of them are outdated. I have it mostly backed up as far as handwritten notes, photos, etc. But I don't really want to have to start from scratch if I don't have to.
I am currently reviewing rwilco's one click options. There are two software packages listed in his directory. One of them is dated 02/27/15 and is called nodata restore. Will this keep from wiping the phone as opposed to the fullrestore exe posted 04/12/14 vs the tar posted 02/27/15.
I am not a complete dodo, but I am having a hard time getting this phone unrooted and updated.
Thanks for any detail instructions or links to the best way to update this as of 9/5/2016!!!
Everything you need to know is explained here. http://forum.xda-developers.com/galaxy-note-3/general/guide-how-to-disable-air-command-pop-t2960839
Sent from my SM-N920C using XDA-Developers mobile app