I flashed the kernel module zip. I am trying to locate the name of the GPE Rom I flashed, but it is the one that was linked to this thread or the other one in General.
[RECOVERY LOCKED] Safestrap Recovery v3.71/v3.72 [2014-04-02 KK Beta]
- Thread starter Hashcode
- Start date
I flashed the kernel module zip. I am trying to locate the name of the GPE Rom I flashed, but it is the one that was linked to this thread or the other one in General.
Did u flash the rom from the link provided or did u look for one in the dev section?? our buddy dtroung23 had a bad flash with a GPE rom. trying to figure out what rom he got.
HI
THIS IS THE THREAD OF WHICH posting ROMS IN GENERAL (AT & T Official Discussion S4 Safestrap) EDIT http://xdaforums.com/show...php?p=43394245
[ROM] Google Edition 4.2.2 [Clean] [Slim] [280MB] [2013.09.07????
THIS WAS THE ONE YOU USE?
THIS IS THE THREAD OF WHICH posting ROMS IN GENERAL (AT & T Official Discussion S4 Safestrap) EDIT http://xdaforums.com/show...php?p=43394245
[ROM] Google Edition 4.2.2 [Clean] [Slim] [280MB] [2013.09.07????
THIS WAS THE ONE YOU USE?
So far running MDOB 2.2 and I am seeing no issues thus far. Wifi is working no problem; texting, calling, GPS all working fine. I am using wifi to assist with my location, however, once I test GPS with wifi off I'll report back. So far, fantastic experience, thanks Hashcode!!!
EDIT: I did flash the mf3 module, just so we're clear.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
EDIT: I did flash the mf3 module, just so we're clear.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Last edited:
If u flashed the one in the General Section link, then it was maybe the verizon version.. Thats the only think i can think of if u did all the steps correctly. What if u press vol Up + Home + power... the release power untill u see "Recovery booting" on the top left.. from there just do a factory data reset... hope that helps..
Ya that is the one I used. I am thinking that it has to do with Rom Slot 1 not activating properly. Not sure why this would happen as others have been able to flash successfully. I'm heading to Best Buy later today to have them restore my phone back to MF3 Stock and/or get a replacement unit.
This is gpe rom I flashed.
http://xdaforums.com/showthread.php?t=2341376
[ROM][DEODEX/ODEX]][ROOTED] Google Edition 4.2.2 - v1.3
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
HI
IF SO YOU FLASHER THE Atachment DE (GS4BUIL.PROP)
THAT POST IN FORUM ROMS? (CLEAN) FOR USERS GS4 ATT??
SORRY FOR THE QUESTION BUT I WANT TO INFORM YOU AS POSSIBLE ..... BUT MANY ARE NOT GUARANTEE AND DOES NOT MAKE THE SAME MISTAKE
THANKS
I'M SORRY FOR MY Inglish, USING GOOGLE TRANSLATOR
IF SO YOU FLASHER THE Atachment DE (GS4BUIL.PROP)
THAT POST IN FORUM ROMS? (CLEAN) FOR USERS GS4 ATT??
SORRY FOR THE QUESTION BUT I WANT TO INFORM YOU AS POSSIBLE ..... BUT MANY ARE NOT GUARANTEE AND DOES NOT MAKE THE SAME MISTAKE
THANKS
I'M SORRY FOR MY Inglish, USING GOOGLE TRANSLATOR
Ok so let me make sure I'm correct before I attempt this. I need to root, install ss and download the mf3 module. Then I can flash a rom and the mf3 module and all should be well, correct?
Make sure you create a rom-slot for flashing ROMs. Don't flash the stock-rom.
Here's the instruction from first post, also note that mf3 module is installed after the rom.
To sum it up and tweak your post a bit is as follows:
Root, install ss, flash your choice of rom that is compatible with SS and flash the mf3 kernel module last.
MDL baseband, not MF3
I saw this question before but didn't seem to be answered.
I never took the official MF3 update, still have the old mdl bootloader and I have Cleanrom 1.5 currently installed. Just debloated TW, nothing strange.
Can I use this to multiboot between cleanrom and a GPE or Cyanogenmod based roms in additional rom slots?
or does this depend on the MF3 bootloader and only works for those who accepted MF3 and are locked out of traditional custom roms?
Thank you very much in advance.
I saw this question before but didn't seem to be answered.
I never took the official MF3 update, still have the old mdl bootloader and I have Cleanrom 1.5 currently installed. Just debloated TW, nothing strange.
Can I use this to multiboot between cleanrom and a GPE or Cyanogenmod based roms in additional rom slots?
or does this depend on the MF3 bootloader and only works for those who accepted MF3 and are locked out of traditional custom roms?
Thank you very much in advance.
Did you flash the kernel that hash posted? Seeing if you did and still don't have wifi.
Sent from the other side of the Milky Way with my S4.
Last edited:
I have all of the needed downloads to be able to flash the GPE ROM onto my phone, just wondering is there any special way to flash a ROM on safestrap? If there is please explain it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I'm running the gpe and everything went smoothly in the install. Everything in the rom works great too including wifi, gps and bt.
Edit :well was working. I lost all sound for some reason after a reboot.
Sent from the other side of the Milky Way with my S4.
Edit :well was working. I lost all sound for some reason after a reboot.
Sent from the other side of the Milky Way with my S4.
Last edited:
How can I tell if my phone is encrypted and well this work with build MDB?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Settings-security. It will tell you there if it is encrypted or not. General rule of thumb-If you dont know if your phone is encrypted or not, it most likely isnt. If your phone is encrypted, it was you who did it. You would probably remember if you did or not.
I never missed around with security settings, except the unknown sources and lock screen security. Other then that, nothing else inside security settings.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
241*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
WARNING #1: CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
USEFUL LINK OF TW ROMS:
http://xdaforums.com/showthread.php?t=2616221
CURRENT PROJECT STATUS:
v3.72 (NB1): Beta testing, no rom-slots
v3.71 (MK2): Debugging some rom-slot issues
v3.65 (TW4.2): Stable
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
- Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
- You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
- Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
- Requirement: Root
- Requirement: Allow APK install from Unknown Sources
- Download the Safestrap APK
- Find the APK using a Filemanager tool and open it on your device, then click "Install".
- (If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
- Once installed, open up the Safestrap application as you would any other app.
- Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
- Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
- From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
- That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
HOW DO I UPGRADE SAFESTRAP?
- Push the APK up to your sdcard.
- Boot back into the "stock" rom-slot.
- Go into your old Safestrap app and use the "Uninstall Recovery" button
- THEN, open a "file explorer" of some sort (even TW "My Files" will work)
- Browse to where you pushed the APK
- Click on it and install like normal
- Once installed, open the APK
- Grant SU access
- Use the "Install Recovery" button
- All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
- [v3.72] ROM-SLOTs aren't supported yet
- [v3.72] "Reboot Recovery" doesn't work in the APK?
NEW TO v3.72:
- TWRP 2.7.0.x update for the base recovery. This includes vibration support, backup time/date fixes and more.
- ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY S4 (NOT THE ACTIVE MODEL)
MAKE SURE IF YOU ARE UPGRADING TO v3.7x FROM v3.65 THAT YOU USE THE "UNINSTALL RECOVERY" BUTTON IN THE v3.65 APK BEFORE INSTALLING v3.7x.
NOTE: USE ONLY ROMS THAT MATCH UP WITH YOUR TOUCHWIZ VERSION. IF YOU'RE ON MK2 THEN ONLY USE ROMS BASED ON MK2 AND IF YOU'RE ON MF3 ONLY USE ROMS BASED ON MF3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
FOR USERS OF NB1:
USE 3.72+:BETA Safestrap-JFLTE-3.72.apk (updated 2014-04-02)
FOR USERS OF MK2:
USE 3.71+:BETA Safestrap-JFLTEATT-3.71.apk (updated 2013-12-27)
FOR USERS OF MF3 (TW4.2):
LATEST FILE: Safestrap-JFLTEATT-3.65.apk (updated 2013-11-15)
Main XDA Downloads Page
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
ALSO DOWNLOAD THE KERNEL MODULES .ZIP THAT MATCHES YOUR BUILD # (FLASH THIS AFTER ROMS):
MF3: http://xdaforums.com/devdb/project/dl/?id=508
MK2: http://xdaforums.com/devdb/project/dl/?id=3275
HOW TO MANUALLY REMOVE SAFESTRAP:
[ INSTRUCTIONS ONLY FOR PRIOR TO v3.65. REMOVE VIA APK FOR v3.70+ ]
Enter adb shell from your pc:
Code:su mount -o remount,rw /system mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh rm -rf /system/etc/safestrap rm /system/etc/firmware/q6.mdt ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt mount -o remount,ro /system
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
This thread is a development ONLY thread.
For discussion go here:
http://xdaforums.com/showthread.php?t=2428254
XDA:DevDB Information
Safestrap Recovery v3.71 (JB) / v3.72 (KK), a Tool/Utility for the AT&T Samsung Galaxy S 4
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Stable Version: 3.71
Stable Release Date: 2013-12-27
Current Beta Version: 3.72
Beta Release Date: 2014-04-02
Created 2013-09-18
Last Updated 2014-04-0240Reserved
KNOWN ISSUES:
- Bluetooth remote control isn't working on rom-slots.
CHANGELOG:
[2013/11/13] TWRP updates
[2013/11/13] "toolbox" binary / symlinks in recovery fixed
[2013/11/11] Uninstall from the APK fixed
[2013/09/17] /sdcard mounting bugfix
[2013/09/17] Hijack improments to support default rootfs files
[2013/09/17] ROM-slot image creation bugfix for size > 2gb
[2013/09/12] Much improved block device handling
[2013/09/11] Bugfix in script translation
[2013/09/11] hijack / init.rc tweaks
[2013/09/11] Bugfix for display lag / buffering issue (WIP)
[2013/09/10] Adjust "ROM-slot" display in UI
[2013/09/10] /data/media handling changes
[2013/09/06] custom twrp.fstab files
[2013/09/06] /data/media handling changes38**Updated** Safestrap-I337-KitKat-v3.75 w/Working ROM Slots!
**No Mirrors Please** All precautions, limitations, and known issues stated in the OP still apply! Proceed to install and use at your own risk!
Current Version:
[11/15/2014] - Safestrap-I337-3.75-KitKat-A03.apk [NB1/NC1/NI1/NJ4] - Requires that you have BusyBox installed (make certain that you open the BusyBox app after downloading from the Play Store and actually install BusyBox!).
Instructions:
1. Uninstall previous Safestrap recovery version using the Safestrap app "Uninstall Recovery" function.
2. Uninstall the previous Safestrap app from your app drawer.
3. Go into SuperSu settings and "forget" the previous Safestrap version's root privileges.
4. Place the new Safestrap-I337-KitKat-3.75.apk onto your sdcard or extsdcard.
5. Install the new Safestrap-I337-KitKat-3.75.apk.
6. Locate and open the new Safestrap app from your app drawer and press "Install Recovery." Done!
Previous Versions:
[11/11//2014]Safestrap-I337-3.75-KitKat-A02.apk[NB1/NC1/NI1]
[10/19/2014] Safestrap-I337-3.75-KitKat-A01.apk [NB1/NC1/NI1]
[Initial Release] Safestrap-I337-3.75-KitKat.apk [NB1/NC1/NI1]
Changelog:
vA03 - [Current Version] Resolved issue where the Safestrap app would "force close" or fail to install after OTA updates. Setting SELinux to permissive is no longer required.
vA02 - Failed! -resolved "reboot from rom slot bug.
vA01 - Added Surge1223's feature setting selinux to permissive upon install and eliminating the need for the SELinux Mode Changer app.
v3.75 - Initial Release - Enabled ROM Slots.
Disclosures/Known Issues:
1) When powering down from the ROM running on a ROM slot the phone will hang. You must long-press the power button to shut down the device. I will debug as time permits.
2) Backups made with earlier Safestrap versions will not restore. You must make a new backup using v3.75.
3) Per Hashcode......."the system size is now not adjustable on 4.3. Samsung put in a verification that has issues if the partition size changes too much. So I opted to keep it exactly the same as stock."
This is a Development Thread! Therefore, please do not post comments related to ROM specific issues, favorite ROM's, that weird rash that won't go away, etc., in this thread. Please use the following thread in the General section for non-development related discussion: http://xdaforums.com/galaxy-s4-att/general/updated-safestrap-i337-kitkat-v3-75-rom-t2904854
Credits:
@Hashcode
@Surge1223 - vA0134Add the MF3 kernel module .zip to the "Downloads" section.
http://xdaforums.com/devdb/project/?id=680#downloads
Keep this on your SD card and flash it to the ROM-slot AFTER flashing a rom.
This will update your kernel modules to match the MF3 kernel and restore function to: wifi, bluetooth, gps etc.
