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.
Related
Hey guys, I was wondering if someone would be willing to help me out. it has been a LONG while since I have owned an android device. as a matter of fact I never truly owned one and my only experience was flashing the TP2 to android and playing with it. I spent the past two years with a WP7 and I loved it but Sprint is taking there sweet ol' time releasing POS low end WP8 so it was time to switch.
I was hoping someone could guide me or point me in the right direction of how to accomplish this. I currently have the galaxy4 and I do like it a lot. I am on stock rom MDL that is rooted with the hot spot mod. my phone got the OTA for the MF9. I looked into being able to root the MF9 and it looks like it is no problem. so I tried to push through the MF9 update but it failed and I believe this is because I am rooted and also modded some system files when I did the hotspot mod. what would be the procedure to update to MF9 from MDL and re-root the device and but the hot spot mod back. if anyone has any guidance it would be most appreciated. Thanks!!
Steveo:laugh:
Questions go in Q&A
Development is for developers to post work
Thread moved
Be Careful I updated to MF9 from MDL and now my phone is no longer rooted and I can't get wifi access
Here is my post:
http://forum.xda-developers.com/showthread.php?t=2372749
steveoski111 said:
Hey guys, I was wondering if someone would be willing to help me out. it has been a LONG while since I have owned an android device. as a matter of fact I never truly owned one and my only experience was flashing the TP2 to android and playing with it. I spent the past two years with a WP7 and I loved it but Sprint is taking there sweet ol' time releasing POS low end WP8 so it was time to switch.
I was hoping someone could guide me or point me in the right direction of how to accomplish this. I currently have the galaxy4 and I do like it a lot. I am on stock rom MDL that is rooted with the hot spot mod. my phone got the OTA for the MF9. I looked into being able to root the MF9 and it looks like it is no problem. so I tried to push through the MF9 update but it failed and I believe this is because I am rooted and also modded some system files when I did the hotspot mod. what would be the procedure to update to MF9 from MDL and re-root the device and but the hot spot mod back. if anyone has any guidance it would be most appreciated. Thanks!!
Steveo:laugh:
Click to expand...
Click to collapse
I was also on MDL stock rom and rooted. I recommend to never take OTA updates if you are rooted. I got MD9 by using info from the post by 'Mudavo': http://forum.xda-developers.com/showthread.php?t=2277480
I used the first one listed of the Index of Guides: "-How to Install Stock MF9 ROM and Firmware". For the 'Choose a Rooted Stock MF9 ROM' I choose the 'odexed no data wipe' zip from 'Crawrj" (FYI at 1.4GB, it's a large file). With 'noobnl' thread, I had to do the ini edit but it's was easy. Don't forget to redo the ini edit when you are done and change it back to what it was before.
Follow it exactly, any problems you can ask 'Mudavo' or 'crawrj' in their post. I have seen others having to repeat the process to make it work so if it doesn't flash the first time, try it again. Hope this helps.
Stock MF9 ROM and Firmware Installation Guide
In TWRP or CWM BACK UP!
Download noobnl's tar from here for MF9 firmware and modem:
http://forum.xda-developers.com/show...php?p=43418277
Choose a Rooted Stock MF9 ROM of choice and Stock MF9 Kernel from here: http://forum.xda-developers.com/show...php?p=43426426
In noobnl's thread, read and apply the instructions on editing the .ini file for the boot loader update in Odin.
Odin flash the MF9 Firmware .tar. Put the .tar in the same folder on your computer that the Odin execution app is. Right click Odin.exe and click run as administrator. Check update phone boot loader. Flash the .tar using PDA mode. Auto reboot checked.
In TWRP or CWM Do a FULL wipe. (system, data, cache, dalvik) Install Stock MF9 ROM and MF9 Kernel.
Profit. You should now be full MF9. You do not need to go any further."
So does that mean that I will wipe all data on my phone, or should I back everything up with root backup? I already did a nandroid, too.
Hello,
This is will be my first XDA post ever since I always fix the most "brickiest" problems with all the Android based devices I have ever owned but not this time.
My Galaxy S4 has been updated to the latest MJA OTA (with successful CF root) and I have attempted to re-mod the hotspot service but this caused the annoying knox message to show. When attempting to restore the JAR and ODEX files, I think I have either overwritten the files in the incorrect order (ODEX -> JAR) and the phone rebooted as FX was trying to do that. So services.odex got corrupted and it was time for my to ODIN flash the MDC full stock rom as that USED to be my solution until Samsung's brand new knox protected bootloader. ODIN is not an option for me now, since the bootloader will prevent me flashing things like the pit, aboot and probably most of the other files inside the tarball. I can flash custom recovery and the MDC kernel successfully and that's about it. With custom recovery I have flashed rooted MF8 for the base operating system, and they applied the rooted MJA rom on top. The phone shows the S4 branding but then it reboots; It cannot boot into the operating system. I do not know the condition of the flash counter atm since I cannot check that in TriangleAway but it will stay "Official" under download mode, I think. I also do not know the versions of the firmware installed either in case something from MDC tar had an succession in replace some of the partitions. I am pretty sure the kernel however is still at MDC while I managed to install the system image of the MJA stock rom.
So my question is, what can I do bring back the working MJA stock rom image (/system and kernel) using TWRP recovery? Else I will have to go to Sprint and saying that the update from OTA has bricked my phone and that I have no idea how phones work.
Thank you.
45553543 450
Sorry, I forgot to add that I know that once you have MJA flashed, you cannot downgrade back unless of course someone figured out how to disable all the bootloader security but I really do not see that happening.
Fixed my own problem. Downloaded the official MJA stock tar.md5 rom from sammobile and flashed it, and managed to restore all my data using Titanium backup. This thread can be now closed.
So basically I went back to stock by "TAR files to flash MF3 via ODIN" and now I am on 4.2.2 stock. I don't really need root and just want to go 4.3
What I want to do is go 4.3 but it won't let me, it says I am up to date even though I am on 4.2.2.
It also won't let me update via kies...how do I fix this?
btort1 said:
Ok so I have a rooted 4.2.2 mf3 S4 and I want to factory reset it because it's pretty laggy if I compare it to my gf's s4 which is also rooted.
I didn’t do the odin root, I used this method to root my s4
http://www.youtube.com/watch?v=A_lu4ibJQtg
Is there any easy way to factory reset without losing the root?
I got a few more questions
Is there a way I can go to 4.3 root from 4.2.2? What would happen if I update to stock 4.3 or 4.4 (when it officially comes out) using the AT&T software update, will it brick my phone or will I be ok?
Click to expand...
Click to collapse
ODIN root method is for the I337m only anyways, so it wouldn't have worked. If you do a factory reset in the stock recovery, it doesn't touch the system files at all so you should still keep root. I'd make SuperSU a system app first though. You can get the 4.3 OTA through the software update menu and as long as you activate survival mode in SuperSU and you haven't made any changes whatsoever to the system files (besides root), it will run just fine.
Nvm got it! thanks
Bump! updated OP
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 have a Galaxy S4 AT&T i377 UCSGOK3 5.01. I have been fiddling with it and broke the recovery mode. When I select "reboot system now" it reboots, BUT has numerous "Unfortunately...has stopped" errors, finally resulting in unresponsive blank screen. I then have to factory reset and rebuild again. I CAN use recovery mode, IF I remove the battery instead of "reboot system now".
Here are the chain of events leading up this this:
- successfully rooted with Kingroot and replaced with Super SU
- attempted to install TWRP with "Official TWRP App" (I know, should not have done that)
- before attempting TWRP install, made backup of recovery.img (original one) with Official TWRP App
- tried to reinstall original recovery.img with Official TWRP App, Odin, and Flashify. Not working, does not boot into recovery mode.
- installed extracted NB1 recovery.img. From "AT&T Galaxy S4 SGH-I337 UCUFNB1 (Android 4.4.2)" with Odin. This one works, but has the reboot error problem.
Questions:
Is there a Stock AT&T OK3 firmware I can get a recovery.img from or will it still be a NB1 recovery?
Would it be helpful to do a complete re-install of stock firmware? Which one?
Can I install Safestrap on OK3?
Is there a fix for the numerous "Unfortunately...has stopped errors" after recovery reboot?
Thanks in advance,
Todd K.
The bootloader on the phone is locked and cannot run any version of TWRP or any custom ROM that is not based off a stock Samsung ROM.
The reboot problem may be due to a mismatch between the bootloader and recovery.
There is no stock OK3 ROM because AT&T never released a Odin-flashable version of the ROM. OK3 was only offered as an OTA update.
I suggest going back to stock OK3. This thread may help: https://forum.xda-developers.com/showthread.php?t=2616221
The S4 is a great phone and I still have one as my backup phone.
audit13 said:
I suggest going back to stock OK3. This thread may help:
Click to expand...
Click to collapse
Thanks Audit13. just to clarify, Do you suggest sticking with stock OK3 instead of safestrapping to some compatible custom ROM?
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
audit13 said:
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
Click to expand...
Click to collapse
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
I have never owned the sgh-i337 as I'm in Canada and the sgh-i337m (unlocked bootloader, works with TWRP) is the version carried by Canadian carriers.
When dealing with bloatware, I either manually freeze or remove it with Titanium Backup.
toddk63 said:
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
Click to expand...
Click to collapse
I use the mybackup app (formerly called my backup root) to debloat/freeze bloat. It's sort of like titanium backup. You can use flash fire on the play store to do a system backup without safe strap, just using safe strap is better and probably faster.