Database Users

[Q] Deleted Stock Recovery?

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!

Can anyone help me figure out why NONE of my safestrap flashes work??

Hi folks. I don't know what I'm doing wrong here. I know I am bound to safestrap at this point but NONE of the safestrap ROMs work for me. I don know what the deal is. I've done probably 5-10 other phones with CWM or TWRP and I never really have too much trouble. I cannot for the life of me get any ROMs to work other than flashing the tar build of the Sammy Stock ROM via Odin. That's the only thing that I can get working. If anyone would help me troubleshoot I would be really grateful. Here is what I have been doing:
1. First ROM was stock Sammy 4.4.4 (i think). whatever the latest that there was for Sammy stock OTA update.
2. Went through days of nonsense after a VZ to ATT phone flash on accident.
3. I now I have Safestrap working when I want it to.
4. Basically my process starts with flashing stock Sammy Rootable 4.4 with Odin
5. Next I root with towl and install safestrap.
6. Then I download and copy ROMs to the SD card.
I do notice that when I install Safestrap, click Install Recovery, it confirms but the second part of the app says "not active". Is that right?

fuzzyreets said:
Hi folks. I don't know what I'm doing wrong here. I know I am bound to safestrap at this point but NONE of the safestrap ROMs work for me. I don know what the deal is. I've done probably 5-10 other phones with CWM or TWRP and I never really have too much trouble. I cannot for the life of me get any ROMs to work other than flashing the tar build of the Sammy Stock ROM via Odin. That's the only thing that I can get working. If anyone would help me troubleshoot I would be really grateful. Here is what I have been doing:
1. First ROM was stock Sammy 4.4.4 (i think). whatever the latest that there was for Sammy stock OTA update.
2. Went through days of nonsense after a VZ to ATT phone flash on accident.
3. I now I have Safestrap working when I want it to.
4. Basically my process starts with flashing stock Sammy Rootable 4.4 with Odin
5. Next I root with towl and install safestrap.
6. Then I download and copy ROMs to the SD card.
I do notice that when I install Safestrap, click Install Recovery, it confirms but the second part of the app says "not active". Is that right?
Click to expand...
Click to collapse
For every ROM i have flashed through Safestrap, I have always had to flash it to the 'stock' slot. Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel) root it, then install safestrap, then reboot into safestrap, wipe everything except sd, and flash the Safestrap compatible TW-based ROM you want from the zip on your extsd into the stock-slot. Then, while still in Safestrap, flash Venom's KitKat magic AT&T modules. At least, that's how I have done it. Follow the Install Instructions section of the [Index] thread: http://forum.xda-developers.com/showthread.php?t=2616221
Once you root and get Safestrap installed, you should only use Odin in case you screw up and softbrick and need to get back to your base stock ROM to start the process over again.
Good luck.

manstable said:
For every ROM i have flashed through Safestrap, I have always had to flash it to the 'stock' slot. Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel) root it, then install safestrap, then reboot into safestrap, wipe everything except sd, and flash the Safestrap compatible TW-based ROM you want from the zip on your extsd into the stock-slot. Then, while still in Safestrap, flash Venom's KitKat magic AT&T modules. At least, that's how I have done it. Follow the Install Instructions section of the [Index] thread: http://forum.xda-developers.com/showthread.php?t=2616221
Once you root and get Safestrap installed, you should only use Odin in case you screw up and softbrick and need to get back to your base stock ROM to start the process over again.
Good luck.
Click to expand...
Click to collapse
Couple questions about what you wrote....
"Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel)"
This is something I have been trying to understand. What is MK2 vs what is NB1? I don't understand these pieces of this rooting puzzle. In my mind currently I have the Boot puzzle piece which is safestrap at this point and the ROM which is WHATEVER. No?
"flash the Safestrap compatible TW-based ROM"
Does it have to be a TW ROM? I'm doing this to try to get away from Touchwiz.
Thank you VERY much for your reply. I appreciate your time in explaining. Outside of flashing the ATT modules, I think I have been doing the other procedure the same.

fuzzyreets said:
Couple questions about what you wrote....
"Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel)"
This is something I have been trying to understand. What is MK2 vs what is NB1? I don't understand these pieces of this rooting puzzle. In my mind currently I have the Boot puzzle piece which is safestrap at this point and the ROM which is WHATEVER. No?
"flash the Safestrap compatible TW-based ROM"
Does it have to be a TW ROM? I'm doing this to try to get away from Touchwiz.
Thank you VERY much for your reply. I appreciate your time in explaining. Outside of flashing the ATT modules, I think I have been doing the other procedure the same.
Click to expand...
Click to collapse
MK2, MF3, NB1, NC1, etc., are all different versions (or builds) of the baseband software our ROMs run on. A kernel (as I understand it at least) is the underlying software that sits below the ROM and is intermediary software that connects the top-most software we interact with (the ROM) to actually control our phone's hardware -- the IR blaster, wifi chips, touch screen capacitive sensors, etc. When playing around with ROMs, you need to know what kernel you are on (i think it's unchangeable for phones with locked bootloaders like ours) -- but more importantly what BASEBAND you are on. The baseband (and possibly the kernel?) updates from taking OTA updates direct from AT&T/Samsung. You can only flash ROMs that are compatible with the baseband you have upgraded too -- which you can see on your "About Device" page in settings. For example, I am running Goldeneye v34 which is a XXUGNE8 build, on my AT&T SGH-i337 that is on a baseband of I337UCUNB1.
Edit: Unfortunately, you have to flash TW-based ROMs...due to our bootloaders being locked (and us being stuck on the stock-kernel). Safestrap is the only way we can flash ROMs with firmware that is MF3 or newer (several several builds ago) but only works with TW-based ROMs.
Please click THANKS if you found this helpful...trying to get posting privileges in dev forums that i've been lurking in for way too long.

manstable said:
MK2, MF3, NB1, NC1, etc., are all different versions (or builds) of the baseband software our ROMs run on. A kernel (as I understand it at least) is the underlying software that sits below the ROM and is intermediary software that connects the top-most software we interact with (the ROM) to actually control our phone's hardware -- the IR blaster, wifi chips, touch screen capacitive sensors, etc. When playing around with ROMs, you need to know what kernel you are on (i think it's unchangeable for phones with locked bootloaders like ours) -- but more importantly what BASEBAND you are on. The baseband (and possibly the kernel?) updates from taking OTA updates direct from AT&T/Samsung. You can only flash ROMs that are compatible with the baseband you have upgraded too -- which you can see on your "About Device" page in settings. For example, I am running Goldeneye v34 which is a XXUGNE8 build, on my AT&T SGH-i337 that is on a baseband of I337UCUNB1.
Edit: Unfortunately, you have to flash TW-based ROMs...due to our bootloaders being locked (and us being stuck on the stock-kernel). Safestrap is the only way we can flash ROMs with firmware that is MF3 or newer (several several builds ago) but only works with TW-based ROMs.
Please click THANKS if you found this helpful...trying to get posting privileges in dev forums that i've been lurking in for way too long.
Click to expand...
Click to collapse
This is invaluable information. I can't thank you enough. I would hit the THANKS button 100 times if I could for you. You totally saved me here and put the pieces together for me for the most part. I don't completely understand it but I have things working now. Thank you VERY much.

manstable said:
MK2, MF3, NB1, NC1, etc., are all different versions (or builds) of the baseband software our ROMs run on. A kernel (as I understand it at least) is the underlying software that sits below the ROM and is intermediary software that connects the top-most software we interact with (the ROM) to actually control our phone's hardware -- the IR blaster, wifi chips, touch screen capacitive sensors, etc. When playing around with ROMs, you need to know what kernel you are on (i think it's unchangeable for phones with locked bootloaders like ours) -- but more importantly what BASEBAND you are on. The baseband (and possibly the kernel?) updates from taking OTA updates direct from AT&T/Samsung. You can only flash ROMs that are compatible with the baseband you have upgraded too -- which you can see on your "About Device" page in settings. For example, I am running Goldeneye v34 which is a XXUGNE8 build, on my AT&T SGH-i337 that is on a baseband of I337UCUNB1.
Edit: Unfortunately, you have to flash TW-based ROMs...due to our bootloaders being locked (and us being stuck on the stock-kernel). Safestrap is the only way we can flash ROMs with firmware that is MF3 or newer (several several builds ago) but only works with TW-based ROMs.
Please click THANKS if you found this helpful...trying to get posting privileges in dev forums that i've been lurking in for way too long.
Click to expand...
Click to collapse
I saw the issue is resolved. Good work. Just to clarify, though... The baseband in the "about device" page is actually your modem. Most of time the modem will match the kernel and bootloader, but it's not always the case...
1. MK2 base users that use the magic tool to flash kitkat roms, end up flashing the mld modem in odin (part of the magic tool files). After they flash a rom, their baseband will show up as mld.
2. You can flash any modem in safestrap and you will see your baseband change... http://forum.xda-developers.com/showthread.php?t=2496517
Unless you are on 100% stock where you know the base matches the modem, the best way to verify your base can be found in post 4 here... http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4

[Q] Why can't I get a custom rom to boot?

Hi all,
Working with a AT&T NC1 safestrap phone. Having problems getting any custom rom to boot. Phone usually shows white on black Samsung logo for a few second then restarts, sometimes into stock recovery.
Detailed below is my method, and methods tried with same result. Perhaps someone can see the error of my ways.
I have been trying to start fresh.... so:
1) Odin I337UCUFNB1_TWRootable_Full_Odin.tar.md5
2) Do not boot, Download mode and flash 2400258.zip
3) Install tr, and SS 3.72
4) Reboot into recovery, install Hyperdrive 18.1 or Gravitron S4 3.2 for SS, then flash SuperUser then NC1 module.
No matter what, I cannot get a rom to boot. Just hangs at Samsung logo
Other methods tried:
1) Using I337_NB1toNC1_KeepRoot_OTA.zip and/or I337_NB1toNC1_KeepRoot_OTAwBL.zip to flash to NC1 before custom rom (after Odin NB1) (instead of 2400258.zip)
2) Using NB1 Odin Files from Magic Tool BL,AP,CP before flash of custom rom, tried also after flashing custom rom
3) flashing NB1 stock kernel
4) flashing NC1 stock kernel
Tried maybe 30 or 40 times, cannot get a custom Rom to boot. To be clear, stock boots just fine whenever i Odin back and upgrade to NC1.
Anyone out there insightful enough to lend a hand? More detailed instructions than on INDEX ALL THINGS POST? See my mistake? Losing my mind just a little bit, flashing the days away...
Any help greatly appreciated!

Are you trying to flash a custom ROM in the STOCK slot? Or a second slot?
I do NOT have safestrap but I know I have read you HAVE TO flash Roms in the STOCK Slot for it to work.

RockRatt said:
Are you trying to flash a custom ROM in the STOCK slot? Or a second slot?
I do NOT have safestrap but I know I have read you HAVE TO flash Roms in the STOCK Slot for it to work.
Click to expand...
Click to collapse
Always stock.

ajoh99 said:
Always stock.
Click to expand...
Click to collapse
Is your ROM SafeStrap Compatible?

Yes indeed. Tried a variety of them off the safe strap compatible page. I feel there is something I am missing but not sure what. I have been wiping data, davliche, cache, and system each time. Is this correct?

[Q] Stock Rom wont load

I am currently on nc4 baseband version and i wanted to go back to my stock rom using safestrap version 3.75 (TWRP v2.7.1.0) When i activate stock rom and reboot, the phone stays on the verizon red screen with out any indication of doing anything. I have to take out the battery and load up to baja rom 15 or alliance rom v1 to get into phone. When i run stock rom the safestrap says its not active (is that normal?)
any help would be appreciated, first time android user.

Stock ROM won't load
Ok, I had this problem when I downgraded the kernel from nc4 to nc2 to load Biggins and Jasmine.
I just looked on Alliance, and the instructions do not say anything about downgrading. I am running Biggins, Jasmine, and Alliance. I lost my stock slot because many instructions tell you to load their ROM into stock slot, which NEVER worked for me! I did lose my stock install though. Try flashing the nc4 kernel with Odin.
This may help:
http://forum.xda-developers.com/showthread.php?t=2794918
If you have not flashed the nc2, I am not sure what is wrong. Let me know what you find out. All my slots work fine except stock, DO NOT overwrite stock if you can help it.

Put custom rom in stock slot on Safestrap

I need some serious help guys. Here's the scenario:
When installing a custom rom to my phone using Safestrap I put it on the stock slot on accident. Here's all my phone information:
Verizon S4
Sch-1545
Android 4.3
I545VRUEMK2
Kernel 3.4.0
Running Hyperdrive RLS15 on Safestrap 3.71 (?)
How do I go about restoring Verizon's stock rom onto the stock slot and having Hyperdrive on a different slot without bricking my phone? I've tried to think of this a million ways and so far have come to few conclusions as to how to make this work. Any guidance would be much appreciated.

Start from scratch. Reinstall the stock ROM via Odin, then do what you need to in order to get SafeStrap back onto the phone, then put the custom ROM in the correct slot.