Database Develop

[Q] Safestrap 3.75 - Unable to display splash screen

I'm in the process of trying to upgrade my Dynamic Kat 4.3 ROM to the most recent 4.4 version, and saw that I needed to update my Safestrap from 3.71 to 3.75. I downloaded the Safestrap 3.75 apk (as well as made sure I had the most recent Busybox version already installed), and installed it. Everything appeared to install fine with no issues. I rebooted to try to go into Safestrap, but did not get the splash screen with an option to boot in the Safestrap recovery. I noticed on the 3.75 post that not seeing a splash screen is known issue and the suggestion was just to try re-installing the apk. I have since tried uninstalling/reinstalling the 3.75 apk probably about 6-8 times, then I tried uninstalling 3.75 and back-leveling to 3.71... still no splash screen. Then I tried uninstalling and re-installing 3.75.... again, no splash screen. At this point I've uninstalled/reinstalled over 10 times now, and am at a loss as to where to go next. I've spent about an hour looking around on google and in the forum here for people with the same issue but haven't had any real luck. This seems like such a trivial problem that should be able to fixed that I really don't want to have to revert back to Stock through ODIN mode and re-root, re-flash ROM, etc. if at all possible. Is there anything else that can be done to resolve this?
Any help/suggestions would be greatly appreciated.

MorningThunder said:
I'm in the process of trying to upgrade my Dynamic Kat 4.3 ROM to the most recent 4.4 version, and saw that I needed to update my Safestrap from 3.71 to 3.75. I downloaded the Safestrap 3.75 apk (as well as made sure I had the most recent Busybox version already installed), and installed it. Everything appeared to install fine with no issues. I rebooted to try to go into Safestrap, but did not get the splash screen with an option to boot in the Safestrap recovery. I noticed on the 3.75 post that not seeing a splash screen is known issue and the suggestion was just to try re-installing the apk. I have since tried uninstalling/reinstalling the 3.75 apk probably about 6-8 times, then I tried uninstalling 3.75 and back-leveling to 3.71... still no splash screen. Then I tried uninstalling and re-installing 3.75.... again, no splash screen. At this point I've uninstalled/reinstalled over 10 times now, and am at a loss as to where to go next. I've spent about an hour looking around on google and in the forum here for people with the same issue but haven't had any real luck. This seems like such a trivial problem that should be able to fixed that I really don't want to have to revert back to Stock through ODIN mode and re-root, re-flash ROM, etc. if at all possible. Is there anything else that can be done to resolve this?
Any help/suggestions would be greatly appreciated.
Click to expand...
Click to collapse
It sounds to me as if you were on JB and tried to use a KK rom through Safestrap. You can't do that because SS doesn't flash the kernel. You can't run a TouchWiz based KitKat rom on a JellyBean kernel. Your only option is to either Odin back to stock JB and use the setup you had been running, or Odin to stock 4.4.2 KitKat after which you can root, install SS 3.75. Only then will you be able to run the latest DynamiKat rom. All this is assuming you're using an AT&T note 3.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
---------- Post added at 02:40 PM ---------- Previous post was at 02:03 PM ----------
I misread your post thinking you were no longer able to boot at all. If you want to stay on JB, just reinstall SS 3.71. Make sure you're actually installing the recovery and not just the apk. But if you want the latest DynamiKat Kitkat version, you're going to have to upgrade your phone to 4.4.2 first.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I misread your post thinking you were no longer able to boot at all. If you want to stay on JB, just reinstall SS 3.71. Make sure you're actually installing the recovery and not just the apk. But if you want the latest DynamiKat Kitkat version, you're going to have to upgrade your phone to 4.4.2 first.
Click to expand...
Click to collapse
Thanks for the reply!!
OK, so maybe I misunderstood what it would take to upgrade to KK... The ROM I'm running now is JB and I had thought that I could just download the APK for Safestrap 3.75, and uninstall the 3.71 version I already had, install 3.75, then go into the 3.75 SafeStrap and install my new KK rom.... it sounds like it isn't that simple.
My phone is booting and working just fine right now on the older Dynamic Kat JB rom I've been running, it just doesn't display the splash screen for Safestrap now when I reboot. You mentioned I need to upgrade my phone to 4.4.2 first in order to use SS 3.75 and install a KK rom, and I thought that just installing the 3.75 Safestrap apk did that. What is the process to upgrade the recovery to 4.4.2 if I can't just install the SS 3.75 APK?

I could be wrong but I'm pretty sure SS 3.75 only works if you're on 4.4.2. I think you're misunderstanding though. SS doesn't upgrade your phone. You have to upgrade your phone's firmware yourself to 4.4.2. Then you can use SS 3.75 which is COMPATIBLE with 4.4.2.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I could be wrong but I'm pretty sure SS 3.75 only works if you're on 4.4.2. I think you're misunderstanding though. SS doesn't upgrade your phone. You have to upgrade your phone's firmware yourself to 4.4.2. Then you can use SS 3.75 which is COMPATIBLE with 4.4.2.
Click to expand...
Click to collapse
Ahh ok. I do have an AT&T Note 3, and I know I haven't updated the firmware to 4.4.2 yet. Is there a post stickied somewhere with a link and instructions to install the new firmware?

This should lead you in the right direction
http://forum.xda-developers.com/showthread.php?t=2838117
Sent from my AT&T Galaxy Note 3 using Tapatalk®

Right on. Thank you for help sir!

You're welcome.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

[How-To] Update to I537_OC7 - 5.0.1 and KeepRoot

**You can begin the following process from 4.4.x Build/ROM or higher but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Caution!** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Download:
- I537_OC7_Stock_Rooted_ROM
- I537_OC7_Stock_Rooted_Deodexed_ROM
Pevious Builds:
- I537_OC6_Stock_Rooted_ROM
- I537_OC6_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to "Download."
6. Press the lightning bolt then "Ok" to begin the flash.
7. Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- I537_OC7_TetherAddOn
- I537_OC6_TetherAddOn (Flash using FF's "Flash zip or ota" option.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@thisisapoorusernamechoice - for capturing the ota update and for his system dump.
@Chainfire

muniz_ri said:
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Attention** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Instructions:
Click to expand...
Click to collapse
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix

thisisapoorusernamechoice said:
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix
Click to expand...
Click to collapse
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon

Joe-Tech said:
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon
Click to expand...
Click to collapse
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option

thisisapoorusernamechoice said:
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option
Click to expand...
Click to collapse
Only way im thinking to boot the new LP ROM, is to use @muniz_ri method so we can upgrade and keep root. So now we going to be on the OC6 kernel and baseband, since the gpe can boot without flashing the kernel. Then we can flash the GPE 5.x ROM, either with safestrap or FlashFire, and we can also use Odin to flash the stock kernel/partitions. But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.

Joe-Tech said:
But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.
Click to expand...
Click to collapse
Were other rooted apps able to get root permission?

thisisapoorusernamechoice said:
Were other rooted apps able to get root permission?
Click to expand...
Click to collapse
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.

delete
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

Joe-Tech said:
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.
Click to expand...
Click to collapse
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question

thisisapoorusernamechoice said:
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question
Click to expand...
Click to collapse
I don't think it will make any difference.

@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.

Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
Extract the tar from the rar. Leave the zip as is. Copy the tar and the zip to your phone's internal memory or external SD card, somewhere it'll be easy for you to find

Devo7v said:
@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.
Click to expand...
Click to collapse
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
If all of the above is beyond your level of understanding I strongly suggest you reconsider attempting to modify your phone.

muniz_ri said:
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.
Click to expand...
Click to collapse
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.

Devo7v said:
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.
Click to expand...
Click to collapse
Did not bother to try since it has not worked on any 5.0 release so far.

muniz_ri said:
Did not bother to try since it has not worked on any 5.0 release so far.
Click to expand...
Click to collapse
Any chance I can implore you to try it since there will inevitably be a bunch of people already on the OC6 firmware asking how to root it and will get pissed when they find they have to wipe their phone? Or maybe you could just provide the stock OC6 kernel and I can convince @thisisapoorusernamechoice to give it a shot?

For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.

bobbylx said:
For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.
Click to expand...
Click to collapse
A couple questions:
What firmware were you coming from?
How long did you wait?
Did you have Xposed enabled?

Lost Safestrap after Lolipop upgrade.

This is a Verizon Samsung Note 3 SM-N900V.
I recently installed Lolipop with Odin to ipgrade.Jasmine ROM 3.5
Safestrap we working until I upgraded to Lolipop. Root is intact, but SS just aren't there. I can't get SS to would at all, it says it is installed in the app, but it doesn't come up on reboot anymore.
Is there any way to get my SS working again? The phone is fine and still rooted, but SS adds a layer of data integrity that we can all deal with more of.
This this no matter
Thanks!!

Gundie said:
This is a Verizon Samsung Note 3 SM-N900V.
I recently installed Lolipop with Odin to ipgrade.Jasmine ROM 3.5
Safestrap we working until I upgraded to Lolipop. Root is intact, but SS just aren't there. I can't get SS to would at all, it says it is installed in the app, but it doesn't come up on reboot anymore.
Is there any way to get my SS working again? The phone is fine and still rooted, but SS adds a layer of data integrity that we can all deal with more of.
This this no matter
Thanks!!
Click to expand...
Click to collapse
I just wanted to add some info that might help:
The phone is a SM-N900V
Kernel version 3.4.0
JasmineROM-V5.1.1-lrx21v.n900vvrue0b6
Se enforcement enabled
Running Knox 2.3
Is there any way that I can put Safestrap back on?
Thanks in advance.

Yes, you need to install NC2 flasher...but before you do this, find the kernel for Lollipop and put it on your phone. That way you can flash it from safestrap so when you reboot it will work correctly. Switching back and forth between kernels is the only way! If you don't have the kernel on your phone, you need to put the phone in download mode and ODIN the kernel over.

Installing Custom Recovery on Rooted ATT Galaxy Note 3 with Lollipop 5.0

Disclaimer: I am not an expert in this field by any means and am just figuring a lot of this out for the first time. I need some help but will appreciate your patience! : )
I recently completed the Step by step tutorial to upgrade my ATT Galaxy Note 3 to Lollipop and Root it, provided here: droidviews.com/update-att-note-3-with-lollipop-ota-and-root-it
Everything seems to have worked out, despite a few errors on my behalf (forgot to back up and boot loop forced me to factory reset and start over. Oops), but now I'm stuck trying to figure out how to get Xposed Framework installed. Since I'm now upgraded to Lollipop, I no longer have access to Safestrap, so I tried to install the Xposed Framework in the stock recovery, which failed. Also, I did confirm that I have Root.
Everything I've read states I need to use custom recovery, such as TWRP, but I can't find a way to install it on my device.
Can somebody please help me out here?

Anyone have any idea if Xposed Framework can be installed on Note 3 w/ Lollipop 5.0 using FlashFire?

MJohnson2k8 said:
Anyone have any idea if Xposed Framework can be installed on Note 3 w/ Lollipop 5.0 using FlashFire?
Click to expand...
Click to collapse
It can, I've done it before. Worked perfectly.

Note 8 Root Advancement Query

Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?

2Tone23 said:
Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?
Click to expand...
Click to collapse
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.

Jammol said:
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.
Click to expand...
Click to collapse
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?

2Tone23 said:
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?
Click to expand...
Click to collapse
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.

So I can actually flash custom roms with this lock bootloader on this variant? Also, safestrap will allow me to flash custom roms as well?

Jammol said:
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.
Click to expand...
Click to collapse
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.

2Tone23 said:
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.
Click to expand...
Click to collapse
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.

Jammol said:
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.
Click to expand...
Click to collapse
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.

2Tone23 said:
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.
Click to expand...
Click to collapse
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.

Jammol said:
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.
Click to expand...
Click to collapse
Jammol, I really appreciate your responsiveness and all of the knowledge you've provided. Thanks you!

Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?

2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
I have the free version of Busy Box installed. Tried installing the pro version in case that would somehow facilitate the installation of Safestrap and the pro version won't install either. The notice suggests I try installing in another location. Not sure how to do that. Can anyone advise me on this and /or how I can get Safestrap to install?

2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.

Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.

Jammol said:
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.
Click to expand...
Click to collapse
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.

2Tone23 said:
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
Click to expand...
Click to collapse
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).

Thanks, J. Really appreciate your feedback. Will let you know if something gives.

Jammol said:
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).
Click to expand...
Click to collapse
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)

2Tone23 said:
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)
Click to expand...
Click to collapse
Lol, no problem.