Related
Hey guys I'm on rooted MDC with TWRP. I want to install the OTA update before flashing ForceROM. What's the proper course of action so everything fine and dandy?
I've read that I have to unroot, OTA, reroot, THEN flash. Is that correct, or is there an easier method now?
jo0b4k4 said:
Hey guys I'm on rooted MDC with TWRP. I want to install the OTA update before flashing ForceROM. What's the proper course of action so everything fine and dandy?
I've read that I have to unroot, OTA, reroot, THEN flash. Is that correct, or is there an easier method now?
Click to expand...
Click to collapse
I am pretty sure that's correct. I am still on MDC because I don't feel like going through all that right now and I have my phone all nice and setup.
some people have had luck installing the OTA with root but for the most part you are correct. unrooting is the only sure fire method as of now.
I just use the one click stock restore which wipes everything and start from scratch.
Sent from my SPH-L720 using Tapatalk 2
I want to know if this is correct,I am on Stock(MDL) with Recovery and Root. If do Flash the latest OTA Firmware to MF3(from AT&T) I can not go back to my Original MDL with the Odin and the Stock.tar file? Also if I do try some of the Custom ROMs now coming out now going from my Present Stock MDL will I or won't I be able to get back to MDL Stock with Odin? One last question,once I am on mF3 no matter if it Stock or Custom my MDL Nandroids are useless?
Thanks
RonH54 said:
I want to know if this is correct,I am on Stock(MDL) with Recovery and Root. If do Flash the latest OTA Firmware to MF3(from AT&T) I can not go back to my Original MDL with the Odin and the Stock.tar file? Also if I do try some of the Custom ROMs now coming out now going from my Present Stock MDL will I or won't I be able to get back to MDL Stock with Odin? One last question,once I am on mF3 no matter if it Stock or Custom my MDL Nandroids are useless?
Thanks
Click to expand...
Click to collapse
This thread should help answer your questions.
http://forum.xda-developers.com/showthread.php?t=2357039
scott14719 said:
This thread should help answer your questions.
http://forum.xda-developers.com/showthread.php?t=2357039
Click to expand...
Click to collapse
Thanks.
scott14719 said:
This thread should help answer your questions.
http://forum.xda-developers.com/showthread.php?t=2357039
Click to expand...
Click to collapse
try this:
http://forum.xda-developers.com/showthread.php?p=43512474
RonH54 said:
I want to know if this is correct,I am on Stock(MDL) with Recovery and Root. If do Flash the latest OTA Firmware to MF3(from AT&T) I can not go back to my Original MDL with the Odin and the Stock.tar file? Also if I do try some of the Custom ROMs now coming out now going from my Present Stock MDL will I or won't I be able to get back to MDL Stock with Odin? One last question,once I am on mF3 no matter if it Stock or Custom my MDL Nandroids are useless?
Thanks
Click to expand...
Click to collapse
1) To flash the latest OTA you will need to get back to stock (lose recovery and root) or it will not let you update. See next 2 posts for the possibility of "temp-unrooting" in order to update to the MF3 OTA and regain root access.
2) At this point, once you go to MF3, you cannot downgrade to MDB or MDL. Maybe someone will find a way around this in the future.
3) If you stay on MDL and then try some custom ROMs, you can always go back to MDL (fully stock) if you follow the correct procedure. Since you are already rooted with custom recovery, you will have to do this same process if you decide to go to MF3 (as mentioned in #1 above).
The process is outlined here:
http://forum.xda-developers.com/showthread.php?t=2261573
You will probably need to perform a data wipe as well in order to be fully stock.
4) Your MDL Nandroids might contain information that you can extract at a later date to help with some issues...but generally they will not help you very much. Since you cannot go back to MDL (at least for now), you cannot restore your phone from that backup.
jeffreii said:
1) To flash the latest OTA you will need to get back to stock (lose recovery and root) or it will not let you update.
2) At this point, once you go to MF3, you cannot downgrade to MDB or MDL. Maybe someone will find a way around this in the future.
3) If you stay on MDL and then try some custom ROMs, you can always go back to MDL (fully stock) if you follow the correct procedure. Since you are already rooted with custom recovery, you will have to do this same process if you decide to go to MF3 (as mentioned in #1 above).
The process is outlined here:
http://forum.xda-developers.com/showthread.php?t=2261573
You will probably need to perform a data wipe as well in order to be fully stock.
4) Your MDL Nandroids might contain information that you can extract at a later date to help with some issues...but generally they will not help you very much. Since you cannot go back to MDL (at least for now), you cannot restore your phone from that backup.
Click to expand...
Click to collapse
Not true. I flashed the OTA while keeping and retaining root with VooDoo Root Keeper (not even temp-unrooting). The custom recovery part is accurate. Also, there are MF3 ROM's out now that are working great. No need to take the OTA at this point unless you'll never explore any further than stock.
The key to successfully retaining root is to have had a full backup made right after gaining root access, restoring that backup, using VooDoo Root Keeper (some people had success with Pro-SuperSU's Root Survival Mode) to backup root, and take the OTA. After everything is said and done you'll be rebooting and restoring root with VooDoo.
Delakit said:
Not true. I flashed the OTA while keeping and retaining root with VooDoo Root Keeper (not even temp-unrooting). The custom recovery part is accurate. Also, there are MF3 ROM's out now that are working great. No need to take the OTA at this point unless you'll never explore any further than stock.
The key to successfully retaining root is to have had a full backup made right after gaining root access, restoring that backup, using VooDoo Root Keeper (some people had success with Pro-SuperSU's Root Survival Mode) to backup root, and take the OTA. After everything is said and done you'll be rebooting and restoring root with VooDoo.
Click to expand...
Click to collapse
You're right that I forgot to offer the advice about using Voodoo to preserve root (if he wants to). I should have included that...so thank you - I will update my post.
However, it is true that you need to convince the OTA update that you are not rooted in order to proceed. Whether you actually unroot or use the "temp unroot" option in Voodoo, it's the same premise. You are losing root, whether temporarily or permanently, in order for it to work.
The caveat here, that should also be mentioned, is that others have reported mixed success when using Voodoo to preserve root through the MF3 OTA. It is definitely possible, but we don't seem to be 100% sure on exactly what conditions must exist for it to work. Some have tried the method and found up on MF3 without root, and no way to gain root or downgrade. Whether or not that is user error or some parameter that we missed, we don't know yet.
Also, note that if you do successfully preserve root after the MF3 OTA, if you ever lose it for any reason...there is currently no way to regain it. You will be stuck on MF3 without root.
Hi,
I have OUDHS-Recovery-jfltespr-1.0.3.3 and CF-Auto-Root-jfltespr-jfltespr-sphl720 flashed on my SPH-L720, on what was stock 4.2.2
My question is, do I HAVE to nuke & pave (factory reset) to get this to 4.3 and then re-root it?
If so, why? I thought one of the big advantages to rooting an Android was the ease with which you could un-root and return to stock.. I remember having to do factory resets to update iPhones before re-jailbreaking them, what a joy! I was hoping to avoid that here, especially as I'm behind a restrictive data cap for internet (~10GB/mo, which is about 300MB/day, combined up & down).
So... any ideas?
0x6A7232 said:
Hi,
I have OUDHS-Recovery-jfltespr-1.0.3.3 and CF-Auto-Root-jfltespr-jfltespr-sphl720 flashed on my SPH-L720, on what was stock 4.2.2
My question is, do I HAVE to nuke & pave (factory reset) to get this to 4.3 and then re-root it?
If so, why? I thought one of the big advantages to rooting an Android was the ease with which you could un-root and return to stock.. I remember having to do factory resets to update iPhones before re-jailbreaking them, what a joy! I was hoping to avoid that here, especially as I'm behind a restrictive data cap for internet (~10GB/mo, which is about 300MB/day, combined up & down).
So... any ideas?
Click to expand...
Click to collapse
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/showthread.php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
oops
Ironically, I had just rooted the day before 4.3 came out. The only 'mod' I have is the CWM custom recovery.. I'm guessing that's what's tripping it up?
When I try to apply the update .zip in CWM, it says,
Code:
-- Installing: /sdcard/0/Download/update_SPH-L720_MDL_CSB_user_RP_to_MF9_CSB_user_RP.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check(" /system/app/AllSharePlay15.apk", "dae9b84dd3cb4810371f2a6136a0536cac926af5", "37b87ff87a955c98258cef2145b4b7b913eb0752")
E:Error in /sdcard/0/Download/update_SPH-L720_MDL_CSB_user_RP_to_MF9_CSB_user_RP.zip
(Status 7)
Installation aborted.
Aaaaand, I found the problem. MF9 is 4.2.2, yes? I've already got that, I need to be trying to flash MJA/4.3 :silly: For some reason I thought MF9 was 4.3, until I realized I had it already and I'm on 4.2.2. Sorry for the confusion. Now to find the 4.3/MJA download... :cyclops:
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu ='Titanium Backup', I'm assuming?or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/show....php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
Click to expand...
Click to collapse
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Sent from my GT-N5110 using Tapatalk 4
cruise350 said:
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Click to expand...
Click to collapse
Correct. And you can get the MF9 one here:
http://forum.xda-developers.com/showthread.php?t=2357471
Camera MJA firmware manual update - possible?
jejb said:
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/showthread.php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
Click to expand...
Click to collapse
cruise350 said:
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
jejb said:
Correct. And you can get the MF9 one here:
http://forum.xda-developers.com/showthread.php?t=2357471
Click to expand...
Click to collapse
Thanks guys. I ended up installing SAC's 4.1 (based on Android 4.3), after manually flashing the MJA modem firmware.
(Because even after flashing stock recovery, I was getting error 7 or something like that, no clue why, I tried searching a few days, but no dice. The recommendation was to flash non-destructive MF9 stock update over first and then update, so I just downloaded Sac's while I had 4G on the way back from work).
NEW QUESTION: How do I get the updated camera firmware, as Sac's modded stock camera seems not to have it. (although, maybe Sac's camera is in error and the firmware is already updated it just doesn't realize).
I can get a patched camera to not do the popup, but I want the firmware. Any way to extract it from the stock MJA OTA file and flash just that?
0x6A7232 said:
Thanks guys. I ended up installing SAC's 4.1 (based on Android 4.3), after manually flashing the MJA modem firmware.
(Because even after flashing stock recovery, I was getting error 7 or something like that, no clue why, I tried searching a few days, but no dice. The recommendation was to flash non-destructive MF9 stock update over first and then update, so I just downloaded Sac's while I had 4G on the way back from work).
NEW QUESTION: How do I get the updated camera firmware, as Sac's modded stock camera seems not to have it. (although, maybe Sac's camera is in error and the firmware is already updated it just doesn't realize).
I can get a patched camera to not do the popup, but I want the firmware. Any way to extract it from the stock MJA OTA file and flash just that?
Click to expand...
Click to collapse
Error 7 is normally when your recovery pics up that you are rooted. Or when there is a problem with the updater script in the zip file.
If sacs used the MJA camera as a base for his nodded camera then he should have the latest camera firmware.
If you worry this much about Tue camera you can download a stock rooted MJA ROM and go into system/apps with a root explorer and extract the camera apk. Then go to where the camera apk is extracted to and move it to your internal memory under system apps. Then set permissions and reboot.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Error 7 is normally when your recovery pics up that you are rooted. Or when there is a problem with the updater script in the zip file.
If sacs used the MJA camera as a base for his nodded camera then he should have the latest camera firmware.
If you worry this much about Tue camera you can download a stock rooted MJA ROM and go into system/apps with a root explorer and extract the camera apk. Then go to where the camera apk is extracted to and move it to your internal memory under system apps. Then set permissions and reboot.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
The camera supposedly had some improvements, that's why I'm trying to find out. I'd ask in Sac's thread, but I don't have enough posts yet. And, I used SuperSU's uninstall to unroot the phone before trying the MJA OTA... although I did put stock recovery first, IIRC. Perhaps the root uninstall needed custom recovery to work? Anyways.
Under cce8d8a155a0602c83356e00311a1695e9a9383f.USER_L720_SPT_MF9_CSB_user_RP_to_MJA_CSB_user_RP_Update_FWD.zip\patch\system\cameradata\ there are a few items:
secimaging\PIP\rear_polaroid.png.p
RS_M10MO_OS.bin.p
RS_M10MO_SL.bin.p
RS_M10MO_SS.bin.p
I'll have to find someone who is knowledgeable about this and pick their brain if they'll let me.
I rooted my SGS4 when I got it, and has TWRP 2.5.0.0. I've been steadily bothered for the MF9 update for several months.
I followed several forums and flashed a couple of zips per some recommendations and at some point the update notification went away and then came back.
Frustrated, I put this on hold for a bunch of months, as I needed my phone for work and couldn't risk bricking it.
All I need is some help recommending procedures flashing all the most recent updates as I've had some LOS issues and its making it an annoyance even to use navigation.
I'm making a complete TWRP backup of all partitions and I just need to know where to go from here
If you want to skip all the hassles just odin directly to the latest MJA firmware. You can download the full MJA tar file from sammobile.com and install it through odin. You may or may not have to factory reset to do this. I did not have to. Once on MJA, you can not odin older firmwares so make sure you want to upgrade. Personally, I have found MJA to be the best and smoothest build yet, but others have had problems. Another thing to consider is with the MJA build, Samsung instituted a Knox warranty flag in the bootloader so if you root MJA it will trip the warranty flag. This may prevent you from getting warranty service from Samsung, if you have Assurian, TEP or other phone insurance programs this won't be a problem. Before you root MJA, you will want to OTA the newest software which is MK2. There currently is not a tar file available since it was just released. After you are all updated, cf-autoroot does work. Again, if you root the newest software, it will trip the knox warranty flag.
cruise350 said:
If you want to skip all the hassles just odin directly to the latest MJA firmware. You can download the full MJA tar file from sammobile.com and install it through odin. You may or may not have to factory reset to do this. I did not have to. Once on MJA, you can not odin older firmwares so make sure you want to upgrade. Personally, I have found MJA to be the best and smoothest build yet, but others have had problems. Another thing to consider is with the MJA build, Samsung instituted a Knox warranty flag in the bootloader so if you root MJA it will trip the warranty flag. This may prevent you from getting warranty service from Samsung, if you have Assurian, TEP or other phone insurance programs this won't be a problem. Before you root MJA, you will want to OTA the newest software which is MK2. There currently is not a tar file available since it was just released. After you are all updated, cf-autoroot does work. Again, if you root the newest software, it will trip the knox warranty flag.
Click to expand...
Click to collapse
I do like to have root for a variety of reasons, but the most glaring is just doing simple backups and restores with TB.
I'm not too worried about warranty - if I did get one, I would probably do Asurion anyway.
So if I got this right:
Odin flash MJA build
OTA MK2 software
CF-Autoroot (which I'm assuming works fine with an L720)
Back in business
Sound ok? (thank you for answering btw)
That looks correct. I would avoid doing restores using TWRP with MJA. A lot of people have reported problems. Philz' s recovery has just been updated and may be the best recovery for now. If you use twrp, use the latest version which is 2.6.3.0 I believe. Titanium Backup was updated and now works great with MJA.
cruise350 said:
That looks correct. I would avoid doing restores using TWRP with MJA. A lot of people have reported problems. Philz' s recovery has just been updated and may be the best recovery for now. If you use twrp, use the latest version which is 2.6.3.0 I believe. Titanium Backup was updated and now works great with MJA.
Click to expand...
Click to collapse
downloading SPR-L720VPUEMJA-20131030154609.zip
Sorry one more thing - should I update my TWRP Recovery or to Philz before Odin-flashing new FW or does it not matter?
RucanorX said:
downloading SPR-L720VPUEMJA-20131030154609.zip
Sorry one more thing - should I update my TWRP Recovery or to Philz before Odin-flashing new FW or does it not matter?
Click to expand...
Click to collapse
Install recovery after installing mja tar and upgrading to mk2, then root.
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!