Related
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Install safestrap. Create a new Rom Slot 1 don't wipe stock ever!! Once Rom Slot 1 is created with atleast 2GB worth of space it will be activated then flash Hyper drive and the ME7 module then you should be golden
Sent from my SCH-I545 using Tapatalk now Free
Maybe I don't fully understand what the 2GB worth of space is used for... does this mean that for the Hyperdrive slot I will only have 1/8 of the phones 16GB for the rom, apps and other stuff or is that just for the rom and apps/etc will still have the rest of the memory to use?
theshadles said:
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Click to expand...
Click to collapse
While I will say you can easily brick your device doing this, I had ODIN ready in case I needed it, and I went ahead and did just this. I installed SafeStrap, wiped cache/dalvik/system, and went ahead and flashed Hyperdrive and the modules fix into the stock ROM slot.
While it is not advisable to do this, my phone has been operating FLAWLESSLY ever since I did this. I have not had a single issue and everything works perfect paired with the stock kernel. I am enjoying Hyperdrive while still having all of my storage. I have had to Odin before so I was prepared to just in case flashing went wrong.
Again, most people will advice against this, but .... it does work.
The possible brick sounds spooky to me but how is the space per slot allocated? Does 2GB mean as far as that slot is concerned the phone only has 2GB internal space to use for the rom and all other data (apps and stuff). Or is it just 2GB for rom only and the other data can fill the rest of the space. (Is it like partitioning a drive for a dual boot on a computer only you can't access the data on the other partitions?)
roboots21 said:
While I will say you can easily brick your device doing this, I had ODIN ready in case I needed it, and I went ahead and did just this. I installed SafeStrap, wiped cache/dalvik/system, and went ahead and flashed Hyperdrive and the modules fix into the stock ROM slot.
While it is not advisable to do this, my phone has been operating FLAWLESSLY ever since I did this. I have not had a single issue and everything works perfect paired with the stock kernel. I am enjoying Hyperdrive while still having all of my storage. I have had to Odin before so I was prepared to just in case flashing went wrong.
Again, most people will advice against this, but .... it does work.
Click to expand...
Click to collapse
I just did this on my Verizon Note 3 SM900V Android version 4.3 with Kernel 3.4.0 and Baseband version N900VVRUBMJE with Hardware version N900V.07 but please excuse the ignorance. What modules fix? Where do I find this modules fix? Is there a special version that I will need for my specs? It seems to be working fine without it so is this a must have? Thank you!
theshadles said:
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Click to expand...
Click to collapse
It is possible to flash over the stock ROM using Safestrap. It's then no longer safe, so if that ROM fails to boot, you must use Odin to restore a factory ROM to recover. That's the concern: if anything goes wrong, then you're going to be in emergency recovery mode.
Also note that flashing over the stock ROM isn't supported.
---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------
whitelion411 said:
I just did this on my Verizon Note 3 SM900V Android version 4.3 with Kernel 3.4.0 and Baseband version N900VVRUBMJE with Hardware version N900V.07 but please excuse the ignorance. What modules fix? Where do I find this modules fix? Is there a special version that I will need for my specs? It seems to be working fine without it so is this a must have? Thank you!
Click to expand...
Click to collapse
If you flash over the stock ROM, then the kernel modules are still there. Without those modules, things like WiFi won't work.
k1mu said:
It is possible to flash over the stock ROM using Safestrap. It's then no longer safe, so if that ROM fails to boot, you must use Odin to restore a factory ROM to recover. That's the concern: if anything goes wrong, then you're going to be in emergency recovery mode.
Also note that flashing over the stock ROM isn't supported.
---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------
If you flash over the stock ROM, then the kernel modules are still there. Without those modules, things like WiFi won't work.
Click to expand...
Click to collapse
Oh ok so there really isn't anything extra I have to do then right? The member above stated that he flashed his rom over the stock rom and installed the modules fix so that had me thinking I had another step to go. So far all is working great and if something does go wrong I do have Odin and I even backed up the stock rom to be safe.
whitelion411 said:
Oh ok so there really isn't anything extra I have to do then right? The member above stated that he flashed his rom over the stock rom and installed the modules fix so that had me thinking I had another step to go. So far all is working great and if something does go wrong I do have Odin and I even backed up the stock rom to be safe.
Click to expand...
Click to collapse
You should be good. And yea if something goes wrong while on that stock slot usually Odin is the only way to.
Sent from my SCH-I545 using Tapatalk
theshadles said:
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Click to expand...
Click to collapse
It's probably not the safest thing to do. What I would recommend, if you feel like you must try it (and I recommend that you not), is install safestrap. Install hyperdrive in the first free slot. Verify that it works. Then, if you really want to, install hyperdrive on the stock rom slot. Verify that it works. Then, if you really must, you can erase the other slot.
GeneralBelisarius said:
It's probably not the safest thing to do. What I would recommend, if you feel like you must try it (and I recommend that you not), is install safestrap. Install hyperdrive in the first free slot. Verify that it works. Then, if you really want to, install hyperdrive on the stock rom slot. Verify that it works. Then, if you really must, you can erase the other slot.
Click to expand...
Click to collapse
Okay, but what do you do if you can't create a rom slot? That's the problem I have so I may be forced to install over the stock rom if I want to use a custom rom.
fdrennon said:
Okay, but what do you do if you can't create a rom slot? That's the problem I have so I may be forced to install over the stock rom if I want to use a custom rom.
Click to expand...
Click to collapse
This thread is from awhile ago, if you're on 4.4 you can't use rom slots on Verizon with safestrap 3.72, you just have to take the risk and use odin or a backup to get your phone working again
I had previously had TWRP and Hyperdrive RLS installed because at the time there was no stable version of CM for the S4. After finally getting tired of Hyperdrive I returned my phone to stock and redid the whole process as written in the CWM wiki step by step though admittedly the only thing I did differently was put the ROM onto my SD card through Windows explorer and not ADB though I really cannot fathom how that would change anything.
Now whenever I try to flash a kernel, I get Secure Fail: Kernel and have to go into recovery and re-install the CM .zip and delete cache+dalvik to get back into Android. I don't understand why I seem to be the only one having trouble. Specifically I am trying to install the latest Ktoonsez AOSP kernel onto CM 11 1/13 nightly.
Do I have to do anything different to CM or in the kernel install process to get it to work?
Markstache said:
I had previously had TWRP and Hyperdrive RLS installed because at the time there was no stable version of CM for the S4. After finally getting tired of Hyperdrive I returned my phone to stock and redid the whole process as written in the CWM wiki step by step though admittedly the only thing I did differently was put the ROM onto my SD card through Windows explorer and not ADB though I really cannot fathom how that would change anything.
Now whenever I try to flash a kernel, I get Secure Fail: Kernel and have to go into recovery and re-install the CM .zip and delete cache+dalvik to get back into Android. I don't understand why I seem to be the only one having trouble. Specifically I am trying to install the latest Ktoonsez AOSP kernel onto CM 11 1/13 nightly.
Do I have to do anything different to CM or in the kernel install process to get it to work?
Click to expand...
Click to collapse
I don't have an mdk build so I cant speak from experience but...
We're you able to successfully flash kernels on twrp? Did you try clearing cache/dalvik before flashing the kernel on cwm?
gnubian said:
I don't have an mdk build so I cant speak from experience but...
We're you able to successfully flash kernels on twrp? Did you try clearing cache/dalvik before flashing the kernel on cwm?
Click to expand...
Click to collapse
I was able to flash kernels in TWRP with no issues, and flashed the kernel the same way I have been for years, which is clearing cache and dalvik after the kernel.
Markstache said:
I was able to flash kernels in TWRP with no issues, and flashed the kernel the same way I have been for years, which is clearing cache and dalvik after the kernel.
Click to expand...
Click to collapse
Maybe your phone just hates cwm.
Have you tried using Odin to flash a stock image? Make absolutely sure you flash the correct firmware; otherwise you're looking at a brick. It should restore the stock recovery, stock Rom, and remove the custom padlock. You'll lose root; but it'll accomplish what you want.
kfres39389 said:
Have you tried using Odin to flash a stock image? Make absolutely sure you flash the correct firmware; otherwise you're looking at a brick. It should restore the stock recovery, stock Rom, and remove the custom padlock. You'll lose root; but it'll accomplish what you want.
Click to expand...
Click to collapse
That's what I had done to go back from RSL and TWRP to CM and CWM; I wiped and returned to stock image, put on unlocked MDK kernel via Odin, rooted via Motochopper, put back original kernel to get rid of the Samsung Custom boot screen and return to Samsung Galaxy S4 boot screen, loki'd in CWM recovery, and then installed CM 11. As far as I know those are the exact same steps everyone else follows, and then everyone else seems to be able to install other kernels, but for whatever reason it trips the Verizon security every time. From what I understand, that should only happen if you have a locked bootloader, which I shouldn't since I have CWM recovery and root and everything, or if the kernel isn't Loki'd, which Ktoonsez always are. Which is why I am stumped.
I'd say go back to stock, update your modem, then flash RLS12
awskier08 said:
I'd say go back to stock, update your modem, then flash RLS12
Click to expand...
Click to collapse
Modems are updated. Also I don't like RLS.
Loki doesn't unlock the bootloader; it is simply a workaround. As of yet, there is no way to unlock the bootloader because security measures are built into the hardware. Verizon security can be bypassed simply by holding the button combination to put it into Odin mode, canceling, and restarting.
kfres39389 said:
Loki doesn't unlock the bootloader; it is simply a workaround. As of yet, there is no way to unlock the bootloader because security measures are built into the hardware. Verizon security can be bypassed simply by holding the button combination to put it into Odin mode, canceling, and restarting.
Click to expand...
Click to collapse
I had heard that and tried it and it didn't work I don't think, but I'll try clearing things before and after and then doing that. If the Kernel is loki'd shouldn't I not have to do that though?
Try Lokiing through ADB.
I wiped cache + dalvik, installed kernel, wiped cache + dalvik again, rebooted, and no matter what I do i get verizon security. Going into Odin and hitting volume down to cancel and reboot does not bypass it. Going into Odin mode completely and holding volume up + power to reboot it does not bypass verizon security.
kfres39389 said:
Try Lokiing through ADB.
Click to expand...
Click to collapse
What do you mean, specifically?
You have to use a command prompt to push files via the Loki method. Basically bypass the stock bootloader to manually flash custom roms, kernels, recoveries, etc. There are both XDA tutorials with scripts, as well as YouTube tutorials.
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
Also, volume down is download mode. You press volume up after it warns you that installing custom files can damage your system. Basically that warning telling you to take it to Verizon is their way of telling you "Oh-oh. Look what you did."
kfres39389 said:
You have to use a command prompt to push files via the Loki method. Basically bypass the stock bootloader to manually flash custom roms, kernels, recoveries, etc. There are both XDA tutorials with scripts, as well as YouTube tutorials.
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
Also, volume down is download mode. You press volume up after it warns you that installing custom files can damage your system. Basically that warning telling you to take it to Verizon is their way of telling you "Oh-oh. Look what you did."
Click to expand...
Click to collapse
I don't have a problem installing them, though. I have a problem with my phone complaining about it afterward.
Markstache said:
I don't have a problem installing them, though. I have a problem with my phone complaining about it afterward.
Click to expand...
Click to collapse
From what I can gather from this thread people are telling you to flash kernels etc via command prompt using the loki method. You seem to be flashing them in recovery instead.
gnubian said:
From what I can gather from this thread people are telling you to flash kernels etc via command prompt using the loki method. You seem to be flashing them in recovery instead.
Click to expand...
Click to collapse
I have been flashing my kernels by recovery from day one...something's really amiss here...
jamesd1085 said:
I have been flashing my kernels by recovery from day one...something's really amiss here...
Click to expand...
Click to collapse
There's always odin.
Markstache said:
I don't have a problem installing them, though. I have a problem with my phone complaining about it afterward.
Click to expand...
Click to collapse
Try using Rom Toolbox to delete every app that contains KNOX. There are several. It stopped giving me that error once I did that. It wasn't a problem after the initial "I'm gonna have a heart attack because I bricked my phone." thought. Like I said, simply put it into download mode, cancel it, and restart. Very easy fix. If you can't straight up uninstall all the KNOX programs, freeze them. Also freeze the security updater. Samsung went way overboard with the S4 to ensure that people don't mess with their devices. At least they seemed to learn from the S3 bricking that they shouldn't destroy the phones when they're trying to prevent modification.
kfres39389 said:
Try using Rom Toolbox to delete every app that contains KNOX. There are several. It stopped giving me that error once I did that. It wasn't a problem after the initial "I'm gonna have a heart attack because I bricked my phone." thought. Like I said, simply put it into download mode, cancel it, and restart. Very easy fix. If you can't straight up uninstall all the KNOX programs, freeze them. Also freeze the security updater. Samsung went way overboard with the S4 to ensure that people don't mess with their devices. At least they seemed to learn from the S3 bricking that they shouldn't destroy the phones when they're trying to prevent modification.
Click to expand...
Click to collapse
Cancelling download mode doesn't ever let me get past the Verizon security screen, and all Knox related things are gone already.
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
DeadlySin9 said:
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
Click to expand...
Click to collapse
Thank you for the information.
remainnameless said:
Thank you for the information.
Click to expand...
Click to collapse
Just make sure you have the Odin tar file for your phone just in case something goes wrong. Me and a few others ran into some issues messing with the stock slot. Good idea to have that anyways.
Sent from my SCH-I545 using Tapatalk
Just in case someone comes across this in the future:
Everything worked as planned. No issues to report.
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Click to expand...
Click to collapse
And yet people are wiping and flashing to stock fine?
Cool, I will try that
Sent from my SCH-I545 using XDA Premium HD app
DaGamer12345 said:
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
And yet people are wiping and flashing to stock fine?
Click to expand...
Click to collapse
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
reason why its called safestrap...and has saved me many times able to get back to my stock rom slot...but we all have our own levels of risk but hashcode made safestrap the way he did for a reason.
I run 3 roms on my S4 and have no issues with memory limitations
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
DaGamer12345 said:
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
Click to expand...
Click to collapse
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
k1mu said:
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
Click to expand...
Click to collapse
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
DaGamer12345 said:
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
Click to expand...
Click to collapse
Whew. I thought "Oh I remember you" was going to be followed by ".. you're that jerk that... " :laugh:
Have a good weekend.
remainnameless said:
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
Click to expand...
Click to collapse
I just installed hyperdrive to the stock slot and everything works perfect.
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
riker147 said:
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
Click to expand...
Click to collapse
Thank you for your response. Actually what I failed to mention is I did have 3.71 installed first, and I had the exact same problem. So it's not an issue with the safestrap version. And I have tried about 12 different ROMs. Including BajaROM-S4-Release-v-2.2 and BoneStock4.3_S4v2.1. As I said, I'm not a newbie at all, and I'm not about to hunt and peck for information again (which is what I've been doing for two days now). I wouldn't have asked for help if I had been successful in my search.
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
decaturbob said:
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Again, thanks for your help. I'm going to start with Odin. Wipe it all clean and start over. That's always the best option. Thanks!
basically, I'd follow this:
http://forum.xda-developers.com/showthread.php?t=2763834
I'd go back to MK2, root, BB, SS 3.71. Then go up to NC5 ROMs with SS 3.72. Wiping EVERYTHING along the way, system included, not just factory reset
Similar Issue
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
same problem
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
im having the same problem i am also frustrated i don't know what to do
Similar Issue
I know there must be a way... If only I can get it to mount the "system" and "systemorig"...
I'm going to play around with the Slots and the datas Size's and see what I come up with.
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
jmgib said:
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Oh ok. The Stock NC5 image... Great.
Where can I find the stock image?
If possible, could you please send a link?
Thanks in advance
damien302 said:
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
Click to expand...
Click to collapse
shonnick01 said:
im having the same problem i am also frustrated i don't know what to do
Click to expand...
Click to collapse
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
liljoe727 said:
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
Click to expand...
Click to collapse
Thanks a lot man. The is has been resolved...
I had to Odin the stock NC5 (exactly what you've just mentioned in your response.) I had to flash it twice actually. The first time only took about 3 mins. I then tried to restore my backup, but during the time it restari SS (when the flash was approximately 90% done) I then went to restart the system and then received the notice "No OS loaded). So I wiped all except my SD card and then I just thought to myself to just try and Odin the stock NC5 one more time (it was getting late and I was about to give up). On the 2nd attempi it took almost 3 times the length as before (15-20mins) when it finished, it bypass the " unlock Samsung screen " and displayed the stock splash screen and audio then the Verizon screen. ( I was happier the a crackhead at a free crack-give-away)...
So I want to thank you for responding, I was determined not to give up,, and it was really close before I was about throw in the towel... Thanks a bunch. (You're response was exactly what I did last night)... I was about to update my issue as soon as I fixed it las night was it was so late and I was really sleepy, then I wake up to your message with the exact fix.
Thanks a lot ☺☺
I've read a couple peoples post on how they are able to successfully flash a custom ROM on the stock slot. However, nothing is mentioned if SS gets wiped or anything like that. If this has been answered, kindly direct me to the post?
VagueDeity said:
I've read a couple peoples post on how they are able to successfully flash a custom ROM on the stock slot. However, nothing is mentioned if SS gets wiped or anything like that. If this has been answered, kindly direct me to the post?
Click to expand...
Click to collapse
No it does not. Just take a backup of the stock slot just to be on the safe side
I have flashed custom ROMs to stock with no issue. Restoring a backup of a custom ROM from slot 1 to stock soft bricked my device and I has to use Matt's tool to get it back running.
Sent from my XT912 using Tapatalk
If you are using latest Safestrap (3.73), it will inject itself into /system/etc on the stock slot every time you overwrite stock. Do NOT allow the phone to reboot until/unless you see the message "updating partition details" succeed, otherwise you will need Matt's Utility (see below).
-Brian
Sent from my continually born again RAZR MAXX!
---------- Post added at 03:24 PM ---------- Previous post was at 03:15 PM ----------
Oops, wrong sig!
- Brian
"It's not exactly rocket science! ...Well, actually it is." - Jimmy Neutron
All-In-One XT912 Utility to:
Reflash Stock ROM/Root Stock ROM/Install SafeStrap
UPDATED!
I have to reply on this.
Some months ago i tried to install ParanoidAndroid into stock slot. So i wiped system. While doing so, Safestrap 3.65 has wiped itself with the system and i needed RSD to restore JB! I had to dirty flash my custom ROM without wiping system!!!!
Be warned, i dont know if 3.73 has fixed this, so it may happen.
I've flashed a number of AOSP-based ROMs on stock slot with success. (Gummy, Paranoid Android, CM, NX5, SlimKat) Using SS 3.73
I do believe most ROMs have a script that wipes system without having to do it manually. I know Gummy ROMs wipe system while flashing. I am on Gummy now & SS is still there.
Anyway, thanks for the answers. :]