yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] ATGkompressor:
If I were u this is what I would do...

Download the .tar from http://xdaforums.com/showthread.php?t=2735172 and FOLLOW THE INSTRUCTIONS WORD FOR WORD!

Since ur stuck with no other option than to Odin, you're gonna lose root. But just temporarily. Sorry, but that's the game.

Ok. Once you've successfully completed that step, download Towelroot v3, make sure >Settings> Security>Unknown Sources is CHECKED! And install it, open and tap Make It Ra1n!

Next go to play store and download SuperSU, and follow the on screen prompts. Make sure you click "Normal" when it asks how u wanna install. DO NOT CLICK CWM/TWRP! U may have to close SuperSU if disabling Knox hangs on u. Just long press home and swipe it away from recents. Then open it back up. Should disable it right away or prompt u and then u would tap OK.

Then, go to Play Store and dl busybox free, grant su access, and tap install. Let it do its thing. Close out.

Then download FlashFire BETA by following the instructions here http://xdaforums.com/showthread.php?t=3096558, as well as the Stock_Deodex_OC1_w/NK4BL.zip from the same thread. Follow the instructions word for word in that thread as well. DON'T FORGET TO SET YOUR SCREEN TIMEOUT TO 10 MINUTES! OR U WILL ARRIVE AT THE SAME PLACE U ARE NOW!

Let it work is magic and BE PATIENT! YOU WILL HANG ON THE VERIZON RED SCREEN FOR APPROX. 10-15 MINUTES! THIS IS NORMAL!

Once it boots, your phone will guide u thru setup and you should be good to go. If I were you, I would stay on the stock deodex until u gain a little bit more knowledge about this rooting/flashing business. Echoe is a very good ROM, but some of the issues you may stumble upon require a skill-set you've yet to obtain. But you'll learn. We all did at one point. I encourage you to read thru the Echoe Dev and Q&A Thread several times, as well as gigilies "Safe OC1/NC5 Up/Down" thread.

Plus, I'm on muniz's stock deodex OC1 w/Xposed, and it is absolutely the fastest and most stable setup I have ever ran. Hope this helps. Good luck!
[Verizon Samsung Galaxy S 4] PantsFullOfGuns:
Followed it word for word, hit start on odin and just says failed, dammit im getting scared here. Also on download mode the screen says write protection enabled and eMMC BURST MODE enabled.

Edit: I am thinking now that because I am trying to flash a NC5 rom (the one that was on the thread) over my OC1 that this might be the problem could some one direct me to a file that would be ok to use thanks. Another note when I go into recovery (holding volume up home and power) I get a message saying Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
[Verizon Samsung Galaxy S 4] ATGkompressor:
Sounds like an OTA...what is your bootloader? If it's OC1, you're stuck with no root or downgrade. NK4...you're ok. Also, check your usb ports and cable. U also need to run Odin as an administrator, otherwise it won't work as desired. Check all these things I just mentioned and we'll go from there.
[Verizon Samsung Galaxy S 4] PantsFullOfGuns:
So i was OC1 but I did muniez method to get root with towelroot the first time, I for sure ran odin as admin, I am using the original supplied cable and I tried a few different ports, if I can have my choice I would actually prefer a downgrade, I really didn't like how many things that didn't work in lollipop such as viper4android and exposed was buggy.
[Verizon Samsung Galaxy S 4] ATGkompressor:
I'm confused...your bootloader is OC1? Because if so, there's no root for that bootloader. What is shown in Settings> About Phone>Baseband Version is completely different from what your bootloader is.
[Verizon Samsung Galaxy S 4] PantsFullOfGuns:
Well currently I cant even get to my phone but it was OC1, I for sure had root though it was OC1 since 4.4.3 then I upgraded from muniez's method to lollipop
[Verizon Samsung Galaxy S 4] ATGkompressor:
What version of Odin are using? 3.09 or 3.10 is what you'll need. Make sure the drivers are installed. If the above prerequisites are achieved, try uninstalling Odin and reinstalling. Make sure your device isn't encrypted. Make sure usb debugging is enabled in developer options. And if none of that works...try using a completely different computer. But, it almost sounds like usb debugging isn't activated.
[Verizon Samsung Galaxy S 4] PantsFullOfGuns:
Tried a different comp and I am happy to report, thanks to your help its working, I am actually prob going to stay on the NC5 build because I know all my must have apps work well on it bug free.. but is there any way to get the latest versions of kitkat on my phone?
[Verizon Samsung Galaxy S 4] ATGkompressor:
No, just 4.4.2. Hyperdrive RLS21 is an exceptional, stable, highly customizable ROM. It's based on NC5. Has a ton cool features.

When using safestrap, flash in the stock slot. ROM slots tend to present problems. Just make sure to make a backup.

Glad I could help!
[Verizon Samsung Galaxy S 4] delsoul6:
Odin seems to be finicky like that. I bricked my phone and spent hours trying to get Odin to work. All different downloads and ask different tars failed. I tried on a different computer and it worked the first time. Go figure.
[Verizon Samsung Galaxy S 4] mn1968:
Safestrap questions:

I am new to the Verizon S4. I use it on AT&T with H2O. I am on NC5, rooted, and have safestrap 3.75 installed. When I first rooted the phone, I was able to make a successful back up. When the phone went wonky, I decided to restore the back up but somehow I wound up in a bootloop. I was able to restore via odin to NC5. Since then, any attempt to make a backup with safestrap results in the dreaded "failed" message. I was able to successfully backup by checking compression, but that backup failed during a restore (more on that later).

So far I have successfully loaded the Eclipse ROM in slot 1 and was able to switch between stock & Eclipse and had wi-fi & data working. However, I found many functions would not work in Eclipse...such as being able to change the notification toggles.

I then tried Hyperdrive, but during install I may not have activated slot 1 and messed up the phone again. When I went to restore my compressed backup, it failed, as did the original backup. So back to odin and restoring that way.

I have again installed Hyperdrive RLS21 in slot 1. I can again switch between stock & Hyperdrive without problems. However, Hyperdrive won't connect to wi-fi (flashed the wi-fi fix) and internet (data) won't connect to internet or play store. The data connection shows in the status bar though. Again, there are also toggles and/or functions that just don't work. I choose Verizon during setup and changed the APN. Should I have chosen AT&T instead?

Is the rom not fully functional because it's running from slot 1? Should I be installing it/running it on the stock slot? I am really hesitant to do that since I can't seem to get a successful back up and/or restore. Odin works but then I have to reset/restore everything from scratch. I have uninstalled safestrap and reinstalled to no avail. Everyone seems to love safestrap but it's just not working for me. Is there a more comprehensive guide?

Thanks,
[Verizon Samsung Galaxy S 4] AlpineMan:
I've done a few Verizon S4's... All using Hyperdrive installed on stock slot. No issues if you flash it right.
[Verizon Samsung Galaxy S 4] mn1968:
So I've played around a bit more with safestrap - when I backup Hyperdrive in slot 1, the backup is successful. Have not tried to restore it yet (for testing purposes). When I try to back up the Stock ROM, it always fails, unless I check compression. The backup destination for the stock slot and slot 1 are the same, so I don't get what's going wrong. I don't trust the compressed stock backup so I don't want to install any other ROM in the stock slot. Looking for any other advice.

Thanks
[Verizon Samsung Galaxy S 4] klabit87:
Ive always used compression and never used slots.

Never had a problem with restoring a compressed backup to stock slot.
[Verizon Samsung Galaxy S 4] aleggsue:
If you're flashing stuff like Hyperdrive and Eclipse, you should install them on stock slot.
[Verizon Samsung Galaxy S 4] mn1968:
Hi,

I have been getting the itch again to try flashing some ROMs (EmptyGalaxyRom in particular). I've successfully made a backup of my current stock ROM, which is surprising because it always failed in previous attempts (see posts above, if interested). This time I entered recovery through the Safestrap app, though, rather than restarting and selecting recovery from the bootup option. Could this be the difference/reason for my success?

Anyway, based on this recent victory I think I feel confidant enough to flash the EGR ROM to the stock slot (as has been suggested above). If things don't work I think I will be able to restore my backup successfully as well. However, before proceeding, I would like to clarify:

Will flashing the EGR ROM to the stock slot then wipe out my safestrap recovery?

If so, reinstalling it is not an issue...just something I want to be aware of. It's been 4 months since I flashed any ROMs but if I recall correctly, when I flashed Eclipse and Hyperdrive to slot 1, I eventually ran into problems that not only wiped my stock & slot 1 ROMs, but also my recovery. I had to then restore via Odin. It was a lot of hassle that I never had to deal with before with other phones. So, all in all, just trying to prepare for what may ( or may not) happen.

Thanks!

EDIT: So I couldn't wait any longer and flashed EGR ROM last night. Everything went smoothly! On first boot Safestrap was not listed in the app menu but after a reboot it magically appeared. Busy playing around with the new ROM. :)
[Verizon Samsung Galaxy S 4] 3link22:
Update safestrap for 0C1 again mr. But safestrap 3.75 not work from OC1 can not backup rom or costum rom...
[Verizon Samsung Galaxy S 4] XxD34THxX:
There will be no update to OC1 due to how Samsung screwed with ART, the new runtime for android. You need to now use Flashfire, made by Chainfire(I swear, he named it that JUST for that rhyme...)

Flashfire can do backups and flash, but it is straight from the app itself.
[Verizon Samsung Galaxy S 4] ATGkompressor:
FlashFire only downside is not being able to interact pre-system boot. Other than that it really is a masterpiece. I wish there were a way for FlashFire to bridge apk to actually a functional recovery. Example: what u do in the app somehow symlinked to a "safestrapish" recovery. I think it would kill alot of confusion...And it would be pretty cool.
[Verizon Samsung Galaxy S 4] CrazyJ36:
I just got this Verizon S4 today, I hard bricked my last one so I'm making sure of this process:

The phone is untouched, not rooted NK1 4.4.2. And I know I can't get TWRP.

1. I should follow exactly "HOW to Root NK1" http://xdaforums.com/galaxy-s4-verizon/general/how-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613

2 Then, for SafeStrap, I follow this threads' Instructions. "Safestrap-I545-3.75-KitKat-A03.apk"

Correct?

I would also need to make sure of what I can flash in Safestrap without ending in another hardbrick.

Thanks, I'm still new to rooting this phone.
[Verizon Samsung Galaxy S 4] npjohnson:
Yes and yes, but remember once your is SafeStrap, you cannot flash custom kernels. You can use some custom ROMs, however. Like my AOSP ROM KitPop.
[Verizon Samsung Galaxy S 4] CrazyJ36:
Great. Kitpop looks awesome as well.

Now, If I screw any thing up (roms not booting), ODIN will still restore factory, erasing Safestrap, correct?

I ask because I want to able to use only Rom slots for other installs. I've seen many issues with rom slots.
[Verizon Samsung Galaxy S 4] Mrgoldenboy:
does anyone have a link for the safestrap for 5.0 for the S4?

How to delete backups in Safestrap recovery IN 5.0.1
[Verizon Samsung Galaxy S 4] ATGkompressor:
You can try this,https://www.androidfilehost.com/?w=files&flid=49430 but be careful. I don't think it is fully operational on a PURE LOLLIPOP BASE! (I.E. OC1 OR OF1). We (I have a mouse in my pocket) are working on a hijack to be able to get this to work for OC1 users. Right now, even those of us who were able to obtain a downgradeable bootloader are stuck flashing a kit Kat kernel in order to use Safestrap. You might wanna go and download FLASHFIRE. It's not a recovery in the best sense of the word but it does work. I've never had a problem out of it. And note: IF U FLASH ANYTHING IN FLASHFIRE THAT REQUIRES A WIPE...MAKE SURE YOU REPOSITION THE WIPE OPTION BACK TO THE TOP. IT HAS A HABIT OF MOVING IT TO THE BOTTOM WHICH RESULTS IN: A FLASH, THEN A WIPE, AND THAT'S NO GOOD.
[Verizon Samsung Galaxy S 4] cicuye:
Have we settled the question?

So this is my question: Is using Safestrap successful when working with an OC1 or OF1 locked bootloader? I see the date on this post and wonder has anyone solved that issue by now. I don't want to brick my phone...I appreciate the input. Oh and I've installed Safestrap 4.0, it shows status installed but doesn't show up on boot. I have not hit the "reboot to recovery" tab.
[Verizon Samsung Galaxy S 4] ATGkompressor:
No, it's a no go on it so far. People were busy with school, and the age of this device doesn't help either. If your not seeing the SS splash screen upon boot there's no getting in...make sure you have busybox installed. A brick is always possible.
[Verizon Samsung Galaxy S 4] cicuye:
That's what I thought. Thanks for getting back with me. I'll limit myself to compatible roms using Flashfire. That pretty much limits it to Stang, Albe and Hyperdrive. I haven't run Hyperdrive yet, I'll probably do that in the near future.
[Verizon Samsung Galaxy S 4] Astr4y4L:
Ya
[Verizon Samsung Galaxy S 4] jerryspring:
How do u manually access safestrap while phone is off? I flashed a ROM and it's stuck on splash screen. Thanks.
[Verizon Samsung Galaxy S 4] Teracotta:
Any update for the PL1 firmware?
[Verizon Samsung Galaxy S 4] shawn2571:
Lollipop?
[Verizon Samsung Galaxy S 4] previse:
Was given the link to test.
[Verizon Samsung Galaxy S 4] Tool Belt:
Cool. Enjoy!!

YOU GO HASHCODE!!
[Verizon Samsung Galaxy S 4] mlin:
I tried as well and had the same results, wasn't able to get to SS recovery when installed on AOSP.
[Verizon Samsung Galaxy S 4] yofife2069:
You could try flashing the modules from ktoonz kernel on top of your ss rom.
[Verizon Samsung Galaxy S 4] bignazpwns:
To fully uninstall can you just use the termanal emulator to do it or do you need a pc?
[Verizon Samsung Galaxy S 4] yofife2069:
I haven't tried it but the OP says to do it from a pc.
[Verizon Samsung Galaxy S 4] Poofster:
How's it going?
[Verizon Samsung Galaxy S 4] bignazpwns:
I havent installed it yet holding off till tomorrow just wanted to see if anyone atempted that. My pc is broke so I was wondering if anyone atempted thst amd if it works.
[Verizon Samsung Galaxy S 4] previse:
in SS 3.60

- No more wipe error on /cache

- Reworded the /boot not found message as INFO

- Boot partition should be protected in stock now.

- TWRP update to 2.6.3.0

- and CPUs #3/#4 are now back on

So far so good w/ tests. There's some other good things to come, Hashcode is killing it!
[Verizon Samsung Galaxy S 4] michaelg117:
What do you mean by this..? Are they disabled in ROMs other then stock?

Sent from Navi
[Verizon Samsung Galaxy S 4] previse:
As of 3.5 , but 3.6 is rolling out soon.
[Verizon Samsung Galaxy S 4] previse:
Boot to stock rom -> install APK -> Install recovery -> Done
[Verizon Samsung Galaxy S 4] michaelg117:
Any idea if update will drop tonight? Or should I just get to bed :P

Sent from Navi
[Verizon Samsung Galaxy S 4] previse:
Hash has stated that hes gonna roll it out; but i'm not sure when.
[Verizon Samsung Galaxy S 4] baling:
Everything is running well in B09 you are the man! :beer:
[Verizon Samsung Galaxy S 4] T.Treez:
I been trying to figure out why I cant see any zip files in ss to flash? Im updated to the new one as well. Am I missing something?

Ive also put out the zips on my sd card too
[Verizon Samsung Galaxy S 4] decaturbob:
Not sure what u mean

send via hashcode powered S4
[Verizon Samsung Galaxy S 4] madAdam6LOVE:
I'm on true ME7, rooted. Haven't been following the forums due to lack of recovery, so forgive noob question: Will this work on Verizon S4 upgraded to ME7 and rooted?
[Verizon Samsung Galaxy S 4] michaelg117:
That's really the only reason SS was built sir. It'd be best if you went over to general and read through the WIP discussion forum. Tons of good info that would be best to know. Been following both since the start and I feel like if I haven't I would've surely messed up my phone :P

Sent from Navi
[Verizon Samsung Galaxy S 4] madAdam6LOVE:
Thank you sir, just what I was looking for. Will now do all my homework. Sorry, but couldn't tell from thread title and OP whether it was ready for us to try.
[Verizon Samsung Galaxy S 4] Tool Belt:
Go for it. It is very straightforward thanks to hashcode!
[Verizon Samsung Galaxy S 4] Poofster:
Also new to android....but have been following... in safe strap if I do a backup of my stockroom is that what I would use to Odin back to?...should that be the very first thing I do?..I backed up using TB also. Does ss make a "rom" backup?
[Verizon Samsung Galaxy S 4] ashertheplague:
So I have a slight problem I partioned my rom slot to 2gb I deleted it because I wanted 3gb but when I did that it didnt give me back my storage space now I have 500mb left with no way of getting the 4.5 gb of storage back idk if this is a bug or what
[Verizon Samsung Galaxy S 4] :
I have a noob question, so please bear with me...

I'm trying to make space on my phone in order to create a 2gb data partition for my 1st rom slot. Right now I only have space available to create a 1gb partition. I hardly have anything on my internal memory, yet it says i have 6.3GBs of Miscellaneous files... Any suggestions on freeing up some up that memory so I can create a 2gb data partition for my custom rom?

-I'm not interested in creating multiple slots, I just need one so I can run Hyperdrive :)
[Verizon Samsung Galaxy S 4] Roland_D:
It happened to me too... Just set the boot back to stock, reboot, reboot back in ss recovery and try to create a new partition.. You should have the right space now.

---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------

Only suggestion is to clean misc files... Tap on misc in storage menu for a breakdown of the space
[Verizon Samsung Galaxy S 4] :
The files on that list only totals 4mb of the 6gb that's apparently being taken up
[Verizon Samsung Galaxy S 4] Roland_D:
Do you have any backup?
[Verizon Samsung Galaxy S 4] MrKleen1:
Thank you for saving the day for all the S4 owners that missed out on Loki.

And those that should have known better but flashed ME7 anyway. :)

You have saved the day.
[Verizon Samsung Galaxy S 4] :
none that I can find
[Verizon Samsung Galaxy S 4] ashertheplague:
Well I did that and still the same results and 6.3 gb is the size of the system storage you cant get rid of that
[Verizon Samsung Galaxy S 4] reinaldistic:
I'm unlucked from mdk and I would like to use this to multiboot. Can I? Or is this only for me7?

Also any other way to multi boot?
[Verizon Samsung Galaxy S 4] jova33:
You can, just can't flash AOSP ROMs. I've tried, doesn't work.
[Verizon Samsung Galaxy S 4] thunderbls:
Are your downloads set to store on SD card or extsd?
[Verizon Samsung Galaxy S 4] thatbigmoose:
/ss/safestrap/

delete any unused ROM-Slot images.

Make sure SS isn't set to boot the ROM Slot you're deleting.
[Verizon Samsung Galaxy S 4] desantim:
I'm curious how the structure of SS works. Under root I see the following Stucture

/ss/0

/ss/legacy

/ss/obb

/ss/safestrap

The 0 directory has all my applications in it, but it does not seem to be that when I install multiple roms do they carry over. Why is there a folder outside of the /ss/safestap/rom-slot1 which I use as my primary?

The images in /rom-slot1 are cache.img, name, system.img, and userdata.img. Shouldn't all the files in /ss/0 be inside userdata.img? It seems redundant if they aren't shared between roms I install?

Maybe I am just confused. Any explanation would be greatly appreciated.

Thanks!

Mario
[Verizon Samsung Galaxy S 4] bikedude880:
Safestrap mounts those .img files in each Rom slot to /ss directories. This allows for a theoretical infinite maximum number of roms. Considering storage, this maximum is not possible sadly :)
[Verizon Samsung Galaxy S 4] purple_zergling:
Hello everyone, while I enjoyed SS for the S4, it looks like I'm going to be returning my phone to Costco for another. Looks like there's some weird backlight issue, but regardless, I'll be uninstalling SS. It looks like Hash updated the SS apk, but it seems there are still issues with getting a clean uninstall. I'm gonna try to Uninstall SS this way, but I'm not sure how to "check" if it was a clean uninstall. If it isn't clean, I'll go ahead and Odin it but if anyone could enlighten me, how would I check to see if the uninstall of SafeStrap was clean?
[Verizon Samsung Galaxy S 4] yofife2069:
I was curious if you tried to flash an AOSP rom to a rom slot with your stock rom also being an AOSP rom.
[Verizon Samsung Galaxy S 4] coor:
So not paying attention I installed 3.6 using the rom slot. Worked fine though. No problems.
[Verizon Samsung Galaxy S 4] Tomsgt:
How to install HyperDrive rom on Verizon Galaxy S4 using safe strap Video

VIDEO

Thanks Hashcode awesome work
[Verizon Samsung Galaxy S 4] hlxanthus:
[MENTION=4243514]Hashcode[/MENTION] does adb work within your recovery? Any chance you can pull me a recovery.log? Still looking for a prop to call to distinguish Loki vs safestrap via edify scripts

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Glynix:
Title of thread says 3.6 is out now but I only see 3.5 in the downloads. Am I missing it or not posted yet?
[Verizon Samsung Galaxy S 4] Tool Belt:
Actually go to the download page, it is there.
[Verizon Samsung Galaxy S 4] Hashcode:
at 1 point i was discussing a prop: ro.safestrap=1 being set in safestrap recovery.

Not sure if that would help with your issue.
[Verizon Samsung Galaxy S 4] Hashcode:
I posted this on the at&t active Safestrap thread but figured, I should echo this to all the dev threads.

---

This is by no means set in stone, but feature / changes that I'm looking at for the next update include:

- Customizable partition sizes (system, data and cache)

- A method for automatically copying the kernel modules from the stock slot after any flash or restore to rom slots.

- Adding more info to the ROM-slot screen (mostly taken from the current build.prop)

- ROM-slot management to include moving to / from SD card for storage

- Splashscreen (during the boot) options for how long to be shown or hidden all together, custom images for when a rom-slot is active, etc.

- Add virtual boot partition to ROM-slots where .zip files with boot.img files could write to. Then after flash, the ramdisk would be extracted for use with 2ndinit. More ROM compatibility with this feature.

And, of course work on kexec to get custom kernel support.
[Verizon Samsung Galaxy S 4] Tomsgt:
That sound alike some awesome updates. By the way where is the safe strap ROM slot stored on my device. I use to be able to delete a slot in a file explorer. Thanks
[Verizon Samsung Galaxy S 4] :
Thank you for your hard work Hashcode!

Wanted to ask, will this work with LiquidSmooth? I am assuming not, since it is AOSP based...

Thanks
[Verizon Samsung Galaxy S 4] bikedude880:
Correct, it needs to be built for safestrap. Porting CM has already shown 10.1 (4.2.2) to be the best starting point.
[Verizon Samsung Galaxy S 4] jova33:
I'm currently on Hyperdrive, otherwise I'd give it a try. I posted yesterday about my attempt to flash AOKP to a ROM slot. Wouldn't boot, and when I flashed an AOSP kernel in TWRP SS was inoperable. I think SS requires a TW kernel.
[Verizon Samsung Galaxy S 4] decaturbob:
that is correct at this point in time

per hashcode: "And, of course work on kexec to get custom kernel support." If kexec is made to work with GS4 and SS, opens up all the other kernels and the roms based on them.
[Verizon Samsung Galaxy S 4] :
Great, I will hold on then until this comes through. :o