As many of you know, we have a update for the 4.4 KitKat version. Also, most people are rooted with SS and some runnning a custom ROM like myself. My question is, how can I fully unroot my phone beacuse I thought I unrooted it fully and the error message popped up. Should i do the unbrick method with the MF3 stuff. Or what other option. Im not brocked though.
I would flash your firmware version in Odin and then take the ota. Back everything up first of course. Also there is currently no root method so tibu is not a good backup solution.
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!
I can't seem to find a thread where there are steps from how to get custom rom when you begin with stock without root.
I had an s2 and I could flash philz recovery (temporary recovery) and install custom rom from there, but I don't know how to do it on the S4.
Is there any tutorial from how to get the custom rom installed on the s4?
(this is the hardest part, the rest is simple)
ps: yes, I know how to recover and fix broken phone, I always use a AOSP rom, but I can't seem to understand how to get a custom rom installed on a phone that is 100% stock without root.
Nevermind, I know how to do it.
Hey.
If I install TWRP recovery and then a custom rom.
If I go back to stock with LG Flash tool, will it remove TWRP also?
Since that'd be great for warranty purposes.
And another tiny question, I'm currently rooted, if I do a factory reset with button combination, it won't cause any problems?
Since I read that if you update to lolipop OTA while rooted your phone gets bricked.
Bump.
Hello
First let it be known that i have searched my butt off and tried many different things. The best i could get was a rooted phone and a non working safestrap install.
Can someone please give clear instructions here in this thread to either a) install safestrap on 4.4.2 nc4 or b) let me know if it's possible to install verizons stock lollipop firmware using odin (no recovery required).
I would love to get a working custom recovery to try different roms. Failing that, id love to know if it's possible to just flash stock lollipop firmware on this device.
I'm sorry to make such a request, as my first post.. But have been rooting and roming and xdaing since the Samsung vibrant. I'm just tired of trying to make this locked bootloader work. I must've tried a hundred different things.
As of right now ive odind back to 4.4.2 stock with nc4 kernel and said root, busybox, and supersu.
I'm familiar with odin, flashing, all the terminology, and can find the files on my own.
scottayy said:
Hello
First let it be known that i have searched my butt off and tried many different things. The best i could get was a rooted phone and a non working safestrap install.
Can someone please give clear instructions here in this thread to either a) install safestrap on 4.4.2 nc4 or b) let me know if it's possible to install verizons stock lollipop firmware using odin (no recovery required).
I would love to get a working custom recovery to try different roms. Failing that, id love to know if it's possible to just flash stock lollipop firmware on this device.
I'm sorry to make such a request, as my first post.. But have been rooting and roming and xdaing since the Samsung vibrant. I'm just tired of trying to make this locked bootloader work. I must've tried a hundred different things.
As of right now ive odind back to 4.4.2 stock with nc4 kernel and said root, busybox, and supersu.
I'm familiar with odin, flashing, all the terminology, and can find the files on my own.
Click to expand...
Click to collapse
Yes..you can flash stock firmware for 5.0 via Odin. You will lose root and as of this time....can not root 5.0
once on 5.0, you can only odin back to 4.4.4 which is also unrootable.
simplyeorange said:
Yeah you can go back to 4.4.4 I've read post of people on this forum saying they were able to get back to 4.4.4 you need to download the stock tar. Which you can find on sammobile than boot into download mode and then open Odin flash the stock tar. After its done flashing Then boot into stock recovery and do factory data reset. Wait about 5-10mins and should boot you into 4.4.4
Click to expand...
Click to collapse
Sent from my Note 3 via Tapatalk
Thanks for that. I'm sorry about the aggressive tone of my original post. I was just quite frankly mad at how much verizon locked the note 3 down. I own it, you know? Lol.
I wanted custom recovery mostly for the nandroid backups. If i flash the nc2 kernel on 4.4.2 with nc4 kernel... Supposedly this is supposed to make safestrap work with one rom slot (stock). I tried this but it soft bricked. Is there a custom nc2 kernel I'm supposed to flash?
Also if i odin the stock 5.0 files will this keep all user apps and data? I suppose i could use titanium backup for that but I'm not sure if it will be compatible from 4.4.2 to 5.0?
I guess i have to debate whether i want nandroid backup abilities or lollipop.