yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Goodtill:
I just did it today. The A2DP issue still is not fixed with the new release. So I flashed 10.2 with the Safestap kernel into the stock partition after 3 complete wipes. No issues and the A2DP works.
[Verizon Samsung Galaxy S 4] an21281:
So I updated to 3.64 last night and made a nandroid backup of slot 1, but couldnt find the backup... Tried again and its giving me a problem, E: Unable to locate '/boot partition for backup. Any idea what the problem might be. Here is a pic
[Verizon Samsung Galaxy S 4] Poofster:
Is 3.6.4 fixed?
[Verizon Samsung Galaxy S 4] michaely123:
Just going to have to wait for SS to work on MJ7.
[Verizon Samsung Galaxy S 4] Easton999GS:
Actually i have AT&T so i ran it under the other carrier option in aroma and i flashed the MF3 Modules and it works fine. Even my air view and pip works without a custom kernel or whatever. even though i cant run one anyway
[Verizon Samsung Galaxy S 4] NilsP:
That actually looks like a normal backup. Will always get the boot and other image error since it is not available to TWRP under SS
[Verizon Samsung Galaxy S 4] joey3002:
Could someone update the OP with a list of Roms that work with this? I am not sure which will work and am planning my weekend of modding. Thanks so much.
[Verizon Samsung Galaxy S 4] lazer9:
Here's a thread dedicated specifically to what you're asking about: ---> http://xdaforums.com/showthread.php?t=2448726

:)
[Verizon Samsung Galaxy S 4] Easton999GS:
NilsP you were my hero on the HTC Rezound =] its nice to see you on the S4. I have AT&T now though... I moved on to a 10GB a month plan. I never stay off my phone lol. << that's with no tethering.
[Verizon Samsung Galaxy S 4] joey3002:
wow, did I swing and miss.. thanks for the link
[Verizon Samsung Galaxy S 4] decaturbob:
??? what do you mean fixed?
[Verizon Samsung Galaxy S 4] lazer9:
There is currently an issue with flashing themes. Atleast the Cobalt one fails to theme when flashing. Hash is looking into it. Otherwise I found no issues with v3.64.
[Verizon Samsung Galaxy S 4] Poofster:
That was it
[Verizon Samsung Galaxy S 4] Hmong_Xiong:
will this work if we're rooted mj7? just got my s4 stock mj7 4.3 and rooted it with vroot
[Verizon Samsung Galaxy S 4] lazer9:
I've moved to the "Dark Side"... Finally started fresh with wiping stock (safe-side) and successfully flashing Hyperdrive v10.2 to Stock -non slot-. Used the Safestrap Kernel in Aroma as mentioned previously. I was also able to restore a fresh Nandroid (Data Only) to get back up and running. I then installed "Safestrap" so I could get recovery back and pressed "Install Recovery" within safestrap as before when starting out.

My only issue is I'm not getting the safestrap splash screen or option to boot into recovery when rebooting from the Rom. Rather, I've found I have to select to turn the phone completely off instead of just "Reboot" and then it will usually bring up the Safestrap screen OR boot directly into recovery.

I know flashing to stock side isn't recommended but I seem to have had a general success and just thought I would post on my minor dilemma and see if any others who took this route are experiencing the same?
[Verizon Samsung Galaxy S 4] an21281:
Yes you are right, its working fine. Not sure why I could not find the backup folder the first time I tried...

---------- Post added at 12:27 PM ---------- Previous post was at 12:23 PM ----------

Will be trying to either flash a custom rom on stock slot or restore a nandroid on stock slot today. Will see if I get the same problem ;)
[Verizon Samsung Galaxy S 4] Hashcode:
New build incoming once some tester feedback rolls in. v3.65 fixes the bug [MENTION=650592]lazer9[/MENTION] pointed out. Also has a TWRP update and other cleanup.
[Verizon Samsung Galaxy S 4] Hashcode:
I'll take a look at this a bit, but it can be a very slippery slope when supporting custom ROMs on the stock slot. I try not to rely on any binaries being installed on the stock ROM but its bound to happen.
[Verizon Samsung Galaxy S 4] vdub2pt0:
Did this fix the bluetooth remote control issue?! I am going to give this a shot if it does
[Verizon Samsung Galaxy S 4] lazer9:
I'm not sure as I don't have bluetooth remote nor ever used that feature but I've heard it does.

--------------------------

Thanks hash for your continued hard work on this and acknowledging my find with the themes flashing issue.
[Verizon Samsung Galaxy S 4] vdub2pt0:
Also, just to clear things up for me, and probable others as well; when you say "wiped" the stock slot, did you just do the factory reset option or advanced wipe (cache, dalvik, data, system)?
[Verizon Samsung Galaxy S 4] lazer9:
If I recall, I did an advanced wipe - choosing the dalvik, cache, data & system. Then in Aroma installer, I changed from just dalvik & cache to also wipe data or whatever that top option is. I did not factory reset.
[Verizon Samsung Galaxy S 4] michaelg117:
Hey hash, is work on kexce or whatever it is coming along?

Sent From Navi

Fired To Beef.

Big Grief Beef.
[Verizon Samsung Galaxy S 4] k1mu:
No. At the current time safestrap does not install on MJ7. There's no way to know if it's possible to bypass the protections that 4.3 adds to allow Safestrap to work.
[Verizon Samsung Galaxy S 4] vdub2pt0:
Awesome. Thanks for the help. Now I am debating if i should try this now and risk a brick. I won't be home to fix it until laye tonight if I do. I will report back my findings when I do and let everyone know how it works

Sent from my SCH-I545 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S 4] Hashcode:
New version of Safestrap in the OP: v3.65

CHANGELOG:

[2013/11/13] [v3.65] TWRP updates

[2013/11/13] [v3.65] "toolbox" binary / symlinks in recovery fixed (was causing some .zip files not to work correctly)

DOWNLOADS:

CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY S4

LATEST FILE: Safestrap-JFLTEVZW-3.65.apk

Main XDA Downloads Page

Mirror 1: http://goo.im/devs/Hashcode/jfltevzw

Mirror 2: http://downloads.crackflasher.com/?dir=Devs/Hashcode0f/jfltevzw/safestrap

Enjoy

EDIT: OK, files are now live.
[Verizon Samsung Galaxy S 4] UK_Wildcats_Fans:
3.65 is only in Mirror 2. I did not see them in the first links.
[Verizon Samsung Galaxy S 4] decaturbob:
having an issue with installing 3.65.

1, downloaded and verified md5 to be ok

2. installed apk thru my existing slot 1 rom (hyperdrive)

3. installed recovery and rebooted

4. reboot skipped safestrap splash screen altogether and booted up my slot rom

5. wtf

6. stock slot still showed 3.64 so I uninstalled and then reinstalled 3.64

7. rebooted as I hoped to safestrap screen and booted slot 1 rom rom

repeated this process a couple times where I installed 3.65 in slot one rom and had same experience where a reboot to me to stock rom slot

not chancing a 3.65 install via stock rom slot
[Verizon Samsung Galaxy S 4] Wi1son:
Yea - Same thing happened to me.
[Verizon Samsung Galaxy S 4] UK_Wildcats_Fans:
Me too. DO NOT INSTALL 3.65 from the stock ROM slot. I learned the hard way.

I changed the boot ROM from Slot 1 (Hyperdrive) to Stock ROM. I then uninstalled 3.62 and installed 3.65. Opened SafeStrap app, grand Superuser permission, install recovery, reboot to recovery. I am still booting into the stock rom and don't ever get the safestrap screen on boot. Powered down, pulled battery and retried. Same thing. I even tried to uninstall 3.65 and reinstall 3.62. It had the "Install Recovery" grayed out stating that I had a newer recovery installed. I could uninstall the recovery, but I didn't want to look my Hyperdrive ROM slot.

I just downloaded and tried 3.64 and I am getting the same results as 3.62.

If I uninstall recovery, do I lose my Slot 1 (Hypderdrive)?
[Verizon Samsung Galaxy S 4] decaturbob:
I was lucky I still was showing 3.64 in my stock rom slot so I did an install recovery there...but safe strap in my slot one is 3.65 and I can't overwrite 3.64 but at this moment I do get ss splash screen and can have slot 1 or slot 2 boot up.

powered by hashcode safestrap hyperdrive 10.2
[Verizon Samsung Galaxy S 4] lazer9:
Guys! You are only supposed to install/update safestrap on the Stock (Safe-Side), NOT IN THE SLOTS!!!
[Verizon Samsung Galaxy S 4] dydigital:
No you won't lose your slots.

I had the same issue when i installed 3.65. here is what i did.

Just go into the safestrap app click uninstall recovery, then uninstall app itself. Then i installed 3.64 app and opened it clicked install recovery. Next time you boot it should just boot to whatever slot you had activated before you installed the 3.65 recovery and you will see the safestrap on reboot also
[Verizon Samsung Galaxy S 4] Lou 270:
Can't get it to download even when I use mirror 2
[Verizon Samsung Galaxy S 4] decaturbob:
Not true. I have done all my ss updates in slot one...no problem till now with 3.65

powered by hashcode safestrap hyperdrive 10.2
[Verizon Samsung Galaxy S 4] UK_Wildcats_Fans:
Thank you. I assumed that I wouldn't lose the rom slots, but I wanted to be safe because I didn't get a chance to backup some stuff on the slot 1. Your method worked for me too.
[Verizon Samsung Galaxy S 4] an21281:
I tried a factory reset on stock slot and I had to Odin, so only do a advanced wipe of cache, Dalvik, system and data on stock slot if you choose this route...

Will be updating to 3.65, like others have pointed out the download is only available in mirror 2. I always apply it to stock slot by clicking uninstall in ss apk, uninstall the old ss apk, install the new apk then click install recovery. Thanks for the support Hash

Sent from SGS4 PAC4.3
[Verizon Samsung Galaxy S 4] Lou 270:
I have been to mirror 2 and it isn't working
[Verizon Samsung Galaxy S 4] lazer9:
:p:confused::eek: That is truly news to me as I have always installed the safestrap app and the subsequent recovery install ONLY from the stock side. I swear this is even in the OP or FAQ somewhere unless I'm mistaking the instructions for the SS I always used on my Droid Rzr Maxx.
[Verizon Samsung Galaxy S 4] Hashcode:
Something is up with this file. Sorry about that. I'll double check everything and re-upload later tonight.
[Verizon Samsung Galaxy S 4] vdub2pt0:
I just installed Hyperdrive 10.2 in the stock slot. I now have working bluetooth remote control and when I restart the phone, I still get the safestrap splash screen that asks if I want to continue booting or go to recovery.

These are the exact steps I took.

1. Delete all rom slots, frees up extra space.

2. Select stock slot and boot up.

3. Reboot to stock android recovery, select wipe data/factory reset. I did it twice just to be sure. Doing this freed up some space on my internal storage that I could not figure out where it was being used.

4. Boot into TWRP, select stock rom and wipe/advanced wipe and select data, system, cache, and dalvik. I also did this twice.

5. Select install and install Hdrive 10.2. I also chose the option to factory reset within aroma. *Be sure to select safestrap kernel in aroma. Un check reboot when done installing. You don't want to leave recovery yet.

6. Flash Me7 modem fix (or whatever the file is called in this thread) that is required for all Me7 phones after installing a rom

7. Reboot and wait 10 minutes to touch anything

Hope this helps. I am up and running strong, zero problems.

Sent from my SCH-I545 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S 4] decaturbob:
thanks hash, also set me straight but I have been able to update SS without being in the stock rom until the 3.65 update.
[Verizon Samsung Galaxy S 4] jackcarroll3:
I updated to 3.65 and my phone would not boot into SS. Now when I try to install 3.64 I get an error. Should I uninstall SS using the instructions in the PO or is there an easier way to revert back to 3.64?
[Verizon Samsung Galaxy S 4] lazer9:
Strange to see the reports of problems with v3.65

I downloaded from the 2nd link (mirror) last night.

Installed to "Stock/Safe-Side" as I always do, this time of course I'm running Hyperdrive v10.2 in that position though.

Have been able to boot up normal and select recovery just fine ever since the update.

:silly::highfive::good:
[Verizon Samsung Galaxy S 4] UK_Wildcats_Fans:
Just look back on the previous page of posts. Uninstall 3.65 app and install 3.64 app. From 3.64 app just uninstall recovery and then reinstall recovery from the app. You won't look any data or slots.

This worked for me.
[Verizon Samsung Galaxy S 4] jackcarroll3:
I guess the only difference is that I am running Hyperdrive 10.2 on slot one. I booted into safe side to install SS and then it would not boot into SS. After uninstalling 3.65 and reinstalling 3.64 all is good now.
[Verizon Samsung Galaxy S 4] Hashcode:
Getting a new Safestrap build ready after a bit of cleanup.
[Verizon Samsung Galaxy S 4] Alowbman:
You the man!
[Verizon Samsung Galaxy S 4] Marshmellow92:
will it only be one rom compatible or any as of the new build to come?
[Verizon Samsung Galaxy S 4] :
Use the discussion thread. This is the development thread.

http://xdaforums.com/showthread.php?t=2428226

[RECOVERY LOCKED/ME7] Safestrap Recovery v3.5x [WIP DISCUSSION]
[Verizon Samsung Galaxy S 4] michaelg117:
Was that a stock ROM or am I tripping?!

Sent from Navi
[Verizon Samsung Galaxy S 4] killajoe:
That was the GPE in the YouTube video
[Verizon Samsung Galaxy S 4] sokrboot:
Those hands on the video are lethal programming weapons! Part surgeon, part artist. If it wouldn't be so creepy I'd reference you as a Man Crush...but it *is* creepy so I won't go there. LOL.

You, sir have my sincerest thanks and gratitude!

««Yeah I'm strapped...SafeStrapped on my S4.»»
[Verizon Samsung Galaxy S 4] michaelg117:
But from my understanding they're basically the same, correct?

Sent from Navi
[Verizon Samsung Galaxy S 4] SamuriHL:
Absolutely epic, man. Congrats to everyone waiting for this and a HUGE THANKS to Hashcode for the amazing work on this! WELL DONE!!
[Verizon Samsung Galaxy S 4] killajoe:
I Believe the kernel is relatively the same but the rom isn't anything like TW.. but don't quote me on that
[Verizon Samsung Galaxy S 4] :
My wallet is ready lol
[Verizon Samsung Galaxy S 4] rickw001:
well done hash,you helped a lot of people,just hope they listen this time
[Verizon Samsung Galaxy S 4] xM Minton Mx:
I'm not on me7 but great work. Congrats on your hard work.
[Verizon Samsung Galaxy S 4] xlightwaverx:
HighSpeed Mirror: http://downloads.crackflasher.com/?dir=Devs/Hashcode0f/jfltevzw

Great Job Hash!

X
[Verizon Samsung Galaxy S 4] michaelg117:
And did I miss something or should it always say Disabled?

Sent from Navi
[Verizon Samsung Galaxy S 4] Hashcode:
I should have explained about the DISABLED / ENABLED splashscreen. When you create a ROM-slot and "Activate" it for booting/flashing. The splashscreen will say ENABLED. When you're on the stock ROM it will show DISABLED.
[Verizon Samsung Galaxy S 4] thejulianath20:
I see what you did there! ;) "HASH"code and post at 4:20... ;)

But seriously, I am so thankful for this once I'm running it all I'm donating fo sho!
[Verizon Samsung Galaxy S 4] Alxoom33:
Awsome HC!!!

Any progress on encryption? I'm on mdk, but no recovery works with encryption. As far as I know except runandhide ' TWRP for Xoom.:rolleyes:
[Verizon Samsung Galaxy S 4] Hashcode:
I'll try and simulate some different scenarios and diff up the 3.64 release with the 3.65 to see what changed.

The APK is working for my current install, but my device is actually on MDK still. So that may be part of the issue.

Sorry for the delay.
[Verizon Samsung Galaxy S 4] SamuriHL:
What, you don't want to upgrade it to MJ7?? :D LOL! (It's a joke, people, relax. :))
[Verizon Samsung Galaxy S 4] Hashcode:
I need one of the users who was having issues on the v3.65 to hop into irc freenode.net #safestrap and run a test of a new build pls. :)
[Verizon Samsung Galaxy S 4] inkdaddy66:
I know this thread states ME7 SS. Is there a SS for MI1?

53N7 FR0M M4 DMAXX V1A 7A9A7A7K
[Verizon Samsung Galaxy S 4] Hashcode:
Can I get a tester or 2 to try this new build of v3.65 for the VZW S4?

http://goo.im/devs/Hashcode/jfltevzw/safestrap/Safestrap-JFLTEVZW-3.65.apk

Let me know if the splashscreen is showing, etc.

NOTE: This APK works on my device. Hopefully it works on the ME7 build as well.
[Verizon Samsung Galaxy S 4] decaturbob:
downloading and moving to my phone.

---------- Post added at 06:01 AM ---------- Previous post was at 05:44 AM ----------

Hash,

downloaded the SS apk and installed in the same manner I have installed all other updates where I do it with in the current ROM Slot and in my case, Slot One (Hyperdrive). Looks like everything works fine. Rebooted and SS splash screen came up. Looks like issue is corrected. Thanks for immediate help and response as always
[Verizon Samsung Galaxy S 4] Gator Brah:
downloading. will report back shortly.

One thing i noticed recently...this happened twice within a week. i reboot my phone and it loads the stock rom slot. rebooting again does the same thing until i pull the battery and then start it up. It will load the correct partition then.

---------- Post added at 02:50 PM ---------- Previous post was at 02:42 PM ----------

Hash,

Installed new SS with no problems. booted to recovery switched back and forth between rom slots, flashed jelly beans to my test slot...ect. everything looks good to me.

GS4 on Verizon - ME7 build
[Verizon Samsung Galaxy S 4] decaturbob:
as far as I know only ME7 is officially supported by Safe Strap and the 4.2 base TW ROMS....4.3 based roms are not supported nor other non-TW ROMS and kernels
[Verizon Samsung Galaxy S 4] lazer9:
People have reported some success using safestrap with MI1, however, you will have to find the module floating around here in the dev forum to flash after the ROMs install. Note, you won't have auto-rotation and I think one other thing.
[Verizon Samsung Galaxy S 4] inkdaddy66:
I guess I should have waited to update the wife's S4. I'll look for the module

53N7 FR0M M4 DMAXX V1A 7A9A7A7K
[Verizon Samsung Galaxy S 4] Hashcode:
Modules for M1 are in the downloads section here:

http://xdaforums.com/devdb/project/dl/?id=1342
[Verizon Samsung Galaxy S 4] inkdaddy66:
Thank you. I really appreciate that

53N7 FR0M M4 DMAXX V1A 7A9A7A7K
[Verizon Samsung Galaxy S 4] Hashcode:
Updated the OP with the new v3.65 build. Oddly Crackflashers is still showing the old md5sum even tho it's the new file. I hope that updates.

For reference the MD5SUM: d181978a97776d928293f1ee21e83a85

Let me know how the installs go
[Verizon Samsung Galaxy S 4] lazer9:
Working fine. I uninstalled recovery via original 3.65 build from the other day. Uninstalled safestrap. Downloaded latest v3.65 build from 1st link. Installed, Installed Recovery from app. Rebooted to recovery. Success! And all seems well. :good:
[Verizon Samsung Galaxy S 4] fillyo:
I just came over from the S3. I have a S4 with MI1 and I'm rooted. I have not done anything else other than debloat a little. If I read correctly, safestrap is a little wonky on MI1, correct? Even still, if you flash a ROM that works for MI1, do you need the ME7 baseband? This is depressing coming from the S3, everything seems so difficult.
[Verizon Samsung Galaxy S 4] lazer9:
It shouldn't be that wonky really. No, you only use the MI1 module after flashing a rom. The main issue I've heard of that lingers and is lost from ME7 to MI1 at this time is Autorotation is broken. Give it a shot! Well worth it to be able to flash a custom ROM! :D:cowboy:
[Verizon Samsung Galaxy S 4] UK_Wildcats_Fans:
I used the same process and it is working for me too. Thank you Hash
[Verizon Samsung Galaxy S 4] Lou 270:
Working good for me also thanks again
[Verizon Samsung Galaxy S 4] Kelsey Jones:
So do we stil need to flash the MI1 module if safestrap support MI1?
[Verizon Samsung Galaxy S 4] lazer9:
Yes, right after installing a ROM.
[Verizon Samsung Galaxy S 4] zmedhaug:
oh sweet man now my phone says custom when i boot up.... freaking sweet i was trying to avoid this. anyone know how to get this off? and i know you cant use triangle away. thats how my last phone bricked.
[Verizon Samsung Galaxy S 4] k1mu:
That's not worth worrying about. If you ever need to return or want to sell the phone, When you need to clear the "custom" flag, just flash a stock ROM and it'll be fine.
[Verizon Samsung Galaxy S 4] zmedhaug:
I odined the stock file and its still there. thats what i mean does anyone know how to remove it at all? I'll write a guide if someone can confirm a way to remove it.
[Verizon Samsung Galaxy S 4] k1mu:
Flash a stock ROM, as I said. No-wipe images may not clear it, but full images will.

Using the Verizon emergency recovery tool will also reset the custom status.

Rooting after flashing stock will often set the custom status. But again, who cares?

If you need to clear that without losing data, use Triangle Away. That worked for me on ME7.
[Verizon Samsung Galaxy S 4] zmedhaug:
ok thanks. it didnt work on MJ7. it actually bricked my device
[Verizon Samsung Galaxy S 4] k1mu:
Wow. Bricked it? As in the proper definition of "bricked" which means that it does nothing? No boot, no recovery, no download mode? Again, wow. That usually means you tried to flash something completely incompatible with your phone- there are, after all, lots of variants of the GS4 and lots of people who seem to not understand that.

I suspect you mean soft bricked, i.e. responding to an invalid flash by dropping in to downloader/recover mode. You can recover from a soft brick by re-flashing valid firmware. You can't recover from a brick fail using anything but JTAG.

So, assuming that you soft-bricked something, did you try the VZ recovery agent?

I soft-bricked my phone trying to test the Root de la Vega hack that I tried to update for MJ7. I recovered it using the full factory reset posted in this forum with no problems other than having lost all of my data.
[Verizon Samsung Galaxy S 4] zmedhaug:
Yes had to drive an hour for a guy to jtag it
[Verizon Samsung Galaxy S 4] todd3835:
First off, let me say that Safe strap is the only reason my S4 didn't go back to the store. That said, I'm wondering what it is that these modules do exactly. Why is it that we can't get one for AOSP builds? Is it that the stock kernal just won't run on something that isn't TW based?
[Verizon Samsung Galaxy S 4] Hmong_Xiong:
I want to do this so bad...stupid MJ7

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] decaturbob:
The lockdown of bootloaders makes the task of finding an exploit extremely difficult. I suspect that Hash concentrates his efforts that benefits the majority and safestrap gives us all options of running a limited number of custom roms based on specific kernel builds. I know hash would like to find a way to get kerec (sp?) working for us but again, finding the exploit to do so is extremely difficult. The sad fact is, in the not so distant future most phones will not be hackable unless the big service providers allow "dev" phones to be available to those who wish to mod. These phones would probably be priced at a premium with a very narrow warranty. This is a business decision to court the enterprise customers who purchase phones in massive quantities. Corporations require complete security that can't be bypassed.
[Verizon Samsung Galaxy S 4] NilsP:
Looking good. Everything seems to be working on latest

Thanks